Hi Jasem,
It looks like the scheduler is working now, as far as I have tested it so far. Thanks to you and Eric for that hard work!
But I wonder whether something happened to the Guide Module during the update. That seems to be out of whack now.
I ran my Messier Marathon schedule last night and it started picking off one target after the other rather nicely, tracking, focusing, aligning all went fine. However, when it came to initiating autoguiding (using the internal guider, not PhD2), it would fail to clear the calibration and instead use the previous guide star window (the green box, set to 32) for guiding, although that would now point to empty space. Only after about a dozen failed attempts would the module then select a new guide star and guiding would work fine from then. However, by that time the object that was previously perfectly aligned in the center of the frame would have drifted uncontrollably, usually now to the edge of the frame, basically destroying the usability of that image sequence. To recalibrate the mount, I had to manually clear the calibration data every time, it no longer happened automatically.
Moreover, instead of waiting for the guide module to settle on a new guide star, the capture module now starts to expose prematurely while the mount is still drifting, making for interesting zigzags in the first image of the sequence.
Then after performing a meridian flip another problem surfaces: Instead of swapping the calibration or recalibrating, the guide module now apparently uses the old calibration data, which then sends the mount way off course and results in huge errors.
The log file is too large to attach, I have put it into my Dropbox. You can download it here:
www.dropbox.com/s/884hw5e8b0vw3oc/log_21-28-55.txt?dl=0
It looks pretty chaotic to me. I would have thought that the guide module would work independent of the scheduler?
Thanks for looking into it. Let me know if I can do anything to help.
Jo