1. Stefan B Avatar Stefan B
  2. nina
  3. NINA
  4. Issues

rotator connection failed in last releases

Issue #642 resolved
pascal created an issue

Hello, there is a problem with the rotator connection in the 1.10 and 1.11 Nina version. I have two home made rotators based on the myRotator and ScopeFocus projects that worked perfectly with the older Nina version (1.10 and all the other software I use), but since the two last releases connection to the ascom driver failed (tested on two pc, solved if Nina is downgraded to the 1.10HF1 version, I use the x86 version on windows 10).

I hope you can do something.

Thanks

Pascal

Comments (25)

  1. Stefan B repo owner

    Hi,

    description is a bit confusing. Which version is working and which isn’t? From what i can read 1.10 HF1 is working but 1.11 not?

    Furthermore can you please attach the logs (located in %localappdata%\nina\logs)

  3. pascal reporter

    Hello,

    you are right, the 1.10 works well but the later not.

    ----------------NINA - Nighttime Imaging 'N' Astronomy----------------

    -------------------Running NINA Version 1.11.0.1004-------------------
    -------------------------2020-10-26T20:29:13--------------------------
    ----------------------ASCOM Platform Version 6.5----------------------
    ---------------------.NET Version 4.0.30319.42000---------------------
    ---------------------Oparating System Information---------------------
    ---------------------------Is 64bit OS True---------------------------
    ------------------------Is 64bit Process False------------------------
    ---------------------------Platform Win32NT---------------------------
    --------------Version Microsoft Windows NT 10.0.17763.0---------------
    ---------------------------Major 10 Minor 0---------------------------
    ----------------------------Service Pack -----------------------------

    [2020-10-26T20:29:15.0365] [DEBUG] [MemberName] GetCameras
    [2020-10-26T20:29:15.0365] [DEBUG] [FileName] E:\Projects\nina\NINA\Utility\CameraSDKs\FLISDK\FLICameras.cs
    [2020-10-26T20:29:15.0365] [DEBUG] [Message] FLI: Found 0 camera(s)

    [2020-10-26T20:29:15.0702] [DEBUG] [MemberName] GetEquipment
    [2020-10-26T20:29:15.0702] [DEBUG] [FileName] E:\Projects\nina\NINA\ViewModel\Equipment\Camera\CameraChooserVM.cs
    [2020-10-26T20:29:15.0702] [DEBUG] [Message] Adding ToupTek Cameras

    [2020-10-26T20:29:15.1139] [DEBUG] [MemberName] GetEquipment
    [2020-10-26T20:29:15.1139] [DEBUG] [FileName] E:\Projects\nina\NINA\ViewModel\Equipment\Camera\CameraChooserVM.cs
    [2020-10-26T20:29:15.1139] [DEBUG] [Message] Adding Omegon Cameras

    [2020-10-26T20:29:19.4013] [DEBUG] [MemberName] GetFilterWheels
    [2020-10-26T20:29:19.4013] [DEBUG] [FileName] E:\Projects\nina\NINA\Utility\CameraSDKs\FLISDK\FLIFilterWheels.cs
    [2020-10-26T20:29:19.4013] [DEBUG] [Message] FLI: Found 0 filter wheel(s)

    [2020-10-26T20:29:19.4052] [DEBUG] [MemberName] GetFilterWheels
    [2020-10-26T20:29:19.4052] [DEBUG] [FileName] E:\Projects\nina\NINA\Utility\CameraSDKs\QHYSDK\QHYFilterWheels.cs
    [2020-10-26T20:29:19.4052] [DEBUG] [Message] QHYCFW: Found 0 filter wheel(s)

    [2020-10-26T20:29:39.6814] [ERROR] [MemberName] WatchTaskAsync
    [2020-10-26T20:29:39.6814] [ERROR] [FileName] E:\Projects\nina\NINA\Utility\NotifyTaskCompletion.cs
    [2020-10-26T20:29:39.6814] [ERROR] [Message] CheckDotNetExceptions ASCOM.scopefocusServer.Rotator Reverse Get System.NullReferenceException: La référence d'objet n'est pas définie à une instance d'un objet. (See Inner Exception for details) 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 663
    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.Rotator.get_Reverse() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Rotator.cs:line 172
    at NINA.Model.MyRotator.AscomRotator.get_Reverse()
    at NINA.ViewModel.Equipment.Rotator.RotatorVM.<Connect>d__57.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at NINA.Utility.NotifyTaskCompletion`1.<WatchTaskAsync>d__5.MoveNext()

    ‌

    ‌

    sorry for the copy/paste only images seemed to be allowed to be uploaded.

    Thanks.

    Pascal

    ‌

  4. Stefan B repo owner

    There were some interface changes to the rotator interface with ascom platform 6.5 which nina is potentially using in 1.11. maybe that’s the problem here.

  5. pascal reporter

    ok, can you do something or do you think that downgrading ascom platform to 6.4 will solve the problem? or I would have to contact the developers for drivers updating?.

    Thanks.

  7. pascal reporter

    ok thank you, I have also a problem to connect the myRotator rotator …

    is it the same issue?

    ----------------NINA - Nighttime Imaging 'N' Astronomy----------------

    -------------------Running NINA Version 1.11.0.1004-------------------
    -------------------------2020-10-27T13:33:38--------------------------
    ----------------------ASCOM Platform Version 6.5----------------------
    ---------------------.NET Version 4.0.30319.42000---------------------
    ---------------------Oparating System Information---------------------
    ---------------------------Is 64bit OS True---------------------------
    ------------------------Is 64bit Process False------------------------
    ---------------------------Platform Win32NT---------------------------
    --------------Version Microsoft Windows NT 10.0.17763.0---------------
    ---------------------------Major 10 Minor 0---------------------------
    ----------------------------Service Pack -----------------------------

    [2020-10-27T13:33:38.7529] [DEBUG] [MemberName] GetCameras
    [2020-10-27T13:33:38.7529] [DEBUG] [FileName] E:\Projects\nina\NINA\Utility\CameraSDKs\FLISDK\FLICameras.cs
    [2020-10-27T13:33:38.7529] [DEBUG] [Message] FLI: Found 0 camera(s)

    [2020-10-27T13:33:38.7608] [DEBUG] [MemberName] GetEquipment
    [2020-10-27T13:33:38.7608] [DEBUG] [FileName] E:\Projects\nina\NINA\ViewModel\Equipment\Camera\CameraChooserVM.cs
    [2020-10-27T13:33:38.7608] [DEBUG] [Message] Adding ToupTek Cameras

    [2020-10-27T13:33:38.7901] [DEBUG] [MemberName] GetEquipment
    [2020-10-27T13:33:38.7901] [DEBUG] [FileName] E:\Projects\nina\NINA\ViewModel\Equipment\Camera\CameraChooserVM.cs
    [2020-10-27T13:33:38.7901] [DEBUG] [Message] Adding Omegon Cameras

    [2020-10-27T13:33:42.4283] [DEBUG] [MemberName] GetFilterWheels
    [2020-10-27T13:33:42.4283] [DEBUG] [FileName] E:\Projects\nina\NINA\Utility\CameraSDKs\FLISDK\FLIFilterWheels.cs
    [2020-10-27T13:33:42.4283] [DEBUG] [Message] FLI: Found 0 filter wheel(s)

    [2020-10-27T13:33:42.4323] [DEBUG] [MemberName] GetFilterWheels
    [2020-10-27T13:33:42.4323] [DEBUG] [FileName] E:\Projects\nina\NINA\Utility\CameraSDKs\QHYSDK\QHYFilterWheels.cs
    [2020-10-27T13:33:42.4323] [DEBUG] [Message] QHYCFW: Found 0 filter wheel(s)

    [2020-10-27T13:34:00.3501] [ERROR] [MemberName] Connected
    [2020-10-27T13:34:00.3501] [ERROR] [FileName] E:\Projects\nina\NINA\Model\MyRotator\AscomRotator.cs
    [2020-10-27T13:34:00.3501] [ERROR] [Message] Serial port connection error at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 559
    at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 646
    at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 314
    at ASCOM.DriverAccess.AscomDriver.set_Connected(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 170
    at NINA.Model.MyRotator.AscomRotator.set_Connected(Boolean value)

    [2020-10-27T13:34:00.3550] [ERROR] [MemberName] Connect
    [2020-10-27T13:34:00.3550] [ERROR] [FileName] E:\Projects\nina\NINA\Model\MyRotator\AscomRotator.cs
    [2020-10-27T13:34:00.3550] [ERROR] [Message] Cannot connect to controller at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 613
    at ASCOM.DriverAccess.MemberFactory.GetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 663
    at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 230
    at ASCOM.DriverAccess.Rotator.get_Position() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Rotator.cs:line 157
    at NINA.Model.MyRotator.AscomRotator.<Connect>b__36_0()

    [2020-10-27T13:34:19.4475] [INFO] [MemberName] Disconnect
    [2020-10-27T13:34:19.4475] [INFO] [FileName] E:\Projects\nina\NINA\ViewModel\Equipment\Focuser\FocuserVM.cs
    [2020-10-27T13:34:19.4475] [INFO] [Message] Disconnected Focuser

    ‌

    Thanks.

    Pascal

  8. Dale Ghent

    Yes. The driver is reporting a problem connecting on the serial/COM port and is emitting an exception as a result. There does appear to be issues with either the hardware, driver, or both.

  9. pascal reporter

    sure that there is no problem with hardware, the rotators work very well with older Nina version or other software.

    Thanks.

    Pascal

  10. Dale Ghent

    This line in the log indicates otherwise:

    [2020-10-27T13:34:00.3501] [ERROR] [Message] Serial port connection error at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 559

    This error is being sent to NINA from the driver, via the ASCOM framework. It’s low-level, and indicates an issue with the driver or the hardware - a serial connection unable to be made. NINA does not make the serial connection; it only directs the driver to connect to the hardware in accordance with the driver’s own, separate configuration.

    It may be that your rotator’s driver is not working will with ASCOM 6.5. It may be that you are running NINA as administrator and the driver has issues using the COM port that it is configured to use. Perhaps the COM port that the driver is configured to use is different than what Windows has registered your rotator device as actually using. There are a multitude of local configuration issues that could lead to this situation. All we see here is NINA is calling the driver’s method to connect to the hardware and the driver claims it is failing.

  12. pascal reporter

    Nina is not running in admin mode, and the 1.10 HF1 version works nicely using exactly the same COM port, hardware and driver. For the ascom platform version I can't say, I contacted the developer, I am waiting for a new driver version if he found something to correct to have a complete compatibility with Ascam 6.5. For info the rotator (myRotator) works fine with SGP (v3.2.0.613, same COM port).

    Thanks

  13. pascal reporter

    Hello,

    last log with updated driver (not definitive)

    ‌

    ----------------NINA - Nighttime Imaging 'N' Astronomy----------------

    -------------------Running NINA Version 1.11.0.1005-------------------
    -------------------------2020-10-28T09:34:45--------------------------
    ----------------------ASCOM Platform Version 6.5----------------------
    ---------------------.NET Version 4.0.30319.42000---------------------
    ---------------------Oparating System Information---------------------
    ---------------------------Is 64bit OS True---------------------------
    ------------------------Is 64bit Process False------------------------
    ---------------------------Platform Win32NT---------------------------
    --------------Version Microsoft Windows NT 10.0.17763.0---------------
    ---------------------------Major 10 Minor 0---------------------------
    ----------------------------Service Pack -----------------------------

    [2020-10-28T09:34:46.2694] [DEBUG] [MemberName] GetCameras
    [2020-10-28T09:34:46.2694] [DEBUG] [FileName] E:\Projects\nina\NINA\Utility\CameraSDKs\FLISDK\FLICameras.cs
    [2020-10-28T09:34:46.2694] [DEBUG] [Message] FLI: Found 0 camera(s)

    [2020-10-28T09:34:46.2768] [DEBUG] [MemberName] GetEquipment
    [2020-10-28T09:34:46.2768] [DEBUG] [FileName] E:\Projects\nina\NINA\ViewModel\Equipment\Camera\CameraChooserVM.cs
    [2020-10-28T09:34:46.2768] [DEBUG] [Message] Adding ToupTek Cameras

    [2020-10-28T09:34:46.3071] [DEBUG] [MemberName] GetEquipment
    [2020-10-28T09:34:46.3071] [DEBUG] [FileName] E:\Projects\nina\NINA\ViewModel\Equipment\Camera\CameraChooserVM.cs
    [2020-10-28T09:34:46.3071] [DEBUG] [Message] Adding Omegon Cameras

    [2020-10-28T09:34:49.6645] [DEBUG] [MemberName] GetFilterWheels
    [2020-10-28T09:34:49.6645] [DEBUG] [FileName] E:\Projects\nina\NINA\Utility\CameraSDKs\FLISDK\FLIFilterWheels.cs
    [2020-10-28T09:34:49.6645] [DEBUG] [Message] FLI: Found 0 filter wheel(s)

    [2020-10-28T09:34:49.6685] [DEBUG] [MemberName] GetFilterWheels
    [2020-10-28T09:34:49.6685] [DEBUG] [FileName] E:\Projects\nina\NINA\Utility\CameraSDKs\QHYSDK\QHYFilterWheels.cs
    [2020-10-28T09:34:49.6685] [DEBUG] [Message] QHYCFW: Found 0 filter wheel(s)

    [2020-10-28T09:35:00.2392] [ERROR] [MemberName] WatchTaskAsync
    [2020-10-28T09:35:00.2392] [ERROR] [FileName] E:\Projects\nina\NINA\Utility\NotifyTaskCompletion.cs
    [2020-10-28T09:35:00.2392] [ERROR] [Message] Property read ASCOM.scopefocusServer.Rotator Reverse is not implemented in this driver. at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 278
    at ASCOM.DriverAccess.Rotator.get_Reverse() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Rotator.cs:line 172
    at NINA.Model.MyRotator.AscomRotator.get_Reverse()
    at NINA.ViewModel.Equipment.Rotator.RotatorVM.<Connect>d__57.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at NINA.Utility.NotifyTaskCompletion`1.<WatchTaskAsync>d__5.MoveNext()

    [2020-10-28T09:37:28.9166] [INFO] [MemberName] Disconnect
    [2020-10-28T09:37:28.9166] [INFO] [FileName] E:\Projects\nina\NINA\ViewModel\Equipment\Focuser\FocuserVM.cs
    [2020-10-28T09:37:28.9166] [INFO] [Message] Disconnected Focuser

    Thanks

    Pascal

  14. Stefan B repo owner

    Hi Pascal,

    as you can see in the Rotator definition by ASCOM that i have linked earlier, the “Reverse” field is mandatory and must be implemented - with the note that this changed from Version 6.4.
    Therefore this is a compliance issue of that driver and NINA just expects that this field is implemented, because the specification by ASCOM is defined like that for ASCOM Platform 6.5.

  15. Stefan B repo owner

    However I can change the code slightly to handle this gracefully for drivers that aren’t updated to the 6.5 specifications due to this exceptional case.

  16. pascal reporter

    Thank you Stephan, I am in touch with the developer (Hi Kevin! thank you again), I gave him the link of this topic, so he have directly your information. Thank you for your quick help.

    Regards.

    Pascal

  17. pascal reporter

    Hi Stefan,

    just for information, I tested the last versions of Nina, the issue is still there, Kevin is still working on the driver. Thanks.

  18. K Sip

    Hello,

    thanks for addressing this issue. I developed the scopefocus rotator. It appears there are some unique attributes to Nina with regards to rotator connection.

    My driver is iRotatorV2 compliant and passes conform with no issues or errors. It does not support reverse ( which c/w V2 requirements, granted not iRotatorV3 complaint though). Clients using ASCOM should still be compliant w/ iRotatorV2.

    CanReverse returns false for my driver, yet Nina appears to try and set the reverse state. My driver does throws the appropriate NotImplemented exception, but the connection fails.

    It seems like Nina should NOT try to ‘get’ or ‘set’ Revere if the CanReverse returns false which can occur w/ V2 drivers.

    This driver works just fine in other applications.

    Thank you!

    kevin

  19. Stefan B repo owner

    From what i see it is just a missing check when reading from the property. I will fix this starting with 1.10 HF2 beta 2 and 1.11 build 10

  20. pascal reporter

    Hi, thank you very much Kevin and Stephan, you did a great job, both Nina and scopefocus rotator are great tools.

    Thanks

    Pascal

  21. Stefan B repo owner

    Hi, can you please update to 1.10 HF2 Beta2 and check if the rotator now works properly?

  24. pascal reporter

    Works properly here too !!

    The buttons (in equipment and imaging panels) has a strange behavior (text disappears and cross stay active after the rotator has stopped) but connection and movement are ok, next step test in real condition …

    Thank you again for you reactivity and your efficiency.

    Pascal

    ‌

  26. Log in to comment
Assignee
–
Type
bug
Priority
major
Status
resolved
Component
User Interface
Version
–
Votes
0
Watchers
1
Jira: the preferred issue tracker for Bitbucket. Join the team!