During this Lab my partner Ellie and I connected to a TELLO Drone and did a test fly. We created a simple code, but the Drone did not do what we wanted because of space limitations. Below is a ScreenCast of the code we test flew as well as a camera angle from the TELLO Drone's point of view.
5.2.e Communicate with students, parents and leaders about the impacts of computing in our world and across diverse roles and professional life, and why these skills are essential for all students.
During the activity, students and their guardians will gain information in how computing can be used in the real world.
5.5.c Use a variety of instructional approaches to help students frame problems in ways that can be represented as computational steps or algorithms to be performed by a computer.
The WeDo LEGO activity will be different instruction from the DroneBlock TELLO Lab. However, once we are working through our activity, Ellie and I may need to make adjustments to help students and/or parents understand in a different way.
Steps
Step 1: Connect to Drone and TELLO.
Step 2: Establish flying area and boundaries for students and/or guardians.
Step 3: Discuss motions and actions of code using print out of code blocks.
Step 4: Fly our demonstration code.
Step 5: Allow students to add on to existing code.
Step 6: Show what drones can do through video.
Conclusion: Discussion with students about if they have seen drones anywhere else and what they enjoyed.
Reflection (after METRO)
TELLO Drone
The METRO drone experience was one of trial, error, problem-solving, and fun. In the beginning, our wifi was not connecting to the drone we had, but to drones that were close by. After some troubleshooting, we were finally able to connect to our drone and show our two students the lesson. While I was trying to get connected, Ellie was demonstrating how to build code. We were finally able to connect to our drone and were able to show the students our code that we had already created. After our example, the girls were able to create their own code. Throughout this activity, both girls were intrigued, asked questions, and seemed to be having fun. Below is the code that the girls created which included loops and flips.
The WeDo activity was more of an issue than the drones in our case. Our robotic hand was having a sensor issue which resulted in the robotic hand failing to lift and move objects. Ellie and I had to pull up our ScreenCast that showed the girls what was supposed to happen. We still explained the process, code, and reasoning for our WeDo activity. But because it was so brief, we had the girls join another WeDo group and participate in their activity. This allowed the girls to still have a chance to play with the LEGO codes and get hands on experience. Below is a picture of the girls watching the ScreenCast since our code was not working in person.