Proposed outcome
Build a differential-drive car that accepts bounded wireless commands, stops when the command link disappears, and records enough telemetry to explain its behavior.
All project proposals
Ground robotics project
Programmable RC Car
Build a small remote-controlled car, then add telemetry and speed feedback as a robotics foundation.
BeginnerCore Engineering
Recommended platform
Start with a Pololu Romi chassis or a comparable two-wheel differential-drive kit with encoder-ready motors. Use an ESP32 or Raspberry Pi Pico W for the first controller so motor control and safety stay visible.
Readiness checklist
Review the skills, goals, acceptance tests, and safety limits before committing to the build.
Prerequisites
- Basic Python or Arduino-style C/C++.
- Comfort measuring DC voltage and continuity with a multimeter.
- A basic understanding of PWM, motor direction, and common ground.
Learning goals
- Choose motors, drivers, batteries, and wiring with current limits in mind.
- Build a wireless command loop with a dead-man failsafe.
- Collect telemetry that explains real robot behavior.
Success criteria
- Drive forward, backward, left, and right from a wireless controller.
- Stop the motors within 300 ms when fresh commands stop arriving.
- Run for five minutes without controller brownouts, loose wiring, or an overheated driver.
- Log command, PWM, battery voltage, encoder counts, and fault state.
- Publish a wiring diagram, bill of materials, test log, demo, and postmortem.
Safety and scope constraints
- Manual RC control comes before autonomy.
- Motor driver current limits must exceed expected load.
- Commands must time out to a safe stop.
Build phases
Parts are cumulative. Pass the exit gate before buying for or starting the next phase.
Phase 1: Requirements and bench setup
Choose a drivetrain and power architecture, read the motor and driver limits, and draw the wiring before connecting power.
Parts for this phase
- Two-wheel differential-drive chassis with two DC gearmotors
- ESP32 or Raspberry Pi Pico W-class controller
- Dual H-bridge sized above motor stall current
- 4xAA NiMH pack or protected battery pack with matching charger
- Main switch, fuse, multimeter, hookup wire, and connectors
Exit gate
Explain the motor-power, logic-power, ground, PWM, direction, and emergency-stop paths from the diagram.
Phase 2: Motor driver bench test
Control one motor at low power and verify forward, reverse, coast, brake, current draw, and controller stability.
Parts for this phase
- One drivetrain motor
- Selected motor driver and microcontroller
- Battery pack or current-limited bench supply
- Motor suppression capacitors and bulk decoupling capacitor
Exit gate
Repeat ten start, stop, and direction-change cycles without a reset, thermal shutdown, or loose connection.
Phase 3: Rolling chassis
Mount the electronics securely, drive from a tethered command script, and calibrate left/right trim.
Parts for this phase
- Complete chassis, wheels, caster, and mounting hardware
- Standoffs, screw terminals or locking connectors, and heat shrink
- Accessible main power switch
Exit gate
Drive two meters, stop on command, and repeat the same test five times at a conservative speed limit.
Phase 4: Wireless control and failsafe
Add browser, laptop, phone, or gamepad control with normalized commands, speed limits, and a dead-man timeout.
Parts for this phase
- Wi-Fi or BLE already provided by the controller
- Laptop, phone, or USB gamepad
- Status LED or buzzer for armed, fault, and low-battery states
Exit gate
The car stops by itself when the controller closes, Wi-Fi drops, or command packets become stale.
Phase 5: Telemetry, encoders, and PID
Measure wheel speed, plot command versus response, and add closed-loop speed control only after the raw data is trustworthy.
Parts for this phase
- Two quadrature encoder kits or encoder-equipped motors
- Battery-voltage divider and optional current sensor
- Laptop with Python, CSV logging, and plotting tools
Exit gate
Produce repeatable straight-line and turn-in-place plots and explain steady-state error, overshoot, and battery sag.
Phase 6: Field test and portfolio writeup
Run a repeatable acceptance test and leave enough evidence for another learner to reproduce the build.
Parts for this phase
- Measured indoor test course
- Phone or camera for demo media
- No new electronics required
Exit gate
Complete a five-minute run and publish the build guide, diagrams, source, logs, plots, demo, and failure postmortem.
Kits and references
Use these established platforms, guides, and repositories to validate component choices and implementation details.
Pololu Romi chassis kit
A compact differential-drive chassis with gearmotors, encoder-ready shafts, wheels, caster, and AA battery contacts.
SunFounder PiCar-X
A Raspberry Pi car kit with camera, ultrasonic ranging, line sensors, Python examples, and mobile control.
NVIDIA JetBot
An open reference robot with compatible kits and notebooks for motor control, collision avoidance, and vision.
Romi 32U4 Arduino library
Pololu's official drivers and examples for the Romi 32U4 control board.
PiCar-X Python library
SunFounder's open Python package and examples for the PiCar-X platform.
NVIDIA JetBot
The reference JetBot software, notebooks, setup tools, and learning examples.
Links and recommendations reviewed July 10, 2026.
The other current proposal
Compare the ground and aerial platforms before choosing where to invest your build time.