Day 03 Β· Report

πŸ‡ΈπŸ‡¬ Singapore Trip Report β€” Day 3

  • 08 September 2026
  • Singapore
  • 6 min read
  • 22 photos
Cover photo of Day 3: πŸ‡ΈπŸ‡¬ Singapore Trip Report β€” Day 3

Timeline Β· 7 stops

  1. Off to ITE College East
  2. Welcome to ITE College East
  3. Meet the mBot
  4. Line Following Challenge
  5. Obstacle Avoidance
  6. Combined Track Challenge
  7. Wrap-up & Reflection

First actual training day at ITE College East. Today was all about the mBot β€” a small educational robot we programmed with block-based code (mBlock). Felt like being back in primary school but way cooler because there's a real robot rolling around in front of you.

08:00 · Singapore Time🚌 Off to ITE College East

Quick breakfast at the hotel, formal outfit on, out the door. The chartered coach picked us up right outside the hotel and drove straight to campus β€” about 45 minutes heading east through the city. Hot already at 8 AM, but the bus AC was cranked all the way up.

πŸ’‘ What I learned

  • Chartered coach is the move for a big group β€” door to door, no line changes, and the whole team stays together in one place.
  • Above-ground travel is way more scenic than going underground β€” you actually see the city change as you head east: downtown skyline β†’ HDB flats β†’ expressways β†’ educational zones.
  • Singapore drives on the left (same as Thailand and the UK). Roads are wide and clean, and even in morning traffic there's no honking. Everyone just… waits.

09:00 · Singapore Time🏫 Welcome to ITE College East

Arrived at the campus. It's huge β€” like a small town. Modern buildings, glass everywhere, clean layout, colour-coded sections. Got name badges, signed in, and sat through the welcome briefing where instructors laid out the week's programme: AI Essentials, Prompt Engineering, Drone Programming, and AI Robotics. Today's block: mBot robotics.

πŸ’‘ What I learned

  • ITE = Institute of Technical Education. It's Singapore's main technical education system β€” similar in spirit to our technical college back home but much larger.
  • ITE College East is one of three ITE colleges in Singapore, each with different specialisations.
  • The programme is run under an OVEC ↔ ITE partnership, which is why the schedule mixes Thai and Singapore teams.

09:30 Β· Singapore TimeπŸ€– Meet the mBot

Everyone got their own mBot β€” a small blue two-wheeled robot with a big open circuit board on top. Instructor walked us through the parts: two DC motors, a line-follower sensor underneath, an ultrasonic distance sensor in the front (looks like eyes), a buzzer, RGB LEDs, and the mCore mainboard running an Arduino-based chip.

Then we opened mBlock 5 on the laptops. Block-based like Scratch β€” you drag and snap blocks instead of typing code. First warm-up: make the mBot go forward, stop, back up, turn left, turn right. Basic, but good for getting the muscle memory.

πŸ’‘ What I learned

  • mBot is made by Makeblock β€” think of it as an Arduino for students.
  • mBlock looks like Scratch but generates real code underneath β€” you can switch to Arduino C++ view and see what your blocks actually compile to.
  • Block coding hides syntax, not logic. You still deal with loops, conditionals, and variables β€” you just don't lose an hour to a missing semicolon.

10:30 · Singapore Time➑️ Line Following Challenge

Now the fun part. The line-follower sensor underneath the mBot has 2 IR(infrared) that read the surface. Black absorbs infrared, white reflects it β€” so the sensor can tell if it's over black tape or white paper.

The logic:

  • Both sensors on black β†’ keep going
  • Left sensor sees black β†’ turn left
  • Right sensor sees black β†’ turn right
  • Both sensors on white β†’ reverse back

Built this with block code and tested on a taped black-line track. First run: my mBot immediately spun in circles. Debug time. Turned out my left and right motor blocks were swapped. Fixed it, ran again, and it followed the whole track. Small win, felt huge.

πŸ’‘ What I learned

  • IR sensors shine infrared light and measure how much bounces back. Cheap, fast, and accurate for line following on plain surfaces.
  • If the robot behaves opposite to what you expect, it's usually a wiring or motor-direction issue, not a logic bug.
  • Speed matters. Too fast and the sensor can't react in time. Too slow is boring. Finding the sweet spot is half the game.

13:30 · Singapore Time🚧 Obstacle Avoidance

After lunch, second mission: make the mBot avoid obstacles. The ultrasonic sensor in front sends out sound pulses and measures how long they take to bounce back β€” which gives you distance in centimetres.

The logic:

  • If distance > 20 cm β†’ go forward
  • If distance < 20 cm β†’ stop, back up, turn, then continue

Sounds simple. In practice, the robot kept turning into the obstacle because my turn timer was too short. Bumped it from 500 ms to 800 ms and it worked. Also learned that shiny or angled surfaces confuse the ultrasonic sensor because the sound bounces off sideways instead of coming back to the receiver.

πŸ’‘ What I learned

  • Ultrasonic sensors use sound at ~40 kHz β€” above human hearing. Same trick as bat echolocation.
  • The formula: distance = (speed of sound Γ— time) / 2. Divided by 2 because the sound goes there and back.
  • Every sensor has blind spots. Ultrasonic can't detect very close (< 2 cm) or angled objects well β€” real robots combine ultrasonic, LiDAR, IR, and cameras for exactly this reason.

15:00 · Singapore Time🏁 Combined Track Challenge

Final boss: follow the black line AND avoid obstacles placed on the track. This means the code has to check both sensors every loop and decide priorities. My logic:

  1. Check ultrasonic first β€” if obstacle close, stop and go around it
  2. Otherwise, check line sensor and follow the line
  3. Loop forever

My mBot mostly made it. Missed one obstacle and clipped a corner, but crossed the line. Some teams got a full clean run. Vibe was great β€” everyone helping each other debug, instructors walking around answering questions.

πŸ’‘ What I learned

  • Real robots do this every day. Line following = staying on a path, obstacle avoidance = reacting to the world. Combined = the basics of autonomous navigation.
  • Priority matters in code. If you check the line before the obstacle, the robot might drive into a wall while trying to stay on line.
  • Iterating fast beats writing perfect code. Test, watch it fail, adjust, test again. That loop is the actual skill.

16:30 Β· Singapore TimeπŸ““ Wrap-up & Reflection

Instructors ran through the day, showed off some of the best runs, and reminded us tomorrow's session is AI Essentials β€” the module that leads to the Google AI Essentials certification. Packed up laptops, formal outfit still holding up somehow, and boarded the coach back to the hotel.

πŸ’‘ What I learned

  • mBot is a gateway drug to real robotics. The same concepts scale up to industrial robots, self-driving cars, and drones.
  • Block coding removes syntax pain but doesn't skip the thinking. Loops, conditionals, priorities, timing β€” all still there.
  • Hands-on training beats theory β€” one robot debugging session teaches more than a week of slides.

Wrap-up

Actually built something today that moved, sensed, and reacted. Different energy from just watching lectures or reading slides. Also confirmed I like the hardware + code combo β€” you can literally see your bug when the robot drives into a wall, which makes debugging weirdly satisfying. Tomorrow: AI Essentials. Bringing the same energy. Goodnight.