Switches Left On After Abort

Sequence Generator
1

Hi Ken,

Minor item, but the switches were left on after a meridian flip abort due to guide star lost. The dome was properly closed and mount parked with equipment disconnected as expected; Log at:

https://www.dropbox.com/scl/fi/inzoem4xka6rb50pcswdi/sg_logfile_20241108180736.log?rlkey=lrlyk4n2p7vcs0o9xrujbw3vw&dl=0

Regards,
Kent

2

Thanks for the report. I’ll look into a bit deeper, but at first glance, it seems that SGPro did set the end of sequence switch state and received no errors while doing so.

[11/08/24 23:52:12.220][DEBUG][Main Thread][NONE] Adding sequence level notification: End of sequence actions completed and end of sequence switch state has been set.
3

Hi Ken,
I have another instance of this issue if it’s of any help. Log:

https://www.dropbox.com/scl/fi/xjlrp2ggom225z0t99ltt/sg_logfile_20241110193220.log?rlkey=5idmqrqxq7znyqpvracci2ne8&dl=0

Regards,
Kent

4

Im unsure. There is no evidence of an issue from SGPro’s perspective. It sets the state and receives no errors.

[11/10/24 23:22:19.917][DEBUG][Main Thread][NONE] Adding sequence level notification: End of sequence actions completed and end of sequence switch state has been set.

What you could do here to get additional data is collect the switch device’s side of the story by grabbing the corresponding ASCOM trace logs. From this we could tell if the switch receives the command, what the command is and if there were any errors within the driver (maybe).

Additional guidance here: How to Generate ASCOM Trace Logs