[Elecraft] Split not available

Sat Feb 12 11:19:42 EST 2011

While there may be some who on some rare occasions need VHF Cross-mode AND
Split at the same time, this is not a valid justification for the radio to
behave in the illogical way it does now. 

And, no, the VFOs should not be tied to each other all the time so changing
the VFO IND parameter is not the answer to this. There is also no need to
sync the VFOs when turning SPLIT OFF and that is not being suggested.

The current logic forces one to have to perform 3 completely unnecessary
steps to go to Split operation when VFOB is not on the same band/mode as
VFOA.  <<< This happens all the time!!!

Think about this: Is there any reason one would press and hold Split aside
from wanting the radio to be placed into SPLIT mode? I cannot imagine any
circumstance where you would deliberately press and hold SPLIT and not want
to go SPLIT.

Once again:  ***if VFOB is not on the same band/mode as VFOA***, and you
press and hold SPLIT [Step 1] (which clearly means you want to go SPLIT)
this should cause a VFOA-> VFOB and then turn on SPLIT all in one step.

The way it works now, is that when you try to do this, the radio will not do
anything but the VFOB display shows SPL/NA and you have to recognize that
this has happened [Step 2]. 

As it is now, when this happens, one has to then TAP VFOA->VFOB (STEP 3] to
make the VFOs the same, then Press and HOLD SPLIT (AGAIN) [Step 4] to go
SPLIT, and then set VFOB's frequency [Step 5]. You can then work the DX
[Step 6].

Again, ***IF and only IF VFOB is not on the same band/mode as VFOA***, here
are the 6 steps currently forced by this bad logic:

Step 1 - Press and Hold SPLIT
Step 2 - Recognize the SPL/NA message in the VFOB display
Step 3 - Tap VFO A - > VFO B
Step 4 - Press and Hold Split (Again)
Step 5 - Set the VFO B Frequency
Step 6 - Work the DX Station

There is no other way to do this ***if VFOB is not on the same band/mode as
VFOA***. 

The 3 extra steps, that the current logic forces are simply a waste of time.
If it worked the way I am hopeful it will someday, it would eliminate the
need to do Steps 2, 3, and 4.

Again: ***IF and only IF VFOB is not on the same band/mode as VFOA*** - it
would be like this:

Step 1 - Press and Hold SPLIT which also sets VFO A - > VFO B 
Step 2 - Set the VFO B Frequency
Step 3 - Work the DX Station

Much more efficient!

Again, when one presses and holds SPLIT, there is nothing else one could be
trying to do but to go SPLIT - if the VFOs must be on the same band to allow
that, then make them the same and turn on SPLIT, then dial up your VFOB
Frequency and work the DX!

73,

Bob W5OV

-----Original Message-----
From: Joe Subich, W4TV [mailto:lists at subich.com] 
Sent: Saturday, February 12, 2011 8:10 AM
To: Bob Naumann; Elecraft Reflector
Subject: Re: [Elecraft] Split not available

If VFO B is not on the same band, you are correct.  However, there
are plenty of times that one might want to use cross mode split -
it is quite common in VHF operation.

You can avoid the "VFO on the wrong band" issue simply by setting
CONFIG:VFO IND = No.  Therefore again, making the VFOs synchronize
VFOs as the default operation when turning split on/off is a bad
idea.  Quite simply, I regularly use VFO B as a quick memory and
have a PF key for B -> A to take advantage of that.  Your "Make
VFO B = VFO A" when turning spit on/off would completely destroy
that capability.

Anyone who wants VFOs to synchronize when turning split on or off
can easily write their own "quick split" macro (tap, tap, hold).
There are several examples of such a macro in the archives of this
list and probably an example in the Help files for the K3 Utility.

73,

    ... Joe, W4TV

On 2/12/2011 4:36 AM, Bob Naumann wrote:
> Joe,
>
> Again, ***if VFOB is not on the same band/mode as VFOA***, and you press
and
> hold SPLIT (which clearly means you want to go SPLIT) this should cause a
> VFOA->  VFOB and then turn on SPLIT.
>
> Please explain how this is a bad idea and under what circumstances this
> would cause a problem.
>
> 73,
>
> Bob W5OV
>
>
>
>
>
> -----Original Message-----
> From: Joe Subich, W4TV [mailto:lists at subich.com]
> Sent: Friday, February 11, 2011 10:15 PM
> To: w5ov at w5ov.com
> Cc: Shel Radin KF0UR; elecraft at mailman.qth.net
> Subject: Re: [Elecraft] Split not available
>
>
>> If the "Split" function were to include a A->B like I suggested
>> recently, this would not be an issue.
>   >
>   >  Some condemned this suggestion as a "bad" idea, but I doubt that they
>   >  operate much or they would know what a pain in the neck this is.
>
> No, I operate More than enough to know how much of a pain it would
> be if the VFOs were synchronized every time one turned split off -
> for example to move one VFO to a different pile-up.  Only to have
> lost the frequency saved in VFO B when returning to an original
> pile-up.
>
> Synchronizing VFOs every time the split status is changed is *still*
> a terrible idea but if you want to do that, you can use the K3 Macro
> capability to build your own "quick split" macro without causing
> inconvenience to others.
>
>   >  If VFO B is already on the same band and mode as VFO A, then just
turn
>   >  Split on.
>   >
>   >  I find that the second condition NEVER occurs.
>
> I find the second condition is almost always the case and if it isn't
> two quick presses of the Split button is all it takes.
>
> 73,
>
>      ... Joe, W4TV
>
>
> On 2/11/2011 11:30 AM, w5ov at w5ov.com wrote:
>> If the "Split" function were to include a A->B like I suggested recently,
>> this would not be an issue.
>>
>> Some condemned this suggestion as a "bad" idea, but I doubt that they
>> operate much or they would know what a pain in the neck this is.
>>
>> The logic should be:
>> When Holding Split: if VFO B is not already on the same band and mode,
>> then it should do a VFO A ->   VFO B, and then Split should be turned on.
>>
>> If VFO B is already on the same band and mode as VFO A, then just turn
>> Split on.
>>
>> I find that the second condition NEVER occurs.
>>
>> 73,
>>
>> Bob W5OV
>>
>>
>>
>>>
>>> Exactly.  I'm a new K3 owner (~1 week) and had the same issue a few days
>>> into
>>> ownership.    VFO B was in a mode other than DATA A.
>>>
>>> To prevent it from happening again, I added a double tap of A->B to my
> "go
>>> to RTTY"  macro, which copies the mode of VFO A to VFO B, so both VFOs
> are
>>> always the proper mode.
>>>
>>> GL&   73,
>>>
>>> Shel  KF0UR
>>> --
>>> View this message in context:
>>>
>
http://elecraft.365791.n2.nabble.com/Re-Split-not-available-tp6012850p601619
> 3.html
>>> Sent from the [K3] mailing list archive at Nabble.com.
>>> ______________________________________________________________
>>> Elecraft mailing list
>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft
>>> Help: http://mailman.qth.net/mmfaq.htm
>>> Post: mailto:Elecraft at mailman.qth.net
>>>
>>> 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:Elecraft at mailman.qth.net
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>>
>
>