See K3 Utility Help, Troubleshooting, "Finding the appropriate COM Port for a USB to Serial Adapter". Sometimes external events (like driver refreshes, installation of new "service packs" or Windows Update activity) can cause COM port numbers to change. I suspect that the COM Port that the K3 Utility is using is really something else than the device attached to your K3.
Many devices, including the K3 in boot loader mode, will echo whatever is sent to them. If your K3 has a "normal" VFO display (instead of MCU LD), then it should not respond with the "boot loader" prompt. See also K3 Utility Help on the Port Tab, "Test Communications" which explains this in a little detail. Dick, K6KR -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] (Baron) Sent: Monday, September 26, 2011 12:47 PM To: [email protected] Subject: [Elecraft] Lost K3/PC Connection AOK for 1 yr.; recent signalink rig control WinXP SP3 not successful; lost pc/K3 utility connection; COM port open, boot loader ready but nada; tried all in forums, helps, etc. ______________________________________________________________ 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 ______________________________________________________________ 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
