- mavlink v2.0 in PX4/Firmware (a26c25ca5bd0168dd2274dd8aa0392aba10feff2): https://github.com/mavlink/c_library_v2/commit/c6ab0459343c78a6a424514b5f64fa65d8cc0cf8
    - mavlink v2.0 current upstream: https://github.com/mavlink/c_library_v2/commit/d8c4e5def38f2ff6079087e579693b4bd9552584
    - Changes: https://github.com/mavlink/c_library_v2/compare/c6ab0459343c78a6a424514b5f64fa65d8cc0cf8...d8c4e5def38f2ff6079087e579693b4bd9552584

- takeoff help is used for fixed wings, it increases the altitude setpoint
after a launch. A vtol does not need this as it's already sufficiently
high up in the air.

Signed-off-by: Roman <bapstroman@gmail.com>

This reverts commit 4a71984f.

This reverts commit 585b9d8c.

This way we prevent a big dip due to TECS in altitude when the
transition happens at 10 m/s already. Apparently the rule of thumb
is to set this transition speed at the same as airspeed cruise speed.

The noise for airspeed is now applied on the Gazebo side and we can
remove this hack.

Includes:
- Fix for vibration on ground for standard_vtol.
- Noise for diff pressure / airspeed on Gazebo side.
- Fix for macOS magnetometer plugin linking error.

the condition to enter the rc mode switch evaluation was neglecting
the first connection of an RC when "no RC switch changed". this means
depending on the actual initialization values of _last_sp_man and the
desired mode preselected on the RC while connecting it would not get
evaluated.

pure refactor using De Morgan's law to make the condition more intuitive
since you think about when should I enter and not when should I skip

pure refactor of the huge condition into smaller const bool junks

There were multiple comments not addressed in pr #11904.
See commit 4bcb37f9bc9ef20b521ebcf33e7a0ed08fa86ccd

The Pixhawk cube as an internal mag on SPI. If there was a bad register
read (e.g. on an IMU failure), _register_wait was non-zero and there was
no transfer but _mag still published mpu_report.mag.

Auto mode traj - limit yaw setpoint rate of change when generated in the flight task instead of clamping the yaw rate in the controller

Move yaw setpoint slew rate from AutoLineSmoothVel to Auto. The slew rate is now applied consistently to all the auto FlightTasks

Add missing underscore prefix to a member variable in mavlink_main.cpp.h and delete unnecessary struct specifiers in mavlink_main.h.

Migrate an additional set of 16 variable initilializations from the Mavlink class constructor list to their respective declarations.

By declaring the params above the navigator modes inheriting from
mission block we make sure the params in navigator are set before
read in the constructor of mission block.

This prevents uninitialized padding from being written to dataman.

This variable was not set and lead to uninitialized memory being written
to dataman.

This should not be any functional change. The only difference are the
variable scopes, and early return versus nested ifs.

Presumably older versions of pyserial do not implement __version__ but
only VERSION, so we need to check for that as well.

on airspeed scaling

Signed-off-by: Roman <bapstroman@gmail.com>

the first position when the oa fails as setpoint to avoid jumps

Inhibiting bias estimation using the EKF2_AID_MASK parameter only applies to the delta velocity bias states.

Mavlink: Get full sensor status even if only subset has changed when composing SYS_STATUS message (#11886)

This should fix the case where the driver initializes even though the
device is not found. The change changes the behavior to return ERROR
if the whoami call fails several times instead of returning OK.

Also, the reset() and thus probe() calls are moved before initializing
the ringbuffer and device name.