Repository navigation
fix: expose navigation settings and correct planner grid height - #255
Open
xiaolefang-dm wants to merge 8 commits into
Open
xiaolefang-dm wants to merge 8 commits into
xiaolefang-dm wants to merge 8 commits into
Conversation
|
xiaolefang-dm
marked this pull request as ready for review
October 15, 2026 03:57
This branch has not been deployed
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.
Changes
Operate now shows the selected current-map name using existing map metadata and opens a Navigation settings dialog. Users can choose a robot preset and edit safety radius, dilation, per-update decay factor, maximum linear/angular speeds, and camera-relative Z bottom/top. Presets supply defaults; the dialog supports restoring them and validates input.
The backend persists settings in the device database and forwards them to both planner and cmd_vel controller on startup/restart, including the legacy navigation startup path. Saving changed settings stops current navigation, clears its target, and restarts running planner/control processes; saving unchanged values leaves navigation running. Manual App velocity commands also respect the configured speed limits. Robot-type changes also restart a running Unitree adapter with the selected model, and saved model selection is used on its next startup.
Planner maintenance changes:
Retains trajectory generation and path timestamps, goal-distance and velocity-estimation logic, the original 106 candidates, and controller tracking behavior from main. No added test or Markdown files are included.
Validation
default.mov