MD-01 Usage Guide
Microduck MD-01 is a compact, programmable biped robot. This guide helps you prepare for first use, find the right controller instructions and explore simulation before developing new behaviours.
First-use checklist · Controls and stopping · Simulation and development
Before the first movement
- Check the box. The published Microduck package includes the robot, a removable battery, a USB-C cable and a game controller. Compare your delivery with the packing list and inspect the shell, feet and joints for visible damage. Contact support before operating a damaged unit.
- Read the battery instructions. Microduck uses a removable NP-F550 battery. Follow the charging and installation instructions supplied with your battery and robot. Use compatible charging equipment; the presence of a USB-C cable alone does not identify the correct charging connection or power supply.
- Choose a clear space. Begin on a level surface away from edges, stairs and water. Keep hands, loose clothing and cables clear of moving joints, and supervise children.
- Match the documentation to your unit. Check the installed software version and controller model before following setup instructions. The public development documentation changes over time and may differ from the software supplied with your robot.
Controller pairing, movement and stopping
Start with the official gamepad pairing guide. It covers different controllers and runtime environments; use the section for your controller instead of trying an unrelated button combination.
Read the official robot controls and status reference before enabling movement. The currently published reference says there is no dedicated stop button. Releasing the sticks returns to standing in that runtime; it does not switch off the motors. Check the rest and shutdown instructions for your installed version before the first test.
Make the first movement short and controlled. Stop using the robot if a joint, battery or cable appears damaged, and power down according to the supplied instructions before inspection or servicing.
Explore simulation before changing behaviours
Using the included game controller and developing a new policy are separate activities. The official Microduck runtime repository documents the robot software, while the simulation guide explains how to run the runtime and policies with MuJoCo.
For reinforcement learning, see the Microduck RL repository and its environment requirements. It documents training and ONNX policy export. GPU training requirements differ from simply operating the robot with a controller.
A successful simulation does not validate physical motors, Bluetooth, camera processing or the AI accelerator. Review a policy in simulation first, then follow the hardware documentation for a supervised, conservative test on the robot.
When you need help
For setup support, note the controller model, installed software version, status indication and the step that failed. Use Microduck support for product or order questions. You can also compare the hardware specifications and accessory packs.
Documentation reviewed on 11 October 2026. Hardware and box contents follow Pollen Robotics’ Microduck overview and published product specifications.