Open Source RoboticsRobots, software & learning

DIY hobby-servos quadruped

Robot / hardware build

Twelve-servo Raspberry Pi/Arduino quadruped with downloadable CAD and Python gait code; hardware is noncommercial source-available and manual calibration is required. [1]

Build & first use →Official websiteBill of materials

For
Experienced makers able to read Python and commission servo electronics [1]
Cost
No current cost yet. Upstream bill of materials [5]
Source rights
Some licenses are unresolved. Includes noncommercial terms. 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
License
CC-BY-NC-SA-4.0 (noncommercial), GPL-3.0-only · license not fully assessed for documentation · Details by part

Requirements · Research details and dates

On this page

Overview

Miguel Ayuso Parrilla's quadruped combines twelve hobby servos with a Raspberry Pi 4 and Arduino Mega. Python supplies kinematics and gait generation, while the Arduino handles servo and sensor signals. The original component list identifies DS3218 PRO servos and an MPU6050 IMU. This is a maker research build with manual setup work, not a documented plug-and-play kit. [1] [5] [6]

Is this for you?

Known limitations
  • Hardware uses CC-BY-NC-SA-4.0 terms and is not unrestricted open hardware
  • Original Arduino build differs from the later Teensy/BNO055 development log
  • Raspberry Pi installation guidance is incomplete and manual calibration is required
  • Historical logs report servo heating and occasional incorrect kinematic solutions; resolution unverified
  • Current complete cost and hardware compatibility remain unverified

Source-available classification reflects explicit noncommercial terms; no legal interpretation beyond stated restriction.

[5] [6] · Editorial assessment

3D preview

DIY hobby-servo quadruped V2 STEP assembly. The creator V2 whole-robot STEP assembly: quadruped_v2.step from the Hackaday.io file Quadruped robot_V2-STEP.zip (uploaded August 12, 2020; a Fusion 360 export with root quadruped_v6 v197), with its source placements and sub-assemblies: four legs (coxa, femur and tibia groups), body, front and back covers, batteries, a Raspberry Pi 4, an Arduino Mega and four UBEC regulators. Purchased component models, including twelve DS3225MG servos, metal servo arms, rod-end bearings, 18650 cells, nuts and screws, are kept as placed; their third-party terms are unknown. One bearing part in the export contains no geometry, so it does not appear. The single-leg file leg_v2.step in the same ZIP, the printable STL set and the later PyBullet URDF branches are not shown. Licensed CC BY-NC-SA 4.0 (noncommercial, share-alike); no commercial-use or manufacturing clearance is claimed. Fit and function are not verified.

Noncommercial license: the creator project page on Hackaday.io states “This project uses the Attribution-NonCommercial-ShareAlike 4.0 International for all hardware components.” (software is GPL v3). This preview and the hosted original ZIP remain under CC BY-NC-SA 4.0 with attribution to Miguel Ayuso Parrilla; shared adaptations stay under the same license. No commercial-use or manufacturing clearance is claimed. Purchased component models in the assembly (Raspberry Pi 4, Arduino Mega, UBEC regulators, 18650 cells, DS3225MG servos, metal servo arms, bearings, nuts and screws) are kept as placed; their third-party terms are unknown. License: CC BY-NC-SA 4.0 (hardware, creator project page) · upstream notice.

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 V2 STEP ZIP from the creator (unchanged; contains quadruped_v2.step and leg_v2.step) · 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: Miguel Ayuso Parrilla (miguelasd688), revision Hackaday.io file Quadruped robot_V2-STEP.zip (uploaded 2020-08-12), sha256 4c7c8df851030f01a2c55080417495db4431f0836f3f3d97c7ec99315a08e052. Original and preview: CC-BY-NC-SA-4.0. 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
  • Python 3 with numpy, csv, evdev, pyserial and simple-pid as listed upstream
  • Arduino firmware for serial servo/IMU communication
  • Pandas and matplotlib for optional telemetry

[1] [5]

Hardware & parts

Upstream bill of materials [5]

Hardware configuration

Printed quadruped with three hobby servos per leg.

[5]

Actuators
  • Twelve DS3218 PRO hobby servos in the listed original configuration

[5]

Controller

Original build: Raspberry Pi 4 and Arduino Mega, with PS3 DualShock input.

Later Teensy 4.1/BNO055 PCB log is a different configuration.

[5]

Sensors
  • MPU6050 IMU in the original listed build

[5]

Degrees of freedom

12

[5]

Assembly & first use

Project documentation [1]

  • Choose the original Arduino/MPU6050 configuration or separately resolve the newer Teensy design
  • Match CAD, servo geometry and component selection
  • Review power wiring and omitted Raspberry Pi supply in the historical diagram
  • Read the host/Arduino code and perform manual servo calibration before gait work

Editorial research sequence; not tested build instructions.

[1] [5] [6] · Editorial assessment

Assembly

Creator instructions describe printed components, bolt quantities, bearing-supported joints and modular servo wiring; STL and V2 STEP packages preserved.

[6] [7]

Calibration

Manual servo calibration and per-servo offsets; creator says users must understand the Raspberry Pi code rather than follow a complete installation guide.

[5] [6]

Cost

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

Budget time for wiring and calibration

The original electronics instructions describe separate servo power branches and USB communication between the Raspberry Pi and Arduino. They also acknowledge that the diagram omits the Raspberry Pi's separate 5 V, 3 A converter. Treat the illustration as a starting reference that needs to be reconciled with the full configuration, not a complete wiring schematic. [6]

The creator says there is no complete Raspberry Pi installation guide and expects users to understand the code and calibrate manually. The repository lists Python dependencies for the robot program and separate plotting dependencies for telemetry. Before working on gait behavior, establish the selected servo geometry and offsets and review the host/embedded interface. No installation, electrical commissioning or motion test was performed here. [1] [5] [6]

Historical creator logs also report very hot servos after runs longer than ten minutes and occasional bad kinematic solutions on the Raspberry Pi causing unexpected leg movement. This review has not established whether those issues were resolved in the selected configuration. [5]

The project page's historical “under $500” description is not a current complete quote. Parts availability, tools, printing, shipping and the chosen electronics revision have not been priced together, so the catalog leaves the delivered-build cost unknown. [5]

Project notes

Available CAD does not settle the configuration

The GitHub printable-files folder redirects readers to Hackaday. The linked STL and V2 STEP archives have now been preserved separately from the code archive, with checksums and file lists. The creator's instructions explain print quantities, fasteners and assembly details, but those downloads were not manufactured or checked for geometric completeness by this publication. [6] [7] [8]

A later project log describes a Teensy 4.1 PCB and BNO055 sensor, whereas the original build instructions use an Arduino Mega and MPU6050. Do not combine those controller and sensor choices into an apparently complete configuration. The selected code README still describes the Raspberry Pi program and points to an older branch for PC/PyBullet simulation. [1] [5]

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

Updates

Upstream last updated
Mar 14, 2021 [2]
Latest release
Not established
Profile updated
Oct 4, 2026
Sources last checked
Oct 1, 2026
Next review
Oct 31, 2026
Reviewed revision
d6291b50db6d05c437b78ec836df243db6f21e8b (commit snapshot; no published stable release found) · combined hardware and software repository

Source files and licenses

Hardware is explicitly CC-BY-NC-SA-4.0; included as source-available with restriction disclosed, not unrestricted open hardware.

LayerAvailability / license
mechanical designavailable · CC-BY-NC-SA-4.0
Creator explicitly applies noncommercial share-alike terms to hardware. Mechanical downloads and wiring references do not establish a fully matched current PCB build. [5] [6] [7]
electronicsavailable · CC-BY-NC-SA-4.0
Creator explicitly applies noncommercial share-alike terms to hardware. Mechanical downloads and wiring references do not establish a fully matched current PCB build. [5] [6] [7]
firmwareavailable · GPL-3.0-only
Creator declares GPL v3 for software; dependencies retain separate terms. [1] [3] [5]
softwareavailable · GPL-3.0-only
Creator declares GPL v3 for software; dependencies retain separate terms. [1] [3] [5]
documentationavailable · License not fully assessed
Public build documentation available; no separate documentation-wide license determined. [5] [6]

Kinematic hobby-servo build; no learned policy or dataset selected.

Software and hardware have different rights

The creator explicitly assigns GPL v3 to software and CC-BY-NC-SA-4.0 to hardware. The latter includes a noncommercial restriction: this entry is classified as source-available hardware, not unrestricted open hardware. Do not extend the software license to the mechanical downloads or assume those hardware files authorize a commercial kit. The documentation is publicly readable, but its separate reuse terms were not established here. [3] [5] [6]

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 4 YouTube reference(s) (S009, S010, S011, S012): official channel or videos linked from the pinned upstream sources. Existing claims, source-check dates and evidence are unchanged.