When we first saw [Ajlitt’s] Hackaday.io project Terrible Cluster we thought, perhaps, he meant terrible in the sense of the third definition:
3. exciting terror, awe, or great fear; dreadful; awful. (Dictionary.com)
After looking at the subtitle, though, we realized he just meant terrible. The subtitle, by the way, is: 5 Raspberry PI Zeros. One custom USB hub. Endless disappointment.
There are four Raspberry Pi Zero boards that actually compute and one Raspberry Pi Zero W serves as a head node and network router. The total cost is about $100 and half of that is in SD cards. There’s a custom USB backplane and even a 3D-printed case.
At first, using five tiny computers in a cluster might not seem like a big deal. Benchmarking shows the cluster (with a little coaxing) could reach 1.281 GFLOPS, with an average draw of 4.962W. That isn’t going to win any world records. However, the educational possibilities of building a $100 cluster that fits in the palm of your hand is interesting. Besides, it is simply a cute build.
We’ve seen much larger Pi clusters, of course. You might be better off with some desktop CPUs, but — honestly — not much better.
Unless you’ve been living under a rock, you’d be familiar with Nintendo’s hugely popular Classic Mini consoles. Starting with the NES, and now followed with the SNES, the consoles ship in a cute, miniature enclosure and emulate Nintendo classics using the horsepower of modern ARM chips. These consoles use an emulator that has been created especially for the purpose by Nintendo, in house – and
[Morris] [krom] wanted to see if he could take the emulator on the SNES Classic Mini and run it on the Raspberry Pi.
Yes, there are already SNES emulators on the Raspberry Pi. But anyone interested in the nuts and bolts of emulation can see the clear interest in the tricks and techniques Nintendo are using to achieve the feat. In particular, Nintendo engineers have the benefit of access to internal documentation that can make the job a lot easier, particularly when dealing with edge cases.
[krom] has been kind enough to share the full instructions necessary to recreate this feat. One stumbling block was the difference in hardware between the Raspberry Pi and the SNES Classic Mini – the Pi using a Broadcom GPU instead of the SNES’s Mali hardware. However, a workaround was simple enough – swapping out some libraries was all that was required. It also gives some interesting insight – it looks like the SNES Classic Mini relies on the SDL libraries to run.
While emulation of the SNES has been a largely solved problem for quite some time, it’s great to see more work going on in the field. In particular, the official Nintendo emulation is reported to be particularly adept at running games that rely on the SuperFX chip.
For another take on SNES emulation, try out your old Mario games on the HoloLens.
Thanks [Morris] for the tip!
Even though the age for first carrying a smartphone seems to be decreasing, there’s a practical lower minimum age at which a kid can reliably use one to make a call. So how do you make sure your tot can reach out and touch mommy or daddy? This toddler-friendly Raspberry Pi hotline is a good start.
With a long trip to Hawaii pending and a toddler staying behind, [kuhnto] wanted a way to make communication as simple as possible. In the days of pervasive landlines, that would have been as simple as a feature phone with a couple of numbers on speed dial buttons. With nothing but cell phones to rely on, [kuhnto] turned to a Raspberry Pi running PBX software and a command line SIP client for making calls over a Google Voice line. The user interface is as simple as can be – a handset and two lighted buttons on a wall-mounted box. All Junior needs to do is pick up the handset and push green to talk to Daddy, blue for Mommy. Something similar might even be useful for elder care.
Kudos to [kuhnto] for thinking through the interface issues to come up with a successful build. We’ve seen other UIs simplified for kids before, such as this button-free jukebox or this special-needs media player.
The Raspberry Pi Zero W is a great platform for IoT projects, with a smattering of GPIO and onboard WiFi. However, security is an important consideration when it comes to the Internet of Things and it can be beneficial to keep your IoT devices on a separate network for safety’s sake. [Albert] wanted to do this all on board the Pi Zero W, and figured out how to get it acting as an access point and a client all at the same time.
[Albert] starts off with a fresh install of Raspbian Stretch, and sets the Pi up in OTG mode. This allows access to the Pi over a USB serial terminal. This is great for productivity when working on headless networking projects, as it can be frustrating trying to work with an SSH session that keeps dropping out when you change settings.
After creating a second named device (ap0) to go along with the one created automatically by the kernal (wlan0), DNSmasq is installed to act as a DHCP server for the AP. Hostapd is then installed to control the AP settings. Following this, like anything in Linux, a flurry of configuration files are edited to get everything humming along and starting up automatically after a reboot. For some reason, things don’t start up smoothly, so [Albert] has a cron job that fires 30 seconds after bootup and toggles the interfaces off and on again, and that’s done the trick.
It’s a useful hack, as it allows the Pi Zero to act as a hub for IoT devices, while also creating a bridge between them and the internet. Traffic can be managed to stop random internet users flicking your lights on and off and overspeeding your dishwasher.
We’ve seen the Pi Zero used for just about everything under the sun so far. If you’re just starting your own IoT build, perhaps you’d like to use the Pi Zero as a streaming camera?
It may seem like an odd concept to younger readers, but there was once a time when people rented their phones rather than buying them outright. Accordingly, these phones were built like tanks, and seeing one of these sturdy classics of midcentury modern design can be a trip down memory lane for some of us. So retrofitting a retro phone with a Raspberry Pi and Google’s AIY seems like a natural project to tackle for nostalgia’s sake.
The phone that [Alasdair Allan] decided to hack was the iconic British desk telephone, the GPO-746, or at least a modern interpretation of the default rental phone from the late 60s through the 70s. But the phone’s looks were more important than its guts, which were stripped away to make room for the Raspberry Pi and Google AIY hat. [Alasdair] originally thought he’d interface the Pi to the rotary dial through DIOs, until he discovered the odd optical interface of the dialer — a mask rotates over a ring of photoresistors, one for each digit, exposing only one to light from an LED illuminated by a microswitch on the finger stop. The digital interface brings up the Google voice assistant, along with some realistic retro phone line sounds. It’s a work in progress, but you can see where [Alasdair] is in the video below.
If stuffing a Google Pi into a retro appliance sounds familiar, it might be this vintage intercom rebuild you have in mind, which [Alasdair] cites as inspiration for his build.
Continue reading “Classic British Phone Gets a Google Makeover”
The Raspberry Pi is a powerful embedded computing platform. However, for all its Linux-based muscle, it lacks one thing that even the simplest 8-bit microcontrollers usually have – analog-to-digital conversion. There are a great many ways to rectify this shortcoming, and [Chris Burgess] has brought us another – with an 8-channel ADC for the Raspberry Pi.
For the ADC, [Chris] chose the MCP3008, for its low cost and availability. In this configuration it offers 10-bit resolution and a maximum sampling rate of 200 kilosamples per second. Adafruit has a great guide on working with the MCP3008, too. With such a useful resource to hand, [Chris] was able to spin up a PCB to interface the chip to the Raspberry Pi using SPI. [Chris] took care to try to make the board to the official HAT specifications. As far as the physical aspects go, the board is to spec, however [Chris] omitted the EEPROM required for auto-configuration purposes. That said, the pads are on the board if someone wants to take the initiative to install one.
It’s a tidy build that provides something sorely missing from the Raspberry Pi, for a reasonable cost. [Chris]’s goal was to build something that would enable the measurement of analog sensors for a robot project; we’d love to hear your ideas for potential uses in the comments!
What do you do when someone gives you a Wurlitzer 3100 jukebox from 1969, but keeps all the records? If you are like [Tijuana Rick], you grab an Arduino and a Rasberry Pi and turn it into a really awesome digital music player.
We’ll grant you, making a music player out of a Raspberry Pi isn’t all that cutting edge, but restoration and integration work is really impressive. The machine had many broken switches that had been hastily repaired, so [Rick] had to learn to create silicone molds and cast resin to create replacements. You can see and hear the end result in the video below.
[Rick] was frustrated with jukebox software he could find, until he found some Python code from [Thomas Sprinkmeier]. [Rick] used that code as a base and customized it for his needs.
There’s not much “how to” detail about the castings for the switches, but there are lots of photos and the results were great. We wondered if he considered putting fake 45s in the machine so it at least looked like it was playing vinyl.
Of course, you don’t need an old piece of hardware to make a jukebox. Or, you can compromise and build out a replica.
Continue reading “Arduino and Pi Breathe New Life into Jukebox”