K3-Problem with DX spot point-&-click

[Terry Schieler]

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

 

 

 

 

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

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

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Julian, G4ILO]

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.

[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
>
> 
>
> 
>
> 
>
> 
>
>
>
>
>
>

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[KH7T]

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

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[dave.wilburn]

Except for contests (where I use N1MM) I use ACLOG for all of my
general logging.  I have not had issues with ACLOG.  It is very handy
for uploading to LOTW.  It would be nice if the interface was a bit
more configurable.

David Wilburn
NM4M
http://www.nm4m.com



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.
>
>  
>
> 73,
>
>  
>
> Terry, W0FM
>
>  
>
>  
>
>  
>
>  
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Elecraft mailing list
> Post to: [hidden email]
> 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

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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