[Elecraft] Notes on beta firmware

[dmoes at nexicom.net]

Im sort of a don't fix what ain't broke.    From time to time I look at the updates to see if there is anything jucy or effect‎s my operation and only do the updates then   why update firmware if it offers nothing to my personal operations. 

 One thing about this Beta update is the Fixed level on TX monitor to the line out.      One thing I didn't  like is that the line out was tied to the front panel monitor level and when recording messages or recording QSOs. The level would be low as I kept the monitor low at least for Phone.    It would be nice if the monitor level in future to the line out is independent from the front panel contol.  

  Original Message  
From: Don Wilhelm
Sent: Sunday, October 2, 2016 6:32 PM
To: dmoes at nexicom.net
Reply To: donwilh at embarqmail.com
Cc: elecraft at mailman.qth.net
Subject: Notes on beta firmware

David and all,

You might want to check the Firmware page of the Elecraft website 
frequently to keep up with updates. Look at the release notes for both 
the production and beta firmware to see if there is anything that 
interests you - if so, download it.

There are several on this reflector who are not familiar with the 
difference between Elecraft production firmware and beta firmware, and 
many are reluctant to install beta firmware.

IMHO, beta firmware is just as good as production level, but has not had 
as much testing by customers who bring to the plate the variety of 
configurations possible - different loggers and control applications 
working in concert with the radio and remote control applications that 
pose additional potential for unforeseen problems to crop up. Releasing 
beta versions to customers allows that firmware to be tested under a 
variety of conditions that are not possible by a select few early testers.

There is no fixed time between a beta release and when it is promoted to 
production level at Elecraft. If there is a flurry of customer requests 
for a new function, it can be a matter of days, but if there is not a 
high demand for the new or improved functions, it can be weeks. If you 
want the new function or problem fix, download and install the beta 
version.

If you want a function that is included in the beta version, go ahead 
and download it, unzip and install it in your K3 (or K3S, KX3, KX2). If 
you encounter a problem, report it and revert to the production level or 
whatever level you have saved on your computer. Yes, it is just that easy.

As far as firmware levels go, the revision level will remain the same if 
the beta version is promoted to production level - in other words, if 
revision 5.54 is determined to be adequate for production, it will still 
be revision 5.54.
This production/beta revision there is a perfect example of the revision 
numbering. The production level is 5.50, but the current beta is 5.54. 
What happened to 5.51, 5.52 and 5.53?
Those versions were released as beta, but either there was a problem 
reported by some of the early users, or it was further modified to add 
some additional function. Since the current beta is 5.54, it will be 
the one advanced to production level unless it is succeeded by a higher 
beta revision. Revisions 5.51, 5.52 and 5.53 will not ever be 
production level. In other words, if 5.54 needs to be "fixed", the 
fixed version will be higher than 5.54.

There should be no fears about beta firmware "breaking your radio" 
because it has been initially tested in-house and by Firmware Field Testers.

I am surprised that the TX monitor out of LINE OUT was not discovered 
between MCU 5.40 and 5.50. My only conclusion is that those who used 
that function did not upgrade and observe the absence.

An additional comment - use the firmware release notes to update your 
list of menu functions in the manual - for instance, MCU 5.40 added an 
option to the menu list for PA TEMP.

73,
Don W3FPR

On 10/2/2016 10:20 AM, dmoes at nexicom.net wrote:
>
> That explains it. I must have missed a few updates.
>
> David Moes
> VE3SD