locked Re: WSJT-X and JT Alert Conflicting
toggle quoted messageShow quoted text
#1 Ensure that there are no green icons on the rig audio device in "Sound Control Panel".
Should look like this:
And not like this:
If you have green icons on your rig audio device then right-click your computer speaker device and select these two items.
The green icons on your rig audio device will disappear.
#2 Do the same for both Playback (the really important one) and Recording (not so important and actually optional or may not be able to be set if you don't have a mic in your computer).
#3 Make sure WSJT-X audio devices are pointing to rig audio (e.g. USB Audio CODEC) and not "Default".
#4 Get some decent chokes (not from Ebay please) and put them on your USB cable on both sides. Remember all cables are antennas.
RFI in the shack can be pretty subtle to really ugly. There can be just enough to mess with the USB protocol or enough to mess with the USB 5V power which will cause device resets. Either one can affect any program talking to the USB audio or CAT control.
On Thursday, January 7, 2021, 12:44:06 AM CST, Scott Armstrong <aa5am@...> wrote:
FWIW... I have experienced the same thing Dave K5HC is reporting.
WSJT-X keys the radio and there is no audio (tones generated) or RF power output. The problem is intermittent and occurs infrequently.
The problem does not appear to be frequency dependent as I have had it occur on various bands from 160m to 6m and possibly 2m which is a totally different radio/configuration.
My work around has been to 'Halt' WSJT-X and then 'Enable" again. Then there is audio and RF power output.
The issue is not RFI related as there is no RF being generated because of the lack of tones.
My configuration is totally different from what Dave has:
WSJT-X v2.2.2 or v2.3.0-rcX and past versions
JTA currently 2.16.17 but has also occurred on past versions
ASUS XonarU5 (external USB sound card)
HP xw4400 workstation dual core 2.13 GHz 6GB RAM
Win7 Pro SP1
I have never considered JTA to be the issue but will try killing it the next time the problem occurs and see what the result is.
My gut feel is that it's a race condition/resource issue with WSJT-X.
On Wed, Jan 6, 2021 at 10:21 PM Jamie GOLLY <k6ngn@...> wrote: