CAT control doesn't seem to be working fully

[n4hcr]

I'm using Log4OM2 with an FT-920. It was working fine until a couple of hours ago, but now the rig control function doesn't seem to work. I'm using Omnirig as the COM interface. Log4OM can read information from the rig, but it doesn't seem to be able to control it. When I try to transmit using WSJT-X, the Slgnalink USB shows the PTT light as transmitting, but the rig doesn't actually transmit. When I try a function from LOG4OM, it doesn't actually control the rig, even though it can see the rig and display the frequency, etc. The CAT indicator on the rig flashes.

I had moved the rig before that to run a cable behind the radio, but didn't unplug anything.

Any thoughts?

Wayne Rash N4HCR

[G4POP]

I had a windows update yesterday that screwed my USB Audio codecs and com ports, so it could be that

[n4hcr]

I've gone through those, and it still isn't working. I also checked the SignaLink settings, and they seem correct.

[G4POP]

Have you tried disconnecting and reconnecting all the cables?

[n4hcr]

Yes. It worked for a while today, then didn't.

[KI5IO]

Yes. It worked for a while today, then didn't.

Wayne,

I've experienced similar (USB connection from laptop to K3 going to sleep) for years.

Some of the elements I stepped through were to make sure that all sleep, hibernation items were turned off. I made sure all the USB drivers (in Device Manager) were set to never sleep/hibernate or let the Windows O/S do anything to the USB port I used.

I was "mostly" successful, but the Windows O/S being what it is would still take control and shut off the port from the laptop to the K3.

My resolution (when I noted it) was to simply unplug the USB cable, wait a moment, and then plug it back it so the O/S would recognize it again.

Granted a PIA, but the unplug/replug routine has worked for me.

Everytime the laptop was rebooted or had an update the USB port would not be communicating ... until I unplugged/replugged.

Still don't have a perfect answer and I pretty much blame the Windows O/S as I don't have to have Log4OM V2 running to have the port go inactive.