[Elecraft] Using K3 (or KX3) Macros for custom SPLIT functions

[Ian White]

Yup, I well remember the day when Wayne announced the macro facility -
and a very fine day that was! From that day, I have used a personalized
SPLIT macro that sets the K3 up just right from a single button-press,
and avoids all risk of appearing on the wrong frequency or seeing that
SPLIT N/A message [1].

The problem is that a Smart Split (or Safe Split) macro is not
assignable to the SPLIT button itself - instead, the SPLIT button become
something to *avoid*.  If there was an option to assign a special
user-defined macro to the SPLIT button (using one of the many available
examples) then the K3's SPLIT control would instantly become "best in
its class".

Moving on to Wayne's question about any missing points in his original
example, the main point is that when the KRX3 is installed, "A>B, A>B"
will also change many other parameters in the sub-rx. That may not be
what every user needs. For example, the main RX (VFO A) generally needs
to be optimized to listen for a weak DXpedition station, while the
sub-rx is tuning a pileup of very strong signals using VFOB. There are a
number of workarounds for that, but those macros will obviously be more
complex than Wayne's original "day 1" example.


[1] If anyone doesn't understand the urge to make the K3 do things
quickly, automatically and with minimum risk...  I am a DXer, a
contester and one of those "race tuners" who spend a lot of time
optimizing the performance and efficiency of our stations. We do this so
that on "race days" - in contest or DX pileups - we won't have to waste
any time or attention on unnecessary complications like pressing 6
different buttons in the correct sequence. Why? Because on "race days"
there are far more important things to do. 


73 from Ian GM3SEK


>-----Original Message-----
>From: Wayne Burdick [mailto:n6kr at elecraft.com]
>Sent: 03 October 2014 17:49
>To: Joe Subich, W4TV
>Cc: Ian White
>Subject: Re: Using K3 (or KX3) Macros for custom SPLIT functions
>
>A>B twice sets mode B equal to mode A, so what am I missing?
>
>On Oct 3, 2014, at 9:43 AM, "Joe Subich, W4TV" <lists at subich.com>
wrote:
>
>>
>> That doesn't address the issue of resetting the VFO B mode when
>> pressing split (or when an external program commands split) if the
>> modes are different e.g., SSB vs. DATA or CW vs. DATA or the VFOs
>> are on different bands (VFO IND = YES).
>>
>> 73,
>>
>>   ... Joe, W4TV
>>
>>
>> On 2014-10-03 11:04 AM, Wayne Burdick wrote:
>>> For those who may have missed this when I first described it--
>>>
>>> * * *
>>>
>>> In a recent discussion about SPLIT, many proposals were made (too
>>> many :)  Others argued for no change.
>>>
>>> With this in mind, we've created a new "switch macro" feature. It
>>> allows you to create your own variation on SPLIT -- or any other
radio
>>> function -- and execute it with a single switch press. In effect,
>>> you'll be creating your own custom firmware for the K3 that
automates
>>> control sequences you use most.
>>>
>>> Example #1 (SPLIT+2):
>>>
>>>    A>B
>>>    A>B
>>>    SPLIT
>>>    VFO B up 2
>>>    RIT and XIT off
>>>
>>> Example #2 (WEAKSIG):
>>>
>>>    Sub ON
>>>    Diversity mode
>>>    main/sub preamps on
>>>    200-Hz bandwidth
>>>    center passband
>>>
>>> Many other combinations are possible, limited only by the K3's
remote-
>>> control command set and the macro length limit (presently 56 bytes).
>>> You'll be able to set VFO frequencies or RIT/XIT offsets, adjust
gain
>>> or filter controls, and virtually "tap" or "hold" nearly any control
>>> on the radio.
>>>
>>> First, you enter a sequence of K3 control commands into one or more
>>> macros using K3 Utility, which can store them in the K3's EEPROM.
>>> Next, you assign the macros to any of the K3's 10 programmable
>>> function switches (PF1, PF2, M1-M4 tap, or M1-M4 hold) using the new
>>> MACRO menu entry.
>>>
>>> After that, activating the switch will perform the desired
functions,
>>> and the name of the macro will flash on VFO B as a reminder (e.g.,
>>> "SPLIT+2").
>>>
>>> * * *
>>>
>>> Many K3 (and KX3) owners are using such macros to obtain exactly the
>splits that they prefer.
>>>
>>> 73,
>>> Wayne
>>> N6KR
>>>
>>>
>>>
>>>