Mobile-robot technical dossier · 02
Trace lifecycle management, localisation, costmaps, planners, controllers, behaviours and safety-adjacent plugins while preserving the boundary between software capability and safe deployment.
Identify the exact system first
Nav2 is the ROS 2 navigation framework for mobile and surface robots. It offers modular servers and plugins for localisation, planning, control, behaviours, docking, routes and related functions; it is not a complete robot, a validated map or a certified safety system.
Engineering asset map
Managed lifecycle nodes, bonds, behaviour-tree navigator and task-specific navigators.
Verify before adoptionDefine startup order, health transitions, failure propagation, cancellation, recovery and restart authority.
AMCL, map server, layered costmaps, filters, voxel processing and transform interfaces.
Verify before adoptionValidate map provenance, sensor model, TF/time chain, footprint, clearing, inflation and unknown-space policy.
Plugin servers for global planning, local control, trajectory smoothing and velocity smoothing.
Verify before adoptionFreeze plugin, parameters, kinematic limits, update rates, latency, saturation and failure criteria.
Collision monitor, docking, waypoint following, route graph, behaviours and ecosystem integrations.
Verify before adoptionDetermine whether each extension is advisory, supervisory or control-authoritative; none should be assumed safety-rated.
Layered licence reading
The repository licence file documents a package/file-level mix including Apache-2.0, BSD-3-Clause and LGPL-2.1-or-later.
Use each package.xml and file header as authoritative; do not label the whole stack with one licence.
Selected planners, controllers, behaviour-tree libraries and middleware retain their own versions and terms.
Generate a dependency bill for the exact deployed image and preserve notices/source obligations.
Operational assets can contain proprietary site layouts, personal data or security-sensitive information.
Define ownership, access, retention, redaction and sharing before collection or publication.
This table is a source-navigation and engineering-decision aid, not legal advice. Use original licence texts and qualified advice for an actual decision.
Navigation & deployment validation gates
ROS distribution, Nav2 release/commits, package graph, container digest, plugins and parameters.
Stop conditionStop if documentation or plugins target a different distribution or API generation.
TF tree, coordinate conventions, clocks, QoS, sensor rates, command timeout and lifecycle transitions.
Stop conditionNo physical navigation with inconsistent transforms, stale data or unbounded commands.
Nominal routes plus blocked paths, sensor loss, localisation jumps, controller failure, cancellation and restart tests.
Stop conditionDo not enter site trials while a single expected fault can create uncontrolled motion.
Map/version, traffic rules, obstacle classes, speeds, stopping distance, interventions, failure log and change control.
Stop conditionPassing one map and robot does not validate another site, payload, sensor set or operating mode.
FUURAA analysis
A modular navigation spine for research and products whose robot, site and operating assumptions are explicitly controlled.
A rich plugin catalogue encourages feature assembly before interface, fault and site contracts are proven.
Nav2 should standardise decisions and evidence, not hide them. Every deployed parameter file is an operational claim that must be tested on the exact system.
Applicability boundary