[Elecraft] [Elecraft_K3] Who said anything about removing diversity? That would *never* happen...

[Joe Subich, W4TV]

> In my 43 years of ham radio operating, I can only think of one
> situation where I wanted to LINK my TX and RX VFOs: Early AMSAT OSCAR
> satellites with linear cross-band transponders.

Except most of the linear transponders are frequency inverting (to
minimize the effect of doppler) and what's needed there is to tune
the two VFOs (rigs) in *opposite* directions <G>.

73,

    ... Joe, W4TV


On 2015-02-17 4:31 PM, Terry Posey wrote:
> The list "din" over relocating the VFO LINK function off of the SUB RX
> button seems to have subsided...  The following comments are about LINK, and
> not about the fabulous DIVERSITY function:
>
> I am VERY pleased that Elecraft has relocated the VFO LINK function off of
> the SUB button.  Accidental LINK of VFO A/B during at least three major
> DXpeditions has been a serious problem, which has probably cost numerous
> DXpedition QSOs.  During the heat of DXpedition operations, it is very easy
> for even a well-seasoned K3 operator to get the critical hold timing on the
> SUB button wrong enough to enable LINK.  Then as the DXpedition operator
> tunes his SPLIT QSX frequency looking for callers, his own TX frequency
> moves up and down the band in step per the command of VFO LINK.  The pileup
> becomes totally confused, the QSO rate goes to ZERO, and the DXpedition op
> does not realize what is happening.  Most DXpedition ops are looking at
> their QSX pileup frequency, not at their TX frequency, and the little
> blinking decimal point is unnoticed.
>
> I have mulled over this K3  LINK function for quite some time.  In my 43
> years of ham radio operating, I can only think of one situation where I
> wanted to LINK my TX and RX VFOs:  Early AMSAT OSCAR satellites with linear
> cross-band transponders.  But, for those who can find a need for LINK, I am
> glad that Elecraft has retained that functionality - just not on the SUB
> button
>
> 73,
> Terry K4RX
>