HD OSD #15
Closed
HD OSD #15
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
|
Give me a green light when you think you done all changes and I can start integrating it into master. |
|
HD OSD support is implemented in main branch. |
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.
Some changes compared to the first version:
#12
OSD no longer flickers (except on the statistics page after the flight, but this is due to INAV).
Analogue OSD still present, plugin automatically switches to HD if INAV reports HD support and is enabled, otherwise analogue is used. The CLI switch has to stay in, it is currently not possible to change the OSD displayport in INAV after initilation.
Full compatibility to INAV without HITL HD OSD
Ring buffer for HD OSD to prevent the MSP packets from becoming too large.
Adapted INAV version:
https://github.com/Scavanger/inav/tree/HITL-HD-OSD
Known issues:
X-Plane crashes randomly when using the map. I don't know if this bug is caused by my changes or if it was already there. The flight path from the HD OSD works.
When I want to debug the error, the map works. :(
For HD OSD a dummy "MSP Displayport" must be configured on a UART in the Configurator, otherwise "WTFOS" cannot be selected in the OSD tab to configure the OSD correctly.
Requires a change in the configurator.
The HD OSD needs a few seconds after connecting to be displayed, but then reacts quickly.