Give each stage a clear record.
Keep the design revision, what you changed, and what you observed together. Readers need the unsuccessful checks as much as the final result.
| STAGE | RECORD |
|---|---|
| Preparation | Source design, parts list and unresolved questions |
| Assembly | Original photos, component references and changes |
| First checks | Conditions, observations and issues |
| Result | What worked, what is unfinished, and the next step |
One project, a series of useful notes.
Connect the log to your project page. Give each substantial procedure its own guide, and keep the discussion attached to the original note.
Copy a record for one build session.
Keep this small enough to fill in immediately after a session. An observation such as “the connector did not fit” is useful when the connector reference and design revision are included.
Session date and goal:
Design URL and full revision:
Parts used (exact references):
What changed since the previous session:
Photos and what each one shows:
Test conditions and procedure:
Expected result:
Observed result or measurement (with units):
Failure / unresolved question:
What has not been tested:
Next single action:Connect later sessions with a link to the previous one. Mark an inferred explanation as a hypothesis until a repeatable check supports it.
What would you like to understand next?
Keep the source, your environment and your observations together.
Before you continue
What makes a build log useful to another maker?
Record the design revision, exact parts, commands, expected result and actual observations. Keep planning, simulation and physical tests separate.
Applies to: MicroDuck DIY · Open Duck Mini v2. Keep the model, image, software and driver versions together. The dated sections below retain their original verification limits.
Source checked:
Sources and review (1)
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.
Open Duck Mini v2 Parts Plan: Components and Budget Example
Use a filled six-component Open Duck Mini v2 parts plan, author-listed EUR prices, printing quantities and a checklist for the remaining costs.
MicroDuck troubleshooting: updates, pairing and policies
MicroDuck 0.20.1: check access before recovery. Wi-Fi SSH stays a local decision. Check daemon/API versions and Setup Code before treating a refused connection as an update failure.
