Sorry I neglected to mention the nontypical port number. I forgot because I use an alias to issue the command.
When you opened port 22 did you also reconfigure sshd to listen on 22?
The port is not blocked by the OS by default. More likely, you are encountering a block on a router between you and the device.
We're at the limits of my knowledge. I don't know if Ekos and the mount communicate regarding geographic position. I can imagine a scenario where they could properly sync on a target without agreeing on the geographic position of the mount, and thus when the meridian flip is necessary.
Looking at the manual, I see that the EQ6-R does not have a GPS. "At the end of the initialization of the SynScan hand control, after entering the proper local longitude, latitude". If you did not do this at least once after receiving the mount back perhaps it doesn't have the right coordinates?
Is that consistent with the hour angles reported in the log?
[2022-01-07T22:18:15.321 EST DEBG ][ org.kde.kstars.ekos.mount] - Meridian flip planned with LST= "05h 14m 20s" scope RA= "05h 08m 19s" ha= 0.10045 , meridian diff= 0.1 , hrstoFlip= -0.000449513 , flipDelayHrs= 0 , "Pier Side: West (pointing East)"
[2022-01-07T22:19:13.536 EST INFO ][ org.kde.kstars.ekos.mount] - Meridian flip: slewing to RA= "05h 08m 02s" DEC= "-03° 18' 47\"" Hour Angle "00h 00m 29s"
[2022-01-07T22:19:31.942 EST DEBG ][ org.kde.kstars.ekos.mount] - Meridian flip planned with LST= "05h 15m 37s" scope RA= "05h 08m 02s" ha= 0.126487 , meridian diff= 0.1 , hrstoFlip= -0.0264867 , flipDelayHrs= 0 , "Pier Side: West (pointing East)"
[2022-01-07T22:19:32.929 EST INFO ][ org.kde.kstars.ekos.mount] - Meridian flip: slewing to RA= "05h 08m 02s" DEC= "-03° 18' 47\"" Hour Angle "00h 00m 30s"
[2022-01-07T22:35:12.340 EST DEBG ][ org.kde.kstars.ekos.mount] - Meridian flip planned with LST= "05h 31m 20s" scope RA= "05h 19m 44s" ha= 0.1935 , meridian diff= 0.1 , hrstoFlip= -1.89019e-05 , flipDelayHrs= 0.093481 , "Pier Side: West (pointing East)"
[2022-01-07T22:38:04.617 EST INFO ][ org.kde.kstars.ekos.mount] - Meridian flip: slewing to RA= "05h 08m 03s" DEC= "-03° 18' 47\"" Hour Angle "00h 01m 45s"
(Were the mount and Ekos in agreement on the geographic location of the mount?)
My guess is that you hadn't yet tracked far enough past the meridian for the mount to switch to the east side when it received a goto command from Ekos.
I removed the astrometry driver from my equipment profile. Curiously, it was still showing up when I started Ekos. I had to reboot the Stellarmate to have this change take effect.
After the remote astrometry drive was removed, Ekos no longer offers the astrometry tab unless the camera is present. When the camera is present, the four-click sequence does not crash.
Nonetheless, it would be good if KStars did not crash in the situation of my original configuration.
Thank you for your reply.
The astrometry driver is a legacy of my original setup. I didi not think to remove it but will do so.
The camera is not showing up because it is unplugged when my scope is in the garage. Of course a camera is necessary to solve, but KStars shouldn't crash if one isn't available.
I do not have log files to offer, but if you are unable to reproduce the crash just let me know what you need and I'll get them for you.
I have a ZWO ASI6200MC camera. For a recent image, the FITS file contained an astrometric solution and also notes that the data are to be interpreted top-down. FITS header excerpt:
ROWORDER= 'TOP-DOWN' / Row Order RA = 2.336768E+01 / Object J2000 RA in Degrees DEC = 3.063624E+01 / Object J2000 DEC in Degrees CROTA1 = 2.4249720376E+02 / CROTA1 CROTA2 = 2.4249720376E+02 / CROTA2
. Excerpt from crash report below.
Kstars 3.5.5. Build: 2021-09-15T21:27:44Z