K3 Memory locations overwriting quick memories

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

K3 Memory locations overwriting quick memories

Nate Bargmann
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.

73, de Nate >>

--

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 Memory locations overwriting quick memories

Don Wilhelm-4
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.
>
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 Memory locations overwriting quick memories

Pierfrancesco Caci
In reply to this post by Nate Bargmann
>>>>> "Nate" == Nate Bargmann <[hidden email]> writes:

    Nate> If I had a choice, I would prefer that selecting a memory which has its
    Nate> programmed frequency outside the amateur band limits would not overwrite
    Nate> the quick band memories.  In other words, in my case, selecting memory
    Nate> 90 would not set VFO A and VFO B to 2.5 MHz, as that is clearly beyond
    Nate> the 160m band edge.  30m and 10 MHz is somewhat less obvious, but I
    Nate> think 10.1 MHz is the lower limit for 30m worldwide.  15 MHz is also
    Nate> well beyond the upper edge of 20m and should not rewrite that quick band
    Nate> memory.

    Nate> Perhaps this is a difficult firmware change, and I'll just have to live
    Nate> with it.  If not, I hope you can look into this, Wayne.


Nate, if all you need is to be able to return to the ham band, not to
your previous frequency in there, you can use the M1-M4 keys. That is,
change band as you do now with M->V [0..9] and then do M->V [M1..M4].
M1-M4 are remembered per band, so I put a CW freq (usually the lower
band edge) in M1, the beginning of SSB band in M2, PSK31 in M3 and RTTY
in M4. They also change mode for me in the proper way.

Pf



--
Pierfrancesco Caci, ik5pvx
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 Memory locations overwriting quick memories

Nate Bargmann
In reply to this post by Don Wilhelm-4
Good idea.  Thanks, Don.

73, de Nate >>

--

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 Memory locations overwriting quick memories

Nate Bargmann
In reply to this post by Pierfrancesco Caci
An interesting idea, Pierfrancesco, and one I had not considered before.
Thanks!

73, de Nate >>

--

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 Memory locations overwriting quick memories

Joe Subich, W4TV-4
In reply to this post by Nate Bargmann

Nate,

The answer is in the Owner's Manual.  Search for CONFIG:MEN 0-9

> If the parameter is set to BAND SEL, frequency memories 0-9 (“quick
> memories”) will act like band switches. Once this mode has been
> selected, exit the menu, then use V > M to assign individual bands to
> keypad switches 0-9. For example, use BAND to get to 160 m, tap V M,
> then tap #1 . From then on, tapping M > V , then #1 , will take you
> to your last-used frequency on 160 m, just as if you had used the
> BAND switch.

The WWV frequencies are "within" the broader bands defined by the K3 -
for example 15 MHz is in the 20 meter "band".  If you do not like the
current behavior, you can set CONFIG:MEM 0-9 to "nor" and store one
frequency/mode for each band and they will not be updated with out
of band frequencies.

73,

    ... Joe, W4TV


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.
>
> 73, de Nate >>
>
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 Memory locations overwriting quick memories

Nate Bargmann
* On 2013 22 Nov 07:20 -0600, Joe Subich, W4TV wrote:
>
> The WWV frequencies are "within" the broader bands defined by the K3 -
> for example 15 MHz is in the 20 meter "band".

That is really my request, that the "bands" be narrowed to just the
common limits of the amateur allocations.

73, de Nate >>

--

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 Memory locations overwriting quick memories

Nate Bargmann
* On 2013 22 Nov 09:02 -0600, Nate Bargmann wrote:
> * On 2013 22 Nov 07:20 -0600, Joe Subich, W4TV wrote:
> >
> > The WWV frequencies are "within" the broader bands defined by the K3 -
> > for example 15 MHz is in the 20 meter "band".
>
> That is really my request, that the "bands" be narrowed to just the
> common limits of the amateur allocations.

Or, make the K3 band limits configurable.

"It's only software!"  ;-)

73, de Nate >>

--

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 Memory locations overwriting quick memories

Joe Subich, W4TV-4

Or provide a "do not save out of band frequencies" option <G>.

73,

    ... Joe, W4TV


On 11/22/2013 10:06 AM, Nate Bargmann wrote:

> * On 2013 22 Nov 09:02 -0600, Nate Bargmann wrote:
>> * On 2013 22 Nov 07:20 -0600, Joe Subich, W4TV wrote:
>>>
>>> The WWV frequencies are "within" the broader bands defined by the K3 -
>>> for example 15 MHz is in the 20 meter "band".
>>
>> That is really my request, that the "bands" be narrowed to just the
>> common limits of the amateur allocations.
>
> Or, make the K3 band limits configurable.
>
> "It's only software!"  ;-)
>
> 73, de Nate >>
>
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 Memory locations overwriting quick memories

N5GE
Nate,

I am a member of Navy Marine Corps MARS and have many of the MARS
allocations saved in my K3 memories.  All of them are outside the Ham
Bands.

My solution to not preventing transmission mistakes like transmitting
on the WWV frequencies, or transmitting SSB in the CW Bands, or out
side the bands allowed by my License, is to look at my VFO (both A
and B) before transmitting, as hams have done since the beginning of
Ham radio.  The procedure works very well for me, so, no thanks, I
don't want my K3 dumbed down.

Amateure Radio Operator N5GE



On Fri, 22 Nov 2013 10:37:23 -0500, you wrote:

>
>Or provide a "do not save out of band frequencies" option <G>.
>
>73,
>
>    ... Joe, W4TV
>
>
>On 11/22/2013 10:06 AM, Nate Bargmann wrote:
>> * On 2013 22 Nov 09:02 -0600, Nate Bargmann wrote:
>>> * On 2013 22 Nov 07:20 -0600, Joe Subich, W4TV wrote:
>>>>
>>>> The WWV frequencies are "within" the broader bands defined by the K3 -
>>>> for example 15 MHz is in the 20 meter "band".
>>>
>>> That is really my request, that the "bands" be narrowed to just the
>>> common limits of the amateur allocations.
>>
>> Or, make the K3 band limits configurable.
>>
>> "It's only software!"  ;-)
>>
>> 73, de Nate >>
>>
>______________________________________________________________
>Elecraft mailing list
>Home: http://mailman.qth.net/mailman/listinfo/elecraft
>Help: http://mailman.qth.net/mmfaq.htm
>Post: mailto:[hidden email]
>
>This list hosted by: http://www.qsl.net
>Please help support this email list: http://www.qsl.net/donate.html

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Amateur Radio Operator N5GE
Reply | Threaded
Open this post in threaded view
|

Re: K3 Memory locations overwriting quick memories

W4GRJ
I agree with Tom..... I am AF MARS, we operate on lot's of Federal frequencies, all outside the Ham bands. Just need to pay attention to your operating which we all should be doing.
Jack
W4GRJ / AFA4DG

On Nov 22, 2013, at 21:55, Tom <[hidden email]> wrote:

Nate,

I am a member of Navy Marine Corps MARS and have many of the MARS
allocations saved in my K3 memories.  All of them are outside the Ham
Bands.

My solution to not preventing transmission mistakes like transmitting
on the WWV frequencies, or transmitting SSB in the CW Bands, or out
side the bands allowed by my License, is to look at my VFO (both A
and B) before transmitting, as hams have done since the beginning of
Ham radio.  The procedure works very well for me, so, no thanks, I
don't want my K3 dumbed down.

Amateure Radio Operator N5GE



> On Fri, 22 Nov 2013 10:37:23 -0500, you wrote:
>
>
> Or provide a "do not save out of band frequencies" option <G>.
>
> 73,
>
>   ... Joe, W4TV
>
>
>> On 11/22/2013 10:06 AM, Nate Bargmann wrote:
>> * On 2013 22 Nov 09:02 -0600, Nate Bargmann wrote:
>>> * On 2013 22 Nov 07:20 -0600, Joe Subich, W4TV wrote:
>>>>
>>>> The WWV frequencies are "within" the broader bands defined by the K3 -
>>>> for example 15 MHz is in the 20 meter "band".
>>>
>>> That is really my request, that the "bands" be narrowed to just the
>>> common limits of the amateur allocations.
>>
>> Or, make the K3 band limits configurable.
>>
>> "It's only software!"  ;-)
>>
>> 73, de Nate >>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html