[Elecraft] Rig control error with K3S and WSJT-X on 30 meters

[Bob McGraw]

Only one band?   Sounds like the classic RFI into the computer, the 
cables between the radio and computer.  Most likely common mode current 
on the feedline coming back down into the station area.   That would 
require common mode choke to be installed at the feed point of the 
antenna.  Might try a couple of turns of coax through a FT core and see 
if that helps.   A couple of clamp on beads on the cable between the 
radio and computer might help. But the antenna feed point is really the 
best place to censure common mode current.

Also......make sure every piece of station equipment is bonded to a 
common point.   I use the station power supply ground terminal for my 
common point.  Each piece of equipment has a dedicated jumper to this 
point.

73

Bob, K4TAX

On 4/21/2022 7:50 AM, elecraft-request at mailman.qth.net wrote:
> Message: 13
> Date: Mon, 18 Apr 2022 22:20:38 -0700
> From: Frank O'Donnell<vfo77 at inkbox.net>
> To:"elecraft at mailman.qth.net"  <elecraft at mailman.qth.net>
> Subject: [Elecraft] Rig control error with K3S and WSJT-X on 30 meters
> Message-ID:<792c3760-8000-ef9b-93d1-30dafa0605ed at inkbox.net>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Over a period of time I've noticed an occasional error when transmitting
> FT8 on 30 meters with my K3S using WSJT-X. A couple of seconds into a
> transmit cycle, WSJT-X will display a "Rig control error" box, and I
> start hearing the rig's modulated audio output on its own speaker. This
> only happens on 30 meters, and not 100% of the time. Over the past day,
> I've done FT8 QSOs normally on various bands, but when I tried 30 meters
> tonight I experienced the above error several times in a row. It's
> occurred over time using various versions of WSJT-X. The computer is a
> Mac running Catalina.
>
> I tried going into WSJT-X preferences and changing Radio > Split
> Operation from "Rig" to "Fake It," but the error persisted.
>
> I can try changing around various parts of the setup (using a Windows
> PC, for example), but first was curious if anyone has seen a
> band-specific error like this.
>
> Thanks,
>
> Frank K6FOD

-- 
IF ONE EXPECTS COMPUTERS AND TECHNOLOGY TO SOLVE THEIR PROBLEMS,
ONE DOESN'T UNDERSTAND COMPUTERS AND TECHNOLOGY
AND ONE DOESN'T UNDERSTAND THEIR PROBLEMS."