Stan:
I had a firmware download failure last night using the latest Utility. Started out OK, but totally disappeared about half way thru MCU 4.39. Got the "blank screen of Death" on the K3. The utility had started hunting for the com port it was already using. Eventually got the force-fed firmware install ( shown in Utility Help) to take on the 4th try. Think you have to shut the computer down as well as the rig before doing the force-feed. The Utility also showed a com port that was not available: perhaps this is what you ran into. Paul WB2ABD K3 #129 + ______________________________________________________________ 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 |
This really sounds more like things that have been reported here in the
past, eventually pinned on the com port that gets wings because something else hijacks the com port in mid-transfer, OR the com port has more than one item assigned to it and something else running on the computer goes for it. OR a USB port or separate USB hub is underpowered (this is exceedingly common), and the hub goes bad with more than one item attached if more than one stream is active. This last was actually true of motherboard USB ports on one motherboard, and only a separate PCI USB card, with it's drivers, and completely separate UN-shared paths to USB devices would fix it. The motherboard ports "sort-of" worked, the issue was intermittent and it drove us nuts. Cheep crap on the motherboard. What OS and version are you people running? 73, Guy. On Fri, Sep 9, 2011 at 12:07 PM, PTA_ABD <[hidden email]> wrote: > Stan: > I had a firmware download failure last night using the latest Utility. > Started out OK, but totally disappeared about half way thru MCU 4.39. Got > the "blank screen of Death" on the K3. The utility had started hunting for > the com port it was already using. Eventually got the force-fed firmware > install ( shown in Utility Help) to take on the 4th try. > > Think you have to shut the computer down as well as the rig before doing > the force-feed. The Utility also showed a com port that was not available: > perhaps this is what you ran into. > > Paul WB2ABD > K3 #129 + > ______________________________________________________________ > 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 > 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 |
Im using w7 64 and a usb to serial cable, running ok with k3 utility, and
upgraded to the latest... enviado desde mi HTC El 09/09/2011 23:47, "Guy Olinger K2AV" <[hidden email]> escribió: > This really sounds more like things that have been reported here in the > past, eventually pinned on the com port that gets wings because something > else hijacks the com port in mid-transfer, OR the com port has more than one > item assigned to it and something else running on the computer goes for it. > OR a USB port or separate USB hub is underpowered (this is exceedingly > common), and the hub goes bad with more than one item attached if more than > one stream is active. This last was actually true of motherboard USB ports > on one motherboard, and only a separate PCI USB card, with it's drivers, and > completely separate UN-shared paths to USB devices would fix it. The > motherboard ports "sort-of" worked, the issue was intermittent and it drove > us nuts. Cheep crap on the motherboard. > > What OS and version are you people running? > > 73, Guy. > > On Fri, Sep 9, 2011 at 12:07 PM, PTA_ABD <[hidden email]> wrote: > >> Stan: >> I had a firmware download failure last night using the latest Utility. >> Started out OK, but totally disappeared about half way thru MCU 4.39. Got >> the "blank screen of Death" on the K3. The utility had started hunting >> the com port it was already using. Eventually got the force-fed firmware >> install ( shown in Utility Help) to take on the 4th try. >> >> Think you have to shut the computer down as well as the rig before doing >> the force-feed. The Utility also showed a com port that was not available: >> perhaps this is what you ran into. >> >> Paul WB2ABD >> K3 #129 + >> ______________________________________________________________ >> 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 >> > ______________________________________________________________ > 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 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 |
In reply to this post by Guy, K2AV
I'm running Win7/64.
Dick D. has provided me with a new version of the K3 utility for testing that does NOT fault on my machine when I change the COM port FROM an invalid or unconnected port. This situation can arise after changing the machine configuration or the port that one is using to talk to the K3. The default COM port, which may no longer be valid, is picked up from the registry. Nothing specific was identified as being causative, but the exception is no longer thrown under those conditions. Thank to Dick for the help.
73, Stan - KR7C
|
The new version 1.4.9.9 is available on ftp://ftp.elecraft.com/tmp/K3/K3UTIL
for anyone else that would like to try it. It went to our Field Test team today. If you experience difficulty, please send me details directly. Thanks, Stan! [hidden email] 73 de Dick, K6KR -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Stan Gibbs Sent: Friday, September 09, 2011 4:58 PM To: [hidden email] Subject: Re: [Elecraft] [K3] Changing COM ports crashes latest K3 utility I'm running Win7/64. Dick D. has provided me with a new version of the K3 utility for testing that does NOT fault on my machine when I change the COM port FROM an invalid or unconnected port. This situation can arise after changing the machine configuration or the port that one is using to talk to the K3. The default COM port, which may no longer be valid, is picked up from the registry. Nothing specific was identified as being causative, but the exception is no longer thrown under those conditions. Thank to Dick for the help. ----- 73, Stan - KR7C -- View this message in context: http://elecraft.365791.n2.nabble.com/K3-Changing-COM-ports-crashes-latest-K3 -utility-tp6776473p6777693.html Sent from the Elecraft mailing list archive at Nabble.com. ______________________________________________________________ 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 ______________________________________________________________ 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 |
Free forum by Nabble | Edit this page |