Fail of the Week: Not All Mold Releases Release All Molds.

I’m writing a series of articles on resin casting as an extension to my experiences with the instructions found in the wonderful Guerrilla Guide. However, mistakes were made. Having run out of my usual mold release I went to a back-up jar that was lying around from a casting project long, long ago in a workshop far, far away.

GLUE
Never much for readin’ the nutrition facts myself.

I’m refining a technique of making a mold the quick and dirty way. Everything was going well, the sprues looked good and the master released from the silicone. It was time to do the second half of the mold. As usual I applied a generous amount of mold release. Since it was the first time this mold was to be used I went ahead and did all the proper steps. Rubbing off the dried release and applying a few more coats just to be sure.

I was completely unaware that I was applying mold release designed for urethane molds only. In other words I thoroughly covered my silicone mold in silicone bonding agents. I remained unaware until trying to separate the halves of the mold and found them thoroughly joined. After going through the stages of grief I finally figured out where it all went wrong.

Oh well. I’m ordering some of my regular pick, Stoner A324, and that should do the trick. There’s also Mann- Ease Release 200. While having probably the best name a release agent can have, it doesn’t work as well and needs approximately 100 years to dry. After this setback I’d rather just, grudgingly, learn my lesson and order the correct thing.

I wonder if the smooth-on description can say URETHANE RUBBER a few more times.
Oh. Yes I see. Urethane… Urethane…

So now that we know the right way to fix this is to order the right product, is there a hack to get around it? Does anyone have a homebrew trick for release agent that can be used in a pinch? Leave your comments below.

Fail of the Week – Steam Cleaner fix goes bad

[Sven337] was gifted a steam cleaner, and seemed pretty happy because it helped clean the floor better than a regular mop. Until it fell one day, and promptly stopped working. It would produce steam for a short while and then start spitting out cold water, flooding the floor.

Like any self-respecting hacker, he rolled up his sleeves and set about trying to fix it. The most-likely suspect looked like the thermostat — it would switch off and then wouldn’t switch on again until the water temperature fell way below the target, letting out liquid water instead of steam after the first switching cycle. A replacement thermostat was ordered out via eBay.

Meanwhile, he decided to try out his hypothesis by shorting out the thermostat contacts. That’s when things went south. The heater worked, and got over-heated due to the missing thermostat. The over-temperature fuse in the heater coil blew, so [Sven337] avoided burning down his house. But now, he had to replace the fuse as well as the thermostat.

[Sven337] bundled up all the parts and put them in cold storage. The thermostat arrived after almost 2 months. When it was time to put it all together, a piece of fibreglass tubing that slides over the heater coil was missing. Without the protective sleeve, the heater coil was shorting out with the grounded heater body, blowing out the fuses in his apartment.

That’s when [Sven337] called it a day and threw out the darn steam mop — a few dollars down the drain, a few hours lost, but at least he learnt a few things. Murphy’s Law being what it is, he found the missing insulation sleeve right after he’d thrown it away.

AirAsia Crash Analysis: Who or What Failed?

Just a few days after Christmas last year AirAsia Flight 8051 traveling to Singapore tragically plummeted into the sea. Indonesia completed its investigation of the crash and just released the final report. Media coverage, especially in Asia is big. The stories are headlined by pilot error but,as technologists, there are lessons to be learned deeper in the report.

The Airbus A320 is a fly-by-wire system meaning there are no mechanical linkages between the pilots and the control surfaces. Everything is electronic and most of a flight is under automatic control. Unfortunately, this also means pilots don’t spend much time actually flying a plane, possibly less than a minute, according to one report.

Here’s the scenario laid out by the Indonesian report: A rudder travel limit computer system alarmed four times. The pilots cleared the alarms following normal procedures. After the fifth alarm, the plane rolled beyond 45 degrees, climbed rapidly, stalled, and fell.

Continue reading “AirAsia Crash Analysis: Who or What Failed?”

Fail of the Week: Dave Jones and the Case of the Terrible Tablet

Nothing spices up a quiet afternoon like the righteous indignance of an upset engineer, especially if that engineer is none other than [Dave Jones], on his EEVblog YouTube Channel. This week [Dave] has good reason to be upset. A viewer sent him what looked to be a nondescript 2010 era tablet from a company called Esinomed. From the outside it looked like a standard issue medical device. Opening up the back panel tells a completely different story though. This thing is quite possibly the worst hack job [Dave] (and we) have ever seen. This is obviously some kind of sales demo or trade show model. Even with that in mind, this thing is a fail.

wtf-solderThe tablet is based upon an off-the-shelf embedded PC motherboard and touchscreen controller. [Dave] took some offense at the hacked up USB connector on the touchscreen. We have to disagree with [Dave] a bit here, as the video seems to show that a standard mini-b connector wouldn’t have fit inside the tablet’s case. There’s no excuse for the USB cable shield draped over the bare touch controller board though. Things go downhill from there. The tablet’s power supply is best described as a bizarre mess. Rather than use a premade DC to DC converter, whoever built this spun their own switch mode power supply on a home etched board. The etching job looks good, but everything else, including the solder job, is beyond terrible. All the jumps and oddly placed components make it look like a random board from the junk bin was used to build this supply.

The story gets even worse with the batteries. The tablet has horribly hand soldered NiMH cells shoved here, there and everywhere. Most of the cells show split shrink wrap – a sure sign they have been overheated. It’s hard to tell from the video, but it appears as if a few cells have their top mounted vent holes covered with solder. That’s a great way to turn a simple rechargeable battery into a pipe bomb. Batteries can be safely hand soldered – Radio Controlled modelers did it for decades before LiPo cells took over.

We’ve all hacked projects together at the last minute; that’s one of the things we celebrate here on Hackaday. However, since this is a commercial medical device (with serial number 11 no less) we have to stamp this one as a fail.

Continue reading “Fail of the Week: Dave Jones and the Case of the Terrible Tablet”

Fail of the Week: OpenMV Kickstarter Project Hits Manufacturing Snag

Making stuff is hard, especially when you are making lots of stuff. The OpenMV Cam project knows this, because it has hit a problem while putting together their cheap machine vision module. The problem is with the BGA solder balls that connect the image sensor to the main board.

openmv-thumbWe’ve covered this intriguing project before: the aim is to build a small, cheap module that can run image processing algorithms to easily give robots sight. The sensor is a Ball Grid Array (BGA) package, which means there are a grid of small solder balls on the back that form the electrical connections. It seems that some of these solder balls are oxidized, preventing them from melting and fusing properly with the board. This is called a head-in-pillow defect, because the ball behaves like your head when you lie down in bed. Your head squishes the pillow, but doesn’t merge into it. There are 38 balls on the OV26040 image sensor and even a single bad link means a failure.

The makers of the project have tried a number of solutions, but it seems that they may have to remake the ball links on the back of each sensor. That’s an expensive process: they say it will cost $7 for each, more than the actual sensor cost initially.

A few people have been posting suggestions in the comments for the project, including using solvents and changing the way the sensors are processed before mounting. We’d like to see them overcome this hurdle. Anybody have any suggestions to quickly and cost effectively move the manufacturing process forward?

Continue reading “Fail of the Week: OpenMV Kickstarter Project Hits Manufacturing Snag”

Fail of the Week: Marginally Documented Pad Shorts to Maskless PCB

[Erich Styger] was bit by a nasty gotcha when soldering a QFN surface mount chip. The problem rears its ugly head when combining a chip possessing a padless conductor and a PCB without a solder mask. As you can see in the image above, there is a conductor exiting the side of the plastic QFN, but there is no pad associated with it. For this reason, you won’t see the conductor documented in the datasheet as a pin. It is documented in the mechanical drawing of the package, without any explicit reference to its existence. This is the Jason Bourne of package quirks.

The PCB layout just happens to have a trace exiting right under this conductor. The two aren’t touching, but without solder mask, a bit of melted metal was able to mind the gap and connect the two conductors. [Eric] notes that although the non-pad isn’t documented, it’s easy to prove that it is connected to ground and was effectively pulling down the signal on that trace.

In a recent article on Hackaday I talked about “dangling pointers” and the challenge when interrupts expose the bug. [Erich’s] covered a ton of posts about embedded software. I was doing some poking around and was delighted to find that he covered the same concept and a solution for it using a program called cppcheck.

Fail of the Week: Exploding Fermentation

It’s no secret that hackers like fermentation, both the process and the end results. I myself have a crock of sauerkraut happily bubbling away in the kitchen right now. Fermentation can lead to tasty endpoints, and the process itself, which basically amounts to controlled rotting, is a fascinating set of biochemical reactions. But done wrong, fermentation can result in injury, as it did at CCC this year when a fermentation vessel exploded.

"It was the one on the left, officer. He did it."
“It was the one on the left, officer. He did it.”

Exactly what happened isn’t really clear, except that Food Hacking Base ran a number of workshops at CCC 2015, several of which involved fermented foods or drinks. A Grolsch-style bottle with a ceramic flip-top was apparently used as a fermentation vessel, but unfortunately the seal was not broken. The bottle found its way to another tent at CCC, this one running an SMD soldering workshop. Carbon dioxide gas built up enough pressure in the bottle to shatter it and send shrapnel flying through the workshop tent. According to a discussion thread on the incident, “people got hurt and need to go to the hospital because glas [sic] particles were stuck in their faces, a throat was cut and an eyelid bleeding.” The explosion was quite energetic, because, “we also found a 20cm long piece of glass that went trough [sic] the ceiling of the tent and propelled for another 4-5 meters afterwards.”

We’ve seen lots of Hackaday projects involving instrumentation and automation of fermentation, including some with really large vessels. The potential for destruction if such a vessel isn’t properly vented is pretty high. At the very least, you’ll be left with a really big mess to clean up. Be careful out there – microbes are not to be trifled with. We don’t want to give you the wrong idea about CCC; this year was incredible as [Elliot Williams] reported during his time there.

Now it’s off to the kitchen to check on my kraut.

[Thanks to Morgan for the tip.]