Hello,
I use the MOUNT SOLVESYNCONLY command at startup because my wired mount has no clue where it is when it starts...
In the past, it worked well, but recently, it has stopped working with an error saying that the mount was too far from the calculated position (or something that extent).
How do I bypass this error and force sharpcap to tell the mount where it is even if the mount currently think that it is far away from it?
Thanks,
Cyrille
Issue with MOUNT SOLVESYNCONLY
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
- admin
- Site Admin
- Posts: 17526
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Issue with MOUNT SOLVESYNCONLY
Hi,
this was a deliberate update to avoid the potential for a rogue plate solve result to mis-align the mount without any warning when used from the sequencer (using it from the UI already had safeguards). This problem had arisen and caught some people out. I think the offset limit is 5 degrees, so if you are within that then all will be fine, but outside that you will get the error.
To bypass the checks, use the following two steps...
'Plate solve and save co-ordinates'
'Sync the mount to a set of co-ordinates that were previously saved'
Using those two separate steps should work without any checks or errors.
thanks,
Robin
this was a deliberate update to avoid the potential for a rogue plate solve result to mis-align the mount without any warning when used from the sequencer (using it from the UI already had safeguards). This problem had arisen and caught some people out. I think the offset limit is 5 degrees, so if you are within that then all will be fine, but outside that you will get the error.
To bypass the checks, use the following two steps...
'Plate solve and save co-ordinates'
'Sync the mount to a set of co-ordinates that were previously saved'
Using those two separate steps should work without any checks or errors.
thanks,
Robin
-
cyrille.de.brebisson
- Posts: 75
- Joined: Sun Oct 01, 2023 4:42 pm
Re: Issue with MOUNT SOLVESYNCONLY
When I saw the error, I immediately assumed that this was the reason...
Thank you for your prompt answer, especially as you provided a solution !
Cyrille
Thank you for your prompt answer, especially as you provided a solution !
Cyrille