Zuko and ElectroPup publish robot CAD

Zuko and ElectroPup were presented this week as two fully documented quadruped robot builds that expose much more than a highlight reel. Their public repositories include mechanical CAD, electronics files, source code and build documentation rather than only demo videos or rendered assemblies. That makes them useful not just as hobby projects, but as examples of how a robot moves from concept to hardware, wiring and software integration. Both projects were circulated on X in posts framing them as end-to-end case studies for replication and study, and the linked repositories back that up with downloadable project files. ### What exactly did these builders publish? Zuko’s GitHub repository shows folders for `cad`, `pcbs`, `stl`, `docs`, `diagrams`, `scripts/kinematics-simulation` and a `quad_ws` ROS workspace. The README says the project uses ROS 2 for communication and launching, and that the robot runs on a Raspberry Pi 4 with a custom expansion board for motor and peripheral control through a PlayStation 4 controller. ElectroPup’s repository exposes a similar full-stack layout. (github.com) Its public files include `cad`, `docs`, `pcbs`, `firmware`, `src` and `videos`, and the repository describes the machine as a DIY 3D-printed quadruped using low-cost BLDC motors. ### Why are these repositories more useful than a normal robot demo? Zuko’s published tree matters because it links design artifacts that are usually scattered across separate tools. (github.com) The repository combines frame CAD, PCB files, ROS 2 code and kinematics scripts in one place, which lets a reader trace how the mechanical design, electronics and control stack fit together. ElectroPup does the same from a different hardware starting point. (github.com) Its repository includes not only CAD and PCB material but also firmware and a simulation model, which gives readers a path from part geometry to controller behavior and testing. ### What are the main hardware differences between the two robots? Zuko is built around a Raspberry Pi 4 and a custom expansion board, according to the project README. (github.com) The repository also describes it as a 12-degree-of-freedom quadruped and says the frame redesign created more room for electronics while the software stack was migrated from ROS 1 to ROS 2. ElectroPup’s listed hardware is newer and heavier. Its repository specifies a Raspberry Pi 5, 12 BLDC motors, an auxiliary board with LCD display, a 9-axis accelerometer/gyro sensor, a 6-cell lithium-ion battery pack rated at about 72 watt-hours, and a total weight of 4.5 kilograms. (github.com) The README says its control system is written in Python. ### Where does simulation enter the picture? ElectroPup includes a dedicated MuJoCo model under `src/model`. (github.com) The model README says users can run the quadruped in MuJoCo, with or without gamepad input, and points to linked CAD assets for the simulation model. That gives builders a way to test poses and walking behavior before or alongside hardware work. Zuko’s repository points more directly to ROS 2 and kinematics tooling. (github.com) Its published folders include simulation scripts and a ROS workspace, and the project notes credit earlier open quadruped work for simulation and kinematics foundations. ### What does this show about how open-source robot projects are changing? GitHub’s public pages for both projects show repositories organized around replication, not just presentation. (github.com) Zuko has 45 stars and nine forks on the surfaced repository page, while ElectroPup is earlier-stage and smaller, with two stars and no forks shown in the same snapshot. The next step for anyone studying the builds is concrete. (github.com) Zuko’s repository says frame v2.2 is being tested and is “nearly ready for replication,” while ElectroPup’s repository already includes CAD, PCB, firmware and MuJoCo model directories that can be pulled directly from GitHub for inspection or build planning.