Skip to main content

EEG - Recording brainwaves and pushing them to a live web feed.

Last Tuesday our EEG device arrived. I think I almost exploded with excitement. The device itself is very cheap so we don't expect particularly accurate results but it does work and it proves a concept for us more than anything else.

This is the device http://www.amazon.co.uk/Brainwave-Starter-incl-MindWave-Mobile/dp/B00B1B1H68/ref=sr_1_1?ie=UTF8&qid=1383037186&sr=8-1&keywords=mindwave it's very basic but it does have a decent SDK with it that you can access in a number of ways so you can't complain.

There was a different model that I was interested in that cost around £800.00 for the device but it transpired that they wanted a completely insane amount for the SDK (around 10k) so we left them well alone.

Initially our plan was just to make sure we could get the readings out of the device which involved pinvoking a dll but the documentation was fairly good. We got that up and running after some fuss with the comm ports etc...



Once that was done we made a little site using SignalR. This worked really nicely as you can create a client using the SignalR.Client library that then fed real time information to the SignalR site. This site then pushed the data as a live feed using WebSockets (it falls back to other things like long posting if your browser doesn't support websockets). 

All in all we had the SDK and the live feed up and running in around 2hrs so last Tuesday night was one of our most successful sessions yet!

I think our next plans are to create a nicer looking signalR website to display the waves and release it onto Azure so people can monitor me and then I then I'd like to work out how to hook the device up to mobile devices so I can track the waves on the move. 




Comments

Popular posts from this blog

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

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