ASCOM error in NINA

[Ryan Parle]

I have just tried to set up the Ascom OC driver with NINA and I get the following error when i attempt to connect:

2022-05-22T15:54:07.6191|ERROR|AscomDevice.cs|Connect|241
ASCOM.DriverException: Conversion error.System.FormatException: Input string was not in a correct format.
   at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
   at ASCOM.mySQMPLUSASCOM.ObservingConditions.set_Connected(Boolean value) ---> ASCOM.DriverException: Conversion error.System.FormatException: Input string was not in a correct format.
   at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
   at ASCOM.mySQMPLUSASCOM.ObservingConditions.set_Connected(Boolean value)
   at ASCOM.mySQMPLUSASCOM.ObservingConditions.set_Connected(Boolean value)
   --- 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 613
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 647
   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 172
   at Castle.DynamicProxy.AbstractInvocation.Proceed()
   at Castle.DynamicProxy.AbstractInvocation.Proceed()
   at NINA.Equipment.Equipment.AscomDevice`3.set_Connected(Boolean value) in E:\Projects\nina\NINA.Equipment\Equipment\AscomDevice.cs:line 143
   at NINA.Equipment.Equipment.AscomDevice`3.<<Connect>b__45_0>d.MoveNext() in E:\Projects\nina\NINA.Equipment\Equipment\AscomDevice.cs:line 235

I am using 127.-07 firmware and have had the same error on both the 016 & 017 versions of the ascom driver.

[Ryan Parle]

A bit of an update, this appears to be an issue on just one of my computers, I installed version 016 on my desktop computer and it works as expected, passes ASCOM Conform tests and connects to NINA without any issue.

I've attached a copy of the output from ASCOM Conform and a relevant ASCOM Log file. which may be useful.

[brownrb]

You are not trying to use the new ascom driver with firmware v127 are you?
I am pretty sure I posted that the new windows/linux/ascom will only work with firmware 128+ which is due for release in a few days time. I was in the process of moving the old 127 apps into the retired folders and uploading the new versions in preperation of the impending release of firmware 128

The new apps are not compatible with firmware 127.

The changelog text file for the ASCOM driver reads
0.0.17
Update to protocol 031 and firmware 128-34

So to use an ascom oc for firmware 127 you have to use the one in the retired folder
https://sourceforge.net/projects/mysqmproesp32/files/APPLICATIONS/ASCOM/retired/

[Ryan Parle]

I think i might have installed the 0.17 driver first by accident, i have since un installed it and replaced it with 0.16 but it seems like something was left behind by 0. 17.
I found another log file that shows the command 031# is sent and then it hits the error with the returned value. compared to the same log file on the working computer there's no command 031# sent at all.

Unfortunately I don't have access to the log files until I am home from work

This problem is persisting after several attempts at unninstalling and rebooting, any ideas on how to proceed?

[brownrb]

:031# is a dead giveaway that this refers to firmware 128-35RC7, which has yet to be released

In prior versions :03 referred to get system up time, and all commands are two characters (03)

In 128+ it does not, and all commands are three characters (031)

The ascom driver dll may have not be uninstalled by Windows, which dislikes users trying to install lower versions over higher versions

Make sure that you use control panel to delete any ascom oc driver for mySQM+ first
then

C:\Program Files (x86)\Common Files\ASCOM\ObservingConditions
is where the dlls are kept
ASCOM.mySQMPLUSASCOM.ObservingConditions.dll
is the file you need to locate and delete

Once deleted, run the install for 016

[Ryan Parle]

That did the trick! Thanks for the help.