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

[Greg - AB7R]

I'm not an expert on this but I think much of it is a timing issue.  I've been 
working with Howard Nurse (CommCat) for a K3 interface and its working pretty well.  
It even turns on the Sub RX (if installed) when clicking a split spot.  When we were 
first starting the changes to freq/band were pretty slow...now they are much 
quicker.  
So I would say any problem like this would be on the 3rd-party software design.

A good test would be to use the K3 Utility and create some macros that do a variety 
of things (using the K3 prgrammers reference) and see how quickly the K3 responds.  
3rd party software should be able to make it respond just as quickly.

-------------------------
73,
Greg - AB7R
Whidbey Island WA
NA-065


On Tue Oct 28 14:52 , "Terry Schieler"  sent:

>
>
>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.
>
>Â 
>
>73,
>
>Â 
>
>Terry, W0FM
>
>Â 
>
>Â 
>
>Â 
>
>Â 
>
>
>
>
>
>