Skip to main content
Use Configure navigation first to choose between dotted overrides and a complete config. This reference inventories every configuration field in the Pre-release schema. Download JSON Schema · Download complete R1Pro omni YAML The tables show generic schema defaults, not recommended tuning and not necessarily your robot’s defaults. A profile overrides them, and geometry propagation may derive further values. Inspect nav.config for actual values. “Factory / see resolved YAML” means a nested object or collection is built by the config loader; the downloadable YAML supplies a complete resolved example. The schema is a snapshot of the documented code. An agent should use the installed runtime’s schema and validation when they differ. It is a JSON Schema for the nested config dictionary, not a tool-call schema.

Units and validation

Distances are metres, speeds m/s, angular speeds rad/s, and frequencies Hz. Names ending in _s, _m, _hz, or _deg specify seconds, metres, Hz, or degrees. Coordinate arrays have the frame and shape described in the configuration guide or matching robot profile. The runtime validates more than JSON Schema alone describes. Root motion caps and update rates must be finite and positive, goal thresholds and failure tolerance finite and nonnegative, and max_steps positive. Camera matrices, transform lengths, image sizes, enumerated modes, and footprint dependencies are checked by the loader. Keep strict booleans and integer ports in runtime settings; unknown root/runtime fields and unknown dotted overrides are rejected. Do not interpret an unconstrained array in JSON Schema as accepting arbitrary calibration dimensions.

Root fields

Nested sections

A section table is relative to that section: field backend under runtime is the override path runtime.backend. Use the nested mapping shape in YAML or JSON. Expand the section you need.
Collision gating, standoff, sensor freshness, and Nav2 collision-monitor policies. mode selects gate or nav2. Geometry and stopping behavior must match the robot.
LiDAR height and range filtering before obstacle processing.
Dynamic Window Approach sampling, scoring, and kinematic parameters; relevant when using the DWA controller.
Progress and stall detection windows and thresholds.
Recovery behavior and round-robin policy. mode selects none, simple, or adaptive; presets are nav2_faithful, deployment_legacy, or benchmark_legacy.
Terminal position/heading alignment. It is used when the final mission goal includes a heading; plain XY goals do not request heading alignment.
Command acceleration/deceleration and smoothing. mode is legacy or nav2; feedback is OPEN_LOOP or CLOSED_LOOP.
DWA costmap and pipeline settings.
MPPI prediction, sampling, costmap, critics, and trajectory validation. motion_model is diff_drive or omni. Footprint-aware cost/validation requires robot_geometry.footprint_polygon.
Optional fallback for extracting the robot from a safety standoff. Disabled unless explicitly configured.
Footprint, dimensions, inflation, and optional articulated projection. Geometry propagation derives related planner/safety values; edit geometry rather than assuming a derived field stays independent.
Robot-specific command and feedback adaptations. Preserve the matching profile; defaults disable these adaptations.
Controller selection, recording, replanning, and GRX streaming defaults. See the configuration guide for supported values and per-run overrides.
Robot identity, camera calibration, image dimensions, rigid transforms, and sensor-frame flags. Preserve the calibration for the physical robot.
Cloud localization timeouts and quality gates, pose fusion, and optional LiDAR refinement. lidar_refine selects off, shadow (diagnostics only), refine, or gate. Frequency hloc_hz is a root field.
Exclusion of robot-body returns from LiDAR, including optional forward-kinematic masking and model assets.
Simulation benchmark parameters present in the config schema. These do not expose a simulation or benchmark service through Nexus.

Nested policy objects

These types are referenced by the section tables. Arrays of these objects must be replaced as a whole when using dotted overrides.

Runtime versus mission policy

constraints is a per-mission argument, not a NavigationConfig field. See polygon constraints for its separate versioned contract. The editor’s map height slice, route optimization, and obstacle clearance are also outside this config.

Present but ineffective settings

The schema still accepts the following fields, but the configuration audit found no effective runtime consumer. Their presence is not a supported capability; use the active settings below where available. See the configuration guide for current limitations in geometry propagation, safety-mode environment precedence, polygon validation, and MPPI timing. Do not assume audit fixes or proposed APIs are present in an installed runtime.