-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSP VTX Code Updates #10355
MSP VTX Code Updates #10355
Conversation
…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. |
Set band/channel/power max values sent from VTX. Optimise VTX logic condition code.
Caveats:
|
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.