Books You Should Read: Why Buildings Fall Down

People with long commutes usually come up with tricks to stay focused and alert and avoid the dangerous tendency to zone out during the drive. One trick I used to use was keeping mental track of the various construction projects I’d pass by on my way to work, noticing which piers on a new highway overpass were nearing completion, or watching steelworkers put together the complex rebar endoskeletons of a new stretch of roadway.

One project I loved to watch back in the 80s was a new high-rise going in right next to the highway, which fascinated me because of the construction method. Rather than putting together a steel frame, laying out decking, and covering each floor with concrete, the workers seemed to be fabricating each floor at ground level and then jacking them up on the vertical steel columns. I was fascinated by this because every time I passed by the floors were in a different position, spreading out vertically as the building grew.

And then one day, it just wasn’t there anymore. Where there had been columns stretching nine stories into the city sky with concrete slabs lined up ready to be jacked up into their final positions, there was just an enormous hole in the ground with a ghastly gray cloud of concrete dust rising from it. It was April 23, 1987, and what was once going to be a luxury apartment building called L’Ambience Plaza in Bridgeport, Connecticut lay pancaked into the ground, entombing the bodies of 28 construction workers.

Continue reading “Books You Should Read: Why Buildings Fall Down”

Pre-exploded PSU close-up: shown is inductor with the heatsink it shorted against.

The Little Replacement PSU That Could: Kill A Microsoft Surface And Monitor

Recently [Big Clive], everyone’s favorite purveyor of anything electronic that’s dodgy, cheap, cheerful, decidedly crispy or any combination thereof, got sent a very dead external power supply unit. Being clearly a third-party PSU with poorly written and many (likely not truthful) safety approval markings on its label, this PSU had the dubious honor of having destroyed a Microsoft Surface computer as well as the monitor that was connected at the time.

In [Clive]’s video (also embedded after the break) the black and very crispy board is examined, showing a wealth of vaporized traces and plenty of soot. What’s however most fascinating is the failure mode: instead of something obvious like e.g. the main transformer between the primary and secondary side failing, here it would seem that an inductor (see heading image) on the secondary side had its insulation rubbed off and shorted on a nearby heatsink. A heatsink that just happened to be also electrically connected on the primary (mains-level) side.

Judging by the former owner’s report and aftermath, this led to a very sudden and violent demise of the PSU, with mains power very likely making its way into the unsuspecting Surface system and connected monitor. The number of ‘very nope’ design decisions made in this PSU are astounding, and a lesson for both aspiring EEs and anyone considering getting a ‘cheap’ third-party replacement PSU.

(Thanks to [Helge] for the tip)

Continue reading “The Little Replacement PSU That Could: Kill A Microsoft Surface And Monitor”

Crossed Wires Crash Rockets

On November 17th, a Vega rocket lifted off from French Guiana with its payload of two Earth observation satellites. The booster, coincidentally the 17th Vega to fly, performed perfectly: the solid-propellant rocket engines that make up its first three stages burned in succession. But soon after the fourth stage of the Vega ignited its liquid-fueled RD-843 engine, it became clear that something was very wrong. While telemetry showed the engine was operating as expected, the vehicle’s trajectory and acceleration started to deviate from the expected values.

There was no dramatic moment that would have indicated to the casual observer that the booster had failed. But by the time the mission clock had hit twelve minutes, there was no denying that the vehicle wasn’t going to make its intended orbit. While the live stream hosts continued extolling the virtues of the Vega rocket and the scientific payloads it carried, the screens behind them showed that the mission was doomed.

Displays behind the hosts clearly showed Vega wasn’t following the planned trajectory.

Unfortunately, there’s little room for error when it comes to spaceflight. Despite reaching a peak altitude of roughly 250 kilometers (155 miles), the Vega’s Attitude Vernier Upper Module (AVUM) failed to maintain the velocity and heading necessary to achieve orbit. Eventually the AVUM and the two satellites it carried came crashing back down to Earth, reportedly impacting an uninhabited area not far from where the third stage was expected to fall.

Although we’ve gotten a lot better at it, getting to space remains exceptionally difficult. It’s an inescapable reality that rockets will occasionally fail and their payloads will be lost. Yet the fact that Vega has had two failures in as many years is somewhat troubling, especially since the booster has only flown 17 missions so far. A success rate of 88% isn’t terrible, but it’s certainly on the lower end of the spectrum. For comparison, boosters such as the Soyuz, Falcon 9, and Atlas have success rates of 95% or higher.

Further failures could erode customer trust in the relatively new rocket, which has only been flying since 2012 and is facing stiff competition from commercial launch providers. If Vega is to become the European workhorse that operator Arianespace hopes, figuring out what went wrong on this launch and making sure it never happens again is of the utmost importance.

Continue reading “Crossed Wires Crash Rockets”

Lessons Learned From A CubeSat Postmortem

On the 3rd of June 2019, a 1U CubeSat developed by students of the AGH University of Science and Technology in Kraków was released from the International Space Station. Within a few hours it was clear something was wrong, and by July 30th, the satellite was barely functional. A number of problems contributed to the gradual degradation of the KRAKsat spacecraft, which the team has thoroughly documented in a recently released paper.

We all know, at least in a general sense, that building and operating a spacecraft is an exceptionally difficult task on a technical level. But reading through the 20-pages of “KRAKsat Lessons Learned” gives you practical examples of just how many things can go wrong.

KRAKsat being released from the ISS

It all started with a steadily decreasing battery voltage. The voltage was dropping slowly enough that the team knew the solar panels were doing something, but unfortunately the KRAKsat didn’t have a way of reporting their output. This made it difficult to diagnose the energy deficit, but the team believes the issue may have been that the tumbling of the spacecraft meant the panels weren’t exposed to the amount of direct sunlight they had anticipated.

This slow energy drain continued until the voltage dropped to the point that the power supply shut down, and that’s were things really started going south. Once the satellite shut down the batteries were able to start charging back up, which normally would have been a good thing. But unfortunately the KRAKsat had no mechanism to remain powered down once the voltage climbed back above the shutoff threshold. This caused the satellite to enter into and loop where it would reboot itself as many as 150 times per orbit (approximately 90 minutes).

The paper then goes into a laundry list of other problems that contributed to KRAKsat’s failure. For example, the satellite had redundant radios onboard, but the software on them wasn’t identical. When they needed to switch over to the secondary radio, they found that a glitch in its software meant it was unable to access some portions of the onboard flash storage. The team also identified the lack of a filesystem on the flash storage as another stumbling block; having to pull things out using a pointer and the specific memory address was a cumbersome and time consuming task made all the more difficult by the spacecraft’s deteriorating condition.

Of course, building a satellite that was able to operate for a couple weeks is still an impressive achievement for a student team. As we’ve seen recently, even the pros can run into some serious technical issues once the spacecraft leaves the lab and is operating on its own.

[Thanks to ppkt for the tip.]

Fail Of The Week: Thermostat Almost Causes A House Fire

Fair warning: any homeowners who have thermostats similar to the one that nearly burned down [Kerry Wong]’s house might be in store for a sleepless night or two, at least until they inspect and perhaps replace any units that are even remotely as sketchy as what he found when he did the postmortem analysis in the brief video below.

The story begins back in the 1980s, when the Southern New England area where [Kerry] lives enjoyed a housing boom. Contractors rushed to turn rural farmland into subdivisions, and new suburbs crawled across the landscape. Corners were inevitably cut during construction, and one common place to save money was the home’s heating system. Rather than engage an HVAC subcontractor to install a complicated heating system, many builders opted instead to have the electricians install electric baseboards. They were already on the job anyway, and at the time, both copper and electricity were cheap.

Fast forward 40 years or so, and [Kerry] finds himself living in one such house. The other night, upon catching the acrid scent of burning insulation, he followed his nose to the source: a wall-mounted thermostat for his electric baseboard. His teardown revealed burned insulation, bare conductors, and scorched plastic on the not-so-old unit; bearing a 2008 date code, the thermostat must have replaced one of the originals. [Kerry] poked at the nearly combusted unit and found the root cause: the spot welds holding the wires to the thermostat terminal had become loose, increasing the resistance of the connection. As [Kerry] points out, even a tenth of an ohm increase in resistance in a 15 amp circuit would dissipate 20 watts of heat, and from the toasty look of the thermostat it had been a lot more than that.

The corner-cutting of the 1980s was nothing new, of course – remember the aluminum wiring debacle? Electrical fires are no joke, and we’re glad [Kerry] was quick to locate the problem and prevent it from spreading.

Continue reading “Fail Of The Week: Thermostat Almost Causes A House Fire”

Nixie Clock Failure Analysis, [Dalibor Farný] Style

We’ve become sadly accustomed to consumer devices that seem to give up the ghost right after the warranty period expires. And even when we get “lucky” and the device fails while it’s still covered, chances are that there will be no attempt to repair it; the unit will be replaced with a new one, and the failed one will get pitched in the e-waste bin.

Not every manufacturer takes this approach, however. When premium quality is the keystone of your brand, you need to take field failures seriously. [Dalibor Farný], maker of high-end Nixie tubes and the sleek, sophisticated clocks they plug into, realizes this, and a new video goes into depth about the process he uses to diagnose issues and prevent them in the future.

One clock with a digit stuck off was traced to via failure by barrel fatigue, or the board material cracking inside the via hole and breaking the plated-through copper. This prompted a board redesign to increase the diameter of all the vias, eliminating that failure mode. Another clock had a digit stuck on, which ended up being a short to ground caused by pin misalignment; when the tube was plugged in, the pins slipped and scraped some solder off the socket and onto the ground plane of the board. That resulted in another redesign that not only fixed the problem by eliminating the ground plane on the upper side of the board, but also improved the aesthetics of the board dramatically.

As with all things [Dalibor], the video is a feast for the eyes with the warm orange glow in the polished glass and chrome tubes contrasting with the bead-blasted aluminum chassis. If you haven’t watched the “making of” video yet, you’ve got to check that out too.

Continue reading “Nixie Clock Failure Analysis, [Dalibor Farný] Style”

A Post-Mortem For An Electric Car Charger

[Mastro Gippo] recently purchased a wall mounted charger for his electric car that looked great and had all the bells and whistles he wanted. There was only one problem: the thing burned up on him. Looking to find out how this seemingly high-end piece of hardware gave up the ghost so easily, he took it apart and tried to figure out where things went wrong. While he’s not looking to sling any mud and actually name the company who produced the charger, he certainly has some choice words for whoever green-lit this particular design.

With the charger open, there’s little doubt that something became very toasty inside. A large swath of the PCB has a black char mark on it, and in some places it looks like the board burned right through. After a close examination, [Mastro] is of the opinion that the board heated up to the point that the solder actually liquified on some connections. This conductive flow then shorted out components below it, and things went from bad to worse.

But where did all the heat come from? [Mastro] was stunned to see that a number of the components inside the charger were only rated for 30 amps, despite the label for the product clearly stating it’s good for up to 32A. With components pushed past their limits, something had to give. He wonders how such a device could have made it through the certification process; an excellent question we’d love to know the answer to.

The worst part is, it looks like the designers might have even known there was an overheating issue. [Mastro] notes that there are heatsinks bolted not to a component as you might assume, but directly to the PCB itself. We’ve seen what happens when designers take a cavalier attitude towards overheating components, and the fact that something like an electric vehicle charger was designed so poorly is quite concerning.