PI4ZLB

If you’ve got a cheap ham rig, it might not be very practical for you to receive certain transmissions out of the box. However, if you were to hack in a convenient little beat frequency oscillator (BFO) to your rig, then you’d be up and running. Here’s a simple way to do just that with a venerable old part everybody knows and loves.

The build in question concerns the use of a 555 timer IC. It’s seasoned with the right smattering of resistors and capacitors to taste, producing a 455 kHz beat frequency oscillator. This can be injected into the intermediate frequency chain of a receiver, making up for the lack of a steady carrier wave when receiving continuous-wave and single side-band suppressed carrier transmissions. Thanks to a potentiometer in the circuit, it’s tunable, too, from 455 kHz, plus or minus twenty percent or so. Thanks to the versatility of the 555, it’s possible to run the chip on a wide voltage range, anywhere from 4.5 volts to 16 volts, which makes it easy to install in just about any old radio set without requiring adding a specialized power supply. There’s also an alternative design that EDN covered in greater detail some time ago.

If you’re eager to dive into a wider range of transmissions than your radio can currently receive, this old-school ham hack could be just what the shack ordered. We feature plenty of good ham hacks around these parts, and don’t forget—we always want to hear about the freshest ones on the tipsline.

When building a radio transmitter, unless it’s a very small one indeed, there’s a need for an amplifier before the antenna. This is usually referred to as the power amplifier, or PA. How big your PA is depends on your idea of power, but at the lower end of the power scale a PA can be quite modest. QRP, as lowe power radio is referred to, has a transmit power in the miliwatts or single figure watts. [Guido] is here with a QRP PA that delivers about a watt from 1 to 30 MHz, is made from readily available parts, and costs very little.

Inspired by a circuit from [Harry Lythall], the prototype is built on a piece of stripboard. It’s getting away with using those cheap transistors without heatsinking because it’s a class C design. In other words, it’s in no way linear; instead it’s efficient, but creates harmonics and can’t be used for all modes of transmission. This PA will need a low-pass filter to avoid spraying the airwaves with spurious emissions, and on the bands it’s designed for, is for CW, or Morse, only.

We like it though, as it’s proof that building radios can still be done without a large bank balance. Meanwhile if the world of QRP interests you, it’s something we have explored in the past.

[Yeckel] recently put the finishing touches on an ambitious implementation of a simple D-STAR (Digital Smart Technologies for Amateur Radio) transceiver using some very accessible and affordable hardware. The project is D-StarBeacon, and [Yeckel] shows it working on a LilyGO TTGO T-Beam, an ESP32-based development board that includes a SX1278 radio module and GPS receiver. It even serves a web interface for easy configuration.

What is D-STAR? It’s a protocol used by radio operators for voice that also allows transmitting low-speed data, such as short text messages or GPS coordinates. While voice is out of scope for [Yeckel]’s project (more on that in a moment) it can do all the rest, including send images. That makes beacon-type functions possible on inexpensive hardware, instead of requiring a full-blown radio.

As mentioned, voice is a big part of D-STAR. While [Yeckel] was able to access the voice data, attempts to decode it were unsuccessful. A valiant effort, but we suppose voice decoding isn’t terribly relevant to beacon-type operations like transmitting APRS (Automatic Packet Reporting System).

So far as [Yeckel] is aware, D-StarBeacon is currently the only open-source implementation of a D-STAR radio available on the internet, which is pretty interesting. We’ve seen projects that touch indirectly on D-STAR, but nothing like this.

Watch it go through its paces in the video embedded below. Since the T-Beam is just a microcontroller development board, the user interface comes from an Android app on a mobile phone, which is why you see a phone in the video.

Antenna design is often referred to as a black art or witchcraft, even by those experienced in the space. To that end, [Janne] wondered—could years of honed skill be replaced by bruteforcing the problem with the aid of some GPUs? Iterative experiments ensued.

[Janne]’s experience in antenna design was virtually non-existent prior to starting, having a VNA on hand but no other knowledge of the craft. Formerly, this was worked around by simply copying vendor reference designs when putting antennas on PCBs. However, knowing that sometimes a need for something specific arises, they wanted a tool that could help in these regards.

The root of the project came from a research paper using an FDTD tool running on GPUs to inversely design photonic nanostructures. Since light is just another form of radio frequency energy, [Janne] realized this could be tweaked into service as an RF antenna design tool. The core simulation engine of the FDTD tool, along with its gradient solver, were hammered into working as an antenna simulator, with [Janne] using LLMs to also tack on a validation system using openEMS, an open-source electromagnetic field solver. The aim was to ensure the results had some validity to real-world physics, particularly important given [Janne] left most of the coding up to large language models. A reward function development system was then implemented to create antenna designs, rank them on fitness, and then iterate further.

The designs produced by this arcane system are… a little odd, and perhaps not what a human might have created. They also didn’t particularly impress in the performance stakes when [Janne] produced a few on real PCBs. However, they do more-or-less line up with their predicted modelled performance, which was promising. Code is on Github if you want to dive into experimenting yourself. Experienced hands may like to explore the nitty gritty details to see if the LLMs got the basics right.

We’ve featured similar “evolutionary” techniques before, including one project that aimed to develop a radio. If you’ve found ways to creatively generate functional hardware from boatloads of mathematics, be sure to let us know on the tipsline!

[GreatScott] has recently been tinkering in the world of radio frequency emissions, going so far as to put their own designs in a proper test chamber to determine whether they meet contemporary standards for noise output. This led them to explore the concept of shielding, and how a bit of well-placed metal can make all the difference in this regard.

The video focuses on three common types of shielding—absorber sheets, shielding tapes, and shielding cabinets. A wide variety of electronic devices use one or more of these types of shielding. [GreatScott] shows off their basic effectiveness by putting various types of shielding in between a noise source and a near-field probe hooked up to a receiver. Just placing a bit of conductive material in between the two can cut down on noise significantly. Then, a software defined radio (SDR) was busted out for some more serious analysis. [GreatScott] shows how Faraday cages (or simple shielding cabinets] can be used to crush down spurious RF outputs to almost nothing, and how his noisy buck-boost designs can be quieted down with the use of the right absorber sheets that deal well with the problematic frequencies in question. The ultimate upshot of the tests is that higher frequencies respond best to conductive shielding that is well enclosed, while lower frequency noise benefits from more absorptive shielding materials with the right permeability for the job.

Shielding design can be a complex topic that you probably won’t master in a ten minute YouTube video, but this content is a great primer if you’re new to the topic. We’ve covered the topic before, too, particularly on how a bit of DIY shielding can really aid a cheap SDR’s performance. Video after the break.