[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[paparazzi-commits] [paparazzi/paparazzi] bbcb16: [nav] remove nav_manua
From: |
Gautier Hattenberger |
Subject: |
[paparazzi-commits] [paparazzi/paparazzi] bbcb16: [nav] remove nav_manual mode (#3234) |
Date: |
Mon, 05 Feb 2024 00:40:20 -0800 |
Branch: refs/heads/master
Home: https://github.com/paparazzi/paparazzi
Commit: bbcb166d37a6293b138da8509c875d674115213d
https://github.com/paparazzi/paparazzi/commit/bbcb166d37a6293b138da8509c875d674115213d
Author: Gautier Hattenberger <gautier.hattenberger@enac.fr>
Date: 2024-02-05 (Mon, 05 Feb 2024)
Changed paths:
M conf/flight_plans/flight_plan.dtd
M sw/airborne/firmwares/fixedwing/nav.h
M sw/airborne/firmwares/rotorcraft/guidance/guidance_h.c
M sw/airborne/firmwares/rotorcraft/navigation.c
M sw/airborne/firmwares/rotorcraft/navigation.h
M sw/airborne/firmwares/rover/guidance/rover_guidance.c
M sw/airborne/firmwares/rover/navigation.h
M sw/airborne/modules/nav/nav_heli_spinup.c
M sw/tools/generators/gen_flight_plan.ml
Log Message:
-----------
[nav] remove nav_manual mode (#3234)
This mode is not really used and not even recommended. It is also not
implemented in all firmwares. If a direct call to stabilization command
is needed, it should be done with a specific function but not from a
builtin instruction from the flight plan.
It was discussed in #3208, but not applyied because of nav_heli_spinup.
A new h_mode 'NONE' allows to disable guidance and stabilization while in
NAV mode, which allows to set directly the commands.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [paparazzi-commits] [paparazzi/paparazzi] bbcb16: [nav] remove nav_manual mode (#3234),
Gautier Hattenberger <=