×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

indi 1.7.4 : possible small bug in skysensor

  • Posts: 56
  • Thank you received: 6
firstly great thanks to the team for latest release, I only got to try it this week and was very excited to see improvements that jumped out, several that were on my wish list:-
- camera temperature indication for Canon (would be great to have tickbox option to add this to filenames)
- better integration of lin_guider
- the pulse guide option for skysensor (not tested yet)

During first run of v1.7.4 with new Raspberrypi 3 using ubuntu mate, I noticed what might be a bug with skysensor slew control while following my normal workflow :-
1. connect skysensor, canon and lodestar guider, check focus, take some flats, start guide calibration - all OK
2. after starting guiding (lin-guider) on remote, I normally use client kstar to slew target using mouse select target, then right click option for skysensor 'slew' or use ekos mount control to move.

Here I got no slew and after setting debug I saw error reported in the remote indi.log

"Driver indi_lx200ss2000pc: indi_lx200ss2000pc dispatch error: Property EQUATORIAL_EOD_COORD is not defined in SkySensor2000PC.

after checking several options I also noticed any attempt at mount control using ekos 'keypad' or indi control panel motion control resulted also in this error

"Driver indi_lx200ss2000pc: indi_lx200ss2000pc dispatch error: Property TELESCOPE_MOTION_NS is not defined in SkySensor2000PC."

I can resolve the issue by clicking 'connect' in kstar (from right click then skysensor) - which is odd since I'm sure I was already connected.

The client kstars (log attached) from a daytime test run doesn't seem to record any errors like above.

I never noticed this before, maybe I've slipped somewhere but could somebody check? I can send skysensor logs if required.

thanks
Andrew
5 years 7 months ago #28377
Attachments:

Please Log in or Create an account to join the conversation.

Thanks. The logs already include skysensor responses. Can you delete the config file if present under ~/.indi and try again? These errors are quite odd.
5 years 7 months ago #28384

Please Log in or Create an account to join the conversation.

  • Posts: 56
  • Thank you received: 6
Thanks Jasem,

I deleted the Skysensor configs under /home/mate/.indi and restarted with same result. I've copied extract of log below with my edit of actions.

I think this is triggered by me not tracking anything i.e. in day testing mode I don't complete guide calibration, obtain target, focus, guide and track.
And it seems resolved if I right-click in KSTARS - Skysensor then Connect or go to EKOS and hit Connect - see below tracking starts and all seems OK:

The only other thing I noticed and it appears an irrelevant and known item, is the log reports an warning:
WARNING 317.448158 sec : Could not process mount date and time: 2018-08-10T

I'll do a full night test tonight with normal workflow to see if the issue is resolved.
Andrew


[AB added - output after setting new config for skysensor]

2018-08-10T09:05:56: Driver indi_lx200ss2000pc: read setSwitchVector SkySensor2000PC CONFIG_PROCESS Ok
CONFIG_LOAD='Off'
CONFIG_SAVE='Off'
CONFIG_DEFAULT='Off'
2018-08-10T09:05:56: Client 0: queuing <setSwitchVector device='SkySensor2000PC' name='CONFIG_PROCESS'>
2018-08-10T09:05:56: Client 0: sending msg copy 1 nq 1:
<setSwitchVector device="SkySensor2000PC" name="CONFIG_PROCESS" state="Ok" timeout="0" timestamp="2018-08-10T09:05:56">
<oneSwitch name="CONFIG_LOAD">
Off
</oneSwitch>
<oneSwitch name="CONFIG_SAVE">
Off
</oneSwitch>
<oneSwitch name="CONFIG_DEFAULT">
Off
</oneSwitch>
</setSwitchVector>

2018-08-10T09:06:16: Client 0: read newSwitchVector SkySensor2000PC ON_COORD_SET
SLEW='On'
2018-08-10T09:06:16: Driver indi_lx200ss2000pc: queuing responsible for <newSwitchVector device='SkySensor2000PC' name='ON_COORD_SET'>
2018-08-10T09:06:16: Client 0: read newNumberVector SkySensor2000PC EQUATORIAL_EOD_COORD
RA='1.69197'
DEC='1.23823'
2018-08-10T09:06:16: Driver indi_lx200ss2000pc: queuing responsible for <newNumberVector device='SkySensor2000PC' name='EQUATORIAL_EOD_COORD'>
2018-08-10T09:06:16: Driver indi_lx200ss2000pc: sending msg copy 1 nq 2:
<newSwitchVector device="SkySensor2000PC" name="ON_COORD_SET">
<oneSwitch name="SLEW">
On
</oneSwitch>
</newSwitchVector>

2018-08-10T09:06:16: Driver indi_lx200ss2000pc: sending msg copy 1 nq 1:
<newNumberVector device="SkySensor2000PC" name="EQUATORIAL_EOD_COORD">
<oneNumber name="RA">
1.69197
</oneNumber>
<oneNumber name="DEC">
1.23823
</oneNumber>
</newNumberVector>

2018-08-10T09:06:16: Driver indi_lx200ss2000pc: indi_lx200ss2000pc dispatch error: Property ON_COORD_SET is not defined in SkySensor2000PC.
2018-08-10T09:06:16: Driver indi_lx200ss2000pc: indi_lx200ss2000pc dispatch error: Property EQUATORIAL_EOD_COORD is not defined in SkySensor2000PC.


[AB added - after EKOS Mount Control motion arrow click ]

2018-08-10T09:07:57: Driver indi_lx200ss2000pc: indi_lx200ss2000pc dispatch error: Property TELESCOPE_MOTION_WE is not defined in SkySensor2000PC.
2018-08-10T09:07:57: Client 0: read newSwitchVector SkySensor2000PC TELESCOPE_MOTION_WE
MOTION_WEST='Off'
MOTION_EAST='Off'
2018-08-10T09:07:57: Driver indi_lx200ss2000pc: queuing responsible for <newSwitchVector device='SkySensor2000PC' name='TELESCOPE_MOTION_WE'>
2018-08-10T09:07:57: Driver indi_lx200ss2000pc: sending msg copy 1 nq 1:
<newSwitchVector device="SkySensor2000PC" name="TELESCOPE_MOTION_WE">
<oneSwitch name="MOTION_WEST">
Off
</oneSwitch>
<oneSwitch name="MOTION_EAST">
Off
</oneSwitch>
</newSwitchVector>
5 years 7 months ago #28436

Please Log in or Create an account to join the conversation.

Time to create page: 3.495 seconds