Software and Motor Setup
Software and Motor Setup Record
Confirm the common pre-assembly software and Motor ID work is recorded before Module Kitting.
Completion Check
- RPU and Raspberry Pi image filenames, versions, release pairing, and checksums are recorded.
- The RPU image write completed without an unresolved error.
- The Raspberry Pi image write and media verification completed.
- Raspberry Pi Imager OS customization was not applied.
- The dashboard reports the RPU as reachable.
- The default dashboard password was changed.
- All 25 unique actuator stickers are present.
- Every actuator was programmed individually through the
LLsetup connection. - Every programmed Motor ID was read back and recorded.
- No duplicate, missing, failed, alarmed, or unidentified actuator remains.
- Boards, battery, setup cables, and actuators are powered down before Module Kitting.
TBC release dependencies still apply
The common setup cannot pass until public matched image downloads, checksums, the exact LL connection, and approved board and actuator power hardware are released. Recording an unknown value does not turn it into a pass.
How is this guide?