Robotics for Beginners: From a First LED to a Robot with Sensors

Many robotics learners start with block programming, dragging coloured commands together in MakeCode for the micro:bit or in a block robot app. Blocks remove semicolons and typos from the picture, so attention goes to the logic itself: sequence, repetition and decisions. The micro:bit suits this stage well because the board already carries a 5x5 LED matrix, two buttons, a motion sensor, a compass and a temperature sensor, so the result of any code is visible without wiring anything.

The smoothest route into text code is a bridge MakeCode already provides: any block program can be opened as JavaScript or Python on the same screen. A useful drill is to build a program in blocks, switch to text view, change one number in the text and watch the blocks update to match. After that the learner is ready for Arduino sketches in a C++ style language, where every statement ends in a semicolon and every block of code sits inside curly braces. Python returns later at the Raspberry Pi stage.

Teenagers and adults who have written code before can skip the block stage and go straight to Arduino. Younger learners usually need a few weeks with blocks before loops and conditions feel natural. The signal that a learner is ready to move on: they can describe their program in their own words, including why one block sits inside a loop and another sits outside it.

An Arduino Uno pin puts out 5 volts, while a typical red LED uses around 2 volts and a current in the low tens of milliamps. With nothing to limit it, current flows as hard as it can, the LED heats up and the board's pin takes the strain. A resistor in series with the LED sets the limit. The sum uses Ohm's law, current equals voltage divided by resistance: the remaining 3 volts across 220 ohms gives about 14 milliamps, comfortable for both the LED and the pin. That is why 220 ohm resistors turn up in nearly every starter kit.

Learners need to recognise the LED's legs. The longer leg is the anode and goes towards positive, and the flat edge on the LED's rim marks the cathode. An LED fitted backwards simply stays dark without damage, which makes this a safe mistake to discover alone. Reading resistor colour bands is worth practising too; a 220 ohm resistor is banded red, red, brown. A multimeter confirms the value when the bands are hard to read under a desk lamp.

The follow-up drill is to swap in 330 ohms and then 1 kilohm while watching the LED dim, writing down the current calculation for each value. Secondary students usually meet Ohm's law in science class, and robotics gives them a place to use it for real. The sign of understanding: the learner can explain why two LEDs wired in parallel should each get their own resistor.

Pins A0 to A5 on an Arduino Uno turn a voltage between 0 and 5 volts into a whole number from 0 to 1023, because the analog-to-digital converter has 10-bit resolution. A potentiometer turned fully one way reads 0 and close to 1023 the other way. A light-dependent resistor wired with a fixed resistor forms a voltage divider, so its number rises and falls with the brightness of the room. The Serial Monitor shows these numbers live, and the Serial Plotter draws them as a moving graph.

The key lesson here is calibration. The same sensor gives different numbers in a bright bedroom and a competition hall, two sensors of the same model disagree with each other, and readings drift as the battery runs down. Learners who hard-code a threshold, say dark means below 400, are puzzled when the robot behaves differently somewhere new. The better habit: record the lowest and highest values where the robot will run, take the midpoint as the threshold, and keep it in a single variable at the top of the sketch so it is easy to change. The map() function converts the 0 to 1023 range into another one, such as 0 to 180 degrees for a servo.

A good exercise is an automatic night light that switches on when a room goes dark, tested in three rooms with each threshold written down. The sign that this skill has formed: before writing any logic, the learner first prints the sensor numbers to the Serial Monitor.

Arduino Uno pins are designed for small currents, around 20 milliamps per pin for safe use, while a small DC motor on a robot chassis can draw hundreds of milliamps, and more at start-up or when stalled. That is why motors run through a driver module such as an L298N or L9110S, which takes small signals from the Arduino and passes large currents from the battery. One rule is often forgotten: the motor battery's ground and the Arduino's ground must be connected, so the control signals share a common reference.

Motor speed is controlled with PWM, switching the power on and off hundreds of times per second. On the Uno, analogWrite() with values from 0 to 255 works on the pins marked with a tilde: 3, 5, 6, 9, 10 and 11. Direction comes from flipping the state of two input pins on the driver. Servos work differently: they take an angle command from 0 to 180 degrees through the Servo library, which suits a pointer arm, a gripper or a sensor head that turns to look around. A small servo such as the SG90 can run from the board's 5V pin for a quick test and behaves more steadily on its own supply.

Power shortages have recognisable symptoms: the board resets every time a motor starts, a servo jitters in place, or the robot runs strongly for a moment and then slows. The drill: run one motor forward, backward and at three speeds before the second wheel goes on. The sign of understanding: the learner checks the ground connection and the battery voltage before suspecting the code.

A robot that misbehaves almost always has its problem in one of three areas: the physical connections, the program logic or the power supply. The beginner habit that costs the most time is guessing and then changing three things at once. The faster method is isolation: test one part in its own small sketch. The motor gets a sketch that only spins the motor. The sensor gets a sketch that only prints its numbers. Once each part has proved itself, the two are combined.

Serial.print() is the cheapest diagnostic tool there is. Printing sensor values, the name of the state the program is in, or a marker showing that a particular branch ran reveals what is going on inside the robot's head. For wiring, a multimeter in continuity mode beeps when two points are connected, a quick way to find a jumper wire broken inside its insulation. For power, measure the battery voltage while the motors are running, since a battery that looks full at rest can sag sharply under load. Upload problems have their own checklist: board and port under the Tools menu, a USB cable that only charges, and parts connected to pins 0 and 1, which double as the Serial lines.

The habit that keeps learners moving forward is a logbook. Each attempt is recorded: what changed, what was expected, what happened. Within a few weeks the book holds a pattern of personal mistakes that is worth a great deal. The sign that debugging has become a skill: the learner can state a hypothesis before touching anything.