Current image, compatibility and recovery
Keep the model, image, software and driver versions together. The dated sections below retain their original verification limits.
- Save the old card, configuration and component versions before changing an image or update package.
- Match the tag, filename and published SHA-256 before writing the card. Keep your working card available.
- Confirm controller and API compatibility before calibration. Preserve the original offsets and orientation records instead of copying another robot's values.
- Read back applied settings and actual device feedback. Separate network recovery, IMU response and policy execution; the dated notes below retain their original test limits.
HD1910 replica: match CAD, print files and BOM
This procurement and printing step covers 机械行者Robo’s CAD hosted in microduck-replica-cad at 2e40221. XL330 v1.1, KISS and official MicroDuck files belong to different build routes.
- Keep a file ledger: HD1910 v2.2 SolidWorks remains dated 2026-10-20; the BOM and Bambu Studio 3MF are dated 2026-11-02. The author describes changes to the right ankle and upper head shell in the newer print package. Our archive inspection finds source names 1013ankle_right脚踝右1-FT.STEP and top_head_shell_头部上壳-FT.STEP. Do not assume the older editable archive contains those revisions.
- The workbook lists 33 print entries and 24 purchased entries, including a controller at row 60. These are line items, not a total part count. Check the HD1910M label at C43; quantities G41/G42 are blank, and I36 is a section-header zero, not a complete budget. Confirm missing quantities and current quotations separately. Saved prices and shopping links establish neither stock nor shipping costs.
- The 3MF contains six plates and 43 top-level build instances. It saves a P2S, 0.4 mm nozzle, 0.2 mm layers and two PLA filament entries. Plate 6 is labelled TPU材料, while BOM E30 still says PLA; F7/F8 also recommend TPU for soft parts. Choose suitable TPU profiles for those parts, check your own printer and reslice. A plate label does not change the saved filament profile.
- The pinned README licenses this author’s drawings and documentation under CC BY-NC-SA 4.0: credit 机械行者Robo, retain notices and follow the noncommercial/share-alike terms. Check other components separately; this is not a blanket commercial-use licence for every MicroDuck file. Keep this file check with your own parts and fit notes before continuing to image setup.
microduck-replica-cad @ 2e40221b398e81428d02bf6d1399275d18436a63
装配BOM-机械行者Robo-2026-11-02-带采购链接.xlsx
17311 bytes
SHA-256 737878c8d6bbcc67474e8f9389533de81e80af0508eb501c5ad16d0b96954541
microduck-飞特版-BambuStudio2026-11-02.3mf
5221356 bytes
SHA-256 c0939b65d9c8d0ab24e48c73799b22f46183429629c80c66eaa8c430726869a6We inspected the original XLSX XML and 3MF archive offline and read the pinned README. No purchases, printing, dimensional fit, electrical compatibility or robot operation were tested. The October 20 file analysis remains in the historical section below.
Which HD1910 image should I download?
The project published image 20261104 on November 4 and removed the GitHub prerelease flag on November 7. Its Radxa Zero 3W and Feetech HD-1910 configuration still uses control.48/API43. Keep the image and software files separate when choosing a route.
| Route / component | Use it for | Check before continuing |
|---|---|---|
| RC4 · ZERO 3W | microduck-replica-zero3w-20261112-rc4.img.xz | 2026.11.12-rc.4.zero3w / API44 |
| RC1 prerelease image | microduck-replica-20261110rc1.img.xz | replica-imu-home-control.50 / API44 |
| 2026-11-09 · Default image | microduck-replica-20261027.img.xz | 2026-11-09 · GitHub Latest opens this tag. Compare the filename and its own SHA-256. |
| Image from its own tag | microduck-replica-20261104.img.xz | Open this tag directly and use a spare card. The paired components are preinstalled. |
| Prerelease software TAR | 2026.11.4.software-update.tar | Web software, then the explicit paired-driver flow; no system hotspot patch |
| Native compatibility | control.48 / API43 | Confirm robotd, padd, service files and the actual running baseline |
HD1910 RC4: read servo and IMU evidence
This is the author’s November 12 RC4 prerelease, fixed at cbf06567, with bundle 2026.11.12-rc.4.zero3w and API44 in the author’s report. Cubie A7Z, the KISS image and the official MicroDuck daemon are different targets.
- Match the board marking and the zero3w filename. Download the image and its same-tag .sha256, compare the digest, and keep your working card and settings before using a spare card. Follow the pinned first-use guide; do not substitute an A7Z image.
- In Studio Overview, expand Diagnostics and select Servos. The 15 cards show online state, angle, temperature, voltage and missing read replies over the last 60 seconds when data is available. The rate is missed replies / sent read requests, not a count of UI refreshes. No requests or insufficient evidence means unknown; retain the observation duration with your report.
- Select IMU and record source, protocol, effective update rate, sample age, angular velocity, quaternion and the last error. Stale or absent feedback is not a zero reading. Viewing these snapshots does not require entering servo calibration. Keep direction, calibration and motion readiness checks separate; do not change read order merely to make the display look healthy.
microduck-replica-zero3w-20261112-rc4.img.xz
756012348 bytes
SHA-256 68acef307bd27b359e1624a7f7b751c911354e9e75be75730fda7b2a5aa58aaf
2026.11.12-rc.4.zero3w / API44
source cbf06567c136c49c36babbd5fbd069db4979e1bcWe checked eight small release attachments and fixed public Python/JavaScript. The author’s report names native revision 0a492d14; the historical native repository returns404, so that native source was not independently inspected. Fresh-card boot, physical missing-reply counts, movement and phone recording remain unvalidated here. Keep component/model licence limits; the image is for personal noncommercial builds.
HD1910 RC1: check IMU calibration
The author released 20261110rc1 on November 10 for Radxa ZERO 3W + Feetech HD-1910. It is an IMU calibration candidate based on 20261104. The default Latest image, tagged 20261104 image and older software TAR remain separate choices.
- Keep the working card and its settings. Download the RC1 .img.xz and matching .sha256 from the same tag, compare the digest, and use a spare card. After first boot, confirm hotspot and Wi-Fi setup. The image pairs Studio with replica-imu-home-control.50 and IPC API 44; online upgrading of an old card still awaits acceptance.
- Support the robot, stop the motion policy, and wait for a settled HOME hold with fresh joint feedback. Follow the screen to capture stationary and forward-tilt samples. RC1 permits calibration while the standing hold stays powered. The 5.1° example in the release notes is a case, so follow the device’s readiness result.
- Run direction verification and save only on success. The new direction then applies immediately; a failed check keeps the old one. Check the saved result before continuing. Starting a walking policy still uses the original HOME gate and requires its own readiness check.
microduck-replica-20261110rc1.img.xz
756509320 bytes
SHA-256 1f4f2224d04dba59f02abb0dab82fcb684c49a1d9dd50512a166442d53914043
replica-imu-home-control.50 / API44
robotd f8c720a3acf2eb5e6c844ba041d79d7312f49a50e99c04182c5ec0dc4bb9ac9eWe checked pinned source and the small release attachments; the full image was not tested here. The author reports 21 native-test failures matching the 1104 baseline and two full-suite web failures that passed individually. Fresh-card boot, standing save, physical movement, V1.12O hotspot loss, intermittent servo-page disconnects and the physical camera remain hardware checks.
20261104 · control.48 / API43
Keep the web update and paired drivers separate
Back up models, joint zeros, IMU direction and personal settings. On a compatible working card, stop policy, audio and recording/calibration sessions, support the robot and confirm torque off, then upload the complete software-update.tar in Settings → Software update. Do not upload bootstrap.tar.gz there. An already completed 2026.10.31-r1 driver transaction must first use Restore old paired drivers, then explicitly install this release. An unfinished old transaction needs its original signed updater; keep its records and protection files. The new image already includes the paired components, so do not install them twice. Check the full component set and running process, not just the web version.
Collect a candidate, then independently verify it
For new HOME-held sampling, the model must be off, HOME stable and feedback fresh. Collect still and forward-tilt data through the author’s UI; support and unload when requested, retaining the candidate for verification. The backend requires the matching independent upright/forward-tilt proof before saving. A response from ID200 or a computed correction is not that proof; invalid direction, cancel or timeout does not save. Default output remains legacy-compatible. Full-quaternion mode needs explicitly matched board firmware; this release does not flash the MCU or supply a universal mounting preset.
The hotspot repair belongs to the image
The bounded Wi-Fi retries and recovered-hotspot-profile loading are system-image changes. Uploading the software TAR to an old card does not replace its networking script. Use a spare card for the new image and follow its first-boot setup, preserving the working card. The author has not yet validated real Wi-Fi roaming on a freshly flashed card, so there is no guaranteed hotspot recovery outcome.
microduck-replica-20261027.img.xz
741604104 bytes
SHA-256 91ab5550e0f409d634722718a638d6e9615412b779b5d26c0af5c777056d0194
microduck-replica-20261104.img.xz
755670732 bytes
SHA-256 f9970ec551bcddbeeae9748b0ce38f36450fa1497618c07920723849f975aa78
2026.11.4.software-update.tar
9676800 bytes
SHA-256 b6e8d90896fd1aaeb4a6288e226ba7228a1fe7d738a79c9dcde7407dfadad211
control.48 / API43
robotd e5ff7fb429fd0dfb762eb4da1bcc5a26b48b6d2dfdae4bb4904213e37e022ed0
padd dc1c7043a108964583fc09a11e3d6f87a25e259c346f7ce9154e77500a0881ecWhat the available evidence proves
We checked the three checksum sidecars and release metadata. The author’s 20261104 record covers offline checks. Fresh-card boot, real hotspot recovery, walking and getting back up still await hardware acceptance. The image and TAR share the same report, which still says prerelease and lists three known native-test failures.
- microduck-software-v2026.11.4 ↗
- microduck-replica-image-20261104 ↗
- 更新说明-20261104.md ↗
- native-update-20261104.md ↗
- imu.py ↗
- microduck-netcheck ↗
- runtime-provenance.json ↗
- SHA256SUMS.txt ↗
- latest ↗
- microduck-replica-image-20261027 ↗
- 官方更新跟踪.md ↗
- validation-report.json ↗
- microduck-replica-image-zero3w-20261112-rc4 ↗
- communication.py ↗
- 烧录和第一次使用.md ↗
- microduck-replica-zero3w-20261112-rc4.img.xz.sha256 ↗
- delivered-image-verification.json ↗
- microduck-replica-image-20261110rc1 ↗
- imu.py ↗
- 56046c5aa10be4de12d4389ae0463e4f129df940 ↗
- microduck-replica-20261110rc1-manifest.txt ↗
- microduck-replica-20261110rc1.img.xz.sha256 ↗
- delivered-image-verification.json ↗
Earlier versions and research notes
Earlier versions and research notes
32 and 34: fix the display, not the robot IDs
Published October 31 at 10:57 UTC, 2026.10.3101 corrects picking, highlighting and leader labels in the replica's 3D model: 32 head yaw, 34 mouth. The changed source files are web/model files. Rewiring, exchanging real IDs or changing joint directions to compensate for the old display would address the wrong layer.
Choose the correct update container
On a compatible image 20261027 with the updater entry, stop policy, audio and motion/calibration sessions before updating software. For offline web upload select the complete 2026.10.3101.software-update.tar, not the bootstrap archive. Version 31's separate controller update is inherited; .47 alone does not prove the pad component is current. Version 3101 did not rebuild those native binaries. Read the actual versions, follow any explicit supported driver step, and recheck the emergency stop after remapping.
What has and has not been checked
We downloaded the outer TAR and matched its bytes to the publisher's checksum; the manifest's inner tar.zst digest belongs to a different container. We reviewed the fixed web source and author provenance, without installing, booting, verifying signatures or operating hardware. Author ARM-engine fixture tests are not a complete robot deployment. New experimental audio/Select tracking on the moving source branch is not treated as a stable feature here.
Pinned original files and checks
2026.10.3101.software-update.tar
9287680 bytes
SHA-256 0502c452e7062aa29286f6a82c046ed4ceaaf8beecaa6d98958341a80c95ea77A waiting IMU no longer hides servo replies
Software 2026.10.29 introduced separate startup observations: a page may show 15/15 responding servos while robotd still waits for the selected IMU. Per-ID position, voltage and temperature come from replies; expired or absent evidence becomes unknown. The author reports this display on one Radxa ZERO 3 with an I²C IMU providing no data and motors unloaded. That is a display observation, not a walking test.
Software 2026.10.30 was published October 29 at 15:50:01 UTC, frozen at 2ba8e5d8. It adds independent read-only bus-IMU diagnostics for ID200, including an IMU-only or partially connected setup. The target is control.47 / IPC42, still official-version 0.15.1 and model API2. The system image remains 20261027; no new image or automatic hardware compatibility is implied.
Update both layers, keeping the existing readiness checks
Use the existing Settings → Software update route or upload the whole 2026.10.30.software-update.tar: 8,089,600 bytes, SHA 256 beginning 880803ef4143. Its inner tar.zst has a different size and hash. Reconnect and verify the web version, then separately support the robot, confirm torque off and approve native .47. Only known .44/.45/.46 predecessors are supported; unknown binaries and unfinished transactions remain blocked for maintainer review.
The first stage retains its original preparation conditions. If an old IMU-only setup cannot pass them, use the documented full-device or maintainer route; do not force a standing state or delete transaction guards. Power off before changing wiring. Browser disconnect does not cancel detached work, and web/voice rollback does not downgrade robotd. The bootstrap attachment is for compatible old cards lacking the update entry, not the browser’s offline-upload file.
Read freshness and identity before trusting a green label
Identification, a sample, mounting calibration and motion eligibility are different facts. The implementation combines capture age with receipt age; evidence at least three seconds old, from a previous daemon hello or an incompatible source/profile is stale or unknown. Re-reading a cache does not renew it. An I²C selection does not automatically switch to a bus IMU; Qinmo retains its separate manual profile.
The author’s .47 verification uses software/browser tests, protocol models and QEMU installation/recovery checks, with explicit full-native-workspace and physical-acceptance gaps. This site checked sources and small attachment bytes, not live installation, an IMU-only board or walking. A practical report names the current web/native versions, selected source/profile, per-ID replies, age and original startup reason.
- Check the actual native build and IPC API, not only the web version.
- Capture IMU and servo states separately, including unknown/stale values and the wait reason.
- Keep diagnostic evidence separate from calibration and permission to enable motion.
Choose the image or the existing-card update
The image was published October 27; the software suite followed October 28. New cards start with image 20261027, whose controller/model baseline remains 23c. Its software-update entry is already installed. Compatible older cards without that entry need the maintainer’s one-time bootstrap; it is not the browser upload file.
For offline browser installation, use the complete 2026.10.28.software-update.tar. Its published outer-file SHA256 begins f6bd4dfb; the manifest describes an inner compressed payload with another size and hash. Do not compare the inner digest with the outer tar, or upload an image, bootstrap or loose source files instead.
Check each update stage separately
The first stage updates Studio, its matching helper and local voice components. It keeps the existing standing/HOME readiness rule and does not replace or restart robotd. Unknown state or an unsupported layout needs maintainer review; do not force motion to pass an update check.
Only the reviewed project-native 20261027 baseline is eligible for automatic native replacement. The target still prints official version 0.15.1; its actual build is 0791fcd-feetech-qinmo-control.45 from bdf494ab. Check the running identity, not just the suite number.
- In Settings → Software update, check and download the package. Stop policies, voice, music, recording, playback and calibration; follow the first-stage readiness checks, then install once.
- Wait for reconnection and read suite version 2026.10.28. For Qinmo only, support the robot and release torque, then give the separate native-update confirmation. The second stage does not require another HOME or standing action.
- After the running controller is verified, select Qinmo · Feetech and complete mounting-direction validation. Existing supported boards keep automatic identification; Qinmo DXL2 is outside this release.
Recover in the same page and keep the limits visible
An independent job can continue when the browser disconnects. Reopen the update page rather than submitting again. Web/voice rollback affects that layer only; it does not downgrade robotd. An unfinished native transaction keeps motion guards in place: support and unload, then use its dedicated recovery action. Do not delete guard files or manually restart controllers.
The publisher still marks old-card hardware upgrades, real power-loss recovery, Qinmo hardware and walking as pending. New-card first use and live camera/ToF acceptance are separate. Local sit/stand voice exists, but music-following and free-form spoken AI are unfinished. This site inspected public sources and small metadata; it did not install, run or test the robot.
What the new motion recordings establish
The author labels two recordings October 24, 2026; they were added to the public repository on October 25. The roughly eight-second clip shows a forward roll followed by standing, and the roughly six-second clip shows tabletop walking. The project also reports a first-use run on a third duck with the earlier 21b image.
The clips do not identify a complete image/runtime/policy/IMU bill of versions or provide repeat counts. They cannot certify every 23c installation, long-duration reliability or all bus IMU boards. This site inspected the source recordings and documents; it did not operate a robot.
- Author’s dated validation history
- Forward roll and recovery: original MP4
- Tabletop walking: original MP4
Use the printable guide with its own image version
The newly linked Chinese V2 PDF has 21 pages: a cover and 20 steps, dated October 22 and explicitly written for image 20261021b. It covers card flashing, hotspot/Wi-Fi, individual servo zeros, IMU orientation, gamepad pairing, e-stop and first walking. It assumes an assembled HD1910 robot; it is not a mechanical assembly manual.
The latest image is still 20261023c. For its protocol-bound IMU approval and initial sampling, follow the current web instructions and the 23c notes below. The PDF’s older four-direction tilt screen is not the current calibration procedure. Record the image, runtime, helper, IMU protocol and mounted module before starting; keep the robot supported and test e-stop before motion.
The author continues to separate the three new PCB designs, individual bus-IMU compatibility, real camera/ToF and self-trained policy deployment from the filmed motions. Studio’s new overview screenshots use simulated device readings. Older dated notes below retain their original test scope.
Current image: 20261023c, published October 23
The author marked 20261023c draft=false, prerelease=false, published 2026-10-23 07:36:28 UTC (15:36:28 Beijing). This is the personal replica’s release status, not an official Pollen daemon release or a completed physical acceptance test. Earlier 23b was published at 04:58:14 UTC and is now historical.
Use microduck-replica-20261023c.img.xz with its matching checksum: 712,068,864 bytes, SHA-256 10009c0a4aa963900719649836f5544036ad52cc15e3a0228eef05f6b747dab5. Download it from the author, retain a known working card and your own configuration backup, and follow first use. We verified the five small text attachments against their API digests; the image size/hash are publisher values. We did not download, unpack or flash the large image.
shasum -a 256 -c microduck-replica-20261023c.img.xz.sha256
Manifest: Studio/build dd7a753026c40b0bf385374a896e7253cff42720; runtime 0791fcd44f71c705dc8bb0fbcde405593b52d19b, build 4734cbb-feetech-imu-auto-control.44; robotd SHA-256 edf182edb7bf11aeeeedfdab98170ab2ec48a9ec18417f9b68c744b0a60c6d16; helper 0.7.1. Unlike image23, the runtime changed. This remains the custom HD1910 stack, not official 0.17.8.
Detection now reaches the motion program
The fixed compatibility record distinguishes Feetech ID200, block56/15; DXL2 ID200, SFLP block124/12; and existing I²C BNO08x/LSM6DSV16X. [bus] imu_protocol defaults to auto, with feetech / dxl2 overrides. Probe reads do not rewrite IDs, baud rates or EEPROM. An arbitrary IMU with a different data layout is not supported by its name alone.
Studio reports detected protocol and layout. Old Feetech mounting approval cannot authorize DXL2 torque. Changing physical module or mounting also requires fresh calibration. The matching runtime/helper, displayed protocol and mounting verification belong together; use the step-by-step calibration distinctions.
What the author verified, and what remains open
The author reports image/offline checks and serial simulation. A host test used ScrapMeta’s original C protocol implementation against the actual Rust reader: 7 conformance cases, not seven boards. The firmware reference db04d323 targets a particular STM32G031F8P6 + LSM6DSV16X board and has its own MIT license; the SD image does not flash that MCU. Real-board sustained reads, calibration, standing and walking remain pending. The pinned ScrapMeta firmware contract uses 1 Mbps; matching protocol does not validate another board’s pinout.
The record also reports 17 existing robotd unit failures in both old and new baselines; it does not claim every Rust test passes. Camera defaults remain a test source; automatic camera/ToF service control and real sensor acceptance remain unfinished. Keep those limits separate from formal release flags. The bundled models’ personal, noncommercial distribution restrictions remain in effect. The model-package procedure below remains relevant; the old image23 component snapshot is folded as history.
What actually changed in image 20261023
The author published image 20261023 at 18:00:11 UTC on October 22, 2026, or 02:00:11 on October 23 in Beijing. This release is explicitly a prerelease. Its offline acceptance record covers source packaging, software tests and filesystem inspection; neither those checks nor the previous 21b robot reports validate this new image on hardware. It is for the HD1910 / Radxa Zero 3W route, not an official XL330 robot or Open Duck Mini.
The compressed file is microduck-replica-20261023.img.xz, 712,183,896 bytes, with SHA-256 2532dbffa46f087ccbc9dcb6fbe76663713ddf4bcf2510212809d5c8908dabab. Download its checksum companion from the same release and check it in that directory. We checked the five small published attachments against their API digests; we did not download or flash the large image.
shasum -a 256 -c microduck-replica-20261023.img.xz.sha256Get-FileHash -Algorithm SHA256 .\microduck-replica-20261023.img.xzThe manifest pins Studio/build source 03136c9a9b5149d1f66b7c4a62e82feb3e9be490 and helper 0.7.0. The custom runtime remains 4734cbb0aac075335ef206d6557d0b6a3eb9e0a9, with the same ead7f2f8… runtime hash as 21b. Its Armbian 26.2.1 / Debian 13 base and official 0.15.1 base runtime are separate from today’s official daemon 0.17.8. A new Studio image does not mean a new robotd binary. Keep your working card and calibration backup. Models still carry the release’s personal noncommercial distribution conditions.
New model pages do not move training onto the robot
Training and export happen on the computer. Studio now manages imported models, selected uses and action-button assignments. For the actual supported input, follow the detailed model import guide: a package containing the model and its matching manifests/contracts, rather than treating a bare ONNX file as compatible. See the package and switching checklist before importing. Installed, selected and currently executing are three different states.
Recalibrate an already saved IMU direction with a recoverable session
A saved quaternion no longer hides the original coarse-calibration route. The new flow requires Studio and helper/sudoers 0.7.0 together. Start with the body supported and torque off; use “Recalibrate direction” and its second confirmation. In motion mode the helper temporarily enters calibration mode; a factory calibration session reuses its existing route. Do not substitute a manual mode edit for this transaction.
Capture stillness, then the requested forward torso tilt. Physically return the robot upright before starting runtime verification, and tilt forward again when prompted. Completion requires reading back the current IMU, new installation direction and mode. Joint zeros, directions and limits are retained; the original mode returns with torque still off. Cancel, refresh or an interruption must be handled through the recovery entry until the session is resolved. The author’s local tests replace the privileged service boundary; a real-board update, cancellation and restart still need hardware acceptance.
Camera service online is not proof of a camera image
The new camera/ToF implementation adds video-source controls, an 8×8 distance grid, valid-zone count and nearest/farthest readings. Check whether data is disconnected, erroneous, stale or simulated. The overview’s seven device indicators include battery, servos, IMU, camera, ToF, gamepad and board. They are diagnostic states, not seven passed hardware tests.
This image still defaults to a camera test picture. A media-service hello or configuration entry does not establish a real camera feed, and a ToF service unit does not establish valid ranging. Opening these read-only status pages does not start the services; unified hardware-dependent automatic startup remains unfinished. Actual camera/ToF checks and this image’s entire first-boot/standing/walking sequence are still pending. The earlier source-checked network, SSH and bus-IMU notes below remain useful within their stated scope.
First boot: hotspot first, then the address for your device
On a fresh card with no saved network, the revised network monitor opens the hotspot immediately after detecting disconnection instead of waiting 45 seconds. Join Microduck-xxxx, open http://10.42.0.1:8000/, and use Studio to choose the home network. The published hotspot password is microduck; it is not an SSH password.
After Wi-Fi changes, Studio attempts to locate the new address. The author’s device routes are Windows http://duck-xxxx:8000/, Apple http://duck-xxxx.local:8000/, and Android the IP shown by your router. Replace xxxx with your actual hostname. If redirection fails, first confirm the phone/computer and robot are on the same LAN and try that IP. The Windows route addresses the author’s Clash / .local problem; it does not justify changing router-wide settings.
SSH is optional; register your own public key
The new Studio instructions put recovery access under More → SSH. Set a Studio login password first. You may register your own OpenSSH public key or deliberately set your own SSH password to enable password access. The image contains no author login keys, and there is no usable default remote SSH password. Paste the .pub line, never a private key. The key parser and helper implement this path. A Studio password and the separately configured SSH/sudo password serve different purposes.
Skipping a checklist step does not validate it
The revised checklist permits skipped steps and fixes a double-click that could land on Completed. Record exactly what was skipped. Skipping IMU orientation uses a default mounting assumption; it does not measure your installation. In calibration mode, “stand-position enable” holds the joints without balance control. Support the robot and disable the hold before committing configuration. The author has not finished the stand-position / skip → commit → pair → walk acceptance sequence; do not treat a reboot or an enabled button as a passed check. See the commit implementation.
Bus IMU: a dated bench record, not full-robot acceptance
The newly uploaded firmware 1.0.0 validation record is dated September 2026. It reports FT-SCS tests at 1 Mbps with servos 2 and 3 plus IMU ID 200. Putting the IMU first returned 3/30; putting it last returned 30/30. The author requires ID 200 after the servos, or in its own read group. This is a specific author bench result, not our test or proof under all 15 servos. Full-body integration, long-duration operation and the new-image IMU sequence remain outside that evidence.
The author reports successful calibration-mode entry, Studio servo/IMU readout, access with Clash running and SSH service startup. Full new-card motion acceptance remains incomplete. If collecting an existing failure, record the exact image, Studio/runtime versions, checklist stage and necessary redacted error; export diagnostics privately rather than posting a full bundle. The earlier six-plate CAD / BOM checks remain a separate print-file topic below.
Historical 21b checks are retained here. Use the 20261023 file, checksum and acceptance limits above for the new prerelease.
Image 20261021b: a new file, with unfinished acceptance
The author published 20261021b on October 21, 2026 at 06:15:52 UTC, after 20261021. The release API reports prerelease: false; the release text and fixed first-use guide still describe an acceptance run in progress. Keep both facts. A GitHub label is not evidence that the whole robot sequence passed. The author explicitly warns against 20261020 because it can stall at checklist step 2.
This is the Feetech HD1910 / Radxa Zero 3W route, not an image for an official XL330 robot or Open Duck Mini. The compressed file is 710,226,628 bytes. We checked the small manifest and checksum text against published asset digests, without downloading or flashing the large image. Models retain the author’s personal noncommercial distribution limits.
Check the file and its component versions first
Download the image and its .sha256 companion from the same release. The compressed-file SHA-256 is 1235cff97c24a315440672160531f81d758a8c2fd525cbd7b735c02cc867b922. Matching it establishes download integrity, not actuator compatibility. Run the check in the download directory; Windows should show the same hash.
shasum -a 256 -c microduck-replica-20261021b.img.xz.sha256Get-FileHash -Algorithm SHA256 .\microduck-replica-20261021b.img.xzThe manifest identifies the official 0.15.1 base, custom robotd revision 4734cbb0aac075335ef206d6557d0b6a3eb9e0a9, and Studio / builder f3927aaf46c3e8ed90096131fa7b434e85dcc04e. The runtime SHA-256 begins ead7f2f8; these are separate components, not official daemon 0.17.8. Preserve the old card and your calibration/configuration before preparing a new card.
These notes describe image 20261020 and the earlier Studio build. The author now reports that image stalls at checklist step 2. Use the current checks above; a historical command or password is not a recommendation for a new card.
What changed after the first Studio snapshot
This update reviews replica 36854c788bbe38b2397e0954813ebe8b16e60983 and CAD dabbda7c592e42e0d016a293dc8c9fcabb300bbf, with original source changes on October 20. Studio now implements coarse IMU calibration in commissioning mode, committing zero/direction/IMU results to the runtime, phone Wi-Fi setup and browser password management. The old statement that Studio cannot write runtime calibration applies to revision 71e45b1 only; it is retained as history below. The author reports Studio running as a service on the second robot with pad pairing and emergency stop tested, while calibration commit, Wi-Fi and fresh-image acceptance remain untested on hardware. This site performed source and archive review only. Author scope · Current fixed Studio guide.
Check the image's composition and scope before downloading
| Check | Reviewed source or expected value |
|---|---|
| Release state | Published October 20 06:08:10 UTC; prerelease=true. The author awaits a complete fresh-card hardware run. |
| Intended hardware | HD1910, Radxa Zero 3W, addressed 15-servo build; not XL330. Match HAT and torso IMU before first boot. |
| Component versions | Armbian 26.2.1 / Debian 13, official base runtime 0.15.1; author fork a844db69; Studio7a050c1; image builder24a2670. This is not official0.17.8 on every component. |
| Compressed image | 709,972,236 bytes; use the matching .img.xz.sha256. We checked checksum text and API metadata, not the large image binary. |
| Distribution terms | Models permit personal noncommercial replication; no preinstallation or distribution with paid kits, robots, HATs or cards, and no paid services. Read the separate component/model terms. |
The published compressed-image SHA-256 is 0e71ea397af70d38067ae4fbde959b3d375bac11aabdc25a29c0b96fc03bd30e. A matching checksum checks file integrity; it does not validate the robot or all bundled software. Release · Manifest · Checksum text · Model terms.
shasum -a 256 -c microduck-replica-20261020.img.xz.sha256Get-FileHash -Algorithm SHA256 .\microduck-replica-20261020.img.xzPhone setup: follow the network transition
The author's guide expects first boot to name the machine duck-xxxx, detect its already connected IMU and create hotspot Microduck-xxxx when no Wi-Fi works. It estimates around three minutes for the initial boot. Connect the phone to that hotspot, keep the connection despite its no-internet notice, and open http://10.42.0.1:8000/. If a phone routes around the hotspot, disable mobile data for this local connection. The shared hotspot password is microduck; Studio initially has no login password. Set a Studio password in More before using the robot around others; HTTP and a Host/Origin check are not encryption or a private network.
After choosing the home Wi-Fi and confirming the switch, losing the hotspot connection is expected. Rejoin the home Wi-Fi and try http://duck-xxxx.local:8000/; on Android, use the device IP from the router if mDNS fails. A wrong key or connection error should return the hotspot, within about two minutes according to the guide. Saved encrypted networks still need a password for each connection request. A manually installed Studio without netcheck, net.json, hotspot configuration and configd permissions will not show the Wi-Fi card; copying Studio alone does not install image networking. First-use guide · Studio/image distinction.
Calibration commit is implemented; readback is still the gate
Keep the author's six stages separate: servo zero → verified IMU orientation → commit to runtime → pair pad → confirm emergency stop → supported movement. The image starts robotd in commissioning mode so an uncalibrated robot can report its IMU and servo samples. The source commit path requires the matching helper0.5.1, readiness checks and a nonactive policy; it backs up files, removes its own commissioning drop-in and restarts the runtime. Success requires mode=motion, phase=control and matching calibration-status values. If files, restart or readback fail, file and mode rollback are reported separately; rollback itself can fail. Do not force a mode switch or treat a restart as proof. foreign_commissioning is a stop-and-diagnose condition for an unrecognized override. Installation and guards · Commit implementation.
Closing Studio or stopping robotd still does not remove existing servo torque. Use the current guide's supported bus handback and a fresh torque-off readback. The image also does not automatically shut down on low battery or relax after a fall. Pairing/stop tests on the author's second robot do not establish that the new card, every board or calibration rollback works. Keep the three newly designed boards marked unaccepted and preserve the earlier turning/restart limitations.
CAD v2.2: reconcile the actual workbook and print project
| Artifact | What was actually read | What to do with the difference |
|---|---|---|
| BOM October20 | 33 print rows;23 purchased rows, not the README's21. Row44 is the AMP2.0 debug lead;row59 is the sole grip pad. | A row is not a physical piece count. Keep quantities, packs, alternatives and optional skating items separate. Blank or / prices are not free parts. |
| 3MF October20 | Six plates,43 build instances. Plate6 has four 合体轮胎.STEP instances; the README still describes five plates,52 objects and separate wheels. | Inspect the current project in your slicer; do not add the old four rims/four tires as another requirement. |
| Material settings | Plate6 is named TPU材料; global profiles still read PLA / PLA. P2S,0.4mm nozzle,0.2mm layer settings are present. | Choose TPU and appropriate slicing parameters for the one-piece tires. Review soft mouth/sole requirements separately; this is not a ready-to-send print job. |
| Version and geometry | The v2.2 author notes add top-shell vents and tighter upper-leg fit. New workbook and3MF bytes differ from the old files. | HD1910 and XL330 mating parts remain separate. We inspected package metadata, not SolidWorks/STEP geometry, fit or a printed robot. |
The inspected 3MF SHA-256 is d1a6a4f640d31f5d9e24e7bb1c736f965294bb35fd86fcd2e3372334f0a16b6e. The workbook servo label contains HD1901M, while the selected route is documented as HD1910: verify the actual model instead of treating that cell as a new compatible servo. The workbook lists a64GB card; the image guide's minimum is8GB and its reported setup uses32GB. Its cached prices and the separate Open Duck Mini budget are not a current all-in quote. CAD notes · v2.2 release · Workbook · 3MF.
Preview the new commissioning and Wi-Fi screens without a robot
The fixed Studio guide supplies Python3.13 fake services and loopback-only development login. Run these from a complete Studio source directory in separate terminals; these are author instructions, not software this site executed. The image omits tests/dev files, so copy the source directory for this preview. On Linux use python3 with Python3.13 instead of the Windows launcher. Never put development autologin on a robot or a public listener.
py -3.13 -I dev/fake_robotd.py --fixture tests/fixtures/now-20261018.jsonl --mode commissioning --calib factory --net-mode hotspot --net-state-file ./state-dev/net.jsonpy -3.13 -I run.py --listen 127.0.0.1:18080 --robotd tcp:127.0.0.1:17001 --configd tcp:127.0.0.1:17002 --net-state ./state-dev/net.json --dev-autologin --state-dir ./state-dev --log-dir ./logs-devFor a useful issue report, record the image tag, actual fork/helper/Studio version, the stage that failed and the first relevant error. A diagnostic export can include serial identifiers and LAN addresses even though passwords are redacted; review it before sharing. Do not publish a full diagnostic bundle or change hardware merely to answer the editorial discussion. Original checklist.
The following describes the October 19 first version. Its missing calibration-write and Wi-Fi features were subsequently implemented in the reviewed October 20 source; physical acceptance remains a separate question. The three new boards still lack physical acceptance.
October 19 additions do not replace the earlier build record
Studio was committed at 16:59 UTC and the hardware projects at 17:01 UTC on October 19, at fixed revision 71e45b1690f4cdd435577bb1312699107914fae2. The source adds a web console for robotd/configd API v40 and local vendor dependencies, not a new ready-to-flash robot image. Earlier V167 I²C trials, weak turning and the unresolved restart remain separate evidence. This site reviewed the source and did not install the console or operate servos. Author record · Studio manual.
Preview without connecting a robot
Use the complete software/studio directory from the fixed source and Python 3.13. In one terminal, start the fake service; in another, start the loopback web UI. The author's Windows commands are below; on Linux or macOS replace py -3.13 with your Python 3.13 executable. Open http://127.0.0.1:18080/. The fixture replays recorded state and simulated responses, so a working preview is not a successful physical test. Never use --dev-autologin on a board or exposed address.
py -3.13 -I dev/fake_robotd.py --fixture tests/fixtures/now-20261018.jsonlpy -3.13 -I run.py --listen 127.0.0.1:18080 --robotd tcp:127.0.0.1:17001 --configd tcp:127.0.0.1:17002 --dev-autologin --state-dir ./state-dev --log-dir ./logs-devRead-only board checks before installing the helper
On a matching board, from the copied Studio directory, the author provides this selfcheck to print versions and query robotd, configd and padd. It does not validate all firmware variants or authorize a bus handover:
python3 -I run.py --selfcheckThe normal board UI is HTTP on port 8000 and starts without a password. Set a separate Studio password before network access and use a trusted LAN; Host/Origin checks do not themselves add login or transport encryption. This command writes Studio authentication state, not the Linux account password:
python3 -I run.py set-passwordDirect servo access needs the separately documented privileged helper and robotd guard. Follow the original install/uninstall guide for the exact user, file permissions and version checks instead of copying a service recipe from a different image. Marker-based holding handback still needs the matching fork and its board checks; an installation checklist is not a published test result. Helper guide and limitations · Authentication implementation.
A click, a closed page and a calibration result mean different things
Studio confirms relax only after a later bus-status readback reports torque off. Closing the page, stopping Studio or stopping robotd does not by itself remove servo torque. A recovered servo session can still be holding position. Use the explicit handback path and actual status, rather than manually starting robotd while Studio owns the bus. The author also documents handover races and untested marker-handback checks.
The servo page can write directly to servos, so it is not a read-only viewer. The first edition can calculate IMU orientation and calibration information but cannot yet write zero/direction and IMU orientation into the main runtime calibration. Tuning/model pages are viewers; browser Wi-Fi provisioning and writable gait tuning are still future work. First-version scope.
Three new boards: check files and remaining work before fabrication
| Board | New information | Still unresolved |
|---|---|---|
| Bus IMU v2 | STM32G031 + LSM6DSV16X; Feetech-compatible A2007WR-3P connector; IMU rotated 180° | Not received/tested; host axis mapping must be redetermined. Old I²C BNO085 settings are not a substitute. |
| Servo bus hub | Passive Battery / DXL_BUS / GND distribution | Not prototyped; the 8.4 mm CN1 terminal conflicts with roughly 5 mm clearance. |
| Battery terminal board | Editable project and STEP; the POGO_PIN name now refers to solder pads, not spring contacts | Not prototyped; match polarity, mechanical fit and the actual connection plan. |
Each folder has an EasyEDA Pro .eprj2 project and STEP model; only the IMU board has a schematic PDF. Gerber, BOM and wiring tables are not yet provided. Connector pin order differs between the 2.0 mm and 1.2 mm families: identify the connector and source labels before planning a cable. The author also calls for checking bus low level with the new 0 Ω R6 and remapping the rotated IMU. These are author design notes, not independently audited circuitry or a ready-to-order board set. Fixed board README.
Source review: October 16, 2026. The latest fanhao375 project revision is 2b734d5; the independent CAD README revision is 1214bc6, while the manufacturing 3MF remains at the earlier source snapshot. Build, bench and camera results below are reported by their authors. We did not print, flash or operate this hardware. Project overview ↗.
Choose the servo and CAD version first
The project separates the physically assembled Feetech HD-1910 route from an XL330 route. The build record ↗ links the 15-servo assembly and posture sequences; standing up and sitting down demonstrate those movements, not a trained walking controller. Use the current print-file pointer ↗ to reach 机械行者Robo’s CAD repository ↗. Its checked versions are HD-1910 v2.1 and XL330 v1.1; the horn mating parts differ. Older simulation meshes left in the main replica repository are not manufacturing-ready substitutes.
September 30 print project: inspect materials and the camera mount
The repository now contains microduck-飞特版-BambuStudio2026-09-30.3mf ↗. Direct inspection of its Bambu Studio ZIP metadata found four 合体轮胎.STEP source objects and no old separate rim/tire source names. The saved project contains two filament presets, both PLA. The author’s BOM correction ↗ says the combined tires, soft jaw and soft mouth top require TPU. Set the materials object by object before slicing; the project’s PLA default is not a printable instruction for every part. This file inspection does not establish fit, strength or a successful print.
The same project embeds a plain face_part_面部零件.stp; it does not include the later face_part-FT1 variant whose hole spacing was changed for the original Radxa camera. Obtain the separate v2.1 changed-parts STEP release ↗ if that camera mount matches your bill of materials. The September 29 assembly workbook ↗ has 33 printed-part categories and 21 purchased-part categories with purchase links, not a 54-piece quantity or a verified delivered cost. Choose the walking or optional roller variant before counting prints. The CAD README still mentions the replaced September 15 3MF; the committed September 30 file is the evidence for this correction.
What the bench and camera tests actually show
- The September 28 feedback record ↗ reports 14 joints held in a pose, 3,000 valid samples each, about 63.99 seconds total and about 46.87 Hz observed against a 50 Hz target. The mouth servo was excluded; goals were not changed. Zero new timeout/ID/checksum errors in that window do not resolve errors in other runs, and this was not IMU sampling, policy inference or motion writing.
- The camera record ↗ reports a 40-frame 1920×1080 short test after cable correction on Radxa Bookworm B1. It does not validate sustained throughput or the project’s separate Armbian image.
Calibrate each HD-1910 joint with the new source tool
The October 11 HD1910M tool change ↗ adds zero (0x0B position calibration), reboot (0x08), degree input for limits, and range checks for deferred writes. Build from the committed Cargo manifest ↗; its binary name is feetech-HD1910M-tester. Replace PORT and SERVO_ID with the actual serial device and joint ID. The default ID is 1, which may be the wrong joint on an assembled robot. Support the joint, keep another controller off the bus, and inspect the author’s wiring and power guide ↗ before energizing it.
cd tools/FeeTech_HD1910M_Servo
cargo build
./target/debug/feetech-HD1910M-tester -p PORT -i SERVO_ID get pos
./target/debug/feetech-HD1910M-tester -p PORT -i SERVO_ID get pos-offset
./target/debug/feetech-HD1910M-tester -p PORT -i SERVO_ID get min-angle
./target/debug/feetech-HD1910M-tester -p PORT -i SERVO_ID get max-angle
./target/debug/feetech-HD1910M-tester -p PORT -i SERVO_ID torque off
# Hold this joint at its intended mechanical zero.
./target/debug/feetech-HD1910M-tester -p PORT -i SERVO_ID zero
./target/debug/feetech-HD1910M-tester -p PORT -i SERVO_ID get pos
./target/debug/feetech-HD1910M-tester -p PORT -i SERVO_ID get pos-offset
zero unlocks EPROM, applies the calibration, relocks it and reads back position plus offset. Its code rejects a position more than four counts from the requested target; it does not compare the offset with the pre-change value for you. Record both readings before making the persistent change. Do not run this single-turn calibration in multi-turn mode. The tutorial and CLI differ in their brief torque-restoration wording, so do not blindly enable torque on a hanging joint: verify the result and use the current source procedure for your supported assembly.
Use limits MIN_DEG MAX_DEG --deg only after deriving a safe range for that joint; without --save it is temporary. Add --save only when the range has been checked and should persist. The CLI prints the two returned limits but does not automatically compare them with the requested numbers. After a persistent change, issue reboot, wait about one second, then read min-angle, max-angle, pos and pos-offset again. A reboot command without a reply may still have restarted the servo; subsequent communication and readbacks check persistence, while an SRAM marker would be needed to prove the restart itself. Reboot does not undo a saved zero. If the previous values were recorded, restore them with offset OLD_OFFSET --save and limits OLD_MIN OLD_MAX --save, then restart and read again; otherwise re-align and recalibrate the zero. Command implementation ↗.
The author’s 15-servo report ↗ names firmware 3.46 and IDs 10–14, 20–24 and 30–34, with standing-pose readbacks within four counts of target. Its changelog is internally dated October 3, but this source entered the repository on October 11; the manifest still says package version 0.1.0 despite a 0.2.0 changelog heading. We have not compiled it or repeated the hardware experiment. The September 28 14-joint, 3,000-samples-each stationary feedback window had no motion writes. That 15-servo record alone did not establish a combined IMU, ONNX inference and motion-control loop; the author reported a distinct, later partial closed-loop trial on October 12 below.
Read the image guide before first login
The image instructions ↗ correct the original public card’s first-login sequence: complete the Armbian initial-root wizard before expecting the regular duck account, then replace defaults. The September 20 image still needs the documented wireless DHCP correction; the September 29 candidate passed offline checks but was not flashed and boot-tested as that exact artifact. Both are base operating-system images, not a bundled runtime, servo console or walking policy. Match the Radxa Zero 3W V1.12 board, image and checksum; follow the source’s separate USB/HAT power instructions.
Where the new training reference fits
The current kissqy HD1910 project ↗ publishes a distinct firmware, model and desktop-console stack. Its earlier R1 release guide ↗ and present packages can now be compared with your own hardware rather than treated as a future download. Its online console preview still uses simulated data. The older pinned baseline described pre-release limits; the new one-robot physical result below is from a separate locally patched replica, not proof that every packaged motion works on every build.
Public R1 image: verify the file and your hardware
The October 12 public release ↗ includes a real, anonymously reachable microduck-zero3w-0.15.1-R1.img.xz asset ↗ (767,412,924 bytes). Its published SHA-256 is 75da978b5d56acd9e4146256431732381de84523bb683e4ab7ac9f0580a7bce5; compute your own local hash after download. The release-body prose has an older filename, so select the actual asset. The pinned setup guide ↗ says to flash the compressed image as a custom image in Armbian Imager, then connect to Microduck-kissqy (initial password 12345678) and complete Wi-Fi plus new login-password setup, using http://10.42.0.1:8088 if the captive page does not open. The Windows R17 V164 ZIP ↗ and R1.5.27 ZIP ↗ are separate fixed-commit downloads, not applications preinstalled on your computer.
sha256sum microduck-zero3w-0.15.1-R1.img.xz
# On macOS, if sha256sum is unavailable:
shasum -a 256 microduck-zero3w-0.15.1-R1.img.xz
R1 uses official Microduck 0.15.1 plus kissqy’s Feetech stack. The author reports one Zero reflash with hotspot/Wi-Fi, SSH, robot-bus and R17 identification, not every board or gait. The published runtime IMU source ↗ reads its bus-mounted imu_to_dxl board; the replica author’s read-only image inspection ↗ found no BNO085 mainboard-I2C path and warned that a particular Zero 3W V1.12/AIC8800 board may need a different bootloader. The author later booted an R1 V164 card on that V1.12 machine after adding an unpublished bootloader and I2C-IMU patch; hotspot and Wi-Fi setup opened, followed by a brief model run. This does not validate unmodified R1 on that board. Do not equate this image with the replica author’s older bare Armbian base images or with the locally modified runtime used in the trial below. The packaged sample calibration must be replaced with the actual robot’s servo zeros, directions, joint limits and IMU mount before HOME or motion.
New physical result: IMU zero, policy hold, alternating legs
In a first bring-up ↗ and October 12 night record ↗, the replica author reports one HD1910 ×15 robot with a BNO085 on the Zero’s I2C bus and a locally patched kissqy R17 runtime. Initial HOME and a 10-second policy hold were followed by falls. Comparing actual joint angles with the official MJCF revealed an approximately 8.54° pitch and 1.78° roll IMU mounting offset on that machine. After correction, the author reports a 70-second policy hold without a fall and three joystick trials in which the knees alternated; the last 6.3-second trial had about 26 swaps. Forward distance was not measured because its odometry stayed at zero, so this is partial closed-loop first motion, not a measured sustained walk. The raw robot logs were not independently inspected here.
The public analysis steps ↗ show how to check axis signs first, capture a stationary HOME pose, compare that build’s actual joint angles with the official MJCF and calculate its own sensor mounting correction. Back up hd1910-calibration.toml, make any mount change only with torque off, restart the service and repeat the static check before movement. The author’s quaternion and 8.54° value are not a calibration for another assembly. Intermittent IMU wiring, power drop and heat were also found in that one build. The locally patched BNO085 runtime is not part of the public R1 download.
Short-run diagnosis: power, model settings and servo response
The author’s October 13 night report ↗ compares that patched R1/V164 card with an older locally patched R17 card on the same HD1910 robot. Both lost whole-board power during short model runs; the new card’s last servo-side voltage was about 3.9 V, and video plus logs ended without a shutdown sequence. The author suspects supply or lead transients, but had not yet measured the transient with a scope or verified a repair. Do not read this as a software fix or a tested wiring prescription. Record the supply, board revision, model and last health/log entries on your own build before repeating a powered test.
The combined walking/fall model in that report loads its own deployment-execution.json. For that model, changing robotd.toml action scale or filters did not change the loaded values: inspect robot.busStatus.loaded_models.walk.runtime_execution_profile first. On this machine, the V164 console’s D and torque-limit boxes also did not affect the servos, while its older R17 setup used another path. The author’s short tests found less high-frequency jitter after several servo settings changed together, but foot clearance remained below its simulation and some responses worsened. The public analysis scripts ↗ show the measurement method; no gain, torque or IMU number from this robot is a reusable tuning recipe. There is still no measured forward distance or sustained-walk verification.
What changed after the V167 source-only review
kissqy V167/control.43 still writes fixed D=0 and torque limit=1000 to servo RAM on each arm; it does not persist to EEPROM or establish arbitrary GUI tuning. The release publisher did not record a physical V167 walking test. The replica author has since installed their separate I2C fork ↗ on one HD1910 robot, with a BNO085 on the Zero’s I2C4, and reports standing, walking and turning on October 15. This is an author-specific fork result, not stock R1 or stock kissqy V167 validation. Its optional servo parameter file has source/unit checks but was not exercised with a file on that robot; UDP pad and pad-loss sit were host-tested, not robot-tested. The updated installer ran once on the board, while real-board rollback remains untested. LSM6DSV16X direct-I2C remains a simulated-bus route.
BNO085 attitude jumps: a limited one-robot gyro-fusion result
In the author’s October 15 report ↗, the BNO085 chip’s own fused orientation sometimes jumped 20–60° within one 20 ms step during walking while its gyro indicated little rotation. The fork can integrate the chip gyro and slowly compare it with the chip attitude; the default still publishes the chip value, and the alternate gyro mode must be selected deliberately. On that robot, the earlier chip segment had 62 seconds upright in walk mode, nine cumulative seconds of stick input and three falls. A later gyro segment had 634 seconds upright, 60 cumulative seconds of stick input and one fall between pushes; none occurred while the stick was held. The committed short walking clip ↗ shows the author’s progress, not a distance test. These were unequal, non-interleaved segments, and the full raw logs/video remain private: this is not a controlled A/B result or proof of long-distance walking. The suspected chip-internal cause is an inference from the author’s telemetry, not a manufacturer finding.
The same report measured this duck at 806 g, found weak turning and recorded another whole-board reboot while standing in walk mode. It does not establish whether that reboot was a power interruption or hang, nor a proven repair. The fork guide ↗ describes shadow-first checks and how to return to chip mode on a particular build; copying its gyro thresholds, servo gains, IMU orientation or wiring to a different robot is not a general recipe. Reinstalling stock kissqy firmware still removes the fork’s I2C support. For new bus-board builds, use the separate FT6 RevA guide; it is not firmware for a ready-made I2C module.
Assembly footage and the still-missing steps
The CAD/BOM creator’s assembly series ↗ has seven videos numbered 1–6 and 8; its current CAD README ↗ still lists only the first six and does not change the older Feetech 3MF or TPU requirements. Episode 7 is absent. Use the direct chapter list in our DIY tutorial guide. The replica author’s corrected purchase note ↗ recommends 1 GB or 2 GB no-eMMC Zero 3W plus 32 GB microSD instead of the old 2 GB/16 GB eMMC preference; the reported integrated test used a 2 GB no-eMMC board, not a tested 1 GB configuration. Document your board revision and use the appropriate image rather than copying a purchase claim across revisions.
For a repeatable walking build, the remaining checks are measured travel on a marked floor, grip on the specified TPU foot parts, repeatable starts, thermal and power margins, and public compatibility of the IMU/runtime patch. The September 28 14-joint stationary readback and October 11 15-servo configuration remain narrower historical tests. This site has not printed, flashed or operated the robot; keep a build log with exact board, firmware, model and failures.
What would you like to understand next?
Keep the source, your environment and your observations together.
Before you continue
Can I order and print the HD1910 replica directly from this BOM and 3MF?
First resolve the blank BOM quantities and the TPU/PLA conflict, then match your printer and the dated files. The November 2 workbook has 33 print entries and 24 purchased entries; it is not a verified shopping basket. The pinned CAD README and files are the sources. This site checked archives only. Continue below to the same-language image and first-use checks.
Does an online servo in RC4 mean the replica is ready to walk?
No. On the ZERO 3W/HD-1910 RC4 prerelease, inspect fresh feedback, missing replies and IMU sample age first, then follow the existing calibration and HOME/motion gates. Unknown data is not zero or success. The author’s report is an offline check, and this site has not booted or tested the robot.
Applies to: fanhao375/microduck-replica · HD1910. Keep the model, image, software and driver versions together. The dated sections below retain their original verification limits.
Source checked:
Sources and review (174)
- github.com/fanhao375/microduck-replica/blob/019b8c54f8a2fa7d800ca1f1394167a1ca8fdef5/README.en.md
- github.com/fanhao375/microduck-replica/blob/019b8c54f8a2fa7d800ca1f1394167a1ca8fdef5/BUILD-LOG.en.md
- github.com/fanhao375/microduck-replica/blob/019b8c54f8a2fa7d800ca1f1394167a1ca8fdef5/tools/radxa/50Hz保持姿势读状态-20260928.md
- github.com/fanhao375/microduck-replica/blob/019b8c54f8a2fa7d800ca1f1394167a1ca8fdef5/tools/radxa/摄像头调试记录-20260928.md
- github.com/fanhao375/microduck-replica/blob/019b8c54f8a2fa7d800ca1f1394167a1ca8fdef5/tools/radxa/镜像使用说明.md
- github.com/fanhao375/microduck-replica/blob/019b8c54f8a2fa7d800ca1f1394167a1ca8fdef5/hardware/imu_to_dxl/README.md
- github.com/fanhao375/microduck-replica/blob/019b8c54f8a2fa7d800ca1f1394167a1ca8fdef5/print/README.en.md
- github.com/fanhao375/microduck-replica-cad/blob/c9a533bc1206d8899950a5d466965a992d7e052a/README.md
- github.com/fanhao375/microduck-replica-cad/blob/c9a533bc1206d8899950a5d466965a992d7e052a/打印/microduck-飞特版-BambuStudio2026-09-30.3mf
- github.com/fanhao375/microduck-replica-cad/blob/c9a533bc1206d8899950a5d466965a992d7e052a/BOM/装配BOM-机械行者Robo-2026-09-29-带采购链接.xlsx
- github.com/fanhao375/microduck-replica-cad/releases/tag/v2.1
- github.com/kissqy/Microduck-kissqy/blob/94328f5b43c8ac825c90f0e564e7d1b926cd770d/microduck-hd1910/README.md
- github.com/kissqy/Microduck-kissqy/blob/94328f5b43c8ac825c90f0e564e7d1b926cd770d/microduck-hd1910/docs/BASELINE.md
- github.com/pollen-robotics/elec_RPI_Robot_HAT/tree/23eab11927f95ceca0dfa35bf182caeb7db39ea0
- github.com/pollen-robotics/microduck_rl/blob/ceca01706143d729305baa94cbd8ab990979e325/LICENSE-MODELS.md
- github.com/fanhao375/microduck-replica/blob/7e314cd41ea87ae859eb901d5d41f9765c285edb/README.en.md
- github.com/fanhao375/microduck-replica/commit/1930de423ed4822fcd21b213e39f263ea9b44b7a
- github.com/fanhao375/microduck-replica/blob/1930de423ed4822fcd21b213e39f263ea9b44b7a/tools/FeeTech_HD1910M_Servo/CHANGELOG.md
- github.com/fanhao375/microduck-replica/blob/1930de423ed4822fcd21b213e39f263ea9b44b7a/tools/FeeTech_HD1910M_Servo/TUTORIAL.md
- github.com/fanhao375/microduck-replica/blob/1930de423ed4822fcd21b213e39f263ea9b44b7a/tools/FeeTech_HD1910M_Servo/src/main.rs
- github.com/fanhao375/microduck-replica/blob/1930de423ed4822fcd21b213e39f263ea9b44b7a/tools/FeeTech_HD1910M_Servo/Cargo.toml
- github.com/kissqy/Microduck-kissqy/blob/a6e9f1a9c4e24005063b69708931c0c03ec29787/README.md
- github.com/fanhao375/microduck-replica/blob/0f365d6574c11b27270055dc3981d26d02d5626e/README.en.md
- github.com/fanhao375/microduck-replica-cad/blob/1214bc668cc5bff4b33cd2b35729cfa6e3ee7583/README.md
- space.bilibili.com/312747174/lists/9279084?type=season
- www.bilibili.com/video/BV1XYpd6qEki/
- github.com/fanhao375/microduck-replica/blob/0f365d6574c11b27270055dc3981d26d02d5626e/docs/%E7%94%B5%E6%8E%A7%E9%87%87%E8%B4%AD%E6%B8%85%E5%8D%95.md
- github.com/fanhao375/microduck-replica/blob/0f365d6574c11b27270055dc3981d26d02d5626e/docs/HD1910-20261012-kissqy%E6%95%B4%E5%A5%97%E4%B8%8A%E6%9C%BA.md
- github.com/fanhao375/microduck-replica/blob/0f365d6574c11b27270055dc3981d26d02d5626e/docs/HD1910-20261012-%E5%A4%9C-IMU%E6%A0%A1%E5%87%86%E4%B8%8E%E9%A6%96%E6%AC%A1%E8%BF%88%E6%AD%A5.md
- github.com/fanhao375/microduck-replica/blob/0f365d6574c11b27270055dc3981d26d02d5626e/tools/radxa/onboard-analysis/README.md
- github.com/fanhao375/microduck-replica/blob/0f365d6574c11b27270055dc3981d26d02d5626e/docs/HD1910-20261012-kissqy%E9%95%9C%E5%83%8FR1%E5%88%86%E6%9E%90.md
- github.com/kissqy/Microduck-kissqy/releases/tag/public-image-r1
- github.com/kissqy/Microduck-kissqy/blob/cfb94a4d5d52974e031e23a51a5e8f407e29fb48/docs/releases/public-image-r1.md
- github.com/kissqy/Microduck-kissqy/releases/download/public-image-r1/microduck-zero3w-0.15.1-R1.img.xz
- raw.githubusercontent.com/kissqy/Microduck-kissqy/3d2b210dae8cd78b20f090fe7bed8c6a49bb7108/release-assets/Microduck-Console-R17-V164.zip
- raw.githubusercontent.com/kissqy/Microduck-kissqy/3d2b210dae8cd78b20f090fe7bed8c6a49bb7108/release-assets/Microduck-Training-Studio-R1.5.27.zip
- github.com/kissqy/Microduck-kissqy/blob/3d2b210dae8cd78b20f090fe7bed8c6a49bb7108/microduck-hd1910/PUBLICATION-MANIFEST.json
- github.com/kissqy/Microduck-kissqy/blob/3d2b210dae8cd78b20f090fe7bed8c6a49bb7108/microduck-hd1910/firmware/duck-control/src/imu.rs
- github.com/fanhao375/microduck-replica/blob/5397eb14d356fa618b294a25cebd4bb0ec59c162/README.en.md
- github.com/fanhao375/microduck-replica/blob/5397eb14d356fa618b294a25cebd4bb0ec59c162/docs/HD1910-20261013-%E5%A4%9C-%E6%8E%89%E7%94%B5-%E8%88%B5%E6%9C%BAD%E4%B8%8E%E8%B9%AD%E5%9C%B0.md
- github.com/fanhao375/microduck-replica/tree/5397eb14d356fa618b294a25cebd4bb0ec59c162/tools/gait-analysis
- github.com/kissqy/Microduck-kissqy/blob/7a52d297a9adfe6d2315481953dc64060252d142/release-assets/README.en.md
- github.com/fanhao375/microduck-replica/blob/1a2936849b47e638dfc596996026f047dcfb5b05/README.en.md
- github.com/fanhao375/microduck-replica/blob/1a2936849b47e638dfc596996026f047dcfb5b05/docs/HD1910-20261014-%E7%99%BD%E5%A4%A9-%E4%BB%BF%E7%9C%9F%E6%89%BE%E5%8E%9F%E5%9B%A0%E4%B8%8E%E6%96%B0%E7%89%88%E6%94%BE%E5%BC%80%E5%8F%82%E6%95%B0.md
- github.com/fanhao375/Microduck-kissqy/blob/19555dae2519aba9a5bc7be6c1b6517439338d54/IMU-MODULE.md
- github.com/kissqy/Microduck-kissqy/blob/692278a600e565c99d932c6de73dd4bbcc27b6ac/microduck-hd1910/firmware/BUILDING-V167.en.md
- github.com/kissqy/Microduck-kissqy/blob/692278a600e565c99d932c6de73dd4bbcc27b6ac/hardware/IMU-FIRMWARE.en.md
- github.com/kissqy/Microduck-kissqy/blob/692278a600e565c99d932c6de73dd4bbcc27b6ac/hardware/3d-print-frankenduck/README.en.md
- github.com/fanhao375/microduck-replica/blob/2b734d5b472688607f5eb80314d3c603eef27094/README.en.md
- github.com/fanhao375/microduck-replica/blob/2b734d5b472688607f5eb80314d3c603eef27094/docs/HD1910-20261015-IMU%E4%B9%B1%E8%B7%B3%E6%A0%B9%E5%9B%A0%E4%B8%8E%E9%99%80%E8%9E%BA%E8%9E%8D%E5%90%88%E4%B8%8A%E6%9C%BA.md
- raw.githubusercontent.com/fanhao375/microduck-replica/2b734d5b472688607f5eb80314d3c603eef27094/assets/%E8%B5%B0%E8%B7%AF-2026-10-15.mp4
- github.com/fanhao375/Microduck-kissqy/blob/e376346723e1670a649b2a00e4dcec0f3d2a46cd/README.en.md
- github.com/fanhao375/Microduck-kissqy/blob/e376346723e1670a649b2a00e4dcec0f3d2a46cd/IMU-MODULE.md
- github.com/fanhao375/microduck-replica/blob/71e45b1690f4cdd435577bb1312699107914fae2/README.en.md
- github.com/fanhao375/microduck-replica/blob/71e45b1690f4cdd435577bb1312699107914fae2/software/studio/README.md
- github.com/fanhao375/microduck-replica/blob/71e45b1690f4cdd435577bb1312699107914fae2/software/studio/deploy/INSTALL.md
- github.com/fanhao375/microduck-replica/blob/71e45b1690f4cdd435577bb1312699107914fae2/software/studio/studio/auth.py
- github.com/fanhao375/microduck-replica/blob/71e45b1690f4cdd435577bb1312699107914fae2/hardware/%E6%96%B0%E7%89%88/README.md
- github.com/fanhao375/microduck-replica/releases/tag/microduck-replica-image-20261020
- github.com/fanhao375/microduck-replica/blob/36854c788bbe38b2397e0954813ebe8b16e60983/software/image/%E7%83%A7%E5%BD%95%E5%92%8C%E7%AC%AC%E4%B8%80%E6%AC%A1%E4%BD%BF%E7%94%A8.md
- github.com/fanhao375/microduck-replica/blob/36854c788bbe38b2397e0954813ebe8b16e60983/software/image/README.md
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261020/microduck-replica-20261020-manifest.txt
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261020/microduck-replica-20261020.img.xz.sha256
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261020/microduck-replica-20261020-models.txt
- github.com/fanhao375/microduck-replica/blob/36854c788bbe38b2397e0954813ebe8b16e60983/software/studio/README.md
- github.com/fanhao375/microduck-replica/blob/36854c788bbe38b2397e0954813ebe8b16e60983/software/studio/deploy/INSTALL.md
- github.com/fanhao375/microduck-replica/blob/36854c788bbe38b2397e0954813ebe8b16e60983/software/studio/studio/commit.py
- github.com/fanhao375/microduck-replica/blob/36854c788bbe38b2397e0954813ebe8b16e60983/README.en.md
- github.com/fanhao375/microduck-replica-cad/blob/dabbda7c592e42e0d016a293dc8c9fcabb300bbf/README.md
- github.com/fanhao375/microduck-replica-cad/releases/tag/v2.2
- github.com/fanhao375/microduck-replica-cad/blob/dabbda7c592e42e0d016a293dc8c9fcabb300bbf/BOM/%E8%A3%85%E9%85%8DBOM-%E6%9C%BA%E6%A2%B0%E8%A1%8C%E8%80%85Robo-2026-10-20-%E5%B8%A6%E9%87%87%E8%B4%AD%E9%93%BE%E6%8E%A5.xlsx
- github.com/fanhao375/microduck-replica-cad/blob/dabbda7c592e42e0d016a293dc8c9fcabb300bbf/%E6%89%93%E5%8D%B0/microduck-%E9%A3%9E%E7%89%B9%E7%89%88-BambuStudio2026-10-20.3mf
- github.com/fanhao375/microduck-replica/releases/tag/microduck-replica-image-20261021b
- github.com/fanhao375/microduck-replica/releases/tag/microduck-replica-image-20261021
- api.github.com/repos/fanhao375/microduck-replica/releases/tags/microduck-replica-image-20261021b
- github.com/fanhao375/microduck-replica/blob/39065e3db2c36223bc572c63a59d2aa91e205248/software/image/%E7%83%A7%E5%BD%95%E5%92%8C%E7%AC%AC%E4%B8%80%E6%AC%A1%E4%BD%BF%E7%94%A8.md
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261021b/microduck-replica-20261021b-manifest.txt
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261021b/microduck-replica-20261021b.img.xz.sha256
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261021b/microduck-replica-20261021b-models.txt
- github.com/fanhao375/microduck-replica/blob/39065e3db2c36223bc572c63a59d2aa91e205248/software/studio/README.md
- github.com/fanhao375/microduck-replica/blob/39065e3db2c36223bc572c63a59d2aa91e205248/software/studio/deploy/INSTALL.md
- github.com/fanhao375/microduck-replica/blob/39065e3db2c36223bc572c63a59d2aa91e205248/software/image/overlay/usr/local/sbin/microduck-netcheck
- github.com/fanhao375/microduck-replica/blob/39065e3db2c36223bc572c63a59d2aa91e205248/software/studio/studio/sshkeys.py
- github.com/fanhao375/microduck-replica/blob/39065e3db2c36223bc572c63a59d2aa91e205248/software/studio/deploy/microduck-helper
- github.com/fanhao375/microduck-replica/blob/39065e3db2c36223bc572c63a59d2aa91e205248/software/studio/studio/commit.py
- github.com/fanhao375/microduck-replica/blob/39065e3db2c36223bc572c63a59d2aa91e205248/hardware/imu_to_dxl/firmware-1.0.0/VALIDATION.md
- github.com/fanhao375/microduck-replica/blob/39065e3db2c36223bc572c63a59d2aa91e205248/README.md
- github.com/kissqy/Microduck-kissqy/blob/aed2403d4c9839701b0ba59edf1a741020170ef1/microduck-hd1910/firmware/docs/robot/armbian-boot-config.md
- github.com/kissqy/Microduck-kissqy/blob/aed2403d4c9839701b0ba59edf1a741020170ef1/microduck-hd1910/firmware/scripts/repair-armbian-env.py
- github.com/kissqy/Microduck-kissqy/blob/aed2403d4c9839701b0ba59edf1a741020170ef1/docs/ASSEMBLY-NOTES.en.md
- github.com/kissqy/Microduck-kissqy/blob/aed2403d4c9839701b0ba59edf1a741020170ef1/hardware/3d-print-frankenduck/README.en.md
- github.com/kissqy/Microduck-kissqy/blob/aed2403d4c9839701b0ba59edf1a741020170ef1/hardware/3d-print-frankenduck/FILE-MANIFEST.json
- github.com/kissqy/Microduck-kissqy/blob/aed2403d4c9839701b0ba59edf1a741020170ef1/hardware/3d-print-frankenduck/SHA256SUMS
- github.com/JoyandAI/OpenMicroDuck/blob/b8c7d6945e5ceda9ceb9706b53c372adb9ae4128/docs/bom.md
- github.com/fanhao375/microduck-replica/releases/tag/microduck-replica-image-20261023
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261023/microduck-replica-20261023-manifest.txt
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261023/microduck-replica-20261023.img.xz.sha256
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261023/microduck-replica-20261023-models.txt
- github.com/fanhao375/microduck-replica/blob/6be8477371832a6b1f526b650dcca90acaa884bb/docs/superpowers/verification/2026-10-23-image-release.md
- github.com/fanhao375/microduck-replica/blob/03136c9a9b5149d1f66b7c4a62e82feb3e9be490/software/studio/MODEL_IMPORT.md
- github.com/fanhao375/microduck-replica/blob/03136c9a9b5149d1f66b7c4a62e82feb3e9be490/software/studio/studio/model_package.py
- github.com/fanhao375/microduck-replica/blob/03136c9a9b5149d1f66b7c4a62e82feb3e9be490/software/studio/studio/models.py
- github.com/fanhao375/microduck-replica/blob/6be8477371832a6b1f526b650dcca90acaa884bb/docs/superpowers/verification/2026-10-23-imu-revalidate.md
- github.com/fanhao375/microduck-replica/blob/03136c9a9b5149d1f66b7c4a62e82feb3e9be490/software/studio/studio/imu.py
- github.com/fanhao375/microduck-replica/blob/03136c9a9b5149d1f66b7c4a62e82feb3e9be490/software/studio/deploy/microduck-helper
- github.com/fanhao375/microduck-replica/blob/03136c9a9b5149d1f66b7c4a62e82feb3e9be490/software/studio/studio/sensors.py
- github.com/fanhao375/microduck-replica/blob/6be8477371832a6b1f526b650dcca90acaa884bb/software/image/%E7%83%A7%E5%BD%95%E5%92%8C%E7%AC%AC%E4%B8%80%E6%AC%A1%E4%BD%BF%E7%94%A8.md
- github.com/Ley-WL/microduck-rl/blob/5de6e0838c65f5b67a2f13e8d0d1dc307f35a5e4/docs/shared-walk-handoff-20261022.md
- github.com/Ley-WL/microduck-rl/blob/5de6e0838c65f5b67a2f13e8d0d1dc307f35a5e4/models/pick_hd1910_1001/README.md
- github.com/fanhao375/microduck-replica/releases/tag/microduck-replica-image-20261023c
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261023c/microduck-replica-20261023c.img.xz.sha256
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261023c/microduck-replica-20261023c-manifest.txt
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261023c/microduck-replica-20261023c-models.txt
- github.com/fanhao375/microduck-replica/blob/0ddce374a30ef91ba4913daabc62b0c9637dd8fa/docs/HD1910-20261023-%E6%80%BB%E7%BA%BFIMU%E8%87%AA%E5%8A%A8%E8%AF%86%E5%88%AB.md
- github.com/fanhao375/microduck-replica/blob/0ddce374a30ef91ba4913daabc62b0c9637dd8fa/software/image/%E7%83%A7%E5%BD%95%E5%92%8C%E7%AC%AC%E4%B8%80%E6%AC%A1%E4%BD%BF%E7%94%A8.md
- github.com/fanhao375/Microduck-kissqy/blob/0791fcd44f71c705dc8bb0fbcde405593b52d19b/microduck-hd1910/firmware/docs/project/imu-bus-autodetect-20261023.md
- github.com/fanhao375/microduck-replica/blob/0ddce374a30ef91ba4913daabc62b0c9637dd8fa/docs/superpowers/verification/2026-10-23-imu-coarse-stance.md
- github.com/fanhao375/microduck-replica/blob/dd7a753026c40b0bf385374a896e7253cff42720/software/studio/studio/imu.py
- github.com/fanhao375/microduck-replica/blob/dd7a753026c40b0bf385374a896e7253cff42720/software/studio/deploy/microduck-helper
- github.com/ScrapMeta/microduck-diy/tree/db04d323caa053ae0c96629268392cdbe7dc8b4f/imu_to_dxl/firmware
- github.com/kissqy/Microduck-kissqy/blob/eccc2fdbbf4c835e12abfa7ae6c93b1b1462fc51/docs/MICRODUCK-BUILD-GUIDE.en.md
- github.com/kissqy/Microduck-kissqy/blob/eccc2fdbbf4c835e12abfa7ae6c93b1b1462fc51/docs/MICRODUCK-FAQ.en.md
- github.com/fanhao375/microduck-replica/blob/e4a1ac854271ec20e2af18b66f838c01dde536fb/docs/update-history.en.md
- github.com/fanhao375/microduck-replica/blob/e4a1ac854271ec20e2af18b66f838c01dde536fb/assets/demos/2026-10-24-roll-and-rise.mp4
- github.com/fanhao375/microduck-replica/blob/e4a1ac854271ec20e2af18b66f838c01dde536fb/assets/demos/2026-10-24-walking.mp4
- github.com/fanhao375/microduck-replica/blob/e4a1ac854271ec20e2af18b66f838c01dde536fb/docs/%E4%B8%8A%E6%89%8B%E6%8C%87%E5%8D%97/Microduck%E4%B8%8A%E6%89%8B%E6%8C%87%E5%8D%97-V2-20261022.pdf
- github.com/fanhao375/microduck-replica/blob/e4a1ac854271ec20e2af18b66f838c01dde536fb/software/image/%E7%83%A7%E5%BD%95%E5%92%8C%E7%AC%AC%E4%B8%80%E6%AC%A1%E4%BD%BF%E7%94%A8.md
- github.com/fanhao375/microduck-replica/releases/tag/microduck-replica-image-20261027
- github.com/fanhao375/microduck-replica/releases/tag/microduck-software-v2026.10.28
- github.com/fanhao375/microduck-replica/blob/fc32b6a23d71c7271179cabb6d5d84d6781feced/docs/软件更新与Qinmo使用说明-20261028.md
- github.com/fanhao375/microduck-replica/blob/53c0dc96dbbdd127deeb2322cc6e551e5fd8f61d/software/studio/deploy/NATIVE-UPDATE.md
- github.com/fanhao375/microduck-replica/blob/fc32b6a23d71c7271179cabb6d5d84d6781feced/docs/Qinmo-IMU-网页使用.md
- github.com/fanhao375/microduck-replica/blob/fc32b6a23d71c7271179cabb6d5d84d6781feced/docs/superpowers/verification/2026-10-28-software-release.md
- github.com/fanhao375/microduck-replica/blob/53c0dc96dbbdd127deeb2322cc6e551e5fd8f61d/software/updater/package.py
- github.com/fanhao375/Microduck-kissqy/tree/bdf494ab3fd74898b5159419fbffe87113b4097c
- github.com/fanhao375/microduck-replica/blob/e20877b8a099e8d669ef14e7f22275a946625f55/docs/软件更新与独立设备状态说明-20261029.md
- github.com/fanhao375/microduck-replica/releases/tag/microduck-software-v2026.10.30
- github.com/fanhao375/microduck-replica/blob/e20877b8a099e8d669ef14e7f22275a946625f55/docs/仅接IMU的独立诊断与软件更新-20261030.md
- github.com/fanhao375/microduck-replica/blob/2ba8e5d8ae4a4cf42f6284baf5dd817b412c4a5d/software/studio/deploy/native_update.py
- github.com/fanhao375/microduck-replica/blob/2ba8e5d8ae4a4cf42f6284baf5dd817b412c4a5d/software/studio/studio/startup_status.py
- github.com/fanhao375/microduck-replica/blob/e20877b8a099e8d669ef14e7f22275a946625f55/docs/superpowers/verification/2026-10-30-independent-imu-software.md
- github.com/fanhao375/Microduck-kissqy/tree/931ce978f2efb27c157b7a583ee402793131a0d2
- github.com/fanhao375/microduck-replica/releases/tag/microduck-software-v2026.10.3101
- github.com/fanhao375/microduck-replica/releases/tag/microduck-software-v2026.10.31
- github.com/fanhao375/microduck-replica/releases/download/microduck-software-v2026.10.3101/runtime-provenance.json
- github.com/fanhao375/microduck-replica/releases/download/microduck-software-v2026.10.3101/2026.10.3101.software-update.tar.sha256
- github.com/fanhao375/microduck-replica/blob/3952471a8394c8b720817d2160ffd95ce5a54456/software/studio/web/model/model.json
- github.com/fanhao375/microduck-replica/blob/3952471a8394c8b720817d2160ffd95ce5a54456/software/studio/web/duck3d.js
- github.com/fanhao375/microduck-replica/releases/tag/microduck-software-v2026.11.4
- github.com/fanhao375/microduck-replica/releases/tag/microduck-replica-image-20261104
- github.com/fanhao375/microduck-replica/blob/f215b658a4f24b669cf664b6381a559c61472009/docs/更新说明-20261104.md
- github.com/fanhao375/microduck-replica/blob/f215b658a4f24b669cf664b6381a559c61472009/docs/native-update-20261104.md
- github.com/fanhao375/microduck-replica/blob/f215b658a4f24b669cf664b6381a559c61472009/software/studio/studio/imu.py
- github.com/fanhao375/microduck-replica/blob/f215b658a4f24b669cf664b6381a559c61472009/software/image/overlay/usr/local/sbin/microduck-netcheck
- github.com/fanhao375/microduck-replica/releases/download/microduck-software-v2026.11.4/runtime-provenance.json
- github.com/fanhao375/microduck-replica/releases/download/microduck-software-v2026.11.4/SHA256SUMS.txt
- github.com/fanhao375/microduck-replica/releases/latest
- github.com/fanhao375/microduck-replica/blob/11a7b64aa7f89ab38e9e96c8e39968f25d15d48b/docs/官方更新跟踪.md
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261104/validation-report.json
- github.com/fanhao375/microduck-replica/releases/tag/microduck-replica-image-zero3w-20261112-rc4
- github.com/fanhao375/microduck-replica/blob/cbf06567c136c49c36babbd5fbd069db4979e1bc/software/studio/studio/communication.py
- github.com/fanhao375/microduck-replica/blob/cbf06567c136c49c36babbd5fbd069db4979e1bc/software/image/烧录和第一次使用.md
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-zero3w-20261112-rc4/microduck-replica-zero3w-20261112-rc4.img.xz.sha256
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-zero3w-20261112-rc4/delivered-image-verification.json
- github.com/fanhao375/microduck-replica/releases/tag/microduck-replica-image-20261110rc1
- github.com/fanhao375/microduck-replica/blob/3c187f1fb88980c2499e9e64506a2249e7ed69bb/software/studio/studio/imu.py
- github.com/fanhao375/Microduck-kissqy/commit/56046c5aa10be4de12d4389ae0463e4f129df940
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261110rc1/microduck-replica-20261110rc1-manifest.txt
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261110rc1/microduck-replica-20261110rc1.img.xz.sha256
- github.com/fanhao375/microduck-replica/releases/download/microduck-replica-image-20261110rc1/delivered-image-verification.json
- github.com/fanhao375/microduck-replica-cad/blob/2e40221b398e81428d02bf6d1399275d18436a63/README.md
- github.com/fanhao375/microduck-replica-cad/blob/2e40221b398e81428d02bf6d1399275d18436a63/BOM/装配BOM-机械行者Robo-2026-11-02-带采购链接.xlsx
- github.com/fanhao375/microduck-replica-cad/blob/2e40221b398e81428d02bf6d1399275d18436a63/打印/microduck-飞特版-BambuStudio2026-11-02.3mf
- github.com/fanhao375/microduck-replica-cad/blob/2e40221b398e81428d02bf6d1399275d18436a63/README.md#声明与许可
Next useful guides
MicroDuck DIY tutorials: choose your build route
FanGe XL330 / KISS HD1910 / fanhao375 HD1910 / Open Duck Mini v2 / OpenMicroDuck. Choose a complete build route.
OpenMicroDuck HD1910 Policies: Slots & Compatibility
Review OpenMicroDuck’s five HD1910 ONNX files, walk/stand slots, missing actions and runtime assumptions before choosing a policy for a DIY robot.
MicroDuck Build Log Template: Parts, Tests & Results
Document a MicroDuck build with a reusable log covering source revisions, parts, assembly photos, first checks, failures and results.