That is sometimes required, but not always.
Only if the K3S or K3 with the KIO3B does not respond to the USB
connection, then that can be used as a last resort.
Often the problem is simply that the computer does not clearly identify
the COM port associated with the K3 USB connection. If that is the
problem, I can help with identifying the proper COM port to put into K3
Utility.
73,
Don W3FPR
On 1/24/2019 3:41 PM, RIchard Williams wrote:
Bob,
If you are trying to use the USB port after a failed firmware update,
you need to either use the RS-232 port or take the top cover off and
the change the little switch on the board (can't remember the name of
it) the USB and RS 232 ports are on to USB position. The you can use
the USB port for a forced download. After you are done, move the
switch back to the other position.
Dick, K8ZTT
Sent from Yahoo Mail on Android
<https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>
On Thu, Jan 24, 2019 at 13:34, Don Wilhelm
<donw...@embarqmail.com> wrote:
Bob,
Since you had an ERR PTT indication in the midst of all this,
unplug all
cables except the USB cable and the Power Cable. Connect ANT1 to a
dummy load.
Then open K3 Utility and open its Help file. Look for "Force a
Firmware
Download" and follow those instructions (the instructions are also in
the manual).
After you are again up and running, plug each of your cables in
one at a
time and recycle power after each cable. If you see an ERR PTT,
investigate that cable. It could be as simple as a closed paddle
or key
contact, or a mic cable that has PTT stuck on. Or it could be more
complicated depending on what else you have in your station.
ERR PTT means that either a key or a mic PTT closure was detected
when
the K3 was turned on.
73,
Don W3FPR
On 1/24/2019 3:03 PM, Bob DeHaney wrote:
> Trouble started with no reception on 14 or 24 mHz. Reloaded
configuration file which got reception back, but had a continuous
ERR PTT. Attempted a complete firmware reload. K3 hung at MCU LD
with all buttons inoperative. I then tried the recovery procedure
in the K3 Utility Help section. The K3 comes on without
backlight, and transmit blinking and MCU LD in the display. The
K3 Utility cannot open the port. I’m stuck. This K3 has all K3S
upgrades including USB, etc. I have also tried rebooting the
computer with and without USB connected.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
<mailto:Elecraft@mailman.qth.net>
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to richarddw1...@yahoo.com
<mailto:richarddw1...@yahoo.com>
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com
