Focuser not works with Meade Classic Ascom Driver
Comments (10)
-
repo owner -
With the first Connect this issue comes, the Focuser moves
(Google Translator)
ConformanceCheck ASCOM Device Conformance Checker Version 6.4.64.0, Build time: 07.06.2019 15:06:44
ConformanceCheck Running on: ASCOM Platform 6.4 SP1 6.4.1.2695ConformanceCheck Driver ProgID: MeadeEx.Focuser
Error handling
Error number for "Not Implemented" is: 80040400
Error number for "Invalid Value 1" is: 80040404
Error number for "Value Not Set 1" is: 80040402
Error number for "Value Not Set 2" is: 80040403
Error messages will not be interpreted to infer state.16:41:11.281 Driver Access Checks OK
16:41:12.109 AccessChecks OK Successfully created driver using late binding
16:41:12.862 AccessChecks OK Successfully connected using late binding
16:41:12.862 AccessChecks INFO The driver is a COM object
16:41:14.297 AccessChecks INFO Device exposes IFocuser interface
16:41:14.641 AccessChecks INFO Device does not expose IFocuserV2 interface
16:41:14.844 AccessChecks INFO Device does not expose IFocuserV3 interface
16:41:15.094 AccessChecks OK Successfully created driver using driver access toolkit
16:41:15.695 AccessChecks OK Successfully connected using driver access toolkit
16:41:15.852 AccessChecks OK Successfully disconnected using driver access toolkitConform is using ASCOM.DriverAccess.Focuser to get a Focuser object
16:41:16.102 ConformanceCheck OK Driver instance created successfully
16:41:16.800 ConformanceCheck OK Connected OKCommon Driver Methods
16:41:16.894 InterfaceVersion OK 1
16:41:16.941 Connected OK True
16:41:16.987 Description INFO No description string
16:41:17.050 DriverInfo INFO No DriverInfo string
16:41:17.112 DriverVersion OK 0.0
16:41:17.175 Name INFO Name is empty
16:41:17.237 CommandString INFO Conform cannot test the CommandString method
16:41:17.253 CommandBlind INFO Conform cannot test the CommandBlind method
16:41:17.269 CommandBool INFO Conform cannot test the CommandBool method
16:41:17.269 Action INFO Conform cannot test the Action method
16:41:17.300 SupportedActions OK Driver returned an empty action listProperties
16:41:17.487 Absolute OK False
16:41:17.503 IsMoving OK False
16:41:17.503 MaxStep OK 7000
16:41:17.519 MaxIncrement OK 7000
16:41:17.534 Position OK Position must not be implemented for a relative focuser and a PropertyNotImplementedException exception was generated as expected
16:41:17.550 StepSize OK Optional member threw a PropertyNotImplementedException exception.
16:41:17.550 TempCompAvailable OK False
16:41:17.566 TempComp Read OK False
16:41:17.581 TempComp Write OK Temperature compensation is not available and a PropertyNotImplementedException exception was generated as expected
16:41:17.597 Temperature OK Optional member threw a PropertyNotImplementedException exception.Methods
16:41:17.659 Halt OK Focuser halted OK
16:41:17.675 Move - TempComp False Moving by: 700
16:41:18.816 Move - TempComp False Asynchronous move found
16:41:18.831 Move - TempComp False OK Relative move OK
16:41:18.862 Move - TempComp False INFO Returning to original position: 0Conformance test complete
No errors, warnings or issues found: your driver passes ASCOM validation!!
With the second Connect this issue comes, the Focuser moves
ConformanceCheck ASCOM Device Conformance Checker Version 6.4.64.0, Build time: 07.06.2019 15:06:44
ConformanceCheck Running on: ASCOM Platform 6.4 SP1 6.4.1.2695ConformanceCheck Driver ProgID: MeadeEx.Focuser
Error handling
Error number for "Not Implemented" is: 80040400
Error number for "Invalid Value 1" is: 80040404
Error number for "Value Not Set 1" is: 80040402
Error number for "Value Not Set 2" is: 80040403
Error messages will not be interpreted to infer state.16:43:02.753 Driver Access Checks OK
16:43:02.894 AccessChecks ERROR Error creating driver object using late binding: System.Runtime.InteropServices.COMException (0x800A01A9): Eine Instanz der COM-Komponente mit der CLSID {CEAB7464-7BDB-4AC7-B298-F6F4DAF21F6D} konnte aufgrund des folgenden Fehlers nicht von der IClassFactory erstellt werden: 800a01a9 Ausnahme von HRESULT: 0x800A01A9.
bei System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
bei System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
bei System.Activator.CreateInstance(Type type, Boolean nonPublic)
bei System.Activator.CreateInstance(Type type)
bei Conform.DeviceTesterBaseClass.CheckAccessibility(String p_ProgId, DeviceType p_DeviceType) in J:\Conform\Conform\Devices\DeviceTesterBaseClass.vb:Zeile 445.16:43:04.402 AccessChecks INFO Device exposes IFocuser interface
16:43:04.731 AccessChecks INFO Device does not expose IFocuserV2 interface
16:43:04.949 AccessChecks INFO Device does not expose IFocuserV3 interface
16:43:05.137 AccessChecks OK Successfully created driver using driver access toolkit
16:43:05.745 AccessChecks OK Successfully connected using driver access toolkit
16:43:05.902 AccessChecks OK Successfully disconnected using driver access toolkitConform is using ASCOM.DriverAccess.Focuser to get a Focuser object
16:43:06.136 ConformanceCheck OK Driver instance created successfully
16:43:06.841 ConformanceCheck OK Connected OKCommon Driver Methods
16:43:06.919 InterfaceVersion OK 1
16:43:06.982 Connected OK True
16:43:07.044 Description INFO No description string
16:43:07.107 DriverInfo INFO No DriverInfo string
16:43:07.169 DriverVersion OK 0.0
16:43:07.232 Name INFO Name is empty
16:43:07.294 CommandString INFO Conform cannot test the CommandString method
16:43:07.310 CommandBlind INFO Conform cannot test the CommandBlind method
16:43:07.325 CommandBool INFO Conform cannot test the CommandBool method
16:43:07.341 Action INFO Conform cannot test the Action method
16:43:07.357 SupportedActions OK Driver returned an empty action listProperties
16:43:07.544 Absolute OK False
16:43:07.560 IsMoving OK False
16:43:07.575 MaxStep OK 7000
16:43:07.591 MaxIncrement OK 7000
16:43:07.607 Position OK Position must not be implemented for a relative focuser and a PropertyNotImplementedException exception was generated as expected
16:43:07.607 StepSize OK Optional member threw a PropertyNotImplementedException exception.
16:43:07.622 TempCompAvailable OK False
16:43:07.622 TempComp Read OK False
16:43:07.638 TempComp Write OK Temperature compensation is not available and a PropertyNotImplementedException exception was generated as expected
16:43:07.653 Temperature OK Optional member threw a PropertyNotImplementedException exception.Methods
16:43:07.716 Halt OK Focuser halted OK
16:43:07.732 Move - TempComp False Moving by: 700
16:43:08.857 Move - TempComp False Asynchronous move found
16:43:08.888 Move - TempComp False OK Relative move OK
16:43:08.919 Move - TempComp False INFO Returning to original position: 0Conformance test complete
Your driver had 1 error, 0 warnings and 0 issues
-
APT has no problem with that
-
repo owner Thank you for the details, can you also attach a logfile from nina itself to see if some internal error occurrs? the logs are located inside “%LOCALAPPDATA%\NINA\Logs”
-
No content on log:
----------------NINA - Nighttime Imaging 'N' Astronomy----------------
-------------------Running NINA Version 1.9.0.9001--------------------
-------------------------2020-01-08T17:02:50--------------------------
----------------------ASCOM Platform Version 6.4----------------------
---------------------.NET Version 4.0.30319.42000---------------------
---------------------Oparating System Information---------------------
---------------------------Is 64bit OS True---------------------------
------------------------Is 64bit Process False------------------------
---------------------------Platform Win32NT---------------------------
---------------Version Microsoft Windows NT 6.2.9200.0----------------
---------------------------Major 6 Minor 2----------------------------
----------------------------Service Pack -----------------------------with x86:
with x64:
-
after restart computer:
----------------NINA - Nighttime Imaging 'N' Astronomy----------------
-------------------Running NINA Version 1.9.0.9001--------------------
-------------------------2020-01-08T17:17:00--------------------------
----------------------ASCOM Platform Version 6.4----------------------
---------------------.NET Version 4.0.30319.42000---------------------
---------------------Oparating System Information---------------------
---------------------------Is 64bit OS True---------------------------
------------------------Is 64bit Process True-------------------------
---------------------------Platform Win32NT---------------------------
---------------Version Microsoft Windows NT 6.2.9200.0----------------
---------------------------Major 6 Minor 2----------------------------
----------------------------Service Pack -----------------------------[2020-01-08T17:17:37] [ERROR] [MemberName] WatchTaskAsync
[2020-01-08T17:17:37] [ERROR] [FileName] D:\Projects\nina\NINA\Utility\NotifyTaskCompletion.cs
[2020-01-08T17:17:37] [ERROR] [Message] Property read MeadeEx.Focuser Position is not implemented in this driver. bei ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:Zeile 283.
bei ASCOM.DriverAccess.Focuser.get_Position() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:Zeile 159.
bei NINA.Model.MyFocuser.AscomFocuser.<Move>d__37.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei NINA.ViewModel.Equipment.Focuser.FocuserVM.<>c__DisplayClass7_0.<<MoveFocuser>b__0>d.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei NINA.ViewModel.Equipment.Focuser.FocuserVM.<MoveFocuser>d__7.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei NINA.ViewModel.Equipment.Focuser.FocuserVM.<MoveFocuserRelative>d__10.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei NINA.Utility.NotifyTaskCompletion`1.<WatchTaskAsync>d__5.MoveNext() -
from meade ascom driver:
PI notes
- The Meade focuser is a "relative" focuser, and therefore the Position Property is not implemented.
- The StepSize Property is not implemented since the Meade focuser does not intrinsically know its step size.
- Temperature is unavailable
- Temperature compensation is not supported
-
The problem is revealed in the AccessChecks test from the the ASCOM conformance tool. This driver does not seems to do late binding, which is a requirement of drivers that operate under ASCOM 6.
NINA is very strict, out of necessity, concerning ASCOM driver conformance.
-
repo owner Additionally to that in NINA only absolute position focusers are supported at the moment.
-
repo owner - changed status to closed
- Log in to comment
Hi, please run the ascom conformance checker and post the logs to identify if there is a driver problem or some problem inside nina. Thanks.
ASCOM Conformance check
Some ASCOM drivers do not conform to the ASCOM interface.
This tool performs a comprehensive set of tests on a driver to determine its conformance with the relevant ASCOM interface standard as well as tests to some aspects of driver behavior against the reference implementation. It is adviced to run the conformance checker against those drivers and report issues to the driver manufacturer to fix these issues.
Make sure to select the correct driver prior to testing under Options->Select Driver