Skip to content
MicroDuckROBOT COMMUNITY
Contribute ↗
FIND THE NEXT USEFUL NOTE

Search the workbench.

Guides, source notes, projects and public discussions.

29 results
Discussions

편집부 질문: 0.15.0의 패드 재연결과 상태 값은 어떻게 확인했나요?

편집부가 공식 변경 기록을 읽고 시작한 토론입니다. 실제 사용자 시험이나 성공 후기를 가장하지 않습니다. 0.15.0은 패드 연결이 끊길 때 남은 길게 누르기 상태를 지우고, robot.state에 관절 속도와 전류를 추가했습니다. 시험했다면 패드 모델, 연결이 끊긴 시간, 데몬 버전, 다시 연결했을 때의 결과를 구분해 알려주세요. 개발자는 새 배열이 없는 예전 프레임을 0으로 처리하지 않았는지도 확인하면 좋습니다. 로그의 계정, 기기 식별자와 토큰을 가리고, 실물 로봇과 시뮬레이션을 분리해 적어 주세요. 공식 릴리스: https://github.com/pollen-robotics/microduck/releases/tag/daemon-v0.15.0 한국어 점검표: https://microduckrobot.org/ko/news/daemon-0-15-0/

Discussions

編集部から：0.15.0 の central 表示で接続先を確認できましたか？

公式リリースを読んだ編集部からの問いです。実機で確認した結果を作り出した投稿ではありません。robotctl health の central 行と robotctl account status を比べた時、未ログイン、登録先アカウントの相違、heartbeat の遅延、再試行のどれが見えましたか。まず version と update status を保存し、更新前後を分けてください。質問には環境、版、最初に違った行を添え、アカウント名、端末 ID、トークンは伏せてください。実機と duck-sim の結果も区別しましょう。公式発表：https://github.com/pollen-robotics/microduck/releases/tag/daemon-v0.15.0 日本語の確認手順：https://microduckrobot.org/ja/news/daemon-0-15-0/

Discussions

编辑发起：0.15.0 更新前，四项只读检查有没有异常？

这是编辑组依据官方 0.15.0 发布记录发起的资料讨论，不是已经完成实机更新的网友反馈。如果手边有机器人或开发板，先保存 robotctl version、update status、update check daemon、health --check。最值得讨论的是：正在运行的版本是否与已安装版本一致？更新源上次有效回应是什么时候？health 的 central 行显示未登录、重试、被拒绝，还是登记在另一账号下？请写明设备类型、软件版本和异常行，公开前遮掉账号名、序列号及令牌。更新过的读者可补充脱敏 update log，并标明实机或仿真。官方发布：https://github.com/pollen-robotics/microduck/releases/tag/daemon-v0.15.0 中文核查：https://microduckrobot.org/zh/news/daemon-0-15-0/

Discussions

Editorial prompt: what does daemon 0.15.0 health show before an update?

Editorial source check, not a member test. The official 0.15.0 release adds a last-answer time for the update source and a central registration line in robotctl health. If you have a robot or dev board, compare robotctl version, update status, update check daemon and health --check before changing software. Which line was unclear, and did the account on the board match the one listing the robot? Share the command, version and a redacted excerpt, not account names, serials or tokens. If you updated, include the update log and what you observed afterward; distinguish a real robot from daemon simulation. Official release: https://github.com/pollen-robotics/microduck/releases/tag/daemon-v0.15.0 Site walkthrough: https://microduckrobot.org/news/daemon-0-15-0/

Discussions

Editorial source check: which DIY duck build files still need verification?

Editorial starting point. Open Duck Mini v2 has a published bill of materials, printable parts and assembly notes; the separate MicroDuck replica effort has an earlier public progress record. If you have built either project, please name the design revision and identify one specific gap you verified: part count, fit, servo direction, wiring, calibration or first-walk procedure. Link original files and your own observation separately. A photograph of printed parts is useful evidence of printing, but it is not proof of a powered, walking robot. Original Open Duck Mini project: https://github.com/apirrone/Open_Duck_Mini Build route and source notes: https://microduckrobot.org/diy/open-duck-mini/

Discussions

편집부 질문: 정책을 바꾸기 전에 어떤 상태를 기록하나요?

편집부가 공식 robotctl 문서를 확인하고 시작한 토론입니다. 로봇에서 새 ONNX를 시험했다면 변경 전 version, health, policy list와 check를 저장했는지, 어떤 슬롯과 고정 리비전을 썼는지, 로봇을 어떻게 지지했는지 알려주세요. load 선택은 재부팅 뒤에도 남습니다. 시험 후에는 reset으로 공식 기본값을 복원하고 list와 health를 다시 확인해야 결과를 해석할 수 있습니다. 입력 61개와 행동 14개의 모양이 맞아도 동작 품질이나 실물 안전이 확인된 것은 아닙니다. 토큰과 개인 정보는 로그에서 지우고 공유해 주세요. 공식 문서：https://github.com/pollen-robotics/microduck/blob/e90389492bd4da42f60da343983e50cecd43b54b/docs/robot/cheatsheet.md 한국어 안내：https://microduckrobot.org/ko/guides/policy-library/

Discussions

編集部から：実機なしで robotd を動かした時、どこまで確認できましたか？

編集部による資料確認を出発点にした議論です。公式 duck-sim は MuJoCo の身体に実際のデーモンを接続します。実行した方は OS、microduck と microduck_rl のコミット、通常モードか boot か、status・health・realtime の結果、最初のエラーを共有してください。実時間率が落ちた時は台数やカメラ数も記録すると切り分けに役立ちます。シミュレーションの成功をモーターバスや Bluetooth の実機確認と混同しないよう、検証範囲も書き添えましょう。公式手順：https://github.com/pollen-robotics/microduck/blob/e90389492bd4da42f60da343983e50cecd43b54b/docs/robot/simulation.md 日本語ガイド：https://microduckrobot.org/ja/guides/daemon-simulation/

Discussions

编辑发起：第一次试用新策略，怎样留下可回退的记录？

编辑组核查了官方 robotctl 命令，想收集真实的测试记录和疑问。开始前保存 robotctl version、health、policy list 与 policy check；加载时记下槽位、模型来源、固定版本、文件哈希、支撑方式和预期动作；试完再运行 policy reset walk，并保存恢复后的 list 与 health。load 成功会跨重启保留，社区模型也不等于官方审核通过。若某一步的输出与你的理解不同，请只分享脱敏日志和实体测试条件，不要上传账号令牌。官方命令：https://github.com/pollen-robotics/microduck/blob/e90389492bd4da42f60da343983e50cecd43b54b/docs/robot/cheatsheet.md 中文步骤：https://microduckrobot.org/zh/guides/policy-library/

Discussions

编辑发起：Open Duck Mini v2 装配到哪一步最容易卡住？

这是编辑组根据原作者手册发起的资料讨论，不是网友已完成装配的经历。Open Duck Mini v2 与 Pollen Robotics 的 MicroDuck 是不同项目，零件和策略不能直接混用。若你正在制作，请说明卡在采购、打印、舵机编号、装配、接线、校准还是首次行走；贴出原始设计版本、具体零件型号、预期动作、实际现象和已经尝试的一项检查。公开照片前遮挡订单、地址和设备凭据。欢迎补充确实跑通的步骤，也欢迎指出原手册仍缺哪一页。原作者资料：https://github.com/apirrone/Open_Duck_Mini 本站八阶段路线：https://microduckrobot.org/zh/diy/open-duck-mini/

Discussions

Editorial prompt: what did duck-sim health reveal on your first run?

Editorial starting point · official source reviewed September 23, 2026. The new duck-sim route runs the real robotd loop against a MuJoCo body. If you tried it, which step did you reach: environment setup, window opening, standing, drive, or health check? Share your OS, both repository revisions, the first failing command, and the health or realtime output with private tokens removed. A result here describes daemon simulation; it does not validate the motor bus or physical balance. Official walkthrough: https://github.com/pollen-robotics/microduck/blob/e90389492bd4da42f60da343983e50cecd43b54b/docs/robot/simulation.md Site guide: https://microduckrobot.org/guides/daemon-simulation/