udev-rules

Community

Create persistent USB device names with udev.

Authorwimblerobotics
Version1.0.0
Installs0

System Documentation

What problem does it solve?

Linux assigns serial device names dynamically based on enumeration order, which can cause launch files to reference stale device paths after reboots or reconnections. This skill teaches how to write udev rules that create stable symlinks such as /dev/teensy_main, /dev/lidar, and /dev/roboclaw.

Core Features & Use Cases

  • Determine device attributes (vendor, product, serial, kernel path) with udevadm and craft precise rules that match those attributes.
  • Map common robot peripherals (Teensy, LIDAR, motor controllers) to deterministic /dev symlinks, replacing hard-coded device paths in ROS 2 launch files.
  • Debug, reload, and verify rules across plug/unplug cycles to ensure consistent device naming and minimal downtime.

Quick Start

Define a rule that maps a connected Teensy serial device to a persistent /dev/teensy_main symlink, reload udev rules, and verify the symlink exists.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: udev-rules
Download link: https://github.com/wimblerobotics/ros2-copilot-skills/archive/main.zip#udev-rules

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.