[Elecraft] K3 Band changing...Devils Advocate...

Dave Van Wallaghen w8fgu at comcast.net
Fri May 30 08:35:29 EDT 2008


Amen to that Don. As a non-contesting ham at this point, I've been following
this conversation trying to understand the use of "stacking band memories".
As I come from a programming background, I too thought the same way about
the "stack" model (FIFO) and have been racking my brain trying to figure out
how this would be beneficial. 

I simply attributed it to my "newness" and lack of understanding. But now I
feel a little better knowing someone else has the same perspective.

Would someone who needs this capability, take a moment to explain its use to
a neophyte? Right now, it seems intuitive to use as is, but then again, it
is all I know and I'm sure that in the heat of the battle there may be a
better way.

73,
Dave W8FGU

> -----Original Message-----
> From: elecraft-bounces at mailman.qth.net [mailto:elecraft-
> bounces at mailman.qth.net] On Behalf Of Don Wilhelm
> Sent: Friday, May 30, 2008 8:12 AM
> To: Don Rasmussen
> Cc: elecraft at mailman.qth.net
> Subject: Re: [Elecraft] K3 Band changing...Devils Advocate...
> 
> Don,
> 
> Do you really want band *stacking* memories?  A stacking memory is
> first-in, last out, so you have to drill down through the stack to get
> the one you want.  That seems likea much worse situation than the normal
> band up/down switch which is a double ended stack.
> 
> If you are referring to something different, then please do not call it
> a stack - the definition of a memory stack has been quite clear since
> the first days of microprocessors.
> 
> 73,
> Don W3FPR
> 
> Don Rasmussen wrote:
> > I brought up the band changing issue early on with the
> > guys, not because I just had to have it, but because
> > it seemed that every transceiver these days that's big
> > enough to have them, does.
> >
> > The thing that I find disconcerting is that even
> > though many of the buttons on the K3 are fully
> > occupied with multiple TAP and HOLD functions, there
> > are (5) that I will never ever use in their TAP -or-
> > HOLD capacity - those being M1, M2, M3, M4, and REC.
> >
> > These could clearly be drafted into service as band
> > stacking registers (on first press), yet they just
> > stay there hogging up space on my front panel.
> >
> > I proposed a CONFIG option that would allow the
> > MESSAGE keys to be used either as DVK on first press
> > as originally fitted, but also could be used as
> > bandstack keys if the user preferred that as a first
> > press function over the DVK.
> >
> > A minimum of 5 band stack keys are waiting there for
> > use, 10 if you include HOLD.
> >
> >
> _______________________________________________
> Elecraft mailing list
> Post to: Elecraft at mailman.qth.net
> You must be a subscriber to post to the list.
> Subscriber Info (Addr. Change, sub, unsub etc.):
>  http://mailman.qth.net/mailman/listinfo/elecraft
> 
> Help: http://mailman.qth.net/subscribers.htm
> Elecraft web page: http://www.elecraft.com




More information about the Elecraft mailing list