Just tested the new version out with my capture and meridian flip code. Guiding seemed to show the right messages, in the PHD2 status bar and I could also see the method invocation traffic in the PHD2 log that seemed to be doing something appropriate. I noticed SharpCap (I think) was requesting a the lock position and then issuing a find star request.
Very nice. Thanks for fixing this so quickly. Now I can sleep through meridian flips! Let me know if there are any other aspects of this guiding code update you would like me to exercise.
It looks like SharpCap might have been sending find star requests after large slews too, not just when the pier side changed. I was a little unsure of the timestamp when this occurred, so I wasn't sure I was looking at the right place in the PHD2 log. PHD2 logging is super verbose, so even when I limit myself to examining only "evsrv" lines, its still pretty confusing.
Guiding: PHD2 attempts to use the same guide star after a slew
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
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
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
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
-
lowenthalm
- Posts: 224
- Joined: Mon May 07, 2018 12:27 am
-
admin
- Site Admin
- Posts: 17539
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Guiding: PHD2 attempts to use the same guide star after a slew
Hi,
good to hear that it worked
On the potentially extra requests to find a guide star, the logic at the moment is
* Ask PHD for the lock position
* If the lock position is missing/invalid or the 'refind' flag is set, request PHD to find a guide star.
The 'refind' flag is set when the mount changes side of pier. In theory there are 3 sides of pier - EastLookingWest, WestLookingEast and 'Unknown'. If your mount ASCOM driver reports the 'Unknown' side at any point then that could end up setting the flag, causing a refind of a guide star at the next point that guiding is requested. You could imagine that an ASCOM driver might report 'Unknown' when parked or in some other special circumstances maybe?
cheers,
Robin
good to hear that it worked
On the potentially extra requests to find a guide star, the logic at the moment is
* Ask PHD for the lock position
* If the lock position is missing/invalid or the 'refind' flag is set, request PHD to find a guide star.
The 'refind' flag is set when the mount changes side of pier. In theory there are 3 sides of pier - EastLookingWest, WestLookingEast and 'Unknown'. If your mount ASCOM driver reports the 'Unknown' side at any point then that could end up setting the flag, causing a refind of a guide star at the next point that guiding is requested. You could imagine that an ASCOM driver might report 'Unknown' when parked or in some other special circumstances maybe?
cheers,
Robin