How The 2020s Chip Crisis Led To A Buggy Saleae Analyzer In 2026

For those of us old enough to remember the harrowing days of the early 2020s, alongside another major kerfuffle there was a complete breakdown in global supply chains that led to the 2020-2023 global chip shortage. Unsurprisingly, this pushed many hardware manufacturers into less orthodox approaches, massive BOM changes, and hurried redesigns. One of the results of this era found its way into the hands of the bloke over at the [Playduino] YouTube channel, who was mystified to find two bodge wires in his fancy Saleae logic analyzer.

The reason for popping open the LA was crosstalk between two channels, which was bad enough that it made the unit quite unusable for the intended task. After seeing the cut traces and bodge wires he initially assumed that since he bought it used that the previous owner had modified it, but said person denied having opened it since purchasing it from an official retailer.

This was when he emailed Saleae support to see whether they knew anything. Initially they denied knowing anything about such a modification, but then the CTO emailed back with a long and very detailed confession. As explained in the video, during the aforementioned chip crisis Saleae was forced to rapidly redesign their LAs to use whatever FPGAs and other parts they could still get their hands on.

An initial prototype unit passed their internal tests, so they had a first batch manufactured using PCBs from a different supplier. Despite sending the same Gerber files, the resulting PCBs had ground fill issues that necessitated the observed rework, but due to insufficient testing for crosstalk a total of 406 units made it into the wild.

Sadly he had to return the defective unit for a replacement, making it somewhat hard to let go of such a piece of history. That said, if you want to know whether you’re also one of the lucky remaining 405 LA owners, the CTO provided the affected serial number range: 00200026245 to 00200026675 are affected.

Continue reading “How The 2020s Chip Crisis Led To A Buggy Saleae Analyzer In 2026”

4-bit Relay Logic Counter Begs To Have Its Buttons Pushed

What’s one to do with some nice little relays of questionable pinout, and prototyping board? How about a quietly clicky 4-bit counter using relay logic with tons of buttons?

The register with LEDs and buttons is on the top board, the incrementer on the bottom board.

[Agatha Mallett] made the counter after finding herself in possession of a quantity of relays burdened by terrible documentation (the datasheet shockingly lacks a pinout, and doesn’t even mention the coil being unidirectional). But since the relays are also small and of decent quality, they were a good candidate for a small relay logic-based project.

The key to the build is implementing D-type flip-flops using relays. This is done by holding the coil voltage of each relay between its set and release voltage levels. A small voltage bump will energize the coil, closing the relay and leaving it closed. Conversely, a small negative spike releases the coil, leaving it open. This forms the basis of the counter, and [Agatha] has a separate write-up all about the details of using relays in this way.

Implementing this was rather less straightforward than it may sound because it relies on balancing the coils of many relays on a figurative knife-edge of voltage, but not every component is perfectly identical. A tweaked resistor or capacitor here and there was needed before things settled into reliability.

The end product has indicator LEDs, buttons to increment or clear the current count, and it even has buttons to set or clear individual bits. This is a project that begs to be interacted with, and there’s a short video on the project page so you can watch it go through its paces.

Thanks to [Jess] for the tip!

RS-485 Sprinkler system

RS-485 Sprinkler Control: Scaling Irrigation Across The Farm

Building your own sprinkler system controller isn’t that difficult on the face of it, but what happens when your system starts to grow, adding more distant areas? To tackle this, [Vinnie] leveraged the tried-and-true RS-485 differential pairs to communicate reliably with ever-more-spread-out valves on his farm’s irrigation system.

The system uses a Raspberry Pi to control when each valve turns on and for how long. It does this via a custom RS-485 valve master board, whose code and design files are on GitHub. The master board communicates with the Pi over I2C and issues RS-485 commands while controlling the 12V line to the valves. Toggling the 12V supply is a smart move it lets [Vinnie] save power by not keeping the valves energized when idle.

At the valves themselves lives a valve node board (also on the GitHub repo). Each node has a unique address so it knows when its name is called to open or close a valve. The valves are latching solenoids, ideal because they don’t require constant current during the watering cycle. The Valve Nodes also support their own protocol to report state, firmware version, and allow in-situ configuration.

Be sure to head over to [Vinnie]’s project page and check out all the work that went into this great DIY irrigation control system, along with the thoughtful boards and tools he made to help others set it up. This is a welcome addition to the sprinkler-related projects we’ve seen.

How To Avoid Failed Screw Holes In 3D Printed Parts

Screws are useful fasteners for 3D prints, but the effectiveness of a screw (not to mention the ease or hassle of insertion) depends on the hole itself. This comprehensive guide on how to design screw holes in 3D printed parts takes guesswork out by providing reference tables as well as useful general tips.

The guide provides handy tables saying exactly how big to design a hole depending on screw type, material (PLA, PETG, or high-flow PETG) and whether the hole is printed in a vertical or horizontal orientation. This takes the guesswork out of screw hole design.

There’s no reason to guess the right size of hole for a screw, just refer to some handy tables.

The reason for different numbers is because multiple (but predictable) variables affect a 3D-printed hole’s final dimensions. Shrinkage, filament properties, and printing orientation can all measurably affect small features like screw holes; accounting for these is the difference between a good fit, and cracking or stripping.

In addition to the tables, there are loads of other useful tips. Designing lead-ins makes screws easier to insert and engage, and while increasing walls is an easy way to add strength it’s also possible to use 3D-printed microfeatures which are more resistant to distortion and don’t depend on slicer settings. There’s even suggested torque amounts for different screw and material types.

Sure, the most reliable way to get a hole of a known size is to drill it out yourself. But that’s an extra step, and drill bits aren’t always at hand in the desired sizes. The guide shows that it is entirely possible to print an ideal screw hole by taking a few variables into account.

If your design calls for screws, be sure to check it out and see if there’s anything you can use in your own designs.

A Guide To CubeSat Mission And Bus Design

If you mention the word bus, you might think of public transportation or, more likely for us, a way to connect things together. But in the satellite world, the bus is the part of a vehicle that supports the payload but isn’t itself the payload. Typically, that means the electric power system, propulsion, radios, and thermal control, among other systems. If you are designing a CubeSat, you will want to read A Guide to CubeSat Mission and Bus Design by [Frances Zhu].

The Creative Commons-licensed book has twelve chapters, ranging from systems engineering — that is, defining what you want to do — to analyzing structures, handling power, setting up communications, and more. Of particular interest to us was the chapter on command and data handling. The final chapters cover software, system integration, and there’s even a chapter on Ethics.

If you want to build a CubeSat or just want to learn more about how satellites actually work, this is a great read. There are videos and other features, too. If you don’t like reading in your browser, you can download an EPUB, PDF, or MOBI near the top of the page.

There are many resources for the want-to-be CubeSat builder. You can even start with an open source design.

Do We Really Need Another Development Board?

It’s fair to say that there are a lot of development board form factors for MCUs, with [Tech Dregs] over on yonder YouTube on the verge of adding another one to the pile, but not before he was having some serious thoughts on the implications of such a decision. Does this world really need another devboard with the ubiquitous 2.54 mm (0.1″) pitch pin headers, all so that it can perhaps be used in the same traditional 2.54 mm pitch breadboards?

The thought that [Tech Dregs] is playing with is to go for something more akin to the system-on-module  (SoM) approach that’s reminiscent of the Raspberry Pi compute module form factor. This means using a 1 mm pitch for the headers and castellated edges in case you want use it as an SMT part, while breaking out many more pins of the onboard ESP32 module in far less space.

Obviously, the main advantage of this approach is that much like with compute modules you can leave most of the tedious cheap stuff on a carrier board, while the expensive to manufacture components are on a self-contained module. Meanwhile with the much finer pitch on the SoM contacts it’d straddle the divide between a 2.54 mm breadboard-capable devboard and a fully custom PCB, while making any mistakes on the carrier board much cheaper to redo.

The counterpoint here is of course that something like an ESP32 module is already a module with a finer pitch, but if you need more than just what it offers, or you want to use an STM32 or RP MCU across boards it could make a lot of sense.

Having 1 mm pitch breadboards would honestly also be rather nifty, natch. That said, what are your thoughts on this matter?

Continue reading “Do We Really Need Another Development Board?”

A prototype VLIW computer made by Multiflow

A History On The “Impossible” VLIW Computing

A computer does one thing at a time, even if it feels like it’s doing multiple things at once. In reality, it’s just switching between tasks very quickly. But a VLIW (Very Long Instruction Word) computer is different. Today, [Asianometry] tells us about VLIW computing and its history.

Processors have multiple functional units; for example, you might have separate units each for addition, multiplication and division. But because it runs one instruction at a time, these units tend to spend a large amount of time idle. VLIW aims to address this inefficiency by reinventing what an instruction means. Instead of telling the whole processor what to do, a VLIW instruction tells each functional unit what to do at once. Sounds good, right? Well, that was the easy part.

The hard part? How to compile a program for a VLIW computer, that can actually make use of all the functional units at once; after all, the efficiency promise is that the higher activity makes up for larger instruction words to fetch. That is the compiler’s job; VLIW compilers try to reschedule the operations in the program to convert sequential code into more parallel operations then compiled into the titular very long instruction words.

[Asianometry] goes into detail about this, the history, and more in the video after the break.
Continue reading “A History On The “Impossible” VLIW Computing”