The reason I mention this is that I recently went through a similar troubleshooting exercise with a KRC2 where it was suggested that my USB->serial device was bad, I should use the K3 AUX connector rather than RS232, I needed a real serial port, etc. etc.
After jumping through all of these hoops, the end result was that it was an Elecraft software problem. Wes --- On Fri, 1/8/10, Don Wilhelm <[email protected]> wrote: From: Don Wilhelm <[email protected]> Subject: Re: [Elecraft] K3 not communicating with PC To: "Wes Stewart" <[email protected]> Cc: [email protected], [email protected], "Roger Dallimore" <[email protected]> Date: Friday, January 8, 2010, 7:47 PM Wes, No-one is holding the K3 blameless, but in the interest of complete troubleshooting, it is quite reasonable (to me) to check the easy things first if for no other reason than to eliminate them from the suspect list. It is often that the things that are most frequently overlooked are the culprit. Despite the fact that these things are easy to check, human nature tends to expect the worst - elimination of items from the suspect list as a first order of business is always a wise undertaking in troubleshooting procedures. In other words, proving what works is just as important as finding what does not work. 73, Don W3FPR ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
