[Elecraft] [K3] WSJT-X settings for K3

Joel Black joel.b.black at gmail.com
Fri Jan 9 17:34:40 EST 2015


For me, it happens *more* when WSJT-X is not the focus. I run OS X 10.10.1.

The problem doesn’t disappear when WSJT-X has focus, but it’s not quite as aggravating. I usually just hit whichever button doesn’t shut the program down (I forget which that is now).

73,
Joel - W4JBB

> On Jan 9, 2015, at 7:03 AM, Mike Reublin NF4L <nf4l at comcast.net> wrote:
> 
> Yep. There is a known "K2/K3 problem". They're working on a solution. The program uses HamLib to interface with the radio and it apparently is the problem. I can't imagine what the problem is, and they won't tell me. The K3 (and I suspect all the Elecraft line) has a very straightforward protocol.
> 
> Send an email to  John Nelson G4KLA at g4kla at rmnjmn.demon.co.uk.
> 
> 73, Mike NF4L
> 
>> On Jan 8, 2015, at 10:13 PM, inventor61 . <inventor61 at gmail.com> wrote:
>> 
>> I have tried the last two versions of WSJT-X and there seems to be some
>> problem with the rig control for the K3.  I get error messages, something
>> about the program not being able to read the mode of the radio's second
>> VFO.
>> 
>> As is often the case, a pretty cryptic error message is what's offered,
>> mostly intended for the programmer, not an end user.  I think the program
>> uses hamlib for radio control options.
>> 
>> Many attempts at different settings were tried, and the one that works best
>> is to set it for no programmatic rig control, at all (other than RTS for
>> PTT).
>> 
>> I have no problem with my K3-P3-KPA500 station, or with other control
>> programs, just WSJT-X.  I use only 'real' UART based COM ports, so, that's
>> not the problem.
>> 
>> Anybody experience similar?


More information about the Elecraft mailing list