In order to bypass the checks, users must set the new
nav_extra_arming_safety value ALLOW_BYPASS and arm with a switch
while holding yaw high. If this is used to arm the craft, the checks
are skipped until the next power cycle in order to allow rearming
quickly in case of an accidental mid air disarm.
Also, the "NAVIGATION IS UNSAFE" OSD message has been replaced
with more specific messages which tell the user the exact reason
why the navigation system is blocking arming.
Allows individually enabling and functions without having to
mentally add 6 digit numbers.
serial ID +n enables function (1 << n)
serial ID -n disables function (1 << n)
Additionally, documentation for the serial command has been added
to Cli.md
rssi_min and rssi_max allow users to specify their RSSI range by
simply introducing the smaller and bigger values they see in the
configurator or OSD, similarly to how rxrange works.
Add a new type for settings to be able to handle strings. This makes
it easier to add more settings of this type and removes the need to
handle them with dedicated CLI commands.
Replace the `name` CLI command with a setting called `name`.
Saves 8 bytes of FLASH on OMNIBUS
- VTX with support for FC control are now totally managed from the
FC. The FC will store the VTX configuration and override any changes
made manually (e.g. with a button). Users can disable VTX control
to manage channels manually.
- OSD VTX item now shows the power level too.
- Added new parameters for VTX configuration: vtx_band, vtx_channel,
vtx_freq, vtx_halfduplex, vtx_low_power_disarm, vtx_pit_mode_freq
and vtx_power.
- Added support for automatically switching the VTX power when
arming (fixes#3112).
Note that there are a several changes from the BF code. We do support
an additional setting for the low power during disarm option and
the MSP messages contain more data to allow users to configure the
VTX channel/power from the configurator. Our MSP messages also work
when the VTX is offline (the settings are stored in the FC and applied
later once the VTX is powered up).
Thanks to Matek (http://www.mateksys.com) for providing an FCHUB-VTX
to test the Tramp protocol.
Thanks to AKK (https://www.akktek.com) for providing an X2-ultimate
to test SmartAudio.