How Hough Transforms Enable Computers To See

Although identifying what we can see with our eyes feels like the most natural thing in the world, the responsible cognitive processes running on our brain’s wetware are quite a marvel. Even when pushed beyond their evolutionary design by e.g. driving a car at high speeds does our vision system mostly manage to keep up. Emulating these cognitive processes with artificial cognition (AC) systems like computer vision required the development of feature extraction algorithms, such as the Hough Transform that’s the topic of this video by [The Synthetic Mind].

The Hough Transform was developed originally by [Paul Hough] in the 1960s for machine analysis of patterns in bubble chamber photographs. From there the basic algorithm has evolved beyond merely detecting the straight lines of particles zipping through said bubble chambers.

Key however remains determining the points in a scene which potentially make up the lines, which requires edge detection. Yet unlike in basic examples, real-life use of these algorithms is made hard by how complex a real-life scene is. Naively checking all possible lines as in the original algorithm would take far too long, which led to the development of optimizations that take considerably less time and deal better with pixel noise.

Of course, after finding all potential lines and borders of objects in a scene the next step for a computer vision is to identify what has been spotted, what it means for the current task and determine an appropriate action. Here getting additional scene information other sensors like radar or Lidar can be incredibly helpful, especially when you’re the system in control of something like a car.

Examples like these definitely promote an appreciation of how hard it is to create AC algorithms that can emulate what we animals can seem to do almost effortlessly. Even before considering the intelligence subset of cognition, one cannot help but marvel at the sheer effort it takes for us humans to not constantly bump into things.

Continue reading “How Hough Transforms Enable Computers To See” →

Tracking Down A Mystery Beep By Giving A Coding Agent A Few Ears

[Simon Willison] recently used a coding agent in an unusual way. A software system temporarily used the microphones on devices scattered around the room to triangulate the source of a mysterious, intermittent beep coming from within one of the many boxes in the room.

The main part of the system is a Python web server, and the listeners can be any old devices one might have hanging around. Scan a QR code, and the device becomes a listening post by leveraging the Web Audio API. With listeners spread around the room, the system has everything it needs to patiently wait, listen, and zero in on the mystery beep. The culprit? An old carbon monoxide detector, buried in a box and emitting a low battery chirp.

That’s neat, but what this project really demonstrates is the benefit of hacking together a way for a coding agent to actually sense the real world, the better for it to design a solution to a physical problem.

The ad-hoc framework of web-based listeners allowed [Simon] to give the agent the ability to gather audio data on its own to refine and recalibrate its approach during development, without any need for him to record audio and pass it on manually.

It’s a bit reminiscent of this WiFi analyzer connected to an AI model, a project that hints at the possibilities of a physical tool that can be steered by an agent. Check out the GitHub repository for beep-locator if you’d like a closer look at the code itself.

The Mega Tamagotchi Manga Reader

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.

Continue reading “The Mega Tamagotchi Manga Reader” →

Handheld Motor Cancels Out Every Twist And Turn

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.

Continue reading “Handheld Motor Cancels Out Every Twist And Turn” →

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!