From b8f75c318b1cd59dbe7a8f3351b0cc3537ba9d27 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Kjellstrup?= <1468842+AndKe@users.noreply.github.com> Date: Mon, 13 Mar 2023 18:17:46 +0100 Subject: [PATCH] Missionitem: Set condition_yaw default to absolute heading (#10594) My experience is that I change heading to absolute direction, rather than relative (because relative will accumulate any heading error on incomplete yaw, especially if the command is executed while turning.) The absolute heading is the most used/typical way of using this mission item. This change does not affect missions that are already created, only the default selection while creating a mission. The default yaw rate is also very slow (unchanged) meaning that any relative yaw command will result in an unknown result, unlress performed long since last one relative. Final reason: Scanning missions consists of with many waypoints are always at an absolute heading. While "make a panoramic turn" with relative amont of degrees, are usually single-command. So it is better to default to a setting used for missions with many such commands. Co-authored-by: forced_to_this_mess --- src/MissionManager/MavCmdInfoCommon.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/MissionManager/MavCmdInfoCommon.json b/src/MissionManager/MavCmdInfoCommon.json index 0168ee1..7421037 100644 --- a/src/MissionManager/MavCmdInfoCommon.json +++ b/src/MissionManager/MavCmdInfoCommon.json @@ -457,7 +457,7 @@ "label": "Offset", "enumStrings": "Relative,Absolute", "enumValues": "1,0", - "default": 1 + "default": 0 } }, { "id": 176, "rawName": "MAV_CMD_DO_SET_MODE", "friendlyName": "Set mode" },