[Elecraft] K3-Problem with DX spot point-&-click

[David Ferrington, M0XDF]

Yes, but on a Mac with MacLoggerDX
The bottom line is, the author (Don Agro of Dogpark Software) changed  
the program to send a mode change after the frequency change.
i have found the K3 quite responsive to frequency change, but since it  
remembers the last mode per band (therefore effectively frequency),  
you must change the mode after frequency change.
He also found that there could be race condition on occasions and put  
a slight delay (100ms) into the change.
73 de M0XDF, K3 #174
-- 
There are three truths: my truth, your truth, and the truth.
-Chinese proverb

On 28 Oct 2008, at 21:52, 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.qth.net/pipermail/elecraft/attachments/20081028/5d1d7226/attachment.htm