STATERA Library · Series 09 · Volume 06 · Chapter 07 · EN
Source: https://github.com/Statera-Library/09_Vol_06_Physical_AI_Hardware_Software_Co_Design/blob/main/Chapter_07_Power_and_Thermal_Constraints/Chapter_07_Power_and_Thermal_Constraints_EN.md

Volume 06. Physical AI Hardware Software Co Design

Chapter 07. Power and Thermal Constraints

07.01. Power as a Primary Physical AI Constraint

Power is not merely a supporting resource in Physical AI; it is one of the fundamental constraints that determines what intelligence can physically exist on a robot. Every sensing, computation, communication, and actuation function ultimately consumes electrical energy. A model that performs exceptionally on a workstation may therefore be unsuitable for an autonomous machine if its continuous power demand exceeds the platform's available energy.

Unlike cloud AI, Physical AI operates inside an energy-constrained body. The robot must carry, generate, receive, or periodically replenish the energy required for both intelligence and motion. Increasing GPU performance, sensor resolution, communication bandwidth, or actuator capability can improve system performance, but each improvement competes for the same limited power source. Power consequently becomes a system-level design variable connecting hardware, software, AI, and embodiment.

The importance of power becomes especially clear in battery-powered robots. Battery capacity establishes a finite energy reservoir, while the combined loads of motors, computers, sensors, networking devices, cooling systems, and auxiliary electronics determine how quickly that reservoir is depleted. Runtime therefore cannot be evaluated from AI compute consumption alone. Physical AI requires an integrated view of energy consumption across the complete cyber-physical system.

Power and energy must also be distinguished carefully. Power describes the instantaneous rate at which energy is consumed, whereas energy determines how long that consumption can be sustained. A robot may have sufficient battery energy for several hours of nominal operation but still fail when simultaneous acceleration, manipulation, perception, and AI inference create excessive instantaneous demand. Both average consumption and short-duration peak loads must therefore influence system architecture.

AI computation introduces a particularly important design tradeoff. Larger neural networks, higher inference rates, richer multimodal representations, world models, and sophisticated reasoning can increase intelligence but also increase computational activity and electrical demand. The correct objective is consequently not maximum AI performance in isolation, but sufficient intelligence per unit of energy while satisfying perception accuracy, reasoning quality, response latency, safety, and mission requirements.

Sensor architecture contributes another layer to the power constraint. Cameras, LiDAR, radar, IMUs, GNSS receivers, microphones, and proprioceptive sensors consume energy directly, while their data streams indirectly increase compute and memory activity. Higher resolution and update rates may therefore create cascading power costs across sensing, data transport, preprocessing, fusion, inference, and storage. Sensor selection should consequently consider information value per unit of system energy.

Actuation often dominates total robot energy consumption because physical motion requires mechanical work. However, the relative balance varies dramatically with embodiment and mission. A stationary inspection platform may devote a substantial fraction of its power to sensing and AI computing, while a heavy mobile robot may consume far more energy through propulsion. A humanoid or quadruped can add continuous stabilization and joint actuation demands that fundamentally reshape the available compute budget.

This interaction means that compute and actuation cannot be independently optimized. Aggressive motion may reduce the energy available for extended reasoning, while computationally expensive perception or planning can shorten the operating time available for movement. Conversely, better AI may identify smoother trajectories, efficient velocities, safer terrain, or lower-energy manipulation strategies. Intelligence consumes energy, but properly designed intelligence can also reduce total physical energy expenditure.

Power constraints also influence where computation should occur. Safety-critical perception, planning, and control generally require reliable on-robot execution, but computationally expensive tasks may sometimes be transferred to on-premise or cloud infrastructure when connectivity and latency permit. Offloading can reduce local computation, although communication itself consumes energy and introduces dependency on network availability. Edge-cloud partitioning must therefore consider energy together with latency, reliability, privacy, and autonomy.

The electrical architecture must support more than nominal operating conditions. Motors can produce large transient currents during acceleration, steering, climbing, manipulation, or recovery from disturbances, while GPUs and other processors can exhibit rapidly changing computational loads. If these demands coincide, voltage drops, current limits, or protection mechanisms may destabilize the system. Power distribution must therefore be designed around realistic concurrent workloads rather than isolated component ratings.

Thermal behavior is inseparable from this power problem because much of the electrical energy consumed by computation ultimately becomes heat. Higher compute power increases cooling requirements, and cooling fans, pumps, or other thermal-management components themselves require additional energy. When heat cannot be removed sufficiently, processors may throttle their operating frequency, reducing inference throughput and increasing latency. Available electrical power does not automatically imply sustainably available AI performance.

Power constraints therefore propagate directly into software architecture. AI workloads can be scheduled according to mission state, uncertainty, environmental complexity, battery condition, and thermal headroom. A robot traveling through a predictable environment may use lightweight perception and slower world-model updates, while uncertain or hazardous conditions can activate more expensive reasoning. Such adaptive computation converts power management from a static hardware concern into an intelligent runtime capability.

This approach encourages multiple operating modes rather than a single fixed performance point. High-performance modes may maximize perception and reasoning during difficult tasks, while nominal modes balance capability and runtime. Energy-saving modes can reduce sensor rates, inference frequency, communication activity, or nonessential computation. Emergency modes may reserve power exclusively for localization, safety monitoring, basic control, communication, and movement toward a safe state or charging location.

Mission planning should consequently include energy as part of the robot's internal world state. Remaining battery energy, predicted actuator demand, compute workload, terrain difficulty, payload, temperature, communication conditions, and distance to charging infrastructure can all affect whether a planned action remains feasible. Energy-aware Physical AI therefore extends conventional path and task planning into resource-aware reasoning about whether the robot can physically complete its intended future behavior.

The resulting design principle is that power should be treated as a first-class constraint from the beginning of Physical AI development rather than checked after hardware and AI models have already been selected. Compute platforms, sensors, actuators, batteries, communication systems, cooling architecture, inference policies, and mission logic must be co-designed around a shared energy envelope. This establishes the foundation for subsequent analysis of robot power budgets, compute consumption, runtime, peak loads, thermal limits, and energy-aware inference.

07.02. Robot System Power Budget

A robot system power budget defines how the available electrical power and stored energy are allocated across all subsystems required for autonomous operation. Rather than treating the battery as a simple source for motors and computers, Physical AI design must account for propulsion, manipulation, AI compute, sensing, communication, cooling, control electronics, and auxiliary loads as parts of one constrained electrical system.

The first step is to establish the total energy source and electrical architecture of the robot. Battery voltage, usable capacity, discharge limits, conversion efficiency, and allowable depth of discharge determine the practical energy envelope. A battery rated at a certain nominal capacity cannot be assumed to deliver all of that energy to useful workloads because conversion losses, protection margins, aging, temperature, and reserve requirements reduce usable energy.

A useful power budget separates continuous, average, and peak power requirements. Continuous loads include computers, controllers, networking equipment, and sensors that remain active during operation. Average power incorporates workloads whose consumption varies over time, such as propulsion or manipulation. Peak power represents short periods in which acceleration, steering, lifting, intensive AI inference, communication, and cooling may simultaneously demand substantially more power.

Actuators frequently represent the largest and most variable part of the budget. Drive motors consume energy according to vehicle mass, payload, velocity, acceleration, rolling resistance, terrain, slope, and drivetrain efficiency. Manipulators add joint motors, brakes, grippers, pumps, or other mechanisms. Because mechanical workloads vary with the mission, actuator power should be estimated using representative duty cycles rather than only maximum motor ratings.

AI computing forms another major budget category. CPUs, GPUs, NPUs, memory, storage, and associated interfaces can create substantial continuous electrical demand, especially when high-resolution perception, multimodal fusion, world modeling, planning, or VLA inference runs continuously. Compute power should therefore be measured under realistic workloads because idle, nominal inference, intensive reasoning, and maximum accelerator utilization can produce very different consumption levels.

Sensor power may appear small compared with propulsion or high-performance compute, but multiple sensors can create a significant cumulative load. Cameras, LiDAR, radar, GNSS, IMUs, microphones, encoders, and environmental sensors all require electrical power. Their interfaces and preprocessing hardware also consume energy. Increasing sensor count, resolution, range, illumination, or update frequency can therefore increase both direct sensing power and indirect compute power.

Communication systems must also be included explicitly. Ethernet switches, Wi-Fi, cellular modems, radios, GNSS correction receivers, antennas with active electronics, and fleet communication devices may operate continuously. Their consumption can vary with transmission activity and link conditions. Offloading computation may reduce local AI power, but frequent high-bandwidth communication can partially offset those savings while introducing additional network dependencies.

Thermal management is another necessary budget item because electrical consumption generates heat that must be removed. Fans, pumps, liquid-cooling systems, heat exchangers, and control electronics consume power while protecting processors, batteries, and power electronics from excessive temperature. Cooling demand can rise as AI compute load increases, creating a secondary energy cost that should be included when estimating the true power required by high-performance computing.

Auxiliary loads are easy to underestimate because each may appear individually small. Lighting, displays, indicators, safety controllers, emergency circuits, storage devices, relays, contactors, DC-DC converters, payload electronics, and miscellaneous I/O remain part of the total system demand. A realistic budget therefore includes these loads together with conversion losses rather than allocating the entire battery capacity only to major components.

The power budget should be represented across operating states rather than as one fixed number. A robot may have standby, idle, navigation, high-speed travel, manipulation, intensive perception, charging, degraded, and emergency states. Each state activates a different combination of components. State-based budgeting reveals which operational combinations produce the highest continuous demand and which create potentially dangerous transient peaks.

Duty cycle is essential when converting subsystem power into mission energy consumption. A motor drawing high power for a short climb may consume less total energy than a GPU operating continuously for several hours. Conversely, propulsion that appears moderate instantaneously can dominate mission energy when the robot travels continuously. Energy estimation therefore requires multiplying power by realistic operating duration and combining the contributions across the mission profile.

A practical budget must reserve margin instead of allocating one hundred percent of theoretical capacity. Engineering margin accommodates modeling error, battery aging, temperature effects, payload variation, unexpected terrain, sensor additions, software growth, and future AI workloads. Energy reserves are also needed so that the robot can reach a charging point, execute a safe shutdown, maintain communication, or preserve essential control when normal mission execution must be abandoned.

Peak-power analysis requires special attention because average energy calculations alone cannot guarantee electrical stability. Simultaneous motor acceleration, manipulator movement, GPU workload spikes, and cooling activation can produce transient demand beyond the battery, battery-management system, wiring, connectors, converters, or regulators. The distribution architecture must tolerate these events without excessive voltage drop, current limiting, resets, or loss of safety-critical control.

Power budgeting consequently becomes an iterative hardware-software co-design process. If estimated demand exceeds the available envelope, designers can increase battery capacity, improve drivetrain efficiency, select lower-power compute, reduce sensor activity, optimize AI models, change inference frequency, schedule workloads, or modify the mission. Each choice affects weight, cost, thermal behavior, runtime, performance, and sometimes the mechanical design itself.

A mature Physical AI system can extend static budgeting into runtime power management. Telemetry from batteries, motor drives, processors, sensors, and thermal systems allows the robot to compare actual consumption with predicted demand. The autonomy stack can then reduce nonessential workloads, alter motion, lower inference rates, defer communication, or enter energy-saving modes when remaining energy or instantaneous power margins become insufficient.

Ultimately, the robot system power budget is a quantitative contract between the energy source and every physical and computational function of the machine. It connects battery capacity, electrical distribution, actuator demand, AI compute, sensing, communication, thermal management, mission duration, and safety reserve within one shared resource model. This budget provides the foundation for sizing the battery and power electronics while ensuring that intended Physical AI capability can be sustained throughout the required operating period.

07.03. AI Compute Power Consumption

AI compute power consumption is a central design concern in Physical AI because computational intelligence must operate within the electrical limits of the robot. CPUs, GPUs, NPUs, memory, storage, and supporting interfaces all consume power while executing perception, world modeling, planning, reasoning, and control workloads. The required compute capability must therefore be evaluated together with energy availability, runtime, thermal limits, and mission requirements.

The power consumed by an AI computer is not a fixed value determined only by its processor rating. Actual consumption changes with accelerator utilization, clock frequency, voltage, memory traffic, model architecture, numerical precision, inference rate, and concurrent workloads. A processor may consume relatively little power while idle but approach its configured power limit when multiple perception networks, multimodal models, or reasoning processes operate simultaneously.

AI workloads differ substantially in their computational characteristics. Conventional object detection or localization may execute with relatively predictable workloads, whereas multimodal fusion, occupancy prediction, world models, foundation models, and Vision-Language-Action models can require much larger amounts of computation and memory movement. Consequently, selecting compute hardware from peak TOPS or FLOPS alone does not reveal the electrical cost of sustaining the intended Physical AI workload.

Model size is an important contributor to compute power because larger models generally require more arithmetic operations, memory capacity, and data movement. However, parameter count alone is insufficient for predicting consumption. Two models with similar parameter counts may exhibit very different power behavior because of differences in architecture, activation size, sparsity, attention mechanisms, memory access patterns, and hardware utilization. Power evaluation should therefore use representative deployed models.

Inference frequency directly connects AI performance to energy consumption. A perception network operating at 30 Hz performs substantially more inference work over time than the same network operating at 5 Hz. High-frequency processing may be essential for fast motion or safety-critical perception, while slower-changing semantic understanding may tolerate lower update rates. Different AI functions should therefore operate at frequencies matched to their physical and temporal requirements.

Memory and data movement can consume a significant portion of AI computing energy. Sensor tensors, intermediate activations, model weights, feature maps, BEV representations, and world-model states repeatedly move between sensors, system memory, accelerator memory, caches, and processing units. Increasing memory bandwidth can improve performance, but unnecessary data transfers waste energy. Efficient Physical AI architectures therefore minimize movement while keeping frequently required information close to computation.

Multimodal perception amplifies this issue because cameras, LiDAR, radar, IMU, proprioception, and other modalities generate heterogeneous streams that require preprocessing and fusion. Higher sensor resolution and update rates increase both input bandwidth and compute activity. The resulting power demand is therefore not merely the consumption of the AI accelerator itself; it includes data acquisition, transfer, preprocessing, synchronization, memory operations, and inference across the complete perception pipeline.

World models and reasoning systems introduce another layer of power demand. Predicting future states, maintaining latent representations, evaluating alternative trajectories, or performing iterative reasoning can require substantially more computation than a single feed-forward inference pass. The energy cost grows further when prediction horizons, candidate actions, reasoning iterations, or model sizes increase. Physical AI must consequently determine how much predictive reasoning is justified by the current environment and mission.

Hardware acceleration can improve energy efficiency when workloads are mapped to the appropriate processing units. CPUs remain valuable for general-purpose logic and orchestration, while GPUs provide highly parallel computation and NPUs or specialized AI accelerators can execute supported neural operations efficiently. Heterogeneous computing allows workloads to be assigned according to their computational characteristics rather than forcing every function onto the most powerful processor.

Numerical precision also affects the relationship between performance and power. Operations using FP32, FP16, BF16, INT8, or other reduced-precision representations have different compute, memory, and bandwidth requirements. Quantization and mixed-precision execution can reduce energy consumption when model accuracy remains acceptable. Similarly, pruning, sparsity, knowledge distillation, efficient attention, and compact architectures can reduce the computational work required for each useful inference.

AI compute power must be evaluated together with thermal management because most consumed electrical power eventually becomes heat. Sustained accelerator utilization can raise processor and enclosure temperatures, requiring fans, pumps, heat sinks, or other cooling mechanisms. Cooling consumes additional energy, and inadequate heat removal can cause thermal throttling. The effective power cost of AI therefore includes both computation and the infrastructure required to sustain that computation continuously.

Peak and average compute power serve different design purposes. Average consumption strongly influences battery runtime and mission energy, while peak consumption determines whether power distribution components can support sudden workload changes. Activating multiple neural networks, increasing GPU utilization, or launching intensive reasoning while motors are simultaneously accelerating can create system-level peaks. Compute scheduling must therefore consider the electrical state of the entire robot rather than the processor alone.

Static maximum-performance operation is rarely the most energy-efficient strategy for autonomous machines. Compute workloads can instead adapt to environmental complexity and uncertainty. Straightforward navigation through a predictable environment may require only lightweight perception and limited reasoning, while crowded, unfamiliar, or hazardous situations can activate richer models and higher inference frequencies. Adaptive computation allows electrical energy to follow the actual information-processing needs of the robot.

Dynamic power and performance management can extend this principle to processor configuration. Clock frequencies, accelerator power limits, workload placement, inference rates, model variants, and active sensor pipelines can be adjusted according to battery state, thermal headroom, mission urgency, and required latency. Rather than maintaining maximum compute capability continuously, the robot can expose additional computational performance only when the expected improvement in autonomy justifies its energy cost.

A useful system metric is therefore not simply maximum AI throughput, but useful intelligence delivered per unit of energy. Measurements such as inference per joule, task success per watt-hour, energy per processed frame, or mission-level energy per successful action can reveal whether additional compute actually improves Physical AI effectiveness. Such metrics connect neural-network optimization to the practical objective of completing physical tasks safely within limited onboard resources.

AI compute power consumption must ultimately be incorporated into the complete robot power budget rather than optimized independently. Increasing compute capability may improve perception and reasoning but can require a larger battery, stronger power electronics, additional cooling, and greater vehicle mass. Conversely, energy-efficient AI can release power and weight for sensing, actuation, payload, or longer runtime. Compute selection is therefore fundamentally a hardware-software-AI co-design decision.

The objective is not to minimize AI power at all costs, because insufficient computation can reduce perception quality, planning capability, responsiveness, and safety. The goal is to provide the required intelligence at the appropriate time while remaining inside electrical, thermal, and mission constraints. This makes AI compute power consumption a dynamic resource-management problem linking model design, accelerator architecture, workload scheduling, energy efficiency, and the physical behavior of the robot.

07.04. Sensor and Communication Power

Sensors and communication systems form a persistent part of the power budget in Physical AI because autonomous robots must continuously observe their environment and exchange information. Cameras, LiDAR, radar, IMUs, GNSS receivers, microphones, encoders, wireless radios, and network interfaces consume electrical power directly, while the data they generate or transmit also creates additional processing, memory, and communication workloads throughout the robot.

Sensor power cannot be evaluated only from the rated consumption of individual devices. A complete sensing pipeline includes the sensor element, illumination or active emitter, signal conditioning, embedded processing, interface electronics, synchronization, data transfer, and downstream computation. Consequently, increasing sensing capability may produce a larger system-level energy increase than the sensor specification alone suggests, particularly when many high-bandwidth sensors operate simultaneously.

Passive and active sensing modalities have different power characteristics. Cameras primarily consume energy through image sensors, onboard processors, interfaces, and sometimes illumination, while active sensors such as LiDAR and radar additionally expend energy generating optical or radio-frequency signals. The appropriate modality therefore depends not only on accuracy, range, and environmental robustness but also on the information obtained relative to its total energy cost.

Resolution strongly influences sensing power indirectly. A higher-resolution camera may require somewhat more device power, but its larger image stream also increases interface bandwidth, memory transfers, preprocessing, neural-network computation, and storage demand. Similar effects occur when LiDAR point density or radar resolution increases. Sensor specifications should therefore be evaluated together with the computational pipeline that consumes their data rather than as isolated hardware components.

Update rate creates another important energy-performance tradeoff. Sensors operating at high frequency provide more timely observations and can improve control of fast-moving robots, but they also generate more measurements per second. This increases sensor activity, data transfer, synchronization, preprocessing, and inference workload. Slow-changing environmental information may not require the same update frequency as obstacle avoidance, stabilization, or other safety-critical functions.

The number and placement of sensors also affect the overall energy budget. Physical AI platforms often use multiple cameras, LiDAR units, radar sensors, and proprioceptive devices to achieve spatial coverage and redundancy. Redundancy can improve robustness against occlusion or component failure, but every additional device adds direct consumption and downstream processing. Sensor architecture must therefore balance coverage, fault tolerance, information quality, bandwidth, compute load, and power.

Sensor interfaces contribute additional consumption that is sometimes overlooked. Ethernet, GMSL, USB, MIPI, CAN, and other interfaces require transceivers, switches, bridges, or controllers to transport measurements across the robot. High-rate multimodal systems can keep these components continuously active. Data movement between sensors, processors, and accelerator memory therefore becomes part of the effective sensing energy rather than merely an implementation detail.

Time synchronization can also introduce infrastructure requirements. Physical AI systems combining cameras, LiDAR, radar, IMU, GNSS, and actuator feedback need accurately aligned timestamps for reliable fusion. Precision Time Protocol, hardware triggers, synchronized clocks, GNSS timing, and associated network devices may consume relatively modest power individually, but they belong in the complete sensing and communication budget because reliable multimodal perception depends on them.

Communication power extends from internal robot networks to external connectivity. Internal communication transports sensor data, control commands, diagnostics, and AI outputs between distributed processors and controllers. External communication connects the robot with other robots, fleet servers, on-premise infrastructure, cloud services, operators, and positioning networks. Ethernet, Wi-Fi, cellular, private 5G, and specialized radios therefore represent both functional and energy resources.

Wireless communication consumption varies with traffic volume, transmission power, distance, signal quality, protocol behavior, and network conditions. Maintaining connectivity may require relatively moderate energy, while continuous transmission of high-resolution images, point clouds, or model data can substantially increase radio and processing activity. Poor signal conditions can further increase communication cost through higher transmission effort, retries, retransmissions, or prolonged connection times.

Communication and computation are closely coupled through workload offloading. Sending a computationally expensive task to an on-premise server or cloud platform may reduce local GPU activity and therefore save onboard compute energy. However, the robot must encode, transmit, receive, and sometimes buffer large quantities of data. Offloading is energy-efficient only when the reduction in local computation exceeds the additional communication and data-processing cost while latency and reliability remain acceptable.

Fleet-scale Physical AI adds another communication dimension. Robots may exchange maps, trajectories, detected hazards, traversability information, model updates, task states, or shared world representations. Such information can improve collective intelligence and prevent redundant computation, but unrestricted sharing can create unnecessary network traffic and energy consumption. Efficient fleet systems therefore transmit information according to relevance, novelty, urgency, and expected value rather than continuously sharing everything.

Adaptive sensing provides an important mechanism for reducing energy consumption. Not every sensor needs to operate at maximum capability in every situation. A robot moving through a predictable environment may lower camera frame rates, reduce LiDAR scanning activity, disable nonessential sensors, or use lightweight sensing modes. When uncertainty, speed, environmental complexity, or safety risk increases, richer sensing configurations can be activated dynamically.

Communication can be managed in a similar way. Noncritical telemetry, logs, training data, or map updates can be buffered and transmitted when network conditions or energy availability are favorable. Safety messages and operational commands, by contrast, require immediate and reliable communication. Classifying traffic by urgency allows the robot to preserve communication resources for critical functions while reducing unnecessary continuous transmission and associated power consumption.

Sensor and communication power management must preserve graceful degradation. Simply disabling devices to save energy may reduce perception coverage, localization accuracy, redundancy, or remote supervision below safe levels. The autonomy system should understand which sensing and communication capabilities are essential for the current operating mode. Reduced-power configurations must therefore be explicitly connected to corresponding limits on speed, task complexity, operating area, or autonomous capability.

Thermal effects should also be considered because sensors, networking equipment, and embedded processors convert electrical power into heat. Dense sensor clusters, high-power radios, and network switches installed inside sealed robotic enclosures can contribute to internal temperature rise. Their heat adds to that produced by AI compute and power electronics, increasing cooling demand and indirectly consuming additional energy through fans, pumps, or other thermal-management systems.

The most useful optimization metric is therefore not minimum sensor or radio power in isolation, but useful information delivered per unit of energy. A sensor consuming more power may be justified if it substantially improves safety or eliminates expensive downstream processing. Similarly, communication energy may be worthwhile when shared information prevents redundant exploration or computation. Energy efficiency must be evaluated according to the value of information for the robot's mission.

Sensor and communication power should ultimately be integrated with AI compute, actuation, thermal management, and auxiliary loads within the complete robot system power budget. Their direct consumption may sometimes be smaller than propulsion or high-performance computing, but their indirect effects can propagate through bandwidth, memory, processing, cooling, and runtime. Energy-aware Physical AI therefore co-designs sensing and connectivity according to information value, mission state, safety, and available energy.

07.05. Actuator vs Compute Energy Consumption

Actuator and compute energy consumption represent two fundamentally different uses of energy in Physical AI. Actuators convert electrical energy into physical motion, force, torque, or mechanical work, while computing hardware converts electrical energy into information processing for perception, prediction, planning, reasoning, and control. Their relative importance depends strongly on robot embodiment, mission, operating environment, and autonomy architecture.

Actuator energy is closely connected to the physical workload imposed on the robot. Mobile platforms must overcome inertia, rolling resistance, slopes, terrain deformation, and aerodynamic drag, while manipulators must move links, payloads, and tools against gravity and external forces. Motors, drives, transmissions, brakes, pumps, and associated power electronics therefore consume energy according to both commanded motion and physical interaction with the environment.

Compute energy follows a different pattern because it depends primarily on information-processing workload rather than mechanical load. CPUs, GPUs, NPUs, memory, and storage consume energy while processing sensor data and executing AI models. Increasing model size, inference frequency, sensor resolution, multimodal fusion, world-model prediction, or reasoning depth can increase compute demand even when the robot itself is physically stationary.

This distinction means that actuator and compute power profiles can vary independently. A stationary inspection robot may perform intensive visual analysis while consuming little propulsion energy, whereas a heavy transport robot climbing a slope may require large motor power while running relatively modest AI workloads. A mobile manipulator can experience both conditions simultaneously when navigating, perceiving, reasoning, and manipulating objects during the same mission.

Robot morphology strongly influences the balance. Wheeled robots operating on smooth surfaces can often move efficiently because rolling locomotion requires relatively little continuous mechanical work. Quadrupeds and humanoids may consume substantially more actuator energy because multiple joints continuously support weight, stabilize posture, and generate locomotion. Aerial robots can be even more actuator-dominated because propulsion must continuously generate lift to remain airborne.

Payload and terrain further shift the actuator side of the energy balance. Increasing payload raises the mechanical effort required for acceleration, climbing, braking, and manipulation. Rough terrain introduces wheel slip, repeated acceleration, suspension motion, or legged stabilization. Consequently, actuator energy should be estimated from realistic mission profiles rather than nominal motor ratings, because identical robots can exhibit very different energy consumption in different environments.

Compute consumption is similarly mission dependent. Simple localization and obstacle avoidance may require moderate processing, while high-resolution multimodal perception, dense occupancy estimation, long-horizon world modeling, foundation models, or Vision-Language-Action reasoning can create sustained accelerator workloads. The compute system may therefore become a significant fraction of total energy consumption as Physical AI platforms adopt increasingly capable onboard intelligence.

Comparing instantaneous power alone can be misleading because mission energy depends on both power and duration. A motor may briefly demand several times the power of the AI computer during acceleration but operate at that level for only seconds. A GPU drawing much less instantaneous power may run continuously for hours. Total energy consumption must therefore integrate each subsystem\'s power over its actual duty cycle throughout the mission.

Peak power creates another important distinction. Actuators commonly generate sharp electrical transients during acceleration, steering, lifting, or recovery from disturbances. Compute systems can also create workload-dependent peaks when accelerators become highly utilized. If these events occur simultaneously, their combined demand can exceed battery, BMS, converter, wiring, or connector limits even when average mission energy remains acceptable.

Actuator efficiency is determined by more than motor efficiency alone. Motor operating point, inverter losses, gearbox efficiency, friction, tire behavior, transmission design, regenerative braking, and mechanical architecture all influence the energy required for useful motion. Poorly selected gearing or inefficient trajectories can waste substantial energy. Mechanical and control optimization can therefore increase runtime without changing battery capacity or reducing AI capability.

Compute efficiency can be improved through an analogous set of software and hardware techniques. Quantization, pruning, sparsity, model distillation, efficient attention, reduced inference frequency, accelerator-aware model design, and heterogeneous computing can reduce energy per inference. Workloads can also be assigned among CPUs, GPUs, and NPUs according to their characteristics, allowing the robot to obtain required intelligence without operating its highest-power processor continuously.

The relationship between actuator and compute energy is not purely competitive because better computation can reduce mechanical energy consumption. AI can select smoother trajectories, avoid unnecessary acceleration, predict terrain difficulty, optimize velocity, reduce wheel slip, coordinate joints, and choose efficient manipulation strategies. Additional computation may therefore be worthwhile when the energy spent on reasoning produces a larger reduction in actuator energy or improves mission success.

The opposite interaction is also important. Excessive reasoning can consume energy without producing meaningful physical benefit. Repeatedly evaluating similar trajectories, processing unchanged observations at maximum frequency, or continuously running large models in simple environments may waste battery capacity. Physical AI should therefore increase computational effort when uncertainty or task complexity justifies it and reduce computation when additional reasoning provides little actionable information.

This creates an energy allocation problem between thinking and acting. During difficult manipulation, navigation, or uncertain terrain traversal, investing more energy in perception and prediction may prevent costly physical mistakes. During straightforward motion, lightweight computation may be sufficient and more energy can remain available for locomotion. The optimal balance is dynamic rather than a fixed percentage assigned permanently to actuators or compute.

Thermal constraints further couple the two domains. High motor currents generate heat in motors, drives, batteries, and power electronics, while intensive AI workloads heat processors and memory. Both heat sources may share the robot\'s cooling capacity and enclosure. Simultaneous high actuation and high computation can therefore create a thermal limit even when sufficient electrical energy remains available, reducing sustainable system performance.

Energy-aware scheduling can manage these interactions at runtime. The autonomy system can monitor battery state, motor demand, compute utilization, temperature, mission progress, and environmental complexity. It can then modify velocity, acceleration, inference frequency, model selection, sensor activity, or reasoning depth. Such coordination prevents one subsystem from consuming resources without considering the requirements and constraints of the rest of the robot.

A useful evaluation should therefore distinguish actuator energy, compute energy, sensing and communication energy, thermal-management energy, and auxiliary consumption while still treating them as one integrated budget. Metrics such as watt-hours per kilometer, joules per manipulation, energy per inference, and total energy per successful task reveal different aspects of efficiency, but mission-level success per unit energy provides the broader Physical AI perspective.

The objective of hardware-software co-design is not to minimize either actuator or compute consumption independently. A robot with extremely low compute power may lack the intelligence required for safe and efficient action, while a highly intelligent robot with inefficient mechanics may waste most of its battery performing physical work. The desired architecture balances mechanical efficiency and computational intelligence within the shared energy envelope.

Ultimately, actuator and compute energy should be understood as coupled investments toward successful physical behavior. Actuation spends energy to change the world, while computation spends energy to decide how that change should occur. Effective Physical AI dynamically allocates energy between these functions so that sufficient intelligence produces efficient action, and efficient action preserves the energy required for continued intelligence, safety, and mission completion.

07.06. Battery Capacity and Runtime

Battery capacity and runtime define how long a Physical AI robot can sustain useful autonomous operation before energy must be replenished. Battery sizing cannot be reduced to selecting the largest practical energy pack, because capacity influences mass, volume, cost, payload, charging time, thermal behavior, and vehicle dynamics. The correct battery must support the required mission while remaining compatible with the robot's overall hardware-software architecture.

Battery capacity is commonly expressed in ampere-hours, while stored energy is more directly represented in watt-hours. For an approximate calculation, nominal energy can be obtained from battery voltage multiplied by ampere-hour capacity. However, this nominal value does not represent the energy that can always be delivered to the robot because operating voltage, discharge limits, conversion losses, temperature, aging, and battery protection reduce usable capacity.

Runtime can be estimated conceptually by dividing usable battery energy by average system power. This simple relationship is valuable for early architecture studies, but its accuracy depends strongly on the quality of the average-power estimate. Robots rarely consume constant power. Propulsion, manipulation, AI compute, sensing, communication, cooling, and auxiliary electronics change their consumption according to operating state, so mission runtime must ultimately be calculated from realistic duty cycles.

Usable energy should therefore be distinguished from nominal battery energy. A robot generally should not plan to consume the battery from its theoretical full state to complete depletion. Battery-management limits, required state-of-charge reserve, safe shutdown energy, return-to-charge requirements, and battery-life considerations reduce the energy available for normal missions. A capacity calculation based only on the battery label can consequently overestimate practical runtime.

The mission profile determines how stored energy is converted into operating time. A robot may spend part of its mission waiting, another period navigating, another performing manipulation, and another executing high-load perception or communication. Each state has a different power demand. Mission energy is obtained by combining the power and duration of these states, making duty-cycle analysis more representative than assuming a single continuous maximum or minimum load.

Actuation often creates the largest variation in runtime. Robot mass, payload, velocity, acceleration, slope, terrain resistance, manipulation force, and mechanical efficiency determine how much energy is required for physical wo...