Archive for the ‘Hacks’ Category
[Via: The Naked Espresso]
[Via: The Naked Espresso]
Julien Bayle is a digital artist and technology developer, and his work is an excellent starting point for anyone interested in the DIY man-machine interfaces.
Back in 2008, Julien created a clone of the Monome, a control surface consisting in a matrix of leds and buttons whose functioning is defined by software. It was called Bonome and RGB leds were used, instead of monochromatic leds of the standard model. Here are the instructions to build it.
Some time later, inspired by the DIY controller used by Monolake, Julien decided to build its own Protodeck to control Ableton Live.
Recently I stumbled upon his post titled “Arduino is the Power” and I discovered that Julien has started writing a book about the Arduino platform. So I thought that regular readers of the Arduino Blog would welcome an interview with this interesting guy. And here it is!
Andrea Reali: Tell us something about you.
Julien Bayle: I’m Julien Bayle from France. I’m a digital artist and technology evangelist. I’m inside computers world since my dad bought us a Commodore 64, around 1982.
I’m working with music softwares since the first sound-trackers and I began to work with visuals too with my Amiga 500, using some first POV-like softwares.
I first began by working as an IT Security Architect by day, then I quit to be only what I am today and especially to be really free to continue my travel inside art & technology.
I’m providing courses & consulting & development around open-source technology like Arduino, java/processing but also & especially with Max6 graphical programming framework which is my speciality. Max6 is really an universe itself and we’d need more than one life to discover all features. As an Ableton Certified Trainer, I’m still teaching that a bit.
All technology always provides tools to achieve art. I guess my path comes from pure technology and goes to pure art.
Nice Grasshopper-to-Arduino plotter hack from FablabTorino maker Pietro Leoni, a collabotator at Carlo Ratti Associati studio in Turin. We’d love to see code & sketches online soon, as much as a second edition of the plotter.
In his blog, Marc from Robot Dialogs presents a very nice hack involving a IBM Selectric II typewriter: by means of an Arduino board and several solenoids, the typewriter can be successfully connected to a computer to emulate a vintage teletype.
The complete story can be found here, together with several videos about its development.
[Via: Hack A Day]
It is a recent trend that hardware too has entered the hackathon scenario. Here are interesting excerpts from his honest account!
A few months ago 3 friends and I participated in the facebook hackathon at UBC. It was a 36 hour, redbull-fueled affair in which quite a few teams participated. We won. I’m not telling you this story to brag, I want to share with you what I learned. In all honesty, I was shocked we won, but I think that sticking to a couple of principles helped:
1. Don’t compete with your second best arsenal
2. Solve a real problem
3. Breadth instead of depth can pay off
Yes, you’ve heard this advice before and there are exceptions to every rule… I’m just sharing my personal experience.
Our team consisted of a designer, a biomedical engineer (who didn’t write a single line of code), a CS student (without a doubt the most “qualified” of all of us), and myself (a Political Science grad). I was the only non-engineering-educated person in the room. One essential lesson I have learned over and over in life is that it is futile to compete on a metric that you cannot possibly be the best at. Don’t compete with your second best arsenal. You need to find the edge that nobody else will think of, or where nobody else can be. If the competition can outspend you, outmanouever them. If the guy at the bar is better looking, be funnier. And if most of the guys in the room have PhDs in CS, go for hardware?
The night before the hackathon I picked up an arduino microcontroller, a few LEDs, some alligator clips, and a breadboard. I didn’t really know how things would come together, but I had spent some time hardware hacking and I was really interested in physical computing. I also figured that most of the guys in the room wouldn’t be thinking about hardware (this was a facebook hackathon, most people were looking up the Open Graph API). I hoped hardware would be our edge, and as it turns out, it was.
After a bit of brainstorming and chinese food we agreed to build Locksmasher – an arduino powered unlocking mechanism that would handle authentication through the Open Graph API. We wanted to create a way to grant one-time access to facebook friends that need to get into your house.
Half an hour into our brainstorming, one of my team members had to leave the hackathon to let a friend into his house. This event sparked the idea of locksmasher and outlines my second point – solve a real problem. A craft for a craft’s sake can often be futile. There are definitely exceptions to this, but most of the time, start with a defined problem and apply your craft, instead of the other way around. The judges loved that they could personally relate to the problem of needing to let someone into their house when they weren’t home.
Our hack was very simple – it was nothing more than a glorified switch that talked to facebook. Graeham (our biomedical engineer) hooked up an old door lock to the arduino for our demo. Yazad (the CS student) and I wrote a NodeJS server to talk to facebook. We spent most of our time dealing with authentication, a problem that could have been solved in a few hours by a better hacker who knows the facebook API well. In the meantime Vince (our designer) made everything look very beautiful. This brings me to my last point point, sometimes breadth is better than depth. I want to credit a tremendous amount of our success to Vince’s design work and Graeham’s hardware. By the end of the 36 hours, we had addressed a little bit of everything.
Most of the hackers in the room built some very elegant projects; machine learning algorithms, recommendation algorithms based on your friends likes, data parsing applications. However many of the projects were elegant for elegance sake and didn’t solve a pain point that the judges could relate to. Furthermore, they didn’t look at the whole package (arguably not necessary for a hackathon but I certainly think our sleek UI helped win over the crowd).
It easily highlights arduino’s adaptability to hooking with various technologies. It truly comes out as the bridge between hardware and software.
The project demo lies here.
Any hackathons worldwide in which our readers have used their Arduino? Please do link the demo or your blog 🙂 We would love to read!
Moppy is a musical floppy controller program. By using an Arduino UNO as a translator, you can command an array of floppy drives with a musical keyboard. The head on each floppy drive is controlled by a stepper motor which will put out sounds when driven at the right frequency.
Here is a link to the Moppy project page.
Enjoy your musical floppy drives!
Using an Arduino board with a data logging shield that holds an SD card for storage, an accelerometer on the front fork and some method of recording wheel speed, it’s possible to collect data about your bike ride. Then, when at home, a Python script captures the data dump and graphs it.
Wdm006 also says:
I’m in the process of building an ABS and active suspension system for mountain bikes. The first task after initial modeling and design work was to gather a lot of data for more specific design.
Original post can be read here.