メニュー
Launch ArduPilot SITL simulator. Use when the user asks to start SITL, run the simulator, or test a vehicle interactively.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review an ArduPilot new-board hwdef PR. Stashes any local changes, checks the PR out as a branch in the current repo, runs DMA / board-ID / file-presence / commit-structure checks, layers the hwdef playbook on top, and (after confirmation) posts a review comment on the PR — then restores the original branch and pops the stash. Use when the user asks to review or pre-review an hwdef PR.
Review an ArduPilot new-board hwdef PR. Stashes any local changes, checks the PR out as a branch in the current repo, runs DMA / board-ID / file-presence / commit-structure checks, layers the hwdef playbook on top, and (after confirmation) posts a review comment on the PR — then restores the original branch and pops the stash. Use when the user asks to review or pre-review an hwdef PR.
Analyze ArduPilot DataFlash .bin log files or MAVLink .tlog telemetry logs. Use when the user provides a .bin or .tlog log file path or asks to analyze flight log data.
Analyze ArduPilot DataFlash .bin log files or MAVLink .tlog telemetry logs. Use when the user provides a .bin or .tlog log file path or asks to analyze flight log data.
Check the local ArduPilot AI Playbook version against the upstream GitHub version and update if newer. Use when the user asks to update the playbooks, check for playbook updates, or wants to know which version is installed.
Write ArduPilot CRSF (Crossfire) menu scripts using crsf_helper.lua. Use when the user asks to create or modify CRSF/ELRS transmitter menus.
| name | sitl |
| description | Launch ArduPilot SITL simulator. Use when the user asks to start SITL, run the simulator, or test a vehicle interactively. |
Start an interactive SITL simulation session.
Parse $ARGUMENTS for vehicle type and options:
/sitl copter — start Copter SITL/sitl plane — start Plane SITL/sitl rover — start Rover SITL/sitl copter --debug — start with GDB attached/sitl copter -I 1 — second instance (different ports)| Argument | sim_vehicle.py -v value |
|---|---|
copter | ArduCopter |
plane | ArduPlane |
rover | Rover |
sub | ArduSub |
tracker | AntennaTracker |
heli | ArduCopter (with --frame heli ) |
blimp | Blimp |
python3 Tools/autotest/sim_vehicle.py -v <Vehicle> [options]
| Option | Purpose |
|---|---|
--debug | Build with debug symbols and launch under GDB |
-I <n> | Instance number (0-based, for multi-vehicle) |
--frame <frame> | Vehicle frame (e.g., hexa, octa, heli, quadplane) |
-L <location> | Start location (e.g., CMAC, AVC2013) |
--map | Show map window |
--console | Show console window |
--no-mavproxy | Don't start MAVProxy (just the simulator) |
--speedup <n> | Simulation speed multiplier |
-A "<args>" | Extra arguments passed to the SITL binary |
--add-param-file <file> | Load additional parameter file |
# Basic copter SITL with map
python3 Tools/autotest/sim_vehicle.py -v ArduCopter --map --console
# QuadPlane
python3 Tools/autotest/sim_vehicle.py -v ArduPlane --frame quadplane
# Hexacopter at specific location
python3 Tools/autotest/sim_vehicle.py -v ArduCopter --frame hexa -L CMAC
# Multi-instance for swarm testing
python3 Tools/autotest/sim_vehicle.py -v ArduCopter -I 0 &
python3 Tools/autotest/sim_vehicle.py -v ArduCopter -I 1 &
sitl board to be configured (./waf configure --board sitl)quit in the MAVProxy console