Gorgeous Specimen Is The Final Word In Word Clocks

At this point, it’s safe to say that word clocks aren’t quite as exciting as they once were. We’ve seen versions that boil the concept down to what amounts to a parts bin build, which for better or for worse, takes a lot of the magic out of it. You just get an array of LEDs, put some letters in front of it, write some code, and you’re done.

But then [Mark Sidell] sent in his build, and we remembered why we collectively fell in love with these clocks in the first place. It wasn’t the end result that captivated us, although the final clock is indeed gorgeous, but the story of its painstaking design and construction. The documentation created for this project is unquestionably some of the best we’ve seen in a very long time, and whether or not you have any desire to build a word clock of your own, you won’t regret sitting down and reading through it.

If you can somehow come away from reading through that build log and not be impressed, surely the clock’s feature set will put you over the edge. The ability to show time in just five minute increments makes this one of the most practical word clocks we’ve seen, and the quality of life features such as automatic brightness control based on ambient light level, and a smartphone-controlled web interface for configuring the clock are just a few of its standout features.

Incidentally the glow behind the clock, provided by a dedicated array of WS2812 RGB LEDs, isn’t just for ambiance. It indicates the position of the sun in the sky as calculated by the Python astral package, as well as mimicking the colors of the sunrise and sunset. There’s even a compass onboard to make sure the LEDs are properly aligned with their astronautical counterpart.

[Mark] actually made several of these clocks, most of which were given away as gifts. Some of the lucky recipients lived far enough away that the clock had to be shipped, so he designed a custom shipping case to hold everything securely during the trip. It also meant he had to come up with a way of remotely maintaining the code on these clocks without user intervention, so he created a firmware update and telemetry gathering backend with Amazon Web Services that they check into periodically. Honestly, the attention to detail put into every element of this project is just staggering.

If you’re interested in seeing what all the fuss is about with these word clocks, but aren’t quite at [Mark]’s level, don’t worry. As we said earlier, you can build a small version with little more than an LED array and a microcontroller. Just don’t blame us if it ends up turning into an obsession.

Continue reading “Gorgeous Specimen Is The Final Word In Word Clocks”

The Compromises Of Raspberry Pi Hardware Documentation

[Rowan Patterson] informed us about a recent ticket he opened over at the Raspberry Pi Documentation GitHub repository. He asked about the the lack of updates to the Raspberry Pi 4’s USB-C power schematics for this board. You may recall that the USB-C power issue was covered by us back in July of 2019, yet the current official  Raspberry Pi 4 schematics still show the flawed implementation, with the shorted CC pins, nearly two years later.

[Alasdair Allan], responsible for the Raspberry Pi  documentation, mentioned that they’re in the process of moving their documentation from Markdown to AsciiDoc, and said that they wouldn’t have time for new changes until that was done. But then [James Hughes], Principal Software Engineer at Raspberry Pi,  mentioned that the schematics may not be updated even after this change due to a of lack of manpower.

As [James] emphasized, their hardware will probably never be open, due to NDAs signed with Broadcom. The compromise solution has always been to publish limited peripheral schematics. Yet now even those limited schematics may not keep up with board revisions.

An easy fix for the Raspberry Pi 4’s schematics would be for someone in the community to reverse-engineer the exact changes made to the Raspberry Pi 4 board layout and mark these up in a revised schematic. This should be little more than the addition of a second 5.1 kΩ resistor, so that CC1 and CC2 each are connected to ground via their own resistor, instead of being shorted together.

Still, you might wish that Raspberry Pi would update the schematics for you, especially since they have updated versions internally. But the NDAs force them to duplicate their efforts, and at least right now that means that their public schematics do not reflect the reality of their hardware.

Raspberry Pi Floppy Driver Uncovers Fishy Secrets

A forum post by New Zealand electronics enthusiast [zl2wrw] about retreiving waypoints from a mysterious floppy disk caught our eye. The navigation system on his friend’s fishing boat had died and was replaced. But the old waypoints were stored on a 3-1/2 inch floppy disk that was unreadable on a normal PC. Not to be deterred, [zl2wrw] then looked for another solution — apparently a list of hot NZ fishing spots is worth quite the effort.

The tool he discovered, and the main point of this story, is the bbc-fdc by [Jasper Renow-Clarke] aka [picosonic]. [Jasper] made this project to read 5-1/4 inch Acorn DFS floppies from his BBC Micro. But bbc-fdc can be used to read a variety of floppy disk formats, such as DOS, C64, Apple II, and others It can also just capture raw magnetic flux transitions on the disk, blissfully unaware of any logical structure to the data. We recently wrote about another Raspberry Pi Floppy Drive Controller project by [Scott Baker]. What sets [picosonic]’s project apart is that he’s not using an FDC controller chip here. The only interface electronics is a couple of open-collector 7406 ICs. Data is read using the SPI peripheral. If you need to archive old floppy disks or do a forensic analysis of unknown disks like [zl2wrw], then one of these two projects will almost certainly do the trick.

Meanwhile back in New Zealand, [zl2wrw] discovered that the floppy format was standard (Modified Frequency Modulation, MFM) by examining the raw flux dump. However, the filesystem was a mystery — it didn’t quite match any of the usual suspects. So [zl2wrw] dug into the hex dump of the data and figured out enough of the structure to manually recover the waypoints. Subsequently, a user on the forum found a document describing the file system used by Furuno GPS units, which proved to be a close match albeit after the fact. Alas, [zl2wrw] hasn’t publish the coordinates of those good fishing spots.

Have you had any successes (or failures) when it comes to reading data from old disks? Or have you encountered peculiar disk formats and/or file systems, where having a tool like this could have been helpful? Let us know in the comments below.

Raspberry Pi Hat Adds SDR With High Speed Memory Access

An SDR add-on for the Raspberry Pi isn’t a new idea, but the open source cariboulite project looks like a great entry into the field. Even if you aren’t interested in radio, you might find the project’s use of a special high-bandwidth memory interface to the Pi interesting.

The interface in question is the poorly-documented SMI or Secondary Memory Interface. [Caribou Labs] helpfully provides links to others that did the work to figure out the interface along with code and a white paper. The result? Depending on the Pi, the SDR can exchange data at up to 500 Mbps with the processor. The SDR actually uses less than that, at about 128 Mbps. Still, it would be hard to ship that much data across using conventional means.

On the radio side, the SDR covers 389.5 to 510 MHz and 779 to 1,020 MHz. There’s also a wide tuning channel from 30 MHz to 6 GHz, with some exclusions. The board can transmit at about 14 dBm, depending on frequency and the receive noise figure is under 4.5 dB for the lower bands and less than 8 dB above 3,500 MHz. Of course, some Pis already have a radio, but not with this kind of capability. We’ve also seen SMI used to drive many LEDs.

Scratch Built Tracked Robot Reporting For Duty

Inspired by battle-hardened military robots, [Engineering Juice] wanted to build his own remote controlled rover that could deliver live video from the front lines. But rather than use an off-the-shelf tracked robot chassis, he decided to design and 3D print the whole thing from scratch. While the final product might not be bullet proof, it certainly doesn’t seem to have any trouble traveling through sand and other rough terrain.

Certainly the most impressive aspect of this project is the roller chain track and suspension system, which consists of more than 200 individual printed parts, fasteners, bearings, and linkages. Initially, [Engineering Juice] came up with a less complex suspension system for the robot, but unfortunately it had a tendency to bind up during testing. However the new and improved design, which uses four articulated wheels on each side, provides an impressive balance between speed and off-road capability.

Internally there’s a Raspberry Pi 4 paired with an L298 dual H-bridge controller board to drive the heavy duty gear motors. While the Pi is running off of a standard USB power bank, the drive motors are supplied by a custom 18650 battery pack utilizing a 3D printed frame to protect and secure the cells. A commercial night vision camera solution that connects to the Pi’s CSI header is mounted in the front, with live video being broadcast back to the operator over WiFi.

To actually control the bot, [Engineering Juice] has come up with a Node-RED GUI that’s well suited to a smartphone’s touch screen. Of course with all the power and flexibility of the Raspberry Pi, you could come up with whatever sort of control scheme you wanted. Or perhaps even go all in and make it autonomous. It looks like there’s still plenty of space inside the robot for additional hardware and sensors, so we’re interested to see where things go from here.

Got a rover project in mind that doesn’t need the all-terrain capability offered by tracks? A couple of used “hoverboards” can easily be commandeered to create a surprisingly powerful wheeled platform to use as a base.

Continue reading “Scratch Built Tracked Robot Reporting For Duty”

2:3 Scale VT100 Terminal Gets Closer To Its Roots

When [Michael Gardi] finished his scaled down DEC VT100 replica a few months ago, he made it very clear that the project was only meant to look like a vintage terminal on the outside. A peek into the case revealed nothing more exotic than a Raspberry Pi running its default operating system, making the terminal just as well suited to emulating classic games as it was dialing into a remote system. But as any hacker knows, some projects end up developing a life of their own.

It started simply enough. The addition of an RS-232 Serial HAT to the Raspberry Pi meant that the 3D printed VT100 could actually operate as a serial terminal using software such as minicom. Then [Lars Brinkhoff] got involved. He loved the look of the printed VT100, and thought it deserved better than a generic terminal emulator. So he went ahead and started developing a custom terminal simulator for it to run.

Reliving those CRT glory days.

The idea here is that an an 8080 emulator actually runs an original VT100 firmware ROM, warts and all. It makes all the beeps and chirps you’d expect from the real hardware, and there’s even some OpenGL trickery used to mimic an old CRT display, complete with scan lines and a soft glow around characters.

Naturally the visual effects consume a fair amount of processing power, so [Lars] cautions that anything lower than the Pi 4 will likely experience slowdowns. Of course, nothing is stopping you from running the simulator on your desktop machine if you’re looking for that classic terminal experience.

Did this gorgeous recreation of the VT100 need to have a true serial interface or a simulator that recreates the unique menu system of the original? Not at all. Even without those additions, it blew us away when [Michael] first sent it in. But are we happy that these guys have put in the time to perfect this already stellar project? We think you already know the answer.

Raspberry Pi Zero Takes The Wheel In Miniature Fighting Robot

Looking to capitalize on his familiarity with the Raspberry Pi, [Sebastian Zen Tatum] decided to put the diminutive Pi Zero at the heart of his “antweight” fighting robot, $hmoney. While it sounds like there were a few bumps in the road early on, the tuxedoed bot took home awards from the recent Houston Mayhem 2021 competition, proving the year of Linux on the battle bot is truly upon us.

Compared to using traditional hobby-grade RC hardware, [Sebastian] says using the Pi represented a considerable cost savings. With Python and evdev, he was able to take input from a commercial Bluetooth game controller and translate it into commands for the GPIO-connected motor controllers. For younger competitors especially, this more familiar interface can be seen as an advantage over the classic RC transmitter.

A L298N board handles the two N20 gear motors that provide locomotion, while a Tarot TL300G ESC is responsible for spinning up the brushless motor attached to the “bow tie” spinner in the front. Add in a Turnigy 500mAh 3S battery pack, and you’ve got a compact and straightforward electronics package to nestle into the robot’s 3D printed chassis.

In a Reddit thread about $hmoney, [Sebastian] goes over some of the lessons his team has learned from competing with their one pound Linux bot. An overly ambitious armor design cost them big at an event in Oklahoma, but a tweaked chassis ended up making them much more competitive.

There was also a disappointing loss that the team believes was due to somebody in the audience attempting to pair their phone with the bot’s Pi Zero during the heat of battle, knocking out controls and leaving them dead in the water. Hopefully some improved software can patch that vulnerability before their next bout, especially since everyone that reads Hackaday now knows about it…

While battles between these small-scale bots might not have the same fire and fury of the televised matches, they’re an excellent way to get the next generation of hackers and engineers excited about building their own hardware. We wish [Sebastian] and $hmoney the best of luck, and look forward to hearing more of their war stories in the future.