RF caused communication problems are quite common, especially with USB
connections.
A pretty conclusive test is to try it while transmitting into a dummy load.
If it only fails with an antenna, then it's probably RF.

Victor 4X6GP

On Fri, Feb 13, 2026, 19:17 Jeff WB0M via Elecraft <[email protected]>
wrote:

> Hello All,
>
> A couple of times ny K3S has quit communicating with my MacBook Pro and
> macMini. For some reason, it no longer  “talked” with any digital logs or
> digital programs.
>
> When I launched the K3 Utility, it would not see the K3S - or more
> precisely, the port used by the K3S.
>
>  I replaced drivers in the computers, unplugged and replugged cables,
> added a new USB to computer cable  (thank you Elecraft) and still nothing
> worked:  Until it did.
>
> The last time I got it to work I also turned on the P3. I was about to
> order a RS-232 to USB cable, but the K3S and the K3 Utility started
> communicating.
>
> Once K3S started communicating, I reloaded all the K3S software and and
> have also added chokes/toroids to my computer cables. I do know there
> is/was a bit of RF floating around the shack.
> I’ve also checked and re-tightened any grounds wire.
>
> Has this happened to anyone else or does anyone have any other suggestions
> to keep this from happening again?
>
>
> Tnx es 73,
> Jeff/wb0m
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[email protected]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [email protected]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected] 

Reply via email to