[Carl] wanted to put his force sensors on a transparent PCB and had to ask his board vendor for a special sample. Flexible PCBs are available on transparent substrates made of PET, but they are not as common as polyimide boards. As [Carl] found out, these boards are a bit thicker, a bit less flexible, and don’t hold up to very high heat as well as the standard boards. Undeterred, he designed a 3D Christmas tree using the clear boards. The result that you can see in the video below looks pretty good and would have been hard to duplicate with conventional means.
When you build the board it is as a flat spiral, but lifting it in the center allows it to expand into a conical tree shape. The circuit itself is just an LED blinker, but the flexible board is the interesting part.
We know what you’re thinking. It’s a bad power supply, of course it was capacitors to blame. But even if we all intuitively know at this point that bad caps are almost always the culprit when a PSU gives up the ghost, it’s not always easy to figure out which one is to blame. Which is why this deep dive into a failed ETK450AWT by [eigma] is worth a look.
The first sign of trouble was when the computer would unexpectedly reboot with nothing in the system logs to indicate a problem. Eventually, [eigma] noticed a restart before the operating system even loaded, which confirmed the hardware was to blame. A quick look at the PSU output with a voltmeter showed things weren’t too far out of spec, but putting an oscilloscope on the 12 V line uncovered a nasty waveform that demanded further investigation.
Connecting all the dots.
By carefully following traces and comparing with common PSU diagrams, [eigma] was able to identify the SG5616 IC that checks the various voltages being produced by the PSU and generates the PWR_OK signal which tells the motherboard that everything is working normally. As before, all of the DC voltages at this chip seemed reasonable enough, but the pin that was measuring AC voltage from the transformer was showing the same ripple visible on the 12 VDC line.
Even more digging uncovered that the transformer itself had a control IC nestled away. The 13 VDC required by this chip to operate is pulled off the standby transformer by way of a Zener diode and a couple capacitors, but as [eigma] soon found, the circuit was producing another nasty ripple. Throwing a few new capacitors into the mix smoothed things out and got the PSU to kick on, but that’s not quite the end of the story.
Pulling the capacitors from the board and checking their values with the meter, [eigma] found they too appeared to be within reasonable enough limits. They even looked in good shape physically. But with the help of a signal generator, he was able to determine their equivalent series resistance (ESR) was way too high. Case closed.
Even if you aren’t an electronics person, you probably have a working knowledge of circuit breakers. When the lights go out, you find the circuit breaker and flip it back to the on position. Most people understand, too, that the breaker will trip if you overload the circuit with too many things plugged in or with an accidental short circuit. But how does this common device actually work? Keep in mind, circuit breakers need to be super reliable and have been around long enough that you can imagine they are pretty low tech. [Learn Engineering] has a very clear video about what goes on inside a circuit breaker that’s worth the eight minutes to watch. You can see the video below.
The handle is a mechanical engineering marvel, using two springs and a special design so that even a tiny force will cause it to snap to the off position. That takes care of a human tripping it. However, you have two other cases where you want to turn it off: overload and short circuit.
I fell in love with cable driven mechanisms a few years ago and put together some of my first mechanical tentacles to celebrate. But only after playing with them did I start to understand the principles that made them work. Today I want to share one of the most important equations to keep in mind when designing any device that involves cables, the capstan equation. Let some caffeine kick in and stick with me over the next few minutes to get a sense of how it works, how it affects the overall friction in your system, and how you can put it to work for you in special cases.
A Quick Refresher: Push-Pull Cable Driven Mechanisms
But first: just what exactly are cable driven mechanisms? It turns out that this term refers to a huge class of mechanisms, so we’ll limit our scope just to push-pull cable actuation systems.
These are devices where cables are used as actuators. By sending these cables through a flexible conduit, they serve a similar function to the tendons in our body that actuate our fingers. When designing these, we generally assume that the cables are both flexible and do not stretch when put in tension. Continue reading “Cable Mechanism Maths: Designing Against The Capstan Equation”→
When Pong hit the scene in the early 70s, there was something about the simplicity of the 2D monochrome tennis game that made it engaging enough that enthusiastic proto-gamers shorted-out machines by stuffing their coin boxes to overflowing. But even with the simplicity of Pong’s 2D gameplay, the question becomes: could it by made simpler and still be playable?
Surprisingly, if this one-dimensional Pong game is any indication, it actually seems like it can. Where the original Pong made you line up your paddle with the incoming ball, with the main variable being the angle of the carom from your opponent, [mircemk]’s version, limited to a linear game field, makes the ball’s speed the variable. Players take control of the game with a pair of buttons at the far ends of a 60-LED strip of WS2812s. The ball travels back and forth along the strip, bouncing off a player’s paddle only if they push their button at the exact moment the ball arrives. Each reflection back to the opponent occurs at a random speed, making it hard to get into a rhythm. To add some variety, each player has a “Boost” button to put a little spice on their shot, and score is kept by LEDs in the center of the play field. Video of the game play plus build info is below the break.
With just a Neopixel strip, an Arduino Nano, and a small handful of common parts, it should be easy enough to whip up your own copy of this surprisingly engaging game. But if the 2D-version is still more your speed, maybe you should check out the story of its inventor, [Ted Dabney]. Or, perhaps building a clock that plays Pong with itself to idle the days away is more your speed.
Linux users are more likely than most to be familiar with Chromium, Google’s the free and open source web project that serves as the basis for their wildly popular Chrome. Since the project’s inception over a decade ago, users have been able to compile the BSD licensed code into a browser that’s almost the same as the closed-source Chrome. As such, most distributions offer their own package for the browser and some even include it in the base install. Unfortunately, that may be changing soon.
A post made earlier this month to the official Chromium Blog explained that an audit had determined “third-party Chromium based browsers” were using APIs that were intended only for Google’s internal use. In response, any browser attempting to access features such as Chrome Sync with an unofficial API key would be prevented from doing so after March 15th.
To the average Chromium user, this doesn’t sound like much of a problem. In fact, you might even assume it doesn’t apply to you. The language used in the post makes it sound like Google is referring to browsers which are spun off of the Chromium codebase, and at least in part, they are. But the search giant is also using this opportunity to codify their belief that the only official Chromium builds are the ones that they provide themselves. With that simple change, anyone using a distribution-specific build of Chromium just became persona non grata.
Unhappy with the idea of giving users a semi-functional browser, the Chromium maintainers for several distributions such as Arch Linux and Fedora have said they’re considering pulling the package from their respective repositories altogether. With a Google representative confirming the change is coming regardless of community feedback, it seems likely more distributions will follow suit.
If you ever watched Dr. Who, you probably know that the TARDIS looked like a police call box on the outside, but was very large on the inside. When asked, the Doctor had some explanation of how something can look small when it is far away and large when it is close up, which never made much sense. However, [iQLess] has been 3D printing boxes in a small area, that fold out to be much larger boxes. (Video, embedded below.) The design comes from someone called [Cisco] who has a lot of interesting print in place designs.
You can find the design on the Prusa site or Thingiverse. The boxes do take a while to print, according to the video below. What was interesting to us, though, is that you should be able to print a design like this to create a box larger than your printer.
