Commodore Is Back Selling New C64s, But Should You Buy Them?

It’s hard to argue with nostalgia, but you can toss a bucket of cold facts over it. In the case of the recent rescuing of the Commodore brand from the clutches of relabeling of generic electronics by [Perifractic] of Retro Recipes, we got [The Retro Shack] doing the proverbial bucket dumping in a new video. Basically the question is whether the fresh Commodore 64 offerings by the new-and-improved Commodore are what you really want, or need.

The thing is that over the decades many people have created all the bits that you need to build your own classical C64, or even buy one off-the-shelf, with people like [bwack] having reverse-engineered the various C64 mainboards. These can be populated with drop-in replacements for chips like the SID, VIC-II, CIAs and others that are readily available, along with replica cases and keyboards. If you crave something less bulky and complex, you can run a bare metal C64 emulator like BMC64 on a Raspberry Pi, or just run the VICE emulator on your platform of choice. There’re also options like the full-sized TheC64 and Ultimate 64 Elite II systems that you can buy ready to go.

Basically, there is a whole gamut of ways to get some part of the C64 experience, ranging from emulator-only to a full hardware DIY or pre-assembled format. Each of which come with their own price tag, starting at $0 for running VICE on your existing system. With so much choice we can only hope that the renewed Commodore company will become something more than Yet Another C64 Experience.

Continue reading “Commodore Is Back Selling New C64s, But Should You Buy Them?”

Meccano model of a Brennan's monorail

A Second Chance For The Single Wheel Monorail?

Lately, this peculiar little single wheel monorail came to our attention. Built by [extraglide1976], all from Meccano. His build started with modest tests: one gyro obviously flopped. Two gyros geared together ran slightly better. But when he adds active gimbal control, things suddenly come to life – the model shudders, catches itself, and carries on. The final green-roofed locomotive, with LEDs signalling ‘system go’, trundles smoothly along a single rail on [extraglide1976]’s deck.

To be fair, it houses a lot of mechanics and engineering which we don’t find in the monorails of today. We do have quite a few monorails in our world, but none of them balance on a single wheel like this one. So, where did this invention derail?

Outside of theme parks, Japan is one of the few countries where monorails are still used as serious urban transport: though Germany’s century-old Wuppertal Schwebebahn, the lesser-known C-Bahn, China’s sprawling Chongqing and Shanghai systems, Malaysia’s Kuala Lumpur line, Brazil’s São Paulo network, the US links in Seattle and Las Vegas, and India’s Mumbai Monorail prove the idea has quietly taken root elsewhere.

The thing you’ll see in nearly all these monorails is how the carriages are designed to clamp onto the tracks. This is of course the most safe option, but it loses out on speed to the ones that sit on top of the tracks, balancing on one wheel. Such a train was actually invented, in 1910, by Louis Brennan. His original monorail promised faster, cheaper transport, even using existing rails. The carriages leaned into turns like a motorbike, without any intervention from the driver. Two counter-rotating gyroscopes kept the carriage upright, cancelling precession forces like a mechanical Jedi trick.

Back then, it failed commercially, but today? With cheap sensors, brushless motors, and microcontrollers, and intelligent software, why  not let it make a comeback? It could carry freight through narrow urban tunnels. With high-speed single-rail pods?

Investors killed Brennan’s idea, but we live in a different time now. You could start out with a gimmicky ‘snacks and beer’ highline from your fridge to your garage. Share your take on it in the comments!

Continue reading “A Second Chance For The Single Wheel Monorail?”

From Smartphone To A Home Server

Some people like their homelabs to be as big and fancy as possible, with racks of new or surplus server hardware sucking down power. [Hardware Haven] evidently has the opposite idea, given he just made a video about making the cheapest, smallest server possible: an Android phone.

Sure, it’s not going to be streaming terabytes of data at multiple gigabytes per second, but that’s not everyone’s use case. Don’t forget, flagship phones had multiple cores and gigabytes of RAM a decade ago, so even an old and busted smartphone has more than enough power for something like Home Assistant, which is what gets installed in this video.

After considering loading termux and rooting his device for Docker-on-Android, he opted for postmarketOS, the premiere Linux for old smartphones. That’s not because the Linux environment you get with termux wouldn’t work; it’s just that he wanted something native. To that end, he bought a somewhat worse-for-wear Xiaomi Mi A1 from eBay to get hardware Alpine-based postmarket could use.

Software wise, it was just a matter of following instructions and reading manuals — Linux is Linux, after all. The firewall proved to be his main challenge, though trying to branch out from Home Assistant to run Minecraft Server did run into Java issues [Hardware Haven] had no interest in troubleshooting. Hardware wise, though, well — do you want to leave a phone plugged in permanently? Smokey the Bear suggests you not, especially if you live near a forest. Besides, you probably don’t want your server on WiFi, and at least this smartphone wouldn’t charge when using a networking dongle.

That meant phone surgery: the battery came out, and 5 V from an old USB charger was piped into the battery charge controller via a diode. The diode was used for its voltage drop, to bring the 5 V supply down to a believable battery voltage — a buck converter might have been better, but you use what you have, and the diode drop doesn’t dissipate much power. Power dissipation is still one watt at idle, six during a stress test.

Given how cheap the phone was, and how little power this thing sips, [Hardware Heaven] has an excellent answer to those who say homelabbing is a rich person’s hobby. This project also reminds us that while our phones might not be as hackable as we’d like, they’re still far from totally locked down. You can even run NixOS on (some of) them.

Continue reading “From Smartphone To A Home Server”

MorPhlex: The TPU Filament That Goes Soft After You Print It

In FDM 3D printing cycles TPU is a bit of a special filament. Not so much because of its properties, but because it’s rather stretchy even as a filament, which makes especially printing certain hardness grades of TPU into somewhat of an nightmare. An interesting new contender here comes from a company called BIQU, who reckon that their ‘MorPhlex’ TPU solves many of those problems. Recently the [ModBot] channel on YouTube got sent a spool of the filament for testing.

The BIQU MorPhlex TPU filament being turned into squishy slippers. (Credit: ModBot, YouTube)
The BIQU MorPhlex TPU filament being turned into squishy slippers. (Credit: ModBot, YouTube)

The ‘magic’ here is that this TPU claims to be a 90A TPU grade while on the spool, but after printing it becomes 75A, meaning a lot softer and squishier. Perhaps unsurprisingly, a big selling point on their product page is that you can print squishy shoes with it. Beyond this is claims to be compatible with ‘most FDM printers’, and the listed printing parameters are typical for TPU in terms of extruder and bed temperature.

After drying the filament as recommended for TPU in general, test prints were printed on a Bambu Lab H2D. Here BIQU recommends not using the AMS, but rather the dedicated TPU feeding channel. For the test prints some slippers were printed over the course of two days. In hindsight glue stick should have been applied to make parts removal easier.

The slippers were indeed squishy, but the real test came in the form of a Shore A hardness meter and some test cube prints. This showed an 80 – 85A for the BIQU MorPhlex test cube depending on whether to test the side or top. As the product datasheet indicates a final hardness of 75A +/- 3A, one could argue that it’s kind-of in spec, but it mostly raises questions on how parameters like temperature and extrusion speed affect the final result.

2025 One Hertz Challenge: STM32 Blinks In Under 50 Bytes

Many of us have run a Blink program on a microcontroller before. It’s effectively the “Hello, World!” of the embedded space. However, few of us have ever thought about optimizing our Blink code to be as miniscule as possible. But that’s precisely what [Rudra Lad] did for this entry into the 2025 One Hertz Challenge!

This example of Blink, delay_blinky_13, is built specifically for the STM32F4 Discovery microcontroller development board. [Rudra] notes the code is “highly optimized” and compiles down to a binary size of under 50 bytes. The code doesn’t even use RAM, and it aims to get the blink as close to 1 Hz as possible. Many optimizations were used to crunch it down as small as possible. For example, the standard startup code isn’t used, with the entire program instead written in the Reset_Handler to save space. Bit-band is also used to write to peripheral registers to blink the LED, since this uses less instructions than the typical methods. Meanwhile, with many tweaks to the delay counting routine, [Rudra] was eventually able to get the blink frequency to 1.00019 Hz, as measured on a logic analyzer. That’s pretty darn close!

While it’s rare that you have only 50 bytes of binary space to blink an LED, work like this is a great way to flex your coding muscles. Code is on Github for the curious, and if you’ve worked up your own impressive tiny binaries, don’t hesitate to let us know!

The Nibbler Was Quite A Scamp

The late 1970s were an interesting time for microcomputers. The rousing success of things like the 8080, the Z80, the 6800, and the 6502 made everyone wanted a piece of the action. National Semiconductor produced its SC/MP. That was technically the Simple Cost-effective Micro Processor, but it was commonly known as Scamp. There were several low-cost development boards built around this processor and [Hello World] is looking at Digikey’s “Nibbler” which was a fairly nice computer for only $150. Check it out in the video below.

The SC/MP was made to be cheap. It had a strange bank switching scheme reminiscent of the Microchip PIC 16F family. It also had, like a lot of old discrete computers, a serial ALU, which made it slower than many of its contemporaries. It did have good features, though. It was cheap and required very few extra parts along with a single 5 V supply in the second and subsequent versions. In addition, it had pins that were made for connecting more than one CPU, which was quite a feat for those days.

Continue reading “The Nibbler Was Quite A Scamp”

Metric, Imperial, And Flexibility

Al Williams wrote up a seemingly innocent piece on a couple of rules-of-thumb to go between metric and US traditional units, and the comment section went wild! Nothing seems to rile up the Hackaday comment section like the choice of what base to use for your unit system. I mean, an idealized version of probably an ancient Egyptian’s foot versus a fraction of the not-quite-right distance from the North Pole to the equator as it passes through Paris? Six of one, half a dozen the other, as far as I’m concerned. Both are arbitrary.

What’s fun, though, is how many of us need to know both systems and how schizophrenic it all can be. My favorite example is PCB layout, where tenths and thousandths of an inch are unavoidable in through-hole and surface-mount parts, yet we call out board sizes and drill bits in millimeters – on the same object, and without batting an eye. American 3D printer enthusiasts will know their M3 hardware, and probably even how much a kilogram weighs, because that’s what you buy spools of filament in. Oddly enough, though I live in Europe, I have 3/4” thread on my garden hose and a 29” monitor on my desk. Americans buy two liter bottles of soda without thinking twice.

The absolute kings of this are in the UK, where the distance between cities is measured in miles, but the dimensions of an apartment in meters. They’ll buy gas in liters and beer in pints. Humans are measured both in feet-and-inches and centimeters, and weighed in pounds, kilograms, or even stone.

And I think that’s just fine. Once you give up on the rightness of either system, they both have their pros and cons. Millimeters are superb for doing carpentry in – that’s just about how tight my tolerances are with hand tools anyway, and if it’s made of wood, you can fudge 0.5 mm either way pretty easily. Sure, you could measure in 32nds of an inch, but have you ever bought a plywood sheet that’s 1536 x 3072 thirty-seconds? (That’s 4’ x 8’, or 1200 mm x 2400 mm.) No, you haven’t.

But maybe stick to one system when lives or critical systems are on the line. Or at least be very careful to call out your units. While it’s annoying to spec the wrong SMT part size because KiCAD calls some of them out in millimeters and inches – 0402 in inches is tiny, but 0402 in metric is microscopic – it’s another thing entirely to load up half as much fuel as you need for a commercial airline flight because of metric vs imperial tons. There’s a limit to how units-flexible you want to be.