|
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? ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
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 [hidden email]. 73, Mike NF4L > On Jan 8, 2015, at 10:13 PM, inventor61 . <[hidden email]> 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? > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
In reply to this post by inventor61 .
I don't have a problem, but I let dxlabs commander talk to the radio and
configure WSJT-X to use dxlabs. Gordon - N1MGO On 01/08/2015 10:13 PM, inventor61 . 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? > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
In reply to this post by inventor61 .
Mr. Inventor61 (call??) - I’ve been running my K3 (full K-Line here, too) with WSJT-X v1.3, r3673 for quite some time with no problems. WSJT-X is able to control the rig’s band setting and I also use the split feature with no issues. I’d be glad to compare settings with you if you’d like. It ought to work fine for you. Drop me an email offline and we can try to get it sorted out.
73, Jim / W6JHB at ARRL dot NET > On Thursday, Jan 8, 2015, at Thursday, 7:13 PM, inventor61 . <[hidden email]> 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? > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
James
Thanks for your reply. For some reason my name-and-call signature line got chopped off my initial reflector posting. I have the new WSJT-X v1.4 installed now. The problem is also experienced by others, according to the many private responses I got, there appears to be a bug in the hamlib file for the K3, and the authors are apparently aware of it. Tnx 73 Steve KZ1X *** On Jan 9, 2015 12:27 PM, "James Bennett" <[hidden email]> wrote: > Mr. Inventor61 (call??) - I’ve been running my K3 (full K-Line here, too) > with WSJT-X v1.3, r3673 for quite some time with no problems. WSJT-X is > able to control the rig’s band setting and I also use the split feature > with no issues. I’d be glad to compare settings with you if you’d like. It > ought to work fine for you. Drop me an email offline and we can try to get > it sorted out. > > 73, Jim / W6JHB at ARRL dot NET > > > > On Thursday, Jan 8, 2015, at Thursday, 7:13 PM, inventor61 . < > [hidden email]> 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? > > ______________________________________________________________ > > Elecraft mailing list > > Home: http://mailman.qth.net/mailman/listinfo/elecraft > > Help: http://mailman.qth.net/mmfaq.htm > > Post: mailto:[hidden email] > > > > This list hosted by: http://www.qsl.net > > Please help support this email list: http://www.qsl.net/donate.html > > Message delivered to [hidden email] > > Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
In reply to this post by Mike Reublin NF4L
On Fri,1/9/2015 5:03 AM, Mike Reublin NF4L wrote:
> There is a known "K2/K3 problem". The problem is ONLY with rig control -- if you run it manually, with no rig control, it works fine. That is, set the rig suppressed carrier frequency for the band you want, use JT65 below about 2 kHz audio, JT9 above it. I use VOX for PTT. 73, Jim K9YC ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
In reply to this post by inventor61 .
On Fri,1/9/2015 9:35 AM, inventor61 . wrote:
> The problem is also experienced by others, according to the many private > responses I got, there appears to be a bug in the hamlib file for the K3, > and the authors are apparently aware of it. Right. I lurk on the WSJT developers' list, and reported my issue with the new version. 73, Jim K9YC ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
In reply to this post by Mike Reublin NF4L
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 <[hidden email]> 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 [hidden email]. > > 73, Mike NF4L > >> On Jan 8, 2015, at 10:13 PM, inventor61 . <[hidden email]> 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? Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
In reply to this post by Mike Reublin NF4L
* On 2015 09 Jan 07:04 -0600, Mike Reublin NF4L 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. I don't know what the problem is and I wrote most of the K2/K3 back end code a few years ago. Since then Bill, G4WJS, has contributed quite a number of fixes back to Hamlib. He would be a good contact for help as I'm not familiar with WSJT-X development nor have I used the program. 73, Nate, N0NB -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and more: http://www.n0nb.us ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
| Free forum by Nabble | Edit this page |
