It may be down to the communication with the SE mount being slow sometimes? Quite why the sync sometimes completes quickly and sometimes takes long enough to cause the ASCOM drivre to time out is unfortunately impossible to tell. In the non-error ASCOM log, you can see that the sync process takes about 0.3s, so quite a difference. ![]() In the corresponding point in the ASCOM log (00:21:48.425), you can see that the ASCOM driver asks the main CPWI program to run the sync process and doesn't get a response - in fact it seems to create the error after about 2s waiting for a response. Thanks for capturing all the logs - looking at the SharpCap / ASCOM ERROR logs, you can see that the CPWI ASCOM driver once again gave an error for the sync request in the SharpCap log.
0 Comments
Leave a Reply. |