Sometimes what you need just doesn’t exist. And when you’ve got stuff to blow up, well…
Whenever someone or something in a movie needs to blow up or get shot, a remote controlled firing system is used. Since the firing system can’t be seen on camera, it needs to be small so it can be easily hidden. Apparently the commercial systems you can buy may or may not be small enough. They might be, like, two or three times bigger than they need to be. That was the position Daniel Arvidsson and David Jensen found themselves in. Thanks to the Arduino, and a lot of experimentation, they produced a small open source squib firing system (but they also made it modular so it can do more than just fire squibs).
What are your names and backgrounds?
- Daniel: My name is Daniel Arvidsson and I’m a former glass worker. 2004-2005 I attended a year of film study at a folk high school, after the school I got into pyrotechnics and SFX. That’s the main reason why the idea of an wireless firing system came up! Now a days I have an ordinary job and do some SFX in my spare time and of course I’m developing fireCrow v2.0 😉
- David: And mine is David Jensen, I’m a software developer and sort of a nerd. Bearded nerd. Not the big guru beard though. I’ve got two small kids, a wife and a house, no dog.
Did you have any engineering experience before you started?
- Daniel: Hardly no electronic experience at all to start with.
- David: About a year before we started I heard about something called the “Arduino”, bought one and started playing with it a bit. Prior to that, no experience at all. I did know how to program though. But not C/C++.
What made you decide to open source the project?
- Daniel: It’s a congenial way to make stuff and I like the idea of a contributing to a lifestyle where you build up a community; where everyone can help or be help without paying for support and updates.
- David: I’m a big fan of free software and a long time Linux user. I wouldn’t have found my way into electronics if it wasn’t for open hardware, especially the Arduino, making it easily accessible and fun, so I felt it was natural that whatever we did should be open hardware and open source.
Did you choose one particular license over others? Why?
- Daniel: TAPR – because it’s created by people who mainly makes wireless applications. I thought our system fitted that description well.
- David: GPL3 for the software since it has copyleft clauses that protects against being engulfed into a proprietary project. Also, copyleft licenses spread more freedom into the world.
Were there any tools/resources that were vital to your success?
- Daniel: I use Cadsoft Eagle to make the schematics and PCB design, and we’ve used the Arduino as a development platform for the remote control.
- David: We use a port of the Arduino library in the firmware to ease development, without it it would take a lot more time. GCC, avrdude and gedit for development.
Could you suggest one really important skill people should learn first?
- Daniel: Only to be patient and accept that it will take time if you don’t know what you’re doing to start with. Of course it helps a lot to have basic knowledge of electronics (and coding)!
Did you ever make a major shift in the direction of the project? Why?
- Daniel: First the pyrofyro was only a 2 channel firing system, then it became a MCU board (the fireCrow). Our idea was to get it out to a broader range of users and to make it easily accessible for Arduino people. Mainly because there’s already a great community with a lot of coding examples and help to get. Pyrofyro became the name of plugin cards (2, 4, or 6 channels) dedicated to firing pyrotechnics. We also have plans to fork the MCU board into a “firing system” fork with intergrated transceiver and an “Arduino-ish” fork (same as now)
- David: The change to a modular system also interested me since I don’t have a license to blow things up 🙂
How much of the project was individual effort and how much was social?
- David: If by individual we count the both of us you could say that most of the effort right now is individual. But it builds upon community efforts like the Arduino library. We wouldn’t be able to build it otherwise.
- Daniel: Also, in the beginning I got some help from electronic forums and googling the net about things that I didn’t understand, but otherwise no.
Do you plan on selling anything when you’re finished?
- Daniel: Yes, hopefully we’ll be able to sell kits or even a finished product. The most difficult part is to get a reasonable price, because there’s no economy to buy enough components to reduce the cost per piece. Maybe if we get founding somehow 😉
What do you think about open source as a philosophy? As a strategy?
- David: As stated above I love free software, I think that as a philosophy open hardware and free software gives us creativity and power as a community to change the world. As a business strategy for software I believe it’s the future, everyone should do it. Open hardware as a business strategy is a bit different though, but there are business doing well. It will be interesting to see what the future holds.
- Daniel: I agree with previous speaker! 😉
In your wildest dreams, what would be open sourced next?
- David: Totally open hardware and drivers for the next Nexus Android phone, with easily accessible connectors.