Starting with the simplest coding language, color! My kindergarten students learn that robots require instructions, which is called coding. They discover that when the robot "sees" different colors, it gives the robot instructions to do different things. I let them break the code and tell me what each color commands the robots to do. I rarely give my kinders structured tasks with these robots. It's more fun for them to just make coding discoveries of their own.
As the train drives over a colored piece, it will perform different actions like creating sounds, turning on lights, or making directional changes.
When you place the car on a green square it will start to drive. As it drives over different colors it will perform different turns or moves.
This task can be somewhat challenging, as students need to create a maze on the fly based on the instructions provided by the robot's color.
My first graders begin with directional arrow coding using code.org to learn algorithms.
We then practice unplugged coding with Code and Go Mouse cards. They find it challenging to grasp that a turn arrow only changes direction without moving the robot forward in the maze.
When students begin using the robots, I provide them with a mat and algorithm cards. After they collaborate to create an algorithm, they can program their robot and put it to the test.
Building an algorithm before programming their mouse encourages students to focus more on the algorithm itself, rather than relying solely on trial and error without the cards.
This project combined robotics and engineering design. Students collaborated to build a mousetrap over the course of several class periods. Although there were criteria, I didn't stress about how well the traps met the criteria because, in first grade, it's all about learning to work together!
After the traps were built, they set up a maze, coded the robot through the maze, and captured the mouse with their team-designed trap.
You can read more about this project on my First Grade Page.
The kiddos love Botely because it has an addition of a remote control, attachable arms, and other fun things they can put along their coding maze.
Beware, there are some downsides to having more than one Botley in a classroom. If two groups are working too closely to one another one remote can program both Botleys at the same time.
For their first challenge, second graders created a Lego transport system using Dash's Lego attachments. They had to be sure it wouldn't fall off or break when Dash was coded to drive around. Students learned that coding Dash with his animation blocks created quite a challenging task.
Later in the year, 2nd graders learned more advanced coding skills, like coding the sensors on Dash to detect objects around them and react.
Groups were tasked with programming their robot to continuously drive forward (utilizing a repeat block) while avoiding collisions with other Dash robots or objects. To achieve success, students needed to ensure their algorithm included instructions for how Dash should respond when it detected nearby objects.
Third graders learned how to code Dash's launcher attachment.
They used Dash to investigate force and motion. I utilized the ping pong balls that came with Dash and I filled some of my own with different amounts of sand. They weighed each ball and measured the distance Dash was able to launch it using different amounts of force.
Teams designed and built a basketball goal and then had to find the right distance and force to launch the ball at to make a goal.
Then, students played a game of Dash-ketball!
Fourth graders learned about energy transfers in collisions then they designed and built a bumper for Sphero. This was tricky because of the way Sphero moves. The bumper could not be connected to the robot or it wouldn't move. It also couldn't be too heavy. We had a lot of great opportunities for problem-solving and redesign iterations.
Sphero has the capability to code an output when a certain level of force is detected, but unfortunately, it rarely worked during this activity. Some teams coded their Spheros to light up different colors, make sounds, or spin around upon impact. It would have been REALLY cool, if only it worked ...
Fifth grade teams built Sphero obstacle courses. Their course must include at least one ramp that Sphero had to travel up, one freefall drop, and one object for Sphero to knock down.
Like with my fourth graders, we utilized Sphero's sensors and coded it to react in different ways when it detected these events. And, again like fourth grade, they didn't work very often. But they sure had a ton of fun and worked on their creativity skills!
I am just starting my journey in the Micro:bit world, but my kids and I have been thoroughly enjoying discovering its possibilities!
There are two challenge sets available: one for newbies and one for more proficient coders.
STEM From The Heart
Copyright © 2025 Stem From The Heart - All Rights Reserved.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.