All courses
Lesson 1 of 20 · Blocks track

Meet Mobot — Open the Box

  • 🧩 Today's parts: 🟡 Control unit · ⚡ Energy · 🟣 Actuators (the LEDs)
  • You will need: the kit, a computer, the USB-C cable
  • Before this lesson: nothing! This is the very first one.
Robot Awakeneryour badge

🎯 Your mission

Hi, Mobot Engineer! 👋

That's you. It's what everyone who builds a Mobot is called — and in twenty lessons' time, when you finish the championship, you'll get the certificate with that name on it.

Inside that box is a robot that cannot do anything yet.

No moving. No beeping. No seeing. Nothing.

Today you are going to wake it up — and by the end of this lesson, a light on your board will turn on because you told it to.

That light is small. But it is the first thing in your whole life that a robot has done because you said so.

Let's go. 🚀

🎒 What you need

  • Your Mobot Smart Car box, unopened
  • A computer (Windows, Mac or Linux)
  • The USB-C cable from the box
  • A clear table
🔋 You do not need batteries today. The USB-C cable carries power as well as your programs, so the board runs happily straight from your computer. The batteries stay in the box until Lesson 9, when the robot is built and needs to drive away from the cable.

🛡️ The safety rules

Read these once, properly. They're the same ones printed in your guidebook.

  • This kit has small parts. Keep it away from children under 5.
  • An adult should help anyone under 10.
  • Never put the connection wires into a wall socket. They are for the board only.
  • Keep the robot away from water.
  • Use it on a stable, dry, flat surface.
  • Always switch the board off before plugging or unplugging a sensor.
  • Don't block the wheels or motors while they're running.
  • Never press RESET while code is uploading. If you do by accident, unplug, plug back in, and upload again.

💡 The new idea

Every robot in the world has four parts

A racing car robot, a factory arm, a Mars rover, a drone — all of them.

Four big circles — control unit, sensors, actuators, energy — each holding the real Mobot components that belong to it
#PartWhat it doesThink of it as…
1🟡 Control unitthinks and decidesthe brain
2🟢 Sensorstake information inthe senses
3🟣 Actuatorsput something outthe muscles and voice
4🔴 Energypowers all threethe food
🧠 This is the map for the whole course. At the top of every lesson you'll see which of the four you're working with that day. By Lesson 9 you'll have met all of them — and then you put them together into a robot.

Now sort your own kit

Tip everything out onto the table. Then put each piece into its group.

Fill this in as you go:

Part of the robotWhat I found in my box
🟡 Control unit________________________
🟢 Sensors________________________
🟣 Actuators________________________
🔴 Energy________________________
Here's the answer, once you've had a go:

So what is firmware?

Right now the brain does not even know how to listen to you.

Firmware is a one-time gift you give the control unit. It teaches the board how to understand the programs you will send it later.

You only ever do this once. After today, you will never think about firmware again.

🧠 It's like teaching someone your language before you start telling them stories.

🧪 Try the block

Step 1 — Plug Mobot into your computer

Take the USB-C cable. One end into the MoBoard Robotics, the other end into your computer.

Where does it go? Here it is on the board — and while you're looking, find LED 1 and LED 2 too. They're the two tiny lights you're about to switch on.

The MoBoard with arrows to the USB-C socket, LED 1 (red) and LED 2 (blue)

🔊 Listen! The board plays a little welcome sound to say hello. That's your first sign it's alive and getting power.

Photo coming soon
USB-C cable plugged into the MoBoard, board powered up

Step 2 — Flash the firmware

Go to flash.mobot.dz in your browser.

Photo coming soon
The Mobot Flash home page showing "No device connected" and the Sign in to Flash button

1 · Sign in. Click Sign in to Flash and log in with your Mobot account.

Photo coming soon
The Mobot Flash sign-in screen

2 · Choose your product. Along the top you'll see the products. Click Robotics — "Robotics development board with motor control". Leave the version on latest.

Photo coming soon
The product tabs at the top with Robotics selected and the version set to latest

3 · Connect. Click the green Connect button, then pick your board from the little window your browser opens.

When it works, the bar turns green and tells you which chip it found: Connected — ESP32.

Photo coming soon
The connected state showing the green Connected bar and the chip name

4 · Flash it. Click Flash Firmware and watch. Six steps light up one after another:

Connect → Detect → Download → Erase → Write → Verify
Photo coming soon
The flashing progress with the six steps, Erase currently spinning

5 · Done! 🎉

Photo coming soon
The finished state, all six steps ticked green
⚠️ Don't touch the cable while it's flashing. If the cable moves, the flash stops halfway. If that happens, unplug, plug back in and start again — nothing is broken.

Your robot is awake. It cannot do anything yet — but now it can listen.

Step 3 — Open Mobot IDE

Go to ide.mobot.dz.

This is where you will build every program in this course.

Photo coming soon
The full Mobot IDE window: control panel top-left, PRODUCT panel below it, category list, empty canvas

Look at the panel down the left-hand side. In the middle of it there's a section called PRODUCT, with four little circles:

IoT · Robotics · Mini · Robotics Formation

Click Robotics. It lights up green. Now the IDE knows which board you have, and shows you the right blocks.

⚠️ Picking the wrong product is the number one reason programs don't work. Check it every single time you open the IDE.

Step 4 — Connect the board to the IDE

Flashing and coding are two different jobs, so you connect again — this time to the IDE.

At the very top of the left panel you'll see:

⚪ Disconnected [ Connect ]

Click Connect, pick your board from the little window, and watch it change to:

🟢 Connected [ Disconnect ]
Photo coming soon
The panel showing Disconnected with the green Connect button
Photo coming soon
The panel showing Connected, with Send to Device now bright yellow

Notice what happened: the Send to Device button was pale and unclickable. Now it's bright yellow and ready.

💡 Pale button = not connected. If Send to Device looks faded, you skipped this step.

🧰 Meet the toolbox

Down the middle of the screen there's a list of drawers. Each one is full of blocks.

You won't use them all today, but it helps to know they're there — and to know the order, because every lesson tells you which drawer to open.

DrawerWhat's inside
🔍 Searchfind any block by typing its name
🎬 Eventsthe block every program starts with
✥ Movementsthe motors
💬 Display and Soundthe LEDs and the buzzer
🌡️ Sensorsline, distance, colour, battery
🔌 Pinsthe board's raw connections
🏷️ Serialshowing messages on your screen
📱 Bluetoothtalking to your phone
➕ Addonsthe extra parts you can buy separately
🔁 Loops & Controlrepeating and waiting
🧠 Logic & Mathdeciding and comparing
🔤 Textworking with words
📦 Variablesremembering a number
🧱 My Blocksblocks you invent
🧱 That last one is the exciting one. In Lesson 3 you will make your own blocks, with your own names, and use them for the rest of the course.

🤔 Guess first

Here is your very first program. Just two blocks.

Block screenshot coming soon
Mobot Start → Set LED 1 ON

Before you send it — what do you think will happen?

Say it out loud, or write it down:

I think the robot will ______________________.

Got your guess? Good. Now find out.

🧱 Build it

  1. From Events, drag out Mobot Start. Every program begins with this block. Nothing works without it.
  2. From Display and Sound, drag Set LED [1] [ON] and snap it underneath.

That's it. Two blocks.

  1. Click Send to Device.
  2. Wait for it to finish.

👀 Look at your board.

A light is on. It was off. Now it is on. Because of you. 🎉

🚀 Run the mission

Mission 1 — Make both eyes open

Can you make both LEDs turn on?

You already know everything you need. Add one more block and change its number.

Block screenshot coming soon
Mobot Start → Set LED 1 ON → Set LED 2 ON

Mission 2 — One eye open, one eye shut

Now make LED 1 on and LED 2 off.

Try it before you look at the answer.

Block screenshot coming soon
Mobot Start → Set LED 1 ON → Set LED 2 OFF

🎉 You just made a robot wink.

Mission 3 — 🌗 The dimmer switch

Look in Display and Sound again. There's a second LED block, and it's cleverer:

Set LED [1] to ( 1 ) %

That number is brightness, from 0 to 100.

  • 0 = completely off
  • 50 = half bright
  • 100 = as bright as it goes

The first block only knew ON and OFF. This one knows everything in between.

Try this:

Block screenshot coming soon
Mobot Start → Set LED 1 to 60 % → Set LED 2 to 30 %

Send it. Two lights, both on, but one brighter than the other.

Now experiment:

TryWhat I saw
Both at 100 %______________________
Both at 10 %______________________
LED 1 at 100, LED 2 at 5______________________
Both at 0 %______________________
🧠 This is a big idea, quietly. Some things in the world are only ON or OFF — a switch, a door. Others have a whole range in between — a dimmer, a tap, a volume knob. Your robot can do both. You'll come back to this in Lesson 19.

🔧 It's not working — let's fix it

Always check these four first:

  1. Is the USB-C cable pushed all the way in? Both ends — the board and the computer. That cable is what powers your robot right now, so a loose cable means a dead robot.
  2. Did you press Connect? Top left of Mobot IDE. It must say 🟢 Connected, not ⚪ Disconnected.
  3. Is the right product chosen? In the PRODUCT panel on the left, Robotics must be the one lit up.
  4. Did you click Send to Device? And wait for it to finish.

And for this lesson:

What's happeningWhyWhat to do
No welcome sound when I plug inThe board isn't getting powerTry the other end of the cable, or a different USB socket on the computer
My computer can't find the boardThe cable might be a charging-only cableUse the cable that came in the box. Some phone cables carry power but no data
Send to Device is pale and won't clickYou haven't pressed Connect yetPress Connect at the top left. It must turn green
The flashing stopped halfwayThe cable moved during the flashUnplug, plug back in, and flash again. Nothing is broken
Nothing happens when I send the codeThe Mobot Start block is missingEvery program must begin with it. Check it's at the very top
The LED number doesn't change anythingBoth blocks are set to the same LEDOne should say 1, the other 2
😌 Everybody gets stuck on lesson one. It's the hardest lesson in the whole course, because nothing is familiar yet. Lesson 2 is easier. Promise.

🌱 Make it easier

Just get one light on. That's a complete success for today. Two lights, winking and dimming can all wait.

🔥 Make it harder

Challenge 1 — The fade. Using only Set LED [1] to ( ) %, build a stack that goes 10, 30, 50, 70, 90. What happens when you send it? (Something surprising — you'll understand exactly why in Lesson 2.)

Challenge 2 — Explore the drawers. Open every category and find one block that sounds interesting. Write its name down. See if you can guess which lesson you'll meet it in.

Challenge 3 — Sort a different robot. Think of a machine at home — a washing machine, a lift, an automatic door. Can you name its control unit, its sensors, its actuators and its energy?

🏅 Badge & what's next

You earned: 🔌 Robot Awakener

☑ Learned the four parts every robot has ☑ Sorted your own kit into the four groups ☑ Flashed the firmware at flash.mobot.dz ☑ Opened Mobot IDE and chose Robotics ☑ Connected the board to the IDE ☑ Wrote a program and made a light turn on ☑ Discovered the brightness block

👉 Next up

Your robot can turn a light on. But one light is a bit boring.

Next lesson you'll make it blink like a firefly, flash like a police car, and play a tune — and you'll learn the single most useful block in all of programming.

Lesson 2 · The Light and Sound Show 💡🎵

📝 Quick quiz

Get every answer right to open the next lesson. You can try as many times as you like.

1. What are the four parts every robot has?
Think first, then look:
2. What is the name of your control unit?
3. Which group do the LEDs and the buzzer belong to?
4. Where do you flash the firmware?
Think first, then look:
5. Which product must you choose in Mobot IDE?
6. Set LED 1 to 50 % — what does the 50 mean?
7. You need batteries for this lesson.

Your progress is kept in this browser. Sign in to find it everywhere.