Hi Steve,

> You key in 9.5mhz and somehow you are supposed to know you are on 30m?

Well, that's the part that I think could be explained better in the  
manual.  As I mentioned, I had to determine those band limits  
experimentally.  It might help to reduce confusion if Elecraft  
published those band limits in the manual.

> Then you hit BAND UP and land on 20m when you started out on 60M?

Yes.  I started on 60m (5.3 MHz), but then punched in 9.5 MHz, thus  
accomplishing a band change.  I might not know just where the  
boundaries are (see above), but suppose I'd punched in 10.110 instead  
of 9.5.  Wouldn't it seem reasonable to assume that the rig is now in  
the 30m band regardless of where I started from or how I got there?

When you arrive on a frequency that's in a different band from where  
you started, regardless of how you got there (band switch, direct  
entry, vfo spinning, or memory recall), you've changed bands.  The  
trick is in knowing where the band edges are.  (Which has been kept a  
closely guarded secret until now.  I'm sure the Aptos mafia is looking  
for me ... :-)

I'm not arguing against your idea of some sort of dedicated general  
coverage receive mode, but it didn't sound like it was likely to show  
up any time soon.  So until it does get implemented, understanding how  
it actually works (no matter how wrong it might feel) might be the  
only option.

73
--
Joe KB8AP


On Nov 15, 2009, at 7:26 PM, Steve Ellington wrote:

> Hi Joe:
> Letsseee.....You were on 60m. You key in 9.5mhz and somehow you are  
> supposed to know you are on 30m? Then you hit BAND UP and land on  
> 20m when you started out on 60M? So you hit BAND DOWN and land back  
> at 9.5mhz? Then you panic and hit BAND DOWN again and your on  
> ummmm....40? Then BAND DOWN again and your on 60m and it looks just  
> fine. What happend to my 9.5mhz? Oh....yea its up there  
> somewhere...let's see...I'll go back up and change it to 30m  
> again...etc.
>
> And you don't see where the order is messed up? So you experimented?
> Look....This is a great rig but changing bands is incredibly weird.  
> Trying to defend it makes it sound even worse.
>
> And for you 60m lovers....I have nothing against it....Just don't  
> use it.
>
> Of course with PowerSDR-IF and LP-PAN I can hop around the spectrum  
> like crazy but that's another matter!
> 73
> Steve
> N4LQ
> n...@carolina.rr.com
> ----- Original Message ----- From: "Joe Planisky" <jp...@jeffnet.org>
> To: "Steve Ellington" <n...@carolina.rr.com>
> Cc: "Elecraft Reflector" <elecraft@mailman.qth.net>
> Sent: Sunday, November 15, 2009 10:09 PM
> Subject: Re: [Elecraft] K3 Firmware Req for SWL band and Using  
> Memories
>
>
>> I don't see how you've "lost" any band or changed any band ordering  
>> in
>> your example.
>>
>>    1. you used the BAND button to go to 60m (5.3xx MHz).
>>
>>    2. you punched in 9.5 MHz.  9.5 MHz happens to be within the
>> boundaries of the K3's 30m band, therefore you've changed bands to  
>> 30m.
>>
>>    3. at this point, pressing BAND UP goes to 20m as expected.
>>
>>    4. from 20m, pressing BAND DN takes you back to your last
>> frequency on 30m (9.5 MHz)
>>
>>    5. pressing BAND DN again, takes you to 40m.
>>
>> I really don't see where any order has been messed up or anything has
>> been lost.  (Unless your rig is behaving differently than mine?)
>>
>> I've found it helpful to know that the actual band limits are as
>> follows (determined experimentally);
>>
>> 160m  0.5 -  2.999999 MHz
>> 80m  3.0 -  4.799999 MHz
>> 60m  4.8 -  5.999999 MHz
>> 40m  6.0 -  8.999999 MHz
>> 30m  9.0 - 12.999999 MHz
>> 20m 13.0 - 16.999999 MHz
>> 17m 17.0 - 18.999999 MHz
>> 15m 19.0 - 22.999999 MHz
>> 12m 23.0 - 25.999999 MHz
>> 10m 26.0 - 30.000000 MHz
>>  6m 44.0 - 54.000000 MHz
>>
>> So any time I go from, say, 5.8 MHz to 6.1 MHz, I've changed bands
>> from 60m to 40m, whether I've gotten there by direct frequency entry
>> or by spinning the VFO knob. If I then hit BAND UP, I go from 40m to
>> 30m.  And since the K3 remembers the last frequency used on any given
>> band, if I then hit BAND DN, I go back to 6.1 MHz, which is the last
>> 40m frequency I was on.
>>
>> Does this help at all, or am I still missing the boat?
>>
>> 73
>> --
>> Joe KB8AP
>>
>>
>> On Nov 15, 2009, at 5:10 PM, Steve Ellington wrote:
>>
>>> Memories are too complicated and too much trouble. Seems like this
>>> band switching confusion has been an ongoing problem since the
>>> beginning. People, including me, foul up the band sequence by moving
>>> out of band then changing bands. Suddenly, their favorite ham band
>>> is missing.
>>> I'm suggesting that another band, GEN, be added to the chain. If one
>>> wants to play SWL, just go to that band and have at it.  It would
>>> not mess up your band sequence nor would it mess up any other band.
>>> My alternate suggestion was to allow the use of any particular band
>>> for this purpose, such as 60 meters or some other band that you
>>> never use. Right now, if one tries to do that it totally screws up
>>> the order and you loose a band that had nothing to do with the one
>>> you changed. I gave an example of this.
>>> Steve
>>> N4LQ
>>> n...@carolina.rr.com
>>> ----- Original Message ----- From: "Joe Planisky"  
>>> <jp...@jeffnet.org>
>>> To: "Elecraft Reflector" <elecraft@mailman.qth.net>
>>> Sent: Sunday, November 15, 2009 7:51 PM
>>> Subject: Re: [Elecraft] K3 Firmware Req for SWL band and Using
>>> Memories
>>>
>>>
>>>> Here's yet another solution.
>>>>
>>>> I have the M1 - M4 per-band memories set up as follows for each ham
>>>> band:
>>>>
>>>> M1 - Mode=CW, Freq = beginning of CW segment.
>>>> M2 - Mode=CW, Freq = end of CW segment.
>>>> M3 - Mode=USB or LSB, depending on the band, Freq = beginning of  
>>>> the
>>>> phone segment.
>>>> M4 - Mode=USB or LSB, depending on the namd, Freq = end of the  
>>>> phone
>>>> segment.
>>>>
>>>> Then, when I've been tuning around the SWL bands and pressing BAND
>>>> UP/
>>>> DN takes me someplace unexpected, I just hit M>V and any of the  
>>>> M1-M4
>>>> buttons and I'm back in the ham band.
>>>>
>>>> 73
>>>> --
>>>> Joe KB8AP
>>>>
>>>> On Nov 15, 2009, at 4:07 PM, John W2XS wrote:
>>>>
>>>>>
>>>>> Steve posted:
>>>>>>> I guess the only way to do this and not get confused is to  
>>>>>>> fiddle
>>>>>>> with
>>>>>>> memories or remember to tune back within whatever ham band
>>>>>>> you happened to screw up before changing bands.
>>>>>
>>>>> I do a lot of SWL'ing and AM BCB listening and always return to  
>>>>> the
>>>>> ham
>>>>> bands by using one of the first 10 memory locations. This was an
>>>>> idea posted
>>>>> a while ago and I still find it very handy.  It's almost like band
>>>>> buttons.
>>>>
>>>> ______________________________________________________________
>>>> Elecraft mailing list
>>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft
>>>> Help: http://mailman.qth.net/mmfaq.htm
>>>> Post: mailto:Elecraft@mailman.qth.net
>>>>
>>>> This list hosted by: http://www.qsl.net
>>>> Please help support this email list: http://www.qsl.net/donate.html
>>>
>>>
>>> --------------------------------------------------------------------------------
>>>
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com
>>> Version: 9.0.707 / Virus Database: 270.14.67/2505 - Release Date:
>>> 11/15/09 14:50:00
>>>
>>
>
>
> --------------------------------------------------------------------------------
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.707 / Virus Database: 270.14.67/2505 - Release Date:  
> 11/15/09 14:50:00
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

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

Reply via email to