[Elecraft] K3 stopped communicating

[Guy Olinger K2AV]

Assume that you are working with winders, make sure that the com port has
not been reassigned because you added or removed some usb device from the
system.  Go into device manager, look under com ports and see if your usb
adapter is on the com port you expect it on.

73, Guy.

On Tue, Sep 6, 2011 at 5:57 PM, stan levandowski <sjl219 at optonline.net>wrote:

> My K3 (#5244) mysteriously stopped working with HRD.  It had been
> working FB for months.  HRD claimed it could not connect with the K3.
> I then tried it with the K3 Utility and I got the following:
>
> Xe2000011 Bootstrap loader did not echo a D
> MCU Firmware load failed
>
> It's a K3/10 which I built and it works just fine except for this.  The
> USB cable is the Elecraft product.
>
> So far I've downloaded a 'fresh' copy of the utility, cold-started the
> system, and reviewed the process.
>
> I'm not particularly computer-literate when it comes to this new-fangled
> stuff and I'm becoming less enthusiastic every day ;-)
> (Gimme a System 360/Mod 67, a bank of 2400 bpi tapes, and assembler
> language any day!)
>
> Any suggestions would be appreciated.  My gut feel is that it's in the
> K3.  The sudden cessation of communication with HRD for no apparent
> reason makes me think this way.
>
> 73, Stan WB2LQF
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>