Like many of us, [C] enjoys an ice-cold, refreshing soda while coding. Driven by a strong desire to keep a soda ice-cold indefinitely without using ice, [C] started Project Frosty Mug.
[C]’s stated goal is to keep a 20oz plastic bottle of soda at ~35F indefinitely while it sits in a room temperature environment. He started with a thermoelectric unit to cool an aluminium disc, like a cold coaster. Builds one and two made him realize that dealing with the generated heat was a big issue: it got so hot that it deformed the PLA frame. [C] also realized that bottom-only cooling wasn’t going to get the job done.
This project is now in its third build, which is pictured above. As you can see, it’s more koozie than coaster. That 3-D printed holster is lined with aluminium sheeting. Another flat piece covers the opening and attaches to the cooling element. A beefy CPU heat sink does its best, and a couple of U-brackets hold it all together.
[C]’s tested it with a glass bottle of Diet Sun Drop chilled to 38F. After 30 minutes in an ambient temperature of ~70F, the soda measured 45F. [C] lamented having not used a control bottle for comparison and reports that the power supply became quite warm. [C] isn’t going to give up that easily. Do you have any ideas for the fourth build?
Editor’s Note: This is one of the last Fail of the Week tips we have stored up. If you want to see the series continue on a weekly basis, we need help finding more documented fails! Please look back through your projects and document the ones that didn’t go quite right. We also encourage you to send in links to other fails you’ve found. Just drop the links in our tips line. Thanks!
Fail of the Week is a Hackaday column which runs every Thursday. Help keep the fun rolling by writing about your past failures and sending us a link to the story — or sending in links to fail write ups you find in your Internet travels.
This Fail of the Week will remind our readers that every project they make, no matter how small they might be, may have big consequences if something goes wrong. Shown in the picture above is an oven that [Kevin] tweaked to perform reflow soldering. The story is he had just moved into a new place a few weeks ago and needed to make a new batch of boards. As he had cycled this oven many times, he was confident enough to leave the room to answer a few emails. A few minutes later, he had the unfortunate experience of smelling something burning as well as discovering white smoke invading his place.
Continue reading “Fail of the Week: How a Cheap USB AC Adapter Might Indirectly Burn Your House Down”
Please don’t judge [Alan] on his choice of vests. This project is from 1999 when it was common to see people rockin’ these threads. Anyone who has ever spent time on the University of Minnesota campus in Minneapolis, Minnesota will know that parking is at a premium. [Alan] had a 12-15 minute walk from his parking garage to his office and was considering a cheaper parking location that would balloon that to 20-25 minutes. But engineers don’t see problems, they see project ideas. He started work on a tiny electric scooter that could slim down his commute. Obviously he did find some success, but it was interspersed with failures that make his scooter the Fail of the Week.
Continue reading “Fail of the Week: Commute-Shortening Electric Scooter”
Frankly we’re tired of Arduino having a bad name here at Hackaday. So [Brian Benchoff] came up with a way to make it useful to a wider audience. His creation, which we call the HaDuino, lets you use the Arduino clone to open a tasty bottle of beer.
Continue reading “HaDuino: Open Your Beer Using Arduino”
We’re changing it up this week with a reverse engineering fail which [Itay] pointed out to us. A couple of years ago [Nate] over at Sparkfun agreed to help a friend with a project that required precise distance measurement. He knew that laser rangefinders are a good way to go and mentions their use in golfing and the building trades. He picked up this handheld version billed as a laser tape measure. He put up a valiant effort to reverse engineer the PCB in hopes of finding a hook for the measurement data.
Obviously his endeavor failed or we wouldn’t be talking about it in this column. But there’s a lot to learn about his methods, and a few of the comments associated with his original post help to shed light on a couple of extra things to try.
Continue reading “Fail of the Week: Capturing Data from a Laser Rangefinder”
There’s so much more to be discovered when your projects just don’t want to work. Grinding out the bugs, getting past roadblocks, and discovering gotchas is where real hacking know-how comes from. But most people aren’t motivated to document their failures. We want to change that.
We want to roll out a new weekly feature that showcases failure… well documented failure. But we need YOU to give up the goods. Write about your failed experience on your blog, post it to our project forums with [FAIL] in the title, or you can just write everything in an email and send it to us. Which ever way you choose, you’ll need to tip us off that you’d like to make it to the front page (come on, it’s not bragging since it didn’t even work!). If you already know of well documented project fails send in those links too even if they’re not your projects.
Make sure you include at least one descriptive image — snapshots, diagrams, schematics, screencaps, anything that tells the story is fair game. To show you what we’re after here’s a few of our favorite failed projects:
We’d like to point out that all of these projects are interesting ideas that show off missteps along the way. We will not be trashing on your skills as a hacker, but instead celebrating the lessons learned and hearlding the sharing of ideas from otherwise doomed projects.
Ah, CSI. What other television show could present digital forensics with such two-bit dialogue?
It’s time once again to put on your hacker hats – a red fedora, we guess – and tell us the worst hacker dialogue you’ve seen in movies or TV. We’ve seen a ton of shows and movies where writers and directors spend zero time doing any sort of research in whatever technology they’d like to show off in the story they’re trying to convey. Usually this results in lines like, “I’ll create a GUI interface using Visual Basic. See if I can track an IP address.” It’s technobabble at its best, and horribly misinformed at its worst.
We’re wondering what you, the readers of Hackaday, think are the worst examples of hacker lingo fails. Anything from, ‘Enhance!’ to the frightening real-life quote, “the Internet is not a big truck. It’s a series of tubes.”
We’ll compile your suggestions in a later post, but I’m betting something from Star Trek: Voyager will make the #1 technobabble/hacking lingo fails. There’s just too much in that show that isn’t internally consistent and doesn’t pay any heed to the laws of (fictional) physics. Warp 10, I’m looking at you. Of course there was the wonderful Habbo reference in last week’s Doctor Who, but I’m betting that was intentional as [Moffat] seems pretty up to speed on the tropes and memes of the Interwebs.
About a month ago, we asked you for your take on the worst hacking scenes ever shown on TV or film. The results made for good viewing, albeit with a surprising absence of Lawnmower Man. Now we want some dialogue to go with these horrendous hacking scenes. So, what say you, Hackaday? What are the worst hacking lingo fails you’ve seen or heard? Please be specific about what movie/TV show you’re referencing. Last time some good stuff probably slipped by because people just said a few words without context assuming we’d know exactly what they were referring to.