Open Source RoboticsRobots, software & learning

ExoMy

Robot / hardware build

Six-wheel printed rover with separately preserved build files and ROS software; the reviewed default software uses ROS Melodic and requires per-robot calibration. [1]

Build & first use →Official websiteBill of materials

For
Makers and educators comfortable with printing, wiring and Linux configuration [1]
Cost
No current cost yet. Upstream bill of materials [14] [15]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
host computer, tools, operating system not fully established. Review gaps

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

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

ExoMy is a printed six-wheel rover whose purchasing list specifies six continuous-rotation drive servos, six modified steering servos, a Raspberry Pi 4 Model B, a camera and a PWM servo HAT. It is a hands-on assembly and calibration project, with mechanical files, electrical drawings and a parts spreadsheet in the v1.0.2 release. The saved release archive passed a file-integrity check; this review did not print or assemble it. [14] [15]

Is this for you?

Known limitations
  • Default software and ROS2 wiki instructions describe different configurations
  • ROS2 wiki lists web control as not working
  • Motor mapping and calibration are specific to each assembled rover

[7] [8] [10]

3D preview

ExoMy v1.0.2 default assembly. The complete official ExoMy v1.0.2 A01_ExoMy_Default STEP assembly (release archive, Default configuration) with its source placements and sub-assemblies: printed chassis, bogies, wheels, head and top parts. Vendor and purchased bodies modeled in the source are kept: Parallax servos, Raspberry Pi 4 and Camera V2, Adafruit PWM Servo HAT, LiPo battery, DC/DC boards, switches, cables, zip ties and catalog fasteners. Their third-party CAD terms are unknown. The repository LICENSE is GPL-3.0; the release archive has no license file of its own. No manufacturing or redistribution clearance is claimed, and fit and operation are not verified.

The 3D preview loads after the page.

Drag to orbit · Scroll or pinch to zoom · Right-drag to pan. Use the view buttons for front, side and top views. The tree shows names supplied by the source; unnamed bodies remain labeled as such.

Download original STEP (gzip) · File checksums and provenance

Separate bodies can be inspected in the model tree. Explode is a viewing aid, not an assembly sequence.

Source, license and scale

Source: ESA Planetary Robotics Laboratory / ExoMy contributors, revision b14c7825f4f59d83aadb33e383c95b4a0b142ddd. Original and preview: GPL-3.0 (repository license). Preview conversion by Open Source Robotics; original file unchanged. Preview coordinates are centered and rounded to six decimal places. STEP preview triangulated in millimetres. No physical part tested.

Viewer: three-cad-viewer 5.0.7 (MIT license). Confirm scale and manufacturing settings before printing.

What you need

Dependencies
  • Reviewed default Dockerfile uses ros:melodic, Python pip and Node.js 12 setup
  • Separate software repository
  • Wiki ROS2 instructions target a different ros2/foxy branch

[6] [8] [10]

Hardware & parts

Upstream bill of materials [14] [15]

Hardware configuration

Printed six-wheel rover with independently driven and steered wheels.

[7] [15]

Actuators
  • Six Parallax continuous-rotation drive servos
  • Six modified steering servos

[15]

Controller

Raspberry Pi 4 Model B and PCA9685 PWM servo HAT in the purchasing list.

[15]

Sensors
  • Raspberry Pi Camera V2

[15]

Power

Purchasing list specifies a 3S 3000mAh LiPo battery and two DC/DC converters.

[15]

Assembly & first use

Project documentation [1]

Calibration

Map PWM channels, adjust drive-neutral potentiometers and configure steering neutral positions before installing wheels.

[7]

Cost

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

A parts spreadsheet is a starting point for the budget

The preserved spreadsheet has a cached total of 514.5402, while many printed parts have blank prices. Its extracted price column does not identify a currency, so that value is not presented as a current euro or dollar build cost. The purchasing guide separately calls for a LiPo charger, display, keyboard, mouse and assembly tools, and warns that substituted parts are the builder’s responsibility. The spreadsheet also includes a gamepad-related line even though the guide lists a gamepad among additional items; reconcile the list before ordering to avoid double counting. No complete current supplier quote was obtained. [5] [15]

The listed power configuration uses a 3S 3000mAh LiPo and two DC/DC converters. Printing, wiring and electronics assembly remain part of the project, even when all purchased parts are available. [7] [14] [15]

Project notes

The preserved default software is ROS 1

ExoMy’s control software is in a separate repository. The inspected Dockerfile starts from ros:melodic, installs Python dependencies and uses a Node.js 12 setup script for its web application. The main wiki guide describes a Raspberry Pi OS Buster-era setup. Docker does not establish compatibility with every current host, camera stack or package mirror; this review did not build the image. [6] [10] [11]

The wiki also describes a 64-bit option and a distinct ros2/foxy software branch. Its ROS2 page explicitly lists web control as not working. Do not combine that branch’s instructions with an assumption that the ROS1 web interface will work unchanged. Select and record one software branch, OS image and camera configuration before following the calibration guide. The ROS2 branch was not installed or tested here. [8] [9]

Calibrate the assembled robot before fitting the wheels

The integration guide maps each motor’s PWM channel into the local config/exomy.yaml file. That file is intentionally ignored by Git because the mapping varies between robots. It then uses separate scripts for drive-neutral and steering-neutral calibration: continuous-rotation drive servos need their potentiometers adjusted until the commanded neutral signal actually stops motion. Wheel installation comes after those steps. [7]

The same guide places maximum-steering calibration in a separate development branch. Check which scripts exist in the selected software revision rather than assuming every step belongs to the default release. The run script provides configuration, development and autostart modes, so retain the robot-specific configuration as part of the build record before relying on automatic startup. [7] [11]

The main design repository and separately inspected software repository contain GPL-3.0 license text. This does not establish matching source or reuse rights for every purchased component, external dependency or separately hosted wiki asset. The catalog preserves the available design and software evidence without claiming a tested build or current compatibility across the documented software variants. [3] [12] [13]

What we checked

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

Not yet established

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

Updates

Upstream last updated
Jul 16, 2020 [2]
Latest release
Jun 2, 2020 [2]
Profile updated
Oct 1, 2026
Sources last checked
Oct 1, 2026
Next review
Oct 31, 2026
Reviewed revision
b14c7825f4f59d83aadb33e383c95b4a0b142ddd (release v1.0.2) · 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 designavailable · GPL-3.0
Root repository license and build artifacts; purchased components and separately hosted wiki are not asserted to share blanket licensing. [3] [4] [14]
electronicsavailable · GPL-3.0
Root repository license and build artifacts; purchased components and separately hosted wiki are not asserted to share blanket licensing. [3] [4] [14]
firmwarenot found · License not fully assessed
Matching source for purchased servo electronics not established. [15]
softwareavailable · GPL-3.0
Separate preserved software repository; third-party dependencies retain their licenses. [12] [13]
documentationavailable · GPL-3.0
Root repository license and build artifacts; purchased components and separately hosted wiki are not asserted to share blanket licensing. [3] [4] [14]

This build profile selects no learned policy or training dataset.

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