| Component | Typical duration | Focus |
|---|---|---|
| Prerequisite | Robotics Level 1 or equivalent | Basic electronics, block coding, simple mechanisms |
| Total duration | 8–16 weeks | 50% theory / 50% lab |
| Platforms | Arduino, LEGO EV3, VEX, ROS intro | Varies by institution |
| Topic | Key concepts |
|---|---|
| Program organization | Top-down algorithm design, flowcharts, pseudocode |
| Data types & variables | Named memory locations, arrays, variable scope |
| Logic control structures | Decision structures (if/else), repetition (loops), system registers |
| Modular programming | Sub-programs/subroutines, calls, jumps, tags |
| Debugging | Syntax errors, run-time errors, logic errors |
| Sensor type | Application |
|---|---|
| Touch / bump | Collision detection, wall following |
| Ultrasonic / distance | Obstacle avoidance, navigation |
| Light / colour | Line following, edge detection |
| Sound | Command activation, environment sensing |
| Encoder | Precise position tracking, speed control |
| Topic | Details |
|---|---|
| Motor types | DC motors, servo motors, stepper motors |
| Drive trains | Differential drive, holonomic vs. non-holonomic systems |
| Speed / torque trade-offs | Gear ratios, power transmission |
| PID control | Proportional–Integral–Derivative for precise motion |
| Behaviour type | Implementation |
|---|---|
| Obstacle avoidance | Sensor fusion (ultrasonic + touch), reactive control |
| Wall following | Distance threshold maintenance |
| Path planning | Basic behaviours, simple vs. complex behaviour composition |
| Navigation basics | Mapping, localization introduction |
| Topic | Details |
|---|---|
| I/O integration | Buttons, lights, external devices for program flow control |
| User frames | Custom coordinate frames for inclined surfaces |
| Positional offsets | Register manipulation for precise object handling |
| Palletizing routines | Infeed/outfeed stacking operations |
| PLC logic | Ladder logic, 5-rung logic basics |
| Topic | Tools / concepts |
|---|---|
| CAD modeling | SolidWorks for robot components and assemblies |
| Chassis construction | Stability, centre of gravity, bracing, material selection (steel vs. aluminium) |
| Pneumatics | Force, pressure, work, power principles; appropriate applications |
| Engineering measurement | Digital multimeter, calipers, micrometers |
| Phase | Deliverable |
|---|---|
| Design | Problem identification, research, engineering notebook documentation |
| Build | Functional prototype integrating sensors, actuators, and control logic |
| Program | Modular, debugged code demonstrating autonomous behaviour |
| Test | Iterate based on performance data |
| Present | Oral report + written documentation of design decisions |
| Level 2 track | Next step (Level 3) |
|---|---|
| Arduino / VEX focus | Advanced AI, machine learning for robotics |
| ROS / programming focus | Collaborative robot automation, industry‑standard platforms |
| Mobile robotics | SLAM, advanced path planning, multi‑robot systems |
| Manipulators | Inverse kinematics, dynamics, human‑robot interaction |
Welcome to Level Two of Fundamentals of Robotics! In Level One, you learned what robots are, how they move, and how to build simple machines. You learned about motors, wheels, and basic block coding. You made a robot move forward, backward, and turn. That was a great start!
Now we are going to take a big step forward. In this module, you will learn how to talk to your robot in a more powerful way. You will learn how to write instructions that your robot can follow step by step. You will learn how to make your robot think using decisions, loops, and sub-programs.
Think of it like this: In Level One, you learned how to say "Hello" to your robot. In Level Two, you will learn how to have a full conversation with your robot. You will tell it what to do when something happens. You will teach it to repeat actions. You will show it how to break big jobs into small jobs.
This module is called Programming Fundamentals for Robotics. That sounds like a big title, but it simply means: the basic ways we write instructions for robots.
You do not need to be a computer genius to understand this. You just need to be curious, patient, and ready to try new things. Every expert programmer started exactly where you are right now.
Let us begin this exciting journey together!
By the end of this module, you will be able to:
Once upon a time, in the city of Enugu, Nigeria, there lived a clever girl named Ada. Ada was twelve years old and she loved robots. Her favourite thing in the whole world was her small robot named Chidi.
Chidi was a simple robot. He had two wheels, a small computer brain, and a little light on his head. Ada could make Chidi move forward, backward, left, and right using a remote control.
One day, Ada's school announced a Robotics Dance Competition. Robots from all over the state would come and perform dance moves. The robot that danced the best would win a prize.
Ada was excited! She said, "Chidi, we are going to win this competition!"
But there was a problem. Chidi only knew how to move in straight lines. He could not dance. He could not spin. He could not wiggle. He could not do anything fancy.
Ada thought and thought. Then she had an idea. "I will write a program for Chidi," she said. "I will give him a list of instructions that he can follow to dance."
Ada sat down with her computer. She wrote:
Step 1: Move forward 2 steps Step 2: Turn right 90 degrees Step 3: Move forward 2 steps Step 4: Turn left 90 degrees Step 5: Spin around 360 degrees Step 6: Blink light 3 times Step 7: Repeat from Step 1
She uploaded the program to Chidi. Then she pressed START.
Chidi began to move! He moved forward. He turned right. He moved forward again. He turned left. He spun around. He blinked his light. Then he did it all over again!
Ada clapped and laughed. "Chidi, you are dancing!" she shouted.
But then something went wrong. Chidi bumped into a chair. He stopped. His light turned red. He was confused.
Ada realised that her program was missing something. Chidi did not know what to do when he hit an obstacle. He needed a decision. He needed to check: "Is there something in front of me? If yes, then turn. If no, then keep going."
Ada added a new instruction:
Step 1: Move forward 2 steps Step 2: IF there is an obstacle in front, THEN turn right Step 3: Turn right 90 degrees Step 4: Move forward 2 steps Step 5: Turn left 90 degrees Step 6: Spin around 360 degrees Step 7: Blink light 3 times Step 8: Repeat from Step 1
She uploaded the new program. Chidi started again. This time, when he came near the chair, he checked. He saw the chair. He turned right. He avoided the chair. He kept dancing!
Ada's robot won second place in the competition. But more importantly, Ada learned something powerful: robots need clear instructions, and good instructions include decisions and repetition.
That is exactly what you will learn in this module. Let us begin!
A program is a list of instructions that tells a computer or robot what to do.
Without a program, a robot is just a pile of metal, wires, and plastic. It cannot do anything on its own. The program is like the robot's brain. It tells the robot what to do, when to do it, and how to do it.
Think of a program like a recipe for cooking jollof rice. A recipe has steps:
Step 1: Wash the rice Step 2: Boil the water Step 3: Add the rice Step 4: Add the stew Step 5: Stir and cook Step 6: Serve
If you follow the steps in order, you get jollof rice. If you skip a step or do them in the wrong order, the food will not be good. A robot program works the same way. The robot follows the steps in order.
When you use a washing machine, you press buttons to choose a cycle. The washing machine follows a program: fill with water, wash, rinse, spin, drain. That is a program.
When your teacher gives you a list of things to do during an exam — read the questions, answer the easy ones first, check your work, submit — that is like a program.
When your mother gives you a list: sweep the floor, wash the plates, arrange the chairs, then you can watch TV — that is a program for you to follow.
A danfo bus conductor follows a program every day: start at the park, pick passengers at stop one, collect money, drop passengers at stop two, pick more passengers, and continue until the last stop.
Program for a Robot
|
V
+-------------+
| Instruction |
| 1 |
+-------------+
|
V
+-------------+
| Instruction |
| 2 |
+-------------+
|
V
+-------------+
| Instruction |
| 3 |
+-------------+
|
V
+-------------+
| Instruction |
| 4 |
+-------------+
|
V
STOP
A program is a list of steps a robot follows. The order matters. Robots cannot think on their own; they need programs.
Sequential execution means doing things one after the other, in order, from top to bottom.
Robots do not understand messy instructions. They need clear, ordered steps. If you tell a robot to "move and turn and blink," it may get confused. But if you say "move forward, then turn right, then blink," it will work perfectly.
Imagine you are giving directions to a friend who is blindfolded. You cannot say, "Go somewhere over there." You must say, "Take two steps forward. Stop. Turn left. Take one step forward. Stop."
Robots are like that friend. They need exact instructions.
When you follow a recipe, you do not add salt before boiling water if the recipe says to boil first. Order matters.
In a chemistry lab, you must put on safety goggles before mixing chemicals. You cannot mix first and then wear goggles. Order matters.
You cannot eat food before cooking it. You cannot wear shoes before wearing socks (well, you can, but it is uncomfortable!). Order matters.
To make pounded yam, you must first boil the yam, then pound it. You cannot pound raw yam. Order matters.
Robot Execution Order
|
V
[Step 1: Move]
|
V
[Step 2: Turn]
|
V
[Step 3: Blink]
|
V
[Step 4: Stop]
|
V
DONE
If order is wrong:
[Step 2: Turn] <-- Robot turns first
|
V
[Step 1: Move] <-- Then moves
|
V
[Step 4: Stop] <-- Stops before blinking
|
V
[Step 3: Blink] <-- Blinks after stopping
Robots follow instructions one by one, in the exact order you give them. The order is very important.
A variable is a named box in the robot's memory that holds information. You can put a number, a word, or a true/false value inside it.
Robots need to remember things. They need to remember how far they have travelled, how many times they have blinked, or what colour they last saw. Variables help robots remember.
Think of a variable like a plastic container in your kitchen. You can write a label on it, like "Rice" or "Beans." Inside, you put something. Later, you can open the container and see what is inside. You can also change what is inside.
A variable works the same way. It has a name (label) and a value (what is inside).
Your school bag is like a variable. Its name is "School Bag." Its value changes: sometimes it holds books, sometimes it holds lunch, sometimes it holds a pencil case.
Your test score is a variable. The name is "Score." The value might be 85, 72, or 100. It changes every test.
The amount of fuel in your father's car is a variable. It goes up when he buys fuel. It goes down when he drives.
The price of a bag of rice is a variable. Sometimes it is ₦45,000. Sometimes it is ₦50,000. It changes with time and market.
Variable: "Distance"
+----------------+
| Value: 10 cm |
+----------------+
|
| (robot moves)
V
+----------------+
| Value: 25 cm |
+----------------+
|
| (robot moves more)
V
+----------------+
| Value: 50 cm |
+----------------+
A variable is a named box that holds information. The information can change. Robots use variables to remember things.
A data type tells the robot what kind of information is inside a variable. The most common types are numbers, words, and true/false values.
Robots need to know the difference between the number 5 and the word "five." They also need to know if something is true or false. Data types help robots understand information correctly.
Imagine you have three different containers:
You would not put water in the rice container. Data types work the same way. Each type has its own purpose.
| Data Type | What It Holds | Example |
|---|---|---|
| Number (Integer) | Whole numbers | 5, 10, 100, -3 |
| Number (Decimal) | Numbers with decimal points | 3.14, 0.5, 2.75 |
| String (Text) | Words and sentences | "Hello", "Ada", "Robot" |
| Boolean | True or False | True, False |
Your age is a number. Your name is a string. Whether you are hungry is a boolean (true or false).
Your class position is a number. Your subject name is a string. Whether you passed the exam is a boolean.
The number of eggs in the fridge is a number. The word "egg" is a string. Whether the fridge is open is a boolean.
The number of passengers in a danfo is a number. The name of the bus stop is a string. Whether the bus is full is a boolean.
Data Types +-------------+ +-------------+ +-------------+ | Number | | String | | Boolean | | [ 42 ] | | ["Ada"] | | [ True ] | +-------------+ +-------------+ +-------------+
Data types tell the robot what kind of information is stored. Numbers, strings, and booleans are the most common types.
An if/else statement lets a robot make a choice. It says: "IF something is true, THEN do this. ELSE, do something different."
Robots need to react to the world around them. If there is a wall in front, turn. If there is no wall, go forward. Decisions make robots smart.
Think about crossing a road. You look left and right. IF there is a car coming, THEN you wait. ELSE, you cross. That is an if/else decision.
A traffic light makes decisions: IF the light is green, THEN cars go. ELSE, cars stop.
IF you finish your homework, THEN you can play. ELSE, you must keep working.
IF it is raining, THEN take an umbrella. ELSE, you can leave it at home.
IF there is no fuel in the generator, THEN you must buy fuel. ELSE, you can turn it on.
If/Else Flowchart
[ Start ]
|
V
+------------------+
| Is there a wall? |
| in front? |
+------------------+
/ \
YES NO
/ \
V V
[ Turn right ] [ Move forward ]
\ /
\ /
V V
[ Continue ]
If/else lets a robot choose between two actions. It checks a condition and decides what to do.
A loop is a way to repeat instructions. Instead of writing the same step ten times, you write it once and tell the robot to repeat it.
Loops save time and make programs shorter. Imagine telling a robot to blink 100 times. You would not write "blink" 100 times. You would write "blink 100 times."
Think of a loop like a song chorus. The chorus repeats after every verse. You do not sing the chorus once; you sing it again and again.
A washing machine repeats the rinse cycle three times. That is a loop.
When you practise multiplication tables, you repeat "2 times 1 is 2, 2 times 2 is 4, 2 times 3 is 6..." That is a loop.
When you stir soup, you move the spoon round and round. That is a loop.
A trader at Balogun Market repeats: "Buy your tomatoes! Fresh tomatoes!" over and over. That is a loop.
Loop Example: Blink 3 Times
[ Start ]
|
V
+------------------+
| Count = 1 |
+------------------+
|
V
+------------------+
| Blink light |
+------------------+
|
V
+------------------+
| Count = Count + 1|
+------------------+
|
V
+------------------+
| Is Count > 3? |
+------------------+
/ \
NO YES
/ \
V V
[ Go back ] [ Stop ]
[ to blink ]
A loop repeats instructions. It saves time and keeps programs short. Loops are used everywhere in robotics.
A sub-program (also called a subroutine or function) is a small program inside a bigger program. It does one specific job. You can call it whenever you need it.
Big programs are hard to manage. If you break a big program into small sub-programs, it becomes easier to write, read, and fix. Sub-programs also save space because you can reuse them.
Imagine you are building a house. You do not do everything alone. You have a carpenter for the roof, a plumber for pipes, and an electrician for wires. Each person has a specific job. Sub-programs are like those workers. Each one does a specific job in the program.
A car has many systems: brakes, engine, steering, lights. Each system does its own job. Together they make the car work. Sub-programs work the same way.
In a school, the principal does not teach every class. There are teachers for maths, English, science, and so on. Each teacher is like a sub-program.
When preparing a party, one person cooks, one person decorates, one person plays music. Each person is like a sub-program.
In a buka (small restaurant), one person cooks the rice, one person makes the stew, one person serves the customers. Each person is like a sub-program.
Main Program
|
+--> Sub-Program: "Move Forward"
|
+--> Sub-Program: "Turn Right"
|
+--> Sub-Program: "Blink Light"
|
+--> Sub-Program: "Stop"
Sub-programs are small programs inside a bigger program. They do specific jobs and can be reused. They make programs easier to manage.
Calling a sub-program means telling the main program to run that sub-program. It is like saying, "Hey, do this job now."
Calling sub-programs keeps the main program clean and organised. Instead of writing all the instructions in one place, you call sub-programs when you need them.
Imagine you are the manager of a football team. You do not play every position yourself. You call the goalkeeper when you need a save. You call the striker when you need a goal. Calling a sub-program is like calling a player to do their job.
When you press the "Start" button on a microwave, you are calling the "Heat Food" sub-program.
When the teacher says, "Prefect, please collect the notebooks," the teacher is calling the prefect to do a job.
When your mother says, "Ada, please wash the plates," she is calling you to do a job. You are the sub-program!
When the bus conductor shouts, "Owa! Owa!" he is calling the driver to stop at Owa bus stop. The driver stopping is the sub-program.
Main Program
|
V
[ Call "Move Forward" ] ---> Sub-Program runs
|
V
[ Call "Turn Right" ] ----> Sub-Program runs
|
V
[ Call "Blink Light" ] ---> Sub-Program runs
|
V
[ Call "Stop" ] ----------> Sub-Program runs
Calling a sub-program means telling the main program to run it. It keeps programs organised and clean.
Debugging means finding mistakes in a program and fixing them. A mistake in a program is called a bug.
No program is perfect the first time. Even expert programmers make mistakes. Debugging helps you find and fix those mistakes so your robot works correctly.
Imagine you are baking a cake. You taste it and it is too salty. You realise you added salt twice. You fix the mistake by not adding salt next time. That is debugging.
| Error Type | What It Means | Example |
|---|---|---|
| Syntax Error | Spelling or grammar mistake in the code | Writing "moov" instead of "move" |
| Run-Time Error | Error that happens while the program is running | Dividing by zero |
| Logic Error | The program runs but does the wrong thing | Telling the robot to turn left when you meant right |
You follow a recipe but add sugar instead of salt. The food is wrong. That is a logic error.
You write the correct answer but shade the wrong option on your answer sheet. That is a logic error.
You iron your shirt but forget to plug in the iron. That is a run-time error.
You tell the bus conductor you are going to Yaba, but he writes Ikeja on your ticket. That is a logic error.
Debugging Process
[ Program not working ]
|
V
[ Find the mistake ]
|
V
[ Fix the mistake ]
|
V
[ Test again ]
|
V
[ Does it work? ]
/ \
NO YES
/ \
V V
[Fix again] [Done!]
Debugging means finding and fixing mistakes in a program. There are three main types of errors: syntax, run-time, and logic.
A flowchart is a drawing that shows the steps of a program using shapes and arrows.
Flowcharts help you plan your program before you write it. They make it easy to see the order of steps and where decisions happen.
Think of a flowchart like a map. A map shows you the roads and turns to reach a destination. A flowchart shows the steps and decisions to complete a program.
| Symbol | Meaning |
|---|---|
| Oval | Start or End |
| Rectangle | Process or Action |
| Diamond | Decision (Yes/No) |
| Arrow | Direction of flow |
A recipe is like a flowchart. It has steps and sometimes decisions: "If the dough is sticky, add flour."
Your school timetable is like a flowchart. It shows what happens at each time.
Your morning routine is a flowchart: wake up, brush teeth, bathe, dress, eat, go to school.
A trader's day is a flowchart: open shop, arrange goods, attend to customers, close shop, go home.
Simple Flowchart: Robot Avoids Wall
( Start )
|
V
+----------------+
| Move forward |
+----------------+
|
V
+----------------+
| Wall ahead? |
+----------------+
/ \
YES NO
/ \
V V
+---------+ +-----------+
| Turn | | Keep |
| right | | moving |
+---------+ +-----------+
\ /
\ /
V V
( Continue )
A flowchart is a drawing that shows the steps of a program. It uses shapes and arrows to show order and decisions.
A complete program uses variables, decisions, loops, and sub-programs together to make a robot do a complex task.
Real robots do not just move forward. They sense, decide, act, and repeat. A complete program brings all the pieces together.
Think of a complete program like a football team. The goalkeeper, defenders, midfielders, and strikers all work together. Each part has a job. Together they win the match.
A self-driving car uses a complete program: it senses the road, decides when to turn, repeats the process, and calls sub-programs for braking and accelerating.
A school assembly is a complete program: students gather, principal speaks, announcements are made, students return to class.
Cooking a full meal is a complete program: prepare ingredients, cook rice, cook stew, set the table, serve.
A wedding ceremony is a complete program: guests arrive, couple enters, vows are taken, food is served, dancing begins.
Complete Robot Program
[ Start ]
|
V
[ Set variable "count" = 0 ]
|
V
[ Loop while count < 5 ]
|
V
[ Move forward ]
|
V
[ Is there an obstacle? ]
/ \
YES NO
/ \
V V
[ Turn right ] [ Blink light ]
\ /
\ /
V V
[ count = count + 1 ]
|
V
[ End loop ]
|
V
[ Stop ]
A complete program uses all the pieces together. It senses, decides, acts, and repeats. This is how real robots work.
Modular programming means building a program from small, independent parts (modules or sub-programs).
Modular programs are easier to write, test, fix, and reuse. If one module breaks, you only fix that module. You do not have to rewrite the whole program.
Think of LEGO blocks. You build a house using many small blocks. If one block is missing, you replace just that block. You do not throw away the whole house. Modular programming is like building with LEGO blocks.
A smartphone has many apps. Each app does one job. If the calculator app crashes, the camera app still works. Each app is a module.
Your school has different subjects. If you are weak in maths, you improve maths. You do not stop learning English. Each subject is a module.
Your home has different rooms: kitchen, bedroom, bathroom. If the kitchen needs repair, you do not rebuild the whole house. Each room is a module.
A market has different stalls: one sells pepper, one sells fish, one sells cloth. If the fish stall closes, the pepper stall still opens. Each stall is a module.
Modular Program
+-------------------+
| Main Program |
+-------------------+
|
+------> [ Module: Move ]
|
+------> [ Module: Turn ]
|
+------> [ Module: Sense ]
|
+------> [ Module: Blink ]
Modular programming means building a program from small parts. It makes programs easier to manage and fix.
Planning means thinking about what you want the robot to do before you write the program.
If you start writing a program without a plan, you will make many mistakes. Planning helps you see the big picture and avoid confusion.
Imagine you want to build a house. You do not just start laying bricks. You draw a plan first. You decide where the rooms will be, where the doors will go, and how many windows you need. Programming is the same. Plan first, then write.
Before a football match, the coach makes a plan: who plays where, what strategy to use. That is planning.
Before writing an exam, you plan: how much time for each question, which questions to answer first. That is planning.
Before cooking a big meal, you plan: what to cook, what ingredients to buy, what order to cook. That is planning.
Before a wedding, the family plans: the venue, the food, the music, the guest list. That is planning.
Planning Process
[ Idea ]
|
V
[ Write down what robot should do ]
|
V
[ Draw a flowchart ]
|
V
[ List the sub-programs needed ]
|
V
[ Write the program ]
|
V
[ Test and fix ]
Planning means thinking before writing. It helps you avoid mistakes and write better programs.
Testing means running your program to see if it works correctly.
Even the best programmers make mistakes. Testing helps you find those mistakes before the robot does something wrong.
Imagine you are baking a cake for a party. You taste it before the party to make sure it is good. If it is not good, you fix it. Testing a program is like tasting the cake before the party.
Car manufacturers test cars before selling them. They drive them, brake them, and check everything. That is testing.
Before submitting your homework, you read it again to check for mistakes. That is testing.
Before wearing a new shirt, you try it on to see if it fits. That is testing.
Before a danfo bus starts its route, the driver tests the brakes and checks the engine. That is testing.
Testing Process
[ Write program ]
|
V
[ Run program ]
|
V
[ Does it work? ]
/ \
YES NO
/ \
V V
[Done] [Find and fix bug]
|
V
[Run again]
Testing means running your program to check for mistakes. It helps you find and fix bugs before the robot fails.
Best practices are good habits that help you write better programs.
Good habits make programming easier and more fun. They help you avoid mistakes and save time.
Think of best practices like brushing your teeth every morning. It is a good habit that keeps you healthy. In programming, good habits keep your code clean and working.
| Practice | Why It Helps |
|---|---|
| Use clear names for variables | Makes your program easy to read |
| Write comments in your code | Helps you remember what you did |
| Break big jobs into sub-programs | Makes programs easier to manage |
| Test small parts before putting them together | Finds bugs early |
| Plan before you write | Saves time and avoids confusion |
| Keep your code neat and organised | Makes it easy to find mistakes |
A carpenter keeps his tools organised. He knows where each tool is. That is a best practice.
A good student keeps notes neat and organised. That is a best practice.
A good cook cleans the kitchen as they cook. That is a best practice.
A good trader arranges goods neatly in the shop. That is a best practice.
Best Practice: Clear Names BAD: x = 5 y = 10 z = x + y GOOD: robot_speed = 5 robot_time = 10 robot_distance = robot_speed * robot_time
Best practices are good habits. They make programming easier and your programs better.
| Word | Simple Definition |
|---|---|
| Program | A list of instructions for a robot or computer. |
| Instruction | A single step in a program. |
| Variable | A named box that holds information. |
| Data Type | The kind of information in a variable (number, word, true/false). |
| If/Else | A decision structure that chooses between two actions. |
| Loop | A way to repeat instructions. |
| Sub-Program | A small program inside a bigger program. |
| Call | Telling the main program to run a sub-program. |
| Debugging | Finding and fixing mistakes in a program. |
| Bug | A mistake in a program. |
| Flowchart | A drawing that shows the steps of a program. |
| Modular Programming | Building a program from small, independent parts. |
| Testing | Running a program to see if it works. |
| Best Practice | A good habit that helps you write better programs. |
| Sequential Execution | Doing things one after the other, in order. |
| Concept | Real-Life Example |
|---|---|
| Program | A recipe for cooking jollof rice. |
| Sequential Execution | Following a recipe step by step. |
| Variable | Your school bag holds different things each day. |
| Data Types | Your age (number), your name (string), whether you are hungry (boolean). |
| If/Else | IF it is raining, THEN take an umbrella. |
| Loop | Stirring soup round and round. |
| Sub-Program | Different workers building a house. |
| Calling | Pressing "Start" on a microwave. |
| Debugging | Tasting food and adding salt if needed. |
| Flowchart | A map showing roads and turns. |
| Modular Programming | Different apps on a smartphone. |
| Concept | Nigerian Example |
|---|---|
| Program | A danfo bus conductor's daily route. |
| Sequential Execution | Making pounded yam: boil yam, then pound. |
| Variable | The price of a bag of rice changes with market. |
| Data Types | Number of passengers (number), bus stop name (string), whether bus is full (boolean). |
| If/Else | IF there is no fuel, THEN buy fuel. ELSE, turn on generator. |
| Loop | A trader repeating "Buy your tomatoes!" |
| Sub-Program | Different workers in a buka: cook, stew maker, server. |
| Calling | Conductor shouting "Owa!" to tell driver to stop. |
| Debugging | Conductor writing wrong destination on ticket and fixing it. |
| Flowchart | A trader's daily routine: open shop, arrange goods, serve customers, close shop. |
| Modular Programming | Different stalls in Balogun Market. |
| Concept | Everyday Example |
|---|---|
| Program | Your morning routine: wake up, brush, bathe, dress, eat, go to school. |
| Variable | The amount of data on your phone. |
| If/Else | IF you finish homework, THEN watch TV. ELSE, keep working. |
| Loop | Brushing your teeth in circles. |
| Sub-Program | Different chores: sweeping, washing, cooking. |
| Debugging | Finding why your phone is slow and fixing it. |
| Mistake | Why It Is Wrong | How to Fix It |
|---|---|---|
| Writing steps in the wrong order | The robot will do the wrong thing. | Plan the order before writing. |
| Using unclear variable names | It is hard to understand the program. | Use clear names like "robot_speed." |
| Forgetting to test | Mistakes go unnoticed. | Always test your program. |
| Writing one big program | It is hard to fix mistakes. | Break it into sub-programs. |
| Ignoring bugs | The robot will not work correctly. | Find and fix bugs immediately. |
| Not planning | You will make many mistakes. | Draw a flowchart first. |
+-------------------+
| Human writes |
| a program |
+-------------------+
|
V
+-------------------+
| Program is |
| uploaded to |
| robot |
+-------------------+
|
V
+-------------------+
| Robot reads |
| instructions |
+-------------------+
|
V
+-------------------+
| Robot follows |
| instructions |
+-------------------+
|
V
+-------------------+
| Robot does |
| the task |
+-------------------+
( Start )
|
V
+----------------+
| Read sensor |
+----------------+
|
V
+----------------+
| Is there an |
| obstacle? |
+----------------+
/ \
YES NO
/ \
V V
+---------+ +-----------+
| Turn | | Move |
| right | | forward |
+---------+ +-----------+
\ /
\ /
V V
( Continue )
| Data Type | Example | Used For |
|---|---|---|
| Integer | 5, 10, 100 | Counting, distances, scores |
| Decimal | 3.14, 0.5 | Measurements, percentages |
| String | "Hello", "Ada" | Names, messages, labels |
| Boolean | True, False | Decisions, conditions |
Step 1: Plan
|
V
Step 2: Write
|
V
Step 3: Test
|
V
Step 4: Debug
|
V
Step 5: Test Again
|
V
Step 6: Done!
A program is a list of instructions. Robots need programs to work. The order of instructions matters.
Robots follow instructions one by one. Sequential execution means doing things in order.
Variables are named boxes that hold information. They can change.
Data types tell the robot what kind of information is stored: numbers, strings, or booleans.
If/else lets robots make decisions. It checks a condition and chooses an action.
Loops repeat instructions. They save time and keep programs short.
Sub-programs are small programs inside a bigger program. They do specific jobs.
Calling a sub-program means telling the main program to run it.
Debugging means finding and fixing mistakes. There are three types of errors: syntax, run-time, and logic.
Flowcharts are drawings that show the steps of a program.
A complete program uses variables, decisions, loops, and sub-programs together.
Modular programming means building a program from small parts.
Planning means thinking before writing. It helps you avoid mistakes.
Testing means running your program to check for mistakes.
Best practices are good habits that make programming easier.
In this module, you learned the fundamentals of programming for robotics. You learned that a program is a list of instructions. You learned that robots follow instructions in order. You learned about variables, data types, decisions, loops, sub-programs, debugging, flowcharts, and best practices.
You also learned why planning and testing are important. You learned how to break big jobs into small jobs. You learned how to find and fix mistakes.
Most importantly, you learned that programming is a skill you can develop with practice. You do not need to be a genius. You just need to be patient, curious, and willing to try again when things go wrong.
In the next module, you will build on these basics. You will learn how to use sensors and actuators to make your robot interact with the world. You will learn how to write programs that react to light, sound, and touch. You will learn how to make your robot move with precision.
But for now, take a moment to celebrate what you have learned. You have taken a big step in your journey to becoming a robotics expert. Well done!
Match the word on the left with its definition on the right.
| Word | Definition |
|---|---|
| 1. Program | A. A named box that holds information |
| 2. Variable | B. A list of instructions |
| 3. Loop | C. Finding and fixing mistakes |
| 4. Sub-program | D. Repeating instructions |
| 5. Debugging | E. A small program inside a bigger program |
| 6. Flowchart | F. A decision structure |
| 7. If/Else | G. A drawing that shows steps |
| 8. Data Type | H. The kind of information in a variable |
Answers: 1-B, 2-A, 3-D, 4-E, 5-C, 6-G, 7-F, 8-H
Title: Build a Robot Dance Program
Instructions:
Example:
Sub-Program 1: "Spin" - Turn right 360 degrees Sub-Program 2: "Blink" - Blink light 3 times Main Program: - Move forward 2 steps - IF obstacle ahead, THEN turn right - Call "Spin" - Call "Blink" - Repeat from Step 1
Title: Write Your First Robot Program
Instructions:
Example Task: A robot that moves forward, avoids obstacles, and blinks when it reaches its destination.
Title: Robot Morning Routine
Goal: Create a program that makes a robot perform a morning routine.
Steps:
Deliverables:
Title: Build a Simple Robot Program
Instructions:
Grading Criteria:
| Criteria | Points |
|---|---|
| Program works correctly | 40 |
| Uses if/else decision | 20 |
| Uses a loop | 20 |
| Report is clear | 20 |
| Total | 100 |
In Module Two, you will learn about Sensors and Perception. You will learn how robots use sensors to see, hear, and feel the world around them. You will learn about touch sensors, ultrasonic sensors, light sensors, and more.
To prepare for Module Two:
Get ready for an exciting journey into the world of robot senses!
Congratulations! You have completed Module One of Fundamentals of Robotics Level Two. You have learned the basics of programming for robots.
You learned that a program is a list of instructions. You learned that robots follow instructions in order. You learned about variables and data types. You learned how to make decisions with if/else. You learned how to repeat actions with loops. You learned how to break big jobs into small jobs using sub-programs. You learned how to call sub-programs. You learned how to find and fix mistakes through debugging. You learned how to plan with flowcharts. You learned why modular programming is important. You learned how to plan and test your programs. You learned best practices for programming.
You also learned many examples from Nigeria, from your home, from school, and from everyday life. You learned through stories, illustrations, and activities.
Now you are ready for Module Two: Sensors and Perception. In Module Two, you will learn how robots use sensors to understand the world. You will learn how to write programs that react to touch, distance, light, and sound. You will learn how to make your robot truly interactive.
But before you move on, take a moment to review this module. Make sure you understand the key ideas. Practise writing simple programs. Draw flowcharts. Test your programs. The more you practise, the better you will become.
You are doing great. Keep learning. Keep exploring. Keep building. The world of robotics is waiting for you!
End of Module One
Next: Module Two — Sensors and Perception
Welcome to Module Two! In Module One, you learned how to write programs for robots. You learned about variables, decisions, loops, and sub-programs. You learned how to give your robot clear instructions.
But there is a problem. A robot that only follows instructions is blind. It cannot see. It cannot hear. It cannot feel. It just does what it was told, even if something is in the way.
Imagine you are walking to school with your eyes closed. You would bump into everything! You need your eyes to see where you are going. You need your ears to hear cars coming. You need your skin to feel if something is hot.
Robots are the same. They need sensors to understand the world around them. Sensors are like a robot's eyes, ears, and skin. They help the robot perceive — that means to notice and understand — what is happening around it.
In this module, you will learn about different types of sensors. You will learn how they work. You will learn how to use them in your programs. You will learn how to make your robot react to the world.
This is where robotics becomes really exciting. Your robot will stop being a machine that just follows orders. It will start being a machine that responds to its environment.
Let us begin!
By the end of this module, you will be able to:
Once upon a time, in the city of Aba, Nigeria, there lived a boy named Emeka. Emeka loved building things. His favourite project was a small robot named Nneka.
Nneka was a simple robot. She had two wheels, a small motor, and a computer brain. Emeka could program Nneka to move forward, backward, left, and right.
One day, Emeka decided to show Nneka to his friends. He put Nneka on the floor and pressed START. Nneka began to move forward. She moved straight. She moved fast. She moved proudly.
Then — BANG! Nneka hit the wall. She kept pushing against the wall. Her wheels spun. Her motor made a loud noise. She did not stop. She did not turn. She just kept pushing.
Emeka's friends laughed. "Your robot is blind!" they said.
Emeka felt sad. But then he thought, "They are right. Nneka is blind. She cannot see the wall. She cannot feel the wall. She just follows instructions."
Emeka went home and thought about the problem. How could he make Nneka see? How could he make her feel?
The next day, Emeka went to the market with his father. He saw many things: a trader touching tomatoes to check if they were ripe, a driver looking at the road, a woman listening for her phone ringing.
"Everyone uses their senses," Emeka thought. "Eyes to see, ears to hear, skin to feel. Maybe I can give Nneka senses too."
Emeka went to a computer shop and bought a small touch sensor. It was like a button. When something pressed it, it sent a signal to the robot's brain.
He attached the touch sensor to the front of Nneka. Then he wrote a new program:
Step 1: Move forward Step 2: IF touch sensor is pressed, THEN stop and turn right Step 3: Repeat from Step 1
He uploaded the program and pressed START. Nneka began to move forward. She moved toward the wall. She touched the wall. The touch sensor was pressed. Nneka stopped. She turned right. She moved forward again. She avoided the wall!
Emeka's friends were amazed. "Nneka can feel!" they shouted.
Emeka smiled. He had given his robot a sense. He had made Nneka perceive the world.
That is what you will learn in this module. You will learn how to give your robot senses. You will learn how to make your robot perceive the world.
Let us begin!
A sensor is a device that detects something in the environment and sends that information to the robot's brain.
Without sensors, a robot is blind and deaf. It cannot react to anything. It just follows its program, even if something goes wrong. Sensors give robots the ability to sense the world and make better decisions.
Think of your five senses: sight, hearing, touch, taste, and smell. These senses tell you what is happening around you. A sensor is like a robot's sense. It tells the robot what is happening around it.
Your phone has sensors. It has a light sensor that adjusts the screen brightness. It has a motion sensor that knows when you turn the phone.
A fire alarm has a smoke sensor. When it detects smoke, it makes a loud noise.
A refrigerator has a temperature sensor. It knows when the fridge is too warm, so it turns on the cooling system.
A generator has a fuel sensor. When the fuel is low, it warns you to buy more fuel.
Sensor in a Robot
+-------------------+
| Environment |
| (world) |
+-------------------+
|
| (something happens)
V
+-------------------+
| Sensor |
| detects it |
+-------------------+
|
| (sends signal)
V
+-------------------+
| Robot Brain |
| decides what |
| to do |
+-------------------+
|
V
+-------------------+
| Robot acts |
+-------------------+
A sensor is a device that detects something in the environment. It sends information to the robot's brain. Sensors give robots the ability to sense the world.
Perception is the process of using sensors to understand the world. It is how a robot makes sense of what its sensors tell it.
A sensor alone is not enough. The robot must also understand what the sensor means. For example, a touch sensor detects a press. But the robot must understand that the press means "there is an obstacle." That understanding is perception.
Imagine you touch a hot pot. Your skin senses heat. But your brain perceives danger. It tells you to pull your hand away. The sensor is your skin. The perception is your brain understanding the danger.
When you see dark clouds, your eyes sense the clouds. Your brain perceives that it might rain. You decide to take an umbrella.
When you hear the school bell, your ears sense the sound. Your brain perceives that it is time for break. You decide to go outside.
When you smell burning food, your nose senses the smell. Your brain perceives that the food is burning. You decide to turn off the cooker.
When a driver hears a horn behind him, his ears sense the sound. His brain perceives that another car wants to overtake. He decides to move aside.
Perception Process
+-------------+
| Sensor |
| detects |
+-------------+
|
V
+-------------+
| Robot |
| brain |
| understands|
+-------------+
|
V
+-------------+
| Robot |
| decides |
+-------------+
|
V
+-------------+
| Robot |
| acts |
+-------------+
Perception is how a robot understands what its sensors detect. It is the bridge between sensing and acting.
A touch sensor (also called a bump sensor) detects when something presses against it. It is like a button.
Touch sensors help robots detect collisions. When a robot bumps into something, the touch sensor sends a signal. The robot can then stop or turn.
Think of a doorbell. When you press it, it makes a sound. A touch sensor works the same way. When something presses it, it sends a signal.
Your phone screen is a touch sensor. When you tap an app, the screen senses your touch and opens the app.
A computer keyboard has touch sensors. When you press a key, the keyboard senses it and sends the letter to the computer.
A light switch is a touch sensor. When you press it, it senses your touch and turns the light on or off.
A car horn is a touch sensor. When you press it, it senses your touch and makes a sound.
Touch Sensor
+-------------------+
| Robot |
| +-----------+ |
| | Touch | |
| | Sensor | |
| +-----------+ |
+-------------------+
|
| (robot moves forward)
V
+-------------------+
| Wall |
+-------------------+
|
| (sensor is pressed)
V
+-------------------+
| Signal sent to |
| robot brain |
+-------------------+
|
V
+-------------------+
| Robot stops |
| or turns |
+-------------------+
A touch sensor detects when something presses it. It helps robots detect collisions and react to obstacles.
An ultrasonic sensor uses sound waves to measure distance. It sends out a sound wave and waits for it to bounce back. The time it takes tells the robot how far away something is.
Ultrasonic sensors help robots avoid obstacles from a distance. The robot does not need to touch the obstacle. It can sense it from far away and change direction.
Imagine you are in a big empty room. You shout "HELLO!" and wait for the echo. If the echo comes back quickly, the wall is close. If the echo takes a long time, the wall is far. Ultrasonic sensors work the same way, but with sound waves that humans cannot hear.
Bats use ultrasonic sound to navigate in the dark. They send out sound waves and listen for the echo. That is how they know where obstacles are.
Some cars have parking sensors. They use ultrasonic waves to detect how close the car is to the wall.
Some vacuum cleaners are robots. They use ultrasonic sensors to avoid bumping into furniture.
A car reversing in a tight parking space in Lagos uses ultrasonic sensors to avoid hitting other cars.
Ultrasonic Sensor
+-------------------+
| Robot |
| +-----------+ |
| | Ultrasonic| |
| | Sensor | |
| +-----------+ |
+-------------------+
|
| (sends sound wave)
V
+-------------------+
| Obstacle |
+-------------------+
|
| (sound wave bounces back)
V
+-------------------+
| Robot receives |
| echo |
+-------------------+
|
| (calculates distance)
V
+-------------------+
| Robot knows |
| how far away |
+-------------------+
An ultrasonic sensor uses sound waves to measure distance. It helps robots avoid obstacles from far away.
A light sensor detects the amount of light in the environment. It can tell if it is bright or dark.
Light sensors help robots follow lines, detect edges, and react to changes in light. They are very useful in line-following robots.
Think of your eyes. When you enter a dark room, your eyes adjust. When you go outside in the sun, your eyes squint. A light sensor does the same thing. It measures how much light is around.
Street lights turn on automatically when it gets dark. They use light sensors.
Some classrooms have automatic lights. When the room is bright, the lights stay off. When it gets dark, the lights turn on.
Your phone screen adjusts its brightness based on the light around you. It uses a light sensor.
Solar panels use light sensors to know when the sun is shining. They store energy during the day.
Light Sensor
+-------------------+
| Robot |
| +-----------+ |
| | Light | |
| | Sensor | |
| +-----------+ |
+-------------------+
|
| (detects light level)
V
+-------------------+
| Bright or dark? |
+-------------------+
/ \
BRIGHT DARK
/ \
V V
+---------+ +---------+
| Robot | | Robot |
| follows | | stops |
| line | | |
+---------+ +---------+
A light sensor detects brightness. It helps robots follow lines and react to light changes.
A sound sensor (also called a microphone sensor) detects sound. It can tell if there is noise and how loud it is.
Sound sensors help robots react to claps, voices, or other sounds. They can be used to start a robot with a clap or stop it with a loud noise.
Think of your ears. When someone claps, your ears hear it. Your brain understands that it is a clap. A sound sensor does the same thing. It detects sound and sends a signal to the robot's brain.
Some toys clap-activated. When you clap, they move or make a sound. They use sound sensors.
The school bell is like a sound sensor for students. When it rings, students know it is time for break or assembly.
Some televisions can be controlled by voice. They use sound sensors to hear your commands.
A clap-activated light in a compound uses a sound sensor. When you clap, the light turns on.
Sound Sensor
+-------------------+
| Robot |
| +-----------+ |
| | Sound | |
| | Sensor | |
| +-----------+ |
+-------------------+
|
| (detects sound)
V
+-------------------+
| Was there a |
| clap? |
+-------------------+
/ \
YES NO
/ \
V V
+---------+ +---------+
| Robot | | Robot |
| starts | | waits |
+---------+ +---------+
A sound sensor detects noise. It helps robots react to claps, voices, and other sounds.
A colour sensor detects colours. It can tell the difference between red, green, blue, and other colours.
Colour sensors help robots sort objects by colour. They can also be used in line-following robots that follow coloured lines.
Think of a traffic light. Red means stop. Green means go. A colour sensor can detect these colours and tell the robot what to do.
Some factories use colour sensors to sort fruits. Red apples go in one box. Green apples go in another.
In art class, you sort crayons by colour. A colour sensor can do that automatically.
A washing machine can sort clothes by colour using a colour sensor. It separates white clothes from coloured clothes.
A tomato sorting machine in a market uses colour sensors to separate ripe red tomatoes from unripe green ones.
Colour Sensor
+-------------------+
| Robot |
| +-----------+ |
| | Colour | |
| | Sensor | |
| +-----------+ |
+-------------------+
|
| (detects colour)
V
+-------------------+
| What colour? |
+-------------------+
/ \
RED GREEN
/ \
V V
+---------+ +---------+
| Robot | | Robot |
| stops | | goes |
+---------+ +---------+
A colour sensor detects colours. It helps robots sort objects and follow coloured lines.
A distance sensor measures how far away an object is. Ultrasonic sensors are one type of distance sensor. There are also infrared (IR) distance sensors.
Distance sensors help robots navigate. They can tell if an obstacle is near or far. This helps the robot decide whether to slow down, stop, or turn.
Imagine you are playing a game where you must guess how far a tree is. You look at the tree and estimate. A distance sensor does the same thing, but with more accuracy.
Some cars have sensors that beep when you are too close to another car. They use distance sensors.
A measuring tape is like a distance sensor. It tells you how long something is.
A laser measure tool uses a distance sensor to tell you how wide a room is.
A danfo driver uses his eyes as distance sensors. He looks at the car in front and decides if he is too close.
Distance Sensor
+-------------------+
| Robot |
| +-----------+ |
| | Distance | |
| | Sensor | |
| +-----------+ |
+-------------------+
|
| (measures distance)
V
+-------------------+
| How far away? |
+-------------------+
/ \
NEAR FAR
/ \
V V
+---------+ +---------+
| Robot | | Robot |
| stops | | moves |
+---------+ +---------+
A distance sensor measures how far away an object is. It helps robots navigate and avoid obstacles.
Sensor fusion means using multiple sensors together to get a better understanding of the world.
One sensor alone can be confused. A touch sensor only knows when something touches it. An ultrasonic sensor only knows distance. But if you combine them, the robot can understand much more.
Think of crossing a road. You use your eyes to see cars. You use your ears to hear cars. You use both senses together to decide when it is safe to cross. That is sensor fusion.
A self-driving car uses many sensors: cameras, ultrasonic sensors, radar, and GPS. It combines all of them to drive safely.
When you study for an exam, you use your eyes to read and your ears to listen. You combine both to learn better.
When cooking, you use your eyes to see the food and your nose to smell it. You combine both to know when it is ready.
A trader at the market uses her eyes to see customers and her ears to hear them. She combines both to serve them better.
Sensor Fusion
+-------------+ +-------------+
| Touch | | Ultrasonic |
| Sensor | | Sensor |
+-------------+ +-------------+
\ /
\ /
V V
+-------------------+
| Robot Brain |
| combines both |
+-------------------+
|
V
+-------------------+
| Better decision |
+-------------------+
Sensor fusion means using multiple sensors together. It gives the robot a better understanding of the world.
A sensor program is a program that reads sensor data and makes decisions based on that data.
Sensors are only useful if the robot can react to them. A sensor program tells the robot what to do when a sensor detects something.
Imagine you have a touch sensor on your robot. You write a program that says: IF the touch sensor is pressed, THEN stop and turn. That is a sensor program.
A doorbell program: IF the button is pressed, THEN play a sound. That is a sensor program.
A fire alarm program: IF smoke is detected, THEN sound the alarm. That is a sensor program.
A fridge program: IF temperature is too high, THEN turn on cooling. That is a sensor program.
A generator program: IF fuel is low, THEN show warning light. That is a sensor program.
Sensor Program Flow
[ Start ]
|
V
[ Read sensor ]
|
V
[ Is sensor triggered? ]
/ \
YES NO
/ \
V V
[ Act ] [ Continue ]
\ /
\ /
V V
[ Repeat ]
A sensor program reads sensor data and makes decisions. It tells the robot how to react to the world.
Calibration means adjusting a sensor so it works correctly. It means setting the sensor to understand what is normal.
Sensors can be confused. A light sensor might think a shadow is total darkness. Calibration helps the sensor understand the difference between normal light and darkness.
Imagine you get a new pair of glasses. At first, everything looks blurry. You adjust them until you can see clearly. That is calibration.
When you set an alarm clock, you are calibrating it to wake you at the right time.
When you adjust the volume on a radio, you are calibrating the sound.
When you adjust the temperature on an air conditioner, you are calibrating it to the right coolness.
When you tune your radio to a station, you are calibrating it to get clear sound.
Calibration Process
[ Sensor gives wrong reading ]
|
V
[ Adjust sensor settings ]
|
V
[ Test again ]
|
V
[ Does it work? ]
/ \
NO YES
/ \
V V
[Adjust] [Done!]
Calibration means adjusting a sensor so it works correctly. It helps sensors understand normal conditions.
A range is the distance or value a sensor can detect. A threshold is the point where the robot decides something has happened.
Every sensor has limits. An ultrasonic sensor might only detect objects up to 4 metres away. A light sensor might only detect a certain range of brightness. Understanding ranges and thresholds helps you write better programs.
Imagine you can only see things that are less than 10 metres away. That is your range. If something is 11 metres away, you cannot see it. A threshold is like deciding: "If something is closer than 2 metres, I will stop."
Your eyes have a range. You cannot see things that are too far away. You cannot see things that are too small.
Your ears have a range. You cannot hear sounds that are too quiet. You cannot hear sounds that are too high-pitched.
Your nose has a range. You can smell food in the kitchen, but not food in your neighbour's house.
A trader's voice has a range. She can call customers near her stall, but not across the whole market.
Sensor Range and Threshold
Sensor Range: 0 to 4 metres
0m 1m 2m 3m 4m
|---------|---------|---------|---------|
NEAR OK FAR TOO FAR
Threshold: 2 metres
If distance < 2m, robot stops.
If distance >= 2m, robot moves.
Range is how far a sensor can detect. Threshold is the point where the robot decides to act. Both are important for good programming.
Sensor problems are issues that cause sensors to give wrong readings or fail to work.
If a sensor gives wrong information, the robot will make wrong decisions. It might stop when it should move, or move when it should stop. Understanding common problems helps you fix them.
| Problem | Cause | Solution |
|---|---|---|
| Sensor gives no reading | Loose wire or dead battery | Check connections and power |
| Sensor gives wrong reading | Needs calibration | Recalibrate the sensor |
| Sensor is too sensitive | Threshold is too low | Increase threshold |
| Sensor is not sensitive enough | Threshold is too high | Decrease threshold |
| Sensor is affected by noise | Environmental interference | Move sensor or add filtering |
If your phone screen is cracked, the touch sensor may not work. You need to fix or replace it.
If a microphone is too far from the speaker, it may not pick up sound well. You need to move it closer.
If a smoke detector keeps beeping even when there is no smoke, it may need cleaning or new batteries.
If a generator's fuel sensor is faulty, it may show full when the tank is empty. You need to repair or replace the sensor.
Sensor Problem Example
[ Sensor gives wrong reading ]
|
V
[ Check connections ]
|
V
[ Check power ]
|
V
[ Recalibrate ]
|
V
[ Test again ]
|
V
[ Works? ]
/ \
YES NO
/ \
V V
[Done] [Replace sensor]
Sensors can have problems. Common issues include loose wires, wrong calibration, and incorrect thresholds. Learning to fix these problems is part of robotics.
Real robots use many sensors together to do complex tasks.
Understanding how real robots use sensors helps you design your own robots better.
| Robot | Sensors Used | Purpose |
|---|---|---|
| Vacuum Robot | Touch, ultrasonic, cliff sensors | Avoid obstacles, detect stairs |
| Self-Driving Car | Camera, radar, ultrasonic, GPS | Navigate roads, avoid accidents |
| Mars Rover | Camera, temperature, radiation | Explore Mars, collect data |
| Surgical Robot | Force sensors, cameras | Perform precise surgery |
| Drone | Gyroscope, accelerometer, GPS | Fly stably, navigate |
A robot vacuum cleaner uses touch sensors to know when it bumps into a chair. It uses cliff sensors to know when it is near stairs.
A school science project robot might use a light sensor to follow a black line on a white board.
A robotic toy uses sound sensors to respond to claps.
A Nigerian-made robot used in a university might use ultrasonic sensors to navigate a maze.
Real Robot: Vacuum Cleaner
+-------------------+
| Robot Vacuum |
| +-----------+ |
| | Touch | |
| | Sensor | |
| +-----------+ |
| +-----------+ |
| | Ultrasonic| |
| | Sensor | |
| +-----------+ |
| +-----------+ |
| | Cliff | |
| | Sensor | |
| +-----------+ |
+-------------------+
|
V
Cleans floor safely
Real robots use many sensors together. Each sensor helps the robot understand a different part of the world.
Designing a sensor-based robot means choosing the right sensors and writing programs that use them.
Not all sensors are right for all tasks. You must choose the best sensor for the job.
If you want a robot to follow a line, you need a light sensor. If you want a robot to avoid walls, you need an ultrasonic sensor.
If you want a robot to sort coloured balls, you need a colour sensor.
If you want a robot to open the door when someone claps, you need a sound sensor.
If you want a robot to help farmers detect ripe tomatoes, you need a colour sensor.
Sensor-Based Robot Design
[ What should robot do? ]
|
V
[ What must it sense? ]
|
V
[ Choose sensors ]
|
V
[ Mount sensors ]
|
V
[ Write program ]
|
V
[ Test and improve ]
Designing a sensor-based robot means choosing the right sensors for the job and writing programs that use them.
| Word | Simple Definition |
|---|---|
| Sensor | A device that detects something in the environment. |
| Perception | Understanding what sensors detect. |
| Touch Sensor | A sensor that detects when something presses it. |
| Ultrasonic Sensor | A sensor that uses sound waves to measure distance. |
| Light Sensor | A sensor that detects brightness. |
| Sound Sensor | A sensor that detects noise. |
| Colour Sensor | A sensor that detects colours. |
| Distance Sensor | A sensor that measures how far away something is. |
| Sensor Fusion | Using multiple sensors together. |
| Calibration | Adjusting a sensor so it works correctly. |
| Range | How far a sensor can detect. |
| Threshold | The point where the robot decides to act. |
| Sensor Program | A program that reads sensor data and makes decisions. |
| Concept | Real-Life Example |
|---|---|
| Sensor | Your phone's light sensor adjusts screen brightness. |
| Perception | You see dark clouds and perceive that it might rain. |
| Touch Sensor | A doorbell button detects your press. |
| Ultrasonic Sensor | Bats use sound waves to navigate in the dark. |
| Light Sensor | Street lights turn on automatically when it gets dark. |
| Sound Sensor | Clap-activated toys respond to sound. |
| Colour Sensor | Factories sort fruits by colour. |
| Distance Sensor | Cars beep when you are too close to another car. |
| Sensor Fusion | Self-driving cars use many sensors together. |
| Concept | Nigerian Example |
|---|---|
| Sensor | A generator's fuel sensor warns when fuel is low. |
| Perception | A driver hears a horn and perceives another car wants to overtake. |
| Touch Sensor | A car horn responds when you press it. |
| Ultrasonic Sensor | A car reversing in Lagos uses parking sensors. |
| Light Sensor | Solar panels use light sensors to know when the sun is shining. |
| Sound Sensor | A clap-activated light in a compound. |
| Colour Sensor | A tomato sorting machine separates ripe and unripe tomatoes. |
| Distance Sensor | A danfo driver uses his eyes to judge distance. |
| Sensor Fusion | A trader uses eyes and ears to serve customers. |
| Concept | Everyday Example |
|---|---|
| Sensor | Your phone's fingerprint sensor unlocks the phone. |
| Perception | You smell food and know it is ready. |
| Touch Sensor | A light switch responds to your touch. |
| Ultrasonic Sensor | A car parking sensor beeps when you are close. |
| Light Sensor | Your phone screen adjusts brightness automatically. |
| Sound Sensor | A baby monitor picks up sounds. |
| Colour Sensor | A washing machine sorts clothes by colour. |
| Distance Sensor | A measuring tape tells you how long something is. |
| Mistake | Why It Is Wrong | How to Fix It |
|---|---|---|
| Not calibrating sensors | Sensor gives wrong readings. | Calibrate before use. |
| Using the wrong sensor | The robot cannot do the task. | Choose the right sensor for the job. |
| Ignoring sensor range | The robot misses obstacles far away. | Know the sensor's range. |
| Setting thresholds wrong | Robot reacts too early or too late. | Adjust thresholds carefully. |
| Not testing sensors | Problems go unnoticed. | Test sensors before using them. |
| Mounting sensors poorly | Sensors cannot detect correctly. | Mount sensors in the right position. |
+-------------------+
| Robot Brain |
| (computer) |
+-------------------+
| | | |
| | | |
V V V V
+-----+ +-----+ +-----+ +-----+
|Touch| |Ultra| |Light| |Sound|
|Sens | |Sonic| |Sens | |Sens |
+-----+ +-----+ +-----+ +-----+
( Start )
|
V
+----------------+
| Move forward |
+----------------+
|
V
+----------------+
| Touch sensor |
| pressed? |
+----------------+
/ \
YES NO
/ \
V V
+---------+ +-----------+
| Stop | | Keep |
| and turn| | moving |
+---------+ +-----------+
\ /
\ /
V V
( Repeat )
| Sensor | Detects | Best For |
|---|---|---|
| Touch | Physical contact | Collision detection |
| Ultrasonic | Distance using sound | Obstacle avoidance |
| Light | Brightness | Line following |
| Sound | Noise level | Clap control |
| Colour | Colours | Sorting objects |
| Distance | Distance | Navigation |
Step 1: Choose sensor
|
V
Step 2: Mount sensor
|
V
Step 3: Calibrate sensor
|
V
Step 4: Write program
|
V
Step 5: Test sensor
|
V
Step 6: Fix problems
|
V
Step 7: Done!
A sensor detects something in the environment. Sensors give robots the ability to sense the world.
Perception is how a robot understands what its sensors detect. It is the bridge between sensing and acting.
A touch sensor detects when something presses it. It helps robots detect collisions.
An ultrasonic sensor uses sound waves to measure distance. It helps robots avoid obstacles from far away.
A light sensor detects brightness. It helps robots follow lines and react to light changes.
A sound sensor detects noise. It helps robots react to claps, voices, and other sounds.
A colour sensor detects colours. It helps robots sort objects and follow coloured lines.
A distance sensor measures how far away an object is. It helps robots navigate.
Sensor fusion means using multiple sensors together. It gives the robot a better understanding of the world.
A sensor program reads sensor data and makes decisions. It tells the robot how to react.
Calibration means adjusting a sensor so it works correctly. It helps sensors understand normal conditions.
Range is how far a sensor can detect. Threshold is the point where the robot decides to act.
Sensors can have problems. Common issues include loose wires, wrong calibration, and incorrect thresholds.
Real robots use many sensors together. Each sensor helps the robot understand a different part of the world.
Designing a sensor-based robot means choosing the right sensors for the job and writing programs that use them.
In this module, you learned about sensors and perception. You learned that sensors are like a robot's senses. They help the robot detect the world around it.
You learned about many types of sensors: touch sensors, ultrasonic sensors, light sensors, sound sensors, colour sensors, and distance sensors. You learned how each one works and what it is used for.
You learned about perception — how the robot understands what its sensors detect. You learned about sensor fusion — using multiple sensors together. You learned about calibration, ranges, and thresholds.
You learned how to write sensor programs and how to design a sensor-based robot. You learned about common sensor problems and how to fix them.
Most importantly, you learned that sensors are what make robots truly interactive. Without sensors, a robot is blind and deaf. With sensors, a robot can understand and react to the world.
In the next module, you will learn about actuators and motion systems. You will learn how robots move and how to control their movement precisely. You will learn about motors, gears, and PID control.
But for now, take a moment to celebrate what you have learned. You have taken another big step in your journey to becoming a robotics expert. Well done!
Match the sensor on the left with what it detects on the right.
| Sensor | Detects |
|---|---|
| 1. Touch Sensor | A. Colours |
| 2. Ultrasonic Sensor | B. Physical contact |
| 3. Light Sensor | C. Noise |
| 4. Sound Sensor | D. Distance using sound |
| 5. Colour Sensor | E. Brightness |
| 6. Distance Sensor | F. Distance |
Answers: 1-B, 2-D, 3-E, 4-C, 5-A, 6-F
Title: Design a Sensor-Based Robot
Instructions:
Example:
Task: Robot avoids obstacles Sensors needed: - Ultrasonic sensor (to detect distance) - Touch sensor (to detect collision) Program: 1. Move forward 2. IF ultrasonic sensor detects obstacle, THEN turn right 3. IF touch sensor is pressed, THEN stop and turn 4. Repeat from Step 1
Title: Sensor Scavenger Hunt
Instructions:
Example:
| Device | Sensor | What It Detects |
|---|---|---|
| Phone | Touch sensor | Your finger press |
| Doorbell | Touch sensor | Button press |
| TV remote | Infrared sensor | Remote signals |
| Fridge | Temperature sensor | Coldness |
| Car | Parking sensor | Distance to objects |
Title: Build a Line-Following Robot
Goal: Create a robot that follows a black line on a white surface using a light sensor.
Steps:
Deliverables:
Title: Build an Obstacle-Avoiding Robot
Instructions:
Grading Criteria:
| Criteria | Points |
|---|---|
| Robot avoids obstacles correctly | 40 |
| Uses ultrasonic sensor properly | 20 |
| Program uses if/else and loops | 20 |
| Report is clear | 20 |
| Total | 100 |
In Module Three, you will learn about Actuators and Motion Systems. You will learn how robots move and how to control their movement precisely.
You will learn about:
To prepare for Module Three:
Get ready for an exciting journey into the world of robot movement!
Congratulations! You have completed Module Two of Fundamentals of Robotics Level Two. You have learned about sensors and perception.
You learned that sensors are like a robot's senses. They help the robot detect the world. You learned about touch sensors, ultrasonic sensors, light sensors, sound sensors, colour sensors, and distance sensors.
You learned about perception — how the robot understands what its sensors detect. You learned about sensor fusion, calibration, ranges, and thresholds.
You learned how to write sensor programs and how to design a sensor-based robot. You learned about common sensor problems and how to fix them.
You also learned many examples from Nigeria, from your home, from school, and from everyday life. You learned through stories, illustrations, and activities.
Now you are ready for Module Three: Actuators and Motion Systems. In Module Three, you will learn how robots move. You will learn about motors, gears, and how to control movement precisely. You will learn how to make your robot move smoothly and accurately.
But before you move on, take a moment to review this module. Make sure you understand the key ideas. Practise writing sensor programs. Draw diagrams. Test your sensors. The more you practise, the better you will become.
You are doing great. Keep learning. Keep exploring. Keep building. The world of robotics is waiting for you!
End of Module Two
Next: Module Three — Actuators and Motion Systems
Welcome to Module Three! In Module One, you learned how to write programs for robots. In Module Two, you learned how robots use sensors to perceive the world. Now you will learn how robots move.
Think about your body. You have a brain that decides what to do. You have senses that tell you what is happening around you. And you have muscles that make you move. Your muscles are what turn your decisions into action.
Robots are the same. They have a brain (the computer). They have senses (the sensors). And they have actuators — the parts that make them move. Actuators are like a robot's muscles.
In this module, you will learn about different types of actuators. You will learn about motors, gears, and wheels. You will learn how robots move forward, backward, and turn. You will learn how to control speed and direction. You will learn about PID control, which helps robots move smoothly and precisely.
This is where robotics becomes really fun. Your robot will stop being a machine that just thinks. It will become a machine that moves.
Let us begin!
By the end of this module, you will be able to:
Once upon a time, in the city of Ibadan, Nigeria, there lived a boy named Tunde. Tunde loved robots. He had built a small robot named Bola using a kit his uncle sent from Lagos.
Bola had two wheels, a motor, and a small computer brain. Tunde could program Bola to move forward, backward, left, and right. But there was a problem. Bola did not move smoothly.
When Tunde told Bola to go forward, Bola would move — but she would wobble. She would drift to the left. Then she would drift to the right. She would move in a zigzag pattern instead of a straight line.
Tunde was frustrated. "Bola, why can't you just go straight?" he asked.
Bola did not answer. She just wobbled.
Tunde decided to investigate. He opened Bola's body and looked inside. He saw the two motors. One motor was slightly faster than the other. That was why Bola was drifting.
"Ah!" Tunde said. "The motors are not moving at the same speed. I need to fix this."
Tunde went to his father, who was an engineer. "Papa, my robot wobbles because the motors are not equal. What can I do?"
His father smiled. "Tunde, you need to learn about motor control. You need to learn how to make the motors move at the same speed. You also need to learn about PID control."
"What is PID control?" Tunde asked.
"It is a way of controlling motors so they move smoothly and accurately," his father explained. "It checks the speed, compares it to what you want, and adjusts automatically."
Tunde was excited. He learned about PID control. He learned how to use encoders to measure how fast each wheel was turning. He wrote a new program that adjusted the motor speeds automatically.
He uploaded the program and pressed START. Bola began to move. She moved forward. She moved straight. She did not wobble. She did not drift. She moved smoothly and accurately.
Tunde jumped for joy. "Bola, you are perfect!" he shouted.
Bola moved smoothly across the floor. She was no longer a wobbly robot. She was a precise robot.
That is what you will learn in this module. You will learn how to make your robot move smoothly and accurately. You will learn about actuators, motors, gears, and PID control.
Let us begin!
An actuator is a part that makes a robot move. It takes energy and turns it into motion.
Without actuators, a robot cannot move. It can think. It can sense. But it cannot act. Actuators are what turn a robot's decisions into movement.
Think of your muscles. When you decide to lift your hand, your brain sends a signal to your muscles. Your muscles contract and your hand moves. Actuators are like a robot's muscles. They move when the robot's brain tells them to.
When you press the button on an electric fan, the fan's motor (an actuator) spins the blades.
When the school bell rings, an actuator (a small hammer) hits the bell to make sound.
When you press the button on a blender, the motor (an actuator) spins the blades to blend food.
When you turn on a generator, the motor (an actuator) starts running to produce electricity.
Actuator in a Robot
+-------------------+
| Robot Brain |
| (decides to |
| move) |
+-------------------+
|
| (sends signal)
V
+-------------------+
| Actuator |
| (motor) |
+-------------------+
|
| (creates motion)
V
+-------------------+
| Robot moves |
+-------------------+
An actuator is a part that makes a robot move. It is like a robot's muscle. Without actuators, robots cannot move.
A motor is a machine that turns electricity into movement. It is the most common type of actuator in robotics.
Motors are what make robot wheels turn. They are what make robot arms lift. They are what make robot joints bend. Without motors, most robots cannot move.
Think of a motor like a spinning top. When you push a spinning top, it spins. A motor spins when you give it electricity. The spinning can be used to turn wheels, lift arms, or move joints.
Your electric fan has a motor. When you plug it in, the motor spins the blades.
A pencil sharpener has a motor. When you press the pencil, the motor spins the blade.
Your washing machine has a motor. It spins the drum to wash clothes.
A grinding machine in the market has a motor. It spins the grinding stone to grind pepper and tomatoes.
Motor in a Robot
+-------------------+
| Battery |
| (electricity) |
+-------------------+
|
| (electric current)
V
+-------------------+
| Motor |
| (spins) |
+-------------------+
|
| (mechanical motion)
V
+-------------------+
| Wheel turns |
+-------------------+
|
V
+-------------------+
| Robot moves |
+-------------------+
A motor turns electricity into movement. Motors are the most common actuators in robots. They make wheels turn, arms lift, and joints bend.
There are three main types of motors used in robotics: DC motors, servo motors, and stepper motors.
Different motors are good for different jobs. A DC motor is good for spinning wheels. A servo motor is good for moving arms to exact positions. A stepper motor is good for precise movements.
Think of three different vehicles:
| Motor Type | How It Works | Best For | Example |
|---|---|---|---|
| DC Motor | Spins continuously when powered | Wheels, fans, simple movement | Robot car wheels |
| Servo Motor | Moves to a specific angle | Arms, joints, steering | Robot arm |
| Stepper Motor | Moves in exact steps | Precise positioning, 3D printers | Printer head |
A fan uses a DC motor. A remote-controlled car uses a servo motor for steering. A 3D printer uses stepper motors.
A school project robot might use DC motors for wheels and a servo motor for a gripper.
A blender uses a DC motor. A washing machine uses a servo motor for the door lock. A sewing machine uses a stepper motor.
A POS machine uses a stepper motor to print receipts. A generator uses a DC motor for starting.
Types of Motors DC Motor: +--------+ | DC | | Motor | +--------+ | V Spins continuously Servo Motor: +--------+ | Servo | | Motor | +--------+ | V Moves to exact angle Stepper Motor: +--------+ | Stepper| | Motor | +--------+ | V Moves in exact steps
There are three main types of motors: DC motors, servo motors, and stepper motors. Each type is good for different jobs.
Gears are wheels with teeth that fit together. They change the speed and power of a motor.
Motors spin very fast. But sometimes you need slower, more powerful movement. Gears help you trade speed for power. They also help you change the direction of movement.
Think of riding a bicycle. When you shift to a low gear, you pedal easily but go slowly. When you shift to a high gear, you pedal harder but go faster. Gears change how speed and power work together.
A car has gears. First gear is slow but powerful (good for starting). Fifth gear is fast but less powerful (good for highways).
A pencil sharpener has gears. They make it easier to sharpen pencils.
A hand mixer has gears. They let you mix slowly or quickly.
A grinding machine has gears. They make the grinding stone turn slowly but with great force.
Gears Changing Speed Small Gear (fast) --> Large Gear (slow but powerful) ___ ___ / \ / \ | 1 |-----| 2 | \___/ \___/ Gear 1: 10 teeth, spins fast Gear 2: 30 teeth, spins slow but powerful
Gears change the speed and power of a motor. They help you trade speed for power. They also change the direction of movement.
Speed is how fast something moves. Torque is how much turning force something has. There is a trade-off between them.
You cannot have both maximum speed and maximum torque at the same time. If you want more speed, you lose torque. If you want more torque, you lose speed. Understanding this helps you design better robots.
Think of a hammer. A small hammer moves fast but has little force. A big hammer moves slow but has great force. Speed and torque work the same way.
| Characteristic | Speed | Torque |
|---|---|---|
| Meaning | How fast something moves | How much turning force |
| Example | A bicycle going fast | A truck pulling a heavy load |
| Trade-off | More speed = less torque | More torque = less speed |
A racing car has high speed but low torque. A tractor has high torque but low speed.
A pencil sharpener needs torque to sharpen. A fan needs speed to blow air.
A blender needs speed to blend. A mortar and pestle need torque to pound yam.
A grinding machine needs torque to grind pepper. A fan needs speed to cool the room.
Speed vs Torque High Speed, Low Torque: Fast spinning wheel +--------+ | --> | +--------+ Can move fast but cannot push heavy things Low Speed, High Torque: Slow spinning wheel +--------+ | -> | +--------+ Can push heavy things but moves slowly
Speed is how fast something moves. Torque is how much turning force it has. There is a trade-off: more speed means less torque, and more torque means less speed.
A drive train is the system that connects the motor to the wheels. It determines how the robot moves.
Different drive trains give robots different abilities. Some can turn in place. Some can move sideways. Some can only move forward and backward.
Think of different vehicles. A car has four wheels and can turn. A motorcycle has two wheels and can lean. A tank has tracks and can turn in place. Each vehicle has a different drive train.
| Drive Train | How It Works | Example |
|---|---|---|
| Differential Drive | Two wheels, each with its own motor | Most robot cars |
| Holonomic Drive | Wheels that can move in any direction | Robots that move sideways |
| Non-Holonomic Drive | Wheels that cannot move sideways | Cars, bicycles |
A car has a non-holonomic drive. It cannot move sideways. It must turn to change direction.
A robot with differential drive can turn in place by spinning its wheels in opposite directions.
A vacuum robot has a differential drive. It can turn in place to clean corners.
A danfo bus has a non-holonomic drive. It cannot move sideways. It must turn to change direction.
Differential Drive
Left Wheel Right Wheel
| |
V V
+-------+ +-------+
| Motor | | Motor |
+-------+ +-------+
| |
V V
+-------+ +-------+
| Wheel | | Wheel |
+-------+ +-------+
To go forward: both wheels spin forward
To turn left: left wheel slows, right wheel speeds up
To turn right: right wheel slows, left wheel speeds up
To spin in place: left wheel forward, right wheel backward
A drive train connects the motor to the wheels. Different drive trains give robots different abilities. Differential drive is the most common in robots.
Motor control means telling the motor how fast to spin and in which direction.
If you cannot control the motor, you cannot control the robot. Motor control lets you make the robot go fast, slow, forward, or backward.
Think of a fan regulator. You can set it to speed 1, 2, 3, 4, or 5. Motor control in robotics works the same way. You can set the motor to different speeds.
A fan regulator controls the speed of the fan. That is motor control.
A remote-controlled car has a controller that changes the motor speed.
A blender has different speed settings. That is motor control.
A generator has a throttle that controls the engine speed. That is motor control.
Motor Control
+-------------------+
| Robot Brain |
+-------------------+
|
| (sends signal)
V
+-------------------+
| Motor Driver |
| (controls |
| speed and |
| direction) |
+-------------------+
|
| (sends power)
V
+-------------------+
| Motor |
| (spins) |
+-------------------+
|
V
+-------------------+
| Robot moves |
+-------------------+
Motor control means telling the motor how fast to spin and in which direction. PWM is a common way to control motor speed.
PWM stands for Pulse Width Modulation. It is a way to control motor speed by turning the motor on and off very quickly.
If you turn a motor on and off very quickly, it spins at medium speed. If you leave it on longer, it spins faster. If you leave it off longer, it spins slower. PWM lets you control speed without wasting energy.
Think of a light switch. If you turn it on and off very fast, the light looks dim. If you leave it on longer, the light looks brighter. PWM works the same way with motors.
PWM Signal Full speed: +-------------------+ | | | | +-------------------+ Half speed: +----+ +----+ | | | | | | | | +----+ +----+ Low speed: +--+ +--+ | | | | | | | | +--+ +--+
LED lights use PWM to dim. The light turns on and off very fast to create different brightness levels.
A school project might use PWM to control the speed of a robot car.
A fan with a dimmer switch uses PWM to control speed.
A rechargeable fan uses PWM to save battery power.
PWM is a way to control motor speed by turning the motor on and off very quickly. It saves energy and gives smooth control.
An encoder is a sensor that measures how much a motor has turned. It tells the robot how far it has travelled.
Without an encoder, a robot does not know how far it has moved. It might go too far or not far enough. Encoders help robots move precisely.
Think of a pedometer. It counts your steps. An encoder counts the turns of a motor. It tells the robot how far it has gone.
A car's speedometer uses an encoder to measure how fast the car is going.
A measuring wheel uses an encoder to measure distance.
A treadmill uses an encoder to measure how far you have run.
A POS machine uses an encoder to measure how much paper has been printed.
Encoder on a Motor
+-------------------+
| Motor |
| (spins) |
+-------------------+
|
| (shaft turns)
V
+-------------------+
| Encoder |
| (counts turns) |
+-------------------+
|
| (sends count)
V
+-------------------+
| Robot Brain |
| knows how far |
| it has moved |
+-------------------+
An encoder measures how much a motor has turned. It helps robots know how far they have travelled. Encoders are important for precise movement.
PID control is a way to control motors so they move smoothly and accurately. PID stands for Proportional, Integral, and Derivative.
Without PID, motors might overshoot. They might go too fast, then slow down, then speed up again. PID keeps the motor steady.
Think of driving a car. You want to go at 60 km/h. If you go too fast, you slow down. If you go too slow, you speed up. PID does this automatically for motors.
Cruise control in a car uses PID to keep a steady speed.
A robot that follows a line uses PID to stay on the line.
An air conditioner uses PID to keep the room at a steady temperature.
A generator's governor uses PID to keep the engine at a steady speed.
PID Control Loop
+-------------------+
| Target Speed |
| (what you want) |
+-------------------+
|
V
+-------------------+
| Compare with |
| actual speed |
+-------------------+
|
V
+-------------------+
| Calculate |
| error |
+-------------------+
|
V
+-------------------+
| Adjust motor |
| speed |
+-------------------+
|
V
+-------------------+
| Motor moves |
+-------------------+
|
| (feedback)
V
+-------------------+
| Encoder measures|
| actual speed |
+-------------------+
|
+--------> (back to compare)
PID control keeps motors moving smoothly and accurately. It compares the target speed with the actual speed and adjusts automatically.
Combining sensors and actuators means using both together to make the robot react to the world.
Sensors tell the robot what is happening. Actuators make the robot move. Together, they make the robot intelligent and responsive.
Think of driving a car. Your eyes are sensors. Your hands and feet are actuators. You see the road, then you turn the steering wheel. Sensors and actuators work together.
A self-driving car uses sensors to see the road and actuators to turn the steering wheel and press the brakes.
A line-following robot uses a light sensor to see the line and motors to stay on it.
A vacuum robot uses sensors to detect dirt and motors to move around.
A robot that sorts tomatoes uses a colour sensor to see the colour and a motor to push the tomato into the right basket.
Sensors + Actuators
+-------------+
| Sensor |
| (sees) |
+-------------+
|
V
+-------------+
| Robot |
| Brain |
| (decides) |
+-------------+
|
V
+-------------+
| Actuator |
| (moves) |
+-------------+
|
V
+-------------+
| Robot |
| acts |
+-------------+
Sensors tell the robot what is happening. Actuators make the robot move. Together they make the robot intelligent and responsive.
Debugging motor problems means finding and fixing issues that stop motors from working correctly.
Motors can fail. They can spin too fast. They can spin too slow. They can spin in the wrong direction. Debugging helps you fix these problems.
| Problem | Cause | Solution |
|---|---|---|
| Motor does not spin | Loose wire or dead battery | Check connections and power |
| Motor spins too fast | Too much voltage | Reduce voltage or use PWM |
| Motor spins too slow | Too little voltage or heavy load | Increase voltage or reduce load |
| Motor spins wrong direction | Wires reversed | Swap the wires |
| Motor jitters | Unstable power | Use a stable power supply |
If your fan does not spin, you check if it is plugged in. That is debugging.
If your robot car does not move, you check the motor wires.
If your blender does not spin, you check the power.
If your generator does not start, you check the fuel and battery.
Motor Debugging
[ Motor not working ]
|
V
[ Check power ]
|
V
[ Check connections ]
|
V
[ Check motor ]
|
V
[ Fix problem ]
|
V
[ Test again ]
|
V
[ Works? ]
/ \
YES NO
/ \
V V
[Done] [Replace motor]
Debugging motor problems means finding and fixing issues. Common problems include loose wires, wrong voltage, and reversed connections.
Designing a motion system means choosing the right motors, gears, and drive train for your robot.
Not all motors are right for all robots. A small robot needs small motors. A big robot needs big motors. Choosing the right parts makes your robot work better.
A robot that needs to climb stairs needs high torque. A robot that needs to race needs high speed.
A school robot that follows a line needs precise motors and encoders.
A robot vacuum needs motors that are quiet and efficient.
A robot that helps farmers plant seeds needs motors that are strong and durable.
Motion System Design
[ What should robot do? ]
|
V
[ How much torque? ]
|
V
[ Choose motor ]
|
V
[ Choose gears ]
|
V
[ Choose drive train ]
|
V
[ Build and test ]
Designing a motion system means choosing the right motors, gears, and drive train for your robot. It starts with understanding what the robot needs to do.
Real robots use different motion systems depending on what they need to do.
| Robot | Motion System | Purpose |
|---|---|---|
| Robot Vacuum | Differential drive with DC motors | Clean floors |
| Self-Driving Car | Electric motors with servo steering | Drive on roads |
| Mars Rover | Six wheels with independent motors | Explore Mars |
| Robot Arm | Servo motors for each joint | Pick and place objects |
| Drone | Brushless DC motors with propellers | Fly in the air |
A robot vacuum uses differential drive to move around furniture.
A school project robot might use a simple DC motor and wheels.
A robotic toy might use a servo motor to move its arms.
A Nigerian-made robot used in a university might use stepper motors for precise movement.
Real Robot: Robot Arm
+-------------------+
| Base |
| (motor 1) |
+-------------------+
|
V
+-------------------+
| Shoulder |
| (motor 2) |
+-------------------+
|
V
+-------------------+
| Elbow |
| (motor 3) |
+-------------------+
|
V
+-------------------+
| Gripper |
| (motor 4) |
+-------------------+
Real robots use different motion systems for different jobs. Each robot's motion system is designed for its specific task.
Safety in motion systems means making sure the robot does not hurt people or damage things.
Robots can be dangerous. They can move fast. They can be strong. They can hurt people if they are not designed safely.
Industrial robots have safety cages to keep people away.
In a robotics lab, students must wear safety goggles.
Robot vacuum cleaners have bump sensors to avoid hitting people.
A robot used in a factory in Lagos has emergency stop buttons.
Safety First
+-------------------+
| Emergency Stop |
| Button |
+-------------------+
|
V
+-------------------+
| Robot stops |
| immediately |
+-------------------+
Safety in motion systems means making sure robots do not hurt people or damage things. Always follow safety rules.
| Word | Simple Definition |
|---|---|
| Actuator | A part that makes a robot move. |
| Motor | A machine that turns electricity into movement. |
| DC Motor | A motor that spins continuously when powered. |
| Servo Motor | A motor that moves to a specific angle. |
| Stepper Motor | A motor that moves in exact steps. |
| Gears | Wheels with teeth that change speed and power. |
| Speed | How fast something moves. |
| Torque | How much turning force something has. |
| Drive Train | The system that connects the motor to the wheels. |
| PWM | Pulse Width Modulation — a way to control motor speed. |
| Encoder | A sensor that measures how much a motor has turned. |
| PID Control | A way to control motors smoothly and accurately. |
| Differential Drive | A drive train with two wheels, each with its own motor. |
| Holonomic Drive | A drive train that can move in any direction. |
| Non-Holonomic Drive | A drive train that cannot move sideways. |
| Concept | Real-Life Example |
|---|---|
| Actuator | Your muscles move your body. |
| Motor | An electric fan spins its blades. |
| DC Motor | A toy car uses a DC motor to move. |
| Servo Motor | A remote-controlled car uses a servo for steering. |
| Stepper Motor | A 3D printer uses stepper motors for precise movement. |
| Gears | A bicycle uses gears to change speed. |
| Speed vs Torque | A racing car has speed. A tractor has torque. |
| Drive Train | A car has a non-holonomic drive. |
| PWM | A dimmer switch uses PWM to control light brightness. |
| Encoder | A treadmill measures how far you run. |
| PID Control | Cruise control in a car keeps a steady speed. |
| Concept | Nigerian Example |
|---|---|
| Actuator | Your legs move you when you walk. |
| Motor | A grinding machine uses a motor to grind pepper. |
| DC Motor | A generator uses a DC motor for starting. |
| Servo Motor | A POS machine uses a servo motor for the printer. |
| Stepper Motor | A POS machine uses a stepper motor to print receipts. |
| Gears | A grinding machine uses gears to turn the stone. |
| Speed vs Torque | A grinding machine needs torque. A fan needs speed. |
| Drive Train | A danfo bus has a non-holonomic drive. |
| PWM | A rechargeable fan uses PWM to save battery. |
| Encoder | A POS machine uses an encoder to measure paper. |
| PID Control | A generator's governor uses PID to keep steady speed. |
| Concept | Everyday Example |
|---|---|
| Actuator | Your hand moves when you write. |
| Motor | An electric toothbrush uses a motor to brush. |
| DC Motor | A blender uses a DC motor to blend. |
| Servo Motor | A washing machine uses a servo for the door lock. |
| Stepper Motor | A sewing machine uses a stepper for precise stitching. |
| Gears | A hand mixer uses gears to mix at different speeds. |
| Speed vs Torque | A pencil sharpener needs torque. A fan needs speed. |
| Drive Train | A vacuum robot has a differential drive. |
| PWM | An LED light dimmer uses PWM. |
| Encoder | A treadmill measures your run. |
| PID Control | An air conditioner keeps a steady temperature. |
| Mistake | Why It Is Wrong | How to Fix It |
|---|---|---|
| Using the wrong motor | The robot cannot do the task. | Choose the right motor for the job. |
| Ignoring torque | The robot cannot move heavy loads. | Calculate torque needs first. |
| Not using gears | The robot is too fast or too weak. | Use gears to adjust speed and torque. |
| Not using encoders | The robot does not know how far it moved. | Add encoders for feedback. |
| Not using PID | The robot moves unevenly. | Use PID to smooth motion. |
| Ignoring safety | Someone could get hurt. | Always follow safety rules. |
+-------------------+
| Robot Brain |
+-------------------+
|
| (signal)
V
+-------------------+
| Motor Driver |
+-------------------+
|
| (power)
V
+-------------------+
| Motor |
+-------------------+
|
| (motion)
V
+-------------------+
| Wheel |
+-------------------+
|
V
+-------------------+
| Robot moves |
+-------------------+
( Start )
|
V
+----------------+
| Motor works? |
+----------------+
/ \
YES NO
/ \
V V
+---------+ +-----------+
| Done | | Check |
| | | power |
+---------+ +-----------+
|
V
+-----------+
| Check |
| wires |
+-----------+
|
V
+-----------+
| Check |
| motor |
+-----------+
|
V
+-----------+
| Fix |
+-----------+
|
V
+-----------+
| Test |
+-----------+
| Drive Train | Can Move Sideways? | Can Turn in Place? | Example |
|---|---|---|---|
| Differential | No | Yes | Robot vacuum |
| Holonomic | Yes | Yes | Omni-directional robot |
| Non-Holonomic | No | No | Car |
Step 1: Choose motor
|
V
Step 2: Choose gears
|
V
Step 3: Choose drive train
|
V
Step 4: Mount motors
|
V
Step 5: Add encoders
|
V
Step 6: Write program
|
V
Step 7: Test
|
V
Step 8: Fix and improve
An actuator is a part that makes a robot move. It is like a robot's muscle.
A motor turns electricity into movement. Motors are the most common actuators in robots.
There are three main types of motors: DC motors, servo motors, and stepper motors. Each type is good for different jobs.
Gears change the speed and power of a motor. They help you trade speed for power.
Speed is how fast something moves. Torque is how much turning force it has. There is a trade-off between them.
A drive train connects the motor to the wheels. Different drive trains give robots different abilities.
Motor control means telling the motor how fast to spin and in which direction.
PWM is a way to control motor speed by turning the motor on and off very quickly.
An encoder measures how much a motor has turned. It helps robots know how far they have travelled.
PID control keeps motors moving smoothly and accurately. It compares target speed with actual speed and adjusts automatically.
Sensors tell the robot what is happening. Actuators make the robot move. Together they make the robot intelligent and responsive.
Debugging motor problems means finding and fixing issues. Common problems include loose wires, wrong voltage, and reversed connections.
Designing a motion system means choosing the right motors, gears, and drive train for your robot.
Real robots use different motion systems for different jobs. Each robot's motion system is designed for its specific task.
Safety in motion systems means making sure robots do not hurt people or damage things. Always follow safety rules.
In this module, you learned about actuators and motion systems. You learned that actuators are like a robot's muscles. They make the robot move.
You learned about motors — the most common actuators. You learned about DC motors, servo motors, and stepper motors. You learned how gears change speed and power. You learned about the trade-off between speed and torque.
You learned about drive trains — differential, holonomic, and non-holonomic. You learned how to control motor speed and direction using PWM. You learned about encoders and how they measure movement. You learned about PID control and how it keeps motion smooth.
You learned how to combine sensors and actuators. You learned how to debug motor problems. You learned how to design a motion system. You learned about real robots and their motion systems. You learned about safety.
Most importantly, you learned that motion is what makes robots useful. Without motion, robots are just computers. With motion, robots can do work, help people, and explore the world.
In the next module, you will learn about Autonomous Navigation and Behaviour. You will learn how robots navigate from one place to another. You will learn about path planning, obstacle avoidance, and behaviour composition.
But for now, take a moment to celebrate what you have learned. You have taken another big step in your journey to becoming a robotics expert. Well done!
Match the term on the left with its definition on the right.
| Term | Definition |
|---|---|
| 1. Actuator | A. How much turning force something has |
| 2. Motor | B. A part that makes a robot move |
| 3. Gears | C. A way to control motor speed |
| 4. Torque | D. A machine that turns electricity into movement |
| 5. PWM | E. Wheels with teeth that change speed and power |
| 6. Encoder | F. A sensor that measures motor turns |
| 7. PID Control | G. A way to control motors smoothly |
Answers: 1-B, 2-D, 3-E, 4-A, 5-C, 6-F, 7-G
Title: Design a Robot That Moves Smoothly
Instructions:
Example:
Task: Robot follows a line Motors needed: - Two DC motors for wheels - Encoders for feedback Drive train: Differential drive Program: 1. Read light sensor 2. IF sensor sees black, THEN turn left 3. IF sensor sees white, THEN turn right 4. Use PID to keep speed steady 5. Repeat
Title: Motor Scavenger Hunt
Instructions:
Example:
| Device | Motor Type | What It Does |
|---|---|---|
| Fan | DC Motor | Spins blades to move air |
| Blender | DC Motor | Spins blades to blend food |
| Washing Machine | Servo Motor | Locks door and spins drum |
| POS Machine | Stepper Motor | Prints receipts |
| Generator | DC Motor | Starts the engine |
Title: Build a Line-Following Robot with PID
Goal: Create a robot that follows a black line smoothly using PID control.
Steps:
Deliverables:
Title: Build an Obstacle-Avoiding Robot with Smooth Motion
Instructions:
Grading Criteria:
| Criteria | Points |
|---|---|
| Robot avoids obstacles correctly | 30 |
| Robot moves smoothly | 20 |
| Uses encoders and PID | 20 |
| Program uses if/else and loops | 15 |
| Report is clear | 15 |
| Total | 100 |
In Module Four, you will learn about Autonomous Navigation and Behaviour. You will learn how robots navigate from one place to another without human help.
You will learn about:
To prepare for Module Four:
Get ready for an exciting journey into the world of autonomous robots!
Congratulations! You have completed Module Three of Fundamentals of Robotics Level Two. You have learned about actuators and motion systems.
You learned that actuators are like a robot's muscles. They make the robot move. You learned about motors — the most common actuators. You learned about DC motors, servo motors, and stepper motors.
You learned about gears and how they change speed and power. You learned about the trade-off between speed and torque. You learned about drive trains — differential, holonomic, and non-holonomic.
You learned about motor control using PWM. You learned about encoders and how they measure movement. You learned about PID control and how it keeps motion smooth.
You learned how to combine sensors and actuators. You learned how to debug motor problems. You learned how to design a motion system. You learned about real robots and their motion systems. You learned about safety.
You also learned many examples from Nigeria, from your home, from school, and from everyday life. You learned through stories, illustrations, and activities.
Now you are ready for Module Four: Autonomous Navigation and Behaviour. In Module Four, you will learn how robots navigate on their own. You will learn how to make your robot avoid obstacles, follow walls, and plan paths. You will learn how to combine simple behaviours into complex ones.
But before you move on, take a moment to review this module. Make sure you understand the key ideas. Practise writing motor control programs. Draw diagrams. Test your motors. The more you practise, the better you will become.
You are doing great. Keep learning. Keep exploring. Keep building. The world of robotics is waiting for you!
End of Module Three
Next: Module Four — Autonomous Navigation and Behaviour
Welcome to Module Four! In Module One, you learned how to write programs for robots. In Module Two, you learned how robots use sensors to perceive the world. In Module Three, you learned how robots move using actuators and motors. Now you will learn how robots navigate on their own.
Think about how you walk from your house to the market. You do not need someone to hold your hand. You look at the road. You avoid cars. You turn at the right corners. You remember where the market is. You do all of this autonomously — that means on your own.
Robots can also move on their own. They can navigate from one place to another. They can avoid obstacles. They can follow walls. They can plan paths. They can even remember where they have been.
In this module, you will learn how robots navigate. You will learn about obstacle avoidance, wall following, path planning, and behaviour composition. You will learn how to make your robot truly autonomous.
This is where robotics becomes really powerful. Your robot will stop being a machine that follows simple commands. It will become a machine that thinks and moves on its own.
Let us begin!
By the end of this module, you will be able to:
Once upon a time, in the city of Abuja, Nigeria, there lived a girl named Ngozi. Ngozi loved robotics. She had built a small robot named Musa using a kit her school provided.
Musa had two wheels, a motor, and a small computer brain. He had sensors: an ultrasonic sensor, a touch sensor, and a light sensor. Ngozi had programmed Musa to avoid obstacles and follow lines.
One day, Ngozi's school announced a Robot Maze Challenge. Robots from different schools would come and try to solve a maze. The robot that solved the maze fastest would win a prize.
Ngozi was excited. "Musa, we are going to win!" she said.
But there was a problem. Musa did not know how to navigate a maze. He could avoid obstacles. He could follow a line. But he could not plan a path. He could not remember where he had been. He could not find his way out.
Ngozi thought and thought. Then she had an idea. She would teach Musa to navigate autonomously.
She started with a simple behaviour: wall following. She programmed Musa to keep his right sensor close to the wall. If the wall was too far, he would turn right. If the wall was too close, he would turn left. If the wall was just right, he would go straight.
She tested Musa on a simple wall. Musa followed the wall perfectly. He moved along the wall without bumping into it.
Next, Ngozi added obstacle avoidance. She programmed Musa to check for obstacles in front. If there was an obstacle, he would turn and go around it.
She tested Musa in a simple maze. Musa followed the wall. He avoided obstacles. He found his way through the maze.
But Ngozi was not done. She added path planning. She programmed Musa to remember where he had been. He would mark paths he had already tried. He would not go in circles.
She added behaviour composition. She combined wall following, obstacle avoidance, and path planning into one complex behaviour.
She tested Musa in a complex maze. Musa followed the wall. He avoided obstacles. He remembered his path. He found his way out of the maze.
On the day of the challenge, Musa performed beautifully. He solved the maze in record time. Ngozi's school won first place.
But more importantly, Ngozi learned something powerful: robots can navigate on their own if you give them the right behaviours.
That is what you will learn in this module. You will learn how to make your robot navigate autonomously. You will learn about obstacle avoidance, wall following, path planning, and behaviour composition.
Let us begin!
Autonomous navigation means a robot can move from one place to another without a human controlling it.
Autonomous navigation lets robots work on their own. They can deliver packages, clean floors, explore dangerous places, and help people. Without autonomy, robots need constant human control.
Think of a self-driving car. It can take you from your house to the market without you touching the steering wheel. That is autonomous navigation. The car sees the road, avoids obstacles, and finds the way.
Robot vacuum cleaners navigate around your house on their own. They avoid furniture and clean the floor.
A robot in a science fair might navigate a maze on its own.
A robotic toy can follow you around the room without you controlling it.
A robot used in a Lagos warehouse can move goods from one shelf to another without a human pushing it.
Autonomous Navigation
+-------------------+
| Start Point |
+-------------------+
|
| (robot decides path)
V
+-------------------+
| Obstacle |
+-------------------+
|
| (robot avoids)
V
+-------------------+
| Turn |
+-------------------+
|
| (robot continues)
V
+-------------------+
| Destination |
+-------------------+
Autonomous navigation means a robot moves on its own from one place to another. It sees the world, makes decisions, and finds its way.
Obstacle avoidance is the ability of a robot to detect and avoid objects in its path.
If a robot cannot avoid obstacles, it will bump into things. It might get stuck. It might break. It might hurt someone. Obstacle avoidance keeps the robot safe.
Think of walking in a crowded market. You see people coming. You step aside. You do not bump into them. That is obstacle avoidance.
A self-driving car uses sensors to detect other cars, pedestrians, and bicycles. It slows down or turns to avoid them.
A robot in a classroom might avoid desks and chairs while moving around.
A robot vacuum avoids furniture, walls, and pets.
A robot in a market in Onitsha avoids people, stalls, and potholes while moving.
Obstacle Avoidance
+-------------------+
| Robot |
+-------------------+
|
| (moves forward)
V
+-------------------+
| Obstacle |
+-------------------+
|
| (sensor detects)
V
+-------------------+
| Robot turns |
+-------------------+
|
| (avoids)
V
+-------------------+
| Robot continues |
+-------------------+
Obstacle avoidance means detecting and avoiding objects. It keeps robots safe and prevents damage.
Wall following is a behaviour where a robot moves along a wall, keeping a constant distance from it.
Wall following helps robots navigate in corridors and mazes. It is a simple way to explore unknown spaces. It is used in many real robots.
Think of walking along a fence. You keep your hand close to the fence. If the fence moves away, you move closer. If the fence comes closer, you move away. That is wall following.
A robot vacuum uses wall following to clean along the edges of a room.
A robot in a maze might use wall following to find the exit.
A robot toy might follow the wall of a room.
A robot used in a hospital corridor might follow the wall to deliver medicine.
Wall Following Wall +-------------------+ | | | | | | +-------------------+ Robot: +-------+ | Robot | --> moves along wall +-------+ If wall is too far: +-------+ | Robot | --> turn right +-------+ If wall is too close: +-------+ | Robot | --> turn left +-------+
Wall following means moving along a wall while keeping a constant distance. It helps robots navigate corridors and mazes.
Path planning is the process of finding a route from one place to another. The robot decides the best way to go.
Without path planning, a robot might get lost. It might go in circles. It might take a long time. Path planning helps the robot reach its destination quickly and safely.
Think of going to school. You can take many routes. Some are shorter. Some are safer. Some have fewer cars. You choose the best route. That is path planning.
Your phone's map app plans a route from your house to your destination. It shows you the best way to go.
When you plan your school timetable, you decide which subjects to study first. That is path planning.
When you plan your morning routine, you decide the order of tasks. That is path planning.
A danfo driver plans his route to avoid traffic. He chooses roads with fewer hold-ups.
Path Planning Start | +--- Path 1 (short but blocked) | +--- Path 2 (long but clear) <-- Best path | +--- Path 3 (medium but rough) | V Destination
Path planning means finding the best route from one place to another. It helps robots reach their destination quickly and safely.
A behaviour is a way a robot acts. Simple behaviours do one thing. Complex behaviours combine many simple behaviours.
Complex tasks are made of simple tasks. If you can build simple behaviours, you can combine them to make complex behaviours. This makes programming easier.
Think of a football player. Simple behaviours: run, kick, pass, tackle. Complex behaviour: play a match. The match is made of many simple behaviours.
A self-driving car has simple behaviours: stay in lane, avoid obstacles, follow signs. Combined, they make the complex behaviour of driving.
A student has simple behaviours: read, write, listen. Combined, they make the complex behaviour of learning.
A cook has simple behaviours: chop, stir, fry, taste. Combined, they make the complex behaviour of cooking a meal.
A trader has simple behaviours: arrange goods, call customers, collect money. Combined, they make the complex behaviour of running a shop.
Simple and Complex Behaviours Simple Behaviours: +-----------+ +-----------+ +-----------+ | Move | | Turn | | Stop | | Forward | | Right | | | +-----------+ +-----------+ +-----------+ Complex Behaviour: +-------------------------------+ | Navigate from A to B | | (uses move, turn, stop, etc.) | +-------------------------------+
A behaviour is a way a robot acts. Simple behaviours do one thing. Complex behaviours combine many simple behaviours.
Behaviour composition means combining simple behaviours to make a complex behaviour.
Robots need to do complex tasks. You cannot write one giant program. You must combine simple behaviours. This makes programming easier and more flexible.
Think of building a house with LEGO blocks. Each block is simple. But when you put them together, you build a complex house. Behaviour composition is like building with LEGO blocks.
A robot vacuum combines wall following, obstacle avoidance, and cleaning into one complex behaviour.
A school robot combines line following, obstacle avoidance, and sound detection.
A robot toy combines walking, talking, and dancing.
A robot in a factory combines moving, picking, and placing.
Behaviour Composition
+-------------+ +-------------+
| Wall | | Obstacle |
| Following | | Avoidance |
+-------------+ +-------------+
\ /
\ /
V V
+-------------------+
| Complex |
| Behaviour |
| (Navigate maze) |
+-------------------+
Behaviour composition means combining simple behaviours to make complex behaviours. It makes programming easier and more flexible.
Mapping means creating a picture of the environment. The robot remembers where things are.
If a robot knows the map, it can plan better paths. It can remember where obstacles are. It can find its way back.
Think of a map of your school. You know where the classrooms are. You know where the library is. You know where the playground is. A robot's map works the same way.
A robot vacuum maps your house. It remembers where walls and furniture are. It cleans more efficiently.
A robot in a school can map the corridors and classrooms.
A robot toy can map your living room.
A robot in a market can map the stalls and walkways.
Mapping +-------------------+ | Room Map | | | | +---+ +---+ | | | | | | | | +---+ +---+ | | | | +---+ | | | | | | +---+ | +-------------------+ Robot remembers where walls and furniture are.
Mapping means creating a picture of the environment. Robots use maps to navigate better.
Localization means knowing where you are on the map. The robot figures out its position.
If a robot has a map but does not know where it is, the map is useless. Localization tells the robot where it is. It can then plan paths from its current position.
Think of using a map on your phone. The map shows you where you are. The blue dot is your location. That is localization.
Your phone's GPS knows where you are. It shows your location on the map.
You know where you are sitting in the classroom. That is localization.
You know which room you are in. That is localization.
A driver knows which bus stop he is at. That is localization.
Localization +-------------------+ | Map | | | | +---+ +---+ | | | | | | | | +---+ +---+ | | | | +---+ | | | X | <-- Robot is here | +---+ | +-------------------+ Robot knows its position on the map.
Localization means knowing where you are on the map. Robots use localization to navigate from their current position.
SLAM stands for Simultaneous Localization and Mapping. It means building a map and finding your position at the same time.
Sometimes a robot does not have a map. It must build one as it moves. SLAM lets the robot explore unknown places and create a map.
Think of exploring a new city. You do not have a map. As you walk, you draw a map in your mind. You also remember where you are on that map. That is SLAM.
A robot vacuum uses SLAM to map your house as it cleans.
A robot in a science fair might use SLAM to explore a maze.
A robot toy might use SLAM to explore your house.
A robot used in a new building in Abuja might use SLAM to map the building.
SLAM Process
[ Start with no map ]
|
V
[ Move and sense ]
|
V
[ Build map ]
|
V
[ Find position ]
|
V
[ Update map ]
|
V
[ Repeat ]
SLAM means building a map and finding your position at the same time. It lets robots explore unknown places.
Reactive navigation means reacting to the world immediately. Deliberative navigation means planning ahead before acting.
Both are useful. Reactive is fast. Deliberative is smart. Many robots use both.
Reactive: You touch a hot pot and pull your hand away. Deliberative: You plan your route to school before leaving.
| Type | How It Works | Good For | Example |
|---|---|---|---|
| Reactive | Reacts immediately to sensors | Avoiding sudden obstacles | Touch sensor stops robot |
| Deliberative | Plans before acting | Finding best path | Path planning |
Reactive: Slamming brakes to avoid an accident. Deliberative: Planning your route to avoid traffic.
Reactive: Answering a question in class. Deliberative: Studying for an exam.
Reactive: Catching a falling cup. Deliberative: Planning a meal.
Reactive: A driver swerving to avoid a pothole. Deliberative: A driver planning a route to avoid traffic.
Reactive vs Deliberative Reactive: Sensor -> Act immediately Deliberative: Sensor -> Think -> Plan -> Act
Reactive navigation reacts immediately. Deliberative navigation plans ahead. Both are useful in robotics.
Programming autonomous navigation means writing a program that lets a robot move on its own.
Without a program, a robot cannot navigate. The program tells the robot what to do with sensor data.
Think of giving directions to a friend. You say: "Go straight. If you see a wall, turn right. If you see a door, go in." That is a navigation program.
A self-driving car's program reads sensors, decides, and controls the car.
A robot in a maze reads sensors, decides, and moves.
A robot vacuum reads sensors, decides, and cleans.
A robot in a warehouse reads sensors, decides, and moves goods.
Navigation Program Loop
[ Read sensors ]
|
V
[ Decide action ]
|
V
[ Control motors ]
|
V
[ Move ]
|
V
[ Repeat ]
Programming autonomous navigation means writing a program that reads sensors, decides, and controls motors.
Debugging navigation problems means finding and fixing issues that stop the robot from navigating correctly.
Navigation is complex. Many things can go wrong. Debugging helps you find and fix problems.
| Problem | Cause | Solution |
|---|---|---|
| Robot gets stuck | Obstacle too close | Adjust avoidance distance |
| Robot goes in circles | Path planning error | Fix path planning algorithm |
| Robot misses destination | Localization error | Improve localization |
| Robot bumps into walls | Sensor not working | Check sensor and calibration |
| Robot moves too slow | Motor speed too low | Increase motor speed |
If your phone's GPS is wrong, you might take the wrong turn. That is a localization error.
If your robot keeps bumping into walls, check the ultrasonic sensor.
If your robot vacuum gets stuck under the sofa, adjust its height or sensors.
If a delivery robot in Lagos gets stuck in traffic, it needs a better path planning algorithm.
Debugging Navigation
[ Robot not navigating correctly ]
|
V
[ Check sensors ]
|
V
[ Check motors ]
|
V
[ Check program logic ]
|
V
[ Fix problem ]
|
V
[ Test again ]
Debugging navigation problems means finding and fixing issues. Common problems include getting stuck, going in circles, and missing destinations.
Real robots use autonomous navigation for many tasks.
| Robot | Navigation System | Purpose |
|---|---|---|
| Robot Vacuum | SLAM, obstacle avoidance, wall following | Clean floors |
| Self-Driving Car | GPS, cameras, radar, path planning | Drive on roads |
| Delivery Robot | Mapping, localization, obstacle avoidance | Deliver packages |
| Mars Rover | SLAM, path planning, obstacle avoidance | Explore Mars |
| Drone | GPS, obstacle avoidance, path planning | Fly and deliver |
A robot vacuum uses SLAM to map your house and navigate around furniture.
A school robot might use obstacle avoidance and wall following to navigate a maze.
A robot toy might use path planning to move around a room.
A robot in a Lagos warehouse might use mapping and localization to move goods.
Real Robot: Delivery Robot
+-------------------+
| Delivery Robot |
| +-----------+ |
| | Sensors | |
| +-----------+ |
| +-----------+ |
| | Motors | |
| +-----------+ |
| +-----------+ |
| | Computer | |
| +-----------+ |
+-------------------+
|
V
Navigates to deliver package
Real robots use autonomous navigation for many tasks. Each robot's navigation system is designed for its specific job.
Safety in autonomous navigation means making sure the robot does not hurt people or damage things while navigating.
Autonomous robots can be dangerous. They move fast. They can bump into people. Safety is very important.
Self-driving cars have many safety features. They slow down near pedestrians.
In a robotics lab, students must follow safety rules.
Robot vacuum cleaners have bump sensors to avoid hitting people.
A delivery robot in Lagos has emergency stop buttons.
Safety in Navigation
+-------------------+
| Emergency Stop |
| Button |
+-------------------+
|
V
+-------------------+
| Robot stops |
| immediately |
+-------------------+
Safety in autonomous navigation means making sure robots do not hurt people or damage things. Always follow safety rules.
The future of autonomous robots is very exciting. Robots will become smarter, faster, and more useful.
Autonomous robots will change the world. They will help farmers, doctors, drivers, and many other people.
Some companies are already testing self-driving taxis.
Students today are learning robotics to prepare for future jobs.
Robot vacuum cleaners are becoming more common in homes.
Nigerian universities are researching autonomous robots for agriculture and healthcare.
Future of Autonomous Robots
Today: Robot vacuum
|
V
Soon: Delivery robots
|
V
Future: Self-driving cars
|
V
Future: Robots in every home
The future of autonomous robots is exciting. They will become smarter and more useful. They will change the world.
| Word | Simple Definition |
|---|---|
| Autonomous Navigation | Moving from one place to another without human control. |
| Obstacle Avoidance | Detecting and avoiding objects. |
| Wall Following | Moving along a wall while keeping a constant distance. |
| Path Planning | Finding the best route from one place to another. |
| Behaviour | A way a robot acts. |
| Behaviour Composition | Combining simple behaviours to make complex behaviours. |
| Mapping | Creating a picture of the environment. |
| Localization | Knowing where you are on the map. |
| SLAM | Simultaneous Localization and Mapping. |
| Reactive Navigation | Reacting immediately to the world. |
| Deliberative Navigation | Planning ahead before acting. |
| Concept | Real-Life Example |
|---|---|
| Autonomous Navigation | A self-driving car takes you to your destination. |
| Obstacle Avoidance | A robot vacuum avoids furniture. |
| Wall Following | A robot vacuum cleans along walls. |
| Path Planning | Your phone's map app plans a route. |
| Behaviour Composition | A robot vacuum combines many behaviours. |
| Mapping | A robot vacuum maps your house. |
| Localization | Your phone's GPS knows where you are. |
| SLAM | A robot vacuum maps and localizes at the same time. |
| Reactive Navigation | Slamming brakes to avoid an accident. |
| Deliberative Navigation | Planning a route to avoid traffic. |
| Concept | Nigerian Example |
|---|---|
| Autonomous Navigation | A robot in a Lagos warehouse moves goods on its own. |
| Obstacle Avoidance | A robot in a market avoids people and stalls. |
| Wall Following | A robot in a hospital corridor follows the wall. |
| Path Planning | A danfo driver plans a route to avoid traffic. |
| Behaviour Composition | A robot in a factory combines moving, picking, and placing. |
| Mapping | A robot maps a new building in Abuja. |
| Localization | A driver knows which bus stop he is at. |
| SLAM | A robot explores a new building and builds a map. |
| Reactive Navigation | A driver swerves to avoid a pothole. |
| Deliberative Navigation | A driver plans a route to avoid traffic. |
| Concept | Everyday Example |
|---|---|
| Autonomous Navigation | A robot vacuum cleans your house. |
| Obstacle Avoidance | You step aside for someone in the market. |
| Wall Following | You walk along a fence. |
| Path Planning | You plan your route to school. |
| Behaviour Composition | You combine walking, talking, and listening. |
| Mapping | You draw a map of your school. |
| Localization | You know where you are in your house. |
| SLAM | You explore a new city and remember the streets. |
| Reactive Navigation | You catch a falling cup. |
| Deliberative Navigation | You plan a meal before cooking. |
| Mistake | Why It Is Wrong | How to Fix It |
|---|---|---|
| Not testing sensors | Robot bumps into obstacles. | Test sensors before navigation. |
| Wrong threshold | Robot reacts too early or too late. | Adjust threshold carefully. |
| No path planning | Robot goes in circles. | Add path planning. |
| No localization | Robot gets lost. | Add localization. |
| Ignoring safety | Someone could get hurt. | Always follow safety rules. |
| Not debugging | Problems continue. | Find and fix problems. |
+-------------------+
| Sensors |
| (see world) |
+-------------------+
|
V
+-------------------+
| Robot Brain |
| (decides) |
+-------------------+
|
V
+-------------------+
| Actuators |
| (move robot) |
+-------------------+
|
V
+-------------------+
| Robot moves |
+-------------------+
|
| (feedback)
V
+-------------------+
| Sensors update |
+-------------------+
( Start )
|
V
+----------------+
| Move forward |
+----------------+
|
V
+----------------+
| Obstacle |
| detected? |
+----------------+
/ \
YES NO
/ \
V V
+---------+ +-----------+
| Turn | | Keep |
| right | | moving |
+---------+ +-----------+
\ /
\ /
V V
( Repeat )
| Type | Speed | Intelligence | Example |
|---|---|---|---|
| Reactive | Fast | Low | Touch sensor stops robot |
| Deliberative | Slow | High | Path planning |
| Hybrid | Medium | High | Self-driving car |
Step 1: Sense environment
|
V
Step 2: Build map
|
V
Step 3: Find position
|
V
Step 4: Plan path
|
V
Step 5: Move
|
V
Step 6: Avoid obstacles
|
V
Step 7: Reach destination
Autonomous navigation means a robot moves on its own from one place to another.
Obstacle avoidance means detecting and avoiding objects. It keeps robots safe.
Wall following means moving along a wall while keeping a constant distance.
Path planning means finding the best route from one place to another.
A behaviour is a way a robot acts. Simple behaviours do one thing. Complex behaviours combine many simple behaviours.
Behaviour composition means combining simple behaviours to make complex behaviours.
Mapping means creating a picture of the environment. Robots use maps to navigate better.
Localization means knowing where you are on the map.
SLAM means building a map and finding your position at the same time.
Reactive navigation reacts immediately. Deliberative navigation plans ahead. Both are useful.
Programming autonomous navigation means writing a program that reads sensors, decides, and controls motors.
Debugging navigation problems means finding and fixing issues that stop the robot from navigating correctly.
Real robots use autonomous navigation for many tasks. Each robot's navigation system is designed for its specific job.
Safety in autonomous navigation means making sure robots do not hurt people or damage things.
The future of autonomous robots is exciting. They will become smarter and more useful.
In this module, you learned about autonomous navigation and behaviour. You learned that autonomous navigation means a robot moves on its own from one place to another.
You learned about obstacle avoidance — detecting and avoiding objects. You learned about wall following — moving along a wall. You learned about path planning — finding the best route.
You learned about behaviours — simple and complex. You learned about behaviour composition — combining simple behaviours to make complex ones. You learned about mapping — creating a picture of the environment. You learned about localization — knowing where you are on the map. You learned about SLAM — doing both at the same time.
You learned about reactive and deliberative navigation. You learned how to program autonomous navigation. You learned how to debug navigation problems. You learned about real robots and their navigation systems. You learned about safety. You learned about the future of autonomous robots.
Most importantly, you learned that autonomous navigation is what makes robots truly useful. Without it, robots need constant human control. With it, robots can work on their own.
In the next module, you will learn about Robot Control Architectures and Integration. You will learn how to combine sensors, actuators, and navigation into a complete robot system. You will learn about I/O integration, user frames, positional offsets, palletizing routines, and PLC logic.
But for now, take a moment to celebrate what you have learned. You have taken another big step in your journey to becoming a robotics expert. Well done!
Match the term on the left with its definition on the right.
| Term | Definition |
|---|---|
| 1. Autonomous Navigation | A. Detecting and avoiding objects |
| 2. Obstacle Avoidance | B. Moving on your own |
| 3. Wall Following | C. Finding the best route |
| 4. Path Planning | D. Moving along a wall |
| 5. Mapping | E. Knowing where you are on the map |
| 6. Localization | F. Creating a picture of the environment |
| 7. SLAM | G. Doing mapping and localization together |
Answers: 1-B, 2-A, 3-D, 4-C, 5-F, 6-E, 7-G
Title: Design an Autonomous Robot
Instructions:
Example:
Task: Navigate a maze Sensors needed: - Ultrasonic sensor (to detect walls) - Touch sensor (to detect collisions) Navigation system: - Wall following - Obstacle avoidance - Path planning Program: 1. Follow right wall 2. IF obstacle ahead, THEN turn left 3. IF dead end, THEN turn around 4. Repeat
Title: Navigation Scavenger Hunt
Instructions:
Example:
| Device | How It Navigates | Purpose |
|---|---|---|
| Robot Vacuum | SLAM, sensors | Clean floors |
| Self-Driving Car | GPS, cameras, radar | Drive |
| Drone | GPS, sensors | Fly |
| Delivery Robot | Mapping, localization | Deliver packages |
| Robot Toy | Sensors | Follow people |
Title: Build a Maze-Solving Robot
Goal: Create a robot that can solve a simple maze using wall following and obstacle avoidance.
Steps:
Deliverables:
Title: Build an Autonomous Delivery Robot
Instructions:
Grading Criteria:
| Criteria | Points |
|---|---|
| Robot navigates correctly | 30 |
| Avoids obstacles | 20 |
| Uses mapping and localization | 20 |
| Program uses if/else and loops | 15 |
| Report is clear | 15 |
| Total | 100 |
In Module Five, you will learn about Robot Control Architectures and Integration. You will learn how to combine sensors, actuators, and navigation into a complete robot system.
You will learn about:
To prepare for Module Five:
Get ready for an exciting journey into the world of robot integration!
Congratulations! You have completed Module Four of Fundamentals of Robotics Level Two. You have learned about autonomous navigation and behaviour.
You learned that autonomous navigation means a robot moves on its own from one place to another. You learned about obstacle avoidance, wall following, and path planning. You learned about behaviours — simple and complex. You learned about behaviour composition. You learned about mapping, localization, and SLAM. You learned about reactive and deliberative navigation.
You learned how to program autonomous navigation. You learned how to debug navigation problems. You learned about real robots and their navigation systems. You learned about safety. You learned about the future of autonomous robots.
You also learned many examples from Nigeria, from your home, from school, and from everyday life. You learned through stories, illustrations, and activities.
Now you are ready for Module Five: Robot Control Architectures and Integration. In Module Five, you will learn how to combine sensors, actuators, and navigation into a complete robot system. You will learn about I/O integration, user frames, positional offsets, palletizing routines, and PLC logic.
But before you move on, take a moment to review this module. Make sure you understand the key ideas. Practise writing navigation programs. Draw diagrams. Test your robots. The more you practise, the better you will become.
You are doing great. Keep learning. Keep exploring. Keep building. The world of robotics is waiting for you!
End of Module Four
Next: Module Five — Robot Control Architectures and Integration
Welcome to Module Five! In Module One, you learned how to write programs. In Module Two, you learned about sensors. In Module Three, you learned about motors and motion. In Module Four, you learned about autonomous navigation. Now you will learn how to put everything together.
Think about your body. Your brain, your senses, and your muscles all work together. Your eyes see. Your brain decides. Your muscles move. If any part stops working, your whole body suffers.
Robots are the same. A robot has sensors, motors, and a brain. But they must work together as one system. That is called integration.
In this module, you will learn how to integrate sensors, actuators, and programs into one complete robot. You will learn about I/O integration, user frames, positional offsets, palletizing routines, and PLC logic. These are the tools that make real robots work in factories, warehouses, and hospitals.
This is where robotics becomes really professional. Your robot will stop being a collection of parts. It will become a complete, working system.
Let us begin!
By the end of this module, you will be able to:
Once upon a time, in the city of Port Harcourt, Nigeria, there lived a boy named Chidi. Chidi loved robots. He had built many small robots using kits and Arduino boards. He could make them move, sense, and navigate.
One day, Chidi's uncle invited him to visit a bottle factory. The factory made plastic bottles for water and drinks. Chidi was excited. He had never seen a real industrial robot before.
When Chidi arrived at the factory, he was amazed. There were robots everywhere. One robot picked up bottles and placed them on a conveyor belt. Another robot filled the bottles with water. Another robot capped the bottles. Another robot packed the bottles into boxes.
Chidi watched in wonder. "Uncle, how do all these robots work together?" he asked.
His uncle smiled. "Chidi, that is called integration. Each robot has its own job. But they must work together as one system. If one robot stops, the whole line stops."
Chidi noticed something. The robot that picked up bottles used sensors to know when a bottle was in position. It used motors to move its arm. It used a program to decide when to pick and when to place. Everything worked together.
"Uncle, how does the robot know where to place the bottle?" Chidi asked.
"It uses a user frame," his uncle explained. "A user frame is a coordinate system that tells the robot where things are. The robot uses the frame to calculate its movements."
"And how does it stack bottles in the box?" Chidi asked.
"It uses a palletizing routine," his uncle said. "That is a program that tells the robot how to stack objects in rows and layers."
Chidi was fascinated. He learned about I/O integration — how sensors and motors connect to the robot's brain. He learned about positional offsets — how the robot adjusts its position for different objects. He learned about PLC logic — how the factory controls all the robots together.
When Chidi went home, he decided to build his own integrated robot system. He took his small robot and added more sensors, more motors, and more programs. He made it pick up objects and place them in different locations. He made it sort objects by colour. He made it stack objects in rows.
Chidi's robot was not as big as the factory robots. But it worked as one complete system. It integrated sensors, motors, and programs. It was a real robot system.
That is what you will learn in this module. You will learn how to integrate sensors, actuators, and programs into one complete robot system.
Let us begin!
Integration means combining different parts into one working system. In robotics, it means making sensors, actuators, and programs work together.
A robot with separate parts is useless. If the sensor does not talk to the brain, the robot cannot react. If the brain does not talk to the motor, the robot cannot move. Integration makes the robot work as one.
Think of a football team. The goalkeeper, defenders, midfielders, and strikers each have a job. But they must work together to win. Integration is like teamwork for robot parts.
A car has an engine, brakes, steering, and lights. They all work together. If the brakes fail, the car cannot stop safely. That is integration.
A school has teachers, students, and administrators. They work together to educate students. That is integration.
A kitchen has a stove, fridge, sink, and utensils. They work together to cook meals. That is integration.
A market has traders, buyers, and transporters. They work together to sell goods. That is integration.
Integration in a Robot
+-------------+ +-------------+
| Sensor | | Motor |
+-------------+ +-------------+
\ /
\ /
V V
+-------------------+
| Robot Brain |
| (integrates) |
+-------------------+
|
V
+-------------------+
| Robot works |
| as one system |
+-------------------+
Integration means combining different parts into one working system. In robotics, it makes sensors, actuators, and programs work together.
A control architecture is the way a robot's brain is organised. It decides how the robot processes information and makes decisions.
Without a control architecture, the robot's brain would be a mess. It would not know what to do first. A good control architecture makes the robot efficient and reliable.
Think of a school. The principal is at the top. Teachers are in the middle. Students are at the bottom. Information flows from top to bottom and bottom to top. That is a control architecture.
| Type | How It Works | Example |
|---|---|---|
| Reactive | Responds immediately to sensors | Touch sensor stops robot |
| Deliberative | Plans before acting | Path planning |
| Hybrid | Combines both reactive and deliberative | Self-driving car |
A car has a hybrid control architecture. It reacts immediately to brakes (reactive) and plans routes (deliberative).
A school has a hybrid architecture. Teachers react to student questions (reactive) and plan lessons (deliberative).
A parent reacts to a child's cry (reactive) and plans meals for the week (deliberative).
A trader reacts to customers (reactive) and plans what goods to buy (deliberative).
Control Architecture
+-------------------+
| Deliberative |
| (plans) |
+-------------------+
|
V
+-------------------+
| Reactive |
| (reacts) |
+-------------------+
|
V
+-------------------+
| Actuators |
+-------------------+
A control architecture is how a robot's brain is organised. It can be reactive, deliberative, or hybrid.
I/O stands for Input/Output. Inputs are signals that come into the robot (from sensors). Outputs are signals that go out of the robot (to motors, lights, etc.).
Without I/O, the robot cannot communicate with the world. Inputs tell the robot what is happening. Outputs let the robot act.
Think of your phone. The touchscreen is an input. The speaker is an output. The camera is an input. The screen is an output. Your phone uses I/O to interact with you.
| Type | What It Does | Example |
|---|---|---|
| Digital Input | Reads on/off signals | Button press |
| Analog Input | Reads varying signals | Light sensor |
| Digital Output | Sends on/off signals | Turn on LED |
| Analog Output | Sends varying signals | Motor speed |
A TV remote sends digital output (infrared signals). The TV receives digital input.
A school bell is a digital output. Students hearing it is a digital input.
A light switch is a digital input. The light turning on is a digital output.
A generator's start button is a digital input. The generator starting is a digital output.
I/O Integration
Inputs: Outputs:
+-------------+ +-------------+
| Sensor | | Motor |
+-------------+ +-------------+
| ^
| |
V |
+-------------------+ |
| Robot Brain |------------+
+-------------------+
I/O stands for Input/Output. Inputs come from sensors. Outputs go to motors and other devices. I/O integration connects the robot to the world.
Digital signals have only two values: on or off (1 or 0). Analog signals can have many values within a range.
Different sensors and devices use different signals. Knowing the difference helps you connect them correctly.
Think of a light switch. It is either on or off. That is digital. Now think of a dimmer switch. It can be bright, medium, or dim. That is analog.
| Characteristic | Digital | Analog |
|---|---|---|
| Values | On or Off (1 or 0) | Many values (0 to 1023) |
| Example | Button press | Light sensor |
| Precision | Exact | Approximate |
| Use | Switches, buttons | Temperature, light |
A digital clock shows exact time (12:00). An analog clock shows approximate time (a little past 12).
A digital scoreboard shows exact scores. An analog thermometer shows approximate temperature.
A digital TV shows channels. An analog radio has a dial.
A digital meter shows exact electricity units. An analog meter has a dial.
Digital vs Analog Digital: +---+ | 1 | +---+ +---+ | 0 | +---+ Analog: +---+---+---+---+---+ | 0 | 1 | 2 | 3 | 4 | +---+---+---+---+---+
Digital signals are on or off. Analog signals have many values. Different devices use different signals.
A user frame is a coordinate system that tells the robot where things are. It is like a map that the robot uses to calculate movements.
Without a user frame, the robot does not know where to go. It might move to the wrong place. A user frame gives the robot a reference point.
Think of your classroom. The teacher's desk is at the front. The door is at the back. The windows are on the left. That is a user frame. It tells you where things are.
A GPS uses a user frame (latitude and longitude) to tell you where you are.
A school map uses a user frame to show where classrooms are.
Your house has a user frame: the kitchen is on the left, the bedroom is on the right.
A market has a user frame: the pepper sellers are on the left, the fish sellers are on the right.
User Frame Y ^ | | (0, 10) | * | | | | | * (10, 0) | +-----------------> X (0,0) The user frame defines coordinates.
A user frame is a coordinate system that tells the robot where things are. It gives the robot a reference point for movement.
A positional offset is a small change in position. The robot adjusts its position based on the offset.
Objects are not always in the same place. A bottle might be slightly to the left. A box might be slightly higher. Positional offsets let the robot adjust.
Think of parking a car. You do not park in the exact same spot every time. You adjust based on the space. That is a positional offset.
A robot arm picks up a bottle. If the bottle is slightly to the left, the robot adjusts its position. That is a positional offset.
When you write on a line, you adjust your pencil position. That is a positional offset.
When you place a plate on a table, you adjust its position. That is a positional offset.
When a trader arranges goods on a table, she adjusts their position. That is a positional offset.
Positional Offset
Original position: (10, 5)
Offset: (+2, -1)
New position: (12, 4)
+-------------------+
| Original |
| (10, 5) |
+-------------------+
|
| (offset)
V
+-------------------+
| New |
| (12, 4) |
+-------------------+
A positional offset is a small change in position. It lets the robot adjust to different situations.
A register is a small storage space in the robot's brain. It holds numbers that the robot uses for calculations.
Registers let the robot remember things. It can remember how many items it has picked. It can remember the position of the last object. Registers are essential for complex tasks.
Think of a calculator. When you type a number, it is stored in the calculator's memory. That is a register. The calculator uses it for calculations.
A cash register in a shop stores the total price. That is a register.
A teacher's mark book stores student scores. That is a register.
A shopping list stores items to buy. That is a register.
A trader's record book stores sales for the day. That is a register.
Register
+-------------------+
| Register R1 |
| Value: 5 |
+-------------------+
|
| (robot adds 1)
V
+-------------------+
| Register R1 |
| Value: 6 |
+-------------------+
A register is a small storage space in the robot's brain. It holds numbers for calculations. Registers help robots remember things.
A palletizing routine is a program that tells a robot how to stack objects in rows and layers.
In factories, robots stack boxes on pallets. They must stack them neatly and efficiently. A palletizing routine tells the robot how to do this.
Think of stacking chairs in a classroom. You put them in rows. You stack them layer by layer. That is palletizing.
A robot in a warehouse stacks boxes on a pallet. It places them in rows and layers.
When you arrange books on a shelf, you stack them in rows. That is palletizing.
When you arrange plates in a cupboard, you stack them. That is palletizing.
When a trader arranges tomatoes in a basket, she stacks them in layers. That is palletizing.
Palletizing Routine Layer 1: +---+---+---+ | 1 | 2 | 3 | +---+---+---+ | 4 | 5 | 6 | +---+---+---+ Layer 2: +---+---+---+ | 7 | 8 | 9 | +---+---+---+ |10 |11 |12 | +---+---+---+ Stacked on a pallet.
A palletizing routine tells a robot how to stack objects in rows and layers. It is used in factories and warehouses.
PLC stands for Programmable Logic Controller. It is a computer used to control machines in factories. PLC logic is the program that runs on a PLC.
In a factory, many robots work together. A PLC coordinates them. It tells each robot when to start, stop, and move. Without a PLC, the factory would be chaos.
Think of a traffic light. It tells cars when to stop and when to go. A PLC is like a traffic light for robots. It tells each robot what to do.
A factory uses a PLC to control a conveyor belt, a robot arm, and a packaging machine.
A school timetable is like a PLC. It tells students and teachers what to do at each time.
A family schedule is like a PLC. It tells family members what to do at each time.
A bus terminal uses a PLC-like system to tell buses when to leave and when to arrive.
PLC Logic
+-------------------+
| PLC |
| (controller) |
+-------------------+
| | |
| | |
V V V
+-----+ +-----+ +-----+
|Robot| |Robot| |Robot|
| 1 | | 2 | | 3 |
+-----+ +-----+ +-----+
PLC tells each robot what to do.
A PLC is a computer that controls machines in a factory. PLC logic is the program that runs on a PLC. It coordinates multiple robots.
Ladder logic is a way to write PLC programs. It looks like a ladder with rungs.
Ladder logic is easy to read. It shows how inputs and outputs are connected. It is used in many factories around the world.
Think of a ladder. Each rung is a step. In ladder logic, each rung is a rule. If the rule is true, something happens.
Ladder logic controls a conveyor belt. If the sensor detects a box, the belt moves.
A school bell system uses ladder logic. If it is 8:00 AM, the bell rings.
A washing machine uses ladder logic. If the door is closed, the machine starts.
A generator uses ladder logic. If the fuel is low, the warning light turns on.
Ladder Logic Rung 1: |----[ Sensor ]----------------( Motor )----| Rung 2: |----[ Button ]----------------( Light )----| Rung 3: |----[ Switch ]----[ Sensor ]--( Alarm )----|
Ladder logic is a way to write PLC programs. It looks like a ladder with rungs. Each rung is a rule.
Integrating sensors and actuators means connecting them so they work together. The sensor detects something. The actuator responds.
Sensors and actuators must work together. If the sensor detects an obstacle, the actuator must stop the robot. Integration makes this happen.
Think of your body. Your eyes see a ball coming. Your muscles move your hand to catch it. Sensors and actuators working together.
A robot vacuum uses sensors to detect dirt and motors to move toward it.
A line-following robot uses a light sensor to see the line and motors to stay on it.
A washing machine uses a water level sensor and a motor to fill and wash.
A robot that sorts tomatoes uses a colour sensor and a motor to push them into baskets.
Sensor + Actuator Integration
+-------------+
| Sensor |
| (detects) |
+-------------+
|
V
+-------------+
| Robot |
| Brain |
| (decides) |
+-------------+
|
V
+-------------+
| Actuator |
| (moves) |
+-------------+
|
V
+-------------+
| Robot |
| acts |
+-------------+
Integrating sensors and actuators means connecting them so they work together. The sensor detects. The actuator responds.
Debugging integration problems means finding and fixing issues that stop the robot's parts from working together.
Integration is complex. Many things can go wrong. A wire might be loose. A program might have a bug. Debugging helps you find and fix these problems.
| Problem | Cause | Solution |
|---|---|---|
| Sensor not working | Loose wire or wrong port | Check connections |
| Motor not moving | No power or wrong signal | Check power and signals |
| Robot moves wrong | Program logic error | Debug the program |
| Robot stops randomly | Loose connection or low battery | Check connections and power |
| Sensor gives wrong reading | Needs calibration | Calibrate the sensor |
If your TV remote does not work, you check the batteries. That is debugging.
If your robot does not move, you check the motor wires.
If your fan does not spin, you check the plug.
If your generator does not start, you check the fuel and battery.
Debugging Integration
[ Robot not working ]
|
V
[ Check sensors ]
|
V
[ Check actuators ]
|
V
[ Check program ]
|
V
[ Fix problem ]
|
V
[ Test again ]
Debugging integration problems means finding and fixing issues. Common problems include loose wires, wrong ports, and program bugs.
Real robots use integration to do complex tasks. They combine sensors, actuators, and programs.
| Robot | Integration | Purpose |
|---|---|---|
| Robot Vacuum | Sensors + motors + SLAM | Clean floors |
| Self-Driving Car | Cameras + radar + motors + GPS | Drive on roads |
| Factory Robot | Sensors + motors + PLC | Assemble products |
| Surgical Robot | Cameras + force sensors + motors | Perform surgery |
| Drone | Gyroscope + GPS + motors | Fly and deliver |
A robot vacuum integrates sensors, motors, and SLAM to clean your house.
A school robot integrates sensors, motors, and a program to navigate a maze.
A robot toy integrates sensors and motors to follow you around.
A robot in a Lagos warehouse integrates sensors, motors, and PLC to move goods.
Real Robot: Factory Robot
+-------------------+
| Sensors |
| (detect) |
+-------------------+
|
V
+-------------------+
| PLC |
| (controls) |
+-------------------+
|
V
+-------------------+
| Motors |
| (move) |
+-------------------+
|
V
+-------------------+
| Robot works |
+-------------------+
Real robots use integration to do complex tasks. They combine sensors, actuators, and programs.
Safety in integrated systems means making sure the robot does not hurt people or damage things.
Integrated systems are powerful. They can move fast and do dangerous things. Safety is very important.
Factory robots have safety cages to keep people away.
In a robotics lab, students must follow safety rules.
Robot vacuum cleaners have bump sensors to avoid hitting people.
A robot in a factory in Lagos has emergency stop buttons.
Safety in Integrated Systems
+-------------------+
| Emergency Stop |
| Button |
+-------------------+
|
V
+-------------------+
| Robot stops |
| immediately |
+-------------------+
Safety in integrated systems means making sure robots do not hurt people or damage things. Always follow safety rules.
The future of robot integration is very exciting. Robots will become more integrated, more capable, and more useful.
Integrated robots will change the world. They will work in factories, hospitals, farms, and homes. They will help people in many ways.
Some factories are already fully automated. Robots work together with no humans.
Students today are learning robotics to prepare for future jobs.
Robot vacuum cleaners are becoming more common in homes.
Nigerian universities are researching integrated robots for agriculture and healthcare.
Future of Robot Integration
Today: Single robot
|
V
Soon: Multiple robots working together
|
V
Future: Fully automated factories
|
V
Future: Robots in every home
The future of robot integration is exciting. Robots will become more integrated and more useful. They will change the world.
| Word | Simple Definition |
|---|---|
| Integration | Combining different parts into one working system. |
| Control Architecture | The way a robot's brain is organised. |
| I/O | Input/Output — signals coming in and going out. |
| Digital Signal | A signal that is either on or off. |
| Analog Signal | A signal that can have many values. |
| User Frame | A coordinate system that tells the robot where things are. |
| Positional Offset | A small change in position. |
| Register | A small storage space in the robot's brain. |
| Palletizing Routine | A program that tells a robot how to stack objects. |
| PLC | Programmable Logic Controller — a computer that controls machines. |
| Ladder Logic | A way to write PLC programs that looks like a ladder. |
| Concept | Real-Life Example |
|---|---|
| Integration | A car's engine, brakes, and steering work together. |
| Control Architecture | A self-driving car uses hybrid architecture. |
| I/O | A TV remote sends output. The TV receives input. |
| Digital vs Analog | A light switch is digital. A dimmer is analog. |
| User Frame | A GPS uses latitude and longitude. |
| Positional Offset | A robot arm adjusts to pick up a bottle. |
| Register | A cash register stores the total price. |
| Palletizing Routine | A robot stacks boxes on a pallet. |
| PLC Logic | A factory controls machines with a PLC. |
| Ladder Logic | A conveyor belt uses ladder logic. |
| Concept | Nigerian Example |
|---|---|
| Integration | A market has traders, buyers, and transporters working together. |
| Control Architecture | A trader reacts to customers and plans purchases. |
| I/O | A generator's start button is input. The generator starting is output. |
| Digital vs Analog | A digital meter shows exact units. An analog meter has a dial. |
| User Frame | A market has pepper sellers on the left, fish sellers on the right. |
| Positional Offset | A trader adjusts goods on a table. |
| Register | A trader's record book stores sales. |
| Palletizing Routine | A trader stacks tomatoes in a basket. |
| PLC Logic | A bus terminal tells buses when to leave. |
| Ladder Logic | A generator warns when fuel is low. |
| Concept | Everyday Example |
|---|---|
| Integration | Your phone's camera, screen, and speaker work together. |
| Control Architecture | You react to a loud noise and plan to investigate. |
| I/O | Your keyboard is input. Your monitor is output. |
| Digital vs Analog | A digital clock is exact. An analog clock is approximate. |
| User Frame | A map of your school shows where classrooms are. |
| Positional Offset | You adjust your chair position at a table. |
| Register | Your shopping list stores items to buy. |
| Palletizing Routine | You stack plates in a cupboard. |
| PLC Logic | Your family schedule tells everyone what to do. |
| Ladder Logic | A washing machine starts if the door is closed. |
| Mistake | Why It Is Wrong | How to Fix It |
|---|---|---|
| Not testing connections | Parts do not work together. | Test each connection. |
| Wrong I/O port | Signals go to the wrong place. | Check the port numbers. |
| Ignoring user frames | Robot moves to the wrong position. | Set up user frames correctly. |
| Not using registers | Robot cannot remember things. | Use registers for storage. |
| Wrong palletizing routine | Objects stack incorrectly. | Check the routine. |
| Ignoring safety | Someone could get hurt. | Always follow safety rules. |
+-------------------+
| Sensors |
| (input) |
+-------------------+
|
V
+-------------------+
| Robot Brain |
| (process) |
+-------------------+
|
V
+-------------------+
| Actuators |
| (output) |
+-------------------+
|
V
+-------------------+
| Robot works |
+-------------------+
|
| (feedback)
V
+-------------------+
| Sensors update |
+-------------------+
( Start )
|
V
+----------------+
| Read sensor |
+----------------+
|
V
+----------------+
| Process data |
+----------------+
|
V
+----------------+
| Send output |
+----------------+
|
V
+----------------+
| Actuator moves |
+----------------+
|
V
( Repeat )
| Type | Speed | Intelligence | Example |
|---|---|---|---|
| Reactive | Fast | Low | Touch sensor stops robot |
| Deliberative | Slow | High | Path planning |
| Hybrid | Medium | High | Self-driving car |
Step 1: Connect sensors
|
V
Step 2: Connect actuators
|
V
Step 3: Write program
|
V
Step 4: Set user frames
|
V
Step 5: Test
|
V
Step 6: Debug
|
V
Step 7: Done!
Integration means combining different parts into one working system. In robotics, it makes sensors, actuators, and programs work together.
A control architecture is how a robot's brain is organised. It can be reactive, deliberative, or hybrid.
I/O stands for Input/Output. Inputs come from sensors. Outputs go to motors and other devices.
Digital signals are on or off. Analog signals have many values. Different devices use different signals.
A user frame is a coordinate system that tells the robot where things are. It gives the robot a reference point.
A positional offset is a small change in position. It lets the robot adjust to different situations.
A register is a small storage space in the robot's brain. It holds numbers for calculations.
A palletizing routine tells a robot how to stack objects in rows and layers.
A PLC is a computer that controls machines in a factory. PLC logic coordinates multiple robots.
Ladder logic is a way to write PLC programs. It looks like a ladder with rungs. Each rung is a rule.
Integrating sensors and actuators means connecting them so they work together. The sensor detects. The actuator responds.
Debugging integration problems means finding and fixing issues. Common problems include loose wires, wrong ports, and program bugs.
Real robots use integration to do complex tasks. They combine sensors, actuators, and programs.
Safety in integrated systems means making sure robots do not hurt people or damage things.
The future of robot integration is exciting. Robots will become more integrated and more useful.
In this module, you learned about robot control architectures and integration. You learned that integration means combining different parts into one working system.
You learned about control architectures — reactive, deliberative, and hybrid. You learned about I/O integration — how inputs and outputs connect the robot to the world. You learned about digital and analog signals.
You learned about user frames — coordinate systems that tell the robot where things are. You learned about positional offsets — small changes in position. You learned about registers — storage spaces in the robot's brain. You learned about palletizing routines — programs that stack objects.
You learned about PLC logic — how factories control multiple robots. You learned about ladder logic — a way to write PLC programs. You learned how to integrate sensors and actuators. You learned how to debug integration problems. You learned about real robots and their integration. You learned about safety. You learned about the future of robot integration.
Most importantly, you learned that integration is what makes robots useful. Without integration, robots are just separate parts. With integration, robots become complete systems that can do complex tasks.
In the next module, you will learn about Mechanical Design and CAD. You will learn how to design robot parts using computers. You will learn about 3D modelling, assemblies, and engineering measurement.
But for now, take a moment to celebrate what you have learned. You have taken another big step in your journey to becoming a robotics expert. Well done!
Match the term on the left with its definition on the right.
| Term | Definition |
|---|---|
| 1. Integration | A. Input/Output signals |
| 2. Control Architecture | B. Combining parts into one system |
| 3. I/O | C. How a robot's brain is organised |
| 4. User Frame | D. A small change in position |
| 5. Positional Offset | E. A coordinate system |
| 6. Register | F. A program that stacks objects |
| 7. Palletizing Routine | G. A storage space in the robot's brain |
| 8. PLC | H. A computer that controls machines |
Answers: 1-B, 2-C, 3-A, 4-E, 5-D, 6-G, 7-F, 8-H
Title: Design an Integrated Robot System
Instructions:
Example:
Task: Sort objects by colour Sensors needed: - Colour sensor (to detect colour) Actuators needed: - Motor (to push objects) - Servo (to move the sorter) Control architecture: Hybrid Program: 1. Read colour sensor 2. IF red, THEN push to basket A 3. IF green, THEN push to basket B 4. Repeat
Title: Integration Scavenger Hunt
Instructions:
Example:
| Device | Parts Integrated | Purpose |
|---|---|---|
| Washing Machine | Motor, sensors, controller | Wash clothes |
| Car | Engine, brakes, steering, sensors | Transport people |
| Phone | Camera, screen, speaker, processor | Communicate |
| Generator | Motor, fuel sensor, controller | Produce electricity |
| Robot Vacuum | Sensors, motors, SLAM | Clean floors |
Title: Build an Integrated Sorting Robot
Goal: Create a robot that sorts objects by colour using sensors and actuators.
Steps:
Deliverables:
Title: Build an Integrated Palletizing Robot
Instructions:
Grading Criteria:
| Criteria | Points |
|---|---|
| Robot stacks objects correctly | 30 |
| Uses user frame | 20 |
| Uses registers | 20 |
| Program uses if/else and loops | 15 |
| Report is clear | 15 |
| Total | 100 |
In Module Six, you will learn about Mechanical Design and CAD. You will learn how to design robot parts using computers.
You will learn about:
To prepare for Module Six:
Get ready for an exciting journey into the world of robot design!
Congratulations! You have completed Module Five of Fundamentals of Robotics Level Two. You have learned about robot control architectures and integration.
You learned that integration means combining different parts into one working system. You learned about control architectures — reactive, deliberative, and hybrid. You learned about I/O integration — how inputs and outputs connect the robot to the world. You learned about digital and analog signals.
You learned about user frames — coordinate systems that tell the robot where things are. You learned about positional offsets — small changes in position. You learned about registers — storage spaces in the robot's brain. You learned about palletizing routines — programs that stack objects.
You learned about PLC logic — how factories control multiple robots. You learned about ladder logic — a way to write PLC programs. You learned how to integrate sensors and actuators. You learned how to debug integration problems. You learned about real robots and their integration. You learned about safety. You learned about the future of robot integration.
You also learned many examples from Nigeria, from your home, from school, and from everyday life. You learned through stories, illustrations, and activities.
Now you are ready for Module Six: Mechanical Design and CAD. In Module Six, you will learn how to design robot parts using computers. You will learn about CAD modelling, assemblies, chassis construction, pneumatics, and engineering measurement.
But before you move on, take a moment to review this module. Make sure you understand the key ideas. Practise writing integration programs. Draw diagrams. Test your systems. The more you practise, the better you will become.
You are doing great. Keep learning. Keep exploring. Keep building. The world of robotics is waiting for you!
End of Module Five
Next: Module Six — Mechanical Design and CAD
Welcome to Module Six! In Module One, you learned how to write programs. In Module Two, you learned about sensors. In Module Three, you learned about motors and motion. In Module Four, you learned about autonomous navigation. In Module Five, you learned about integration. Now you will learn how to design the body of a robot.
Think about building a house. Before you start laying bricks, you need a plan. You need to know how many rooms you want. You need to know where the doors and windows will go. You need to know how big the house will be. That plan is called a design.
Robots are the same. Before you build a robot, you need to design it. You need to know how big it will be. You need to know where the motors will go. You need to know how strong the frame must be. You need to know how the parts will fit together.
In this module, you will learn how to design robot parts using computers. This is called CAD — Computer-Aided Design. You will learn about 3D modelling, assemblies, chassis construction, and engineering measurement. You will also learn about pneumatics — using air to move things.
This is where robotics becomes really creative. You will stop just using robots that others have designed. You will start designing your own.
Let us begin!
By the end of this module, you will be able to:
Once upon a time, in the city of Kano, Nigeria, there lived a girl named Amina. Amina loved robotics. She had built a small robot named Zaki using a kit her school provided.
Zaki had two wheels, a motor, and a small computer brain. He had sensors and could navigate around obstacles. But there was a problem. Zaki wobbled when he moved. His body shook. His wheels slipped. He could not move in a straight line.
Amina was frustrated. "Zaki, why can't you move smoothly?" she asked.
Zaki did not answer. He just wobbled.
Amina decided to investigate. She looked at Zaki's body. It was made of cardboard and tape. The motors were attached with glue. The wheels were not straight. The body was too light.
"Ah!" Amina said. "The body is the problem. It is not strong enough. It is not balanced. I need to design a better body."
Amina went to her teacher. "Madam, my robot wobbles because the body is not good. What can I do?"
Her teacher smiled. "Amina, you need to learn about mechanical design. You need to design a strong, balanced body for your robot. You need to use CAD."
"What is CAD?" Amina asked.
"CAD stands for Computer-Aided Design," her teacher explained. "It is a way to design things on a computer before you build them. You can see how the robot will look. You can test if the parts fit together. You can make changes before you build."
Amina was excited. She learned to use a simple CAD program. She designed a new body for Zaki. She made it from strong plastic. She made it balanced. She made sure the motors were straight.
She printed the design using a 3D printer. She assembled the new body. She attached the motors and wheels. She uploaded her program and pressed START.
Zaki began to move. He moved forward. He moved straight. He did not wobble. He did not shake. He moved smoothly and accurately.
Amina jumped for joy. "Zaki, you are perfect!" she shouted.
Zaki moved smoothly across the floor. He was no longer a wobbly robot. He was a well-designed robot.
That is what you will learn in this module. You will learn how to design your robot's body. You will learn about CAD, 3D modelling, assemblies, chassis construction, and engineering measurement.
Let us begin!
Mechanical design is the process of planning and creating the physical parts of a robot. It includes the shape, size, and materials of the robot's body.
Without good mechanical design, a robot will not work well. It might wobble. It might break. It might not fit together. Good design makes the robot strong, stable, and reliable.
Think of building a house. You do not just start laying bricks. You draw a plan first. You decide how many rooms. You decide where the doors will go. That is design.
A car is designed before it is built. Engineers draw the shape, decide the materials, and test the design.
A school desk is designed before it is made. The designer decides the height, width, and materials.
A chair is designed before it is made. The designer decides the shape and materials.
A keke napep (tricycle) is designed before it is built. The designer decides the size and materials.
Mechanical Design Process
[ Idea ]
|
V
[ Draw plan ]
|
V
[ Choose materials ]
|
V
[ Build prototype ]
|
V
[ Test and improve ]
|
V
[ Final design ]
Mechanical design is planning the physical parts of a robot. It includes shape, size, and materials. Good design makes robots strong and reliable.
CAD stands for Computer-Aided Design. It is software used to create designs on a computer.
CAD helps you design before you build. You can see how the robot will look. You can test if parts fit together. You can make changes easily. CAD saves time and money.
Think of drawing a picture on paper. But instead of paper, you use a computer. And instead of a flat picture, you can see it in 3D. That is CAD.
Engineers use CAD to design cars, aeroplanes, and buildings.
Students use CAD to design projects in science and technology class.
Architects use CAD to design houses before they are built.
Nigerian engineers use CAD to design roads, bridges, and buildings.
CAD on a Computer
+-------------------+
| CAD Software |
| +-----------+ |
| | 3D Model | |
| +-----------+ |
+-------------------+
|
V
+-------------------+
| Design saved |
+-------------------+
|
V
+-------------------+
| Build or print |
+-------------------+
CAD stands for Computer-Aided Design. It is software used to create designs on a computer. It helps you design before you build.
2D design is flat. It has length and width. 3D design has length, width, and height. It is like a real object.
2D design is good for simple drawings. 3D design is better for robots because you can see how they will look in real life.
Think of a drawing of a house on paper. That is 2D. Now think of a model house you can hold in your hand. That is 3D.
| Characteristic | 2D Design | 3D Design |
|---|---|---|
| Dimensions | Length and width | Length, width, and height |
| Example | Drawing on paper | Model of a robot |
| Use | Simple plans | Complex objects |
| View | Flat | Can rotate and see all sides |
A map is 2D. A globe is 3D.
A drawing of a cell is 2D. A model of a cell is 3D.
A photo is 2D. A sculpture is 3D.
A drawing of a house is 2D. A model of a house is 3D.
2D vs 3D 2D: +--------+ | | | | +--------+ Flat, like a drawing 3D: +--------+ |\ |\ | +------+ + | | | | +--------+ | \| \| +--------+ Has depth, like a box
2D design is flat. 3D design has depth. 3D design is better for robots because you can see how they will look in real life.
CAD tools are software programs used to create designs. Different tools are good for different jobs.
Choosing the right CAD tool makes design easier. Some tools are simple. Some are advanced. You need to choose the one that fits your skill level and project.
| Tool | Best For | Difficulty |
|---|---|---|
| Tinkercad | Beginners, simple 3D designs | Easy |
| Fusion 360 | Robot parts, assemblies | Medium |
| SolidWorks | Professional engineering | Hard |
| AutoCAD | 2D drawings, architecture | Medium |
| Blender | 3D animation, art | Medium |
Engineers at car companies use SolidWorks to design car parts.
Students use Tinkercad to design simple 3D objects.
Hobbyists use Fusion 360 to design parts for 3D printing.
Nigerian engineers use AutoCAD to design buildings.
CAD Tools +-------------+ +-------------+ +-------------+ | Tinkercad | | Fusion 360 | | SolidWorks | | (Beginner) | | (Medium) | | (Advanced) | +-------------+ +-------------+ +-------------+
CAD tools are software programs used to create designs. Different tools are good for different jobs. Choose the one that fits your skill level.
An assembly in CAD is a design that combines many parts into one object. It shows how the parts fit together.
Robots are made of many parts. You need to know how they fit together. An assembly shows you this. It helps you check for mistakes before you build.
Think of a jigsaw puzzle. Each piece is a part. When you put them together, you get the full picture. That is an assembly.
A car is an assembly of thousands of parts. Engineers use CAD to design how they fit together.
A school project might be an assembly of a simple machine.
A bicycle is an assembly of wheels, frame, and pedals.
A generator is an assembly of engine, fuel tank, and alternator.
Assembly in CAD Part 1: Wheel +-------+ | | +-------+ Part 2: Motor +-------+ | | +-------+ Part 3: Frame +-------+ | | +-------+ Assembly: +-------+ | Wheel | +-------+ | Motor | +-------+ | Frame | +-------+
An assembly in CAD combines many parts into one object. It shows how parts fit together. It helps you check for mistakes before building.
A chassis is the frame or body of a robot. It holds all the parts together.
The chassis is the foundation of the robot. If the chassis is weak, the robot will break. If the chassis is heavy, the robot will be slow. A good chassis is strong, light, and balanced.
Think of your body. Your skeleton is your chassis. It holds your muscles, organs, and skin together. A robot's chassis does the same thing.
A car's chassis holds the engine, wheels, and body together.
A school robot's chassis might be made of plastic or metal.
A toy car's chassis holds the motor and wheels.
A keke napep's chassis holds the engine, wheels, and passenger cabin.
Robot Chassis +-------------------+ | Chassis | | +-----------+ | | | Motor | | | +-----------+ | | +-----------+ | | | Battery | | | +-----------+ | | +-----------+ | | | Brain | | | +-----------+ | +-------------------+
A chassis is the frame or body of a robot. It holds all the parts together. A good chassis is strong, light, and balanced.
The center of gravity is the point where the robot's weight is balanced. If the center of gravity is too high or too far to one side, the robot will tip over.
Balance is important for robots. If a robot tips over, it cannot move. If it wobbles, it cannot go straight. Keeping the center of gravity low and centered makes the robot stable.
Think of a see-saw. If both sides are equal, it balances. If one side is heavier, it tips. The center of gravity is the balance point.
A racing car has a low center of gravity. It does not tip over when turning.
A tall bookshelf has a high center of gravity. It can tip over easily.
A table with heavy legs at the bottom is stable. A table with heavy top is unstable.
A loaded truck has a high center of gravity. It must drive carefully to avoid tipping.
Center of Gravity Stable: Low center of gravity +-------+ | | | X | <-- Low | | +-------+ Unstable: High center of gravity +-------+ | X | <-- High | | | | +-------+
The center of gravity is the balance point of the robot. Keeping it low and centered makes the robot stable.
Materials are the substances used to build the robot's body. Different materials have different properties.
The material you choose affects the robot's weight, strength, and cost. You need to choose the right material for the job.
| Material | Properties | Best For |
|---|---|---|
| Plastic | Light, cheap, easy to shape | Small robots, toys |
| Aluminium | Light, strong, more expensive | Medium robots, drones |
| Steel | Heavy, very strong | Large robots, factory machines |
| Wood | Cheap, easy to work with | Simple projects, prototypes |
| Carbon Fibre | Very light, very strong, expensive | Racing robots, drones |
A drone is made of carbon fibre. It is light and strong.
A school robot might be made of plastic or wood.
A toy robot might be made of plastic.
A locally made robot might use aluminium from recycled cans.
Materials Plastic: Light, cheap +-------+ | | +-------+ Aluminium: Light, strong +-------+ |=======| +-------+ Steel: Heavy, very strong +=======+ |=======| +=======+
Materials are the substances used to build the robot. Different materials have different properties. Choose the right material for the job.
Pneumatics is the use of air to create movement. It uses compressed air to push or pull things.
Pneumatics is used in many robots and machines. It is strong, fast, and clean. It is used in factories, hospitals, and construction.
Think of blowing up a balloon. The air pushes the balloon bigger. Pneumatics uses air to push or pull things in a robot.
A bus door opens and closes using pneumatics. Compressed air pushes the door.
A school project might use a syringe and tube to make a pneumatic arm.
An air pump for a bicycle uses pneumatics.
A mechanic uses a pneumatic drill to remove car tyres.
Pneumatics
Compressed Air
|
V
+-----------+
| Cylinder |
| +-----+ |
| | | |
| +-----+ |
+-----------+
|
V
Piston moves
|
V
Robot arm moves
Pneumatics is the use of air to create movement. It is strong, fast, and clean. It is used in many machines and robots.
Engineering measurement tools are devices used to measure things accurately.
Robots need precise parts. If a part is too big, it will not fit. If it is too small, it will be loose. Measurement tools help you get the right size.
| Tool | Measures | Example |
|---|---|---|
| Ruler | Length | Straight lines |
| Vernier Caliper | Length, diameter, depth | Small parts |
| Micrometer | Very small lengths | Thin wires |
| Multimeter | Voltage, current, resistance | Electronic circuits |
| Weighing Scale | Weight | Robot parts |
A mechanic uses a caliper to measure a car part.
Students use rulers and calipers in science class.
A tailor uses a measuring tape to measure cloth.
A trader uses a weighing scale to measure rice.
Measurement Tools Ruler: +-------------------+ | 1 | 2 | 3 | 4 | 5 | +-------------------+ Caliper: +-------------------+ | | | | | +----------+ | +-------------------+ Multimeter: +-------------------+ | [ 12.5 V ] | +-------------------+
Engineering measurement tools are devices used to measure things accurately. They help you get the right size for robot parts.
3D printing is a way to make objects from a CAD design. A machine builds the object layer by layer.
3D printing lets you make custom parts quickly. You do not need a factory. You can print your design at home or school.
Think of building a sandcastle. You add sand layer by layer. 3D printing works the same way, but with plastic.
Doctors use 3D printing to make custom medical implants.
Students use 3D printers to make parts for their robots.
Hobbyists use 3D printers to make toys and tools.
Nigerian startups use 3D printing to make prototypes and small products.
3D Printing
CAD Design
|
V
+-----------+
| 3D Printer|
| +-----+ |
| | | |
| +-----+ |
+-----------+
|
V
Printed Object
3D printing makes objects from a CAD design. It builds the object layer by layer. It lets you make custom parts quickly.
Debugging design problems means finding and fixing issues in the robot's design.
Design problems can cause the robot to fail. It might wobble. It might break. It might not fit together. Debugging helps you fix these problems before building.
| Problem | Cause | Solution |
|---|---|---|
| Robot wobbles | Unbalanced design | Lower the center of gravity |
| Parts do not fit | Wrong measurements | Check dimensions in CAD |
| Robot too heavy | Wrong materials | Use lighter materials |
| Robot too weak | Thin parts | Use thicker parts or stronger material |
| Motors not aligned | Poor design | Adjust motor mounts |
If a chair wobbles, the legs are not balanced. Fix the design.
If your robot's wheels are not straight, fix the design.
If a table is too heavy, use lighter wood.
If a keke napep tips over, the center of gravity is too high.
Debugging Design
[ Robot wobbles ]
|
V
[ Check balance ]
|
V
[ Check measurements ]
|
V
[ Fix design ]
|
V
[ Test again ]
Debugging design problems means finding and fixing issues in the robot's design. Common problems include wobbling, wrong measurements, and wrong materials.
Real robots use careful mechanical design to do their jobs.
| Robot | Design Features | Purpose |
|---|---|---|
| Robot Vacuum | Low profile, light, bump sensors | Clean under furniture |
| Self-Driving Car | Aerodynamic, strong, low center of gravity | Drive safely |
| Robot Arm | Strong joints, precise motors | Pick and place |
| Drone | Light, strong, balanced | Fly stably |
| Mars Rover | Rugged, six wheels, strong chassis | Explore Mars |
A robot vacuum is designed to be low so it can clean under beds.
A school robot is designed to be simple and easy to build.
A robot toy is designed to be safe and fun.
A robot used in a Nigerian factory is designed to be strong and durable.
Real Robot: Robot Vacuum
+-------------------+
| Low Profile |
| +-----------+ |
| | Sensors | |
| +-----------+ |
| +-----------+ |
| | Motors | |
| +-----------+ |
+-------------------+
|
V
Cleans under furniture
Real robots use careful mechanical design. Each robot's design is suited for its specific job.
Safety in mechanical design means making sure the robot does not hurt people or damage things.
Robots can be dangerous. They can have sharp edges. They can be heavy. They can move fast. Safety in design prevents accidents.
Factory robots have safety cages to keep people away.
In a robotics lab, students must follow safety rules.
Robot toys have rounded edges to prevent injury.
A robot in a Nigerian factory has emergency stop buttons.
Safety in Design
+-------------------+
| Emergency Stop |
| Button |
+-------------------+
|
V
+-------------------+
| Robot stops |
| immediately |
+-------------------+
Safety in mechanical design means making sure robots do not hurt people or damage things. Always follow safety rules.
The future of robot design is very exciting. Robots will become more advanced, more capable, and more useful.
Good design will make robots work better. They will be stronger, lighter, and smarter. They will help people in many ways.
Scientists are already working on soft robots that can squeeze through small spaces.
Students today are learning CAD to prepare for future jobs.
3D printers are becoming common in homes.
Nigerian universities are researching new materials for robot design.
Future of Robot Design
Today: Simple designs
|
V
Soon: Complex designs
|
V
Future: Self-designing robots
|
V
Future: Robots in every home
The future of robot design is exciting. Robots will become more advanced and more useful. They will change the world.
| Word | Simple Definition |
|---|---|
| Mechanical Design | Planning the physical parts of a robot. |
| CAD | Computer-Aided Design — software for designing on a computer. |
| 2D Design | Flat design with length and width. |
| 3D Design | Design with length, width, and height. |
| Assembly | A design that combines many parts. |
| Chassis | The frame or body of a robot. |
| Center of Gravity | The balance point of the robot. |
| Pneumatics | Using air to create movement. |
| 3D Printing | Making objects from a CAD design layer by layer. |
| Vernier Caliper | A tool for measuring small lengths. |
| Micrometer | A tool for measuring very small lengths. |
| Multimeter | A tool for measuring voltage, current, and resistance. |
| Concept | Real-Life Example |
|---|---|
| Mechanical Design | A car is designed before it is built. |
| CAD | Engineers use CAD to design aeroplanes. |
| 2D vs 3D | A map is 2D. A globe is 3D. |
| Assembly | A bicycle is an assembly of wheels, frame, and pedals. |
| Chassis | A car's chassis holds the engine and wheels. |
| Center of Gravity | A racing car has a low center of gravity. |
| Materials | A drone is made of carbon fibre. |
| Pneumatics | A bus door opens using compressed air. |
| Measurement | A mechanic uses a caliper to measure car parts. |
| 3D Printing | Doctors use 3D printing to make implants. |
| Concept | Nigerian Example |
|---|---|
| Mechanical Design | A keke napep is designed before it is built. |
| CAD | Nigerian engineers use AutoCAD to design buildings. |
| 2D vs 3D | A drawing of a house is 2D. A model is 3D. |
| Assembly | A generator is an assembly of engine, fuel tank, and alternator. |
| Chassis | A keke napep's chassis holds the engine and passenger cabin. |
| Center of Gravity | A loaded truck must drive carefully to avoid tipping. |
| Materials | A locally made robot might use aluminium from recycled cans. |
| Pneumatics | A mechanic uses a pneumatic drill to remove car tyres. |
| Measurement | A trader uses a weighing scale to measure rice. |
| 3D Printing | Nigerian startups use 3D printing to make prototypes. |
| Concept | Everyday Example |
|---|---|
| Mechanical Design | A chair is designed before it is made. |
| CAD | Architects use CAD to design houses. |
| 2D vs 3D | A photo is 2D. A sculpture is 3D. |
| Assembly | A bicycle is an assembly of parts. |
| Chassis | A toy car's chassis holds the motor. |
| Center of Gravity | A table with heavy legs is stable. |
| Materials | A toy robot is made of plastic. |
| Pneumatics | A bicycle pump uses air. |
| Measurement | A tailor uses a measuring tape. |
| 3D Printing | Hobbyists print toys and tools. |
| Mistake | Why It Is Wrong | How to Fix It |
|---|---|---|
| Not planning before building | Parts do not fit. | Design in CAD first. |
| Ignoring center of gravity | Robot tips over. | Lower the center of gravity. |
| Using wrong materials | Robot too heavy or too weak. | Choose the right material. |
| Wrong measurements | Parts do not fit. | Measure accurately. |
| Ignoring safety | Someone could get hurt. | Follow safety rules. |
| Not testing design | Problems go unnoticed. | Test the design before building. |
+-------------------+
| Idea |
+-------------------+
|
V
+-------------------+
| CAD Design |
+-------------------+
|
V
+-------------------+
| Simulation |
+-------------------+
|
V
+-------------------+
| 3D Print |
+-------------------+
|
V
+-------------------+
| Build Robot |
+-------------------+
( Start )
|
V
+----------------+
| Identify need |
+----------------+
|
V
+----------------+
| Design in CAD |
+----------------+
|
V
+----------------+
| Test design |
+----------------+
|
V
+----------------+
| Build prototype|
+----------------+
|
V
+----------------+
| Test prototype |
+----------------+
|
V
( Improve )
| Material | Weight | Strength | Cost | Best For |
|---|---|---|---|---|
| Plastic | Light | Low | Low | Small robots |
| Aluminium | Light | Medium | Medium | Medium robots |
| Steel | Heavy | High | Medium | Large robots |
| Carbon Fibre | Very light | Very high | High | Racing robots |
Step 1: Design in CAD
|
V
Step 2: Test design
|
V
Step 3: Choose materials
|
V
Step 4: Build chassis
|
V
Step 5: Add motors and sensors
|
V
Step 6: Program
|
V
Step 7: Test and improve
Mechanical design is planning the physical parts of a robot. It includes shape, size, and materials.
CAD stands for Computer-Aided Design. It is software used to create designs on a computer.
2D design is flat. 3D design has depth. 3D design is better for robots.
CAD tools are software programs used to create designs. Different tools are good for different jobs.
An assembly in CAD combines many parts into one object. It shows how parts fit together.
A chassis is the frame or body of a robot. It holds all the parts together.
The center of gravity is the balance point. Keeping it low and centered makes the robot stable.
Materials are the substances used to build the robot. Different materials have different properties.
Pneumatics is the use of air to create movement. It is strong, fast, and clean.
Engineering measurement tools are devices used to measure things accurately.
3D printing makes objects from a CAD design. It builds the object layer by layer.
Debugging design problems means finding and fixing issues in the robot's design.
Real robots use careful mechanical design. Each robot's design is suited for its specific job.
Safety in mechanical design means making sure robots do not hurt people or damage things.
The future of robot design is exciting. Robots will become more advanced and more useful.
In this module, you learned about mechanical design and CAD. You learned that mechanical design is planning the physical parts of a robot.
You learned about CAD — Computer-Aided Design. You learned about 2D and 3D design. You learned about common CAD tools. You learned about assemblies and how they combine parts.
You learned about designing a robot chassis. You learned about the center of gravity and why it matters. You learned about materials — plastic, aluminium, steel, and carbon fibre. You learned about pneumatics — using air to move things. You learned about engineering measurement tools. You learned about 3D printing.
You learned how to debug design problems. You learned about real robots and their design. You learned about safety. You learned about the future of robot design.
Most importantly, you learned that good design is the foundation of every great robot. Without good design, even the best program will not work. With good design, your robot will be strong, stable, and reliable.
In the next module, you will learn about Capstone Project. You will put everything you have learned into one big project. You will design, build, program, and test a complete robot.
But for now, take a moment to celebrate what you have learned. You have taken another big step in your journey to becoming a robotics expert. Well done!
Match the term on the left with its definition on the right.
| Term | Definition |
|---|---|
| 1. Mechanical Design | A. Computer-Aided Design |
| 2. CAD | B. The frame or body of a robot |
| 3. 3D Design | C. Planning the physical parts of a robot |
| 4. Assembly | D. The balance point of the robot |
| 5. Chassis | E. Design with length, width, and height |
| 6. Center of Gravity | F. Combining many parts in CAD |
| 7. Pneumatics | G. Making objects layer by layer |
| 8. 3D Printing | H. Using air to create movement |
Answers: 1-C, 2-A, 3-E, 4-F, 5-B, 6-D, 7-H, 8-G
Title: Design a Robot Chassis
Instructions:
Example:
Task: Line-following robot Chassis design: - Rectangle base - Two motor mounts at the back - One caster wheel at the front - Sensor mount at the front - Battery holder in the middle Materials: - Plastic base - Aluminium motor mounts
Title: Design Scavenger Hunt
Instructions:
Example:
| Object | Material | Purpose |
|---|---|---|
| Chair | Wood | Seating |
| Bottle | Plastic | Holding water |
| Car | Steel and aluminium | Transport |
| Phone | Plastic and glass | Communication |
| Table | Wood | Working surface |
Title: Design and Build a Robot Chassis
Goal: Create a strong, balanced chassis for a small robot.
Steps:
Deliverables:
Title: Design a Robot Arm Using CAD
Instructions:
Grading Criteria:
| Criteria | Points |
|---|---|
| Design is complete and functional | 30 |
| Uses CAD software | 20 |
| Parts fit together | 20 |
| Report is clear | 15 |
| Design is creative | 15 |
| Total | 100 |
In Module Seven, you will complete a Capstone Project. You will put everything you have learned into one big project. You will design, build, program, and test a complete robot.
To prepare for Module Seven:
Get ready for an exciting journey into the world of complete robot projects!
Congratulations! You have completed Module Six of Fundamentals of Robotics Level Two. You have learned about mechanical design and CAD.
You learned that mechanical design is planning the physical parts of a robot. You learned about CAD — Computer-Aided Design. You learned about 2D and 3D design. You learned about common CAD tools. You learned about assemblies and how they combine parts.
You learned about designing a robot chassis. You learned about the center of gravity and why it matters. You learned about materials — plastic, aluminium, steel, and carbon fibre. You learned about pneumatics — using air to move things. You learned about engineering measurement tools. You learned about 3D printing.
You learned how to debug design problems. You learned about real robots and their design. You learned about safety. You learned about the future of robot design.
You also learned many examples from Nigeria, from your home, from school, and from everyday life. You learned through stories, illustrations, and activities.
Now you are ready for Module Seven: Capstone Project. In Module Seven, you will put everything you have learned into one big project. You will design, build, program, and test a complete robot. You will present your project to the class.
But before you move on, take a moment to review this module. Make sure you understand the key ideas. Practise using CAD. Draw diagrams. Test your designs. The more you practise, the better you will become.
You are doing great. Keep learning. Keep exploring. Keep building. The world of robotics is waiting for you!
End of Module Six
Next: Module Seven — Capstone Project
Welcome to Module Seven! This is the final module of Fundamentals of Robotics Level Two. You have come a long way.
In Module One, you learned how to write programs. In Module Two, you learned about sensors. In Module Three, you learned about motors and motion. In Module Four, you learned about autonomous navigation. In Module Five, you learned about integration. In Module Six, you learned about mechanical design and CAD. Now you will put everything together in a Capstone Project.
A capstone project is a big project that brings together everything you have learned. It is like the roof of a house. All the walls, doors, and windows come together to make a complete building. Your capstone project is the roof that completes your learning.
In this module, you will:
This is the most exciting part of the course. You will become a real robotics engineer. You will create something new. You will solve a problem. You will show the world what you can do.
Let us begin!
By the end of this module, you will be able to:
Once upon a time, in the city of Enugu, Nigeria, there lived a group of young robotics students. Their names were Ada, Tunde, Ngozi, Chidi, and Amina. They had all completed Fundamentals of Robotics Level Two.
One day, their teacher announced exciting news. "There will be a Big Robotics Exhibition in Abuja," she said. "Students from all over Nigeria will come and show their robots. The best project will win a prize."
The students were excited. They wanted to enter the exhibition. But they had a problem. They did not have a project idea.
"What problem can we solve?" asked Ada.
"Let us think about our communities," said Tunde. "What problems do people face every day?"
Ngozi had an idea. "In my village, farmers have trouble knowing when their crops are ready to harvest. They waste a lot of time checking."
Chidi had another idea. "In my area, the market is very crowded. It is hard for traders to move goods around."
Amina had a third idea. "In my school, we waste a lot of water because the taps are always left running."
The students discussed these ideas. They decided to build a robot that could help farmers. They would build a Crop Monitoring Robot.
The robot would:
The students worked hard. They designed the robot using CAD. They built the chassis. They added motors, sensors, and a small computer. They wrote programs. They tested the robot in a small garden.
At first, the robot did not work well. It got stuck in the mud. The sensors gave wrong readings. The program crashed.
But the students did not give up. They debugged the problems. They improved the design. They tested again and again.
Finally, the robot worked. It moved through the garden. It checked the soil. It sent alerts to a phone. It was a success.
At the exhibition in Abuja, the students presented their robot. The judges were impressed. The robot won first prize.
But more importantly, the students learned something powerful: with teamwork, planning, and hard work, you can build anything.
That is what you will do in this module. You will plan, design, build, program, and test your own robot. You will create a capstone project.
Let us begin!
A capstone project is a big project that brings together everything you have learned. It is the final project of a course.
A capstone project shows what you can do. It proves that you have learned the skills. It is a chance to be creative and solve a real problem.
Think of building a house. You learn to lay bricks. You learn to install pipes. You learn to wire electricity. The capstone project is building the whole house. It uses all your skills.
A university student might do a capstone project to build a robot that helps doctors.
A school student might do a capstone project to build a robot that cleans the classroom.
A hobbyist might do a capstone project to build a robot that waters plants.
A Nigerian student might do a capstone project to build a robot that helps farmers in their village.
Capstone Project
Learn Skills
|
V
Apply Skills
|
V
Build Project
|
V
Present Project
|
V
Celebrate 🎉
A capstone project is a big project that brings together everything you have learned. It shows what you can do.
Choosing a project idea means deciding what your robot will do. It should solve a real problem.
A good project idea keeps you motivated. It makes the project meaningful. It helps you focus your learning.
Think of what problems you see around you. A problem could be: too much traffic, dirty streets, or water waste. Your robot can help solve one of these problems.
A student might choose to build a robot that sorts recycling.
A student might choose to build a robot that cleans the classroom.
A student might choose to build a robot that feeds pets.
A student might choose to build a robot that helps farmers detect ripe crops.
Choosing a Project Idea
Look around
|
V
Find a problem
|
V
Think of a robot solution
|
V
Check skills and materials
|
V
Choose idea
Choosing a project idea means deciding what your robot will do. It should solve a real problem.
Planning means thinking about what you will do before you do it. It includes setting goals, making a schedule, and listing what you need.
Without planning, projects become messy. You might forget something. You might run out of time. Planning helps you stay organised.
Think of planning a party. You decide the date. You make a guest list. You buy food. You decorate. That is planning.
A builder plans a house before building. They make a blueprint and schedule.
A student plans a science project. They decide what to research and when to submit.
A parent plans a family trip. They decide where to go, how to get there, and what to pack.
A trader plans her day. She decides what to buy, where to sell, and how much to charge.
Planning Process
Goal
|
V
List needs
|
V
Make schedule
|
V
Assign tasks
|
V
Set checkpoints
Planning means thinking before doing. It helps you stay organised and finish your project on time.
Designing means creating a plan for your robot. It includes drawing the shape, choosing materials, and deciding how parts fit together.
A good design makes building easier. It prevents mistakes. It ensures the robot works well.
Think of drawing a picture before painting it. The drawing is the design. The painting is the build.
Car designers draw cars in CAD before building them.
Students design their robot chassis before building.
A carpenter designs a chair before cutting wood.
A tailor designs a dress before sewing.
Designing a Robot
Sketch on paper
|
V
Draw in CAD
|
V
Choose materials
|
V
Place motors and sensors
|
V
Check measurements
|
V
Final design
Designing means creating a plan for your robot. It includes drawing, choosing materials, and deciding how parts fit together.
Building means putting the robot together using your design.
Building turns your design into a real robot. It is where you see if your plan works.
Think of assembling a jigsaw puzzle. You follow the picture to put the pieces together. Building a robot is like that.
A car factory builds cars on an assembly line.
Students build their robot in the lab.
A child builds a toy with LEGO blocks.
A mechanic builds a generator from parts.
Building a Robot
Chassis
|
V
Motors and wheels
|
V
Sensors
|
V
Wires
|
V
Brain
|
V
Test
Building means putting the robot together. It turns your design into a real robot.
Programming means writing instructions for your robot. It tells the robot what to do.
Without a program, the robot cannot do anything. Programming brings the robot to life.
Think of giving directions to a friend. You say: "Go straight. Turn left. Stop." That is programming.
A washing machine has a program for washing clothes.
Students program their robot to navigate a maze.
A microwave has a program for heating food.
A POS machine has a program for processing payments.
Programming a Robot
Plan
|
V
Write code
|
V
Upload
|
V
Test
|
V
Debug
|
V
Done
Programming means writing instructions for your robot. It tells the robot what to do.
Testing means running your robot to see if it works correctly.
Testing finds problems before you present your robot. It helps you fix mistakes.
Think of tasting food before serving it. If it needs salt, you add salt. Testing a robot is like tasting food.
Car manufacturers test cars before selling them.
Students test their robot in the lab.
You test a new phone before using it.
A mechanic tests a generator before delivering it.
Testing a Robot
Test part 1
|
V
Test part 2
|
V
Test whole robot
|
V
Find problems
|
V
Fix problems
|
V
Test again
Testing means running your robot to see if it works. It helps you find and fix problems.
Debugging means finding and fixing problems in your robot.
Every robot has problems at first. Debugging helps you fix them. It makes your robot work correctly.
Think of a puzzle with a missing piece. You look for the missing piece and put it in. Debugging is like finding the missing piece.
| Problem | Cause | Solution |
|---|---|---|
| Robot does not move | Loose wire or dead battery | Check connections and power |
| Robot moves wrong | Program logic error | Debug the program |
| Sensor gives wrong reading | Needs calibration | Calibrate the sensor |
| Robot wobbles | Unbalanced design | Lower center of gravity |
| Robot stops randomly | Loose connection | Check all wires |
If your TV remote does not work, you check the batteries. That is debugging.
If your robot does not move, you check the motor wires.
If your fan does not spin, you check the plug.
If your generator does not start, you check the fuel and battery.
Debugging
[ Robot not working ]
|
V
[ Check sensors ]
|
V
[ Check motors ]
|
V
[ Check program ]
|
V
[ Fix problem ]
|
V
[ Test again ]
Debugging means finding and fixing problems in your robot. It makes your robot work correctly.
Documenting means writing down what you did. It includes drawings, notes, and photos.
Documentation helps you remember what you did. It helps others understand your project. It is required for presentations.
Think of a diary. You write what you did each day. Documentation is like a diary for your project.
Scientists document their experiments in notebooks.
Students keep a project notebook.
A cook writes down a recipe.
A trader keeps a record of sales.
Documentation Project Notebook +-------------------+ | Date: 10/10/2026 | | What I did: | | - Built chassis | | - Attached motors | | Problems: | | - Wires loose | | Solutions: | | - Tightened wires | +-------------------+
Documenting means writing down what you did. It helps you remember and helps others understand your project.
Presenting means showing your project to others. It includes explaining what it does and how it works.
Presenting shows what you have learned. It helps others understand your work. It is a chance to be proud of your achievement.
Think of show-and-tell at school. You show your project and tell others about it. That is presenting.
Scientists present their research at conferences.
Students present their projects at science fairs.
You show your new toy to your friends.
A trader shows new goods to customers.
Presenting
Prepare
|
V
Practice
|
V
Show robot
|
V
Explain
|
V
Answer questions
|
V
Celebrate 🎉
Presenting means showing your project to others. It shows what you have learned.
Working in a team means collaborating with others to complete a project.
Teamwork makes projects easier. Different people have different skills. Together, you can do more.
Think of a football team. Each player has a role. Together they win. Teamwork in robotics is the same.
| Role | Responsibility |
|---|---|
| Project Leader | Keeps the team on track |
| Designer | Draws the robot and chooses materials |
| Builder | Assembles the robot |
| Programmer | Writes the code |
| Tester | Tests the robot and finds problems |
| Documenter | Writes down what the team does |
Engineers work in teams to design cars.
Students work in groups for science projects.
A family works together to clean the house.
Workers in a factory work as a team to assemble products.
Teamwork
Leader
|
+-- Designer
|
+-- Builder
|
+-- Programmer
|
+-- Tester
|
+-- Documenter
Working in a team means collaborating with others. Different roles make the project easier.
Solving real problems means using your robot to help people in real life.
Robots are most useful when they solve real problems. They can help farmers, doctors, traders, and many others.
Think of a problem in your community. Your robot can help solve it. That is solving a real problem.
A robot that delivers medicine in hospitals.
A robot that cleans the classroom.
A robot that waters plants.
A robot that helps farmers detect ripe tomatoes.
Solving Real Problems
Problem
|
V
Think of solution
|
V
Build robot
|
V
Test
|
V
Solve problem
Solving real problems means using your robot to help people. Robots are most useful when they solve real problems.
Improving means making your project better after testing.
No project is perfect the first time. Improving makes it better. It shows you are learning.
Think of writing a story. You write it once. Then you read it and make it better. That is improving.
Car companies improve cars every year.
Students improve their projects after feedback.
You improve a recipe after tasting it.
A trader improves her stall after customer feedback.
Improving
Test
|
V
Find problems
|
V
Think of solutions
|
V
Make changes
|
V
Test again
Improving means making your project better. It shows you are learning and growing.
Celebrating means being proud of what you have done.
You have worked hard. You have learned a lot. You deserve to celebrate.
Think of finishing a race. You cross the finish line. You cheer. That is celebrating.
Graduates celebrate after finishing university.
Students celebrate after presenting projects.
Families celebrate birthdays and achievements.
Communities celebrate festivals and successes.
Celebrating
Finish project
|
V
Show to others
|
V
Take photos
|
V
Be proud
|
V
Celebrate 🎉
Celebrating means being proud of what you have done. You have worked hard and deserve to celebrate.
What comes next means thinking about your future in robotics.
Learning never stops. There is always more to learn. Thinking about the future helps you plan your next steps.
Think of climbing a mountain. You reach one peak. Then you see another peak. You keep climbing. Learning is like that.
Engineers keep learning new skills throughout their careers.
Students continue to advanced robotics courses.
Hobbyists keep building and improving.
Nigerian students can join robotics clubs and competitions.
What Comes Next?
Finish Level 2
|
V
Learn more
|
V
Build more
|
V
Enter competitions
|
V
Become an expert
What comes next means thinking about your future. Learning never stops.
| Word | Simple Definition |
|---|---|
| Capstone Project | A big project that brings together everything you have learned. |
| Project Idea | What your robot will do. |
| Planning | Thinking before doing. |
| Designing | Creating a plan for your robot. |
| Building | Putting the robot together. |
| Programming | Writing instructions for your robot. |
| Testing | Running your robot to see if it works. |
| Debugging | Finding and fixing problems. |
| Documenting | Writing down what you did. |
| Presenting | Showing your project to others. |
| Teamwork | Working together with others. |
| Improving | Making your project better. |
| Concept | Real-Life Example |
|---|---|
| Capstone Project | A university student builds a robot for their final project. |
| Choosing an Idea | Finding a problem in your community. |
| Planning | A builder makes a blueprint and schedule. |
| Designing | Car designers draw cars in CAD. |
| Building | A car factory builds cars on an assembly line. |
| Programming | A washing machine has a program. |
| Testing | Car manufacturers test cars before selling. |
| Debugging | Checking batteries when a remote fails. |
| Documenting | Scientists write in notebooks. |
| Presenting | Scientists present at conferences. |
| Teamwork | Engineers work in teams. |
| Improving | Car companies improve cars every year. |
| Celebrating | Graduates celebrate after finishing university. |
| Concept | Nigerian Example |
|---|---|
| Capstone Project | A Nigerian student builds a robot for a national competition. |
| Choosing an Idea | A student builds a robot to help farmers detect ripe crops. |
| Planning | A trader plans her day. |
| Designing | A tailor designs a dress before sewing. |
| Building | A mechanic builds a generator. |
| Programming | A POS machine has a program for payments. |
| Testing | A mechanic tests a generator before delivering. |
| Debugging | Checking fuel and battery when a generator fails. |
| Documenting | A trader keeps a record of sales. |
| Presenting | A trader shows new goods to customers. |
| Teamwork | Factory workers assemble products as a team. |
| Improving | A trader improves her stall after feedback. |
| Celebrating | Communities celebrate festivals and successes. |
| Concept | Everyday Example |
|---|---|
| Capstone Project | Building a piece of furniture from scratch. |
| Choosing an Idea | Deciding what to cook for dinner. |
| Planning | Planning a family trip. |
| Designing | A carpenter designs a chair. |
| Building | Building a toy with LEGO. |
| Programming | Setting a microwave timer. |
| Testing | Testing a new phone. |
| Debugging | Checking the plug when a fan stops. |
| Documenting | Writing a recipe. |
| Presenting | Showing a new toy to friends. |
| Teamwork | A family cleaning the house together. |
| Improving | Improving a recipe after tasting. |
| Celebrating | Celebrating a birthday. |
| Mistake | Why It Is Wrong | How to Fix It |
|---|---|---|
| Not planning | Project becomes messy. | Make a plan first. |
| Choosing a project that is too hard | You cannot finish it. | Choose something achievable. |
| Not testing | Problems go unnoticed. | Test everything. |
| Not debugging | Robot does not work. | Fix problems immediately. |
| Not documenting | You forget what you did. | Write everything down. |
| Not practicing presentation | You get nervous. | Practice before presenting. |
+-------------------+
| Choose Idea |
+-------------------+
|
V
+-------------------+
| Plan |
+-------------------+
|
V
+-------------------+
| Design |
+-------------------+
|
V
+-------------------+
| Build |
+-------------------+
|
V
+-------------------+
| Program |
+-------------------+
|
V
+-------------------+
| Test |
+-------------------+
|
V
+-------------------+
| Debug |
+-------------------+
|
V
+-------------------+
| Improve |
+-------------------+
|
V
+-------------------+
| Present |
+-------------------+
|
V
+-------------------+
| Celebrate 🎉 |
+-------------------+
( Start )
|
V
+----------------+
| Robot fails? |
+----------------+
/ \
YES NO
/ \
V V
+---------+ +-----------+
| Find | | Done |
| problem | | |
+---------+ +-----------+
|
V
+---------+
| Fix |
| problem |
+---------+
|
V
+---------+
| Test |
| again |
+---------+
|
V
( Back to start )
| Role | Responsibility | Skills Needed |
|---|---|---|
| Project Leader | Keeps team on track | Organisation, communication |
| Designer | Draws robot, chooses materials | Creativity, CAD |
| Builder | Assembles robot | Hands-on skills |
| Programmer | Writes code | Programming, logic |
| Tester | Tests robot, finds problems | Attention to detail |
| Documenter | Writes down what team does | Writing, organisation |
Week 1: Choose idea and plan
|
V
Week 2: Design
|
V
Week 3: Build
|
V
Week 4: Program
|
V
Week 5: Test and debug
|
V
Week 6: Improve
|
V
Week 7: Document
|
V
Week 8: Present
|
V
Week 9: Celebrate 🎉
A capstone project is a big project that brings together everything you have learned.
Choosing a project idea means deciding what your robot will do. It should solve a real problem.
Planning means thinking before doing. It helps you stay organised.
Designing means creating a plan for your robot. It includes drawing and choosing materials.
Building means putting the robot together. It turns your design into a real robot.
Programming means writing instructions for your robot. It tells the robot what to do.
Testing means running your robot to see if it works. It helps you find problems.
Debugging means finding and fixing problems. It makes your robot work correctly.
Documenting means writing down what you did. It helps you remember and helps others understand.
Presenting means showing your project to others. It shows what you have learned.
Working in a team means collaborating with others. Different roles make the project easier.
Solving real problems means using your robot to help people.
Improving means making your project better. It shows you are learning.
Celebrating means being proud of what you have done. You deserve to celebrate.
What comes next means thinking about your future. Learning never stops.
In this module, you learned how to complete a capstone project. You learned that a capstone project brings together everything you have learned.
You learned how to choose a project idea that solves a real problem. You learned how to plan your project. You learned how to design your robot. You learned how to build your robot. You learned how to program your robot. You learned how to test your robot. You learned how to debug your robot. You learned how to document your work. You learned how to present your project.
You learned about working in a team. You learned about solving real problems. You learned about improving your project. You learned about celebrating your achievement. You learned about what comes next.
Most importantly, you learned that with planning, hard work, and teamwork, you can build anything. You are now a robotics engineer.
Congratulations on completing Fundamentals of Robotics Level Two!
Match the term on the left with its definition on the right.
| Term | Definition |
|---|---|
| 1. Capstone Project | A. Creating a plan for your robot |
| 2. Planning | B. A big project that brings everything together |
| 3. Designing | C. Thinking before doing |
| 4. Building | D. Writing instructions for your robot |
| 5. Programming | E. Putting the robot together |
| 6. Testing | F. Showing your project to others |
| 7. Debugging | G. Running your robot to see if it works |
| 8. Presenting | H. Finding and fixing problems |
Answers: 1-B, 2-C, 3-A, 4-E, 5-D, 6-G, 7-H, 8-F
Title: Plan a Capstone Project
Instructions:
Example:
Problem: Farmers waste time checking crops Robot solution: Crop Monitoring Robot Plan: - Week 1: Research and design - Week 2: Build chassis - Week 3: Add sensors and motors - Week 4: Program - Week 5: Test and improve - Week 6: Present Design: - Small robot with wheels - Soil moisture sensor - Camera for crop colour - Small computer
Title: My Dream Robot
Instructions:
Example:
| Problem | Robot Solution | Sensors Needed | Motors Needed |
|---|---|---|---|
| Water waste in schools | Robot that closes taps | Water sensor, touch sensor | Servo motor |
| Crowded markets | Robot that carries goods | Ultrasonic sensor | DC motors |
| Ripe crop detection | Robot that checks crops | Colour sensor | DC motors |
Title: Build a Simple Capstone Robot
Goal: Create a small robot that solves a simple problem.
Steps:
Deliverables:
Title: Complete a Capstone Project
Instructions:
Grading Criteria:
| Criteria | Points |
|---|---|
| Project solves a real problem | 20 |
| Design is complete | 15 |
| Robot is well built | 15 |
| Program works correctly | 20 |
| Documentation is clear | 15 |
| Presentation is confident | 15 |
| Total | 100 |
Congratulations! You have completed Fundamentals of Robotics Level Two. You are now ready for Level Three.
In Level Three, you will learn more advanced topics:
To prepare for Level Three:
Get ready for an exciting journey into advanced robotics!
Congratulations! You have completed Module Seven of Fundamentals of Robotics Level Two. You have learned how to complete a capstone project.
You learned that a capstone project brings together everything you have learned. You learned how to choose a project idea that solves a real problem. You learned how to plan your project. You learned how to design your robot. You learned how to build your robot. You learned how to program your robot. You learned how to test your robot. You learned how to debug your robot. You learned how to document your work. You learned how to present your project.
You learned about working in a team. You learned about solving real problems. You learned about improving your project. You learned about celebrating your achievement. You learned about what comes next.
You also learned many examples from Nigeria, from your home, from school, and from everyday life. You learned through stories, illustrations, and activities.
Most importantly, you learned that with planning, hard work, and teamwork, you can build anything. You are now a robotics engineer.
You have completed Fundamentals of Robotics Level Two. You have learned:
You are now ready for Level Three. You are ready for advanced robotics. You are ready to change the world.
Keep learning. Keep exploring. Keep building. The world of robotics is waiting for you!
End of Module Seven
End of Fundamentals of Robotics Level Two
Next: Fundamentals of Robotics Level Three