A robot actuator module is an integrated joint-level motion unit, not only a motor
Boundary used here: motor + torque path + feedback + defined power/control interface
This is an RFQ screening definition, not a formal standards term. Identify who owns torque generation, sensing, drive interface, thermal protection, brake behavior, and harness boundary.
Evidence: [Page method][S3 for the generic actuator term]
Robot safety standards changed materially in 2025
ISO 10218-1:2025 and ISO 10218-2:2025 replaced older industrial robot safety editions
Definition pages should not imply safety approval. The module definition can list safety-relevant interfaces, but final robot risk reduction must be validated at robot and cell level.
Evidence: [S1][S2]
The right definition depends on integration boundary, not marketing vocabulary
Six boundary elements are checked in the tool: motor, torque path, encoder, brake, drive, thermal sensing
If feedback or power/control ownership is missing, the item is better described as a motor, reducer, brake, encoder, or joint subassembly until evidence closes the gap.
Evidence: [Tool Formula][S3]
Continuous torque and thermal data matter more than peak-torque headline
The 3.5x ratio is an internal review prompt, not a universal acceptance limit
Peak torque can be valid for short events. Confirm peak duration, repetition, temperature rise, reducer life, brake heat, and encoder reliability against the actual operating profile; the checker does not collect duty cycle.
Evidence: [S4][S5]
Medical and human-collaborative contexts need explicit evidence boundaries
Collaborative operation and medical support are system-level risk contexts
ISO 10218 and ISO/TS 15066 address industrial robot systems; ISO 10218-1 explicitly excludes medical, healthcare, public-access service robots, and people-lifting uses. Define the applicable framework before reusing an industrial checklist.
Evidence: [S1][S6]