[Elecraft] K3: activating sub receiver disables tx ?

ww2r2 at g4fre.com ww2r2 at g4fre.com
Tue Feb 17 13:15:28 EST 2009


Thanks to information from Charles Allen (who suffered the same issue) and
help from  Dale at elecraft,  the problem has now been identified as a subin
board production defect

The inductor (L3) that supples bias to switch the tx/rx pin diode to the tx
path on the board was not, and had never been fitted, hence drive doesnt get
switched to the tx path

The missing inductor is on its way from CA

The board was supplied with the subrx last november.  Wayne assures me all
subin boards are now 100% tested

Dave

ww2r




Message: 11
Date: Sat, 14 Feb 2009 02:09:47 -0500
From: ww2r2 at g4fre.com
Subject: [Elecraft] K3: activating sub receiver disables tx ?
To: elecraft at mailman.qth.net
Message-ID:
	<S359335AbZBNHJs/20090214070948Z+2601 at swip007.ftl.affinity.com>
Content-Type: text/plain; format=flowed; charset="iso-8859-1"

I wonder if anyone else has experienced the following? (and what the cure
was?)

In a k3 with atu xverter interface and subrx.

Ant 1 is selected

vfo a is set to cw mode and receives OK. Keying it shows rf output on the k3
power meter and the external power meter

vfo b is set to cw mode on the same band. Doing an a/b swap and it receives
OK, Keying it shows rf output on the k3 power meter and the external power
meter

if I activate split (rx a tx b) using the above settings, keying shows rf
output on the k3 power meter and the external power meter

however if I activate the subreceiver with split (still) enabled keying
shows NO rf output on the k3 power meter and NO rf on the external power
meter. A signal can be heard on a monitor receiver.


Also if I leave the subreceiver activated and turn off the split (no split)
keying still shows NO rf output on the k3 power meter and NO rf on the
external power meter. A signal can be heard on a monitor receiver

using <bset> <ant> changes the subrx receive path as expected but doesnt
affect the tx output

I was using the 2.82 software. I rolled back to 2.76 but still have the same
issue

Dave

ww2r




More information about the Elecraft mailing list