rumengb
commented
1 month ago Hi, Your log is partial and I do not see the mount model. What mount are you using? However, the log shows no driver issue. This overshooting behavior is normal. Some mounts (especially the budget ones) overshoot and then return to the desired position. The simulator does not do this. Please note that the driver does not control the mount motors. It is the mount firmware that does it. The driver only issues commands like "goto X Y" and waits for the response that the operation is complete or failed. How it would be executed is a responsibility of the firmware. When it comes to the last slew when the mount remains offset in RA, it is not a driver issue too. The log clearly shows that the driver asked the mount to go to 6.89211h but the mount decided to stop at 6.94316h and reported that the slew is complete. So it is likely a firmware issue.
Rumen
wgoltz
I have observed Mount Nexstar GOTO's stopping in unexpected places. I have studied this using Skychart (Carte du Ciel) program and its "telescope->slew to chart center" function, and created an Indigo trace log showing the 4 telescope goto commands that were traced.
(for a starting position looking West in southern hemisphere, image aligned N top, W right)
Case 1, moving to the top left : the telescope goes through the desired new position, but then overshoots in both RA and Dec before returning to desired position.
Case 2 moving to top right : the telescope moves to the desired position, but then overshoots in Dec before returning to desired position.
Case 3 moving to bottom right : the telescope moves to desired position with no overshoot.
Case 4 moving to bottom left : the telescope moves to the desired position, but then overshoots in RA. It does not return to the correct position and remains offset in RA.
I have not seen any strange behaviour using the Mount Simulator driver using Skychart, so infer that this is a problem with the Mount Nexstar driver rather than with Skychart.