Moving onto INAV 3.0 or later
When we started Project Rosetta Stone, INAV 3.0 was being worked on. The first release candidate came out and there were no show stoppers. Most of the initial comments from people who tried out INAV 3.0 have been positive.
When we write these documents, they sometimes stay up for years. And thus, you may be reading this knowing that INAV 3.2 is out. Thus, what I am going to do with this week, along with covering what the new steps for this week is to first go over how to upgrade INAV.
You do not want to borrow someone’s diff file
There is a common feeling that someone who has a Mini Drak that flies perfect can copy their diff files and you can use it on your AR Pro. Would this be better than defaults? No, it’s far worse than defaults. Please, just use the defaults. Select the default based on if your plane has a tail or not, nothing else.
Can’t I do an diff /all from an old version of INAV and copy it over to the one?
A straight save and reload is also a bad idea. But, there are things in that Diff/All file you can certainly bring over. You can follow these steps for future releases of INAV as well. We’re just borrowing a few things from the previous build but not changing any flight settings.
ACC Variables – Accelerometer
In your diff /all file there will be lines that look like this, closer to the bottom of the file.
set acczero_x = (some number)
set acczero_y = (some number)
set acczero_z = (some number)
set accgain_x = (some number)
set accgain_y = (some number)
set accgain_z = (some number)
These are your gyro calibration variables. If you did a good job calibrating your gyro, you don’t ever need to do it again. Just copy and paste these six lines into the CLI, be sure type “Save” and the flight controller will reboot.
AUX – Modes
These are your mode settings. Just copy and paste in the lines of code and all your modes will be setup correctly once again.
OSD
I bet you know what this is! Yes, it’s your OSD layouts. So, here’s a clue for you. If you have Google Doc or Microsoft 360 make a file and drop all these OSD lines of code into it. When you tweak your OSD layouts, update the online file so that you can copy and paste it to other planes. Some people stick with one OSD layout and never change. I find that there is so much to the OSD layouts that you can add that I will add one thing at a time and see how it works. It’s better to use multiple OSD’s than one cluttered OSD.
The aspect ratios for PAL and NTSC are different. The cameras always say PAL/NTSC switchable. But very few cameras have a legitimate switch on the camera. Mostly it’s done in the firmware which requires you to hook up a cable and get inside to switch it. I don’t often do this and thus will make an OSD layout for PAL and a separate one of NTSC. If something gets cut off, or if there is too much space on the bottom I will load the other layout. When it looks right, don’t forget to upload your favorite font in the OSD menu.
The rest of the setup I simply do by hand. I find that if you do it enough it takes around 20 minutes to flash and setup the flight controller. I use defaults for INAV.
No more Autotrim
INAV is switching over to continuous servo trim. Thus the emphasis of the week has changed, its a lot more simple and the steps will be explained. By now you should have a functional manual trim and you should have no problem taking off in manual. You also need to be sure that all your radio trims and mixing is turned off. This is all done in INAV.
The very simple steps
- In INAV Configurator, go to the Configuration page. At the bottom on the right you’ll see Permanently enable servo trim. Make sure this is on and save and reboot.
- Take off in manual, get up at least two mistakes high
- Switch to Acro mode. This is the least stabilized flight mode and the one most similar to manual. There is quite a bit more information about ACRO in our modes documentation, but it’s best to know that Acro mode is very different from all the other flight stabilized modes. When you autotune with INAV 3.0, you must use Acro.
- Switch to Angle mode. When you’re plane is flying nearly level you can switch to Angle mode. I wouldn’t start the flight off with angle mode because the rates are low and you may not have enough travel to even get off the ground. Once you’re in the air it may be too watered down to effectively swerve and avoid things. Thus, wait until you’re high enough up to switch to Angle mode. Keep your eyes on your altitude in your OSD. At some point you should be able to fly level long enough to take your hands off the sticks for a five seconds.
- Land and disarm. The new servo trims are saved, ready for the next flight
Go back and fly again
This time you should be able to take off in Acro mode. Fly around some more, switch to angle mode and once again fly level let go of the sticks and land, then disarm. You should notice a bit of improvement from the last flight. I tend to like to do this a few times, to the point where I see no changes in each successive flight.
1450-1550
At this point your plane is trimmed, not tuned. In the defaults for INAV, the rates are very much turned down. You should notice that the plane isn’t as nice to fly in any other mode than manual. Don’t worry about it, we’ll fix that in the autotune. The autotune will be build off of your trims. The difference between a great plane and one you somewhat tolerate is correct CG and correct trims. Just because the autotrim step has been removed doesn’t make trims any less important.
If you want to really maximize your flying experience, do the following
Go to your outputs tab and ensure that each servo falls somewhere between 1450 and 1550. If you’re seeing a 1300 it usually means your control surfaces are sitting up fairly high. You can stick a pin in the control surface to lack it, and reset your servo in the output tab to 1500. Shore up your control rod to ensure that the servo is centered and the control surfaces is where its locked in with the pins. When this is done, remove the pins and go out and fly some more as described above.
When you have ensured that the plane flies well and each control surface is between 1450 and 1550 you can move on to the autotrim, which will be the very last step in our series.
Rare Air days
I somewhat live in the real world where the weather conditions don’t always work out well enough. Perhaps you’ve moved along quickly through the servo trims process and after autotune you start to realize that your plane doesn’t fly as well as it should. Can you fix this? Yes, of course.
Once again check your servo numbers, make sure they are between 1450 and 1550. If you get one of those rare air days where there is no wind to speak of, or it’s very mild, this is a good time to recheck your servo trims in your output tab after a few flights in this rare air. When you’ve gotten the servos in that 1450-1550 zone, you can always go back and do another autotune.
Where you should be right now.
In our group we see all the extremes when it come to INAV. Some people make their planes so perfect, so exact that they are extremely worried about crashing and having to fix their plane and dealing with imperfections. And, we get people who cut corners and expect INAV will fix their shortcomings.
If you’ve followed the guide you should have a very flyable plane. If you have the CG right, and have worked out the trims so that your servos are between 1450 and 1550 you should be ready for the final step. The autotune.
