sensor-frame-mounting

Mount sensor frames in URDF with fixed joints and accurate origins.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sensor frames in URDF must be defined so that every sensor has a valid TF chain; misalignment leads to incorrect data framing and degraded perception.

Core Features & Use Cases

  • URDF-based mounting: Define fixed joints to attach sensor frames to the robot, ensuring a consistent transform from base_link to sensor_link.
  • Frame conventions guidance: Distinguishes ROS body vs optical frames (e.g., camera optical frame) and provides origin offsets to align sensors with driver frame_ids.
  • Verification guidance: Commands to inspect TF frames and validate transforms to avoid data misplacement in RViz or perception pipelines.

Quick Start

Add a fixed joint in your URDF linking the sensor to its frame and set the origin to the sensor physical offset.

Frequently Asked Questions about sensor-frame-mounting

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

FAQPage Schema
How do I mount a sensor frame in URDF for ROS 2?

To mount a sensor frame in URDF, add a fixed joint linking the sensor to its parent link and set the origin to the sensor's physical offset. This ensures a consistent transform from base_link to the sensor_link for correct ROS 2 TF workflows.

Why does my lidar or camera data appear misaligned in RViz?

Sensor data appears misaligned in RViz due to incorrect URDF sensor frame mounting. Misaligned frames lead to invalid TF chains, causing data framing errors and degraded perception pipelines. Correct frame_id naming and origin offsets are required to fix this.

What is the difference between a ROS body frame and an optical frame for cameras?

A ROS body frame follows the standard X-forward orientation, while an optical frame follows the Z-forward convention used by camera drivers. Defining the correct origin offset between them in URDF aligns the sensor data with the designated frame_id.

How can I verify my URDF sensor transforms are correct in ROS 2?

You can verify URDF sensor transforms by running TF inspection commands to validate the transform chain. This ensures the fixed joints and origin offsets are correctly configured, preventing data misplacement in RViz or downstream perception pipelines.

Do I need a fixed joint to attach a GPS or IMU sensor frame in URDF?

Yes, a fixed joint is required to attach GPS or IMU sensor frames in URDF. Using fixed joints ensures a valid TF chain from the base_link to the sensor_link, preventing frame misalignment and data corruption for mounted sensors.