Differences

This shows you the differences between two versions of the page.

--- searchwing-ardupilot-firmware [2019/07/30 23:07]
simonkun [Mag Sensor Setup]
+++ searchwing-ardupilot-firmware [2019/08/12 20:28]
simonkun [Parameters]
@@ Line 1: / Line 1: @@
 ====== Ardupilot Firmware ======
-We currently use the current Ardupilot ArduPlane stable firmware version (current: 3.9.8)
+We use the current Ardupilot ArduPlane stable firmware version (current: 3.9.8)
 ===== Firmware installation =====
-The firmware is installed on the PixRacer via the QGroundControl Software. [[https://docs.qgroundcontrol.com/en/SetupView/Firmware.html|https://docs.qgroundcontrol.com/en/SetupView/Firmware.html]]
+The firmware is installed on the PixRacer via the QGroundControl Software. [[https://docs.qgroundcontrol.com/en/SetupView/Firmware.html|https://docs.qgroundcontrol.com/en/SetupView/Firmware.html]]\\
+Select "ChibiOs - ArduPlane V3.9.8" from drpdown.
 ==== Mag Sensor Setup ====
@@ Line 21: / Line 22: @@
 After the mag setup is changed, the mag sensors have to be calibrated. If you see a "Mag Inconsistent Error" in QGC, then this setup is wrong.
 ==== Parameters ====
--TBD-
+=== Procedure ===
+  - Load parameters "deafult_to_Paolo" (NOT TESTED YET!) from https://gitlab.com/searchwing/operational/searchwing-config/tree/master/ardupilot/V3.9.8
+  - There may be warnings that parameters were skipped even though they were written anyway.
+  - Reboot Vehicle.
+  - Export parameter from QGC (.params file)
+  - Diff downloaded params with previously loaded params if they are the same.// Except parameters like bootcnt, num_resets, stat_* etc.//
+=== Failsafes ===
+Geofence is not configurable through QGC. But if a fence was set in Ardupilot Mission Planner, it is updated on vehicle boot.
+–TODO–