Documentation Discussion

You can use 'compare document' to compare 2 versions of the manual to make it easier to see what has changed.

Please do not add chapter numbers. As long as you use references, we can easily reformat at the end to say 'page 5' or whatever. If you manually add chapter numbers we need to manage them by hand.

The Advanced GUI should be 1st in the manual. The default interface is 'Advanced' and we generally encourage its use.

Yes, what you've done there looks fine.
Now that I have my X9D, I'd like to start working on development for it, which means I want to get the current release done. On top of that, I'll have more free time over the next 2 weeks then I've had in a long time. So I'm going to actively try to get the documentation done over the next week or so. That means I'll probably take a copy of wherever you guys are, port it to the devo8/12 and call that good enough for the next release. If you have further improvements, we can always make future documentation releases.

kreidler wrote: PB, please forgive me but I changed the version number on the first page

Please don't.
It makes it too easy for someone to mistake unfinished documentation. When I'm ready I will update it apropriatly.

kreidler wrote: I have not had the time that I needed...
Nevertheless I did some sorting, removing, rewriting, etc. Additionally I noticed that still some screens missed.

Paragraph 175: this is not true. Alternate templates can be loaded, to change the layout, but there is no layout editor available in the firmware. The templates can be created in the emulator or downloaded from the forums.
Paragraph 365: The prepositional phrase is too long. Split into 2 sentences.
Paragraph 880:
*****
The datalog feature allows storing a history of input or output positions as well as telemetry info over a period of time. This can be used to examine and replay a flight as well as to visualize telemetry information at a later time. Logs are persistent and Deviation will continue writing tothe end of the previous log by default.

Note: There is currently no software provided to analyze the logs, and they cannot be visualized from within the transmitter. This is a feature for advanced users only.

* bytes left: indicates how many bytes can be written to the log before it is full
* Enable: input which enables logging.
* Reset: clear the current log.
* Rate: how often to write current info to the log file
* Select: Quickly set or reset which items are logged.
* Controls: Following 'Select' are a list of all controls which may be logged. They include timers, inputs, outputs, and virtual channels, and Telemetry. the more items logged the faster the log wil fill up.

Logging more information
By default, the log can only store 16kB of data. This can be increased by updateingthe datalog.bin file on the transmitter to be a larger size. Deviation cannot increase the size of this file, so its size indicates the maximum data that can be stored.
*****

That is as far as I've gotten. I still need to read through the standard mixer stuff, but the manual is definitely looking good to me.

Thanks.

A couple small points:
200 the image I put in to show the different spinboxes. We need a comparable one showing what they look like when highlighted like this:



990
(Devo7e stuff) should move up to 980. It is always better to tell people ahead of time that what they are about to read doesn't apply to them. We could also move it up to 925. I'm not sure which is better.
The same goes for 920

Between 8.7.1 and 8.7.2 we need to describe the 'Load' button and get a picture of the Load screen

As for the datalog, I have a script in the source-code called datalog2csv.py (which could be compiled to an executable for Windows users to convert the data into a more generic format. If I put it in the downloads section, that is probably enough