K3 Band changing...Devils Advocate...

[Don Rasmussen]

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.

But I'll not malign the K3 for missing what was on the
756Pro and the OMNI VI+, because once I find a
frequency with the K3 it's a more enjoyable place to
be.

[Elecraft] K3 Band changing...
ab2tc ab2tc at arrl.net
Thu May 29 17:35:19 EDT 2008

Previous message: [Elecraft] K3 Band changing...
Next message: [Elecraft] K3 Band changing...
Messages sorted by: [ date ] [ thread ] [ subject ] [
author ]

--------------------------------------------------------------------------------

We are indeed spoiled. If Elecraft could just fix the
disappearing of ham
bands on the BAND button when tuning to a non-ham-band
frequency, I would be
happy as punch. Not all radios have a dedicated button
for each band (at
least 11), which is really a waste of panel space. I
have been happy
band-switching (up/down buttons) with my IC-718 for
years, but it doesn't
have the Elecraft disappearance quirk.

Knut - AB2TC


_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Don Wilhelm-4]

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: [hidden email]
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

[Dave Van Wallaghen]

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: [hidden email] [mailto:elecraft-
> [hidden email]] On Behalf Of Don Wilhelm
> Sent: Friday, May 30, 2008 8:12 AM
> To: Don Rasmussen
> Cc: [hidden email]
> 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: [hidden email]
> 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

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Don Wilhelm-4]

Dave,

I believe what is really wanted is "random access" band buttons - in
other words a single button press for each band.  For the life of me, I
cannot figure out how this ever has been construed in ham circles to use
the term "band stacking memories" - perhaps someone can tell me how
'random access'  equates to a 'stack'.

Despite the fact that several proposals have been brought forward for
how to use the quick memory keypad (as well as the other memories) for
this purpose (and it is also suggested in the K3 manual), the complaints
continue because Elecraft has not chosen to make that function a
permanent (and unchangable) feature.  I just can't understand why the
complaints, since that 'feature' is already present if one wants to set
it up that way.

73,
Don W3FPR

Dave Van Wallaghen wrote:

> 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
>  
>

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Dave Van Wallaghen]

Ok, lets see if I get it - users want to randomly assign bands to a set of
buttons in an order of their choosing, that makes sense to the operation
they are performing, then memorize the meaning of the buttons, and call up a
particular (and memorized) band with a single button.

And this would be more convenient than cycling through the band select
buttons, presumably because you are forced to cycle through bands you may
not need to at this point in your operation.

Am I getting this right? I apologize for the bandwidth - I'm just trying to
get educated.

73,
Dave W8FGU

> -----Original Message-----
> From: Don Wilhelm [mailto:[hidden email]]
> Sent: Friday, May 30, 2008 9:02 AM
> To: Dave Van Wallaghen
> Cc: 'Don Rasmussen'; [hidden email]
> Subject: Re: [Elecraft] K3 Band changing...Devils Advocate...
>
> Dave,
>
> I believe what is really wanted is "random access" band buttons - in
> other words a single button press for each band.  For the life of me, I
> cannot figure out how this ever has been construed in ham circles to use
> the term "band stacking memories" - perhaps someone can tell me how
> 'random access'  equates to a 'stack'.
>
> Despite the fact that several proposals have been brought forward for
> how to use the quick memory keypad (as well as the other memories) for
> this purpose (and it is also suggested in the K3 manual), the complaints
> continue because Elecraft has not chosen to make that function a
> permanent (and unchangable) feature.  I just can't understand why the
> complaints, since that 'feature' is already present if one wants to set
> it up that way.
>
> 73,
> Don W3FPR
>
> Dave Van Wallaghen wrote:
> > 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
> >
> >

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[John W2XS]

I haven't used the K3 receiver enough to really comment, but I like the way the TS-930 works (with the PIEXX board installed).  There are 99 memories available which are accessed via the RIT knob (similar to the K3 and the VFO B knob).  In addition, there are 9 individual band buttons on the front panel that are assignable to any frequency in that band. So, for example, I can be listening to WBCQ on 7415 and then press the "80" button to move to 3530 (the frequency that I have programmed for 80 meters). The direct-frequency-entry capability of the K3 is roughly the same thing with a few more button pushes. The 930 also has "up" and "down" buttons that allow scrolling through the spectrum in 500kHz steps.

73,  John W2XS

[Gary, W7TEA]

My K3 should be arriving in a 2-3 weeks so I'll
obviously pass on making suggestions until I can play with it awhile.  
My Omni VII's band stacking registers are not FIFO
but rather like having four sets of VFO's for each band at
the push of one button.  

So VFO A could be at 14.001 and VFO B operating
split at 14.003 on register A.  Registers B, C, and D
can have their own unique settings.  Rotating back to
Register A brings back the last frequency you were at
in this register-or 14.001/14.003.  You move thru the
registers by punching the band buttons. In addition,
there are 100 memories each able to save both VFO's
and split operation.  They take two button pushes to
either choose or save a frequency and to transfer it
from memory to VFO.

Seems pretty intuitive to me and very easy to use.

Gary W7TEA

[Phil Salas]

Band Stacking:  I can tell you how it worked on the Yaesu MKV.  There were
two "band stacking" registers per band.  When I'd push the band keypad
button for a particular band, I'd go back to the frequency and mode I was
last using on that band.  If I pressed that same band button again, I'd go
to a second previously used frequency and mode in that same band.  If I
pressed the band button again, I'd go back to the first frequency mode, etc.

So I set up one "push" for the CW end of the band, and the second "push" for
the SSB end of the band.  The nice thing was that I'd go back to the
previous frequency, not to a memory frequency, when I'd push the buttons.
So I might be checking an SSB conversation occasionally, but spending most
of my time on CW.  So just pushing the band button (a single push) would
toggle me back and forth between the two frequencies.

Phil - AD5X

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[drewko]

I don't have a K3 yet but I'm happy with the Band+ and Band- buttons
on my K2. I pretty much know how many pushes I'll need to get from one
band to another, usually only one or two away.

Anyhow, the display changes instantly with each button push before the
relays get a chance to switch, so you can quickly step through
multiple bands, watching the display without tripping the relays,
until your target band is reached. For the ten or so ham bands we have
this seems like a reasonable way of getting around.

I don't know that I'd want ten or twelve extra buttons for this. That
just doesn't seem any more convenient to me. In fact, it is less
convenient. (But then I am a bug and straight key op so pushing a
switch many hundreds of times in sequence is not a big deal to me,
haha!)

I never have to look at the Band+/Band- buttons; I know where they are
by touch and can just focus on the display. I see that the K3 also has
them in the same location: top left corner. That is ideal as far as
I'm concerned.

Now, getting around the non-ham bands is a different story. I'm not
too crazy about direct frequency entry. Would prefer to just spin a
knob to increment or decrement the frequency in 1-Mhz steps, maybe
five 1-MHz steps per each full turn of the knob.

I understand there is some problem with going between ham bands and
non ham frequencies. I expect this will get straightened out at some
point.


73,
Drew
AF2Z


On Fri, 30 May 2008 09:18:58 -0400, Dave W8FGU wrote:

>Ok, lets see if I get it - users want to randomly assign bands to a set of
>buttons in an order of their choosing, that makes sense to the operation
>they are performing, then memorize the meaning of the buttons, and call up a
>particular (and memorized) band with a single button.
>
>And this would be more convenient than cycling through the band select
>buttons, presumably because you are forced to cycle through bands you may
>not need to at this point in your operation.
>
>Am I getting this right? I apologize for the bandwidth - I'm just trying to
>get educated.
>
>73,
>Dave W8FGU
>

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Dave KQ3T]

I'm starting to think that if, historically, all rigs had come with
Band+ and Band- buttons, plus dedicated GoToBandXY buttons, we'd be
seeing posts asking for a knob connected by a shaft to a multi-gang
rotary switch, hooked to a big air-wound coil with multiple taps.

I'm confident the Elecraft guys are prioritizing their efforts, and
putting "Fifty ways to change bands" at the nether end of the list.

73,
Dave KQ3T



Dave Van Wallaghen wrote:

> Ok, lets see if I get it - users want to randomly assign bands to a set of
> buttons in an order of their choosing, that makes sense to the operation
> they are performing, then memorize the meaning of the buttons, and call up a
> particular (and memorized) band with a single button.
>
> And this would be more convenient than cycling through the band select
> buttons, presumably because you are forced to cycle through bands you may
> not need to at this point in your operation.
>
> Am I getting this right? I apologize for the bandwidth - I'm just trying to
> get educated.
>
> 73,
> Dave W8FGU
>
>  

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Don Wilhelm-4]

John,

If you assign the 'Quick Memories' to the bands  as suggested in the
manual (and per Windy's solution on the reflector), then you have
exactly the same function as your TS-930 provides.  In addition, the
K3's band up/down buttons will take you to the last used frequency on
any band rather than to the fixed frequency you have programmed into the
quick memories.

The only 'catch' is that the buttons are labeled '1' thru '9', so you
have to remember which band corresponds to which button - the
assignments are your choice.

73,
Don W3FPR

John W2XS wrote:

> I haven't used the K3 receiver enough to really comment, but I like the way
> the TS-930 works (with the PIEXX board installed).  There are 99 memories
> available which are accessed via the RIT knob (similar to the K3 and the VFO
> B knob).  In addition, there are 9 individual band buttons on the front
> panel that are assignable to any frequency in that band. So, for example, I
> can be listening to WBCQ on 7415 and then press the "80" button to move to
> 3530 (the frequency that I have programmed for 80 meters). The
> direct-frequency-entry capability of the K3 is roughly the same thing with a
> few more button pushes. The 930 also has "up" and "down" buttons that allow
> scrolling through the spectrum in 500kHz steps.
>
> 73,  John W2XS
>  
>  

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[W6NEK]

Hi Dave,
I think the "Band Stacking Register" definition came from the way Icom
implemented it on their 756PRO series of radio.  This is taken from the
IC-756PROIII operating manual on page 24:

"The triple band stacking register provides 3 memories
in one band. 3 sets of a frequency and operating mode
on each band are automatically stored when used.

If a band key is pushed once, the frequency and operating
mode last used are called up. When the key is
pushed again, another stored frequency and operating
mode are called up.

This function is convenient when you operate 3 operating
modes on one band. For example, one register
is used for a CW frequency, another for an SSB frequency
and the other one for an RTTY frequency."

The 756PRO series of radio has 12 dedicated "Band Keys" which allows this
kind of user interface.  To implement this on the K3 in hardware is simply
not possible.  As I mentioned in a earlier post, it has been achieved using
PowerSDR & LP-PAN.

When not using PowerSDR I simply enter the 1st two digits of the band I want
to go to and press enter.  Works for me.

Best 73,
Frank - W6NEK


----- Original Message -----
From: "Dave Van Wallaghen" <[hidden email]>
To: <[hidden email]>; "'Don Rasmussen'" <[hidden email]>
Cc: <[hidden email]>
Sent: Friday, May 30, 2008 5:35 AM
Subject: RE: [Elecraft] K3 Band changing...Devils Advocate...

> 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

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Mike Harris-9]

Hi Drew,

----- Original Message -----
From: <[hidden email]>
To: <[hidden email]>
Sent: Friday, May 30, 2008 10:20 AM
Subject: Re: [Elecraft] K3 Band changing...Devils Advocate...


|I don't have a K3 yet but I'm happy with the Band+ and Band- buttons
| on my K2. I pretty much know how many pushes I'll need to get from one
| band to another, usually only one or two away.

You will find that the rubber buttons on the K3 do not offer the same
crisp tactile feedback as those on the K2.  The quad function BAND and
MODE buttons are particularly bad in this respect.

Regards,

Mike VP8NO

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[David Woolley (E.L)]

Don Wilhelm wrote:
>
> 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.

I find it confusing to have people request a feature with a confusing
name and not explain exactly what it means, but it seems to me that what
people are asking for might be slightly better described as stacking
band registers.

What they want is a stack, for each band as well as a button for each
band.  The stack isn't a true stack, as it is of limited depth, popping
it is non-destructive and underflowing wraps round.  (I'd need to use
one of the rigs that actually implements this to get the fine details,
so people requesting need to specify in more detail).

 From the discussion, I think what they really want is either most
recently used behaviour (with some means to nominate which settings are
significant) or one sub-register for each mode (in which case there
might be some most recently used behaviour, but there won't really  be
any stacking). (It's possible that some of the "band stacking register"
rigs really are using some form of most recently used behaviour.)

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

The terminology predates microprocessors.  It's necessary to describe
Algol 60, which was started in the late 1950s, and is probably even
older than that.  "The Art of Computer Programming" was written in the
mid-60s, and would certainly have fixed the usage of the term by then.

On the other hand, in my software development career, I've found it not
that uncommon for management track people (i.e. strong marketing skills
to promulgate the usage, but weak enough technically not to understand
it is wrong) to introduce all sorts of misusages into project, or even
company, jargon, specifically including stacks.
>


--
David Woolley
"The Elecraft list is a forum for the discussion of topics related to
Elecraft products and more general topics related ham radio"
List Guidelines <http://www.elecraft.com/elecraft_list_guidelines.htm>
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Mark Bayern]

>"The Art of Computer Programming" was written in the mid-60s, and
> would certainly have fixed the usage of the term by then.

_was_ written in the mid-60s? ... volume 1 maybe. Volume 4 is
currently shown as 'in preparation'. When I first realized that the
work had expanded to 7 volumes I was afraid I wouldn't have the $'s to
purchase the entire set. Now I wonder if I'll live long enough.
<http://www-cs-staff.stanford.edu/~uno/taocp.html>

Mark AD5SS
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Don Wilhelm-4]

Mark Bayern wrote:

>> "The Art of Computer Programming" was written in the mid-60s, and
>> would certainly have fixed the usage of the term by then.
>>    
>
> _was_ written in the mid-60s? ... volume 1 maybe. Volume 4 is
> currently shown as 'in preparation'. When I first realized that the
> work had expanded to 7 volumes I was afraid I wouldn't have the $'s to
> purchase the entire set. Now I wonder if I'll live long enough.
> <http://www-cs-staff.stanford.edu/~uno/taocp.html>
>
> Mark AD5SS
>  

Another question is whether Don Knuth will live to complete all 7
volumes! (or even the 5 volumes that he promised 'for certain').   I
recall he was working in the computer lab as a grad student at Case Tech
when I started there in 1958.  At that time, he pretty much dominated
the entire computer lab.

73,
Don W3FPR
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Brian Lloyd-6]

The biggest problem with all of this is that different manufacturers  
have given different names to the same thing and the same name to  
different things. We can talk about "band stacking registers" (no clue  
as to what those do even tho' I have them in my Icom rig), "memories,"  
etc., until we are blue in the face but the real question is, "what is  
the goal of this feature?"

When designing computer networking equipment my customers used to  
drive me nuts with requests for various features they had seen in  
other products. After much poking and prodding I would usually find  
out that it was some feature that someone else had been sold upon by  
another vendor. Getting people to tell me what problem they were  
trying to actually solve was like pulling teeth. OTOH, once I found  
out what problem they were trying to solve, it was usually quite easy  
to do that AND incorporate it with something else to make the whole  
thing simpler for everyone. So here is my guess at what people are  
trying to accomplish.

As I tune across the band I often hear a signal that sounds  
interesting, e.g. a station in QSO that I want to go back to or a pile-
up I don't want to try to deal with now, but I don't want to stop  
there. I want to keep going. So usually I quickly scribble the  
frequency on a piece of paper but lately I have taken to use the VFO A/
B to "remember" the frequency in VFO B while continuing to tune with  
VFO A (not much use when working split). So I think what people are  
asking for is a way to hit a single button to drop the frequency,  
mode, and filter setting in to temporary memory that will remember the  
last n (2? 3? 10?) button pushes. Then you can move through these by  
pushing some kind of "go-to-previous/go-to-next" button. That way you  
can immediately jump back to something you had previously heard. (I  
like the idea of a knob myself but a forward/back toggle works too.)

I don't know that I would get all excited about that -- heck, I think  
that there are already WAY to many features on most radios and all the  
"features" make operation confusing -- but I can imagine someone  
wanting to do this, especially during a contest.

So, is this a good problem statement?

--

73 de Brian, WB6RQN
Brian Lloyd - brian HYPHEN wb6rqn AT lloyd DOT com


P.S. -- Pet peeve -- radios with a plethora of computer features but  
crappy RF hardware. Now the K3 may be well on the way to the "plethora  
of useless features" but at least it has a great RF deck.

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[k6dgw]

Don Wilhelm wrote:
>
> 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.
>

Actually, well before the first u-processors.  The first stack
architecture computers I can remember came from Burroughs, a company
that was always just a couple of steps ahead of the pack which,
unfortunately, was far enough to lead to their ultimate demise.  The
Burroughs D-824 [I think I remember that right] was a room full of 7
foot cabinets that ran the back-up air defense system for NORAD in the
late 60's and early 70's.  SW was written in JOVIAL.

I wish I understood the issue with band changing.  All of my radios
[FT-847, TS-850, KX1, K2, and K3] have "band-up/band-down" buttons which
has always worked for me.

73,

Fred K6DGW
- Northern California Contest Club
- CU in the 2008 Cal QSO Party  4-5 Oct 08
- www.cqp.org

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[Dave KQ3T]

That sounds like a ring, or circular queue, in CS terms. I'm another who
has never quite understand what a band-stacking memory is, or does.

73,
Dave KQ3T


David Woolley (E.L) wrote:
>
>
> What they want is a stack, for each band as well as a button for each
> band.  The stack isn't a true stack, as it is of limited depth,
> popping it is non-destructive and underflowing wraps round.  (I'd need
> to use one of the rigs that actually implements this to get the fine
> details, so people requesting need to specify in more detail).
>

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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

[drewko]

On Sat, 31 May 2008 10:17:24 -0700, Brian, WB6RQN wrote:

>
>As I tune across the band I often hear a signal that sounds  
>interesting, e.g. a station in QSO that I want to go back to or a pile-
>up I don't want to try to deal with now, but I don't want to stop  
>there. I want to keep going. So usually I quickly scribble the  
>frequency on a piece of paper but lately I have taken to use the VFO A/
>B to "remember" the frequency in VFO B while continuing to tune with  
>VFO A (not much use when working split). So I think what people are  
>asking for is a way to hit a single button to drop the frequency,  
>mode, and filter setting in to temporary memory that will remember the  
>last n (2? 3? 10?) button pushes. Then you can move through these by  
>pushing some kind of "go-to-previous/go-to-next" button. That way you  
>can immediately jump back to something you had previously heard. (I  
>like the idea of a knob myself but a forward/back toggle works too.)
>

I'd often thought that idea would be good for a TV remote control unit
(instead of the standard single-channel "Last" memory button)... until
I realized that I often click through a hundred cable channels and
there is not one channel I want to go back to, let alone many... But
yes, that would be a nice feature for a ham rig (and especially a
general coverage receiver), in my opinion.

I've also been day-dreaming about a mode-specific Band Up/Down switch.
For example, in CW mode the frequencies/settings recalled by cycling
through Band Up/Down would be different than those when you are in
USB/LSB. Or AM, etc. This would suit me because I usually stick to a
single mode and jump around the bands, rather than switching among
different modes within a single band.

73,
Drew
AF2Z

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
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