Skip to the content
2 layers64.5 × 94.5 mmPuppybot, the printed circuit board in 3D

PuppyBot's controller, Linux runtime, simulator, visual-control training and classic ESP32 serial firmware are implemented in Flexscript. The maintained source is in src/, organized by purpose.

Size
64.5 × 94.5 mm
Copper layers
2
Thickness
1.6 mm
Parts
20
Nets
34
Pads
123
Tracks, vias
67, 0
Routed
Yes
KiCad
KiCad 9.0 (file 20241229)
Created
9 Mar 2025
Updated
4 Nov 2026

Overview

Puppybot is an open-source printed circuit board by puppycorp, from the puppycorp/puppybot repository on GitHub. It is a 2-layer board of 64.5 × 94.5 mm with 20 parts on 34 nets, routed with 67 tracks and 0 vias.

It is built around the ESP32-C3-WROOM-02-H4, L298N and XL4015E1. Its parts include 10 capacitors, 3 ICs and 3 connectors. It belongs with the ESP32 and RISC-V boards of this library.

Main components

3

README

readme.md

PuppyBot

PuppyBot's controller, Linux runtime, simulator, visual-control training and classic ESP32 serial firmware are implemented in Flexscript. The maintained source is in src/, organized by purpose.

Run

From the repository root:

sh
flexscript run puppybot.flex

Open http://127.0.0.1:8081/ for the robot dashboard. The default is a fake servo bus. The launcher compiles and executes the native runtime; configuration comes from puppybot.json. See the controller instructions for physical serial control and output enable.

Run a separate 3D simulator with flexscript run simulator.flex. It prints the private serial device and the controller connection command. For the lightweight servo model use flexscript run simulator.flex --servo-only.

For autonomous simulation and visual-control experiments:

sh
flexscript run sim.flex --list-cases
flexscript run sim.flex --case house-blocks-into-box --drift 10
./src/control.sh build

See simulation, visual control, Gym and exploration. Python remains in experiment orchestration, data preparation and independent verification; the repository is not exclusively Flexscript.

Build and verify

Install Flexscript and keep the sibling ../flexscript Git checkout available. The native build snapshots a pinned compiler/library revision from that checkout into build/native-toolchain; it never changes the sibling checkout. Set FLEXSCRIPT_SOURCE to use another checkout containing that revision. To supply an already verified matching toolchain instead, set FLEXSCRIPT_COMPILER and FLEXSCRIPT_ROOT (and FLEXSCRIPT_SOURCE for firmware link tooling).

sh
./src/scripts/build-runtime.sh
./src/scripts/test-runtime.sh

These commands build and test the native controller, HTTP/WebSocket runtime, CLI, serial simulator and simulated firmware without the GPU training toolchain. The tests use loopback sockets and private PTYs, not a physical robot.

The broader ./src/scripts/build.sh and ./src/scripts/test.sh include Gym, vision, controller differential tests and additional tooling. They require a compatible Flexscript source checkout and GPU libraries; set FLEXSCRIPT_ROOT and follow the detailed build instructions.

For classic ESP32 serial firmware:

sh
python3 src/scripts/prepare-esp32-tools.py
./src/scripts/build-esp32.sh

See firmware wiring, verification and flashing. The Flexscript target is serial-only: Wi-Fi/WebSocket/mDNS, Android wireless control, persistent calibration and physical hardware qualification are still separate work. Replacing the source layout does not establish those capabilities.

Repository layout

PathPurpose
src/core/, src/transport/Shared controller, kinematics, safety and protocol
src/runtime/, src/host/, src/cli/Linux service, dashboard, serial adapter and CLI
src/firmware/, src/platform/ESP32 and simulated firmware adapters
src/sim/, src/simulator/, src/gym/3D simulation, serial plant and rollout UI
src/control/, src/ml/, src/vision/, src/exploration/Learning, inference and navigation
src/scripts/, src/tests/Build tools and verification
tests/reference/rust-core/Original Rust controller used only as a test oracle
datasets/, experiments/, diary/Dataset recipes, experiment programs and research notes
build/flex/sim/Local generated datasets and experiment artifacts
models/, robotdreams/Owned assets and retained historical scene/calibration evidence
android/, python/, design/Android client, servo service utilities and electronics

The Rust runtime, CLI, ESP32 firmware and collision tools are retired from the maintained source tree; earlier versions remain in Git history. The native build workflow packages Flexscript runtime binaries and the Flexscript ESP32 ROM image. The Android client remains a separate application.

flex is a compatibility symlink to src; puppybot/core points to the Rust test reference. New development uses the canonical paths. Existing experiments, receipts and build/flex output paths are not renamed by this migration. Source changes still require fresh provenance checks before an old run can be repeated; a compatibility path does not guarantee identical source hashes.

Dataset storage

Actual data lives primarily under build/flex/sim/; datasets/ contains recipes and documentation. Follow the storage rules: budget every run, preserve required evidence, review retention when it finishes, and verify physical space recovered after cleanup. Git-ignored data is not necessarily disposable.

Parts

20
QtyValueFootprintReferences
5CCapacitor_SMD:C_0805_2012MetricC1, C4, C6, C7, C10
5C_PolarizedCapacitor_THT:CP_Radial_D5.0mm_P2.00mmC2, C3, C5, C8, C9
4Motor_DCTerminalBlock_RND:TerminalBlock_RND_205-00234_1x04_P5.08mm_HorizontalM1, M2, M5, M6
3XL4015Connector:FanPinHeader_1x04_P2.54mm_VerticalJ1, J2, J3
2L298NPackage_DIP:DIP-16_W7.62mmU1, U4
1ESP32-C3-WROOM-02RF_Module:ESP32-C3-WROOM-02U2

Similar boards

  • 2 layers56.4 × 21 mmOptiplower, the printed circuit board in 3D

    Optiplower

    jamwaffles/optiplower

    Power a Dell Optiplex 3050 Micro from a 24V industrial power supply

    22 parts33
  • 2 layers120 × 100 mmRoot, the printed circuit board in 3D

    Root

    GonzaCerv/noah-hardware

    This repo contains all the hardware description for the Noah project. Here lies 3D models, electronics PCB and Firmware software of the robot.

    127 parts28MIT
  • 2 layers80.9 × 92.7 mmEvo Borne, the printed circuit board in 3D

    Evo Borne

    SRA-VJTI/Evo-Borne

    This repository focuses on building an open-source morphobot.

    126 parts12MIT
  • 2 layers65 × 100 mmSyringe pump, the printed circuit board in 3D

    Syringe pump

    wenzel-lab/syringe-pumps-and-controller

    Design of 3d printable syringe pumps and dual controller.

    141 parts11
  • 2 layers92 × 72.2 mmDevelopower v2.0, the printed circuit board in 3D

    Developower v2.0

    leoheck/developower-v2.0

    Developower-v2.0 Board

    50 parts8
  • 2 layers88 × 114.3 mmMicromouse, the printed circuit board in 3D

    Micromouse

    Ojasp21/Micromouse

    The dimensions of our full-size micromouse is 11.5 x 10 cm

    95 parts8
  • 2 layers237 × 139.1 mmMothbox 5.0.6, the printed circuit board in 3D

    Mothbox 5.0.6

    Digital-Naturalism-Laboratories/Mothbox_Electronics

    This is where the electronics for the Mothbox are developed, such as the PCB! It's copied over from https://github.com/Digital-Naturalism-Laboratories/Mothbox/tree/main/Hardware/PCB so you can check that out if you want…

    185 parts3MIT
  • 2 layers143.5 × 110.2 mmTest platform, the printed circuit board in 3D

    Test platform

    kwiecinski/MultiChem-Battery-Tester

    Multi-chemistry (Lithum, PB and others) battery charger/discharger with capacitance measurement and discharge graph for diffrent charge/load currents.

    151 parts2MIT

Questions

How big is the Puppybot PCB?

It measures 64.5 × 94.5 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Puppybot use?

20 parts, built around the ESP32-C3-WROOM-02-H4, L298N and XL4015E1. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Puppybot KiCad files?

From the puppycorp/puppybot repository on GitHub, at the commit this page was made from: the board is design/puppybot.kicad_pcb and its schematic design/puppybot.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Puppybot design in my own project?

Its repository states no licence, so its author keeps all rights: ask puppycorp before reusing the design.