Robo Travels to Toytown
Activity Stages: I.
Lead-in: 4 steps - 5 - 7 min
II.
Guided Activity: 6 steps - 15-20 min
III.
Independent Activity: 15 - 20 min
IV.
Reflection and Feedback: 5-7 min
V.
Clean Up
Recall ● Which Modules did we already use for all our projects? ● Which Actions did we program? ● What two types of a code did we program?
Lead-in: activate and motivate students asking about their previous knowledge and personal experiences. 4 steps - 5 - 7 min 1. Recall: ● Which Modules did we already use for our projects and why? (We used: 1) The Main Block because we need it in every project in order to make all the other Modules work; 2) The (RGB) Light because we wanted to program light signals; 3) The (DC) Motors to program Robo to drive around; 4) The Big wheels, Small wheel and Connectors to build a Robo-vehicle) ● Which actions did we program? (We programmed Sounds, Visuals - Constant Light and Blink actions, Movement - Drive and Turn actions) ● What type of a code did we program? (We programed two different types of code - Sequential code and Parallel Execution.)
Keywords ● Action ● Sequential code ● State ● Transition ● Parallel execution
Lead in - 5-7 min 2. Recall the keywords: ●
Action - it's an icon which indicates a command for Robo to perform.
●
Sequential logic - the type of code where one Action leads to only one other Action until a program is complete.
●
State - set of Actions (in one bubble) which can consist of one or more Actions performed parallel - at the same time /simultaneously.
●
Parallel execution - the type of code where several Actions are performed or executed at the same time within a State.
●
Transition - the act of changing from one State to another ( = the act of happening).
Sequential code ⇔ Parallel Execution
➔ How are they different, and how did this influence Robo’s performance?
Lead in - 5-7 min 2. Recall the terminology: Compare Sequential Logic to Parallel Execution ●
How are they different, and how did this influence Robo’s performance?
(In Sequential code one Action leads to only one other Action, so they are performed sequentially, one after another. In Parallel Execution several Actions are executed simultaneously, so Robo performs some commands at the same time.)
Robo’s Story Robo is invited to visit Toytown! To get there, Robo has to travel a long way, avoiding obstacles and making tricky turns. Are we ready for some serious programming to help Robo?
Lead in - 5-7 min 3. Tell the Robo’s Story: Robo is invited to visit Toytown! To get there, Robo has to travel a long way, avoiding obstacles and making tricky turns. Are we ready for some serious programming to help Robo? 4. Lesson’s Goal: To help Robo to get to Toytown, we will program a Robo-vehicle to avoid obstacles and cope with some challenges.
Robo travels to Toytown! Plan: 1) Which Modules will we need? 2) Build Robo-traveller and create Toytown 3) Program Robo-traveller
Guided Activity: Plan => Carry Out => Sum Up - 15-20 min Plan the activity together with your students: ●
What are the steps for our project?
Discuss all the answers and formulate the plan: ●
Find the Modules needed for a project
●
Build Robo-traveller and create Toytown
●
Program Robo-traveller
1) Which Modules will we need?
Guided Activity - 15-20 min Carry Out: Step 1: Modules for the project. â—? â—?
Hand out the Robo Wunderkind boxes.
Open the boxes and discuss: Which Modules will we need to add to the Main Block to build the Robo-traveller? Why? (We will need: The Main Block in order to make all Modules work; 2 (DC) Motors in order to make Robo-car drive; 2 Big Wheels, 2 Connectors and a small wheel to build the stable Robo-vehicle; (RGB) Light to light up the road to Toytown)
2) Build a Robo - traveller
Guided Activity - 15-20 min Carry Out: Step 2: Build a Robo-traveller â—?
Attach DC Motors to the Main Block and recall their mechanical details: the rotating part without Pogo-Pins, compare it to the Connector; DC Motors should be attached with the help of the Connectors in order to work properly. The rotating part should be attached to the Big Wheels.
â—?
Add the (RGB) Light to the build.
2) Create Toytown
Guided Activity - 15-20 min Carry Out: Step 2: Create Toytown: Use different materials to build the road to Toytown with various obstacles - trees, rocks, turns.
3) New project in Robo Code App
Guided Activity - 15-20 min Carry Out: Step 3: Program: Let students do these steps by themselves, consolidating learned skills. ●
Open the Robo Code App and connect the Main Block to the tablet;
●
Check My Robo Menu to see if Robo’s battery level is high enough to program it;
●
Create a new project and get ready for programming.
Challenge 1: Drive and Turn actions 1) Robo avoids obstacles to get to Toytown ➔ Sequential code
Guided Activity - 15-20 min Carry Out: Step 3: Program the Robo-traveller. Set challenges for students and let them explore the Robo Code programming language on their own; guide them by questions if needed. Challenge #1: Program the Drive and Turn actions as a Sequential code. ●
Create an environment: obstacles such as trees, rocks or road’s turns.
●
Program Movement - Drive and Turn actions to avoid certain obstacles and get to Toytown.
●
Pay attention that it is a Sequential code because the Actions are performed one after another; they can not be added into one State because they are the same type - Movement.
●
Discuss different settings for the Drive and Turn actions and how they affect Robo’s movement.
●
Program 2-3 different paths for Robo increasing the complexity.
Note: It’s best to start with simple concrete tasks and increase their complexity as the students become more proficient. In this case, students will create a simple code and improve it step by step. For some students, it could be easier to start with the code that imitates real Robo movements or even try all the movements by themselves before coding.
Challenge 1: Drive and Turn actions
Guided Activity - 15-20 min Carry Out Challenge #1 - Check ●
Show an example of a code for the challenge, if needed. But let students create their own codes for Robo’s different paths.
●
Pay attention that it is a Sequential code because the Actions are performed one after another; they can not be added into one State because they are the same type - Movement.
●
Discuss different settings for the Drive and Turn actions and how they affect Robo’s movement.
●
Program 2-3 different paths for Robo, increasing the complexity.
Note: It’s best to start with simple concrete tasks and increase their complexity as the students become more proficient. In this case, students will create a simple code and improve it step by step. For some students, it could be easier to start with the code that imitates real Robo movements or even try all the movements by themselves before coding.
Challenge 2: Sounds and Visuals 1) Robo makes a sound after each Drive action 2) Robo lights up the road after each Turn action ➔ Sequential code
Guided Activity - 15-20 min Carry Out Challenge #2: Modify the Sequential code - add Sounds and Visuals ●
Ask students to modify a code by adding Sounds and Visuals in a certain order:
1)
Robo makes a sound after each Drive action
2)
Robo lights up the road after each Turn action
●
Pay attention that it should be a Sequential code - the Actions are performed one after another
Challenge 2: Sounds and Visuals
Guided Activity - 15-20 min Carry Out Challenge #2 - Check ●
Show an example of a code for the challenge but let students to create their own codes for different Robo’s paths.
●
Discuss different settings for added Sounds and Visuals and how their settings, especially time, affect Robo’s performance.
(Each Action has a certain length - how long Robo is performing it. Note: This question prepares students to a new term coming in the next slides - Lifespan.)
Challenge 3: State 1) Robo makes a sound each time it performs Drive action - parallel ➔ Parallel Execution
Guided Activity - 15-20 min Carry Out Challenge #3: Program a State. ●
Ask students to modify their codes to form a State: Robo makes a sound each time it performs Drive action - simultaneously or parallel
●
Pay attention that it should be a Parallel Execution - the Actions are performed at the same time - parallel.
Challenge 3: State Lifespan
Guided Activity - 15-20 min Carry Out Challenge #3: Program a State ●
Show an example of a code and check the answers
●
Discuss the settings for each Action in the State - how long is a sound, how long does Robo drive for;
●
Ask: When does the Transition to the next Action take place?
(Each Action, Sound and Movement, has a certain length - how long Robo is performing it. The Transition takes place when both Actions in one State are performed by Robo.) ●
Introduce the term - Lifespan - length of time for which an Action is performed / executed by Robo.
Challenge 4: State 2) Robo lights up the road each time it makes a Turn action - parallel ➔ Parallel Execution
Guided Activity - 15-20 min Carry Out Challenge #4: Program a State ●
Ask students to modify their codes to form a more States: Robo lights up the road each time it makes a Turn action - simultaneously or parallel
●
Pay attention that it should be a Parallel Execution - the Actions are performed at the same time - parallel
Challenge 4: State Lifespan
Guided Activity - 15-20 min Carry Out Challenge #4: Program a State ●
Show an example of a code and check the answers
●
Discuss the Lifespan for each Action in the State; Ask: What is Action’s Lifespan? Who can we find out the Action’s lifespan? What does it affects?
(Lifespan is a length of time for which an Action is performed / executed by Robo. We can open the setting and see the time settings for the Visuals. The Lifespan affects when the Transition to the next State happens - the Transition happens when all the Actions in one State are performed until the end.)
Challenge 5: Different States ➔ Parallel Execution 1) 2 different Actions in one State 2) 3 different Actions in one State 3) 1 Action - Is it a State?
Guided Activity - 15-20 min Carry Out Challenge #5: Play around ●
Ask students to program different States and Connections between them.
●
Share codes with each other and discuss:
1)
2 different Actions in one State: Which types of Actions can be in one State? What are their Lifespan settings?
2)
3 different Actions in one State: Which types of Actions can be in one State? What are their Lifespan settings?
3)
1 Action - Is it a State?
(Yes, State can consist of only one Action)
Sum Up ● Sequential code ⇔ Parallel Execution ● How can different Actions - Sounds, Visuals and Movement help Robo to travel to Toytown?
Guided Activity - 15-20 min Sum up new information before the independent activity. ●
Analyze the difference between Sequential code and Parallel Execution and how it influenced Robo’s performance.
●
Discuss how all these Actions help Robo to travel to Toytown.
Build and program YOUR Robo!
Independent Activity: 15 - 20 min Students work in small groups; they can cooperate to make the common project with two or more robots. Teachers observe or help students if needed. The concrete tasks for the own project: ●
Build your Robo-traveller using all the known Modules;
●
Create an environment - a road to your Toytown with various challenges;
●
Program your Robo to solve these challenges and get to Toytown.
Additional: Competition. Students can team up to create different challenges for each other. Each team has to create an obstacle course for the other teams; the team that solves all the challenges using the least attempts wins.
Check for understanding ➔
Find a code with a mistake.
Reflection and Feedback - 5-7 min 1) Find the code with a mistake. Explain the mistake: ●
There is a mistake in the second code: The second Connection is drawn in the wrong direction, so the Transition won’t happen.
Check for understanding ➔
Find 1 mistake in each code.
Reflection and Feedback - 5-7 min 2) Find 1 mistake in each code. 1.
Mistake: There are TWO Connections going from the second State, so Robo will automatically choose only one and the other part of the code won’t be performed.
2.
Mistake: There are TWO Codes which are not connected to each other; since the Start Point is attached to the State in one of them, the second code won’t be performed by Robo.
Check for understanding âž”
Which code will last longer? Why?
Reflection and Feedback - 5-7 min 3) Which code will last longer? Why? â—?
The first code will last longer because the Lifespan of the Blink action is longer 10 times, so it takes more time for Robo to perform it.
Check for understanding âž”
Which code will last longer? Why?
Reflection and Feedback - 5-7 min 4) Which code will last longer? Why? â—?
The second code will last longer because the Lifespan of each the Drive action is longer - Robo drives 60 each time, so it takes more time for Robo to perform the code.
Reflection & Feedback ● Today I have learned… ● The
tasks
were…
easy
or
complex?
Interesting or boring? ● Which part of the lesson was the most interesting? Why?
Reflection and Feedback - 5-7 min Ask students to make a short reflection on what they have learned today. Receive feedback: Were the tasks easy or complex? Interesting or boring? Which part of the lesson was the most interesting? Why?
Clean Up
Clean up: Teach students to take care of the devices they use - RW Modules and the tablets.
Thank you!