Preserving Floppy Disks Via Logic Analyser

The floppy disk is a technology that is known only to the youth of today as the inspiration for the Save icon. There’s a lot of retro computing history tied up in these fragile platters, thus preservation is key. But how to go about it? [CHZ-Soft] has found an easy way, using a logic analyzer and a healthy dose of Python.

Floppy drives have particularly low-level interfaces, offering up little more than a few signals to indicate the position of the head on the disk, and pulses to indicate changes in magnetic flux. The data is encoded in the pattern of flux changes. This has important implications as far as preservation goes – it’s best to record the flux changes themselves, and create an image of the exact magnetic state of the disk, and then process that later, rather than trying to decode the disk at the time of reading and backing up just the data itself. This gives the best likelihood of decoding the disk and preserving an accurate image of floppy formats as they existed in the real world. It’s also largely platform agnostic – you can record the flux changes, then figure out the format later.

[CHZ-Soft] takes this approach, explaining how to use a Saleae logic analyser and a serial port to control a floppy drive and read out the flux changes on the disk. It’s all controlled automatically through a Python script, which automates the process and stores the results in the Supercard Pro file format, which is supported by a variety of software. This method takes about 14MB to store the magnetic image of a 720KB disk, and can even reveal a fingerprint of the drive used to write the disk, based on factors such as jitter and timing.

It’s an impressive hack that shows that preservation-grade backups of floppy disks can be achieved without spending big money or using specialist hardware. We’ve seen other projects in this space before, too.

Vintage Programmer Gets Modern Chip Adapter

While trying to revive a Donkey Kong Jr arcade board, [Jelmer Bruijn] found himself in the market for an EPROM programmer and became the proud owner of a 1990’s era Dataman S4. Despite its age, it’s a fairly nice tool which allows you to read and write a laundry list of different EPROM types, all without being tied to a computer. The only catch is that a few types of chips need an adapter to work in the Dataman S4, some of which are unsurprisingly no longer available.

After some above and beyond support from the current crew at Dataman set him on the right track, [Jelmer] decided to try his hand at reverse engineering how the old adapters worked so he could build his own. His ultimate goal was to read 40 pin EPROMs on the 32 pin Dataman S4, but in the end he says the information he gathered should be applicable for building other adapters if you ever find yourself in need of such things.

As you might expect, there’s a bit more to the project than a simple pin adapter. [Jelmer] assumed some kind of shift register or latching arrangement would be required to make up for the shortage of pins on the Dataman S4’s ZIF socket. It was just a matter of figuring out how it all went together.

Luckily, [Jelmer] found that the programmer would happily attempt to perform operations on a 16 bit EPROM even though no adapter was physically present. This gave him a chance to probe around with a logic analyzer to figure out what it was trying to accomplish. The trick turned out to be splitting the 16 bit bus into two 8 bit buses which are requested sequentially.

With careful observation, close studying of 16 bit chip datasheets, and much brow furrowing, he was eventually able to come up a design that used five 74xx573 latches and put a schematic together in Eagle. There were a few kinks to iron out when the boards finally arrived, but ultimately the design worked on the first try. [Jelmer] says the same technique should work for 42 pin EPROMs, but as Dataman still actually sell adapters for those he decided not to supply schematics for it.

[Jelmer] tells us that he was inspired to send this success story our way after reading how our very own [Elliot Williams] took the long away around to erase a couple UV EPROMs recently While this isn’t the first time we’ve seen somebody have to hack support for 16 bit EPROMs into their programmer, it’s good to see that the manufacturer at least had the customer’s back in this case.

Raspberry Pi Powers This Retro Chess Computer

If you imagine somebody playing chess against the computer, you’ll likely be visualizing them staring at their monitor in deep thought, mouse in hand, ready to drag their digital pawn into play. That might be accurate for the folks who dabble in the occasional match during their break, but for the real chess aficionados nothing beats playing on a real board with real pieces. Of course, the tricky part is explaining the whole corporeal thing to a piece of software on your computer.

Enter the “Chess Challenger” by [slash/byte]. Modeled after a commercial gadget of the same name from 1978, his retro-themed open hardware design utilizes the Raspberry Pi Zero and modern chess software to bring the vintage concept into the 21st century. With the Chess Challenger and a standard board, the player can face off in an epic battle of wits against the computer without risk of developing carpal tunnel. We can’t guarantee though that a few boards might not get flipped over in frustration.

The pocket sized chess computer uses a “sandwich” style construction which shows off the internals while still keeping things reasonably protected. All of the electronics are housed on the center custom PCB which features a HT16K33 driver for the dual LTP-3784E “starburst” LED displays, a MCP1642B voltage regulator, 16 TL3305 tactile switches for the keyboard, and a MCP73871 battery management chip for the 3.7 volt lithium-ion battery that powers the whole show. The Pi Zero itself connects to the board by way of the GPIO header, and is mechanically supported by the standoffs used to hold the device together.

On the software side of things, the Pi is running the mature Stockfish open source chess engine. In development now for over a decade, this GPL licensed package aims to deliver a world-class chess gameplay on everything from smartphones to desktop computers, and we’ve seen it pop up in a number of projects over the years. [slash/byte] has provided a ready to flash SD card image for the Raspberry Pi, and even provides detailed installation and setup instructions which guide you through some of the more thorny aspects of the setup such as getting the Pi running from a read-only operating system so that abrupt power cuts don’t clobber the filesystem.

Over the years, some of the most impressive projects we’ve seen revolved around playing chess, and this latest entry by [slash/byte] is no exception. Another example of the lengths the chess community will go to perfect the Game of Kings.

Continue reading “Raspberry Pi Powers This Retro Chess Computer”

RC Controller Becomes XInput Controller

XInput is an API that is used by applications to interface with the Xbox 360 Controller for Windows. The 360 controller became somewhat of a “standard” PC gamepad, and thus many games and applications support the XInput standard.

[James] is working on an entry for a robotics competition, and wanted a controller to use with their PC that was more suited to their build. They took an RC controller, and converted it to work with XInput instead.

The controller in question is the JJRC Q35-01, a trigger-type RC controller available for under $20. The conversion is executed neatly, with the original STM microcontroller being removed from the board, and the PCB traces instead being connected to a Teensy 3.5 which takes over running the show.

The conversion is remarkably complete, with the team not stopping at just reading the buttons and steering potentiometer. A USB logic analyzer was used to figure out how to control the LCD, and a calibration mode implemented just in case.

[James] has shared the work on Github so it’s reproducible for the average maker. We’ve seen plenty of builds in this space, like this tilt controller from [Electronoobs]. Video after the break.

Continue reading “RC Controller Becomes XInput Controller”

A Foggy Lightsaber Build

Lightsabers have enchanted audiences since their appearance in the very first Star Wars film in 1977. Unfortunately, George Lucas hasn’t shared the technology in the years since then with the broader public, so we’re left to subsist on pale imitations. This is just such a build.

The closest human analog to Jedi technology is the laser, and this build uses 8 of them in combination with two LEDs. They’re aimed to coincide at a fixed distance above the hilt. A CO2 bicycle inflater is then used to blow through an e-cigarette to create a fog. This makes the red lasers readily visible to the human eye.

This ersatz lightsaber does have its limitations – fast motion tends to scatter the fog, making it once again invisible, and it’s really at its best held in a vertical orientation. There’s also some divergence beyond the focused point. With that said, it does look somewhat impressive when held still, smouldering away.

Until we gain a better mastery of plasma physics, perhaps you can make do with this fire-based build? Video after the break.

[Thanks to qrp-gaijin for the tip!]

Continue reading “A Foggy Lightsaber Build”

1973: When Calculators Were Built Like Computers

Should you ever pick up [Steve Wozniak]’s autobiography, you will learn that in the early 1970s when his friend [Steve Jobs] was working for Atari, [Woz] was designing calculators for Hewlett Packard. It seems scarcely believable today, but he describes his excitement at the prospects for the calculator business, admitting that he almost missed out on the emerging microcomputer scene that would make him famous. Calculators in the very early 1970s were genuinely exciting, and were expensive and desirable consumer items.

[Amen] has a calculator from that period, a Prinztronic Micro, and he’s subjected it to an interesting teardown. Inside he finds an unusual modular design, with keyboard, processor, and display all having their own PCBs. Construction is typical of the period, with all through hole components, and PCBs that look hand laid rather than made using a CAD package. The chipset is a Toshiba one, with three devices covering logic, display driver and clock.

The Prinztronic is an interesting device in itself, being a rebadged 1972 Sharp model under a house brand name for the British retailer Dixons, and that Toshiba chipset is special because it is the first CMOS design to market. It was one of many very similar basic calculators on the market at the time, but at the equivalent of over 100 dollars in today’s money it would still have been a significant purchase.

Long-tern Hackaday readers will remember we’ve shown you at least one classic calculator rebuild in the past, the venerable 1975 Sinclair!

Forcing Amazon Alexa Compatible Stuff To Speak To Google Assistant

It took a long time, but it’s 2019, and we’re starting to get used to the concept of talking to a computer to make it control things around the house. It’s not quite as cool as it seemed when we saw it in films way back when, but that’s just real life. The problem is, there’s a multitude of different systems and standards and they don’t all necessarily work together. In [Blake]’s case, the problem is that Woods brand hardware only works with Amazon Alexa, which simply won’t do.

[Blake] went through the hassle of getting an Amazon Alexa compatible WiFi outlet to work with Google Assistant. It’s a bit of a roundabout way of doing things, but it works. A TP-Link HS-105 WiFi plug is used, which can be controlled through Google Assistant voice commands. The part consists of two PCBs – a control board that speaks WiFi, and a switching board with relays. [Blake] used the control board and hooked it up to a Raspberry Pi. When switched on by a command from Google, the HS-105 sets a pin high, which is detected by the Raspberry Pi. The Raspberry Pi then runs a software implementation of the KAB protocol used by the Woods hardware, triggering it when it receives the signal from the TP-Link hardware.

If we understand correctly, [Blake] had to go to this trouble in order to make his special outdoor-rated outlets work with his Google Home setup. Hopefully interoperability improves in years to come, but we won’t hold our breath.

We’ve seen some pretty convoluted projects in this space before, often using IFTTT — like this ESP8266 voice controlled tank.