K3 communcation issue solved!

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

K3 communcation issue solved!

Chester Alderman
Thank you to those who have been trying to help me to get my new K3 to talk
with N1MM. That issue is now solved.
It wasn't until I thought I had checked and rechecked all configurations,
both in N1MM and in the K3, that I finally became convinced it was not a
software/firmware issue. In checking my serial cables, I found the DB-9
connector to the K3 had slipped partially out of the K3 connector. I simply
reseated that connector (AND used a screw driver to fasten it to the K3 and
the K3 immediately started communicating with N1MM again.
I do appreciate everyone offering me very well thought out suggestions to
solve this problem.
Thank you all again
73,
Tom - W4BQF





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

Re: K3 communcation issue solved!

Buck - k4ia
I often find the true solution is the simplest.  Occam's Razor
 
k4ia

In a message dated 8/3/2010 3:47:13 P.M. Eastern Daylight Time,  
[hidden email] writes:
Thank you to those who have been trying to  help me to get my new K3 to talk
with N1MM. That issue is now solved.
It  wasn't until I thought I had checked and rechecked all configurations,
both  in N1MM and in the K3, that I finally became convinced it was not  a
software/firmware issue. In checking my serial cables, I found the  DB-9
connector to the K3 had slipped partially out of the K3 connector. I  simply
reseated that connector (AND used a screw driver to fasten it to the  K3 and
the K3 immediately started communicating with N1MM again.
I do  appreciate everyone offering me very well thought out suggestions to
solve  this problem.
Thank you all again
73,
Tom -  W4BQF






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

Re: K3 communcation issue solved!

Edward R Cole
In reply to this post by Chester Alderman
Occam's Razor!  Haven't heard that on this list before.  Sounds like
an adherent of SETI?

Regarding the simplest solution is often true, reminds me of the
advice of an old mentor back 30-years ago advising me not to be
looking for complicated causes for electronic malfunctions, ... "the
solution is usually very simple".

Regarding non-seated computer cables, that issue "bit" me recently
when I could not turn on a remote piece of equipment.  The control
wire was on a DB-25 plug that had slipped a little so not fully
seated.  I am now looking for those little hex-nut couplers that
provide for securing the plug to the receptacle on sub-D computer
connectors.  I wish they were supplied when one bought the connectors.

My SO2R control panel uses three Sub-D9M and two Sub-D25M panel
receptacles for control line connections (and ten RCA-phono
connectors).  One 9M goes to the computer Serial port and two go to
each radio (FT-847 & K3).  The two 25M are for control lines to other
equipment, towers and antenna switches.  They terminate on barrier
terminal strips for interconnection to control lines.

73, Ed - KL7UW
----------------------------------
Message: 25
Date: Tue, 3 Aug 2010 16:57:15 -0400 (EDT)
From: [hidden email]
Subject: Re: [Elecraft] K3 communcation issue solved!
To: [hidden email], [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="US-ASCII"

I often find the true solution is the simplest.  Occam's Razor

k4ia

In a message dated 8/3/2010 3:47:13 P.M. Eastern Daylight Time,
[hidden email] writes:
Thank you to those who have been trying to  help me to get my new K3 to talk
with N1MM. That issue is now solved.
It  wasn't until I thought I had checked and rechecked all configurations,
both  in N1MM and in the K3, that I finally became convinced it was not  a
software/firmware issue. In checking my serial cables, I found the  DB-9
connector to the K3 had slipped partially out of the K3 connector. I  simply
reseated that connector (AND used a screw driver to fasten it to the  K3 and
the K3 immediately started communicating with N1MM again.
I do  appreciate everyone offering me very well thought out suggestions to
solve  this problem.
Thank you all again
73,
Tom -  W4BQF



73, Ed - KL7UW, WD2XSH/45
======================================
BP40IQ   500 KHz - 10-GHz   www.kl7uw.com
EME: 144-QRT*, 432-100w, 1296-QRT*, 3400-fall 2010
DUBUS Magazine USA Rep [hidden email]
======================================
*temp
______________________________________________________________
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