openrcforums

The latest version of this documentation can now be found here:

viewtopic.php?f=45&t=8724

Very impressive! Thank you for putting this together. It will be very handy to refer to as I build new models in my radios.

I do note that the section on GVARS does not mention Name, Unit, Precision, Min or Max - what they are, and possible limitation on their use (ie - "precision" of 0.0, when reading a + or - 100% value will move the decimal, giving a GVAR of only 10%, etc.). Or is this a really new feature of 2.2.1, so wasn't applicable to 2.2.0?

Yes, thank you!

I found your document on 2.1 very good indeed and am sure this will be equally helpful. From one who spends quite a bit of time writing instructions of this kind for other equipment, thank you for an excellent job.

sande005 wrote: ↑Mon Mar 05, 2018 10:47 pm Very impressive! Thank you for putting this together. It will be very handy to refer to as I build new models in my radios.

I do note that the section on GVARS does not mention Name, Unit, Precision, Min or Max - what they are, and possible limitation on their use (ie - "precision" of 0.0, when reading a + or - 100% value will move the decimal, giving a GVAR of only 10%, etc.). Or is this a really new feature of 2.2.1, so wasn't applicable to 2.2.0?

Good point. There are bound to be a few holes here and there. Will work on that!

This is awesome! We now have online, printed and PDF options:)
If you're looking for an
Online Manual http://rcdiy.ca
Printed Manual https://alofthobbies.com

Please note, neither of the above references are for the same manual as this.

Please look at Section 3, page 15

Lua - Enables the use of lua scripts

.

Lua scripts are always enabled. This option enables the custom scripts screen which in turn enables us to configure mix scripts.

Section 3, page 16

Backup folder - The location of where firmware backup files will be stored on the computer

I used to think this as well but when I check/tried to verify I found it not to be the came.

Backup Folder: Location of backup eeproms/model settings on the computer

Hi Rcdiy, Point taken for the LUA scripts, Another change to make.

However, had a play with the backup, and I think it is a bug. I have found that nothing is saved in the backup files location despite a lot of different loading and saving. The models are saved in the file directed by the "Save as" command.

What rcdiy said is correct, but it was made for the AVR radios back in the day (where flashing firmware erases all settings, so it was even more important to have a backup) and probably never really got support added for newer radios.

There has never been an automatic firmware backup feature for any radio.

So what is the enable automatic backup before writing box for:

"Enable automatic backup of models and settings before writing firmware." BUT as I said may or may not do anything on some radios.

I think I’ll add a note in my documentation explaining not to rely on it and to do our own backups. I may create a GitHub issue. It would be nice to have clarity on expectations of that option.

At the very least, the boxes are unclear. As far as I can see, It was of some use with the Taranis, as a 32k bin file was stored in the directory, however it has no effect whatsoever with the Horus. I will alter my docs too to clarify this. I think you are right not to rely on it doing model backups. The program is complicated enough as it is, could these boxes simply be removed?

If it works for the Taranis which I wasn't even sure about then it should be left for it. For Horus it wasn't possible but the upcoming bootloader might change that.

Could the text in the edit settings menu be improved to clarify things?

This is a most impressive manual. Easily the best available. I like how it shows Taranis, X7, X10 and X12 and illustrates the differences in their displays. Very well done. That said, might you consider rotating the illustrations on pgs 5-34,35, and 36? As published, when you print them and then 3-hole punch the pages, they read from across the left side of a binder. I could 3-hole punch the other side of the pages but then the page numbers would be upside down at the top of the page which doesn't work too well.

Your page 9-15 for recording what switches are used for is nice but is there any chance of doing similar pages using the other transmitters as your illustration?

Thank you for those comments. Good point about the illustrations. Nobody else has commented on that!

As for the switch diagram. I'll have to work on that. I ran out of time/effort/patience/coffee when I was finishing that section off.

There will have to be an update soon to correct a number of omissions, errors , suggestions, and the changes made to 2.2.2 when it comes out, though this would appear a while away yet.

The OpenTX Companion
Section 3
Page 15

Lua - Enable the use of LUA scripts. Use of LUA scripts are outside the scope of this guide.
Incorrect.
Lua - Enables the Lua custom scripts screen.
Similar to how noheli removes the heli CCP screen. Lua adds the custom scripts screen.
The companion Lua mouse over tool tip has now been updated to say this.

Page 16
Backup folder: The location of where firmware...
Incorrect
Backup Folder: Location of backup eeproms/model settings on the computer

Both these mistakes are ones I made during my documentation but corrected on discussion with the developers.

Oops I see I already reported this but they haven't been addressed.
How often will you update your documentation. While outstanding in the production/presentation we need them to be correct as well. I'm directing people to your documents from the OpenTX Manual Post sticky on this site and from the RCDIY.ca home page.

Just so you know, I'm not reading through looking for errors I was reading through to figure out how Companion connects to the Horus transmitters. Turn off Horus, plug in USB cable, Zadig STM32 drivers used, then use Companion to edit models and settings and do firmware updates????

Hi Rcdiy

I haven't updated any of your issues yet. Life has been very hectic the last few months outside OpenTX and even the chance to fly. I have also been waiting for 2.2.2 to emerge and then do one big update. I assume people who download the docs will read some of the comments on here and see if they apply.


Am hoping the Horus connect will get easier once the bootloader is up and running. At the moment it can be trying to say the least. Don't mind you finding all the errors, indeed I would welcome that.

Hi

It is possible to upgrade the Taranis X9D to X9D Plus.?

What is the last softw for the x9d ?.

I have it with the 2.0.8 International.

Thank you
Best regards
Artabro

X9D is still fully supported in current version.

Upgrading requires replacing the entire electronics, and doesn't bring much at all.

Ok

Thk
Artabro

Great work. Well done.

I've just skimmed through this as I was printing a copy and I've already found a few things that would have saved me lots of heartache whilst I was learning to program my X9D. I've just picked up an X12s so this will be invaluable as I get to grips with setting up the new radio.

why are not G_ROLL and G_PICH available for the HORUS X12 in OPEN_TX?

I presume you mean programming for the 6 axis accelerometer. It was never implemented by the programmers. I think there was some problem getting the data out of the accelerometer. It is still sitting there as one of the issues from May 2016.

Thanks for your work with that, Great! I have an issue with Horus X12S when I going to create a new model only can select 2 options: Glider and Plane (see photo), could you know how to solve it? how to activate other model types as a multirotor, boat, heli, or wherever?

You set them up manually since no wizards have been made for them.