1. Packages
Hardware-independent logic (kinematics, PID, encoder decoding, line position, multiplexer, brake) lives in ROS-free
modules and is tested with
pytest.
2. Data Flow
mode_manager_node forwards to the /cmd_vel topic only the velocity command coming from the source that matches the
active mode; the emergency stop and the lidar brake are also applied in this node.
3. Driving Modes
- The emergency stop takes precedence over all modes and switches the mode to
idle. - When leaving
navmode, Nav2 goals are canceled. - The lidar brake (enabled by default,
control.yaml→safety.enabled) limits the forward/backward speed in every mode. Obstacles are only searched for in the corridor the robot is about to travel (body width + margin), and the distance is measured from the front/rear end of the body. A wall at the side does not block driving, and turning is never restricted (control.yaml→safety, body dimensions inrobot.yaml).
3.1. Direction convention
All/cmd_vel* commands and kinematics follow REP-103: linear.x > 0 is forward, and angular.z > 0 is a
counterclockwise (left) turn viewed from above.
The only exception is the web interface key mapping. When reversing, the left/right keys behave like a car’s
steering wheel; the left key moves the rear of the vehicle to the left (
angular.z < 0). This translation is done only
in the browser (app.js → steering); the command sent to the robot still follows REP-103. Line following and Nav2
do not go through this translation.4. TF Tree
The transforms belowbase_link are published by robot_state_publisher.

