[Elecraft] 60 meters

[Fred Jensen]

This began as a simple question, I can't understand why it is so hard to 
explain:  K3 frequency memories hold frequency, mode, and DSP BW for 
both VFO A and VFO B.  I used the K3 Frequency Editor to load the CW 
parameters into VFO A and USB parameters into VFO B in 5 consecutive 
memory channels.  Those 5 are "ganged together" with an "*" in the name, 
IIRC.

When I rotate the Big Knob, I expected the VFO's to rotate through the 
channels [end-around].  VFO A does, but VFO B does not follow, it 
remains on whatever channel I originally selected.

The sequence M>V, Select memory, M>V sets both VFO's to the parameters 
stored in that memory, as one would expect.  Selecting a new memory with 
the BK should load the parameters for that memory into both VFO's, or so 
it would seem.  It does for VFO A. It doesn't for VFO B.  My question 
was, "Is this a bug or intentional behavior?"  If it's intentional, I'd 
be curious what the use case is for that behavior.  I'm also aware this 
is a K3 question and likely to get lost in all the K4 commotion.

73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

On 6/3/2019 4:13 PM, K8TE wrote:
> While you can scan or dial through VFO A, once you "land" on a particular
> channel, the VFO B frequency and mode associated with that channel is
> available by using the VFO A/B button.
>
> I originally loaded the 60m CW frequencies in VFO A for my 60m channels
> since I'm more likely to use them working SOTA activators.  However, I
> usually scan the SSB channels.  Thus, I swapped between VFO A and B so I can
> scan USB channels and select the appropriate VFO B CW channels when needed.
> This comes in handy when someone suggests 60m for USB or when I see a SOTA
> dude spotted on 60m CW.
>
> 73, Bill, K8TE, waiting "patiently" to return home and start using HF again!
> BCNU at Ham-Com.
>