Believe it or not, there was a time when the only way for many of us to play video games was to grab a roll of quarters and head to the mall. Even though there’s a working computer or video game console in essentially every house now doesn’t mean we don’t look back with a certain nostalgia on those times, though. Some have turned to restoring vintage arcade cabinets and others build their own. This hackerspace got a unique request for a full-sized arcade cabinet that was also easily portable as well.

The original request was for a portable arcade cabinet, and the original designs were for a laptop-like tabletop arcade. But further back-and-forth made it clear they wanted full-size cabinets that just happened to also be portable. So with that criteria in mind the group started building the units. The updated design is modular, allowing the controls, monitor, and Raspberry Pi running the machines to be in self-contained units, with the cabinets in two parts that can quickly be assembled on-site. The base is separate and optional, with the top section capable of being assembled on the base or on something like a tabletop or bar, and the electronics section quickly drops in.

While the idea of a Pi-powered arcade cabinet is certainly nothing new, the quick build, prototyping, design, and final product that’s mobile and quickly assembled are all worth checking out. There is even more information on the build at the project’s GitHub page including Fusion 360 models. If you need your cabinets to be even more portable, this tabletop MAME cabinet is a great place to start.

This week Jonathan Bennett and Doc Searls chat with Igor Pecovnik and Ricardo Pardini about Armbian, the Debian-based distro tailor made for single-board computers. There’s more than just Raspberry Pi to talk about, with the crew griping about ancient vendor kernels, the less-than-easy ARM boot process, and more!

– https://www.armbian.com/
– https://github.com/armbian

Did you know you can watch the live recording of the show right in the Hackaday Discord? Have someone you’d like use to interview? Let us know, or contact the guest and have them contact us! Take a look at the schedule here.

Direct Download in DRM-free MP3.

If you’d rather read along, here’s the transcript for this week’s episode.

Around here, printers have a life expectancy of about two years if we are lucky. But [techtipsy] has a family member who has milked a long life from an old Canon PIXMA printer. That is, until Microsoft or Canon decided it was too old to print anymore. With Windows 10, it took some hacking to get it to work, but Windows 11 was the death knell. Well, it would have been if not for [techtipsy’s] ingenuity with a Raspberry Pi.

The Pi uses Linux, and, of course, Linux will happily continue to print without difficulty. If you are Linux savvy, you can probably see where this is going.

It is a simple task to connect the printer to the Pi, set up CUPS, and then share the printer over the network. While Windows doesn’t want to drive the printer directly, it is more than happy to talk to it as a network printer.

While [techtipsy] was happy enough just to use Linux to start with, not everyone appreciates that option either because they are familiar with Windows or there’s some reason (e.g., hardware or work rules) that requires Windows. Once the printer is set up with the Pi, it doesn’t require any special knowledge to use it.

We’ve thought about doing something like this to put cheap thermal printers on the network. CUPS supports 3D printers, too, but we’ve never seen anyone really using it that way.

Just a few months after releasing the long-awaited second version of his Raspberry Pi Recovery Kit, [Jay Doscher] is back with an alternate take on his latest Pi-in-a-Pelican design. This slightly abridged take on the earlier design should prove to be easier and cheaper to assemble for those playing along at home while keeping the compromises to a minimum.

Probably the biggest change is that the Raspberry Pi 5 has been swapped out for its less expensive and more abundant predecessor. The Pi 4 still packs plenty of punch, but since it requires less power and doesn’t get as hot, it’s less temperamental in a build like this. Gone is the active cooling required by the more powerful single-board computer, and the wiring to distribute power to the Kit’s internal components has been simplified. The high-end military style connectors have been deleted as well. They looked cool, but they certainly weren’t cheap.

One of the most striking features of the original Recovery Kit was the front-mounted switches — both the networking type that’s intended to help facilitate connecting the Raspberry Pi to whatever hardware is left after the end of the world, and the toggles used to selectively control power to to accessory devices. Both have returned for the Recovery Kit 2B, but they’re also optional, with blank plates available to fill in their vacant spots.

Ultimately, both builds are fairly similar, but there’s enough changes between the two that it will have a notable impact on how much time (and money…) it would take you create one of your own. [Jay] has attempted to offer less intimidating versions of his designs in the past; while other creators take a “one and done” approach to their projects, he seems eager to go back and rethink problems that most others would have considered solved.

While most of us have likely spun up a virtual machine (VM) for one reason or another, venturing into the world of containerization with software like Docker is a little trickier. While the tools Docker provides are powerful, maintain many of the benefits of virtualization, and don’t use as many system resources as a VM, it can be harder to get the hang of setting up and maintaining containers than it generally is to run a few virtual machines. If you’ve been hesitant to try it out, this guide to getting a Docker container up and running is worth a look.

The guide goes over the basics of how Docker works to share system resources between containers, including some discussion on the difference between images and containers, where containers can store files on the host system, and how they use networking resources. From there the guide touches on installing Docker within a Debian Linux system. But where it really shines is demonstrating how to use Docker Compose to configure a container and get it running. Docker Compose is a file that configures a number of containers and their options, making it easy to deploy those containers to other machines fairly straightforward, and understanding it is key to making your experience learning Docker a smooth one.

While the guide goes through setting up a self-hosted document management program called Paperless, it’s pretty easy to expand this to other services you might want to host on your own as well. For example, the DNS-level ad-blocking software Pi-Hole which is generally run on a Raspberry Pi can be containerized and run on a computer or server you might already have in your home, freeing up your Pi to do other things. And although it’s a little more involved you can always build your own containers too as our own [Ben James] discussed back in 2018.

Sometimes, startups fail due to technical problems or a lack of interest from potential investors and fail to gain development traction. This latter case appears to be the issue befalling A³ Audio. So, the developers have done the next best thing, made the project open source, and are actively looking for more people to pitch in. So what is it? The project is centered around the idea of spatial audio or 3D audio. The system allows ‘audio motion’ to be captured, mixed and replayed, all the while synchronized to the music. At least that’s as much as we can figure out from the documentation!

The system is made up of three main pieces of hardware. The first part is the core (or server), which is essentially a Linux PC running an OSC (Open Sound Control) server. The second part is a ‘motion sampler’, which inputs motion into the server. Lastly, there is a Mixer, which communicates using the OSC protocol (over Ethernet) to allow pre-mixing of spatial samples and deployment of samples onto the audio outputs. In addition to its core duties, the ‘core’ also manages effects and speaker handling.

The motion module is based around a Raspberry Pi 4 and a Teensy microcontroller, with a 7-inch touchscreen display for user input and oodles of NeoPixels for blinky feedback on the button matrix. The mixer module seems simpler, using just a Teensy for interfacing the UI components.

We don’t see many 3D audio projects, but this neat implementation of a beam-forming microphone phased array sure looks interesting.

Anyone who first experienced music on computers using Winamp probably shares a memory of seeing that classic UI for the first time. Everything about it was a step ahead of the clunky, chunky interfaces we were used to, and even though it was supposed to be unobtrusive, it was hard to tear your eyes off that silky-smooth spectrum analyzer bouncing out your favorite MP3s.

Recapturing a little of the Winamp magic is the goal of Linamp, an physical version of the classic media player. It reproduces the Winamp UI on a touchscreen LCD with a wide aspect ratio that almost perfectly matches the original layout. Behind the display is a Raspberry Pi 4 with a 32 GB SD card, with all the important connections brought out to a board on the back of the case. The case itself is a treat, as it borrows design elements from another bit of retro gear, the mini-rack audio systems that graced many a bookshelf in the 1980s — and powered many high school parties too, if memory serves.

To recreate the case, [Rodmg] designed a sheet metal case and had it custom-made from anodized aluminum by PCBWay. He also printed a bezel for the display that looks very similar to the Winamp window border, complete with control icons. Where the build really shines, though, is with the work [Rodmg] put into the software. He matched the original Winamp UI very closely, both in terms of layout and performance. The pains he went to to get the spectrum analyzer working, including a deep dive into FFT, are impressive.

The results speak for themselves on this one, and hats off to [Rodmg] for the effort and the ride on the nostalgia train. We don’t know if the recent announcement of Winamp’s impending open-sourcing will have much impact on this project, but it might result in a flood of new Winamp builds.

While 3D printers have evolved over the past two decades from novelties to powerful prototyping tools, the amount of support systems have advanced tremendously as well. From rudimentary software that required extensive manual input and offered limited design capabilities, there’s now user-friendly interfaces with more features than you could shake a stick at. Hardware support has become refined as well with plenty of options including lighting, ventilation, filament recycling, and tool changers. It’s possible to automate some of these subsystems as well like [Caelestis Workshop] has done with this relay control box.

This build specifically focuses on automating or remotely controlling the power, enclosure lighting, and the ventilation system of [Caelestis Workshop]’s 3D printer but was specifically designed to be scalable and support adding other features quickly. A large power supply is housed inside of a 3D printed enclosure along with a Raspberry Pi. The Pi controls four relays which are used to control these various pieces hardware along with the 3D printer. That’s not the only thing the Pi is responsible for, though. It’s also configured to run Octoprint, a piece of open-source software that adds web interfaces for 3D printers and allows their operation to be monitored and controlled remotely too.

With this setup properly configured, [Caelestis Workshop] can access their printer from essentially any PC, monitor their prints, and ensure that ventilation is running. Streamlining the print process is key to reducing the frustration of any 3D printer setup, and this build will go a long way to achieving a more stress-free environment. In case you missed it, we recently hosed a FLOSS Weekly episode talking about Octoprint itself which is worth a listen especially if you haven’t tried this piece of software out yet.

If you use home automation these days, you’re probably used to using smart speakers, your smartphone, or those tabletop touchscreen devices. If you wanted something cooler and more personal, you could try building something like [Rick] did.

A Raspberry Pi 400 is the basis for the machine, and it still uses the original keyboard. It’s paired with a 3D-printed shell with a 7″ Waveshare HDMI touch display in it. The LCD is placed behind a Fresnel lens which provides some magnification. It displays a glowing blue command line which accepts text commands. It’s hooked up to the OpenAI API, so it’s a little smarter than just any old regular terminal. It’s hooked up to [Rick’s] home automation system, so he can use natural language queries to control lighting, music, and all the rest. Think Alexa or Siri, but in text form.

The design of the case, with its rounded edges, vents, and thick bezels gives it a strong retro-futuristic look, reminiscent of something out of Fallout. [Rick’s] neat application of weathering techniques helped a lot, too.

It reminds us of some of the cooler Pip Boy builds we’ve seen. Meanwhile, if you’ve got your own creative terminal build in the works, don’t hesitate to drop us a line!

Stringing a badminton racquet is a somewhat complicated job. It needs to be done well if the racquet is to perform well and the player is to succeed. To that end, [kuokuo] built a machine of their own to do that very task. Even better, they’ve made it open source so other hobbyists can benefit from their work.

The build is named PicoBETH, which stands for Pico Badminton Electronic Tension Head. It’s based around the Raspberry Pi Pico, as you might imagine. The Pico is charged with controlling the stringing procedure via a stepper motor and lead screw, while using a load cell to measure string tension during the process. A small two-line character LCD serves as the user interface, along with some buttons, LEDs and a buzzer for feedback. The electronic stringing gear is mounted on to a traditional manual drop-weight stringing machine to execute the process faster and more accurately, at least in theory.

Files are on Github for those that wish to explore the build further. It’s not the first stringing machine we’ve featured here, either! Video after the break.

Operating systems! They’re everywhere these days, from your smart TV to your smartphone. And even in your microcontrollers! Enter BreadboardOS for the Raspberry Pi Pico.

BreadboardOS is built on top of FreeRTOS. It’s aim is to enable quick prototyping with the Pi Pico. Don’t confuse operating system with GUI—BreadboardOS is command-line based. You’d typically interface with it via a terminal, but joy of joys—it does support color!

Using BreadboardOS is a little different than typical microcontroller development. Creating an application involves adding a “service” which is basically a task in FreeRTOS parlance. The OS handles running your service for you. Via the CLI interface, you can query running services, and start or kill them at will. Meanwhile, running df will happily give you stats on the flash usage of the Pi Pico, and free will tell you how full the memory is doing. If you really want to get raw, you can make calls to control GPIO pins, the SPI hardware, or other peripherals, and do it right on the command line.

BreadboardOS isn’t for everyone, but it could prove a useful tool if you like that way of doing things. It’s not the only OS out there for the Pi Pico, either! after the break.

The Mostly Printed CNC is famous for two things. First, being made mostly from 3D printed parts and commonly available steel tubing. Second, because of the materials used, its rigidity isn’t fantastic. But any CNC router is better than no CNC router, and [Alex Reiner]’s “Mostly Mostly Printed CNC” upgrades the base MPCNC into a much more capable unit.

MPCNC purists may want to look away, as the video below shows [Alex] committing the heresy of adding linear rails to his machine. The rails were sourced from VEVOR and at less than $100 for 10 meters, it must have been hard to resist. The rigidity wasn’t amazing — witness the horrific chatter at around the 5:15 mark — but [Alex] sorted that out with some aluminum extrusion and printed adapters.

Those upgrades alone were enough to let [Alex] dive into some aluminum cutting, but he also wanted to address another gripe with his base build: the Z-axis backlash. The fix there was to add another lead screw nut on an adjustable carrier. By tweaking the relative angles of the two opposed nuts, almost all of the backlash was taken up. [Alex] also replaced the motor coupling on the Z axis with a Lovejoy-style coupler, to remove as much axial compliance as possible.

Along with the motion control mods, [Alex] improved work holding and added an enclosure to tame the chip beast, along with some upgrades to the control electronics. The results are pretty good and appear well worth the modest added expense. Maybe a wireless controller can be next on the upgrade list?

The Raspberry Pi finds a use in a huge variety of applications, and in almost any location you could imagine. Sadly those who use those machines might not be in the same place as the machines themselves, and thus there’s the question of providing a remote connection between the two. This may not be a huge challenge to those skilled with Linux and firewalls, but to many Pi users it’s a closed book. So the Pi folks have come up with a painless way to connect to your Pi wherever it is, and it’s called Raspberry Pi Connect.

To use the service all you need is a Pi running the latest 64-bit version of Raspberry Pi OS, so sadly that excludes base model Zeros and older models. Sign in to the Raspberry Pi Connect server, follow the instructions, and you’re on your way. Under the hood it’s the well-known VNC protocol at work, with the connection setup being managed via WebRTC. The Pi servers are intended to act simply as connection facilitators for peer-to-peer traffic, though they are capable of handling through traffic themselves. It’s a beta service with a single server in the UK at the time of writing, though we’d expect both the number of servers and the offering to evolve over time.

We think this is a useful addition to the Pi offering, and we expect to see it used in all manner of inventive ways. Meanwhile it’s a while since we had a look at connecting to a headless Pi, but much of the information is still relevant.

There should be rejoicing among fans of the original ARM operating system this week, as the venerable RISC OS received its version 5.30 update. It contains up-to-date versions of the bundled software as well as for the first time, out-of-the-box WiFi support, and best of all, it can run on all Raspberry Pi models except the Pi 5. If you’ve not encountered RISC OS before, it’s the continuing development of the OS supplied with the first ARM product, the Acorn Archimedes. As such it’s a up-to-date OS but with an interface that feels like those of the early 1990s.

We like RISC OS here, indeed we reviewed the previous version this year, so naturally out came the Hackaday Pi 3 and an SD card to run it on. It’s as smooth and quick as it ever was, but sadly try as we might, we couldn’t get the Pi’s wireless interface to appear in the list of available network cards. This almost certainly has more to do with us than it does the OS, but it would have been nice to break free from the tether of the network cable. The included Netsurf 3.11 browser is nippy but a little limited, and just as it was during our review, sadly not capable of editing a Hackaday piece or we’d be using it to write this.

It’s great to see this operating system still under active development, and we can see that it so nearly fulfills our requirement here for a lightweight OS on the road. For those of us who used the original version, then called Arthur, it’s a glimpse of how desktop computing could, or perhaps even should, have been.

When the first Raspberry Pi came out back in 2012 it was groundbreaking because it offered a usable little Linux machine with the proud boast of a $25 dollar price tag. Sure it wasn’t the fastest kid on the block, but there was almost nothing at that price which could do what it did. Three leap years later though it’s surrounded by a host of competitors with similar hardware, and its top-end model now costs several times that original list price.

Meanwhile the cost of a “real” x86 computer such as those based upon the Intel N100 has dropped to the point at which it almost matches a fully tricked-out Pi with storage and peripherals, so does the Pi still hold its own? [CNX Software] has taken a look.

From the examples they use, in both cases the Intel machine is a little more expensive than the Pi, but comes with the advantage of all the peripherals, cooling, and storage coming built-in rather than add-ons. They rate the Pi as having the advantage on expandability as we’d expect, but the Intel giving a better bang for the buck in performance terms. From where we’re sitting the advantage of the Pi over most of its ARM competition has always been its good OS support, something which is probably exceeded by that on an x86 platform.

So, would you buy the Intel over the high-end Pi? Let us know in the comments.

One of the greatest things about the hacker ecosystem is that whole standing-on-the-shoulders-of-giants thing. Somebody makes something and shares it, and then someone else takes that thing and remixes it, sometimes making it objectively better. For their T3rminal cyberdeck, [calebholloway08] was inspired by a number of projects and came up with something that looks simply fantastic.

Whether you want to call this beauty a cyberdeck or a mobile PC, the guts are what you might expect — a Raspberry Pi 4, an affordable mini keyboard, and a touch screen. But this one took some doing, as in [calebholloway08] had to do a little bit of surgery on the Pi 4, the PiSugar S plus power supply platform, and the display. But you shouldn’t let that stop you from standing on the shoulders of giants, as [calebholloway08] provides (or guides you towards) clear instructions for all three mods.

One thing [calebhollway08] would have done differently was to use something other than a 18650 battery for power, like a 21700. The question is, what will you do differently?

Maybe this is a little too small for you. If so, check out this EMP-protected cyberdeck.

There’s always an appeal to a cool-looking computer case or cyberdeck – and with authentic-looking Vault-Tec style, [Eric B] and [kc9psw]’s fallout-themed cyberdeck is no exception.

The case looks like it came straight out of one of the Fallout games and acts the part: while (obviously) not capable of withstanding a direct nuclear bomb impact, it can protect the sensitive electronics inside from the electromagnetic pulse and shockwave that follows – if you keep it closed.

And it’s not just the case that’s cool: This cyberdeck is packed full of goodies like long-range radios, SDRs, ADSB receivers, a Teensy 4.1, and dual Raspberry Pis. But that’s just the hardware! It also comes with gigabytes upon gigabytes of Wikipedia, Wikihow, TED talks, and other information/entertainment, for the less eventful days in the wastelands.

If you, too, would like to have one, fret not! The parts list and design files are public, even though some assembly is required.