Polymorph/Physical AI, ExplainedGlossary

Physical AI, Explained · Part 5

Hardware

Read this part in the book →

Robot hardware has matured to the point where it is adequate for many commercial tasks, yet every major subsystem still carries characteristic weaknesses. This part examines those subsystems in turn: how a robot's body is described, what its joints are made of, why hands remain difficult, which senses it relies on, what shape it should take, where its computation runs, what it takes to certify it, and how it fails once deployed.

5.1 Embodiment and degrees of freedom

Embodiment refers to the specific physical robot a model controls: its geometry, its joints, its sensors and the limits of its motors. A policy trained on one embodiment does not automatically transfer to another, because the same intended motion requires different joint commands on a body with different link lengths or joint layouts.

Degrees of freedom (DoF) are the number of independent ways a joint or a whole system can move. An elbow hinge has 1, a human shoulder has 3, and a human hand has roughly 20 or more. A conventional industrial arm has six, which is the minimum needed to place a tool at any position and in any orientation within its reach; an arm with more joints than the task requires is called redundant, and the spare freedom lets it reach around obstacles or choose a more comfortable posture for the same tool position. One semi-humanoid robot adds four DoF in its waist alone.

Each additional degree of freedom brings dexterity at a price. It adds a motor, a gearbox, a sensor and wiring, all of which cost money and can fail. It also makes control harder: computing the joint angles that produce a desired hand position, the problem of inverse kinematics, has more solutions to choose between as DoF increase, and a learned policy must output a longer action vector and learn how the joints interact. The count is also not fixed for the life of the machine. When a joint fails in the field, a 32-DoF robot becomes a 30-DoF robot, and its software must either compensate or stop (3.10).

5.2 Actuators and component cost

An actuator is the robot's equivalent of a muscle and joint combined. It integrates an electric motor, a transmission (usually gears), one or more sensors and the control electronics that convert electrical power into precise motion. The bill of materials (BOM) lists the cost of every physical part in a product. Actuators make up 30 to 50 percent of a humanoid's BOM, and their basic design has barely changed in 50 years.

The central design choice in an actuator is the transmission. Electric motors spin fast with little torque, while joints need to move slowly with a lot of torque, so a gearbox trades speed for torque by its gear reduction (the ratio of motor turns to output turns). The common families are these:

The trade-off runs along a single axis. High reduction gives precision and strength in a small motor but makes the joint stiff, frictional and hard to backdrive, so contact forces are hard to sense and collisions are hard to absorb. Low reduction gives compliance and good force sensing but needs a heavier motor and runs warmer. Designs that need both often add a dedicated joint torque sensor at the output, or a deliberate spring in series with the gearbox (a series elastic actuator), whose measured deflection gives the force directly.

Actuator choice also determines how faithfully the robot can be modelled and simulated. Friction, backlash and gear compliance are difficult to capture in a physics engine, so a simulation of a stiff, high-reduction joint may diverge from reality in exactly the contact-rich moments that matter. For this reason some teams design their own actuators specifically to be easy to model. That reasoning suggests a general rule for building versus buying. Buy any component with clear inputs and outputs and mature suppliers, such as lidar developed for self-driving cars or many cameras. Build any component that determines how well the whole system performs, because the hardware ultimately carries the intelligence: a model can only exploit the precision, compliance and sensing the body provides.

Why it matters: A component that accounts for up to half the cost of a humanoid and has barely changed in decades is a direct drag on margins, and for the same reason it is one of the clearest openings for investment and new design.

5.3 Hands and dexterity

Hands are the hardest part of robot hardware to build. A dexterous hand must pack many small, precise actuators, transmissions and sensors into a volume the size of a human hand, survive years of repeated loading and impact, and still perform delicate work. Few engineers have the combination of mechanical, electrical and manufacturing skills needed to build one.

Designers handle the space problem in a few standard ways. Some place motors in the forearm and route force to the fingers through tendons (cables running over pulleys), as the human hand does with forearm muscles; this keeps the fingers light but introduces cable stretch, friction and wear. Others put small motors directly in the fingers, which simplifies the mechanics but adds mass and heat at the fingertips. Many hands are underactuated, meaning they have fewer motors than joints and use linkages or springs so that the fingers curl and conform around an object passively. Underactuation trades individual joint control for simplicity and gentle adaptive grasps.

Human grasps remain the benchmark and are still only partly understood. They are strong yet compliant, stable under disturbance, and continuously adjusted using touch, in ways that current science cannot fully explain or reproduce. Heat is a practical limit as well: today's best dexterous robot hands overheat under sustained load, because small motors held at high torque dissipate heat in a tiny volume, and engineers have cooled them with bags of ice. Some teams therefore use simple parallel-jaw or suction grippers, because no available dexterous hand survives the duty cycle of a factory, and a hand that did would find buyers immediately.

The debate: One view holds that hands are an excuse for why general-purpose robots have not arrived, and that the intelligence controlling them is always the real limit; the other holds that dexterity is the most valuable problem as well as the hardest, because solving it unlocks an enormous range of tasks. Both can be true: hands are not yet durable enough for many deployments, and the model remains the main limit on what robots can do.

5.4 Sensors

Robots perceive the world through two broad classes of sensor. Proprioceptive sensors measure the robot's own state: joint encoders report angles, motor currents indicate effort, and an inertial measurement unit (IMU) combines accelerometers and gyroscopes to track orientation and acceleration. Exteroceptive sensors measure the environment: cameras, depth sensors, lidar, microphones, force/torque sensors (usually mounted at the wrist, measuring the forces and twisting moments the hand experiences) and tactile sensors (skins or fingertip pads that report pressure, contact location and sometimes slip).

One early research platform used three cameras, one on each wrist and one at the base, with no touch or force sensors at all. The choice was deliberate, based on the hypothesis that a good learning method can compensate for deficient sensing. Wrist cameras partly substitute for touch: when the gripper presses on an object, the camera sees it deform, slide or tilt, and a learned model can infer from those visual cues how hard it is squeezing.

Cheaper rigs push the same idea further. An omelette-making setup costing about $4,000, using inexpensive arms with a camera as the only sensor, cracks and whisks eggs after training on less than 10 hours of data, judging force from vision alone (a reported result). Results like this suggest that better intelligence could extract far more from existing sensors than current robots do.

The limits of vision are equally well understood. Cameras suffer occlusion (the hand itself blocks the view of the contact it is making), struggle with transparent and reflective objects, and degrade in poor lighting. Touch fills those gaps: it reports contact directly and early, before an object has visibly moved, which is when a slip can still be corrected. Tactile sensing has been slow to spread because skins are fragile, need dense wiring, and lack a standard data format that learning methods can easily consume.

The debate: Relying on cameras alone is a bet. Humans also hear, feel and smell, integrating all of it without noticing, and video is highly redundant, since neighbouring pixels and consecutive frames are nearly identical, while touch may carry far more task-relevant information per byte; by one estimate, a model using vision plus touch could be 100x more data efficient. Some teams already add infrared sensors, for example to judge how well food is cooked, and the practical course is to start with few sensors while watching for tasks where a missing sense caps performance.

5.5 Form factors: wheels, legs and humanoids

A robot's form factor is its overall body plan. Humanoids are not the right shape for every robot, and the choice involves trade-offs in stability, energy, cost and the range of tasks the body can reach: - Wheels make sense for now. A wheeled base is statically stable: it stays upright with the motors switched off, because its centre of mass sits over its support. A legged robot is dynamically stable at best, meaning it stays up only while its controller keeps acting, so a software fault, a power loss or an unexpected push can bring it down. For that reason a first home robot should have wheels and two arms, so that it cannot fall and injure a pet or a child. Legs also consume more energy, since they must support the body's weight continuously even when standing still. Demonstrations in which a robot recovers from being pushed show good balance control, which says little about readiness for useful work. - A human-like upper body on a wheeled base. One semi-humanoid robot mounts a human-shaped upper body on wheels, with a waist that has four joints. People bend, twist and lean constantly without noticing, a fact that becomes obvious only when a stiff neck takes the movement away, and human video is full of that motion. A flexible waist lets the robot reproduce postures seen in human demonstrations and extends the reach of its arms, from the floor to a high shelf, without legs. - Humanoids are the likely long-term shape, reached in stages. Homes, factories and tools are built around human bodies, so a general-purpose robot that must use them will probably converge on a humanoid form; a human-like body also makes human video and teleoperation data easier to map onto the robot. Hardware decisions are slow and expensive to reverse, however, so some teams deploy a simpler body with customers now instead of spending years perfecting the final design. - Fleets will mix robot types. No single robot type is likely to dominate. Fixed arms will stay in factories, four-legged robots will handle inspection on rough terrain, humanoids will take some jobs designed around people, and wheeled carts will move goods, with a single model potentially controlling all of them. Models trained across many embodiments are an active research direction precisely because of this mix. - Take risk in only one place. One approach is to buy commercial robot arms, already shown to be capable enough through teleoperation, and build only the grippers and data-capture devices, so that all the engineering risk sits in the part that actually differentiates the product.

Why it matters: The right body is the simplest one that can perform the valuable task; every extra joint, leg or sensor adds cost and failure points that must be justified by work the robot could not otherwise do.

5.6 Onboard vs. offboard compute

Onboard compute means the model runs on processors inside the robot. Offboard compute means it runs in a remote data centre (the cloud) or a nearby server and exchanges observations and commands with the robot over a network. The choice affects cost, power consumption, latency and safety, and it is one of the most actively debated questions in the field.

Any approach must respect a layered timing structure. The lowest layer, the motor control loop that holds each joint at its commanded position or torque, runs on dedicated electronics at hundreds of hertz to a kilohertz and is always local. The question is where the higher layers, the learned policy and any reasoning model, should run. The main positions are these: - Cloud with action chunking. The model predicts a short sequence of future actions at once, a technique called action chunking. It begins computing the next sequence while the robot is still executing the current one, called real-time chunking, and the new chunk is blended in smoothly when it arrives. Network delay is thereby hidden inside the buffer of actions the robot already holds, as long as the delay is shorter than the chunk. This avoids an expensive, power-hungry computer on the robot, and the robot's hardware does not become obsolete as models grow larger. Teams using this approach run it in production for laundry, coffee making and navigation. - On the robot. Other teams, along with safety-critical driving systems, keep the model on the robot. A falling robot has no time to consult a server, and a robot holding a knife cannot freeze for three seconds without alarming the people around it. Networks cannot guarantee timing, because packet loss, congestion and outages are unpredictable, so these teams train a large model and then distill it: they train a smaller model to imitate the large model's outputs, producing a policy compact enough to run on the robot's own processors, usually with some loss of capability. - Split by speed. Some teams run fast reflexes, operating on a timescale of milliseconds, on the robot, and run slower reasoning about what the robot sees in the cloud, about once a second. The slow layer chooses goals and sub-tasks; the fast layer turns them into motion and reacts to contact. This mirrors the general hierarchical design of robot control, in which each layer runs at a rate matched to how quickly its decisions go stale. - Connectivity sets a ceiling. Many warehouses barely have internet access, with dead zones among metal racking, which limits how much any robot there can rely on the cloud.

Resolution: Decide by how sensitive the task is to delay, how much safety depends on the response, and how reliable the site's connection is. Fast or safety-critical control belongs on the robot, and slower planning can run elsewhere.

5.7 Redundancy, validation, and homologation

Removing the human operator completely, for example from a truck, requires hardware as well as software. The vehicle needs fully redundant steering and braking, meaning duplicate, independent systems so that the failure of one leaves the other able to stop or steer the vehicle safely, and each system must be independently tested and approved. This hardware is often not mass-produced, and getting it approved can take longer than building the software. Homologation is the regulatory approval a vehicle or component needs before it can be sold in a given market.

The same logic applies to any robot working near people, under the discipline of functional safety: the engineering practice of ensuring that a system responds correctly and predictably when something goes wrong. Its core method is to identify hazards, estimate their severity and likelihood, and assign each safety function a required level of reliability. Safety functions are typically implemented in certified, often duplicated hardware and simple software that sit beside the learned model and can override it. Common examples include an emergency stop wired directly to the motor drives, safe torque off (a hardware-enforced cutoff of motor power), limits on joint speed and force near people, and monitoring that slows or stops the robot when a person enters its workspace. A learned policy is not certified as safe in its own right; the system is made safe by bounding what the policy is permitted to do.

Validation is the evidence that the system meets those requirements: test campaigns, fault-injection trials in which components are deliberately disabled, and documentation that an independent assessor can audit. Because a neural network's behaviour cannot be exhaustively verified, this evidence leans on the surrounding safety layer and on extensive statistical testing.

Why it matters: For any pilot near people, safety engineering and hardware approval, more than the model, will usually consume most of the schedule, and visibly treating that work as a priority builds credibility with partners and investors.

5.8 Real-world failure modes

Deployed hardware fails in mundane, physical ways. Cameras and lidar overheat in enclosed spaces, sensors drift out of calibration as mounts loosen or temperatures change, so that a camera's estimate of where an object sits slowly diverges from where it actually is, and fog, dust, glare or steam confuse perception. Actuators wear: gear teeth develop backlash, bearings loosen, and motors run hotter as friction rises, which changes the dynamics a policy learned on a fresh machine.

Robots also lack a shared operating system of the kind phones and browsers rely on. Each platform has its own drivers, communication protocols and safety interfaces, so a company that runs on many kinds of machine must build and maintain that software layer itself. One autonomy software company runs on more than 50 platforms.

Problems can sit deep in the system and present themselves far from their cause. A model may appear to fail because of a training setting when the real fault is in the hardware: in one case the fingers left a small gap when commanded to close fully, because a connector had been attached incorrectly, and the policy's dropped objects looked like a learning problem. Diagnosing such faults requires tracing an observed behaviour back through software, firmware, wiring and mechanics. The most valuable trait in robotics engineers is therefore attention to detail across every level of the system, from tightening gripper screws to training models on thousands of GPUs.

Supply chains add a further layer of risk. The permanent magnets in electric motors depend on rare-earth materials sourced from very few countries, which exposes every actuator to concentrated geopolitical and price risk, and moving hardware production back to the US is much harder than it appears, because the specialised suppliers, tooling and manufacturing expertise have accumulated elsewhere over decades.


← Part 4. Data, simulation and world models   Part 6. From demo to reliable product →