Tag Archives: Robot

ISTE 2011: LEGO Workshops (Post 2 of 2)

26 Jul

ISTE 2011 Post #2: Notes: Working my way through my conference notes. Trying to get them out of the brain and onto the page. 

LEGO Sponsored Workshop: Revolution through Serious Play and WeDo 

I have only one big gripe as a newbie at ISTE this year; the online program was a pain in the neck to navigate. Searching by keywords brought up a few workshops and presentations, but completely ignored others. “Sponsor Activities” weren’t listed under “Presentations by Time” and… well… I won’t waste your time venting about the schedule. The short of it is that I paid for a half-day NXT workshop, when I could have attended a free sponsored workshop on the same topic by the same presenter, and I almost missed out on the opportunity to attend this LEGO WeDo workshop that I completely lucked into when I happened to walk by and I recognized the familiar kits.

Part 1: Serious Play

I slipped into the room a few minutes late and took an empty seat. We sat in pairs at workstations, each containing a WeDo Kit and a laptop. While I was interested in hearing what the presenter, Kathy Holberg, would share about WeDo, I was also interested in:

1) Connecting with other educators who are using WeDo in the K-6 classroom

2) Learning about “LEGO Serious Play“, something I had read about, but had never seen.

Kathy started by giving us this brief overview of LEGO Serious Play (LSP). LSP is used as a training tool or training methodology in a variety of industries and businesses, as well as in schools, for purposes such as team building, fostering out-of-box thinking, encouraging the expression of feelings, ice-breaking activities, making connections, aiding awareness of others’ feelings, and developing listening skills. It is also used to improve communication skills, logical thinking, and creative thinking. It is a vehicle for exploring metaphoric language and thoughts.

After her overview, Kathy gave each participant a bag of LEGO Serious Play parts and this prompt:

Construct a model that represents a hands-on STEM lesson in your classroom. Try to use all the pieces.

I looked at the meager pile of random pieces lying on the table in front of me, and thought “Really? Do that? With these?” I looked over at my neighbor; she appeared equally hesitant. Regardless, we set to work clicking and snapping pieces together.  What I found interesting, is that due to the limited number of pieces to choose from, I was quickly forced to let go of any desire to create a specific or concrete representation of an object or idea and to instead embrace my creativity and explore which pieces I could use to represent an object or symbolize an idea. It got easier and easier.

After five minutes, Kathy stopped us and asked us to turn to our neighbor to describe our models regardless of where we were in the building stage. This was my model…

…and here is my partner, LeRhonda’s (@lgreats) model.

I love that even with so few pieces to work with, we were both still able to create and share something unique regarding our ideas on STEM lessons in the classroom.

According to Kathy, a teacher’s, or facilitator’s, main role during a Serious Play build, is to ask questions and move around the room without introducing any type of bias into the building effort. For example, a facilitator should not say “Good job, Tom”, because it could create the impression that there is a “good way” or a “bad way” to complete the activity. The goal is to have everyone be comfortable using the LEGO blocks as a vehicle to explore or express an idea, a thought, or a feeling without worrying about the consequences of not doing it well, or right, or as good as the next guy.

Kathy made sure to clarify that the LEGO Serious Play methodology required specific training in regards to how to“properly” write a challenge question, set the stage for using LSP (LEGO Serious Play), work with students when they are telling their stories, and  connect the activities to student learning, but I would venture to say that any teacher with a bunch of LEGO bricks and a good grasp on inquiry-based, constructivist instruction could engage a classroom in some “LEGO Serious Play”. 

That’s not to say that teachers wouldn’t benefit from a formal LSP training or from having access to specific LSP kits. It’s more to say that the use of LEGOs or other manipulatives to explore thoughts, ideas, and feelings is something that could be done with little to no additional cost to a school that already has access to LEGOs, granted a teacher did a little research to understand the core concepts involved in the LSP model.

Part 2: LEGO WeDo

Kathy next introduced us to the new LEGO Education WeDo Robotics Extension Activity Bundle. Basically, LEGO took the same basic 12 builds for the WeDo Kits and then created a new curriculum set to connect the builds with subject matter from PE, language arts, and social studies. I’m not too interested in purchasing this extension pack. I tend to naturally make cross-curricular connections when using the kits. For teachers who prefer to teach from a written curriculum, or for new teachers who may benefit from the structure of a pre-designed curriculum, it will be great. For those of us who nerd out on the creative aspects of unit planning and lesson writing, it may be less appealing.

The rest of the workshop gave teachers time to explore the kits and build a model.

Here are few WeDo tips Kathy shared: 

1.Use “fun foam” to cover the WeDo kit lids.  Kathy likes using fun foam on the lids so that students don’t get distracted by the images on the lids, so they can use the lid as a building mat since the LEGOs don’t bounce off the fun foam, and finally so the lid can be used as a tray to display the students’ builds.

2. Create an “NXT” parts diagram for organization. Kathy creates a system for arranging the kits and then takes a picture for the kids to help them stay organized. (I thought about doing this when I initially started to work with the kits, but decided not to for the sake of time. I think it’s a great idea for teachers who are uber-organizers.) 

My favorite tip… Use “Alt-tab” to quickly see the desktop when working in WeDo. (If you are familiar with the WeDo software interface then you know it defaults to a full-screen view. This tip will come in handy for sure.)

A Fun Fact: Black axels are even. Grey axels are odd. (I never noticed that.)

During the workshop, Kathy was kind enough to give me the opportunity to plug my blog and to invite teachers using the WeDo kits  to send ideas, lessons, or reflections that I could include in a post or put up as a “guest blogger post”.  Although a few people expressed interested in sharing or posting, I haven’t heard from anyone yet. The offer stands! If you want to get something out there about elementary robotics, but don’t want to commit to your own blog… just let me know.

By the way… we got to keep our LSP kits and we got these sweet keychains. Pretty cool, huh? 😉

ISTE 2011 LEGO Workshops (Post 1 of 2)

15 Jul

I’ve been wanting to post my notes from the LEGO workshops I attended at ISTE 2011, but I’ve been procrastinating. I need to post them so that I can make room in my brain for some new ideas. So here goes!

ISTE 2011 Post #1: Notes from Sunday June 26, 2011…

Introduction to Classroom Robotics: Computer Science in Motion!

The workshop room was full of people seated behind workstations. Each workstation had a LEGO NXT kit, a pre-built Domabot with a few sensors attached, and a computer with NXT-G software.

Our presenter was Christopher Michaud, a Music Teacher at  Nebo Elementary School in Dallas, Georgia, and a graduate from Temple University’s Music program. (Woot! Philadelphia in the house.) He taught himself to program, and now in addition to teaching music, he teaches a computer science curriculum for grades 3-5. He focuses mainly on Open Office/ Alice/ Python/ and Robotics and has a terrific website with loads of great resources. (I couldn’t help but secretly love the fact that his background is in music, since my undergrad was a music technology degree. music + math + curiosity = awesome life!)

Chris started the workshop with a Powerpoint presentation in which he provided us with a brief overview of his goals for the workshop: Build, Program, Experiment, Apply, and listed a few of his reasons for teaching robotics at the elementary level, including my favorite, “Robots are cool.”  (He has headier reasons listed in the presentation that will make for stronger plugs when trying to sell a robotics program to your administration, so  I encourage you to check it out.)

The remainder of the Powerpoint presentation was a bit of NXT Robotics 101, which sensors did what and the like, and was a perfect introduction to NXT robotics.

Within just a few minutes of starting the first workshop activity, getting the domabot to drive in a square, I, and the woman next to me, realized that this was perhaps a true beginners workshop. (As in, many people in the room had never even touched an NXT kit before. I guess it’s time for me to bump my status up to advanced beginner.) My partner was open to going off script to explore some of the features of NXT-G that we were curious about and so we started messing about, clicking on buttons and pulling down menus.

Chris came over and asked how we were doing. We confessed and told him we had gone rogue.

Lucky for us, he was not at all offended and was an excellent differentiator of instruction and he immediately found us a task that would both challenge us and highlight a few new features of the software that we were not familiar with. We worked on “Simple Pi Challenge 1” and “Simple Pi Challenge 2”,  two worksheets which not only provided us with an excellent opportunity to practice writing formulas within the NXT-G software, but which also gave us great take-away lesson to use in the classroom. It provides a perfect opportunity for students to see “Pi in action”.

Once we had worked our way through that challenge, we quickly discussed what else we’d like to get out of the remaining time.

We both admitted that we had no idea how to use… DATA WIRES.

Yep. It’s true. I’ve been avoiding them. I don’t why. I think it’s because I learn so many things just by messing around or through trial and error. But when I approached data wires in this manner… there was a whole lot of “error” at the end of every “trial”. Chris was great, and he broke datawires down for us and helped make them seem at least approachable. (I’ll try to post a simple example of the use of datawires at some point for anyone else who is hesitating on getting a handle on them. Or maybe someone has a great intro resource they could suggest…)

Here are few helpful suggestions Chris made for teachers who are about to take on robotics…

1. Start with a robot built. “Kids understand build. Programming is more difficult.” The domabot is great example of a robot you can easily have ready for students to work with.

2 .Organize the room with computers on the perimeter and workspace in the middle. Have a place  in the room where it is possible to have students with empty hands.

Here’s some new vocabulary for neophyte robot programmers:

Swing turn: 1 wheel turns 1 wheel doesn’t. (Think “pivot” on a basketball court.)

Point turn: 1 wheel turns forward, the other goes in reverse. (Think… I don’t know… any ideas?)

To be honest. That’s all I got for you. Those are my notes. I know. Not very impressive. Which might be why I was procrastinating. But at least there out of my head and on the page. 😉

Thanks Chris! I finally learned to use variables, custom blocks, data wires, and the formula review in NXT-G. It’s about time. My students better get ready… next year will be a whole new ball game!

Taking Damien Kee’s NXT “Mexican Wave Activity” for a Test Drive

16 Jun

In my last post about the Tufts LEGO Engineering Symposium, I mentioned Damien Kee‘s  presentation and included an embedded  video of his NXT “Mexican Wave” activity.

Yesterday morning, I tried the activity with a group of 21 fifth graders that had never worked with robotics before and it was a blast! It was the perfect activity for introducing the kids to the NXT robots and the NXT-G software.

We met from 9:30-12:15 and took a 15 minute snack break, so all told, we had about 2.5 hours to try to meet the following three objectives:

1) Work collaboratively in small groups to program the NXT Domabot to move from one specified location to another. Time permitting, write a program to turn the robot around and have it return to it’s starting position.

2) Gain a basic understanding of what sensors and thresholds are and find out how they apply to today’s activity.

3)Work collaboratively as a class to program all five NXT Domabots to do a wave and at least one additional choreographed movement.

Students collaborated well and worked hard and met all three objectives by lunch!

After reviewing the objectives, we warmed up with a five minute activity called “Computer Says”. (The activity is similar to Simon Says. I am the computer; students are the robots. Robots should only follow programs that start with “Computer says”) Students made three lines and faced me.

For Round 1, I said, “First we’ll learn use a motor block to run simple programs. Let’s try a few.” I then led them through a few simple commands,  “Computer says take one step forward.”  “Computer says take one step back”.

In Round 2, I said, “Next we’ll learn to use a “wait-for-sensor block and write slightly more complex programs.” I then gave a few commands like these: “Computer says wait until you hear me clap, then take one step forward. Computer says, wait until I shout loudly and then jump”

And finally for Round 3, I said, “For our third objective, we will have to collaborate to write a series of programs to get our robots to work together to create a movement wave. Let’s try to run three programs at once and see what happens. Computer says, Line 1 robots, wait until I clap then put both hands in the air and back down again. Line 2 robots, wait until I clap, then wait one second, then put both hands in the air and back down again.  Line 3 robots, wait until I clap, then wait two seconds, then then put both hands in the air and back down again.” I clapped my hands and watched as the students did a perfect mini-Mexican-wave!

The whole activity took less than 5-minutes, but it helped to build a context for what came next. Being able to refer back to the warm-up came in especially handy when we started thinking about how to program the robots to do a wave.

After our warm-up, students then learned to move their robots using a single motor block. As recommended by Damien in his presentation, I placed two lines of tape on the floor at a random distance from each other and then students worked to program their robots to start with wheels on the first line and stop with wheels on the second line. They set to work trying different motor on durations and very quickly developed an appreciation for the decimal point! If 5 rotations were too many, they tried 4, then 4.5, 4.6, 4.7…

They began to see that trial and error and persistence were important for solving this problem, and they experienced the intrinsic joy that came along with finding an exact solution to a problem.

Soon all groups had mastered the line-to-line challenge and were on to trying to figure out how to turn the robot around and bring it home. Despite my having mentioned that changing the “degree” parameter of the motor block to 180° would not turn their robot around, all the groups tried that strategy first, which led to a series of great teachable moments surrounding what “rotation” meant in the motor block. After some experimentation with the remaining parameters in the motor block, groups soon started to catch on that the steering parameter in combination with the duration setting was the ticket to that 180° turn. At least two of the five groups got the turn close to an exact 180° turn, and the remaining groups were well on their way before I cut them off and moved on to objective 2.

Once the kids had a general sense of how to move their robots and turn them, we regrouped and I introduced them to the sound sensor and to the threshold parameter.

As I usually do when explaining threshold to kids, I said, “I bet you already know what threshold means. Let me show you. Listen to my voice and when I reach your threshold between soft and loud, clap.”

I then talk very quietly and get progressively louder until they clap. I repeat and set the threshold for “really loud”. I do a few more examples of simple thresholds they understand. For example, their threshold for drinking hot liquids. I quickly made the correlation to the threshold parameter on the  sensor block. Students seemed confident they understood the wait-for-sound block and so we moved directly on to discuss how to create a wave.

To plan the wave, we created a chart on the wall that sketched what each group needed to do and then parted. We met back up about five minutes later.

On the kids’ first try, the robots took off and executed a perfect little wave. Wow! We had thirty minutes left to add a choreographed movement of our choice. We lined up 5 students to represent the five robots and planned our dance move. Groups ran off in all directions to program. Shortly after we met back up, pushed run, waited for the signal and yelled “Go” What came next was…

Terrible. Our little robots were all over the place. And so we began to learn about collaborative trouble-shooting. We came back to the line over and over again, each time it got better, but something wouldn’t be quite right.

With one minute left and groups scrambling to download their last attempts, I called them back to the line. The room was quiet. Thumbs went up to signal all programs were running. Their classroom teacher quietly counted “1-2-3” and then the kids yelled “Go!” one last time. You can see for yourself the fruits of their efforts in our video. The simple sequence of movements won’t blow your mind… but the kids’ cheers and screams of enthusiasm may brighten your day. 

Crime fighting robots?

18 Feb

Today, we left the LEGO WeDo kits in the closet and turned to a few new tools to help us think about two of the essential questions we are exploring in our first grade pilot robotics unit.

“How can robots help solve problems?”

“What robot could you invent to help solve a problem?”

To kick off the lesson, we read “If I Were an Engineer”, a compact, colorful rhyming book that introduces engineering to kids aged 5-8. It was my first time using the book in the classroom. The students loved guessing the end rhyme words as in… “I’d help sick people young and old- I’d even cure the common?” “COLD!” It was a great introduction to the day’s lesson.

After reading the book, I reminded students that we were a group of “problem-solving engineers” and informed them that today we would be “imagining solutions” just like engineers.

Next, we watched two YouTube videos on ReWalk technology and students identified the “problem” in the video. “The woman can’t walk.” They also answered the question, “How do her robotic legs make her life better or solve the problem?”

We reviewed… Engineers solve problems. Sometimes they create robots to solve problems. We just watched a video. The video showed us an example of a woman who had a problem and an example of how engineers designed a “robot” to help solve her problem. We are engineers. Let’s think of some problems to solve.

We brainstormed and charted  “Problems in the World”.  Here’s a tip. Don’t be fooled by the pint-sized stature of a first grader. If you ask one a question, he or she will give you an honest answer. Just take a look at a few of the “Problems in the World” my group identified.

“Guns and cursing on my street.” “Hair all over the house.” “Smoking in the elevator.””Fighting and Arguing.””Baby sister crying at 12 midnight when I’m trying to go to sleep.””Traffic.””Car accidents.”

And the problem that really caused me to reflect and still hurts my heart to think about…

“My father plays video games all the time and doesn’t pay attention to me.”

“Yep, that’s a problem.” I said.

Now that we had identified some of the world’s problems, we were ready to create some robots. Students used ABCya! Make a Robot to design their very own problem-solving robot! Would you like to meet one?

Meet Ken…

**If you are looking for a fun activity to do with your first or second grade class for National Robotics Week in April, you may enjoy this one.

 

Materials Needed: EGFI “If I Were an Engineer Book”, a video that shows a problem, a place to record a brainstorm session, and computers with an Internet connection.

On a 1-10 tech difficulty scale… I’d give this a 3 because you have to load a video to play and help students navigate to a website and print. (You could also save the images digitally and go-paper free. I printed due to time constraints caused by our unplanned fire-drill.) If you’d like a Lesson Plan copy, just let me know!

Five First Grade Activities for Robotics Instruction!

14 Jan

We had our second robotics lesson down in the first grade today, and before too much time passes I want to share a few activities from weeks one and two.  Any of these activities could be easily modified to be more age appropriate or to be used for different subject matter.

Activity 1: “Computer Says”

To help first graders make the connection that robots must receive commands in order to operate, I borrowed an idea from members of the Robotics Outreach at Lincoln Laboratory (ROLL) who had visited a first grade classroom to introduce students to the concepts of programming and robotics. (Read about their visit!)

The activity is simple… replace “Simon Says” with “Computer Says”.

Say, “I am the computer. You are the robots. Robots can only move if they receive a command from the computer. If you move without a command, I will have to power you down.” I used it both weeks for one or two minutes. The kids love it and the idea that a command must be sent to a robot has stuck! I’m a bit of a goofball, so I like to give my commands in a robot voice.

Activity 2: Robot K-W-L in Voicethread

I love Voicethread and I love K-W-L charts, and they work beautifully together. To keep track of our learning during the unit I set up a new Voicethread account and created an identity for each of the first grade students using the image of a cartoon or comic robot for their avatars. These avatars were also printed under their name on each of their name tags.

The layout of the Voicethread is super basic. It has three slides in total. Each one features an image of a robot. Slide 1 is titled “What do we know about robots?”, Slide 2 is titled, “What do we want to learn about robots?” and Slide 3 is titled, “What have we learned about robots?”

When a child has something to add, they come up and find their robot identity, they share their idea and I take dictation and type their ideas. Eventually we will move into recording their voices in place of typing comments.

You can visit our Voicethread and see what it looks like after three class periods. On day 1, we did not have Internet access, so I kept track of their ideas on the board and added them later. (I wish I could embed the thread, but WP doesn’t allow it, so you’ll need to click this link to see it.) 1649945

Activity 3: Prezi Story – Jerome’s Dirty Floors

I always look for ways to include literacy in lessons and this week’s lesson provided a great opportunity for a story. I couldn’t find any stories that featured the concepts I wanted to introduce, so I wrote a story to accompany the lesson. I created a Powerpoint of the story, but then I remembered that I had seen Prezi used for storytelling and thought I should give it a try.

It was a fun way to create a flow to the story and it kept the students engaged. I was able to have a student do the page turning by clicking the next arrow, and I could embed a video as well.

Click on the Prezi image below to take the story for a test drive! ( Special thanks to the folks at ProfessionGenie for giving me permission to modify one of their images for my main character, Jerome, the mechanical engineer. )


%d bloggers like this: