Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
I've been successfully using BYE and PHD2 in concert for Guiding and Dithering since early BYE v2 and PHDv1.12, and with BYE v3.12 and PHD2 v2.4 I've successfully imaged and Guided two separate Mounts simultaneously, so I know that it all DOES WORK.
But, I've been using the recently released PHDLogView App to review many of these successful Sessions, and I'm perplexed...
According to the Dither setting for SettleAt (defaulted to 0.25), many of my BYE Sessions would have NEVER resumed Imaging after most of the Dithers as per the PHDLogViewer (using the Settings/Exclude Settling Parametrically and the Exclude Frames Settling settings that match those used in BYE) the Excluded-for-Settling portion often runs for several minutes at "0.25 pixels".
So, that leads me to ask: Does BYE implement the two components of "Settle" sequentially (as indicated in the "Debunking Dithering" HowTo) or are they evaluated simultaneously ?? All my experience sitting in front of BYE for whole Nights at at time say they are evaluated sequentially.
But then, the PHDLogViewer App was written by one of the lead OpenPHD Devs, and we'd assume that it is also correctly interpretting the evidence in the Log Files. And that indicates otherwise...
So, can you confirm which PHD API Property/Value is being evaluated for the Settle Distance ??
(I've posted an equivalent question on the OpenPHD forum in this Thread... )
Link to comment
Share on other sites
12 answers to this question
This topic is now archived and is closed to further replies.