Go Back   IceInSpace > Equipment > Software and Computers

Reply
 
Thread Tools Rate Thread
  #1  
Old 26-06-2021, 04:34 PM
rogerg's Avatar
rogerg (Roger)
Registered User

rogerg is offline
 
Join Date: Feb 2006
Location: Perth, Western Australia
Posts: 4,561
Question COM ports not visible to ASCOM

I wonder if anyone has had the experience where COM ports show up normally in Device Manager but ASCOM simply doesn’t see them at all?

When I say “doesn’t see them at all” what I mean is the dropdown of COM port selection in ASCOM settings is empty. Simply nothing there to select, while at the same time Device Manager shows ports for two distinct devices.

I have uninstalled and reinstalled ASCOM and it’s delivers several times, installing as both Administrator and as not.

Details:
- Windows 10
- USB COM ports
- TheSkyX can see the COM ports
- Serial debugging software can see the COM ports
- ASCOM cannot see the COM ports

Next step is format and start from scratch again.

Thanks,
Roger.
Reply With Quote
  #2  
Old 26-06-2021, 04:53 PM
Pepper (Steve)
Registered User

Pepper is offline
 
Join Date: Dec 2018
Location: Daruka
Posts: 328
Are you using an eqdir cable to connect?
If so download the drivers from ftdi.com?? You’ll have to search
It essentially makes the USB device appear as a com port.
Reply With Quote
  #3  
Old 26-06-2021, 05:05 PM
rogerg's Avatar
rogerg (Roger)
Registered User

rogerg is offline
 
Join Date: Feb 2006
Location: Perth, Western Australia
Posts: 4,561
Quote:
Originally Posted by Pepper View Post
Are you using an eqdir cable to connect?
If so download the drivers from ftdi.com?? You’ll have to search
It essentially makes the USB device appear as a com port.
Hi Steve,

For the EQ8 mount I have tried both eqdir with various drivers including fadi.com and the SkyWatcher USB adapter device also. Both result in the same scenario of a COM port visible in device manager but not visible in ASCOM.

The other device I am trying is the Celestron focus motor which has a direct USB cable from focus motor to PC. That shows up in Device Manager as COM 4, the Focus utility from Celestron can connect to it (it does not provide any COM port selection, just ‘auto detects’). But again COM4 is not visible in ASCOM at all.

Thanks,
Roger.

Last edited by rogerg; 26-06-2021 at 05:06 PM. Reason: fix typo
Reply With Quote
  #4  
Old 26-06-2021, 05:12 PM
rogerg's Avatar
rogerg (Roger)
Registered User

rogerg is offline
 
Join Date: Feb 2006
Location: Perth, Western Australia
Posts: 4,561
A picture speaks a thousand words so here's a screenshot illustrating the situation.
Attached Thumbnails
Click for full-size image (2021-06-26 15_08_52-Telescope1a - TeamViewer.jpg)
177.4 KB27 views
Reply With Quote
  #5  
Old 27-06-2021, 10:09 AM
Pepper (Steve)
Registered User

Pepper is offline
 
Join Date: Dec 2018
Location: Daruka
Posts: 328
Sorry mate IT is my Achilles heel.
I reached my ceiling on that one!
Reply With Quote
  #6  
Old 27-06-2021, 10:45 AM
rogerg's Avatar
rogerg (Roger)
Registered User

rogerg is offline
 
Join Date: Feb 2006
Location: Perth, Western Australia
Posts: 4,561
Haha, al good

Much discussion has ensued on the ASCOM support groups.io forum and it seems not ASCOM but either the ASCOM device drivers or some other drivers on the PC are the issue. At least it's narrowed the problem down slightly.

It turns out the ASCOM diagnostics tool can see the COM ports but the specific drivers are refusing to use them.

Roger.
Reply With Quote
  #7  
Old 27-06-2021, 12:09 PM
redbeard's Avatar
redbeard (Damien)
Registered User

redbeard is offline
 
Join Date: Nov 2010
Location: Adelaide
Posts: 512
When you install the specific accom driver for your device, was there a message about driver signing? If so, was the message indicating that the driver installation was all good or was there a message stating that there might be an issue but go ahead and install anyhow? If the latter, there might be an issue with the drivers digital signature. A later device accom driver may help as Win10 always needs correctly signed drivers to work. That may explain why the direct drivers work for the device but not the accom.

Good luck.

Cheers,
Damien
Reply With Quote
  #8  
Old 27-06-2021, 02:15 PM
Sitt (Simon)
Registered User

Sitt is offline
 
Join Date: Jul 2007
Location: Perth
Posts: 49
I recon you may have a conflict, try removing the USB Dongle - could be they are both trying to use COM1. If so, you will have to allocate one device another COM Port
Reply With Quote
Reply

Bookmarks

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +10. The time is now 12:16 AM.

Powered by vBulletin Version 3.8.7 | Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.
Advertisement
Testar
Advertisement
NexDome Observatories
Advertisement
Bintel
Advertisement
Limpet Controller
Advertisement
Astronomy and Electronics Centre
Advertisement