Focuser not moving to correct location causing sequence abort

Last night my sequence was aborted. It appears to be related to the focuser not moving to the correct location. Running 4.4.1.1441

I saw the following in the log during the evening regarding auto focus notifications.

at 12/19/25 23:07:06 I got a warning that the HFR was not what it was expected to be. The sequence continued.

at 12/20/25 03:34:35 I got a timeout error that the focuser was trying to get to 17074 but was reporting 17113. The sequence continued

at 12/20/25 03:34:44 I got a warning that the HFR was not what it was expected to be. The sequence continued.

at 12/20/25 03:35:54 I got a timeout error that the focuser was trying to get to 17074 but was reporting 17113. The sequence continued

at 12/20/25 03:37:01 I got a timeout error that the focuser was trying to get to 17074 but was reporting 17113

at 12/20/25 03:37:01 The sequence was aborted

Here is the link to the log file:

I have been using this system for about 3 months and never seen these errors or had this type of abort. I am not at all sure if this is a hardware issue or a software issue. Any thoughts about possible causes would help a lot.

For issues like this SGPro does not ever have the full story because it only asks the focuser to move somewhere and then the actual execution of that move is deferred to the ASCOM driver. In this case the driver never emits an error but at the same time either misreports its position of failed to move. If this continues to happen, the path forward is to also capture the corresponding ASCOM focuser logs so we can take a look at the other half of the story here.

In general though, we see more of these issues in the winter (not sure what hemisphere you are in) especially when many devices are controlled via a single USB hub. When the hub gets cold the connectors shrink at different rates than the cables and things can get squirrely *power as well).

Here is some guidance on how to capture ASCOM device logs