[Elecraft] K3 Memory locations overwriting quick memories

[Don Wilhelm]

Nate,

May I suggest that you use a 'workaround' until that problem can be 
resolved.  Copy the quick memories into 10 other memory locations - say 
memories 10 thru 19.  Then if something (including punching the wrong 
buttons), you can restore the quick memory locations easily.

I have my quick memories set up in a similar manner, but have not 
noticed them being overwritten, but I have the copy to fall back on 
should anything wipe them out.

73,
Don W3FPR

On 11/22/2013 7:14 AM, Nate Bargmann wrote:
> For easy band access, I am using the quick band memories laid out such
> that 1 is 160m to 0 is 6m excluding 60m.  This gives an easy two tap
> band change.  These occupy memory locations 00 to 09.
>
> For convenience I have entered the WWV frequencies into memory locations
> 90 to 94 (the 60m frequenciesoccupy 95 to 99).  I found that when I
> choose certain WWV memories that certain quick band memories are changed
> to the WWV frequency so that the former in-band frequencies are lost.
>
> For example.  Choosing memory 90 (2.5 MHz) results in both VFO A and VFO
> B frequencies being written to 2.5 MHz when I tap M>V then 1 (memory
> location 01).  I found the same for 30m (WWV 10 MHz, quick band memory
> 4) and 20m (WWV 15 MHz quick band memory 5).
>
> If I had a choice, I would prefer that selecting a memory which has its
> programmed frequency outside the amateur band limits would not overwrite
> the quick band memories.  In other words, in my case, selecting memory
> 90 would not set VFO A and VFO B to 2.5 MHz, as that is clearly beyond
> the 160m band edge.  30m and 10 MHz is somewhat less obvious, but I
> think 10.1 MHz is the lower limit for 30m worldwide.  15 MHz is also
> well beyond the upper edge of 20m and should not rewrite that quick band
> memory.
>
> Perhaps this is a difficult firmware change, and I'll just have to live
> with it.  If not, I hope you can look into this, Wayne.
>
>