As Bryan said, these are NINA logs and they don’t appear to cover the time period you’re talking about. The messages aren’t coming from PHD2 – PHD2 pays no attention to tracking, has no code to turn it on or off, and never synchs the scope. I think it’s more likely the messages are coming from the ASCOM mount driver but the real question will be why tracking was disabled and what application disabled it. One possibility is that you hit a meridian limit setting of some kind that the imaging app (NINA) wasn’t aware of. I’m willing to help you analyze log files from these other applications but you will need to post the correct ones for the situation you encountered. Automated imaging is a fairly complex process so over time you will probably get the hang of knowing what apps are generating messages, where their log files are stored, and how to look at the logs to at least identify the “simple” problems.
Regards,
Bruce
--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/79ae512c-e33b-41e9-b7c6-66e7d85bb051n%40googlegroups.com.