Closed xthestreams closed 4 years ago
Can you enable INDI+Dome logging and share these. I just tested with simulators again and I cannot reproduce this behavior. The dome was following the mount motion during GOTOs and also while tracking. I kept it now for 2 hours and the Dome Simulator behaves normally.
I can only imagine your frustrations! I left the dome synched and running for a while, that's what you can see right before I press "Abort" - prior to that teh dome had been at 73" which was where the scope was pointing when EKOS was started.
[2020-08-04T11:01:47.600 AEST DEBG ][ org.kde.kstars.indi] - Paramount : "[DEBUG] RES: 11.788374102948339,-15.48422212877864|No error. Error = 0. "
[2020-08-04T11:01:47.602 AEST DEBG ][ org.kde.kstars.indi] - Paramount : "[SCOPE] Current RA: 11:47:18 Current DEC: -15:29:03 "
[2020-08-04T11:01:48.601 AEST DEBG ][ org.kde.kstars.indi] - Paramount : "[DEBUG] CMD: / Java Script /var Out;sky6RASCOMTele.GetRaDec();Out = String(sky6RASCOMTele.dRa) + ',' + String(sky6RASCOMTele.dDec); "
[2020-08-04T11:01:51.734 AEST DEBG ][ org.kde.kstars.indi] - Paramount : "[DEBUG] RES: 11.788374247628994,-15.484228199712987|No error. Error = 0. "
[2020-08-04T11:01:51.734 AEST DEBG ][ org.kde.kstars.indi] - Paramount : "[SCOPE] Current RA: 11:47:18 Current DEC: -15:29:03 "
[2020-08-04T11:01:52.734 AEST DEBG ][ org.kde.kstars.indi] - Paramount : "[DEBUG] CMD: / Java Script /var Out;sky6RASCOMTele.GetRaDec();Out = String(sky6RASCOMTele.dRa) + ',' + String(sky6RASCOMTele.dDec); "
[2020-08-04T11:01:54.001 AEST DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] Processing event
I've trimmed a third iteration of the "abort" sequence" from my testing. From what I can see below, it would appear that there is no "STOP" event - which is consistent with the published API. Instead a SER event is issued with the estimated AZ of the dome - in essence the driver is waiting for a message that never comes.
[2020-08-04T11:37:17.627 AEST DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] CMD <@SWR> "
[2020-08-04T11:37:17.678 AEST DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <:SER,10863,0,55080,28228,300> "
[2020-08-04T11:37:17.680 AEST DEBG ][org.kde.kstars.ekos.observatory] - Setting dome status to 0
[2020-08-04T11:37:17.680 AEST INFO ][org.kde.kstars.ekos.observatory] - "Dome is idle."
[2020-08-04T11:37:17.909 AEST DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] Processing event <:SWR#> with value
I've had a detailed look at the logs and the command/event protocol for the dome and it appears that the driver is waiting for a response that never comes. I have tried changing the STOP command text to be the SER, text but this has not helped, so perhaps the bug lies deeper as Jassem suggests. As soon as Abort is issued the driver returns to an "IDLE" state and starts responding to commands again - I'd love to find a simple workaround but most of the logic hacks I have tried have not worked.
do we think it might have something to do with the fact that Nexdome can issue asynchronous status messages?
Best thing right now is to set teamviewer and send me credentials so I can login and debug this directly there. Send credential to support@stellarmate.com
are you saying my coding skills are terrible?! ;-) happy to do so, I would much rather solve problems than create problems, but I'm still feeling my way around the INDI codebase and re-learning C++ so probably not the best person to be messing around.
Sent!
I actually didn't receive anything yet, please resend.
just resent
This specific issue should now be fixed with the latest changes.
working great! @knro I don't know how to thank you enough!
Describe the bug In indi_nexdome, per the thread on INDI forum, the following bug appears to be specific to the Nexdome driver - taken from MarkG's original post
https://indilib.org/forum/general/6272-nexdome-driver-will-not-slave-dome-without-abort-press.html
Per Jassem's concern re: the base class, there appears to be a second bug with the Simulator whereby it does not slew at all until EKOS is disconnected and re-started.
To Reproduce Exact steps to reproduce the behavior. "The dome will move to slave one time after unparking the mount but not after that. Also the manual CCW and CW buttons in the driver will work once only. Until, that is, the abort button is pressed, where the dome will then move to the correct mount azimuth. Similarly the CW & CCW buttons will again move the dome once, after each abort button press."
Expected behavior The dome should slew as teh mount changes azimuth angles.
Screenshots N/A - a movie can be provided if required.
Desktop (please complete the following information):
Log Files Make sure to enable logging and include log files https://indilib.org/support/logs-submission.html