[Elecraft] [K3] more function keys please

[Ian White GM3SEK]

Wayne Burdick wrote:
>The main application I had in mind for this was various splits. The
>macros would all be the same, but VFO B might be moved up 1 kHz by
>doing PF1+1, up 2 with PF1+2, etc.
>

Macros requiring multiple key-presses will be fine for some functions, 
but please let's remember that others need to be quick!  In the case of 
"quick split", it's in the name.

For the past week I have been trying out an all-purpose quick split 
macro which covers all the relevant modes  - SSB, CW and data - with 
just one macro key. At present I have it assigned to M1-tap (close to 
the existing SPLIT control) and it does almost everything I need.

QIK-SPL
LN0;RT0;XT0;SWT13;SWT13;SWH58;SWT11;SWT11;FT1;UPB6;SB1;

The initial split value is a simple compromise: UPB6 is +3kHz on all 
modes. Any split can only be an initial value, a place to start tuning 
away from, but always the most important thing is to shift the TX VFO 
off the DX frequency!  On SSB you then tune upward into the pileup, 
while on CW or data you would generally start tuning downwards. People 
who favor SSB more than the other two modes might wish to program +5kHz 
as an initial split.

This isn't perfect but - at least, for me  - it works far better than 
having to remember different keys for different modes.

The same principle applies to the setup of the sub-RX passband. It isn't 
necessary to use a series of macros to select different bandwidths - 
this one macro selects your favorite passband settings for whichever 
mode you happen to be using. Those favorite settings  are the ones you 
already have stored as NORMAL for each mode, so they should also be good 
general-purpose settings for tuning a pileup [1]. The settings of the 
main RX are not affected.

Quick split is a highly personal function, and the beauty of the K3's 
macros is that now it really *can* be personalized.  But it does need to 
be quick!




[1] Recalling the NORMAL settings is done by the SWH58 command, which 
presently seems to have a minor glitch: the command immediately 
following is skipped and not executed. To get around this, the macro has 
two SWT11 commands where only one should actually be needed. When this 
issue is resolved, one of the SWT11 commands should be deleted.


-- 

73 from Ian GM3SEK
http://www.ifwtech.co.uk/g3sek