ROS2 Case Studies: Production Indoor AMR
ملخص
Pixel shares Chapter 12 of the Robot Middleware and ROS2 series, examining a production indoor AMR built on ROS 2 Humble. Learn how modular hardware interfaces, ros2_control, sensor fusion, safety supervision, and fleet connectivity help turn robotics middleware into a stable industrial runtime.
DEV Community
Robot Middleware and ROS2 — Ch.12: ROS2 Case Studies [EN]
STATERA Library · Series 08 · Volume 05 · Chapter 12 · EN Source: https://github.com/Statera-Library/08_Vol_05_Robot_Middleware_and_ROS2/blob/main/Chapter_12_ROS2_Case_Studies/Chapter_12_ROS2_Case_Studies_EN.md Volume 05 Robot Middleware and ROS2 12. ROS2 Case Studies 12.01 Indoor AMR Production Robot: ROS2 Humble Case A production indoor AMR built on ROS 2 Humble demonstrates how a general robotics middleware can be transformed into a stable industrial runtime rather than remaining a collection of research-oriented nodes. The Humble distribution provides a long-term support baseline for Ubuntu-based deployments, while the production architecture organizes sensing, localization, navigation, drive control, safety supervision, diagnostics, and fleet connectivity as explicitly managed subsystems. The robot software is typically divided according to execution responsibility. Hardware-facing nodes acquire LiDAR, camera, encoder, IMU, battery, motor-controller, and safety-controller information, while higher layers consume normalized ROS 2 interfaces rather than vendor-specific protocols. This separation allows sensors or controllers to be replaced without redesigning navigation logic and provides a clear boundary between device integration and autonomous behavior. At the mobility layer, ros2_control can provide a standardized connection between the ROS 2 software environment and the physical drive system. Wheel velocity commands, encoder feedback, joint states, and controller status are exchanged through hardware interfaces, while deterministic motor regulation remains inside the motor controller or lower-level real-time subsystem. ROS 2 therefore coordinates motion without unnecessarily moving hard real-time electrical control into middleware processes. Localization combines wheel odometry, inertial measurements, and environmental observations to maintain the robot pose within the operating map. A production implementation must handle more than nominal localization accuracy: initialization, temporary sensor degradation, localization confidence, map changes, and recovery after pose loss must be explicitly managed. The resulting map-to-odom and odom-to-base transforms form a dependable spatial reference for navigation and monitoring components. Navigation2 provides the principal autonomous navigation framework, integrating global planning, local trajectory generation, costmaps, behavior execution, recovery mechanisms, and goal management. Production configuration emphasizes predictable behavior rather than maximum algorithmic complexity. Planner and controller parameters are validated against vehicle geometry, payload, stopping distance, aisle width, pedestrian interaction, floor conditions, and operational speed limits before deployment. ROS 2 communication is configured according to the semantics of each data stream. High-rate sensor information may favor best-effort delivery where freshness is more valuable than retransmission, whereas commands, operational states, alarms, and selected control information can require reliable delivery. Queue depth, history, durability, deadline, and liveliness settings are treated as architectural parameters because inappropriate DDS QoS configuration can create latency, stale data, or unnecessary network load. Lifecycle management is particularly important when the AMR transitions from boot to autonomous service. Sensor drivers, localization, map services, navigation components, docking functions, and fleet interfaces should not become operational in an arbitrary order. Managed nodes can be configured, activated, deactivated, cleaned up, or restarted according to dependencies, allowing startup orchestration to verify prerequisites before motion capability is enabled and to isolate failed components during recovery. Safety remains independent from ordinary navigation decisions. Emergency stop circuits, protective scanners, safety PLCs, drive enable signals, and certified safety functions shou...

Powered by Readybot.io