P3 Ubdate

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

Re: P3 Ubdate

Wes (N7WS)
I'm not sure that my gripe is "on the list", although I've mentioned it several
times in other postings.

So maybe Elecraft can take this as a PIP (Performance Improvement Proposal/Program).

The memory management in the K3 is, to be kind, awful.

Things one believes are written to memory aren't. A really pet peeve is using
the M1-M4 to save per-mode settings on each band. For example CW, SSB, AFSK A
and DATA A.  If I set preferred BW for AFSK A of 400 HZ and store it in M4 and
set 2 KHz for DATA A and store it in M3, then immediately recall M4, the BW will
be what I just saved in M3. In other words, the BW isn't really saved despite
the manual saying, "The K3 has 100 general-purpose memories (00-99), plus
per-band memories (M1-M4 on each band). Each memory holds VFO A and B
frequencies, modes, filter presets, antenna selection, and other settings...."

The manual goes on to say, "Memories 00-09 are quick memories, accessible with
just two switch taps. These could be used to get to a starting point in each of
10 ham bands."  Not even close.  If I use the Memory Editor software to set
frequencies and modes in the memories, the best that can be said is that you
will get the band changed.  The frequencies will be whatever they were the last
time you were on that band.

So could we please have a firmware change that makes memories actually
remember---and recall---what was stored in them?  My 13 year, at the time I
acquired the K3, Kenwood TS-870 did this flawlessly.

Wes  N7WS

On 12/6/2014 4:33 PM, Ian White wrote:
>>
>> Sorry, but I am no longer feeling so generous about and further delays
>> to features that have been waiting "on the list" for 7 years now.

______________________________________________________________
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
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: P3 Ubdate

wayne burdick
Administrator
Wes,

At present we only save one bandwidth in data modes. Fixing that is a top priority.


> The manual goes on to say, "Memories 00-09 are quick memories, accessible with just two switch taps. These could be used to get to a starting point in each of 10 ham bands."  Not even close.  If I use the Memory Editor software to set frequencies and modes in the memories, the best that can be said is that you will get the band changed.  The frequencies will be whatever they were the last time you were on that band.

There are two settings for quick-memories 00-09:  fixed-frequency (NOR) or last-used-frequency (BAND-SEL). The CONFIG:MEM 0-9 menu entry is used to make this selection.

Wayne
N6KR


______________________________________________________________
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
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: P3 Ubdate

Don Wilhelm-4
In reply to this post by Wes (N7WS)
Wes,

I have my K3 set for Quick Memories, and use that for band switching.  I
run with the CONFIG:MEM0-9 set to BAND SEL.  If you set it to NOR, it
will not change to the last used frequency but will behave just like any
other 00 - 99 memory.

I use the Quick Memories for band switching (and seldom touch the
BAND^/V button.  Additionally, I have set the M1-M4 memories for each
band.  M1 takes me to the mid-CW segment of that band, M2 takes me to a
mid-frequency for the SSB segment, and M3 takes me to the correct
frequency for PSK Data mode operation on that band (I don't currently
use M4).

So I use the Quick Memories to take me to a particular band, then use
the M1-M4 memories to navigate to a particular fixed frequency band
segment and operating mode.

I have the Quick Memories set to BAND SEL so if I hear something I might
be interested in on the band I am tuned to at the moment, but want to
check another band - when I come back to the original band, I am set to
the last frequency used and can continue with that 'interesting' station.

YMMV, but you *can* set the quick memories to go to a specific
frequency, mode, etc.  You just have to change the MEM 0-9 menu
parameter to "NOR" - but then those memories behave just like any other
memory slot - they will not be "Quick Memories".

73,
Don W3FPR

On 12/10/2014 2:25 PM, Wes (N7WS) wrote:

> I'm not sure that my gripe is "on the list", although I've mentioned
> it several times in other postings.
>
> So maybe Elecraft can take this as a PIP (Performance Improvement
> Proposal/Program).
>
> The memory management in the K3 is, to be kind, awful.
>
> Things one believes are written to memory aren't. A really pet peeve
> is using the M1-M4 to save per-mode settings on each band. For example
> CW, SSB, AFSK A and DATA A.  If I set preferred BW for AFSK A of 400
> HZ and store it in M4 and set 2 KHz for DATA A and store it in M3,
> then immediately recall M4, the BW will be what I just saved in M3. In
> other words, the BW isn't really saved despite the manual saying, "The
> K3 has 100 general-purpose memories (00-99), plus per-band memories
> (M1-M4 on each band). Each memory holds VFO A and B frequencies,
> modes, filter presets, antenna selection, and other settings...."
>
> The manual goes on to say, "Memories 00-09 are quick memories,
> accessible with just two switch taps. These could be used to get to a
> starting point in each of 10 ham bands."  Not even close.  If I use
> the Memory Editor software to set frequencies and modes in the
> memories, the best that can be said is that you will get the band
> changed.  The frequencies will be whatever they were the last time you
> were on that band.
>
> So could we please have a firmware change that makes memories actually
> remember---and recall---what was stored in them?  My 13 year, at the
> time I acquired the K3, Kenwood TS-870 did this flawlessly.
>
> Wes  N7WS

______________________________________________________________
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
Message delivered to [hidden email]
HP
Reply | Threaded
Open this post in threaded view
|

Re: K3 bamdswutching

HP
Get a KPA500 - you get bandswitch buttons thrown in for free.
Then I have M1-M4  set up modes wise on each band

At my age I cannot remember which K3 number is which band.
Now I just peck the band buttons on the KPA.  

K7HP

I have my K3 set for Quick Memories, and use that for band switching.  I
run with the CONFIG:MEM0-9 set to BAND SEL.  If you set it to NOR, it
will not change to the last used frequency but will behave just like any
other 00 - 99 memory.

I use the Quick Memories for band switching (and seldom touch the
BAND^/V button.  Additionally, I have set the M1-M4 memories for each
band.  M1 takes me to the mid-CW segment of that band, M2 takes me to a
mid-frequency for the SSB segment, and M3 takes me to the correct
frequency for PSK Data mode operation on that band (I don't currently
use M4).

So I use the Quick Memories to take me to a particular band, then use
the M1-M4 memories to navigate to a particular fixed frequency band
segment and operating mode.

I have the Quick Memories set to BAND SEL so if I hear something I might
be interested in on the band I am tuned to at the moment, but want to
check another band - when I come back to the original band, I am set to
the last frequency used and can continue with that 'interesting' station.

YMMV, but you *can* set the quick memories to go to a specific
frequency, mode, etc.  You just have to change the MEM 0-9 menu
parameter to "NOR" - but then those memories behave just like any other
memory slot - they will not be "Quick Memories".

73,
Don W3FPR

On 12/10/2014 2:25 PM, Wes (N7WS) wrote:

> I'm not sure that my gripe is "on the list", although I've mentioned
> it several times in other postings.
>
> So maybe Elecraft can take this as a PIP (Performance Improvement
> Proposal/Program).
>
> The memory management in the K3 is, to be kind, awful.
>
> Things one believes are written to memory aren't. A really pet peeve
> is using the M1-M4 to save per-mode settings on each band. For example
> CW, SSB, AFSK A and DATA A.  If I set preferred BW for AFSK A of 400
> HZ and store it in M4 and set 2 KHz for DATA A and store it in M3,
> then immediately recall M4, the BW will be what I just saved in M3. In
> other words, the BW isn't really saved despite the manual saying, "The
> K3 has 100 general-purpose memories (00-99), plus per-band memories
> (M1-M4 on each band). Each memory holds VFO A and B frequencies,
> modes, filter presets, antenna selection, and other settings...."
>
> The manual goes on to say, "Memories 00-09 are quick memories,
> accessible with just two switch taps. These could be used to get to a
> starting point in each of 10 ham bands."  Not even close.  If I use
> the Memory Editor software to set frequencies and modes in the
> memories, the best that can be said is that you will get the band
> changed.  The frequencies will be whatever they were the last time you
> were on that band.
>
> So could we please have a firmware change that makes memories actually
> remember---and recall---what was stored in them?  My 13 year, at the
> time I acquired the K3, Kenwood TS-870 did this flawlessly.
>
> Wes  N7WS

______________________________________________________________
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
Message delivered to [hidden email]
______________________________________________________________
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
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: P3 Ubdate

Wes (N7WS)
In reply to this post by wayne burdick
Mea Culpa.  Although I have the latest (I think) pdf K3 manual, some of my
research used the printed (and now out-of-date) manual that came with my radio.  
I now understand the difference between "NOR" and "Band-Sel".

However, that doesn't negate all of my concerns.  The manual states for example,
that antenna selection is remembered.  Perhaps that applies to units with the
built-in tuner, but it sure doesn't remember the state of the RX antenna selection.

Other parameters that I believe should be memorized and recalled are ATT, PRE,
LOCK, FIL and probably others.  In other words I would like to be able to
recover to a previously recorded state.

Now, let's say I use my "Split" macro that locks VFO A, and sets VFO B up 1 KHz
and goes into Split mode, while there I fiddle with the Filter selection.  If in
M1, Split is off, VFO A = X, VFO B = Y, a FIL is selected and normalized and
Lock is off I would like to get this all back by a press of M>V and M1.  As it
stands, the VFOs will revert okay but will still be locked and the filter will
be what ever it was before.

Maybe this is the best that can be expected but I hope not.

Wes  N7WS


On 12/10/2014 12:51 PM, Wayne Burdick wrote:

> Wes,
>
> At present we only save one bandwidth in data modes. Fixing that is a top priority.
>
>
>> The manual goes on to say, "Memories 00-09 are quick memories, accessible with just two switch taps. These could be used to get to a starting point in each of 10 ham bands."  Not even close.  If I use the Memory Editor software to set frequencies and modes in the memories, the best that can be said is that you will get the band changed.  The frequencies will be whatever they were the last time you were on that band.
> There are two settings for quick-memories 00-09:  fixed-frequency (NOR) or last-used-frequency (BAND-SEL). The CONFIG:MEM 0-9 menu entry is used to make this selection.
>
> Wayne
> N6KR
>
>
>

______________________________________________________________
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
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: P3 Ubdate

Don Wilhelm-4
Wes,

Are you certain you had all the desired parameters set in the K3 when
you stored the M1-M4 per band memories?  I find that they do save the
mode, frequencies, filter settings and antenna selection that you have
requested.
I don't know about your Split Macro and the LOCK functions or the RX
antenna because I have not tried those in my setup.

73,
Don W3FPR

On 12/11/2014 12:44 PM, Wes (N7WS) wrote:

> Mea Culpa.  Although I have the latest (I think) pdf K3 manual, some
> of my research used the printed (and now out-of-date) manual that came
> with my radio.  I now understand the difference between "NOR" and
> "Band-Sel".
>
> However, that doesn't negate all of my concerns.  The manual states
> for example, that antenna selection is remembered.  Perhaps that
> applies to units with the built-in tuner, but it sure doesn't remember
> the state of the RX antenna selection.
>
> Other parameters that I believe should be memorized and recalled are
> ATT, PRE, LOCK, FIL and probably others.  In other words I would like
> to be able to recover to a previously recorded state.
>
> Now, let's say I use my "Split" macro that locks VFO A, and sets VFO B
> up 1 KHz and goes into Split mode, while there I fiddle with the
> Filter selection.  If in M1, Split is off, VFO A = X, VFO B = Y, a FIL
> is selected and normalized and Lock is off I would like to get this
> all back by a press of M>V and M1.  As it stands, the VFOs will revert
> okay but will still be locked and the filter will be what ever it was
> before.
>

______________________________________________________________
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
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: P3 Ubdate

Wes (N7WS)
I'm positive that I had everything set as desired.  I thought my original post
said as much.

The Lock function survives everything, even band changes, which I find curious.  
Perhaps there is a need for it other than how I use it, which is to lock the A
VFO when I use split.  Since I have no second receiver,  but do have an SDR-IQ
bandscope I often use the REV button and the main tuning knob to set my TX
frequency to the last calling station's frequency.  A slip on the REV button
while doing this will move the A VFO rather than the B, so locking A prevents
this. It would be helpful (and to me, logical) to have a memory recall or band
change unlock the VFO.

The RX Ant state is not memorized.  This is easy to see.  Turn on the RX antenna
and recall any M1-M4 memory.  It will stay on.

Wes  N7WS

On 12/11/2014 4:09 PM, Don Wilhelm wrote:
> Wes,
>
> Are you certain you had all the desired parameters set in the K3 when you
> stored the M1-M4 per band memories?  I find that they do save the mode,
> frequencies, filter settings and antenna selection that you have requested.
> I don't know about your Split Macro and the LOCK functions or the RX antenna
> because I have not tried those in my setup.
>

______________________________________________________________
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
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: P3 Ubdate

wayne burdick
Administrator

On Dec 13, 2014, at 12:11 PM, Wes (N7WS) <[hidden email]> wrote:

> I'm positive that I had everything set as desired.  I thought my original post said as much.
>
> The Lock function survives everything, even band changes, which I find curious.  Perhaps there is a need for it other than how I use it, which is to lock the A VFO when I use split.

Lock is global because it was intended to keep the VFO from moving while operating mobile. Your application suggests making it per-band/per-memory, which I will add to the list.

>
> The RX Ant state is not memorized.  This is easy to see.  Turn on the RX antenna and recall any M1-M4 memory.  It will stay on.

RX ANT is stored per-band, not per-memory. This seems like the right choice.

Wayne
N6KR


______________________________________________________________
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
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: P3 Ubdate

Wes (N7WS)
On 12/13/2014 2:28 PM, Wayne Burdick wrote:
> On Dec 13, 2014, at 12:11 PM, Wes (N7WS) <[hidden email]> wrote:
>
>> I'm positive that I had everything set as desired.  I thought my original post said as much.
>>
>> The Lock function survives everything, even band changes, which I find curious.  Perhaps there is a need for it other than how I use it, which is to lock the A VFO when I use split.
> Lock is global because it was intended to keep the VFO from moving while operating mobile. Your application suggests making it per-band/per-memory, which I will add to the list.

Understood.  Thanks. (Does anyone actually use these mobile?)
>> The RX Ant state is not memorized.  This is easy to see.  Turn on the RX antenna and recall any M1-M4 memory.  It will stay on.
> RX ANT is stored per-band, not per-memory. This seems like the right choice.

Okay.  But the manual verbiage says that antenna selection is memorized :-)
>
> Wayne
> N6KR
>

______________________________________________________________
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
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: P3 Ubdate

Don Wilhelm-4
Wes,

I guess we have to differentiate between the ANT1/2 jacks (which are
memorized) and the RX ANT function (which is only a per band setting,
and not memorized.

73,
Don W3FPR

On 12/13/2014 4:52 PM, Wes (N7WS) wrote:
>
> Okay.  But the manual verbiage says that antenna selection is
> memorized :-)

______________________________________________________________
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
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: P3 Ubdate

charlie carroll
In reply to this post by Wes (N7WS)
Yep, sure do.

73 charlie, k1xx

> Understood.  Thanks. (Does anyone actually use these mobile?)



______________________________________________________________
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
Message delivered to [hidden email]
12