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.
Sharpcap/mount issues that have suddenly cropped up
- admin
- Site Admin
- Posts: 17573
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Sharpcap/mount issues that have suddenly cropped up
Hi,
I can fill in some info that might help when looking for the cause, but I don't have an exact answer...
Checking that the mount actually went to the position that SharpCap asked it to is a relatively new thing (last 6 or 9 months or so). Before, SharpCap just assemed the mount did what it had been asked, but we encountered cases where GOTOs would be wrong and on further digging it turned out that the mount was doing the same sort of thing as yours - not ending up at the requested location.
I suspect that the place you need to look is in the settings for your Skywatcher ASCOM driver (or, if you are using the Synscan App driver, the settings in the Synscap App). It may be that you have enabled a pointing model and that it has bad data stored, or similar.
One thing to note is that you can test this sort of problem without needing to wait for dark skies, since the issue is an inconsistency between where the mount is asked to go and where it ends up. That at least helps with the troubleshooting.
cheers,
Robin
I can fill in some info that might help when looking for the cause, but I don't have an exact answer...
Checking that the mount actually went to the position that SharpCap asked it to is a relatively new thing (last 6 or 9 months or so). Before, SharpCap just assemed the mount did what it had been asked, but we encountered cases where GOTOs would be wrong and on further digging it turned out that the mount was doing the same sort of thing as yours - not ending up at the requested location.
I suspect that the place you need to look is in the settings for your Skywatcher ASCOM driver (or, if you are using the Synscan App driver, the settings in the Synscap App). It may be that you have enabled a pointing model and that it has bad data stored, or similar.
One thing to note is that you can test this sort of problem without needing to wait for dark skies, since the issue is an inconsistency between where the mount is asked to go and where it ends up. That at least helps with the troubleshooting.
cheers,
Robin