backup-behavior

Configure Nav2 BackUp recovery behavior for reverse motion when robots are stuck.

Updated Aug 16, 2026
One-click install
npx skills add https://github.com/three1324/yeonjinautomotive --skill backup-behavior-three1324
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backup-behavior
Source: https://github.com/three1324/yeonjinautomotive/tree/main/.claude/skills/backup-behavior
Command: npx skills add https://github.com/three1324/yeonjinautomotive --skill backup-behavior-three1324

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Robots navigating with Nav2 sometimes get stuck in tight spaces where spinning alone cannot free them, and the BackUp recovery behavior often fails silently due to sensor self-occlusion or TF timing issues. This Skill provides the configuration knowledge to tune backup distance, speed, and collision checking so reverse recovery works reliably. ## Core Features & Use Cases - BT Node and YAML Configuration: Set backup_dist and backup_speed in the Behavior Tree and configure the behavior_server plugin, costmap topics, and simulate_ahead_time in YAML. - Failure Diagnosis: Fix the most common failure mode where rear-facing sensors mark the robot's own body as occupied, using min_range tuning and footprint_clearing_enabled. - Recovery Pattern Design: Build escalating recovery sequences combining Wait, Spin, BackUp, and costmap clearing in a RoundRobin BT structure. - Use Case: Your differential-drive robot repeatedly fails its BackUp recovery with TF errors and refuses to reverse. Use this Skill to raise transform_tolerance, adjust rear sensor min_range, and verify negative cmd_vel output. ## Quick Start Configure the Nav2 BackUp behavior to reverse 0.3 meters at 0.05 m/s and fix the rear sensor self-occlusion causing it to fail.

Frequently Asked Questions about backup-behavior

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

FAQPage Schema
How do I configure the Nav2 BackUp recovery behavior?

Set backup_dist and backup_speed in the Behavior Tree BackUp node, and register the nav2_behaviors::BackUp plugin under behavior_server in YAML. The YAML also controls collision checking via simulate_ahead_time and transform_tolerance.

Why does Nav2 BackUp fail immediately without moving?

BackUp usually fails immediately because rear-facing sensors mark the robot's own body as occupied in the local costmap. Fix it by raising the sensor min_range, enabling footprint_clearing_enabled, or adjusting the robot footprint to match the chassis.

What backup_speed and backup_dist values should I use in Nav2?

Keep backup_speed slow at 0.05 to 0.15 m/s for safety, and use backup_dist of 0.15 to 0.30 meters. Duration equals distance divided by speed, so 0.30 m at 0.05 m/s takes about 6 seconds.

Why does BackUp fail with TF lookup errors?

TF errors occur when transform_tolerance on behavior_server is too tight for jittery hardware drivers. Increase it from the default 0.1 to 0.2-0.5 seconds to tolerate stale transforms.

How do I combine BackUp with Spin in a Nav2 recovery sequence?

Use a RoundRobin BT node with escalating sequences: Wait, then Spin, then BackUp followed by Spin, and finally clear the costmap plus a longer BackUp. This tries cheap recoveries before aggressive ones.