DSM: Add extra XPlus channels to protocol #1138
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Fixes #1137
Added the code to support the Spektrum X-Plus channels (CH13-CH16) encoding and multiplexing.
No need to change anything in the TX code, since the TX is already transmitting 16ch to the Multi-Module, even if the channel range is CH1-CH12. XPlus channels will only be transmitted on DSM X2F when using 12 channels, not when is fewer.
Changing the MM and TX firmware send CH17-20 will be much more work on the TX, and TX->MM protocol, but 16ch is a good start.
The X-Plus channels are very LOW refresh channels, 88ms compared to the regular 11ms/22ms servo refresh... not intended for surfaces, but for low priority items, like gains, flight modes, and with a channel extender, other servos.
Tested with:
RX:
AR637TA Using CH16 for flight mode.
LemonRX Gen2 Ignores extra channels
NOTE: CH14 Throttle Kill functionality is still ON by default for backward compatibility, I think at some point of time, it should be deprecated, since the same functionality can be done with most new radios with a Thr Kill functionality (EdgeTX special function).