Sharpcap/mount issues that have suddenly cropped up
Posted: Thu Mar 05, 2026 7:52 am
Hello,
I’m using a Sky-Watcher EQM-3 Pro mount with a Sky-Watcher Evostar 62ED refractor, SharpCap, ASCOM 7.1 plus Sky-Watcher drivers, and an ASI335MC camera.
The system has been working reliably until my first session since the new year. I haven’t changed any hardware or software that I can detect, but now when I ask SharpCap to “Go To” an object from the database it slews and plate-solves to correct, then moves to the corrected position and reports:
“Move to RA/Dec Position — The mount failed to arrive at the target co-ordinates (off by 3.3°). Expected to arrive at RA=07:27:25.0, Dec=+22:10:20, but mount finished slewing at RA=07:14:01.2, Dec=+23:10:58.”
If I re-plate-solve (even though it’s dead on the object visually) it still sees a ~3.3° error and then slews another 3.3° away from the target. I’ve power-cycled everything with no change — the offset magnitude can vary slightly but the problem persists, always in the same direction.
Has anyone seen this strange, consistent offset behavior? Any suggestions for debugging or possible causes would be appreciated.
I’m using a Sky-Watcher EQM-3 Pro mount with a Sky-Watcher Evostar 62ED refractor, SharpCap, ASCOM 7.1 plus Sky-Watcher drivers, and an ASI335MC camera.
The system has been working reliably until my first session since the new year. I haven’t changed any hardware or software that I can detect, but now when I ask SharpCap to “Go To” an object from the database it slews and plate-solves to correct, then moves to the corrected position and reports:
“Move to RA/Dec Position — The mount failed to arrive at the target co-ordinates (off by 3.3°). Expected to arrive at RA=07:27:25.0, Dec=+22:10:20, but mount finished slewing at RA=07:14:01.2, Dec=+23:10:58.”
If I re-plate-solve (even though it’s dead on the object visually) it still sees a ~3.3° error and then slews another 3.3° away from the target. I’ve power-cycled everything with no change — the offset magnitude can vary slightly but the problem persists, always in the same direction.
Has anyone seen this strange, consistent offset behavior? Any suggestions for debugging or possible causes would be appreciated.