Programming

On the Monday after the Regional, I proudly put our trophy up on the front office counter along with the certificate. Whether we decided next, our first FLL outing had a tangible memento of that team's success.But we had decisions to make - would we take the team to the Sydney National Championship? First of all, I have to find out if the families would commit to the idea first. I drafted a letter to send home, setting the minimum response at six students to make the trip viable and asking for a commitment (if funding was available) by Wednesday. Immediately, two students informed that they would not be able to be part of it as their families had already committed to overseas trips to visit family in Korea and India respectively that departed prior to the Championship dates of December 2 and 3. I wasn't that hopeful.

Then an email lobbed in my inbox on Tuesday morning that set a deadline by the end of the week to either confirm our place or release it for a wildcard entrant. A few team members visited me in my office with pleas to "make it happen" - they were still flushed with success and even with the whole venture totally unconfirmed continued to practice and perfect robot coding missions. A couple of Splice Cube members offered moral support and advice as well which was really appreciated. On Wednesday, six forms came back to me meaning that families were supportive of seizing the opportunity. By Thursday we had secured funding for the trip and so I excitedly sent off the confirmation that we would indeed be heading to Macquarie University! After securing tickets and accommodation, the team ran through all of the crucial things that needed to be organised and fine tuned before the next weekend.

The coding missions were refined and the script for the presentation modified for fewer participants. They decided to stick with "simplicity is the key" robot design and we packed some attachments and spare parts into a ziploc bag, padded the robot for the trip and added some spare batteries. Notes were sent home and permission forms gathered in readiness for the early flight out of Adelaide the next morning.

We flew out of Adelaide at 6.00 am and got into Sydney at around 8.30 am local time. We secured a Maxicab for the trip out to Macquarie and the driver took us over the Sydney Harbour Bridge. We were quite early so headed over to the local food court to eat some "brunch". We then joined the massing teams near the registration area - there were teams from state schools, quite a few private schools and some homeschooled teams. There were teams wearing their school uniforms and others like us in their customised team t-shirts. There were teams who were carting in large black plastic crates filled with robots and attachments. By comparison, when it rained later on, our robot fitted in a plastic shopping bag!

Once registered, we found our pit area which was a lot smaller than the spacious room we had shared at Novar Gardens. There was certainly no room to spread out so I was glad that I didn't bring our game mat. We looked at our schedule and just like the Regional, we were super fortunate to have a great run. Everything was well spaced out - the first thing was the Research Project which the kids agreed would be great to get out of the way and minimise the length of time battling nerves. This was followed by Robot design and then Core Values which the team was really, really confident about. Then we would have our three Robot games, one mid afternoon, one early evening and then the final mid-morning on Sunday. It was time to head over to the opening ceremony.

There were 68 teams at the Nationals, plus volunteers adding up to around 1200 people at this event which meant that the Opening Ceremony was held in two theatres at the same time, with any spectators watching a live stream in a third theatre. Each team were allocated coloured wristbands that sent you to a specific theatre - we were off the the Lotus Theatre which would house about a third of the participants while the Macquarie held the majority. The hosts took it turns while being broadcast on the screens behind them. As seems to be the case with Lego events, it was high energy and dynamic, building up the excitement for everyone. The ceremony took longer than we expected and we nervously watched the time tick up closer to our 1.00 pm start time for our Research Project. We raced out of the theatre with ten minutes to spare, grabbed the props and pounded up two flights of stairs to get to the right venue .... but the judges weren't there yet! They were still on their way back from the theatre so the team calmed themselves. This was held in a lecture theatre and at the coaches' meeting we were told to be respectful of how many visitors and family members we were bringing to watch as to not interfere with the judges' job. That wasn't a problem for us - our audience was a total of one person, Casey, an upper primary teacher from PNPS who was generously giving up her weekend to be our female staff member on duty. A judge arrived and the students got started with their presentation on water contamination only to have the second judge join his offsider a few minutes in. The team took it all in stride and were done in around three minutes, possibly indicating that the research project needed more depth.

Time seemed to move very quickly and it was soon approaching time for Robot Design judging. With our key coder in India, his compatriots had to step up and explain the coding choices while the others talked through their design choices, their mission strategy and demonstrated some of the missions with the robot. This was good because they were relieved to see that the missions that worked so well back in the STEM room at school looked like they would yield similar results here in Sydney. A couple of missions were a bit awry so immediately after the session concluded, a couple of times were booked for later on the practice tables. Shortly afterwards, we moved over to another building for the Core Values activity. All weekend long, all of the team members talked about this area being their strength, how they got on so well together, how they complemented each other and communicated to others. They were certain that with this chemistry that I could really feel, that they would do well.

And they did. The challenge was a simple one - a scenario of a flooded neighbourhood and six items that could be of use in such a disaster. Unanimously decide and justify which item would be kept within two minutes. They astounded the judges when they came to consensus in under forty seconds! They justified their choice clearly, and spoke like a team, finishing each other's sentences without interrupting - it just showed through that they were all on the same page. They answered some questions about decision making and choices within the context of the team and they were finished. "I think we nailed it", said Anna, our youngest member.

The Robot Game setup was pretty much the same as the Regional but in a much larger theatre with more hype and overhead cameras boradcast on the screens behind. The first game scored 50 points which was no disgrace but we could see some of the more advanced teams scoring in the 200 - 300 point range. A lot of these teams were using box robots that could handle various types of attachments, and could sweep down the game table covering numerous missions before returning to base. Not really knowing much about robot design prior to becoming a coach, I could see how teams with multiple years of experience can build on their prior robot and can continue to work on the design even during the "off season". After all, even if the theme and missions are different every year, what the robot is being asked to do can be predicted and designed in advance. The missions dictate that a robot can push, lift, pick up, move objects, flip, rotate, push down, release and so on. Even with a couple of year's experience, a team could build a robot that can be readily adapted to the requirements of a new theme. YouTube is full of videos shared by FLL teams from all over the world so there is no shortage of inspiration and concepts to try out.

The rain came down mid afternoon and we dodged showers to head back to the food court for a late lunch/early dinner. The team was in great spirits and I had managed to livestream the first round to the school FaceBook page. As we ate our food, I checked some of the comments and found Vedant, the team member who had gone to India just a few days prior had watched the footage, and offered strategy and words of advice to the team. This was fantastic and again, spoke to how bonded together the team was. He offered tips on how to improve the next round through improved positioning of attachments and so on.

... remember one slight movement in the position will change the whole missions success rate.

The second round was at 6.30 pm and things went well for a new high score of 70. Remembering that the original goal was any score above zero and that H2Flo were really using a "booklet robot" with precise coding based on wheel rotations and exact starting spots, this was a good effort. It didn't matter that we were ranking in the 50's because we knew our strength wasn't robots - but that still was the fun part. We put the robot back in its plastic bag, tidied up our pit area and then caught a maxicab to our accommodation at Mantra Chatswood.

The rain from Saturday's afternoon and evening were gone by Sunday morning which was cloudless and sunny. After fuelling everyone on toast, we packed up and headed back to Macquarie University for the second day. Everyone was relaxed and that might have been why no one checked the robot very closely prior to our final Robot Game, which turned out to be a sticking point when the pressure of the "1, 2, 3, Lego" start commenced. The final round stalled when the robot wouldn't move - the culprit was loose cables but after a bit of freaking out and getting one mission complete, things fell apart rapidly for a 10 point final score. Luckily only the best round counts, and lots of teams have at least one bad round.

We stayed to watch some of the other teams including the amazing Project Bucephalus whose robot scored a mind boggling 390 points. And the cool thing was that my team weren't intimidated by this - they were inspired! We then packed up the pit area fully and then headed back over to the food court again for an early lunch with plenty of time for the Closing Ceremony. Again, this was back in the Lotus Theatre with live crossing back and forth from the Macquarie Theatre. There was dancing and a high five line and plenty of celebrating when they announced that all teams would be getting FLL medals for making it to Nationals. When over 680 teams who participated in First Lego League from all over Australia, being in the top 10% was quite an achievement for all National Championship teams.

They then listed out the trophy categories and the winners, second and third place getters. With 36 trophies being given out, we were optimistic that maybe, just maybe our good fortune might continue. And it did ... with a Third Place trophy in the Inspiration category, a sub branch of the Core Values part of the competition. Turns out H2Flo's instincts about the team chemistry were very accurate. Then it was all over very quickly, and it was time to get back to the airport, catch the plane and greet some very amazed and justifiably proud families back at Adelaide Airport.

So, last night I tried to document my preparation for my two First Lego League teams. As I wrote in the previous post, I was a rookie coach with two rookie teams so I had spent a lot of time checking through documents from the First website but still really felt like the teams weren't really getting the guidance they needed. Part of it was that I was also very busy with other responsibilities both at work and at home. Anyway, I had registered both teams for the Novar Gardens Regional, which was to be held a week after the PAC Regional as a result of more teams entering FLL for the first time. There were about 40 teams lined up for the PAC event, and there were 18 teams in the Novar Gardens one. I recall thinking that this was good as that meant my kids wouldn't be overwhelmed and overrun by experienced teams who really knew their robotics. Even so, I told both teams that our main goal was to have fun and enjoy the experience - by now, everyone was pretty confident that their Robot Game score wouldn't be zero!

The Novar Gardens event was held at Immanuel College where a long, long time ago I was a student. In FLL, each team gets allocated an area to call their home for the day, commonly known as "the pits". These were all in the Margaret Ames Centre, on the site of the old boys boarding house. An interesting sidenote is that Margaret Ames was my Year 12 English teacher - I have said in the past that no teacher in my education inspired me to become a teacher but in her case, she was definitely one of the better ones. It helped that I liked English.

We put all of our gear in the pits area and I went over to the Coaches Meeting to get the lowdown on latest rulings in the Robot Game, how the practice table areas could be booked and where to find every part of the day's schedule. We were reminded to remind our students that judges were always on the lookout for examples of Gracious Professionalism ™ so teamwork, helping out others and being thoughtful were aspects outside of the actual robotics that would determine how teams fared on the day. Marg, my principal, came along for the day and luckily so as I soon found that trying to juggle two teams was an extreme challenge for one coach as two different schedules meant some clashes where I could not be in two places at once. After an opening ceremony, both teams got to have a practice Robot Game on the competition tables in the Century Theatre. Then the day was up and running.

I attended with both teams at various times to go to their three judging sessions. These sessions are held with the team and coach only in the room - no external spectators. Even though both teams had these in differing orders, I will recount them as if it was sequential. Both teams had to present their Research Project to a couple of judges. Splice Cubes tackled their human based water problem on the issue of the lack of fresh water in the world. Their research told them that about 3% of the world's water is fresh and two thirds of that is frozen. Their proposal was to mine icebergs and melt that water and transport it to countries where water is in short supply. The judges asked some probing questions about their concept - what would be the effect on the world's climate if this were to happen? H2Flo tackled water contamination as their issue and had created a 3D printed filter prototype. Again, some probing questions from the judges kept them wondering if they needed more depth in their research as their presentation was quite entertaining. From my perspective, both teams did a reasonable job but I felt that their research needed more depth and their solution needed further development.

Another session was the Robot Design Judging session. Both teams had developed relatively simple robots that were devoid of sensors. H2Flo went with the mantra that their design embraced the "simple is better" philosophy with less to go wrong. Our coding experts were able to talk to the judges about their strategy for tackling the various missions. Splice Cubes had build a squared off structure using Lego beams on the back on the robot to assist with more accurate mission launches. For this session, I felt that Splice Cubes had the edge. After all, in the week leading up to the Regional, their robot was regularly scoring between 50 and 90 points in practice sessions. They also had more mission runs up their sleeve; the result of the time that the girls in their team had invested during their break times. However, at one lunch time the H2Flo robot went on a spree where everything clicked and the robot scored a hypothetical 95 points. I still thought that the Splice Cubes robot and coding was superior and that would show out in the Robot Games still to come.

The final judges session was the Core Values session. The task was for the team to build a tower as tall as possible from Lego in two minutes, have it measured by a judge and then break up it all up and return it to the box in pieces ready for the next team. The judges also asked questions of the team - how did you come up with your name? What is the best part of FLL? What is the most important thing that you have learnt? It was in this session that H2Flo really clicked especially when Jimmy (remember him from the past post?) responded to the last question by saying that he felt that the most important thing he had learned was teamwork as prior to this, he didn't really know any of his team mates all that well and they were all very different people but through teamwork they had come together to share the common goal of being committed to the team and doing their collective best. This was really cool and when I look back at their team, of the nine kids who came on that day, there were four different religious backgrounds represented and five different cultural backgrounds as well as being balanced gender wise.

Then there were the three Robot Game matches. This is the spectator friendly component of FLL and is probably the hook that gets kids interested in the first place. Marg streamed all of the matches to our school FaceBook page which was great as I missed three of the matches due to the judging sessions. This was pretty close - in these matches only the best of the three scores counts towards the final outcome. Splice Cubes managed a credible 55 points as their best and H2Flo slid just past them with a 60 point best effort. This had the two teams at fifth and sixth place at the end of the matches - which we thought was pretty good for first timers. The best score posted was 130 by a team of high school students but the smaller field at this Regional meant that the big scores we had seen on YouTube weren't happening here. Once again, the teamwork of H2Flo showed through after a disastrous second robot game where nearly every mission failed. The student who had designed most of the coding was beside himself and was very upset, feeling that he had completely let the team down. Sitting down in misery, he was quickly surrounded by his teammates who all did their best to assure him that he had done his best, they were all right behind him, these things happen so don't worry and maybe the robot just needed a fresh battery. I don't know if any judges saw this but the team surrounding and supporting their colleague was super genuine and could well have been the biggest learning moment of the day for these guys.

Mid-afternoon was the time for the closing ceremony. After a demonstration from a FRC robot, and some obligatory YMCA dancing, the hosts and judges had results ready to announce. My two teams were sitting back, relaxed as they had met their goal of enjoying the day. Sitting next to Marg, I said to her, "You know, even though it doesn't matter, it would be pretty cool if one of the teams won a trophy. It would really raise the profile of Lego League in the school and help with STEM hype."

The next thing I know, they were announcing that H2Flo had won the Judges Trophy as the most consistent performers throughout the day. The kids were so excited as it was so unexpected! I felt for their Splice Cube colleagues as they too had given the day their best shot but they were sporting in congratulations for their jubilant team. I was very pleased - the rookie team had worked like a team all day and had been recognised and the Lego trophy was very cool.

A bigger surprise was still to come as the announcements wound to a conclusion. "Before we announce the day's Champion who will be invited to compete at the National Championship in Sydney, we will announce the second place getter who will also be invited to go to Sydney. That team is .... H2Flo!"

As the kids screamed and leapt to head to the front of the theatre, Marg and I looked at each other and thought, how are we going to pull this off? The rookies from the disadvantaged state school had exceeded all expectations and now an enormous opportunity sat in front of us. Could we get organised in time? Would parents support it? So, as we headed back to the pits to pack up for the day, my head was swirling with what might be possible. I had seen the email reminder a few weeks earlier that alerted all teams to the National Championship but I had binned it, never thinking that either team were going to gain anything but experience from their first FLL foray. Once the excitement subsided on Monday, we had some serious decisions to make before any promises could be made.

 

 

In the past I think I have mentioned that I haven't always been that interested in robots, or even coding for that matter. On a personal level I just struggled to be interested in learning about then, even though on a professional level I knew it was important. In the previous few years at Woodville Gardens I was spoiled to have a talented teacher, Mel, on board who was super keen in this area and single-handedly got the school's Lego Robotics program off the ground. My contribution was limited to signing off on the purchases from the budget and coming along to a RoboCup event in 2015. I checked in from time to time to see how she was going with the students and thought that entering teams in the First Lego League was a great idea but I didn't really step up and really find out exactly what was involved. Which was to my detriment - one of my few professional regrets of the last few years. But it was a testament to Mel's talent and drive that she didn't come looking for my support or help. Her efforts were rewarded at the 2016 Regional day where her team won the Research Project trophy.

Fast forward to this year and I stepped into a new role as Assistant Principal - STEM at Prospect North Primary. My principal, Marg (who in her own words is a "fellow techhead") described my role as getting a lot of technology programs up and running to really widen opportunities for the students, and hinted that I might want to get a First Lego League program up and running. And so away I went on a whirlwind journey that would progress way beyond my own expectations.

Not content with just learning how to be a rookie coach in a new-for-me venture, my fellow AP Nicola and I also decided to get involved in First Lego League Junior, a first for the school and indeed as it turned out a first for any school in this state. But that's another story for another post because as successful as FLL Jr was for our first go, it was still contained within our own expectations. And unlike how I left Mel by herself at WGS, Nicola was an equal driver of this program.

But on the FLL front, it was just me to get it all up and running. I called a meeting of interested students from Year 5 to 7, and had just over twenty keen potential participants come along. Trying to be inclusive and democratic, we decided to form two teams of ten with a couple of reserves should anyone find it wasn't for them. At that stage, I wasn't even sure it was for me either! I gave them the option of forming their own teams and one group quickly formed around two friendship groups and a connection between twins. This team became Splice Cubes. The other team was a mixed bag of students who didn't really know each other that well - the only common factor was that they were interested in pursuing this whole venture further. And interestingly, when teams meant that one person had to be a reserve, a Year 7 boy called Jimmy volunteered to be that person because he "didn't want anyone else to miss out." This is retrospectively interesting so remember the name as this post rambles along. This team decided to name themselves H2Flo.

I had ran lessons with the upper primary classes using our newly purchased Lego Mindstorms EV3 robot kits but felt like I was only just a step or two ahead of the students. A quite a few of the talented and keen kids who had signed up for FLL grasped the concepts of Mindstorms coding quickly and moved quickly past my expertise to figure a lot of stuff for themselves. Again, it is important for teachers to realise that they don't have to expert in everything but affording the students the opportunity to learn for themselves and not be constrained by their teacher's limitations. I tried to operate with that mindset throughout this whole journey, trying to relay information as required for them to get to their goals efficiently.

For any readers not familiar with Lego League, the deal is something like this. You can have a team of up to ten students aged 9-16 and they have several tasks that they must prepare for in order to compete at a Regional Championship. Every year, Lego have a new theme based around a social human issue - previous years have looked at rubbish, senior citizens and human interaction with animals. This year's theme was HydroDynamics and was focussed on human use of water and associated problems. The Robot Game is a large mat with Lego constructed missions that an EV3 based robot must undertake in order to score points within a two and half minute Game. The team must also prepare a Research Project presentation that must take no more than five minutes in front of judges, and it must offer a unique solution to a problem identified that ties in with the season's theme. At the Championships, there is also a Robot Design section and a Core Values activity that the team does not get to see until the day.

The August launch date for the new season loomed quickly and we ordered a custom built practice table from the carpenter partner of Jasmin, one of our Reception teachers who had worked with Mel in 2016 with the Woodville Gardens team in their successful Animal Allies foray. This table is a thing of beauty - so nice we have resisted the urge to paint it and left in its natural unvarnished state. After a quick online application I registered both teams and scored some sponsorship from Google who paid for our registration, the cost of the game kit and a new EV3 kit. This is part of Google and Lego's commitment to try and encourage schools from a disadvantaged background to get involved - for us, it was much appreciated.

It didn't take long for the game kit to arrive and I got both team to unpack and build the Lego models for the game mat that fitted into our practice table. There was a model toilet that triggered a water treatment plant when flushed, there were water pipes that needed replacing, a well to push into place, a fountain and flower that needed "big waters" and other models that required the robot to lift, push, move or carry to complete successfully. These models were placed or locked into place with velcro like tabs and the students could start planning for their robot games. Both teams decided to build robots based on the EV3 booklets and decided not to include infrared or colour sensors as our fast tracked learning curve had not allowed time to get particularly competent in their use. Each team met and allocated roles so that the Research Project would not get neglected but as they had not participated before or seen this before, they were unsure of how the whole thing should look and be structured. And because I had neglected to take a close look at Mel had done it with her teams, I was only guessing with my own advice.

After a while, a small group of girls from the Splice Cubes team started asking me if I could supervise them during their breaks as they felt they were getting somewhere with their coding. They designed attachments and modified their robot in an effort to get consistency when they "launched" it out to tackle a mission. They analysed the game mat and planned which missions were within their reach as rookies, and worked towards those goals. The other team were more sporadic in their break time visits and seemed to have a rotating roster of students who were looking at their coding. Their robot was less sophisticated and they were in awe of how far in front the Splice Cube students were in comparison. Once the whole gamut of expectations were unveiled and regular meetings at break times, we had a couple of kids decide that it wasn't for them and this opened up the opportunity for a reserve to join in. This was fortunate for H2Flo as Jimmy was able to participate fully and share his coding and strategic skills with the team.

It was about that time that I went to FLL training run by Concept2Creation who run the FLL events here in Adelaide. They had referees and volunteers from the community team RoboRoos there and I learned a lot of key information that was invaluable. One comment that stuck in my mind was that is not unusual for a rookie team to have a Robot Game where nothing goes right and scores a 0. So, don't be concerned - if your team can get your robot to score anything then that counts as a success! That was a great message to take back to the students.

At the end of Term 3, I realised that there were only 4 weeks to go before our Regional at Novar Gardens in mid November. We met with the teams and checked on their projects and Game progress. Splice Cubes were looking promising with their robots but had still to get going on their Research Project and were still even to identify a problem to solve. Meanwhile to my surprise, H2Flo were quietly well advanced in their research showing me a draft script and a prototype 3D design, but their robot game efforts were a batch of individually developed mission coding strings sitting on four to five different laptops. We resolved to have every break time available to either team to work on their priorities, and I negotiated an extended release time from regular lessons for the students. One of the guidelines of FLL is that teachers/coaches are there to help but the students do all of the work - I made sure that was the case resisting the adult urge to meddle and give them "better ideas". We had team t-shirts designed and ordered so that we would look just like those teams we could see on YouTube videos of American FLL events. At $20 a student, they were a great investment in team spirit.

The November 19 Regional was rushing up at us. There was panic, apprehension and excitement in equal measures. Media release forms were signed and returned and the two teams were as ready as any team who doesn't really know what they have signed up for looks like. Would the whole experience live up the expectations we had in our own minds? We were about to find out.

 

 

In my new role here at Prospect North I have to provide some non-contact lessons for the classes here but the good thing is that it can be delivered flexibly and all teachers want it to be of a STEM or Digital Technologies flavour. This is good because it is an area I am pretty comfortable in and quite frankly, an expected part of my role. The school is still building up its STEM resources (another reason my role exists) and is a focus school in a partnership with Social Ventures Australia.

So, I have spent today planning for the upper primary classes as I will deliver 4 x 90 minute sessions spread over the next six weeks and I thought I would start with using Sphero as an introduction to coding. I have used Spheros quite a bit over the past two years and so thought I was working in familiar territory. The school had bought 24 new Sphero SPRK+ robots prior to my arrival and so on Friday I thought I had better charge them up ready for the coming week and check the iPads in the area to ensure that the apps I wanted to use were all there.

Looking at the new SPRK+ my initial thought was that they were very attractive with the clear exterior of the standard SPRK model with a blue equatorial stripe. They also appeared to be the same size as the standard white Sphero as the SPRK models I had bought at WGS were slightly smaller, meaning that covers were a little loose and it spun inside the plastic chariots without moving. I hooked everything up and left them all to charge in the library for a few hours.

After lunch, I checked by with my iPad to start the labelling process that I had established before and picked up the first fully charged robot I could see and went tap tap on the bench to wake it up. But ..... nothing happened. I tapped a bit harder but still no response. I assumed that maybe it hadn't charged properly so I dropped it back on the charger and tried the next one. Same result even when I dropped it directly onto the carpet. I thought that maybe the Spheros were in deep sleep mode and went through the process I thought would bring them out of that mode. No deal and nothing was being detected when I looked at Bluetooth on my iPad - something was not right here so I headed for the internet.

On the Sphero FAQ page I found the following:

Does SPRK+ work with other Sphero apps?

Modified on: Fri, Nov 18, 2016 at 3:12 PM


Currently, SPRK+ is only compatible with SPRK Lightning Lab application which you can download at https://sprk.sphero.com/d, and the main Sphero app.

I could feel my plans and accumulated knowledge of relevant apps crumbling into dust in my mind. I couldn't use Drive, or Draw'n'Drive, or even Tickle if I was to believe this post. I quickly rushed over to see the school technician before he wasted his time trying to find the now-outdated apps for the iPads!

So I went over to my previously ignored Lightning Lab app to see how it would all work. Straight away I could see a new feature for connection that was a big improvement from the past. Simply you open up Lightning Lab and choose SPRK+ from the Tap a Robot to connect menu and I was away. No more opening up Bluetooth and looking for the three letter colour code to connect. No more accidentally bumping a Sphero and waking it up in transit and wasting valuable battery. Even better, there is now a battery life indicator on the main page.

Through this app, the user can progress through a Learning to Code series of mini-lessons and activities although you need an account to access this feature. This worked fine at home but there were some issues on Friday on the school network. A workaround might be to get the kids to sign up on their own laptops and follow the lessons in a self paced self managed style that would suit quite a number of learners, as long as the website isn't filtered on there as well. Something to negotiate with the IT department but unlikely to be resolved in the short amount of time before I want to use these with my first class.

Within Lightning Lab you can use joystick style controls which essentially makes the old Drive app redundant. That was good and even better was the option to code by Draw which meant I still have access to the same capability that the Draw'n'Drive app provided. I then went onto the Tickle app site and found out that they do support the SPRK+ on the latest version which sent me hurrying back to our IT support to change my order to include that as a required update. Finally to make my day, two staff members came through the library where I was starting to pack up the charged Spheros and asked if they could borrow one for the weekend. They downloaded Lightning Lab on their phones and were already buzzing with the possibilities as they had to give the Spheros a run around before heading off for the weekend.

So, this is a greatly improved Sphero. After getting over the fact that its improvements had made some familiar apps and processes irrelevant, I can see that this is a more focussed_on_learning_that_is_fun product with less connection to pure entertainment which can cloud the learning potential for some students. I am looking forward to see how the students engage with these robots and perhaps show me some new possibilities with their learning.

I described my Digital Leadership initiative in my last post and how students have signed on to participate. I managed to secure some time in our Resource Centre to supplement the lunchtime sessions so that students could work towards their badges. We have started with the twin options of MinecraftEDU and Sphero Robotics, but potentially down the track, the program could expand to Digital Leadership in iPads, BeeBots or other technology connected possibilities. We've had a Minecraft server for a few years now and I've blogged about some of the ways it has been used at our school after the research our school has done in the past.

But the Spheros are brand new to me and the students. So in the last three weeks since I took delivery of the 15 little robotic balls, I have held two afternoons and four lunchtime sessions with the sole intent of letting the Leaders loose to work things out for themselves. It has been fascinating to watch. We have a few accessories to use with the Spheros - rubberised covers, small plastic chariots that have a Lego like connection section and Terrain packs with ramps, poles and connectors to create a stunt park or obstacle course. I nabbed a building's travel case of ten iPads and downloaded eight of the most useful Sphero apps, and supplemented them with my own staff iPad and a couple of spare Nexus 7 tablets not currently being used for anything else.

The first challenge was getting the Spheros to connect and communicate with a device. The connection is made via Bluetooth and every Sphero flashes its own tri-colour sequence when woken. My eBay special at home here has a sequence of Green, Blue, Red so it appears in the BlueTooth settings as Sphero-GBR. But you can imagine the mayhem when a whole bunch of stuents double tap their Spheros to wake them, forget to see what sequence is flashing and are confronted by a list of four to seven visible devices that are offering connection!greensphero bluesphero

We started to see that often the Sphero the Leader wanted to use would not respond, or would suddenly start showing its blue aiming light but be under the control of someone else in the room who did not really know what their app was doing but they could tell they were connected to something! Once the connection issues were sorted, students had no problems getting the Spheros moving around the area using the Drive app - a simple set of controls allowing direction and speed as well as the ability to change LED colours and a limited number of "tricks" (zigzag, figure 8, square, circle, lightning). They tried out the nubby covers, zoomed around in the chariots, even allowing me to insert my iPhone into one of them and filming a Sphero Chariot POV of the Resource Centre surrounds.

Eventually, a couple of the students asked to use the Terrain Pack gear and starting setting up jumps and obstacle challenges to drive the Spheros over and through. One of the badges I had designated was a Rally Driver's badge and we had some discussion about what this would entail. I talked about being able to successfully negotiate a prescribed route but that they could set up their own challenge. A number decided that getting over the long ramp as pictured left would be testament to their skill but it turned out not to be as easy as they first imagined! The Sphero's smooth surface spun and skidded on the way up so some Leaders switched to a cover to get some much needed traction. Eventually there was a lot of excitement as Spheros veered off track at the last second, as successful attempts went unwitnessed and unverified. A lot of play and a lot of learning was going on in all sessions, and the cooperative learning I envisaged was starting to unfold.

A couple of more adventurous students decided to try out some of the other apps. One leader tried out the Sphero app which turns the use of the ball into a gaming experience with levels, points and rewards. This is quite a good way to get students thinking creatively about the Sphero and not just see it as a toy to drive around. The tricks that can be unlocked in the Core Exchange show that colour and movement sequences can be humorous and artistic, and can lead to the use of the MacroLab app where the programming aspect of Spheros can be utilised. Only a a small number of students have felt confident enough to have a go in this app but the pride in creating and programming a simple Macro could be clearly seen in the face of the two Leaders who just had to show me what they had coded.

These leaders clearly need more time to grow their expertise and I am learning a lot just simply through observation and trying to solve their problems as they arise. Some students are even keen to help me pack everything up at the end of a session, ensuring that all Spheros are powered down and "asleep", everything in its correct box and easy to access for the next time. I want this group of about twenty students to be able to assist me when I start using these robotic balls with middle primary classes. One test lesson with a class in my building taught me that one teacher on his or her own will struggle to get first timers up and going without headaches galore. Having some expert Leaders on hand to help with connection, modelling appropriate care and encouragement will be of benefit to all parties. The teacher will appreciate the support, the students in the class will get a better lesson and the leaders will have helped others in their learning and put their particular skills to great use.

2 Comments

For someone who likes technology, particularly for learning, I have never been that interested in the field of robotics. For all of this recent focus on coding and programming in education, I haven't really got swept up in becoming personally skilled or knowledgeable in the area. I recognise its importance but have to admit to putting things like Lego MindStorms in the "too hard" basket. My interest has always been in the internet and like many self taught learners, it's easy to play to my own strengths and steer away from might be a steep learning curve out of my comfort zone.

The recent release of the Australian Curriculum for Technologies (pending final endorsement) has renewed the focus on specific ICT and digital technology skills. The Technologies curriculum is now split into two specific subjects - Digital Technologies and Design & Technology. The latter of these contains much of the SACSA Design & Technology curriculum and its focus on Design/ Make/ Appraise so in general, most of my primary school colleagues feel comfortable with the expectations of that subject. The Digital Technologies curriculum is a more specific focus on skills and knowledge that our previous state curriculum spent time integrating throughout the curriculum. So it feels a little bit like subject matter that is making a comeback even though we know that digital technologies work at a more sophisticated and lower cost point in our daily lives than even ten years ago.

https://www.flickr.com/photos/ocg_bilder/8571558534/

We held one of our student free days as an Australian Curriculum focus, and had two DECD consultants spend half of the day focussing on the Digital Technologies curriculum. 2015 is a familiarisation year and we looked at several of the key concepts like computational thinking and programming. We looked at and used BeeBots and one of our talented upper primary teachers showed how her work with Lego MindStorm robotics was giving students opportunity to program. This teacher has been totally self taught after recognising the need within the upper primary students and led the way in overhauling our resources for Lego Robotics. She has spread her expertise across the whole five class unit, and even fostered interest through a lunchtime club. So, again, I know her work in this area is good but I have never dabbled using these tools myself. The BeeBots are great - simple in terms of setting out a sequence of commands and very accessible for early years students. After the day, I had a lot of teachers requesting that our meager supply of these robots be replenished. I've ordered them and they are on their way.

So, Beebots filled that need for the programming part of our new curriculum nicely for our Early Years students, and MindStorms is targetted at the Upper Primary area so I asked the consultants what would be best for the Middle Primary Students (Year 2, 3, 4) and their suggestion was the Probot. I then remembered that there were four of these sitting in a tub in my office! These were from one of the closing schools (my school was formed in 2011 from 3 smaller sites) and hadn't been touched in four years. To my mind, they weren't that much more sophisticated than the BeeBots, and when I went to purchase some, the price for each was over $160. That was $100 more than a BeeBot - withe major differences being that it was larger (not really a plus) and had an input screen so that instead of pushing > four times, I could key in 4> for the same result. Not exactly a quantum leap forward in extending programming skills, and potentially could have students complaining that Probots were boring and they were doing the same stuff as they would have with the BeeBot.

So sitting at my desk, I was hesitant to buy the fleet of Probots for the school because of these concerns. So, I turned to my trusty ally, the internet, as I was sure that there must be a better alternative to the Probot. Something to bridge the gap between BeeBot and Lego Robotics - but unique and engaging in its own way. I remembered that I had something that might be useful in my neglected delicious account - and found Romo. This is a neat idea where you plug an iPhone into a robotic base and interact with it. This was promising but not quite what I was after. The school isn't flush with iPad Touches and iPhones so I went looking anew.

https://www.flickr.com/photos/karasutech/14150146105/

Then I found what I was after - Sphero. Basically a ball shaped robot, controlled via apps on a tablet or device. The site was informative and I liked the fact that it linked into its own Education section. One of the Apps where I could imagine potential was MacroLab where users can create macros; basically long lines of commands in order to get Sphero to perform a particular action or routine. I could see the programming aspect coming into focus - but unlike MindStorms where the robots being built are very sophisticated, the ball robot was conceptually very simple. I watched some videos, and went to see Marg, my line manager, who has a deep background in digital learning to see whether her impressions matched mine.

My original thought was to buy one and play with it myself to work out the potential. Marg was more confident. "Buy a class set if you think that they are what you want," was her reassuring reply.

So I did.

I ordered them from the Sphero US store, and they arrived in under a week. (I am still waiting on the BeeBots, ordered from an Australian company!) I paid the GST import duty and bought power adaptors as they shipped with the US version. I bought covers for the Spheros and several Terrain packs which have click and hold pieces to create obstacles and barriers to manouevre the Sphero through. I also purchased an original Sphero on eBay (I ordered Sphero 2's for the school) for $46 as an investment in my own professional learning.

So, they are pretty cool and I think that they will serve the purpose I envisage. I had a search through my blogging connections to see if I could find anyone I knew using them for learning - my only link was to Wes Fryer's STEM resources as part of his after school Maker's club. He had four of the beasts and was feeling well resourced - but I had ordered fifteen!

How does Sphero work? Basically, the ball needs to be charged prior to use on its own induction stand. Three hours charging gives the user an hour's worth of constant use. I've downloaded about nine apps to try but the first one I have had students start on is Drive, a simple app that gets them to use the tablet as a remote control for the Sphero. They can control direction, speed and colour within that app. The standard Sphero app is wrapped up in a gaming interface where points accumulate for Missions and can be exchanged at the Core Exchange for pre-programmed Macros or tricks. This app is the one that gets users thinking beyond just getting it to move around and crash into things. An example is the Frog macro where Sphero turns green and jerks forward with a timed croak from the app. There are many others but these "tricks" then can lead to using MacroLab, where users can then create their own - the actual programming!

I'm only in the beginning stages of this all. I have been using my Digital Leaders at school to become the student experts using Spheros, and I have had to think through many logistical issues when using then ranging from charging to security, from sourcing enough iPads to dealing with multiple Spheros trying to connect to their iPad via Bluetooth all at the same time. These devices could suck up a lot of my time if I allow it, but I also still have to introduce them to staff, provide support in their use in classrooms and in planning for the coverage of the Digital Technologies curriculum. But this is still the first robot that I have got seriously excited about. We'll see how it progresses.