[Elecraft] 160RX Not Recognized by MCU
Jack Brindle
[email protected]
Wed Feb 18 15:24:10 2004
Since the K2 is able to exercise the RxAnt function, then it indeed
must be also recognizing the K160 module. This tells me that the
problem lies elsewhere. Amazing as it seems, it is most likely a
problem with AuxBus communications when trying to select 160 meters. In
this case the K2's AuxBus is heavily loaded. Make sure that all of the
proper upgrades which affect the AuxBus have been performed.
Specifically, any that change the capacitance and series resistance on
a module's AuxBus connection will have effect here. You might also
check to make sure you have the KDSP2 upgrade which address its AuxBus
problems.
By the way, one hint I can give is that when band changes occur, there
is a lot of traffic on the AuxBus. This appears to be the time that
excess capacitance on the AuxBus has its worst effects.
On Feb 18, 2004, at 1:49 AM, Sverre Holm wrote:
>> I've been out of two for a few weeks and upon my return I
>> fired up the K2 (SN=3043). I tried to switch to 160 and the
>> rig does not recognize the 160RX module. I accessed the menus
>> and found that I do see the RXant on/off function. The RX
>> antenna seems to work fine as well.
>
> Hi
>
> I would measure the coil of the 160m relay with an ohm-meter. The K2
> recognizes its presence by sensing it. Check for poor solder joints at
> or near the relay or the PCB connector.
- Jack Brindle, WA4FIB
------------------------------------------------------------------------
---------------------