[Elecraft] Feature request

[W0MU Mike Fatchett]

The B vfo is not locked.  You can still move it.

Having the 2nd receiver in the K3 makes it easier.

Believe it or not many users do not have the 2nd receiver.

I rarely ever use it for CW. Since the splits are normally just a few KC's.
I use XIT and RIT since I can't split A and B in my headphones, yet. 


"A slip of the foot you may soon recover, but a slip of the tongue you may
never get over." Ben Franklin
-----Original Message-----
From: elecraft-bounces at mailman.qth.net
[mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Jim Brassell
Sent: Monday, February 16, 2009 10:45 AM
To: elecraft at mailman.qth.net
Subject: Re: [Elecraft] Feature request

I've got to go along with Joe on this.  The way I do split on an FT2000 now
and all the radios I've used in the past is to set VFO B to VFO A's
frequency (the DX frequency), select SPLIT, put VFO B's receiver in either
my left or right ear, tune VFO B to the last guy the DX worked, and start my
calling there.  I truly don't understand the advantage of an automatic
split.  If you are not transmitting where the DX is listening, you will be a
long time working him.  And what if he is down 5, not up 1?

73,

Jim, K4ZMV


----- Original Message -----
From: "Joe Subich, W4TV" <lists at subich.com>
To: "'Ian White GM3SEK'" <gm3sek at ifwtech.co.uk>; <elecraft at mailman.qth.net>
Sent: Monday, February 16, 2009 11:17 AM
Subject: Re: [Elecraft] Feature request


>
> I have to disagree ... quick split would cause too may
> other problems like losing the frequency if one has
> already set VFO B (subreciever) to the desired place.
>
> Except for actions explicitly designed to change frequency
> (tune the VFO, change band, recall a memory, etc.), the user
> interface should never change the frequency and it should
> never change the frequency of the "other" VFO.
>
> Any "Quick split" function should require an explicit
> input sequence ... perhaps "Freq Enter, Split" or "XIT,
> set the offset, Split" ... but the current Split
> function should not be overloaded with "quick split."
>
> Even if "Quick Split" were a menu option for "Split,"
> the time to through the menu to change the function
> would be greater than the current multiple keystroke
> method of setting a specific split.  Since not every
> "split" is the same (5 to 25 KHz on phone vs. 1 to 5
> on CW in most cases) is useful only on one mode and
> only if the preset value happens to match the other
> station's offset.
>
> 73,
>
>   ... Joe, W4TV
>
>
>
>> -----Original Message-----
>> From: elecraft-bounces at mailman.qth.net
>> [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Ian
>> White GM3SEK
>> Sent: Monday, February 16, 2009 3:28 AM
>> To: elecraft at mailman.qth.net
>> Subject: Re: [Elecraft] Feature request
>>
>>
>> W0FK wrote:
>> >
>> >Having a "quick split" feature would be great! My IC-7800
>> has that, and
>> >I miss it on the K3. Hold split, enter the "up" split
>> frequency (up 1,
>> >up 5, etc.) and the seconnd VFO is there. No counting or adding.
>> >
>>
>> "Quick split" - otherwise known as "auto split" or "pileup
>> split" - is
>> an option that has been available in serious transceivers for almost
>> twenty years.
>>
>> If this option was available and selected, then holding SPLIT would
>> automate the following sequence which presently has to be
>> done manually:
>>
>> 1. Double-tap A>B (reset VFO B, and sub-rx if present, to a
>> known state)
>>
>> 2. Hold SPLIT.
>>
>> 3. Tune VFO B away from VFO A by a selected amount (+/- in
>> 1kHz steps,
>> either by pre-selection or 'on the fly' - but the latter
>> would require
>> extensive error trapping).
>>
>> 4. Turn sub-rx on (if it wasn't already on).
>>
>> 5. Disable TX on VFO A frequency until SPLIT is canceled
>> (error trapping
>> for the A/B, REV and A>B buttons).
>>
>> At present this whole sequence relies on the operator doing all the
>> right things, and then continuing not to do any wrong things.  Errors
>> are punished by major embarrassment (literally, world-class).
>>
>> Nevertheless, this function should only be an OPTION. It will not be
>> needed by anyone who never works a pileup, is never in a hurry and/or
>> never makes a mistake.
>>
>>
>>
>> -- 
>>
>> 73 from Ian GM3SEK
>> ______________________________________________________________
>> 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
> 

______________________________________________________________
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