[Elecraft] A way to show both "SPLIT" and "NON-SPLIT" warnings

[Vic Rosenthal]

I like this. Also changing the color on the P3 cursor when going into transmit, not just when selecting or deselecting SPLIT.

Vic 4X6GP/K2VCO 

> On Feb 19, 2015, at 9:33 AM, Wayne Burdick <n6kr at elecraft.com> wrote:
> 
> Useful analysis, Rich. I agree this might cause some confusion.
> 
> Here's a simpler variation. Suppose we give operators the option of briefly flashing the entire transmit VFO frequency off/on once each time you start keying? This would duplicate the intent of the "TX" arrow, which points to either "A" or "B" but is small enough to get lost unless you're looking right at it. No new semantics -- just a more visible TX VFO indication.
> 
> This wouldn't tell you whether you're in split mode. But flashing the A vs. B displays would look quite different to the eye, so you'd quickly get used to looking for the right one as confirmation of your intent.
> 
> Wayne
> N6KR
> 
>> On Feb 18, 2015, at 12:14 PM, Richard Ferch <ve3iay at storm.ca> wrote:
>> 
>> It's nice to see some recognition that the issue is not the same for people using two receivers as for people using a single receiver, but I am not sure how well the proposed solution will actually work in the two-receiver "sub-RX implied split" (or "reverse split") situation.
>> 
>> When I am using "sub-RX implied split", the K3's SPLIT indicator is off, because I am transmitting on VFO A. The proposed solution would show "NON.SPLT" on the VFO B display, which is not correct in this situation (I am actually operating split, listening on VFO B and transmitting on VFO A). If I manage somehow to leave my K3 in SPLIT mode with the DX in the subRX, I will be transmitting on the DX frequency but the VFO A display will show "SPLIT" even though in this case I am erroneously operating non-split.
>> 
>> I also operate SO2V in many contests, meaning that I have two logging windows open in my contest software, one for each VFO. If I choose to work someone non-split from the VFO B logging window, the software automatically puts the K3 into SPLIT mode in order to transmit on VFO B. The VFO A display would show "SPLIT" while I am transmitting, but actually I am not operating split.
>> 
>> The real problem is that the rig cannot read my mind. It has no way of knowing whether I am listening to the other station on the main RX or the subRX, hence whether I am actually operating split or non-split. My solution to this is to ignore the K3's display and never use the SPLIT button on the radio, i.e. to do all split- or VFO B-related operations from software. The software knows my intention because it gives me a way to tell it what I want to do, whereas until someone comes up with a mind-reading module, the radio cannot know my real intention.
>> 
>> 73,
>> Rich VE3KI