Teensy Spectrum Analyzer Has 170 Channels

While high-fidelity audio has come a long way in the past several decades, a lot of modern stereo equipment is still missing out on some of the old analog meters that were common on amplifiers and receivers of the 60s through the 80s. Things like VU meters don’t tend to be common anymore, but it is possible to build them back in to your sound system with the help of some microcontrollers. [Mark] shows us exactly how to reclaim some of the old-school functionality with this twin audio visualizer display.

Not only does this build include two displays, but the microcontroller is keeping up with 170 channels in real-time in order to drive the display. What’s more impressive is that it’s being done all on a Teensy 4.1. To help manage all of the data and keep the speed as fast as possible it uses external RAM soldered to the board, and a second Teensy audio board is used to do the real time FFT analysis. Most of the channels are sent to the display hosting the spectrum analyzer but two are reserved for left and right stereo VU meters on the second display.

The project from [Mark] is originally based on this software from [DIYLAB] so everything is open-source. While it was originally built for a specific piece of hardware, [Mark] has it set up with a line in and line out plus a microphone input so it can be used for virtually any audio hardware now. For another take on the classic VU meter, take a look at this design based on an Arudino instead.

Continue reading “Teensy Spectrum Analyzer Has 170 Channels”

Helium Recovery System Saves Costs

Helium is the most common element in the universe besides hydrogen, but despite this universal abundance it is surprisingly difficult to come across on Earth. Part of the problem is that it is non-renewable, so unless it is specifically captured during mining its low density means that it simply escapes the atmosphere. For that reason [Meow] maintains a helium recovery system for a lab which is detailed in this build.

The purpose of the system is to supply a refrigerant to other projects in the lab. Liquid helium is around 4 Kelvin and is useful across a wide variety of lab tests, but it is extremely expensive to come across. [Meow]’s recovery system is given gaseous helium recovered from these tests, and the equipment turns it back into extremely cold liquid helium in a closed-cycle process. The post outlines the system as a whole plus goes over some troubleshooting that they recently had to do, and shows off a lot of the specialized tools needed as well.

Low-weight gasses like these can be particularly difficult to deal with as well because their small atomic size means they can escape fittings, plumbing, and equipment quite easily compared to other gasses. As a result, this equipment is very specialized and worth a look. For a less lab-based helium project, though, head on over to this helium-filled guitar instead.

Porting DOOM To A Forgotten Apple OS

Apple hasn’t always had refined user experiences in their operating systems. In the distant past of the ’90s they were still kind of clunky computers that were far from the polished, high-end consumer machines of the modern era. That wasn’t all that Apple offered back then, though. They had a long-forgotten alternative operating system that was called A/UX designed for government applications, and [Keriad] is here to show us this relic operating system and port DOOM to it.

A/UX was designed in the pre-PowerPC days when Macintosh computers ran on Motorola 68000 chips. Luckily, [Keriad] has a Mac Quadra 800 with just such a chip that is still fully-functional. DOOM was developed with the NeXTSTEP operating system which can run on old Macs thanks to another tool called MacX which allows X11 applications to run on Mac. A version of gcc for A/UX was found as well and with the source code in hand they were eventually able to compile a binary. There were several hiccups along the way (including the lack of sound) but eventually DOOM was running on this forgotten operating system.

The main problem with the build in the end, besides the lack of sound, is that the game only runs at 2 – 3 frames per second. [Keriad] speculates that this is due to all of the compatibility layers needed to compile and run the game at all, but it’s still impressive. As far as we know, [Keriad] is the first person to port DOOM to this OS, although if you’re looking for something more straightforward we would recommend this purpose-built Linux distribution whose sole task is to get you slaying demons as quickly as possible.

A Linux Distribution For DOOM

If you’ve gone further into the Linux world than the standard desktop distributions like Ubuntu or Fedora, you have undoubtedly come across some more purpose-built distributions. Some examples are Kali for security testing, DragonOS for software-defined radio, or Hannah Montana Linux for certain music fans. Anyone can roll their own Linux distribution with the right tools, including [Shadly], who recently created one which only loads enough software to launch the 1993 classic DOOM.

The distribution is as simple as possible and loads no bloat other than what’s needed to launch the game. It loads the Linux kernel and the standard utilities via BusyBox, then runs fbDOOM, which is a port of the game specifically designed to run on the Linux framebuffer with minimal dependencies. After most of that, the only thing left is to use GRUB to boot the distribution, and in just a moment, Doomguy can start slaying demons. The entire distribution is placed into a bootable ISO file that can be placed on any bootable drive.

As far as DOOM hacks go, we’re used to seeing the game running on hardware it was never intended for like the NES  or on an office phone. This one, on the other hand, gives us a little more insight into just how little is needed for a full-fledged Linux distribution, as long as what you need to do is relatively straightforward.

Continue reading “A Linux Distribution For DOOM

Induction Heater Uses New Coil

Induction cook tops are among the most efficient ways of cooking in the home that are commercially available to the average person. Since the cook surface uses magnetic fields to generate heat in the cookware itself, there is essentially no heat wasted. There are some other perks too, such as faster cooking times and more fine control, not to mention that it’s possible to build your own induction stove. All you need is some iron, wire, and a power source, and you can have something like this homemade induction cooker.

This induction heater has a trick up its sleeve, too. Instead of using an air coil to generate heat in the cookware, this one uses an iron core instead. The project’s creator [mircemk] built an air core induction stove in the past, and this new one is nearly identical with the exception of the addition of the iron core. This allows for the use of less wire, and uses a driver circuit called a Mazzilli ZVS driver running through some power MOSFETs to power the device. A couple inductors limit the current to 20A, but it appears to work just as well as the previous stove.

This build puts a homemade induction stove well within reach of anyone with an appropriate power supply and enough wire and inductors to build the coils. [mircemk] has made somewhat of a name for himself involving project that use various coils of wire, too, like this project we featured recently which uses two overlapping air-core coils to build an effective metal detector.

Continue reading “Induction Heater Uses New Coil”

Bug Eliminator Zaps With A Laser

Mosquitoes tend to be seen as an almost universal negative, at least in the lives of humans. While they serve as a food source for plenty of other animals and may even pollinate some plants, they also carry diseases like malaria and Zika, not to mention the itchy bites. Various mosquito deterrents have been invented over the years to solve some of these problems, but one of the more interesting ones is this project by [Ildaron] which attempts to build a mosquito-tracking laser.

The device uses a neural learning algorithm to identify mosquitoes flying nearby. Once a mosquito is detected, a laser is aimed at it and activated in order to “thermally neutralize” the pest. The control system as well as the neural network and machine learning are hosted on a Raspberry Pi and Jetson Nano which give it plenty of computing power. The only major downside with this specific project is that the high-powered laser can be harmful to humans as well.

Ideally, a market for devices like these would bring the price down, perhaps even through the use of something like an ASIC specifically developed for these mosquito-targeting machines. In the meantime, [Ildaron] has made this project available for replication on his GitHub page. We have also seen similar builds before which are effective against non-flying insects, so it seems like only a matter of time before there is more widespread adoption — either that or Judgement day!

Continue reading “Bug Eliminator Zaps With A Laser”

Building Faster Rsync From Scratch In Go

For a quick file transfer between two computers, SCP is a fine program to use. For more complex, large, or regular backups, however, the go-to tool is rsync. It’s faster, more efficient, and usable in a wider range of circumstances. For all its perks, [Michael Stapelberg] felt that it had one major weakness: it is a tool written in C. [Michael] is philosophically opposed to programs written in C, so he set out to implement rsync from scratch in Go instead.

[Michael]’s path to deciding to tackle this project is a complicated one. His ISP upgraded his internet connection to 25 Gbit/s recently, which means that his custom router was the bottleneck in his network. To solve that problem he migrated his router to a PC with several 25 Gbit/s network cards. To take full advantage of the speed now theoretically available, he began using a tool called gokrazy, which turns applications written in Go into their own appliance. That means that instead of installing a full Linux distribution to handle specific tasks (like a router, for example), the only thing loaded on the computer is essentially the Linux kernel, the Go compiler and libraries, and then the Go application itself.

With a new router with hardware capable of supporting these fast speeds and only running software written in Go, the last step was finally to build rsync to support his tasks on his network. This meant that rsync itself needed to be built from scratch in Go. Once [Michael] completed this final task, he found that his implementation of rsync is actually much faster than the version built in C, thanks to the modernization found in the Go language and the fact that his router isn’t running all of the cruft associated with a standard Linux distribution.

For a software project of this scope, we find [Michael]’s step-by-step process worth taking note of for any problem any of us attempt to tackle. Not only that, refactoring a foundational tool like rsync is an involved task on its own, let alone its creation simply to increase network speeds beyond what most of us would already consider blazingly fast. We’re leaving out a ton of details on this build so we definitely recommend checking out his talk in the video below.

Thanks to [sarinkhan] for the tip!

Continue reading “Building Faster Rsync From Scratch In Go”