I am having issues connecting to Nina. The standalone app connects fine, and I can control the Nema17 stepper, but Nina refuses to connect to the ascom driver. The ASCOM Conformance tester also fails to connect to the controller.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
19:53:10.709 Driver Access Checks OK
19:53:11.368 AccessChecks OK Successfully created driver using late binding
19:53:11.385 AccessChecks ERROR Error connecting to driver using late binding: ASCOM.DriverException: Cannot connect to controller ---> ASCOM.NotConnectedException: Serial port connection error ---> System.UnauthorizedAccessException: Access to the port 'COM4' is denied.
at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520
at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
--- End of inner exception stack trace ---
at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Symbols.Container.InvokeMethod(Method TargetProcedure, Object[] Arguments, Boolean[] CopyBack, BindingFlags Flags)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments)
at Conform.DeviceTesterBaseClass.CheckAccessibility(String p_ProgId, DeviceType p_DeviceType) in J:\Conform\Conform\Devices\DeviceTesterBaseClass.vb:line 452
19:53:12.055 AccessChecks INFO Device does not expose IFocuser interface
19:53:12.126 AccessChecks INFO Device does not expose IFocuserV2 interface
19:53:12.195 AccessChecks INFO Device does not expose IFocuserV3 interface
19:53:12.263 AccessChecks OK Successfully created driver using driver access toolkit
19:53:12.278 AccessChecks ERROR ** Error connecting to driver using driver access toolkit: Cannot connect to controller**
Conform is using ASCOM.DriverAccess.Focuser to get a Focuser object
19:53:12.380 ConformanceCheck OK Driver instance created successfully
19:53:12.442 Connected ERROR Error changing focuser connected state: ASCOM.DriverException: Cannot connect to controller ---> ASCOM.DriverException: Cannot connect to controller ---> ASCOM.NotConnectedException: Serial port connection error ---> System.UnauthorizedAccessException: Access to the port 'COM4' is denied.
at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520
at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
--- End of inner exception stack trace ---
at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
--- End of inner exception stack trace ---
at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
at ASCOM.myFocuser2ASCOM.Focuser.set_Link(Boolean value)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Symbols.Container.InvokeMethod(Method TargetProcedure, Object[] Arguments, Boolean[] CopyBack, BindingFlags Flags)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments)
at Conform.FocuserTester.set_Connected(Boolean value) in J:\Conform\Conform\Devices\FocuserTester.vb:line 215
19:53:12.456 ConformanceCheck OK Connected OK
Common Driver Methods
19:53:12.513 InterfaceVersion OK 2
19:53:12.548 Connected OK False
19:53:12.584 Description OK myFocuserPro2ASCOM
19:53:12.619 DriverInfo OK Arduino myFocuserPro2ASCOM driver by RB Brown.
19:53:12.654 DriverVersion OK 2.7.4
19:53:12.689 Name OK myFocuserPro2 ASCOM driver
19:53:12.725 CommandString INFO Conform cannot test the CommandString method
19:53:12.736 CommandBlind INFO Conform cannot test the CommandBlind method
19:53:12.748 CommandBool INFO Conform cannot test the CommandBool method
19:53:12.760 Action INFO Conform cannot test the Action method
19:53:12.771 SupportedActions OK Driver returned an empty action list
Properties
19:53:12.895 Absolute OK True
19:53:12.909 IsMoving ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:12.921 MaxStep ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:12.934 MaxIncrement ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:12.948 Position ERROR Unexpected DriverException(0x80131500), Position must be implemented for an absolute focuser: Cannot connect to controller
19:53:12.960 StepSize OK Optional member threw a PropertyNotImplementedException exception.
19:53:12.972 StepSize ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:12.986 TempComp Read ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:12.998 TempComp Write ERROR Unexpected DriverException(0x80131500), Temperature compensation is not available: Cannot connect to controller
19:53:13.012 Temperature ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
Methods
19:53:13.073 Halt ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:13.088 Move - TempComp False Moving to position: 0
19:53:13.104 Move ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
Conformance test complete
Your driver had 13 errors, 0 warnings and 0 issues
Last edit: brownrb 2020-10-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Key portion says this Access to the port 'COM4' is denied.
Are you using com4 with another app?
A lot of us use NINA without any issue.
ASCOM drivers are always tested against conform before release.
Here is latest conform results.
Start-up ASCOM Device Conformance Checker - 64bit mode
20:00:22.642 Start-up DEBUG Initial application error level: ERRORMODE_SYSTEM_DEFAULT
20:00:22.642 Start-up DEBUG New application error level: ERRORMODE_NO_WINDOWS_ERROR_DIALOGUES
Start-up ASCOM Platform 6.4 SP1 6.4.1.2695
20:00:22.658 Form.Load DEBUG Found loaded assembly: mscorlib 4.0.0.0
20:00:22.658 Form.Load DEBUG Found loaded assembly: Conform 6.4.64.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: Microsoft.VisualBasic 10.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System 4.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System.Core 4.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System.Windows.Forms 4.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System.Drawing 4.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System.Configuration 4.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System.Xml 4.0.0.0
20:00:22.689 Form.Load DEBUG Found loaded assembly: System.Runtime.Remoting 4.0.0.0
20:00:22.689 Form.Load DEBUG Found loaded assembly: ASCOM.Utilities 6.0.0.0
20:00:22.689 DEBUG
CheckForUpdates Checking for Conform updates with 10 second timeout
20:00:22.689 CheckForUpdates INFO This version of Conform is: 6.4.64.0
20:00:22.711 CheckForUpdates DEBUG Target URI: https://download.ascom-standards.org/devtools/conform.txt
20:00:22.711 CheckForUpdates DEBUG No proxy server detected, going directly to Internet
20:00:22.727 CheckForUpdates DEBUG Sending request to web server with 10 second timeout...
20:00:23.591 CheckForUpdates ERROR WebException: The request was aborted: Could not create SSL/TLS secure channel.
20:00:51.791 SelectDriver DEBUG Selected ProgID is: ASCOM.myFocuser2ASCOM.Focuser Focuser
Support information
20:00:55.399 Support INFO OS version: Microsoft Windows NT 6.2.9200.0
20:00:55.399 Support INFO .NET version: 4.0.30319.42000
20:00:55.399 Support INFO Processor count: 12
20:00:55.415 Support INFO System directory: C:\WINDOWS\system32
20:00:55.415 Support INFO Program files directory: C:\Program Files
20:00:55.415 Support INFO Common program files directory: C:\Program Files\Common Files
20:00:55.415 Support INFO Common application data directory: C:\ProgramData
20:00:55.415 Support INFO Current directory: C:\Program Files (x86)\ASCOM\Conform
20:00:55.431 Support INFO Current culture: en-US
20:00:55.431 Support INFO Total physical memory: 34,200,629,248
20:00:55.431 Support INFO Total virtual memory: 140,737,488,224,256
20:00:55.562 Support INFO OS full name: Microsoft Windows 10 Pro
20:00:55.578 Support INFO Available physical memory: 28,415,717,376
20:00:55.578 Support INFO Available virtual memory: 140,732,399,714,304
ConformanceCheck ASCOM Device Conformance Checker Version 6.4.64.0, Build time: 6/7/2019 2:06:44 PM
ConformanceCheck Running on: ASCOM Platform 6.4 SP1 6.4.1.2695
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.
20:00:55.631 Driver Access Checks OK
20:00:55.647 AccessChecks About to create instance using Activator.CreateInstance
20:00:55.678 AccessChecks DEBUG Successfully created driver using Activator.CreateInstance
20:00:55.684 WaitForAbsolute DEBUG 500 Waiting for driver initialisation
20:00:56.380 AccessChecks OK Successfully created driver using late binding
20:00:56.380 AccessChecks About to set Link property true
20:01:00.674 AccessChecks About to set Link property false
20:01:00.690 AccessChecks OK Successfully connected using late binding
20:01:00.690 AccessChecks INFO The driver is a .NET object
20:01:00.690 AccessChecks INFO The AssemblyQualifiedName is: ASCOM.myFocuser2ASCOM.Focuser, ASCOM.myFocuser2ASCOM.Focuser, Version=6.0.75
20:01:00.705 AccessChecks INFO The driver implements interface: ASCOM.DeviceInterface.IFocuserV2
20:01:00.705 ReleaseCOMObjects DEBUG Start of ReleaseCOMObject
20:01:00.712 AccessChecks About to release driver instance
20:01:00.712 ReleaseCOMObjects DEBUG Unmarshalling Focuser
20:01:00.712 ReleaseCOMObjects DEBUG Releasing COM object
20:01:00.727 ReleaseCOMObjects DEBUG ReleaseComObject Exception: The object's type must be __ComObject or derived from __ComObject.
Parameter name: o
20:01:00.727 ReleaseCOMObjects DEBUG End of ReleaseCOMObject
20:01:00.743 AccessChecks DEBUG Collecting garbage
20:01:00.743 AccessChecks DEBUG Collecting garbage complete
20:01:00.759 AccessChecks DEBUG Finished waiting for pending finalisers
20:01:00.759 WaitForAbsolute DEBUG 500 Waiting for device driver to be cleaned up by operating system
20:01:01.492 AccessChecks INFO Device does not expose IFocuser interface
20:01:01.576 AccessChecks DEBUG Successfully created driver with IFocuserV2 interface
20:01:05.833 AccessChecks INFO Device exposes IFocuserV2 interface
20:01:05.918 AccessChecks INFO Device does not expose IFocuserV3 interface
20:01:06.003 AccessChecks OK Successfully created driver using driver access toolkit
20:01:10.262 AccessChecks OK Successfully connected using driver access toolkit
20:01:10.277 AccessChecks OK Successfully disconnected using driver access toolkit
Conform is using ASCOM.DriverAccess.Focuser to get a Focuser object
20:01:10.346 CreateDevice DEBUG Successfully created driver
20:01:10.362 ConformanceCheck OK Driver instance created successfully
20:01:10.446 Connected DEBUG Setting connected state to: True
20:01:14.683 AccessChecks DEBUG Successfully changed connected state
20:01:14.683 ConformanceCheck OK Connected OK
Common Driver Methods
20:01:14.752 InterfaceVersion About to get property InterfaceVersion
20:01:14.752 InterfaceVersion OK 2
20:01:14.815 Connected About to get property Connected
20:01:14.815 Connected OK True
20:01:14.852 Description About to get property Description
20:01:14.852 Description OK myFocuserPro2ASCOM
20:01:14.899 DriverInfo About to get property DriverInfo
20:01:14.899 DriverInfo OK Arduino myFocuserPro2ASCOM driver by RB Brown.
20:01:14.952 DriverVersion About to get property DriverVersion
20:01:14.952 DriverVersion OK 2.7.4
20:01:14.999 Name About to get property Name
20:01:14.999 Name OK myFocuserPro2 ASCOM driver
20:01:15.053 CommandString INFO Conform cannot test the CommandString method
20:01:15.053 CommandBlind INFO Conform cannot test the CommandBlind method
20:01:15.053 CommandBool INFO Conform cannot test the CommandBool method
20:01:15.053 Action INFO Conform cannot test the Action method
20:01:15.068 SupportedActions About to call method SupportedActions
20:01:15.084 SupportedActions OK Driver returned an empty action list
Properties
20:01:15.237 Absolute OK True
20:01:15.300 IsMoving OK False
20:01:15.300 MaxStep OK 10000
20:01:15.316 MaxIncrement OK 10000
20:01:15.322 Position OK 5000
20:01:15.353 StepSize OK 50
20:01:15.400 TempCompAvailable OK False
20:01:15.454 TempComp Read OK False
20:01:15.523 TempComp Write OK Temperature compensation is not available and a PropertyNotImplementedException exception was generated as expected
20:01:15.538 TempComp Write DEBUG Exception: ASCOM.PropertyNotImplementedException: Property read Unknown is not implemented in this driver. ---> ASCOM.PropertyNotImplementedException: TempComp is not available is not implemented in this driver.
at ASCOM.myFocuser2ASCOM.Focuser.set_TempComp(Boolean value)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Symbols.Container.InvokeMethod(Method TargetProcedure, Object[] Arguments, Boolean[] CopyBack, BindingFlags Flags)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments)
at Conform.FocuserTester.CheckProperties() in J:\Conform\Conform\Devices\FocuserTester.vb:line 350
20:01:15.685 Temperature OK 20
Methods
20:01:15.754 Halt OK Focuser halted OK
20:01:16.001 Move - TempComp False Moving to position: 6000
20:01:21.297 Move - TempComp False Asynchronous move found
20:01:21.482 Move - TempComp False OK Absolute move OK
20:01:21.498 Move - TempComp False INFO Returning to original position: 5000
Conformance test complete
**No errors, warnings or issues found: your driver passes ASCOM validation!! **
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you are having issues, then this is what I need to resolve them
1. Remove the current ASCOM driver [use control panel-uninstall program]
2. Ensure that there is no ASCOM.myFocuser2ASCOM.Focuser.dll file left over in C:\Program Files (x86)\Common Files\ASCOM\Focuser
3. Install the latest 274 ascom driver
4. Start NINA
5. In the focuser setupdialog form for the ASCOM focuser 274 driver, make sure TRACE ON is enabled
6. Try to connect to the ascom driver
7. If it fails please post here the trace log files found in Documents\ASCOM\Logs xx-xx-xxxx that relate to the myfocuserpro2
In the log file posted by Chester, the COM port could not be opened. It may be being held open by another program [use task manager to check if there is any orphaned myfocuserpro2 application still running], OR it may be because the privledge is set wrong - in other words trying to run NINA in privledged administrator mode instead of as a standard user [Run as Adminstrator in advanced properties for NINA should be turned off [unchecked].
Last edit: brownrb 2020-10-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
And remember, you should be using rev 300 firmware and ascom driver 274 and Windows app 2457.
I stress again, when upating apps or ascom drivers, you should uninstall the old one using control panel first, then install the new version, otherwise the apps etc may not work as instended/
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's mostly curious that the driver 2.60 works for him despite ASCOM 6.5
I'll try to reproduce the other steps later, but my last attempt was with a freshly flashed controller and latest ascom driver back then, without running as admin and never having opened the standalone application and I had the same issues. Reverted to 2.60 and it worked fine for me.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My results, looks good. I guess my issues were with an older version (maybe 2.7.2 or 3?).
Potentially Chesters problem originates in super old firmware (I made this focuser and sent it to a friend which sent it to him because he switched to something else and I don't think he ever updated the firmware)
Focuser Firmware myFP2A4998, 298 on COM9
myFocuserPro2 Software 2.4.5.0:
- Connects
NINA 1.10 + myFocuserPro 2.6.0 ASCOM:
- Connects
Uninstalled 2.6.0
Manually deleted DLL file
NINA 1.10 + myFocuserPro 2.7.4 ASCOM:
- Connects
Last edit: Stanley Dimant 2020-10-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can only support the latest versions. In many cases the changes listed in the change file is incomplete where a lot of minor fixes are also included but not listed. On all my systems I always run the latest versions [or next release] of everything.
Yes a lot of earlier versions of ascom drivers did report issues connecting with NINA but that was resolved several versions ago [but was not listed in the changelog file].
I can only repeat what I have said earlier - running the latest versions of everything will generally resolve known issues.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert,
I seem to have the same problem with connecting to NINA.
I followed your steps above (msg on 2020-10-06) and I have ASCOM 6.5, ASCOM driver version 276, Myfocuserpro version 300.
The trace I get is:
20:37:22.822 Focuser Starting initialisation
20:37:22.838 Focuser Completed initialisation
20:37:22.839 InterfaceVersion Get 2
20:37:22.847 Connected ASCOM Driver 2.7.6
20:37:22.847 Connected True
20:37:22.847 IsConnected Get False
20:37:22.847 START Connect Started
20:37:22.847 Connected Set = True
20:37:22.847 Connected Create serial port
20:37:22.849 Connected Get portname: (None)
20:37:22.850 Connected Get baudrate: 9600
20:37:22.850 Connected Setting baudrate to 9600
20:37:22.850 Connected Get ResetControllerOnConnect: True
20:37:22.850 Reset Controller On Conne True
20:37:22.850 Connected Set Receive Timeout = 5
20:37:22.872 Connected Cannot connect to COM port: Missing?
20:37:22.873 Connected ASCOM.Driver Exception ERROR- if( value ): Possible serial port disconnect.[0A]ASCOM.DriverException: Serial port connection error ---> System.ArgumentException: The given port name does not start with COM/com or does not resolve to a valid serial port.[0D][0A]Parameter name: portName[0D][0A] at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)[0D][0A] --- End of inner exception stack trace ---[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
The windows app connects without a problem.
Any ideas?
Thanks,
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Rob
The telltale line is
20:37:22.849 Connected Get portname: (None)
This means that the driver does NOT have a com port defined.
In Nina, reselect the ascom driver and MAKE SURE that the properties window is shown - on there you must specify the com port and speed - the driver errorlog shows it has not been selected
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Mike
if you are using ASCOM driver to access the controller - then in the setup dialog form that you use to select com port and speed, make sure that Trace is checked so that a logfile can be produced.
In windows systems, the logfile will be in a folder underneath Documents\ASCOM\logsxxxx
Please send me the ASCOM logs.
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
22:02:39.943 Focuser Starting initialisation
22:02:40.011 Focuser Completed initialisation
22:02:40.011 InterfaceVersion Get 2
22:02:40.043 Connected ASCOM Driver 2.7.8
22:02:40.043 Connected True
22:02:40.043 IsConnected Get False
22:02:40.043 START Connect Started
22:02:40.043 Connected Set = True
22:02:40.043 Connected Create serial port
22:02:40.049 Connected Get portname: COM3
22:02:40.050 Connected Get baudrate: 9600
22:02:40.051 Connected Setting baudrate to 9600
22:02:40.051 Connected Get ResetControllerOnConnect: True
22:02:40.051 Reset Controller On Conne True
22:02:40.052 Connected Set Receive Timeout = 5
22:02:40.510 Connected NotConnectedExceptionSystem.UnauthorizedAccessException: Access to the port 'COM3' is denied.[0D][0A] at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
22:02:40.518 Connected ASCOM.Driver Exception ERROR- if( value ): Possible serial port disconnect.[0A]ASCOM.NotConnectedException: Serial port connection error ---> System.UnauthorizedAccessException: Access to the port 'COM3' is denied.[0D][0A] at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)[0D][0A] --- End of inner exception stack trace ---[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are using firmware 294. This is out of date/not supported
Firmware 294 does NOT work with the ASCOM driver you are using or the Windows app you are using.
Program the controller with the CLEAREEPROM.ino file to erase controller flash memory.
Program the controller with firmware 305
regards
Robert
For reference (these are NO longer supported or available) - Firmware 298 would require
Firmware 298-299
ASCOM Driver 2.7.3
Windows App - Probably 2.4.4.9
Last edit: brownrb 2021-04-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am having issues connecting to Nina. The standalone app connects fine, and I can control the Nema17 stepper, but Nina refuses to connect to the ascom driver. The ASCOM Conformance tester also fails to connect to the controller.
This is what the conformance tester spat out
ConformanceCheck ASCOM Device Conformance Checker Version 6.5.7500.22515, Build time: 14/07/2020 11:30:30 am
ConformanceCheck Running on: ASCOM Platform 6.5 6.5.0.3091
ConformanceCheck Driver ProgID: ASCOM.myFocuser2ASCOM.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.
19:53:10.709 Driver Access Checks OK
19:53:11.368 AccessChecks OK Successfully created driver using late binding
19:53:11.385 AccessChecks ERROR Error connecting to driver using late binding: ASCOM.DriverException: Cannot connect to controller ---> ASCOM.NotConnectedException: Serial port connection error ---> System.UnauthorizedAccessException: Access to the port 'COM4' is denied.
at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520
at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
--- End of inner exception stack trace ---
at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Symbols.Container.InvokeMethod(Method TargetProcedure, Object[] Arguments, Boolean[] CopyBack, BindingFlags Flags)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments)
at Conform.DeviceTesterBaseClass.CheckAccessibility(String p_ProgId, DeviceType p_DeviceType) in J:\Conform\Conform\Devices\DeviceTesterBaseClass.vb:line 452
19:53:12.055 AccessChecks INFO Device does not expose IFocuser interface
19:53:12.126 AccessChecks INFO Device does not expose IFocuserV2 interface
19:53:12.195 AccessChecks INFO Device does not expose IFocuserV3 interface
19:53:12.263 AccessChecks OK Successfully created driver using driver access toolkit
19:53:12.278 AccessChecks ERROR ** Error connecting to driver using driver access toolkit: Cannot connect to controller**
Conform is using ASCOM.DriverAccess.Focuser to get a Focuser object
19:53:12.380 ConformanceCheck OK Driver instance created successfully
19:53:12.442 Connected ERROR Error changing focuser connected state: ASCOM.DriverException: Cannot connect to controller ---> ASCOM.DriverException: Cannot connect to controller ---> ASCOM.NotConnectedException: Serial port connection error ---> System.UnauthorizedAccessException: Access to the port 'COM4' is denied.
at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520
at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
--- End of inner exception stack trace ---
at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
--- End of inner exception stack trace ---
at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
at ASCOM.myFocuser2ASCOM.Focuser.set_Link(Boolean value)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Symbols.Container.InvokeMethod(Method TargetProcedure, Object[] Arguments, Boolean[] CopyBack, BindingFlags Flags)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments)
at Conform.FocuserTester.set_Connected(Boolean value) in J:\Conform\Conform\Devices\FocuserTester.vb:line 215
19:53:12.456 ConformanceCheck OK Connected OK
Common Driver Methods
19:53:12.513 InterfaceVersion OK 2
19:53:12.548 Connected OK False
19:53:12.584 Description OK myFocuserPro2ASCOM
19:53:12.619 DriverInfo OK Arduino myFocuserPro2ASCOM driver by RB Brown.
19:53:12.654 DriverVersion OK 2.7.4
19:53:12.689 Name OK myFocuserPro2 ASCOM driver
19:53:12.725 CommandString INFO Conform cannot test the CommandString method
19:53:12.736 CommandBlind INFO Conform cannot test the CommandBlind method
19:53:12.748 CommandBool INFO Conform cannot test the CommandBool method
19:53:12.760 Action INFO Conform cannot test the Action method
19:53:12.771 SupportedActions OK Driver returned an empty action list
Properties
19:53:12.895 Absolute OK True
19:53:12.909 IsMoving ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:12.921 MaxStep ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:12.934 MaxIncrement ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:12.948 Position ERROR Unexpected DriverException(0x80131500), Position must be implemented for an absolute focuser: Cannot connect to controller
19:53:12.960 StepSize OK Optional member threw a PropertyNotImplementedException exception.
19:53:12.972 StepSize ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:12.986 TempComp Read ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:12.998 TempComp Write ERROR Unexpected DriverException(0x80131500), Temperature compensation is not available: Cannot connect to controller
19:53:13.012 Temperature ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
Methods
19:53:13.073 Halt ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
19:53:13.088 Move - TempComp False Moving to position: 0
19:53:13.104 Move ERROR Unexpected DriverException(0x80131500), : Cannot connect to controller
Conformance test complete
Your driver had 13 errors, 0 warnings and 0 issues
Last edit: brownrb 2020-10-06
Key portion says this
Access to the port 'COM4' is denied.
Are you using com4 with another app?
A lot of us use NINA without any issue.
ASCOM drivers are always tested against conform before release.
Here is latest conform results.
Start-up ASCOM Device Conformance Checker - 64bit mode
20:00:22.642 Start-up DEBUG Initial application error level: ERRORMODE_SYSTEM_DEFAULT
20:00:22.642 Start-up DEBUG New application error level: ERRORMODE_NO_WINDOWS_ERROR_DIALOGUES
Start-up ASCOM Platform 6.4 SP1 6.4.1.2695
20:00:22.658 Form.Load DEBUG Found loaded assembly: mscorlib 4.0.0.0
20:00:22.658 Form.Load DEBUG Found loaded assembly: Conform 6.4.64.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: Microsoft.VisualBasic 10.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System 4.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System.Core 4.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System.Windows.Forms 4.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System.Drawing 4.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System.Configuration 4.0.0.0
20:00:22.674 Form.Load DEBUG Found loaded assembly: System.Xml 4.0.0.0
20:00:22.689 Form.Load DEBUG Found loaded assembly: System.Runtime.Remoting 4.0.0.0
20:00:22.689 Form.Load DEBUG Found loaded assembly: ASCOM.Utilities 6.0.0.0
20:00:22.689 DEBUG
CheckForUpdates Checking for Conform updates with 10 second timeout
20:00:22.689 CheckForUpdates INFO This version of Conform is: 6.4.64.0
20:00:22.711 CheckForUpdates DEBUG Target URI: https://download.ascom-standards.org/devtools/conform.txt
20:00:22.711 CheckForUpdates DEBUG No proxy server detected, going directly to Internet
20:00:22.727 CheckForUpdates DEBUG Sending request to web server with 10 second timeout...
20:00:23.591 CheckForUpdates ERROR WebException: The request was aborted: Could not create SSL/TLS secure channel.
20:00:51.791 SelectDriver DEBUG Selected ProgID is: ASCOM.myFocuser2ASCOM.Focuser Focuser
Support information
20:00:55.399 Support INFO OS version: Microsoft Windows NT 6.2.9200.0
20:00:55.399 Support INFO .NET version: 4.0.30319.42000
20:00:55.399 Support INFO Processor count: 12
20:00:55.415 Support INFO System directory: C:\WINDOWS\system32
20:00:55.415 Support INFO Program files directory: C:\Program Files
20:00:55.415 Support INFO Common program files directory: C:\Program Files\Common Files
20:00:55.415 Support INFO Common application data directory: C:\ProgramData
20:00:55.415 Support INFO Current directory: C:\Program Files (x86)\ASCOM\Conform
20:00:55.431 Support INFO Current culture: en-US
20:00:55.431 Support INFO Total physical memory: 34,200,629,248
20:00:55.431 Support INFO Total virtual memory: 140,737,488,224,256
20:00:55.562 Support INFO OS full name: Microsoft Windows 10 Pro
20:00:55.578 Support INFO Available physical memory: 28,415,717,376
20:00:55.578 Support INFO Available virtual memory: 140,732,399,714,304
ConformanceCheck ASCOM Device Conformance Checker Version 6.4.64.0, Build time: 6/7/2019 2:06:44 PM
ConformanceCheck Running on: ASCOM Platform 6.4 SP1 6.4.1.2695
ConformanceCheck Driver ProgID: ASCOM.myFocuser2ASCOM.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.
20:00:55.631 Driver Access Checks OK
20:00:55.647 AccessChecks About to create instance using Activator.CreateInstance
20:00:55.678 AccessChecks DEBUG Successfully created driver using Activator.CreateInstance
20:00:55.684 WaitForAbsolute DEBUG 500 Waiting for driver initialisation
20:00:56.380 AccessChecks OK Successfully created driver using late binding
20:00:56.380 AccessChecks About to set Link property true
20:01:00.674 AccessChecks About to set Link property false
20:01:00.690 AccessChecks OK Successfully connected using late binding
20:01:00.690 AccessChecks INFO The driver is a .NET object
20:01:00.690 AccessChecks INFO The AssemblyQualifiedName is: ASCOM.myFocuser2ASCOM.Focuser, ASCOM.myFocuser2ASCOM.Focuser, Version=6.0.75
20:01:00.705 AccessChecks INFO The driver implements interface: ASCOM.DeviceInterface.IFocuserV2
20:01:00.705 ReleaseCOMObjects DEBUG Start of ReleaseCOMObject
20:01:00.712 AccessChecks About to release driver instance
20:01:00.712 ReleaseCOMObjects DEBUG Unmarshalling Focuser
20:01:00.712 ReleaseCOMObjects DEBUG Releasing COM object
20:01:00.727 ReleaseCOMObjects DEBUG ReleaseComObject Exception: The object's type must be __ComObject or derived from __ComObject.
Parameter name: o
20:01:00.727 ReleaseCOMObjects DEBUG End of ReleaseCOMObject
20:01:00.743 AccessChecks DEBUG Collecting garbage
20:01:00.743 AccessChecks DEBUG Collecting garbage complete
20:01:00.759 AccessChecks DEBUG Finished waiting for pending finalisers
20:01:00.759 WaitForAbsolute DEBUG 500 Waiting for device driver to be cleaned up by operating system
20:01:01.492 AccessChecks INFO Device does not expose IFocuser interface
20:01:01.576 AccessChecks DEBUG Successfully created driver with IFocuserV2 interface
20:01:05.833 AccessChecks INFO Device exposes IFocuserV2 interface
20:01:05.918 AccessChecks INFO Device does not expose IFocuserV3 interface
20:01:06.003 AccessChecks OK Successfully created driver using driver access toolkit
20:01:10.262 AccessChecks OK Successfully connected using driver access toolkit
20:01:10.277 AccessChecks OK Successfully disconnected using driver access toolkit
Conform is using ASCOM.DriverAccess.Focuser to get a Focuser object
20:01:10.346 CreateDevice DEBUG Successfully created driver
20:01:10.362 ConformanceCheck OK Driver instance created successfully
20:01:10.446 Connected DEBUG Setting connected state to: True
20:01:14.683 AccessChecks DEBUG Successfully changed connected state
20:01:14.683 ConformanceCheck OK Connected OK
Common Driver Methods
20:01:14.752 InterfaceVersion About to get property InterfaceVersion
20:01:14.752 InterfaceVersion OK 2
20:01:14.815 Connected About to get property Connected
20:01:14.815 Connected OK True
20:01:14.852 Description About to get property Description
20:01:14.852 Description OK myFocuserPro2ASCOM
20:01:14.899 DriverInfo About to get property DriverInfo
20:01:14.899 DriverInfo OK Arduino myFocuserPro2ASCOM driver by RB Brown.
20:01:14.952 DriverVersion About to get property DriverVersion
20:01:14.952 DriverVersion OK 2.7.4
20:01:14.999 Name About to get property Name
20:01:14.999 Name OK myFocuserPro2 ASCOM driver
20:01:15.053 CommandString INFO Conform cannot test the CommandString method
20:01:15.053 CommandBlind INFO Conform cannot test the CommandBlind method
20:01:15.053 CommandBool INFO Conform cannot test the CommandBool method
20:01:15.053 Action INFO Conform cannot test the Action method
20:01:15.068 SupportedActions About to call method SupportedActions
20:01:15.084 SupportedActions OK Driver returned an empty action list
Properties
20:01:15.237 Absolute OK True
20:01:15.300 IsMoving OK False
20:01:15.300 MaxStep OK 10000
20:01:15.316 MaxIncrement OK 10000
20:01:15.322 Position OK 5000
20:01:15.353 StepSize OK 50
20:01:15.400 TempCompAvailable OK False
20:01:15.454 TempComp Read OK False
20:01:15.523 TempComp Write OK Temperature compensation is not available and a PropertyNotImplementedException exception was generated as expected
20:01:15.538 TempComp Write DEBUG Exception: ASCOM.PropertyNotImplementedException: Property read Unknown is not implemented in this driver. ---> ASCOM.PropertyNotImplementedException: TempComp is not available is not implemented in this driver.
at ASCOM.myFocuser2ASCOM.Focuser.set_TempComp(Boolean value)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Symbols.Container.InvokeMethod(Method TargetProcedure, Object[] Arguments, Boolean[] CopyBack, BindingFlags Flags)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments)
at Conform.FocuserTester.CheckProperties() in J:\Conform\Conform\Devices\FocuserTester.vb:line 350
20:01:15.685 Temperature OK 20
Methods
20:01:15.754 Halt OK Focuser halted OK
20:01:16.001 Move - TempComp False Moving to position: 6000
20:01:21.297 Move - TempComp False Asynchronous move found
20:01:21.482 Move - TempComp False OK Absolute move OK
20:01:21.498 Move - TempComp False INFO Returning to original position: 5000
Conformance test complete
**No errors, warnings or issues found: your driver passes ASCOM validation!! **
2.6 also works for me. Im using the exact same circut that stanley is using (He bulilt mine).
I have the same issue. Focuser works fine with driver version 2.60 for me, but I could not get any versions beyond 2.72 to run.
Edit: not sure if it's related but I am using cheap arduino nano clones from china with ch340 chip in the circuitry.
Edit2: if I remember correctly, the standalone application works
Last edit: Stanley Dimant 2020-10-06
If you are having issues, then this is what I need to resolve them
1. Remove the current ASCOM driver [use control panel-uninstall program]
2. Ensure that there is no ASCOM.myFocuser2ASCOM.Focuser.dll file left over in C:\Program Files (x86)\Common Files\ASCOM\Focuser
3. Install the latest 274 ascom driver
4. Start NINA
5. In the focuser setupdialog form for the ASCOM focuser 274 driver, make sure TRACE ON is enabled
6. Try to connect to the ascom driver
7. If it fails please post here the trace log files found in Documents\ASCOM\Logs xx-xx-xxxx that relate to the myfocuserpro2
In the log file posted by Chester, the COM port could not be opened. It may be being held open by another program [use task manager to check if there is any orphaned myfocuserpro2 application still running], OR it may be because the privledge is set wrong - in other words trying to run NINA in privledged administrator mode instead of as a standard user [Run as Adminstrator in advanced properties for NINA should be turned off [unchecked].
Last edit: brownrb 2020-10-06
And remember, you should be using rev 300 firmware and ascom driver 274 and Windows app 2457.
I stress again, when upating apps or ascom drivers, you should uninstall the old one using control panel first, then install the new version, otherwise the apps etc may not work as instended/
regards
Robert
I also see chester is running ASCOM Platform 6.5 whereas my test system is still on 6.4 SP1
If you have the time, you might check if 6.5 is the issue?
It's mostly curious that the driver 2.60 works for him despite ASCOM 6.5
I'll try to reproduce the other steps later, but my last attempt was with a freshly flashed controller and latest ascom driver back then, without running as admin and never having opened the standalone application and I had the same issues. Reverted to 2.60 and it worked fine for me.
Nothing related to any of myFP2, myFP, myFP2ESP etc has been tested in ASCOM 6.5 as of date.
I am guessing you all updated to ASCOM 6.5 recently yes?
iirc I'm still on 6.4 SP1 on my machine
My results, looks good. I guess my issues were with an older version (maybe 2.7.2 or 3?).
Potentially Chesters problem originates in super old firmware (I made this focuser and sent it to a friend which sent it to him because he switched to something else and I don't think he ever updated the firmware)
Focuser Firmware myFP2A4998, 298 on COM9
myFocuserPro2 Software 2.4.5.0:
- Connects
NINA 1.10 + myFocuserPro 2.6.0 ASCOM:
- Connects
Uninstalled 2.6.0
Manually deleted DLL file
NINA 1.10 + myFocuserPro 2.7.4 ASCOM:
- Connects
Last edit: Stanley Dimant 2020-10-06
Thanks for the update. Good to hear.
I can only support the latest versions. In many cases the changes listed in the change file is incomplete where a lot of minor fixes are also included but not listed. On all my systems I always run the latest versions [or next release] of everything.
Yes a lot of earlier versions of ascom drivers did report issues connecting with NINA but that was resolved several versions ago [but was not listed in the changelog file].
I can only repeat what I have said earlier - running the latest versions of everything will generally resolve known issues.
Hi Robert,
I seem to have the same problem with connecting to NINA.
I followed your steps above (msg on 2020-10-06) and I have ASCOM 6.5, ASCOM driver version 276, Myfocuserpro version 300.
The trace I get is:
20:37:22.822 Focuser Starting initialisation
20:37:22.838 Focuser Completed initialisation
20:37:22.839 InterfaceVersion Get 2
20:37:22.847 Connected ASCOM Driver 2.7.6
20:37:22.847 Connected True
20:37:22.847 IsConnected Get False
20:37:22.847 START Connect Started
20:37:22.847 Connected Set = True
20:37:22.847 Connected Create serial port
20:37:22.849 Connected Get portname: (None)
20:37:22.850 Connected Get baudrate: 9600
20:37:22.850 Connected Setting baudrate to 9600
20:37:22.850 Connected Get ResetControllerOnConnect: True
20:37:22.850 Reset Controller On Conne True
20:37:22.850 Connected Set Receive Timeout = 5
20:37:22.872 Connected Cannot connect to COM port: Missing?
20:37:22.873 Connected ASCOM.Driver Exception ERROR- if( value ): Possible serial port disconnect.[0A]ASCOM.DriverException: Serial port connection error ---> System.ArgumentException: The given port name does not start with COM/com or does not resolve to a valid serial port.[0D][0A]Parameter name: portName[0D][0A] at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)[0D][0A] --- End of inner exception stack trace ---[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
The windows app connects without a problem.
Any ideas?
Thanks,
Rob
Hi Rob
The telltale line is
20:37:22.849 Connected Get portname: (None)
This means that the driver does NOT have a com port defined.
In Nina, reselect the ascom driver and MAKE SURE that the properties window is shown - on there you must specify the com port and speed - the driver errorlog shows it has not been selected
regards
Robert
Arrgh! I felt sure I had selected the port!
All connecting up perfectly now, all I need is a clear night :-)
Thanks Robert
Hi Guys and Girls,
I have problems to connect the focuser with NINA as it works via App.
23.04.2021 01:22:33: Exit =START=========================================================
23.04.2021 01:22:33: Exit: exiting
23.04.2021 01:22:33: Exit: Com port closed: exiting
23.04.2021 01:22:33: FormClosing: Start
23.04.2021 01:22:33: ExtraSettings Form is closing
23.04.2021 01:22:33: DelayOnConnect :
23.04.2021 01:22:33: SerialReadTimeOut :
23.04.2021 01:22:33: StatusMsgClrDelay :
23.04.2021 01:22:33: MaxFocuserLimit : 2000000000
23.04.2021 01:22:33: StepSize :
23.04.2021 01:22:33: Temp Coefficient :
23.04.2021 01:22:33: Backlash IN : False
23.04.2021 01:22:33: Backlash OUT : False
23.04.2021 01:22:33: Backlash IN Steps :
23.04.2021 01:22:33: Backlash OUT Steps:
23.04.2021 01:22:33: BL Send on Connect: False
23.04.2021 01:22:33: Temp Direction : False
23.04.2021 01:22:33: Temp Comp Update On Connect : False
23.04.2021 01:22:33: FormClosing: Serial port not connected
23.04.2021 01:22:33: FormClosing: Save application settings
23.04.2021 01:22:33: FormClosing: Stop timers
23.04.2021 01:22:33: FormClosing: Finish
23.04.2021 01:22:33: FormClosing: Start
23.04.2021 01:22:34: ExtraSettings Form is closing
23.04.2021 01:22:34: DelayOnConnect :
23.04.2021 01:22:34: SerialReadTimeOut :
23.04.2021 01:22:34: StatusMsgClrDelay :
23.04.2021 01:22:34: MaxFocuserLimit : 2000000000
23.04.2021 01:22:34: StepSize :
23.04.2021 01:22:34: Temp Coefficient :
23.04.2021 01:22:34: Backlash IN : False
23.04.2021 01:22:34: Backlash OUT : False
23.04.2021 01:22:34: Backlash IN Steps :
23.04.2021 01:22:34: Backlash OUT Steps:
23.04.2021 01:22:34: BL Send on Connect: False
23.04.2021 01:22:34: Temp Direction : False
23.04.2021 01:22:34: Temp Comp Update On Connect : False
23.04.2021 01:22:34: FormClosing: Serial port not connected
23.04.2021 01:22:34: FormClosing: Save application settings
23.04.2021 01:22:34: FormClosing: Stop timers
23.04.2021 01:22:34: FormClosing: Finish
Serial port not connected? Any ideas?
Thanks in advance
Mike
conformance tester says o errors btw
Hi Mike
if you are using ASCOM driver to access the controller - then in the setup dialog form that you use to select com port and speed, make sure that Trace is checked so that a logfile can be produced.
In windows systems, the logfile will be in a folder underneath Documents\ASCOM\logsxxxx
Please send me the ASCOM logs.
regards
Robert
will do tonight ;-)
Thanks Robert
Here you are Robert:
22:02:39.943 Focuser Starting initialisation
22:02:40.011 Focuser Completed initialisation
22:02:40.011 InterfaceVersion Get 2
22:02:40.043 Connected ASCOM Driver 2.7.8
22:02:40.043 Connected True
22:02:40.043 IsConnected Get False
22:02:40.043 START Connect Started
22:02:40.043 Connected Set = True
22:02:40.043 Connected Create serial port
22:02:40.049 Connected Get portname: COM3
22:02:40.050 Connected Get baudrate: 9600
22:02:40.051 Connected Setting baudrate to 9600
22:02:40.051 Connected Get ResetControllerOnConnect: True
22:02:40.051 Reset Controller On Conne True
22:02:40.052 Connected Set Receive Timeout = 5
22:02:40.510 Connected NotConnectedExceptionSystem.UnauthorizedAccessException: Access to the port 'COM3' is denied.[0D][0A] at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
22:02:40.518 Connected ASCOM.Driver Exception ERROR- if( value ): Possible serial port disconnect.[0A]ASCOM.NotConnectedException: Serial port connection error ---> System.UnauthorizedAccessException: Access to the port 'COM3' is denied.[0D][0A] at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)[0D][0A] --- End of inner exception stack trace ---[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
and this is the log directly with the App a few moments later.
Hope you are able to solve this :-)
Greetings
Mike
Last edit: CCDMike 2021-04-23
22:02:40.510 Connected NotConnectedExceptionSystem.UnauthorizedAccessException: Access to the port 'COM3' is denied.
Are you running NINA as an administrator?
There is a privledge issue here with NINA, in that access by NINA to the com ports is being denied.
There might be a forum on Nina where you can find this issue with a resolution.
regards
R
You are using firmware 294. This is out of date/not supported
Firmware 294 does NOT work with the ASCOM driver you are using or the Windows app you are using.
regards
Robert
For reference (these are NO longer supported or available) - Firmware 298 would require
Firmware 298-299
ASCOM Driver 2.7.3
Windows App - Probably 2.4.4.9
Last edit: brownrb 2021-04-24
Thanks Robert.
I will try to do that. Is there a dummy instruction for the FW update?