From spot to Elecraft K3. Order of CAT-commands.

[ON6NG]

Hello

The Elecraft K3 remembers the last used mode on a per band basis.
Knowing this, when clicking a spot, the order of CAT-commands is important.
First frequency/band, then mode.
I have the impression that the present order of CAT-commands causes a bug.

73 Marc

[HB9BRJ]

Hello

Marc is right, but the problem is more complex: When switching mode, the VFO display jumps by the amount defined as CW pitch. So the CAT sequence to be transmitted must be frequency - mode - frequency.

A few experiments done today showed mixed results. Sometimes everything works as expected, despite the last used mode on the target band was different from the mode in the cluster spot. Sometimes however the mode switches to the cluster spot mode on the current band and not on the target band. My workaround is simple: Double-click the same spot again!

There must be many K3 owners out there double-clicking cluster spots in Log4OM. Please report your observations.

73, Markus HB9BRJ

Update 2016-03-16:
As discussed in the Elecraft reflector, the K3 config setting CW WGHT > VFO OFS compensates for the CW pitch offset when switching between modes. This solves the problem with same band cluster spots. The mode switching problem remains when double-clicking cluster spots involving a band change.

[KI5IO]

Marc & Markus,

Out of curiosity what baud rate are you using with OmniRig to talk to your K3?

I've typically used 38400 and just today (as part of my trouble-shooting) lowered it to 19200. I've not seen any difference one way or another in that baud rate change.

I've also changed RTS and DTR from High to Low, but also have not noted any differences.

I've set my Polling and Timeout each at: 100

I think that y'alls' observations in the above posts are "spot on" with respect to the K3 and it's band memory.

I did a complete removal and complete "new" installation and things are much more stable. Seeing the nuances that y'all have noted as of now, but that is about it.

I only just completed the installation and still have more testing to do, but as of now it is looking pretty good.

[HB9BRJ]

Marc & Markus,
Out of curiosity what baud rate are you using with OmniRig to talk to your K3?

Baud rate = 38400, RTS = DTR = High, Poll interval = 100, Timeout = 4000.

73, Markus HB9BRJ

[ac2ev]

I am experiencing the same issue with my K3. Here's what I'm seeing

Current Mode USB 20m
<Double click on spot on 40M>
Radio changes from USB to LSB
Radio changes to frequency on 40m band
Radio changes from LSB to USB
<Double Click on same spot again>
Radio changes to LSB

The same thing happens if I'm on 40m and double click on a spot on 20m
If I'm 20m and double click on a spot on 15m the mode stays the same

Next I tried the following:

Current Mode USB 20m
Set mode LSB manually on radio
<Double click on spot on 40M>
Radio changes from LSB to USB
Radio changes to frequency on 40m band
<Double Click on same spot again>
Radio changes to LSB

73, Markus HB9BRJ

Update 2016-03-16:
As discussed in the Elecraft reflector, the K3 config setting CW WGHT > VFO OFS compensates for the CW pitch offset when switching between modes. This solves the problem with same band cluster spots. The mode switching problem remains when double-clicking cluster spots involving a band change.

I'm don't understand the meaning of this CW WGHT > VFO OFS

on my radio CW WGHT is a numerical value and VFO OFS is a On/Off

[HB9BRJ]

Behind the CW WGHT item in the K3 config menu there is a flag correcting the offset when switching between modes. Tap the "5" key to toggle between VFO NOR (default, no offset correction) and VFO OFS (with offset correction). Hope this helps.

Here is the link to the recent thread in the Elecraft forum:
http://elecraft.365791.n2.nabble.com/Sw ... 15202.html

73, Markus HB9BRJ