motor-testing

Test and calibrate Rob Box motor performance and odometry in ROS2 and VESC.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/krikz/rob_box_project --skill motor-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: motor-testing
Source: https://github.com/krikz/rob_box_project/tree/main/.agents/skills/motor-testing
Command: npx skills add https://github.com/krikz/rob_box_project --skill motor-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Motor testing, movement calibration and odometry verification for Rob Box robot. Use when testing motor response, calibrating gear_ratio or min_duty, verifying odometry accuracy, or diagnosing movement issues (speed amplification, turning problems, deadzone compensation).

Core Features & Use Cases

  • Motor testing and calibration of gear_ratio and min_duty
  • Odometry verification and troubleshooting movement issues in Rob Box

Quick Start

Run the move_test.py script with appropriate speed and duration to perform a basic motor test.

Frequently Asked Questions about motor-testing

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

FAQPage Schema
How do I calibrate gear_ratio and min_duty for a VESC motor in ROS2?

To verify odometry accuracy in a ROS2 and VESC setup, use this skill to run movement tests and diagnose speed or turning issues. It validates wheel parameters and exposes odometry data to ensure deadzone compensation and speed calculations are correct.

Why does my robot speed amplification or deadzone cause turning problems during odometry testing?

Speed amplification and turning problems during odometry testing stem from uncalibrated min_duty and gear_ratio values. Use this skill to diagnose movement issues by applying deadzone compensation and verifying wheel parameters within your ROS2 control stack.

How do I run a basic motor test to diagnose movement issues?

Run the move_test.py script with appropriate speed and duration parameters to perform a basic motor test. This executes movement testing to diagnose speed, turning, and deadzone issues while verifying odometry accuracy for the robot.

Can I use this motor testing approach for a ROS2 and VESC-based control stack?

Yes, this approach satisfies requirements for exposing gear_ratio, min_duty, wheel parameters, and odometry validation in a ROS2 + VESC-based control stack. It supports motor performance testing and odometry verification for the Rob Box robot.

What is the best way to verify odometry accuracy after changing wheel parameters?

The best way to verify odometry accuracy after changing wheel parameters is to run movement testing and odometry verification scripts. This skill diagnoses resulting speed and turning issues to ensure the ROS2 control stack accurately reflects the new calibration.