lidar-driver-config

Configure ROS 2 lidar driver parameters for LD19, RPLidar, Hokuyo, and Velodyne sensors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a 2D or 3D lidar on a ROS 2 robot requires matching the correct driver package, serial baud rate, frame_id, scan direction, and URDF transform for each sensor model, and small mistakes produce mirrored SLAM maps or disconnected TF trees. ## Core Features & Use Cases - Driver launch configurations: Ready-to-adapt ROS 2 launch snippets for LDROBOT LD19, RPLidar A1/A2/S2 (rplidar_ros and sllidar_ros2), Hokuyo URG-04LX, Velodyne VLP-16, and Livox Mid-360. - Frame and orientation handling: Guidance on frame_id, URDF joint placement, inverted mounting, angle offsets, and fixing mirrored scans caused by wrong scan direction. - Multi-lidar and filtering setups: Merge front and rear scans with ira_laser_tools and clean data with laser_filters range, angular, and median filters. - Use Case: You mount an LD19 upside-down on a mobile robot and your SLAM map appears mirrored; use this Skill to set laser_scan_dir, the inverted flag, and the correct URDF rpy values. ## Quick Start Ask the assistant to generate a ROS 2 launch configuration for your specific lidar model, serial port, and mounting position.

Frequently Asked Questions about lidar-driver-config

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

FAQPage Schema
How do I configure an LD19 lidar with ROS 2?

Use the ldlidar_stl_ros2 package with port_baudrate 230400, set port_name to your serial device, and define frame_id matching your URDF link. Set laser_scan_dir to True so the clockwise LD19 scan matches the ROS counterclockwise convention.

What is the difference between rplidar_ros and sllidar_ros2?

rplidar_ros is the legacy Slamtec driver package while sllidar_ros2 is the current one supporting newer models like the RPLidar S2. Both expose serial_port, serial_baudrate, frame_id, and scan_mode parameters, with sllidar_ros2 adding scan_frequency control.

Why does my SLAM map look mirrored with my lidar?

A mirrored map means the scan direction is wrong relative to the ROS counterclockwise convention. Fix it by toggling the driver's laser_scan_dir or inverted parameter, or by rotating the laser frame 180 degrees in the URDF joint origin.

How do I merge two lidar scans in ROS 2?

Use the laserscan_multi_merger node from ira_laser_tools with your scan topics listed in laserscan_topics and destination_frame set to base_link. It transforms each scan via TF and publishes one unified scan topic for SLAM and navigation.

How do I handle an upside-down mounted lidar in ROS 2?

Set the driver's inverted parameter to True to flip the scan vertically, and add a 180-degree roll (rpy="3.14159 0 0") to the lidar joint in URDF. Verify in RViz that scan points appear at the correct height and orientation.

How do I filter out bad lidar readings before SLAM?

Use the laser_filters package with a scan_to_scan_filter_chain combining LaserScanRangeFilter for distance bounds, LaserScanAngularBoundsFilter to exclude angles blocked by the chassis, and LaserScanMedianFilter to smooth noise.