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
Lynn:
This sounds to me like the classic bad solder connection: sometimes it
works perfectly and sometimes it doesn't work at all. If you can tune
in the oscillator when the interface isn't working, you might
concentrate your inspection from J1 to U1 and J2. Also, your tests
indicate the
Lynn
When something is intermittent like you describe, first suspect that elusive
unsoldered connection.
If it works from the K2 panel, but does not work with control through the
computer interface, check the components shown on sheet 2 of the KPA100
schematic in the lower left corner labeled
John Donthanks for your feedback! Sound like it should be a cinch.
I'll pack up the rig PS take to work with me tomorrow where I have
workbench with good magnified lighting my soldering iron on standby.
Hope to be back to you in a couple of days with good news that I've found
the
However, communication in the opposite direction is nonexistent;
that is, following the procedure on page 14 to issue the Test
Message from the K2 causes no response on Hyperterminal.
If you're connecting to your computer via a serial-to-USB adapter, I've
found from comments I've read
Thanks, Craig .. the device you are referring to is made by Iogear:
GUC232A - USB to PDA/Serial Adapter ... found it on Google.
However, I am going straight in to a serial port on a Dell Latitude D400
notebook ... so I think the problem lies elsewhere.
Thaanks again.
9 matches
Mail list logo
