Mysterious Files PH

Wednesday, November 18, 2026

The Mega Tamagotchi Manga Reader

November 18, 2026 0

You could read manga in the classic bound paper format. But then you’d have to carry around lots of volumes that take up lots of space. The way around this is to use an e-reader, that stores lots of manga in digital form. [Arnov Sharma] built his own themed after the classic Tamagotchi.

What you’re looking at is a big ol’ 3D printed mega-Tamagotchi. It apes the design of the original digital pet, but is scaled up to a size large enough to host a large screen. In particular, the Waveshare ESP32-P4 Touch LCD 4.3 development board, which pairs the 480 x 800 screen with the capable wireless-enabled microcontroller and even a little speaker. Two, as it happens, because there’s an ESP32-P4 and an ESP32-C6 on the board. Power is via a pair of 2000 mAh lithium-ion cells. Manga is loaded on to the device via an SD card, in JPEG format. [Arnov] uses the ESP32-P4’s hardware JPEG decoder to make flipping pages quicker than the 2-5 seconds it would take to do the same decode in software. There are also some fun tricks in the firmware that improve contrast in black-and-white scans and vibrancy in color scans, too.

If you want to read manga on the go in a device with a fun form factor, consider building something similar yourself. To populate your reader, consider a past project we examined that turns movies into comic books. Video after the break.


Handheld Motor Cancels Out Every Twist and Turn

November 18, 2026 0

It’s one thing to know that input from a motion sensor can steer a motor. It’s another to see and feel the two cancelling out the other in real-time, right in the palm of one’s hand. That’s [cpietsch]’s takeaway from the CAN do GYRO, a brushless motor with a CAN interface and tiny STM32-based development board perched atop it.

No matter how one moves, the motor swivels to keep pointing the top in the same direction; a bit like a south-pointing chariot.

It’s essentially a one-axis gimbal with a few thoughtful features. The unit tracks itself fully in three dimensions, so while the motor is limited to one axis, the unit doesn’t get confused by complex movements. It also auto-calibrates, and auto-stops within half a rotation if it detects the motor spinning freely.

The hardware consists of a tiny XIAO STM32C5 microcontroller board with integrated IMU (Inertial Measurement Unit) and CAN transceiver, and an M5Stack RollerCAN motor. The motor, handily, has a small OLED screen built into it.

Combined with a battery it’s small enough to be handheld while it shows off what a tight control loop paired with a suitable motor can do. Watch it in action in the video, embedded below.

Of course, accurate gimbals using brushless motors have been around for many years. But one thing that’s plain is just how much the kind of hardware available to individuals has changed. Compare this build to a DIY gimbal project from about ten years ago and you’ll see the function looks about the same, but today’s hardware has evolved considerably.


Serial: The Port That Won’t Die

November 18, 2026 0
Serial: The Port That Won’t Die

Computers have changed quite a bit over the last 60 years. Good luck plugging in an old MFM disk into your modern computer. Plugging in a parallel printer is difficult, although not impossible, as long as the device really is a printer. But the humble serial port refuses to die.

Sure, you probably don’t have a 25-pin connector on your laptop anymore. You might not even have a nine-pin connector. But serial communication is everywhere, especially if you work with microcontrollers or industrial equipment. The connectors have changed, but much of the underlying technology would be recognizable to someone working with a computer in 1975.

From Clicking Teletypes

The ASR-33 was the best way to talk to a computer until it wasn’t. (Photo by [ArnoldReinhold] CC-BY-SA-3.0)
Before video terminals, there were teletypes. These electromechanical beasts could send and receive characters over wires using a current loop. Older machines, such as the Teletype Models 15 and 28, commonly used 60 mA loops (and five-bit codes), often at 120 volts DC. Later machines, including the iconic ASR-33, generally used 20 mA loops. Current flowing represented a mark, while an interruption in the current represented a space. Marks and spaces on the line translate to 1s and 0s. The beauty of current loops was their simplicity, relative resistance to electrical noise, and their ability to drive very long cables.

The Electronic Industries Association introduced RS-232 in 1960, followed by RS-232A in 1963 and RS-232B in 1965. The familiar RS-232C arrived in 1969, followed by revisions D, E, and F. You’ll also see EIA-232 and TIA-232, but everyone still calls it RS-232. Unlike ordinary logic signals, RS-232 uses positive and negative voltages. A mark (logic 1) is negative, while a space (logic 0) is positive. Receivers recognize voltages more negative than -3 V as a mark or more positive than +3 V as a space. The region between is undefined. Actual transmitters often produce something like ±12 V, although lower voltages are common, especially on things like laptops.

As computer systems got simpler, turning TTL levels into negative voltages was always a design nuisance. Many systems had a bipolar 12 V supply just for the RS-232 interface. Some chips would “steal” negative voltage from the device they were connected to (these were notorious for often working only when the other device was quiet, so some chips could only do half-duplex). The MAX232 and similar chips won the day. Using capacitors in a charge pump configuration, they can take a single-ended logic power supply like 5 V and convert it to positive and negative voltages sufficient for RS-232. The MAX3232 does the same for 3.3 V systems.

RS-232 is a standard, but it only dictates the electrical interface, connector assignments, and control signals. It doesn’t tell you what the data means.

Who’s Talking?

Female DB-25 and DE-9 connectors ([Project Kei] CC-BY_SA-4.0)
RS-232 was designed to connect Data Terminal Equipment (DTE), such as a computer or terminal, to Data Circuit-terminating Equipment (DCE), typically a modem. Signal names are always from the DTE’s perspective. Transmitted Data (TXD) leaves the DTE, while Received Data (RXD) enters it. The DCE does the opposite. Originally, RS-232 used a 25-pin D-subminiature connector, properly called a DB-25. IBM PCs popularized a smaller nine-pin connector, often incorrectly called a DB-9. Technically, it is a DE-9.

Here are the important signals, assuming a DTE connection (2/25 means pin 2 on the 25-pin connector):

  • TXD (2/25, 3/9; output) – transmit data.
  • RXD (3/25, 2/9; input) – receive data
  • RTS (4/25, 7/9; output) – request to send
  • CTS (5/25, 8/9; input) – clear to send
  • DSR (6/25, 6/9; input) – data set ready
  • GND (7/25, 5/9; – ) – signal ground
  • DCD (8/25, 1/9, input) – data carrier detect
  • DTR (20/25, 4/9, output) – data terminal ready
  • RI (22/25, 9/9, input) – ring indicator

The DB-25 also has a protective ground on pin 1, generally associated with the connector shell on a DE-9. For DCE, switch every output to input and vice versa.

Most modern applications need only TXD, RXD, and ground. But the remaining signals were important when computers communicated through actual telephone modems, or when talking to devices that can’t handle 100% throughput. DTR indicated that the terminal was ready, DSR indicated the modem was ready, and DCD reported a connection to a remote modem. RI indicated an incoming telephone call. Plus, RTS and CTS usually indicate that a device has data to send or is ready to receive data. It is also possible to send a character (like XOFF) to stop a transmitter from overflowing a receive buffer, but that’s not part of the standard. In fact, you can’t actually depend on the handshaking signals, either. Some devices ignore handshaking or use the lines differently from other devices.

Bits and Pieces

Of course, having the correct wires doesn’t guarantee communication. Both ends must agree on the format. Most serial connections use asynchronous communication. The line idles in the mark state. A space start bit announces an incoming character, followed by data bits transmitted least-significant bit first, optional parity, and one or more stop bits.

The letter H sent via RS-232 — probably followed by “ackaDay.”

Really, stop bit is a misnomer. A stop bit is a mark, and that’s also the idle state of the line. So the stop bit is more of a promise not to start transmitting again for at least a certain time period. One stop bit means you’ll get at least one bit’s worth of idle before the next character starts. Two means two bits’ worth. But these are minimums. If you send one character per minute, you’ll have — effectively — many stop bits.

You’ve probably seen a setting like 9600 8N1. That means 9,600 baud, eight data bits, no parity, and one stop bit. Including the start bit, each character takes ten bit times. So 9,600 baud carries, at most, 960 eight-bit characters per second, ignoring higher-level protocol overhead and gaps in sending or handshaking holdoffs. Common options include five through eight data bits, even or odd parity, and one or two stop bits. Some older equipment uses 1.5 stop bits. Parity provides rudimentary error detection (because it assures all characters have an even or odd number of 1 bits), but it can’t correct errors and won’t detect every possible corruption.

A prolonged space is called a break. It isn’t an ordinary character and was traditionally used to signal special conditions or interrupt a system.

Making a Connection

One problem with serial communication is that the sender might produce data faster than the receiver can handle it. Hardware flow control generally uses RTS and CTS. Historically, these signals helped coordinate modem transmission, but modern equipment commonly uses them to indicate whether another device may send data. Software flow control instead sends special characters: XOFF (ASCII 19, or Ctrl-S) means stop, and XON (ASCII 17, or Ctrl-Q) means resume. Software flow control saves wires but can interfere with binary data unless the protocol handles those control characters appropriately. You also have to send XOFF early enough for the sender to process it before your buffer overruns. Again, there is a wide variation in how different devices or software packages handle handshaking.

The April 1983 Byte Magazine had a homebrew breakout box from the legendary [Steve Ciarcia]
Connecting DTE to DCE requires a straight-through cable. Connecting two computers presents a problem: both transmit on their TXD pins and listen on RXD. Everyone is talking on one pin and listening on the other. The solution is a null modem cable, which crosses transmit and receive signals. Depending on the equipment, it may also cross RTS/CTS and connect DTR to DSR/DCD. There are several null modem wiring arrangements, which explains why one cable works perfectly while another one won’t.

Anyone who has worked extensively with serial equipment probably remembers breakout boxes. These useful devices sat between two connectors and provided LEDs showing signal states, along with switches or patch connections to rearrange the wiring. A breakout box, a terminal program, and a little patience could solve almost any serial mystery. Or at least reveal that someone had wired pins 2 and 3 backward. You’d usually figure out how to make things talk with a box like that and then select or build a matching cable, saving the box for the next job. Boxes ranged from simple connectors with patch cords to boxes with multiple LEDs and switches for each pin.

Serial Without the Serial Port

Today, USB-to-serial adapters have largely replaced physical PC serial ports. Chips from FTDI, Silicon Labs, WCH, and others provide virtual serial ports, typically appearing as COM devices under Windows or /dev/ttyUSB* under Linux. USB CDC ACM devices commonly appear as /dev/ttyACM*. You can get cables that terminate with a DE-9 or logic-level wires. You can also find multiport adapters that offer a bank of DE-9s via one USB port, but they are usually pricey, at least when new.

Logic-level cables are especially good for us. Microcontrollers often have serial ports with this level. Because they are meant to live behind a chip (like a MAX232) to get to RS-232 voltages (and those chips invert), the line state is reversed. That is, a high is a mark and a low is a space. Connecting a true RS-232 output directly to a microcontroller RX pin can damage the chip. Of course, a 5V-only cable on a 3.3V system isn’t a good idea either. While some 3.3V cables are made to work with 5V, always confirm the specs before making a connection. Some boards now have a built-in USB serial port or a direct USB CDC ACM implementation, so the PC sees a USB device, and the onboard system sees a serial port.

Serial communications survive because they are simple, inexpensive, and easy to debug. You don’t need an elaborate network stack or even a sophisticated operating system. A UART, a few wires, and some software will do. After more than six decades, that’s a pretty good argument for keeping an old technology around.

If you don’t like a USB cable, try WiFi. If you want to watch a serial port, you can use an oscilloscope, a logic analyzer, or just resort to software tricks.


Remarkable Observatory Receives Orbital Radio

November 18, 2026 0
Remarkable Observatory Receives Orbital Radio
Starlab Observatory Received Image

There’s nothing quite so nostalgic as the time honored tradition of tuning across the HF bands, picking out signals from the noise. Add satellites and VHF/UHF to the mix, then replace the old shortwave receiver with a smattering of software-defined radios. With an ESP32 controlled antenna switch (and the matching antennae), some Python, and a dash of Claude Code, and you’re approaching what [Tommy Lather] has done with his Starlab Observatory.

Starlab Equipment neatly organized on a wall
A neat installation makes maintenance and upgrades straightforward

Determined to find out what was inhabiting his local electromagnetic spectrum, [Tommy] picked up a cheap RTL-SDR receiver and an antenna. The goal? Receiving some ISS image transmissions. The results? Let’s say mixed. But it lit a fire, and soon, he had more hardware than he could handle on his own. The slope became slippery, and before he knew it, the Starlab Observatory was an Open Source GitHub Project!

What makes it an Observatory instead of a random menagerie of radio memorabilia? Intelligence. An ESP32 based antenna switch takes  commands from a dedicated Ubuntu computer. The PC, running Starlab, predicts satellite passes, and selects the correct receiver and antenna combination to receive data, which then gets logged and processed. Multiple jobs can run at once. The RF spectrum doesn’t stand a chance!

We have to wonder if a fully programmable az-el mount such as the AntRunner isn’t in [Tommy]’s near future!


Tuesday, November 17, 2026

Custom Firmware for Fortinet FortiGate 60 Firewall/Router

November 17, 2026 0
Custom Firmware for Fortinet FortiGate 60 Firewall/Router

When [Matt Williams] found an old enterprise firewall in the trash, he knew he had to do something with it. After cracking it open, he found that this 2000s-era Fortinet FortiGate 60 hardware firewall has some very hackable hardware in the form of a VIA C3 mainboard. This is an x86-compatible CPU that was very popular in small form-factor and industrial solutions around 2000s, meaning that it should be able to run just about anything that’s happy to run on its 400 MHz single core.

Unfortunately it wasn’t a standard Mini-ITX C3 board like the one that [Matt] also has kicking around, as that one features standard DIMMs for the memory modules. For this firewall the 128 MB of SDRAM was soldered to the board, with the only clue as to how to initialize it in the original firmware. Ergo this firmware had to be reverse-engineered to figure out just how this was supposed to happen.

With that done, Linux 2.4 was happy enough to boot on it with a bit more tweaking. Using the framebuffer driver applications like DOOM happily ran, as the above graphic shows. That it’s very much green is due to only the green pin on the VGA connector being probed. Since it’s a firewall Fortinet only added a physical DE-9 port in addition to the internal IDE interface and CF card slot.

If one were to wire up these pads on the mainboard to physical connectors, it would actually make for a pretty decent little system for what the kids call retro gaming these days.


Testing TISMO Whisker-Reinforced Poticon STD1 PA Filament

November 17, 2026 0

Although at first glance potassium-titanite (TISMO) whiskers don’t seem to be much of a change from chopped glass- and carbon fiber in FDM filaments, they’re really quite different. They’re not only much smaller, they’re also less abrasive, and work with 0.2 mm nozzles. Although basically just found in industrial filaments right now, [JanTec Engineering] put a spool to the test to see what these whiskers bring to the party.

While at an event in Japan, [JanTec] got handed a spool of Poticon STD1 NTL34M PA filament, presumably the common PA6, AKA Nylon. In their messaging the company calls it LEXTER, a bio-based polyamide.

This was subsequently put to the test after returning home, with the recommended print settings and the newly constructed testing machine, called the Atlas 2000. This is an open source testing machine that could be handy if you have about $500 lying around and an urgent need to test the tensile, compression and bending properties of materials.

The filament under test is 20% TISMO by weight, with it scoring well in the tensile strength test, while being about as brittle as the datasheet suggests. Such reinforced polymers are generally known for being stiff and brittle, so this is little surprise. Perhaps the biggest advantage of this filament is that you can print finer details with it using an 0.2 mm nozzle, making it an interesting engineering filament in that respect.

Also touched upon in the video are the potential health risks of this filament, with these whiskers being definitely easy to inhale. This also is reminiscent of the potential carcinogenic risks of chopped carbon fiber, where fragments of these already small fibers can pose similar risks as asbestos.

As for the constant brittleness in these purported reinforced filaments, this would seem to be due to poor adhesion between the fiber (or whisker) and the thermoplastic. Unlike with thermoset polymers where there’s an active interface between the fiber and the polymer that creates a strong molecular bond, there’s generally a void between thermosets and additives like fibers due to the lack of any chemical activity while cooling.


The FM-1: Open Source Hacked Open, Vibe Coding, and Farting Synthesizers

November 17, 2026 0

The M-Vave FM-1 was a pretty unremarkable little synthesizer “toy” until the open-source synth hackers took it over. Now, it’s a sweet platform for exploration, the incredible work done by the community has encouraged the manufacturer to release an open SDK, and it has recently taken the global synth nerd community by storm. (It has sadly also gotten about a 50% markup in the last month due to this popularity.)

It’s the perfect storm of inexpensive hardware, vibe-coded software, and easy-to-use tooling that enables synthesizer firmware-hacking for the mainstream. It is also the fashionable box of the moment in a nerdy niche of the synthesizer world at the moment and it’s something that we’re going to see in non-synthesizer contexts as well, so buckle up.

Opening Already Open Software

The funny thing about the FM-1 is that most of the good stuff inside it was open-source all along. As it is sold, it is a Yamaha DX7 emulator, and it appears to be running the same sound engine as Dexed, which is an open-source DX7 clone based on the even older music synthesizer for android (msfa).

Dexed, and its smaller brother MiniDexed, has given birth to many sweet synthesizer hacks that we’ve seen here, including a personal favorite: a Yamaha TX816 clone based on a Raspberry Pi. So it certainly looked to everyone at the time as if M-vave wrapped a not-entirely-inspiring user interface around this sound engine and shipped it.

And that would have been the end of it too, if it weren’t for those meddling kids [AL-255] who did a thorough reverse-engineering of the machine about four months ago, which laid the groundwork for everything else to come. Today, we’re looking at around 250 firmwares for this little beasty, so it’s no exaggeration to say that this opened the floodgates. And along the way, he verified signatures of the msfa code, so everyone’s suspicions proved correct.

The Robots Take Off

A quick note on the LLM / agentic coding elephant in the room here. From reading through [AL-255]’s work, it was most almost certainly worked on and documented by the robots, and we have no idea of the relative contribution of man and machine. Publishing a reverse engineering effort like this enables others in the community to point their robots at the repo, and gives them a tremendous leg up in the next steps along the path. We have just as little clue about how much of any of the subsequent synthesizer and sequencer routines were written with LLM assistance, but at the rate they’re popping up, we’d guess a lot.

[Baud Girl]’s sequencer looks great!
About two months after [AL-255]’s work, [Madeline] wrote one of the first reworks of the firmware for the FM-1, working as “Baud Girl”. It added some virtual analog to the cold DX7 tones, but notably wrapped it up in a much nicer UI than the original. It has so far been kept closed-source, but as a proof of what’s possible, it certainly inspired many others.

And then along came [Leo Kuroshita]’s open-source Felucca. This program added a yet fancier sequencer, multiple instruments, drums, and even sound effects. It turned the single-instrument FM-1 into a miniature music-production workshop – what the kids from the 1990’s would call a “groovebox”. [isod89]’s Sloop would refine on Felucca, and is probably the standout application running on the FM-1 platform at the moment.

The Firmware Hub started collecting a list of applications written by the community, and there are 250 of them in about six weeks’ time. Suffice it to say that we can’t even begin to scratch the surface, but they range from serious musical interface explorations, to rainbow-colored kids toys, to fart machines, and then to recreations of iconic synthesizers of the past. Something for everyone? Certainly more interesting than Dexed-in-a-box!

There is no guarantee of quality or of suitability for purpose. On some of them, pitch bend won’t work because the bot or person doing the coding just didn’t get around to it. On others, there will be USB problems. Some have audio glitches, which is a serious issue for a sound-making machine. It’s hard to judge the signal-to-noise ratio of the software output for this device (pun intended); it’s the wild west. And at the rate that applications are piling in, you can only hope to review a snapshot anyway.

If you want a guided tour of some of the best applications as of last week, we love [AudioPilz]’s Tier List, embedded below, that also comes with a heavy dose of synth-nerd inside jokes. [Floyd Steinberg]’s video is full of thoughtful commentary on the state of the art.

Plot Twist: Open Source!

Then the story takes a cool turn. M-vave, the company that makes the FM-1, decided to open-source its firmware and its entire SDK. Well, kinda. The strangest turn of events is that they opened up everything except the sound engine itself, which they release as a binary blob. Why? Nobody knows. Some have speculated that it’s because it is based on the GPL-licensed Dexed and are covering their tracks, which is possible. But if M-vave went further back than that, and based it exclusively on the Apache 2.0-licensed msfa, then they’re in the clear.

Either way, there is now official open-firmware support for this little gadget, and a growing community of folks writing new software for it. Because of this official support, musicians who have never flashed an Arduino are overwriting their stock bootloaders. For their part, M-vave is selling a lot more FM-1s than it would otherwise. It’s a win all around.

Apocalypse? Now? In this Economy?

If you watch a number of video reviews of the FM-1, they range from “Game Changer: The Industry is Doomed!” to “The Only Synth You’ll Ever Need” to “Robot Slop”. We think that’s all a little bit overblown. There have always been awesome open-source projects in the synthesizer space. Mutable Instrument’s [Émilie Gillet] gave us countless amazing open examples, many of which are implemented for the FM-1. Major synth manufacturer Korg flirted around with encouraging users to code their own synthesizers in the Minilogue series. None of the FM-1’s capabilities are new, and not all of it is even musical. As a pure synth, it sounds fine, but it’s nothing to write home about.

But what is interesting about the FM-1 story is the sheer velocity at which things are progressing, the positive manufacturer response to being “hacked”, and the empowerment of a community to write its own oddball sound machines. There is more new firmware coming out for the FM-1 than any one person can hope to keep up with, even though the tooling to do so has never been easier. It’s a microcosm of the creation-overflow that we live in. Will this be seen as the beginning of a new era of custom firmware for commercial devices? Fun times!