An Orbital Sanders Crash Course And The Threat Of HAVS

This is your hand on bad vibrations. (Credit: Five Duck Studio, YouTube)
This is your hand on bad vibrations. (Credit: Five Duck Studio, YouTube)

Most people know about orbital sanders, as the cousin of sheet sanders, with many people using them every day to make wood and other surfaces smooth. Yet if you have ever wondered at the slightly numb and tingling feeling in your hands after using them for a while, you really want to watch this deep dive by [Five Duck Studio] on how orbital sanders work and why not all vibrations are good vibrations.

First, the basic workings of an orbital sander are explained in the video, including the way that the orbital sanding pattern is created by the spinning disc. These patterns aren’t the same size for each sander, with the ‘finisher’ ~2.5 mm pattern being decidedly more suitable for fine work, while the roughly 5 mm pattern is better for coarser work.

From here, the details spiral into the various brake mechanisms, which prevent the disc from spinning wildly when not on a surface. This can be as simple as an O-ring providing some friction.

Continue reading “An Orbital Sanders Crash Course And The Threat Of HAVS” →

Borland C++ 2.0 Compiler Source Reconstructed

As the successor to Turbo C++, Borland C++ was a staple of professional IDEs for C and C++ development, starting with the initial 2.0 release in 1991. Being a commercial project the original source code for the toolchains were naturally not made available by Borland, but thanks to the efforts of [Abedegno] we have now got what is claimed to be a byte-perfect recreation, in the sense that the binaries compiled using the toolchain are identical to the original toolchain.

The process of creating the source from the original toolchain binaries is detailed in a separate document, including the use of [Abedgno]’s Claude Code-based Exhume tool to assist in the effort.

Having the source code for BC++ 2.0 available is probably most useful for projects that deal with DOS-based software from the same era, as well as for purely historic interest reason. When BC++ 2.0 was released, the C programming language had only just seen itself standardized in the form of C89, and C++’s initial standard in 1998 was still years away.

Thanks to [Stephen Walters] for the tip.

Using A Toothbrush’s NFC Chip To Unlock A Computer

Depending on which type of electric toothbrush you are using, the replaceable brushes may contain an NFC chip that the handle and possibly base station uses to track various details, such as time spent brushing and when to replace the brush. The Philips Sonicare of [Circuit Helper] is one such unit, with its NFC chip tracking aspects like runtime and pressure.

Unsurprisingly it’s easy enough to read and write this same NFC chip with a PN532 NFC reader and ESP32-S3 MCU. This reveals data fields for everything from brush type, to total runtime and expected lifetime, inviting a bit of experimentation on how certain usage patterns affects these data fields.

This much is perhaps not too shocking, but the fun part is what you can do with the chip after you have figured out how to write to its memory. How to unlock these units and their NXP NTAG213 IC has been figured out a few years ago already, so the hardest part was to figure out what to do with this information.

The demonstrated use case in the video is to unlock an Apple Macbook, which is maybe a bit too niche. Also demonstrated is taking the chip and its antenna out of the brush, which turns out to be quite easy. Perhaps salvaging just this one part of the brush is the more practical and hygienic option, as who doesn’t like building up a strategic supply of ‘free’ NFC chips?

Continue reading “Using A Toothbrush’s NFC Chip To Unlock A Computer” →

Drop-in Vintage CPU Replacements With The TranZPUter Project

One of the struggles with vintage computer systems is that many of the ICs in them have no modern-day version that you can just purchase and drop-in. Creating replacements that use modern-day ICs inside has consequently become a popular direction, with [Philip Smart]’s TranZPUter being one such example.

Standing for ‘transformable ZPU Computer’, the tranZPUter is transformable in the sense that it features an FPGA or MCU and the initial iteration targeting the ZPU Evo CPU design. This has led to a number of variants of this concept, including a version targeting the Z80, the 6502 and 6809. These are based around the RP2350B MCU, using its PIO peripheral to great effect.

Of these the Motorola 6809 is probably the lesser known MPU, having been launched in 1978 as an 8-bit MPU with some 16-bit features that could beat the 6502 in many metrics courtesy of its more advanced hardware. It being more expensive led to it only being used in systems like the TRS-80 Color, Dragon 32/64, SuperPET and a whole range of arcade systems.

If you have any of those 6809-based systems and the MPU gave up the ghost, you can drop in the Pico6809 board featuring said RP2350B MCU as well as an ESP32 co-processor. Currently it targets the Dragon 32/64 systems, adding not just a fresh MPU, but also adds virtual floppy and cassette devices as well as network support as options.

Overall it seems like a pretty extensive project that might already have found purchase within the retrocomputing community.

Fixing A Dead Socket LGA 1851 Mainboard With A Resistor

Doing board level diagnosis on a PCB is hardly black magic, but some PCBs are definitely more daunting than others. The Socket LGA 1851 mainboard that [Fix the Pixel] got in for repair being one of the harder cases due to the sheer size and complexity. Adding to the excitement was having to purchase a used CPU for it off eBay to even test the board and work through the boot-up sequence to find the culprit.

A basic understanding of how these mainboards power up and verify that they can move on to the next phase is essential here, starting with the power rails. Although the culprit turned out to be a single missing 5.1 Ohm resistor on an SPI clock line, you still have to reason your way through the diagnosis. For this mainboard the boardview was fortunately available, but that still doesn’t make it easy to spot components that have quietly left the chat.

With the CPU and RAM installed the board doesn’t bother to boot up, with the VRM controller for the CPU’s power phases showing its enable pin to stay low. Going down the list of conditions for this pin to be pulled high the culprit was eventually found, when the PCH – the board’s chipset – never reading the BIOS chip.

Checking the SPI lines on the mainboard near the BIOS chip quickly showed the knocked-off resistor on the SPI clock line. Soldering a fresh resistor in place resulted in the board happily booting up once more. Although having a boardview here available helps a lot, checking such basics like the SPI line resistors around the BIOS can be a quick checklist item before dragging out the big diagnostics guns or shelling out money for a boardview file.

Continue reading “Fixing A Dead Socket LGA 1851 Mainboard With A Resistor” →

Baochip-1x: A Mostly-Open, 22nm SoC For High Assurance Applications

For most people, just getting any old microcontroller or system on chip (SoC) from our favorite – or cheapest – vendor is more than good enough. But if you’re really into high assurance computing where every transistor has to be accounted for, you got a bit of a problem. This is basically why [Andrew “Bunnie” Huang] pitched in and had the Baochip-1x produced.

This SoC’s design is based heavily on the FPGA-based CPU in the Precursor device, which itself is claimed to be a fully verifiable communicator design. Since it does have an MMU, you can run any software on it that supports the RV32IMAC RISC-V instruction set, with a Coder’s Guide available for those who might feel interested in this SoC, along with the SystemVerilog and Verilog-based sources.

In addition to the DIY assembly process, you can even get a physical hardware version, including the ‘Dabao’ evaluation board with a very Raspberry Pi Pico-shaped form factor. Inside this SoC is a single-core, 350 MHz VexRISC-V core, 4 MB resistive RAM (RRAM) and 2 MB of SRAM, along with a whole heap of security-related features.

Why Engineers Are Forced To Create Junk Designs

It’s become a bit of a platitude to state that products were manufactured better in ‘the olden days’, but as [The Meandrous Engineer] covers in a recent video essay, the truth is a lot more greyscale and nuanced than something so trite.

The very short version is that it is the dominant culture of a nation in which products are manufactured that determines how many shortcuts and potential product life-shortening decisions are made. This same culture works its way down into company culture, including the engagement of the so-called C-suite with the engineers and folk who keep the now mostly automated manufacturing lines running, as well as vice-versa.

Old-school die-cast models and incandescent light bulbs saw their own series of manufacturing shortcuts, including a pre-World War 2 scandal about the artificial limiting of the lifespan of lightbulbs so that customers would buy more of them. This foreshadows what happened as soon as plastics and computer-aided design and manufacturing came on the scene.

Post-WW2, people like W. Edwards Deming were welcome guests in Japan and other rebuilding nations, introducing the Lean method of manufacturing which was at the time not deemed desirable in a post-war USA. For Japan, South Korea and other nations in the region this meant a boom in manufacturing, with a quality level that would ultimately trounce that of their Western equivalents.

Continue reading “Why Engineers Are Forced To Create Junk Designs” →