Implement VTX MSP protocol support so the video channel can be changed from Betaflight, ELRS Lua Script or any other system that supports VTX MPS protocol.
The plan is be able to change algo power and bandwidth in the future.
Setup
Update the MSP-OSD package in both ends, Caddx vista/air unit and goggles V1/V2.
Load a VTX table data on Betaflight (this will happen automatically when develop is completed)
The feature is disabled by default, in order to enable it open the MSP-OSD package settings on the WTF OS configurator.
The flow
VTX startup up
VTX setup the Betaflight VTX table and mark it as READY
VTX request every 200ms the VTX-MSP data
VTX read the channel from the MSP message
VTX send the data to the goggles via UDP protocol.
Goggles get the message
Goggles update the channel sent from the VTX
Technical details
The VTX-MSP data, including the channel is being pulled every 200ms in a loop. The channel data is added to a data frame sent to the goggles pretty frequently.
Once the data is on the goggles we check if the channel is different to the one from the previous message.
The FC will only send VTX message when the VTX has been marked as READY.
What does it mean ready?
It has VTX table
TODO
Sync channel changes from googles to BF. This probably is better to be handled on the VTX side. There is no other system doing this now. Probably it won't be done now.
Automatically set a valid VTX table data on BF.
Enable power change (need to find a method)
Enable bitrate mode change (need to find a method)
Known issues
If channel is changed from the goggles, the sync with the MSP-VTX is lost. Right now this channel change is not being controlled.
You can setup any channel, even if is not supported, it will simply not do the channel change. This happen for index channels bigger than 8 in 25mbits or 3 in 50mbits.
Support for VTX MSP
Implement VTX MSP protocol support so the video channel can be changed from Betaflight, ELRS Lua Script or any other system that supports VTX MPS protocol.
The plan is be able to change algo power and bandwidth in the future.
Setup
MSP-OSD
package in both ends, Caddx vista/air unit and goggles V1/V2.MSP-OSD
package settings on the WTF OS configurator.The flow
Technical details
The VTX-MSP data, including the channel is being pulled every 200ms in a loop. The channel data is added to a data frame sent to the goggles pretty frequently.
Once the data is on the goggles we check if the channel is different to the one from the previous message.
The FC will only send VTX message when the VTX has been marked as READY.
What does it mean ready?
TODO
Known issues