Terry Schieler wrote:
>
> Fellow Elecraftonians,
>
>
>
> For years I have used N3FJP's ACLog logging software in conjunction with
> my
> FT1000MP and TS-850SAT. Like most others, the program has a DX Tel-net
> spot
> "point-&-click" feature that changes the frequency, band and mode on my
> rigs
> with lightning quickness. This weekend in the contest I used ACLog with
> my
> K3 for the first time.
>
>
>
> K3/100 #474
>
> Firmware: v2.46
>
> DSP: v1.92
>
>
>
> I found that the K3 was very slow to respond to clicking on the DX spots
> in
> the logging software. Both the logging program and the K3 were set to
> 38,400 baud, 8 data bits, NO parity and 1 stop bit. When I would click on
> a
> spot that was in the same band that the K3 was currently set to, the
> frequency change was made fairly quickly. But when I clicked on a spot
> that
> called for a band change, I noticed that the mode would often change first
> (on the K3's existing frequency) then a 1-2 second delay before the rig
> changed to the newly spotted band. To top it off, the resulting mode was
> often incorrect on the K3 after making the change to the new spot. I
> could
> find no specific pattern to the mode changes.
>
>
>
> I checked and rechecked the logging software settings to no avail. It was
> obvious to me from the get go that the K3 doesn't change bands all that
> quickly when pressing the BAND button on the front panel, so I suspect
> that
> the logging software is "pressing the button" but the K3 just takes longer
> to respond to a band change than my old 'MP or TS-850.
>
>
>
> Has anyone else experienced this? If so, is there a known fix? I have
> also
> sent this info to the logging software's developer as well as it may be an
> issue on that end.
>
>
Hi Terry.
Yes, it is a known issue. I think there is a conflict between the K3's
behavior of restoring the mode last used on a band, and your desire to have
the software select the mode appropriate for the part of the band you are
going to, regardless of what you last used on that band.
I encountered the problem when writing my program KComm. I solved the
problem by sending the command to change band, pausing for about half a
second, and then sending a mode change.
Because I am not interested in supporting any radios other than the Elecraft
K2 and K3, it was not a problem to make my software work the way the
Elecraft radios like to work. You must appreciate that for developers who
have to support every radio under the sun, each with its own peculiar way of
doing things, it is not so easy.
-----
Julian, G4ILO. K2 #392 K3 #222.
http://www.g4ilo.com/ G4ILO's Shack http://www.ham-directory.com/ Ham
Directory http://www.g4ilo.com/kcomm.html KComm for Elecraft K2 and K3
--
View this message in context:
http://n2.nabble.com/K3-Problem-with-DX-spot-point---click-tp1390814p1390969.html
Sent from the Elecraft mailing list archive at Nabble.com.
_______________________________________________
Elecraft mailing list
Post to: Elecraft@mailman.qth.net
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
