NINA: Filter Wheel Setup crashes on Win11

Astrobert

In Nina the call of "ZWO Filter Wheel Setup" is working. But the I'm trying to klick on "Edit Wheel" the app crashes with the following trace:

System.ArgumentOutOfRangeException: Die Anzahl der zu erstellenden Kopien muss immer positiv sein. (The number of copies to be created must always be positive)
Parametername: count
bei System.Windows.Forms.DataGridViewRowCollection.Add(Int32 count)
bei ASCOM.EFW2.SetNameForm..ctor(String[] slotName, String[] FocusOffset, String SN)
bei ASCOM.EFW2.SetupDialogForm.button_setName_Click(Object sender, EventArgs e)
bei System.Windows.Forms.Control.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
bei System.Windows.Forms.Button.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Geladene Assemblys **************
mscorlib
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.9168 (WinRelRS6.050727-9100).

CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll.

ASCOM.ASICamera2
Assembly-Version: 6.5.8404.20604.
Win32-Version: 6.5.28.0.

CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/ZWO/ASCOM.ASICamera2.DLL.

ASCOM.DeviceInterfaces
Assembly-Version: 6.0.0.0.
Win32-Version: 6.6.1.3673.

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.DeviceInterfaces/6.0.0.0__565de7938946fba7/ASCOM.DeviceInterfaces.dll.

ASCOM.Utilities
Assembly-Version: 6.0.0.0.
Win32-Version: 6.6.1.3673.

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Utilities/6.0.0.0__565de7938946fba7/ASCOM.Utilities.dll.

Microsoft.VisualBasic
Assembly-Version: 8.0.0.0.
Win32-Version: 8.0.50727.9157 (WinRelRS6.050727-9100).

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.

mscorlib.resources
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.9168 (WinRelRS6.050727-9100).

CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll.

System
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.9157 (WinRelRS6.050727-9100).

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll.

ASCOM.Exceptions
Assembly-Version: 6.0.0.0.
Win32-Version: 6.6.1.3673.

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Exceptions/6.0.0.0__565de7938946fba7/ASCOM.Exceptions.dll.

System.Web
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.9164 (WinRelRS6.050727-9100).

CodeBase: file:///C:/WINDOWS/assembly/GAC_64/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll.

System.Configuration
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.9157 (WinRelRS6.050727-9100).

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.

ASCOM.SettingsProvider
Assembly-Version: 6.0.0.0.
Win32-Version: 6.6.1.3673.

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.SettingsProvider/6.0.0.0__565de7938946fba7/ASCOM.SettingsProvider.dll.

ASCOM.Attributes
Assembly-Version: 6.0.0.0.
Win32-Version: 6.6.1.3673.

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Attributes/6.0.0.0__565de7938946fba7/ASCOM.Attributes.dll.

System.Xml
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.9157 (WinRelRS6.050727-9100).

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll.

ASCOM.Internal.Extensions
Assembly-Version: 6.0.0.0.
Win32-Version: 6.6.1.3673.

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Internal.Extensions/6.0.0.0__565de7938946fba7/ASCOM.Internal.Extensions.dll.

ASCOM.EFW2
Assembly-Version: 6.0.8336.27707.
Win32-Version: 6.0.8.0.

CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/ZWO/ASCOM.EFW2.DLL.

ASCOM.EAF
Assembly-Version: 6.0.8336.27180.
Win32-Version: 6.0.6.0.

CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/ZWO/ASCOM.EAF.DLL.

System.Windows.Forms
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.9157 (WinRelRS6.050727-9100).

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.

System.Drawing
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.9157 (WinRelRS6.050727-9100).

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.

System.Windows.Forms.resources
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.9157 (WinRelRS6.050727-9100).

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

Software@ZWO

Astrobert Thank you for your feedback. We have fixed this bug. We plan to release a new version of ASCOM next week.
Best Regards.

Astrobert

Software@ZWO
Any news on this issue? The download center is new, the issue dates are new. But the version numbers remain old.

Astrobert

Thank you.

Astrobert

One more Error with ASCOM and EAF (3.3.37):

2023-04-08T15:01:23.2910|INFO|AscomDevice.cs|GetProperty|323|Retrying to GET IFocuserFacadeProxy.StepSize - Attempt 3 / 3
2023-04-08T15:01:23.2921|ERROR|AscomDevice.cs|GetProperty|350|An unexpected exception occurred during GET of IFocuserFacadeProxy.StepSize:
ASCOM.DriverException: CheckDotNetExceptions _strProgId StepSize System.NotImplementedException: Die Methode oder der Vorgang sind nicht implementiert. (See Inner Exception for details)
---> System.NotImplementedException: Die Methode oder der Vorgang sind nicht implementiert.
--- End of inner exception stack trace ---
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_StepSize()
at NINA.Equipment.ASCOMFacades.FocuserFacadeProxy.get_StepSize() in C:\Projects\nina\NINA.Equipment\Equipment\AscomDeviceFacades.cs:line 60
at Castle.Proxies.Invocations.IFocuserFacade_get_StepSize.InvokeMethodOnTarget()
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at NINA.Equipment.Equipment.DeviceDispatchInterceptor1.<>c__DisplayClass7_0.<InterceptSynchronous>b__0() in C:\Projects\nina\NINA.Equipment\Equipment\DeviceDispatchInterceptor.cs:line 52 at NINA.Equipment.Equipment.DeviceDispatcher.Invoke(DeviceDispatcherType deviceType, Action callback) in C:\Projects\nina\NINA.Equipment\Equipment\DeviceDispatcher.cs:line 97 at NINA.Equipment.Equipment.DeviceDispatchInterceptor1.InterceptSynchronous(IInvocation invocation) in C:\Projects\nina\NINA.Equipment\Equipment\DeviceDispatchInterceptor.cs:line 52
at Castle.DynamicProxy.AsyncDeterminationInterceptor.Intercept(IInvocation invocation)
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Castle.Proxies.IFocuserFacadeProxy.get_StepSize()
at InvokeStub_IFocuserFacadeProxy.get_StepSize(Object, Object, IntPtr)
at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr args, BindingFlags invokeAttr)

Zzzz

Astrobert Thank you for your feedback. How does this happen? Can you describe the process？
Best Regards.

Astrobert

The error occurs every time the focuser gets "connected" in N.I.N.A.
And it repeats every 1-2 seconds.

Zzzz

Astrobert Thank you for your feedback！We're going to try to reproduce that problem。

Zzzz

Astrobert There is no problem after connected to focuser on my computer on my computer. What version of NINA do you use? In addition, please provide the screenshot when the problem occurs.
Looking forward to your h reply.

Software@ZWO

Astrobert Our new official website is still constantly improving. The new version of ASCOM will be released before April 24th. Thank you very much for your feedback.
Best Regards

Astrobert

Hello ZWO,

the problem still exists withe the new ASCOM driver: Pls. take care.

2023-06-03T08:14:10.9933|DEBUG|AscomDevice.cs|Connected|141|SET ZWO Focuser (1) Connected to True
2023-06-03T08:14:12.0700|ERROR|AscomDevice.cs|GetProperty|353|An unexpected exception occurred during GET of IFocuserFacadeProxy.StepSize:
ASCOM.DriverException: CheckDotNetExceptions ASCOM.EAF.Focuser StepSize Get System.NotImplementedException: Die Methode oder der Vorgang sind nicht implementiert. (See Inner Exception for details) ---> System.NotImplementedException: Die Methode oder der Vorgang sind nicht implementiert.
--- End of inner exception stack trace ---
at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 629
at ASCOM.DriverAccess.MemberFactory.GetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 664
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 287
at ASCOM.DriverAccess.Focuser.get_StepSize() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:line 191
at Castle.Proxies.Invocations.IFocuserFacade_get_StepSize.InvokeMethodOnTarget()
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Castle.Proxies.IFocuserFacadeProxy.get_StepSize()
2023-06-03T08:14:12.1741|INFO|AscomDevice.cs|GetProperty|327|Retrying to GET IFocuserFacadeProxy.StepSize - Attempt 2 / 3
2023-06-03T08:14:12.1769|ERROR|AscomDevice.cs|GetProperty|353|An unexpected exception occurred during GET of IFocuserFacadeProxy.StepSize:
ASCOM.DriverException: CheckDotNetExceptions ASCOM.EAF.Focuser StepSize Get System.NotImplementedException: Die Methode oder der Vorgang sind nicht implementiert. (See Inner Exception for details) ---> System.NotImplementedException: Die Methode oder der Vorgang sind nicht implementiert.
--- End of inner exception stack trace ---
at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 629
at ASCOM.DriverAccess.MemberFactory.GetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 664
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 287
at ASCOM.DriverAccess.Focuser.get_StepSize() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:line 191
at Castle.Proxies.Invocations.IFocuserFacade_get_StepSize.InvokeMethodOnTarget()
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Castle.Proxies.IFocuserFacadeProxy.get_StepSize()
2023-06-03T08:14:12.2783|INFO|AscomDevice.cs|GetProperty|327|Retrying to GET IFocuserFacadeProxy.StepSize - Attempt 3 / 3
2023-06-03T08:14:12.2890|ERROR|AscomDevice.cs|GetProperty|353|An unexpected exception occurred during GET of IFocuserFacadeProxy.StepSize:
ASCOM.DriverException: CheckDotNetExceptions ASCOM.EAF.Focuser StepSize Get System.NotImplementedException: Die Methode oder der Vorgang sind nicht implementiert. (See Inner Exception for details) ---> System.NotImplementedException: Die Methode oder der Vorgang sind nicht implementiert.
--- End of inner exception stack trace ---
at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 629
at ASCOM.DriverAccess.MemberFactory.GetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 664
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 287
at ASCOM.DriverAccess.Focuser.get_StepSize() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:line 191
at Castle.Proxies.Invocations.IFocuserFacade_get_StepSize.InvokeMethodOnTarget()
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Castle.Proxies.IFocuserFacadeProxy.get_StepSize()
2023-06-03T08:14:12.2890|INFO|AscomDevice.cs|GetProperty|358|GET IFocuserFacadeProxy.StepSize failed - Returning last known value 0
2023-06-03T08:14:12.3227|INFO|FocuserVM.cs|ChooseFocuser|307|Successfully connected Focuser. Id: ASCOM.EAF.Focuser Name: ZWO Focuser (1) Driver Version: 6.0

Zzzz

Astrobert Hi Astrobert,
Try the following methods:

(1) Ensure that all software currently using ASCOM has been closed
(2) Enter the control panel and uninstall ASCOM.
(3) Download the latest ASCOM from our official website and install it.
Hope this can help you.

Astrobert

Zzzz

Hello again,

the drivers are already the latest. Any other ideas?

Cheers

Zzzz

Astrobert We'd like to help you out, but we can't see what's going on right now. We hope you will allow us to control your computer remotely
Please install an APP called Sunflower：https://sunlogin.oray.com/download?categ=personal.We will arrange professional personnel to help you solve the problem through remote assistance.