[Elecraft] k3 : no CAT mode change (was Split Operation)

[Julian, G4ILO]

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.

-----
Julian, G4ILO. K2 #392  K3 #222.
http://www.g4ilo.com/ G4ILO's Shack   http://www.ham-directory.com/ Ham
Directory    http://www.g4ilo.com/kcomm.html KComm for Elecraft K2 and K3 
-- 
View this message in context: http://n2.nabble.com/k3-%3A--Split-Operation-tp1298735p1304198.html
Sent from the Elecraft mailing list archive at Nabble.com.