We think it’s OK to admit that when someone puts a binary display on a project, it’s just a thinly veiled excuse to get more blinkenlights into the world. That and it’s a way to flex a little on the normies; you’ve gone pretty far down the tech rabbit hole to quickly decipher something like this binary-display thermometer, after all.

Don’t get us wrong, we think those are both perfectly valid reasons for going binary. And all things considered, a binary display for a thermometer like [Clovis Fritzen]’s is much simpler to decode than, say, a clock. Plus, it seems a bit that this build was undertaken at least partially as an exercise in Charlieplexing, which [Clovis] uses to drive the six-bit LED display using only three lines of GPIO from the Digispark ATtiny85 board running the show.

The temperature sensor is a DHT11, whose output is read by the microcontroller before being converted to binary and sent to the six-bit display. The 64-degree range is perfect for displaying the full range of temperatures most of us would consider normal, although we’d find 63°C a touch torrid so maybe there’s a little too much resolution on the upper end of the scale. Then again, switching to Fahrenheit would shift it toward the hypothermia end of the scale, which isn’t helpful. And you can just forget about Kelvin.

If there’s one thing we like better around here than old, obscure displays, it’s old, obscure displays with no documentation that need a healthy dose of reverse engineering before they can be put to use. These Plessey dot-matrix displays are a perfect example of that.

We’re not sure where [Michael] scored these displays, but they look fantastic. Each 8-pin DIP has two 5×7-matrix, high-visibility LED displays. They bear date codes from the late 80s under the part number, GPD340, but sadly, precious little data about them could be dredged up from the Interwebz. With 70 pixels and only six pins after accounting for power and ground, [Michael] figured there would be a serial protocol involved, but which pins?

He decided to brute-force the process of locating them, using a Pico to sequentially drive every combination while monitoring the current used with a current sensor. This paid off after only a few minutes, revealing that each character of the display has its own clock and data pins. The protocol is simple: pull the clock and data pins high then send 35 bits, which the display sorts out and lights the corresponding pixels. The video below shows a 12-character scrolling display in action.

Plessey made a lot of displays for military hardware, and these chunky little modules certainly have a martial air about them. Given that and the date code, these might have come from a Cold War-era bit of military hardware, like this Howitzer data display which sports another Plessey-made display.

[Carl Bugeja] finds the engineering behind the Las Vegas Sphere fascinating, and made a video all about the experience of designing and building a micro-sized desktop version. [Carl]’s version is about the size of a baseball and crams nearly a thousand RGB pixels across the surface.

Putting that many addressable LEDs — even tiny 1 mm x 1 mm ones — across a rounded surface isn’t exactly trivial. [Carl]’s favored approach ended up relying on a flexible four-layer PCB and using clever design and math to lay out an unusual panel shape which covers a small 3D printed geodesic dome.

Much easier said that done, by the way. All kinds of things can and do go wrong, from an un-fixable short in the first version to adhesive and durability issues in later prototypes. In the end, however, it’s a success. Powered over USB-C, his mini “sphere” can display a variety of patterns and reactive emojis.

As elegant and impressive as the engineering is in this dense little display, [Carl] has some mixed feelings about the results. 945 individual pixels on such a small object is a lot, but it also ends up being fairly low-resolution in the end. It isn’t very good at displaying sharp lines or borders, so any familiar shapes (like circles or eyes) come out kind of ragged. It’s also expensive. The tiny LEDs may be only about 5 cents each, but when one needs nearly a thousand of them for one prototype that adds up quickly. The whole bill of materials comes out to roughly $250 USD after adding up the components, PCB, controller, and mechanical parts. It’s certainly a wildly different build than its distant cousin, the RGB cube.

Still, it’s an awfully slick little build. [Carl] doubts there’s much value in pursuing the idea further, but there are plenty of great images and clips from the build. Check out the video, embedded below.

[Nick Lombardy] took on a job almost every maker imagines themselves doing at some point. He built a giant LED wall and he did a damn fine job of it, too. Introducing BoneBlocker.

BoneBlocker is an 8 x 14 wall of glass blocks that lives at a bar called Coin-Op. Each block was given a length of WS2812B LED strip. 30 LED/meter strips were chosen, as initial maths on the 60 LED/meter strips indicated the whole wall would end up drawing 1.5 kW. Discretion, and all that.

The whole display is run from a WT32-ETH01 board, which is a fast ESP32-based module that has onboard Ethernet to boot. [Nick] used the WLED library as he’d seen others doing great things with it, performance-wise. He ended up using one board per column to keep things fast, but he reckons this was also probably a little bit of overkill.

His article steps through the construction of the wall, the electronics, and the software required to get some games working on the display. The final result is quite something. Perhaps the best bit is his explanation of the custom controller he built for the game. Dig into it, you won’t be disappointed.

In particular, we love how the glass blocks elevate this display to a higher aesthetic level. We’ve seen other great projects tread this same route, too. Video after the break.