[Ray] is in a bit of a pickle. All appeared well when he began selling an ESP8266-based product, but shortly thereafter some of them got hot and let the smoke out. Not to worry, he recommends ignoring the problem since once the faulty components have vaporized the device will be fine.
The symptom lies in the onboard red power indicator LED smoking. (Probably) nothing is wrong with the LED, because upon testing the batch he discovered its current limiting resistor is sometimes a little bit low to spec. Off by a hair of, oh, call it an even 1000x.
Yep, the 4700 ohm resistor is sometimes replaced with a 4.7 ohm. Right across the power rail. That poor little LED is trying to dissipate half a watt on a pinhead. Like a sparrow trying to slow a sledgehammer, it does not end well. Try not to be too critical, pick ‘n place machines have rough days now and then too and everyone knows those reels look practically the same!
The good news is that the LED and resistor begin a thermal race and whoever wins escapes in the breeze. Soon as the connection cuts the heat issue disappears and power draw drops back to normal. Everything is fine unless you needed that indicator light. Behold – there are not many repairs you can make with zero tools, zero effort, and only a few seconds of your time.
[Ray] also recommends measuring and desoldering the resistor or LED if you are one of the unlucky few, or, if worst comes to worst, he has of course offered to replace the product too. He did his best to buy from authentic vendors and apologizes to the few customers affected. As far as he knows no one else has had this problem yet so he wanted to share it with the community here on Hackaday as soon as possible. Keep an eye out.
If you have never seen
smoke ISO9001-certified electronics repair before, there is a short video of this particular disaster upgrade caught live on tape after the break.
Continue reading “Faulty ESP8266s Release Smoke, Then Keep Working?”
The card you see above is a floppy drive emulator for Macintosh. [Steve Chamberlain] has been hand assembling these and selling them in small runs, but is troubled by about a 4% burn-out rate for the CPLD which has the red ‘X’ on it. He settled into figure out what exactly is leading to this and it’s a real head-scratcher.
He does a very good job of trouble-shooting, starting with a list of all the possible things he thinks could be causing this: defective part, bad PCB, bad uC firmware, damage during assembly, solder short, tolerance issues, over-voltage on the DB connector, or bad VHDL design. He methodically eliminates these, first by swapping out the part and observing the exact same failure (pretty much eliminates assembly, solder short, etc.), then by measuring and scoping around the card.
The fascinating read doesn’t stop with the article. Make sure you work your way through the comments thread. [Steve] thinks he’s eliminated the idea of bad microcontroller code causing damage. He considers putting in-line resistors on the DB connector but we wonder if clamping diodes wouldn’t be a better choice (at least for testing purposes)? This begs the question, why is he observing a higher voltage on those I/O lines during power-up? As always, we want to hear your constructive comments below.
Fail of the Week is a Hackaday column which runs every Wednesday. 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.
We’re sure you’ve all been waiting on the edge of your seats to see whose project makes it as the first Hackaday Fail of the Week. Wait no longer, it’s [Mobile Will] with his woeful tale about monitoring AC current usage.
He had been working on a microcontroller actuated mains outlet project and wanted an accurate way to measure the AC current being used by the device connected to it. The ADE7753 energy metering IC was perfect for this so he designed the board above and ordered it up from OSH Park. After populating the components he hooked it up to his Arduino for a test run, and poof! Magic blue smoke arose from the board. As you’ve probably guessed — this also fried the Arduino, actually melting the plastic housing of the jumper wire that carried the rampant current. Thanks to the designers of the USB portion of his motherboard he didn’t lose the computer to as the current protection kicked in, requiring a reboot to reset it.
We can’t wait to hear the conversation in the comments. But as this is our first FotW post we’d like to remind you: [Mobile Will] already knows he screwed up, so no ripping on his skills or other non-productive dibble. Let’s keep this conversation productive, like what caused this? He still isn’t completely sure and that would be useful information for designing future iterations. Update: here’s the schematic and board artwork.
We’ve got a bit more to share in this post so keep reading after the break.
Continue reading “Fail of the Week: Inaugural Edition”
Unfortunately [manekinen] wrecked a couple of AVRs during his tinkering. Not letting this get him down he decided to blow them up to see what would happen. In exchange for their precious magic smoke the AVRs revealed a good portion of their silicon die.
While the details are a little sparse it seems like he hooked them up to a high (and possibly reverse) source to blow open the chips casing. From the pictures it looks like he was able to reveal some of the flash or SRAM (the big multi colored rectangles) and what could possibly be the power supply. Be sure to checkout the videos after the break for some silicon carnage.
Continue reading “Exploding an AVR”