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

Post a Comment

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.
Post a Comment
Read more

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi
Post a Comment
Read more

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
Post a Comment
Read more