Hi,
can someone explain whats the diffrent between plate solve only (only solution) and plate solve (resynchronisation)? I want to sync with my mount, but this diesent work, only plate solve only. Is there a wrong setting? It doesent matter if i user the sharpcap plate solving or ASTAP.
I want to unterstand why the first one works finde, and the secone one failed.
Thanks.
Problem with Plate Solving
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
-
archer1960
- Posts: 98
- Joined: Sun Feb 23, 2025 9:04 pm
Re: Problem with Plate Solving
What kind of mount do you have? Some mount drivers will refuse a sync command, mostly high-end ones that use an internal sky model like Planewave, Astro-Physics, etc.
- admin
- Site Admin
- Posts: 17526
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Problem with Plate Solving
Hi,
@archer1960 is right that some sorts of mount will refuse to accept a sync request, but I think your problem is happening before we even get to that stage - the plate solve is failing for 'solve and sync', but not for 'solve only'.
The likely cause of this is that the 'solve and sync' operation restricts the plate solve search to within 15 degrees of the current mount position - this speeds things up and is usually a sufficiently large area to find the right location even if the mount position is a bit off. The 'solve only' operation instead will try to search the whole sky.
Given this, it seems very probable that your mount co-ordinates are actually incorrect by some considerable amount (more than 15 degrees) - possibly because the mount has become confused about the home position or some alignment stage has not been completed or went wrong. You can see the co-ordinates calculated by plate solving in the second screenshot - at a declination of +85, this is close to the North celestial pole. Compare those to the mount position readout in the mount section on the right hand side to see if there is a large deviation.
You can go to the SharpCap settings and in the 'Plate Solving' tab increase the area that the 'solve and sync' operation will search - taking this all the way up to 180 degrees will mean that the 'solve and sync' will search the whole sky, which will probably resolve the immediate issue (and the sync may put the mount co-ordinates to the correct values - if the ASCOM driver for the mount will accept a sync that requires such a big correction - some will not).
Hope this helps,
Robin
@archer1960 is right that some sorts of mount will refuse to accept a sync request, but I think your problem is happening before we even get to that stage - the plate solve is failing for 'solve and sync', but not for 'solve only'.
The likely cause of this is that the 'solve and sync' operation restricts the plate solve search to within 15 degrees of the current mount position - this speeds things up and is usually a sufficiently large area to find the right location even if the mount position is a bit off. The 'solve only' operation instead will try to search the whole sky.
Given this, it seems very probable that your mount co-ordinates are actually incorrect by some considerable amount (more than 15 degrees) - possibly because the mount has become confused about the home position or some alignment stage has not been completed or went wrong. You can see the co-ordinates calculated by plate solving in the second screenshot - at a declination of +85, this is close to the North celestial pole. Compare those to the mount position readout in the mount section on the right hand side to see if there is a large deviation.
You can go to the SharpCap settings and in the 'Plate Solving' tab increase the area that the 'solve and sync' operation will search - taking this all the way up to 180 degrees will mean that the 'solve and sync' will search the whole sky, which will probably resolve the immediate issue (and the sync may put the mount co-ordinates to the correct values - if the ASCOM driver for the mount will accept a sync that requires such a big correction - some will not).
Hope this helps,
Robin