Initial cut on DJI HD FPV goggles support #5303
Merged
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
|
Reviewed the code, it looks good. |
|
I'm going to merge this at it's current state and address full support for PID/filter tuning in the following PRs. |
|
thanks so much for this, can we get a full list of the values that we can use with this? |
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.
DJI supports Betaflight's flavor of MSP protocol which is in many aspects different from INAV flavor. To avoid introducing more complexity to already complex MSP code (3500 lines long, very hard to follow) this PR creates a subset of DJI-compatible MSP API and exposes it via a dedicated serial function (enable via CLI with
serial N 2097152).In addition this PR introduces a new SBUS_FAST protocol (SBUS with 200k baud rate, corresponds DJI's fast serial link).
Still TODO:
This supersedes #5289. Also many thanks to @idavidstory for creating bridging the gap while I was arranging better collaboration with DJI folks.