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.
telemetry_inverted applies to any telemetry protocol and causes
the default protocol inversion to be flipped. This means that a
default of 0 (OFF) will work for most users, while hacked and custom
RXs can be used by enabling this new setting.
The parameter group version for PG_TELEMETRY_CONFIG has been
increased to prevent the value from the old telemetry_inversion
setting to overwrite telemetry_inverted when upgrading from
previous versions.
Documention and target files have been updated too.
Changed the CLI variable to `gps_ublox_use galileo` for consistency with
other GPS variables
Changed the eligibility test to M8N hardware and v3 firmware (or later)
