Day: September 27, 2018

Today at the Open Hardware Summit at MIT, OSHWA, the Open Source Hardware Association has announced a huge revision to the Open Hardware certification process. The goal here is to design a better platform for creating Open Hardware.

While all hardware already certified as Open Hardware will remain Open Hardware, this revamp of the ‘hub’ of the certification process is greatly improved. There’s a new website. There are learning modules telling everyone what it means to be Open Source hardware. There are community examples — real-life walk-throughs of projects that have already been created. There’s a streamlined certification process, and an improved listing of Open Hardware projects.

But Why A Certification Program?

While Open Source in the world of software is easily defined, it is effectively a hack of copyright law; all software is closed by default, and an Open Source software license is merely that; a license for anyone to use it, with the various restrictions and philosophical battles. Hardware, on the other hand, is big-O Open by default. The code used to program an FPGA is covered by copyright, but the circuit itself isn’t. The firmware on your Arduino project is covered by Open Source software licenses, but the physical implementation of your Fritzing picture isn’t.

In the absence of a legal framework to truly make an Open Hardware license work, the only other option is a certification program. The current Open Source Hardware certification program launched in 2016, and has since seen hundreds of projects certified from dozens of countries. It is, by any measure, a remarkable success. The people who make hardware are certifying that their work complies with community-set standards, and all of these projects are registered.

The New, Improved Interface for the Certification Program

While the core of the Open Hardware Certification program hasn’t changed, the user interface — the ‘killer app’ of a directory of Open Hardware projects — has. According to the press release put out by OSHWA ahead of the announcement, “The revamped website consolidates a broad range of information about open source hardware onto a single site. To maximize comprehension for people pursuing certification for their own hardware, important documentation and licensing concepts are illustrated with specific existing examples from the registry. An improved directory and search function makes it easy to find hardware that matches a broad range of criteria.”

Compared to last week’s version of OSHWA’s website, this is a huge improvement. Now, you can easily find information about what it means to make Open Hardware. The complete directory of Open Hardware projects isn’t just a spreadsheet on a webpage anymore, you can actually search for projects now. This is a huge improvement to the Open Hardware certification program, and we can’t wait to see how this new platform will be used.

It seems a simple enough concept for anyone who’s spent some time hacking on open source code: once you release something as open source, it’s open for good. Sure the developer might decide that future versions of the project close up the source, it’s been known to happen occasionally, but what’s already out there publicly can never be recalled. The Internet doesn’t have a “Delete” button, and once you’ve published your source code and let potentially millions of people download it, there’s no putting the Genie back in the bottle.

But what happens if there are extenuating circumstances? What if the project turns into something you no longer want to be a part of? Perhaps you submitted your code to a project with a specific understanding of how it was to be used, and then the rules changed. Or maybe you’ve been personally banned from a project, and yet the maintainers of said project have no problem letting your sizable code contributions stick around even after you’ve been kicked to the curb?

Due to what some perceive as a forced change in the Linux Code of Conduct, these are the questions being asked by some of the developers of the world’s preeminent open source project. It’s a situation which the open source community has rarely had to deal with, and certainly never on a project of this magnitude.

Is it truly possible to “take back” source code submitted to a project that’s released under a free and open source license such as the GPL? If so, what are the ramifications? What happens if it’s determined that the literally billions of devices running the Linux kernel are doing so in violation of a single developer’s copyright? These questions are of grave importance to the Internet and arguably our way of life. But the answers aren’t as easy to come by as you might think.

The past few years have been all about electronic conference badges and this year is no different. Right now, we’re setting up at the Open Hardware Summit at MIT, and this year’s badge is nothing short of extraordinary. It’s a WiFi and Bluetooth-enabled e-paper badge, individually programmed for every attendee. The 2018 Open Hardware Summit badge is a work of art, and it was all created over on hackaday.io.

This board is based on the ESP trINKet designed by [Mike Rankin] with additional hardware design from [Alex Camilo]. The badge is based around the ESP32-wroom-32 module with a 2.13 inch e-paper display with a resolution of 250 x 122 pixels. To this, the badge adds an I2C accelerometer and support for add-ons. There’s also pads for an SD card holder — a soldering challenge, if you will — and few additional pads for bits and bobs.

But a badge is nothing without software, and that’s where this really gets good. The ESP32 module is a powerhouse, capable of emulating NES games or serving as a file server. Here, the stock configuration of the badge is rather simplistic: you can start a WiFi AP, log onto a web page, and change the name displayed on the badge. You can also start an FTP server, which is where things get really fun. Drop an application on that FTP server, and you can run Micro Python.

The badge is great, but the programming jig is awesome

The boards were made through OSH Park, and Screaming Circuits took care of the assembly. Anyone who has ever built a badge will tell you it isn’t the assembly that gets you — it’s the programming and provisioning. This is especially true since the Open Hardware Summit badge is distributed with the attendee’s names already preloaded. That’s a few hundred badges, all with unique firmware. This is a nightmare by any definition.

However, there’s always a good solution to a problem, and [Drew] from OSH Park showed me the best programming jig I’ve ever seen during the Summit pre-game at Artisan’s Asylum.

What you’re looking at is a 3D printed box loaded up with a touch-screen display, a Raspberry Pi Zero W, and a few pogo pins. This Raspberry Pi does all the heavy lifting by connecting to the Internet, pulling down the current version of the firmware, and loading that firmware onto the badge. There are a few more options thanks to the touch-screen interface, including provisioning all the badges with the names of the attendees — this can be done by reading a list of attendees and uploading the next one to the badge in the jig. All of this is wrapped up with a nice laser-cut cover that securely holds each badge exactly where it needs to be for the pogo pins to make contact.

This is, without question, the best programming jig I’ve seen. Any badge makers out there should take note: this is how you program a few hundred badges. The badge, itself, is great and just as this post is published there will be hundreds of eager hackers futzing about with this remarkable piece of hardware. If you want to check out the current progress of the badge hacking, check out the updates on Twitter

Although it’s not an idea that has yet trickled down to $200 printers drop-shipped from China, one of the most innovative ideas in the 3D printing world in the last few years is putting plastic down on a conveyor belt. Yes, MakerBot was doing it back in 2010, but we’re not going to talk about that. Printing on a conveyor belt instead of a static bed allows you to easily print multiples of an object autonomously, without any human interaction. If you’re really clever, you could rotate the hot end 45° and build a piece of plastic that is infinitely long, like the printer [Bill Steele] built, the Blackbelt, or ‘the CAD files might exist somewhere’ Printrbot infinite build volume printer.

At this year’s World Maker Faire, we didn’t see an infinite printer, but we did catch a glimpse of an idea that could reliably take 3D printers into production. It’s a Multiprinter Autonomous 3D Printer, designed and built by [Thomas Vagnini].

The idea of using 3D printers for production and manufacturing is a well-studied problem. Lulzbot has a heated room filled with printers they use to manufacture all their machines. Prusa’s manufacturing facility is similarly well-equipped. However, both of these setups require helper monkeys to remove a part from the bed and set the machine up for the next print.

Instead of a strictly manual process, [Thomas]’ machine uses a sort of cartridge-based system for the printing bed. The glass beds are stored in a cassette, and for the first print, the printer pulls a bed onto the heated build plate through a system of conveyors. When the print is finished, the part and the bed ar fed into a rotating cassette, where it can be removed by a tech, prepped for the next print, and placed back in the ‘bed feeder’. It’s a system that brings the manual intervention cycle time of a 3D printer down to zero. If you’re producing hundreds of parts, this will drastically speed up manufacturing.

While it is a relatively niche idea, this is a very well-designed machine. It’s all laser cut, uses core-XY mechanics, and with the right amount of tuning, it does exactly what it says it will do. It’s not for everybody, but that’s sort of the point of manufacturing parts on a 3D printer.

Is it a badge? Is it a watch? Well, it’s [Sarif’s] take on a wrist-mounted computer from the Fallout series, so you’re free to choose your own designation! We think the Brotherhood of Steel would be proud to have this piece of kit.

[Sarif] commenced the build after first getting their feet wet with the pipman, a watch inspired by Metro 2033 and Steins;;gate as much as Bethesda’s popular post-apocalyptic RPG. It features all the fruit – GPS, compass, a TV-B-Gone – and perhaps the coolest feature, long-since-deprecated bubble LED displays and flippy switches for that Altair-esque charm.

The build log is full of details, from the components used and the debugging battles involved in the journey. [Sarif] learned about using transistors, burning up a few along the way – some say setting the lab on fire is the quickest way to learn important lessons, anyway. On top of that, there were some software niggles but in the end, the watchputer made it to DEFCON 26 anyway!

Builds like this that start from limited experience and go deep into the trials and tribulations involved are an excellent way to learn about what goes into the average DIY electronics project, particularly when talking about embedded systems. And if you’re keen to check out the work of [Sarif’s] contemporaries, we’ve got a collection of all the awesome badges from DEFCON 26. Enjoy!