Anything can be a remote controlled airplane, and ‘copters – quad or not – simply beat the air into submission. Remote controlled cars are easy, and RC tanks can even shoot their guns. One type of vehicle has eluded remote control hobbyists to a large extent; building a remote control submarine is hard. Not only do you have buoyancy to worry about, but you also need a way to keep the dry parts dry, all while operating in an environment where radio doesn’t really work well.
[Ivan] has already built RC planes, but wanted to tackle a new challenge. He built an RC submarine, and he did it using the simplest household materials.
What do you get when you combine a Tesla coil, 315 film canisters and a fortune wheel? The answer is of course a film canister Gatling gun. [ScienceBob] has taken the simple film canister cannon hack to a whole new level. The idea is simple, the film canister has a lid that fits tight and allows pressure to build up, so if you fill it with alcohol vapor and ignite it with a spark gap, you get a small explosion that sends the can flying away.
[ScienceBob] uses 21 rows of fifteen canisters each around the wheel. There is a spark gap for each canister, and all the spark gaps in the same row are in series. You need a lot of volts to turn on fifteen spark gaps, and that is why the Tesla coil is part of the game. When the outer end of the wire in one row passes near the Tesla coil, a spark jumps and fires all the spark gaps, igniting the alcohol vapor and fifteen cans are expelled from the wheel. The wheel rotates until all rows are fired.
Nadya Peek is one of the hackers that should require no introduction for the regular Hackaday reader. She is a postdoc at the Center for Bits and Atoms at the MIT Media Lab. She’s responsible for Popfab, a CNC machine that fits in a suitcase and one of the first implementations of a Core XY stage we’ve seen. Nadya has joined the ranks of Rudolf Diesel, Nikola Tesla, Mikhail Kalashnikov, and George W.G. Ferris by having a very tiny piece of the Novena laptop bear her name. She’s built cardboard CNC machines, and taken the idea of simple, easy to build printers, routers, and drawbots worldwide. She just defended her thesis, the gist of which is, ‘How to rapidly prototype rapid prototyping machines.’ She’s also one of this year’s Hackaday Prize judges, for which we have the utmost appreciation.
This year, the organizers of the Fab 12 conference on digital fabrication in Shenzhen turned to Nadya and her team to bring their amazing experience to conference attendees. A workshop was in order, but Nadya didn’t have time to organize the logistics. The conference organizers made a deal: the Center for Bits and Atoms would teach a workshop, but getting all the materials and electronics was the responsibility of the organizers.
Upon arriving at the Shenzhen Sheridan, Nadya found the organizers didn’t hold up their end of the bargain. The cardboard, motors, electronics, and glue were nowhere to be found. A “rider” doesn’t quite translate from English, it seems. This is Shenzhen, though, where you can buy all the cardboard, motors, electronics, and iPhone clones you could imagine. What was the solution to this problem? Founding a company in Shenzhen for eight days.
Half a tourist’s guide to Shenzhen and half a deconstruction of what goes into cardboard CNC, Nadya’s talk for the 2016 Hackaday SuperConference covers what happens when you have a week to build a company that will build machines that build machines.
Imagine trying to make a ball-shaped robot that rolls in any direction but with a head that stays on. When I saw the BB-8 droid doing just that in the first Star Wars: The Force Awakens trailer, it was an interesting engineering challenge that I couldn’t resist. All the details for how I made it would fill a book, so here are the highlights: the problems I ran into, how I solved them and what I learned.
The ESP8266 is officially checking into the Hackaday 1kB Challenge. Doing something meaningful in 1kB of compiled code is tricky; modern SDKs like the ones often used for ESP8266 compile even the simplest programs to nearly that size. If you want to use this hardware in your 1kB Challenge entry, I have a solution for you!
The ESP8266 now has a barebones build environment focused on minimizing code size, as little as 131 bytes to boot up and blink an LED. It also “supports” some new, insane clock rates (like 346 MHz) and crazy development cycle speeds. The WiFi is stuck in “airplane mode,” but it will be worth your time to consider the ESP for the next non-WiFi project you’ll be doing.
Far too often, we follow design patterns that ‘just work’ instead of looking for the ones that are optimal because we’re afraid of wasting time. The benefits of keeping code tight and small are frequently overlooked. When code is small and environments minimal, RAM and FLASH become easier to come by, compiled binaries shrink and time wasted by compiling and flashing can decrease by an order of magnitude! We rarely see just how much value is added when we become a good engineer: being done only when there’s nothing left to remove from a design. Nosdk8266 will let you see what it’s like to test out code changes several times a minute.
Just a month ago, when preparing the ESP8266 for a USB bootloader, I had to make a stripped-down environment for it. It’s not based on the Official Non-OS SDK or the RTOS sdk, but an environment that can boot up and blink an LED. Not just blink an LED, but tweak the clock in some totally unexpected ways and even run the I2S bus (used for espthernet and Color NTSC Broadcast Video). If you’re not at the submission phase for your 1kB challenge, you can even use the mask ROM for printf! Now you can tweak your code and — in under 2 seconds — see what the new code does!
Even in PICO mode, the part still has to use the mask ROM to be loaded, but thankfully, the 1kB Challenge has added an exception for unavoidable bootloaders. No longer bound by the shackles of WiFi, I can’t wait to see what you’ll do with the ESP8266. Just beware that the processor may not work reliably when overclocked at 346 MHz (332.5%,) and you’ll certainly be voiding any warranties you may have. Sounds like fun, right?
Editorial Note: This is a guest article from Charles Lohr, aka [CNLohr]. Although he has written a few other guest articles, he is not a regular contributor to Hackaday and therefore, this article does not disqualify him from entering the 1kB Challenge. We felt it more fair to publish this article which shares the tools he’s using to make code smaller, rather than to keep them to himself for fear of disqualification. While we have your attention, we wanted to mention one of Charles’ articles which was published on April 1st — we still think there’s a lot of people who don’t realize it wasn’t a prank.
There’s nothing more freeing than to be an engineer with no perceptible budget in sight. [BrendaEM] walks us through a teardown of a machine that was designed under just such a lack of constraint. It sat inside of a big box whose job was to take silicon wafers in on one side and spit out integrated circuits on the other.
[BrendaEM] never really divulges how she got her hands on something so expensive that the engineer could specify “tiny optical fiber prisms on the end of a precision sintered metal post” as an interrupt solution for the wafer. However, we’re glad she did.
The machine features lots of things you would expect; pricey ultra precise motors, silky smooth linear motion systems, etcetera. At one point she turns on a gripper movement, the sound of it moving can be adequately described as poetic.
It also gives an unexpected view into how challenging it is to produce the silicon we rely on daily at the ridiculously affordable price we’ve come to expect. Everything from the ceramic plates and jaws that can handle the heat of the silicon right out of the oven to the obvious cleanliness of even this heavily used unit.
It’s a rare look into an expensive world most of us peasants aren’t invited to. Video after the break.
Regular Hackaday readers will be familiar with our convention of putting the name, nickname, or handle of a person in square brackets. We do this to avoid ambiguity as sometimes names and particularly nicknames can take unfamiliar forms that might be confused with other entities referred to in the text. So for example you might see them around [Bart Simpson], or [El Barto]. and occasionally within those brackets you’ll also see a capitalised string of letters and numbers after a name. For example the electronic music pioneer [Bob Moog, K2AMH], which most of you will recognise as an amateur radio callsign.
Every licenced radio amateur is issued one by their country’s radio authority as a unique identifier, think of it as similar to a car licence plate. From within the amateur radio bubble those letters and numbers can convey a significant amount of information about where in the world its user is located, when they received their licence, and even what type of licence they hold, but to outsiders they remain a mysterious and seemingly random string. We’ll now attempt to shed some light on that information, so you too can look at a callsign in a Hackaday piece or anywhere else and have some idea as to its meaning.
