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

[John Buck]

I noticed a similar problem with V2.57 and N3FJP used via LPBridge.
While checking settings, I reset the CW WGHT tap 1 parameter. It looked 
correct before I reentered the parameter. I did not see the wrong band 
again. Playing with the Baud rate and settings had not had any effect.
A clue?
Aloha,
John KH7T K3#125

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.
>
> snip