Pathfinder
RobotForge's own demo robot — an original design, not a copy of anything: a four-wheel skid-steer rover for warehouse aisle patrol, described in one plain paragraph and built entirely by the forge. Entry #004 is ours.
Spec
| Battery | LiPo 14.8 V (4S), 5200 mAh |
|---|---|
| Drivetrain | skid-steer — 4 driven wheels |
| Footprint | 0.42 m x 0.31 m, 0.18 m tall |
| Mass | 3.4 kg |
| Motors | 4x 12 V DC gearmotors |
| Sensors | ultrasonic ranger (front), IMU (centre) |
| Wheels | 100 mm diameter x4 |
examples/pathfinder.jsonRobotForge's in-repo reference design (examples/pathfinder.json), authored for the hackathon demo.Gate runs
Measured against simulator ground truth at the locked thresholds: pass ≤ 5% / 5°, fail over 10% / 10°. The gate tests the spec's simulated twin, not a physical robot.
| Run | Drive vs truth | Turn vs truth | Odometry distance | Odometry heading |
|---|---|---|---|---|
| Run 1 | 1.500% | 4.770° | — | — |
| Run 2 | 1.375% | 2.205° | — | — |
- Run 1: Gate verification on scythe, 2026-10-26 (bindings transport, locked thresholds)
- Run 2: Gate verification on scythe, 2026-10-26 (repeat run)
Harness checks
Electrical computations over this robot's documented wiring graph — voltage drop, ampacity, logic levels, rail budgets, connector matching. Not a gate run and not a simulation: each check is Checked, Partial or Not checked, and the headline is counts, never a blanket pass.
0 checked clean · 0 with warnings · 0 with errors · 0 partial · 21 not checked · missing data: cable.gauge_awg ×8, connector at both ends (connector_from / connector_to) ×7, current_a for motors ×5
| Check | Checked | Partial | Not checked |
|---|---|---|---|
| voltage drop | 0 | 0 | 4 |
| ampacity | 0 | 0 | 4 |
| logic levels | 0 | 0 | 3 |
| rail budget | 0 | 0 | 3 |
| connector match | 0 | 0 | 7 |
Findings: none — the inputs that could be checked raised nothing. That is not the same as everything being checked; the counts above say how much was.
Missing data — the datasheets still to hunt. A check that could not run says what it needs:
| Missing input | Blocks | Needed by |
|---|---|---|
cable.gauge_awg | 8 | battery -> driver, driver -> motors, battery -> controller, controller -> ultrasonic |
connector at both ends (connector_from / connector_to) | 7 | battery -> driver, driver -> motors, battery -> controller, controller -> driver … |
current_a for motors | 5 | battery -> driver, driver -> motors, driver rail |
current_a for ultrasonic | 5 | battery -> controller, controller -> ultrasonic, controller rail |
cable.length_mm | 4 | battery -> driver, driver -> motors, battery -> controller, controller -> ultrasonic |
logic_v for controller | 3 | controller -> driver, controller -> ultrasonic, controller -> imu |
connection voltage (volts) | 2 | driver -> motors, battery -> controller |
current_a for controller | 1 | battery rail |
current_a for driver | 1 | battery rail |
logic_v for driver | 1 | controller -> driver |
logic_v for imu | 1 | controller -> imu |
rated output current for battery | 1 | battery rail |
rated output current for controller | 1 | controller rail |
rated output current for driver | 1 | driver rail |
Report: catalog/harness-reports/pathfinder.json · checked 2026-10-27 · reproduce with robotforge harness examples/pathfinder.json
Take it apart
Every spec becomes a kit of simple, 3D-printable parts (robotforge cad). This viewer lays the kit out the way the kit's own assembly file does, straight from the spec's numbers — flat views, or in 3D with the toggle. Click any part.
examples/pathfinder.json…Reproduce it
Run these from a clone of the repository.
robotforge validate examples/pathfinder.json
robotforge urdf examples/pathfinder.json --out build/pathfinder.urdf
robotforge cad examples/pathfinder.json
robotforge run-gate examples/pathfinder.json
robotforge harness examples/pathfinder.json