[Elecraft] Proposal for change pages for manuals

[W2xj]

What you are advocating is a federal government style of documentation. It doesn’t come cheap. How much more would you be willing to pay for products to support a vastly increased Elecraft documentation team? 

Sent from my iPad

> On May 23, 2019, at 9:23 PM, N4ZR <n4zr at comcast.net> wrote:
> 
> I wasn't suggesting that Elecraft "issue a new manual" with every firmware release, just that it institute a "change page" system. Currently the K3 documentation is confused at best.  According to the release notes, the latest MCU is 4.77, but my radio was back to the factory early this year, and it now reports an installed MCU version of 5.66.  Oddly, though, the K3 Utility says that 4.67 is still the latest available.  There are similar discontinuities in the FPF and DSP firmware. So I have absolutely no idea what's changed in my radio.
> 
> 73, Pete N4ZR
> Check out the Reverse Beacon Network
> at <http://reversebeacon.net>, now
> spotting RTTY activity worldwide.
> For spots, please use your favorite
> "retail" DX cluster.
> 
>> On 5/23/2019 4:14 PM, Don Wilhelm wrote:
>> Pete,
>> 
>> If you download the newest manual, you will have the most up to date information that is printed in the manual.
>> 
>> Above and beyond that (and equally important), you should pay attention to the Firmware Release Notes.  They are on the website and also included on the K3 Utility Help Tab.
>> Those Firmware Release changes also constitute changes/additions to whatever level manual you have.  So if you mark up you manual starting with each firmware release after the date in the manual, you will have all the information in the manual.
>> 
>> I don't think it is practical for Elecraft to issue a new manual with each firmware release.
>> 
>> 73,
>> Don W3FPR
>> 
>> 
>>> On 5/23/2019 3:55 PM, N4ZR wrote:
>>> One of the nice things about Elecraft gear is the continuous improvement that goes on, even years after initial release.  Unfortunately, these improvements are often only documented at release time, and nine years' worth (in my case) is hard to organize.
>>> 
>>> Recently, I ran into issues with my middle-aged K3 that turned out to be caused by a change in functionality  undocumented in my manual from 2010, which I inadvertently triggered.
>>> 
>>> Why wouldn't it be possible to put someone to work identifying which pages in each manual have been changed or added and then producing "change pages" that we could print out and insert - for example a new page 6, and pages 6a, 6b etc., as needed to bring the manual back in sync with the