I built myFocuserPro2 v270 on a arduino nano with an L298N, NEMA-14 motor,
and temp probe.
All works great, and I can control everything through the Windows app via
the com port (Windows 10 running on an Intel CS125 Compute Stick). All
functions work, and I can control all motor movement, and I get back a good
temperature reading.
However, when I try to use the ascom interface, it can't connect to the com
port. I've tried different usb cables, different usb ports, different hubs,
a new arduino nano, and I still get the same results.
I have no trouble with other ascom connected devices (celestron mount and
zwo filter wheel), but I went ahead and re-installed the latest ascom core,
plus I've tried older versions of the ascom myfocuserpro2 driver (both
versions 249 and 259). The device shows up in the list, and I'm able to
select the settings and click "connect", but when ascom tries to connect,
there's always an issue connecting to the com port.
I get the error from myfocuserpro2 ascom tester, the ascom diagnostics app,
SGP, and other ascom-enabled apps.
I've also tried the registry permission fixes for ascom problems under
windows 10, with no changes.
I'm not sure what else to do at this point. There definitely seems to be an
issue with ascom connecting to the com port.
Hi Chris
You say that
I get the error from myfocuserpro2 ascom tester, the ascom diagnostics app,
SGP, and other ascom-enabled apps.
Are you running an anti-virus such as bitdefender. The fact that is is happening with a number of drivers/apps seems to point to a permissions issue
ASCOM loves to write to the Documents\ASCOM folder to create log files. If it does not have persmission to do so, then you can see the driver but when you try to load the driver it will fail. Can u post a screen shot of the error?
I suspect that this is the case.
Try running the confirm program - select the focuser and see if you can access the setup dialog/
Also try running the Profile explorer - under Focuser Drivers,ASCOM.myFocuser2ASCOM.Focuser set the TraceEnabled parameter to False and then try again.
Regards
Robert
Last edit: brownrb 2018-05-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried opening up permission on Documents\ASCOM (to Everyone full permissions), and that didn't seem to work, so I did the same for the full Documents folder, with no change.
I disabled the firewall (just the built in windows firewall), and no change.
I enabled Trace, reran, and have attached the log file below.
I believe the two lines you're looking for are:
18:54:20.262 CS: Exception System.Runtime.InteropServices.COMException (0x80040402): Timed out waiting for received data[0D][0A] at ASCOM.Utilities.Serial.ReceiveTerminated(String Terminator) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 1204[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.CommandString(String command, Boolean raw)
18:54:20.262 Connected ASCOM.Driver Exception ERROR- if( value ): Possible serial port disconnect.[0A]ASCOM.DriverException: Serial port connection error ---> System.Runtime.InteropServices.COMException: Timed out waiting for received data[0D][0A] at ASCOM.Utilities.Serial.ReceiveTerminated(String Terminator) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 1204[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.CommandString(String command, Boolean raw)[0D][0A] --- End of inner exception stack trace ---[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.CommandString(String command, Boolean raw)[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
I also tried to bump up the SerialPortReadTimeout in ASCOM Profile Explorer, but that didn't seem to make a difference either.
18:54:15.246 Connect Get StepSize
18:54:15.246 CS: :33#
18:54:15.246 CS: Get StepSize cmd= :33#
18:54:20.262 CS: Exception System.Runtime.InteropServices.COMException (0x80040402): Timed out waiting for received data[0D][0A] at ASCOM.Utilities.Serial.ReceiveTerminated(String Terminator) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 1204[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.CommandString(String command, Boolean raw)
I'm not sure what I did wrong - I double checked, and I used the same file (at least, the same file name), so I can only presume you changed something. Either way, I was able to upload the file and connect both through ASCOM diagnostics and via SGP. I'll need to wire up everything again to do a full test, but at least it all the software seems to be working.
Thanks so much for your help, and thanks for providing such a useful package for the astro world!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all-
I built myFocuserPro2 v270 on a arduino nano with an L298N, NEMA-14 motor,
and temp probe.
All works great, and I can control everything through the Windows app via
the com port (Windows 10 running on an Intel CS125 Compute Stick). All
functions work, and I can control all motor movement, and I get back a good
temperature reading.
However, when I try to use the ascom interface, it can't connect to the com
port. I've tried different usb cables, different usb ports, different hubs,
a new arduino nano, and I still get the same results.
I have no trouble with other ascom connected devices (celestron mount and
zwo filter wheel), but I went ahead and re-installed the latest ascom core,
plus I've tried older versions of the ascom myfocuserpro2 driver (both
versions 249 and 259). The device shows up in the list, and I'm able to
select the settings and click "connect", but when ascom tries to connect,
there's always an issue connecting to the com port.
I get the error from myfocuserpro2 ascom tester, the ascom diagnostics app,
SGP, and other ascom-enabled apps.
I've also tried the registry permission fixes for ascom problems under
windows 10, with no changes.
I'm not sure what else to do at this point. There definitely seems to be an
issue with ascom connecting to the com port.
Any ideas would be greatly appreciated!
-chris
Hi Chris
You say that
I get the error from myfocuserpro2 ascom tester, the ascom diagnostics app,
SGP, and other ascom-enabled apps.
Are you running an anti-virus such as bitdefender. The fact that is is happening with a number of drivers/apps seems to point to a permissions issue
ASCOM loves to write to the Documents\ASCOM folder to create log files. If it does not have persmission to do so, then you can see the driver but when you try to load the driver it will fail. Can u post a screen shot of the error?
I suspect that this is the case.
Try running the confirm program - select the focuser and see if you can access the setup dialog/
Also try running the Profile explorer - under Focuser Drivers,ASCOM.myFocuser2ASCOM.Focuser set the TraceEnabled parameter to False and then try again.
Regards
Robert
Last edit: brownrb 2018-05-19
Thanks for the detailed reply.
I tried opening up permission on Documents\ASCOM (to Everyone full permissions), and that didn't seem to work, so I did the same for the full Documents folder, with no change.
I disabled the firewall (just the built in windows firewall), and no change.
I enabled Trace, reran, and have attached the log file below.
I believe the two lines you're looking for are:
18:54:20.262 CS: Exception System.Runtime.InteropServices.COMException (0x80040402): Timed out waiting for received data[0D][0A] at ASCOM.Utilities.Serial.ReceiveTerminated(String Terminator) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 1204[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.CommandString(String command, Boolean raw)
18:54:20.262 Connected ASCOM.Driver Exception ERROR- if( value ): Possible serial port disconnect.[0A]ASCOM.DriverException: Serial port connection error ---> System.Runtime.InteropServices.COMException: Timed out waiting for received data[0D][0A] at ASCOM.Utilities.Serial.ReceiveTerminated(String Terminator) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 1204[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.CommandString(String command, Boolean raw)[0D][0A] --- End of inner exception stack trace ---[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.CommandString(String command, Boolean raw)[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
I also tried to bump up the SerialPortReadTimeout in ASCOM Profile Explorer, but that didn't seem to make a difference either.
Any other ideas?
Hi Chris
The problem is here
18:54:15.246 Connect Get StepSize
18:54:15.246 CS: :33#
18:54:15.246 CS: Get StepSize cmd= :33#
18:54:20.262 CS: Exception System.Runtime.InteropServices.COMException (0x80040402): Timed out waiting for received data[0D][0A] at ASCOM.Utilities.Serial.ReceiveTerminated(String Terminator) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 1204[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.CommandString(String command, Boolean raw)
Its failing on Get Stepsize.
Try attached firmware file
This ino file fixed the problem!
I'm not sure what I did wrong - I double checked, and I used the same file (at least, the same file name), so I can only presume you changed something. Either way, I was able to upload the file and connect both through ASCOM diagnostics and via SGP. I'll need to wire up everything again to do a full test, but at least it all the software seems to be working.
Thanks so much for your help, and thanks for providing such a useful package for the astro world!
Was my fault - sorry - left out a bot code when moving to v270 for that file