Printable bipedal duck robot that walks and balances

Oct 21, 2026 Last reply: 12 hours ago 3 Replies
Jump to replies (3)

The hardest part of a bipedal robot is getting many servos to act as one coordinated pair of legs, and CyberBionic Maker tackles it in a methodical order: the build opens with the finished duck already walking and balancing, then rewinds to wiring, deploying the xgo_duck_arduino app through Arduino App Lab, and programming each of the 15 servos one by one. The web-based configuration tool on port 9527 scans and assigns IDs from 10 to 34, and every servo is programmed with KP 5 and KD 20, all following an on-screen placement diagram.



The mechanics are just as carefully handled. Printed white, yellow and grey frame parts come together with servo horns swapped out for frame mounts, ball bearings seated into joint sockets, and two screw sizes, M2 x 6 mm countersunk and M2.3 x 8 mm flat-head, driven with a powered screwdriver and a precision driver. Routing the multi-pin servo cables between adjacent servos with tweezers looks like the fiddliest job in the whole assembly.



A few details stand out to me. The electronics stack pairs the Arduino UNO Q board with a dedicated expansion board that carries a power switch, plus a rechargeable battery pack, and the board links to a computer over USB-C. Since there is no vocal narration, on-screen captions carry every step, and the whole project is backed by a GitHub repository with the 3D models, parts list and assembly guide. The design itself is adapted from an earlier robot called Microduck by another designer, which the maker credits by building on it.



One open point: the tutorial stops while the upper torso and hip servo brackets are still being assembled, so the last stretch of the build is not shown. I would very much like to see a follow-up that finishes the upper body.



Project by CyberBionic Maker. Watch it on their YouTube channel:

formatting link


Assigning servo IDs through the web interface against a placement diagram is a smart choice in my view. With 15 servos in a small duck body, mixing up two positions would be a nightmare to trace later, and doing the IDs and PID values in one pass before mechanical assembly closes everything up avoids exactly that. The trade-off is that the board has to stay connected to a computer over USB-C during setup, so planning the workspace around that matters.

During the servo ID scan, does each servo have to be plugged in individually and programmed one at a time, or can the whole multi-pin daisy chain be scanned in a single pass through the port 9527 interface? Also, when routing those cables with tweezers between adjacent servos, is there a recommended slack length, or is it just a matter of trial and error before the frame halves get screwed shut?

Here is a concrete addition that would fit the existing workflow: after the App Lab app deploys and the IDs are programmed, a first-boot check could wiggle each servo in ID order before any frame mounts get screwed on. If the leg that moves does not match the position shown on the placement diagram, you catch a swapped or loose multi-pin connector immediately instead of discovering it when the duck takes its first step. It needs no extra hardware, only a few extra lines in the app.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required