BETT 2016 - Raspberry Pi physical computing workshop

Last year I was intending to run a workshop for Raspberry Pi at BETT but was recovering from an appendectomy instead. This year tempting fate I volunteered again and fortunately avoided any surgery in the run up to the show.

I had been working with ,my son Toby who had created his own robot using the CamJam EduKit 3 and I had used GPIO Zero to help to reduce the level of typing required to get his creation working. As I intended to talk about Physical computing Toby came along too with his robot. to show what could be done with a few simple lines of code.

He was very pleased to be able to show off his creation and say a little about how he had made it. he was also very excited to have his own badge with his newly created job title.

We then got hands on and had the attendees making their own simple circuits and writing the code to make things happen in the real world. Having some hands on time was a really powerful tool to demonstrate how quickly results could be seen using simple components and GPIO Zero. I did promise at the show that I would add the presentation here with the information links so here it is on Prezi - Lets get physical -  an introduction to Physical computing with GPIO Zero.


The show was challenging environment to deliver training in with all of the competing noise and activities occurring around the stand. It was an interesting cross between market trader and teacher. Attracting people into the stand and then guiding them through creating a circuit and controlling it with code It was also a challenge with people arriving to the stand (attracted by what was happening) part way through the session and wanting to join in.

The sessions both ran slightly different to the plan (and  to each other) but I think we were able share the power of being able to make things happen in the physical world.  I think especially with the late arrivals it was a great demonstration of how results can be achieved really quickly using GPIO Zero due to the less onerous volume of code required.

If i was going to do this again i would probably take some pre-prepared  kits with the components for the circuits or even use a HAT to simplify the process. I would also think about printing some copies of the code / circuit diagrams to make it easier to manage with late arrivals and swapping the screen around from basic to advanced tasks. Having both on a laminated card (or just a bit of paper would do) would have made it easier for those who arrived late to have a play with the basic example without me having to switch the screen back and forward.

GPIO Zero - making coding less language intensive.

In a previous post Getting Physical with Python I wrote about the difficulty some of the younger children in my computing group had with the volume of typing required to get started with physical computing. They did not struggle with understanding but it took too much time and help to enter the volume of text required. This took away some of the excitement and slowed things down.

At the time I thought to speed this up it would be good to write a python library to reduce the amount of text needed to get things to happen. Unfortunately I had lots of other things to do and this never went anywhere. However someone else also thought it would be good to make it easy to get started with physical computing and was able to do something about it.

That person was Ben Nuttall of the Raspberry Pi Foundation. Along with Martin O'Hanlon and Dave Jones he has created GPIO Zero. You can read his account of how it happened on his blog.

This python library can be used to very simply control components using the GPIO pins. The initial function set is based around the popular CamJam EduKits  (Kit 1- Starter, Kit 2 - Sensors) and makes a great starting point for physical computing using python.

A simple light and button combination can be controlled with the below example:

from gpiozero import LED, Button led = LED(15) button = Button(14) button.when_pressed = led.on button.when_released = led.off

instead of something like this:

import os 
import time  
import RPi.GPIO as GPIO

GPIO.setmode(GPIO.BCM) 
GPIO.setwarnings(False) 


GPIO.setup(14, GPIO.IN)
GPIO.setup(15, GPIO.OUT) 

while True: 
        if GPIO.input(14) == False: 
              GPIO.output(15, HIGH)   
        else: 
               GPIO.output(15, LOW)  

 time.sleep(0.5) 

The reduction in volume of code and setup required is brilliant. GPIO Zero is an amazing tool for education. This is especially true where the volume of text entry is a barrier (either with younger or SEN children).

The tool allows the focus to be on the programming concepts and not on the entry of text. When i worked with my HomeEd computing group there was a difficulty fro a number of the students (aged between 5 and 15) in using the GPIO library as there was a lot of code to enter. They were generally happy with what they were trying to achieve but found that it took a long time to enter the lines of code required just to light up the LEDs.

This meant that in the one hour session that is what we achieved, lighting up the LEDs. Whilst this was a success and the children were happy with getting there it would have been much better to spend more of the time in the session exploring what could be done rather than entering lots of text.

GPIO Zero takes away some of the burden allowing children to focus on what they are trying to achieve rather than on copying out lots of lines of code (especially the set up parts that are conceptually more difficult to grasp and result in questions about what is BCM etc).

I have found that where I have used this it has meant I can more on more quickly and cover more of the computational thinking ideas where previously there would have been more time waiting for the students to catch up with the typing required. It also works well to satiate the desire for instant gratification that appears to be fairly common among my pupils. They only have to spend a short time entering code before they can see a result.

It is also much easier in a classroom to debug the code they have written if there are errors. The reduced volume of code makes for less searching to find the capitol that should't be there. This make students more able to do it themselves or makes it quicker for me when they can't see what is wrong. The reduction in time taken here give me the opportunity to get to more pupils and help them to progress.



I have also used this at home with my son (8) whilst he has been creating a robot using the CamJam EduKit 3 - Robots. This was really powerful because it allowed him to achieve results in short pockets of time before he lost focus and wanted to move on. He used the provided worksheets to set up the robot and connect the components and I translated the code parts into GPIO Zero for him to get the robot working.

So in summary the feedback is - Thanks Ben this is an awesome tool to help me teach computing.

If you are interested in using GPIO Zero there is a great getting started guide on the Raspberry Pi website in the resources 'Learn' Section.

More information can be found on pythonhosted.org or on GitHub. There is also a Google Doc with information and a place to add comments / requests.

The Sound of Music - Sonic Pi with The Home Ed Computing Group

With the last session I had discovered the difficulty of the volume of text required when using python and the CamJam Edukits for some of the younger children. I have been working on a python library to help with this but this week i decided to use a different tool to look at coding concepts.

Sonic Pi is a great tool because it allows you to teach coding and make music at the same time. It was also a good way of being able to progress in complexity with computing concepts (introducing iteration) but keeping the level of text entry required to a minimum.

Sonic Pi is freely available software as part of the standard Raspian build and is also available for other platforms (more information here on the Sonic Pi Website)

The simple nature of the commands required for the children to be able to make music means it is a really good tool for younger (or children less able to read / type).

Some of the barriers I had found in the Python session had been easily overcome by the simple nature of the commands. I think would have struggled with getting some of the children to start looping blocks of code in Python yet they were all happily making repeating tunes with Sonic Pi. I really wanted to avoid simplifying things too much and this has provided a great bridge between the simple block programming that some of the children have done before and text based languages.

Sonic Pi itself is based on Ruby so it teaching a specific code structure and language that will continue to be useful. O so it is simplified in that the tasks it is performing are much more complex than the Play and sleep combinations, but it is a really engaging and relevant way to work with code.

I have written lots before about Sonic Pi so i will try and avoid this becoming the Sonic Pi fan page. However in reducing the volume of typing required I have found another way in which Sonic Pi makes coding accessible to a wider audience.

The group seemed to really enjoy this session and it was one of the most requested areas to do more with.

I am starting to look to move away from just leading the sessions and i already have several children with ideas for their own projects. This is an idea I am really keen to explore as i feel the best way to learn about computing is by finding challenges and solving them using computing. If children can find something that interests them they are much more motivated to explore than if they are being directed by someone else.

Getting Physical with Python

This session with my HomeEd group I introduced some physical computing using the CamJam Edu kit .

Last time I blogged about the challenge of teaching a group with my own children (who are not used to a classroom environment). This week I had the additional challenge of my normal child swap falling through so I ended up with 3 of my own children to contend with.

With this in mind my plan was for more independent work with some supporting materials to make it easier for the children to work without my direction all of the time.

I also planned to manage the situation by placing my offspring carefully either side of me in the room so I could switch between the instruction and paying them attention. This worked much better for me to be able to manage the session. Although at one stage it did mean carrying 2 of my children whilst trying to explain things on the board (using my daughter to point out the relevant bits whilst I talked).

I had decided that I did not want to over simplify things for the children by using scratch. We had also been mainly working at the command line so it made sense to progress with this and use nano to create python files to control the components. This also followed the CamJam worksheets so I could use those to provide additional guidance so the children could refer back to the instructions.

As the group is very mixed (5-15) there was a range of experience in the group but most had not used electrical components in a breadboard before. After a quick introduction they were all setting up the simple LED and resistor circuits.

Most of the group managed to get as far as getting the lights lit but it did take some time to get there. The real limiting factor I found with using python with the younger children was the speed they were able to type the code was very slow compared to the older students (as they are still working on their reading skills this is actually quite a hard task).

There was no apparent problem understanding the concepts and adding text to control things, but the amount of text that needed reading and adding to the code was a problem. To make it easier for these younger students (and any students who find reading / typing difficult) it would be useful to reduce the volume of typing that is required to produce a result.

That said nearly all of the children had at least lit the LEDs by the end of the session even if this had involved a bit of help with typing from the adults in the room.

Basic Computing for Sheffield Home Educators

I have been talking for some time about starting a Computing / STEM group for home educated children in Sheffield.

We home educate our 7 year old son and there is a large community of home educators around Sheffield. As computing can be quite equipment heavy it is not something that is easy to do at home and until now there hasn't been an alternative.

The difficulty was finding a venue and some equipment that I could use to run the sessions. Fortunately I had seen a post about a lending library of Raspberry Pi equipment that had been set up at Sheffield University - The Pi bank. Fortune was smiling on me as this also led to the rediscovery of the Access Space. They charge for the space but they have an ideal flexible teaching space ideal for this sort of group. A few phone calls, Facebook posts and  emails later and the group was all set

The group is a very mixed group with children raging from 5 to 15 with a different levels of prior knowledge of computers and programming. This presented a different challenge to my normal classes but makes for interesting class dynamic. I say class but the plan is to try and not be too school like and see how we can follow the children's interests as we progress. We have a few structured 'lesson' type activities planned but after that I am hoping to split the group down and work on projects that they are interested in.

Today I ran the first ever session with a focus on how computers work and an introduction to algorithms.

First we made a human computer with the children forming the components and passing information around the computer to first perform simple sums.

The children took on roles with one student acting out each part of the computer and several (the more active and excitable younger boy mainly) passing the information between the components.

The user, although not too keen to hold on to the human mouse moved the mouse around our ( A4 paper calculator display) and the mouse driver reported the position. This was passed to the processor stored in memory and also displayed on the monitor (children with with pencil and paper and whiteboard and maker respectively).

This was repeated for each of the movements of the mouse to complete the sum. I had planned on simple single digit arithmetic for our volunteer processor but the user had other plans (I did managed to keep it to 2 digits, but I think she would have gone for more if left to her own devices). The processor then calculated the answer and passed that to the monitor and memory. In this case the user forgot to save (or i forgot to ask her to) so we talked about what would happen to the information and then pretended we had saved to pass the information to the hard drive (child with paper and a pen).

After that we simplified our computer, using just a camera/computer combination, lots of willing active information conduits and a rather excitable printer (my Son Toby) we experimented with how computers see and describe images using binary. To keep things simple we used a simple 1 bit black and white image which was only shown t the camera. The camera passed the appropriate 1 or 0 (each an A4 sheet with 1 on the front and black on the back or 0 with white on the back) to the information carriers and the printer started to put the image together on the floor.

This was really great as the first stages were rendered accurately but as the information carriers gained confidence and enthusiasm we started to see some arriving out of order which corrupted our image slightly. This gave us an opportunity to talk about the importance of the data arriving in the correct order.

After getting everyone sat down again I introduced our next activity which was the Sandwich making robot by Philip Bagge. I explained the activity and handed out the sheets to allow the children to plan their Sandwich making algorithms.

After donning the special robot uniform (pink pinny borrowed from home) i took on the role of robot and we tested some algorithms. We didn't get as far as a full sandwich but we learnt some good lessons about how to think through a problem. We also took the opportunity to talk about debugging.

I was surprised by how many children though that cutting the bread bag was the way to open bread until at the end someone mentioned there was no open on the instruction set. I thought this was an error until I watched the videos again and noticed that Phil starts with his bread bag open.

Overall I am quite happy with how the session went and the children seemed for the most part engaged in the activities. I now need to go off and plan for next weeks introduction to Raspberry Pi and programming in python.




Thank you to Computer Science Unplugged and Philip Bagge for the inspiration for the activities for the session.

This is Phil in action -

Outtakes - https://www.youtube.com/watch?v=leBEFaVHllE - very good lessons on how important it is to get the algorithm correct.

The Visual-Pi-ser a low cost classroom visualiser

In may last post I described my idea for a low cost visualiser based on the Raspberry Pi kit I was sent as part of the Element 14 Raspberry Pi Educators Road Test. I promised i would add more detail so here it is.

The box for the kit is used as a stand to hold the RPi case. The case in the kit has a mounting point for the camera and the arrangement holds the camera steady over the items to be shown. The main issue for this set up using the box is that the camera has a relatively large minimum focal distance so items at the range as out of focus until the camera is modified.

To modify the camera is a fixed focus unit and the lens is held in place with blobs of glue that can be removed with a craft knife to free up the lens (N.B. the lens can be sensitive to static and can be easily damaged so this needs to be done with care).

This modification allows the lens to be rotated and the items brought into focus. It also has the added advantage of slightly magnifying the subject.

The size of the box supplied is ideal for small physical computing projects but a larger box would give a larger field of view for bigger projects. The camera itself is controlled by using the Raspivid command:

raspivid -t 300000 -rot 90

This rotates the video by 90 degrees (as the camera mount is at 90 degrees to the box) and runs the video for 30000 miliseconds (30 seconds). If a longer or shorter time period is required then the number of milisecond can be changed. If you want to terminate the video session you can do so by using ctrl+c

I have created a guide on how to crate you own Visual-Pi-ser on github.

Low cost Raspberry Pi Visualiser

The kit I revived from takeing part in the Element 14 Raspberry Pi Educators Roadtest gave me another project idea.

After delivering CPD at Sheffield Hallam University i was very envious of their AV set up with a visulaiser and PC and RPi all connected to the screen. I can't make all this happen but with the RPi and camera I can make my own.

For work with the Raspberry Pi the box was even the right size to make a stand so i added a lighting solution (cheap torch from the garage and/or a clip on e reader light. Now for under £40 I had a visulaiser set up that i could use in the classroom.

A quick mock up above shows the basic idea but I'll post the full details here once it has been completed along with the python code to control the camera.

Element 14 Educators Road test

Over the holidays I have been experimenting with timelapse photography of crystal formation with the Raspberry Pi. i have been doing this as I have been selected as on of the participants in the Element 14 Raspberry Pi Educators Roadtest. If you haven't come across the Element 14 Roadtests before they are a scheme where kit is sent out to a selected group of volunteers to test and write about. They runs the tests fairly regularly and all you need to do to enter is to write a proposal of what you will do with the kit.

This particular roadtest is of the Raspberry Pi B+ Camera Kit and i wanted to come up with a proposal using the camera functionality in a way I could use the kit with students to teach Computing and Science. My proposal was to work with KS£ and Home educated students on two slightly different projects both based around taking timelapse photography of crystals forming.

We have been playing with crystals at home for a bit with my Home Educated son and this looked like a great project to try with the Raspberry Pi and Pi Camera Module. The Addition of the Wi-Pi adapter and the case with camera mount made it ideal for applications like this where connection to monitor and keyboard would be difficult and a secure mount for the camera essential.

Part of the deal is that you write at least three blog posts and a review of the kit on the Element 14 community website . I am still working on the review and the third blog post but the first two are up already:

Part 1: Introduction to the project

Part 2: Testing



EDIT: (09/03/15)

The Road test is now complete and I have some more blog entries and a review of the kit. I also ended up doing a couple of side projects and wrote a scheme of work for the Time Lapse Crystals project.

Part 3: Home Education Project

Part 4: Summary

Review

Scheme of Work

Side Project 1: Visual-Pi-ser

Side Project 2: Snow Timelapse


The Roadtest was a good opportunity to experiment with the RPi camera module and I enjoyed the chance to try something different. The time lapse photography was a good way to combine science and computing and also produce some beautiful results. I have included one of the example videos here. This one is probably my favourite, It was taken from below the crystals with lighting above as part of the home education project.

Conversations with computers using python

I had the idea of making the standard 'Hello World' introduction to programming a new language a little bit more interesting for my Y7 class.

The idea of the computer conversations and the recent Turing test success or (near success) by Eugene gave me the idea of getting the students to make a (vastly simplified) version of Eugene using Python. The plan would be to teach them some basic Python concepts like displaying information and filling variables based on user input and then maybe progress onto selection.

This would initially start as a very simple program with them entering their name and then including the name in the response. The students could then work up some complexity from there using more questions. The next step would be to switch things round and have the computer answer user question based on a list of pre-programmed responses.

The Plan

Introduction

Show the class a video by way of introduction to the test. Something like - Jeremy Clarkson Explains the Turing test or The Turing test, as described by Expect Labs CEO, Timothy Tuttle.

Explain the plan to create a basic chat bot that can have a basic conversation with the user.

Task 1- Hello World

Students to open IDLE and the a new window. They then create a basic 'Hello World' program and save and run.

e.g. 

print ('hello world!') 

Students to experiment changing hello world for whatever greeting they choose. (Yes they will probably make it say rude words!)

Task 2 - Talk to me

Obviously this is a pretty one boring conversation so we need to add in the ability for the user to input information.

e.g.

myName == input('What is your name?')

print ('hello ' + myName)

Students to experiment with this and then try adding more questions.

e.g.

myName == input('What is your name?')

print ('hello ' + myName)
myColour == input('What is your favourite colour?')

print ('That is amazing ' + myName + ', ' + myColour + ' is my favourite colour too')

Task 3 - Selection

To try and make the computer's responses a little more realistic it would be good if the response wasn't the same what ever you type so we can add add selection to change the response based on what is input.

This can start with a simple if else:

e.g.
myColour == input('What is your favourite colour?')
if myColour == 'orange':

    print ('That is amazing ' + myName + ', ' + myColour + ' is my favourite colour too')
else:
    print ('It is nice that you like ' + myColour + myName + ' I prefer orange')

This can then be moved on to add more choice using else if (elif):

e.g.
myColour == input('What is your favourite colour?')
if myColour == 'orange':

    print ('That is amazing ' + myName + ', ' + myColour + ' is my favourite colour too')
elif myColour == 'black':
    print (myName + ' your are strange ' + myColour + ' is not even a real colour, how can it be your favourite?')
else:
    print ('It is nice that you like ' + myColour + myName + ' I prefer orange')

Task 4 - Ask me a question

This basic idea can then be used to switch things around and let the students ask questions. This will only handle a pre-programmed list of questions and answers but completes the very basic conversation idea.

This can be added to the first code or used to start a new program. if in the same program some of the old variables can be used to add more interest.

First the computer needs to prompt the user to ask a question:

myQuestion == input('Ask me a Question?')
if myQuestion == 'how old are you':
    print ('I am 12, how old are you ' + myName + ' ?')
elif myQuestion == 'What is your name?':
    print ('My name is Simon')
else:
    print ('Sorry i didn't understand that question')

Students experiment with their own versions.

This is a fairly simple program so it only has one question opportunity and only a couple of possible questions. If students still have time then they could be challenged to find a way to give more than one question opportunity or add further questions and answers. Another idea is for the students to program a combination of questions for the student and opportunities to answer questions like in a conversation, they could also look at getting the answers from a text file and possibly they could use the text file to allow the program to 'learn' by storing answers given by students to questions and then use those to respond when it is asked that question later!


Plenary

Show some examples of students programs to the class and use them to highlight the key parts of the program.

Further Resources

Since writing this I have found a short scheme of work based on the turning test on the Rapspberry Pi website http://www.raspberrypi.org/learning/turing-test-lessons/. This 3 lesson scheme explains the idea of the Turing test and uses a speech module to have the robot speak to you.

Raspberry Why?

(1)

 

I have heard lots anecdotally about the use of Raspberry Pi in schools and there has been some talk about them “gathering dust in school cupboards”(2). and questioning along the lines of “Do UK schools really need the Raspberry Pi?”(3). In my own experience I have seen schools use them to “do programming” where they could be best to use the suite of 30 PCs they already have.

 

This forced use of technology for the sake of it is neither what the Raspberry Pi was intended for or based on good pedagogy. Eben Upton stated that the idea of starting the Raspberry Pi project was to get more children programming, but this is not how it will happen.

 

His vision was a playground for the children to experiment and even likens the Pi to a child's bike (compared to the family car that is the PC) the Pi is “owned by the child” and “if they break it it's not a disaster, they can walk”.(4) This ownership and experimentation is not the case in a classroom of Pis attached to PCs used to do “some programming”. All this is doing is making it take a little longer to get to the programming bit that they could do more quickly and easily by using the PC they are attached to.

 

This forced usage comes from a well meaning desire to give pupils some exposure to a device that has become a must have in computing education. It is a very admirable thing to be able to expose the young people in our care to a range of different devices, but we should understand fully what we are trying to do with them before running out and buying a class set.

 

This approach seems very common in education and it it is what has led me to create this blog. We see new technology and then try and find a use for it in the classroom. Some of these technologies would be much better not used at all when they are implemented in this way (how many interactive whiteboards in secondary schools are actually used interactively?).

 

For the Raspberry Pi, a device that was designed to engage and interest students in computing is in danger of becoming a tool to do the opposite.(5) Without using these devices to fulfil their potential we are doing our pupils (and the devices) a disservice. we have been presented with an amazing tool and we are wasting it because of a lack of imagination or lack of flexibility in the way we manage the learning process.

 

We should be using these Pi to enable experimentation and self led learning. It should be a tool that allows the students to answer for themselves the “what happens if I...” questions we get asked about computers all of the time. It gives us a platform where students can try things out. They can break things and no one is going to come shouting.

“If Something goes wrong it’s no big deal - you just swap out a new SD card, and your Raspberry Pi is factory-new again” (6)

 

Where the Pi will add most value is where students are able to set the agenda and pursue projects that interest them. A great example of this is Amy Mather(7) who got interested in the Pi and programming after attending events outside of school. She became interested in Conway's Game of Life and programmed a version on her Pi. She went through several versions and eventually added on an external LED display. If we can create an environment in our classrooms that will encourage this kind of exploration then we will be doing things right.

 

The Pi was not designed as a tool to sit in rows in a classroom with. but that doesn't mean we can’t use it effectively in a school. We just need to change our approach. I also recognise that we cannot completely change the paradigm within which we operate.

 

To move to a more productive usage of these devices we need to find ways to help teachers bridge the gap. There are several schemes that aim to do this. One successful scheme is Sonic Pi developed by Dr Sam Aaron. Sonic Pi is an open source programming environment designed to explore and teach programming concepts through the process of creating new sounds.(8) The software comes with a scheme of work that was jointly developed with Carrie Anne Philbin (Teacher, Author (9) and founder of Geek Gurl Diaries) . The Scheme of work is designed around the new Computing PoS and teaches programming concepts in an interesting and engaging way. As an introduction to the Pi it gives students a good grounding on some key programming concepts.

 

If we can take this sort of scheme as a start point then find ways to allow students to experiment with less directed projects then I think we are getting closer to utilising this tool to it’s potential. Where people have allowed this experimentation in schools (mostly as extra curricular activity) there have been some amazing projects. Students have created robots, wearable devices and even sent their creations into space (well nearly).(10)

 

(11)



For me the ultimate utilisation of the PI would be some form of introduction and then cross curricular projects where students can be creative and make things for themselves. It would be even better if students had ownership of the devices and products. We should aim to create a space where students contribute ideas and expertise to their peers, where we could guide and direct rather than dictate we will be able to help to foster pupils natural enthusiasm. We should aim to create mini Raspberry Jams in our classrooms.(12)

 

This approach also meet the demands of the National curriculum, the Computing PoS explicitly mentions undertaking creative projects using a range of devices.(13)

 

As we are limited in our time and resources we need to think about what we can do to make the devices more classroom friendly. There are lots of products available aimed to help us to do this. Teachers worried about the robustness of the devices can find a myriad of cases designed for the Pi. My particular favourite is the Pimoroni Pibow it’s robust construction is ideal for school use. It even comes in a range of colours from Rainbow to Ninja. I especially like the fact that it does not hide the Pi away inside an opaque box.

 

Where we are limited by time we need to look at premade kits to add on to the PI to allow the physical computing elements to be created quickly Products such as Buzz box are the start of these but there is still work to be done. The system allows consists of modules that can be linked together to create a diverse range of products.(14) This modular approach means that devices ranging from a simple calculator to a Robot of physiological monitoring device can be built. These ready made plug and play additions can reduce the time it takes to put together a working prototype, allowing pupils interest to be maintained in the early stages of a project where failure or limited activities can be demotivating.(15)

We don't need to rely on commercial suppliers we can add some structure to give students a little direction. Provide our own kit of parts that they can experiment with until they are ready to fully strike out on their own. We can also look to our colleagues in technology to see how they approach creative "maker" style projects, they have been doing this for years. We should look at what they do best and steal it for use in our classrooms. Even better if we can work with them to collaborate on work building student led projects.

 

Educational suppliers are beginning to catch on to this approach and when visiting the BETT show I found a supplier already offering Raspberry Pi Project kits for use in the classroom. The kits range from breadboards and components to kits with units of work. As more teachers take this approach the range of equipment available to support us will also increase making it an easier path to follow.

 

I think the Raspberry Pi is an awesome piece of hardware. It is already really great used in the hobbyist context where personal interests are pursued. I think it will also be great in the classroom one we get over the “wonder device”  stage where every school has got to have them without a lot of thought on why. We should be looking to see what new technologies can offer educationally rather than looking for places to shoehorn them into lessons just for the sake of it.

 

---

References:

(1) <http://www.raspberrypi.org/wp-content/uploads/2011/07/7513051848_9a6ef2feb8_o.jpeg>

(2) Shona Ghosh. "Raspberry Pi "gathering dust" in schools | Education | News | PC Pro." 2014. 15 Jan. 2014          <http://www.pcpro.co.uk/news/education/386302/raspberry-pi-gathering-dust-in-schools>

(3) "Bash Street bytes: Do UK schools really need the Raspberry Pi ..." 2012. 15 Jan. 2014                                    <http://www.theregister.co.uk/2012/11/27/feature_raspberry_pi_in_schools/>

(4) "Bash Street bytes: Do UK schools really need the Raspberry Pi ..." 2012. 15 Jan. 2014                                    <http://www.theregister.co.uk/2012/11/27/feature_raspberry_pi_in_schools/>

(5) "About us | Raspberry Pi." 2012. 15 Jan. 2014 <http://www.raspberrypi.org/about>

(6) Upton, Eben, and Gareth Halfacree. Meet the Raspberry Pi. Wiley. com, 2012.

(7) "Raspberry Jamboree 2013: Amy Mather - Conway's ... - YouTube." 2013. 15 Jan. 2014                                      <http://www.youtube.com/watch?v=a35XINnYFtA>

(8) "Sonic Pi." 2013. 15 Jan. 2014 <http://www.cl.cam.ac.uk/projects/raspberrypi/sonicpi/>

(9) "Adventures in Raspberry Pi: Amazon.co.uk: Carrie Anne Philbin ..." 2013. 18 Jan. 2014                                    <http://www.amazon.co.uk/Adventures-Raspberry-Carrie-Anne-Philbin/dp/1118751256>

(10) "High Altitude Ballooning, sixth-form style | Raspberry Pi." 2013. 16 Jan. 2014                                                    <http://www.raspberrypi.org/archives/4390>

(11) <http://www.raspberrypi.org/wp-content/uploads/2013/07/vlcsnap-2013-07-05-19h11m22s59.png>

(12) "#RaspberryJam | the global community of events for enthusiasts of ..." 2012. 16 Jan. 2014                                  <http://raspberryjam.org.uk/>

(13) "National curriculum in England: computing programmes of ... - Gov.UK." 2013. 16 Jan. 2014                              <https://www.gov.uk/government/publications/national-curriculum-in-england-computing-programmes-of-study/national-curriculum-in-england-computing-programmes-of-study>

(14) Callaghana, Vic et al. "Putting the Buzz Back into Computer Science Education." Workshop Proceedings of the 9th International Conference on Intelligent Environments 26 Jul. 2013: 454.

(15) Callaghan, Victor. "Buzz-Boarding; practical support for teaching computing based on the internet-of-things." The Higher Education Academy-STEM (2012).

(16) "Raspberry Jamboree 2013 Panel Discussion ... - YouTube." 2013. 15 Jan. 2014 <http://www.youtube.com/watch?v=1cqc0XdYezM>

(6)