Open source hardware has been around since the early days of electrical & electronic modules and subsystems. Arguably, my first office mate, Evan Colton, designed an early piece of open source hardware, the first sucessive approximation analog to digital converter. Whether or not we intend it, designs get copied all the time. My first hardware design, a 100MHZ video digital to analog converter with unprecidented low glitch energy. Within 6 months, a west coast company cloned the design, which I considered to be the highest flattery a designer could receive. Ironically, my company sued them for copyright on the data sheet (which they were careless about copying), and won. Today, the biggest difference in open-source hardware is in the area of programmably alterable circuitry, and the accompanying open-source code for popular configurations.
True! I've heard many people refer to open source hardware as a return to the free data roots of innovation. We used to share our tools freely! However, we also used to be paid primarily for skills, mass manufacturing changed that.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.