Thanks Pablo, That’s good, it means that the log shows a good park and a failed park.
Yes Rob, what is happening is that PHD is sending guide commands to the mount while the park is in progress, this is what causes the park to fail.
PHD is under the control of SGP and I would expect that SGP would stop guiding and wait for it to stop before continuing with the park process. According to the log that was posted earlier SGP is only attempting to stop guiding after the park command has been sent.
[07/10/18 21:19:21.987][DEBUG] [Telescope Thread] ASCOM Telescope: Park message received.
[07/10/18 21:19:21.988][DEBUG] [Telescope Thread] ASCOM Telescope: Sending park…
[07/10/18 21:19:45.046][DEBUG] [PHD2 Listener Thread] Error: Guide star reported as lost!
[07/10/18 21:20:40.453][DEBUG] [PHD2 Listener Thread] Error: Guide star reported as lost!
[07/10/18 21:22:09.412][DEBUG] [PHD2 Listener Thread] Error: Guide star reported as lost!
[07/10/18 21:22:17.790][DEBUG] [Telescope Thread] ASCOM Telescope: Error in ParkTel! : 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.Telescope.Park() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Telescope.cs:line 728
at qr.br(String& A_0)
[07/10/18 21:22:17.790][DEBUG] [Telescope Thread] Error parking telescope: Error in Parking Telescope! See logs.
[07/10/18 21:22:17.791][DEBUG] [Telescope Thread] Attempting to stop PHD2 guiding…
[07/10/18 21:22:17.791][DEBUG] [Telescope Thread] Checking PHD2 state…
[07/10/18 21:22:17.791][DEBUG] [Telescope Thread] PHD2 GetPhdStatus - Pre-Wait : LostLock
[07/10/18 21:22:17.791][DEBUG] [Telescope Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}
It would help enormously if SGP were to be a little more helpful instead of leaving PHD to cope with the mount being pulled out of it’s control.
I can do things to prevent the guide commands from interfering with a park command but these will mean that PHD will get new errors when it tries to send guide commands.
This really needs to be fixed by SGP, their current behaviour is pretty hostile to the driver and other applications.