Introduction: Why Robotics, Why Now Robotics is everywhere. Over the years we have seen products from the Romba, to Boston Dynamics dog to self-driving cars and now humanoid robots. This robots are made to handle differenet circumstances then a automationous machine in a factory. They go through differenet process to make them into what they are. Using fundamentals and concepts to help shape how each robot works. So weither you are a hobbyist, a student or a merely curious, in this post we will discuss the core concepts of robotics. Robotics Concepts for Beginners What Is a Robot, Really? Oxford diconary defines robot as "a machine that can perform a complicated series of tasks by itself". This is the very basic idea of a robot. Robots can complete tasks that a automatious machines can't do. Robots can think and decide on what they need to do and how to act apon that. So what counts as a robot then? Does a dishwasher count? No, I wouldn't think so. A dishwasher has set programs, it does count if there is 1, 5 or 30 dishes. Maybe a smart thermostat? Well it can detect if a room is colder or hotter then x amount and change accordingly so it must be a robot. Well a thermostat can't tell if the outside world is summer or winter. It can't tell if you the individual is roasting or shivering in their room. It cant't tell if their is people even in the room for there to be a need to be on in the first place. The user still has to control it. Take a Roomba for an example. A Roomba can clean a house unsupervised at a desired timed. A Roomba uses multiple sensor and trained data sets to learn and understand it's envirnoment. It maps your floor layout and will clean surfaces based on that. However let's say one day you deciede that you want to move your couch or you left a box in the middle of your living room. A Roomba has the ablility to notice that the floor plan has changed and is able to make the decision to go around that object. A user just has to set it up, pick a time and let the robot doe it's magic. The Three Building Blocks: Sensors, Actuators, and Control A robot only really needs three things. It needs a way to take in information about the world, a way to physically do something about it, and something in the middle that decides what that something should be. Sensors, actuators and a controller. Every robot you have ever seen is some version of those three parts bolted together. Sensors are how a robot perceives. A camera gives it sight. An ultrasonic sensor or a lidar unit measures distance by firing out a signal and timing how long it takes to bounce back, which is how your Roomba knows the wall is 30cm away and not 3cm. A bump sensor is about as simple as it gets, it is a switch that gets pressed when the robot physically walks into something. A gyroscope tells the robot which way is up and how fast it is tipping over, which is the only reason a two wheeled balancing robot stays upright at all. Actuators are how a robot moves and acts. If sensors are the senses, actuators are the muscles. Motors spin the wheels. Servos rotate to a specific angle and hold there, which is what you want in a joint or a steering mechanism. Grippers open and close so the robot can pick things up. On their own they are dumb lumps of metal, they just do what they are told. The controller is the brain, and it sits between the two. It reads what the sensors are saying and it commands the actuators to respond. For beginners this is almost always an Arduino or a Raspberry Pi. An Arduino is a microcontroller, it runs one small program over and over forever with very precise timing and no operating system to get in the way. A Raspberry Pi is a full computer running Linux, so it can handle cameras, vision and networking, but it is worse at the kind of split second timing that motors like. So put it together with a robot that stops before it hits a wall. The ultrasonic sensor reports that the wall is 20cm away. The controller checks that number against a rule you wrote, something like "if the distance is under 30cm, stop". The controller then cuts power to the motors. Sense, decide, act. That is the whole loop, and it is running dozens of times a second. How Robots "Think": Control Loops and Feedback Forget robots for a second and think about driving down a road. You are not holding the wheel perfectly still. You are constantly looking at where the car is in the lane, noticing it has drifted slightly right, and nudging the wheel back left. Then you check again. That constant cycle of look, compare, correct is a feedback loop, and you run one every time you drive. Robots do the same thing, and the difference between a good robot and a frustrating one usually comes down to whether it bothers to check its own work. Open loop control is acting blindly. You tell the robot to drive forward for three seconds and you hope that gets it where you wanted. It has no idea whether it actually moved. If a wheel slips on a rug or the battery is a bit low, the robot has no clue and no way to fix it. Closed loop control is when the robot checks. It drives forward, reads a sensor, sees that it has only travelled half as far as it should have, and keeps going until the sensor agrees with the goal. You will eventually run into something called PID control, and all it really is is a clever recipe for deciding how hard to correct when you are off target, so the robot does not overshoot and wobble back and forth forever. Do not worry about the maths yet, just know the name so it is not scary when you meet it. Making Robots Move: Kinematics and Degrees of Freedom Hold your arm out in front of you. Your shoulder can swing your arm up and down, side to side, and rotate it. Your elbow bends one way. Your wrist bends, tilts and twists. Every one of those independent movements is a degree of freedom, and your arm has around seven of them. That is why you can reach around a corner to grab a mug, and why a cheap robotic arm with three joints cannot. Degrees of freedom is just a way of asking how many different ways a robot's body can move through space. Kinematics is the follow on question, if I move this joint by this much, where does the hand end up? Different bodies are good at different jobs. A wheeled robot is simple, cheap, efficient and stable, and it is completely useless the moment it meets a set of stairs. A legged robot can handle rough ground and steps, but it is far more complicated, it burns through battery, and it spends most of its processing power just not falling over. A robotic arm does not go anywhere at all, it stays bolted to one spot and does precise repeatable work in the space it can reach, which is exactly what a factory wants. If you are starting out, start with wheels. The Software Side: Programming and a Word on AI Programming a robot sounds intimidating until you realise what you are actually writing. You are writing the rules for the sense, decide, act loop. Read this sensor. Compare it to this number. Turn this motor on or off. That is it. The complexity comes later from stacking a lot of small rules on top of each other. There are a few sensible places to start. Block based coding, the Scratch style drag and drop stuff, is genuinely good for getting the logic into your head without fighting semicolons. Python is where most beginners land next, because it reads almost like English and both the Raspberry Pi and most hobby kits support it. ROS, the Robot Operating System, is the thing to graduate toward, it is a framework that handles the messy plumbing of getting sensors, motors and vision talking to each other on serious robots. One thing worth clearing up early. Not every robot uses AI, and the two words are not interchangeable. A line following robot is following a fixed rule you wrote by hand, if the left sensor sees dark, turn left. It will do that same thing perfectly forever and it will never get better at it. A robot using machine learning is different, it has been shown thousands of examples and has worked out its own rules from them, which is how a robot can recognise a cat sitting in the hallway when nobody ever wrote a rule describing a cat. Most hobby robots are the first kind, and that is completely fine. Types of Robots You'll Encounter Type What it does Where you'd see it Beginner friendly? Industrial arms Repeat precise movements all day Car factories, packing lines No, but small desktop versions exist Mobile robots Move around a space on wheels or tracks Vacuums, warehouse bots, delivery bots Yes, this is the usual starting point Humanoids Balance and move like a person Research labs, tech demos No, very hard and very expensive Drones Fly and carry a camera or payload Filming, surveying, agriculture Yes, and cheap kits are everywhere Educational kits Teach the fundamentals in a box Classrooms, your kitchen table Yes, start here If you are buying or building your first robot, you are realistically choosing between a mobile robot, a small drone or an educational kit. Everything else is something to admire on YouTube for now. Getting Hands-On: How a Beginner Actually Starts Buy a kit. I know it feels like cheating, but sourcing your own motor driver, working out why it is drawing too much current and discovering three weeks later that you bought the wrong voltage regulator is not learning robotics, it is learning procurement. A kit gives you parts that are guaranteed to work together, so when something breaks you know the problem is your code and not your shopping. An Arduino starter kit, a Raspberry Pi kit or a LEGO Mindstorms style set will all do the job. For a first project, build an obstacle avoiding car. It is two motors, one ultrasonic sensor, a controller and a chassis. The robot drives forward until the sensor says something is close, then it stops, turns and carries on. It sounds trivial, and it teaches you almost everything from this post at once. You will wire up a sensor and read real values off it. You will drive a motor. You will write the sense, decide, act loop yourself. You will discover that the sensor gives you a mad reading now and then and you need to handle it. That last one is the real lesson. For free learning, the Arduino Project Hub and the official Arduino docs are worth your time, and the Raspberry Pi Foundation publishes free beginner projects on their site. On YouTube, DroneBot Workshop is excellent for the electronics side and James Bruton is great for watching someone build ambitious things and hit problems out loud. For getting unstuck, r/robotics and the Arduino forums are active and generally patient with beginners. Now set your expectations. Your first build will not work. Something will be wired backwards, a motor will spin the wrong way, or the robot will drive confidently into a wall while the sensor swears it is clear. This is normal and it is the job. The people who get good at this are not the ones who got it right first time, they are the ones who found it funny enough to try again. Common Beginner Misconceptions "Robots are basically like the movies." They are not. Real robots are narrow and a bit stupid. The most advanced humanoid in the world would struggle to make you a cup of tea in an unfamiliar kitchen. "You need to be a maths genius." For your first year, you need to be able to compare two numbers and know what an average is. The heavy maths shows up in advanced control and motion planning, and by the time you need it you will actually understand why. "Robots and AI are the same thing." A robot is a body that senses and acts. AI is one possible way of doing the deciding part. Plenty of robots use no AI at all, and plenty of AI never touches the physical world. "It is too expensive to start." A decent Arduino starter kit with motors and sensors costs less than a night out. The expensive part of robotics is the stuff you do not need yet. Conclusion: Your Next Step Strip everything else away and this is the mental model you keep. A robot senses the world, decides what to do, then acts on it, and it does that over and over. Sensors, controller, actuators. If you can point at those three things on a machine, you understand its basic shape. So here is the next step. This week, order an Arduino starter kit and build the obstacle avoiding car. Do not read another ten articles first. Get the thing on your desk and get it driving into a wall, then fix it. If you do build it, leave a comment and tell me what went wrong first. It is always something.