Elecraft

60 meters

Classic

List

Threaded

10 messages Options

k6dgw

60 meters

I loaded the 5 US 60 m "channels" into my K3 frequency memories, with
VFO A set to CW parameters, VFO B to USB parameters for each one, and
set to step through the 5 of them when recalled from memory. It works
great, just turn the Big Knob to step through the channels ... remember
CB? ... with one wrinkle: Moving the BK moves only VFO A, it doesn't
take VFO B along with it. The VFO B knob adjusts the frequency in
whatever steps are set just like all other bands. The result is that I
can switch between CW and USB on the channel I originally recalled from
memory using the A/B switch, but can't if I move VFO A.

Usually, when I discover an unexpected operation like this, there's a
very good reason why it is so that I never thought of. Does anyone know
the reason for this one?

73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County
______________________________________________________________
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

Rick WA6NHC-2

Re: 60 meters

I'm not sure what your question is, can you restate it?

Each of the memories can be programmed so that both VFO (and mode for
each if I recall, been some years) are set, in this case one VFO for
USB/FT8 and the other for CW, with their specific frequencies as required.

Then you would simply use the A/B for the mode choice of the moment and
tap mode if you want DATA A from USB for example.

To change channels, recall another memory slot; correct the mode if needed.

I went a slightly different route, using ten memories, I have each
channel programmed for a specific mode, "1 CW", "1 USB" etc. then if
data, remember that the USB channel is used, but switch to DATA mode.

It would be FAR simpler in the US if the BAND was permitted (as other
countries allow), not limited to specific frequencies and that would
also allow simpler contact with other that have different channel
requirements (yeah, it's become a DX band, duh).

Rick nhc

PS The dual VFO programming in one memory simplifies programming of say,
6M repeaters where the offset is not a constant (i.e. -500 kHz in CA but
-1700 kHz in Idaho).

On 6/3/2019 11:50 AM, Fred Jensen wrote:

> I loaded the 5 US 60 m "channels" into my K3 frequency memories, with
> VFO A set to CW parameters, VFO B to USB parameters for each one, and
> set to step through the 5 of them when recalled from memory. It works
> great, just turn the Big Knob to step through the channels ...
> remember CB? ... with one wrinkle: Moving the BK moves only VFO A, it
> doesn't take VFO B along with it. The VFO B knob adjusts the
> frequency in whatever steps are set just like all other bands. The
> result is that I can switch between CW and USB on the channel I
> originally recalled from memory using the A/B switch, but can't if I
> move VFO A.
>
> Usually, when I discover an unexpected operation like this, there's a
> very good reason why it is so that I never thought of. Does anyone
> know the reason for this one?
>
> 73,
> Fred ["Skip"] K6DGW
> Sparks NV DM09dn
> Washoe County
> ______________________________________________________________
> 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

k6dgw

Re: 60 meters

On 6/3/2019 12:14 PM, Rick WA6NHC wrote:
> I'm not sure what your question is, can you restate it?
I'll try although it wasn't a question, it was an unexpected observation.
>
> Each of the memories can be programmed so that both VFO (and mode for
> each if I recall, been some years) are set, in this case one VFO for
> USB/FT8 and the other for CW, with their specific frequencies as
> required.
Yes, and very thoughtful of Wayne. That's exactly what I did. In
addition, I set the "channel hopping" mode ["*" in the name IIRC] for
the 5 of them so that once recalled, the Big Knob jumps through each of
them meaning you don't have to recall the next one, it's automagic ...
for VFO A at least.
>
> Then you would simply use the A/B for the mode choice of the moment
> and tap mode if you want DATA A from USB for example.
El Correcto ... at least that was my plan. Unfortunately, when I channel
hop to the next one with the BK, VFO A hops very proficiently, however
it doesn't drag VFO B along to the next channel with it.
>
> To change channels, recall another memory slot; correct the mode if
> needed.
That's what my slick little scheme was supposed to avoid -- having to do
a recall [tap M>V, select, tap M>V]
>
> I went a slightly different route, using ten memories, I have each
> channel programmed for a specific mode, "1 CW", "1 USB" etc. then if
> data, remember that the USB channel is used, but switch to DATA mode.
That works too, and it's not like I'm going to run out of memory slots,
and if all 10 were placed into a channel hopping block, you can move
from one to the next with the BK only.
>
> It would be FAR simpler in the US if the BAND was permitted (as other
> countries allow), not limited to specific frequencies and that would
> also allow simpler contact with other that have different channel
> requirements (yeah, it's become a DX band, duh).
Well, 60 m is what it is worldwide and being one of the regulators is
way above my pay grade. A great number of countries have allocated the
WRC-15 decision of 5351.500 - 5366.500 KHz [15 KHz] which overlaps the
US "Channel 3" at 5358.500. At WRC-12, 5250 - 5450 was originally proposed.

73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County
>

______________________________________________________________
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

K8TE

Re: 60 meters

While you can scan or dial through VFO A, once you "land" on a particular
channel, the VFO B frequency and mode associated with that channel is
available by using the VFO A/B button.

I originally loaded the 60m CW frequencies in VFO A for my 60m channels
since I'm more likely to use them working SOTA activators. However, I
usually scan the SSB channels. Thus, I swapped between VFO A and B so I can
scan USB channels and select the appropriate VFO B CW channels when needed.
This comes in handy when someone suggests 60m for USB or when I see a SOTA
dude spotted on 60m CW.

73, Bill, K8TE, waiting "patiently" to return home and start using HF again!
BCNU at Ham-Com.

--
Sent from: http://elecraft.365791.n2.nabble.com/
______________________________________________________________
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

k6dgw

Re: 60 meters

This began as a simple question, I can't understand why it is so hard to
explain: K3 frequency memories hold frequency, mode, and DSP BW for
both VFO A and VFO B. I used the K3 Frequency Editor to load the CW
parameters into VFO A and USB parameters into VFO B in 5 consecutive
memory channels. Those 5 are "ganged together" with an "*" in the name,
IIRC.

When I rotate the Big Knob, I expected the VFO's to rotate through the
channels [end-around]. VFO A does, but VFO B does not follow, it
remains on whatever channel I originally selected.

The sequence M>V, Select memory, M>V sets both VFO's to the parameters
stored in that memory, as one would expect. Selecting a new memory with
the BK should load the parameters for that memory into both VFO's, or so
it would seem. It does for VFO A. It doesn't for VFO B. My question
was, "Is this a bug or intentional behavior?" If it's intentional, I'd
be curious what the use case is for that behavior. I'm also aware this
is a K3 question and likely to get lost in all the K4 commotion.

73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

On 6/3/2019 4:13 PM, K8TE wrote:

> While you can scan or dial through VFO A, once you "land" on a particular
> channel, the VFO B frequency and mode associated with that channel is
> available by using the VFO A/B button.
>
> I originally loaded the 60m CW frequencies in VFO A for my 60m channels
> since I'm more likely to use them working SOTA activators. However, I
> usually scan the SSB channels. Thus, I swapped between VFO A and B so I can
> scan USB channels and select the appropriate VFO B CW channels when needed.
> This comes in handy when someone suggests 60m for USB or when I see a SOTA
> dude spotted on 60m CW.
>
> 73, Bill, K8TE, waiting "patiently" to return home and start using HF again!
> BCNU at Ham-Com.
>

Don Wilhelm

Re: 60 meters

Fred and all,

I have observed what you found. On Channel Hopping, VFO A follows the
hop to the next channel, but VFO B does not.

While a "fix" may be coming sometime, it is not likely to be coming
soon. So I propose a workaround.

The simple solution is to set 10 channel hopping memories instead of
only 5. 5 for SSB/DATA and 5 more for CW. I doubt that you are using
all 100 memory slots in the K3.

Arrange them any way you want - each CW memory next to the SSB memory,
or go through all 5 SSB memories and then the next 5 are CW. Put some
identifier in the label so you can see which is which without referring
to the frequency.

73,
Don W3FPR

On 6/4/2019 3:02 PM, Fred Jensen wrote:

> This began as a simple question, I can't understand why it is so hard to
> explain: K3 frequency memories hold frequency, mode, and DSP BW for
> both VFO A and VFO B. I used the K3 Frequency Editor to load the CW
> parameters into VFO A and USB parameters into VFO B in 5 consecutive
> memory channels. Those 5 are "ganged together" with an "*" in the name,
> IIRC.
>
> When I rotate the Big Knob, I expected the VFO's to rotate through the
> channels [end-around]. VFO A does, but VFO B does not follow, it
> remains on whatever channel I originally selected.
>

Wes Stewart-2

Re: 60 meters

I do what Don suggests. That said, I think if you do an A/B it will fix your
problem, if I understand it correctly.

Wes N7WS

On 6/4/2019 4:21 PM, Don Wilhelm wrote:

> Fred and all,
>
> I have observed what you found. On Channel Hopping, VFO A follows the hop to
> the next channel, but VFO B does not.
>
> While a "fix" may be coming sometime, it is not likely to be coming soon. So
> I propose a workaround.
>
> The simple solution is to set 10 channel hopping memories instead of only 5.
> 5 for SSB/DATA and 5 more for CW. I doubt that you are using all 100 memory
> slots in the K3.
>
> Arrange them any way you want - each CW memory next to the SSB memory, or go
> through all 5 SSB memories and then the next 5 are CW. Put some identifier in
> the label so you can see which is which without referring to the frequency.
>
> 73,
> Don W3FPR
>
> On 6/4/2019 3:02 PM, Fred Jensen wrote:
>> This began as a simple question, I can't understand why it is so hard to
>> explain: K3 frequency memories hold frequency, mode, and DSP BW for both VFO
>> A and VFO B. I used the K3 Frequency Editor to load the CW parameters into
>> VFO A and USB parameters into VFO B in 5 consecutive memory channels. Those
>> 5 are "ganged together" with an "*" in the name, IIRC.
>>
>> When I rotate the Big Knob, I expected the VFO's to rotate through the
>> channels [end-around]. VFO A does, but VFO B does not follow, it remains on
>> whatever channel I originally selected.

k6dgw

Re: 60 meters

That doesn't work Wes, the problem is simpler than that. However, Don
has confirmed the behavior, and now it's time for me to be a "Real Ham"
and do something here in NE Sparks NV [instead of on the list] to fix
"my" problem. Don's [and one other's] solution with 10 memories is a
first-run candidate. Since I haven't been on SSB in years, ignoring what
happens to VFO B may be an answer too. [:-)

73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

On 6/4/2019 4:31 PM, Wes wrote:

> I do what Don suggests. That said, I think if you do an A/B it will
> fix your problem, if I understand it correctly.
>
> Wes N7WS
>
> On 6/4/2019 4:21 PM, Don Wilhelm wrote:
>> Fred and all,
>>
>> I have observed what you found. On Channel Hopping, VFO A follows
>> the hop to the next channel, but VFO B does not.
>>
>> While a "fix" may be coming sometime, it is not likely to be coming
>> soon. So I propose a workaround.
>>
>> The simple solution is to set 10 channel hopping memories instead of
>> only 5. 5 for SSB/DATA and 5 more for CW. I doubt that you are
>> using all 100 memory slots in the K3.
>>
>> Arrange them any way you want - each CW memory next to the SSB
>> memory, or go through all 5 SSB memories and then the next 5 are CW.
>> Put some identifier in the label so you can see which is which
>> without referring to the frequency.
>>
>> 73,
>> Don W3FPR
>>
>> On 6/4/2019 3:02 PM, Fred Jensen wrote:
>>> This began as a simple question, I can't understand why it is so
>>> hard to explain: K3 frequency memories hold frequency, mode, and
>>> DSP BW for both VFO A and VFO B. I used the K3 Frequency Editor to
>>> load the CW parameters into VFO A and USB parameters into VFO B in 5
>>> consecutive memory channels. Those 5 are "ganged together" with an
>>> "*" in the name, IIRC.
>>>
>>> When I rotate the Big Knob, I expected the VFO's to rotate through
>>> the channels [end-around]. VFO A does, but VFO B does not follow,
>>> it remains on whatever channel I originally selected.
>

Don Wilhelm

Re: 60 meters

The other easy solution is to use only 5 channel hopping memories and
create a Macro to move the VFO A up or down 1.5kHz depending on whether
you stored SSB or CW frequencies in VFO A. The frequency shift is
constant for all channels, so one Macro will do for all channels.
Assign the Macro to a PF button.

73,
Don W3FPR

On 6/4/2019 7:52 PM, Fred Jensen wrote:
> That doesn't work Wes, the problem is simpler than that. However, Don
> has confirmed the behavior, and now it's time for me to be a "Real Ham"
> and do something here in NE Sparks NV [instead of on the list] to fix
> "my" problem. Don's [and one other's] solution with 10 memories is a
> first-run candidate. Since I haven't been on SSB in years, ignoring what
> happens to VFO B may be an answer too. [:-)
>
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Elecraft mailing list

Re: 60 meters

The second suggestion by Don sounds like it would be "more fun" and not take up an additional five memories.

BobKA2TQV On Tuesday, June 4, 2019, 8:22:28 PM EDT, Don Wilhelm <[hidden email]> wrote:

The other easy solution is to use only 5 channel hopping memories and
create a Macro to move the VFO A up or down 1.5kHz depending on whether
you stored SSB or CW frequencies in VFO A. The frequency shift is
constant for all channels, so one Macro will do for all channels.
Assign the Macro to a PF button.

73,
Don W3FPR

On 6/4/2019 7:52 PM, Fred Jensen wrote:
> That doesn't work Wes, the problem is simpler than that. However, Don
> has confirmed the behavior, and now it's time for me to be a "Real Ham"
> and do something here in NE Sparks NV [instead of on the list] to fix
> "my" problem. Don's [and one other's] solution with 10 memories is a
> first-run candidate. Since I haven't been on SSB in years, ignoring what
> happens to VFO B may be an answer too. [:-)
>
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]