Building Hardware Following Open Source Principles
Since the beginning of this year we at Institute IRNAS and Fabrikor fabrication lab have started several exciting collaborations with organizations from around the world, helping them bring to life useful products by providing our expertise in open hardware development and manufacturing.
This blog post serves as an introduction into a series of posts on open hardware development collaborations coming up in the following months, where you’ll be able to learn how we integrate and use open technologies to build new useful and open projects in practice, as well as follow the progress updates of these open projects, from our KORUZA wireless networking solution, citizen science environment monitoring devices, endangered species monitoring and conservation platform to open medical equipment.
We are taking the projects from the idea and research stage to scale manufacturing. To better explain our work flow we prepared the following diagram, where you can see how we work as well as how we’re applying open source principles along the way.
Choosing our default style of working when developing a new product — by open source principles — benefits all parties involved as transparency holds everyone accountable and aligned with agreed values. And it is not only beneficial for us and our clients but for broader community as well.
Openness is what helps us move fast in all stages of the development process.
The initial research phase, when we test an idea, check its feasibility and try out a number of solutions is best done when we can peek into a number of existing products and solutions, learning from each one of them to form our solution. When devices are open hardware, it becomes almost trivial to learn from them.
Building an operational prototype of hardware is an exciting step, significantly empowered with an open hardware systems ranging from Arduino, Raspberry Pi and a bulk of different small modules available online. This immense library of modular solutions, which enables rapid prototyping, is sometimes tedious due to poor documentation of some systems, but significantly faster and more cost effective then other options.
Product development as such is a detailed process when aiming for product manufacturing, having an insight into how existing products are built enables the discovery of best practices, speeding up the development and educating developers in the process.
Also for the after sales activity and users support openness proves itself as beneficial since it leads to direct understanding of the user and makes serviceability of the devices easier, but most importantly, empowers the communication with the developers to collaboratively identify the improvements, changes and features for the upcoming versions.
In the series of blog posts on KORUZA Pro development you can learn about the design choices we made for our new robust telecommunication solution. In KORUZA Pro we have successfully integrated several open source technologies, for example — Arduino based modules for the Koruza driver, as well as some standard and commonly available parts — for instance commercially available binoculars, which we customized for our need and built cost effective aiming mechanism with camera module.
Of course, we are keeping the project well documented with all the source files published on Github platform. (You can learn more on how we’re using Github for documenting hardware design in irnas-hardware-workflow repository.) Similarly as in the previous version of Koruza, we are also preparing complete manuals for efficient use of KORUZA Pro since the first batch is about to come out of production and will be delivered to the first users in the upcoming weeks.
Openness is not only empowering development and manufacturing process but it is also bringing very practical outcomes for our customers and their final users.
Openess comes together with total ownership allowing full use and repair of existing products as a complete insight into operation is available.
It ensures the devices are future proof, since they are are designed and documented such that users are empowered to innovate, explore and upgrade them outside the original specification. The lifespan of devices is extended, their reuse encouraged and their open hardware documentation an enabling component in communication between all parties involved.
It also simplifies collaborative design, bridging the gap between the development, manufacturing and use of a device, enabling evolution of the product to be optimal for everyone involved.
We are finishing this introduction with a sneak peak into one of the projects we’re working on. Together with The Crees Foundation, the Zoological Society of London and the Arribada Initiative we are building a monitoring network on a very particular and important location of our planet. More soon. Stay tuned!
This project was originally posted on the official blog of Institute IRNAS.