Mysterious Files PH

We try to steer clear of politics and societal issues here at Hackaday, so a protest is not usually the sort of thing we’d cover. But we figure it’s safe enough to bend the rules a bit when the ones doing the protesting happen to be robots.

About 30 bots gathered — or at least were commanded to gather by the event organizers — in Warsaw to spur discussion about the impact AI and robots will have on the labor market. Beyond getting public and media attention, the demonstration was also designed to raise awareness of what modern humanoid robots can do. While we appreciate the idea of showing robots taking the “jobs” of the protesters, it does seem somewhat ironic that marching around and chanting for hours is exactly the sort of repetitive work that most people would be happy to see taken over by machines.

Although we hope these protests remain peaceful, there’s always a chance things can turn violent when tensions are high. Should things go south, take comfort in the knowledge that a company in Japan has introduced a robot ambulance service. It’s probably more accurate to compare it with roadside assistance, as the goal is to repair the robot on-site. That said, if the fault is more serious, they can bring the damaged bot back to HQ. Of course, the major difference between this program and a traditional ambulance service is that they’ll be able to bring along a spare robot that can take over the patient’s job while repairs are being made. Should anyone start doing that for humans, expect a few more protests.

Speaking of repairs, [Boone Ashworth] at WIRED recently wrote up an interesting hands-on experience he had with John Deere’s AI-driven DIY repair service at the company’s corporate headquarters. Armed with a laptop and tasked with fixing the error message showing on a ~$120,000 USD tractor, he was able to follow the instructions provided by the software to identify a sensor that had been unplugged. Reconnecting the sensor fixed the error message and elicited applause from the Deere reps who presumably had carefully unplugged the sensor in the first place for the purposes of the demonstration.

If that doesn’t strike you as a particularly impressive display for a subscription service which starts at $195 a year for each individual machine, you aren’t alone. When Boone reported his experience to critics of Deere’s repairability track record, it was met with literal laughter. You don’t have to have worked in the fields to know that a sensor becoming unplugged ranks pretty low on the list of potential problems you might face in the middle of a harvest.

We can certainly understand why Deere wouldn’t ask journalists to fix a blown clutch or a leaky hydraulic cylinder for the purposes of a media demo. Even so, they could surely have come up with something a bit more challenging if their goal was to convince customers to log into their repair service — something the company claims only about a thousand users do each day.

Finally, this one leans more heavily into the “arts and crafts” than we’d usually cover here on Hackaday, but [Terence Eden]’s Collection of Imaginary Software is too cool not to get a mention.

The idea is simple enough: make up fake disk labels for a bunch of fictional pieces of software (think the games David Lightman was trying to get his hands on in WarGames), stick them on some of the old 3.5 floppies we know you have hiding in a box somewhere, and put them in a frame.

As we’ve talked about in the past, many of us in the hacker and maker community were inspired by nerds in the media. This project strikes us as a fantastic way to show off just which examples you resonated with personally, and if any readers come up with something similar to adorn the walls of their basement, we’d love to see it.

See something interesting that you think would be a good fit for our weekly Links column? Drop us a line; we’d love to hear about it.

It is a classic Hackaday situation. You have an Egret GT E-scooter. It has a screen that shows the usual dash stats, but that led to an annoyance. You could accidentally enter firmware update mode and, from there, enter operational mode without the security PIN. [Ben] couldn’t let that stand, so he reverse-engineered the protocol and rewrote the firmware in Rust. As he put it, “… because I have to break… everything I own…” We get it.

The mobile app was useful for some basic info, since sniffing Bluetooth is fairly easy and analyzing mobile code is, more or less, straightforward. Analysis revealed some data that doesn’t show on the display and that several things are sent back to home base tagged with the scooter’s unique ID — another reason to gut the existing firmware.

Internally, the scooter uses the CAN Bus, so out came the oscilloscope and a homebrew CAN decoder.  Surprisingly, the CAN bus is accessible on the USB-C port’s data pins. Officially, the port is only for charging phones, so you have to wonder what your phone makes of the alien signals on the data pins when it is charging.

Firmware updates actually come in at least three flavors: display, input panel, and main controller. Reverse engineering the firmware update process was crucial to installing the new firmware.

If you own a similar scooter, this post is a goldmine. If you don’t, it is still a very detailed breakdown of a reverse-engineering workflow, and you can apply many of the tools and techniques to your next project.

Of course, another option is to just keep the scooter and replace the brains. If you want to learn more about reverse engineering, there are literally dozens of Hackaday posts to help you get started.

We’re at a fortunate moment: microcontrollers available at modest prices are edging into the capability level previously reserved for full-fat systems and can, through emulation, run software beyond classic 8-bit home computers, consoles, or old arcade games. A project we’ve been watching for a while is tiny386, an emulator for ESP32 boards that provides a 386 PC with just enough 486 and 586 instructions enabled to run a modern Linux kernel. Now we’re pleased to note that this platform is making it to the RP2350, with ports for both the FRANK emulation platform and the Waveshare Pi Zero boards. You can now have a 32-bit PC with all the peripherals, including VGA and DVI/HDMI, for the cost of an inexpensive development board.

Having seen tiny386 run on its minimum-spec ESP32 platform, we’ll concede that while it’s usable, it’s not the fastest experience, but the RP2350 port promises better performance. It’s not for a modern full-fat Linux distro, but should work well for running older operating systems such as DOS, or Windows 3.1 and 95, or even a lean Linux setup. This has fascinating potential: while these systems are old, they still have an enormous software library. The idea of useful general-purpose computing, 1990s style, in the palm of the hand, is interesting.

If you’re curious, you can find tiny386 here and the FRANK boards here. Maybe they’re a better route to ’90s fun and games than a 386 laptop.

You want Retro? We did, when we started our retrocomputing challenge. [Peter] decided that transistors weren’t retro enough, and sent us this lovely homebrew relay computer, complete with 16- bit CPU, which is rather more bits than one normally associates with clicky clacky contacts.

The architecture is very simple– it just uses an accumulator register, ACCU, and goes from there. All mathematics and save/load operations go through ACCU. There whole instruction set is only 19 commands, and he’s used that set to program such lovely things as calculating 3 digits of Pi– which only took 8 minutes of glorious clicking. There’s a demo video of that embedded below. [Peter] has even implemented a display by hooking his computer to a 32×32 LED matrix, but don’t expect it to relay updates really quickly.

If this computer looks familiar, it’s because its earlier incarnation was one of the more “extra” entries in last year’s one-hertz challenge, where it was used to blink an indicator lamp. Yes, even relay computers apparently get started with the “blinky” sketch.

If you want in on the fun, our retrocomputer challenge runs until October 27th, so there’s lots of time left to turn back the clock.

Although building a table saw out of LEGO is probably not the first thing that comes to mind when you look at those colorful bits of plastic, [Jamie] has been on a bit of a search for more applications of his LEGO-based air-powered motors. Naturally this led to the idea of doing something useful with it, like making a table saw you can actually use for real wood.

Starting off with a basic prototype using only regular LEGO pieces to get the mechanism figured out, [Jamie] then builds this up into said air-powered table saw featuring an actual metal blade. Suffice it to say that this isn’t something that you want your children to do with their LEGO while unsupervised.

The star of the show is of course the air-powered turbine that spins the blade. This is something that [Jamie] has been working on for a while, going through a number of prototypes to figure out a 3D printed geometry for the turbine blade that helps to convert as much of the high-pressure air into rotation.

Along the way it was also discovered that 3D printing saw blades is pretty hard, probably due to the lack of a sharp edge. This is definitely an area where it’s hard to beat a real table saw blade, with the added caveat that anything that’s good at cutting up boards of wood and sausages will just as happy slice through careless primate fingers.

In terms of safety features, the air supply is cut automatically with a sort of dead-man switch that requires you to keep one hand on it while using the final table saw design. There also an auto-feeding system added that tries to guide the board into the saw, but this turned out to be finicky. Suffice it to say that an air compressor and a handful of non-LEGO-approved components created a pretty convincing table saw.

[Andy Huot] has a fantastic-looking infinity mirror digital clock that really raises the bar. It uses high quality components, smart use of RGB LED animations, and a clever “stacked diffuser” vertical design to the 7-segment display elements that really enhances the infinity mirror effect. It needs to be seen in action, so check it out.

The end result is expressly portal-like, with the smooth animations of the LEDs really playing into the effect. The size helps, too. It’s 24 inches in diameter, giving it considerable presence.

A basic infinity mirror design consists of lit elements sandwiched between a reflective back surface and a partially-reflective, partially-transmissive top cover. That same basic principle is used here, but with great care given to ensure nothing so much as a fingerprint spoils the illusion. For example, the top cover is a disk of acrylic with a 90% reflective film affixed to the inside surface. That’s easy enough to DIY with some car tint, but [Andy] found that for the very best results it was worth having high-quality film professionally applied.

We like the use of 3D-printed custom jigs for soldering the segments of RGB LED strips, and holding the pre-measured wires in place with some putty is a great way to keep them in place while working. In case you’re wondering, the mirrored acrylic making up the back wall has holes in it for mounting each segment’s LED strip in a holder, and running the wires to the rear.

The video (embedded below) documents every step of the assembly, and it’s a serious build. While the design files for the 3D-printed parts are not free, there’s certainly enough detail for an enterprising hacker to replicate the design in their own way.

Apple hardware has always been proprietary, sometimes to an extreme. But that’s not to say that it’s impossible to make something that does the same job, which is what [DosFox1] appears to have done with the OSHintosh. It’s an open source PCB that implements a Mac 512k. Is it a 68k Hackintosh? You decide.

While it boots into a classic Mac OS image, it’s not quite a Mac. For a start, there are no disks, and no SCSI. Instead it boots from a disk held in ROM, which we guess will be a lot faster than the floppy from back in the day. They’ve even managed to do it on a 2-layer board, which means that despite its size, it shouldn’t be too expensive to have made.

We’re not sure quite what the legality of dumping a Mac ROM image to the ROM on this board would be, but assume for a moment that you own a copy in a defunct original Mac. This board can’t yet replace the original due to the disk issue, but given that original Macs are now long in the tooth, a modern replacement for those who must have hardware rather than an emulator sounds like a good idea. Perhaps for some people it will join the FPGA Amiga.