I also addressed this with Scott a couple years ago and he had no interest
in modifying the software for the K3. 73 Greg AB7R On Tue, Feb 15, 2011 at 12:52 PM, Terry Schieler < [hidden email]> wrote: > I have used N3FJP's ACLog logging software for quite a few years. I'm not > a > big contester and his software has previously done everything I needed. It > always worked very well with my FT-1000MP (I helped Scott configure his > software rig control for that radio early on and he seemed very grateful at > the time). However, although his web site indicates compatibility with > the > K2 and K3, I have not found that to be entirely accurate. When I click on > a > DX spot in ACLog's DX window the K3 eventually moves to the spotted > frequency, BUT the mode doesn't follow the frequency. With the FT-1000MP, > it used to automatically match the mode to the area of the band that the > spot related to (very quickly too). It seems as perhaps the information is > being sent to the K3 in a sequence that the K3 doesn't like. Mode first, > then freq. OR, freq first then mode. I don't know. And, very slow to > move > to the spot frequency. I've tried changing the data reporting settings in > the ACLog software without success. All other aspects of the K3 rig control > work fine. > > I called Scott, the software author, and this time he was pretty > indifferent > to my K3 issue. If someone has discovered a work-around to get the N3FJP > rig control DX Spotting software in proper sync with the K3 please contact > me directly. I would appreciate the help. Thanks in advance. > > 73, > > Terry, W0FM > > My call @ swbell dot net > > ______________________________________________________________ > 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 > 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 |
I think the problem is the K3's habit of restoring the mode last used on a band when you change to that band. It seems to override the mode set in the software. In KComm I overcame it by waiting a bit before sending the mode command to give the unwanted mode change time to take effect. But since I'm only supporting Elecraft radios I can work around the quirks. I can understand a developer's unwillingness to make major logic changes to accommodate one radio which might end up causing issues with several others. I actually would like the K3 to do ONLY what the software command tells it to do. It may be helpful to restore the last used mode when changing bands via the front panel but it is illiogical to change modes when you send a computer command that just says change frequency. If the K3 would do what the computer tells it and only what the computer tells it then it would fix an annoying problem with several programs besides N3FJP.
Julian, G4ILO. K2 #392 K3 #222 KX3 #110
* G4ILO's Shack - http://www.g4ilo.com * KComm - http://www.g4ilo.com/kcomm.html * KTune - http://www.g4ilo.com/ktune.html |
The big issue here is that most software that uses 'kenwood protocol'
sends the mode change BEFORE the new frequency I modified the radio control file for dxbase to send frequency and mode together as opposed toe setting the mode THEN chaining the frequency My modified command sets mode and frequency in one command string with no pause and it works just fine On Tue, 2011-02-15 at 14:30 -0800, Julian, G4ILO wrote: > > Greg - AB7R wrote: > > > > I also addressed this with Scott a couple years ago and he had no interest > > in modifying the software for the K3. > > > > > > I think the problem is the K3's habit of restoring the mode last used on a > band when you change to that band. It seems to override the mode set in the > software. In KComm I overcame it by waiting a bit before sending the mode > command to give the unwanted mode change time to take effect. But since I'm > only supporting Elecraft radios I can work around the quirks. I can > understand a developer's unwillingness to make major logic changes to > accommodate one radio which might end up causing issues with several others. > > I actually would like the K3 to do ONLY what the software command tells it > to do. It may be helpful to restore the last used mode when changing bands > via the front panel but it is illiogical to change modes when you send a > computer command that just says change frequency. If the K3 would do what > the computer tells it and only what the computer tells it then it would fix > an annoying problem with several programs besides N3FJP. > > ----- > Julian, G4ILO. K2 #392 K3 #222. > * G4ILO's Shack - http://www.g4ilo.com > * KComm - http://www.g4ilo.com/kcomm.html > * KTune - http://www.g4ilo.com/ktune.html > -- 73 Brendan EI6IZ ______________________________________________________________ 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 |
In reply to this post by Julian, G4ILO
Julian,
I do not understand the reluctance of the developers to reverse the order of sending frequency and mode changes. The "set mode first" will work with those radios that do not recall the last used mode on a new band. but the sequence of setting the frequency first and then setting the mode should work for all radios - including the K2 and K3, and should still work fine with the Kenwoods. The K3 IS doing just what the software tells it to do. The problem is that the K3 retains the last used mode on a per band basis, and I understand that many other radios do not provide that operating convenience. Maybe there is something I am missing. 73, Don W3FPR On 2/15/2011 5:30 PM, Julian, G4ILO wrote: > > I think the problem is the K3's habit of restoring the mode last used on a > band when you change to that band. It seems to override the mode set in the > software. In KComm I overcame it by waiting a bit before sending the mode > command to give the unwanted mode change time to take effect. But since I'm > only supporting Elecraft radios I can work around the quirks. I can > understand a developer's unwillingness to make major logic changes to > accommodate one radio which might end up causing issues with several others. > > I actually would like the K3 to do ONLY what the software command tells it > to do. It may be helpful to restore the last used mode when changing bands > via the front panel but it is illiogical to change modes when you send a > computer command that just says change frequency. If the K3 would do what > the computer tells it and only what the computer tells it then it would fix > an annoying problem with several programs besides N3FJP. > > ----- > Julian, G4ILO. K2 #392 K3 #222. > * G4ILO's Shack - http://www.g4ilo.com > * KComm - http://www.g4ilo.com/kcomm.html > * KTune - http://www.g4ilo.com/ktune.html > 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 |
In reply to this post by Julian, G4ILO
Julian,
Actually, the sequence of setting the mode first will change the mode on the current band - then after the command to change to another band is issued, the K3 will dutifully follow that command - and will retrieve the last used mode on that band - because that is what the K3 programmer's reference says it will do - simply change bands. Reversing the order to change band, and then change mode should hurt nothing, and will solve the problem for many K3 users. 73, Don W3FPR On 2/15/2011 5:30 PM, Julian, G4ILO wrote: > > Greg - AB7R wrote: >> I also addressed this with Scott a couple years ago and he had no interest >> in modifying the software for the K3. >> >> > I think the problem is the K3's habit of restoring the mode last used on a > band when you change to that band. It seems to override the mode set in the > software. In KComm I overcame it by waiting a bit before sending the mode > command to give the unwanted mode change time to take effect. But since I'm > only supporting Elecraft radios I can work around the quirks. I can > understand a developer's unwillingness to make major logic changes to > accommodate one radio which might end up causing issues with several others. > > I actually would like the K3 to do ONLY what the software command tells it > to do. It may be helpful to restore the last used mode when changing bands > via the front panel but it is illiogical to change modes when you send a > computer command that just says change frequency. If the K3 would do what > the computer tells it and only what the computer tells it then it would fix > an annoying problem with several programs besides N3FJP. > > ----- > Julian, G4ILO. K2 #392 K3 #222. > * G4ILO's Shack - http://www.g4ilo.com > * KComm - http://www.g4ilo.com/kcomm.html > * KTune - http://www.g4ilo.com/ktune.html > 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 |
Don,
Thanks! Now I understand what is happening. The mode change being sent first is what is causing the delay in moving to the spot frequency. I recall hearing the audio quality change on the initial frequency (like you'd expect changing to CW from LSB), then an annoying delay, then the frequency changes to the DX spot frequency. We can't fix that in the radio and the software author isn't interested in helping. But at least I now understand WHY I'm stuck with this in this logging program. 73, Terry, W0FM -----Original Message----- From: Don Wilhelm [mailto:[hidden email]] Sent: Tuesday, February 15, 2011 5:19 PM To: Julian, G4ILO Cc: [hidden email] Subject: Re: [Elecraft] [K3] N3FJP and K3 control issue Julian, Actually, the sequence of setting the mode first will change the mode on the current band - then after the command to change to another band is issued, the K3 will dutifully follow that command - and will retrieve the last used mode on that band - because that is what the K3 programmer's reference says it will do - simply change bands. Reversing the order to change band, and then change mode should hurt nothing, and will solve the problem for many K3 users. 73, Don W3FPR ______________________________________________________________ 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 |
Free forum by Nabble | Edit this page |