NOTE: The Nexdome and CEM120 was working fine with KStars 3.5.2 - as far as synced slaving was concerned.I just updated to the stable release of 3.5.3, and now my Nexdome has a new problem.When I HOME my CEM120 mount - which of course is ZERO degrees azimuth, the Nexdome driver thinks it is at 90 degrees!If I move my mount to any location OTHER than home, the dome does slave to the correct spot and tracks. But as soon as I direct my mount to slew and locate the HOME position - (90 DEC, 00 degrees Az), the Nexdome driver rotates to 90 degrees Azimuth instead of zero.Is it looking at the mount's DEC and using that as the Azimuth direction?
LOG excerpt shows the dome calculating the wrong azimuth after the mount slews to home (0 degrees azimuth):
Go back to previous version, if all was good why did you update....?
Stellarmate OS on Raspberry pi4b
Skywatcher EQ8 pro, on steel pier
Takahashi FSQ85, FS60cb & Meade 8” SCT (de-forked)
Starlight Xpress SXVR H18, SXVR M25c, Lodestar x2 Guide Camera
Pegasus Ultimate Hub V2 for all USB & Power
Pegasus focus motors on all scopes
I reinstalled everything to the latest stable again, and the issue is still there. The dome continues to think zero azimuth is 90 degrees.
I still do not know how to go back to 3.5.2, but that wont solve the issue going forward as new releases are published.
Does anyone have any idea what is happening to cause this error?
iOptron CEM120 EC2 and CEM25P
Celestron C11 EdgeHD
William Optics Star71
ASI 1600Mm Pro, ASI 462MC
Moonlight motorfocus & Esatto focuser
LodeStar X2 and ZWO OAG