[Elecraft] K3 option request

[Guy Olinger K2AV]

Hmm,

Anybody try these things out first?

Double tap  A>B.  Hold <SPLIT>.  Tap XIT.  Current XIT setting
displays briefly.  Change XIT to split offset desired.  While turning
R/XIT knob the offset (e.g. +2.00) displays.  When the knob ceases
turning, the VFO B reverts to the transmitting frequency (RX+offset)
and VFO A shows the receiving frequency.  If you have the subRX and
have <SUB> on you can listen to both RX and TX frequency.

Use that when what you have is the offset from the spot.

If you have the actual frequency specified on the spot, turn off XIT
and tune VFO B to the specified frequency.

What am I missing?

73, Guy.

On Sun, Apr 11, 2010 at 12:29 PM, Ted Roycraft <w2zk at comcast.net> wrote:
> Well LS, if  "the K3 is already setup _ideally_ for working split", as
> you say, then case closed.  Forget I said anything.
>
> By the way, I'm not in a hurry to hit the key.  I can also do arithmetic
> in my head.  As I said, it gives you a different perspective on the
> environment around the DX.  If your argument is that this option is
> useless don't use it but let's listen to user comments.  So far, there
> have been more positive ones than negative ones and most of the negative
> ones have been from the same person. Remember, it would be OPTIONAL.  As
> for Elecraft resources, I would rather hear from the Elecraft people on
> that rather than from you.  You might be right but only Elecraft can say
> whether this option would cost more development time and resources than
> other implemented options of equal or lesser value.
>
> I personally don't use VFO B very much except for working split and I
> would find this option useful - not essential but useful.  I proposed
> this option to start a discussion.  Please don't shoot it down just
> because you wouldn't use it.  There have been many many options proposed
> for the K3 that I wouldn't find useful but others would and I haven't
> weighed in to try and shoot them down just because I wouldn't use them.
> We get it - you won't use it.  It's a danger to world peace.  Thanks.
>
> 73, Ted, W2ZK
>
> On 4/11/2010 12:02 PM, lstavenhagen wrote:
>>
>>> everyone has their own
>>>
>> style and this option would just support that.  All I'm suggesting is
>> that this be an option.  No one would force you to use it.<
>>
>> But there's a cost - additional complexity to the K3 feature set. I submit
>> that you'd only want to do this if there's a compelling reason to do so.
>> Simply adding a feature with little or no demonstrable use is not something
>> I'd personally want to pester elecraft to do.
>> Again, the K3 is already setup _ideally_ for working split (and I assume
>> also with the sub RX installed) so I just don't see what value this adds
>> (relative to the cost).
>>
>>
>>> It's ridiculous to say that this would create QRM.  We definitely want to
>>>
>> keep those pileups pristine and without QRM and I would never suggest
>> anything that would do that!<
>>
>> Well lemme put it another way - If you're in that much of a hurry to hit the
>> key that you're unable or unwilling to do simple math on the buffer
>> contents, you probably havn't done the necessary footwork of listening to
>> start with. Instead, you're probably more likely to simply be adding QRM
>> than you are to actually make the QSO. These folks are easy to pick out in
>> the pile; they're 20 over 9 at least and endlessly call and call. Note that
>> the DX takes a while to get back to them if they answer them at all. The
>> chances are good the DX is using a K3 and, since the KW's are off his RX
>> freq. he can't hear them anyway hi hi.
>>
>> 73,
>> LS
>> W5QD
>>
>
> ______________________________________________________________
> 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
>