Disable processing MSPVTX commands if there is not SPIVTX #2525
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
|
Looks ok, I'll test with the hardware shortly and let you know if it works as it should with an RTC6705 attached. |
phobos-
approved these changes
Jan 13, 2024
JyeSmith
approved these changes
Jan 21, 2024
zeebrababrik
pushed a commit
to zeebrababrik/ExpressLRS
that referenced
this pull request
Jan 23, 2024
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.
MSP VTX should only operate and send the VTX table if the receiver actually has a VTX.
The fix is to initialise the state machine in the STOPPED state and only enter the waiting state if there is an SPI VTX configured in the hardware layout.
Fixes #2452