Workaround for providing automatic SSB < > CW VFO offset

[Ralph Parker]

>...VFO automatically offset... when switching between SSB and CW...
>On VHF and UHF, SSB and CW are used interchangeably...

Good work, Bill!
Non-6m ops don't quite understand the problem, complicated by the fact that
"normal" CW is on LSB, making us ex-Yaesu drivers crazy.
I've solved the offset problem for now by using my PRO III on 6m
(has the spectrum display, too :-)

VE7XF

______________________________________________________________
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

[Julian, G4ILO]

Ralph Parker wrote

Good work, Bill!
Non-6m ops don't quite understand the problem, complicated by the fact that
"normal" CW is on LSB, making us ex-Yaesu drivers crazy.

I often find myself wandering around the CW end of 20m in the wrong mode, then finding that I "lose" the station after switching to CW. So I don't understand why this is being discussed as of benefit only to VHF operators.

I have managed to implement the VFO shift when changing modes to/from CW in the next version of KComm.

[Bill VanAlstyne W5WVO]

I have discovered one "gotcha" in my workaround, and that is the inability to
lock the "B" VFO knob -- the KNOB, not the VFO -- because if you accidentally
touch it, you lose the 700 Hz offset. I've been training myself not to touch it,
but it would be nice if there was a way to lock it down so it wouldn't do
anything. Removing the knob and epoxying the shaft seems a little extreme. ;-)
Perhaps a function that does this could be implemented that could be invoked
from one of the PF function buttons.

Of course, all of this is moot if the VFO mode-switching behavior gets fixed so
it works correctly in the first place. I have faith that Wayne will eventually
get to it. But the Elecraft folk do tend to respond to the squeakiest wheel
first, so if this behavior is at all important to you, please let Wayne know.
Otherwise he will continue to think I'm the only nutcase who cares about it. :-)

While we're on the subject -- Is there anyone else here besides me who thinks
that the "normal" CW tuning behavior should reflect the default SSB sideband for
a given frequency band? In other words, instead of always tuning like LSB, the
"CW" mode would tune like LSB on 160, 80, and 40, and would tune like USB on all
other bands. "CW REV" would reverse this default correlation. Seems more
intuitive to me than the way it is now.

Bill W5WVO


Julian, G4ILO wrote:

> Ralph Parker wrote:
>>
>> Good work, Bill!
>> Non-6m ops don't quite understand the problem, complicated by the
>> fact that
>> "normal" CW is on LSB, making us ex-Yaesu drivers crazy.
>>
> I often find myself wandering around the CW end of 20m in the wrong
> mode, then finding that I "lose" the station after switching to CW.
> So I don't understand why this is being discussed as of benefit only
> to VHF operators.
>
> I have managed to implement the VFO shift when changing modes to/from
> CW in the next version of KComm.
>
> -----
> Julian, G4ILO. K2 #392  K3 #222.
> * G4ILO's Shack - http://www.g4ilo.com
> * KComm - http://www.g4ilo.com/kcomm.html
> * KTune - http://www.g4ilo.com/ktune.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

[Don Wilhelm-4]

Bill,

I for one have to disagree with you on the CW sideband item.
 From day one of my hamming days, I have always wanted CW to tune so the
higher pitches were higher in frequency than lower pitched signals
(blame that on my early elmer).  So I have come to relate the audio
pitch to the relative frequency - which means LSB CW for all bands.

Yes, I know SSB is different, but SSB is different than CW.

73,
Don W3FPR

Bill W5WVO wrote:

> I have discovered one "gotcha" in my workaround, and that is the inability to
> lock the "B" VFO knob -- the KNOB, not the VFO -- because if you accidentally
> touch it, you lose the 700 Hz offset. I've been training myself not to touch it,
> but it would be nice if there was a way to lock it down so it wouldn't do
> anything. Removing the knob and epoxying the shaft seems a little extreme. ;-)
> Perhaps a function that does this could be implemented that could be invoked
> from one of the PF function buttons.
>
> Of course, all of this is moot if the VFO mode-switching behavior gets fixed so
> it works correctly in the first place. I have faith that Wayne will eventually
> get to it. But the Elecraft folk do tend to respond to the squeakiest wheel
> first, so if this behavior is at all important to you, please let Wayne know.
> Otherwise he will continue to think I'm the only nutcase who cares about it. :-)
>
> While we're on the subject -- Is there anyone else here besides me who thinks
> that the "normal" CW tuning behavior should reflect the default SSB sideband for
> a given frequency band? In other words, instead of always tuning like LSB, the
> "CW" mode would tune like LSB on 160, 80, and 40, and would tune like USB on all
> other bands. "CW REV" would reverse this default correlation. Seems more
> intuitive to me than the way it is now.
>
> Bill W5WVO
>
>
> Julian, G4ILO wrote:
>  
>> Ralph Parker wrote:
>>    
>>> Good work, Bill!
>>> Non-6m ops don't quite understand the problem, complicated by the
>>> fact that
>>> "normal" CW is on LSB, making us ex-Yaesu drivers crazy.
>>>
>>>      
>> I often find myself wandering around the CW end of 20m in the wrong
>> mode, then finding that I "lose" the station after switching to CW.
>> So I don't understand why this is being discussed as of benefit only
>> to VHF operators.
>>
>> I have managed to implement the VFO shift when changing modes to/from
>> CW in the next version of KComm.
>>
>> -----
>> Julian, G4ILO. K2 #392  K3 #222.
>> * G4ILO's Shack - http://www.g4ilo.com
>> * KComm - http://www.g4ilo.com/kcomm.html
>> * KTune - http://www.g4ilo.com/ktune.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
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.339 / Virus Database: 270.12.65/2171 - Release Date: 06/12/09 05:55: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

[W7GJ, Lance]

Bill W5WVO wrote:

> I have discovered one "gotcha" in my workaround, and that is the inability to
> lock the "B" VFO knob -- the KNOB, not the VFO -- because if you accidentally
> touch it, you lose the 700 Hz offset. I've been training myself not to touch it,
> but it would be nice if there was a way to lock it down so it wouldn't do
> anything. Removing the knob and epoxying the shaft seems a little extreme. ;-)
> Perhaps a function that does this could be implemented that could be invoked
> from one of the PF function buttons.
>
> Of course, all of this is moot if the VFO mode-switching behavior gets fixed so
> it works correctly in the first place. I have faith that Wayne will eventually
> get to it. But the Elecraft folk do tend to respond to the squeakiest wheel
> first, so if this behavior is at all important to you, please let Wayne know.
> Otherwise he will continue to think I'm the only nutcase who cares about it. :-)
>
> While we're on the subject -- Is there anyone else here besides me who thinks
> that the "normal" CW tuning behavior should reflect the default SSB sideband for
> a given frequency band? In other words, instead of always tuning like LSB, the
> "CW" mode would tune like LSB on 160, 80, and 40, and would tune like USB on all
> other bands. "CW REV" would reverse this default correlation. Seems more
> intuitive to me than the way it is now.
>
> Bill W5WVO
>
>
> Julian, G4ILO wrote:
>> Ralph Parker wrote:
>>> Good work, Bill!
>>> Non-6m ops don't quite understand the problem, complicated by the
>>> fact that
>>> "normal" CW is on LSB, making us ex-Yaesu drivers crazy.
>>>
>> I often find myself wandering around the CW end of 20m in the wrong
>> mode, then finding that I "lose" the station after switching to CW.
>> So I don't understand why this is being discussed as of benefit only
>> to VHF operators.
>>
>> I have managed to implement the VFO shift when changing modes to/from
>> CW in the next version of KComm.
>>
>> -----
>> Julian, G4ILO. K2 #392  K3 #222.
>> * G4ILO's Shack - http://www.g4ilo.com
>> * KComm - http://www.g4ilo.com/kcomm.html
>> * KTune - http://www.g4ilo.com/ktune.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
>
>

Hello Bill,

I am with you on needing a way to be able to switch back and forth from CW to USB on
6m, and I also use CW-R for this.  However, I like to keep my B VFO free for other
things - like quickly QSYing off the calling frequency by just switching to the other
VFO.  I think the neat way to switch to CW and back to SSB again would be to somehow
define your steps as a macro and program it into some hot key so you could
automatically do all the steps quickly and without error by just pressing a single
button.  I don't know if this is possible with the K3, but I imagine that it is.

While we are on the subject, I still would like to see use footswitch operators be
able to send CW to SSB operators, like the VOX people do ;-)

VY 73, Lance

--
Lance Collister, W7GJ (ex: WN3GPL, WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8)
P.O. Box 73
Frenchtown, MT  59834  USA
QTH: DN27UB
TEL: [phone]
URL: http://www.bigskyspaces.com/w7gj
2m DXCC #11/6m DXCC #815


______________________________________________________________
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

[wayne burdick]

Bill, you can lock VFO B by going into BSET mode, then holding LOCK. If
the VFOs are linked, this preserves VFO B tracking.

73,
Wayne
N6KR

On Jun 12, 2009, at 3:57 PM, Bill W5WVO wrote:

> I have discovered one "gotcha" in my workaround, and that is the
> inability to
> lock the "B" VFO knob -- the KNOB, not the VFO -- because if you
> accidentally
> touch it, you lose the 700 Hz offset. I've been training myself not to
> touch it,
> but it would be nice if there was a way to lock it down so it wouldn't
> do
> anything.

---

http://www.elecraft.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

[Bill VanAlstyne W5WVO]

Wayne,

This is why I emphasized the KNOB, not the VFO. When you swap VFOs A and B by
pressing the A/B button, the locked status follows what was originally VFO B and
now becomes VFO A. What we want here is for the VFO B KNOB (i.e., the middle
one) to stay locked, regardless of which VFO frequency it is controlling,
because moving it changes the 700 Hz offset when VFO B is not locked. If the
locked status didn't follow the frequency from VFO B to VFO A, it would work to
prevent accidentally corrupting the offset. However, that is clearly not the way
LOCK was designed to work.

Bill W5WVO


wayne burdick wrote:

> Bill, you can lock VFO B by going into BSET mode, then holding LOCK.
> If the VFOs are linked, this preserves VFO B tracking.
>
> 73,
> Wayne
> N6KR
>
> On Jun 12, 2009, at 3:57 PM, Bill W5WVO wrote:
>
>> I have discovered one "gotcha" in my workaround, and that is the
>> inability to
>> lock the "B" VFO knob -- the KNOB, not the VFO -- because if you
>> accidentally
>> touch it, you lose the 700 Hz offset. I've been training myself not
>> to touch it,
>> but it would be nice if there was a way to lock it down so it
>> wouldn't do
>> anything.
>
> ---
>
> http://www.elecraft.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

[wayne burdick]

Ah...QSL. Rather than fix this problem, I think I'll just endeavor to
add the desired pitch offset when switching modes, like you originally
wanted :)

73,
Wayne
N6KR

On Jun 12, 2009, at 6:16 PM, Bill W5WVO wrote:

> Wayne,
>
> This is why I emphasized the KNOB, not the VFO. When you swap VFOs A
> and B by pressing the A/B button, the locked status follows what was
> originally VFO B and now becomes VFO A. What we want here is for the
> VFO B KNOB (i.e., the middle one) to stay locked, regardless of which
> VFO frequency it is controlling, because moving it changes the 700 Hz
> offset when VFO B is not locked. If the locked status didn't follow
> the frequency from VFO B to VFO A, it would work to prevent
> accidentally corrupting the offset. However, that is clearly not the
> way LOCK was designed to work.
>
> Bill W5WVO
>
>
> wayne burdick wrote:
>> Bill, you can lock VFO B by going into BSET mode, then holding LOCK.
>> If the VFOs are linked, this preserves VFO B tracking.
>>
>> 73,
>> Wayne
>> N6KR
>>
>> On Jun 12, 2009, at 3:57 PM, Bill W5WVO wrote:
>>
>>> I have discovered one "gotcha" in my workaround, and that is the
>>> inability to
>>> lock the "B" VFO knob -- the KNOB, not the VFO -- because if you
>>> accidentally
>>> touch it, you lose the 700 Hz offset. I've been training myself not
>>> to touch it,
>>> but it would be nice if there was a way to lock it down so it
>>> wouldn't do
>>> anything.
>>
>> ---
>>
>> http://www.elecraft.com
>
>
>

---

http://www.elecraft.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

[Bill VanAlstyne W5WVO]

Excellent! :-)
Bill

wayne burdick wrote:

> Ah...QSL. Rather than fix this problem, I think I'll just endeavor to
> add the desired pitch offset when switching modes, like you originally
> wanted :)
>
> 73,
> Wayne
> N6KR
>
> On Jun 12, 2009, at 6:16 PM, Bill W5WVO wrote:
>
>> Wayne,
>>
>> This is why I emphasized the KNOB, not the VFO. When you swap VFOs A
>> and B by pressing the A/B button, the locked status follows what was
>> originally VFO B and now becomes VFO A. What we want here is for the
>> VFO B KNOB (i.e., the middle one) to stay locked, regardless of which
>> VFO frequency it is controlling, because moving it changes the 700 Hz
>> offset when VFO B is not locked. If the locked status didn't follow
>> the frequency from VFO B to VFO A, it would work to prevent
>> accidentally corrupting the offset. However, that is clearly not the
>> way LOCK was designed to work.
>>
>> Bill W5WVO
>>
>>
>> wayne burdick wrote:
>>> Bill, you can lock VFO B by going into BSET mode, then holding LOCK.
>>> If the VFOs are linked, this preserves VFO B tracking.
>>>
>>> 73,
>>> Wayne
>>> N6KR
>>>
>>> On Jun 12, 2009, at 3:57 PM, Bill W5WVO wrote:
>>>
>>>> I have discovered one "gotcha" in my workaround, and that is the
>>>> inability to
>>>> lock the "B" VFO knob -- the KNOB, not the VFO -- because if you
>>>> accidentally
>>>> touch it, you lose the 700 Hz offset. I've been training myself not
>>>> to touch it,
>>>> but it would be nice if there was a way to lock it down so it
>>>> wouldn't do
>>>> anything.
>>>
>>> ---
>>>
>>> http://www.elecraft.com
>>
>>
>>
>
> ---
>
> http://www.elecraft.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