OK, with the help of Rick Bates and Greg Buhyolf I have solved it. Background (more of it): I use a PC hooked to the KX3 in the shack but I am a Mac guy in the rest of my life. I had been trouble shooting this issue with that PC. Since I have 3 USB brand new cables from Elecraft, I decided to open one that had not been used and try updating with my trusty Macbook Air.
Steps: 1. Download the FTDI USB drivers for the Mac. 2. Download KX3 Utility from Elecraft. 2b. Open Utility and make sure verbose logging, trace, and Advanced options were selected-figuring that Elecraft will want this type of information. 3. Disconnect (already was) USB serial connection from KX3-leaving only power to radio. 4. Press and hold power for 10 seconds as per help file about MCU LD. 5. Connect USB cable to Mac then to KX3 6. Open KX3 Utility try connecting to KX3-success. 7. Click on Firmware Tab and Copy New Files From Elecraft 8. Still on Firmware Tab, select MCU box and then click "Send Checked Items to KX3" Wait.....I turned on trace and verbose logging in case I needed to send error log to Elecraft so it took longer than a normal firmware update. 9. SUCESS Message stated complete (or something like that) and I look over to see the KX3 on the frequency I left it on last night. I can only speculate but perhaps the recent FTDI driver update via Windows may have been the cause (more here: http://www.adafruit.com/blog/2014/10/22/ftdi-drivers-brick-counterfeit-chips-with-latest-windows-update/ ) NOT stating that the Elecraft chips supplied are counterfeit, but rather something with that update made my PC to KX3 connection wonky. The only supporting evidence that I have is that I changed OS Platform to OS X which would have completely different drivers and hardware handling. To my knowledge, FTDI update issues like those on the PC have not been reported on OS X. BTW, I am running OS X Yosemite. Oh, and yes I could/should have switched to the Mac and used the cable hooked to the PC first to rule out a bad cable. So I violated the first rule of trouble shooting: only change one thing at a time. HI HI. So all good now! Thanks for the suggestions that got me to where I had a solution Greg and Rick! Hopefully, you have access to a different OS platform and can try it. I suspect I could reproduce this via some Linux variant if I tried. 73 K5RHD /randy On Sun, Nov 16, 2014 at 10:42 AM, Rick Bates, WA6NHC < happymooseph...@gmail.com> wrote: > This may sound stupid, but reboot the computer and try again. It might > not be the radio not understanding the data coming in the i/o port, but > rather it may be the computer (driver) got hosed and isn't sending proper > data streams. Who among us hasn't had an OS go stupid? > > Then keep it simple, attach to ONLY the radio directly (you did). I also > suggest that you do not have the computer attached to the radio during the > (radio or computer) boot process because on occasion, the USB device reader > (what is attaching?) may 'read' the device improperly and attach the > incorrect driver. > > If that doesn't work, then 'prove' that the interface cable is still good > (test it). > > With all the complexity of attaching various components (OS, firmware, > hardware) together, it's a wonder any work at all. > > You should be able to get it back to working without EEINT, once the > firmware is reloaded. > > Rick, WA6NHC > > iPad = small keypad = typos = sorry ;-) > > > On Nov 16, 2014, at 9:32 AM, Randy Diddel <k5...@arrl.net> wrote: > > > > As I stated. I have read the manua (RTFM)l and tried the EEINT proceedure > > stated there. It will NOT respond to a Parameter INIT. It still says > "MCU > > LD." I have tried all documented solutions to get it back right. I > realize > > that I would have to recalibrate or load original config file after but I > > cannot even get there.... > > > > 73 > > > > K5RHD > > > > /randy > > > > On Sun, Nov 16, 2014 at 10:09 AM, Don Palmer <d.pal...@btinternet.com> > > wrote: > > > >> Hi hope this may help you if you go to page 43 of your owner’s manual. > >> > >> Look for Parameter Initialization and see if that will help you. > >> > >> > >> > >> Don > >> > >> G6CMV > > ______________________________________________________________ > > Elecraft mailing list > > Home: http://mailman.qth.net/mailman/listinfo/elecraft > > Help: http://mailman.qth.net/mmfaq.htm > > Post: mailto:Elecraft@mailman.qth.net > > > > This list hosted by: http://www.qsl.net > > Please help support this email list: http://www.qsl.net/donate.html > > Message delivered to happymooseph...@gmail.com > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
