fldigi - Rig Control can't see Device (Com Port from CAT)

  • 1
  • Question
  • Updated 4 years ago
I had fldigi running perfectly prior to Windows 10 upgrade.  Now I try to set up the rig control and it doesn't see any of the com ports. I've reinstalled SDR to catch up on all the drivers and reinstalled fldigi and the XML file.  CAT appears to work correctly by providing the default COM 4.  but fldigi doesn't see the port.  I get no rig control or frequency info in fldigi.  DAX works fine and I can even transmit if I key manually on the SDR screen. Am I missing something?  Tnx 
Photo of Nick

Nick

  • 47 Posts
  • 2 Reply Likes

Posted 4 years ago

  • 1
Photo of George Molnar, KF2T

George Molnar, KF2T, Elmer

  • 1644 Posts
  • 600 Reply Likes
Did you uninstall all Flex software, including VSP, before upgrading? If not, go ahead and do so, removing drivers when asked. Reboot, make sure no ghost "hidden" ports exist in Device Manager, then reinstall. Good luck!
Photo of Nick

Nick

  • 47 Posts
  • 2 Reply Likes
yes,  completely uninstalled Flex S/W.  I had the same config on my laptop and have the same results on it. 
Photo of Nick

Nick

  • 47 Posts
  • 2 Reply Likes
added into:  Went to device manager and com 4 is listed as having problems.  tried to repair and got this error  Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19).  tried to search for driver and it couldn't be found.  Any ideas?
Photo of John n0snx

John n0snx

  • 229 Posts
  • 54 Reply Likes
Nick  delete all those comp ports  reboot computer.... then reload SSDR and reboot again and that should solve your com port issues...Then go into FLdigi and choose the correct com port and initiallize....  I had the same issue when I upgraded to win 10...
Photo of Walt - KZ1F

Walt - KZ1F

  • 3040 Posts
  • 645 Reply Likes
I was researching virual ports for Linux when I came across something that may be applicable . there was an issue with bad ftdi drivers. It may not be applicable in your case but something to check. It could be a software install sequencing issue and you have bad drivers. Not so much bad drivers per se but a change to the specs which manifests as bad drivers.
(Edited)
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9185 Posts
  • 3532 Reply Likes
Nick - does it work with other programs other than Fldigi?