Open Source Hardware can be designed with both open and closed tools. While closed tools pose risks like vendor lock-in, many successful open hardware projects have been designed with non-open tools. Fully open tools that are gratis, libre, and use open standards provide the greatest benefits like longevity and ability for others to modify and build upon designs. As complexity increases, the availability of capable low-cost or free tools is declining. Improving open tools through sponsorship, standards, and contests can help speed innovation for open hardware.

1. Open Source Hardware...
What about the tools?
by Chris Gammell
Electrical Engineer
Founder of Contextual Electronics
Co-host of The Amp Hour Electronics Podcast

2. Outline
● What is open source hardware (OSHW)?
● Why do we do it?
● How do we design it?
● When will the tools improve?

3. A note about free
● "Free software is a matter of liberty, not price. To
understand the concept, you should think of free
as in free speech, not as in free beer." — Richard
Stallman
● We'll refer to the “free beer” example as “gratis”
and the “free speech” example as “libre”

4. Open Source Hardware Official
Definition
● Open source hardware is hardware whose design is made publicly available so that anyone can
study, modify, distribute, make, and sell the design or hardware based on that design. The
hardware’s source, the design from which it is made, is available in the preferred format for making
modifications to it. Ideally, open source hardware uses readily-available components and materials,
standard processes, open infrastructure, unrestricted content, and open-source design tools to
maximize the ability of individuals to make and use hardware.

5. Shades of gray in openness
● Closed hardware
● Open hardware, closed format files, closed tools
● Open hardware, open format files, closed tools
● Open everything

6. Comparing Open Source Hardware
and Software
● Closed hardware
– like having object code/executable only
● Open hardware, closed format files, closed tools
– Like having an encrypted library
● Open hardware, open format files, closed tools
– Like having all the necessary library with a expensive, closed
compiler (i.e. not GCC)
● Open everything
– Like having source code and using GCC or similar.

7. A practical test for openness of the
hardware
● “Can one other person in the world build what
you have built?”
● What about 10 people? 100? 1000?
● How much above BOM did it cost them?

8. Why do designers like OSHW?
● Sharing
● Giving Back
● Support
● Community
● Marketing

9. Why do users like open?
● Relational data (which parts go with which)
● Easy modification for new versions.
● Open hardware makes easier firmware/software
● Platforms upon which to build

10. Do the tools really matter?
https://www.flickr.com/photos/cityhunter12/2520752983

11. Especially given the reality

12. Some are going to modify and
advance your OSHW project
● Hard to track progress to an open source
platform over time when a variety of closed
source tools are used.
● Open tools and standards allows tracing a chain
back through GitHub or similar and viewing the
differences.

13. The design files are the
documentation as well

14. Levels of compressions
● Schematic to PDF
● Layout to gerbers
● Mechanical designs to STL

15. Are open tools the only way?
https://www.flickr.com/photos/chewbackski/11222467824

16. Of course not, OSHW already exists
● Many of which were designed and propagated
with non-open tools.
http://en.wikipedia.org/wiki/File:Arduino316.jpg

17. Tradeoff between usability and risk.
Usability Risk

18. What about gratis (freeware) tools?
● Usability:
– Non-open source, no cost to user.
– Often offered as an add-on or loss
leader for some other service.
● Risks:
– No guarantee of long term
availability.
– No guarantee of it always being
gratis.
● Example: LTspice
LTspice IV

19. What about freemium?
● Usablity:
– Non-open source, no cost to
user until a level is reached
inside the program.
● Risks:
– Projects that grow outside the
constraints impose necessary
costs for OSHW projects.
– Vendor lock in.
● Example: Cadsoft EAGLE

20. What about tools (non-gratis, non-
libre) with open standards?
● Usability:
– Can import/export a variety of
files.
– User could build applications
on top of data structure.
● Risks:
– Changing or closing of the
standard.
– Imported files often are kept at
an ongoing cost.
● Example: Upverter

21. Open (gratis, libre) Tools
● Usability:
– Can download for multiple platforms
– Have access to and ability to modify
source code or build separate versions if
necessary.
– Can retain source and build for any
platform in perpetuity.
● Risks:
– Build instability
– Loss of developer interest
– Changing formats
● Example: KiCad

22. The impact of commercial
involvement
● Open tools have the greatest chance at longevity
without vendor lock in.
● There is no “magic” part of the design file that
could be held ransom by a company.
● Tools available to all

23. The impact of rising complexity
● The set of low-cost/no-cost tools capable of doing
increasingly complex boards dwindles
– i.e. BeagleBone Black vs Arduino
● A common, open standard and open source tools
will speed innovation by allowing building on top
of existing work.
● Many of these tools are available today (with
increasing ease of use)

24. Electrical Examples
● CAD
– KiCad
– GEDA
● Other tools
– Berkeley SPICE
– Octave

25. Mechanical Examples
● CAD
– OpenSCAD
– FreeCAD
– LibreCAD
– Blender
– Inkscape (2D)
● CAM
– PyCAM
– OpenSCAM
– BlenderCAM
● Machine control
– LinuxCNC
– GRBL

26. When will the tools improve?
● Sponsored development, such as at CERN
● Software companies moving into hardware
(Autodesk)
● Premium support models (ie. RedHat for
hardware)
● Converging hardware and software.
● Contests encouraging openness.

27. Summary
● Do the design tools HAVE to be open/free for
Open Source Hardware? No.
● Improving the availability of open and accessible
design tools will help to speed innovation.

28. Questions?

29. Questions?