[Elecraft] Parameter Initialization (EE INIT)

[Matt Zilmer]

EE INIT restores factory default settings.  You should only use it if
the K3 is misbehaving due to corruption of its stored data structures.

Wayne never mentioned it, but I'd bet even money that the initial data
structure locations (from the original design) are the same today, and
that he's added some as needed, or when the expandability of the K3
changed.  For example when the Ref Lock accessory was designed in, it
may have required some added memory and storage space.  I've had to do
firmware  designs like this a few times, to maintain backward
compatiblity with downrev hardware.

It's a really good idea to save the Config prior to EE INIT, and
probably periodically is  a good recommendation.  Then you can restore
your own settings after an EE INIT or if you (the user, general) dorks
some set up or parameter and can't figure it out easily enough.

AFAIK, only the K3 has an EE INIT function by that name.  There are
various front or back doors in all recent Elecraft transceivers for
functions like this.

73,
matt W6NIA


On Sun, 01 Jul 2012 10:34:34 -0700, you wrote:

>Configuration data, housed in non-volatile memory, is usually only cleared
>and reloaded in either of two situations:
>
>1. when a program revision alters the layout of the data.
>2. when the stored data, due to defect, causes functional problems that
>necessitate return to a known good baseline.
>
>In general is this not the case with the elecraft products?
>
>During init is ALL the variable storage written?  Or just a portion?
>
>
>WW6L
>
>
>______________________________________________________________
>Elecraft mailing list
>Home: http://mailman.qth.net/mailman/listinfo/elecraft
>Help: http://mailman.qth.net/mmfaq.htm
>Post: mailto:Elecraft at mailman.qth.net
>
>This list hosted by: http://www.qsl.net
>Please help support this email list: http://www.qsl.net/donate.html