Listen to this chapter
Wired for Motion

System Architecture and Engineering Foundations

Chapter 14

Why Humanoid Robotics Needs a Mission Profile

Industrial humanoid robot beside a technical DHMP mission-profile infographic.
32 min readVersion 1.0
Humanoid robotics has entered the phase in which an impressive demonstration is no longer enough. Industrial users must know how long a robot can work, which joint becomes thermally limiting, how much energy one productive operation consumes, which semiconductor devices see the highest current and temperature cycling, and how changes in mass, payload, compute, or cooling propagate through the complete system. Today, those questions are usually answered against private and incompatible workloads.

This chapter argues that humanoid robotics needs a shared mission profile: a time-resolved, manufacturer-neutral workload that makes energy, thermal, runtime, actuator, battery, compute, and semiconductor results reproducible. The proposed DXresearch Humanoid Mission Profile, or DHMP, begins with a five-minute reference family containing 300 one-second records. It does not declare a finished international standard. It provides an open engineering proposition that can be tested, criticized, measured, and eventually transferred into consensus standardization.

The central thesis is simple: without a common workload, published runtime, efficiency, thermal performance, and component value remain fundamentally incomparable.

The Missing Measurement Language

A humanoid robot is not a single machine load. It is a moving network of actuators, inverters, sensors, processors, communications links, safety functions, converters, and thermal paths. During one minute it may stand quietly while camera pipelines and world models consume most of the electrical power. During the next it may accelerate its full body, carry a payload, arrest a fall, or hold an awkward posture that produces little mechanical motion but substantial RMS current and copper loss.

Manufacturers commonly publish mass, battery capacity, payload, degrees of freedom, joint torque, speed, and nominal operating time. These specifications are useful, but their engineering meaning is incomplete unless the associated workload and boundary conditions are disclosed. Four hours of “typical use” cannot be compared with three hours measured under another manufacturer’s undisclosed sequence. A low average power may reflect efficient actuation, but it may also reflect long idle intervals, a small payload, reduced compute, or conservative motion.

Automotive engineering faced a related problem. The Worldwide Harmonized Light Vehicles Test Procedure does not claim to reproduce every possible journey. It creates a controlled demand history and associated test conditions so that vehicles, batteries, powertrains, and control strategies can be evaluated on a common basis. The analogy is methodological, not literal. A humanoid needs more than a speed trace because zero translational speed can describe both low-load standing and high-load manipulation.

A common mission does not make robots identical. It makes the consequences of their differences measurable.

What Existing Benchmarks Already Solve—and What They Do Not

The proposed framework starts from a mature body of robotics test work and from the source DHMP methodology. DXresearch DHMP manuscript v0.2 The ISO 18646 series provides performance criteria and related test methods for service-robot navigation, manipulation, and legged locomotion. ISO 18646-5:2026 addresses complete-machine locomotion performance for legged robots. ISO 18646-2:2024 and ISO 18646-3:2021 address navigation and manipulation. These standards establish terminology, apparatuses, metrics, and repeatable capability tests. They do not prescribe a combined second-by-second workload spanning walking, payload handling, perception, compute, recovery, and auxiliaries.

NIST and ASTM response-robot methods offer another strong precedent. NIST test-method catalogue The NIST response-robot programme separates elemental capability testing from increasingly realistic operational scenarios and covers mobility, manipulation, sensing, energy, communications, logistics, endurance, and safety. More than fifty ground, aerial, and maritime methods have been developed and replicated. Their procedural discipline is directly relevant to humanoids, even though their target systems and operational context differ.

EUROBENCH advanced reproducibility for bipedal and wearable robots through shared facilities, protocols, performance indicators, and structured experiment data. EUROBENCH data format HumanoidBench provides 27 simulated whole-body locomotion and manipulation tasks for algorithm research. Fraunhofer IPA’s 2026 benchmark adds application-relevant assessment of humanoid capabilities, energy efficiency, safety, cybersecurity, and other deployment criteria. Fraunhofer IPA humanoid benchmark These initiatives solve important pieces of the evaluation problem. None yet functions as a broadly adopted equivalent of an integrated humanoid system duty cycle.

Approach Primary question Strength Remaining gap
Capability standard Can the robot perform a defined function? Controlled apparatus and metric No integrated workload sequence
Task benchmark Can a policy solve a task? Algorithm comparison and repeatability Often omits battery and electrothermal realism
Deployment profile Can the robot work at one specific site? High operational relevance Not portable across customers and platforms
Reference mission How does the complete system behave under shared demand? Cross-platform energy, thermal, and runtime comparison Requires community validation and governance

DHMP: Standardize the Workload, Not the Robot

Five-layer flow from mission profile through robot execution, physical demand, electrothermal state, and comparable metrics.
Figure 1. DHMP separates the standardized workload from robot-specific implementation and models. Credit: DXresearch.eu.

DHMP uses a layered architecture. The first layer states what the robot must do and when. The second translates that mission into robot-specific motion. The third derives torque, speed, contact, current, and power. The fourth propagates electrical losses into battery and thermal states. The final layer reports comparable outcomes such as energy per cycle, runtime, peak power, thermal margin, and completed tasks.

This separation is essential. A manufacturer may use high-ratio geared actuators; another may use lower-ratio, more backdrivable joints. One robot may use a 72 V battery with distributed inverters, while another uses a higher-voltage backbone. One may execute the same walking segment with long strides; another with short, frequent steps. DHMP does not suppress those differences. It exposes how each choice changes the system result.

The framework assigns an evidence class to every material input. Values may be verified from a primary source, derived from verified data, calibrated against measurement, assumed for concept work, defined as an engineering envelope, or left unknown. This prevents a polished simulation from implying confidence that its inputs do not justify.

The Five-Minute Reference Family

The first implementation, DHMP-5, contains exactly 300 one-second records. Five minutes is long enough to combine system initialization, standing, walking, approach, manipulation, loaded movement, placement, recovery, and inspection, while remaining practical for simulation and laboratory execution. The cycle is repeated with continuous battery and thermal states until a defined termination condition is reached.

Timeline of the eleven phases in the five-minute DHMP composite mission with an illustrative power trace.
Figure 2. DHMP-5C composite cycle and workbook-derived illustrative H80 power trace. Credit: DXresearch.eu.
Time Phase Representative activity Dominant system demand
0–19 s Boot and self-check Initialize control, perception, and safety Compute, sensing, system readiness
20–49 s Idle perception Stand and scan environment Perception, compute, standing control
50–89 s Transit Walk to workstation at 0.8 m/s Locomotion, balance, communications
90–119 s Approach Slow approach and alignment Planning, balance, precision positioning
120–149 s Pick Reach and grasp a 5 kg payload Upper-body actuation, grip, perception
150–189 s Loaded transit Carry payload at 0.55 m/s Locomotion, payload support, stability
190–219 s Place Align and place payload Arm actuation, waist, precision control
220–249 s Recovery transit Walk unloaded with turn Lower body, lateral control, timing
250–269 s Dynamic event Step-over and disturbance recovery Peak power, current, balance response
270–289 s Inspection Stand and inspect Perception, inference, static holding
290–299 s Safe stop Return to controlled idle State transition, diagnostics, reporting

Three additional profiles retain the same duration and data structure. DHMP-5L emphasizes logistics and loaded walking. DHMP-5A emphasizes bimanual assembly, posture holding, tool exchange, and compute-intensive inspection. DHMP-5M emphasizes ramps, stairs, uneven terrain, fast walking, and recovery. The composite profile is the general comparison baseline; the application profiles reveal how architecture choices shift when the dominant work changes.

One-second resolution is suitable for mission states, energy integration, battery state of charge, and slow thermal networks. It is not sufficient for motor current control, impact, inverter switching, or balance-loop dynamics. The required solution is multirate reporting: higher-frequency simulation or measurement produces average, RMS, minimum, and peak descriptors for each one-second record.

Reference Robots Without Inventing a Universal Humanoid

DHMP requires a workload definition, not a mandatory reference body. Nevertheless, transparent reference classes are useful when proprietary robot data are unavailable. The source study uses Boston Dynamics Atlas as a high-capability industrial boundary and Unitree H2 as a public parameter anchor.

Boston Dynamics publishes Atlas at 1.9 m, 90 kg, 56 degrees of freedom, 2.3 m reach, 30 kg sustained payload, 50 kg instantaneous capacity, IP67, and an operating range from −20°C to +40°C. Its specification sheet states four hours of battery life under typical use, two hours with heavy lifting, and autonomous battery swap in approximately three minutes. These are manufacturer claims tied to the product configuration and not a standardized DHMP result. Atlas product page Atlas specification sheet

Unitree publishes H2 at approximately 70 kg including battery, 1.82 m height, and 31 motorized joints. It lists 120 N·m maximum arm-joint torque, 360 N·m maximum leg-joint torque, approximately 7 kg rated and 15 kg peak arm payload, a 15 Ah/0.972 kWh battery, 75.6 V maximum voltage, local air cooling, and approximately three hours of battery life. The company explicitly notes that parameters vary by configuration and scenario. Unitree H2 specifications

An intermediate H80 class is therefore defined as a modelling construct: 80 kg total mass, 1.85 m height, 31 primary body joints, 10 kg nominal payload, 72 V nominal battery architecture, and 1.5 kWh installed battery energy. H70 and H90 classes provide sensitivity boundaries. None reconstructs a proprietary platform.

From Motion to Silicon

The industrial value of a mission profile appears when system behaviour is translated into component requirements. A motion segment becomes a joint torque-speed trajectory. The actuator model converts torque into motor current. The inverter model converts current and voltage into conduction and switching loss. The thermal model converts loss into winding, housing, and junction temperature. The battery model integrates bus power and regeneration into SOC, voltage sag, and temperature.

For joint j, mechanical power is the product of torque and angular velocity:

P_mech,j(t) = τ_j(t) · ω_j(t)

Positive power represents actuator work. Negative power indicates mechanical energy flowing toward the actuator, but it does not guarantee battery recovery. Regeneration depends on transmission backdrivability, inverter operation, simultaneous bus loads, battery charge acceptance, SOC, and protection limits. DHMP therefore distinguishes negative mechanical energy from recovered electrical energy.

A geared permanent-magnet motor can be approximated by:

τ_joint,j = K_t,j · I_q,j · N_j · η_g,j

Copper loss depends on RMS current and temperature-dependent phase resistance:

P_Cu,j = 3 · I_ph,rms,j² · R_ph,j(T)

The complete DC-link demand adds joint electrical power, compute, sensing, communications, cooling, safety, and auxiliary rails. This is where the mission profile connects behaviour to semiconductor selection.

Motor-control microcontrollers

The dynamic-event and precision-manipulation phases place different requirements on real-time controllers. Disturbance recovery demands deterministic current loops, synchronized sampling, fast protection, and coordinated multi-axis control. Precision placement requires low-noise sensing, high-resolution position feedback, and stable torque at low speed. A common mission allows MCU and control-software teams to report processor loading, control latency, missed deadlines, and energy against the same operational sequence.

Power semiconductors and gate drivers

Inverter technology should be compared under identical bus voltage, current history, switching frequency, cooling, and modulation assumptions. Silicon MOSFETs, gallium-nitride devices, and other technologies may trade conduction loss, switching loss, electromagnetic emissions, cost, packaging, and fault ruggedness differently. The relevant output is not a catalogue figure of merit; it is energy and temperature under the mission’s torque-speed envelope.

Current, position, and temperature sensing

Joint current sensors must capture RMS loading and fast overcurrent events. Magnetic and inductive position sensors must maintain accuracy near high-current switching nodes. Temperature sensing and model-based observers determine available thermal margin and permit controlled thermal derating rather than abrupt shutdown. DHMP can identify which phases should be used to validate sensor bandwidth, drift, immunity, and diagnostic coverage.

Compute and memory

Perception and inference are not negligible auxiliaries. Inspection and approach phases may shift the power balance from actuation toward cameras, accelerators, memory bandwidth, and cooling. A lighter robot does not automatically consume proportionally less power because compute, sensing, safety, and communications create a mass-independent floor. Mission-level measurement therefore reveals the energy value of neural-network optimization, dynamic power management, and memory architecture.

Connectivity, synchronization, and diagnostics

A distributed humanoid requires synchronized sensor sampling, coordinated motor control, deterministic safety communication, and high-volume perception data. The mission provides event markers against which timing error, packet latency, bus utilization, diagnostic coverage, and fault recovery can be measured. Loaded transit and disturbance recovery are particularly useful for observing how communication and control margins behave under simultaneous system stress.

Functional safety and cybersecurity

DHMP is not a safety certification procedure. It can, however, define repeatable operational contexts for testing safety functions and cyber-resilience. The safe-stop phase can verify controlled transition, diagnostic reporting, and energy isolation. The boot phase can exercise secure startup and identity. Networked update, fleet, and teleoperation functions create cybersecurity requirements whose computational and timing cost belongs in the system workload. The ISO/TC 299 work programme includes dynamically stable mobile-robot safety and broader robotics safety activities, reinforcing the need to align benchmark evolution with formal safety work rather than substitute for it. ISO/TC 299 work programme

Battery Runtime Is a Result, Not a Specification

The simplest runtime relationship is usable battery energy divided by average battery power. Yet both terms depend on definitions. Installed energy is reduced by SOC limits, ageing, reserve, temperature, and power capability. Average power depends on mission, payload, mass, control, actuators, compute, cooling, and regeneration.

The source workbook separates a fixed power floor from mass-dependent mechanical demand. DHMP workbook v0.2 For an illustrative 55 kg robot, 3.0 kWh installed battery, 90% usable energy, and 300 W fixed load, the 80 kg profile values are scaled by the mass ratio 55/80. This is an engineering illustration rather than a validated physical model.

Bar chart comparing idealized runtime for composite, logistics, assembly, and mobility profiles for a 55 kilogram robot with a 3 kilowatt-hour battery.
Figure 3. Illustrative runtime resulting from four DHMP-5 profiles. Credit: DXresearch.eu.
Profile H80 mean power 55 kg scaled power Energy per cycle Idealized runtime
Composite 591.2 W 500 W 41.7 Wh 5.4 h
Logistics 702.1 W 576 W 48.0 Wh 4.7 h
Assembly 518.9 W 451 W 37.6 Wh 6.0 h
Mobility 699.9 W 575 W 47.9 Wh 4.7 h

The range is more informative than a single runtime claim. Assembly reduces locomotion energy but may produce sustained shoulder, elbow, hand, and compute loading. Mobility increases hip, knee, ankle, and peak bus demand. Logistics stresses repeated loaded transport. A future joint-level model may change the numbers, but the structure of the comparison remains valid.

Energy may not be the first limit. A large battery can keep SOC high while a knee motor, inverter, gearbox, battery cell, or AI module reaches its thermal threshold. A repeated-cycle simulation must carry every thermal state forward. Resetting temperatures every five minutes would invalidate the prediction.

Conformance, Validation, and the Difference Between a Benchmark and a Score

DHMP should initially define conformance to execution and reporting, not a minimum performance grade. A robot can conform while consuming high energy or failing a phase, provided the failure and deviation are disclosed. This avoids collapsing unlike system objectives into one opaque score.

Level Scope Minimum evidence
0 Mission execution Profile, configuration, completion, timing, deviations
1 System energy Battery power, energy per cycle, SOC, estimated runtime
2 Subsystem energy Actuation, compute, sensing, cooling, communications, auxiliaries
3 Joint electrothermal Torque, speed, current, loss, actuator and semiconductor temperature
4 Validated digital twin Measured-to-simulated correlation, error, uncertainty, validity range

Validation should progress from formula and file checks to independent simulation implementations, one instrumented robot, multiple robot classes, multiple laboratories, and field correlation. The most important measurements are battery voltage and current, joint position and speed, measured or estimated torque, phase current, compute and auxiliary rail power, relevant temperatures, payload position, ambient conditions, and synchronized mission events.

Repeatability asks whether one laboratory obtains stable results from repeated execution. Reproducibility asks whether independent laboratories interpret the mission and reporting rules similarly. Field correlation asks whether DHMP trends align with real applications even though the reference cycle is not a literal copy of one customer site.

Governance: From Reference Proposal to Industry Standard

The initiative should be explicit about maturity. DHMP is currently a public reference proposal. A validated industry benchmark would require multi-platform evidence, controlled revision, and independent replication. A consensus standard would require a recognized standards process.

DXresearch can initiate the package, maintain the repository, curate evidence, and convene contributors. It should not claim sole authority. A durable governance model needs robot OEMs, industrial users, universities, test laboratories, actuator and battery suppliers, semiconductor companies, simulation vendors, and safety experts.

Changes to phase timing, payload, environment, or required signals should follow documented proposals, evidence, public review, and version control. Frozen revisions must remain available so that historical results stay interpretable. New profiles should inherit the same data schema and evidence rules to prevent fragmentation.

Formal engagement with ISO, IEEE, ASTM, or other organizations should occur after physical validation and community participation. The objective is to contribute a working method, datasets, and lessons learned—not to pre-empt consensus.

What Must Improve Next

The present proposal is deliberately incomplete. The profiles are engineering constructs rather than statistically derived field cycles. H80 is not a reconstruction of Atlas, H2, or another product. The workbook uses normalized joint-group utilization and generic power coefficients rather than complete 31-joint torque-speed-current traces. Payload position, turn geometry, friction, stair fixtures, disturbance magnitude, and manipulation geometry need more precise definitions.

The next technical release should add a reference URDF or morphology-neutral joint mapping, higher-frequency trajectories, actuator maps, inverter loss interfaces, battery voltage and thermal models, and repeated-cycle electrothermal simulation. The next experimental release should publish an instrumented execution with uncertainty and measurement synchronization.

These limitations are not reasons to postpone a shared mission. They are reasons to publish the assumptions openly and improve them through use.

Strategic Synthesis

Humanoid robotics is moving from capability theatre toward industrial engineering. That transition requires a change in the questions the industry asks. “Can the robot lift this object?” must be followed by “How many times can it lift, carry, and place the object before energy, temperature, reliability, or availability becomes limiting?”

A shared mission profile provides the missing bridge. It connects human-scale work to joint trajectories; joint trajectories to current and losses; losses to temperatures and battery demand; and those states to runtime, reliability, and economics. For semiconductor developers, it turns vague claims about the value of faster control, lower loss, better sensing, deterministic connectivity, and robust diagnostics into testable system outcomes.

DHMP should not become a rigid definition of the “correct” humanoid. Its purpose is narrower and more powerful: to establish what was tested, under which conditions, with which assumptions, and with what result. That is the foundation on which credible comparison, efficient co-design, and eventual standardization can be built.

Conclusion

The absence of a common humanoid workload leaves runtime, energy, thermal, and subsystem claims difficult to compare. Existing standards and benchmarks provide strong capability methods, but they do not yet supply one broadly adopted integrated mission trace. DHMP proposes a five-minute, one-second-resolution family that separates mission definition from robot implementation and connects behaviour to mechanical, electrical, thermal, battery, compute, safety, and semiconductor consequences.

The framework is not a finished standard and the illustrative values are not product claims. Its value is transparency. A common workload makes assumptions visible, enables repeatable simulation and measurement, and gives the industry a shared language for improving the complete Physical AI system.

References

  1. United Nations Economic Commission for Europe, “UN Global Technical Regulation No. 15: Worldwide harmonized Light vehicles Test Procedures.” https://unece.org/sites/default/files/2022-06/ECE-TRANS-180a15am6e.pdf
  2. International Organization for Standardization, “ISO/TC 299 Robotics — Standards catalogue and work programme.” https://www.iso.org/committee/5915511/x/catalogue/
  3. International Organization for Standardization, “ISO 18646-5:2026 Robotics — Performance criteria and related test methods for service robots — Part 5: Locomotion for legged robots.” https://www.iso.org/standard/86850.html
  4. International Organization for Standardization, “ISO 18646-2:2024 Robotics — Performance criteria and related test methods for service robots — Part 2: Navigation.” https://www.iso.org/standard/76545.html
  5. International Organization for Standardization, “ISO 18646-3:2021 Robotics — Performance criteria and related test methods for service robots — Part 3: Manipulation.” https://www.iso.org/standard/69058.html
  6. National Institute of Standards and Technology, “Standard Test Methods for Response Robots.” https://www.nist.gov/el/intelligent-systems-division-73500/standard-test-methods-response-robots
  7. National Institute of Standards and Technology, “Response Robot Test Methods.” https://www.nist.gov/el/intelligent-systems-division-73500/test-methods
  8. European Commission CORDIS, “EUROBENCH — European Robotic Framework for Bipedal Locomotion Benchmarking.” https://cordis.europa.eu/project/id/779963/results
  9. EUROBENCH Consortium, “EUROBENCH Software Documentation and Data Format.” https://eurobench.github.io/sofware_documentation/latest/data_format.html
  10. Fraunhofer IPA, “Fraunhofer IPA develops standardized analyses for application-relevant criteria of humanoid robots.” https://www.ipa.fraunhofer.de/en/press-media/press_releases/benchmark-for-humanoid-robots.html
  11. University of California, Berkeley and Yonsei University, “HumanoidBench: Simulated Humanoid Benchmark for Whole-Body Locomotion and Manipulation.” https://humanoid-bench.github.io/
  12. Boston Dynamics, “Atlas Humanoid Robot.” https://bostondynamics.com/products/atlas/
  13. Boston Dynamics, “Atlas Specification Sheet.” https://bostondynamics.com/wp-content/uploads/2026/01/atlas-spec-sheet.pdf
  14. Unitree Robotics, “Unitree H2 Destiny Awakening — Product Parameters.” https://www.unitree.com/mobile/H2/
  15. DXresearch, “An Open Reference Mission Profile for Humanoid Robots: A Framework for System-Level Energy, Thermal, Electrical, and Runtime Evaluation.” DXresearch source document.
  16. DXresearch, “Humanoid Mission Cycle 5 min v0.2 — Atlas, H2, and H80.” DXresearch source document.

Glossary

10BASE-T1S

A 10 Mb/s single-pair Ethernet physical layer supporting short-reach multidrop operation.

Bluetooth Low Energy

Low-power wireless technology used for provisioning, peripherals, diagnostics, ranging and selected sensor links.

Conformance

Correct execution and reporting against a defined profile, independent of whether the measured performance is favorable.

Cybersecurity

Protection of robot systems, communications, updates, identities, data, and control functions against malicious or unauthorized action.

The direct-current electrical bus connecting the battery or converter to distributed motor inverters and auxiliary loads.

Delay/Disruption Tolerant Networking

Store-and-forward networking designed for delayed, intermittent or disrupted communications paths.

Determinism

Ability to guarantee that communication or computation completes within defined temporal bounds.

Digital twin

A computational model connected to physical design or measurement data and maintained within a stated validity range.

Distributed Clocks

EtherCAT mechanism for synchronizing device clocks so distributed axes execute against a common time base.

Duty cycle

The distribution and sequence of operating states that determine average loading, peaks, temperature, energy, and lifetime.

EtherCAT

An Ethernet-based industrial fieldbus optimized for deterministic cyclic process data and synchronized motion.

Evidence class

A label distinguishing verified, derived, calibrated, assumed, envelope, and unknown inputs or results.

Fail-operational

Capability to continue a defined level of operation after one or more faults instead of immediately stopping.

Fault containment region

An architectural boundary intended to prevent a fault or compromise from propagating into other subsystems.

Field-oriented control

A motor-control method that regulates orthogonal current components to control torque and magnetic flux.

Functional safety

The part of overall safety that depends on correct operation of electrical, electronic, and programmable electronic systems.

Graceful degradation

Maintaining bounded, reduced functionality after a fault instead of abruptly losing all operational capability.

Hardware Root of Trust

A protected hardware foundation for device identity, cryptographic keys, measurements and trusted startup.

In-situ resource utilization

Producing useful materials, energy or consumables from resources found at the destination.

In-space servicing, assembly and manufacturing

Robotic or crew-assisted servicing, assembly and manufacturing performed after launch in space.

Jitter

Variation in packet or task timing relative to its intended schedule.

Junction temperature

The estimated or measured temperature of a semiconductor device's active junction.

Latency

Elapsed time from transmission or event generation until the required receiving action can occur.

Local safety loop

A deterministic control path that detects hazards and produces a response without remote intervention.

LunaNet

An interoperable framework for lunar communications, networking, position, navigation and timing services.

Mission profile

A time-resolved workload describing what a robot does, under which conditions, and in which sequence.

Mixed-criticality system

A computing system hosting functions with different assurance and timing requirements under controlled isolation.

Over-the-Air Update

Remote delivery of authenticated software or firmware packages through a managed update system.

Physical AI

Artificial intelligence embodied in machines that sense, decide, and act within the physical world.

Position, navigation and timing

Services and measurements used to establish location, motion and synchronized time.

Quality of Service

Traffic classification and scheduling mechanisms used to allocate bandwidth and prioritize communication flows.

Radiation tolerance

The capacity of electronics to continue functioning within specified limits under ionizing radiation and particle events.

Regenerative energy

Mechanical energy converted back into electrical energy during braking, lowering, or negative joint power.

Regolith

Loose fragmented material covering the surface of the Moon or another planetary body.

Root mean square

A statistical measure used to represent the effective magnitude of varying current, torque, speed, or voltage.

Safety over EtherCAT

A safety communication protocol transported over EtherCAT while maintaining an independently assessed safety layer.

Secure boot

A startup process that cryptographically verifies executable components before allowing them to run.

Shared autonomy

Control in which humans set goals or intervene while robots execute local perception, planning and motion.

Single-event effect

A transient or permanent electronic disturbance caused by one energetic particle.

Single-Pair Ethernet

Ethernet physical layers using one balanced conductor pair, reducing cable mass and enabling compact links.

Software Bill of Materials

A machine-readable inventory of software components and dependencies used to manage vulnerabilities and updates.

State of charge

The available battery charge expressed relative to a defined full-charge reference.

Thermal cycling

Repeated heating and cooling that stresses materials, solder joints, packages and interconnects.

Thermal derating

The controlled reduction of torque, power, or compute performance as component temperature approaches a defined limit.

Time-Sensitive Networking

A set of IEEE 802.1 mechanisms for bounded-latency, synchronized and reliable Ethernet communication.

Torque-speed envelope

The permissible combinations of actuator torque and rotational speed under voltage, current, thermal, and mechanical constraints.

Wi-Fi

Wireless local-area networking based on IEEE 802.11, suitable for service, fleet and high-throughput non-safety links.

References

  1. An Open Reference Mission Profile for Humanoid Robots: A Framework for System-Level Energy, Thermal, Electrical, and Runtime Evaluation. Provides the source methodology, H80 reference model, DHMP-5 profiles, equations, example runtime calculation, and standardization strategy.
  2. Atlas Humanoid Robot. Publishes Atlas dimensions, mass, payload, reach, degrees of freedom, operating range, sensing, runtime, and environmental protection claims. Source
  3. Atlas Specification Sheet. Provides detailed Atlas battery-life, payload, charging, environmental, safety, operating-mode, and autonomous battery-swap specifications. Source
  4. Automation and Robotics. ESA program overview covering robotic technologies for Earth orbit, planetary exploration, human-robot interaction and supporting engineering facilities. Source
  5. Automation and Robotics Laboratories. ESA laboratory description for engineering and validating robotic solutions for in-orbit operations, manipulation and low-gravity sampling. Source
  6. Bluetooth Core 6.0 Feature Overview. Explains Bluetooth 6.0 feature additions, particularly secure ranging and improvements relevant to provisioning and location services. Source
  7. Bluetooth Core Specification Version 6.0. Defines Bluetooth Core 6.0, including channel sounding, advertising improvements and changes to isochronous operation. Source
  8. CADRE. Mission page for three small lunar rovers designed to cooperate through local networking and largely autonomous distributed exploration. Source
  9. China’s First Standards System for Humanoid Robots and Embodied Intelligence. Reports China’s initial humanoid and embodied-intelligence standards framework and a first list of proposed standardization topics. Source
  10. Choosing the Right TSN Tools to Meet a Bounded Latency. Explains how completed TSN mechanisms can be selected and combined to provide bounded-latency Ethernet communication. Source
  11. Delay/Disruption Tolerant Networking. NASA explanation of store-and-forward networking for delayed, intermittent links and its role in future solar-system communications. Source
  12. EtherCAT – The Ethernet Fieldbus. Describes EtherCAT frame processing, topology flexibility and distributed-clock synchronization for deterministic industrial motion and I/O. Source
  13. EtherCAT SubDevice Implementation Guide, ETG.2200. Provides implementation guidance for EtherCAT subdevices, including precise synchronization through the distributed-clocks mechanism. Source
  14. EtherCAT Technology Group Brochure. Summarizes EtherCAT performance, distributed clocks, cable redundancy and industrial-network implementation characteristics. Source
  15. EUROBENCH — European Robotic Framework for Bipedal Locomotion Benchmarking. Documents a European framework, facilities, protocols, and performance indicators for reproducible benchmarking of bipedal and wearable robots. Source
  16. EUROBENCH Software Documentation and Data Format. Defines experiment data structures and processing concepts that provide a useful precedent for machine-readable humanoid benchmark packages. Source
  17. Fraunhofer IPA develops standardized analyses for application-relevant criteria of humanoid robots. Introduces a modular humanoid benchmark covering capabilities, energy efficiency, safety, cybersecurity, cleanroom suitability, and industrial readiness. Source
  18. Hello Universe: NASA's Next-Gen Space Processor Undergoes Testing. Testing update describing the HPSC processor's intended performance increase and environmental qualification before use in future spaceflight systems. Source
  19. High Performance Spaceflight Computing. Program status for a radiation-tolerant high-performance processor undergoing power, reliability, performance and radiation qualification testing for future missions. Source
  20. Humanoid Mission Cycle 5 min v0.2 — Atlas, H2, and H80. Companion workbook defining four 300-second profiles, reference parameters, normalized joint utilization, power estimates, and energy results.
  21. HumanoidBench: Simulated Humanoid Benchmark for Whole-Body Locomotion and Manipulation. Provides twenty-seven simulated whole-body tasks for algorithm research, illustrating the difference between task benchmarks and physical duty cycles. Source
  22. IEC 62443-4-1:2018 — Secure product development lifecycle requirements. Defines secure development lifecycle requirements covering requirements, design, implementation, verification, defect management, patch management and product end-of-life. Source
  23. IEC 62443-4-2:2019 Technical Security Requirements for IACS Components. Defines component-level technical cybersecurity requirements and capability security levels for industrial control-system products. Source
  24. IEC TR 62443-2-3:2015 Patch Management in the IACS Environment. Provides a structured approach to security-patch information, evaluation, distribution and deployment in industrial automation environments. Source
  25. IEEE 802.1AS-2025: Timing and Synchronization for Time-Sensitive Applications. Specifies synchronized time for time-sensitive applications, including operation through network changes, additions, removals and failures. Source
  26. IEEE 802.3da-2026: Enhanced 10 Mb/s Single-Pair Ethernet Multidrop Segments. Enhances 10BASE-T1S multidrop operation with time-synchronization support and optional power delivery to multiple devices. Source
  27. In-Space Servicing, Assembly, and Manufacturing. NASA program overview for robotic refueling, repair, upgrading, assembly and manufacturing of spacecraft and structures in space. Source
  28. ISO 10218-1:2025 Robotics — Safety Requirements — Industrial Robots. Specifies safety requirements for industrial robots as machines, complementing system-integration requirements in ISO 10218-2. Source
  29. ISO 18646-2:2024 Robotics — Performance criteria and related test methods for service robots — Part 2: Navigation. Defines navigation performance criteria and repeatable tests relevant to pose accuracy, repeatability, and obstacle detection and avoidance. Source
  30. ISO 18646-3:2021 Robotics — Performance criteria and related test methods for service robots — Part 3: Manipulation. Defines manipulation performance criteria and related tests, complementing but not replacing an integrated humanoid mission workload. Source
  31. ISO 18646-5:2026 Robotics — Performance criteria and related test methods for service robots — Part 5: Locomotion for legged robots. Provides methods for specifying and evaluating complete-machine locomotion performance of bipedal, quadrupedal, and other legged service robots. Source
  32. ISO/TC 299 Robotics — Standards catalogue and work programme. Lists published and developing robotics standards, including energy measurement, legged locomotion, mobile robot safety, and humanoid datasets. Source
  33. ISO/WD 25874.2 Robotics — Safety Requirements. Developing common safety requirements for robotics outside existing industrial, medical and selected service-robot scopes. Source
  34. LunaNet Interoperability Specification Version 5. Interoperability specification defining communications, networking and position-navigation-timing services for future lunar users and service providers. Source
  35. Lunar Dust Mitigation: A Guide and Reference. Technical reference describing lunar dust properties, contamination mechanisms, system effects and mitigation considerations for surface hardware. Source
  36. Lunar Environment Structural Test Rig. Description of a vacuum and cryogenic test facility for materials, electronics and structures intended for lunar environments. Source
  37. Lunar Surface Technology. NASA overview of power, communications, construction, dust mitigation and autonomous systems needed for scalable long-duration lunar surface infrastructure. Source
  38. Moon to Mars Architecture Definition Document, Revision C. Architecture framework describing evolving lunar exploration segments, robotic support, mobility, logistics and preparation for sustained human operations and Mars. Source
  39. Moon to Mars Architecture White Papers. Supporting studies covering lunar logistics, surface operations, communications disruption and the autonomy implications of missions farther from Earth. Source
  40. NASA Enables Construction Technology for Moon and Mars Exploration. Overview of robotic large-scale additive construction research using simulated regolith for prospective lunar and Martian infrastructure. Source
  41. NASA JPL Unveils Rover Operations Center for Moon, Mars Missions. JPL facility announcement connecting decades of Mars operations experience with future lunar and planetary rover mission support. Source
  42. NASA Testing Advanced Capabilities for Moon, Mars Rovers. Testing report on ERNEST mobility and autonomy techniques for traversing difficult terrain on future lunar and Martian missions. Source
  43. On-Orbit Servicing, Assembly, and Manufacturing 1. Official status of the discontinued OSAM-1 project, documenting programmatic challenges relevant to assessing orbital servicing maturity. Source
  44. Renesas Solutions for Robotics. Shows industrial robot architectures combining central motion-network controllers with distributed axis-control devices.
  45. Response Robot Test Methods. Presents elemental robot test apparatuses and metrics for repeatable evaluation of mobility, dexterity, perception, navigation, and endurance. Source
  46. Robotics at JPL. JPL overview of robotic exploration technologies and missions spanning the Moon, Mars, asteroids and other planetary destinations. Source
  47. Silicon Carbide Electronics and Sensors: Benefits and Collaborations. NASA overview of silicon-carbide electronics for high-temperature, high-radiation environments where reduced cooling and shielding can benefit missions. Source
  48. Standard Test Methods for Response Robots. Describes modular quantitative methods covering robot mobility, manipulation, sensing, energy, communications, logistics, endurance, and safety. Source
  49. The Harsh Environment of the Lunar South Pole. NASA reference on extreme temperature, illumination, dust and operational conditions affecting hardware near the lunar south pole. Source
  50. Time-Sensitive Networking Task Group. Defines TSN’s purpose as deterministic IEEE 802 connectivity with bounded latency, controlled variation and low packet loss. Source
  51. UN Global Technical Regulation No. 15: Worldwide harmonized Light vehicles Test Procedures. Defines the harmonized vehicle test procedure used as a methodological precedent for repeatable mission-based system evaluation. Source
  52. Unitree H2 Destiny Awakening — Product Parameters. Publishes H2 mass, geometry, degrees of freedom, actuator torque, payload, battery, cooling, compute, sensing, and runtime specifications. Source