Thanks for resolving of FT-991/FT-991A CAT problem.
But It does not resolve on FT-897. Error message is "riglib error Target VFO unaccessible getting frequency" and CAT testing goes into  fales(RED).
I am using VFO A at this time and conneting with SCU-17 via USB. It works well under WSJT-X V 2.1.2.
--
7L1RLL / Rick

That’s why I suggested that be checked. If the wrong audio is ticked, it will appear that everything is working but no power output.

Gerry Klotz

Hi Gerald, when you click the speaker icon to go into sounds on speaker you see the various speaker alternatives including USB audio codec. The default audio speaker is Realtech (which has the green tick ) and the USB audio codec has the green telephone icon next to it. I believe that the default audio device is NOT meant to be the USB audio codec
Wayne VK4WTN 

Wayne click on the speaker icon on the bottom task bar. Make sure you have chosen the usb not the regular speakers.

KB9pki
Gerry Klotz

Hi Herb I will look in privacy settings I think it will be the speaker rather than microphone for TX
Cheers Wayne VK4 WTN

Thanks Bill as soon as I get home I will try the steps in the procedure and get back to the group
cheers Wayne VK4WTN

hi all, I hope someone can help me. I just changed my shack computer (Windows 10). I downloaded the driver from the Kenwood website ok. I run wsjt-x via DXCommander. Rig control via CAT is ok. Recieve decodes just fine , keys the TX via CAT ok but there appears to be no audio reaching the Kenwood TS590s. I am seeing " USB Audio codec in Sounds (speaker) and have the level turned to maximum. In Windows settings I have  2. USB AUDIO CODEC selected for both audio device both Tx and rx . The TX level slider on the wsjt-x is also set at maximum.
 The settings in the TS590s are fine as the radio still works on Tx and RX when my previous computer is reconnected.
any help would greatly be appreciated
Wayne VK4WTN

Hi Wayne,

please follow the steps in this old post on how to set Tx audio levels:

https://groups.io/g/WSJTX/message/5077

let us know if that doesn't get you up and running.

73
Bill
G4WJS.

hi all, I hope someone can help me. I just changed my shack computer (Windows 10). I downloaded the driver from the Kenwood website ok. I run wsjt-x via DXCommander. Rig control via CAT is ok. Recieve decodes just fine , keys the TX via CAT ok but there appears to be no audio reaching the Kenwood TS590s. I am seeing " USB Audio codec in Sounds (speaker) and have the level turned to maximum. In Windows settings I have  2. USB AUDIO CODEC selected for both audio device both Tx and rx . The TX level slider on the wsjt-x is also set at maximum.
 The settings in the TS590s are fine as the radio still works on Tx and RX when my previous computer is reconnected.
any help would greatly be appreciated
Wayne VK4WTN

On Jun 6, 2020, at 13:27, Gerald Klotz <KB9PKI@...> wrote:

If so, we will still have the added frequencies until we refresh them correct?

Do remember that you can add any frequency you want to the list in less than a minute.

Gary - AG0N

On Jun 6, 2020, at 17:23, Ted <k7trkradio@...> wrote:

Did I miss the memo? I thought 50.313 was the recommended spot for WSJT 6m. Is it now 50.323 ??

Not really. A few days ago, when .313 was plugged with activity, several took to the alternate of .323. Even that got fairly full for awhile, but did manage. Surprisingly, very few showed up on .318 FT4 frequency during that time. Not sure why.

I really hate spreading out over more than one frequency, because most people don’t have band scopes to discover all that alternate traffic. I know I’m in the minority though. Interestingly, I heard nothing on 50.125. :)

Gary - AG0N

I have the same problem with my FT-991A. Installed WSJT-X 2.2.0; then it would not communicated CAT controls via USB; however, it would communicate the audio signals and decode from the radio on the PC. Oddly enough, starting WSJT-X also turned on the radio - behavior that I had never had before.

Then when I went back to the previous version - 2.1.2 - of WSJT-X; all hell broke loose. IT would not communicate via CAT; as well, the radio didn't like it. I got a flashing TX symbol for about 8 seconds; and then the radio went into transmit mode; no idea what was being transmitted. I had to kill power to shut down the radio. This kept happening. A subsequent install of 2.2.0 and then reinstall of 2.1.2 had it working properly again. I have tried version 2.2.0 several times; made changes and tests with the CAT settings - nothing gets it to work. I get the following error:



73,
W2ZF

Hi Ralph,

please read the release notes for the latest WSJT-X v2.2.1 release.

73
Bill
G4WJS.

On 06/06/2020 20:55, Steven - DL8SE wrote:

Hi guys,

I am relatively new to digital modes, so please bear with me if I ask beginner questions.

I haven't found the error using the search topic, so it might be new / easy to solve.

I have the following settings in WSJTX:

Rig: Yaesu FT-817

CAT
Serial Port. /dev/ttyUSB0
Baud: 38400
Data Bits: Default
Stop Bits: Default
Handshake: Default
Force Control lines: N/A (none set

PTT-Method :CAT

Mode: Data /PKT
Split: None

My configuration appearantly gives me the following error(s) Every other TX cycle it gives me the hamlib error IO error while setting PTT off. This happens irregularly, sometimes every 2nd / 3rd TX cycle, sometimes every 4th. This happens at the end of the transmission. It also happens with a dummy load attached.
If I set the PTT-Method to VOX, it also gives me an error at the end of the transmission: Hamlib error: Command rejected by the rig while exchanging VFOs

My first instinct was that my USB cables were the reason, so I put RF chockes on all 3 cables (and all 6 ends). Might I need to attach more as it did seem to lessen the occurence of the problem.

Thanks for any clues and 73 from Germany,

Steven DL8SE

Hi Steven,

the FT-817/857897(D) series of rigs will no accept CAT QSY commands while in SEND mode, this means you must have the WSJT-X option "Setting->General->Allow Tx frequency changes while transmitting" unchecked. Further, if you are using a SignaLink USB interface you need to reduce the DELAY knob to the minimum.

73
Bill
G4WJS.

FYI - running Windows 10 Pro - same prob with my FT-991A.

GM all,
I installed WSJT-X 2.2.1 this morning and when I tried to lookup an EME station who is in my call3.txt the program could not find his locator and I had to manually enter it.
I then attempted to look up another known EME station to see whether he had moon or not and again I did not get the correct lookup response and had to I manually update his details.
The problem seems to be that it's not looking up the call3.txt file correctly nor updating the data in the astronomical data pane.
I'm not sure whether this is finger trouble on my end or something I did wrong on the install.
Any help would be appreciated.
Thanks,
Chris zl7dx

I have the same problem with my FT-991A. Installed WSJT-X 2.2.0; then it would not communicated CAT controls via USB; however, it would communicate the audio signals and decode from the radio on the PC. Oddly enough, starting WSJT-X also turned on the radio - behavior that I had never had before.

Then when I went back to the previous version - 2.1.2 - of WSJT-X; all hell broke loose. IT would not communicate via CAT; as well, the radio didn't like it. I got a flashing TX symbol for about 8 seconds; and then the radio went into transmit mode; no idea what was being transmitted. I had to kill power to shut down the radio. This kept happening. A subsequent install of 2.2.0 and then reinstall of 2.1.2 had it working properly again. I have tried version 2.2.0 several times; made changes and tests with the CAT settings - nothing gets it to work. I get the following error:



73,
W2ZF

Hi guys,

I am relatively new to digital modes, so please bear with me if I ask beginner questions.

I haven't found the error using the search topic, so it might be new / easy to solve.

I have the following settings in WSJTX:

Rig: Yaesu FT-817

CAT
Serial Port. /dev/ttyUSB0
Baud: 38400
Data Bits: Default
Stop Bits: Default
Handshake: Default
Force Control lines: N/A (none set

PTT-Method :CAT

Mode: Data /PKT
Split: None

My configuration appearantly gives me the following error(s) Every other TX cycle it gives me the hamlib error IO error while setting PTT off. This happens irregularly, sometimes every 2nd / 3rd TX cycle, sometimes every 4th. This happens at the end of the transmission. It also happens with a dummy load attached.
If I set the PTT-Method to VOX, it also gives me an error at the end of the transmission: Hamlib error: Command rejected by the rig while exchanging VFOs

My first instinct was that my USB cables were the reason, so I put RF chockes on all 3 cables (and all 6 ends). Might I need to attach more as it did seem to lessen the occurence of the problem.

Thanks for any clues and 73 from Germany,

Steven DL8SE