Metabot V2

Project notes

Select a mechanical route and its matching parts

The V2 BOM specifies twelve ROBOTIS XL-320 servos, Ollo fittings, rivets, fasteners and tools. The printing route lists eight U parts, eight sides, four legs and the body/head parts. The alternative laser route uses 3 mm PMMA, with cutting and engraving layers and several parts requiring bending. Choose one route before combining quantities or fabrication instructions. Supplier availability and a current complete delivered price were not established. [3]

The inspected OpenSCAD assembly defines four legs using three joint angles and includes separate configuration, joint and part modules. The additional configuration/parts source contains dimensions and calls to the body, head, U, side and leg modules. These are actual source relationships, not a native CAD load, a render or evidence that the entire include graph produces fabrication-ready geometry. No printed/laser-cut fit, strength or assembly was checked. [4] [9] [10]

Keep XBoard hardware and servo configuration together

The electronics BOM describes a Maple Mini STM32F103CBT6, GY-85 IMU, distance sensor, Bluetooth module and XBoard components. The original Eagle schematic was retrieved and its pinned Git identity matched; XML parsing found 41 parts and 40 nets. That establishes inspectable circuit source, not an electrical design review, PCB fabrication check or validated power protection. The controller and commercial servo designs remain separate from the project's design contribution. [3] [5] [11]

The BOM's battery reference is a 2S 7.4 V 1000 mAh LiPo with attention to physical size and a separate charger. Treat those as historical source selections requiring a matched power/charging investigation, rather than a tested replacement-pack specification. No current battery purchase or powered commissioning was performed. [3]

Treat the upload instructions as historical

The firmware README explicitly limits its adaptation to the original twelve-DOF arrangement. Its Linux route installs Python/serial support, then runs sudo python robotis-loader.py /dev/ttyACM0 metabot2.bin from firmware. The binary-upload recipe is distinct from rebuilding the available firmware source, and current Python/toolchain compatibility was not reproduced. The Windows example requires its own driver/serial-port reconciliation. [6] [8]

The documented serial terminal has start to enable torque and stop to shut it down. These are upstream command descriptions, not observed motor behavior or a validated emergency-stop system. Phone-app availability and current kit supply were not checked. The noncommercial notice and third-party terms require review before reuse or redistribution. No firmware build, upload, app connection, sensor calibration or walking test was performed. [1] [2] [6]