Angry Birds, flash mobs, Russell Brand, fidget spinners. All of these were virtually unavoidable in the previous decade, and yet, like so many popular trends, have now largely faded into obscurity. But in a recent announcement, the developers of LightBurn have brought back a relic of the past that we thought was all but buried along with Harambe — popular software not supporting Linux.

But this isn’t a case of the developers not wanting to bring their software to Linux. LightBurn, the defacto tool for controlling hobbyist laser cutters and engravers, was already multi-platform. Looking forward, however, the developers claim that too much of their time is spent supporting and packaging the software for Linux relative to the size of the user base. In an announcement email sent out to users, they reached even deeper into the mid-2000s bag of excuses, and cited the number of Linux distributions as a further challenge:

The segmentation of Linux distributions complicates these burdens further — we’ve had to provide three separate packages for the versions of Linux we officially support, and still encounter frequent compatibility issues on those distributions (or closely related distributions), to say nothing of the many distributions we have been asked to support.

We’re not sure how much of their time could possibly be taken up by responding to requests for supporting additional distributions (especially when the answer is no), but apparently, it was enough that they finally had to put their foot down — the upcoming 1.7.00 release of LightBurn will be the last to run on Linux.

To really add insult to injury, LightBurn is paid software, with users having to purchase a yearly license after the time-limited demo period. Accordingly, any Linux users who recently purchased a year’s license for the software can ask for a refund. Oh, and if you’re holding out hope that the community can swoop in and take over maintaining the Linux builds, don’t — LightBurn is closed source.

While there are open source projects like LaserWeb that can be used to control these types of machines regardless of what operating system you’re running, losing LightBurn on Linux definitely hurts. While we try not to put our stamp on closed source proprietary software because of situations exactly like this one, we have to admit that LightBurn was a nice tool, especially when compared to the joke software that many of these lasers ship with.

The developers end their notice to Linux users with what seems like a particularly cruel kick while they’re already down:

Rest assured that we will be using the time gained by sunsetting Linux support to redouble our efforts at making better software for laser cutters, and beyond. We hope you will continue to utilize LightBurn on a supported operating system going forward, and we thank you for being a part of the LightBurn community.

So take comfort, Linux users — LightBurn will emerge from this decision better than ever. Unfortunately, you just won’t be able to use it.

These days, laptop computers are all more or less the same, at least externally. Some are thicker than others, they might come in different colors, or with a 360° hinge that lets you flip the screen around the back and use it as a tablet, but overall they’ve all got the same shape and proportions. The industry, and indeed the users, eventually agreed on the best way to make a computer portable and are now fully committed to it.

But that wasn’t always the case. In the 1980s there were a number of laptops from the likes of Toshiba, Tandy, and even IBM that took a slightly different approach to the clamshell design. These computers featured ultra-wide displays with a hinge located closer to the center of the computer, giving the machine a distinctive “trunk” in the back. It’s these classic machines that clearly inspired [Michael Mayer] to design the Portable Pi 84.

[Michael] says that the 3D printed enclosure was largely designed around the 40% ortholinear keyboard, which itself is based on the Happy-Keyboard from [Luis Alegría]. The rest apparently just fell into place, such as the fact that the 1600 x 600 Waveshare 9.3 inch display happens to be almost the perfect size to cover the keyboard below it.

Compared to many of the other custom computer builds we’ve covered, the rear compartment of the Portable Pi 84 provides ample free space for the various system components. That includes the Raspberry Pi 4 that runs the show, a UPS “hat” that powers the system via a pair of 21700 batteries, and even a set of amplified speakers. It looks like there’s still plenty of room in the back for additional gear, such as an RTL-SDR or perhaps even a cartridge slot.

A particularly nice feature of this build are the inset panels on the rear of the machine, which allow for the various ports and connectors to be reconfigured by the user without having to re-print the entire case — one could imagine a replacement panel that features a connector for an external WiFi antenna, for example. We also like the use of heat-set inserts throughout the case, which will not only make the build sturdier, but means the case can be opened and closed regularly without fear of stripping out the screw holes.

So is this a computer or a cyberdeck? It’s hard to say. We tend to think that a proper deck needs to have a more unique physical layout, and technically this form factor was actually fairly popular at one point. But whatever you want to call builds like this, we’re stoked to see them become more common and better documented. Long live the truly personal computer.

If you’ve ever built a model rocket, you’ll know there’s not a whole lot to them. Essentially it’s a cardboard tube, a plastic nosecone, some fins, and a little clip that will keep it riding the launch rail as it accelerates off the pad. Extra points awarded if you add in a parachute, but strictly speaking, even that’s a luxury. Stick an Estes motor in that thing and send it.

But pointing out that lightweight cardboard tubes can be tricky to ship without getting crushed, [Concrete Dog] has come up with HEXA, a clever model rocket kit that uses pre-scored cardstock instead. The immediate advantage is that this allows the rocket to be shipped as flat sheets of material, but as a secondary bonus, once folded into its final shape the rocket has an awesome hexagonal cross section.

As with a traditional kit, both the nosecone and fins are plastic. Except here they’ve been 3D printed in either PLA or PETG depending on their proximity to he hot and fiery area of the rocket. [Concrete Dog] says the printed parts are largely ready to fly as-is, but that some quality time with a piece of sandpaper and a coat of paint could improve the aerodynamics a bit if you were so inclined.

Ready for the best part? [Concrete Dog] has decided to release all of the design files for the rocket under the CERN Open Hardware Licence, meaning you’re free to reproduce and modify the rocket as you see fit. In fact, on July 24th, the HEXA rocket was officially certified as Open Hardware by the Open Source Hardware Association (OSHWA) — a first for a DIY rocket, as far as we can tell.

Now, we wouldn’t necessarily call ourselves connoisseurs of fine art here at Hackaday. But we do enjoy watching [Julian Baumgartner]’s YouTube channel, where he documents the projects that he takes on as a professional conservator. Folks send in their dirty or damaged paintings, [Julian] works his magic, and the end result often looks like a completely different piece. Spoilers: if you’ve ever looked at an old painting and wondered why the artist made it so dark and dreary — it probably just needs to be cleaned.

Anyway, in his most recent video, [Julian] pulled out a piece of gear that we didn’t expect to see unleashed against a painting of one of America’s Founding Fathers: a Er:YAG laser. Even better, instead of some fancy-pants fine art restoration laser, he apparently picked up second hand unit designed for cosmetic applications. The model appears to be a Laserscope Venus from the early 2000s, which goes for about $5K these days.

Now, to explain why he raided an esthetician’s closet to fix up this particular painting, we’ve got to rewind a bit. As we’ve learned from [Julian]’s previous videos, the problem with an old dirty painting is rarely the paining itself, it’s the varnish that has been applied to it. These varnishes, especially older ones, have a tendency to yellow and crack with age. Now stack a few decades worth of smoke and dirt on top of it, and you’ve all but completely obscured the original painting underneath. But there’s good news — if you know what you’re doing, you can remove the varnish without damaging the painting itself.

In most cases, this can be done with various solvents that [Julian] mixes up after testing them out on some inconspicuous corner of the painting. But in this particular case, the varnish wasn’t reacting well to anything in his inventory. Even his weakest solvents were going right through it and damaging the paint underneath.

Because of this, [Julian] had to break out the big guns. After experimenting with the power level and pulse duration of the 2940 nm laser, he found the settings necessary to break down the varnish while stopping short of cooking the paint it was covering. After hitting it with a few pulses, he could then come in with a cotton swab and wipe the residue away. It was still slow going, but it turns out most things are in the art conservation world.

This isn’t the first time we’ve covered [Julian]’s resourceful conservation methods. Back in 2019, we took at look the surprisingly in-depth video he created about the design and construction of his custom heat table for flattening out large canvases.

It’s difficult to nail down exactly what counts as a “real” cyberdeck in this brave new era of bespoke computing. But at the minimum, most in the community would agree that a proper deck should have a non-traditional form factor, and be designed to meet the unique needs of the builder. If you’re looking for a fantastic example of both concepts, check out the Cyberdore 2064 from [Tommi L].

At first glance the 3D printed enclosure of the Cyberdore looks a bit like a Speak & Spell, but it’s really more of an amalgamation of everything that made 1980s computers so unique. You’ve got the vents, the chunky switches, the undersized display, and of course, the handle. The case might have been extruded in 2024, but it’s doing a fantastic impression of a piece of tech from 40 years ago.

One of the key external features of the Cyberdore 2064 is the side-mounted rotary encoder that allows for smoothly scrolling through online feeds (such as your favorite hardware hacking site) or long documents. The cheap and easy to work with KY-040 encoder has been converted to a USB input device by way of a Pi Pico, and has been paired with an over-sized 3D printed knob that really makes this build stand out — not only visually, but in terms of usability. These cyberdeck builds often rely on touch screens for input, but we always appreciate a physical interface.

Under the hood you’ve got a Raspberry Pi Zero and an 18650 cell to keep the whole thing running while on the go. Though the Zero is certainly showing its age compared to the more modern variants of the Pi, for a device like this, raw computing power isn’t really the driving concern. A mechanical keyboard usually rounds out these cyberdeck builds, but in this case, [Tommi] went with a fairly common Rii 518BT portable board that’s been skillfully integrated into the front of the Cyberdore.

All of the STL files necessary to print out your own Cyberdore 2064 are available on Printables, and while [Tommi] didn’t exactly provide build instructions, the write-up provides plenty of information to get you started.

So is it just us, or does looking at Cyberdore 2064 make you think it’s time for another Hackaday Cyberdeck Challenge?

If you’re reading Hackaday, we’re willing to bet that if somebody asked you about a serial terminal, you’d immediately think about a piece of software — a tool you run on the computer to communicate with some hardware gadget over UART. You might even have a favorite one, perhaps minicom or tio. You’d be technically correct (which we all know is the best kind of correct), but if you wind back the clock a bit, there’s a little more to the story.

You see, the programs we use these days to talk to microcontrollers and routers are more accurately referred to as serial terminal emulators, because they are doing in software what used to be the job of hardware. What kind of hardware? Why beauties like this DEC VT220 for example.

The [Vintage Apparatus] channel recently got their hands on a couple of these dedicated serial terminals, and thought it would be interesting to take modern audiences through a brief tour of how they worked and what they were capable of. Despite being built sometime around 1984, the simplistic nature of these devices make them highly reliable — so long as the power supply is good, there’s not a whole lot else that can go wrong.

That being said, using one wasn’t quite as bare bones an experience as you might think. As [Vintage Apparatus] demonstrates, you can press a key on the VT220’s keyboard to bring up a series of configuration menus that don’t look too far removed from what you might be used to from your modern software terminal. Familiar options like baud rate, parity, and local echo are accounted for, but then there’s also settings for connecting a printer up to the serial terminal should you need to bang out some hard copy.

Getting your hands on one of these decades old serial terminals isn’t always easy, but if you’re more interested in the retro looks than technical accuracy, you can always 3D print yourself a replica.

A troubling report from the Belgian consumer protection group Testaankoop: several models of Velop Pro routers from Linksys were found to be sending WiFi configuration data out to a remote server during the setup process. That would be bad enough, but not only are these routers reporting private information to the mothership, they are doing it in clear text for anyone to listen in on.

Testaankoop says that while testing out the Pro WiFi 6E and Pro 7 versions of Velop routers, they discovered that unencrypted packets were being sent to a server hosted by Amazon Web Services (AWS). In these packets, they discovered not only the SSID of the user’s wireless network, but the encryption key necessary to join it. There were also various tokens included that could be used to identify network and user.

While the report doesn’t go into too much detail, it seems this information is being sent as part of the configuration process when using the official Linksys mobile application. If you want to avoid having your information bounced around the Internet, you can still use the router’s built-in web configuration menus from a browser on the local network — just like in the good old days.

The real kicker here is the response from Linksys, or more accurately, the lack thereof. Testaankoop says they notified them of their discovery back in November of 2023, and got no response. There’s even been firmware updates for the affected routers since then, but the issue is still unresolved.

Testaankoop ends the review by strongly recommending users avoid these particular models of Linksys Velop routers, which given the facts, sounds like solid advice to us. They also express their disappointment in how the brand, a fixture in the consumer router space for decades, has handled the situation. If you ask us, things started going downhill once they stopped running Linux on their hardware.

As far as video games go, Pong is already about as simple as it gets. But if even two dimensions is a bit more than you’re looking to tackle, [mircemk] shows how you can distill the core gameplay of this iconic title to its absolute minimum using an Arduino and a row of LEDs.

While [mircemk] brings their usual design aesthetic and flash to the project, this one could truly be done as a parts bin build. All you really need is a microcontroller with enough I/O pins (here, an Arduino Nano is used), a couple of buttons, and the aforementioned LEDs. A 16×2 LCD and a buzzer have been added to improve on the user interface a bit, but even that isn’t strictly required.

To play, each user holds their button and gets ready to hit it as soon as the LED closest to them lights up. Again, [mircemk] spruces this build up by offering both integrated buttons on the front panel of the game, as well as a pair of external “controllers” so you don’t have to crowd around the main unit. In this incarnation the score is shown on the LCD, but swapping that out for a pair of seven-segment LEDs could give the whole thing a bit more of a retro flair.

This isn’t the first time [mircemk] has tackled 1D Pong — if you can spring for addressable LEDs, you can pull the whole thing off with significantly less wiring.

Here on Earth, being able to 3D print replacement parts is handy, but rarely necessary. If you’ve got a broken o-ring, printing one out is just saving you a trip to the hardware store. But on the Moon, Mars, or in deep space, that broken component could be the difference between life and death. In such an environment, the ability to print replacement parts on demand promises to be a game changer.

Which is why the recent successful test of a next-generation 3D printer developed by a group of Berkeley researchers is so exciting. During a sub-orbital flight aboard Virgin Galactic’s Unity spaceplane, the SpaceCAL printer was able to rapidly produce four test prints using a unique printing technology known as computed axial lithography (CAL).

NASA already demonstrated that 3D printing in space was possible aboard the International Space Station in a series of tests in 2014. But the printer used for those tests wasn’t far removed technologically from commercial desktop models, in that the objects it produced were built layer-by-layer out of molten plastic.

In comparison, CAL produces a solid object by polymerizing a highly viscous resin within a rotating cylinder. The trick is to virtually rotate the 3D model at the same speed as the cylinder, and to project a 2D representation of it from a fixed view point into the resin. The process is not only faster than traditional 3D printers, but involves fewer moving parts.

Lead researcher [Taylor Waddell] says that SpaceCAL had already performed well on parabolic flights, which provide a reduced-gravity environment for short periods of time, but the longer duration of this flight allowed them to push the machine farther and collect more data.

It’s also an excellent reminder that, while often dismissed as the playthings of the wealthy, sub-orbital spacecraft like those being developed by Virgin Galactic and Blue Origin are capable of hosting real scientific research. As long as your experiment doesn’t need to be in space for more than a few minutes to accomplish its goals, they can offer a ticket to space that’s not only cheaper than a traditional orbital launch, but comes with less red tape attached.

These days, even hobbyist multi-rotor aircraft are capable of carrying considerable payloads. For example, the test rig that [Brian Brocken] recently put together should be able to loft more than 80 pounds (36 kilograms) without breaking a sweat. That would be a whole lot of camera gear or other equipment, but in this case, he’s planning on carrying something a bit more interesting: a full-scale foam DeLorean.

We first covered this project in December of last year, when [Brian] started using a massive robotic arm to carefully cut the body and individual parts of the car out of expanded polystyrene foam. He estimated at the time the body should weigh in at less than 30 lbs (14 kg), so he’d need to build a quadcopter with a maximum lift of roughly twice that much to keep the performance where he wanted it.

In the latest update to the Hackaday.io project page, [Brian] goes over the work that’s been done since we first got a glimpse of this incredible build. Improvements have been made to the motorized flaps and slats that cover up the front and rear motors when not in operation. The DeLorean’s iconic gull-wing doors have also been recreated, although in this case they’re motorized.

But the real news is the prototype airframe. Made of aluminum and 3D printed components, [Brian] is using it to get a feel for how much thrust can be expected from the motors, as well as provide some early numbers for the eventual PID tuning that’ll be needed to get the car flying smoothly. Unfortunately, there’s a bit too much flex in this version of the frame — [Brian] says that a later carbon fiber version will not only be more rigid, but also shave off a few more precious pounds.

We’re just as eager as the rest of you to see the first flight of this ambitious build, so stay tuned for the next update.

Non-contact infrared (IR) thermometers used to be something of an exotic tool, but thanks at least in part due to the COVID-19 pandemic, they’re now the sort of thing you see hanging up near the grocery store checkout as a cheap impulse buy. Demand pushed up production, and the economies of scale did the test. Now the devices, and the sensors within them, are cheap enough for us hackers to play with.

The end result is that we now have projects like this ultra compact IR thermometer from [gokux]. With just a handful of components, some code to glue it all together, and a 3D printed enclosure to wrap it all up, you’ve got a legitimately useful tool that’s small enough to replace that lucky rabbit’s foot you’ve got on your keys.

If this project looks familiar, it’s because the whole thing is closely related to the LiDAR rangefinder [gokux] put together last month. It shares the same Seeed Studio XIAO  ESP32-C3 microcontroller, 0.49 inch OLED display, and tiny 40 mAh LiPo battery. The only thing that’s really changed, aside from the adjustments necessary to the 3D printed enclosure, is that the LiDAR sensor was replaced with a MLX90614 IR temperature sensor.

[gokux] has put together some great documentation for this build, making it easy for others to recreate and remix on their own. Assembly is particularly straightforward thanks to the fact that both the display and temperature sensor communicate with the ESP32 over I2C, allowing them to be wired daisy chain style — there’s no need for even a scrap of perfboard inside the case, let alone a custom board.

The look, the feel, the sound — there are few things more satisfying in this world than a nice switch. If you’re putting together a device that you plan on using frequently, outfitting it with high-quality switches is one of those things that’s worth the extra cost and effort.

So we understand completely why [STR-Alorman] went to such great lengths to get the aftermarket seat heaters he purchased working with the gorgeous switches Toyota used in the 2006 4Runner. That might not sound like the kind of thing that would involve reverse engineering hardware, creating a custom PCB, or writing a bit of code to tie it all together. But of course, when working on even a halfway modern automobile, it seems nothing is ever easy.

The process started with opening up the original Toyota switches and figuring out how they work. The six-pin units have a lot going on internally, with a toggle, a rheostat, and multiple lights packed into each one. Toyota has some pretty good documentation, but it still took some practical testing to distill it down into something a bit more manageable. The resulting KiCad symbol for the switch helps explain what’s happening inside, and [STR-Alorman] has provided a chart that attributes each detent on the knob with the measured resistance.

But understanding how the switches worked was only half the battle. The aftermarket seat heaters were only designed to work with simple toggles, so [STR-Alorman] had to develop a controller that could interface with the Toyota switches and convince the heaters to produce the desired result. The custom PCB hosts a Teensy 3.2 that reads the information from both the left and right seat switches, and uses that to control a pair of beefy MOSFETs. An interesting note here is the use of very slow pulse-width modulation (PWM) used to flip the state of the MOSFET due to the thermal inertia of the heater modules.

We love the effort [STR-Alorman] put into documenting this project, going as far as providing the Toyota part numbers for the switches and the appropriate center-console panel with the appropriate openings to accept them. It’s an excellent resource if you happen to own a 4Runner from this era, and a fascinating read for the rest of us.

The ongoing story of bogus analytical data being submitted to the public OctoPrint usage statistics has taken a surprising turn with the news that a second plugin was being artificially pushed up the charts. At least this time, the developer of the plugin has admitted to doing the deed personally.

Just to recap, last week OctoPrint creator [Gina Häußge] found that somebody had been generating fictitious OctoPrint usage stats since 2022 in an effort to make the OctoEverywhere plugin appear to be more popular than it actually was. It was a clever attempt, and if it wasn’t for the fact that the fake data was reporting itself to be from a significantly out of date build of OctoPrint, there’s no telling how long it would have continued. When the developers of the plugin were confronted, they claimed it was an overzealous user operating under their own initiative, and denied any knowledge that the stats were being manipulated in their favor.

Presumably it was around this time that Obico creator [Kenneth Jiang] started sweating bullets. It turns out he’d been doing the same thing, for just about as long. When [Gina] contacted him about the suspicious data she was seeing regarding his plugin, he owned up to falsifying the data and published what strikes us as a fairly contrite apology on the Obico blog. While this doesn’t absolve him of making a very poor decision, we respect that he didn’t try to shift the blame elsewhere.

That said, there’s at least one part of his version of events that doesn’t quite pass the sniff test for us. According to [Kenneth], he first wrote the script that generated the fake data back in 2022 because he suspected (correctly, it turns out) that the developers of OctoEverywhere were doing something similar. But after that, he says he didn’t realize the script was still running until [Gina] confronted him about it.

Now admittedly, we’re not professional programmers here at Hackaday. But we’ve written enough code to be suspicious when somebody claims a script they whipped up on a lark was able to run unattended for two years and never once crashed or otherwise bailed out. We won’t even begin to speculate where said script could have been running since 2022 without anyone noticing…

But we won’t dwell on the minutiae here. [Gina] has once again purged the garbage data from the OctoPrint stats, and hopefully things are finally starting to reflect reality. We know she was already angry about the earlier attempts to manipulate the stats, so she’s got to be seething right about now. But as we said before, these unfortunate incidents are ultimately just bumps in the road. We don’t need any stat tracker to know that the community as a whole greatly appreciates the incredible work she’s put into OctoPrint.

Developing free and open source software can be a thankless experience. Most folks do it because it’s something they’re passionate about, with the only personal benefit being the knowledge that there are individuals out there who found your work useful enough to download and install. So imagine how you’d feel if it turns out somebody was playing around with the figures, and the steady growth in the number of installs you thought your software had turned out to be fake.

That’s what happened just a few days ago to OctoPrint developer [Gina Häußge]. Although there’s no question that her software for remotely controlling and monitoring 3D printers is immensely popular within the community, the fact remains that the numbers she’s been using to help quantify that popularity have been tampered with by an outside party. She’s pissed, and has every right to be.

[Gina] discovered this manipulation on June 26th after taking a look at the publicly available usage stats on data.octoprint.org. She noticed that an unusually high number of instances appeared to be running an old OctoPrint release, and upon closer inspection, realized what she was actually seeing was a stream of bogus data that was designed to trick the stat counter. Rolling back the data, she was able to find out this spam campaign has been going on since late 2022. Tens of thousands of the users she thought she’d gained over the last two years were in fact nothing more than garbage spit out by some bot. But why?

Here’s where it gets interesting. Looking at the data being reported by these fake OctoPrint instances, [Gina] could tell the vast majority of them claimed to be running a specific plugin: OctoEverywhere. The perpetrators were clever enough to sprinkle in a random collection of other popular plugins along with it, but this specific plugin was the one most of them had in common. Sure enough this pushed OctoEverywhere to the top of the charts, making it seem like it was the most popular plugin in the community repository.

So what do the developers of OctoEverywhere have to say for themselves? In a statement that [Gina] posted on the OctoPrint blog, they claim they were able to determine a member of the community had performed the stat manipulation of their own accord, but as of this writing are unwilling to release this individual’s identity. A similar statement now appears on the OctoEverywhere website.

On June 27th, Gina Häußge, the developer behind OctoPrint, informed us of an incident involving the OctoPrint usage stats. Gina had observed that the stats were being manipulated to boost OctoEverywhere’s rankings.

We took the report very seriously and quickly started an investigation. Using private community channels, we determined a community member was responsible for manipulating the OctoPrint stats. We had a private conversation with the individual, who didn’t realize the impact they were having but apologized and promised never to do it again.

From a journalistic perspective, it would be inappropriate for us to leap to any conclusions based on the currently available information. But we will say this…we’ve heard more convincing stories on a kindergarten playground. Even if we take the statement at face value, the fact that they were able to figure out who was doing this within 48 hours of being notified would seem to indicate this person wasn’t exactly a stranger to the team.

In any event, the bogus data has now been purged from the system, and the plugin popularity charts are once again showing accurate numbers. [Gina] also says some safeguards have been put into place to help prevent this sort of tampering from happening again. As for OctoEverywhere, it slid back to its rightful place as the 6th most popular plugin, a fact that frankly makes the whole thing even more infuriating — you’d think legitimately being in the top 10 would have been enough.

On Mastodon, [Gina] expressed her disappointment in being fooled into thinking OctoPrint was growing faster than it really was, which we certainly get. But even so, OctoPrint is a wildly popular piece of software that has become the cornerstone of a vibrant community. There’s no question that her work has had a incredible impact on the world of desktop 3D printing, and while this turn of events is frustrating, it will ultimately be little more than a footnote in what is sure to be a lasting legacy.

Over the last few years, it’s been increasingly common for concertgoers to be handed a light-up bracelet from PixMob that synchronizes with the others in the crowd to turn the entire audience into a music visualizer. They’re a clever way of enhancing the concert experience, but unfortunately, they don’t do anything once you leave the show. Or at least, that used to be the case.

We’ve seen efforts to reverse engineer the IR (and occasionally radio) signals that drive these PixMob devices, but since we checked in last it seems like things have gotten a lot easier for the home gamer. [David Pride] has recently posted a brief write-up that shows how quickly and easily it is to get these devices fired up using nothing more exotic than an Arduino, an IR LED, and an audio sensor module.

With the audio sensor module connected to the Arduino’s digital input and the IR LED wired to digital out, all you need to do is flash firmware to the board and start playing some beats. The source code [David] has provided is a a remixed version of what’s previously been published by [Carlos Ganoza], which, in this case, has been tweaked to make the lighting patterns less random.

Presumably, this is to make the devices behave more like they do during an actual concert, but since nobody at Hackaday is cool enough to have seen a live musical performance in the last decade, we’re not really sure. All we can say is that the effect looks pretty sweet in the demo video.

Back in 2019, we saw a teardown of an early PixMob device, and by 2022, the efforts to reverse engineer their IR control protocol were well underway. We’re glad to see things have progressed to the point that you can piece together a transmitter from what’s in the parts bin, as it means at least some of these devices will have a lifespan longer than a single concert.