Elecraft

K3 comatose

Classic

List

Threaded

6 messages Options

GW0ETF

K3 comatose

Forgot I still had a telnet session open while doing a 1.68 to 1.69 MCU
firmware upload; the upload failed and everything stopped responding, no
communication between the K3 upload facility etc. The power button did
nothing so eventually had to turn off the power supply; turning back on
and then doing a 'Parameter Initialization' (page 55 ) powered up the
radio but it is stuck in 'MCU LD'. In the words of Monty Python - "This
is a dead K3"

I'm sure it's just in a coma and wonder if anyone here knows how to
resuscitate prior to Aptos waking up; maybe I should play some music to
it, always thought the K3 would be a Frank Zappa sort of radio.....
There must be contingency plans for repairing wiped out firmware such as
would happen if a power cut occurred mid way through a re-flash so I'm
not panicking (yet).

This is always assuming the problem was caused by a serial port
contention of some sort.......I'd closed the ports in Logger32 but still
had the telnet open though not that sure why that would interrupt the PC
to K3 comms.....

Stewart Rolfe, GW0ETF
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

Ken Wagner K3IU

Re: K3 comatose

Have you tried the Help menu item in the K3 Utility Program? Here is one
thing is suggests...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Forcing the K3 into "firmware load required" mode

To force the K3 into a state that it requires a firmware download,

* Unplug the K3 from its power supply for at least 5 seconds.
* Plug the power supply back in.
* Press and hold the K3's power switch in for about 10 seconds until
the red TX LED begins to flash.
* Click "Check Versions Now" on the Firmware page.
* Click "Send All New Firmware".

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
73, Ken K3IU

Stewart Rolfe wrote:

> Forgot I still had a telnet session open while doing a 1.68 to 1.69
> MCU firmware upload; the upload failed and everything stopped
> responding, no communication between the K3 upload facility etc. The
> power button did nothing so eventually had to turn off the power
> supply; turning back on and then doing a 'Parameter Initialization'
> (page 55 ) powered up the radio but it is stuck in 'MCU LD'. In the
> words of Monty Python - "This is a dead K3"
>
> I'm sure it's just in a coma and wonder if anyone here knows how to
> resuscitate prior to Aptos waking up; maybe I should play some music
> to it, always thought the K3 would be a Frank Zappa sort of radio.....
> There must be contingency plans for repairing wiped out firmware such
> as would happen if a power cut occurred mid way through a re-flash so
> I'm not panicking (yet).
>
> This is always assuming the problem was caused by a serial port
> contention of some sort.......I'd closed the ports in Logger32 but
> still had the telnet open though not that sure why that would
> interrupt the PC to K3 comms.....
>
> Stewart Rolfe, GW0ETF
> _______________________________________________
> Elecraft mailing list
> Post to: [hidden email]
> You must be a subscriber to post to the list.
> Subscriber Info (Addr. Change, sub, unsub etc.):
> http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/subscribers.htm
> Elecraft web page: http://www.elecraft.com
>

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

dj7mgq

Re: K3 comatose

In reply to this post by GW0ETF

Hi Stewart,

> I'm sure it's just in a coma and wonder if anyone here knows how to
> resuscitate prior to Aptos waking up; maybe I should play some music to
> it, always thought the K3 would be a Frank Zappa sort of radio.....
> There must be contingency plans for repairing wiped out firmware such
> as would happen if a power cut occurred mid way through a re-flash so
> I'm not panicking (yet).

Try doing this:
================================================
Forcing a Firmware Download

If you accidentally load an old or incompatible
firmware version and find the K3 unresponsive, do
the following:

(1) unplug the K3 from the power supply and wait 5 seconds;

(2) plug the power supply back in;

(3) hold the K3?s POWER switch in; after about 10 seconds, you?ll see
the TX LED flash (you?ll also see MCU LD on the LCD);

(4) load the correct firmware version.
================================================
From page 42 of K3 Owners Manual C1.pdf

vy 73 de toby
--
Delta Delta 5 Frank Zappa

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

GW0ETF

Re: K3 comatose - sorted, thanks

[hidden email] wrote:

> Hi Stewart,
>
>> I'm sure it's just in a coma and wonder if anyone here knows how to
>> resuscitate prior to Aptos waking up; maybe I should play some music to
>> it, always thought the K3 would be a Frank Zappa sort of radio.....
>> There must be contingency plans for repairing wiped out firmware such
>> as would happen if a power cut occurred mid way through a re-flash so
>> I'm not panicking (yet).
>
>
> Try doing this:
> ================================================
> Forcing a Firmware Download
>
> If you accidentally load an old or incompatible
> firmware version and find the K3 unresponsive, do
> the following:
>
> (1) unplug the K3 from the power supply and wait 5 seconds;
>
> (2) plug the power supply back in;
>
> (3) hold the K3?s POWER switch in; after about 10 seconds, you?ll see
> the TX LED flash (you?ll also see MCU LD on the LCD);
>
> (4) load the correct firmware version.
> ================================================
> From page 42 of K3 Owners Manual C1.pdf
>
> vy 73 de toby

Toby and Ken,

I tried a 'Force Firmware Download' but got the response from the K3
Utility of no response from the K3. Then I remembered I use a virtual
com port via my Microham cw keyer and the usb router; this normally
works fine but I tried a direct hardware comm port connection and the
'forcing' worked....! so all is well now and many thanks for the quick
responses to you both.

Presumably the interruption screwed the virtual com port software
interface while leaving the hardware port unscathed. I've just
reconnected the Microham and reset the port settings and all is back to
normal between the radio and upload utility.

73,

Stewart, GW0ETF
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

Greg - AB7R

Re: K3 comatose - sorted, thanks

Stewart,

I also use a Microham device (MK2R+). Click SETUP for the radio port on the PORTS
tab. Set the radio to NONE and disable querries. Save the configuration as
something like "K3 Firmware". Now it should work fine. It may be a little slower
than a straight native COM port, but it has worked fine for me for the past 4
months or so.

Now whenever I need to update, I just click that preset and there's no problems.

-------------------------
73,
Greg - AB7R
Whidbey Island WA
NA-065
K3#0009

On Thu Feb 21 4:58 , Stewart Rolfe sent:

>[hidden email] wrote:
>> Hi Stewart,
>>
>>> I'm sure it's just in a coma and wonder if anyone here knows how to
>>> resuscitate prior to Aptos waking up; maybe I should play some music to
>>> it, always thought the K3 would be a Frank Zappa sort of radio.....
>>> There must be contingency plans for repairing wiped out firmware such
>>> as would happen if a power cut occurred mid way through a re-flash so
>>> I'm not panicking (yet).
>>
>>
>> Try doing this:
>> ================================================
>> Forcing a Firmware Download
>>
>> If you accidentally load an old or incompatible
>> firmware version and find the K3 unresponsive, do
>> the following:
>>
>> (1) unplug the K3 from the power supply and wait 5 seconds;
>>
>> (2) plug the power supply back in;
>>
>> (3) hold the K3?s POWER switch in; after about 10 seconds, you?ll see
>> the TX LED flash (you?ll also see MCU LD on the LCD);
>>
>> (4) load the correct firmware version.
>> ================================================
>> From page 42 of K3 Owners Manual C1.pdf
>>
>> vy 73 de toby
>Toby and Ken,
>
>I tried a 'Force Firmware Download' but got the response from the K3
>Utility of no response from the K3. Then I remembered I use a virtual
>com port via my Microham cw keyer and the usb router; this normally
>works fine but I tried a direct hardware comm port connection and the
>'forcing' worked....! so all is well now and many thanks for the quick
>responses to you both.
>
>Presumably the interruption screwed the virtual com port software
>interface while leaving the hardware port unscathed. I've just
>reconnected the Microham and reset the port settings and all is back to
>normal between the radio and upload utility.
>
>73,
>
>Stewart, GW0ETF
>_______________________________________________
>Elecraft mailing list
>Post to: [hidden email]
>You must be a subscriber to post to the list.
>Subscriber Info (Addr. Change, sub, unsub etc.):
> http://mailman.qth.net/mailman/listinfo/elecraft
>
>Help: http://mailman.qth.net/subscribers.htm
>Elecraft web page: http://www.elecraft.com

Joe Subich, W4TV-3

RE: K3 comatose - sorted, thanks

> Click SETUP for the radio port on the PORTS tab. Set the
> radio to NONE and disable querries.

It is not necessary to do both. Setting the radio type to
"none" will disable the polling completely.

73,

... Joe Subich, W4TV
microHAM America
http://www.microHAM-USA.com
http://groups.yahoo.com/group/microHAM
[hidden email]

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Greg - AB7R
> Sent: Thursday, February 21, 2008 11:32 AM
> To: [hidden email]; Stewart Rolfe
> Cc: elecraft reflector
> Subject: Re: [Elecraft] K3 comatose - sorted, thanks
>
>
> Stewart, I also use a Microham device (MK2R+). Click SETUP
> for the radio port on the PORTS tab. Set the radio to NONE
> and disable querries. Save the configuration as something
> like "K3 Firmware". Now it should work fine. It may be a
> little slower than a straight native COM port, but it has
> worked fine for me for the past 4 months or so. Now
> whenever I need to update, I just click that preset and
> there's no problems. ------------------------- 73, Greg -
> AB7R Whidbey Island WA NA-065 K3#0009 On Thu Feb 21 4:58 ,
> Stewart Rolfe sent: >[hidden email] wrote: >> Hi
> Stewart, >> >>> I'm sure it's just in a coma and wonder if
> anyone here knows how to >>> resuscitate prior to Aptos
> waking up; maybe I should play some music to >>> it, always
> thought the K3 would be a Frank Zappa sort of radio..... >>>
> There must be contingency plans for repairing wiped out
> firmware such >>> as would happen if a power cut occurred mid
> way through a re-flash so >>> I'm not panicking (yet). >> >>
> >> Try doing this: >>
> ================================================ >> Forcing a
> Firmware Download >> >> If you accidentally load an old or
> incompatible >> firmware version and find the K3
> unresponsive, do >> the following: >> >> (1) unplug the K3
> from the power supply and wait 5 seconds; >> >> (2) plug the
> power supply back in; >> >> (3) hold the K3?s POWER switch
> in; after about 10 seconds, you?ll see >> the TX LED flash
> (you?ll also see MCU LD on the LCD); >> >> (4) load the
> correct firmware version. >>
> ================================================ >> From page
> 42 of K3 Owners Manual C1.pdf >> >> vy 73 de toby >Toby and
> Ken, > >I tried a 'Force Firmware Download' but got the
> response from the K3 >Utility of no response from the K3.
> Then I remembered I use a virtual >com port via my Microham
> cw keyer and the usb router; this normally >works fine but I
> tried a direct hardware comm port connection and the
> >'forcing' worked....! so all is well now and many thanks for
> the quick >responses to you both. > >Presumably the
> interruption screwed the virtual com port software
> >interface while leaving the hardware port unscathed. I've
> just >reconnected the Microham and reset the port settings
> and all is back to >normal between the radio and upload
> utility. > >73, > >Stewart, GW0ETF
> >_______________________________________________ >Elecraft
> mailing list >Post to: [hidden email] >You must be
> a subscriber to post to the list. >Subscriber Info (Addr.
> Change, sub, unsub etc.): >
> http://mailman.qth.net/mailman/listinfo/elecraft > >Help:
> http://mailman.qth.net/subscribers.htm >Elecraft web page:
> http://www.elecraft.com
> _______________________________________________
> Elecraft mailing list
> Post to: [hidden email]
> You must be a subscriber to post to the list.
> Subscriber Info (Addr. Change, sub, unsub etc.):
> http://mailman.qth.net/mailman/listinfo/elecraft
>
> Help: http://mailman.qth.net/subscribers.htm
> Elecraft web page: http://www.elecraft.com