LOG system has multiple levels, selectable both at compile and run
times. FEATURE_TRACE has been removed, since we now rely just on
the log level/topic and the defined outputs for the log messages.
* CLI for servo mix conditions
* RC channel greater than on servo mixer
* RC channel value based conditions
* MSP2 frames
* Docs update
* mixer condition changed to logic condition and generalized
* basic logic framwork extarcted to separate file'
* minor fixes
* Processing refactoring
* Flight values added to conditions
* Use logic conditions only on > F3
* Make logic conditions a separate entity and link from servo mixer to logic condition
* empty task to periadically compute logic conditions
* Compute logic conditions as task
* Add flags
* CLI logic to configure logic conditions
* MSP frames to get and set logic conditions
* Disabled condition always yelds false
* fixes for F3
* Review changes
* final fix in MSP2_INAV_SERVO_MIXER
* TIM/DMA abstraction
* Migrage F7 TIM/DMA to HAL_LL
* Refactor timers to use conventional HZ
* Refactor PWM ourput code to use highest possible resolution
* Remove TIMER_OUTPUT_ENABLED
* Temporary disable SPRACINGF3NEO due to out of RAM
Split INVERTER_PIN_UART<n> into INVERTER_PIN_UART<n>_RX and
INVERTER_PIN_UART<n>_TX. This allows us to invert just one line
of the port in F4 based controllers, like we can do on F3.
Fixes#3466
- 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.
