How to methodically configure and tune any ArduCopter

RC_OPTIONS, 288 is used for telemetry passthrough over CRSF for the Yaapu telemetry script on the Radiomaster TX16S (no connection to Mission Planner at this point).

SERIAL2 was connected to the Crossfire Nano RX pins 3 & 4 for MAVLink over CRSF, where the PC with Mission Planner is connected via wifi to the Crossfire Micro TX. However that didn’t work for us in the end because of strict firewall settings (company laptop).

SERIAL1 is connected to a self-designed ESP32 telemetry module running dronebridge for the connection to Mission Planner, the comment is outdated.

1 Like

I had PID checked. I don’t see a RATE item to check in the bitmask. I was using the logging bitmask from this tuning process. (LOG_BITMASK = 145372)
Is RATE part of “Fast Attitude” maybe? Thanks.

@andyp1per if you found a bug in the log bistmask value of the configurator, please submit a pull request or suggest the bit that fixes it.

@KevinB Section8 of the document above has details about that.
And you can also plot the PID?, RATE objects in the .bin log files and compare them with the RCIN objects.

As to LOG_BITMASK bits and their meaning see: How to methodically tune (almost) any multicopter using ArduCopter 4.4.x - #52 by amilcarlucas

No idea what the configurator does - I am just referring to the LOG_BITMASK settings available in mission planner

The configuration uses different LOG_BITMASK values depending on which configuration step you are currently doing.

So if for example the LOG_BITMASK for the Notch filter evaluation is wrong, you just need to fix it on the vehicle_examples/diatone_taycan_mxc/4.5.1-params/13_logging.param file

Here are the configuration files for your vehicle.
sauravhobyy.zip (259.6 KB)

It requires the -t ArduPlane command line parameter for now when starting the tool.
But otherwise it is a start.

Many parameters are not correctly configured, you should really load these files into the tool and use it to get the parameters done.

1 Like

I will have a look at this.

But today we tuned another same size drone and we couldn’t save prams when we used the configuratior maybe some issue from my end must be missing out on something maybe.

But we tuned using the above guide. And tuned it completely ( wihtout wind compensation and motor calibration ) and it was just much easier this time and quicker.

Also had to disable current and volt sensor because of wrong reading I hope that won’t affect tuning and magfit ?

Here are the logs plus the pram files.

https://drive.google.com/drive/folders/1niSBuMIsgpodRNjT6HT5-OOe0HUZgXdY?usp=sharing

How exactly are you installing the software? Which version of the software are you using?

Version 0.2.2 can now autodetect ArduPlane without requiring the -t ArduPlane command line parameter if an FC is connected.

1 Like

That table in your link was EXACTLY what I needed. Thank you!

1 Like

testing of the radio failsafe and rc failsafe?

Thanks @DavidBuzz I’ll add that

@rmackay9 for the impatient users I now added a path to jump from section 3.2 into section 12 skipping the optimization steps in between and trading-off complexity and comprehension with simplicity and speed.

I also added a quicktune step at the end of section 3.2 to reduce the risk of the second (MAGFit) flight.

1 Like

Radio Failsafe was already on section 2.10 and I now added it to section 2.4 as well. Thanks.

@amilcarlucas,

OK, sounds good! Thanks!

Please forgive my newbie question, but I’m experiencing trouble on what appears to be a Python related installation issue. Can someone tell me how to handle this error output during MethodicConfiguratorWinBuild…

C:\Windows>python.exe -m pip install . --user
ERROR: Directory ‘.’ is not installable. Neither ‘setup.py’ nor ‘pyproject.toml’ found.

Thanks for your kind help

On windows you should use the provided .exe installer. Do not try to install python manually.

Thanks a lot Lucas for your quick reply… I was doing it the laborous way and did not even notice there was an exe windows file readily available.

Downloaded and operational now. Thanks.

1 Like

Thanks @amilcarlucas and the other contributors for this excellent guide.

Just a little side note:

Meanwhile there is an “Ultralight” version of that Helical H-RTK F9P available, that will save some significant amount of weight for such a small build.

1 Like