collision-monitor

Enforce obstacle-aware velocity control on Nav2 using laser scans and point clouds.

18|2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/wimblerobotics/ros2-copilot-skills --skill collision-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collision-monitor
Source: https://github.com/wimblerobotics/ros2-copilot-skills/tree/main/collision-monitor
Command: npx skills add https://github.com/wimblerobotics/ros2-copilot-skills --skill collision-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The collision monitor enforces safe velocity commands by monitoring real-time sensor data and halting or slowing the robot when obstacles are detected, preventing collisions before they occur.

Core Features & Use Cases

  • Real-time obstacle detection across LaserScan, PointCloud, and range sensors.
  • Polygon-based safety zones to define stop, slowdown, and approach behaviors.
  • Seamless Nav2 integration ensuring the collision monitor is the last node in the velocity pipeline and provides diagnostics for safety tuning.
  • Use case: in a warehouse robot, the collision monitor stops the robot when a person steps into a PolygonStop zone, or slows down within a PolygonSlow zone as it nears obstacles.

Quick Start

Configure the collision_monitor YAML block and polygons, then deploy the Nav2 pipeline to enable real-time safety checks.

Frequently Asked Questions about collision-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent collisions in ROS 2 Nav2 using real-time sensor data?

To prevent collisions in ROS 2 Nav2, a collision monitor enforces obstacle-aware velocity control by processing real-time LaserScan, PointCloud, and range sensor data to halt or slow mobile robots before impacts occur.

How do I configure polygon safety zones for velocity slowdown and stop actions in Nav2?

Configuring polygon safety zones in Nav2 involves defining PolygonStop and PolygonSlow areas in a YAML configuration file, allowing the collision monitor to execute stop or slowdown actions when obstacles enter these specific boundaries.

Does the Nav2 collision monitor support integration with LaserScan and PointCloud observation sources?

Yes, the Nav2 collision monitor supports seamless integration with real-time observation sources including LaserScan, PointCloud, and range sensors to actively safeguard against unexpected obstacles in dynamic environments.

What is the purpose of base_shift_correction in a ROS 2 collision safety monitor?

Base_shift_correction is a configurable parameter in the ROS 2 collision safety monitor that adjusts the robot's footprint reference frame, ensuring accurate polygon-based safety zone enforcement and reliable obstacle detection during movement.

Can I use a collision monitor as a final safety layer for warehouse robots in dynamic environments?

Yes, you can use a collision monitor as a final safety layer for warehouse robots in dynamic environments, configuring it to stop robots when people enter PolygonStop zones or slow them near obstacles within PolygonSlow zones.

Why should the collision monitor be the last node in the Nav2 velocity pipeline?

The collision monitor should be the last node in the Nav2 velocity pipeline to ensure it serves as the final safety layer, intercepting and overriding velocity commands with obstacle-aware control before they reach the robot's actuators.