MSP VTX Code Updates #10355
Draft
MSP VTX Code Updates #10355
+233
−604
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e capabilities. Add one to the power to allow HDZERO 0mW option.
Include uint definitions.
|
probably related to or causing hd-zero/hdzero-vtx#203 |
Move telemetry function definition back to correct place.
Simplify initialisation.
|
VTX band/channel/power/pitmode/lpmode can be changed in the FC VTX menu; the actual VTX menu; the programming tab; and the ELRS VTX lua script. If you use more than one of these methods, you may find discrepancies between what you think you have set and and what is actually set. For example, using a switch to set a power level of 1 can be overriden by a VTX menu or the ELRS lua. Only use one of these methods to get consistent results. Also, pit mode is not very well supported in iNav, and you may find issues when using it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Current VTX Control from ELRS and FC is erratic.
The MSP VTX code, originally pulled from BF, was not properly integrated into iNav. This led to the "stealing" of VTX messages meant for the original FC VTX processing. Also, the FC message processing was incorrectly calling MSP VTX code directly rather than allowing the existing VTX support framework to process any changes to band/channel/power.