Hacklet 113 – New Robots

I start each day checking out the new and updated projects over on Hackaday.io. Each day one can find all manner of projects – from satellites to machine vision to rockets. One type of project which is always present are robots- robot arms, educational ‘bots, autonomous robots, and mobile robots. This week’s Hackaday.io had a few great robot projects show up on the “new and updated” page, so I’m using the Hacklet to take a closer look.

bot1We start with [Jack Qiao] and Autonomous home robot that does things. [Jack] is building a robot that can navigate his home. He’s learned that just creating a robot that can get itself from point A to point B in the average home is a daunting task. To make this happen, he’s using the Simultaneous Localization and Mapping (SLAM) algorithm. He’s implementing SLAM with the help of Robotic Operating System (ROS).  The robot started out as a test mule tethered to a laptop. It’s evolved to a wooden base with a mini ITX motherboard. Mapping data comes in through a Kinect V2, which will soon be upgraded to a Neato XV-11 LIDAR system.


tyrobotNext up is [Tyler Spadgenske] with TyroBot. TyroBot is a walking robot with some lofty goals, including walking a mile in a straight line without falling down. [Tyler’s] inspiration comes from robots such as Bob the Biped and Zowi. So far, TyroBot consists of legs and feet printed in PLA. [Tyler] is going to use a 32 bit processor for [TyroBot’s] brain, and wants to avoid the Arduino IDE at any cost (including writing his own IDE from scratch). This project is just getting started, so head on over to the project page and watch TyroBot’s progress!


friendbotNext is [Mike Rigsby] with Little Friend. Little Friend is a companion robot. [Mike] found that robots spend more time charging batteries than interacting. This wouldn’t do for a companion robot. His solution was to do away with batteries all together. Little Friend is powered by super capacitors. An 8 minute charge will keep this little bot going for 75 minutes. An Arduino with a motor shield controls Little Friend’s DC drive motors, as well as two animated eyes. If you can’t tell, [Mike] used a tomato as his inspiration. This keeps Little Friend in the cute zone, far away from the uncanny valley.


logi-botFinally we have the walking robot king, [Radomir Dopieralski], with Logicoma-kun. For the uninitiated, a Logicoma is a robot tank (or “logistics robot”) from the Ghost in the Shell series. [Radomir] decided to bring these cartoon tanks to life – at least in miniature. The bulk of Logicoma-kun is built carefully cut and sculpted acrylic sheet. Movement is via popular 9 gram servos found all over the internet. [Radomir] recently wrote an update outlining his new brain for Logicoma-kun. An Arduino Pro Mini will handle servo control. The main computer will be an ESP8266 running Micropython. I can’t wait to see this little ‘bot take its first steps.

If you want more robotic goodness, check out our brand new mobile robot list! Did I miss your project? Don’t be shy, just drop me a message on Hackaday.io. That’s it for this week’s Hacklet, As always, see you next week. Same hack time, same hack channel, bringing you the best of Hackaday.io!

Fail of the Week: Arachno∙fail∙ia

Going down the list (FCC, CE, UL, etc.) we can’t think of a regulating body that will test for this failure mode. Reportedly, a $1M irrigation system was taken down by a spider. And an itsy-bitsy spider at that.

This fail turned up as a quick image post over on /r/mildlyinteresting but I wasn’t the only electronics person attracted like a moth to a flame. Our friend [Sprite_TM] popped in to answer a question about conformal coating. Seems this board was sealed in a waterproof enclosure but was obviously not conformally coated.

fotw-spider-short-relay-diagram[Sprite_TM] also helped out with some armchair-engineering to guess at what happened. It’s not hard to tell that the footprint on the board looks like a set of mechanical relays all in a line. He looked up the most likely pinout for the relay.

We’ve superimposed that pinout on the board to help illustrate the failure. High voltage comes in on the pin shown with the red trace leading away from it. On either side of that pin are the connections for the low voltage coil which switches from normally closed (the pin in the upper right that is not connected to anything) to the normally open pin (which has the wide trace leading away from it).

So there sat the high voltage pin in between the coil pins when, along came a spider. It shorted the pins and presumably all the way back to the power supply for the low voltage rail. [Fugly_Turnip] (the OP) share some additional detail about the system and this failure; in addition to this card it fried the control module as well.

Another comment on the same thread shares a different story of two boards mounted next to each other with a bug shorting a 1/4″ air gap between two boards and causing similar carnage. Have you encountered Arachno-fail-ia of your own? Let us know below.

Books You Should Read: The Car Hacker’s Handbook

I just had my car in for an inspection and an oil change. The garage I take my car to is generally okay, they’re more honest than a stealership, but they don’t cross all their t’s and dot all their lowercase j’s. A few days after I picked up my car, low and behold, I noticed the garage didn’t do a complete oil change. The oil life indicator wasn’t reset, which means every time I turn my car on, I’ll have to press a button to clear an ominous glowing warning on my dash.

For my car, resetting the oil life indicator is a simple fix – I just need to push the button on the dash until the oil life indicator starts to blink, release, then hold it again for ten seconds. I’m at least partially competent when it comes to tech and embedded systems, but even for me, resetting the oil life sensor in my car is a bit obtuse. For the majority of the population, I can easily see this being a reason to take a car back to the shop; the mechanic either didn’t know how to do it, or didn’t know how to use Google.

The two most technically complex things I own are my car and my computer, and there is much more information available on how to fix or modify any part of my computer. If I had a desire to modify my car so I could read the value of the tire pressure monitors, instead of only being notified when one of them is too low, there’s nowhere for me to turn.

2015 was the year of car hacks, ranging from hacking ECUs to pass California emissions control standards, Google and Tesla’s self-driving cars, to hacking infotainment systems to drive reporters off the road. The lessons learned from these hacks are a hodge-podge of forum threads, conference talks, and articles scattered around the web. While you’ll never find a single volume filled with how to exploit the computers in every make and model of automobile, there is space for a reference guide on how to go about this sort of car hacking.

I was given the opportunity to review The Car Hacker’s Handbook by Craig Smith (259p, No Starch Press). Is it a guide on how to plug a dongle into my car and clear the oil life monitor the hard way? No, but you wouldn’t want that anyway. Instead, it’s a much more informative tome on penetration testing and reverse engineering, using cars as the backdrop, not the focus.

Continue reading “Books You Should Read: The Car Hacker’s Handbook”

150,000 Members Strong, Hackaday.io Flies Past Another Milestone

We’re growing so fast that soon your mom will be on Hackaday.io. That’s fine, everyone who loves hardware is welcome. 150,000 members have made Hackaday.io a home for their creativity — looking for inspiration in the work of others, sharing successes and temporary failures, and building their dream team to take on amazing new challenges. There is no place in the world that can come close to matching the Open Hardware ecosystem that is Hackaday.io.

What is in that one number, 150k? It is a monumental chunk of a much bigger picture: the thriving Hackaday ecosystem that spans from staking down your own workshop full of projects and skills, to following the editorial pulse of hardware used in new and creative ways. Looking over the last twelve months on all of the Hackaday sites we’ve seen about 18.5 Million visitors and registered nearly 85 Million views. Hackaday is not a passive community. We all have an insatiable hunger to delve into the next big trick, and to celebrate the accomplishments that made it happen.

Want to find a new and unique way to use the tech you find most interesting? Your leap forward needs input to pollinate the idea. Hackaday has a critical mass of hackers, designers, and engineers waiting with excitement to hear and help out in exploring and expanding the frontier. These interaction are what has packed Hackaday.io with interesting people. Most would say: I came for a specific hack or to see what a particular hacker was up to, but then I felt at home and decided to stick around and share what I’ve spent way to much time doing (but I wouldn’t have it any other way).

As we continue to knock down one membership milestone after another I want to thank you all for being involved, for valuing the free and open sharing of information and ideas, and for sharing your own time and talent. You are what moves this community of hardware hackers to dizzying heights of excellence and awesome.

This is all too good to be a secret. Talk to your hardware-loving friends, colleagues, family, and acquaintances and invite them to Hackaday.io if they’re not already with us.

What Could Go Wrong: Asynchronous Serial Edition

It’s the easiest thing in the world — simple, straightforward serial data. It’s the fallback communication protocol for nearly every embedded system out there, and so it’s one that you really want to work when the chips are down. And yet! When you need it most, you may discover that even asynchronous serial can cost you a few hours of debugging time and add a few gray hairs to your scalp.

In this article, I’m going to cover most (all?) of the things that can go wrong with asynchronous serial protocols, and how to diagnose and debug this most useful of data transfer methods. The goal is to make you aware enough of what can go wrong that when it does, you’ll troubleshoot it systematically in a few minutes instead of wasting a few hours.

Continue reading “What Could Go Wrong: Asynchronous Serial Edition”

Gawking Text Files

Some tools in a toolbox are versatile. You can use a screwdriver as a pry bar to open a paint can, for example. I’ve even hammered a tack in with a screwdriver handle even though you probably shouldn’t. But a chainsaw isn’t that versatile. It only cuts. But man does it cut!

aukAWK is a chainsaw for processing text files line-by-line (and the GNU version is known as GAWK). That’s a pretty common case. It is even more common if you produce a text file from a spreadsheet or work with other kinds of text files. AWK has some serious limitations, but so do chainsaws. They are still super useful. Although AWK sounds like a penguin-like bird (see right), that’s an auk. Sounds the same, but spelled differently. AWK is actually an acronym of the original author’s names.

If you know C and you grok regular expressions, then you can learn AWK in about 5 minutes. If you only know C, go read up on regular expressions and come back. Five minutes later you will know AWK. If you are running Linux, you probably already have GAWK installed and can run it using the alias awk. If you are running Windows, you might consider installing Cygwin, although there are pure Windows versions available. If you just want to play in a browser, try webawk.

Continue reading “Gawking Text Files”

Mosaic Palette: Single Extruder Multi-Color and Multi-Material 3D Printing

Lots of solutions have been proposed and enacted for multi-color and multi-material 3D printing, from color mixing in the nozzle to scripts requiring manual filament change. A solution proposed fairly early on was to manually splice the filament together, making a custom spool. The printer would print as normal, but the filament would change color. This worked pretty well, but it was tedious and it wasn’t entirely possible to control where the color change happened on the model.

You’ll find some examples of the more successful manual splicing hacks in the pictures below. Scroll down a bit further to find our interview with Mosaic Manufacturing at Bay Area Maker Faire 2016. They have a new product that automates the filament splicing process with precision as the ultimate goal. It unlocks a single extruder printer to behave like a multi-extruder model without stopping and starting.

Mosaic pulled off a very difficult combination of two methods mentioned above. Their flagship product is a machine they’ve dubbed, “Palette”. It’s an automatic filament splicer. Up to four different filaments can feed into Palette, and it will splice them at determined intervals. This would be cool by itself, if only to save the tedium of splicing and winding a custom spool by hand.

The real killer app with Palette, however, is the software that runs alongside it. Palette can take the GCODE output of any properly prepared multi material file from any slicer, and then precisely combine and splice the filament. This can feed into any printer without modifying it, aside from sticking an encoder somewhere in the filament path. The results are indistinguishable from a dual, or quad extruder set-up.

Continue reading “Mosaic Palette: Single Extruder Multi-Color and Multi-Material 3D Printing”