Elecraft

K3: KIO3 dgital board failed (I think)

Classic

List

Threaded

3 messages Options

Edward R Cole

K3: KIO3 dgital board failed (I think)

My K3 SN 4340 bought in 2010 apparently has a failure in the RS232 I/F.

My computer says the FDTI cable is working and using com port-6 but
there is no connection using the K3 Utility or WSJT-X which was
running fine in July. The radio no longer keys up on computer
boot-up as before. I bought another FDTI USB/RS232 conversion cable
and it does not work wit the K3, either. I checked the com port and
cable via Device Manager and both are shown as working with no
problems. I even used my second computer to test the cables (also
showing working well). Computers are i5 running win10pro64.

I contacted Elecraft Service Dept on Friday so waiting to hear back from them.

I gave a passing thought to just upgrade to the KIO3B but it totals
$437.80 before shipping. I don't really need the USB I/F for my use
of the K3. I use two com ports to support control of the K3 (I won't
bother you with details) to run MAP65 and TRAKBOX programs
simultaneously. But just have the single com port recently in use with WSJT-X.

I guess I wonder if anyone else has had this failure?

73, Ed - KL7UW
http://www.kl7uw.com
Dubus-NA Business mail:
[hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Nr4c

Re: K3: KIO3 dgital board failed (I think)

Oh yes. And the only way out is to upgrade the whole system. Or look for used items here.

Sent from my iPhone
...nr4c. bill

> On Sep 14, 2020, at 4:48 PM, Edward R Cole <[hidden email]> wrote:
>
> My K3 SN 4340 bought in 2010 apparently has a failure in the RS232 I/F.
>
> My computer says the FDTI cable is working and using com port-6 but there is no connection using the K3 Utility or WSJT-X which was running fine in July. The radio no longer keys up on computer boot-up as before. I bought another FDTI USB/RS232 conversion cable and it does not work wit the K3, either. I checked the com port and cable via Device Manager and both are shown as working with no problems. I even used my second computer to test the cables (also showing working well). Computers are i5 running win10pro64.
>
> I contacted Elecraft Service Dept on Friday so waiting to hear back from them.
>
> I gave a passing thought to just upgrade to the KIO3B but it totals $437.80 before shipping. I don't really need the USB I/F for my use of the K3. I use two com ports to support control of the K3 (I won't bother you with details) to run MAP65 and TRAKBOX programs simultaneously. But just have the single com port recently in use with WSJT-X.
>
> I guess I wonder if anyone else has had this failure?
>
> 73, Ed - KL7UW
> http://www.kl7uw.com
> Dubus-NA Business mail:
> [hidden email]
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

David Gilbert-2

Re: K3: KIO3 dgital board failed (I think)

In reply to this post by Edward R Cole

I had exactly that same problem, Ed, and I also first thought it was the
USB/RS232 cable (which it wasn't). I also do not need the direct USB
connectivity, or the associated internal sound card. Luckily, I was able
to buy replacement boards from someone who had done the upgrade to the
KIO3B for another ham and still had the old boards, one of which ... the
audio board ... was itself bad but at least the RS232 board was good.
Problem fixed.

In my case, the KIO3A apparently was damaged by a line transient that
came in via the laptop that was connected to the USB/RS232 line. Most
everything was disconnected at the time, but that line wasn't.

I had sent an email to Elecraft technical support when I first had the
problem, asking whether or not they had replacement boards or whether
they could fix the KIO3A. The tech didn't bother to answer either of
those questions and simply replied with a rather curt "just upgrade to
the KIO3B ... you'll be happier".

Somebody could probably make a small business gathering various older
K3/K3s boards from folks who had done various upgrades in order to
service users like us who can't get help anymore from Elecraft.

73,
Dave AB7E

On 9/14/2020 1:43 PM, Edward R Cole wrote:

> My K3 SN 4340 bought in 2010 apparently has a failure in the RS232 I/F.
>
> My computer says the FDTI cable is working and using com port-6 but
> there is no connection using the K3 Utility or WSJT-X which was
> running fine in July. The radio no longer keys up on computer boot-up
> as before. I bought another FDTI USB/RS232 conversion cable and it
> does not work wit the K3, either. I checked the com port and cable
> via Device Manager and both are shown as working with no problems. I
> even used my second computer to test the cables (also showing working
> well). Computers are i5 running win10pro64.
>
> I contacted Elecraft Service Dept on Friday so waiting to hear back
> from them.
>
> I gave a passing thought to just upgrade to the KIO3B but it totals
> $437.80 before shipping. I don't really need the USB I/F for my use
> of the K3. I use two com ports to support control of the K3 (I won't
> bother you with details) to run MAP65 and TRAKBOX programs
> simultaneously. But just have the single com port recently in use
> with WSJT-X.
>
> I guess I wonder if anyone else has had this failure?
>
> 73, Ed - KL7UW