Several posts back and forth to Ascom, Bisque, and ACP are now to this point:
The failure occurs when ACP is in a Refresh loop to update the status of the Main screen. Basically, it is checking the current RA/Dec of the scope, whether Tracking and Slewing are active. In the course of checking this, the SkyX scripting object gives the error “Process Aborted. Error – 212” and stops. ACP then disconnects from the scope. The Phase 3 has to do with where ACP is in the refresh process.
So, back to Bisque – what does error 212 mean?
Of course, I cannot get the failure to occur anymore. I am suspicious that the error occurs when a plate solve is successful, which of course isn’t happening now. I am running inside with the roof closed since it is still cloudy.
I added Pipe to the driver stack, so the various scope commands are being logged to the file Pipe.log in Common Files.Ascom/Telescope. If I can ever get it to faill again, perhaps I will have more information for Bisque.