Hi Bob, it might work but you should test before trying it out with a real F&H situation. With QSOs being logged at potentially 100's per hour you want to be sure it is all performing as expected. I d

Hi again, sorry, I thought I might get away with a small inline image but it was not small enough and got stripped by Groups.io. You can find the image here: https://www.dropbox.com/s/fwo8fibdvnnarfu/

Hi Dave and Andy, the first thing I need to understand is why are port number 5002 and 5004 being mentioned in this thread. The default port Command listens for CAT commands from WSJT-X if 52002 and a

Hi Norman, I believe the TS-570 will only take Tx audio from the rear ACC socket when it is keyed via the PKS pin on that socket, the SignaLink USB will do that autonomously without any PTT input from

Hi Ed, I and others get this regularly because we have the log file in a directory managed by Dropbox, going to Config->Log and pushing the Open button always successfully opens the log and everything

Hi Jim, you didn't mention JTAlert but that audio message sounds like one it might emit. If you have system sounds going to your rig then there are two possibilities, either you have a separate sound

Hi Jamie, "CAT" is the correct selection if Commander is able to key the rig.

Hi Dave, Ah, ok. I don't have a CAT capable Kenwood rig. If Commander thinks it is a 590 then that would seem to be the problem. 73 Bill G4WJS.

Hi Curt, I'm not sure what you mean by "thinks I'm running a TS-590"? You pick the rig in Commander. The mode arrangement for the TS-590 is very different from the TS-990, if Commander is set to drive

Hi Curt, thanks for that. I assume the rig was switched on when this happens. What do you have selected for "Settings->Radio->Mode"? What mode shows in the Commander window when the WSJT-X error messa

Hi Curt, if you get to providing Dave with a debug log from Commander, it would also be helpful to know what the WSJT-X error message said, including the details. You can conveniently copy the whole t

Thanks for the update Dave, the next release candidate of WSJT-X v2.1.0 will be consistent with that.

Hi André, make sure that you are not running WSJT-X as Administrator as that will block communications with other applications. Make sure no other application is set up to communicate with WSJT-X usin

Hi Andy, it is not provided exclusively for Commander, there are reasons why a user may not wish to have WSJT-X control their rig's mode, whatever mechanism is used for CAT control. It works the same

Hi Dave, which is exactly what it does if the options in WSJT-X to have it control the rig's mode are used. 73 Bill G4WJS.

Hi Dave, the most notable one is that queries after a change sometimes do not reflect the change just asked for. I have hoisted dealing with this up to a higher level in WSJT-X so that for all CAT met

Hi Andy, oops, sorry my bad, I thought you were using a K3. Anyway, WSJT-X when using Commander as a rig control proxy has to do some things that have been found to be necessary for specific rigs even

Andy, the root problem with the K3 is the ridiculous time taken for that rig to process some CAT commands which grows exponentially if the commands are repeated. 73 Bill G4WJS.

Hi Mark, neither Commander nor WSJT-X will work correctly using the VSPE serial port splitter or any other dumb (not protocol aware) serial port splitter.

HI Mark, make sure "CI-V Transceive Mode" is disabled on the rig.