Rotator Timeout adjustable?

Perhaps the fault of the ASCOM driver, but with my DIY rotator I am seeing this:

[02/25/20 18:55:08.784][DEBUG][Telescope Thread][SQ;CE;] Performing auto center step 3 (rotator)…
[02/25/20 18:55:08.784][DEBUG][Telescope Thread][SQ;CE;] Moving rotator to 180.0…
[02/25/20 18:55:08.787][DEBUG][Telescope Thread][SQ;CE;] ASCOM Rotator: Moving rotator to 180
[02/25/20 18:55:08.787][DEBUG][Telescope Thread][SQ;CE;] ASCOM Rotator: Sync offset is -160527.244995117
[02/25/20 18:55:13.858][DEBUG][Telescope Thread][SQ;CE;] ASCOM Rotator: Error in Move(abs) : Timed out waiting for received data (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Runtime.InteropServices.COMException: Timed out waiting for received data
— End of inner exception stack trace —
at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, CultureInfo culture)
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 443)
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 483
at ASCOM.DriverAccess.Rotator.MoveAbsolute(Single Position) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Rotator.cs:line 105
at SequenceGenerator.AscomRotator.g8(Single A_0)
[02/25/20 18:55:13.858][DEBUG][Telescope Thread][SQ;CE;] Rotate failed…
[02/25/20 18:55:13.858][DEBUG][Main Thread][SQ;CE;] Adding sequence level notification: Rotate to reference failed.
[02/25/20 18:55:13.908][DEBUG][Telescope Thread][SQ;CE;] Sending Notification: Error - Rotate to reference failed.
[02/25/20 18:55:13.908][DEBUG][Telescope Thread][SQ;CE;] Auto center failed! Camera rotate failed.
[02/25/20 18:55:13.913][DEBUG][Telescope Thread][SQ;CE;] Close centering dialog…

however when the sequence recovers everything is fine without further rotation adjustment, so it seems like just a timeout problem.

This is SGP 3.1.0.452

Targets, with different rotator angles, are working fine, other than this issue which seems to happen at the start of the sequence each night.

That error is being thrown from inside of your ASCOM driver and SGP is merely logging it.

Once we start the move we also ask for the current position and a hunch would be that the driver is not protecting against any overlapping I/O on the serial port. Just a guess though.

Jared

OK thanks so much for looking into this.

I do have C# source code for the driver (I didn’t write it) so maybe I can figure something out.

It is an ASCOM hub, with PHD2 and SGP both connected.