Forums › SA Series Discussions › Missing SH Port Used in Device Manager
- This topic has 1 reply, 2 voices, and was last updated 2 years, 3 months ago by
Justin Crooks.
- AuthorPosts
Jay ZebrykParticipantHello,
After installation of the most recent update to Win10 on a 64Bit machine, I noticed that the Comm Port occupied by the SA44B is missing.
(This is after configuring windows to display all devices not in use.)
The unit works fine and I am wondering if it is now redefined as a “Sensor” or other by Windows?
Comm4 for example, is a FTDI serial adapter.
Comm1 is a U-Blox GPS unit.I think the SA44 is actually using Comm6?
This is a issue as I actually use many different USB devices and need to manage these.
From Spike, how can you tell which Comm Port is it using? (Again, normally it would be listed.)
Is the SA44B actually a HID device?Peace,
Jay Zebryk
Justin CrooksModeratorJay,
When everything is installed correctly, the SA44B should use the FTDI D2xx driver, not the FTDI virtual com port. It should show up under USB devices, but not under your list of COM ports. Hopefully this helps.- AuthorPosts
You must be logged in to reply to this topic.