Stackable Open Source 3D Printer Enclosure

December 11, 2019 by Tom Nardi 20 Comments

One of the unfortunate realities of desktop FDM 3D printing is that environmental factors such as ambient temperature and humidity can have a big impact on your results. Even with the exact same settings, a part that printed beautifully in the summer can warp right off the bed during the winter months. The solution is a temperature-controlled enclosure, but that can be a daunting project without some guidance. Luckily, [Jay Doscher] has spent the last few months designing a very impressive enclosure that he’s released to the community as open source.

While we’ve seen no shortage of DIY printer enclosures over the years, they tend to be fairly lightweight. But that’s not the case here. Obviously not wanting to leave anything to chance, [Jay] designed this enclosure with 2020 extrusion and aluminum side panels. You could probably sit on the thing with no ill-effects, which is good, since he also designed the enclosure to be stackable should your print farm need to expand vertically.

Of course, there’s more to this enclosure than just an aluminum box. It’s packed with features like an integrated Raspberry Pi for running Octoprint, internal and external environmental monitoring with the Adafruit SHT31-D, and a Logitech Brio 4K video camera to watch the action. While not currently implemented, [Jay] says he’s also working on an internal fire suppression system and a fan controller system which will circulate air inside the enclosure should things get a little too toasty.

The enclosure has been designed around the ever-popular Prusa i3 MK3/S, even going so far as to relocate the printer’s display to the outside so you don’t have to open the door to fiddle with the settings. But adapting it to whatever rig you happen to be running shouldn’t be a problem. Though admittedly, perhaps not as easy as adjusting an enclosure made out of metal shelving.

Continue reading “Stackable Open Source 3D Printer Enclosure” →

An Open Hardware Laser Engraver For Everyone

November 6, 2019 by Tom Nardi 14 Comments

Right now, you can get a diode laser engraver on eBay for around $100 USD. That sounds like a deal, but it’ll probably use some arcane proprietary software, won’t be terribly accurate, and the laser itself will almost certainly be fully exposed. Of course there’s no shortage of DIY builds which improve upon this situation greatly, but unfortunately the documentation and instructions to replicate them yourself often leave a lot to be desired.

To get a safe and accurate laser platform into the hands of hackers everywhere, we need more well documented open source designs that are actually built with community in mind. Projects like the Engravinator from [Adam Haile]. This isn’t a one-off design with documentation thrown together after the fact, it’s a fully open hardware engraver with a concise assembly guide that’s built from 3D printed parts and readily available components. You’re free to source and print the parts yourself or, eventually, purchase everything as a kit.

The microwave-sized Engravinator is built from standard 2020 aluminum extrusion, and offers a workable area of 130mm x 130mm. There’s a hatch on the front of the enclosure for objects that are small enough to fit inside the machine, but the open bottom and handles on the top also allow the user to place the Engravinator directly onto the work surface. [Adam] says this feature can be especially useful if you’re looking to burn a design into a tabletop or other large object.

Outside of the aluminum extrusion and miscellaneous hardware that make up the frame, most of the other parts are 3D printed. Released under the CERN Open Hardware License v1.2 and distributed as both STL and STEP files, the printable parts for the Engravinator are ripe for modification should you be so inclined. The same goes for the DXF files for the enclosure panels, which will need to be cut out of orange acrylic with a CNC or (ironically) a laser.

Continue reading “An Open Hardware Laser Engraver For Everyone” →

Supercon Keynote: Dr. Megan Wachs On RISC-V

November 6, 2019 by Elliot Williams 28 Comments

Hackaday has open-source running deep in our veins — and that goes for hardware as well as software. After all, it’s great to run open-source software, but if it’s running on black-box hardware, the system is only half open. While software has benefited mightily from all of the advantages of community development, the hardware world has been only recently catching up. And so we’ve been following the RISC-V open-source CPU development with our full attention.

Our keynote speaker for the 2019 Hackaday Superconference is Dr. Megan Wachs, the VP of Engineering at SiFive, the company founded by the creators of the RISC-V instruction-set architecture (ISA). She has also chaired the RISC-V Foundation Debug Task Group, so it’s safe to say that she knows RISC-V inside and out. If there’s one talk we’d like to hear on the past, present, and future of the architecture, this is it.

The RISC-V isn’t a particular chip, but rather it’s a design for how a CPU works, and a standard for the lowest-level language that the machine speaks. In contrast to proprietary CPUs, RISC-V CPUs from disparate vendors can all use the same software tools, unifying and opening their development. Moreover, open hardware implementations for the silicon itself mean that new players can enter the space more easily, bring their unique ideas to life faster, and we’ll all benefit. We can all work together.

It’s no coincidence that this year’s Supercon badge has two RISC-V cores running in its FPGA fabric. When we went shopping around for an open CPU core design, we had a few complete RISC-V systems to pick from, full compiler and development toolchains to write code for them, and of course, implementations in Verilog ready to flash into the FPGA. The rich, open ecosystem around RISC-V made it a no-brainer for us, just as it does for companies making neural-network peripherals or even commodity microcontrollers. You’ll be seeing a lot more RISC-V systems in the near future, on your workbench and in your pocket.

We’re tremendously excited to hear more about the project from the inside, and absolutely looking forward to Megan’s keynote speech!

The Hackaday Superconference is completely sold out, but that doesn’t mean that you have to miss out. We’ll be live-streaming the keynote and all other talks on the Supercon main stage, so subscribe our YouTube channel and you won’t miss a thing.

Building An Open Hardware EBook Reader

October 31, 2019 by Tom Nardi 26 Comments

On the whole, hackers aren’t overly fond of other people telling them what they can and cannot do with the hardware or software they’ve purchased. Unfortunately, it’s becoming more and more difficult to avoid DRM and other Draconian rules and limitations as time goes on. Digital “eBooks” and the devices that are used to view them are often the subject of such scrutiny, which is why [Joey Castillo] has made it his mission to develop a open hardware eReader that truly belongs to the user.

[Joey] has been working on what he calls the “The Open Book Project” for a few months now, and he’s just recently announced that the first reader has been successfully assembled and powered up. As is usually the case, a few hardware issues were identified with this initial prototype. But it sounds like the device was largely functional, and only a few relatively minor tweaks to the board layout and components should be necessary before the hardware is ready for the masses.

An earlier prototype, using the Adafruit Feather

If you’re feeling a bit of déjà vu seeing this, don’t worry. The Open Book Project has taken a somewhat circuitous path to get to this first prototype, and [Joey] had previously developed and built the “eBook Feather Wing”. While they look very similar, that earlier incarnation required an Adafruit Feather to operate and was used to help refine the firmware and design concepts that would go into the final hardware.

The Open Book is powered by a ATSAMD51N19A processor with a GD25Q16 2MB flash chip to hold the CircuitPython code, and a microSD slot to store the actual book files. It also features support for audio output via a standard 3.5 mm headset jack, an RGB status LED, and expansion ports that tap into the I2C interface for adding whatever other hardware you can dream up.

One of the most interesting aspects of this Creative Commons licensed reader is the extensive self documentation [Joey] has included on the silkscreen. Every major component on the back of the PCB has a small description of its purpose and in some cases even a breakdown of the pin assignments. The idea being that it not only makes the device easier to assemble and debug, but that it can also explain to the curious user what everything on the board does and why it’s necessary. It’s a concept that makes perfect sense given the goals of the Open Book Project, and something that we frankly would love to see more of.

[Marc Juul] presented his work on a FOSS operating system for older-model Kindles at HOPE XII as a way to avoid Orwellian monitoring of the user’s reading habits, so it’s interesting to see somebody take this idea to the next level with completely libre reader hardware. Unfortunately none of this addresses the limited availability of DRM-free eBooks, but one step at a time.

Open Hardware Month Hack Chat

October 21, 2019 by Dan Maloney No comments

Join us on Wednesday, October 23 at noon Pacific for the Open Hardware Month Hack Chat with Michael Weinberg!

It seems like everything and everyone has a special day set aside on the calendar. You know the drill – a headline declaring it National Grilled Cheese Day (sorry, you missed it – April 12) or National Bundt Pan Day (not even kidding, November 15). It seems only fair with all these silly recognition days floating around that we in the hacking community should have a day of our own, too, or even a whole month. That’s why the Open Source Hardware Association declared the entire month of October to be Open Hardware Month.

Open hardware is all about accessible, collaborative processes that let everyone see and understand the hardware they’re using. The technological underpinnings of our lives are increasingly hidden from us, locked away as corporate secrets. Open hardware tries to turn that on its head and open up devices to everyone, giving them the freedom to not only use their devices but to truly understand what’s happening in them, and perhaps repair, extend, and even modify them to do something new and useful. Celebrating that and getting the message out to the general public is certainly something worth doing.

Michael Weinberg is a board member at OSHWA, and he’ll be joining the Hack Chat on October 23 (National Boston Cream Pie Day) to discuss Open Hardware Month and open-source hardware in general. We’ll learn about some of the events planned for Open Hardware Month, how open hardware is perceived beyond the hacker community, and what’s on tap for the 10th anniversary Open Hardware Summit in 2020.

Our Hack Chats are live community events in the Hackaday.io Hack Chat group messaging. This week we’ll be sitting down on Wednesday, October 23 at 12:00 PM Pacific time. If time zones have got you down, we have a handy time zone converter.

Click that speech bubble to the right, and you’ll be taken directly to the Hack Chat group on Hackaday.io. You don’t have to wait until Wednesday; join whenever you want and you can see what the community is talking about.

Glia Is Making Open Medical Devices, And You Can Help

August 25, 2019 by Tom Nardi 40 Comments

The Glia project aims to create a suite of free and open-source medical equipment that can be assembled cheaply and easily when and where it’s needed. Even essential tools like stethoscopes and tourniquets can be difficult to acquire in certain parts of the world, especially during times of war or civil unrest. But armed with a 3D printer and the team’s open-source designs, an ad-hoc factory can start producing these lifesaving tools anywhere on the planet.

Glia member [Tarek Loubani] has recently written a blog post discussing the team’s latest release: an otoscope that can be built for as little as $5. Even if you don’t recognize the name, you’ve almost certainly seen one of them in use. The otoscope is used to look inside the ear and can be invaluable in diagnosing illnesses, especially in children. Unfortunately, while this iconic piece of equipment is quite simple on a technical level, professional-quality versions can cost hundreds of dollars.

Now to be fair, you’ll need quite a bit more than just the 3D printed parts to assemble the device. The final product requires some electrical components such as a battery holder, rocker switch, and LED. It also requires a custom lens, though the Glia team has thought ahead here and provided the files for printable jigs that will allow you to cut a larger lens down to the size required by their otoscope. In a situation where you might have to improvise with what you have, that’s a very clever design element.

So far the team is very happy with how the otoscope performs, but they’ve run into a bit of a logistical snag. It turns out that early work on the project was done in the web-based TinkerCAD, which isn’t quite in line with the team’s goals of keeping everything free and open. They’d like some assistance in recreating the STLs in FreeCAD or OpenSCAD so they’re easier to modify down the road. So if you’re a FOSS CAD master and want to earn some positive karma, head over to the GitHub page for the project and put those skills to use.

We’ve previously covered Glia’s work with 3D printed tourniquets to treat gunshot wounds, a project that led to [Tarek] himself being shot by a sniper while attempting to field test the design in Gaza. If that’s not commitment to the principles of open-source hardware, we don’t know what is.

Continue reading “Glia Is Making Open Medical Devices, And You Can Help” →

You Wouldn’t Download A Nuclear Reactor, But Could You?

June 17, 2019 by Tom Nardi 43 Comments

By pretty much any metric you care to use, the last couple of decades has been very good for the open source movement. There was plenty of pushback in the early days, back when the only people passionate about the idea were the Graybeards in the IT department. But as time went on, more and more developers and eventually companies saw the benefit of sharing what they were working on. Today, open source is effectively the law of the land in many fields, and you don’t have to look far to find the community openly denouncing groups who are keeping their source under lock and key.

The open source submarine that won 2017 Hackaday Prize.

In the last few years, we’ve even seen the idea gain traction in the hardware field. While it’s not nearly as prevalent as opening up the software side of things, today it’s not uncommon to see hardware schematics and PCB design files included in project documentation. So not only can you download an open source operating system, web browser, and office suite, but you can also pull down all the information you need to build everything from a handheld game system to an autonomous submarine.

With so many projects pulling back the curtain, it’s not unreasonable to wonder where the limits are. There’s understandably some concerns about the emerging field of biohacking, and anyone with a decent 3D printer can download the files necessary to produce a rudimentary firearm. Now that the open source genie is out of the bottle, it seems there’s precious little that you can’t download from your favorite repository.

Scratching an exceptionally surprising entry off that list is Transatomic, who late last year uploaded the design for their TAP-520 nuclear reactor to GitHub. That’s right, now anyone with git, some uranium, and a few billion dollars of seed money can have their very own Molten Salt Reactor (MSR). Well, that was the idea at least.

So six months after Transatomic dumped a little under 100 MB worth of reactor documentation on GitHub, is the world any closer to forkable nuclear power? Let’s find out.

Continue reading “You Wouldn’t Download A Nuclear Reactor, But Could You?” →