Documentation Discussion

Ok, translation reasons.
What about a small graphic arrow cross instead of the word? Just to save some space and moved near to the Y.

PhracturedBlue wrote:

kreidler wrote:

PhracturedBlue wrote: Lastly. I'm currently working on redoing the build system. I'll likely set it up so the filesystem and dfu (or exe for the emulator) are included in one zip file, with the emulator ready to go.

Perfect, will wait for it.

I just added this.
However, I am not going to change the way nightlies are built. Most folks updating nightlies replace just the dfu without the FS on a frequent basis.
The official builds will now include the fs at the root directory (and the emu will have it in the filesystem/<target>/ dir.
Here are some examples (note that the emulator was built for linux and so likely isn't useful except to see the layout)

DFU:

File Attachment:

File Name: deviation-...7f3d.zip
File Size:756 KB

Emulator:

File Attachment:

File Name: deviation-...bf67.zip
File Size:771 KB

sorry full quote. I do have my mobile with me.
Fully understood, good idea, will simplify the installation process. I will update the manual accordingly. Assuming protocol directory is included in Devo7e zip.

kreidler wrote: Assuming protocol directory is included in Devo7e zip.

i just built the latest code and it looks like the 7e still builds in the old manner with seperate zips for the fs and the dfu/debug

Just pulled in kreidler's last pull request and created a new PDF for review. The PDF is in the downloads of my Bitbucket repo and the source is up to date as of 23:31 GMT-5

I did fix a couple of image scaling issues and crop margins.

Bud

PB, I added the stuff about telemetry for DSM and images, I fixed the image for the layout display to show your cute arrows and the correct placement of the Battery / Power. But I am a noob to Bitbucket, I just wanted to pull the .fodt file but it pulled three other files along with it. I don't know what I did wrong or how to fix it.

I apologize if this just made you more work then necessary.

I also have a question about the Layout, all the boxes are sequentially numbered except for Model (which is named) yet the Battery and Power are both numbered 1. Was this intentional, it makes it harder to know which box you are moving and when I redid my personal layout I actually had to configure it twice since I moved the boxes into the incorrect positions.

PhracturedBlue wrote: As far a battery/power layout, it isn't intentional, but I don't know if I'll get it fixed before the next release. Options are limited due to the micro-font having a reduced character set, so I can't label them as 'Power' and Battery'

...

Could they just use the next two numbers in sequence?

At the moment the Devo10manual looks a bit destroyed. Some manual breaks seems to be displaced or missing. For the new installation I did a new image which had not been transferred in the actual version. Without this picture the sense of the description is at least a bit confusing because the dfu etc have been included in all builds. Please reconsider and come back if I shall improve the optic:).

PhracturedBlue wrote: As I said, trying to merge changes is a pain.

I know......

Regarding image I do not know if you mean something like this: I you do a drag and drop into a copied old image the new one gets the size of the old one. If the height is different change the percentage via the properties. That's my way.

You left the line numbers on and it shows in the PDF

Some minor things:

Batt alarm default for 7e is missing (4.10V). Default for Devo 10 (8.00V) is shown on the image.

I cannot generate an image via the emu for the Safe Value screen which appear on an incorrect setting while loading another model. Afaik changing or adding different control could be realised atm via editing the ini file only. But in general an image with some words might be helpful. E.g. this a safety warning only or transmission will be initiated after resolving this screen.

Off-topic: In the source the heli_std.ini do have a layout section which is ignored when loading the template. The part could be removed.