Conway’s Game Of Life With Physical Buttons

Conway’s Game of Life excels in its simplicity, creating a cellular automaton on a 2D grid where each cell obeys a set of very simple rules that determine whether a cell is ‘alive’ or ‘dead’. After setting an initial condition the ‘game’ then evolves naturally from there, creating an endless series of patterns as a simplified form of bacterial evolution. Of course, setting an initial state and then watching cells light up or fade away seems like a natural fit for light-up buttons. After struggling with intrusive thoughts related to such a project for a while, [Michal Zalewski] finally gave in, creating a pretty amazing looking result.

Although there is no set size for the game board, [Michal] was constrained by his budget for the selected NKK JB15LPF-JF tactile buttons, resulting in a 17×17 matrix. That’s 289 buttons, for those keeping score, which comes down to over $1,000 over at e.g. Digikey even with quantity-based pricing. Add to this the custom PCB and a Microchip AVR128DA64 squeezed in a corner of said PCB to run the whole show and it’s quite the investment.

Finishing up the PCB, driving the lights is done with a duty cycle as the matrix is scanned along with detecting inputs in a similar manner. This required the addition of MOSFETs and transistors, the details of which can be found in the downloadable project files, along with the firmware source code. In the article a video of the board in action can be watched, allowing one to admire the very pretty wooden enclosure as well.

How Long Can A Quadcopter Drone Fly On Just Solar?

The final second prototype flying. (Credit: Luke Maximo Bell, YouTube)
The final second prototype flying. (Credit: Luke Maximo Bell, YouTube)

The dream of fully powering everything from aircraft to cars on just the power generated from solar panels attached to the machine remains a tempting one, but always seems to require some serious engineering including putting the machine on a crash diet. The quadcopter that [Luke Maximo Bell] tried to fly off just solar power is a good case in point, as the first attempt crashed after three minutes and wrecked its solar panels. Now he’s back with a second attempt that ought to stay airborne for as long as the sun is shining.

Among the flaws with the first prototype were poor support for the very thin and fragile PV panels, requiring much better support on the carbon fiber frame of the drone. To support the very large solar array, the first drone’s arms were made to be very long, but this interfered with maneuvering, so the second version got trimmed down and the array raised above the frame. This saved 70 grams of weight from the shortened tubs, which could then be added to the new panel supports.

After an initial test flight resulted in a crash when the PV output dropped, the need for a small battery buffer was clear, so this was added, along with a reduction of the array to 4×7 panels to get the same 20V as the battery. The array also had to be reinforced, as the thin array was very wobbly in addition to making it impossible to fly with any significant wind.

Continue reading “How Long Can A Quadcopter Drone Fly On Just Solar?”

User Repair Of A Not User-Repairable Victron CCGX Issue

Power banks come in many sizes, and those that target construction sites are probably among the largest. The massive four ton unit based around lead-acid batteries which the [Buy it Fix it] YouTube channel got handed is a good example. Inside it are Victron CCGX inverters among a lot of other Victron electronics, with the control panel for the system throwing up an error that was deemed to be not user-serviceable. Naturally, this makes for a good challenge.

The exact error as thrown up on the central control panel is error #42, indicating a storage corruption issue on the device. According to the manual this means an issue with the internal flash memory that stores settings, serial numbers and WiFi credentials, requiring it to be shipped back to the manufacturer.

To further diagnose the issue, this Color Control unit was taken out of the power bank and coaxed onto a repair bench. This device has a whole host of Ethernet, CAN and other buses on the back, along with a USB host feature, but using the latter to reflash the firmware made no difference. Fortunately it’s just an embedded Linux system running on the System-on-Module and gaining remote SSH access was a snap due to easy root access.

Interestingly, running a diagnostic on the flash IC showed it to be still in good condition. Instead an ECC issue was logged that caused it to be marked as bad. This seems to have been due to the flash IC requiring 4 bits of ECC per 528 bytes, but the software using only a single bit. After reformatting and clearing the error it seems to have fixed the issue. Apparently it was just a weird configuration error that soft-bricked the device, raising the question of how that happened.

Continue reading “User Repair Of A Not User-Repairable Victron CCGX Issue”

Hackaday Podcast Episode 362: Compression Molding, IPv4x, And Wired Headphones

As the sun goes down on a glorious spring evening on the western edge of Europe, Elliot Williams is joined by Jenny List for a look at the week in all things Hackaday.

First up: Hackaday Europe tickets are on sale! Bad luck folks, the early bird tickets disappeared in an instant, but regular ones are still available for now. We’re really looking forward to making our way to Lecco for a weekend of hacks, and it would be great to see you there too.

Then we have a new feature for the podcast, the Hackaday Mailbag. This week’s contribution comes from [Kenny], a longtime friend of Hackaday and probably our most regular conference attendee.

To the hacks, and we have some good ones. An air hockey robot might not seem like a challenge, but the engineering which went into [BasementBuilds’] one proves it’s not a job for the faint hearted. Then we look at compression molding of recycled plastic using 3D-printed molds, something that seems surprisingly accessible and we’d like to try, too. We’ve got a new DOS, a 3D-printed zipper repair, the IPv4 replacement we didn’t get, and the mind-bending logic of ternary computing. It’s one of those weeks where the quick hacks could all deserve their own in-depth look, but perhaps the stand-outs are and Arduino style compiler that includes the source code compressed within the binary, and a beautifully-done revival of a 1980s brick cellphone as a modern 5G unit.

Finally in the longer reads we’ve got an examination of wired versus Bluetooth headphones — we’re both in the wired camp — and a look back at the age of free dialup. As is so often the case, the experience there differed between Brits and Americans. Anyway, enjoy the episode, and we have another week to look forward to.

Download your own personal copy of the Podcast in glorious 192 kB MP3.

Continue reading “Hackaday Podcast Episode 362: Compression Molding, IPv4x, And Wired Headphones”

Powering USB Devices With A Bench Supply Adapter Board

Sometimes you wanna test a piece of USB hardware, but you don’t just want to plug it into a random old phone charger. [KS-Elektronikdesign] has whipped up a useful tool for just that case, allowing one to easily power USB hardware from a common bench supply.

It would have been simple enough to whip up an adapter board to connect banana jacks to the power pins of a regular USB port. Easing the hookup process was indeed a part of the motivation for this project, in making it easy to power hardware that hooks up via USB-A and USB-C. However, it also goes a little further. It includes TUSB319 chip to handle the all-important power negotiation, without which many USB devices will not feel confident drawing their required amount of current.

There is also polarity protection and over-voltage protection to stop you from blowing stuff up if you hook the board up wrong, which might save you a smartphone or three in the lab. The board will allow negotiated output power up to 10 W via USB-A and 15 W via USB-C, which isn’t heaps, but will be fine for lots of smaller devices. You can up that to 25 W and 35 W respectively if the board is switched to pass-through mode. We particularly like the physical design—the board will plug straight into the banana plugs on any supply with a jack spacing of 19 to 23 mm.

Overall, this is a useful tool to have in the lab if you want to run USB hardware with the flexibility of the voltage and current limits available on your bench supply. There are other ways to power modern USB devices, too, and you can do all kinds of wild stuff if you learn about USB PD and USB PPS. If you’re working up your own nifty lab tools for similar purposes, we’d love to know about it on the tipsline.

This Week In Security: Linux Flaws, Python Ownage, And A Botnet Shutdown

The ides of security March are upon us — Qualys reports the discovery by their threat research unit of vulnerabilities in the Linux AppArmor system used by SUSE, Debian, Ubuntu, and Kubernetes as an additional security mechanism and application firewall.

AppArmor was added to Linux in 2010, and the vulnerabilities Qualys discovered have been present since 2017, and allow unprivileged (non-root) local users to elevate privileges by executing arbitrary code in the kernel, gaining root access, or perform a denial-of-service attack across the entire system by replacing all AppArmor behavior with “deny all” rules.

All Linux kernels since Linux 4.11 are vulnerable. If your Linux distribution enables AppArmor, and quite a few do, you’ll want to be updating as soon as fixes are available from your distribution maintainers. On systems with untrusted users, such as shared environments, VPS server environments, and the like, this is even more critical and urgent. Even on single-user systems, vulnerabilities like these allow other exploits, like the Python attack below, mechanisms to elevate their access and persistence.

At the time of writing, the full details of the AppArmor vulnerability are limited until the Linux Kernel team releases a stable version with the fixes for distribution maintainers. Qualys has published the technical write-up with the currently public information.

Python Projects Compromised

StepSecurity reports on a new campaign to infect Python projects on GitHub with a complex malware that, once deployed, appears to be yet another crypto and login stealer.

The attacker first gains access to the GitHub credentials via another info stealing worm – the Glassworm stealer infects VSCode extensions with over 35,000 downloads of infected extensions in October of 2025. Glassworm harvests NPM, GitHub, and OpenVSX credentials and sends them to a remote command and control (C2) server. It also harvests a wide range of crypto currency wallet extensions to steal crypto directly. Continue reading “This Week In Security: Linux Flaws, Python Ownage, And A Botnet Shutdown”

Google Unveils New Process For Installing Unverified Android Apps

It’s no secret that Google really doesn’t like it that people are installing Android applications from any other source than the Play Store. Last year they proposed locking everyone into their official software repository by requiring all apps to be signed by verified developers, an identity which would be checked against a Google-maintained list. After a lot of pushback a so-called ‘advanced flow’ for installing even unsigned APKs would be implemented, and we now know how this process is supposed to work.

Instead of the old ‘allow installing from unknown sources’ toggle, you are now going to have to dig deep into the Developer Options, to tap the Allow Unverified Packages setting and confirm that nobody is forcing you to do this. This starts a ‘security delay’ of twenty-four hours after you restart the device, following which you can finally enable the setting either temporarily or permanently. It would seem these measures are in place to make it more difficult for a scammer to coerce a user into installing a malicious app — whether or not that’s a realistic concern or not, we’re not sure.

When we last covered this issue this ‘advanced flow’ had just been introduced as an appeasement option. In addition to this a limited free developer account was also pitched, which now turns out to allow for up to only 20 device installations. If you want more than this, you have to pay the $25 fee and provide your government ID.

Although Google’s public pitch is still that this is ‘for user security’, it will also mean that third-party app stores are swept up in these changes, with developers who publish on these stores subject to the same verification rules. This means that Android users will have to learn quickly how to enable this new option as it will be rolled out to more countries over the coming months.

The reality is that scammers will simply work around this issue by buying up already verified developer accounts. At the same time, it’ll cripple third-party app stores and indie developers who had intended to distribute their Android app by simply providing an APK download.