Riger Systems Auto Focus Fail

at as.GetCurrentPosition(Boolean force)
[6/10/2014 6:44:56 AM] [DEBUG] [Camera Thread] AF abort requested
[6/10/2014 6:44:56 AM] [DEBUG] [Camera Thread] Resuming auto guiding (settling)…
[6/10/2014 6:44:56 AM] [DEBUG] [Camera Thread] PHDA resuming…
[6/10/2014 6:44:56 AM] [DEBUG] [Camera Thread] PHDA: Sent command (PHD_GETSTATUS)…
[6/10/2014 6:44:56 AM] [DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_ABS message received…
[6/10/2014 6:44:56 AM] [DEBUG] [Focuser Thread] Focuser moving to 7459
[6/10/2014 6:44:56 AM] [DEBUG] [Camera Thread] PHDA: Received (100)…
[6/10/2014 6:44:56 AM] [DEBUG] [Camera Thread] PHDA: Sent command (PHD_RESUME)…
[6/10/2014 6:44:56 AM] [DEBUG] [Camera Thread] PHDA: Received (0)…
[6/10/2014 6:44:56 AM] [DEBUG] [Focuser Thread] ASCOM Focuser: Error in Move(abs) : MoveThe focuser cannot be moved while temperature compensation running
at ASCOM.Interface.IFocuser.Move(Int32 val)
at SequenceGenerator.SafeFocuser.Move(Int32 val)

Last night I turned on temperature compensation inside the ASCOM driver and ended up with it freezing the focuser dialog. Would this be similar to the backlash problem?

My preference for something like this would be a watchdog. If a process takes too long, something has happened, and it could fail out gracefully, park the mount/close the roof.