docs: add OSD HUD and Craft Radar page - #24
Open
Raffi1202 wants to merge 2 commits into
Open
Conversation
Ports the "OSD-Hud-and-ESP32-radars" page from the GitHub wiki into the Docusaurus site as docs/06-advanced-features/osd-hud-and-craft-radar.mdx, and repoints the related-documents entry in the OSD page at it. Every setting was checked against src/main/fc/settings.yaml on maintenance-10.x and the defaults and ranges corrected where they had drifted: osd_hud_homing, osd_hud_homepoint, osd_hud_radar_disp and osd_hud_wp_disp all default to off/zero rather than enabled, osd_hud_radar_range_min defaults to 3 m and not 10 m, and eight crosshair styles exist rather than seven. The three settings the wiki never documented are now covered: osd_hud_radar_alt_difference_display_time, osd_hud_radar_distance_display_time and osd_radar_peers_display_time. The peer data path is described from the firmware rather than from the old text: peers arrive over MSP2_COMMON_SET_RADAR_POS with the payload parsed in fc_msp.c, are stored in the radar_pois slots, and are drawn by osd_hud.c. Two points that readers regularly get wrong are now stated explicitly - the peer element is OSD_FORMATION_FLIGHT while OSD_RADAR is a home-point map, and the firmware applies no timeout to peer positions, so a stale marker stays on screen until the module updates it. Third-party ESP32 and FormationFlight hardware and firmware are kept as external links only, with no version or capability claims.
This was referenced Sep 10, 2026
Raffi1202
marked this pull request as ready for review
September 11, 2026 15:00
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can switch off images and animations for a plain-text comment |
PR Summary by QodoDocument OSD HUD and craft radar configuration
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
This file contains hidden or 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
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.
Part of moving the GitHub wiki onto the docs site. Ports "OSD-Hud-and-ESP32-radars" to
docs/06-advanced-features/osd-hud-and-craft-radar.mdxand repoints the related-documents entry on the OSD page at it.The old defaults were wrong
Every setting was checked against
src/main/fc/settings.yamlonmaintenance-10.x, and most of the values on the wiki page had drifted:osd_hud_homing,osd_hud_homepoint,osd_hud_radar_dispandosd_hud_wp_dispall default to off / zero, not enabled. The wiki showed the peer display as 3; it is actually off by default, so following the old page left readers waiting for markers that could never appear.osd_hud_radar_range_mindefaults to 3 m, not 10 m.Three settings the wiki never documented at all are now covered:
osd_hud_radar_alt_difference_display_time,osd_hud_radar_distance_display_timeandosd_radar_peers_display_time.The peer data path is described from the firmware
Peers arrive over
MSP2_COMMON_SET_RADAR_POS, the payload is parsed infc_msp.c, stored in theradar_poisslots and drawn byosd_hud.c.Two things readers regularly get wrong are now stated explicitly:
Third-party hardware
ESP32 and FormationFlight hardware and firmware are kept as external links only, with no version or capability claims, so the page does not go stale when they change.
Image
static/img/features-adv/osd-hud-craft-radar-layout.pngwas not in the wiki repository, only as an attachment URL. It was fetched, viewed and checked against the code before being committed here.