I am SO GLAD your guiding is working!!

There are a couple of things to note:

1. The first failure in the log occurred at 10:40:00 exactly (odd), and immediately after ACP told TheSky to start a slew:

10:39:41 Do periodic or plan-start auto-focus...
[...]
10:39:54 Using star at mag 4.5. Slew to star.
10:39:54 Start slew to AutoFocus...
10:39:59 (wait for slew to complete)
10:40:00 [**HARDWARE OR DRIVER ERROR**]
10:40:00 [Source: System.Dynamic]
10:40:00 [Object reference not set to an instance of an object.]
10:40:00 [This is not an ACP problem]
10:40:00 **Script Error**
10:40:00 Source: ACP
10:40:00 Message: The telescope is not connected.
10:40:00 Location: line 1632 column 33.


2. The screen shots appear to be taken an hour later, (starting at 11:11:04 UTC) probably when you discovered the problem and tried to re-connect ACP.

3. It's hard to read, but the errors in the ACP console on the screen shots appear to show the tail end of the same sequence of error messages.

The key clue is the highlighted line showing the source of the error to be System.Dynamic. This is an earmark of a problem coming from TheSky. Here are a couple of identical reported errors (here we see the value of the Comm Center)

Hardware or Driver Error System.Dynamic error likely caused by activity in TheSkyX

Startup with TheSky: Mount hardware error on first autofocus / slew

They are reporting the identical issues and each contain some things to check. Unfortunately, both of these were inconclusive other than neither party had reported back with more problems.

Colin or Paul, have you seen any more of these errors coming from TheSky when starting a slew?