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
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
I agree. I had a strike zap the KIO3 in my K3 because even though all
my other gear was unplugged at the time, my laptop (which interfaces to
my K3) wasn't. at first thought it was the KUSB. I bought a second
one figuring it wouldn't hurt to have a spare if the cable turned out to
not be
On 11/19/2021 1:40 PM, Dave Sublette wrote:
I'm wondering if the KUSB cable is bad(probably due to the strike)?
I would expect damage to electronics rather than cables. But ya never
know. :)
73, Jim K8YC
__
Elecraft mailing list
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
5 matches
Mail list logo
