True, true, but ---
Ideally, that saved configuration file should be one that was obtained
before the problem came up.
If a configuration file is generated right before the EEINIT, the same
problem may be re-loaded afterwards.
Of course, whether that is true or not depends on the type of failure.
73,
Don W3FPR
On 1/25/2013 8:26 AM, Lee Trout wrote:
Larry:
Over the years I have had several intermittent, seemingly inexplicable
problems with the K3 that have been solved simply by doing a EEINT (see K3
manual) and a reload of the firmware. If you haven't found a hardware
problem, this may be worth a try since it doesn't take long to do. Just be
sure to save your configuration before you do the EEINT so you can reload
your settings after, and use the SEND ALL FIRMWARE TO THE K3 in the utility.
Lee, K9CM
______________________________________________________________
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
