Bill,

The errors I am getting are not easy to reproduce but I also always get a sound card error - sorry I thought it was a Hamlib error and I was writing from memory. I have been ignoring this to some extent as I always get one of two Hamlib errors: IO error while opening connection to rig or IO error while getting current frequency.

The sound card error (in both cases) is: Error in sound O/P. Requested I/P audio format is not supported on device.

Most times the sound config does not display the USB audio codec option but occassionally I get a (2 - USB audio DEVICE option. I have tried plugging the cable into both USB2 and USB ports but the results are the same.The audio device option is related to the virtual USB device ports.

I know there is a problem with Asus motherboards but I installed a new driver for the sensor device - AMDA00 and now I consistently get the Virtual COM ports showing in Device Manager but I am either not connecting to the rig or cannot read the frequency. I know my rig setup is fine as it is the same for my main PC (the one giving problems) and for my laptop (which works fine and made a contact this evening).

I really would like to get WSJT working on my main PC.

73 George

Thank you all for the suggestions. It seems it was an issue with the com port, unchecking 'use FIFO buffers' solved the problem.

Bill

I don't have a screen shot, but this is the text:

Hamlib error: Communication timed out while opening connection to rig

Again, I don't think its a WSTJ-X issue. I think its something in the USB or the computer power management.

Thanks again. If it does it again I'll get a screen shot. Fickle 40 has been either dead or the noise levels are so high I have not made an FT8 qso all day. 30m and 80m no better at the moment here.
Frank
KB3PQT


--
This email has been checked for viruses by AVG.
https://www.avg.com

On 26/12/2020 18:57, George Nelson wrote:

Chris,

I am having a similar problem with a Hamlig errors using my FT991A. I have WSJT running on my laptop with no issues but it won't run on my main PC - both run Window 7. I can't help you with your issue but I'd suggest looking at Device Manager when you plug the USB cable into your PC (assuming you are running Windows). What you want to look for is Ports and LPT and open it if it is not already open. The issues I see explain the two errors I am seeing - I just don't understand why.

I don't have any COM ports at all on my PC - the Ports & LPT sometimes does not appear and I get a Hamlib error that syas it can't connect to the rig. If it does appear there are two port entries (on my system COM4 is the enhanced COM port and COM3 is the standard COM port). If I get a connection to the rig I get a Hamlib error warning that the audio config is not correct. Again, I have one of two situations - either there is no audio Codec entry in the audio settings or I get an Audio USB device option rather than Audio USB Codec option. In either case I can't fix the audio setup error.

The interesting thing that happens when I plug the rig USB cable into my PC - first the USB devices list opens and there can be 1, 2 or 3 entries flagged as in error and no Ports & LPT item appears. Two of the flagged errors will be for USB2 or USB3 devices depending on which type of USB socket you typed it into - the other error is for an AMDA00 device and I don't know what that is. However, if the one or both of the other 2 errors correct themselves the Ports and LPT item appears and there will be two new COM ports. If I see this I manage to connect to the rig and successfully run the Test CAT and Test PTT in the radio setup. However I have on the audio setting I either have no Audio USB Codec option or an Audio USB Device option is available but the latter does not solve the audio connection problem.

I did research the AMDA00 error and it may be the cause of my problems - apparently it is a bug with Asus mptherboards (which is the one that is giving me my problems) and the solution is to update the driver for this. This error only appears when I plug the rig USB cable in and disappears when I unplug it. I've not managed to find the driver on the Asus webset so been unable to try an updated driver but if your PC has an Asus motherboard it may be the cause of the problem.

Sorry this doesn't help you solve your problem but hopefully gives you a path to pursue. If you have an Asus motheboard and I do find the appropriate driver, I'll post again and let you know. However the Device Manager is worthwhile looking at as you plug and/or unplug your rig USB cable - it may point you to an issue with the USB connection to the rig. Also well worth double checking your rig settings.

Good luck,

73 George M0MGN

George,

there are no Hamlib error messages about audio, Hamlib has nothing to do with audio connections between your rig and PC.

If you are getting an error message from WSJT-X then please include the full text of the error message including the details.

For rigs with internal USB audio and CAT control that are powered from the rig rather than the USB bus 5V line you should ensure that programs like WSJT-X that use those connections are shut down before you power off the rig, and conversely make sure the rig is powered up be starting such applications. You can check if you have such a rig by powering it on and subsequently off while watching Windows Device Manager, if the audio and virtual COM port devices come and go then the rig is powering its internal USB controller rather than it being powered from the USB bus 5V line.

73
Bill
G4WJS.

On 26/12/2020 19:15, Frank Mellott wrote:

Good affternoon
I have been running a Yaesu FTDX-1200 using flrig for cat contol with WSJT-X and JTAlert for a couple years.   I get the occasional hamlib error, but today i encountered something I wasted 2 hours on and it seems to have healed itself.  Your FT991A issues sound similar.

Yesterday I turned the computer off as normal.  Today I started it, started flrig, WSJTX, N3FJP call log and JT Alert and everything was good.  That lasted until I tried to transmit and immediately the "hamlib" error unable to communicate popped up.  I closed it down and restarted.  COM9 where the radio plugs into the computer seemed active..then it was not.   I double checked the power management and windows still showed set to never power down UBS ports.  I was stumped.   I restarted the computer and it would be good for a couple minutes, then my various back up drives would pop up like the USB cables were just plugged in.   That made me think something was amiss,  so I went back through power management and triple checked everything.
I prowled around the internet looking for ideas and came up dry. I was pretty irritated by this point so I shut everything down. Came back a couple hours later and everything seems fine.

I cannot find it, but I think something in windows is the culprit, unless it is some fault in the USB.

Not sure, but really sure it is not a WSJT-X or flrig or N3FJP issue.
Any ideas appreciated.

Thanks
Frank
KB3PQT

Frank,

if you are using flrig to control you rig you will not get Hamlib errors in WSJT-X. Please tell us the exact error message, including details, you are getting from WSJT-X?

73
Bill
G4WJS.

Good affternoon
I have been running a Yaesu FTDX-1200 using flrig for cat contol with WSJT-X and JTAlert for a couple years. I get the occasional hamlib error, but today i encountered something I wasted 2 hours on and it seems to have healed itself. Your FT991A issues sound similar.

Yesterday I turned the computer off as normal. Today I started it, started flrig, WSJTX, N3FJP call log and JT Alert and everything was good. That lasted until I tried to transmit and immediately the "hamlib" error unable to communicate popped up. I closed it down and restarted. COM9 where the radio plugs into the computer seemed active..then it was not. I double checked the power management and windows still showed set to never power down UBS ports. I was stumped. I restarted the computer and it would be good for a couple minutes, then my various back up drives would pop up like the USB cables were just plugged in. That made me think something was amiss, so I went back through power management and triple checked everything.
I prowled around the internet looking for ideas and came up dry. I was pretty irritated by this point so I shut everything down. Came back a couple hours later and everything seems fine.

I cannot find it, but I think something in windows is the culprit, unless it is some fault in the USB.

Not sure, but really sure it is not a WSJT-X or flrig or N3FJP issue.
Any ideas appreciated.

Thanks
Frank
KB3PQT

--
This email has been checked for viruses by AVG.
https://www.avg.com

Chris,

I am having a similar problem with a Hamlig errors using my FT991A. I have WSJT running on my laptop with no issues but it won't run on my main PC - both run Window 7. I can't help you with your issue but I'd suggest looking at Device Manager when you plug the USB cable into your PC (assuming you are running Windows). What you want to look for is Ports and LPT and open it if it is not already open. The issues I see explain the two errors I am seeing - I just don't understand why.

I don't have any COM ports at all on my PC - the Ports & LPT sometimes does not appear and I get a Hamlib error that syas it can't connect to the rig. If it does appear there are two port entries (on my system COM4 is the enhanced COM port and COM3 is the standard COM port). If I get a connection to the rig I get a Hamlib error warning that the audio config is not correct. Again, I have one of two situations - either there is no audio Codec entry in the audio settings or I get an Audio USB device option rather than Audio USB Codec option. In either case I can't fix the audio setup error.

The interesting thing that happens when I plug the rig USB cable into my PC - first the USB devices list opens and there can be 1, 2 or 3 entries flagged as in error and no Ports & LPT item appears. Two of the flagged errors will be for USB2 or USB3 devices depending on which type of USB socket you typed it into - the other error is for an AMDA00 device and I don't know what that is. However, if the one or both of the other 2 errors correct themselves the Ports and LPT item appears and there will be two new COM ports. If I see this I manage to connect to the rig and successfully run the Test CAT and Test PTT in the radio setup. However I have on the audio setting I either have no Audio USB Codec option or an Audio USB Device option is available but the latter does not solve the audio connection problem.

I did research the AMDA00 error and it may be the cause of my problems - apparently it is a bug with Asus mptherboards (which is the one that is giving me my problems) and the solution is to update the driver for this. This error only appears when I plug the rig USB cable in and disappears when I unplug it. I've not managed to find the driver on the Asus webset so been unable to try an updated driver but if your PC has an Asus motherboard it may be the cause of the problem.

Sorry this doesn't help you solve your problem but hopefully gives you a path to pursue. If you have an Asus motheboard and I do find the appropriate driver, I'll post again and let you know. However the Device Manager is worthwhile looking at as you plug and/or unplug your rig USB cable - it may point you to an issue with the USB connection to the rig. Also well worth double checking your rig settings.

Good luck,

73 George M0MGN

On 25/12/2020 23:33, chrisdg4kvi@... wrote:

Merry Christmas. I recently loaded MMSSTV to receive the ISS. All seems fine but now WSJT is reporting a Hamlib error. Tried everything (obviously not) so does anyone have any ideas? This has been working fine until today.

OM,

there's little we can help you with if you do not share the error message, including the details. Hint, on MS Windows, if you get message box from WSJT-X, hit Ctrl+C as soon as it appears. That copies the whole contents of the message box text to the Windows clipboard ready to be pasted into a reply here.

73
Bill
G4WJS.

Well, the mystery continues. Downloaded Flrig and that now works fine with WSJT. Obviously not ideal but very strange that all the CAT commands work with that and still Hamlib error when trying WSJT 'standalone'

I've experienced several ham applications that do not exit cleanly.  Some may not release a COM port, while others may not release CAT control.   I always stress to be sure and close the program correctly.  Thus use FILE and EXIT, CLOSE or QUIT depending on how it is defined. 

I will say I have not had an incident with WSJT-X current release.   I've two different brands/models of radios which I use.  

As to HRD, I've had issues with that application not making a proper or clean exit with one brand/model of radio.   That appears to be in the USB communications between the computer application and the radio.  Who is to blame?   Dang if I know.  Neither company wants to accept responsibility and says it is the other company's fault.   Translation:   They have my money and don't care.

73

Bob, K4TAX

Did the previous program release the COM port?    That may be the issue.  I'd shut everything down, restart the computer (do not shut down as it actually does a hibernation save of the current state) and see if it still happens.

Neil, KN3ILZ

Merry Christmas. I recently loaded MMSSTV to receive the ISS. I also used the RT systems to safe the memories. All seemed fine but now WSJT is reporting a Hamlib error. Tried everything (obviously not) so does anyone have any ideas? This has been working fine until today.