Open Source RoboticsRobots, software & learning

Donkey Car

Robot / hardware build

Python RC-car platform for manual driving and optional learned control; reviewed Raspberry Pi/PCA9685 build guidance has OS-version conflicts and an incomplete parts budget. [1]

Build & first use →Official websiteBill of materials

For
Builders comfortable with RC hardware, Raspberry Pi configuration and Python environments [1]
Cost
No current cost yet. Upstream bill of materials [5]
Source rights
Some licenses are unresolved. Review licenses
Unknowns
tools not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware
License
MIT · license not fully assessed for electronics, documentation · Details by part

Requirements · Research details and dates

On this page

Overview

Donkey Car combines a purchased RC vehicle with a computer, camera and Python control pipeline. This profile selects the Raspberry Pi/PCA9685 route described for HSP94186 or Exceed Magnet-style cars. Other RC chassis may require different mounts, servos or motor controllers, so the platform name does not identify one interchangeable kit. The software snapshot reviewed here is release 5.4.0; the build guide was preserved separately. [2] [5] [10]

Is this for you?

Known limitations
  • Mutable documentation checkout differs from pinned software release
  • OS headings conflict within Pi setup guide
  • External printed-design files and their rights not fully reconciled
  • No complete current build budget

Source comparison and review scope, not a reproduction result.

[5] [7] [10] · Editorial assessment

What you need

Operating system
  • Pi guide introduction specifies64-bit Raspberry Pi OS Trixie for5.4; later heading still says Bookworm

[7]

Host computer

Onboard Raspberry Pi; separate Linux, Windows or macOS host for the documented learned-policy training workflow.

[5] [8]

Dependencies
  • Release Python requirement >=3.12,<3.14
  • Pi extra includes LiteRT; PC training extra includes TensorFlow2.19
  • Camera and PWM hardware configured for selected drivetrain

[9] [5] [6]

Hardware & parts

Upstream bill of materials [5]

Hardware configuration

Selected guide route: purchased HSP94186/Exceed Magnet-style RC chassis with Raspberry Pi, camera and PCA9685 steering/throttle interface.

[5]

Actuators
  • Purchased RC steering servo
  • Purchased RC drive motor and ESC

[5] [6]

Controller

Raspberry Pi with PCA9685 PWM board controlling the RC steering servo and ESC.

[5] [6]

Sensors
  • Raspberry Pi camera in the selected guide route

[5]

Assembly & first use

Project documentation [1]

Assembly

Fit a printed mounting plate and roll cage, camera, Pi and PWM board to the chosen purchased chassis.

[5]

Calibration

Record actual steering endpoints and ESC forward, stopped and reverse settings in myconfig.py; initial calibration with car elevated.

[6]

Cost

No current, complete configuration-specific build cost has been established for this profile.

3D preview

Preview not available yet. Design-source links are available, but the reviewed record does not establish unambiguous reuse rights for a hosted CAD preview.

Project notes

Complete the parts list for the selected car

The hardware guide lists the car, Pi, camera, storage, USB power bank, PWM board and fasteners, but gives printed mounting parts an unpriced placeholder. It also discusses chassis-specific adapters hosted elsewhere. Those omissions prevent the table from establishing a complete delivered budget. This review has not acquired and reconciled all external print files or their licenses. [5]

The guide’s hardware table names a Pi 5B with 8GB RAM and a 64GB card, while the software page recommends a Pi 4 or 5 with 4GB RAM and a 128GB card. Treat these as different documented choices to resolve, not as one exact bill of materials. The RC vehicle’s own steering servo, ESC and motor remain purchased components. [5] [6] [7]

The saved installation guide contains a version conflict

The Pi setup page opens by saying Donkey Car 5.4 requires 64-bit Raspberry Pi OS Trixie, but its installation heading and following sentence still name Bookworm. Its environment command uses Python 3.13. The software release metadata independently requires Python at least 3.12 and below 3.14, with separate Pi and host-training dependency groups. [7] [9]

The guide’s developer installation also checks out main, which does not reproduce the pinned release automatically. Select and record the OS image, Python environment and software revision together before treating the instructions as a repeatable setup. No installation or compatibility test was performed here. The guide also says TensorFlow Lite models need regeneration across the versions it discusses; existing model files should not be assumed compatible. [7]

Calibrate the actual steering and ESC

The calibration guide directs builders to raise the car off the ground, find steering endpoints without forcing the servo, and save the values in myconfig.py. The ESC needs its own forward, neutral and reverse settings; the guide describes a reverse-neutral-reverse sequence for RC controllers that require it. Its example PWM numbers are starting points, not measurements of your car. [6]

After initial calibration, the guide checks straight driving and adjusts the steering settings. Preserve those configuration values with the chosen drivetrain and PWM channel mapping. A working camera and manual driving configuration are prerequisites to collecting useful demonstrations, not evidence that an autonomous policy will generalize to a new track. [6] [7] [8]

Training and hardware openness are separate questions

The documented learned-driving route uses data collected on the car and a separate host computer for training. The inspected package has distinct Pi inference and host training dependencies. This profile does not select or validate a trained model, dataset or autonomous-driving result. [8] [9]

The software repository carries an MIT license. That license does not establish rights to the separately hosted build documentation, external printed parts or purchased RC components. The documentation archive was preserved, but no license file was identified in its inventory. No assembly, calibration, model training or driving test was performed for this entry. [3] [10]

What we checked

Source research only; no installation, physical build or performance test performed. No affiliate links added.

Not yet established

  • Requirements: tools
  • A step-by-step setup summary

Updates

Upstream last updated
Aug 22, 2026 [2]
Latest release
Aug 22, 2026 [2]
Profile updated
Oct 4, 2026
Sources last checked
Oct 1, 2026
Next review
Oct 31, 2026
Reviewed revision
59b6a5fed7b7fb3ba0c77577fe2970bb5ff4abc2 (release 5.4.0) · combined hardware and software repository

Source files and licenses

Available project sources support research coverage; complete build and commercial qualification remain separate.

LayerAvailability / license
mechanical designnot found · License not fully assessed
Matching complete source and rights not established in inspected archives. External print files and purchased RC components require separate reconciliation; not a claim of closed source. [4] [5] [10]
electronicsavailable · License not fully assessed
Assembly and connection instructions available; complete manufacturer design source and hardware reuse terms not established. [5]
firmwarenot found · License not fully assessed
Matching complete source and rights not established in inspected archives. External print files and purchased RC components require separate reconciliation; not a claim of closed source. [4] [5] [10]
softwareavailable · MIT
Selected software repository; external hardware, models and dependencies are not blanket covered. [3] [9]
documentationavailable · License not fully assessed
Separate documentation source preserved; license file not identified in its archive inventory. [5] [10]

Physical platform/manual-control route selected; optional training workflow does not select a qualified model or dataset.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Project sources

Videos

Correction guidance · Discussion is not enabled · Profile format 0.6.0-draft.1

Change history

2026-10-04 — Added 1 YouTube reference(s) (S011): official channel or videos linked from the pinned upstream sources. Existing claims, source-check dates and evidence are unchanged.