- active boxes use bitmask instead of array
- active box serialization is loop based instead of huge expression
Was included in
https://github.com/cleanflight/cleanflight/pull/2075/commits, but never
ported to BF and eventually lost
Conflicts:
src/main/fc/fc_msp.c
How it works:
1. Current Meter Source on FC is set to MSP/OSD Slave by user.
2. On reboot FC sends MSP_ANALOG to OSD Slave.
3. OSD Slave listens for incoming MSP as usual.
4. OSD responds to MSP as usual.
6. The FC recevies the data from the OSD Slave and updates the MSP
Current Meter.
CF/BF - Fix typo in max7456DmaInProgress. Always define an
implementation even when there is no TX-DMA.
CF/BF - Ensure that max7456 communication does not disrupt RTC6705
communication when using the same SPI port for both.
CF/BF - Port RTC6705 to use the VTX API.
* Support VTX channel/band/power on OSD for ALL vtx APIs - previously it only supported RTC6705.
* Remove all FEATURE_VTX usage.
* Remove all `#define VTX` usage.
Note that due to the async nature of tramp/smartaudio it's not possible
to know the current band/channel after requesting a change (as the
request hasn't been processed) so it makes no sense to try and save the
config - and on the tramp/smartaudio vtx the vtx maintains it's state.
So on an RTX6705 equipped FC the user should now MANUALLY save the
config using the save config stick position.
CF/BF - Move CMS for RTC6705 into vtx_rtc6705.c for consistency with
other VTX CMS menus.
CF/BF - Update RTC6705 via SOFT SPI to use VTX API.
* Achieved by simply aligning the API at the driver level and removing
all legacy conditional compilation checks.
CF/BF - Use new IO for RTC6705 CLK Hack
CF/BF - Port VTX button from CF v1.x.
Features:
* Channel Cycle
* Band Cycle
* Power Cycle
* Save Settings
* Works with any VTX using VTX API.
CF/BF - Allow support for Internal and External VTX - External takes
precedence when configured.
CF/BF - Fix display of VTX power in CMS.
* Issue occured when CMS was transitioned from integer to list of
strings.
CF/BF - Disable SMARTAUDIO and TRAMP on the SPRacingF3NEO due to flash
size.
CF/BF - Cleanup const usage of bass-by-value parameters. Cleanup
naming.
CF/BF - Cleanup naming. Removing noise-words. Improving consistency.
CF/BF - Improve readability by further naming cleanups.
CF/BF - Remove some magic numbers in the RTC6705 VTX code.
CF/BF - Use braces on some procedural macros.
CF/BF - Improve code readability by renaming rtc6705SetChannel to
rtc6705SetBandAndChannel.
CF/BF - Remove editor mishap.
CF/BF - Make the rtc6705Dev variable static.
CF/BF - remove duplicate state variablertc6705Dev_t - vtxDevice_t had
all we needed. Use brackets on some procedural style macros. Make all
the vtx vtable static const.
CF/BF - making some declarations const.
CF/BF - Fix vtx_power maximum value (out by one).
In CF 1.x the structure was packed, resulting in a size of 14 bytes.
The servoParam_t is not currently packed, likely due to recent PG group
implementation, so the test for data length in the MSP command fails.
the flight controller code.
Likely the dependencies can be further improved. This is a
minimal-impact solution while there are a lot of other Betaflight PR's
still pending.
This highlights the face that MSP_SET_OSD_CONFIG is ill-conceived. See
Cleanflight v1.x where multiple commands are used - one for video config
and one for element config.
In light of other recent changes it's possible a 3rd command is needed,
for unit selection and alarms.
now it's really obvious that 3d throttle deadband really doesn't belong
in it. If you need 3D specific ESC/MOTOR configuration use this. If yo
need specific 3D RX configuration use other commands like
MSP_RC_DEADBAND, etc.
The commands that are deleted have been deprecated for a LONG time.
They have long been superceed with more specific commands.
Fix voltage meter config to include id and type in the subframe.
update the MSP configuration of current and voltage sensors to use IDs.
revert the i2s_bst changes, since TBS won't be updating their firmware
there is no point adding new features to it, we just need to keep it
compatible
msp code is still unfinished, but the plan is clearer now.
move some defaults from battery.h and allow targets to override them.
define ID's for all voltage and current sensors, the idea being a list
of ids wil lbe created for each build which will allow all the voltage
and current meters to be exposed via MSP.
