(K3) Utility Interface Problem

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

(K3) Utility Interface Problem

k8jrm

I need help!  I cannot get my computer to communicate with my K3. A
week ago, I had no trouble doing this.  Now, when I attempted to use
the transceiver using either the K3 Utility, revision 1.13,5.9, or
TRX-Manager (a CAT program), there is no handshaking. At one time,
both of these programs worked separately with the K3.

My computer is a Dell Vostro 320 using Windows 7, Professional,
SP1.  The interconnect is a straight thru RS-232 cable, DB-9.

Using the utility, under firmware, I continually see "attempting to
contract K3 on Port COM1 at **** bit/s".

Suspecting the cable, I replaced it with another cable and the
interface problem continued.  Based upon this test, I assume that the
original cable was good and now have it back in-line.

Using the "good" cable I tried a second XP based computer with
1.13.5.9. The problem continued!

To double check, I've ran Dell's diagnostics on the computers (OS Win
XP, SP3 and Win 7 Pro, SP1). Both machines pass the serial port tests!

I ensured the both the K3 and computers were setup with the same COM
port, 8N1 and Speeds.  In this case, 38,400 bit/s.

Based upon the above, I suspect that the problem is in my K3.  Most
likely, I have unknowingly changed the configuration parameter
affecting communications.

Can someone point me in right direction to solve my interface
problem? I'm stumped!

Tom, K8JRM

______________________________________________________________
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]
Reply | Threaded
Open this post in threaded view
|

Re: (K3) Utility Interface Problem

Nr4c
Tom.  

I suspect one of two possibilities. Check ALL RS-232 settings, both on computer and radio. You seem ok w/computer end, chk CONFIG:RS232 for radio settings. Mine says 38,400 b.

But you may have an issue with the serial interface chip in the K3. This is not a common occur acne but it has happened to 3 of about 12 owners I know locally. There are simple voltage checks you can do to determine if this is the problem but I'll suggest you contact Dave or Howard at Elecraft Support to direct you thru this. If this is the cause they will prob send you a new KIO3 bd and you return old one after the swap. Easy to do.

Good luck.  

Sent from my iPhone
...nr4c. bill


> On Jun 20, 2014, at 1:08 PM, Tom Laszynski <[hidden email]> wrote:
>
>
> I need help!  I cannot get my computer to communicate with my K3. A week ago, I had no trouble doing this.  Now, when I attempted to use the transceiver using either the K3 Utility, revision 1.13,5.9, or TRX-Manager (a CAT program), there is no handshaking. At one time, both of these programs worked separately with the K3.
>
> My computer is a Dell Vostro 320 using Windows 7, Professional, SP1.  The interconnect is a straight thru RS-232 cable, DB-9.
>
> Using the utility, under firmware, I continually see "attempting to contract K3 on Port COM1 at **** bit/s".
>
> Suspecting the cable, I replaced it with another cable and the interface problem continued.  Based upon this test, I assume that the original cable was good and now have it back in-line.
>
> Using the "good" cable I tried a second XP based computer with 1.13.5.9. The problem continued!
>
> To double check, I've ran Dell's diagnostics on the computers (OS Win XP, SP3 and Win 7 Pro, SP1). Both machines pass the serial port tests!
>
> I ensured the both the K3 and computers were setup with the same COM port, 8N1 and Speeds.  In this case, 38,400 bit/s.
>
> Based upon the above, I suspect that the problem is in my K3.  Most likely, I have unknowingly changed the configuration parameter affecting communications.
>
> Can someone point me in right direction to solve my interface problem? I'm stumped!
>
> Tom, K8JRM
>
> ______________________________________________________________
> 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]
Reply | Threaded
Open this post in threaded view
|

Re: (K3) Utility Interface Problem

k8jrm
In reply to this post by k8jrm
Hi All,

After over a week of trying various fixes, Bill, NR4C, may have found
the solution to my communications interface problem!  I had total
forgotten about a severe Thunder storm we has less than a weeks
ago!  Never thought to couple my problem with nearby lightning strikes!

Bill wisely e-mailed me saying  "... you may have an issue with the
serial interface chip in the K3. This is not a common occurrence but
it has happened to 3 of about 12 owners I know locally." Bill, BTW,
lives in Williamsburg Va area.  I guess they have thunderstorm like
we have in Oklahoma!

After speaking with Elecraft, I am sending my K3 in for a check-up
and to be upgraded while it is there!  At my age installing a new
surface mounted chip is out of the question!

Thanks to all who responded to my call for help!

73, Tom

______________________________________________________________
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]