T ThinkEdge Learn

Physical AI: Intelligence That Has to Act

A chatbot that gives a bad answer costs you a rephrase. A physical AI that gives a bad answer drives a motor into a wall. That single difference changes the whole design.

physical ai physical ai robots embodied ai
AI and Electronics · Splitting the model, the controller and the feedback

What makes AI physical

The difference between a wrong sentence and a wrong motor command changes the design completely. The model is allowed to choose what should happen, but a separate controller is allowed to refuse: the controller holds the limits, and the model's output is treated as a request the controller can reject. That is the most important architectural habit in any physical AI project, and it costs about ten lines of code.

There is a second, less obvious difference. Text is reversible, a motor is not. A robot that pushes against an obstacle loads the gearbox, heats the motor and drains the battery, and none of that shows up as an error message. Physical systems also have state nobody wrote down: friction, backlash, the texture of the floor. A physical AI has to cope with a world that does not hold still between two samples.

The three jobs in every physical AI

Split the system into three parts and it stops being mysterious. The model is the planner, and it decides what the goal is, for example follow the light. The controller is the low-level loop that holds a setpoint, for example the PWM duty cycle that puts the sensor on the light. The sensors close the loop back to the planner. Each part runs at a different rate: the planner at a few hertz, the controller at hundreds, the sensors at kilohertz.

Almost every failed student robot tries to put all three in one loop, and the servo twitches because the planner and the controller are fighting over the same variable. Split them, run each at its own rate with millis(), and the same hardware starts working. The projects below are ordered in exactly that way, because a planner built on a controller that does not work yet tells you nothing about the planner.

Step by step

  1. Start with the part that is easy to control

    A fan or a servo responds predictably and cannot be damaged by a bad decision. Get the whole loop working on it before anything with wheels.

  2. Write the controller first

    On-off, then proportional, then PID if you need it. Know how the output behaves before you let anything else change it.

  3. Add the sensor that closes the loop

    One sensor whose reading you can compare against a setpoint. Log both numbers so you can see the error you are trying to reduce.

  4. Give the planner a menu, not raw control

    Let the higher level choose between track, stop and search. Letting a model write raw motor values is how things break.

  5. Enforce the limits below the planner

    Clamp the angle and the speed in the controller code, and add a physical limit switch for the one axis that could hurt someone.

  6. Test the failure case first

    Unplug the sensor mid-run and confirm the robot stops rather than spinning. A physical AI that is only tested when everything works has not been tested.

What you'll need

ItemQtyWhy
Arduino Uno R31Enough pins and timers for a closed loop at 16 MHz, and the board most students already own.
SG90 micro servo2A safe first actuator, with a limited range and no free-running wheels, and easy to mount to a sensor.
Light-dependent resistor1The light source the tracker follows, and an analogue input whose error curve you can plot.
HC-SR04 ultrasonic sensor1Distance feedback for the second axis of the tracker, and the reading the planner uses.
L298N dual H-bridge module1Drives small DC motors with current that an Arduino pin cannot supply on its own.
Pushbutton1A manual stop that works even when the code does not, which is the point of a stop button.

Practise it before you build it

Every step above has a matching circuit in the ThinkEdge Learn simulator. The simulator runs a real Arduino sketch against a modified-nodal-analysis solver, so digitalWrite actually drives the LED on screen and the readings change when you change the wiring — no hardware, no burnt components.

Common questions

Do robots need AI to work?

Most industrial robots do not. A robotic arm on an assembly line runs the same fixed program thousands of times a day, and that is exactly why it is fast and reliable. AI earns its place when the world varies: a crate that is not always in the same place, a light that moves, a surface that is wet. If your project has a fixed environment, plain control logic will usually do better.

Is a humanoid robot the same thing as physical AI?

No. A humanoid is a shape, physical AI is a capability. A tracked robot can do physical AI perfectly well, and a humanoid walking on flat floor with no disturbance is mostly a control problem with a very hard actuator budget. Judge a physical AI project by how well it handles something unexpected, not by how human it looks.

How much does a physical AI project cost?

A solar tracker with a servo and two sensors runs about $35 to $60 in parts: $12 to $20 for the board, $5 to $10 for the servo, $3 to $6 for the light sensor, $4 to $8 for the ultrasonic sensor, and the rest on wires and a stand. The controller is the project. The hardware is the cheap part.

Related guides

Edge AI: Decisions Made on the DeviceEdge AI runs the decision on the device instead of in the cloud. Here is what that buys you in latency and privacy, and what a 32 KB microcontroller can really do. What an AI Agent Actually IsAn AI agent is a loop of model calls, tools and memory. Learn how that loop maps onto the sense, decide, act cycle of a robot you can build this term. AI Swarm: Many Small Robots, Three RulesA swarm is not a clever algorithm, it is three local rules. Learn separation, alignment and cohesion, then build them as if-statements on an Arduino. Robotics and Autonomous Systems: The Four Sub-AreasRobotics and autonomous systems split into perception, planning, control and SLAM. Here is what each needs, and which parts an Arduino can reach. Humanoid Robots: Balance First, Walking SecondWhat makes a humanoid robot work: inverted-pendulum balance, joint torque budgets and centre of mass, plus the Arduino projects to get you there.

Try the full simulator with your class

103 guided circuit projects, 21 lessons and an in-browser Arduino simulator. The first 15 projects are free, no account needed. NCERT Science mapping on 47 projects, with Arabic and English copy in the regional builds.