This has been a very thoughtful, introspective week for me. I had a birthday a few weeks ago and my wife’s birthday was a few days ago. In a couple of months, we’ll celebrate 49 years of marriage. I am, quite simply, amazed…and when I look back in time, there is an awful lot to remember.

But those marker moments are also cause for reflection, and some of my ruminations spilled over into the amateur radio realm. The first piece in this issue of the Random Wire is about where AI is taking our hobby: The Machine Learns to Listen. The second piece is about re-centering the Random Wire and EtherHam, and seeking feedback: The Journal and the Workbench.

As a fun diversion, I wrote up how to use a small ESP32-powered device to mine for Bitcoin: Playing the Bitcoin Lottery at Home. The crossover with amateur radio? Learning about ESP32 devices in general. The ESP32 is everywhere in the maker/IoT world. I’m hoping the Bitcoin article will give hams a friendly on-ramp through something as immediately tangible as “plug it in and it does a thing.” Bitcoin lottery mining is probably the most motivating possible introduction to the platform — much more fun than blinking an LED. I expect to be learning, and sharing, about the ESP32 platform in future issues.

I also did some Python coding to pull recent topics from a variety of Groups.io conversations into a one-page summary: Groups.io Digest with Python. I already learned something new from making it easier to harvest this information.

Yesterday, I went looking for a traffic reporter for YSF/C4FM/WiRES-X, and that took me to a place of realization I didn’t quite expect. The full piece is on EtherHam at Walled Gardens and Unlabeled Mazes: Why C4FM Users Can’t Find Each Other.

And I fiddled with some radios and added a fan to a Raspberry Pi 4-based AllStar node. Nothing special, but certainly enjoyable. Lots of projects on the bench to work on, including an Arduino Uno Q board — I’m really looking forward to playing with this platform. It has 4 GB of RAM and 32 GB of eMMC storage for just $59. Fingers crossed.

The bench didn’t slow down just because I was feeling reflective. Let’s dive into the Random Wire topics for this week!

A Thank You Long Overdue

Some tools become so woven into how you operate that you stop noticing them. APRS is like that for me. The little icons moving across a map, a beacon confirming a friend made it over the pass, a weather object appearing before the storm does — it’s just part of the fabric of how I think about being on the air. My Yaesu FTM-300DR radio in the pickup truck runs APRS automatically.

None of that would exist without Bob Bruninga, WB4APR (SK).

APRS traces back to 1982, when Bruninga wrote his first data map program to plot the positions of U.S. Navy ships on an Apple II computer. A few years later he was running packet communications on a VIC-20 and C-64 to support an endurance race. By 1988 the program had moved to the IBM PC, and in 1992 it got the name we know: APRS. He kept pushing it — not just as a position reporting system but as a live tactical picture of whatever a community of operators needed to share.

Bob was a retired U.S. Naval Academy senior research engineer who never seemed to retire from the work that mattered. He founded the Appalachian Trail Golden Packet event, fielding APRS nodes from Stone Mountain in Georgia all the way to Mount Katahdin in Maine every July. He wrote. He answered questions. He kept the vision alive long after he could have handed it off and walked away.

Bob passed away on February 7, 2022, at age 73, after a battle with cancer complicated by COVID-19. His key is silent now. The network he built is not.

I’m lucky to know someone who carries that tradition forward locally. Herb, KB7UVC, is one of those hams who has forgotten more about APRS than most of us will ever learn — and who will actually sit down with you and work through a problem until it makes sense.

So: thank you, Bob. Thank you, Herb. APRS may mean “automatic” but I know the work to build and support APRS has been anything but.

This “thank you” section is a weekly feature to share my gratitude and appreciation for radio amateurs that have helped make my journey more enjoyable.

The Machine Learns to Listen

Those of us who came up turning dials have watched amateur radio change beneath our hands. The rigs got quieter, then smarter, then started doing things we couldn’t do ourselves. I’ve been thinking about that arc lately — from the glow of a tube radio warming up, to FT8 pulling signals out of noise I couldn’t hear, to what comes next.

Because something is coming next. Machine learning is already reshaping weak-signal decoding and interference rejection. Further out are transceivers that model your RF environment and learn your operating patterns over time — not radios that operate themselves, but genuinely intelligent partners. The hardware headroom already exists. This is a software problem now.

I wrote a longer piece about all of this over at EtherHam — where the arc came from, where it appears to be going, and what I think the real question is for our hobby as AI starts showing up in high-end rigs. If you’ve ever felt the particular unease of watching a machine exceed your capabilities, or wondered whether the vintage operators and the SDR experimenters are in conflict or in conversation, I think you’ll find it worth the read. See: The Machine Learns to Listen.

Exciting News: M17 Audio Over RF

Jeff AE5ME posted this YouTube video early this week about using Greg W5GGW’s M17 app on iOS with a Mobilnkd TNC4 to send M17 audio over RF, and to receive it in the app from an RF signal. This is a great moment for M17!

This nine-minute video describes and demonstrates how to configure the M17 app and the TNC4 to send and receive over-the-air M17 audio.

Jeff’s video was also picked up by the M17 Project.

The Journal and the Workbench

I started writing the Random Wire because I wanted to capture what I was doing so I didn’t have to relearn it later. I had been keeping project notes and a radio friend suggested I publish what I was working on because “other hams are having the same problems.” So I did, and I named this journal of my amateur radio explorations the Random Wire newsletter.

As time went on, the articles got longer and more detailed. Deep dives with plenty of workbench-level detail. Some of them amount to A-to-Z how-to guides. At some point I realized I was writing two different kinds of things: a journal of what I was experiencing, and a workbench record of what I actually did and learned. That’s when EtherHam was born.

The Random Wire is the journal. EtherHam is the workbench.

Everything published on both platforms comes from direct personal experience. I built it, or it broke and I fixed it, or I tried something and it didn’t work the way I expected. The knowledge sitting in my head does nobody any good if I don’t share it — and whatever problem I just solved, someone else has already hit that same wall, probably at 11pm with their soldering iron in hand.

This split in style is not a true dichotomy because the two often overlap. You can’t really separate what you are experiencing from what you are doing. But they come at the same territory from different directions, and I think of them as a complementary pairing rather than competing platforms.

Along the way, I added sections to the Random Wire — band conditions, radio history, a digital news digest — that felt like things a newsletter should have rather than things that naturally belonged here. Good content, wrong home. I’m moving those sections to EtherHam where focused reference material belongs, and the Random Wire goes back to being what it started as: a craftsman’s journal, written at the end of a week at the workbench.

I wish I knew more precisely how subscribers and readers perceive these two platforms. The available metrics are genuinely useless unless you think total subscribers or page hits tell you something meaningful. I don’t. What matters to me is hearing from you that something I wrote was useful, or saved you an evening of frustration, or pointed you somewhere worth going. That’s the whole measure of success here.

So here’s what I’d genuinely like to know: when something I’ve written has been useful to you, what kind of article was it? A build walkthrough? A troubleshooting story? A short take on something new? Tell me in the comments or drop me a note. That feedback helps shape what lands on the workbench next.

Leave a comment

TIDRADIO TD-H9: More

Since I’ve always had good luck with programming software and cables from RT Systems, I ordered their programmer and special cable for the TIDRADIO TD-H9. I have two TD-H9 radios. One will probably be largely devoted to APRS work. The other will be for general analog use. Being able to program them both with one program and one cable will be efficient.

The RT Systems package arrived and I loaded up the programmer on my old ToughBook. However, I was taken aback by the sparseness of the programming interface. I had hoped to be able to configure other aspects of the radio, such as APRS beaconing, through the programmer. I’m not seeing where to accomplish that from within the RT Systems software. This means that to get the radio working correctly for you, you’ll still need to dive into the radio menus through the front keypad.

It’s easy to enter a frequency, specify whether it is simplex or a repeater frequency with an offset, and set the power level. That is truly more convenient than wading through the menus in the radio. But if you want to enable GPS, turn APRS on or off, and enable beaconing, you’re stuck doing that directly on the radio.

I don’t regret buying the RT Systems package for the TIDRADIO TD-H9 radio. It works brilliantly for what it is. But I wish it did more than just the basics of frequencies, channels, offsets, and power level.

Groups.io Digest with Python

I monitor a lot of Groups.io mailing lists — ARDC, PNW DMR, LinuxHam, TinySA, and a bunch of others — and I got tired of checking them one at a time. So I built a Python script that does it for me. When I want to catch up, it hits the Groups.io API, pulls recent activity from every group on my list, and generates a digest report that opens in my browser with everything ranked by activity and every thread title linked directly to the discussion. It took longer to figure out the API quirks than to write the script, but the result is exactly what I wanted.

The script is free, requires no external Python libraries, and runs on Windows, macOS, and Linux. I wrote it up in detail on EtherHam — including how to handle subgroups, restricted groups, and scheduling it to run automatically every morning. Grab it at etherham.com or directly from the EtherHamRadio GitHub repo (and thank you to the subscribers who urged me to set up a GitHub space for code like this).

Listening to W6EK on Baofeng UV-5R Mini

While grinding up my wife’s morning meds, I grabbed the Baofeng UV-5R Mini transceiver to listen to traffic on the W6EK repeater. I never thought I’d say that I like a Baofeng radio…but I do like this one. It sounds fine, it slips easily into a pocket, and is just a very convenient package to use:

BAOFENG UV-5R Mini Ham Radio Long Range Handheld Two Way Radio, Bluetooth APP Programming Walkie Talkies 2 Pack, 999CH One-Key Copy Frequency, NOAA Weather, USB-C Charging, Dual-Band, Green (affiliate link)

I added a stubby antenna to make it even more convenient at home:

ABBREE Ham Radio Antenna Dual Band VHF/UHF 144/430Mhz 1.96inch AR-805S SMA- Female Long Range Stubby Short Antenna for Baofeng UV-5R Mini 5RM BF-F8HP PRO, K5 Plus, DM32, UV32 Radio Accessories, 2 Pack (affiliate link)

In this photo, the radio is sitting on the kitchen stove while I listen to the W6EK repeater through my AllScan ANF101 node that is transmitting to the Baofeng.

Later, while finishing this section, I listened to ASL node 516221 which carries ISS radio traffic, passing through my local ASL node 588418.

I shared my first impressions of the tiny UV-5R Mini back in February. I continue to be surprised at how much I like this little transceiver.

B.B. Link Adapter: Last Chance

If you use an iPhone or iPad and have a Kenwood TH-D74 or D75A transceiver, this alert may be for you. Georges WH6AZ reached out to me last week with an aloha and a note about the last stock of his B.B. Link adapter.

Meet B.B. Link, the adapter that allows iPhones and iPads to connect to Kenwood TH-D75 and D74 radios via Bluetooth. iOS devices, which are limited to Bluetooth Low Energy (BLE), can’t pair natively with these radios. With this adapter, iOS applications like RadioMail can access the radio’s built-in KISS TNC packet modem for off-grid communication. Simply plug the adapter into a USB-C port for power, turn your radio on, and you’re set.

Georges authored Transceive, an AllStar app I use on my iMac. Transceive received a rare Random Wire Recommended sticker from me. I like Transceive.

His B.B. Link product is reaching the end of its production run and he does not plan another run. He writes:

Nearly two years ago, I introduced the B.B. Link, an adapter that allowed apps like RadioMail, Packet Commander, and now Radio Messenger to use the built-in packet TNC of the Kenwood TH-D74 and TH-D75 radios. At the time, iPhone-friendly ham radio interfaces were scarce, and B.B. Link filled a real need.

The landscape has evolved. We now have capable audio adapter options such as the Digirig Lite and AIOC, which let software modems interface over audio directly. We also have reasonably priced HT radios like the UV-PRO and VG-N76 that expose their TNCs over BLE.

I hope radio manufacturers continue this trend and ensure future hardware exposes a TNC, or at least a Bluetooth or Wi-Fi–accessible audio interface, so more people can participate with less friction.

I never set out to become a hardware maker. I built the first prototype for myself and hoped I might sell the initial batch of 100 to recoup my cost. Demand far exceeded that, and I’ve been humbled by the reception.

But B.B. Link has always been a handcrafted project. Managing supply chain challenges, tariffs, assembly, testing, order fulfillment, and support has been meaningful work, but also time consuming. It’s time for me to reclaim that bandwidth and focus fully on software development, where I can deliver the most impact for the community.

With that in mind, B.B. Link availability will end once the current batch sells out. I expect most who want one already have it, but if you need a spare (or know someone who would) now is the moment.

The firmware remains open source for anyone who wants to build their own DIY version.

If you use an iPhone or iPad and have a Kenwood TH-D74/D75 radio platform, this is a “last chance” notice to get a useful tool that eases access to the TNC in those radios. I do have a TH-D74A so this notice applies to me, too!

Playing the Bitcoin Lottery at Home

A friend of mine has been running a tiny Bitcoin miner on her home network for the better part of a year. She knows — with complete mathematical certainty — that she is almost certainly never going to find a block. She does it anyway. “It’s the cheapest lottery ticket I’ve ever bought,” she told me, “and it never expires.” That was enough to get me curious.

The device is called a NerdMiner — an ESP32 microcontroller running open-source firmware called NMMiner — available on Amazon for around $22. It draws a fraction of a watt, connects to your WiFi, and quietly submits hashes to a solo Bitcoin mining pool around the clock. Your odds of finding a block are approximately those of winning the Powerball. But the hardware costs less than a tank of gas and runs indefinitely on any USB charger, so the ongoing cost is a few cents a day.

Setting one up is more involved than plugging it in — the shipped firmware is out of date, there’s a specific pool configuration that actually works for low-powered devices, and there’s one bootloader quirk that will stop you cold if you don’t know about it. I’ve written up the complete walkthrough, including the COM port gotcha that would have saved me time if I’d known it going in.

If the idea of a perpetual lottery ticket running quietly on your shelf sounds like your kind of thing, the full article is at EtherHam.com.

Added a Fan to the RPi4 AllStar Node

My AllStar node 588410, built on a Raspberry Pi 4 platform with an uninterruptible power supply (UPS) hat, was running rather warm. Not the 80°C temperature where the SoC (system on a chip) begins to self-throttle, but much warmer than I liked.

I bought a very inexpensive 30mm fan from Pi-Shop that was made to fit my tall RPi4 case. It fit perfectly. Even though it is a 5-volt fan, I powered it from a 3.3V GPIO pin on the hat. Why? Because the fan runs slower at 3.3V, and slower means quieter. It is running silently and doing a good job of bringing the 60°C temps down to the mid 40°C range: quite acceptable.

I’m happy with this small addition to the package. Node 588410 now has the RPi4 and UPS and cooling fan inside a single case.

During this journey, I learned of a useful alternative to the Enhanced Parrot node 55553, and that is AllStar node 2002. I knew this but had forgotten it until I read this in the SHARI Groups.io group: “…call Allstarlink node 2002, which is a parrot that has a built-in IAX ping diagnostic. If after you connect, it comes back and says ‘your node is unreachable’, then either your port is not forwarded correctly, or something upstream is blocking incoming packets to that port, i.e., CG-NAT.” Node 2002 provides useful information, whether you are testing the accessibility of your node or just checking your transmitted audio volume.

Walled Gardens and Unlabeled Mazes: Why C4FM Users Can’t Find Each Other

If you’ve ever keyed up on a WiRES-X room and heard nothing but silence, you’re not alone — and you’re not doing anything wrong. The problem isn’t your radio or your node. It’s that the C4FM ecosystem was never built to help you find where the conversation is happening. This week on EtherHam I went looking for the monitoring tools that should exist for YSF and WiRES-X users — the kind DMR and AllStarLink operators take for granted — and what I found was a more interesting story than I expected.

It turns out open protocols don’t automatically produce open, navigable ecosystems. Somebody still has to build the town square. WiRES-X and YSF aren’t just two names for the same thing — they’re two fundamentally different systems with different governance, different infrastructure, and different reasons why the tools that would make them navigable never got built. One is a classic corporate walled garden. The other is something stranger: an open protocol that the community never quite organized around…but still could.

The full piece is on EtherHam. It gets into why this happened, what partial solutions exist, and whether it’s fixable. Spoiler: one side of that answer is more hopeful than the other.

Weekly Reports Moved to EtherHam

I’ve moved the Band Conditions, Digital Radio News, and Groups.io Digest reports to the EtherHam website. This week’s post is Weekly Report: June 11, 2026.

I’ll use the same header image as shown here for each weekly report. That will make it easier to key in on this regular informational feature. In general, I run my routines once a week, on Thursday, for publication by Friday morning.

Short Stack

APRS

• LightAPRS Gateway 1.0: A Standalone APRS Digipeater and iGate in a Small Box — $130 for a standalone digi and igate!

• Build a Low-Power APRS Station with Raspberry Pi Zero 2 W — “Building a low-power APRS station using a Raspberry Pi Zero 2 W…a comprehensive guide on setting up Graywolf on Tixie OS Lite, allowing you to operate a compact and efficient APRS station or digipeater.”

• Radio Messenger Is What Ham Radio Chat Should Have Been All Along — “Radio Messenger is a new iPhone and iPad app that…takes the underlying technology of APRS – the same open amateur radio protocol that’s been quietly running on VHF frequencies worldwide – and wraps it in a messaging interface that looks and feels like a chat app.”

• APRSdroid NA7Q Edition: The Most Feature-Rich APRS Client for Android — “While the official APRSdroid project remains a popular choice, the NA7Q Edition takes the application significantly further.”

Shortwave

• Tecsun PL-520: An Excellent Upgrade — I don’t find this nicely reviewed radio in stock on Amazon. Apparently, “stock fluctuates.”

Windows

• This 20-year-old Windows tool fixed my dead PC when nothing else would — I’d forgotten about Hiren’s, but I’ve used it in the past few years. When I look through my collection of saved USB sticks, I see one labeled: Hiren’s. “If you’re an oldhead like me, you probably know all about Hiren’s BootCD, but it’s one of the most useful tools anyone can have handy.”

AI

• I’ve tested so many desktop AI tools, but Hermes with Ollama is my new favorite – here’s why — “Local AI is the way to go, and Hermes with open-source Ollama is my preferred setup right now.”

Support

Occasionally, I remind subscribers that supporting the Random Wire and EtherHam is very helpful. There are many ways to give support as described on the Support EtherHam page, should you choose to do so.

I’ve been trying to add a summer hat in time for Field Day but my EtherHam store is rejecting the custom embroidery for some reason. Looks like a nicely ventilated booney hat will have to wait until I get that sorted out.

As I noted several issues back, the location of the EtherHam logo on the Champion sweatshirt was not quite right. I adjusted it and the new location looks better.

Thank you to all who support the Random Wire and EtherHam. Support doesn’t mean you contributed money — it also means you subscribe and read and comment from time to time.

And who are EtherHams? We are. Since we all use computers in some aspect of our amateur radio activities, I think we are all EtherHams.

Home

I found a box of old compact discs in the closet. It’s a box of memories, really, of the many great times my wife and I shared with music. She was a music educator her entire working life, so music was ever-present in our lives. For many years, I also functioned as her roadie, setting up music concerts, repairing band instruments, and fixing amplifiers and wires. Those are great memories, both of helping my wife and of all of her great students.

Many of the CDs are so old they don’t have metadata encoded on the disc. When I rip the music to my network storage, it often shows up as Unknown Artist and Track 1, Track 2 instead of names, and doesn’t show any cover art.

To fix this, I started using Mp3tag to edit the metadata for tracks I’m saving on the new network-attached storage box. This is a bit time consuming, but it also lets me dwell a bit on the songs. (Lots and lots of memories!) After editing the metadata, I open the album in MusicBee and ask it to find the cover art…and it usually does. Then I re-scan my music folder on the NAS to add the album and named tracks to my music library.

But then I discovered a shortcut — I found I can rip CDs directly into MusicBee. The app does a good job of finding metadata and album cover art as part of that process. I rip the CD to my laptop, then copy the entire folder to my NAS drive and tell OwnTone to rescan my music library. Very easy.

Music really does touch the soul. When I listen to these songs, I’m remembering where we were, what we were talking about, how we were feeling. What’s more important is that these old songs evoke memories and emotions in my wife, despite her cognitive challenges. It’s truly amazing and I’m happy to help her experience such moments.

Right now? We’re listening to a two-disc collection of Tom Jones greatest hits. There are a ton of memories embedded in those tunes!

73, and remember to touch a radio every day!

00 QRV: Are You Ready?

Welcome to Random Wire 185.

On the amateur radio side, I’m very pleased to share a positive outcome after a month of trying to get APRS beaconing working reliably on my TIDRADIO TD-H9 handheld transceiver. As is often the case with stubborn problems, the solution ended up being a simple on-off setting, but finding that took extensive trial-and-error testing. It’s a small thing that felt like a very big thing when I finally cracked it

On the technology side, I’m also happy to share my new network-attached storage (NAS) solution using a Beelink ME Mini PC. It’s affordable, quick, and should be reliable. This project is well within reach of anyone who runs Linux on a computer, and it’s a great learning opportunity if you’re just getting started.

Find links to these below in the New on EtherHam section.

01 Thank You…America’s Kansas City Wide Network

This week’s thank-you goes to the team behind America’s Kansas City Wide Network — one of the most reliably busy watering holes on the digital amateur radio scene. Dedicated volunteers keep the lights on, and a very active group of regulars keeps it from ever getting too quiet.

I tune in when I travel. There’s a Portland repeater on the network, which means I can monitor and participate whenever I’m in range — a small thing that makes a long drive considerably more interesting. What I especially appreciate is that KCWide hasn’t stood pat. They’ve linked an M17 instance, extending a warm welcome to the new kid on the block. That kind of openness matters.

If you haven’t found your way to KCWide yet, consider this your invitation. Thank you to everyone who keeps it going.

02 New on EtherHam

It was a very satisfying week with several big wins.

The TIDRADIO TD-H9: A $70 APRS Radio Worth the Effort

The TIDRADIO TD-H9 offers 10 watts, VHF/UHF, AM airband, a built-in TNC, GPS, APRS, Bluetooth, and a spectrum analyzer for around $70. The hardware delivers on that promise. Getting APRS automatic beaconing to work reliably, however, took two radios, weeks of testing, packet log analysis, and a lot of time on aprs.fi. The culprit turned out to be an undocumented interaction between two settings — and once identified, it was a one-sentence fix. This is what I learned, so you don’t have to learn it the hard way.

The full writeup is on EtherHam: settings, firmware notes, real-world packet data, and more. Make the jump to Getting APRS Working on the TIDRADIO TD-H9 for the details.

An AllStar Node on the Seeed reRouter CM4

The Seeed Studio reRouter CM4 1432 is a compact mini-router built around the Raspberry Pi Compute Module 4 — and unlike standard Pi builds, it stores its operating system on onboard eMMC flash rather than a microSD card. For AllStar node builders who’ve lost a node to card corruption, that’s a compelling detail. This article walks through converting the reRouter from its factory OpenWRT installation to Raspberry Pi OS, installing ASL3 on Debian 13, and building a fully functional AllStar node — including UCI radio interface setup and thermal testing of the passive cooling system.

Read the complete article: An AllStar Node on the Seeed reRouter CM4.

Retiring the Pi 4: Building a Better Home NAS with the Beelink ME Mini

The Beelink ME Mini is a purpose-built NAS mini PC that competes directly with a Raspberry Pi 5 kit on price but wins decisively on performance, thermal design, and expandability. It ships with an Intel N150 processor, 16GB LPDDR5, a 1TB NVMe, dual 2.5GbE ports, and six M.2 slots — all in a compact enclosure with a substantial internal metal heatsink and a built-in power supply. If your Pi-based NAS is running out of steam, this is worth a serious look. Here’s my experience migrating a home NAS and OwnTone music server to this platform, running Debian 13 and OMV 8, including the gotchas worth knowing before you start.

Visit Upgrading the Home NAS: From Raspberry Pi 4 to Beelink ME Mini for more.

DroidStar IAX Still Broken — But the Fix Exists

DroidStar’s IAX/AllStar connection mode stopped working for many users in early 2026 — the Connect button simply does nothing. This article traces the bug to its root cause, tests available prebuilt Android APKs, and then builds DroidStar from source on a Raspberry Pi 4 utility machine to confirm that the fix is real, the IAX handshake works, and the problem is that nobody has shipped a working Android build yet.

Learn more at DroidStar IAX Connections: Broken Builds, a Working Fix, and a Rabbit Hole Worth Falling Down.

03 Gadgets

USB Cable Tester

I got a little frustrated last week trying to find a USB-C cable that carried data. It seemed like every cable I pulled out of the box was a charge-only cable.

Time for a cable tester. I ordered this one, even though it requires the user to interpret the LED lights displayed when testing:

Treedix USB Cable Tester USB Cable Checker Data Wire Fast Detection for Type-C, USB-A 3.0, Micro-B 3.0, Micro-B 2.0, Mini-B 2.0, and for Lightning Cables by Checking the LEDs (this is an affiliate link)

It is rated 4.5 stars by more than 100 users. For $19, I think this will save me a whole bunch of frustration. There is a less expensive version with clear acrylic panels and open sides, but since this will get tossed in the radio bag, I was more comfortable with an enclosed case.

Marking tested cables was the next problem — I didn’t want to test the same cable twice. I thought about heat shrink, but that seemed like overkill. Colored electrical tape would work, but cables hit the floor and tape ends lift, collecting lint and dirt. The solution I landed on: red and green gel nail polish. Charge-only cables get red. Data-capable cables get green. I cure the dots with the UV flashlight I carry when I travel.

365nm Black Light Flashlight, UV Flashlight Rechargeable with LCD Display, Powerful Ultraviolet Lights for Pet Urine Detection, Resin Curing, Rockhounding, Scorpion, Uranium Glass, A/CLeak (this is an affiliate link)

That seemed to work. It took about a minute of exposure to cure the nail polish dots to the point they were firm and no longer tacky.

And I have another use planned for the red polish. Mom used to love going trolling for trout. Her favorite lure was a Dick Nite spoon. She always used a spot of red polish to put an eye on her lure. She called it her “Tricky Dicky” lucky lure. Good memory.

Earbud for AllScan UCI80M

I went looking for a way to monitor conversations on AllStar using one of my nodes configured with an AllScan UCI80M USB Communications Interface. The UCI80M uses a Motorola M1 speaker-mic connector. I found an earbud with an M1 connector and gave it a try. These are common in K1 (Kenwood) configurations but harder to find in M1.

It works. The push-to-talk mic tested as “good audio” with the Enhanced Parrot on node 55553. Transmitted audio isn’t studio quality, but it’s understandable.

More interesting is the earbud itself. It’s a single unit with a rubbery tip that fits comfortably in the ear canal. When I first plugged it in, the audio level was painfully high and distorted.

In AllStar, TX and RX audio levels are set in /etc/asterisk/simpleusb.conf. It’s somewhat counterintuitive: the audio you hear is set on the TXMIXASET line, and the audio you transmit is set on RXMIXASET. I worked my way down from the default of 500 — tried 400, 300, 100, 50. Still too loud. At 40, still too loud. At 30, clear and comfortable. Below 30, no output at all. So 30 it is.

The package also included an acoustic tube earbud. I normally skip those — never liked how they feel — but tested it anyway. Surprise: barely any audio at 30. Cranked TXMIXASET back to 500 and got excellent, clear audio at a comfortable level. Pro tip: if the standard earbud is too loud, try the acoustic tube before fiddling with the config. Also, if you’re getting static, try rotating the plug slightly in the PTT housing.

2 Pin Earpiece M1 Ear Piece Headset Ptt Mic to 3.5mm Aux Audio Earphone for Motorola cp100 cls1410 gp300 cp200d bpr40 CLS 1110 1410 cp185 dlr1060 rdm2070d dlr1020 rmu2040 rdu4100 dtr700 (this is an affiliate link)

This device has only 3.1 stars on Amazon, but from a sample of seven reviews. I thought it was worth the gamble at around $20. I’d give it 3.5 stars myself — maybe 4 if it proves durable. It does exactly what I needed: a way to monitor and participate in AllStar conversations through the UCI80M.

Fair warning: overmodulated stations really punch through when the speaker is millimeters from your eardrum. Great in a noisy environment. In a quiet room, bring TXMIXASET down.

04 Run Your Own NotebookLM — Locally

If you’ve used Google’s NotebookLM, you already know the appeal: drop in a document, ask questions, get answers grounded in your actual source material rather than whatever the model feels like inventing.

Open Notebook is the self-hosted version of that idea. Same workflow — upload PDFs, web pages, or documents, chat with an AI about the content, generate notes and summaries — but running entirely on your own hardware, with your choice of AI provider. It supports Ollama, so if you’re already running local models, you’re most of the way there.

I spun it up in a morning in an LXC container on my Proxmox server, pointed it at my existing Ollama instance, and had it ingesting a budget document within the hour. The install is Docker Compose — two containers, a config file, and you’re done.

The Open Notebook project is at github.com/lfnovo/open-notebook. If you’ve got a home lab and you’ve been curious about NotebookLM but prefer keeping your documents off Google’s servers, this is worth your time.

05 Digital Radio News Digest

Digital radio news is a bit light this week.

Recent developments in amateur radio digital voice and VoIP linking modes include updates to AllStarLink, with improvements to QSO One stability and the introduction of YAAMon, a new AllStarLink monitor. The MMDVMHost repository has also seen an update, and the app_rpt repository has received several commits, including fixes for call failures and additions to non-blocking PTT kick pipes. The Amp-ASL amp-server repository has been working on a custom Pi image to streamline installation.

06 Band Conditions This Week

With a solar flux of 144 and a sunspot number well into the triple digits, the higher HF bands are in fine shape right now — 10 through 20 meters should reward anyone willing to spin the dial, and DX contacts are well within reach. Today’s K-index of 1 points to quiet, stable conditions, but don’t let that lull you into thinking it’s been a smooth week; a max K of 4.3 tells us the geomagnetic field threw a minor tantrum at some point, likely giving the polar paths a rough go and knocking the low bands around for a stretch. If propagation felt frustrating earlier in the week, today’s the day to get back on and make up for lost time.

• Solar Flux Index (SFI): 144.0 — Good — solid conditions on 10m through 20m

• K-Index (current): 1.0 — Quiet — excellent conditions

• K-Index (7-day max): 4.3 — Minor storm — HF disruption likely

• A-Index: 42 — Minor storm (predicted)

• Sunspot Number (NOAA/USAF daily): 211

• Sunspot Number (SIDC daily EISN): 149

• Active Solar Regions: 14

Source: NOAA Space Weather Prediction Center (swpc.noaa.gov) + SIDC (sidc.be)
Generated: 2026-06-04 21:03 UTC

07 Radio History

Sixty-three years ago this week, radio amateurs put their second satellite into orbit.

OSCAR 2 lifted off from Vandenberg Air Force Base on June 2, 1962, riding piggyback as ballast on a Thor-Agena B rocket carrying a classified military reconnaissance satellite. The irony is hard to miss — while the Air Force was running a spy mission, a group of volunteer hams had quietly hitched their homebuilt spacecraft along for the ride.

OSCAR 2 was nearly identical to OSCAR 1, which had launched just five and a half months earlier in December 1961. The team had learned from the first flight. They adjusted the thermal coatings to keep temperatures lower inside the spacecraft, tweaked the temperature-sensing system to get better data as the batteries aged, and dropped the transmitter power from 140 mW to 100 mW to stretch battery life. The satellite operated for 18 days before going silent, re-entering the atmosphere on June 21.

What’s remarkable isn’t the hardware — it was a simple battery-powered beacon in a metal box — it’s what it represented. By June 1962, amateur radio operators had already placed two satellites into orbit, making them among the earliest civilian participants in the Space Age, arriving only four years after Sputnik. That Project OSCAR lineage runs in a direct line to today’s AMSAT satellites, CubeSats, and the ARISS station aboard the ISS.

Not bad for a bunch of volunteers working on weekends.

08 Short Stack

Digital Radio

• The Iconic aprs.fi App Finally Lands on Android! — “If you are an APRS enthusiast, a portable HF operator, or an automation geek, this is arguably the biggest software drop of the year.”

• Empower Your Emergency Communications with ACK Off Grid Server — “The ACK Off Grid Server presents a transformative solution for emergency communications, catering specifically to amateur radio operators and emergency response teams.”

• Discover Graywolf: The Ultimate APRS Station Software — “Graywolf emerges as a revolutionary all-in-one APRS station software, combining multiple functionalities into a single, user-friendly interface.”

• What Is FT8 and How Does It Work? — “FT8 is a digital ham radio mode designed for making reliable contacts using extremely weak radio signals.”

• APRStac: A Modern APRS Suite in a Single Binary — “APRStac is an APRS web client, digipeater, I-Gate, BBS, fileshare host, email gateway, and multi-protocol bridge developed by KN4MKB under the ModernHam project.”

SDR

• How to Listen to Aircraft with an SDR — “This guide will walk you through everything you need to know to start listening to aircraft using an SDR.”

LoRa

• When Amateur Radio Meets Search and Rescue: LoRa APRS in the Search for Missing Hiker Jaslinda — “As search and rescue teams worked tirelessly to locate missing hiker Jaslinda Saludin, technology from the amateur radio community became part of the operation. Members of the Cameron Highlands Amateur Radio Club supported the effort by providing LoRa APRS tracking devices…”

Antennas

• Should You Disconnect Your Antennas During Thunderstorms? — I do. “If a thunderstorm is close enough that I can hear thunder, I disconnect my antennas. That practice is common among experienced ham radio operators and shortwave listeners alike.”

• Ham Radio Tech: Do Nearby Metal & Trees Significantly Affect Antennas? — “Radio waves don’t exist in isolation. Every antenna interacts with its environment. Houses, gutters, vehicles, power lines, aluminum siding, steel towers, wet leaves, and even your neighbor’s rusty trampoline all become part of the antenna’s ‘neighborhood.’”

Gadgets

• HRWB 264 – Gadgets For The Shack With Randy Hall K7AGE — There are plenty of gadgets listed in the show notes, and as always, the Ham Radio Workbench podcast is a great time.

AI

• NotebookLM finally has an open-source rival, and I’m hooked — “Open Notebook is a project by developer Luis Novo, available freely on GitHub. It does what NotebookLM does. You upload sources, chat with them, ask questions, generate summaries, and even make podcasts.”

• Engineer builds AI laser defense system that wiped out every mosquito in his home — My first thought was: what could go wrong? “A computer vision specialist has built a system that uses deep learning and a laser-based targeting setup to hunt down mosquitoes. Steven Cheng, who works in computer vision and robotics, documented the project as he developed what he calls “the ultimate mosquito killer,” turning a simple household annoyance into an engineering challenge.”

Security

• Your Android phone is already a security key and most people never turn it on — I just don’t know about this. We are so dependent upon our phones that they are becoming single points of failure in our lives. Making my phone my security key? I just don’t know.

09 Privacy-Focused Document Software

Do you need an alternative to Microsoft 365 or Google Workspace? If so, you’ve probably looked at LibreOffice and OnlyOffice, or maybe Nextcloud. These are document creation and editing packages, sometimes self-described as content collaboration systems.

Something new is on the near horizon: Euro-Office. This software is based on OnlyOffice but comes with a consortium of vendors backing it. It is being updated for the European market with an initial release date of June 9.

Euro-Office doesn’t have the email offering that draws people to M365 or GW. However, it appears that Office.EU will combine Euro-Office and email into a Europe-focused suite, compliant with GDPR and avoiding the U.S. Cloud Act (but I’m not a lawyer, so don’t bank on this conclusion). If all that sounds attractive to you — and it kind of does to me! — head over to https://office.eu/.

If privacy-centered software is your cup of tea, you may also want to think about where your website is hosted. Hetzner, based in Germany, is an affordable option with a solid reputation.

10 If I Win the Lottery: Coffee, Curiosity, and Radio

I’ve often thought: if I win the lottery, I’ll build a clubhouse for my local amateur radio club. It would be great to have a space with different operating stations, maybe some workspaces for making and repairing gear, and since we’re hams: coffee — lots of coffee.

This is purely a thought experiment. As I’ve pondered this, I’ve started to wonder if this might be a way to attract new people into the hobby: a coffee shop with amateur radio operating stations. Certainly the local hams would visit, so we’d often have licensed, experienced people available. But would younger people visit? Maybe — if it was positioned as a coffeehouse where makers and radio operators were doing things with hardware and software and radio waves.

Is that enough of a draw? I don’t know. I do know it’s different than what I hear in conversations about attracting people to the hobby. Clearly, what brought licensed hams into the community over the years has varied. Service in the military is one group of people. Silicon Valley folks another. I’m a Sputnik/Apollo kid, so NASA and hearing radio coming to Earth live from space was a big deal for me. Later, we’ve seen preppers getting licensed.

People in each of these groups saw amateur radio as something they could use to do something with. And for most of them, worldwide communication was not something they carried around in their pocket. That has changed. Getting connected is no longer the draw — the smartphone solved that problem decades ago, and younger generations have never known a world without it.

But maybe, just maybe, connecting locally over a cup of coffee in a tech-oriented space would pull the curtain back on this mysterious thing called amateur radio, at least for some people.

Will I ever do this? I would have to buy lottery tickets, and that’s something I almost never do. But if I did, and if I won, I think creating a radio maker space with coffee would be a grand thing to do. The best part: I’d never run out of coffee.

11 QRT: End Transmission

New Mini PC by HP

HP announces new OmniDesk Mini PC: World’s first “AI Mini PC” with Intel Core Ultra and Thunderbolt Share — I do love me a good PC by HP. No idea how much this is going to cost (undoubtedly too much) but might be worth watching for on eBay in a few years!

The Knack

I overheard some conversation on the W6EK repeater in California about “the knack.” This brought back memories of how I would disassemble many things in my childhood…and only occasionally getting them put back together again in working order. I share this Dilbert YouTube in case you find the humor entertaining. I do.

I’m guessing that “The Knack” is a real thing. The disassembly-to-reassembly success ratio in childhood is probably a reasonable predictor of career trajectory in this great hobby of hobbies: amateur radio.

73, and remember to touch a radio every day!

00 QRV: Are You Ready?

Welcome to Random Wire 184.

It’s great to see the sun again — we don’t get all that many warm, clear days during winter in the Pacific Northwest. And while I am really enjoying baking the winter cold out of my bones, I’m concerned that we’re in for another historic wildfire season. We had a warm-ish winter and the snowpack is generally well below average. Predictions are for a hot, dry summer that may set new records. We joke about Californians moving to Washington and Oregon, but it’s not quite as funny that California weather is also creeping northward. I have my fingers and toes crossed, hoping that we don’t have a perfect storm of wildland fire conditions this year. In short: please be careful out there!

01 Thank You…to Field Day Operators

ARRL Field Day 2026 is just around the corner and savvy radio operators are busy organizing their gear and making plans. For some, this is a contest. For others, it’s an annual social event. And for others, it’s a chance to give the general public a glimpse into our very wide and deep hobby. Whatever camp you’re in, I want to express gratitude for participating in one of the biggest annual amateur radio events in the world. Have fun, make lots of contacts, and share your challenges and successes with others. That’s how we learn how to do it better next time and to be prepared!

02 New on EtherHam.com

It was a busy week in all aspects of my life, but I still found some time to dive into a few topics…mainly Raspberry Pi-focused, but interesting, nevertheless:

• AllStar Node with Raspberry Pi 4: New Case and UPS Hat

• Inside EtherHam: May 2026

• Monitoring and Managing a Raspberry Pi 4: Three Tools, Three Jobs

• Your Raspberry Pi 4 Makes a Surprisingly Good Home NAS — With Music Streaming

For next week, I’ll also be working up an article on using a mini PC powered by an N150 CPU as the basis for a network-attached storage (NAS) device. As I tie a ribbon around this issue, I have that NAS box running on my LAN and streaming Steely Dan music to my laptop. It is working much better than the Raspberry Pi 4 NAS, running the same software stack. This is a win and I’m looking forward to sharing my write-up with you. Here’s a teaser photo of the interesting hardware platform I built this on.

Vertically cooled, six NVMe spaces, two 2.5GB Ethernet ports, and powered straight off the mains (no power brick or wall wart). It is much more responsive than the Raspberry Pi 4-based NAS build, and just as important to me, it runs much cooler.

04 TIDRADIO TD-H9: Still Working On It

I spent more time — lots of time! — trying to get APRS to beacon automatically on the TD-H9. I’ve not been able to figure out cause-and-effect with this radio. I change a setting and the behavior doesn’t change. Then I don’t change a setting and the behavior does change. It beacons when I move the radio, then it doesn’t. Or it doesn’t beacon at all, even though it is set to do so. I’ve driven to town with the radio set to beacon and it beacons when I leave, but not again. I’ve driven to another city, and once it beaconed and the other time it didn’t.

Confusing doesn’t begin to cover it.

I find no explanation of the differences between two firmwares: a TD-H9 1.0.32 version dated May 7, 2026, and a TD-H9 APRS 1.0.15 version dated January 9, 2026. Maybe I need to try the APRS firmware version…but first, I’ll update to the latest and greatest firmware and try that.

I did not find a USB-C cable that worked, nor do I have the proper K-1 programming cable. I will before Friday, though, so hopefully I’ll get this done in time for this issue of the Random Wire.

I have a second radio coming so I can make sure this isn’t baked into the radio. It’s orange and you’ll want to see pictures, so I should have more to report and show you next week.

Bottom line: still working on it, stay tuned.

05 Repackaged AllStar Node and Restored Configs

I bought a case with room for a Raspberry Pi hat, and added an uninterruptible power supply hat to the Pi. The AllStar node is built on a Raspberry Pi 4 and uses the AllScan UCI80M USB Communications Interface for high-quality audio. That seems to be working well, although there are two modifications I want to make: add a momentary on/off button to trigger a safe shutdown if the system locks up, and add a cooling fan. Find the article on the EtherHam site: AllStar Node with Raspberry Pi 4: New Case and UPS Hat

Once I got the Pi moved into the new case, did some scripting, and tested, I noticed that the system was unstable. Suspecting a microSD card that was beginning to fail, I chose to install a fresh AllStarLink 3 Appliance package to a new microSD card.

Normally, I would then walk through the configuration menus and manually enter all the necessary settings. This time, I didn’t do that. This time, while running on the failing microSD card, I copied a host of configuration files to a network drive. Then I shut down, installed the ASL3 Appliance package to a new microSD, booted from the new card, and copied those configuration files to the new card.

There were a couple of permission issues that interrupted things. The Allmon3 package had no password set, so I took care of that manually. And the Cockpit interface kept failing, but that was because it was reading old cookies from my browser. Once I flushed those cookies, the system stabilized and all was well.

I don’t think I saved any time doing it this way, but I did prevent most of the inevitable fumble-fingered mistakes that always come with manually configuring settings. I wanted to test how easy it was to mount a network drive, move files from the node, then move files back to the node. That worked nicely.

The performance of this particular platform proved to be poorer than I expected, so I changed some settings to push the chip a little harder. That increased the operating temperature, with the CPU reaching 70°C — still below the point where throttling begins at 80°C, but warmer than I’m comfortable with. To resolve this, I’ve ordered a fan to add to the system and should be able to report on this next week.

06 The Short Stack

EmComm

• Ham Radio EmComm Insights: A Look at the Narrow Band Emergency Messaging System — “…the Narrow Band Emergency Messaging System…is an open-source software package that allows licensed amateurs to send data via RF.”

• The Best Two-Way Radios for Bug-Out Bags and Off-Grid Emergency Communications — “…not all radios are equal, and there’s an enormous amount of bad information online right now. If you’re building a bug-out bag or emergency communications kit, here’s what actually matters — and what doesn’t.”

Shortwave

• The internet’s creepiest radio mystery is live on shortwave, and you can hear it for yourself — “I found some genuinely strange signals. Some of them were ordinary military, utility, or timing signals, but some of what I found have a genuinely creepy and interesting history behind them.”

Raspberry Pi

• Why Are Raspberry Pis So Expensive? (+Tips to Get One Cheap) — “I dug into the reasons why, and there are a few tricks that can really help.”

• RAKwireless WisMesh Pi HAT RAK6421 turns your Raspberry Pi 4/5 into a modular Meshtastic gateway — “RAKwireless WisMesh Pi HAT RAK6421 is a modular Meshtastic gateway expansion board for Raspberry Pi 4/5 that adds support for the company’s WisBlock ecosystem. Designed for users running meshtasticd (the Linux-native Meshtastic service), it enables scalable, always-on Meshtastic base stations, MQTT gateways, and backbone relay nodes.”

Logging

• Best Amateur Radio Logging Apps for Android and iOS in 2026 — “Here are the best amateur radio logging apps for Android and iOS right now, based on features, LoTW/QRZ support, contest use, and offline capability.”

07 Digital Radio News Digest

Perhaps the most interesting item to me is the update on the LinHT project. I’m looking forward to eventually getting one of these open source transceivers in my hands and on the air.

Summary

Recent developments in amateur radio digital voice and VoIP linking modes include updates to M17 hardware testing, AllStarLink forum discussions on Asterisk core dumps and Debian 12 server issues, and GitHub commits for various VoIP linking systems. The M17 Project has reported on the hardware testing status of LinHT Rev B, while the AllStarLink community has been discussing issues with Asterisk core dumps and server setup. VoIP linking systems have seen updates to app_rpt, ASL3, and amp-server.

Per-Mode Breakdown

DMR

There is limited information available for DMR, with only one GitHub commit mentioning a cleanup involved with renaming in MMDVMHost.

YSF/C4FM/WiRES-X

Random Wire has published an article on upgrading MMDVM hats, but there are no other notable updates for YSF/C4FM/WiRES-X.

M17

The M17 Project has reported on the hardware testing status of LinHT Rev B, and there have been GitHub commits for OpenRTX firmware, including a fix for the miosix GCC toolchain path.

Wojciech Kaczmarski was kind enough to alert me to an update published on the M17 Project page. Find that at: LinHT Rev B – hardware testing status.

VoIP Linking

The AllStarLink community has been discussing various issues on their forum, including Asterisk core dumps, Debian 12 server setup, and Echolink loopback. There have also been several GitHub commits for VoIP linking systems, including updates to app_rpt, ASL3, amp-server, and asl-parrot.

Notable Firmware or Software Updates

• app_rpt version 3.9.3

• app_rpt version 3.9.2

• ASL3 commit to improve Broadcastify Experience

• OpenRTX firmware commit to fix miosix GCC toolchain path

• amp-server commit to overhaul call state management

• asl-parrot commits to overhaul call state management and update to latest amp-core

Last run: 2026-05-28 22:07 UTC — 23 items collected.
Download the collected items here.

08 Band Conditions This Week

Conditions: a decent setup heading into the weekend, but not without caveats. An SFI of 108 and a quiet K-index of 2 put us in good shape for reliable HF propagation, with 20, 17, and 15 meters likely performing well for both regional ragchews and longer DX paths.

That said, the past week wasn’t entirely smooth sailing; a 7-day max Kp of 3.7 hints that we saw some unsettled stretches that may have rattled the higher bands, and with the predicted A-index sitting at 11, it’s worth keeping an eye on conditions rather than assuming the calm will hold. With 15 active solar regions and a healthy sunspot count, the sun is staying busy, so there’s plenty of potential energy in the pipeline — for better or worse.

• Solar Flux Index (SFI): 108.0 — Moderate — reliable HF propagation

• K-Index (current): 2.0 — Quiet — good conditions

• K-Index (7-day max): 3.7 — Active — some HF degradation

• A-Index: 11 — Unsettled (predicted)

• Sunspot Number (NOAA/USAF daily): 103

• Sunspot Number (SIDC daily EISN): 155

• Active Solar Regions: 15

Source: NOAA Space Weather Prediction Center (swpc.noaa.gov) + SIDC (sidc.be)
Generated: 2026-05-28 22:05 UTC

09 Radio History

A few milestones cluster around this time of year that are worth a moment of reflection — especially if you’re the kind of operator who thinks about where we came from…and maybe wonder where we’re going!

May 1919: QST comes back to life

When QST returned in May 1919, it came back as an eight-page bulletin with no cover, barely resembling the magazine it had been before the wartime shutdown. Amateur radio had been banned since April 1917, and hams still weren’t back on the air — that wouldn’t happen until that October, when a supplement to the fall issue famously proclaimed “BAN OFF.” But the magazine’s return was the signal that the community intended to survive the hiatus.

June 1933: The first Field Day

The first ARRL Field Day was held June 10–11, 1933, under the name International Field Day. Ed Handy, W1BDI, then ARRL Communications Manager, is credited with the idea. About 50 portable stations participated, and the point was straightforward: could amateurs pack up their gear, get out of their shacks, and keep communicating under field conditions? Ninety-three years later, that question still drives the last full weekend of June every year. POTA, portable ops, and EmComm culture are all downstream of that original experiment.

May 1952: The 15-meter band opens — but just for CW

On May 1, 1952, the FCC opened the 15-meter band to U.S. amateurs — CW only. Phone privileges on 15 meters didn’t arrive until March 1953, and the same 1952 rulemaking also extended phone operation to 40 meters, which had previously been CW-only. Taken together, these changes reshaped HF operating and helped accelerate the slow migration from AM toward SSB that would play out across the rest of the decade. It’s one of those regulatory moments that didn’t look like a turning point at the time, but really was.

A personal aside: I missed the real Kon-Tiki anniversary

I wanted to work the topic of the Kon-Tiki into this column, but I missed the anchor: the raft departed Peru on April 28, 1947. That’s a late April anniversary, not late May, and I didn’t catch it until after the fact.

Still worth saying: the Kon-Tiki expedition carried an amateur radio station — callsign LI2B — operated by Knut Haugland and Torstein Raaby, both former Norwegian resistance radio operators from World War II. Over a 101-day voyage across the Pacific, they maintained regular contact with American, Canadian, and South American ham stations, relaying position and meteorological data to the Norwegian Embassy in Washington. The December 1947 issue of QST called it “the most unusual expedition ever to place reliance on amateur radio for communication.”

I read Heyerdahl’s book over and over as a kid, long before I knew anything about ham radio. His writing instilled in me a taste for adventure, and a realization that sometimes, one had to think outside the box to achieve something wondrous.

It turns out the radio operators on that raft were doing something I’d later spend a lot of time thinking about: proving that if you have the right gear, the right skills, and a schedule to keep, you can communicate from anywhere.

That’s not a bad way to describe Field Day, either.

10 QRT: End Transmission

Busy Week

I was surprised by how busy I was this past week. The biggest event was a medical incident requiring taking my wife by ambulance to the emergency room. We got home 11 hours later. The good news: we got home. The bad news: we’re going to have to make that trip to the hospital again to fully resolve the situation.

Domain renewals

If you followed Random Wire issues 182 and 183, you know I’ve been talking a bit about the rising cost of domain renewals. Hours after issue 183 was published, I receive a notice that my EtherHam domains were up for renewal. I’m glad they remind me and I immediately paid to renew them…and yes, costs are rising.

Embarrassing Shack Moment

There I was, concentrating on my laptop screen, when I heard audio on my AllStar node beside me. That’s odd, I thought — that node isn’t supposed to be connected to anyone right now. I turned up the volume but it didn’t respond. I looked at Allmon3 and AllScan to try to figure this out but wasn’t getting anywhere. Then I asked Claude what might be causing connected nodes not to show up, and boy, that was a rabbit hole.

Several minutes later, I reached for the node and that’s when I noticed what I had done: I had put my M1KE device right behind the speaker-mic stand. I wasn’t hearing my node. I was hearing our local YSF/WiRES-X repeater through the M1KE. This is where that SMH abbreviation — shaking my head — really hits home.

The good news? The M1KE audio sounded almost as good as my AllStar node!

73, and remember to touch a radio every day!