Open Source RoboticsRobots, software & learning

e-puck

Robot / hardware build

Small wheeled research robot; this profile covers e-puck2 using its official hardware guide, pinned Qt monitor and separately preserved STM32F407 firmware sources. [1] [2] [5] [6]

Build & first use →Official website

For
Researchers distinguishing e-puck generations and firmware variants [1]
Cost
No current cost or bill of materials established yet.
Source rights
Some licenses are unresolved. Review licenses
Unknowns
host computer, tools not fully established. Review gaps

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

Upstream paper photograph of an e-puck2 robot (Figure 1, 2023).
Upstream paper photograph of an e-puck2 robot (Figure 1, 2023). Daniel H. Stolfi and Grégoire Danoy · CC-BY-4.0. Embedded image extracted from page 2 of the source PDF and losslessly decoded to PNG; no retouching. Preview re-encoded for faster display; the link opens the original file.
Licenses & related hardware
License
GPL-2.0-or-later · license not fully assessed for firmware, documentation · Details by part

Requirements · Research details and dates

On this page

Overview

The e-puck2 is a small wheeled research robot with sensing and expansion interfaces. This profile selects e-puck2, while retaining the catalog's broader e-puck name. The original primary archive is the Qt desktop monitor, not a complete robot source package. The official guide and separately preserved STM32F407 firmware establish the additional context. [1] [5] [6]

Is this for you?

Known limitations
  • Original primary archive is a desktop monitor, not the whole robot
  • Main firmware source archive omits ten linked submodule payloads
  • Radio firmware differs between hardware 2.0/2.1 and 2.2
  • Programmer-update procedure differs for robot IDs at or above 5400

[1] [5] [7]

What you need

Operating system
  • Qt monitor documented for Windows, macOS and Linux; current OS compatibility not tested

[1] [5]

Dependencies
  • Matched robot generation and hardware revision
  • Correct firmware for main controller, radio and programmer
  • Qt 5.10.0 for the selected monitor build documentation
  • Separate main-firmware submodules and toolchain

[1] [5] [7]

Hardware & parts

Hardware configuration

Compact wheeled research platform; e-puck2 is the selected generation.

[5]

Actuators
  • Two geared stepper motors
  • LEDs including radio-controlled RGB LEDs
  • Speaker

[5]

Controller

STM32F407 main controller, STM32F413 programmer/power-management controller and ESP32 radio module.

[5] [6]

Sensors
  • Infrared proximity and ambient sensing
  • Front time-of-flight distance sensor
  • IMU
  • Camera and digital microphones; component revisions vary

[5]

Assembly & first use

Project documentation [1]

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

One robot has three different controller roles

The main STM32F407 handles sensors, actuators and robot algorithms. An STM32F413 provides programming/debugging and power-management functions. The ESP32 handles wireless communication and also controls the RGB LEDs and user button. Treating every behavior as main-controller firmware would miss those dependencies. [5]

The official documentation records changes within the e-puck2 family: the camera changed around July 2019, while hardware 2.2 changes the IMU and adds ESP32 PSRAM. It supplies separate radio factory images for hardware 2.0/2.1 and 2.2. These are configuration boundaries, not interchangeable specifications. No physical unit was inspected to identify its variant. [5]

The desktop-monitor route is narrower than embedded development

With the documented factory firmware, the guide uses selector position 8 and the main-controller USB serial port for the monitor. The debugger and radio serial ports are separate, and their operating-system numbering can vary. The monitor can display sensor information and camera images and control outputs, but using it is optional. [5]

The preserved monitor revision is b7fd0ae3095f56eda37027df8f54cfc0d16ec60d. Its build README names Qt 5.10.0 and historical deployment procedures. Those instructions do not establish compatibility with every current operating system. No application was installed, compiled or connected to a robot during this review. [1] [2]

Preserve firmware dependencies before claiming reproducibility

The separately archived main firmware is commit 3f174338a0bcc0e21cb75b5bd16dead0b2828a36. Its Git configuration lists ten submodules, including ChibiOS, Aseba and supporting communication libraries. Those payloads are not included merely by preserving the parent repository archive. The radio and programmer are also separate source and binary qualification tasks. [6] [7] [8]

The guide distinguishes classic Bluetooth factory operation from dedicated WiFi and BLE firmware routes, and provides a separate macOS 15 BLE option. It also warns that programmer updates differ for robot IDs at or above 5400. This profile records the distinctions without prescribing a flash operation for an unidentified robot. No firmware or bootloader was changed. [5]

What we checked

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

Not yet established

  • Requirements: host computer, tools
  • A step-by-step setup summary

Updates

Upstream last updated
Mar 9, 2021 [2]
Latest release
Not established
Profile updated
Oct 26, 2026
Sources last checked
Oct 1, 2026
Next review
Oct 31, 2026
Reviewed revision
b7fd0ae3095f56eda37027df8f54cfc0d16ec60d (commit snapshot; no published stable release found) · 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
Official hardware descriptions available, but complete matched fabrication CAD/PCB sources and licenses not established in the selected software archives. This is not a claim that no hardware designs exist elsewhere. [4] [5] [8]
electronicsnot found · License not fully assessed
Official hardware descriptions available, but complete matched fabrication CAD/PCB sources and licenses not established in the selected software archives. This is not a claim that no hardware designs exist elsewhere. [4] [5] [8]
firmwareavailable · License not fully assessed
Main STM32F407 firmware only. Complete licensing across source components and ten submodule dependencies is unresolved; radio/programmer sources were not preserved in this review. [6] [7] [8] [9]
softwareavailable · GPL-2.0-or-later
Monitor source notice allows GPL version 2 or later; included COPYING contains GPL3. This does not license the entire robot firmware or hardware. [1] [3] [10]
documentationavailable · License not fully assessed
Official guide preserved; an explicit blanket reuse license for wiki text/images was not established. [5]

Selected conventional robot and monitor workflow does not require learned policy weights or training data.

License the source layer that was actually reviewed

The monitor's source notice allows GPL version 2 or later, while its included COPYING file contains GPL version 3. That software license does not establish the rights for all robot firmware or hardware. The selected main-firmware archive and its dependencies still need a complete component-license review. Complete matched fabrication CAD and PCB packages were not established from these software sources. [3] [4] [7] [8] [10]

The remaining build questions are concrete: identify the actual robot revision, match all three firmware roles and host tools, and establish delivered costs and applicable source rights. The catalog has not tested motion, camera performance, wireless behavior or sensor accuracy. [5]

References

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

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

Change history

2026-10-26 — Added attributed upstream media with linked reuse terms; technical evidence dates unchanged.