Same here...
73
Stewart G3RXQ
On Sun, 06 Feb 2011 16:52:15 -0500, Dan Atchison wrote:
With all the email traffic on the K3 and the microKEYER II / updating
software, I felt compelled to respond.
I have the K3, the P3, and the microKEYER II. For the past two years I
have used the microKEYER
In the 3 years of running my K3 I can only remember once having to do a
forced reload and it was completely straightforward.don't understand the
stress this seems to generate.
Since moving to a netbook recently I've been rebooting my desktop every time
I wanted to do a firmware upload using
This discussion of the firmware updating process brings to mind the
phrase under-engineered.
Too bad this problem doesn't also cause a short first dit at 80 wpm,
in which case I'm sure it's remedy would be a top priority for Elecraft.
73 Jack KZ5A
On 2/6/2011 6:02 PM, Dick Dievendorff
As long as the Win 7 user does not understand how the OS handles USB
devices, there will always be folks tripping over this opaque procedure in
Windows. The drill is anything but intuitive, but if the user does not
understand it, the use of complex combinations of loggers, data mode
programs,
Well said !
73
Stewart G3RXQ
On Mon, 7 Feb 2011 12:02:05 -0500, Guy Olinger K2AV wrote:
As long as the Win 7 user does not understand how the OS handles USB devices,
there will always be folks tripping over this opaque procedure in Windows.
The drill is anything but intuitive, but if the
Subject: Re: [Elecraft] Fwd: K3 Failed DSP Firmware Download
My first time FW upgrade failed too. The problem? I use Router a
virtual port defining piece of software microHAM uses for their
product's interfaces to such things as the microKEYER II.
In their manual is a warning in Yellow
Dan,
Please do not distribute instructions that directly contradict the
warning included in the User's Manual for every microHAM product.
While you may have been lucky to avoid a negative outcome, that can't
be guaranteed. Neither microHAM nor microHAM America, LLC (and I doubt
Elecraft) can
Craig's problem brings up a question. If, for whatever reason, one or more of
the downloaded firmware files is corrupted, do you need to delete all the
downloaded files from your computer, do a new download from Elecraft so that a
reload doesn't just grab the corrupted file again? Thanks, Lee
Don and all,
It isn't the K3 utility's problem either.
Just how is the utility's supposed lack of robustness affect the
connection between radio and computer? It doesn't.
The entire planet has been sold a bill of goods concerning laptops,
mostly because of the gee whiz factor. They are
Craig,
The last few times I have attempted downloads to my K3 they failed and
it took a few days to get it running again.
I've ended up having to remove the K3 from my station setup, and put it
on my work bench where I have a Vintage PC with a native serial port.
Baring the remote possibility
I would.
I don't now the inner workings of the utility but I assume there's
something built in to check file integrity before the upgrade process.
If not then that would be something to seriously think about adding.
Easy enough to check MD5sums.
On Sun, 6 Feb 2011 07:55:15 -0500
Lee Trout
It seems to be very few people that have a problem updating firmware.
And it's amazing that it still gets blamed on the Utility, the radio, file
integrity, whatever. Of course it could be any of these, but that isn't nearly
as likely as a broken USB/RS232 driver. Most of us have never had a
On 2/6/11 8:47 AM, R. Kevin Stover wrote:
Don and all,
It isn't the K3 utility's problem either.
Just how is the utility's supposed lack of robustness affect the
connection between radio and computer? It doesn't.
The actual connection, no. BUT, K3 utility's lack of robustness DOES
allow the
Each of the firmware files is checked for line by line checksum validity and
the presence of a file end record during FTP (which isn't used in the Beta
unzip process) and the firmware files are read into the PC's RAM and similarly
verified before initiating firmware load. We don't access the
Grant,
On 2/6/2011 8:20 AM, Grant Youngman wrote:
It seems to be very few people that have a problem updating firmware.
Hardly a day goes by that there is not at least one firmware download
problem string running on the reflector.
And it's amazing that it still gets blamed on the Utility,
On Sun, 06 Feb 2011 09:36:59 -0600
Jack Brabham k...@att.net wrote:
Jack,
Hardly a day goes by that there is not at least one firmware
download problem string running on the reflector.
Most of which turns out are caused by USB to Serial adapters,
Those using real serial reports very rarely
I am not disputing your point, but want to add that the USB-serial adapters I
have had, 3 different types, were prone to lightning damage if not
disconnected. I have suffered damage to a serial port, too, over 25 years ago
when the discrete driver chips were replaceable. But not in 10 years
On 2/6/2011 8:40 AM, K9ZTV wrote:
On 2/6/2011 7:49 AM, Jack Brabham wrote:
Baring the remote possibility that Elecraft comes up with a more
sophisticated system for doing these down loads, my plan is to limit
doing these in the future to about once a year, due to their being such
a PITA.
the plumbing, the easier it is to stop up the
drain.
-lu- W4LT
K3 #3192
Message: 3
Date: Sun, 06 Feb 2011 07:49:15 -0600
From: Jack Brabham k...@att.net
Subject: Re: [Elecraft] Fwd: K3 Failed DSP Firmware Download
To: elecraft@mailman.qth.net
Message-ID: 4d4ea6db.3060
My first time FW upgrade failed too. The problem? I use Router a
virtual port defining piece of software microHAM uses for their
product's interfaces to such things as the microKEYER II.
In their manual is a warning in Yellow to not perform FW upgrades via
the microKEYER II interface which
9:46 AM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] Fwd: K3 Failed DSP Firmware Download
I see posts like these often here, and (knock on wood) I have *never*
experienced any problem whatsoever in loading firmware into my K3 (#3192)
since I have owned it. I dont understand why
Don et al,
This is a follow up to my original post, and will hopefully help others
in this similar situation.
I went to the Elecraft website and read the KUSB serial to USB driver
notes, which I originally failed to do. I then went to the FTDI
website, located the correct driver, and found
My first time FW upgrade failed too. The problem? I use Router a
virtual port defining piece of software microHAM uses for their
product's interfaces to such things as the microKEYER II.
In their manual is a warning in Yellow to not perform FW upgrades via
the microKEYER II interface which
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] Fwd: K3 Failed DSP Firmware Download
My first time FW upgrade failed too. The problem? I use Router a
virtual port defining piece of software microHAM uses for their
product's interfaces to such things as the microKEYER II.
In their manual
On 2/6/2011 10:23 AM, Ron D'Eau Claire wrote:
Good observation about the plumbing Lu. I'll remember that. Even though the
K3 is an amazing bit of technology, sometimes I long for the rough
simplicity of the homebrew station I started out with years ago, Hi!
I don't. Right after I retired in
@mailman.qth.net
Subject: Re: [Elecraft] Fwd: K3 Failed DSP Firmware Download
The radio queries can be disabled in the microHAM USB Device
Router if you go to the ports tab and click the SET button for the
CAT port you will get a new screen the has a check box for Disable
router queries. If you are brave
Craig and all,
Dick has indicated several times that the firmware does have checking
data bits, and they are used for validity checks and as an indication
that the firmware downloads are successful.
What is happening in the discussion that has ensued is that the MicroHam
device is adding
On 2/6/11 3:36 PM, Don Wilhelm wrote:
I do not know how any additional degree of robustness in K3 Utility
could correct for that condition.
Simple... Don't write ANYTHING to the K3 EEPROM (I assume) until the K3
has received the ENTIRE firmware file w/o errors. Blocks with errors can
always
The PIC18F8722 microcontroller used has 128KB of flash program memory and a bit
less than 4KB of RAM. Its a Harvard architecture machine, not the Von Neumann
model. Your simple suggestion is infeasible. There is no place on chip to
buffer the firmware in its entirety.
Dick, K6KR
On Feb 6,
.
73,
- Craig, AE6RR
-Original Message-
From: elecraft-boun...@mailman.qth.net
[mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Dick Dievendorff
Sent: Sunday, February 06, 2011 1:08 PM
To: n...@aiko.com
Cc: Elecraft; d...@w3fpr.com
Subject: Re: [Elecraft] Fwd: K3 Failed DSP Firmware
...@mailman.qth.net
[mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Dick Dievendorff
Sent: Sunday, February 06, 2011 1:08 PM
To: n...@aiko.com
Cc: Elecraft; d...@w3fpr.com
Subject: Re: [Elecraft] Fwd: K3 Failed DSP Firmware Download
The PIC18F8722 microcontroller used has 128KB of flash program
Hi all,
I have loaded virtually every firmware version that ever came out without a
single incident, using several different USB adapters (never had a real
serial port with the K3) and several computers. So I don't have problem with
this at all. With this said, it does appear that a few things
From what I have been reading about the protocol used, it seems it is not at
all robust. Someone else said this as well. The ACKs and NAKs are a good
start. These are at times being lost it appears. The utility should have a
timer that lets it resend a frame if there is not ACK or NAK that gets
Dick
On Feb 6, 2011, at 15:08, Dick Dievendorff die...@comcast.net wrote:
The PIC18F8722 microcontroller used has 128KB of flash program memory and a
bit less than 4KB of RAM. Its a Harvard architecture machine, not the Von
Neumann model. Your simple suggestion is infeasible. There is no
The serial communications are tested before sending firmware. There is a per
block checksum test and Ack. There is no on chip storage of sufficient to
buffer very much firmware. The program store is 128KB and the available RAM is
less than 4K.
I can work on the error messages, and specific
Hmmm..seems like this failed FW load is caused by operator
forgetfullness..don't think that's a word...by owners of Microham
products.
I sure don't need windoze' to remind me to turn something off or
check some other device is present and running etc, etc, etc.
Maybe I live in the dark ages in
I needed to make a real rs232 cable to get mine to work nbsp;
The usb adaptors don't work very well including the ones elecraft sell.
It's time to work on robustness on the loader instead on new features.
This is a problem that will damage the K3 reputation if it is not addressed.
nbsp; As
Craig,
If you are able, try using a real serial port on a desktop computer if
you are able - no adapter drivers to confuse the issue. I use a real
serial port and have done many firmware upgrades. The only time I had a
problem was when I pushed a button during the upgrade process (that was
Don,
I have trouble blaming the problem on the K3 when the real problem lies
with the Operating System and properly operating drivers (or lack
thereof) for the USB to serial adapters.
Use of a desktop computer for the hamshack is quite desirable IMHO -
mine sits under the desk and the
Thanks for the input, Don.
I deleted the old firmware file in my local folder, and reloaded just
the latest DSP files. Worked perfectly. I really don't think the USB
cable is the issue. Anyway, I'm a happy camper!
Craig W6WL
On 2/5/2011 7:07 PM, Don Wilhelm wrote:
Don,
I have trouble
Craig,
I am glad to hear you had success.
Unfortunately, many of similar problems are OS and USB to serial driver
related. The USB cable itself is not the problem, but the available
drivers to support it for the various OS versions seems to be the
biggest problem.
From my recall, the
41 matches
Mail list logo
