[Elecraft] K3 problem with logging program after download upgrade

[Dick Dievendorff]

No, that sounds like you got a bad file from the Elecraft file server.  I'd
recommend erasing the hmcu*.hex file and re-do the "Copy files from
elecraft".  If you open the hex file in Notepad, every line should start
with a colon.

73 de Dick, K6KR


-----Original Message-----
From: elecraft-bounces at mailman.qth.net
[mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Ken Kopp
Sent: Monday, December 03, 2007 9:52 PM
To: elecraft at mailman.qth.net
Subject: Fw: [Elecraft] K3 problem with logging program after download
upgrade

Could this account for the "Intel Hex file ran out of bytes before Intel
End file record was read" -and- "Intel Hex Read error: Expected start
characher ":" not found" messages when attempting (unsuccessfully)
to load the new upgrade into my K3?

73! Ken Kopp - K0PP
k0pp at arrl.net



----- Original Message ----- 
From: Don Rasmussen
To: elecraft at mailman.qth.net
Sent: Tuesday, 04 December, 2007 05:40
Subject: [Elecraft] K3 problem with logging program after download 
upgrade


Hi, Buck.

The K3 Utility attempts to communicate with the MCU initially to
establish its baud rate.  This is done by sending a small command
at each of the supported speeds. <snip>

Soapbox ON.

IMO - This is a tragic WASTE of BITS.

And this happens every time there is an update?

Calculate the number of updates over the life of the
radio, now how big is the bit bucket - remembering
ASCII is 7 bits per character plus parity plus start
bits and stop bit.

Could be some major overflow problems when folks least
expect it... 


_______________________________________________
Elecraft mailing list
Post to: Elecraft at mailman.qth.net
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