From d36b06f779d49d8dc7387bf2b4fa3aade999ada3 Mon Sep 17 00:00:00 2001
From: Daniel Agar <daniel@agar.ca>
Date: Sat, 13 Apr 2019 10:44:06 -0400
Subject: [PATCH] fw_pos_control_l1: FW_LND_EARLYCFG disable by default

 - change to boolean param
---
 .../fw_pos_control_l1/fw_pos_control_l1_params.c      | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/src/modules/fw_pos_control_l1/fw_pos_control_l1_params.c b/src/modules/fw_pos_control_l1/fw_pos_control_l1_params.c
index 14ef783acc..72548fd321 100644
--- a/src/modules/fw_pos_control_l1/fw_pos_control_l1_params.c
+++ b/src/modules/fw_pos_control_l1/fw_pos_control_l1_params.c
@@ -334,19 +334,18 @@ PARAM_DEFINE_INT32(FW_LND_USETER, 0);
 /**
  * Early landing configuration deployment
  *
- * When set to 0/disabled, the landing configuration (flaps, landing airspeed, etc.) is only activated
- * on the final approach to landing. When set to 1/enabled, it is already activated when entering the
- * final loiter-down (loiter-to-alt) WP before the landing approach. This shifts the (often large)
+ * When disabled, the landing configuration (flaps, landing airspeed, etc.) is only activated
+ * on the final approach to landing. When enabled, it is already activated when entering the
+ * final loiter-down (loiter-to-alt) waypoint before the landing approach. This shifts the (often large)
  * altitude and airspeed errors caused by the configuration change away from the ground such that
  * these are not so critical. It also gives the controller enough time to adapt to the new
  * configuration such that the landing approach starts with a cleaner initial state.
  *
- * @value 0 Disable early land configuration deployment
- * @value 1 Enable early land configuration deployment
+ * @boolean
  *
  * @group FW L1 Control
  */
-PARAM_DEFINE_INT32(FW_LND_EARLYCFG, 1);
+PARAM_DEFINE_INT32(FW_LND_EARLYCFG, 0);
 
 /**
  * Flare, minimum pitch
-- 
GitLab