Split operation - display of Transmit frequency on keydown

[Brendan Minish]

In my opinion the K3 already does a more than adequate job of indicating
split.

The Delta LED is Eye catching enough. Mind you my P3 is to the left of
My K3 thus the LED certainly within my eye-line when operating.
However from the point of view of a standalone radio it might make
better sense if the Delta LED was just to the right of the main display,
but I am sure there are good design reasons why this is not the case.

Fundamentally however we have an operating problem, far too many jump
straight into a pileup without first listening to see what is happening.
Taking a little time to listen first always pays dividends in terms of
working the dx and lessens the chance of footshooting.

If I was to suggest one change it would be for an option to prevent the
Delta LED coming on when small amounts or RIT/XIT are applied, Even 1 Hz
of RIT or XIT applied activates it, thus training the operator to pay
less attention to the Yellow LED.
Perhaps an option to only enable the Delta LED when the TX/RX offset is
greater than 200Hz or 500Hz ?

In IT we have a technical term for a certain type of problem that
involves the operator, it's PEBKAC (Problem Exists Between Keyboard And
Chair  )
I too have occasionally been the problem in pileups but it's my fault,
it's PEBKAC and not the fault of the radio.


73
Brendan
EI6IZ
______________________________________________________________
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]

[K9QJS]

I’m not sure why I feel compelled to contribute to his thread when I am, in general, more the reader than the contributor.   Perhaps it is because I was deathly afraid of being called a L** while trying to work Navassa.  

In any event, on the topic of split display, feedback, I make the following observation.     I really don’t need to know when I am in split (bare with me), I need to know that I am not in split when I should be.   Wayne - I’m not sure how you would code for this one.  

Only once was I in split when I should not have been, and nobody complained.  

Hoop
K9QJS


______________________________________________________________
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]

[QUENTIN COLLIER]

And in order to make the user interface properly user friendly, we could have a CONFIG item to set the shock voltage so that the operator suffers unbearable pain rather than death.... :-)




73, Quin G3WRR



________________________________
 From: Mitch Wolfson DJØQN <[hidden email]>
To: "Joe Subich, W4TV" <[hidden email]>; [hidden email]
Sent: Wednesday, 18 February 2015, 11:21
Subject: Re: [Elecraft] Split operation - display of Transmit frequency on keydown
 

Joe, that is a great idea, but it doesn't go far enough. Some users might switch off the test mode on purpose. In this case, the K3 should induce an electric shock. Add some voice recognition software, so that when the user says "UP" in simplex mode, the K3 self-destructs.  ;-)

73,
Mitcn DJ0QN

Mitch Wolfson
DJØQN / K7DX
Neubiberger Str. 21, 85640 Putzbrunn
Skype: mitchwo - Home:[phone] - Mobile:[phone]
Echolink: 3001 - IRLP: 5378

On 18.02.2015 02:00, Joe Subich, W4TV wrote:

>
> Looking for the *absence* of a change when the PTT is pressed or the
> key is tapped to indicate that one has forgotten to engage split is a
> bit counter intuitive.  The *three* current indicators that split is
> engaged *before* entering transmit are the logical UI.
>
> Perhaps the better solution is to ask the logging software authors to
> determine when VFO A is tuned to a frequency spotted as split and
> select TEST MODE if split is not engaged or both VFOs are on the same
> frequency <G>!   Maybe a lack of output will be sufficient "immediate
> feedback".
>
> 73,
>
>    ... Joe, W4TV
>
>
> On 2015-02-17 7:38 PM, Wayne Burdick wrote:
>> Or, we could replace the *entire* VFO A display with the word "SPLIT" during key-down. This would be even more obvious, and it wouldn't mess up the VFO B display. VFO B is what you care about during split TX.
>>
>> Wayne
>

______________________________________________________________
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]

[Laurent F6DEX]

HI Wayne

Anyway, a useful indication could be the split (i.e +1.50) offset instead of the VFO B frequency (user choice based on the DISP status).  This is rarely done by manufacturers (I know the TS-990 which does this) but this is very useful in practice and avoids mental calculations.

73, Laurent F6DEX