[Elecraft] KIO2 problem -- maybe

[Clark Macaulay]

I had a similar failure several years ago.  Don helped me troubleshoot that
little board and the problem turned out to be a few diodes that got blown
due to a lightning strike.  I was glad it took out the diodes and not the
K2.

I do not use a KUSB converter with the K2 as I have 'real' RS232 ports in
the shack computer.  Since that time, though, I have used a wireless link
between the internet box (also taken out by lightning) and my shack
computer. This removes one path for any future strikes to come through and
blow up my modest shack.

GL on fixing your problem, Dave.  It's worth the time.

On Fri, Nov 19, 2021 at 5:46 PM Don Wilhelm <don at w3fpr.com> wrote:

> Dave,
>
> Being a little 'tongue in cheek' the answer is -- That depends on what
> you mean by "good"!
> Seriously, the fact that you can turn it on and off in the menu only
> means that there is a response from the KIO2 when it is communicating
> with the MCU over the AUXBUS line.
> I would suspect the MAX1406 IC, but since there was a lightning strike,
> it could be something different - anything!
>
> First do all the voltage measurements on the KIO2 board.
> Does anything get hot?  The voltage regulator in particular.
> Are you using the "special cable" between the KIO2 and the KUSB cable?
> You MUST use that!  It does not have to be long, but must be present.
> Check that all the inductors show continuity.
>
> If none of that is revealing, I can give you a series of tests that you
> can do to test the KIO2 alone (without removing it).
> If we get to that point, take it off-list (Delete "[Elecraft]" from the
> subject line) and I can give you the steps via private email.
>
> 73,
> Don W3FPR
>
> On 11/19/2021 4:40 PM, Dave Sublette wrote:
> > I had a lightning strike and am getting things back together.  I am
> > attempting to connect via a KUSB cable with a series adapter to make it a
> > proper cable for the K2.
> >
> > The PORT menus says the port is ON and I can turn it ON and OFF as
> outlined
> > in the manual.
> >
> > Prior to the strike, this same radio and cable and software was operating
> > normally.  Now the software cannot connect to the radio, even though the
> > setup shows an available USB/serial port available.
> >
> > I'm wondering if the KUSB cable is bad(probably due to the strike)?
> >
> > First item I need to know, is the KIO2 OK if I can turn it on and off
> from
> > the EDIT menu?  If the KIO2 is good, then it has to be the KUSB cable.
> >
> > What say ye?
> >
> > Thanks,
> >
> > Dave, K4TO
> > ______________________________________________________________
> > Elecraft mailing list
> > Home: http://mailman.qth.net/mailman/listinfo/elecraft
> > Help: http://mailman.qth.net/mmfaq.htm
> > Post: mailto:Elecraft at mailman.qth.net
> >
> > This list hosted by: http://www.qsl.net
> > Please help support this email list: http://www.qsl.net/donate.html
> > Message delivered to don at w3fpr.com
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to clark.macaulay at gmail.com



-- 
73,

Clark, WU4B
Little Pistol With Wires
QRPARCI #10815
SKCC #3892
NAQCC #5055
CWOPS #1869
Collins Collectors #AC90-12432
Southeastern DX Club <http://www.sedxc.org>
North Georgia QRP Club <http://www.nogaqrp.org>


*"It is vain to do with more what can be done with less."*
*Attributed to *William of Occam (1288 AD - 1348 AD)