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.

Continue reading “Serial: The Port That Won’t Die” →

Starlab Observatory Received Image

Remarkable Observatory Receives Orbital Radio

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 antennas), 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!

We’re Hiring: Come Join Us!

You wake up in the morning, and check Hackaday over breakfast. Then it’s off to work or school, where you’ve already had to explain the Jolly Wrencher to your shoulder-surfing colleagues. And then to a hackspace or back to your home lab, stopping by the skull-and-cross-wrenches while commuting, naturally. You don’t bleed red, but rather #F3BF10. It’s time we talked.

The Hackaday writing crew goes to great lengths to cover all that is interesting to engineers and enthusiasts. We find ourselves stretched a bit thin and it’s time to ask for help. Want to lend a hand while making some extra dough to plow back into your projects? We’re looking for contributors to write a few articles per week and keep the Hackaday flame burning.

Contributors are hired as private contractors and paid for each article. You should have the technical expertise to understand the projects you write about, and a passion for the wide range of topics we feature. You’ll have access to the Hackaday Tips Line, and we count on your judgement to help us find the juicy nuggets that you’d want to share with your hacker friends.

If you’re interested, please email our jobs line (jobs at hackaday dot com) and include:

  • One example article written in the voice of Hackaday. Include a banner image, between 150 and 300 words, the link to the project, and any in-links to related and relevant Hackaday features. We need to know that you can write.
  • Details about your background that make you a valuable addition to the team. What do you like, and what do you do?
  • Links to your blog / project posts / etc. that have been published on the Internet, if any.
  • Or just write us with questions. We’ll be glad to answer.

Ladies and Gentlemen, start your applications!

Local Prusa Connect Cuts Out The Cloud

One of the ways 3D printing has changed over the last few years has come in the form of cloud services that exist alongside your printer. In some cases they are locked-in to using the thing, while in others such as Prusa Connect, they are an adjunct that provides useful services but doesn’t restrict the printer to using it.

Now Prusa have gone a step further in keeping control closer to the owner of the printer, by releasing a local version. You can run it on your own server, giving all the benefits with none of the ties.

All the code can be found in a GitHub repository, under their Open Community Licence, which makes everything available but puts some restrictions on who can use it, for example requiring that large enterprises have a paid version. As well as in code form it’s supplied pre-built for Apple, Windows, and Linux platforms, on different architectures including the Raspberry Pi. Out of the box it supports Prusa printers, but it’s not restricted to them as there is a driver API should you wish to add a non-Prusa model.

We know there’s a reaction to the heavier reliance on the cloud found in for example Bambu Labs printers, and we know that some users may have commercially sensitive parts they may not wish to pass off their own network. So we see this as a clever move from Prusa, offering a more palatable way towards a networked printer service without relying on the vendor.

Thanks [Renze] for the tip.

Header image: US Embassy New Zealand, Public domain.

Not-So-Large Language Model Fits On A Floppy Disk

At some point when hackers start pushing edge cases, nomenclature gets weird, like Large Language Models, or LLMs. At some point, the word “large” obviously becomes impossible to justify, but we’re not going to call [WollyMonjac]’s Tiny2.1 DOS PC Chatbot just a ‘language model’ — perhaps “transformer” is the better term. That’s what LLMs and not-so-L-LMs like this one are under the hood, after all.

In any case, this one was written in Turbo C 2.0 by the no-debate ‘large’ LLM Fable 5.2 and trained by Opus 5.5. So for those of you who’ve got this one on their apocalypse bingo card: yes, machines are making machines. This second-gen transformer targets a 486DX or Pentium processor and runs on DOS, and you can get it onto the machine on a single period-appropriate floppy disk.

The actual network is 380 KB of 8-bit weights, while the rest of the floppy would hold the handy interface. As you might imagine, it needs 540 KB of free memory to run in. The transformer holds 3,500 facts in its 367K-parameter but outside of that it makes stuff up with the reckless abandon that these models can’t escape, regardless of size. 

The project is of course more of a conversation-starter than anything else, though if you want to train it on your own 3,500 facts the scripts for that are on GitHub under an MIT license. We’ve seen an LLM on a 486 before, but being able to easily curate exactly what the model knows raises some interesting possibilities.

Linux In A Browser Tab

Linux was once distributed on CDs and DVDs stuck to the front of computer magazines. Now, technology has advanced to the point where you can simply run a Linux kernel right in your browser. That’s precisely what you get with Unkernel from [pithings].

Unkernel is described as “Linux 7.x built as a single wasm module with an MMU.” Yes, thanks to the magic of WebAssembly, you can run Linux in a browser tab at a decent fraction of native speed. All the proper kernel stuff—like syscalls, the scheduler, memory management, file systems, and networking—is compiled code. User programs are then emulated with a just-in-time compiler, so you can run Ubuntu and Alpine packages without any fuss. You get a shell, package manager, persistent storage, sound, and internet access out of the box. It’s basically a whole Linux computer sitting in a single browser tab for your convenience.

It’s generally not as fast as running the kernel natively, but where you need a little Linux on the go, it should come in clutch. We’ve discussed Linux showing up in weird places quite recently on the Hackaday Podcast, too. If you’re sticking kernels where they’re not expected, be sure to let us know on the tipsline.

Coding On Windows? Redmond May Already Know.

File this one under “shocked, but not that shocked”– hacker [Xusheng Li] did some digging on a recent Windows 11 build and found that it seems to be phoning home with details about not only what AI agents you might be using on your system, but what dev tools are in use too. The full writeup is worth reading before rushing to judgement on this, but no doubt Microsoft has your best interests at heart– they always do, right?

The saga starts with a library called MissionControlAggregator.dll, which contains a list of executable files to look for– things like codex.exe on the agent front, but also dev tools as common as python.exe or gcc.exe–which would be innocent enough, and perhaps even helpful if the OS was watching for these files to do something locally. It might be doing something locally, but [Xusheng] was able to trace the diagnostic that triggers when you launch one of the apps it is listening for, and yes, at least on a default Windows 11 install, it phones home about it. Alas, WSL won’t save you this time, as the same event is apparently generated when you launch the linux version in said subsystem.

Of course the default Windows 11 install does have “optional diagnostics” enabled by default, so you could argue that this is something that the system administrator consented to– provided they knew about it, which they likely don’t. We certainly had no idea that this was part of those “optional diagnostics” and are thankful to [Xusheng] for the tip.

Our own [Jenny List] took Windows 11 for a drive back in June, and emerged rather unimpressed. Your mileage may vary, but if you are, like the majority of the world’s desktop users, on Windows, you might want to double-check those privacy settings.