Did anybody else noticed the change in behavior when executed manually (from Imaging tab) or if it's triggered from sequencer?
Very often I am having issues when executing autofocus from sequence at various stages. When I trigger it from HFR or temperature change I often see errors (see below log from N.I.N.A which seems the issue is from ASCOM driver) and is aborted - it will re-try the autofocus next image which may or may not succeed. This re-tries can take quite some time from imaging. Yesterday I noticed also during the filter switch it just aborted after first two autofocus movements but without error.
I don't understand why would this happen, because I tried to execute it manually and I didn't see any issues at all in quite some tests. Are there any other settings for delays or something else for sequencer? I assume the 'autofocus' in sequencer is the same as it's executed in Imaging tab (hocus focus) as I couldn't find multiple autofocus routines in sequencer.
I am using Moonlite Nitecrawler WR35, N.I.N.A version 3.1.2.9001 and Nitecrawler ASCOM driver v6.2.0.
I checked a log and I see this issue (which points to ASCOM driver issue, but I don't understand why I can't reproduce with manual start of autofocus):
2025-03-02T18:54:04.8072|ERROR|AscomDevice.cs|GetProperty|398|An unexpected exception occurred during GET of Rotator.Position:
ASCOM.DriverAccessCOMException (0x80131505): WaitOne Timeout on command 32-47-50-23, count 0, terminator 23
---> System.Runtime.InteropServices.COMException (0x80131505): WaitOne Timeout on command 32-47-50-23, count 0, terminator 23
at ASCOM.Com.DriverAccess.DynamicAccess.CheckDotNetExceptions(String memberName, Exception e)
at ASCOM.Com.DriverAccess.DynamicAccess.TryGetMember(GetMemberBinder binder, Object& result)
at CallSite.Target(Closure, CallSite, Object)
at ASCOM.Com.DriverAccess.Rotator.get_Position()
at InvokeStub_Rotator.get_Position(Object, Object, IntPtr*)
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
2025-03-02T18:54:05.0383|INFO|AscomDevice.cs|GetProperty|356|Retrying to GET Rotator.Position - Attempt 2 / 3
2025-03-02T18:54:10.7253|ERROR|AscomDevice.cs|GetProperty|398|An unexpected exception occurred during GET of Focuser.IsMoving:
ASCOM.DriverAccessCOMException (0x80131505): WaitOne Timeout on command 31-47-4D-23, count 0, terminator 23
---> System.Runtime.InteropServices.COMException (0x80131505): WaitOne Timeout on command 31-47-4D-23, count 0, terminator 23
at ASCOM.Com.DriverAccess.DynamicAccess.CheckDotNetExceptions(String memberName, Exception e)
at ASCOM.Com.DriverAccess.DynamicAccess.TryGetMember(GetMemberBinder binder, Object& result)
at CallSite.Target(Closure, CallSite, Object)
at ASCOM.Com.DriverAccess.Focuser.get_IsMoving()
at InvokeStub_Focuser.get_IsMoving(Object, Object, IntPtr*)
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
2025-03-02T18:54:10.9271|INFO|AscomDevice.cs|GetProperty|356|Retrying to GET Focuser.IsMoving - Attempt 2 / 3
2025-03-02T18:54:12.9376|ERROR|AscomDevice.cs|GetProperty|398|An unexpected exception occurred during GET of Focuser.IsMoving:
ASCOM.DriverAccessCOMException (0x80131505): WaitOne Timeout on command 31-47-4D-23, count 0, terminator 23
---> System.Runtime.InteropServices.COMException (0x80131505): WaitOne Timeout on command 31-47-4D-23, count 0, terminator 23
at ASCOM.Com.DriverAccess.DynamicAccess.CheckDotNetExceptions(String memberName, Exception e)
at ASCOM.Com.DriverAccess.DynamicAccess.TryGetMember(GetMemberBinder binder, Object& result)
at CallSite.Target(Closure, CallSite, Object)
at ASCOM.Com.DriverAccess.Focuser.get_IsMoving()
at InvokeStub_Focuser.get_IsMoving(Object, Object, IntPtr*)
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
2025-03-02T18:54:13.1391|INFO|AscomDevice.cs|GetProperty|356|Retrying to GET Focuser.IsMoving - Attempt 3 / 3
