Each branch should be named for the version of the MONARK platforms the params are designed for, e.g. v1.0, v1.2, v1.3, etc. If there is a need to sub-branch, use v1.0a, v1.0b, etc. convention.
ArduPilot/ArduCopter
Multi-Rotor
4.5.7 (monark branch https://github.com/EchoMAV/ardupilot/tree/monark)
Several of these params are drone-specific and/or readonly. However, this is the full output from mavlink and as such can be inputted into the same or different drone without issue. Then once the drone reboots, ardupilot will update unique params. Note, for some params you will need to do this TWICE in a row since param A needs to be enabled for param B to apply.
After exporting the params from QGC (NOT mission planner) rename as exported_monark.params
. Then run python scrub_params.py
and source control both including the modified "import_monark.paramsfile. The import file is what gets imported into the GCS under the parameter tools section in the app. Also, if you want to make a modification outside of QGC, then change
exported_monark.paramsand rerun
python scrub_params.py`.