Example 1: Rotary RFQ arithmetic
45 ÷ 1.4 ≈ 32.1 Nm/kg; 45 × 2.2 = 99 Nm peak request. The calculator reproduces these numbers. Obtain speed, peak duration, cooling and impact evidence before selecting a sample.
Calculate output per mass and peak demand for humanoid robot actuators, then prepare a supplier RFQ worksheet.
Result
This tool calculates continuous output per actuator mass and a peak output request. The arithmetic does not establish whether a specific actuator fits your robot.
Candidate lane from selected inputs
Awaiting inputs
Selecting actuators for humanoid robots means matching motor, transmission, feedback, drive and thermal design to the joint duty. Compare joint mechanical impedance, continuous torque limits and dynamic impact tolerance alongside peak output. McKinsey estimates actuators at 40%–60% of hardware BOM [S10]; this is an industry estimate, not a platform quote. Compare complete installed systems, not isolated peak torque headlines. For the broader sourcing sequence, see the humanoid actuator procurement guide.
Conceptual layout of one possible rotary module with dual feedback, cable routing and a holding brake. Components and specifications vary by design; this is not a manufacturer cross-section.
Motor-side and load-side feedback can improve positioning through a compliant transmission [S6]. Select sensing, update rates and controller tuning from the actual error budget. Dual encoders do not remove mechanical backlash.
Motor and load feedback serve different control roles [S6]. This conceptual cascade has no fixed bandwidth: sampling rate, tuning and achievable response depend on the drive and mechanical system.
Clear application boundaries prevent costly engineering mismatches between humanoid dynamics and conventional industrial automation.
The distribution of actuators across a humanoid robot depends on joint mechanical impedance, dynamic impact velocity, and spatial packaging constraints.
Candidate topologies by joint duty, not a standard body-wide specification. Derive loads from your robot model; no common torque or mass range is established here.
Rotary or Remote Transmission
Rotary or Linkage Drive
High-Load Rotary or Linear Linkage
RFQ requirements worksheet, not a standard humanoid specification. N/A means no comparable verified value is available here. Derive loads, speed and axis count from your robot model and motion profiles.
| Joint Zone | DoF | Peak Torque/Force | Continuous Output | Max Velocity | Candidate Topologies | Dominant Mechanical Hazard |
|---|---|---|---|---|---|---|
| Hip | Define from kinematic model | N/A: derive from trajectory | N/A: derive from duty cycle | N/A: derive from motion profile | Rotary or linkage-driven | Body mass, payload, posture and gait dynamics; Coupled axis loads and impact spectrum |
| Knee | Define from kinematic model | N/A: derive from trajectory | N/A: derive from duty cycle | N/A: derive from motion profile | Rotary or linear linkage | Link inertia, contact forces and motion trajectory; Stroke/speed extremes and repeated impacts |
| Ankle | Define from kinematic model | N/A: derive from trajectory | N/A: derive from duty cycle | N/A: derive from motion profile | Compact rotary or push-pull linkage | Ground contact, balance and moment-arm map; Side loads, singularities and distal mass |
| Torso | Define from kinematic model | N/A: derive from trajectory | N/A: derive from duty cycle | N/A: derive from motion profile | Rotary with holding strategy | Upper-body mass and acceleration; Power-loss load path and cable twist |
| Shoulder | Define from kinematic model | N/A: derive from trajectory | N/A: derive from duty cycle | N/A: derive from motion profile | Rotary or remote transmission | Payload reach plus arm self-weight; Gravity holding and brake sizing |
| Elbow | Define from kinematic model | N/A: derive from trajectory | N/A: derive from duty cycle | N/A: derive from motion profile | Rotary, cable or linkage | Forearm inertia and payload; Harness motion and thermal holding |
| Wrist | Define from kinematic model | N/A: derive from trajectory | N/A: derive from duty cycle | N/A: derive from motion profile | Compact rotary or remote drive | Tool inertia and positioning task; Mass, stiffness and angular accuracy |
| Hand / fingers | Define from kinematic model | N/A: derive from trajectory | N/A: derive from duty cycle | N/A: derive from motion profile | Miniature rotary or linear | Contact force and tendon routing; Friction, fatigue and pinch-force mapping |
The preflight gives a candidate lane from your selections, not a verified fit. This table explains when each lane suits a program, key specifications, what evidence to request, and where trade-offs appear during prototype builds.
| Actuator lane | Specification Boundary | Best fit | Evidence to request | Procurement caution |
|---|---|---|---|---|
| Integrated rotary joint module | Model-specific; request torque-speed and mass data | Compact rotary joints needing a packaged motor, transmission and feedback | Continuous and peak output at speed, peak duration, thermal mounting, backlash and brake behavior | Integrated does not mean strain-wave or specified lost motion. Compare the whole module under identical test conditions. |
| QDD or low-ratio rotary module | Ratio and backdrive torque: verify per model | Joints where low reflected inertia and backdrive torque are priorities | Motor inertia, measured backdrive torque, current-to-output torque calibration and impact tests | A lower ratio reduces reflected motor inertia for the same rotor, but does not guarantee safe impacts or accurate current-based output torque. |
| Frameless torque motor stack | Motor-only ratings; not directly comparable to module density | Teams integrating their own housing, bearings, transmission, cooling and controls | Winding data, motor torque constant, inertia, magnet temperature limits and mechanical tolerances | Include bearings, reducer, brake, electronics and cooling in the finished joint mass and integration cost. |
| Linear actuator or screw-driven linkage | Force-speed-stroke curve: verify per model | Mechanisms designed around force, stroke and linkage geometry | Continuous/peak force, stroke, speed, side-load limits, friction, life and changing perpendicular moment arm | Joint torque is force × perpendicular moment arm. Derive the moment arm from actual geometry over the full motion range. |
Qualitative comparison with explicit unknowns. No cross-vendor torque-density, efficiency or overload dataset is established here. The strain-wave principle is documented in [S5]; the QDD study [S4] is a single exoskeleton, not a humanoid-wide benchmark. For every rotary topology, add transmission inertia to the reflected rotor term before comparing complete joints.
| Technology | Ratio / Lead | Output per Mass | Backlash | Reflected Inertia | Backdrivability | Shock Overload | Candidate Use / Limits |
|---|---|---|---|---|---|---|---|
| Low-ratio planetary / QDD | Model-specific low reduction | N/A: comparable module tests unavailable | Measure on selected assembly | Jmotor × N² (rotor term only) | Measure friction and backdrive torque | N/A: request repeated-impact evidence | Candidate for force-controlled joints; validate load case |
| Strain-wave | Model-specific high reduction | N/A: comparable module tests unavailable | Zero-backlash gearing; elastic deflection remains [S5] | Jmotor × N² (rotor term only) | Depends on ratio, friction, preload and control | N/A: check allowable transient torque and life | Candidate for compact positioning; validate compliance |
| Cycloidal | Model-specific | N/A: comparable module tests unavailable | Model, preload and wear dependent | Jmotor × N² (rotor term only) | Requires measurement; no universal category value | N/A: no generic overload percentage | Candidate where load capacity and stiffness suit duty |
| Roller screw or ball screw | Lead in mm/revolution, not rotary ratio | N/A: force density is not torque density | Axial play and stiffness depend on preload | Requires screw and linkage coordinate conversion | Depends on lead, friction, preload and gearing | N/A: check contact life and shock loads | Candidate for linkage-driven joints; validate full stroke |
Arithmetic comparison for the same assumed rotor: its output-referred inertia scales with the square of reduction ratio N. Friction, gearing inertia and impact response require separate measurements.
A proximal linear drive can move mass away from the foot, but the benefit depends on the complete linkage. Compute torque using the actual perpendicular moment arm at every pose; do not assume a universal sine relationship.
Converting axial push-pull actuator thrust into rotary joint torque depends on changing perpendicular moment arm geometry r⊥(θ) across the entire joint travel range.
Continuous and peak ratings depend on the winding, ambient, mounting and cooling assumptions [S7]. No universal peak duration or cooling uplift is established here. Validate the final enclosed installation.
| Cooling Topology | Torque Retention | Peak Duration | Thermal Time Constant | Mass Penalty | Sealing | Engineering Reality |
|---|---|---|---|---|---|---|
| Passive enclosed limb | N/A: test in final installation | N/A: supplier current/time/temperature limit | N/A: measure winding and housing response | Include housing and mounting | N/A: enclosure-level qualification | Do not assume open-air catalog ratings apply. Record ambient, mounting, starting temperature and steady-state winding temperature [S7]. |
| Conductive chassis heat path | N/A: test in final installation | N/A: supplier current/time/temperature limit | N/A: measure winding and housing response | Include pads and structural changes | N/A: enclosure-level qualification | Validate contact resistance, chassis heat rejection and neighboring heat sources; no universal torque uplift follows from adding a heat sink [S7]. |
| Forced air | N/A: test in final installation | N/A: supplier current/time/temperature limit | N/A: measure winding and housing response | Include blower, filters and ducting | N/A: enclosure-level qualification | Measure airflow, noise and blocked-filter behavior. Ventilation and sealing require enclosure-specific validation. |
| Liquid jacket | N/A: test in final installation | N/A: supplier current/time/temperature limit | N/A: measure winding and housing response | Include coolant, hoses, pump and radiator | N/A: enclosure-level qualification | Verify coolant flow/temperature, leak containment, pump-fault behavior and full-system mass. Liquid cooling is not instantaneous or unlimited. |
Copper loss grows with current squared at a fixed resistance. Peak duration also depends on starting temperature, speed, repeated duty, drive limits and heat rejection; no universal time-to-trip curve applies.
Conceptual positive torque-speed quadrant, not a measured product curve. Request continuous and peak envelopes at your bus voltage, temperature and cooling conditions, plus duration and repetition limits.
Budget worst-case command and feedback traffic, synchronization, device processing and fault behavior. A protocol name or axis count alone cannot establish a control-loop rate [S9].
| Protocol | Bus Cycle Rate | Jitter | Node Budget | Harness Wiring | Bandwidth Evaluation | System Trade-off |
|---|---|---|---|---|---|---|
| EtherCAT | N/A: budget and measure end-to-end | DC clock accuracy: <1 µs; not end-to-end jitter [S9] | N/A: depends on payload, topology and cycle | Ethernet physical layer; specify cables and connectors | Budget command/feedback bytes and device processing per cycle | Synchronization can help coordinated axes; requires compatible drives and a real-time master. |
| CAN FD | N/A: calculate from message schedule | Arbitration and implementation dependent | N/A: no universal node cutoff | Shared differential bus; verify termination and stub lengths | Include arbitration/data rates, frame overhead, priorities and fault traffic | Segment buses if the measured schedule misses deadlines; axis count alone cannot prove saturation. |
| RS-485 with an application protocol | N/A: protocol and implementation dependent | Polling, scheduling and controller dependent | N/A: transceiver and loading dependent | Differential physical layer; topology must suit protocol | RS-485 alone specifies no control loop rate; Modbus is one possible protocol | Evaluate the selected protocol against the required deadlines rather than inferring suitability from the physical layer. |
Assumed values illustrate reproducible arithmetic, not tested robots or product recommendations. Each example identifies missing evidence and a next action. Examples 1 and 5 can be reproduced in the calculator.
45 ÷ 1.4 ≈ 32.1 Nm/kg; 45 × 2.2 = 99 Nm peak request. The calculator reproduces these numbers. Obtain speed, peak duration, cooling and impact evidence before selecting a sample.
Add arm/link self-weight, acceleration and all relevant loads. 36.8 Nm is a lower-bound component of static torque, not a final actuator rating. Check brake engagement time and dynamic stopping separately [S8].
The moment arm changes with pose. Map force, stroke, speed, friction and side-load through the full motion range. The 175 Nm calculation does not prove continuous capacity or impact tolerance.
The rotor contribution differs by 100× under this fixed-rotor assumption. Different motors, friction, compliance and controls can change the system comparison. This calculation does not predict gear fracture or safe contact.
8 ÷ 0.1 = 80 N/kg; 8 × 2.5 = 20 N peak axial request. Determine tendon routing losses, lever arms, stroke and speed before translating to fingertip force or claiming a pinch capability.

Published September 24, 2026; reviewed November 9, 2026. Published by Humanoid Robot Actuators. Next source review: May 9, 2027, or earlier if supplier specifications change. [S1]–[S10] refer to the source cards below. Diagrams are conceptual; worked numbers are hypothetical unless tied to a source. The sources do not replace supplier test data, but they explain which actuator claims should be verified before samples are approved. Where public data is proprietary, limits are explicitly flagged. For mass-normalized design context, read the humanoid actuator power-density guide.
Published April 17, 2024; checked November 9, 2026
Confirms the transition to electric Atlas. It does not provide actuator torque classes or supplier module specifications.
Open sourcePublication date not stated; checked November 9, 2026
Describes the Optimus program. This page does not disclose actuator counts, screw types, torque ratings, or thermal limits.
Open sourcePublication date not stated; checked November 9, 2026
States a design target of 90%+ actuator energy efficiency. This company claim has no published operating point or independent validation on the page.
Open sourcePublished April 1, 2020; checked November 9, 2026
Reports 17.5 Nm nominal torque, 0.4 Nm backdrive torque and 62.4 Hz bandwidth for one tested hip exoskeleton. These measurements are not specifications for humanoid leg joints.
Open sourcePublication date not stated; checked November 9, 2026
Explains strain-wave gearing and its zero-backlash characteristic. This does not establish zero elastic deflection, arbitrary impact tolerance, or complete actuator torque density.
Open sourceUpdated August 29, 2024; checked November 9, 2026
Explains motor-side and load-side feedback and controller tuning. Load feedback can reduce positioning errors caused by compliance and backlash; it does not remove those mechanical properties.
Open sourceCatalog listed October 7, 2025; checked November 9, 2026
Lists model-specific continuous and peak stall ratings and links the selection guide. Request its winding, ambient, mounting and heat-sink conditions; a motor-only rating does not establish capacity in a sealed humanoid limb.
Open sourceIssue November 2022, sections 5.2.5 and 6.5; checked November 9, 2026
Specifies switching times and separate static/dynamic brake sizing. Engagement takes time; a holding brake alone does not establish safe stopping or prevent robot collapse.
Open sourcePublication date not stated; checked November 9, 2026
Describes sub-microsecond distributed-clock accuracy within Beckhoff XFC. This vendor capability is not a measured humanoid network result. Clock synchronization accuracy is not the same as total sensor-to-actuator latency or a guaranteed robot control bandwidth.
Open sourcePublished April 17, 2026; checked November 9, 2026
Estimates actuators at 40%–60% of hardware BOM. This industry analysis is not an audited platform BOM or a supplier quotation; scope and integration level affect the share.
Open sourceMcKinsey’s April 17, 2026 analysis [S10] estimates actuators at 40%–60% of humanoid hardware BOM. This is an industry estimate, not a universal per-platform figure; BOM boundaries and robot architectures vary.
Read the McKinsey analysismaxon’s dual-loop explanation [S6] separates motor and load feedback. Use it to plan output error measurements and controller tuning; do not infer a universal encoder resolution or bus rate.
Read the dual-loop explanationLower transmission ratios can reduce reflected rotor inertia and improve backdrivability, while reducing output torque for a given motor. The QDD study [S4] demonstrates one low-ratio design; impact response still depends on the complete joint, friction, compliance, controller, and load case.
Read the QDD studyThe checker screens the initial architecture path. It cannot certify final actuator life, impact tolerance, sealing, controller stability, or robot-level safety. Those require sample bench testing and supplier-provided test data.
| Risk Mode | Root Cause | Evidence Needed | Mitigation Action |
|---|---|---|---|
| Thermal derating | Catalog conditions differ from enclosed installation. | Torque-speed region, mounting, ambient and measured winding temperature [S7] | Test the intended duty cycle to thermal equilibrium; respect supplier current/time limits. |
| Impact overload | Load spectrum, inertia, compliance and controller response interact. | Allowable transient loads, fatigue and relevant repeated-impact tests | Validate the full joint. Neither low ratio nor a transmission name establishes impact safety. |
| Position error and oscillation | Backlash, compliance, sensing and tuning affect output motion. | Loaded output accuracy, hysteresis and closed-loop stability [S6] | Select feedback and tune under actual loads; dual encoders cannot mechanically remove backlash. |
| Communication deadlines | Traffic schedule and device latency exceed control timing budget. | Worst-case bus utilization, jitter and end-to-end timing [S9] | Measure under maximum traffic and faults; adjust payload, cycle or bus segmentation. |
| Power-loss motion | Brake torque, engagement delay or stopping energy is unsuitable. | Brake switching times, static/dynamic ratings and safety analysis [S8] | Verify a controlled stop and holding strategy; a holding brake is not a robot-level safety guarantee. |
| Magnet overheating or supply change | Operating temperature, demagnetizing field or material substitutions exceed design assumptions. | Supplier magnet curves, rotor thermal estimate and change-control records | Confirm temperature/current limits with the motor supplier. Winding temperature is not magnet temperature; Curie temperature is not an operating limit. |
| Integration cost and scene mismatch | A motor-only price or mass omits the finished joint and test effort. | BOM boundary, NRE, electronics, cooling, tooling, validation and spare-part terms | Compare complete installed cost at stated quantity; sample first and postpone custom interfaces until baseline evidence is accepted. |
Extract joint torque-speed and angular acceleration profiles from full-body simulation (MuJoCo/Isaac Gym).
Verify continuous RMS torque against thermal dissipation; confirm peak multiplier and bus voltage margin.
Select feedback from the output error budget, measure communication deadlines, and validate stopping and power-loss holding.
Benchmark catalog samples for thermal rise, backdrive friction, impact fatigue, and lost-motion hysteresis.
Root Cause: Repeated contact or fall loads exceeding the selected transmission limits.
Mitigation: Obtain transient torque and fatigue limits; test the full joint against the load spectrum. Low ratio alone does not establish impact safety.
Root Cause: Insufficient heat rejection or operation beyond winding, magnet or drive temperature limits.
Mitigation: Measure the installed thermal path and sensor response; set protection from the selected components, including sensor lag.
Root Cause: Worst-case scheduling, arbitration, retransmission or processing delays exceed the control deadline.
Mitigation: Measure end-to-end latency under fault traffic; adjust schedule, processing or segmentation. Clock accuracy is not total latency.
Root Cause: Mechanical engagement delay and insufficient static or dynamic brake capacity under the actual load [S8].
Mitigation: Size stopping energy, load torque and engagement time with the supplier; test the power-loss load path. A holding brake alone does not guarantee a safe robot stop.
A useful humanoid actuator RFQ should require the supplier to demonstrate fit against the joint duty, not only against a catalog model name.
joint zone, continuous and peak torque or force, output speed or stroke, duty cycle, impact or holding events, and ambient operating temperature
outer diameter, axial length, mass target, flange mounting, output shaft or hollow bore for wiring, cable exit orientation, and drawing revision
bus voltage, controller location, required communication schedule, feedback interfaces, brake supply and switching requirements, fault behavior, and harness length
Selection, controls, evidence and sample-review questions. Source IDs refer to the evidence cards above.
Common candidates include packaged rotary modules, low-ratio QDD drives, frameless motor stacks and linear screw/linkage systems. These categories overlap: QDD describes a low-ratio drive approach, frameless describes motor packaging, and integrated rotary actuators package a motor, transmission and feedback. Reducer type, encoder count and drive integration are model-specific. Select against measured joint duty rather than body location alone.
Start with a kinematic joint map, derive torque-speed or force-stroke trajectories, and define envelope, mass and communication constraints. Use this preflight worksheet to summarize continuous output per mass and peak requests, then compare candidate supplier hardware under identical thermal and mounting conditions.
For an ideal rigid rotary reduction N, the rotor contribution referred to output is Jmotor × N². This is one system term. It does not alone predict tooth fracture, backdrive torque or safe contact; compare the full motor, transmission and control design.
No. Motor-side and load-side feedback can improve load positioning and compensate some transmission errors when properly tuned [S6]. Mechanical backlash, elastic deflection, friction and wear remain.
No universal bus choice follows from joint count. Budget command and feedback traffic, device processing, synchronization and worst-case latency. EtherCAT distributed clocks support synchronized acquisition [S9]; CAN FD suitability depends on its actual message schedule.
There is no universal time. Obtain the supplier current-time-temperature limits, starting temperature, speed, bus voltage and cooling assumptions. Continuous capacity must be validated in the final installation [S7].
Compare model-specific force-speed curves, lead, stroke, stiffness, preload, lubrication, backdrivability, life and cost under the same load spectrum. No generic load or life multiplier is established by the sources on this page.
Request continuous output at speed with ambient, mounting and thermal conditions. Then confirm peak output duration and repeatability. Linear paths also need stroke, side-load and linkage geometry.
Consider low reduction when measured backdrive torque and reflected inertia matter. A published exoskeleton demonstrates this approach [S4], but does not validate humanoid impacts. Check motor size, current, heat and output torque accuracy.
Consider a linear path when the joint geometry can accommodate stroke and linkage forces. Compute the changing perpendicular moment arm and check singularities, side loads, bearing reactions and full-range speed.
McKinsey estimates 40%–60% of hardware BOM in its April 17, 2026 analysis [S10]. Treat this as an industry estimate; the platform, accounting scope, quantity and degree of integration determine the actual share.
Include joint zone, continuous and peak output, peak duration, speed or stroke, duty cycle, mass and envelope, output interface, voltage, protocol, encoder and brake needs, harness routing, drawing revision, quantity and validation date.
Joint loads, speed, packaging and feedback needs differ. Standardize only after comparing each joint duty; this page does not prescribe a universal number of frame sizes or torque classes.
Peak versus continuous values, motor-only versus complete-module mass, and different thermal mounting or speed conditions are not directly comparable. Normalize those boundaries before ranking suppliers.
Use a catalog sample while validating curves, temperature, output accuracy, brake behavior and control stability. Custom flanges and connectors add cost and lead time before these uncertainties are resolved.
Request output envelopes, repeated-load and impact tests relevant to the intended gait, transmission life, thermal conditions, sealing, cable routing and power-loss behavior. Architecture alone is not evidence of walking suitability.
Mark missing values as unknown, request test conditions and agree a sample test plan. Compare another supplier if the evidence remains insufficient; avoid freezing a design around an unverified catalog claim.
Use the result as an RFQ worksheet and send the joint map, motion profile, envelope, interfaces and duty cycle for sample review. Thermal margin, fatigue life and robot safety require additional engineering and tests.
No. Obtain the specific platform command rate, latency budget, feedback format and fault behavior. An AI capability demonstration does not establish actuator bandwidth or hardware specifications.
No. A spring-applied, electrically released brake takes time to engage. Check holding torque, dynamic braking energy, switching time and control sequencing for the selected brake [S8]. Robot stability and stopping safety require a system-level assessment.
Request the supplier magnet grade, temperature-dependent demagnetization curves and permitted current/temperature envelope. Estimate rotor temperature separately from winding temperature; do not use a generic safety factor or Curie temperature as a working limit.
Include the preflight values, joint map, envelope drawing, and duty-cycle assumptions. A practical early-program sequence is a catalog sample, evidence review, then custom interface decisions.
Inquiry Email
Subject: Humanoid robot actuator RFQ preflight and sample review
Include the preflight output, joint map, interface drawing, duty cycle, and target sample date.
Instant Chat
WhatsApp Engineering Support
Best for quick model-fit questions before a full RFQ email.