Elecraft › [K3]

K3 Firmware Req for SWL band

Classic

List

Threaded

26 messages Options

Steve Ellington

K3 Firmware Req for SWL band

let me make this an offical request for FW if it's possible.
Either:
1. Add an extra band for general coverage.
2. Or allow use of one of the bands for gen. cov. and fix it so it doesn't
screw up another band. (Hard to put in words).
Steve
N4LQ
[hidden email]
----- Original Message -----
From: "Joe Subich, W4TV" <[hidden email]>
To: "'Steve Ellington'" <[hidden email]>
Sent: Sunday, November 15, 2009 2:36 PM
Subject: RE: [Elecraft] K3 More Bandmap gab

>
>> I happen to have a little IC-7000. It has a similar BAND
>> up/down button on the front panel. If I tune out of a ham
>> band and change bands, it still remembers all the ham bands
>> PLUS it comes back to my SWL band as I scroll through the
>> bands again.
>
> Most Icom rigs have the "Gen" band which holds the last non-
> ham band frequency. Yaesu has added that feature to the
> FT-9000/FT-2000/FT-950/FT-450 ... it is very convenient as
> opposed to leaving the VFO out of band as in the K3.
>
> 73,
>
> ... Joe, W4TV
>
>
>
>
>
>> -----Original Message-----
>> From: [hidden email]
>> [mailto:[hidden email]] On Behalf Of Steve Ellington
>> Sent: Sunday, November 15, 2009 1:42 PM
>> To: [hidden email]
>> Subject: [Elecraft] K3 More Bandmap gab
>>
>>
>> I like to surf the SW bands on occasion and as we know, if
>> you tune out of a
>> ham band and change bands you screw up the band sequence.
>> Well I had this
>> brilliant idea....Since I never operate 60 meters I would
>> just designate
>> that as my SW band mode and not mess up my usual ham band
>> sequence. But
>> nooooo. I can go to 60 meters, punch in 9.5 mHz then change
>> bands with the
>> BAND button and find out I've lost 30 meters....Yes 30 meters
>> is now 9.5 mHz
>> and 60 meters is still there.
>>
>> 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 happen to have a little IC-7000. It has a similar BAND
>> up/down button on
>> the front panel. If I tune out of a ham band and change
>> bands, it still
>> remembers all the ham bands PLUS it comes back to my SWL band
>> as I scroll
>> through the bands again. Cool. The microphone has a band
>> button for each
>> band and one of them is labeled GEN for general coverage.
>>
>> I'm just wondering if there would be some easy firmware
>> change that would
>> help with this?
>> Steve
>> N4LQ
>> [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
>

______________________________________________________________
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

John W2XS

Re: K3 Firmware Req for SWL band and Using Memories

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. I use:

Mem 1 = 10 meters
Mem 2 = 20 meters
Mem 3 = 30 meters
Mem 4 = 40 meters
Mem 5 = 15 meters
Mem 6 = 60 meters (then M1 to M4 for the rest)
Mem 7 = 17 meters
Mem 8 = 80 meters
Mem 9 = 6 meters (6 = upside down 9)
Mem 0 = 160 meters

I have been able to remember these assignments. To get to 12 meters, I first go to 15 meters as above and then press Band Up.

I have most of the other 90 available memories filled with misc. SWL and AM BCB station frequencies. To rapidly switch between memories, I normally use the program "Commander", which has access to all 100 memory locations. I programmed the first 10 in Commander to be the same as the first 10 in the K3.

73,

John W2XS

Joe Planisky

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

Steve Ellington

Re: K3 Firmware Req for SWL band and Using Memories

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
[hidden email]
----- Original Message -----
From: "Joe Planisky" <[hidden email]>
To: "Elecraft Reflector" <[hidden email]>
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:[hidden email]
>
> 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

______________________________________________________________
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

Don Wilhelm-4

Re: K3 Firmware Req for SWL band and Using Memories

In reply to this post by Joe Planisky

Joe,

I think that is a good solution (except for those who use the M1-M4
frequency memories for other purposes), because it will always take you
back to the "proper" ham band - The M1-M4 memories are 'per band'.

73,
Don W3FPR

Joe Planisky wrote:

wayne burdick

Re: K3 Firmware Req for SWL band and Using Memories

Administrator

In reply to this post by Steve Ellington

Hi Steve,

I'd like to do something along these lines. It's a nontrivial change
to the firmware, but I've added it to the list.

tnx
Wayne
N6KR

On Nov 15, 2009, at 5:10 PM, Steve Ellington wrote:

> Memories are too complicated and too much trouble....
> 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.

______________________________________________________________
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

Joe Planisky

Re: K3 Firmware Req for SWL band and Using Memories

In reply to this post by Steve Ellington

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
> [hidden email]
> ----- Original Message ----- From: "Joe Planisky" <[hidden email]>
> To: "Elecraft Reflector" <[hidden email]>
> 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:[hidden email]
>>
>> 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
>

Steve Ellington

Re: K3 Firmware Req for SWL band and Using Memories

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
[hidden email]
----- Original Message -----
From: "Joe Planisky" <[hidden email]>
To: "Steve Ellington" <[hidden email]>
Cc: "Elecraft Reflector" <[hidden email]>
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
>> [hidden email]
>> ----- Original Message ----- From: "Joe Planisky" <[hidden email]>
>> To: "Elecraft Reflector" <[hidden email]>
>> 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:[hidden email]
>>>
>>> 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
>>
>

David Gilbert

Re: K3 Firmware Req for SWL band and Using Memories

Yes, that's exactly what you're supposed to do. Reread KB8AP's chart
below for your answer. You're simply glued into thinking that "30m"
somehow means 10.100 MHz to 10.150 MHz. It doesn't. And it never will
unless you want Elecraft to do one of two things:

a. disable general coverage tuning on the K3

b. create a whole bunch of other "bands" to step through that includes
all the segments between the ham bands.

Dave AB7E

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

> ----- Original Message -----
> From: "Joe Planisky" <[hidden email]>
> To: "Steve Ellington" <[hidden email]>
> Cc: "Elecraft Reflector" <[hidden email]>
> 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
>>> [hidden email]
>>> ----- Original Message ----- From: "Joe Planisky" <[hidden email]>
>>> To: "Elecraft Reflector" <[hidden email]>
>>> 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:[hidden email]
>>>>
>>>> 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:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
>

Steve Ellington

Re: K3 Firmware Req for SWL band and Using Memories

Yes I should know that 9 mHz 30 meters instead of 33 meters. Yep...."Glued into thinking". That's me! Gotta shake that urge. I'll glue this chart somewhere. No suggestions please.

Steve
N4LQ
[hidden email]
----- Original Message -----
From: David Gilbert
To: Steve Ellington
Cc: Joe Planisky ; Elecraft Reflector
Sent: Sunday, November 15, 2009 11:07 PM
Subject: Re: [Elecraft] K3 Firmware Req for SWL band and Using Memories

Yes, that's exactly what you're supposed to do. Reread KB8AP's chart below for your answer. You're simply glued into thinking that "30m" somehow means 10.100 MHz to 10.150 MHz. It doesn't. And it never will unless you want Elecraft to do one of two things:

a. disable general coverage tuning on the K3

b. create a whole bunch of other "bands" to step through that includes all the segments between the ham bands.

Dave AB7E

Steve Ellington wrote:
You key in 9.5mhz and somehow you are supposed
to know you are on 30m?

----- Original Message -----
From: "Joe Planisky" <[hidden email]>
To: "Steve Ellington" <[hidden email]>
Cc: "Elecraft Reflector" <[hidden email]>
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
[hidden email]
----- Original Message ----- From: "Joe Planisky" <[hidden email]>
To: "Elecraft Reflector" <[hidden email]>
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:[hidden email]

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

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

Joe Planisky

Re: K3 Firmware Req for SWL band and Using Memories

In reply to this post by Steve Ellington

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
> [hidden email]
> ----- Original Message ----- From: "Joe Planisky" <[hidden email]>
> To: "Steve Ellington" <[hidden email]>
> Cc: "Elecraft Reflector" <[hidden email]>
> 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
>>> [hidden email]
>>> ----- Original Message ----- From: "Joe Planisky"
>>> <[hidden email]>
>>> To: "Elecraft Reflector" <[hidden email]>
>>> 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:[hidden email]
>>>>
>>>> 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
>

Bob Naumann W5OV

Re: K3 Firmware Req for SWL band and Using Memories

AB7E said:

" b. create a whole bunch of other "bands" to step through that includes
all the segments between the ham bands".

I think that this sounds like a great solution.

Would it be reasonable to have an alternative "SWL" selection of bands
available as a CONFIG option?

It could be as simple as BANDS: HAM / SWL

When in SWL mode, no transmit would be possible and the various SWL bands
could be "band-upped" or "band-downed" to change from one to the other.
Maybe show SWL somewhere on the display to indicate that one is in SWL mode.

A good listing of the possible bands for SWL mode is here:

http://www.dxing.com/tuning.htm

Some of them could obviously be combined to reduce the # of bands.

When finished SWLing, go back to CONFIG, BAND, and select "HAM" and go back
to "normal".

Possible?

W5OV

______________________________________________________________
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

Steve Ellington

Re: K3 Firmware Req for SWL band and Using Memories

How about a "Take me back to the ham band macro button"?
Let's pretend that we get up one morning, turn on the rig and while
scrolling through the bands, 9.5 mHz pops up. Instead of trying to figure
out what band this is and cranking the VFO or entering a freq. just hit PF2
or something. I haven't bothered to study all that macro stuff but is there
a possibility?
Steve
N4LQ
[hidden email]
----- Original Message -----
From: "Robert Naumann" <[hidden email]>
To: "'Elecraft Reflector'" <[hidden email]>
Sent: Monday, November 16, 2009 7:14 AM
Subject: Re: [Elecraft] K3 Firmware Req for SWL band and Using Memories

> AB7E said:
>
> " b. create a whole bunch of other "bands" to step through that includes
> all the segments between the ham bands".
>
>
> I think that this sounds like a great solution.
>
> Would it be reasonable to have an alternative "SWL" selection of bands
> available as a CONFIG option?
>
> It could be as simple as BANDS: HAM / SWL
>
> When in SWL mode, no transmit would be possible and the various SWL bands
> could be "band-upped" or "band-downed" to change from one to the other.
> Maybe show SWL somewhere on the display to indicate that one is in SWL
> mode.
>
> A good listing of the possible bands for SWL mode is here:
>
> http://www.dxing.com/tuning.htm
>
> Some of them could obviously be combined to reduce the # of bands.
>
> When finished SWLing, go back to CONFIG, BAND, and select "HAM" and go
> back
> to "normal".
>
> Possible?
>
> W5OV
>
>
> ______________________________________________________________
> 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

Richard Ferch

Re: K3 Firmware Req for SWL band and Using Memories

In reply to this post by John W2XS

W5OV wrote:

> Would it be reasonable to have an alternative "SWL" selection of bands
> available as a CONFIG option?
>
> It could be as simple as BANDS: HAM / SWL
>
> When in SWL mode, no transmit would be possible and the various SWL bands
> could be "band-upped" or "band-downed" to change from one to the other.
> Maybe show SWL somewhere on the display to indicate that one is in SWL mode.

This is still quite complex. I'd go for something simpler, namely a
single SWL "band" that contains all of the frequencies outside the ham
bands. The SWL "band" could be placed between 6 meters and 160 meters in
the BAND switch's rotation, and would always contain the last
non-amateur frequency used.

The existing CONFIG:BND MAP menu item could be used to enable/disable
this feature: SWL IN would enable the new feature, SWL OUT would restore
the existing modus operandi for those who prefer it.

73,
Rich VE3KI

______________________________________________________________
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

Joe Planisky

Re: K3 Firmware Req for SWL band and Using Memories

In reply to this post by Steve Ellington

Hi Steve,

> How about a "Take me back to the ham band macro button"?

Yes, that's essentially what the scheme I described with the M1-M4
buttons does. You wouldn't have to set up all 4 buttons like I did.
Here's how you could set it up with just one:

1. Go to the 160m band.

2. Set VFO A to your favorite frequency in that band (say, 1.9 MHz)

3. Set the mode to whatever you want.

4. Press V>M then the M1 button (or M2, M3, or M4)

5. Now, any time your VFO is in the range of 0.5 to 2.9 and you press
M>V followed by M1, you'll go to 1.9 MHz and the mode will be set to
whatever you used in step 3.

6. Now go to 80m and repeat steps 2 - 4, using the same button in step
4. Repeat for 60m, 40m, 30m, etc. All 11 bands.

Once you have all 11 bands set up this way, then no matter what
frequency you're on, anywhere in the K3's range, pressing M>V,M1 will
take you to your favorite frequency in the nearest ham band. You don't
have to know the boundaries or anything.

If you really want a one-button solution, set things up as described
above and then try this macro in PF2:

SWT23;SWT21;

(which just taps the M>V key followed by the M1 key.)

Hope this helps

73
--
Joe KB8AP

On Nov 16, 2009, at 4:35 AM, Steve Ellington wrote:

> How about a "Take me back to the ham band macro button"?
> Let's pretend that we get up one morning, turn on the rig and while
> scrolling through the bands, 9.5 mHz pops up. Instead of trying to
> figure
> out what band this is and cranking the VFO or entering a freq. just
> hit PF2
> or something. I haven't bothered to study all that macro stuff but
> is there
> a possibility?
> Steve
> N4LQ
> [hidden email]

drewko

Re: K3 Firmware Req for SWL band

In reply to this post by Steve Ellington

I wouldn't mind keeping BAND as a hamband-only control. However, in
this case it would be nice if the K3's band boundaries usng this
control did conform to the legal ham bands (i.e., 40m should end at
7.000, not 6.000 MHz). I suppose this would mean, for instance, when
you wander below 7.0 MHz, that BAND should remember "7.000" and no
lower. (But I guess this would be complicated by the differring band
assignments for different jurisdictions....)

I would like to have a coarse tuning rate of 1.0 MHz so that any 1 MHz
band in the entire 30 MHz HF coverage could be accessed within one
revolution of the VFO knob. I think this would be slightly more
convenient than direct frequency entry.

I would also like to have some macro commands for manipulation of
frequency memory. With this capability you could program a "band bank"
macro that would copy a range of ten frequency slots into the 00-09
"quick memory" positions. Then you could switch in a bank of ten SWL
frequency pairs, or a bank of SSB, or CW, AM Bcst, etc. Then use the
"M>V x" quick memory to access the bands in your currently selected
bank.

73,
Drew
AF2Z

On Sun, 15 Nov 2009 16:30:34 -0500, Steve N4LQ wrote:

>let me make this an offical request for FW if it's possible.
>Either:
>1. Add an extra band for general coverage.
>2. Or allow use of one of the bands for gen. cov. and fix it so it doesn't
>screw up another band. (Hard to put in words).
>Steve
>N4LQ

______________________________________________________________
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

Mike Harris

Re: K3 Firmware Req for SWL band and Using Memories

In reply to this post by Joe Planisky

G'day,

Seems too complicated. My general coverage module is in the main RX
and I tune with VFO A. VFO B always has a return frequency and a
simple A/B and then A>B sorts things out.

It does it for me.

Regards,

Mike VP8NO

----- Original Message -----
From: "Joe Planisky" <[hidden email]>
To: "Steve Ellington" <[hidden email]>
Cc: "Elecraft Reflector" <[hidden email]>
Sent: Monday, November 16, 2009 11:10 AM
Subject: Re: [Elecraft] K3 Firmware Req for SWL band and Using
Memories

> Hi Steve,
>
>> How about a "Take me back to the ham band macro button"?
>
>
> Yes, that's essentially what the scheme I described with the M1-M4
> buttons does. You wouldn't have to set up all 4 buttons like I
> did.
> Here's how you could set it up with just one:
>
> 1. Go to the 160m band.
>
> 2. Set VFO A to your favorite frequency in that band (say, 1.9
> MHz)
>
> 3. Set the mode to whatever you want.
>
> 4. Press V>M then the M1 button (or M2, M3, or M4)
>
> 5. Now, any time your VFO is in the range of 0.5 to 2.9 and you
> press
> M>V followed by M1, you'll go to 1.9 MHz and the mode will be set
> to
> whatever you used in step 3.
>
> 6. Now go to 80m and repeat steps 2 - 4, using the same button in
> step
> 4. Repeat for 60m, 40m, 30m, etc. All 11 bands.
>
> Once you have all 11 bands set up this way, then no matter what
> frequency you're on, anywhere in the K3's range, pressing M>V,M1
> will
> take you to your favorite frequency in the nearest ham band. You
> don't
> have to know the boundaries or anything.
>
> If you really want a one-button solution, set things up as
> described
> above and then try this macro in PF2:
>
> SWT23;SWT21;
>
> (which just taps the M>V key followed by the M1 key.)
>
> Hope this helps
>
> 73
> --
> Joe KB8AP

Joe Subich, W4TV-4

Re: K3 Firmware Req for SWL band and Using Memories

In reply to this post by Richard Ferch

> The SWL "band" could be placed between 6 meters and
> 160 meters in the BAND switch's rotation, and would
> always contain the last non-amateur frequency used.

Let it fall in frequency sequence. If one used it for
MW broadcast (US AM band) it would fall between 6 and 160
but if it was being used for WWV at 10 MHz it would fall
between 40 and 30 Meters. This is the way both Icom and
Yaesu do it.

> The existing CONFIG:BND MAP menu item could be used to
> enable/disable this feature: SWL IN would enable the new
> feature, SWL OUT would restore the existing modus operandi
> for those who prefer it.

Alternatively, SWL OUT could simply disable storage of a
frequency outside of the specific amateur band. If one
tuned to WWV on 10 MHz then used the band up/down to go
to 20 Meters, the 30 Meter bad would be reset to 10.100
and similarly on the other bands. It should not be too
difficult to reset to the bottom of the band since the
K3 already knows the band edges to disable out of band
transmit.

73,

... Joe, W4TV

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Richard Ferch
> Sent: Monday, November 16, 2009 8:40 AM
> To: [hidden email]
> Subject: Re: [Elecraft] K3 Firmware Req for SWL band and
> Using Memories
>
>
> W5OV wrote:
>
> > Would it be reasonable to have an alternative "SWL"
> selection of bands
> > available as a CONFIG option?
> >
> > It could be as simple as BANDS: HAM / SWL
> >
> > When in SWL mode, no transmit would be possible and the various SWL
> > bands could be "band-upped" or "band-downed" to change from
> one to the
> > other. Maybe show SWL somewhere on the display to indicate
> that one is
> > in SWL mode.
>
> This is still quite complex. I'd go for something simpler, namely a
> single SWL "band" that contains all of the frequencies
> outside the ham
> bands. The SWL "band" could be placed between 6 meters and
> 160 meters in
> the BAND switch's rotation, and would always contain the last
> non-amateur frequency used.
>
> The existing CONFIG:BND MAP menu item could be used to enable/disable
> this feature: SWL IN would enable the new feature, SWL OUT
> would restore
> the existing modus operandi for those who prefer it.
>
> 73,
> Rich VE3KI
>

Steve Ellington

Re: K3 Firmware Req for SWL band and Using Memories

In reply to this post by Mike Harris

Mike
Not sure I follow this. Do you use dual receives? What do you mean by "VFO B
always has a return frequency"?

Steve
N4LQ
[hidden email]
----- Original Message -----
From: "Mike Harris" <[hidden email]>
To: "Reflector Elecraft" <[hidden email]>
Sent: Monday, November 16, 2009 9:19 AM
Subject: Re: [Elecraft] K3 Firmware Req for SWL band and Using Memories

> G'day,
>
> Seems too complicated. My general coverage module is in the main RX
> and I tune with VFO A. VFO B always has a return frequency and a
> simple A/B and then A>B sorts things out.
>
> It does it for me.
>
> Regards,
>
> Mike VP8NO
>
> ----- Original Message -----
> From: "Joe Planisky" <[hidden email]>
> To: "Steve Ellington" <[hidden email]>
> Cc: "Elecraft Reflector" <[hidden email]>
> Sent: Monday, November 16, 2009 11:10 AM
> Subject: Re: [Elecraft] K3 Firmware Req for SWL band and Using
> Memories
>
>
>> Hi Steve,
>>
>>> How about a "Take me back to the ham band macro button"?
>>
>>
>> Yes, that's essentially what the scheme I described with the M1-M4
>> buttons does. You wouldn't have to set up all 4 buttons like I
>> did.
>> Here's how you could set it up with just one:
>>
>> 1. Go to the 160m band.
>>
>> 2. Set VFO A to your favorite frequency in that band (say, 1.9
>> MHz)
>>
>> 3. Set the mode to whatever you want.
>>
>> 4. Press V>M then the M1 button (or M2, M3, or M4)
>>
>> 5. Now, any time your VFO is in the range of 0.5 to 2.9 and you
>> press
>> M>V followed by M1, you'll go to 1.9 MHz and the mode will be set
>> to
>> whatever you used in step 3.
>>
>> 6. Now go to 80m and repeat steps 2 - 4, using the same button in
>> step
>> 4. Repeat for 60m, 40m, 30m, etc. All 11 bands.
>>
>> Once you have all 11 bands set up this way, then no matter what
>> frequency you're on, anywhere in the K3's range, pressing M>V,M1
>> will
>> take you to your favorite frequency in the nearest ham band. You
>> don't
>> have to know the boundaries or anything.
>>
>> If you really want a one-button solution, set things up as
>> described
>> above and then try this macro in PF2:
>>
>> SWT23;SWT21;
>>
>> (which just taps the M>V key followed by the M1 key.)
>>
>> Hope this helps
>>
>> 73
>> --
>> Joe KB8AP
>
> ______________________________________________________________
> 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

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

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.707 / Virus Database: 270.14.67/2506 - Release Date: 11/16/09
02:43:00

______________________________________________________________
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

drewko

Re: K3 Firmware Req for SWL band and Using Memories

In reply to this post by wayne burdick

Wayne,

In the meantime, would it be feasible for you to add some macro
commands for manipulation of frequency memory? Then we could write
switch macros that would copy ten slots in upper frquency memory to
the 00-09 "quick memory" locations.

In that way a bank of SWL freqs could be copied to 00-09 (or
similarly, a bank of SSB, CW, AM Bcst, etc). One could swap in
whatever bank one wished and use the "M>V x" quick memories to select
the bands in one's chosen bank.

73,
Drew
AF2Z

On Sun, 15 Nov 2009 18:39:26 -0800, you wrote:

>Hi Steve,
>
>I'd like to do something along these lines. It's a nontrivial change
>to the firmware, but I've added it to the list.
>
>tnx
>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