- changed status to closed
Connection to ASCOM Skywatcher fails after update to 6.5
Issue #794
closed
Since NINA recommends ASCOM 6.5 on startup (I was running ASCOM 6.4), I’ve installed ASCOM 6.5 SP1. After that, I cannot connect my Skywatcher. But connecting and controlling in ASCOM DeviceHub works fine.
I switched back to 6.4 and it works also in NINA, but I always get the message that 6.5 is needed and I’m unsure if I run into problems when I don’t update.
Cheers,
Ralph
Here’s the NINA log:
----------------------------------------------------------------------
----------------NINA - Nighttime Imaging 'N' Astronomy----------------
-------------------Running NINA Version 1.11.0.1051-------------------
-------------------------2021-03-03T18:57:03--------------------------
----------------------ASCOM Platform Version 6.5----------------------
---------------------.NET Version 4.0.30319.42000---------------------
---------------------Oparating System Information---------------------
---------------------------Is 64bit OS True---------------------------
------------------------Is 64bit Process True-------------------------
---------------------------Platform Win32NT---------------------------
--------------Version Microsoft Windows NT 10.0.19042.0---------------
---------------------------Major 10 Minor 0---------------------------
----------------------------Service Pack -----------------------------
----------------------------------------------------------------------
DATE|LEVEL|SOURCE|MEMBER|LINE|MESSAGE
2021-03-03T18:57:04.2692|TRACE|CameraChooserVM.cs|GetEquipment|44|Adding ASI Cameras
2021-03-03T18:57:04.2692|TRACE|CameraChooserVM.cs|GetEquipment|58|Adding Altair Cameras
2021-03-03T18:57:04.2852|TRACE|CameraChooserVM.cs|GetEquipment|69|Adding Atik Cameras
2021-03-03T18:57:04.6117|TRACE|AtikCameraDll.cs|GetDevicesCount|21|Number of Atik Cameras: 0
2021-03-03T18:57:04.6117|TRACE|CameraChooserVM.cs|GetEquipment|71|Cameras found: 0
2021-03-03T18:57:04.6117|TRACE|CameraChooserVM.cs|GetEquipment|84|Adding FLI Cameras
2021-03-03T18:57:04.6117|DEBUG|FLICameras.cs|GetCameras|28|FLI: Found 0 camera(s)
2021-03-03T18:57:04.6117|TRACE|QhyccdSdk.cs|.ctor|41|QhyccdSdk: Loading QHY SDK, refCount=0, sdkIsInitialized=False
2021-03-03T18:57:04.6117|TRACE|CameraChooserVM.cs|GetEquipment|104|Adding QHYCCD Cameras
2021-03-03T18:57:04.6117|TRACE|QhyccdSdk.cs|InitSdk|50|QhyccdSdk: Initializing QHY SDK, refCount=0, sdkIsInitialized=False
2021-03-03T18:57:05.6255|TRACE|QHYCameras.cs|Count|32|QHYCamera - found 0 camera(s)
2021-03-03T18:57:05.6255|DEBUG|CameraChooserVM.cs|GetEquipment|122|Adding ToupTek Cameras
2021-03-03T18:57:05.6255|DEBUG|CameraChooserVM.cs|GetEquipment|133|Adding Omegon Cameras
2021-03-03T18:57:05.6409|TRACE|ASCOMInteraction.cs|GetCameras|40|Adding (ASCOM)
2021-03-03T18:57:05.6409|TRACE|ASCOMInteraction.cs|GetCameras|40|Adding (ASCOM)
2021-03-03T18:57:05.6409|TRACE|ASCOMInteraction.cs|GetCameras|40|Adding MGEN.APP (ASCOM)
2021-03-03T18:57:05.6409|TRACE|ASCOMInteraction.cs|GetCameras|40|Adding Camera V2 simulator (ASCOM)
2021-03-03T18:57:05.6409|TRACE|ASCOMInteraction.cs|GetCameras|40|Adding Simulator (ASCOM)
2021-03-03T18:57:05.6880|DEBUG|DllLoader.cs|LoadDll|401|Successfully loaded C:\Program Files\N.I.N.A. - Nighttime Imaging 'N' Astronomy\External\x64\FTDI\ftd2xx.dll
2021-03-03T18:57:05.6880|DEBUG|DllLoader.cs|LoadDll|401|Successfully loaded C:\Program Files\N.I.N.A. - Nighttime Imaging 'N' Astronomy\External\x64\MGEN\MG3lib.dll
2021-03-03T18:57:08.4536|TRACE|FlatWizardVM.cs|UpdateFilterWheelsSettings|38|Start: 03.03.2021 05:57:08.453; Stopped: 03.03.2021 05:57:08.453; Elapsed: 00:00:00.0002059
2021-03-03T18:57:09.4065|TRACE|FilterWheelChooserVM.cs|GetEquipment|42|Adding FLI filter wheels
2021-03-03T18:57:09.4065|DEBUG|FLIFilterWheels.cs|GetFilterWheels|28|FLI: Found 0 filter wheel(s)
2021-03-03T18:57:09.4065|TRACE|FilterWheelChooserVM.cs|GetEquipment|61|Adding Atik EFW filter wheels
2021-03-03T18:57:09.5003|TRACE|Profile.cs|Save|38|Start: 03.03.2021 05:57:09.500; Stopped: 03.03.2021 05:57:09.500; Elapsed: 00:00:00.0056709
2021-03-03T18:57:09.5003|TRACE|ProfileService.cs|Save|38|Start: 03.03.2021 05:57:09.500; Stopped: 03.03.2021 05:57:09.500; Elapsed: 00:00:00.0064446
2021-03-03T18:57:09.5473|TRACE|FilterWheelChooserVM.cs|GetEquipment|75|Adding Atik internal filter wheels
2021-03-03T18:57:09.5473|TRACE|AtikCameraDll.cs|GetDevicesCount|21|Number of Atik Cameras: 0
2021-03-03T18:57:09.5473|TRACE|FilterWheelChooserVM.cs|GetEquipment|77|Cameras found: 0
2021-03-03T18:57:09.5473|TRACE|FilterWheelChooserVM.cs|GetEquipment|94|Adding QHY integrated/4-pin filter wheels
2021-03-03T18:57:09.5473|TRACE|QhyccdSdk.cs|InitSdk|50|QhyccdSdk: Initializing QHY SDK, refCount=0, sdkIsInitialized=True
2021-03-03T18:57:09.5473|DEBUG|QHYFilterWheels.cs|GetFilterWheels|62|QHYCFW: Found 0 filter wheel(s)
2021-03-03T18:57:09.5473|TRACE|FilterWheelChooserVM.cs|GetEquipment|113|Adding ZWOptical filter wheels
2021-03-03T18:57:29.1674|TRACE|AscomDevice.cs|Connect|159|SkyWatcher Telescope - Calling PreConnect
2021-03-03T18:57:29.1684|TRACE|AscomDevice.cs|Connect|162|SkyWatcher Telescope - Creating instance for ASCOM.SkyWatcher.Telescope
2021-03-03T18:57:29.3070|DEBUG|AscomDevice.cs|Connected|115|SkyWatcher Telescope - Try SET Connected to True
2021-03-03T18:57:29.6306|TRACE|AscomDevice.cs|Connect|166|SkyWatcher Telescope - Calling PostConnect
2021-03-03T18:57:29.6528|ERROR|AscomDevice.cs|Connect|175|CheckDotNetExceptions ASCOM.SkyWatcher.Telescope SiteLongitude Get System.TypeInitializationException: Der Typeninitialisierer für "ASCOM.SkyWatcher.Location" hat eine Ausnahme verursacht. (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 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.Telescope.get_SiteLongitude() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Telescope.cs:line 948
at NINA.Model.MyTelescope.AscomTelescope.get_SiteLongitude()
at NINA.Model.MyTelescope.AscomTelescope.PostConnect()
at NINA.Model.AscomDevice`1.<<Connect>b__30_0>d.MoveNext()
2021-03-03T18:57:29.7369|ERROR|NotifyTaskCompletion.cs|WatchTaskAsync|35|CheckDotNetExceptions ASCOM.SkyWatcher.Telescope SiteLatitude Get System.TypeInitializationException: Der Typeninitialisierer für "ASCOM.SkyWatcher.Location" hat eine Ausnahme verursacht. (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 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.Telescope.get_SiteLatitude() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Telescope.cs:line 933
at NINA.Model.MyTelescope.AscomTelescope.get_SiteLatitude()
at NINA.ViewModel.Equipment.Telescope.TelescopeVM.<ChooseTelescope>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NINA.Utility.NotifyTaskCompletion`1.<WatchTaskAsync>d__5.MoveNext()
Comments (4)
-
repo owner
-
reporter
OK, I’ve taken a closer look to that: it’s a matter of the number format: it looks like the driver 6.5 now expects the decimal character according to the locale settings in windows (see post from merkel1986 http://www.astrotreff.de/topic.asp?TOPIC_ID=254414).
I’ve cleared the lat/long setting using the ASCOM Profile Browser, then set the windows locale to “.” for decimals. Then start NINA and push the lat/long from NINA to Teleskope … with that, it works …Cheers,
Ralph -
repo owner
Great! good that it is working now
-
repo owner
- removed version
Removing version: 1.11 Nightly (automated comment)
- Log in to comment
Hi,
the error emitted in the logs is coming from the driver. Make sure your latitude and longitude are set up properly in your driver setup.If the problem persists, you need to reach out to the driver vendor, as this is not a problem NINA can fix, but needs to be fixed by the driver vendor.
Thanks.