KX3 bricked by F/W upgrade attempt
Locked
12
12
KX3 bricked by F/W upgrade attempt
 
|
Hello Elecrafters,
First of all let me say that I have RTFM, and RTFHF (read the freaking help file) before posting this. I have read many digests both from here and on the Elecraft KX3 Yahoo group. Greg (K2UM) has the same issue and so does one other person (call, name uncertain). So, I am posting this here in hopes it has happened to someone and they have a solution. In an attempt to update to 2.25, the MCU load failed. If just froze during the process. After waiting a reasonable amount of time (20 minutes) to complete,I closed the Utility and tried to manually restart the KX3. No luck. I don't have batteries in my KX3 so I pulled the power and then tried to bring up the radio. "MCU LD" still stuck on the display. Tried the hold power buttons down for 10 seconds and all that outlined in the Help topic in the KX3 Utility. No luck. As a last resort, I figured I would just EEINT and reload config file or re-calibrate. The radio will not EEINT. I have left power off overnight and tried many steps to revive it this morning. I will mention that I had the PX3 in line but not on. I now know to update all firmware with the USB cable directly from computer to radio. Unless Wayne, Eric, anyone else has any ideas, it looks like I may have to send the rig home for repairs. Thanks, 73. K5RHD /randy ______________________________________________________________ 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 Message delivered to [hidden email] |
Re: KX3 bricked by F/W upgrade attempt
|
|
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 <[hidden email]> 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:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Re: KX3 bricked by F/W upgrade attempt
|
|
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 <[hidden email]> 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 <[hidden email]> > 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:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] 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 Message delivered to [hidden email] |
Re: KX3 bricked by F/W upgrade attempt
|
|
It doesn't sound stupid at all, Rick. I just went through the same
exercise with a K3 I'm rebuilding. On loading it the first time, the load failed mid-step. Trying to redo the firmware load, the utility couldn't even find a K3 attached. But it was because of the state of the serial port driver (or hardware maybe), not some failure at the K3 or within the K3 Utility program. In this case, I only had to exit the utility and cycle power on the USB hub with the serial converter attached. After doing that, the utility found the K3 in its "waiting for firmware load" state. This same scenario has played out with the KX3 as well. Rebooting the computer with nothing attached at the serial port would (should) work just as well. 73, matt W6NIA On Sun, 16 Nov 2014 09:42:44 -0800, you 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 <[hidden email]> 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 <[hidden email]> >> wrote: >> >>> Hi hope this may help you if you go to page 43 of your owners 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:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] >______________________________________________________________ >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 >Message delivered to [hidden email] -- "Give me six hours to chop down a tree and I will spend the first four sharpening the axe." -A. Lincoln ______________________________________________________________ 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 Message delivered to [hidden email] |
Re: KX3 bricked by F/W upgrade attempt
|
|
In reply to this post by Randy Diddel-2
Please try the procedure described in KX3 Utility Help, Troubleshooting, MCU
Load failure. The page is titled "MCU Boot Loader Troubleshooting". It describes a procedure to recover from interrupted firmware loads. One of several steps suggested include rebooting the computer to start the USB device driver from a known state. There are other important steps as well. EEINIT has to do with clearing the microcontrollers' EEPROM. The microcontroller we use stores firmware in one memory space (the "program memory") and EEPROM is a different area entirely. EEINIT does not influence the program (firmware) store. The "program memory" is changed by the firmware load process. EEPROM is changed by EEINIT and by normal operation of the radio. Loading firmware doesn't change EEPROM. (But the new firmware does immediately read that EEPROM on startup). The front panel steps needed to perform EEINIT depend on program code in installed firmware, so it's reasonable that you wouldn't be able to perform that procedure without proper firmware installed. 73 de Dick, K6KR -----Original Message----- From: Elecraft [mailto:[hidden email]] On Behalf Of Randy Diddel Sent: Sunday, November 16, 2014 8:44 AM To: [hidden email] Subject: [Elecraft] KX3 bricked by F/W upgrade attempt Hello Elecrafters, First of all let me say that I have RTFM, and RTFHF (read the freaking help file) before posting this. I have read many digests both from here and on the Elecraft KX3 Yahoo group. Greg (K2UM) has the same issue and so does one other person (call, name uncertain). So, I am posting this here in hopes it has happened to someone and they have a solution. In an attempt to update to 2.25, the MCU load failed. If just froze during the process. After waiting a reasonable amount of time (20 minutes) to complete,I closed the Utility and tried to manually restart the KX3. No luck. I don't have batteries in my KX3 so I pulled the power and then tried to bring up the radio. "MCU LD" still stuck on the display. Tried the hold power buttons down for 10 seconds and all that outlined in the Help topic in the KX3 Utility. No luck. As a last resort, I figured I would just EEINT and reload config file or re-calibrate. The radio will not EEINT. I have left power off overnight and tried many steps to revive it this morning. I will mention that I had the PX3 in line but not on. I now know to update all firmware with the USB cable directly from computer to radio. Unless Wayne, Eric, anyone else has any ideas, it looks like I may have to send the rig home for repairs. Thanks, 73. K5RHD /randy ______________________________________________________________ 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 Message delivered to [hidden email] ______________________________________________________________ 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 Message delivered to [hidden email] |
Re: KX3 bricked by F/W upgrade attempt
|
|
In reply to this post by Matt Zilmer-3
I remember a problem I had a year or so ago where I was using
the K3 (Mac) utility to load all the K3 microprocessors' firmware. I was failing on loading one of them and restarting it did not cure the problem. I got around the problem by loading just that specific piece of firmware. I vaguely remember seeing a bug fix for the utility that seemed to be my problem, but I could have misinterpreted the README. I haven't had the problem since. Bottom line: Try loading just that piece of firmware. Then load the others separately if they aren't up to date. 73 Bill AE6JV On 11/16/14 at 9:57 AM, [hidden email] (Matt Zilmer) wrote: >It doesn't sound stupid at all, Rick. I just went through the same >exercise with a K3 I'm rebuilding. On loading it the first time, the >load failed mid-step. Trying to redo the firmware load, the utility >couldn't even find a K3 attached. But it was because of the state of >the serial port driver (or hardware maybe), not some failure at the K3 >or within the K3 Utility program. ------------------------------------------------------------------------- Bill Frantz | When it comes to the world | Periwinkle (408)356-8506 | around us, is there any choice | 16345 Englewood Ave www.pwpconsult.com | but to explore? - Lisa Randall | Los Gatos, CA 95032 ______________________________________________________________ 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 Message delivered to [hidden email] |
Re: KX3 bricked by F/W upgrade attempt
|
|
In reply to this post by Randy Diddel-2
Randy,
MCU LD is a normal display by the KX3 when waiting for firmware to be loaded. It may be that the KX3 is just sitting there waiting for the computer to feed it some data. Because this all started during a firmware update that stopped midstream for some unknown reason, I would suggest you be suspicious of the computer, the adapter cable and anything else associated with the serial connection. You may even want to try reloading the driver for the USB to serial adapter. It would be a shame to send the KX3 back to Elecraft only to discover that there was a problem at the computer end. If you have another computer (or can borrow one) try loading the USB cable adapter driver and KX3 Utility on that computer. If you have an XG3 signal generator, try using the same cable and the XG3 Utility - the cable for the XG3 and the KX3 are the same. 73, Don W3FPR On 11/16/2014 12:32 PM, Randy Diddel 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.... > > ______________________________________________________________ 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 Message delivered to [hidden email] |
Re: KX3 bricked by F/W upgrade attempt
|
|
In reply to this post by Rick WA6NHC
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 < [hidden email]> 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 <[hidden email]> 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 <[hidden email]> > > 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:[hidden email] > > > > This list hosted by: http://www.qsl.net > > Please help support this email list: http://www.qsl.net/donate.html > > Message delivered to [hidden email] > 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 Message delivered to [hidden email] |
Re: KX3 bricked by F/W upgrade attempt
|
|
In reply to this post by Don Wilhelm-4
Don,
You are correct. I tried it on a Mac with a brand new cable (I have many extras as I have bought a lot of Elecraft toys). See my notes on the post that just went to the reflector. Good ideas and I got to a solution just before reading this. Thanks for the help. On a side note, I wish I could use a Mac in the shack for everything natively (not in a VM like Parallels or VMWare, etc). Thanks for the input and 73, K5RHD /randy On Sun, Nov 16, 2014 at 11:58 AM, Don Wilhelm <[hidden email]> wrote: > Randy, > > MCU LD is a normal display by the KX3 when waiting for firmware to be > loaded. > It may be that the KX3 is just sitting there waiting for the computer to > feed it some data. > > Because this all started during a firmware update that stopped midstream > for some unknown reason, I would suggest you be suspicious of the computer, > the adapter cable and anything else associated with the serial connection. > You may even want to try reloading the driver for the USB to serial adapter. > > It would be a shame to send the KX3 back to Elecraft only to discover that > there was a problem at the computer end. If you have another computer (or > can borrow one) try loading the USB cable adapter driver and KX3 Utility on > that computer. If you have an XG3 signal generator, try using the same > cable and the XG3 Utility - the cable for the XG3 and the KX3 are the same. > > 73, > Don W3FPR > > > On 11/16/2014 12:32 PM, Randy Diddel 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.... >> >> >> > 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 Message delivered to [hidden email] |
Re: KX3 bricked by F/W upgrade attempt
|
|
Randy,
Re "On a side note, I wish I could use a Mac in the shack for everything natively (not in a VM like Parallels or VMWare, etc).", you can. Just use Bootcamp and install Windows as an alternate boot option. I do that with my MBAir and my MBPro. Both have solid-state drives, so re-boot is fast. I got tired of dealing with Parallels! 73, Phil W7OX On 11/16/14 11:08 AM, Randy Diddel wrote: > Don, > > You are correct. I tried it on a Mac with a brand new cable (I have many > extras as I have bought a lot of Elecraft toys). See my notes on the post > that just went to the reflector. Good ideas and I got to a solution just > before reading this. Thanks for the help. > > On a side note, I wish I could use a Mac in the shack for everything > natively (not in a VM like Parallels or VMWare, etc). > > Thanks for the input and 73, > > K5RHD > > /randy > > On Sun, Nov 16, 2014 at 11:58 AM, Don Wilhelm <[hidden email]> wrote: > >> Randy, >> >> MCU LD is a normal display by the KX3 when waiting for firmware to be >> loaded. >> It may be that the KX3 is just sitting there waiting for the computer to >> feed it some data. >> >> Because this all started during a firmware update that stopped midstream >> for some unknown reason, I would suggest you be suspicious of the computer, >> the adapter cable and anything else associated with the serial connection. >> You may even want to try reloading the driver for the USB to serial adapter. >> >> It would be a shame to send the KX3 back to Elecraft only to discover that >> there was a problem at the computer end. If you have another computer (or >> can borrow one) try loading the USB cable adapter driver and KX3 Utility on >> that computer. If you have an XG3 signal generator, try using the same >> cable and the XG3 Utility - the cable for the XG3 and the KX3 are the same. >> >> 73, >> Don W3FPR >> >> >> On 11/16/2014 12:32 PM, Randy Diddel 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.... >>> >>> >>> > ______________________________________________________________ > 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 > Message delivered to [hidden email] > ______________________________________________________________ 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 Message delivered to [hidden email] |
Re: KX3 bricked by F/W upgrade attempt
|
|
In reply to this post by Randy Diddel-2
Hey Randy. Ready for a surprise?
The FTDI driver is actually built in to Yosemite. Mavericks, too. That means you don’t need to download the driver from FTDI. Why is this important? In Yosemite, drivers must be signed. The ones on the FTDI site are not. I didn’t believe this when I first heard it, so I tried an FTDI USB device with a fresh install (not upgrade) of Yosemite. It worked! The devices were recognized and worked properly. As a developer, I was surprised since I had seen no notification about this previously. 73, and glad you have things going. Jack B, W6FB > On Nov 16, 2014, at 11:08 AM, Randy Diddel <[hidden email]> wrote: > > Don, > > You are correct. I tried it on a Mac with a brand new cable (I have many > extras as I have bought a lot of Elecraft toys). See my notes on the post > that just went to the reflector. Good ideas and I got to a solution just > before reading this. Thanks for the help. > > On a side note, I wish I could use a Mac in the shack for everything > natively (not in a VM like Parallels or VMWare, etc). > > Thanks for the input and 73, > > K5RHD > > /randy > > On Sun, Nov 16, 2014 at 11:58 AM, Don Wilhelm <[hidden email]> wrote: > >> Randy, >> >> MCU LD is a normal display by the KX3 when waiting for firmware to be >> loaded. >> It may be that the KX3 is just sitting there waiting for the computer to >> feed it some data. >> >> Because this all started during a firmware update that stopped midstream >> for some unknown reason, I would suggest you be suspicious of the computer, >> the adapter cable and anything else associated with the serial connection. >> You may even want to try reloading the driver for the USB to serial adapter. >> >> It would be a shame to send the KX3 back to Elecraft only to discover that >> there was a problem at the computer end. If you have another computer (or >> can borrow one) try loading the USB cable adapter driver and KX3 Utility on >> that computer. If you have an XG3 signal generator, try using the same >> cable and the XG3 Utility - the cable for the XG3 and the KX3 are the same. >> >> 73, >> Don W3FPR >> >> >> On 11/16/2014 12:32 PM, Randy Diddel 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.... >>> >>> >>> >> > ______________________________________________________________ > 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 > Message delivered to [hidden email] ______________________________________________________________ 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 Message delivered to [hidden email] |
|
|
I had an earlier update crash (user error) and had similar MCU Load stuck. I checked everything on radio side then decided to check computer side. Somewhere in the process, it assigned a new internal PC port to the usb adapter and would not reassign to the correct one. I shut down computer and rebooted and correct port came up and firmware install completed successfully .
|
|
|
What are opinions of leaving my K3 and KPA500 on 24/7 or should they
be powered on and off for daily use? Jack W4GRJ ______________________________________________________________ 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 Message delivered to [hidden email] |
|
|
K3, KPA500, KAT500, and P3 are on 24/7 most of the time unless we're
leaving for a day or two. Works for me. 73, Fred K6DGW - Northern California Contest Club - CU in the 50th Running of the 2015 Cal QSO Party 3-4 Oct 2015 - www.cqp.org On 11/17/2014 5:47 AM, w4grj wrote: > What are opinions of leaving my K3 and KPA500 on 24/7 or should they > be powered on and off for daily use? > Jack > W4GRJ ______________________________________________________________ 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 Message delivered to [hidden email] |
|
|
In reply to this post by W4GRJ
Same here
Harlan NC3C Sent from my Verizon Wireless 4G LTE smartphone -------- Original message -------- K3, KPA500, KAT500, and P3 are on 24/7 most of the time unless we're leaving for a day or two. Works for me. 73, Fred K6DGW - Northern California Contest Club - CU in the 50th Running of the 2015 Cal QSO Party 3-4 Oct 2015 - ______________________________________________________________ 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 Message delivered to [hidden email] |
|
|
Always on here, I use it remotely too.
Rick, WA6NHC iPad = small keypad = typos = sorry ;-) > On Nov 17, 2014, at 10:08 AM, hsherriff <[hidden email]> wrote: > > Same here > Harlan > NC3C > > Sent from my Verizon Wireless 4G LTE smartphone > > -------- Original message -------- > > > K3, KPA500, KAT500, and P3 are on 24/7 most of the time unless we're > leaving for a day or two. Works for me. > > 73, > > Fred K6DGW > - Northern California Contest Club > - CU in the 50th Running of the 2015 Cal QSO Party 3-4 Oct 2015 > - > ______________________________________________________________ > 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 > Message delivered to [hidden email] 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 Message delivered to [hidden email] |
|
|
In reply to this post by W4GRJ
On Mon,11/17/2014 5:47 AM, w4grj wrote:
> What are opinions of leaving my K3 and KPA500 on 24/7 or should they > be powered on and off for daily use? If you live in California (escalating rates based on monthly usage), you probably want to turn everything off when you leave the shack to save on your electricity bill. My differential rate is in the range of $0.35 per kWh, and even being frugal, I'm always subject to that rate. Back in Chicago, where I was paying in the range of $0.13 in the summer and a few pennies less in the winter, I left everything on all the time. :) 73, Jim K9YC ______________________________________________________________ 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 Message delivered to [hidden email] |
|
|
In reply to this post by W4GRJ
Jack,
Since Jan 2014, I've left my K3 and P3 on 24/7. The KPA500 I sometimes turn it off, but with the front panel ON switch only. The rear panel power switch I leave alone, so it's always on, except for total power outages. No problems doing it so far. 73, Rick W7LKG -----Original Message----- From: Elecraft [mailto:[hidden email]] On Behalf Of w4grj Sent: Monday, November 17, 2014 05:47 To: [hidden email] Subject: [Elecraft] K3 KPA500 power on 24/7 What are opinions of leaving my K3 and KPA500 on 24/7 or should they be powered on and off for daily use? Jack W4GRJ ______________________________________________________________ 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 Message delivered to [hidden email] ______________________________________________________________ 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 Message delivered to [hidden email] |
|
|
In reply to this post by W4GRJ
Why would you want to leave it on? It's just wasting power, though being Elecraft, not much. I turn everything off, ground all antennas, and switch the k-line into a dummy load. Even for the demands of EME the K3 and XV-144 are stable in 20 minutes.
I once had the K3 go into a runaway state where it started transmitting on a 12 mhz frequency I use to listen to marine cw during the annual Night of Nights. Smoke escaped. Elecraft Support was baffled, but it has never reoccured (after the K3 was repaired). It could have been my PC. I leave the K3 unattended when it is running WSPR, but I don't understand what the upside is to leaving everything on when there are known and unknown downsides, static discharges for example. Stuff Happens. 73 Eric WD6DBM Sent on a Sprint Samsung Galaxy S® III <div>-------- Original message --------</div><div>From: w4grj <[hidden email]> </div><div>Date:11/17/2014 5:47 AM (GMT-08:00) </div><div>To: [hidden email] </div><div>Subject: [Elecraft] K3 KPA500 power on 24/7 </div><div> </div>What are opinions of leaving my K3 and KPA500 on 24/7 or should they be powered on and off for daily use? Jack W4GRJ ______________________________________________________________ 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 Message delivered to [hidden email] ______________________________________________________________ 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 Message delivered to [hidden email] |
|
|
Anyone who, for no really good reason, leaves anything on 24/7, must be
paying far less for their electricity than we do over on this side of the Atlantic! 73 Stephen, G4SJP On 17 November 2014 22:40, norrislawfirm2 <[hidden email]> wrote: > Why would you want to leave it on? It's just wasting power, though being > Elecraft, not much. I turn everything off, ground all antennas, and switch > the k-line into a dummy load. Even for the demands of EME the K3 and > XV-144 are stable in 20 minutes. > > I once had the K3 go into a runaway state where it started transmitting on > a 12 mhz frequency I use to listen to marine cw during the annual Night of > Nights. Smoke escaped. Elecraft Support was baffled, but it has never > reoccured (after the K3 was repaired). It could have been my PC. > > I leave the K3 unattended when it is running WSPR, but I don't understand > what the upside is to leaving everything on when there are known and > unknown downsides, static discharges for example. > > Stuff Happens. > > 73 > > Eric WD6DBM > > > Sent on a Sprint Samsung Galaxy S® III > > <div>-------- Original message --------</div><div>From: w4grj < > [hidden email]> </div><div>Date:11/17/2014 5:47 AM (GMT-08:00) > </div><div>To: [hidden email] </div><div>Subject: [Elecraft] K3 > KPA500 power on 24/7 </div><div> > </div>What are opinions of leaving my K3 and KPA500 on 24/7 or should they > be powered on and off for daily use? > Jack > W4GRJ > > > ______________________________________________________________ > 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 > Message delivered to [hidden email] > ______________________________________________________________ > 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 > Message delivered to [hidden email] 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 Message delivered to [hidden email] |
«
Return to Elecraft
|
1 view|%1 views
| Free forum by Nabble | Edit this page |