Start with your intended project
For learning biped movement, servo configuration and joint calibration, the basic kit covers the documented motion platform. It can make sense when your immediate goal is to assemble the mechanism, inspect the open-source code and control movement from a browser.
Choose the full kit when your project specifically needs camera preview, audio interaction or ToF distance sensing. These additions do not remove the assembly and calibration work. Neither edition should be selected on an assumption that every demonstrated research behavior is ready to use.
Compare the documented hardware and functions
The table separates shared motion functions from modules added to the full kit. It describes the reference editions, not a promise about any third-party bundle. Check the bill of materials for the exact listing you intend to buy.
Scroll sideways to compare all columns.
| Item | Basic kit | Full kit |
|---|---|---|
| Controller | Arduino Uno Q | Arduino Uno Q |
| Motion actuators | 15 serial servos | 15 serial servos |
| Browser movement and calibration | Supported | Supported |
| Audio, camera and ToF modules | Not included | Included |
| Printed shell | Separate 3D printing required | Confirm supplied printed parts with seller |
| Assembly and calibration | Required | Required |
| Sensing runtime | Not applicable to absent modules | Microduck Robot AI branch |
Allow time for assembly and 3D printing
Both editions are self-assembly kits. Plan for servo ID setup, mechanical assembly, joint zero-position calibration and a default-pose check before walking. A full kit is not the same thing as a robot delivered assembled.
The source explicitly says the basic kit shell must be printed separately. Use the matching structural STL files and assembly guide rather than assuming a similar-looking shell will fit. For either edition, compare the seller’s package list with the hardware repository and clarify which printed parts are supplied.
Match the runtime to the installed modules
The motion interface provides browser control and calibration. The full kit’s audio, camera and ToF features require the Microduck Robot AI runtime branch and its installation instructions. Voice conversation additionally requires an internet connection, account binding and an agent selection; translated website copy does not establish localized voice support.
ToF forward obstacle avoidance is not autonomous navigation. The documented pickup is a manually triggered pretrained movement, not object recognition or autonomous object search. Tasks present in the training environment may still require training, runtime integration and physical validation. Ordinary browser control does not require a separate GPU computer; custom training does.
Project origins and software compatibility
The original Microduck robot is a Pollen Robotics project. The micro duck robot kit described here uses an adaptation of Microduck and microduck_rl. Consult the documentation for the exact hardware revision and runtime used by this kit; firmware is not automatically interchangeable between projects.
Do not transfer a price, battery-life claim, demonstration or firmware image from the original project to Microduck Robot without checking its own documentation. This page does not establish identical features or interchangeable firmware, and it does not rank one project above the other.
Check the complete purchase before ordering
Confirm the edition, board version, printed shell, power components, cables and module list with the seller. Ask which software branch the supplied hardware is documented to use. Compare total project requirements rather than just the headline kit price.
Price, stock, destinations, shipping dates and after-sales terms belong to the current seller listing. Historic sale notices are not delivery guarantees. Keep the applicable bill of materials and documentation version with your order, then use the assembly and usage guides for the next steps.