Skip to main content

Getting back up to speed with Arduino

We have been working on devleoping a new lab space at North 51 recently with a view to trying out some new technology and messing about with different interaction ideas. 

One little bit of kit I am very enthusiastic about is the Arduino. Most people I have worked with haven't had the opportunity to play with one so we bought one in and a load of electronic bits and bobs to play with. 

On Tuesday evenings we now have a Geek night after work. The plan is to play with technology and just see what comes from it. This Tuesday was fairly quiet as it was a little late notice so me and my friend Jon decided to use it as a chance to get back up to speed with the Arduino. 

We started with the blinking an LED (the most basic but always satisfying) and then moved onto blinking the LED at a pace determined by an LDR. 









With that success we moved onto setting the Arduino up as a little server and plugging it into a switch. We then plugged laptops into the switch and were able to use the Arduino as a Chat server. 

After that, we plugged in a little speaker and used the laptops to send commands to the Chat Server that played a different note based on the command. With this we then able to talk to each other on the chat server and agree a tune that we built up over two different computers. All in all very cool. 

We have some more people coming next week and I hope we can build on this. After some pizza we had a brainstorming session and came up with some really cool projects that we are going to start messing about with. Next on our list is remote data collection using sensors and a GPRS shield / module for the Arduino!

Exciting times! 


Comments

Popular posts from this blog

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second

Accessing the UI Thread with Tasks in F#

I have a Windows Forms program written in F# that can deploy a code base to n number of sites at once (you select the sites you would like to deploy to and it goes off and completes a number of tasks (backing up current sites, various unpacking and moving of files etc... ). Once you start it, it begins it's merry journey and begins to update the UI with what has happened. At the moment this method of updating the UI is not pretty because the threads I am doing the work on can't update the UI so I perform some fiendery to make that happen (don't ask). I knew there was a better way using some newer .NET features but I just hadn't got round to having a fiddle yet. I have now found that if you use the built in Task class but break your code up in a nicer way and then chain the tasks together you can then pass the correct context into the task that you want to talk to the UI. Here's a little script to give you a feel for it. You can press the "start" butt

NESTA - Next Gen.

via nesta.org.uk Following on from an article on the BBC about Raspberry Pi, this next gen report has some interesting findings. The scariest stat which I picked out from the BBC website was "out of the 28,767 teachers who were awarded Qualified Teacher Status... in 2010, only three qualified in computing or computing science as their primary qualification" Having worked as a computer science teacher for a year in a school that was a specialist in Computing I can concur that the uptake in Comp Sci was woeful. 2 Students for A2... The other teachers backgrounds in Computer Science was also fairly woeful (most knowing a bit about Office but still a paltry amount even about that). I couldn't speak for my counterpart that I was covering however. I suspect they were fairly up on things. All in all what kills me is that Computer science is not a secondary level subject. Areas are often covered, a little in IT, a little in DT subjects (if kids choose Systems and Contr