K3 Locked Up - MCU LD
|
Upgrading FW on my older K3 (4866) using USB/serial converter. Same setup used successfully for many years.
Converter continues to work with other devices so suspect laptop and converter are good (connects okay to other rig) At switch on or after holding on/off button for 10 seconds, TX LED flashes, no backlight and MCU LD showing on screen. Utility is unable to connect to the K3. I have tried the solutions in the help files and from online but cannot get the K3 utility to connect. Left the K3 completely disconnected overnight and followed the Elecraft troubleshooting doc but no change. Is there a way to reset the K3 to allow a connection? Many thanks Jim, MM0BQI Error message Elecraft K3 Utility Version 1.20.1.15 OS Version 10.0 Build 18363 K3 MCU version ??.?? on COM3 at 38400 bit/s Error code 0xE2000083: No response to semicolon poll after testing for P3 Click "Close" to close this window |
|
|
|
Hi Jim,
From your description, I take it that your USB/RS232 converter has the USB in the laptop and the RS232 into the back of the K3. My K3s RS232 connection is very sensitive to any dirt or corrosion on any of the pins of the RS232 connector.
You might try plugging and unplugging the RS232 connector a few times and ensure that it is firmly seated on the RS232 socket.
Worth a shot …
I hope you get this sorted.
- 73 and good DX de Mike, K6MKF, NCDXC Secretary
From: Elecraft-K3@groups.io <Elecraft-K3@groups.io> On Behalf Of Jim MM0BQI via groups.io
Sent: Thursday, November 19, 2020 07:29 To: Elecraft-K3@groups.io Subject: [Elecraft-K3] K3 Locked Up - MCU LD
Upgrading FW on my older K3 (4866) using USB/serial converter. Same setup used successfully for many years. |
|
|
|
Thanks for the advice Mike
Just stripped down the serial end of the converter to check for dry joints but all okay. (Still works okay testing with N1MM and TS2000) Checked the K3 I/O board connections all good. Initially the utility recognises that the K3 is waiting for a FW download, wonder if I can assume that that the comms are good and it is the K3 that is not able to communicate because of the current state? 73 Jim |
|
|
|
Sounds like you’ve checked everything.
toggle quoted message
Show quoted text
Do you have the latest version of the K3 Utility Program? -- 73 de Mike Flowers, K6MKF, NCDXC - "It's about DX!" On Nov 19, 2020, at 9:21 AM, Jim MM0BQI via groups.io <MM0BQI@...> wrote:
|
|
|
|
Hi Jim, Also make SURE that the RS-232 connection is DIRECT to the K3, not through the P3 (if there is one there) or any other component. If you're using a USB to RS-232 dongle, try another USB port, verify (device manager) the 'new' com port value is the same as expected; if not adjust the software as required (Windows may assign it a different value, depending on the version of OS in play). Good luck, please report success/failures here,
73
On 11/19/2020 8:20 AM, Mike Flowers
wrote:
|
|
|
|
Thanks Rick
Direct connection between laptop and K3. Device manager shows device working and showing same port as K3 utility. I am using latest version of utility which works with the K3S (using different direct USB connection of course) 73 Jim |
|
|
|
Keith_WE6R <keithtrinity@...>
Check Config menu RS232, make sure it is not on USB (which you should not see unless you upgraded the KIO3 to the new one with USB).
Try 4800 baud vs 38400. Also note; sometimes in MCU LD, it will not appear you are connected when you actually are. You may see the "send firmware" button in the K3 Utility and it -looks- greyed-out, just click it anyway. Keith WE6R Elecraft K3 Tech |
|
|
|
Jim
Thanks Keith
Using the original KIO3 so no USB connector When I switch on, display immediately shows MCU LD on screen, TX LED flashes and all buttons/functions disabled If I apply power and hold button for 10 seconds does same thing Tried different speeds, pressing greyed out buttons etc, no joy. Still no comms 73 Jim |
|
|
|
Keith_WE6R <keithtrinity@...>
Hi Jim;
Confirming, your computer "device manager" changes to show the comm port when you plug the USB end into the computer? (takes maybe 10 seconds). And you set the K3 Utility to that comm #? Directly to the K3, no P3 or any other equipment inline? Will the computer talk to the P3 with the P3 utility? Send me an email direct with the whole story, I have too many things going on. Next would be pull the KIO3 digital board and check the little black cube chokes, they should be about 4 ohms (they can get popped open). Keith WE6R Elecraft Tech keith at elecraft.com |
|
|
|
Jim
Thanks Keith
P3 works perfectly so does Kenwood for rig control using the same converter. I will check the chokes after this weekend and drop you an email. No rush as I am working single band this weekend using the K3s Thanks again Jim |
|
|
|
Joe, KO8V
If the USB converter is an FTDI based device, be sure serial enumeration is not set. The setting is in the advanced area of the driver properties for the com port.
It's something FTDI continues to turn on be default in their driver, even though there are probably only "two" serial mice left in the entire world. When's the last time any one saw one in the wild? I really wish they would change the driver to drop it. It's hassle to have to turn it off for every new com port created by the FTDI driver. -- 73 Joe, KO8V |
|
|
|
Gordon LaPoint N1MGO
Joe,
Not sure why you have the problem
with "serial enumeration" on FTDI based devices. I have used
them, on multiple computers, with multiple operating systems, and
have never had to "turn off" the serial enumeration. I have had
to change the comport number on occasion, but that is about all
the "adjustments" I have ever had to do the the FTDI com port
setup.
Gordon - N1MGO
On 11/24/2020 7:09 AM, Joe, KO8V wrote:
If the USB converter is an FTDI based device, be sure serial enumeration is not set. The setting is in the advanced area of the driver properties for the com port.
|
|
|
|
Joe, KO8V
When that is selected I've had problems with it causing an instantiation of a serial mouse. Then the system thinks it has two mice. From then on random mouse inputs start happening. Then the real mouse on the computer acts up. I was just thinking that that could also be causing problems going the other way and possibly causing the OP's problem. I've seen the recommendation in more than one place to turn that off as well as disabling modem control on start up. In some ways FTDI is still in the dark ages with their driver. Better than others, but could be improved upon.
-- |
|
|
|
Jim
Many thanks for everyone's assistance.
Issue was resolved by using the IO board from my K3S to reload the firmware and get out of the bricked state. Original board re-installed and no further issues. I am pretty sure it was not a connector issue as the board had been in and out several times. The support I received from Keith Trinity at Elecraft was exceptional, very patient and methodical, cheers Keith! Best 73 Jim MM0BQI/GM1J |
|
|