Why This Checklist Exists
Use this checklist to convert a vague request for actuator testing into measurable conditions that engineering, procurement, and incoming quality can all review before samples are paid for.
Define a humanoid actuator sample test plan before DVT, including operating cycle, measurement setup, thermal rise, backlash, noise, endurance, FCT, and report handoff.
Use this checklist to convert a vague request for actuator testing into measurable conditions that engineering, procurement, and incoming quality can all review before samples are paid for.
Checklist
The goal is to make acceptance measurable before the quote, PO, sample, or pilot gate creates pressure to accept incomplete proof.
| Area | Buyer Question | Define Before Review | Evidence / Output | Red Flag |
|---|---|---|---|---|
| Operating cycle | What does the actuator actually experience inside the robot? | Joint axis, motion range, speed profile, peak and continuous torque or force, duty cycle, ambient condition, stall event, and safety margin. | Duty-cycle table, torque-speed or force-stroke target, thermal boundary, and sample pass/fail limits. | Only a peak torque number is provided, with no time, temperature, or load-cycle context. |
| Mechanical boundary | Is the test measuring the assembled actuator or only one component? | Unit under test, output flange, shaft, bearing support, housing, preload, cable route, mounting stiffness, and whether the robot link is included. | Fixture drawing, boundary diagram, measurement location, and excluded components list. | Supplier reports reducer or motor data as if it proves the final joint module. |
| Performance sweep | Does the actuator meet useful torque-speed or force-stroke conditions? | Voltage window, current limit, controller mode, speed points, load points, dwell time, encoder source, and allowable derating. | Torque-speed curve, force-stroke curve, no-load current, efficiency notes, and current-limit record. | A single no-load speed or stall torque value is treated as full performance validation. |
| Thermal rise | Will heat change continuous output, backlash, noise, or electronics reliability? | Ambient temperature, cooling path, housing contact, allowed surface temperature, sensor location, duration, and post-test inspection. | Thermal-rise record, derating note, sensor placement, load profile, and pass/fail rule. | Thermal evidence is requested after samples are complete, forcing a late design change. |
| Backlash and lost motion | Is backlash measured at the same location and load condition the robot cares about? | Reversal load, preload, output measurement location, encoder topology, fixture stiffness, repeat count, and post-cycle limit. | Backlash method, lost-motion result, hysteresis note where relevant, and serial-level result. | A no-load reducer backlash claim is accepted for an assembled robot joint. |
| Noise, vibration, and feel | Could the actuator pass torque tests but fail user-visible quality expectations? | Speed points, load points, microphone or vibration location, threshold, lubrication state, and acceptable subjective observations. | Noise or vibration record, abnormal sound notes, run-in condition, and inspection after test. | Noise is reviewed only after the robot team has already integrated the sample. |
| Electronics and FCT | Are driver, encoder, brake, harness, and calibration responsibilities testable? | Voltage, protocol, brake control, firmware boundary, connector map, calibration revision, FCT fixture, and buyer-supplied parts. | FCT record, calibration note, firmware boundary, harness check, and fault-condition observations. | Mechanical sample approval is separated from electrical responsibility until late integration. |
| Endurance and post-test review | What changes after load cycling, run-in, or burn-in? | Cycle count, load case, temperature condition, speed, duty cycle, stop rule, inspection points, and post-test acceptance limits. | Load-cycle record, burn-in note, post-test backlash or torque check, wear observations, and issue log. | The sample is approved before anyone defines what must remain true after cycling. |
A credible test plan begins with the joint load case, not with the supplier catalog. Translate motion, load, temperature, and control limits into bench conditions.
Early samples may produce exploratory data. Sample acceptance needs a smaller set of fixed pass/fail limits that both sides can repeat.
Name the fixture, output point, encoder source, sensor locations, firmware revision, and excluded robot components before results are compared.
Every useful report should point to drawing revision, BOM revision, sample serial, fixture or setup, date, and open issues.
Gate Review
| Gate | Pass Signal | Fail Signal | Next Action |
|---|---|---|---|
| Before sample PO | The buyer and supplier agree which tests are required for sample acceptance and which are exploratory. | The PO only says "test report required" without method, boundary, or limit. | Attach a test matrix to the PO or quote notes before payment is released. |
| Before EVT bench test | Fixture, load profile, sensors, controller mode, and report format are frozen enough to repeat. | Engineering teams debate the setup after data is already collected. | Run a short setup confirmation before the full actuator test sequence. |
| Before DVT sign-off | Thermal, backlash, FCT, burn-in, and post-cycle criteria are tied to the real operating cycle. | The actuator meets a catalog value but fails a robot integration condition. | Update the acceptance matrix and repeat only the affected tests. |
| Before pilot release | Reports are tied to drawing revision, sample serial, fixture, issue closure, and incoming inspection needs. | A working sample cannot be converted into a repeatable pilot build record. | Move unresolved tests into the pilot readiness checklist with owners and dates. |
Proof Boundary
No. The useful plan is risk-based. A low-load wrist sample, a compact finger actuator, and a high-torque knee actuator should not carry the same test burden. The checklist helps both sides decide what is mandatory for the current gate.
Use bounded assumptions and mark them as provisional. Freeze an interim duty cycle for sample testing, then reopen the limits before DVT or pilot release when robot data improves.
Ownership depends on program maturity. The important part is that the fixture boundary, stiffness, sensors, calibration state, and revision are visible in the report so results can be repeated or challenged later.
Send the drawing baseline, joint role, performance target, and current gate. Mark unknowns clearly so the first review can separate feasible assumptions from missing acceptance data.
Inquiry Email
Include target torque/speed, quantity, and delivery location.
Application Engineer
+8618857971991
Talk directly about drawings, torque-speed targets, and RFQ data gaps.