Open Source RoboticsRobots, software & learning

Hoverbot

Robot / hardware build

Two-wheel balancing robot project using a Raspberry Pi, pi3hat and moteus motor controllers, with printed parts and source-defined balance settings. [5] [6] [9] [13]

Build & first use →Official websiteBill of materials

For
Experienced builders comfortable with motor configuration, C++ and Raspberry Pi deployment [1]
Cost
No current cost yet. Upstream bill of materials [5]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
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

The reviewed snapshot is commit 83acee48e6648176f81c7ee471fe97089372dfb5, not a stable release. [2]

The mjbots hoverbot repository contains the source and design files for a two-wheel balancing robot. The bill of materials selects a Raspberry Pi 4 with 2 GB RAM, pi3hat, two moteus-c1 controllers and a power distribution board. The two configured joints and the pitch, stand-up and drive control code establish the balancing design; this review did not operate it. [1] [5] [6] [13]

Is this for you?

Known limitations
  • BOM does not specify exact motor and battery products
  • Legacy setup script describes Pi 3B+ while the BOM selects Pi 4
  • Configuration values are source settings, not tested operating limits
  • External Fusion 360 assembly was not preserved

[1] [5] [6] [7] [8] [12]

What you need

Host computer

Ubuntu 22.04 is the documented host build environment; Raspberry Pi is the deployment target.

[1]

Dependencies
  • Bazel build tooling
  • moteus dependency pinned to fe3a19f2c05de9aa36017f7e21f95a2bca362c75
  • pi3hat dependency pinned to ab632c82bd501b9fcb6f8200df0551989292b7a1

[1] [10] [11]

Hardware & parts

Upstream bill of materials [5]

Hardware configuration

Two-wheel balancing platform with printed base, chassis and battery mounting pieces.

Design classification from BOM, two configured joints and pitch/drive control source.

[5] [6] [9] [13] · Editorial assessment

Actuators
  • Two motor channels; exact motor product selection is not specified in the inspected BOM

[5] [6] [8]

Controller

Raspberry Pi 4 with 2 GB RAM, pi3hat and two moteus-c1 motor controllers.

[5]

Sensors
  • IMU orientation data used by the balance controller
  • Hall sensor input configured for each motor

[8] [13]

Assembly & first use

Project documentation [1]

Assembly

Printed PETG parts, heat-set inserts, motor/power wiring and a custom battery PCB are listed; a complete verified assembly sequence was not established.

[4] [5]

Calibration

Match motor electrical and Hall settings, joint sign, IMU mounting and balance gains to the physical configuration.

Editorial configuration checklist; no calibration performed.

[6] [7] [8] · Editorial assessment

Cost

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

3D preview

Preview not available yet. Mesh files were identified. Their source inventory does not by itself establish assembly hierarchy or component placement.

Project notes

Available parts do not yet make a complete shopping list

The bill of materials specifies printed components designed for Prusament PETG on a Prusa MK3s with a 0.6 mm nozzle. It also lists heat-set inserts, fasteners, connectors and wiring. The archive contains STL and 3MF files plus KiCad design and fabrication files for the battery PCB. A Fusion 360 assembly is linked separately from the README and was not preserved or inspected here. [1] [4] [5] [14]

The inspected BOM does not name the exact drive-motor products or the battery pack itself. Battery terminals, mounting hardware and cables do not establish those missing selections. These are material configuration gaps: motor and power choices must be reconciled with the controller settings before a complete build or delivered cost can be specified. No current full cost was verified. [5] [8] [9]

Configuration includes electrical details

The motor setup utility programs two servo IDs on separate pi3hat buses. Its values include Hall sensor configuration, motor pole count, winding resistance, voltage constant and controller gains. The script still carries a quad A1 description, so the file name or introductory comment alone is not a reliable guide to its applicability; the actual two-channel configuration needs inspection. [8]

Preserve utils/config_servos.py with servo 1 on bus 1 and servo 2 on bus 3, including the complete motor settings. Preserve configs/hoverbot.cfg with joint 2 sign −1 and all pitch, yaw and drive gains. In configs/hoverbot.ini, mounting yaw/pitch/roll are 90/0/90 degrees, the real-time and pi3hat CPU affinities are 2 and 3, and max_torque_Nm=3. These values describe the selected source configuration. They are not verified limits or a universal calibration for substitute motors, a differently mounted board or a changed chassis. [6] [7] [8]

Keep the host build and target setup distinct

The README says the host setup should work on Ubuntu 22.04 and gives separate Bazel targets for host tests and a Raspberry Pi deployment archive. The dependency definitions pin moteus and pi3hat to specific commits and archive hashes. Those declarations help identify a build, but the external archives and complete board firmware were not validated as a working combination here. [1] [10] [11]

The preserved target setup script is under utils/rpi3 and describes a Pi 3B+, whereas the BOM specifies Pi 4. It changes boot, network and service settings. Treat it as source to reconcile with the intended target image, rather than proof that an unmodified setup works on every Pi. No setup script, build target or controller configuration was executed during this review. [5] [12]

Scope of the release

The project states that most hardware and software files use Apache 2.0, and the root license notice refers to that license. The preserved mechanical and battery-PCB artifacts are recorded under that project-level statement; external components and dependencies retain their own terms. The profile does not claim a preserved native Fusion assembly, a complete matching firmware set, or a reproduced balancing result. [1] [3] [4] [10] [11]

What we checked

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

Not yet established

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

Updates

Upstream last updated
May 7, 2025 [2]
Latest release
Not established
Profile updated
Oct 4, 2026
Sources last checked
Oct 1, 2026
Next review
Oct 31, 2026
Reviewed revision
83acee48e6648176f81c7ee471fe97089372dfb5 (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 designavailable · Apache-2.0
STL and 3MF files preserved under project-level terms; linked Fusion 360 assembly not preserved or inspected. [1] [3] [4] [5]
electronicsavailable · Apache-2.0
Battery PCB KiCad files and fabrication outputs present. Other purchased electronics are external components. [1] [3] [4]
firmwarenot found · License not fully assessed
Motor configuration utility and external dependency revisions present, but complete matching board firmware payloads were not preserved in this review. [8] [10] [11]
softwareavailable · Apache-2.0
Project states most hardware and software files are Apache 2.0; individual notices and dependency terms remain separate. [1] [3] [4]
documentationavailable · Apache-2.0
Project states most hardware and software files are Apache 2.0; individual notices and dependency terms remain separate. [1] [3] [4]

Selected source-defined balancing control route does not use a learned policy or training dataset.

References

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

Project sources

Videos

  • S015 Josh Pieper (YouTube channel)
    The project’s own YouTube channel, found by searching YouTube and checked against the channel page. Not reviewed by us for accuracy.
    Revision, date & where cited

    YouTube channel Josh Pieper · youtube.com · Accessed Oct 4, 2026

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

Change history

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