A couple of weeks back, we covered an interesting method for prototyping PCBs using a modified CNC mill to 3D print solder onto a blank FR4 substrate. The video showing this process generated a lot of interest and no fewer than 20 tips to the Hackaday tips line, which continued to come in dribs and drabs this week. In a world where low-cost, fast-turn PCB fabs exist, the amount of effort that went into this method makes little sense, and readers certainly made that known in the comments section. Given that the blokes who pulled this off are gearheads with no hobby electronics background, it kind of made their approach a little more understandable, but it still left a ton of practical questions about how they pulled it off. And now a new video from the aptly named Bad Obsession Motorsports attempts to explain what went on behind the scenes.
Hackaday Columns4225 Articles
This excellent content from the Hackaday writing crew highlights recurring topics and popular series like Linux-Fu, 3D-Printering, Hackaday Links, This Week in Security, Inputs of Interest, Profiles in Science, Retrotechtacular, Ask Hackaday, Teardowns, Reviews, and many more.
Hackers, Patents, And 3D Printing
Last week, we ran a post about a slightly controversial video that claimed that a particular 3D-printing slicing strategy was tied up by a patent troll. We’re absolutely not lawyers here at Hackaday, but we’ve been in the amateur 3D printing revolution since the very beginning, and surprisingly patents have played a role all along.
Modern fused-deposition modelling (FDM) 3D printing began with Stratasys’ patent US5121329A, “Apparatus and method for creating three-dimensional objects”, and the machines they manufactured and sold based on the technology. Go read the patent, it’s an absolute beauty and has 44 different claims that cover just about everything in FDM printing. This was the watershed invention, and today, everything claimed in the patent is free.
Stratasys’ patent on the fundamental FDM method kept anyone else from commercializing it until the patent expired in 2009. Not coincidentally, the first available home-gamer 3D printer, the Makerbot Cupcake, also went on sale in 2009.
The Stratasys machines were also one of the big inspirations for Adrian Bowyer to start the RepRap project, the open-source movement that basically lead to us all having cheap and cheerful 3D printers today, and he didn’t let the patent stop him from innovating before it lapsed. Indeed, the documentation for the RepRap Darwin dates back to 2007. Zach [Hoeken] Smith delivered our hackerspace the acrylic parts to make one just around that time, and we had it running a year or two before the Cupcake came out of the company that he, Bre, and Adam shortly thereafter founded.
The story of hackers and 3D printers is longer than the commercial version of the same story would imply, and a lot of important innovations have come out of our community since then too. For instance, have a look at Stratasys’ patent on heated bed technology. At first read, it seems to cover removable heated beds, but have a look at the cutout at the end of claim 1: “wherein the polymer coating is not a polymer tape”. This cutout is presumably in response to the at-the-time common practice of buying Kapton, PEI, or PET tape and applying that to removable heated bed surfaces. I know I was doing that in 2012, because I read about it on IRC or something, long before the Stratasys patent was filed in 2014. They could only get a patent for sprayed-on coatings.
As [Helge] points out, it’s also easily verifiable that the current patent on “brick layers” that we’re worrying about, filed in 2020, comes later than this feature request to Prusa Slicer that covers essentially the same thing in 2019. We assume that the patent examiner simply missed that obvious prior art – they are human after all. But I certainly wouldn’t hesitate to implement this feature given the documented timing.
I would even be so bold as to say that most of the post-2010 innovation in 3D printing has been made by hobbyists. While the RepRap movement was certainly inspired by Stratasys’ invention in the beginning, our community is where the innovation is happening now, and maybe even more starkly on the software side of things than the hardware. Either way, as long as you’re just doing it for fun, let the suits worry about the patents. Hackers gotta hack.
Hackaday Podcast Episode 296: Supercon Wrapup With Tom And Al, The 3DP Brick Layering Controversy, And How To Weld In Space
In this episode you’ll get to hear not one, not two, but three Hackaday Editors! Now that the dust has mostly settled from the 2024 Hackaday Supercon, Al Williams joins Elliot and Tom to compare notes and pick out a few highlights from the event. But before that, the week’s discussion will cover the questionable patents holding back a promising feature for desktop 3D printers, a new digital book from NODE, and the surprisingly limited history of welding in space. You’ll also hear about the challenge of commercializing free and open source software, the finicky optics of the James Web Space Telescope, and the once exciting prospect of distributing software via pages of printed barcodes.
Direct MP3 download for offline, “easy” listening.
This Week In Security: Hardware Attacks, IoT Security, And More
This week starts off with examinations of a couple hardware attacks that you might have considered impractical. Take a Ball Grid Array (BGA) NAND removal attack, for instance. The idea is that a NAND chip might contain useful information in the form of firmware or hard-coded secrets.
The question is whether a BGA desolder job puts this sort of approach out of the reach of most attackers. Now, this is Hackaday. We regularly cover how our readers do BGA solder jobs, so it should come as no surprise to us that less than two-hundred Euro worth of tools, and a little know-how and bravery, was all it took to extract this chip. Plop it onto a pogo-pin equipped reader, use some sketchy Windows software, and boom you’ve got firmware.
What exactly to do with that firmware access is a little less straightforward. If the firmware is unencrypted and there’s not a cryptographic signature, then you can just modify the firmware. Many devices include signature checking at boot, so that limits the attack to finding vulnerabilities and searching for embedded secrets. And then worst case, some platforms use entirely encrypted firmware. That means there’s another challenge, of either recovering the key, or finding a weakness in the encryption scheme. Continue reading “This Week In Security: Hardware Attacks, IoT Security, And More”
Microfluidic Motors Could Work Really Well For Tiny Scale Tasks
The vast majority of motors that we care about all stick to a theme. They rely on the electromagnetic dance between electrons and magnets to create motion. They come in all shapes and sizes and types, but fundamentally, they all rely on electromagnetic principles at heart.
And yet! This is not the only way to create a motor. Electrostatic motors exist, for example, only they’re not very good because electrostatic forces are so weak by comparison. Only, a game-changing motor technology might have found a way to leverage them for more performance. It achieves this by working with fluid physics on a very small scale.
Continue reading “Microfluidic Motors Could Work Really Well For Tiny Scale Tasks”
Retrotechtacular: The TV Bombs Of WWII
Anyone who was around for the various wars and conflicts of the early 2000s probably recalls the video clips showing guided bombs finding their targets. The black-and-white clips came from TV cameras mounted in the nose of the bomb, and were used by bombardiers to visually guide the warhead to the target — often providing for a level of precision amounting to a choice of “this window or that window?” It was scary stuff, especially when you thought about what was on the other side of the window.
Surprisingly, television-guide munitions aren’t exactly new, as this video on TV-guided glide bombs in WWII indicates. According to [WWII US Bombers], research on TV guidance by the US Army Air Force started in 1943, and consisted of a plywood airframe built around a standard 2000-pound class gravity bomb. The airframe had stubby wings for lift and steerable rudders and elevators for pitch and yaw control. Underneath the warhead was a boxy fairing containing a television camera based on an iconoscope or image orthicon, while all the radio gear rode behind the warhead in the empennage. A B-17 bomber could carry two GB-4s on external hardpoints, with a bulky TV receiver provided for the bombardier to watch the bomb’s terminal glide and make fine adjustments with a joystick.
In testing, the GB-4 performed remarkably well. In an era when a good bombardier was expected to drop a bomb in a circle with a radius of about 1,200′ (365 meters) from the aim point, GB-4 operators were hitting within 200′ (60 meters). With results like that, the USAAF had high hopes for the GB-4, and ordered it into production. Sadly, though, the testing results were not replicated in combat. The USAAF’s 388th Bomber Group dropped a total of six GB-4s against four targets in the European Theater in 1944 with terrible results. The main problem reported was not being able to see the target due to reception problems, leaving the bombardiers to fly blind. In other cases, the bomb’s camera returned a picture but the contrast in the picture was so poor that steering the weapon to the target was impossible. On one unfortunate attack on a steel factory in Duren, Germany, the only building with enough contrast to serve as an aiming point was a church six miles from the target.
The GB-4’s battlefield service was short and inglorious, with most of the 1,200 packages delivered never being used. TV-guided bombs would have to wait for another war, and ironically it would be the postwar boom in consumer electronics and the explosion of TV into popular culture would move the technology along enough to make it possible.
FLOSS Weekly Episode 809: Pi4J – Stable And Boring On The Raspberry Pi
This week, Jonathan Bennett and David Ruggles chat with Frank Delporte about Pi4J, the friendly Java libraries for the Raspberry Pi, that expose GPIO, SPI, I2C and other IO interfaces. Why would anyone want to use Java for the Pi? And what’s changed since the project started? Listen to find out!
Continue reading “FLOSS Weekly Episode 809: Pi4J – Stable And Boring On The Raspberry Pi”