Thanks Julian, what the length of the delay?
I assume that’s how you fixed it?
73 de M0XDF, K3 #174
--
Write the bad things that are done to you in the sand, but write the
good things that happen to you on a piece of marble. -Arabian wisdom
On 7 Oct 2008, at 18:16, Julian, G4ILO wrote:
David Ferrington, M0XDF wrote:
nothing to do with split
I see this problem with MacLoggerDX - if the mode of the band to
which
I'm tuning the K3 is different, invariably, I need to make it tune
twice, so the mode gets set. However, if the mode of the band is
correct, everything is ok.
Don, the author of MacLoggerDX tells me he sends a mode change, a
frequency change and then a mode change again, but the K3 doesn't
appear to see it. using 2.45 (but others did so too)
Any ideas, those that write interface software?
73 de M0XDF, K3 #174
I remember having this trouble early on in the development of KComm.
I seem
to remember what I did was send the frequency change, wait a bit and
then
send the mode change. The K3 seems to perform some commands
asynchronously,
i.e. it goes on to the next command before the prevoius one has been
fully
executed. The problem you are seeing is probably that the mode
change is
being sent before the K3 has recalled the last mode used on that
band, so it
is being overridden.
_______________________________________________
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
