This week’s PHP2Shell flaws sent me checking my own nodes. After all, the NSA published an advisory, saying apply the emergency patch today.

After running updates on what I thought was all of them, I found one I’d missed: a Raspberry Pi node, running the standard ASL3 image, was one release short of the PHP fix, with 13 security updates waiting and automatic updates turned off. I hadn’t turned them off. Installing ASL3 simply doesn’t turn them on.

So I put together a script that checks an AllStarLink 3 node and reports, in plain language, what needs attention and exactly what to type to fix it. It checks whether your node is getting security updates, whether PHP has the PHP2Shell fix, whether anything is still running old code after an update, whether your firewall and fail2ban are running, and how your node accepts logins. It doesn’t change anything on your node.

The script is free, MIT licensed, and available on GitHub right now. It’s for ASL3 nodes only; on HamVoIP or ASL2, it stops and tells you why. From your node’s command line (at the node itself or over SSH), run these two commands:

wget https://raw.githubusercontent.com/EtherHamRadio/asl-node-check/main/asl-node-check.sh

sudo bash asl-node-check.sh

I’ve tested it on a Dell Wyse 3040, a cloud server, and a Raspberry Pi 4, and it found something worth fixing on all three.

Later this morning on EtherHam, “Checking the Locks: A Morning Security Review” will publish, along with a link to a checklist you can use with your home network devices.

See: asl-node-check on GitHub

1. QRV: Are You Ready?

New Here? Welcome!

The short version of what you’ll find in the Random Wire newsletter: eclectic, electric, and sometimes a skeptic. I rarely take a straight trail through a single topic. Usually, we enjoy a winding, up-and-down walk through the territory where amateur radio, computing, and technology overlap, and some weeks we might even wander off the map.

This week is a good example. I started the week wondering what I’d write about, and then the sparklers started going off: an M17 reflector update, two essays, a change in AllStarLink’s sound system, a security notice that will touch many radio amateurs, and a script to help you act on it. Then a database idea woke me at 3 a.m., and by the end of the morning it lived in a repo on GitHub and ran on my Proxmox server.

I always sign off by asking you to touch a radio every day. The past few days reminded me of a quieter version of that advice: think about radio every day. The ideas will come.

2. QST: News and Notices

2.1 Security Alert: Update Your Hotspot or Node Today

PHP released fixes on October 21 for two critical flaws, the PHP2Shell flaws, that can let an attacker take over a Pi-Star or WPSD hotspot, or an AllStar node, without a password. Debian has the fix, so update today. If you run an ASL3 node, the script in this issue’s lead item will tell you whether you’re covered. On EtherHam, I explain who’s affected, why older Pi-Star and HamVoIP systems may never get the fix, and why the five Nginx patches this month are lower risk.

See: Two Security Updates for Hotspot and Node Owners: One Urgent, One Not

Sources:

• PHP News Archive 2026: Security advisory, October 21

2.2 Your Phone Is Now a DMR Transceiver

I’ve not tried the Z3DMR app yet. This app surfaced during the weekly M17 net on the Kansas City Wide network. Looks interesting. Available on Google Play.

Connect over the internet, key up, and talk to operators anywhere in the world - in your own language. No extra hardware. No ads. No tracking. Completely free.

2.3 QSO One 4.1.8 Released

QSO One 4.1.8 claims a built-in, from-scratch voice codec, tuned for D-STAR. However, the release notes don’t say whether DMR or Fusion use it, and the app is closed source, so the claim can’t be independently checked. I’m amazed at what the author, Frank KD8JKK, has accomplished, but I worry about project stability. It appears to be a one-person effort, and with closed code, there’s no opportunity for someone else to pick it up and carry it forward.

3. Thank You for the Coffee

A big Random Wire/EtherHam thank you to Mike for the coffees! He wrote: “I love how clearly you document each step in a project.”

Mike, that one made my day. I write things out step by step because I’ve been the ham stuck halfway through a project, wondering what the instructions left out. Knowing it helps is the best reward there is, and the coffee is a very nice bonus. Thank you!

4. New on EtherHam & Random Wire

4.1 Updating My M17 Reflector to mrefd 1.1.5

My M17 reflector, M17-PNW, was running mrefd 1.1.1 when Thomas Early N7TAE’s GitHub repository had already moved on to 1.1.5. The update itself is short and well documented in the README, but it has to start from the folder where you built the software, and I had forgotten where that was. Two old Linux standbys saved the day. find located the build folder once I searched for a file that could only exist there, and grep showed me that my config still used an option the new version had retired. After I commented that line out, a second grep proved the edit had landed, which mattered because the tool I used to make the change works silently.

The reflector was offline for just under five minutes, and the startup log confirmed 1.1.5 was running, with my hotspot back on within a second. The bigger lesson isn’t about M17 at all: search, change, then search again, and read what the log actually says before reacting to an ERROR in capital letters. The full story, including all 17 commands in order, is on EtherHam: Updating My M17 Reflector to mrefd 1.1.5

4.2 About Those Limits We Think We Have

Some of my best ideas show up when I’m behind the wheel. This week’s second EtherHam article — About Those Limits We Think We Have — took shape on a morning drive, somewhere between home and an Egg McMuffin breakfast sandwich.

It started with a question I couldn’t shake: how many of the limits we accept in ham radio are real, and how many are just habits we’ve stopped noticing? David Rowe VK5DGR didn’t accept that digital voice had to depend on a closed codec, so he wrote Codec 2. Wojciech Kaczmarski SP5WWP didn’t accept that hams couldn’t design their own digital voice standard, so he started M17. And Bruce MacKinnon KC1FSZ found that the 8 kHz ceiling we’d all assumed was baked into AllStarLink wasn’t there at all.

None of this is new, either. Hams have been walking around “impossible” since 1912. The article closes with a question for you, and I promise it’s a friendly one: what mountain have you stopped seeing?

4.3 POTA/SOTA: From Park and Peak to Preparedness

What if every POTA and SOTA activation helped make us a little more ready for an emergency? In this week’s third EtherHam piece, POTA/SOTA: From Park and Peak to Preparedness, I float an idea: a voluntary “super activation” bonus for passing a formal NTS message from the field, with something in it for hunters and chasers, too.

I already know the official answer is probably “no thanks.” But if it gets a few more of us curious about traffic handling, it will have done its job.

4.4 AllStarLink Quietly Cuts an Old Cord

AllStarLink 3.10 finally dropped its dependence on OSS, a Linux sound interface from the 1990s. One of the developers called it a first step toward supporting more audio devices, which could someday free nodes from the C-Media fob. On EtherHam, I explain what changed, where it might lead, and the one thing to check on your node after you update. See: AllStarLink Quietly Cuts an Old Cord

4.5 Two Security Updates for Hotspot and Node Owners: One Urgent, One Not

As noted in the QST section, this is explained over at EtherHam.com in Two Security Updates for Hotspot and Node Owners: One Urgent, One Not

4.6 Weekly Report

Each week’s report has four parts, and each one comes from a different source. The Short Stack is a curated list of links drawn from more than 90 amateur radio, technology, and space feeds that I collect on EtherHam’s mega feeds page. An AI assistant pulls the week’s items and sorts them into sections; I decide what stays, add notes where I have something to say, and I usually drop the shopping posts and filler.

Band Conditions summarizes solar and geomagnetic data from NOAA’s Space Weather Prediction Center, plus SIDC’s sunspot count when their site is reachable, as of the time the report was generated.

Digital Radio News and the Groups.io Digest are produced by my own scripts. Digital Radio News collects the week’s code commits, releases and forum threads for DMR, D-STAR, YSF, M17, AllStar and the other linking modes, and an AI model summarizes them; the raw source list is linked at the end of that section so you can check anything that looks off. The Groups.io Digest checks about 30 mailing lists and shows which topics were busiest over the past seven days. I review everything before it’s published, but the generated sections can still contain errors. If you spot one, please tell me in the comments.

See: Weekly Report: October 21, 2026

4.7 A Database Born at 3 A.M.

I woke up in the middle of the night thinking about tables. Not the kitchen kind, but tables that hold information. Between two homes, a garage, and a Proxmox server, I have AllStar nodes, routers, hotspots, APRS stations, and spare Raspberry Pis scattered around, and I wanted a better way to answer some simple questions. Which of my boxes run AllStar? Where is that spare Pi? What did I change last month?

What popped into my head was a “tri-dex,” a single table I could search three ways: what a thing is, where it is, and when something happened to it. By breakfast it had grown a fourth dimension: why a thing exists (its role, like AllStar or networking), and the tri-dex became a quad-dex. It now has a proper name: QuaTrel, a mashup of quaternary and relational, which I pronounce KWAH-trel.

The idea is simple. You pick one of the four facets (WHAT, WHY, WHERE, or WHEN) as your primary search, optionally a second and a third, and each one sorts the results its own way. “WHY = AllStar, then WHERE” lists my AllStar nodes grouped by location. “WHEN in September, newest first” lists everything I did that month. A separate status filter (In service, Spare, Surplus, Broken, Retired) makes the gear on the shelf just as easy to find as the gear on the air, because a spare is valuable precisely because it could be used. And every item keeps its full history, so when a node moves from one house to the other or picks up a new job, QuaTrel can track it.

Getting started takes about five minutes if you already keep a gear list in a spreadsheet. QuaTrel imports a simple CSV file (name, what, why, where) and builds its vocabulary from your own words, so my “lake house” and your “county EOC” both work without any setup. I’m running it in a small Proxmox container (a lightweight, isolated space on my home server, similar to a virtual machine), so I can reach it from any computer at home, password-protected. It also runs fine on an ordinary Windows, Mac, or Linux computer.

I built QuaTrel with Claude’s help over a single morning, from that middle-of-the-night idea to a working app on my home network, then tested it with my real gear. It’s free and open source under the MIT license, and you’ll find it on GitHub, along with a step-by-step guide for installing it in a Proxmox container.

It’s a version 0.1 tool — still early days, not fancy, just useful — and I’d like to hear what works for you and what doesn’t. If you try it, open an issue on GitHub or simply reply to this email.

Sources

• QuaTrel on GitHub: https://github.com/EtherHamRadio/quatrel

• QuaTrel Proxmox install guide: https://github.com/EtherHamRadio/quatrel/blob/main/deploy/quatrel-proxmox-install-v1.1.md

5. Gear

5.1 New AMBE Stick and Telephone-style Handset

A month ago, I mentioned I had ordered a new AMBE stick. GigaParts carries them. It arrived and I put it into service, but more on that in a moment.

I used my original DVStick 30 when I built an AllStar+DVSwitch node on an old Evolve III laptop. That stick had a label on it — BlueDV — because I’d been using it with BlueDV for Windows back when I had two sticks. One failed, so I ordered a replacement. When the new stick arrived, it went into the AllStar+DVSwitch node, and the labeled stick went back to its old home in the USB port on my Windows Surface laptop.

I had a tiny curve ball to deal with when I switched sticks: the COM port changed. Even though the new stick and old stick are identical model numbers, one registered as COM3 and the other as COM6. Switching the devices in the same USB port caused BlueDV to report no device…because the COM port was different. That was an easy fix.

While I was at it, I saw an update link in BlueDV so I updated to the latest beta release. It is working well.

Along the way, I had also picked up an audio device I thought would be fun to try: an old-style phone handset with a USB-C plug.

I took a snapshot with the laptop’s camera (raw and unfiltered) while using this retromod device to listen to a QSO on the Kansas City Wide network over BlueDV for Windows. The audio quality is fine on the handset, and I can listen without the audio disturbing my wife nearby. It’s perfect for those times I just don’t want to use a headset.

The handset is called the POP Phone by Native Union. Cost: about $40. (Less expensive options from about $15 to $30 are available through Amazon.) The “pick up and hang up button” doesn’t work with BlueDV — you have to manually click the transmit button in the bottom right corner of the app:

That’s not much of a bother, and I like that the app button makes it very obvious if you are transmitting or just monitoring.

And you know, it feels wonderfully familiar and comfortable to plug it into my Android phone for a phone call. Old and new, coming together in a modern working device. What’s not to like about that?

5.2 Omada ES208G 8-Port Easy Managed Switch

I just added a TP-Link Omada ES208G to my gear, an 8-port Gigabit “easy managed” switch that was about $30 on Amazon (this is an affiliate link). It replaces an old 16-port switch in the Portland rack that once powered a pile of devices using Power over Ethernet (PoE) but now powers nothing, since most of that gear has moved to the lake house. Eight ports is plenty for what’s left there, and every port is Gigabit speed, a step up from the old switch’s slower Fast Ethernet ports.

So why would an ordinary home user want a managed switch instead of the plug-and-forget kind? The feature that sold me is port isolation. On a normal switch, every device can talk to every other device, so if one gets compromised, it can go looking for network neighbors. With port isolation turned on, each isolated port can reach the router and the internet but not the other isolated ports. That limits an intrusion to a single device, without my having to build separate networks or VLANs (virtual networks that divide one physical network into several).

The ES208G also has built-in cable diagnostics. That’s handy when you’re staring at a tangle of patch cables wondering which ones are dead. It also automatically protects against loops, the classic mistake of plugging both ends of a cable into the same switch and knocking the network over. The switch can be managed with TP-Link’s Omada cloud app, but it doesn’t have to be: everything I need is on the switch’s own web page.

For $30, that’s a lot of value for an 8-port switch.

6. Weekly M17 Net Summary

This was an information-packed net full of exciting news. As usual, the net was well run.

I used my AllStar Net Transcriber fork to capture audio, with light AI processing of the resulting transcript. Then I asked Gemini to summarize from the transcript (to save space, I am not including the list of check-ins).

Please consume this information with a grain of salt. First, the content pasted below has been processed by an AI. Second, I was having trouble getting my logger to work, so I missed some of the initial content in the net. (This was a problem I caused when I swapped in a new DVStick device. I was getting a little frantic as the net started, with three SSH sessions open on two computers, plus DVSwitch running, and two AllStar nodes (578494 and 588416) active and connected. Except they weren’t. The audio chain had broken when I put the new DVStick into service.) I got it fixed about ten minutes into the net, so I did catch most of the content.

Executive Summary

The net was hosted by Jeff (AE5ME). The session focused on technical updates regarding the M17 Project software/hardware ecosystem, recap and insights from the ARDC / Zero Retries Digital Conference (ZRDC 2026) held on October 16, and discussions on the evolving landscape of amateur radio technology. The NTS portion of the net was skipped due to time constraints. There were 33 check-ins recorded for the net.

1. M17 Project & Technical Updates

• Codec 2 Neural Mod (Codec2 Mod Neural):

  • Developed by Wojciech.

  • Acts as a drop-in alternative decoder for Codec 2 voice streams (3,200 bps, 8-byte frames) without changing the transmitted over-the-air bitstream.

  • Takes 8 bytes in and outputs 320 samples at 16 kHz, significantly improving receiver voice quality over the classic buzzy/synthetic decoder.

  • Uses Opus C-inference code with 818,000 parameters (~1.6 ms CPU time per 20 ms frame).

  • Neural speech synthesizer research by Felix Schaefer (DG8SF) was also referenced.

• Hardware Progress:

  • Photos of the latest LUN HD RevC [Editor: this should say LinHT, not LUN HD] boards were shared; boards have been manufactured and are undergoing testing prior to ordering.

  • libm17 was updated for lightweight Cortex-M4 microcontroller environments (e.g., OpenRTX).

• MMDVM Host, M17 Gateway, & WPSD Infrastructure:

  • Jim (N1ADJ) updated M17 Project forks for MMDVM_HS / MMDVMHost and M17Gateway to sync with upstream repositories.

  • End-to-end M17 packet mode (including SMS messaging) is now supported across radios, hotspots, gateways, reflectors, and dashboards.

  • Live updates for WPSD are available via nightly updates or manual triggers.

  • MQTT updates broke backward compatibility; three repository branches are maintained (v1.0 branch for classic, master for current restored M17 code, and an archive master).

  • Voice announcements (full reflector name + module) added to M17Gateway.

  • Firmware/hardware constraints: M17 packet/SMS support works on MMDVM HS hat, Dual Hat, generic GPIO, and MM repeater boards, but ZoomSpot, NanoHotspot, NanoDV, and Skybridge boards do not yet have packet-capable firmware.

2. ARDC / Zero Retries Digital Conference 2026 Recap

• Event Details: Held on October 16, 2026, in San Ramon, California.

• Key Topics:

  • Discussions on the future of ham radio and appealing to “New Tech Hams”.

  • Engaging new technical users entering via MeshTastic / MeshCore.

  • Work on DigiPot [Editor: probably meant DigiPi] software (Packet Radio, Pat Winlink).

  • Panel Discussion on Encryption: Explored regulatory constraints (only permitted for space/satellite control links), medical privacy (HIPAA compliance during disaster response), and the pros/cons of encryption in amateur radio.

  • Overview of the IP400 project—a mesh network digital radio system targeting high-speed data (~56 kbps) planned for Q1 2027.

  • Mercury Modem and M73 modem progress as potential competitors to VARA/VARA FM.

  • Microcontrollers in radio.

  • Updates on the FreeDV project.

  • Development of the Open Source TNC (OpenTNC).

• Conference proceedings and Zoom recordings will be available at zeroretries.org.

7. Administrivia

7.1 Now Comes the Substack Freewall — but Not Here

Substack (the service that hosts the Random Wire newsletter) has added a feature for authors called the Freewall. When an author turns it on for a post, web readers who aren’t subscribed can read only up to a point the author chooses; to see the rest, they have to subscribe (for free). Email subscribers still get the whole post. On the face of it, that sounds like a great way to convert casual visitors to subscribers.

However, this makes no sense for the Random Wire newsletter. It’s free. It’s open. And amateur radio operators rightly tend to be wary about handing over their email address.

The real problem: requiring people to subscribe to my free newsletter would ultimately make my content less accessible. Anyone who followed a link posted in a discussion group or forwarded in an email would hit a wall, and people would soon stop sharing those links.

While the Freewall isn’t a modal popup like you see on some sites (newspapers, I’m looking at you), it would still disrupt the user experience. I can see a case for using it on older, archived posts, but overall, it’s simply not a good choice for current issues of the Random Wire.

To paraphrase a line often used in the TV show Shark Tank: For these reasons, I’m out.

7.2 I Modified My Documentation Wiki

I spent Saturday afternoon reorganizing my NETDOCS wiki. It was split by location (Portland and the lake house), which stopped making sense once I realized I would eventually consolidate everything in Portland. Now every runbook lives in one place, grouped by system, and location is just a tag I can change when the gear moves. I also found the wiki had been running on Berlin time all along. I’ve added the details, including one Move-plugin mistake worth avoiding, as an update to A Wiki That Lives on the Rack on EtherHam.

7.3 Two Quote Marks Short of a Working Search

If you’ve used the Random Wire Archive search on EtherHam (etherham.com/rw_search/), you may have hit a wall without knowing it. The day after publishing issue 204, I did a fresh import and went looking for “ZRDC,” which I’d written about. Nothing came back. A search for “1962,” which is right in that issue’s title, also came back empty. But when I browsed the archive without a search word, there was issue 204, sitting at the top of the list.

My first suspicion was the import, since I had just run it a few minutes earlier. Claude and I went down that road for a little while. Claude even reproduced an import failure on a test database, which made the theory look solid. But the search results kept saying something different. The clue that cracked it was that “1962” found five issues with the year set to “All years,” and none at all with the year set to 2026, even though four of those five issues are from 2026. Whatever was wrong had nothing to do with the new issues. It was the year filter in the search code.

The culprit was in a single line of code that was missing two quote marks. When you search with a keyword and pick a year, the database pulls the year out of each issue’s date as text, in this case the characters “2026.” My code compared that text to the number 2026, written without quotes. To the database, text and numbers are different things, so the comparison could never be true, and every keyword search with a year selected found nothing. Browsing by year worked fine because that part of the code had the quotes. The version on GitHub had them too. My server was running an older copy.

The fix took about a minute once found, and all of this happened while I was listening to the weekly M17 net on the Kansas City Wide network. I also fixed a separate bug in the setup script on GitHub, which could have tripped up anyone building the search from scratch. As far as I know, nobody else has built it from scratch yet, but now the repo matches what’s running on EtherHam. The lesson I keep relearning is that a good theory doesn’t mean much without testing it. My first theory was plausible, but the search results were telling me where to look the whole time. If the archive search ever misbehaves for you, please let me know.

7.4 My Meta Descriptions Were Broken

I discovered that my meta descriptions of each EtherHam page and post were getting truncated, often in the middle of a sentence or word. I spent some time on Monday fixing that. It won’t matter to regular visitors, but it does affect what gets picked up by search engines.

There was also a strange issue with some images having a 50% transparent overlay, making them dark and dim. I fixed that, too.

As I was working on these things, I was also reflecting on WordPress. It is a popular and powerful content management system (CMS). But it doesn’t really finish the job. You can set up a website in minutes, but there are a host of things to take care of. I think I’m going to brainstorm a checklist of such things, if only to help me remember to check on them from time to time!

7.5 Random Wire Newsletter Updates

I published my solution to the Arduino UNO Q problem with USB host mode in July 2026. In September, a hardware solution was published: Force USB Host Mode on UNO Q

I’ve not tried the hardware fix, but I added information to my original post as a comment: AllStar on Arduino UNO Q: Part 2

7.6 A New Front Door: TomSalzer.com

This week I gave my corner of the internet a new front door. I converted TomSalzer.com from a bio page to a simple, clean landing page that points to the three things I spend my time on: books, amateur radio, and advisory work. The first book, a field guide for conservation district leaders, is with my publisher now, and a radio book may follow. The radio section points to EtherHam, and the advisory work is something I expect to take on in 2027.

Why did I use my name and not my call sign? KJ7T was assigned to me by the FCC, the agency that licenses radio operators in the United States. I value it, but a call sign is a license, not a legacy. My name will (I hope) last longer.

With this, I also turned on a new email address that matches the tomsalzer.com branding: tom@tomsalzer.com. Replying to this newsletter still reaches me just as it always has.

Building the page turned into a small adventure of its own. It involved a GitHub repository I hadn’t touched in three years, a hosting service that had quietly lost its connection to that repository, and domain redirects dating back to 2012 that still pointed to a page that no longer existed. I also converted an existing paid Google Workspace account to a different domain, and that involved modifying records with the domain registrar. If readers are interested, I may write up the technical side for EtherHam.

8. QRT: End Transmission

A few personal notes…

8.1 Morse Code…Again?

I’m going to try it again. Learning Morse code is what stopped my progression in Scouting. I couldn’t wrap my head around it. I’ve tried several times in my adult years to learn and it just hasn’t landed.

This time around, I’m using podcasts to learn code by ear. I have a couple of keys to practice with and just ordered a Vail adapter for the computer. A Morserino could be in my future, too.

I feel like I’m missing something special by not knowing code…and I can’t know what that is until I learn it and use it. I did get the button add-on with the Vail adapter so that I can practice with a key and headphones — without a computer — if necessary.

All my fingers and toes are crossed for luck this time. As a way to encourage myself, I’ve changed the section separators in the newsletter to Morse code.

8.2 Medical

Those who have been following my wife’s situation will want to know we’ve increased her pain medication to help keep her comfortable. Hospice care continues as her condition slowly trends downward. The times she recognizes me are becoming rarer, making them all the more memorable.

8.3 Stars

I love gazing at stars. When I saw this product — https://us.seestar.com/ — my first reaction was “Oh wow!” This is something that can bring the universe closer for more people. Innovative. And delightful. I hope you get an “oh wow” moment from it, too.

73, and remember to touch a radio every day!

Notice: As an Amazon Associate, I earn from qualifying purchases.

1. QRV: Are You Ready

As I predicted in issue 203, this has been a busy week.

The most exciting news is the Zero Retries Digital Conference is happening today! But I need to be more precise in my description: this is the second annual Zero Retries Digital Conference. The ZRDC team put together a great schedule this year. I truly wish I could be there in person.

2. QST: News and Notices

2.1 M17: OpenRTX v0.4.5 Released

I missed sharing this last week, so here it is: better late than never. From the M17 Project: OpenRTX v0.4.5 released. The GitHub CHANGELOG is at https://github.com/OpenRTX/OpenRTX/blob/master/CHANGELOG.rst

This is a bigger deal than might be suggested by such a brief note. It is great to see M17 continue to steadily move forward.

2.2 M17 Texting Comes to WPSD, Sort Of

This week the M17 Project announced that its WPSD fork now supports SMS. If, like me, you read that, ran an update, and saw nothing change, here’s the backstory.

In July 2025, Jonathan Naylor G4KLX removed M17 from MMDVMHost, the program at the heart of most hotspots, and WPSD dropped M17 along with it. The M17 Project kept M17 alive in its own forks of that code, but the forks gradually fell behind the main code. Jim Ancona N1ADJ has now brought them current. Along the way he got M17’s packet mode working all the way through the chain: radio to hotspot, hotspot to gateway, gateway to reflector, and onto the dashboard. Packet mode is how M17 carries short text messages and other data alongside voice.

But here’s the confusing part: almost nobody can send an M17 text yet. The hotspot software is ready, but the radio has to be able to send SMS, and the OpenRTX developers are still working on that. Some hotspot boards also need new modem firmware. The MMDVM_HS_Hat, the dual hats, and full MMDVM repeater boards can get it now through WPSD’s firmware updater. ZUMspots, Nano hotSPOTs, NanoDVs and SkyBridges don’t have packet-capable firmware yet.

And there’s one more catch. Hotspots built on the ADF7021 chip listen to one mode at a time and rotate through whatever modes you’ve enabled. M17 voice can survive a late start, but a short text message can get lost completely. The M17 Project’s advice is to enable only M17 on your hotspot if you want reliable texting.

When I clicked Update on my WPSD-M17 hotspot, it reported “no updates required” for both the dashboard and the binaries. That puzzled me until I checked the version numbers against the M17 Project’s GitHub. The nightly update had already installed everything a day or two earlier. My dashboard is on the build that adds SMS to the last heard list, and MMDVMHost is on the new v1.0 branch. Nothing looks different because nothing has sent my hotspot a text yet. When one arrives, it will appear in the last heard list as “M17 SMS,” and hovering the mouse over that entry should show the message. My hotspot uses an MMDVM_HS_Hat, so I can flash the packet firmware whenever I’m ready.

All this matters because of the energy keeping the M17 project moving forward. M17 lost its seat in the most popular hotspot software a little over a year ago, and volunteers have kept it going since. This update brings M17 back up to date with that software, and it adds something the other digital modes on our hotspots don’t offer in an open, documented form: text messaging from the radio. The M17 Project’s binaries are now built automatically on GitHub, so future fixes should reach WPSD users faster. It isn’t finished, but every piece needed for M17 texting now exists except the radio firmware.

Read the M17 Project’s announcement: M17 WPSD fork now supports SMS

2.3 Interesting: View HamClock on Your Roku TV

Got a spare Roku TV? From https://github.com/openhamclock/roku-viewer-for-hamclock/blob/main/README.md:

A thin-client Roku channel for HamClock. Roku can’t run HamClock’s C++ engine the way the Android app does (no native code, no WebView), so HamClock keeps running on a Pi / PC / Docker host / Android device and the Roku just displays it and sends remote-control taps.

Unofficial. This is an independent project. It is not made, endorsed or supported by the author of HamClock or by Roku, Inc. It contains no HamClock code; it only talks to a HamClock you run yourself.

2.4 Winlink: RadioMail 2.0 Now Available

Georges WH6AZ wrote in to let me know about the new version of RadioMail: “The goal remains the same: build the best Winlink app for portable operating on iPhone and iPad (and even Mac).”

After many months of development, testing, and feedback from the TestFlight community, RadioMail 2.0 is available on the iPhone App Store.

This isn’t RadioMail 1.x with a fresh coat of paint. RadioMail 2.0 is a completely new application, built from the ground up, based on real world experiences over the past few years.

2.5 Virtualization: VirtualHere

If you — like me — have multiple computers and perhaps want to share one USB microphone with them, you probably thought you needed a USB switch. Well, VirtualHere allows USB devices to be used remotely over a network just as if they were locally connected.

This USB server solution is perfect for allowing USB devices to be used remotely over a LAN network, over the Internet, or in the Cloud without the USB device needing to be physically attached to a remote client machine.

This is a paid application that runs on many different operating systems. Virtualizing the USB cable makes this rather interesting. I haven’t tried it yet, but I will.

2.6 Travel: GL.iNet Mini Dashcams

True, this isn’t radio, but this is good-looking tech from a vendor I trust. I’ve purchased many GL.iNet devices and have not been disappointed. Now comes a pair of small dashcams with suction-cup mounts you can move between vehicles. The smaller of the pair records 2K video, and the larger records 4K. Since I share a work vehicle with others, having a dashcam I can easily stick to the windshield and pop into my bag later is a solution that works for me.

I subscribed to get the launch news. Translation: this dish isn’t fully cooked yet. I anticipate reasonable pricing and good quality, simply because that has been GL.iNet’s style so far.

2.7 John Burwell KI5QKX on RATPAC to talk about 44Net Connect

Join the RATPAC (Radio Amateur Training Planning and Activities Committee) session on Wednesday, October 21 (9 p.m. Eastern / 6 p.m. Pacific), where 44Net Program Manager John Burwell KI5QKX will be giving a presentation on 44Net Connect.

You can catch the presentation at: https://www.ratpac.us/

On that page, scroll down to the table and click the date. (The screenshot below is what the table looks like; the links don’t work in this image.) That will open a Zoom link for the presentation.

2.8 Let’s Encrypt Shortens Free Certificates Again

Let’s Encrypt is shortening the lifetime of its free certificates again. Starting February 10, 2027, every certificate it issues or renews will be valid for 64 days instead of 90, unless the subscriber has chosen one of the even shorter 45-day or 6-day options. Existing certificates won’t be revoked, and Let’s Encrypt expects the last 90-day certificate to expire on May 11, 2027. The 64-day limit is a waypoint, not the end: the default drops to 45 days on February 16, 2028.

You can test this now. The staging environment switched to 64-day certificates on October 14, 2026, and Let’s Encrypt recommends testing there before the change reaches production. If your renewals are automated and your ACME client supports ACME Renewal Info (ARI), you’re probably fine, because ARI has Let’s Encrypt tell the client when to renew. If your renewal is hard-coded to a fixed number of days, change it to renew at about two-thirds of the certificate’s lifetime. For a 64-day certificate, that’s around day 43. Let’s Encrypt suggests searching your cron jobs, wrapper scripts and runbooks for common hard-coded values like 83, 80 or 60.

For hams, this matters to anyone running Allmon3, Supermon, AllScan or another web dashboard behind a Let’s Encrypt certificate. If your setup renews automatically with a current client, you probably won’t notice. If you set up renewal years ago and haven’t touched it since, now is a good time to check it. Let’s Encrypt will also check more often that you still control your domain, so renewals need to be able to pass that check on their own, without you stepping in. Rate limits, ACME endpoints and certificate chains stay the same.

Sources:

• 64-Day Certificate Lifetimes Coming Feb 2027 – Let’s Encrypt

• Let’s Encrypt announces 64-day TLS certificates from February 10, 2027 – Pasquale Pillitteri

• Let’s Encrypt to Cut SSL Certificate Lifetimes to 64 Days in February 2027 – Linuxiac

3. Thank You

Thanks to everyone who reads, shares, and writes in. Your notes and questions shape what ends up in these pages. And thank you to those who buy me a coffee, shop through my Amazon links, or pick up some merch. Every bit of it helps keep Random Wire and EtherHam on the air. Learn more on EtherHam.com.

4. New on EtherHam

This week brings a backup for my documentation wiki, plus a newly installed 8K/16K AllStarLink parrot and some thoughts on why the 8K audio codec isn’t a limitation we must simply accept. I had some late evening fun making the hero images for these articles, too.

The weekly report is a regular feature.

4.1 Three Ways My Wiki Backup Failed

Last week, I built a DokuWiki-based information manager on an external SSD to document my two home networks, and I closed that article by confessing that the only copy of the wiki lived on that one drive. Two days later, I sat down to fix the risk of loss or corruption. Since the wiki is just a folder of text files, I thought: How long could copying a folder take? Five minutes?

Surprisingly, it took most of an hour, three versions of a batch script, and one restore test that fell flat on its face. What I learned is worth sharing, in case this is something you wanted to try. First, the script skipped my lake house NAS entirely, because Windows had quietly marked the mapped drive letter as disconnected. Then the copy to my Portland NAS crawled along over Tailscale, sending a couple of thousand tiny files one round trip at a time. Zipping everything into one file fixed that, and the script finally printed three cheerful OK lines.

I’m glad I didn’t stop there. An untested backup isn’t a backup you can count on. When I unzipped a backup and tried to start it, DokuWiki refused to run, because I’d excluded a few “disposable” folders to keep the zip small, and it turns out DokuWiki has to see those folders. That backup would have let me down at exactly the moment I needed it.

It all works now, and I have three copies: the drive on the rack, a zip at the lake house, and a zip 150 miles away in Portland. “Two is one and one is none,” so I’m finally ahead. The lesson is an old one, but I got to learn it fresh: a backup you haven’t tested is really just a hope. The full story, with the working script and a step-by-step setup guide, is on EtherHam: Three Ways My Wiki Backup Failed

4.2 Why AllStarLink Still Uses a 1962 Telephone Standard

This was an enjoyable article to research and write, especially because I gained some insights into how creative minds work.

When I set up my own Ampersand-ASL parrot (more on this below), I asked myself a question I couldn’t immediately answer: why is standard AllStarLink audio still limited to 8 kHz when the radios and computers on both ends can do far more?

I expected to find an old protocol that couldn’t be changed — some kind of locked-in limitation. I was wrong. The 8 kHz rate goes back to Bell engineers who, in 1962, picked 8,000 samples per second to squeeze voices down copper phone lines. That choice became part of the G.711 telephone standard, then Asterisk, and then Jim Dixon’s app_rpt code that AllStarLink is built on.

Somewhere along the way, what was a sensible telephone default turned into something most of us assumed was a hard limit…but it turns out it wasn’t. IAX2, the protocol nodes use to talk to each other, was never restricted to 8 kHz. An old Asterisk header file had even reserved a code for 16 kHz audio, though it never made it into the official documentation.

Bruce MacKinnon KC1FSZ found that unused path and put it to work in Ampersand-ASL, his built-from-scratch AllStarLink application with no Asterisk inside. The project calls that 16 kHz audio “ASL-HD.” The clever part is that nothing breaks. An Ampersand node offers 16K audio first and falls back to standard 8 kHz if the other node doesn’t support it, so no one else has to upgrade anything.

What stayed with me wasn’t just the innovative code. It was that Bruce questioned a limit the rest of us had stopped noticing. The full story, including how a 1960s phone decision ended up on our nodes, is on EtherHam: Why AllStarLink Still Uses a 1962 Telephone Standard

4.3 Raising My Own Parrot

A parrot is the simplest test in AllStarLink. You connect, key up, say a few words, and it plays your audio back so you can hear what everyone else hears. Bruce MacKinnon KC1FSZ wrote a better one as part of his Ampersand project. It reports your codec, whether your node is registered, and your audio levels, with a plain-language rating.

When Bruce’s public parrot went quiet, I lost my only way to hear the 16K wideband audio described in the item above, so I decided to build my own. It’s now on the air as AllStar node 578492, running in a small Debian 13 container on my Proxmox server.

The build had a few snags. Bruce’s install packages now return “403 Forbidden,” so I compiled the parrot from source instead in a Proxmox LXC (Linux Container). Luckily, the voice files it needs could still be downloaded. Once it was installed, I backed up the whole container, so I can restore a working parrot even if those files disappear. It’s a quiet reminder that when one person maintains a project, it’s smart to keep a copy of the pieces you rely on.

My parrot earned its keep the same morning. My very first test call came back full of noise, which turned up a problem at my station that I didn’t know I had. Later, my Ampersand node on the Arduino UNO Q connected at 16K, but my push-to-talk did nothing. The cause was a USB cable I’d moved to a different port, and the software was still looking for it at the old port address. Once I fixed that, I heard myself clearly in wideband audio (click here to find an audio clip on EtherHam).

My parrot (AllStar node 578492) is open to any AllStar node, whether it’s a standard 8K node or an Ampersand node running 16K audio. Please give it a try, with the understanding that it’s a personal node, not a guaranteed service. The full story, plus step-by-step instructions for building your own, is on EtherHam: Raising My Own Parrot

If you try the parrot, I’d appreciate feedback: EtherHam@pm.me

4.4 Weekly Report

Every week, I publish a weekly report on EtherHam. It starts with the Short Stack, a curated list of links from more than 90 ham radio, tech, and space feeds. Then come band conditions from NOAA and SIDC, a Digital Radio News roundup of the week’s code commits and forum threads across DMR, D-STAR, YSF, M17, AllStar and more, and a digest of the busiest Groups.io lists. AI helps gather and summarize the material, and I review it all before it goes out. Find this week’s report is here

5. In The Lab

5.1 Search Links You Can Share

The Random Wire search page at etherham.com/rw_search/ picked up a small but useful upgrade this week. The search now lives in the page’s web address, not just in a form field on the web page, which means a search can be shared as a link. You can click a link like https://etherham.com/rw_search/?q=%22QSO+One%22 and the page opens with the results for “QSO One” already loaded, with no typing required. You can narrow things down by year or post type, too. For example, adding &year=2025 limits the results to issues from 2025.

A single word search looks like this: https://etherham.com/rw_search/?q=AllStar

I made this change for a practical reason. When readers email me asking whether I’ve ever written about a particular radio or project, I can now run the search, copy the address from my browser, and paste it into my reply. That’s faster for me, and it lets them see every relevant issue at once rather than the one or two I happen to remember. The same trick works for you: run a search, copy the address from your browser’s address bar, and you have a link you can bookmark or pass along to a friend.

If you publish your own newsletter on Substack and want a search page like this one, the code is free and open source at github.com/EtherHamRadio/substack-search. The README now explains how these shareable links work.

5.2 AllStar: One Name, One Front Door

This week, I typed 578494.nodes.allstarlink.org into my browser, expecting to reach my DVSwitch+AllStar node. Instead, what appeared was the landing page for node 588418, a different node at the lake house.

Nothing was broken. AllStarLink gives every registered node a hostname in that format, but the hostname points to an address, not to a particular machine. When a node registers, the AllStarLink servers record the public IP address the registration came from…and every node behind my home router registers from the same public address.

So every lake house node name leads to the same front door, and my router decides who answers. I have port 80 forwarded to 588418, so 588418 answers for all of them. Node linking isn’t confused by this, because AllStarLink also publishes each node’s IAX port (the port nodes use to connect to each other), so several nodes sharing one address can each have their own port. Web pages can sit on other ports, too, but nothing in AllStarLink’s DNS tells a browser about it. A browser looks up only the address and knocks on port 80, so reaching a node’s page on any other port would require typing that port into the URL yourself.

The lesson is that only one node per public address can answer at its plain node name, and the web pages of every other node behind that address stay hidden from the internet unless I deliberately forward a port to them. That got me thinking about which of my nodes need to be public at all. My hub node 588416 does need to be public, and I hardened it accordingly, as I described in Putting fail2ban on Allmon3 and AllScan, and the Bug That Bit Back. Most of my other nodes don’t need to be public.

If you don’t want people knocking on your node’s door, you don’t have to give them a door. Consider keeping the web ports closed to the internet, reaching your Allmon3 or AllScan pages over Tailscale instead. Tailscale is a private network service, free for personal use, that links your own devices to each other from anywhere, encrypted, without opening a single port on your router.

5.3 Setting AllStar Node 588416 to Automatically Power On

As noted last week, and in Putting fail2ban on Allmon3 and AllScan, and the Bug That Bit Back, I needed to configure my AllStar node 588416 to automatically boot up after a power loss. I did that last Sunday, hauling a spare monitor, a DisplayPort-to-HDMI cable, and keyboard with me to Portland. This is one of the few times when getting a shell into the machine doesn’t cut it. You have to be physically connected to a monitor and keyboard to do this work.

So I powered up my Dell OptiPlex 7050 SFF computer and began rapidly tapping the F2 key. That opened the BIOS settings, where I changed the power management setting and rebooted.

Then I shut down my Synology DS220+ and AllStar node 588416 before powering off the old APC Back-UPS 450 uninterruptible power supply. I took that out of the system, replacing it with a new CyberPower CP1000AVRLCD, from their Intelligent LCD line, rated 1000 VA / 600 W. It is substantially heavier than the old APC! The little APC I could grip and lift with one hand. Not so the CyberPower. If weight = capacity, this is a big step up.

After powering up the DS220+ NAS and giving it a few minutes to get settled, I enabled the UPS server in the NAS settings. Then I installed nut-client on node 588416 and enabled it as a service.

That’s done. Here’s the summary:

DS220+ (DSM 7.4.1)

• UPS connected by USB; UPS type: USB UPS

• Standby: Until low battery

• Shut down UPS when the system enters Standby Mode: on

• Network UPS server: enabled, with 588416 as the only permitted IP

• Email alerts through the Synology Account at Warning level (battery mode, low battery, UPS disconnected)

• Restart automatically when power returns: on

Node 588416 (Dell OptiPlex 7050 SFF, Debian 12)

• BIOS AC Recovery: Power On

• BIOS POST Warnings and Errors: Continue on Warnings and Errors

• BIOS Keyboard Errors: Disabled

• NUT client (nut-client 2.8.0) in MODE=netclient

• MONITOR ups@<NAS address> 1 monuser secret secondary, connecting over Tailscale

• nut-monitor service enabled at boot

5.4 Net Summary: “Let’s Talk Digital”

I used my net logger to capture the Let’s Talk Digital net carried on the Kansas City Wide Network on Thursday, October 8th, then processed the transcript through Gemini.

This was a well-attended net. At one point, I saw 102 stations logged into netcontrol.live (but there may have been more), which doesn’t include those connected over RF. If you are interested in digital radio, the Let’s Talk Digital net is worth putting on your list of regular nets.

Net Information & Dashboard

• Net Name: “Let’s Talk Digital”, hosted every Thursday at 8:00 PM Central by the Colorado Digital Team.

• Websites & Resources: Colorado Digital reflector/dashboard (dash.coloradodigital.net) and Kansas City Wide (kansascitywide.com).

• Net Control Logging: Uses netcontrol.live (an open-source upgrade of ham.live adapted for Ham and GMRS).

• Topics Covered: VHF/UHF digital modes including D-STAR, DMR, System Fusion/Wires-X, P25, NXDN, M17, EchoLink, AllStar, and hotspots.

Key Technical Discussions

• Yaesu FTX-1 Field Radio & Wires-X: Chris (KB2IDX) shared his experience testing the FTX-1. He confirmed it can host its own Wires-X room/node over a simple USB-C connection to a PC without needing a secondary radio, provided it runs user software version 2.01. Bucky (W0SUN) noted this is also used on the upcoming DR-3X repeater featured on HRO’s catalog cover.

• AllStar Link Authentication Updates: Based on Tom’s (KJ7T) Random Wire newsletter, AllStar Link (ASL) is phasing out unauthenticated WebTransceiver (WT) and legacy IAX2 logins in favor of secure token-based authentication. Testing begins in mid/late October, going live in November, with legacy compatibility options being retired over the following 6–12 months. Third-party applications (like M1KE and QSO1) will require firmware and software updates.

• M17 Support in Hotspots: Matt (AJ6LX) asked about M17 hotspot support. Chris and Bucky noted that while WPSD dropped M17, original Pi-Star still supports it, and specialized M17 software images/hats are available at m17project.org/WPSD.

• Wires-X to DMR/MMDVM Bridging: Ty (NJ8X) asked about bridging Wires-X to DMR. Bucky advised using dedicated hardware (a dedicated Wires-X node radio tuned to the same frequency as a dedicated hotspot/RF bridge) or using multi-protocol reflectors with a transcoding server to ensure stable audio levels and avoid local interference.

• QSO1 Software & D-STAR Transcoding: Frank added experimental D-STAR and P25 support to QSO1. Bucky explained why D-STAR transcoding is difficult. D-STAR relies on proprietary AMBE1 hardware chips, while DMR, Fusion (C4FM), and P25 use AMBE+2. That mismatch makes cross-mode transcoding complex without hardware vocoders, such as AMBE USB sticks or servers. [Editor’s note: P25 Phase 1 uses the IMBE vocoder; only P25 Phase 2 shares AMBE+2 with DMR and Fusion. — KJ7T]

Announcements

• Zero Retries Digital Conference: Marty (K1NP) announced the event taking place on October 16 in San Ramon, CA, with a Zoom registration option available via zeroretries.org.

Post-Net Troubleshooting

• FT-991A & Hotspot Issue: Dirk (W4IPD) reported his FT-991A cannot transmit to his hotspot on C4FM, though his FT-70D works fine. Suggestions included moving the hotspot farther away to avoid overwhelming the receiver with 5 Watts, checking for frequency offset/duplex errors, separating hotspot frequencies, and running a Bit Error Rate (BER) test.

5.5 Surprised to Reach My Home Machines From a Hotel

On Wednesday morning, in a hotel meeting room 60 miles from home, I opened a browser, hit a saved bookmark with the local address of a computer on my lake house network…and it answered.

Let’s just pause on that for a moment. I had not opened a port on my home router to that machine, or set up a dynamic DNS name, or configured a VPN server. The machine at home thought the request came from inside the lake house. The service that makes this possible is Tailscale, which I mentioned above. If you manage radio gear or computers in more than one place, it’s worth knowing about.

At its core, Tailscale builds a private network — called a “tailnet” — with only the devices you choose to connect. You install a small app on each one: your laptop, your phone, a Raspberry Pi running an AllStar node, a NAS. Then you sign in with the same account. Each device gets its own private address, and from then on they can all reach each other as if they were plugged into the same switch, no matter where they physically are. The traffic between them is encrypted with WireGuard, a modern, fast VPN protocol that’s well regarded in security circles.

The clever part is how the devices find each other. A traditional VPN needs a server at home with a port open to the internet, which means touching your router’s port forwarding settings and accepting some exposure. Tailscale skips that. Each device reaches out to Tailscale’s coordination service, which tells the devices how to contact one another. They then punch a direct connection through whatever routers and firewalls are in between. If a hotel or campground Wi-Fi network is too locked down for that, the traffic goes through one of Tailscale’s relay servers instead. It’s a little slower but still encrypted end to end, so the relay can’t read it. This even works behind the carrier-grade NAT (“CGNAT”) used by many cellular, fixed wireless, and satellite providers. With CGNAT, ordinary port forwarding isn’t possible, though in that case the traffic often goes through a relay and runs a bit slower.

What surprised me that morning was a feature called a subnet router. Using a subnet router, I didn’t have to have Tailscale installed on every device. One always-on machine at home, in my case my Proxmox server, can announce to the tailnet, “I can reach everything on this local network.” Your laptop then sends any traffic for those home addresses through the encrypted tunnel to that machine, which passes it on to the local network and relays the answers back. Printers, network switches, radios with web interfaces, and old gear that could never run Tailscale itself all become reachable from anywhere, at the same addresses you use at home, over a WireGuard tunnel.

For hams, this solves a lot of everyday headaches. I administer a router in Portland from 150 miles away, check on AllStar nodes, read logs, and keep monitoring pages that I never want exposed to the public internet. None of it requires opening a single port. If you’ve ever wanted to check on a remote station, manage a hotspot at a club site, or reach your shack from the road without turning your home network into a target, Tailscale is the easiest way I’ve found to do it.

5.6 A Few Changes to My Wiki

As described in A Wiki That Lives on the Rack, I’m using DokuWiki on a Stick to help document my home networks:

I’ve added “General runbooks” with how-to guides for things that don’t live on just one LAN. Under Shared, I’ve added a compendium of Devices. And as a visual reminder, I included a photo of the actual Lexar SSD device the wiki lives on.

I made this system a little too granular, which makes it too complicated, so I’ll probably refactor the pages in the next few weeks to simplify the workflow.

5.7 Understanding Capacitors

Finally, a simple set of explanations on how capacitors work. This Nuts & Volts article, Understanding Capacitors, made things much clearer for me.

But capacitors? What could they possibly be good for with that gap between their conductors? How could current flow through such a thing? What were these for? Even today, when I look at a complicated schematic, the placement of capacitors always intrigues me the most. The purpose of this article is to give you a few points that have helped me to finally understand come to terms with, these ghastly components.

6. QRT: End Transmission

Sometimes the AI Isn’t Very Smart

Hey Claude, how can I add a comment form to a WordPress page? I thought the answer would be simple, but several paragraphs later, I stopped the process. What was presented to me involved creating a new page template and copying/modifying page layouts. No. That went too far. So I stepped outside of the Claude-verse and did a simple online search. It turns out there’s a simple setting in WordPress for a comment form to be open (available) or closed (invisible) on a page. Boom. And this is accomplished without having to monkey with custom page templates. Which page? This experimental recipe page: https://etherham.com/recipes/mikrotik-44net-allowlist/

I hope this hodgepodge of amateur radio and tech proved interesting. If you learned one new thing, I’m happy.

73, and remember to touch a radio every day!

Notice: As an Amazon Associate, I earn from qualifying purchases.

1. QRV: Are You Ready

It’s been a full week. Last Friday, issue 202 published. That same day I dove into using fail2ban to help block login attempts to my Allmon3 dashboard and the AllScan favorites management tool. Along the way, I discovered a bug in Allmon3 that had been fixed and then resurfaced in a later change. That bug is fixed now.

Sunday, I made a long day of it with an early morning drive to Portland. Driving Interstate 5 is not nearly as bad at 5 am on a Sunday morning, compared to the rest of the week. It felt relatively peaceful. While there, I packed up my old WiRES-X station and brought the bits to the lake house. That resulted in a write-up about getting my WiRES-X station back online. I chose to stay on version 1.57 for compatibility with legacy rooms and nodes, and to avoid some known operational issues with version 2.x.

One of the issues I ran into in Portland was bringing my network back online. That story is in this newsletter. It revealed to me that my documentation of my own network was so poor that it took longer than it should have to get things running right again. So on Monday and Tuesday, I built a simple wiki system for tracking my gear and connections. It runs off a USB device for portability. I wrote that up in case you want to try something similar.

When Wednesday dawned, I could feel my newsletter deadline looming, so it was time to stop playing with tech and finish writing issue 203 of the Random Wire! While I did that, I had my WiRES-X node running right beside me, catching some traffic from the Kansas City Wide network and the local Yaesu System Fusion repeater.

Next week, I have two all-day meetings. One is in Silverdale, Washington and the other is in Vancouver, Washington. Add in a day trip to Portland and it means I’ll get no writing done on Sunday, Tuesday and Wednesday, so expect a lighter Random Wire newsletter in issue 204.

2. Notices

2.1 It’s World Space Week!

World Space Week ends tomorrow. I missed alerting you to it last week, and it seems silly to bring it up now. But for those of us interested in space topics, it’s good to be aware of this. Mark your calendar for next year!

2.2 RadioID to Begin Verifying Numbers

Find the full notice at https://radioid.net/

I recommend everyone log onto RadioID and see if your account is now “due for annual review.” Mine was. It was a multi-step process to verify information, and the prompts are a little confusing. Even though I wasn’t deleting anything, I had to check the box that said I understood what it meant if I was deleting something. On the plus side, it was all self-certification, so it only took a few minutes.

Thank you to Jeff for sharing this.

2.3 Search for Random Wire Content

Reminder: you can search the Random Wire newsletter history on EtherHam at https://etherham.com/rw_search/. This is a custom archival system that takes my exported data from Substack (the entity that hosts the Random Wire) and pushes it to a database on EtherHam. Someday, I’ll find time to properly index my content. For now, at least there is search.

2.4 Zero Retries Conference is October 16

Live Attendance via Zoom: Price $45.00

The ZR team writes:

We have hired an AV team to provide a live feed into the conference so that people can be part of the live conference without being there. The URL will be sent a few days prior to the conference and a link to download the materials.

Click here to register.

2.5 AllScan Web App Updates

The release notes tell the tale: version 1.02 added a touchscreen option and 1.03 fixed one issue with it. The touchscreen is a pretty big deal, in my opinion. If you run AllScan on a tablet or phone, it makes a real difference in usability.

v1.03 2026-10-07
Fix issue in TouchGUI where it would not use the favorites file selected in the main GUI. Add check to ignore duplicate node entries in favorites files.

v1.02 2026-10-03
Added a new touchscreen / small screen optimized GUI that can be accessed by clicking/touching the “TouchGUI” link in the header links at the top of the page. To then exit the TouchGUI just click/touch the AllScan link at the top left. Thanks to Ben WY2K for this contribution.

Once updated, you’ll see version 1.03 on the left side of the top bar, and over to the right, you’ll find the new TouchGUI option.

In the side-by-side view above are two views of my phone screen. The left view is the standard AllScan interface. The right panel is the new TouchGUI. Now imagine you are walking or driving. Which interface seems easier to use? For me, the big touch buttons are far easier on a small device.

3. Thank You

Jonathan and Marty, thank you for the coffee! It seems as if my world runs on caffeine, so this is much appreciated.

4. New on EtherHam

4.1 Getting My WiRES-X Node Back Online

Months ago, the computer that ran my WiRES-X system in Portland died. This week, I finally got around to replacing it. As part of that process, I moved it to the lake house and got it set up there. I’ll add a bit more below, but if you want to jump straight to the full story, visit Getting My WiRES-X Node Back Online, on EtherHam.com.

When looking for a new computer, I knew I wanted small, inexpensive, and capable enough to run the WiRES-X application. I read several reviews before I ordered a GMKtec NucBox G10, and I think the tradeoffs are reasonable for a WiRES-X platform. Here is one of those reviews: GMKtec NucBox G10 mini PC review.

This budget model PC uses DDR4 memory, not the more modern and faster DDR5 RAM. What this means is the available bandwidth for the CPU is effectively reduced. And since the GPU shares main memory, video performance is also impacted by the use of DDR4. But none of that matters much for WiRES-X on Windows 11.

I do have to say that when I went shopping, I quickly discovered there are no good deals anymore on new computers. A few years ago, you could score a solid little computer like this for a few hundred bucks. Not today, it seems!

To redirect the audio from the radio speaker more toward me, I made a temporary shroud from a margarine container. It looks odd but works fine, pushing the audio toward my ears instead of to the entire room. Read the story in Getting My WiRES-X Node Back Online, on EtherHam.com.

4.2 Putting fail2ban on Allmon3 and AllScan, and the Bug That Bit Back

I started working on hardening a few of my AllStar nodes, and one of the first things I did was to implement fail2ban for Allmon3 and AllScan logins. Usually, you see fail2ban used to jail unruly folks trying to break into your SSH port. But it can do more, and I was eager to try this.

What I thought would be a simple fail2ban setup for node logins revealed an unexpected surprise: a password leak. I privately reported the issue, which was resolved the very same day. If you saw a version change in your Allmon3 package to 1.11, that’s the fix.

Read all about it in Putting fail2ban on Allmon3 and AllScan, and the Bug That Bit Back, on EtherHam.com.

4.3 Documenting My Networks with a Wiki

I wanted a way to document my network topology, equipment, and all the other details one must remember — including why I picked certain things and what they were expected to do. The system had to be simple. I’ve tried network scanners and complicated, SQL-based systems. No thank you. My solution needed to be a flat-file system I could take with me, something I could read even if the software died.

I settled on DokuWiki on a Stick, installed on a Lexar external device. The wiki is beginning to take shape.

The catalyst for this was a power loss at the Portland QTH. As I worked on recovering my network, I discovered that my records were not complete. I had to dig more than expected to find information, and that cost me a few extra hours of work. I realized that centralizing much of this information in one place would be helpful, so I started thinking about how to do that.

And I’m starting to put how-tos into the wiki because frankly, I’ve got so many different devices and ways of doing things, I’m forgetting important steps.

Read the write-up in A Wiki That Lives on the Rack.

4.4 The Weekly Report

Jump to your favorite section:

• Short Stack from the Interwebs

• Band Conditions

• Digital Radio News

• Groups.io Digest

Or click through for the full report: Weekly Report: October 8, 2026

5. In The Lab

5.1 Recipes at EtherHam.com?

A reader suggested taking some of the content on EtherHam and making it more succinct. I have to admit I do get wrapped up in the storytelling sometimes, so I can certainly understand the desire for more concise, step-by-step instructions.

I’m testing that idea with information about the 44Net allowlist I added to my MikroTik router, and I’m calling it a recipe. Personally, I like the recipe idea. We can all relate to it, and it sounds a lot less daunting than “installation procedures” and similar descriptors.

Find the first recipe at: https://etherham.com/recipes/mikrotik-44net-allowlist/

Take a look and let me know how this lands with you. Thumbs up? Thumbs down? Let me know with a comment or email me at etherham@pm.me.

Leave a comment

5.2 Changed at EtherHam.com

I run a bot blocker at EtherHam.com because I don't want the overhead of bots constantly crawling the site. This week I made one exception: ChatGPT-User. Unlike a crawler, it only visits a page when a person asks ChatGPT to read it. So now people can have ChatGPT read and cite EtherHam articles, while OpenAI's training crawler stays locked out. That seems like a reasonable balance to me.

5.3 AllScan Fix: Favorites Files Now Work Across Nodes

I have more than one AllStarLink node, and I wanted them to share the same list of AllScan favorites. AllScan stores favorites in a file called favorites.ini, so I copied that file from one node to another. That’s when I hit a problem.

The favorites.ini file can group favorites under a heading for a specific node number. My copied file had a heading for the node it came from. When I used Add Favorite on the new node, AllScan added the new favorite to the end of the file, which put it under the other node’s heading. AllScan only displayed favorites for the node it was running on, so the favorite I had just added never appeared.

I shared this with David Gleason NR9V, the author of AllScan. He fixed it within days. AllScan now reads the favorites under every node heading in the file and merges them into one list. As David put it, favorites files “ideally should be interchangeable between various nodes.” If you want different favorites on different nodes, he suggests keeping a separate favorites file for each node instead.

If you upgrade AllScan (the latest version is 1.03), it should bring in that fix.

Thanks, David, for the quick turnaround.

5.4 WA7ABU Tech Net (Tuesday)

I listened to the WA7ABU tech net at 10 am Pacific last Wednesday, October 7th. This net has a regular group of participants who have technical proficiency in many aspects of amateur radio. I learn something new every time I tune in. Here’s a glimpse of some of the content discussed in just this one net.

Net Schedule & Repeater Info

Meets weekdays from 10:00 AM to 11:00 AM PDT on 145.290 MHz (Alternate: 145.190 MHz, CTCSS 100.0 Hz) via the WA7ABU repeater in Oregon’s Mid-Willamette Valley. Linked via AllStar (Node 543260) and EchoLink (WA7ABU-R).

Technical Discussion Highlights

• Digital Voice Modes & Vocoders:

  • The group discussed the differences between hardware vocoders (such as the AMBE-3000 chip used in DMR, D-STAR, and System Fusion) and software codecs.

  • Brett (KG7GDB) and John (K7JCD) noted that AMBE chips analyze speech and model a simulated vocal tract on the receiving end, which often yields a distinct “robotic” voice quality and discards original audio data.

• FreeDV & The RADE Codec:

  • Discussion centered on recent ARRL/QST coverage of FreeDV and the new RADE (Romeo Alpha Delta Echo) auto-encoder. RADE uses machine learning/AI techniques to train an encoder/decoder pair over Orthogonal Frequency Division Multiplexing (OFDM) parallel carriers. [KJ7T comment: RADE stands for Radio Autoencoder. Like AMBE, it is a vocoder system. It sends a compact set of speech features (pitch, spectrum, voicing) rather than the original audio, and the receiver synthesizes the voice from them. RADE’s advantage is better speech quality and robustness on HF, not lossless audio.]

  • Unlike AMBE, software codecs like RADE compress audio without discarding voice information, delivering clearer, more natural SSB-width voice without squelch crashes or background hiss. [KJ7T comment: not quite. As noted above, RADE is lossy, like AMBE.]

• Web Apps & M17 Project:

  • Rogene (K7OLI) shared information about K1FM’s web application that integrates Icom CAT control with browser-based digital voice streaming.

  • Dan (W3HDB) brought up M17, an open-source digital protocol using Codec 2. Nate (N8NAT) mentioned recent community discussions regarding hotspot support and open-source emulation efforts.

• AllStar & Hotspot Bridging:

  • Nate (N8NAT) detailed his homemade dual-antenna MMDVM setup on a Raspberry Pi 4, bridging digital modes to AllStar using CPU emulation rather than a physical AMBE chip.

This content was captured on my AllStar node 588416 using an AI-assisted net logging system. The transcript was then processed through Gemini AI to help summarize and improve readability. The Gemini output is what you see in the bullet points above.

6. QRT

Throw a Breaker, Break the LAN

Last Saturday afternoon, a maintenance worker was in my Portland apartment to repair some plumbing and “heard a tone,” said his report. I was 150 miles away at the lake house. He didn’t know where the sound was coming from, so he did the sensible thing from his point of view: he switched off the circuit breaker for that part of the apartment. The tone stopped. So did my entire home network, once the battery in my uninterruptible power supply (the battery box that keeps equipment running through short outages) ran out.

Watching from the lake house, everything went dark at once. My security cameras were not on the UPS, so they went dark instantly. As soon as the UPS battery bank died, AllStar node 588416 dropped off the network, and so did the MikroTik router that connects it to 44Net, as well as the GL.iNet router that serves my home LAN. Every remote path I have into that rack runs through those routers, so from where I sat, it looked like one of them had died.

When I got to the apartment Sunday morning and switched the breaker back on, the routers came right back up. The GL.iNet Flint 2 connected to Xfinity and the MikroTik router reconnected to the 44Net server in Dallas. The Synology storage box, the Mac Mini running my packet BBS, and the Wyse thin client running node 578493 all restarted on their own too.

However, node 588416 didn’t come back up. It sat there dark, because I had never set the computer's firmware (the BIOS) to power on automatically after a power loss. I figured the UPS had the loss-of-power situation covered. But the UPS covers short outages, not long ones, and this one lasted longer than the battery. One press of the power button and the node booted up and registered with AllStarLink. It became reachable from the internet about 18 hours after it went down.

During the several hours I was at the apartment, I did not hear the sound the maintenance person heard. It’s possible it was a warning chirp from the UPS, which could occur if the load on the system was too high. Then again, a UPS on battery usually beeps more, not less, so that theory has a hole in it.

I’ve temporarily removed a couple of devices from the UPS. The old UPS has remained silent. The one sound my security camera caught afterward turned out to be a wall being bumped next door, not a beep. The camera now records audio, so if it happens again, I’ll have data instead of an “I heard something” report.

Two changes come out of this:

• First, every machine in that rack now gets checked for the power-on-after-outage setting. Node 588416 gets it on my next visit, once I bring an adapter for its DisplayPort-only video output.

• Second, I’m replacing the small APC Back-UPS 450 with a CyberPower CP1000AVRLCD (this is an affiliate link), the same model I use at the lake house. It has more than twice the capacity, and its display shows the load and estimated runtime at a glance. I’ll configure it to cleanly shut down node 588416 if the power is lost for more than ten minutes.

The lesson for me: the UPS was the safety net I thought was rock solid, and the BIOS setting was one thing I forgot. An outage can come from a neighborhood power failure as easily as from a maintenance worker, and each device has to be able to come back on its own when the power does. Otherwise, the safety net has a big hole in the bottom of it.

73, and remember to touch a radio every day!

Notice: As an Amazon Associate, I earn from qualifying purchases.

This is breaking news…but let’s hope it won’t break AllStar!

If you use an app to connect to an AllStar node from your phone or computer, without a radio or a node of your own, the way that connection gets approved is about to change. On September 25, the AllStarLink team announced that it will retire WebTransceiver authentication. A new App Authentication standard, called ASL002, will replace it.

What WebTransceiver Is (and Isn’t)

The name comes from a Java applet that once let a web browser talk to AllStar nodes. The applet was retired long ago, but its login method survived. It became the standard way apps such as DVSwitch Mobile, Repeater Phone, Transceive and QSOone get onto the network. The ASL team calls this “nodeless” access: you connect as a user with an AllStarLink account, not as a node.

WebTransceiver isn’t a separate mode. It uses IAX2, just like every AllStar connection. IAX2 is the voice-over-IP protocol that AllStar nodes use to talk to each other. What’s changing is how a node decides whether to let an app user in.

Why Change It

The ASL002 document is blunt about it: the old method has “no session security of any form.” Its login tokens also weren’t built to be unique, so in principle two different logins could look the same to the network.

How the New System Works

Under ASL002, your app will send your AllStarLink username and password to an ASL server once. The server sends back a token that works like a single-use ticket, good for 24 hours. When the app connects, it gives the node that token along with your call sign. The node checks the ticket with the ASL server, and the server cancels it so it can’t be used again. Your password never goes to the node itself.

The server will also limit how fast any one app or address can request tokens, which makes password-guessing attacks harder. Each app install can hold at most three unused tokens at a time.

For app users, the change should be mostly invisible. You’ll still log in with a username and password. You’ll need an updated version of your app once its developer adopts the new standard.

What Node Owners Need to Know

If you run a node that accepts app connections, this part applies to you.

ASL3 nodes (the current AllStarLink release): a package update is expected to make a one-time automatic change to /etc/asterisk/extensions.conf, the file that tells Asterisk how to handle incoming calls. However, if you’ve customized the [allstar-public] section of that file, you’ll want to check it after the update instead of assuming the automatic fix worked. I’ll be checking my nodes after the update.

Pre-ASL3 nodes: operators will need to edit extensions.conf themselves before the transition period ends if they want to keep accepting app connections. The ASL002 document includes the new configuration lines.

Unknown at this time is how HamVOIP nodes may be affected. That was not part of the announcement.

My thoughts: ASL writes standards for software it maintains. It can't say how HamVOIP will behave because it doesn't control HamVOIP's code or release schedule. Like pre-ASL3 AllStarLink nodes, HamVOIP runs a much older version of Asterisk (1.4-era). The new configuration lines ask Asterisk to check each app user's token with an ASL server over the web, then read the first few characters of the server's reply. There's no word yet on whether those lines have been tested on older installations, whether HamVOIP or pre-ASL3 AllStarLink.

The Timeline

• Now through October 2 (yes, the day this newsletter is published): the “fatal flaw” review period (the announcement doesn't specify a time or time zone). Questions and concerns go in the forum thread.

• Mid-to-late October: the new login service is expected to be available for testing.

• First or second week of November: expected to go live. ASL says a formal announcement will follow.

• About six months after go-live: the old WebTransceiver login is scheduled to retire, along with most of the older compatibility options.

• About a year after go-live: the last compatibility option, which lets older nodes accept connections from updated apps, is scheduled to end.

The standard is still a draft, and some of the server addresses in the document are placeholders. Details could change before November.

I expect to write more about this change as the important dates get closer.

Read more: the announcement on the ASL Community forum and the ASL002 App Authentication standard on GitHub.

1. QRV: Are You Ready?

I put the AllStar story ahead of QRV because it's breaking news that matters to a lot of AllStar users.

There is a lot of computing content in Random Wire issue 202. That tracks with the nature of digital radio. I finish up the four-part series on 44Net by adding a second firewall to my system (The Third Tent Stake: A Router That Says No First).

I also recap last weekend's M17 net because it was packed with great information (M17 Next: A $60 Radio, a Linux HT, and Data on the Way). There is a lot happening behind the curtain, and it’s all positive. I also started working on the CC1200 HAT for M17, with a note below (Working on CC1200 HAT for M17). Expect a thorough article soon.

Then I moved my Proxmox server containers from a small i7-powered PC to my large Lenovo P510 ThinkStation machine with a 14-core Xeon processor (A Bigger House for the Homelab). It's not the cheapest computer to run, but I keep it around because it is such an incredible workhorse.

Finally, the Weekly Report captures a lot of information in one place.

2. Thank You

Thank you to Brian, who wrote: “A few coffees to help you write Part 4 on 44 Net/Mikrotik.” The coffee helped, article is done (see 3.1 below)!

3. New on EtherHam & Random Wire

3.1 The Third Tent Stake: A Router That Says No First

This is the fourth article about putting AllStar node 588416 on 44Net. Part 1 raised the tent. Part 2 and Part 3 drove the first two stakes. This one drives the third: an allowlist on the MikroTik router, so that new connections arriving over the 44Net tunnel are filtered, reaching my machines only on the ports they actually serve. Everything else is dropped at the router, before a machine’s own firewall ever sees it.

The router’s log turned up two surprises. About 980 connection attempts arrived in the first eleven minutes, most of them aimed at addresses in my block that I assumed were empty. And one of those addresses wasn’t empty: it was my packet BBS, which the new rule had just cut off from the internet. The article covers how I found it, how I fixed it, and why the identical spare router I keep on the shelf turned out to be out of date, too.

The big takeaway: before you build a firewall allowlist, ask the router what’s connected. It already knows, and asking takes two easy commands. Read about it at: The Third Tent Stake: A Router That Says No First.

3.2 M17 Next: A $60 Radio, a Linux HT, and Data on the Way

M17’s hardware has lagged behind its protocol. That’s starting to change. The Retevis C62, an inexpensive FM handheld, is on the way to running M17 with a firmware update and no hardware mods. It’s early days: transmit works, but receive and saved settings are still being finished, and the firmware is waiting for review in OpenRTX pull request #510. Close behind is the LinHT, which uses the same C62 case but puts a full Linux computer and a software-defined radio inside. That means it can learn new modes after you’ve bought it.

There’s more. OpenRTX 0.5 is expected before the holidays and will bring text messaging and APRS to M17 radios people already own. Codec 2 got a big speed boost, old DVMega hotspots can move to M17, and an Oklahoma club has converted a multimode MMDVM repeater to carry M17 alongside its other modes. And because every piece of this is open (the protocol, the codec, and the firmware), no single vendor gets to decide where it goes next. Read the full article on EtherHam →

3.3 A Bigger House: Proxmox Server Moved to a ThinkStation

My Proxmox server has been living on an old i7 desktop with a single drive and a UPS it had never been configured to talk to. When I looked at the logs, I found it had been through 127 unsafe shutdowns!

This week I moved everything to a refurbished Lenovo ThinkStation P510 that had been sitting under my desk. This platform was made and marketed as a workstation but it serves quite well in the role of a home server.

My objective was to make each container’s move completely transparent: it would retain its number, network address, and data, so everything else on the home network would continue working as if nothing had changed. Before I could start, though, I had to break into my own computer. I’d installed Ubuntu on it at some point and written down nothing about it. That lesson made it into the article, along with a Tailscale subnet router that lets me reach the whole lake house network from 150 miles away without installing Tailscale on every box.

There was one surprise after the move. My local AI models slowed to under a word per second, and I nearly went shopping for a pricey graphics card. The real cause was a mismatch between the processor cores the container was allowed and the number the AI software assumed it had. Changing one setting made it about 80 times faster. If you run a homelab, or are thinking about moving one to bigger hardware, the full write-up is on EtherHam: A Bigger House: Proxmox Server Moved to a ThinkStation.

3.4 The Weekly Report

There is a ton of information in the Weekly Report this week. Included are these topic areas:

• Short Stack from the Interwebs

• Band Conditions

• Digital Radio News

• Groups.io Digest

3.5 New on Random Wire: Reply Rules

I want the Random Wire to be a place where people can disagree freely, treat each other with respect, and come away with better ideas. Substack, which hosts the Random Wire newsletter, lets authors set "reply rules" for commenters. I've written mine, squeezing them into the 500 characters allowed:

• Stay on topic: the post or amateur radio.

• No politics.

• Welcome every ham; no gatekeeping by license class, mode, or experience.

• Argue with ideas, not people.

• Share firsthand experience and sources.

• Selling used gear you own is fine; promoting a product you make or sell is not.

• Makers may join discussions if they disclose, and can email me about reviews.

• For the benefit of this community, I remove comments that break these rules.

• Judgment calls are mine.

• 73, Tom KJ7T

I’d love to hear your feedback. Please leave a comment or email me at tsalzer@pm.me.

Leave a comment

4. In The Lab

4.1 Working on CC1200 HAT for M17

One year ago, I placed the minimum order with PCBWay for five CC1200 HATs for M17. This week, I pulled one out of the box and prepared to install it. The HAT is designed to fit on a Raspberry Pi Zero 2 W.

The first dilemma I faced was finding the right standoffs to separate the HAT from the RPi. If the standoffs are too tall, the RPi’s GPIO pins don’t reach through the holes in the HAT. If they are too short, the soldered legs of the SMA connector come into contact with the mini-HDMI port shell.

Eventually, I decided to use some side snips and trim the SMA legs shorter. That allowed me to use some standoffs I had in the lab. The GPIO pins barely extend past the top of the holes in the HAT. They are ready to be soldered.

That’s where I stopped this week. I need to get my soldering station space cleared for the next step. I did ask Claude for soldering advice, and I appreciate the “tiny volcano” description. Maybe Claude said this because I’m a geologist. Whatever it was, it made me smile:

…heat the pad and pin together, feed solder where they meet, and stop when a small shiny cone forms around the tip. A good joint looks like a tiny volcano hugging the pin. If you see a ball sitting on top, the pad didn't get hot enough.

Once I get it soldered, configured, and tested, I’ll write it up properly with an in-depth article on EtherHam.com.

4.2 Audio Upgrade for Lake House

At the Portland QTH, I have an inexpensive-but-adequate audio setup, with an Audio-Technica AT2005USB dynamic microphone (affiliate link). Audio from the mic travels via XLR cable to a Behringer MIC500USB preamp. The preamp’s USB output goes directly into Audacity on my computer. I do my trimming and some sound leveling in Audacity, then push the audio file through Auphonic for final cleanup and leveling.

At the lake house, I've been using a Maono PD200W dynamic microphone (affiliate link) plugged straight into my laptop over USB, with no preamp. It sounds fine that way, but I like what the Behringer does for my voice in Portland, so a second MIC500USB is on its way. UPDATE: It arrived last night:

The PD200W will run over XLR into the Behringer, and the preamp's USB output will go into Audacity on the laptop. The rest of the workflow stays the same: trimming and leveling in Audacity, then final cleanup in Auphonic. With the same preamp at both stations, episodes recorded in either place should sound more alike.

I have used both microphones for video calls over Zoom and Microsoft Teams, but most of the time I use a Poly Blackwire 5220 Wired Headset (affiliate link) for those. My voice comes through fine, and incoming audio is clear. The Poly headset is not a candidate for piping audio through the preamp.

5. APRS

5.1 My APRS Stations Are Working

My mobile station is KJ7T-9, running on a Yaesu FTM-300DR transceiver.

In the lake house garage, I have a one-watt iGate/digipeater on 144.390 MHz operating as KJ7T:

I’m also running a roughly 120-milliwatt iGate/digipeater on LoRa on 433 MHz as KJ7T-2:

5.2 APRS Messaging

I’ve mentioned before how much the Zero Retries team covers. It’s simply amazing, and the depth and breadth of the Zero Retries newsletter is so good I read every issue. I recently found this gem in ZR 0263 that looks well worth digging into: Introducing APRS-WebMesg: A Modern, Free Web Front-End for APRS Messaging. The direct link to APRS-WebMesg is https://aprsmsg.app/.

I was curious, so I tested by sending a message from APRS-WebMesg to my APRSdroid app (KJ7T-5), and then replied from APRSdroid back to the sender (me as KJ7T-7). Here is what that exchange looks like in WebMesg:

That was nearly instantaneous. Pretty cool. In APRSdroid:

You might wonder if APRS will store-and-forward messages. I asked myself that and then heard from a highly trusted source that it does not work that way. I verified that: messages sent via the APRS-WebMesg service are carried by APRS-IS, and APRS-IS does not store-and-forward messages. It only delivers a message to a station that's connected at that moment. Winlink will do store-and-forward, but not APRS.

There is, however, one “kinda sorta” fallback: aprs.fi logs APRS-IS messages. If your message was carried at some point by APRS-IS, it will show up on your station’s messages page. In this screenshot from that page, you can see how my exchange was captured in the aprs.fi log for KJ7T-5:

6. QRT: End Transmission

6.1 HamClock Update Available

For those of us using the traditional HamClock connected to the Open Hamclock Backend, version 4.32 is now available. In the HamClock display, look to the right of the big current time in the upper left part of the screen to find the current version number. If an update is available, that version number will be shown in bold red letters (I’ve already clicked mine, so v4.32 is no longer red).

When you click that version number, you’ll get a popup in the middle of the screen:

6.2 WordPress Alternative?

I’ve known WordPress since the early days when it was, quite frankly, horrible to use. It was so bad when I first tried it, I moved to Joomla and Drupal for a few years. Then I rolled my own for a couple of years before recognizing that I couldn’t keep up on the security side and continue developing, at least as a one-person shop. That’s when I took another look at WordPress and found it much easier to understand and use.

But WordPress — the engine behind EtherHam.com — remains problematic. That’s why I continue to keep my eyes open for alternatives. Now comes a new CMS (content management system) from Cloudflare called EmDash that looks attractive. I may try a local install on my Proxmox server and see how it actually functions. It sounds like EmDash is still early days, but I'm hopeful something more secure will come along to replace WordPress. Fingers crossed.

6.3 Busy Season for Me

My busy season has officially started. I have six regional meetings in October, plus the usual committee and board meetings. My team is simultaneously putting the final touches on our statewide annual conference, coming up right after Thanksgiving. We get a slight break for the Christmas holiday and then the Legislature convenes a long session where we are proposing some special legislation. In the middle of all this, I’m working with attorneys and partners on an amicus brief for a case that will affect my state association members.

Thank goodness I have amateur radio to lean on when paid work gets overwhelming!

6.4 TriCorder?

Something for those of us who grew up with Star Trek: Open Source Tricorder Is In It For The Science.

You won’t be scanning for veteron radiation with this, but you do get a scintillation crystal to get a spectroscopic analysis of beta- or gamma-ray sources; there’s also a visible light spectrometer, thermal camera, and magnetic field camera along with a standard magnetometer and the usual environmental sensors to give you temperature, pressure, and humidity, plus particulate, VOC and CO2 concentration.

That’s a lot packed into one handheld device. Trekkies will find one of the comments humorous: “Ah! A keyboard! How quaint.”

73, and remember to touch a radio every day!

I had no idea AllStar was going to figure so prominently in my radio week. The firewall for my node 588416 on 44Net was important to get done. Building an AllStar node and adding DVSwitch Server and an AMBE stick was on my long-standing to-do list, and I’m pretty pleased with the result.

Then I enabled audio prompts on my AllStar node 578494…but they didn’t work. When I investigated, I found a few gotchas you should be aware of if you’re going to do this. The audio prompts and DTMF commands add usability to an AllStar node.

While working with node 578494, the node authentication check threw scary-looking errors at me, so I wrote up what they all mean.

While I was fiddling with the audio prompts, I thought I might as well install my click-three-times shutdown script on the node. But I found that my published directions were not as clear as they could be, so I updated that information on GitHub.

I modified my node information page on GitHub that I described last week three times. I added a status indicator, made the starter pages easier to implement, and then made a front door for the pages. All of this is free to do on GitHub.

2. Thank You

I’m sending a big Random Wire/EtherHam thank you to Brian and Mike for their support. It helps a great deal and I appreciate it.

Random Wire and EtherHam.com will stay free for readers, but running them still costs money. The Random Wire newsletter now reaches more than 2,400 subscribers, up about a third in the past year, and drew 161,000 views over that time. These subscribers are engaged, technically minded amateur radio operators who build, test, and buy gear. If you'd like to support this work, email me at tsalzer@pm.me or visit the Support page.

Contact KJ7T

3. New on EtherHam

3.1 Your Firewall Reflects the Moment You Built Your System

This is the third article about putting AllStar node 588416 on 44Net, and it may not be the last. If the series is a tent, Part 1 put it up: the hardware, the tunnel, the certificate, and the remote administration. Part 2 was the first anchor, two one-line router fixes. This article is the second anchor: the firewall, and the logging that shows you what it's doing.

The big takeaway: if your system has changed since you set up its firewall, the firewall probably hasn't kept up, and it's time to review it.

I proved that to myself again last night. While preparing for the next step, I found two leftover rules for a SIP phone that is no longer connected. The rules didn't do what I thought they did, so I deleted them.

Today, I'm adding a second protective layer in front of the node's own Uncomplicated Firewall (UFW). The MikroTik router will get an allowlist, so new connections arriving over the 44Net tunnel reach node 588416 only on the ports it actually serves. Everything else gets dropped at the router, before UFW ever sees it. If I write that up, it will become Part 4.

3.2 Reviving an Evolve III as an AllStarLink/DVSwitch Hub

I went looking for my old Winlink-in-a-box station, contained in a heavy-duty Pelican briefcase. When I opened the case, I found an old Evolve III laptop hiding in a document slot. This was a hot item several years ago and I remember picking one up to experiment with. What I didn’t remember was where I had stashed it. And then I recalled something from my ham radio to-do list: install DVSwitch Server and document not only how to install and configure it, but how to control it. I did that on the Evolve laptop. This is that story.

3.3 Don’t Panic: Reading The AllStarLink Node Authentication Check

Ever have that feeling like the bottom is falling out of your stomach when you see an AllStar error message? If so, this article is for you. AllStarLink 3 includes a handy tool, asl-node-auth-check, that tells you whether your node is registered and whether other nodes can reach it. It’s genuinely useful, but its report is full of “Error” and “Warning” lines, and many of those scary messages aren’t problems at all. On my own node, it flagged five errors in one afternoon, even though the node was working. Some of those pointed to things worth fixing. Others were false alarms, and one was AllStarLink’s own server telling me to slow down.

This new EtherHam article sorts every message the tool can print into three groups: normal, “the check couldn’t run,” and real problems worth fixing, with what to do about each. It also shows the three lines to look for first, and how to see exactly what address and port AllStarLink gives other nodes when they look you up. It starts at 10,000 feet over Indonesia, with a warning light and a pilot who wasn’t worried. Read it here: Don’t Panic: Reading The AllStarLink Node Authentication Check.

3.4 Teaching My AllStar Node to Say Its Own IP Address

I have written a lot about AllStarLink over the past year, and it turns out I can lose track of my own work. I went looking on EtherHam for the post where I explained how to make a node announce its IP address at boot. It isn’t there. It was a single sentence in Random Wire 145, back in August 2025, and the DTMF commands behind it were in Random Wire 142. Both track back to a post David Gleason NR9V wrote in April 2025 in his AllScan AllStar App & Nodes group on Facebook.

But information on Facebook can be hard to find, so I documented all of the steps in this article, personally tested on my own AllStar node 578494. This content is based on David’s great work and his AllScan app. Read it at Teaching My AllStar Node to Say Its Own IP Address.

3.5 Weekly Report

Another jam-packed weekly report for your consumption. What a wonderful time to be involved in amateur radio. There is activity in all aspects of our great hobby. The weekly report captures some of the items, but there is far more activity than I can possibly report here.

4. Shutdown Script: Tested Again, Instructions Updated

I installed my three-key-up shutdown script on another AllStar node this week: node 578494, the Evolve III laptop from the article above.

Three key-ups, a “goodbye,” and a clean power-down. The script worked as written, but the install instructions on GitHub had a few rough spots, including a reboot step buried mid-sentence where it was easy to miss. I’ve rewritten the install section as explicit, numbered steps with the commands spelled out, added a hand test you can run before turning on the service, and expanded the troubleshooting notes. The updated instructions are at github.com/EtherHamRadio/asl-shutdown-monitor.

5. A Free Front Door for KJ7T Nodes

I have to laugh at myself, because after I published AllStar Node Info Pages: A Step-by-Step Guide, I added a postscript. Then I added a second postscript. And finally, an update. Technically, that’s a postscript, a postscript to the postscript, and a postscript to the postscript to the postscript. Whew!

Here’s the shorthand version: I posted the article, then added a live status indicator for a node, then realized I could make the starter script easier to implement. Finally, I saw I needed a front door for my individual node pages so I built that, too.

Let me start with the latest postscript, the one I called an update. In that addition, I finally gave my AllStar node pages a home page. Up until now, kj7t.github.io/588416, /578494, /578493, and /588418 each stood alone. I had built some documentation but provided no top-level home for the information. This week I built a proper landing page at the root (https://kj7t.github.io/), with a personal introduction and a directory tying all four nodes together, plus some information about my HF, mobile, and APRS setups. This is a small project, but it's the kind of thing that turns a pile of pages into an actual site. It was also rather enjoyable to put this information into one space.

The first postscript

Next is the very first postscript. After publishing AllStar Node Info Pages: A Step-by-Step Guide, I wondered if there was a way to show a live status indicator for the node on the node’s GitHub page. Why yes, yes there was. Details are at the end of the Guide and the download has been updated to include this information.

It looks good — simple, but informative:

The second postscript

I used my “starter kit” template for a new page for node 578494…and found using it to be painful. Entering the same information, over and over, is a process that guarantees errors, and I made plenty. I decided right then: I need to find a better way.

So I rebuilt it. Now, you enter some key information in only two places: the .yaml file and in the index.md file. Those entries are carried into all the other pages. Much simpler. A new and improved starter kit (version 1.2) with updated instructions is now uploaded to the AllStar Node Info Pages: A Step-by-Step Guide article.

GitHub is free, and I find that free is often pretty attractive to radio amateurs. It’s not fancy, but it works. My new content hasn’t been “up” long enough to get indexed by search engines, but it’s on GitHub, so I know it will.

So that is the story of having an idea, improving it, improving it again, and finally giving all the individual node pages a single front door to this house of information.

6. AllScan Favorites Fix

I ran into something unexpected this week while copying an AllScan favorites file from one AllStar node to another. AllScan (from AllScan.info) makes it easy to build and manage a list of favorite nodes, and I’d built up a good list on my node 588418 that I wanted to put on node 578494. Simple enough: download the favorites file from 588418, upload it to 578494.

That worked fine, right up until I tried to add a new favorite on 578494. Nothing happened. The entry never showed up in the list.

AllScan really was saving my change. I could see it in the file on disk. What I hadn’t understood is how a favorites file is organized. It has a [general] stanza, whose entries appear on every node, and it can also have a stanza named for a specific node number, whose entries appear only on that node. My file had [general] plus a [588418] stanza, and [588418] held most of the favorites I actually cared about. On node 578494, AllScan looks for [general] and [578494]. It has no reason to show a stanza named for some other node, so while those favorites were present, they were effectively invisible. On top of that, AllScan adds a new favorite right after the last entry in the file, which dropped everything I added into the very stanza 578494 wouldn’t display. Saved, but hidden. From the browser it looks exactly like a file permissions or ownership problem, and that’s where I spent a good while looking.

The actual fix was one line: rename the [588418] stanza to [578494]. Everything appeared at once, and adding favorites has worked normally since.

So that I don’t have to think about it again, I wrote a small Python script that takes a downloaded favorites file and folds any node-specific stanza into [general], skipping entries that are already there. The result works on any node with no editing. It can also rename the stanza to a different node number, or strip it out entirely, depending on what you want. Eventually I’d like to extend it to merge favorites files from several nodes into one master list I can import everywhere.

This isn’t a flaw in AllScan. What I was doing is probably an edge case that the vast majority of AllScan users won’t do. Those per-node stanzas exist so one favorites file can serve several nodes, which is a sensible design. It’s the download-from-one-node, upload-to-another path that didn’t go quite right for me. I’ve passed the details along to David Gleason NR9V, AllScan’s author. AllScan is a great bit of helpful software and I install it — and will continue to install it — on my AllStar nodes.

7. 44Net Getting Some Press

• John Burwell KI5QKX was on the Late Shift on September 18th talking about 44Net Connect. You can catch the show at https://www.youtube.com/live/qKnC682SJuw or view it below:

• 44Net was featured in Japan's FB News! The first part of this three-part series describes 44Net's history and how to get started using the network. You can read the article here: https://www.fbnews.jp/202608/special/.

• ARDC showed off 44Net Connect at JARL Ham Fair 2026 in Tokyo. In its September 4 recap of JARL's centennial Ham Fair, ARDC says visitors at its booth saw 44Net Connect running live. Tom Mabuchi JF3LGC, ARDC's 44Net Regional Coordinator for Japan, translated and helped run the demos. The recap is at https://www.ardc.net/highlights-from-jarl-ham-fair-2026/.

• Software updates this month. 44Net Connect also got a few maintenance updates this month (September 6, 8, and 18), mostly behind-the-scenes fixes. The last big release was 1.1.0 in July. The changelog has the details.

8. Radios and Gadgets

Icom IC-7110 radio

Need and want are interesting things: while I don’t need a full-duplex, all-band, all-mode radio, I want one. And Icom is set to deliver it:

IC-7110, an HF/VHF/UHF all mode transceiver featuring a 4.3-inch color touchscreen, real-time spectrum scope, and comprehensive D-STAR functionality.

That comes straight from the Icom website (hit the link to see a promotional photo of the radio), except the full-duplex behavior was surfaced by the Ham Radio Workbench crew in HRWB 271. No word on cost, but my observation has been that prices from all major suppliers have been rising, so we can expect some sticker shock when the IC-7110 price is announced.

No matter the price, it looks like a great radio. Having full duplex available makes this a natural for working satellites.

FX-4CR Transceiver

FX-4CR is currently SOLD OUT! proclaims the headline at https://bg2fx.com/fx-4cr-transceiver-so. I don’t see a provision for a waiting list. If you are thinking about this great little radio, you’ll need to monitor the website, or consider joining the FX-4CR HF SDR Transceiver User Group on Facebook to catch informational updates. This is another radio on my want (not need) list.

9. Net Transcription

As I continue to experiment with net logging, I captured the weekly M17 net on Saturday, September 19. I thought it would not be a successful test because the M17 audio I was hearing sounded choppy when I monitored the signal. I was surprised that the transcription actually turned out well.

I pasted the full transcript into ChatGPT and asked for a summary. I find that it accurately reflects what I heard during the net:

The weekly M17 Net covered recent developments in the M17 open-source digital voice and data project. Major news included experimental M17 transmission on an unmodified Retevis C62 using OpenRTX, progress on the LinuxHT board, and upcoming firmware releases 0.4.5 and 0.5. Discussion also covered hardware versus software vocoders, DVSwitch, CC1200 Raspberry Pi boards, and National Traffic System training. No formal NTS traffic was passed.

The paragraph was derived from this pathway:

1. M17 over the M17-KCW reflector, which also carries the net onto the Kansas City Wide system;

2. my USRP2M17 implementation, connected to my AllStar node 588416;

3. on 588416, the transcription system captured audio files in .wav format;

4. the .wav files were then transcribed on the node itself by OpenAI's open-source Whisper speech-recognition model (via faster-whisper, running locally on the node's CPU — no cloud service, no per-minute fees);

5. then call sign matching was done using regular expressions (no AI);

6. production of the transcript;

7. final summary produced by feeding the transcript to ChatGPT.

Here are the first few minutes of the net, as created by the transcription system:

Notice there are some errors in the transcription (for example, “Kansas City Wide” was transcribed as “Kansas Citywide”, NXDN captured as NXTN, and “Neck Control” instead of “Net Control”), but all of these are decipherable without additional AI help.

Then I took one more step, which is optional and not automatic: I pasted the text transcript of the entire net into ChatGPT and asked for a summary. That summary is what’s quoted above.

What pleases me most is the balance between AI use and accuracy. The only AI in the automated pipeline is Whisper, running locally on the node. As you can see in the raw text above, the transcript is usable on its own, without the extra processing performed by ChatGPT.

I have to say that Jeff AE5ME runs a fabulous net: clear, clean, well structured, plenty of pauses for other stations, and something I rarely encounter: room allowed for emergency traffic. Kudos to Jeff!

10. Driving with Claude

Last Sunday, I made a day trip to Portland, about a three-hour drive on state and federal highways. On the way, I did something I thought I would never do: I talked with Claude (hands-free, voice mode) through the app on my phone while I drove.

I left the lake house at 5:00 am Pacific time — still dark, with little traffic and only a few deer wandering about. This is the time of day when I like to think. It’s a creative period of the day for me, and it’s often when I do my best thinking about writing.

10.1 Packet radio: AX.25 vs. FX.25

I started the conversation wanting to learn more about the differences between AX.25 and FX.25. Before the conversation, I knew a little bit about AX.25, but I knew next to nothing about FX.25.

AX.25 packets are validated by CRC (Cyclic Redundancy Check) and simply discarded on error, with no retransmission request on one-way links. FX.25, on the other hand, wraps AX.25 packets in a forward error correction layer. FX.25 works alongside existing AX.25 gear since a standard AX.25 receiver can still decode an FX.25 signal. Direwolf natively supports FX.25. It particularly helps satellite links at low elevations where signal quality suffers.

FX.25 is really an RF error rate solution. For an internet-based packet system running over TCP, TCP already handles error correction and retransmission, so you wouldn’t gain anything by trying to use FX.25 in that path. It would only earn its keep if the packets ever moved over-the-air.

10.2 M17 packet mode and the data channel angle

Then I pivoted the FX.25 discussion to M17. M17 has two modes: stream mode, which offers one continuous 3200 bits-per-second channel of encoded speech or data, or two 1600 bits-per-second channels carrying speech and data simultaneously; and packet mode, for discrete data transfer.

M17 packet mode is interesting to me. It already supports text messaging, APRS, AX.25, 6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks), Winlink, and raw data. The M17 spec defines all of these, and pyM17 looks like a possible starting point, so I parked this as a future Python exploration idea.

10.3 Winlink’s threading gap

Then I jumped from M17 to Winlink, where I think there is also some potential for two-way packet communications. Winlink has a store-and-forward bulletin system that functions as a one-way broadcast…a one-to-many system. If there was a way to intake replies to bulletins and show them in context — threaded — you would have a two-way Winlink-based BBS.

What I really like about this idea is Winlink is well established within the amateur radio community, both as a system and by reputation. That provides the potential for better adoption if a positive change could be implemented. Layering a many-to-many system on top of the existing one-to-many broadcast capability might add value. I’m thinking of this as a modernized BBS system built on the Winlink framework.

To be clear, this is just me thinking about possibilities. These aren’t proposals, just ideas.

10.4 APRS Chat, ANSRVR, and “next generation packet BBS”

As the Winlink thread was percolating in my mind, it triggered some thoughts about APRS Chat, APRS Connect, and the ANSRVR group-messaging server that powers #APRSThursday via CQ and join commands. As I talked with Claude, I recognized that the command style used by ANSRVR actually resembles classic BBS commands. That took me to the idea of an APRS-based (which is packet radio, after all) BBS. ANSRVR seems slightly more modern than old-school packet, and as #APRSThursday has shown, can be robust for wide-area communications.

10.5 Debian on phone for portable node?

And then I went to a new place, at least for me: the idea of installing Debian, AllStar, and DVSwitch on a phone to create a truly compact multi-mode node.

A phone-based build would need root access, an unlocked bootloader, and either a proper chroot or a full Linux install, none of which is guaranteed across phone models. It would also still need external USB audio hardware (the UCI90, the hub, the DV stick) riding alongside the phone, so the actual size and weight savings over using a small laptop becomes insignificant.

However, with the advent of all-in-one apps like QSO One that handle all of these modes in software, a compact hardware solution is probably a moot point.

10.6 Wrap-up

Well there you have it. That represents about an hour of talking with Claude while I was driving. That was an enjoyable way to burn up about 60 miles of highway, thinking about amateur radio and conceptually exploring some of the little sparks flitting around in my mind. I think this time was well spent, so I plan to do it again.

How about you? Do you ever go driving with Claude?

11. QRT: End Transmission

11.1 Net news

Heard on September 23rd on the morning Coffee Break Net on the W6EK repeater (AllStar node 51018): a schedule change. If I caught it correctly, the Coffee Break Net will move to 9:00 am Pacific time beginning October 1. This net is sponsored by the Sierra Foothills Amateur Radio Club.

11.2 Radio in the garage

I have a VHF APRS iGate/digipeater in the garage, along with a LoRa APRS iGate/digi. But what about FM broadcast radio? At the lake house, Dad used to have a small AM/FM receiver out in the garage, along with a few beat up speakers. I’m pretty sure he sourced those items a long time ago at a local Radio Shack store. His old twin-lead FM antenna is still tacked to the wall, but the rest of that setup is long gone.

In his memory, I purchased a low-cost FM receiver/amplifier and a pair of speakers to mount in the garage. The cheap radio only has a small telescoping aerial, so I attached about five feet of insulated wire to it to make a more-or-less half-wave FM antenna. It works fine. Dad would be happy about it, and it will remind my family members of him. It’s also a reminder to me that radio, in some form, touches all of us, in some way.

11.3 Notation Polish Reverse used you have?

I have a calculator nobody around me wants to touch, because it is a complete mystery to them. It’s a Hewlett Packard HP-15C, still going strong, built like a tank, and utterly indecipherable to the uninitiated. You see, it uses RPN logic: reverse polish notation. The best explanation might not be from XKCD but it’s my favorite, where RPN is presented in the guise of RPS: Reverse Polish Sausage. (I’m a big fan of the ultra-nerdy XKCD humor.)

I love that calculator. I love it so much, in fact, that I also have the financial version, the 12C. Both are still going strong after all these years. More importantly, each one brings a smile to my face when I pick it up. I can’t explain why. It’s like a favorite radio, I guess. I just like how it feels and functions.

11.4 Update on the book manuscript

My conservation book manuscript is at the publishing house. They tell me it will be about 330 pages in paperback. That’s a bit more than I expected. The manuscript still needs professional editing. We’ve finalized the title and settled on a conceptual cover design. I’m expecting publication by spring 2027, but my fingers and toes are also crossed for luck! I'll share more as publication gets closer.

11.5 More Likely Than Lightning: What My Bitaxe’s Best Share Really Means

My Bitaxe's best-ever share looked impressive until I did the math. It's still 4,400 times short of a block, but a block win is more likely than getting struck by lightning. Read: More Likely Than Lightning on EtherHam.

With that, I’ll say 73. My best wishes to all. Remember to touch a radio every day!

Welcome to issue 200! Remarkable! Without you (as of Wednesday: 2,400 subscribers!) this would not have been possible. Thank you to every person who subscribes.

It’s been a pretty steady march forward over 4+ years for the Random Wire newsletter, with a few bumps along the way from mentions in the Zero Retries newsletter and on the Ham Radio Workbench podcast.

Simply amazing. I continue to learn so much from so many, it makes this effort well worth it. I hope you find value, too.

Issue 200 has been a challenge because I’ve been dwelling in the land of computer code and remote machines. Last week was all kinds of AllStar goodness. This week I’m cleaning up a bit of that work from last week and diving into more. For example, I bridged M17 to a private AllStar node, giving me a bidirectional path: M17-to-AllStar and AllStar-to-M17. Along the way I learned I don’t need to have a costly M17 radio or an M17 hotspot to get on M17 — I can do this with an AllStar node and some software. It’s not perfect, but if you have an AllStar node and wanted to dabble in M17 without spending money, you can!

This is also a big work week for me. We’re putting together an amicus brief (technically, an amicus curiae brief) for a case before a higher court in Washington State. My team is fully consumed with preparing for multiple regional meetings next month, plus putting the finishing touches on our annual statewide conference. We are also preparing for what promises to be a very challenging legislative session that launches in January. And this week has many meetings, including a meeting of the primary state agency we work with, plus a meeting on Friday with our nonprofit association members. All of these things have pulled me away from radio this week. The flipside of this is returning to radio will taste sweeter when I get more time.

With that, let’s dive and see what happened in my radio week.

2. New on EtherHam

Bridging M17 Into AllStarLink

This item is, to me, pretty cool, and has a great takeaway.

I spent a chunk of this week connecting my M17 reflector (M17-PNW) to an AllStarLink node. These two systems have been running as two separate worlds since they were launched. The mechanism is USRP2M17 talking to a private AllStar node over the loopback interface.

I am certainly not the first person to do this. In fact, I recall a 2024 article in Zero Retries was where I first heard about it. I am standing on the good work of others.

The most interesting part turned out not to be building it — that went about as expected — but something I did not see until later. I had been testing the whole chain through my M17 hotspot, because that is how I built it. I never questioned my assumption that this was the correct configuration.

Then it landed: USRP2M17 is itself an M17 client. It connects to the reflector on its own, appears in the client list like any other station, and receives the module’s stream directly. The hotspot was never required. I do not need an M17 radio, or a hotspot, or any M17 hardware at all to put a reflector’s audio into AllStarLink.

That is a huge takeaway for me. Until that moment, I really did not recognize that the software I was fiddling with functioned as an M17 client, negating the need for a hotspot. That reframes what the bridge is. It is not an accessory to a hotspot; it is an independent gateway, and it can be pointed at any reflector I choose. I proved it by accident, monitoring a net on an ordinary analog handheld several links downstream and noticing the audio was markedly cleaner than anything I had managed in a morning of test transmissions. Of course it was. My transmissions had been going out through a radio whose microphone I cannot adjust, which is its own story and cost me most of a morning to pin down.

One of the very best takeaways, though, is this: you don’t need a special M17 radio or hotspot to use M17 if you have an AllStar node. Install and configure USRP2M17 and use your existing analog radio to get started with M17.

The full account is on EtherHam, including the gain setting that is not really decibels, and the very first test that failed for a reason I had deliberately built into the node myself.

Automatic Net Logging, Part 3: The Bug That Ate 16 Percent

This is Part 3 of a series about building an automatic net logger on an AllStarLink hub node. Part 1 covered who it’s for and how to get audio out of a node with no radio. Part 2 covered the bugs that live traffic exposed in the detection logic. In Part 3, I describe the bug I nearly missed entirely and what it taught me about trusting my own tools. It closes with where the whole project ended up:

But overall, it works. A net happens, and twenty minutes later there’s a record of it — searchable, exportable, and reasonably accurate about everything except the call signs. That last one turned out to be more tractable than I expected, but that’s a story for another day. Radio traffic is gone the moment it ends. It doesn’t have to be.

The Router Rule That Sent My Replies to Dallas

This is the second of three articles about putting AllStar node 588416 on 44Net. Part 1 is the tent: the hardware, the tunnel, the certificate, the remote administration. This one is an anchor that keeps the tent secured.

I found two bugs in my MikroTik hAP ax2 router configuration. Each was fixed by a single line. Both took hours to find. In both cases, the configuration that caused the problem looked entirely reasonable on the screen — plausible values, in the right fields, doing something close enough to the right thing that reading it told you nothing.

The takeaways, summarized:

• When symptoms contradict your theory, go find a counter.

• Check what you’re measuring before you trust what you measured.

• A vendor configuration is correct for the traffic its author anticipated.

• Redundancy that shares a dependency is not redundancy.

I did share my notes with the 44Net folks who acknowledged my concern. It felt good to try to help make the campsite better for all of us.

Weekly Reports

Perhaps the most interesting item in the Weekly Report this week, for me, is: Successful M17 transmission using an unmodified Retevis C62 running OpenRTX. I say that because of the preliminary work I explored in Flashing OpenRTX for M17 on the Retevis C62: Almost There. It’s really great to see this project moving forward.

Postscript to The Anatomy of Remote Assistance over SSH

I found a simpler solution for the one-on-one help session in my SSH reverse-tunnel article, and added a postscript about it. That solution is Tailcat, a tool that creates lightweight, temporary, peer-to-peer encrypted tunnels, built by the same people who built Tailscale. Instead of a permanent tailnet, you download a file, share a key, and make an ephemeral connection that goes away when you’re done.

I could have used that in helping “Dan” with his radio configuration. I did not learn until this week that he is setting up the same full-duplex AllStar node that I have!

The device is an AllScan ANF101 full-duplex node. Behind the backplane is a Dell Wyse 3040 thin client machine that powers it. It runs my AllStar node 588418. You can see the frequency I transmit into (431.1800 MHz) and the frequency the node transmits over to me (147.4700 MHz). This is one of my favorite AllStar devices.

I was really tickled to help “Dan” get his machine up and running.

8-Day Contest Feed Removed

The 8-day contest feed on EtherHam.com was swamping other results in the feeds. Since no one has ever said “I like the contest feed” I removed it. Please let me know if you’d like it to return!

Leave a comment

3. New in the Shack

When I say “shack,” I really mean all the places where I have a ham radio presence: the Lake House (Washington), the QTH (Oregon), and the cloud server (Seattle).

My 1980s-Style BBS at a Real IP Address

Let’s cut to the chase: why? Why put an old-school-ish BBS online?

Well, why not? I wanted to learn more about packet systems, and I wanted to put one of my 44Net addresses to use on a low-bandwidth service. A packet BBS is exactly that.

There’s something quietly satisfying about standing up a BBS on my own public IP address — not a port forward, not a dynamic DNS name that breaks when the cable modem hiccups, but an actual routable address on 44Net, amateur radio’s own slice of the internet. I now have two: 44.27.19.242 for AllStarLink node 588416, and 44.27.19.243 for an old Intel Mac Mini running LinBPQ as a packet node, BBS, and chat server at packet.etherham.com. Both sit behind a MikroTik hAP ax2 in a Portland rack — power and internet aren’t reliable enough at the Lake House for a public-facing box, so Portland was the better choice.

The 44Net Connect side turned out to be the easy part. ARDC’s self-service tunnel provisioning handed me a WireGuard endpoint and a /28 within minutes, and adding the Mac Mini to an already-working setup was close to anticlimactic — new port, new bridge, done.

The hard part had nothing to do with networking. LinBPQ runs three separate engines — node, BBS, and chat — and by default only the node starts. Setting BBS=1 merely permits applications; an APPLICATION line merely adds “BBS” to the command list. What actually launches the mail server is a bare LINMAIL line in bpq32.cfg, and without it every symptom points somewhere else: no config file, because the engine that writes it never starts; no debug log, rather than an empty one; a web config page that appears to save and then quietly reverts. I chased permissions, session tokens, and form behavior before finding the answer in G8BPQ’s own install notes — one sentence, easy to miss. LINCHAT does the same job for chat. Once both lines were in place, everything came up on the first try.

The last piece was making sure it comes back by itself. LinBPQ runs as a systemd service now, and a small unit flips the bit that tells this 2014 Mac Mini to power itself back on after an outage — the same thing macOS does behind the “start up automatically after a power failure” checkbox. I tested it the only way that counts: pulled the cord and watched it come back on its own. For a station I administer from three hours away, that’s the part that actually matters.

I now have a small cadre of folks helping me test this system. We are all learning together. I don’t know if there is a solid place for an old-school BBS in these modern times, but without trying it, I really can’t know.

Insta360 ACE Camera Is Back in Service

Not radio but technology.

When my wife and I made a long road trip to Kansas, I included a (then) new Insta360 ACE camera. That sat on the pickup truck dash with a sandbag mount which kept it in place, most of the time.

Well, I was digging through a box and ran across a 1-terabyte microSD card. Back when I bought it, I think I paid $88 for it. Today, a new 1TB card is like buying gold! I stuck it in my laptop to read the card and found videos from that trip, particularly the stretches in and around Moab, Utah. Great memories.

I dug around some more and found the Insta360 ACE camera. The mount was missing so I bought a new one and have been using the camera+mount on the truck dash for the past few weeks.

The other morning, on a dark, early drive for my morning coffee (this is my thinking time) I rounded a corner to find a deer standing in the middle of the road. I slowed down and let the animal finish crossing. The Insta360 ACE caught it:

Of course, the cam also picks up people who cut me off in traffic, or who pass me and then hit their brakes. I’m sure I have one video where someone has shown me with their hand that I’m #1. I don’t need to share those videos but it’s good to have a record.

I just looked at the price of this camera on Amazon. Oh my. That cost has gone up — way up. I think I bought mine on sale when Insta360 was transitioning to the new ACE PRO series, because I don’t remember prices anywhere near what I’m now seeing.

4. APRS

Here’s a nice product to point you toward: the iGateMini. This is a VHF, single-board device with one-watt out that can serve as a tracker, an iGate, or a digipeater. I think it is particularly well suited to serve as a fill-in digi/iGate in your shack. Hat tip to Ham Radio Workbench for this. See HRWB 270 - Satellite Tracking with CSN Technologies.

And while I like the looks of the iGateMini, I must say I do like my LightAPRS Gateway 1.0 device that I wrote about here and here. At $130, the price is quite reasonable for a tracker, iGate, and digipeater. There’s a lot to like with this little device. As you can see below, it is working well for me, despite the antenna being inside the garage, located in a basin surrounded by hills.

Does it seem like APRS applications are proliferating? There is the long-standing #APRSThursday check-in, and I do that occasionally over LoRa APRS. There is APRS OTA, and I confess it looks like fun. There is SpaceAPRS which will become more useful when the ISS APRS station comes back online.

And there is APRS Connect and APRS Chat for Android. Although I don’t have a modern iPhone, there are great apps for Apple phones, too.

In fact, there are so many new APRS things going on I know I’ve forgotten a few that I meant to share. Hopefully I’ll remember them before Friday’s publication deadline! Bottom line: APRS seems to be making a bit of a resurgence. I’m okay with that.

5. A Repeater 250 Miles over Your Head

Since I touched on the ISS APRS station above, what about the VHF/UHF repeater on the ISS? Do you know how to work it?

Aboard the International Space Station, in the Columbus module — ESA's European lab, built in Italy by Thales Alenia Space — the amateur radio crossband repeater is up and running. Heads up, though: ARISS has a scheduled outage coming September 18 (15:20 UTC) through September 19 (16:50 UTC) for spacewalk support, so don't be surprised if it goes quiet for a day.

▸ Uplink: 145.990 MHz FM, 67 Hz CTCSS tone

▸ Downlink: 437.800 MHz FM

▸ Radio: any dual-band FM handheld or mobile will do

▸ Antenna: a handheld whip works; a small directional gains you the margins, best is a little portable YAGI antenna

The technique:

1. Look up the next high pass for your location (any ISS tracker app or website — pick passes above 40° elevation).

2. Program both frequencies before you go out — remember the 67 Hz tone, or the repeater stays silent.

3. Listen on 437.800 first. When the pass starts you’ll hear traffic from stations already working it — the downlink comes with Doppler shift, so tune around slightly.

4. Transmit on 145.990 when there’s a gap, give your call, and listen for yourself coming back through the orbiting machine.

That’s it. Your signal goes up, gets retransmitted from space at up to 25 watts out, and comes down half a continent away.

6. QSO One Continues to Grow

I’ve got to hand it to Frank KD8JKK — he has really pushed QSO One forward. He writes:

QSO One is live on Google Play, right now, in 177 countries. https://play.google.com/store/apps/details?id=com.qsoone.qso_one

That’s a pretty big deal. I feel better knowing the code has passed through Google’s gauntlet. No guarantees that it is safe, but it feels safer than before, so I installed it on my phone.

There is one aspect to setting up your AllStar credentials in the phone app that I think is incorrectly described. For the IAX2 password, Frank says to go to AllStarLink.org and find your node password. That is not what I think of as my IAX2 password. I have passwords for various contexts in my /etc/asterisk/iax.conf file. Those are the ones I think of as IAX2 passwords, so that’s where I went first…and none of them worked. What did work is exactly what Frank described. I used the node password from my AllStarLink.org portals page for node 588418 and that worked. I just don’t think it is best described as an IAX2 password. That confuses me.

Other than that small quirk, this is brilliant software for the Android smartphone ecosystem. Job well done, Frank!

7. ARDC Seeks Volunteers in 2027

Amateur Radio Digital Communications (ARDC) needs your help.

ARDC is now accepting applications for their 2027 volunteer cohort. Applications are open Sept. 15 – Oct. 30, 2026. They are looking for qualified individuals to contribute their time and expertise across several committees and teams:

• Grants Advisory Committee (GAC) – reviews grant applications.

• Technical Advisory Committee (TAC) – works on 44Net-related projects and policies.

• Grants Evaluation Team (GET) – evaluates and analyzes grant reports.

• Grants Communications Team (GCT) – writes about grant results for the public to learn from.

• Conduct Review Committee (CRC) – helps to evaluate Code of Conduct incident reports. Must concurrently serve in another volunteer role.

Read more at: https://www.ardc.net/volunteer-with-ardc-in-2027/

8. AllStar: Best Practice for Node Information?

Several days ago, I heard a fair question about the AI net-transcription project I’ve been running on my AllStarLink node 588416: should participants be told their traffic is being captured?

The short answer: probably not required by U.S. law. Amateur radio carries no expectation of privacy under FCC rules or federal wiretap law, and that’s by design, not an oversight. But the more interesting answer turned out to be practical, not legal: even if I wanted to notify people, AllStarLink’s own infrastructure gives a node owner almost nowhere to say anything at all. The node registration portal, which is where you might expect people to go to find node details, has exactly one optional text field, capped at 20 characters, meant for a frequency label. That’s it.

But not legally required doesn’t mean not necessary. The very first item in the Radio Amateur’s Code is Considerate. Informing people they may be recorded — even though it’s not required to do so — is courteous amateur radio behavior.

For AllStar nodes, there is no standard place to publish this kind of information.

The gap is worse for a node like mine. It’s a hub — no radio, no coverage area, nothing that fits neatly into the tools that already exist for this hobby. QRZ covers callsigns, not node numbers. RepeaterBook covers physical repeaters with frequencies and PL tones, not link nodes. And the one thing I’d already built — a small web page served directly off the node itself — had an obvious flaw: it disappears exactly when the node goes down, which is precisely when someone might most want to know what’s going on.

My fix was to stop hosting that information on the node at all. I built a free node page on GitHub Pages instead — no server to run, no uptime to maintain, and it publishes automatically from plain text files the moment I push a change. I put it under a new GitHub organization named for my callsign rather than folding it into my existing EtherHam brand, since a callsign is what is associated with my node number, and it keeps my station’s own documentation independent of whatever EtherHam does or doesn’t become down the road.

The page itself is short: what the node is and how it’s used, a plain-language disclosure that traffic may be recorded, a description of the transcription project specifically, and a running changelog of what’s changed on the node over time. I then pointed the node’s own web address (which lives on the node at /var/www/html/index.html) at this new page with a simple redirect, so there’s exactly one place to keep current rather than two drifting copies.

None of this took more than an evening, and most node owners are in an easier spot than I was — running one or two nodes rather than a dozen, which makes this a single small repository rather than anything to architect around. If you operate a hub or link node in particular, where there’s no repeater and no physical footprint for the usual directories to hang a listing on, I think this is worth thirty minutes of your time. I’ll be writing up the full how-to soon; consider this the introduction to what may be a best practice for AllStar node owners.

I added a how-to document at EtherHam.com — AllStar Node Info Pages: A Step-by-Step Guide — if you want to give this a try. It’s really not too hard.

9. QRT: End Transmission

The QRT section is a bit of a catch-all this week.

PocketCHIRP

I haven’t tried PocketCHIRP yet, but I will.

PocketCHIRP is an Android radio programming app for amateur radio, GMRS, radio enthusiasts, commercial/business users, DMR, and other supported radios, with tools for reading, editing, saving, and programming compatible amateur radios over Bluetooth or USB — plus repeater search, satellite Doppler channel generation, custom groups, cloud backups, Android TalkBack accessibility, custom drivers, diagnostics, and more.

Now available in the Google Play Store.

Question about my DMR hotspot

My WPSD-driven DMR hotspot is set up to look to Brandmeister first, then to PNWDigital. I’m not sure that works well when I’m keying up to connect to PNWDigital. For my purposes, this hotspot only needs to contact PNWDigital, so I’m wondering if I should remove Brandmeister altogether. I’d appreciate thoughts from folks more experienced in DMR than me! Contact me at KJ7Tom@gmail.com.

Rain barrels…not radio but it is technology of a sort

My technology interests range widely, and sometimes they intersect with my natural resources conservation field. Rain barrels can be useful but they are hard to site in a way that looks attractive (which is probably why most people put them in the backyard or behind a side yard fence). You can also use cubic IBCs (Industrial Bulk Containers), but again, they take up a lot of space and look, well, industrial.

In contrast, I love this concept I just ran across: the Rainwater Wall. Jump to The Rainwater Wall: A Space-Saving Water Harvesting Tank and scroll down to see it. It’s clever. Compared to round barrels and cubes in cages, it looks pretty nice situated along a wall or fence. I hope this idea takes off.

Windows RDP and drive redirection

I learned something new about Windows Remote Desktop (RDP), which I use over Tailscale to operate my work computer remotely. The new thing: I can map a local drive so it shows up on my work computer. (Technically, it’s called drive redirection.)

How?

• Open Remote Desktop Connection on your Windows computer (search for it in the Start menu)

• Click Show Options in the lower left corner

• Click the Local Resources tab

• Click More... under “Local devices and resources”

• Expand Drives and check the drive(s) you want accessible

• Click OK, then click Connect

I needed to move a script from my Lake House NAS box to the work PC, by through drive redirection, it was easy. I could simply drag-and-drop or copy-and-paste the folder I needed. I don’t know why I never knew this before, but that was a gold nugget AHA moment. It saved me from the whole zip-the-folder-and-email-it-as-an-attachment method.

All you networking gurus who are rolling your eyes, well, I’m just happy to learn a new, useful thing. Old dogs, new tricks, and all that!

73, and remember to touch a radio every day!

Share Random Wire℠

1. QRV: Are You Ready?

Random Wire issue 199 is big on AllStarLink this week, including:

• an updated how-to for installing to a Dell Wyse 3040 thin client machine;

• getting a node up on 44Net;

• part two of a series on transcribing AllStar nets; and

• new apps for AllStar.

If I provided this level of coverage for AllStar every week, my tagline might be: AllStar, All the Time! Fortunately, topics change from week to week.

Random Wire/EtherHam Community Links

• EtherHam at https://etherham.com

• EtherHam store at https://etherham.printful.me/

• Groups.io at https://groups.io/g/EtherHam

• GitHub at https://github.com/EtherHamRadio

• Random Wire at https://www.randomwire.us/

• Random Wire Facebook at https://www.facebook.com/RandomWireReview

2. Random Wire and EtherHam

I get asked now and then why I run two publications instead of one. Here’s the short answer.

Random Wire is the journal. It’s where I write about what’s happening — what I built this week, what broke, what I’m noticing, what’s rattling around in my head. It doesn’t have to be finished or tidy. A half-formed thought about digital modes, a detour into geology or fly fishing, a reaction to something going on in the hobby — it all belongs here. When I write this, I’m writing to you, one of 2,500 people who get it in their inbox every Friday.

EtherHam is the workbench. It’s where the ideas from Random Wire actually get built. The full how-to, the firmware quirk that cost me an afternoon, the radio that doesn’t leave the bench until I’ve pushed on it from every angle — that level of detail lives there, not here. If Random Wire tells you I moved my AllStar node onto 44Net this week, EtherHam is where I show you exactly how, mistakes and all.

Short version: read Random Wire to keep up with what I’m doing. Read EtherHam when you’re ready to do it yourself.

3. New on EtherHam

Installing AllStarLink on a Dell Wyse 3040 (2026 Update)

A reader wrote in, stuck on getting Debian Linux onto a Dell Wyse 3040 thin client machine. After I responded, I realized my older guidance from June 2023 was quite outdated…so I updated it and published the fresh guide on EtherHam.com.

And then I realized I was simply wrong on some points, so I went to David Gleason’s (NR9V) AllScan.info site for truth and found it. That means if you read the article last Friday evening before 8:30 pm, it had incorrect information. The article as posted now is much better.

If you have a 3040 on the bench you want to dust off, or if can get your hands on a used unit in good shape, it remains a superb platform for building an AllStar node.

• Installing AllStarLink on a Dell Wyse 3040 (2026 Update)

Putting My AllStar Node On 44Net

This is the thing that took much of my time this week: moving my AllStar node 588416 from an address on my LAN to a 44Net static IP address. Sounds simple but it wasn’t. I feared this would be too complicated for me so I put this off for months, but it turned out to be a little easier than I expected. Simple? No. I was challenged, but I also achieved a positive outcome.

I moved my AllStarLink node 588416 onto a public 44Net address, nine months after ARDC announced the WireGuard-based 44Net Connect service in December 2025. The article opens by admitting the node already worked fine, so why do this? My motives may be just as interesting as the technical details: learning routing and tunnels by hand rather than in the abstract, owning an address block tied to a call sign instead of renting one from Comcast, and actually occupying address space the hobby already owns rather than admiring it from a distance.

My build centers on a MikroTik hAP ax2 router placed behind an existing GL.iNet Flint 2 router, which achieves complete isolation between 44Net and household traffic without VLANs or a managed switch.

The article closes on the day’s actual lesson: the modern, unfamiliar part worked on the first try, and every real problem was local — port defaults, PoE behavior, and a bug in a config file.

• AllStar on 44Net, Part 1: Putting My AllStar Node on 44Net

Parts two and three are in the works.

Related: MikroTik routers being attacked. Do a Google search or check here and here.

Automatic Net Logging, Part 2: What Five Live Nets Taught

Over on EtherHam, I’ve published Part 2 of my automatic net logging series, and this one’s about what happens when your code works perfectly in isolation but falls apart against real traffic. I tested my AllStarLink net-detection system against five actual nets and found four separate bugs — the kind that only surface once you throw real repeater audio at something instead of a clean test case. Each one alone just nudged the accuracy down a little; together, they made the whole system unreliable.

The bigger lesson wasn’t about any single bug, though. It’s this: unit tests can tell you every piece works and still miss the failure that only shows up when the pieces interact. Fixing that took real listening, not just better regex. If you’re building anything that has to survive contact with real-world audio, it’s worth a read.

• Automatic Net Logging, Part 1: Who It’s For, and Getting Audio Out of a Hub Node

• Automatic Net Logging, Part 2: What Five Live Nets Taught

The Anatomy of Remote Assistance over SSH

This is the tale of helping someone get AllStarLink installed on their Dell Wyse 3040 thin client machine, using an SSH reverse tunnel to take control of the terminal on the other end of the pipe. With no desktop environment installed, the usual screen sharing applications were not going to work. On top of this, the user was not an accomplished computer user, so I needed to find the simplest steps he could accomplish to provide me with remote access.

Weekly Reports

• Short Stack is even longer this week with the addition of some space-related feeds.

• Band Conditions look to be on the mend, so now’s a good time to get on the air and make up for lost time.

• Digital Radio News — The M17 Project released a new draft of the M17 specification. AllStarLink’s app_rpt code received more fixes. There’s a new commit for MMDVMHost. And LoRa APRS iGate posted some updates.

• Groups.io Digest saw RepeaterBuilder leading the pack with 155 messages, followed by TinySA (85 messages), ARDC 44Net Connect (75 messages), and APRS (46 messages).

Retevis RT85 Cheat Sheet

A subscriber asked if I had a cheat sheet for the Retevis RT85 dual-band handheld radio. I did not…so I made one. There are still a few unresolved or unconfirmed items, but if you have one of these radios, find version 7 of the cheat sheet at https://etherham.com/downloads/#cheat-sheets

I have several of these radios so the cheat sheet is a help to me, too. This is one of the easiest dual-band VHF/UHF HTs available that is both reliable and usable. When I checked earlier this week, the price for the 2-pack was about $35 on Amazon. Yes, $35, for two radios, antennas, batteries, desk chargers, belt clips, and hand straps.

Retevis RT85 Handheld Ham Radios, Portable Dual Band Walkie Talkies, 2 Pack. Emergency Two Way Radio Long Range, Built in VFO, 200CH, VOX, FM, DTMF, Flashlight, 1400mAh, for Survival Preppers Off-Grid (this is an affiliate link)

Creating the cheat sheet was an interesting exercise because some published information was missing or conflicting. The Retevis RT85 cheat sheet joins another cheat sheet I made for the RT3S when flashed with OpenGD77 firmware. Both are in the Downloads section of EtherHam.com: https://etherham.com/downloads/.

New Reference Pages

I’ve added some Reference Guide pages to the EtherHam site. The first set are:

• AllStarLink Node — Reference Guide

• fail2ban — Reference Guide

• Security Hardening — Reference Guide

Find these in the main menu under the Downloads selection. Please let me know if you have suggested edits, or if there are topics for which you’d like a simple reference sheet.

Leave a comment

4. New Amateur Radio Applications for AllStar

There is so much going on today with all-in-one dashboards! What a great time to be a ham.

One of the newest suites comes from Terry Claiborne KC3KMV. Terry first contacted me about a year ago about IAX and AllStar nodes. He dove in and hasn’t looked back. He writes:

I have a deep background in the IS field, spanning everything from Assembler, Fortran, and COBOL to C, B, C++, Unix, and Turbo Pascal. I retired at 55 and am turning 70 next year. My journey into this space started with HamVoip before I transitioned to ASL3. When I first emailed you about creating a user in iax.conf, it sparked a deep dive, and I haven't stopped since. My main goal now is to share different options and presentations to make things easier for others in the community.

Find his Amateur Radio Applications listed on his QRZ page:

• Alltune2 is a high-performance utility for BM, TGIF, YSF, D-Star, P25, NXDN, AllStar, and EchoLink nodes on ASL3.

• AllStar View is a standalone, read-only web monitor for AllStarLink 3 / app_rpt systems.

• AllStar Connect is a web dashboard for controlling and monitoring AllStarLink and EchoLink connections on an ASL3 node.

• DVSwitch Cockpit is a modern web dashboard for watching what your ASL3 / DVSwitch node is doing in real time.

• AllStar Web Transceiver — Windows is a native AllStarLink client for Windows.

• AllStar Web Transceiver — Android is a native AllStarLink client for Android 12+.

I installed the AllStar Web Transceiver on my Windows laptop. I was curious if it would install because my laptop runs on an ARM processor, but it installed just fine via the Microsoft Store. I’m listening to the W6EK Coffee Break Net using Terry’s AWT (my abbreviation) application while I type this.

It sounds great:

AWT is pretty convenient. Once you add some stations to the Favorites list, a click of the mouse and you’re connected. If you install AWT, be sure to connect to node 55553 over Web Transceiver mode to test your audio. Mine returned with “just about right.”

The dark mode is particularly nice:

I’ll be trying some of the other applications as time permits. I’m particularly interested in AllTune 2, billed as “One Dashboard. All Your Networks.” That sounds like a very practical way to use a Raspberry Pi.

Kudos to Terry for providing some great tools to the amateur radio community. Well done.

5. A Touchscreen for Your Physical AllStar Node?

Speaking of AllStar, how about this pull request for touchscreen support in the wonderful AllScan app! See: https://github.com/davidgsd/AllScan/pull/32/

Add a new /simple/ interface focused on quick, touch-friendly favorite node control. The interface is designed to behave more like a channelized radio than the full AllScan control page: favorites are shown as large channel buttons, and the normal workflow is to select one channel/node at a time.

When a channel is selected, the Simple interface uses the existing connect API with autodisconnect enabled so the local node is first disconnected from other nodes before connecting to the selected favorite. If additional connections are still present, the page shows a warning state and offers a disconnect-all control instead of treating that as the normal single-channel state.

Having a compact AllStar device that incorporates a touchscreen and simple user interface seems like a winning combination. It will be interesting to watch how this develops.

6. Interesting: SDR Without a PC

OrcSDR: Why folks no longer need a $650 SDR tells the tale:

The OrcSDR project centers on the M5Stack Tab5, a battery-powered handheld tablet powered by a dual-core RISC-V ESP32-P4 processor. By plugging an RTL-SDR directly into the Tab5's USB host port, the ESP32 handles the heavy lifting: it processes the raw digital radio stream, demodulates audio, and renders a live, touch-responsive spectrum and waterfall display on a 5-inch color screen without a PC.

This is literally a tablet with an RTL-SDR dongle plugged into it:

The simplicity of this approach, the compactness of the configuration, and the capability of the RTL-SDR makes this a very interesting project indeed.

7. These Are a Few of My Favorite AllStar Nets

Set that title to the tune of My Favorite Things from The Sound of Music. Is that stuck in your head now? You’re welcome!

WA7ABU in Salem, Oregon — AllStar node 543260 — A daily tech net at 10 am Pacific. Topical nets each evening. A community filled with rich skills and experiences. The daily tech net is also linked in listen-only mode through AllStar 55915 and AllStar 57945.

W6EK in Auburn, California — AllStar node 51018 — A daily social net, the Coffee Break Net, from 7:30 am to 10 am Pacific. An All-Nodes tech net on Monday at 6 pm Pacific. And just a friendly bunch of hams who know each other well. AllStar node 51018.

PSRG in Seattle, Washington — AllStar node 2462 — Daily social nets at 9 am, noon, and 9 pm Pacific. Also a daily Boater’s Net that starts at 7:47 am Pacific (that time must be a nod to the Boeing 747 aircraft).

8. Another Logo Design

I’m trying — inexpensively — a variation on the EtherHam logo, with an order for vinyl decals from Sticker Mule. These are “two-fers” that tell others you are an EtherHam who enjoys tinkering with technology.

Custom stickers like this are the cheapest way to check the resolution of the design. My cost for 30 decals is $48, delivered. That works out to, what, $1.60 per decal? My calculator says yes.

I can hold it up to a ball cap to see how it looks. I ordered them a bit larger than hat size because I also want to see how they look on T-shirts and sweatshirts. At 4” × 2.25”, they will work well on water bottles and the back window of the pickup truck.

These are “kiss cut” vinyl stickers. What does kiss cut mean? It’s a printing and cutting technique where a blade cuts through only the top layer while leaving the protective backing paper completely intact. Peel and stick. Done. Vinyl is more resistant to washing (think: reusable water bottles) and weather. For a sticker that might go on a laptop, vinyl will also be more resistant to damage from sliding the computer in and out of a bag.

I’m looking for feedback. If you like this, let me know and I’ll add some items to the EtherHam Store. I’d like to get a coffee mug that stares back at me with ”I tinker with technology”.

9. Transcribing Examples

These are excerpts of summaries produced by ChatGPT from my Transcript Viewer captures. Functionally, I specify the start and stop times in the Transcript Viewer page, run the query, then download the resulting text file.

I feed that text file to ChatGPT with this prompt:

Attached is a transcript of an amateur radio net, captured off the air and transcribed automatically by speech recognition. The transcription is imperfect. Call signs are frequently garbled: sometimes spelled out phonetically ("November 6 Quebec Delta Yankee" = N6QDY), sometimes hyphenated ("K-E-6-R-A-X" = KE6RAX), sometimes mangled outright.

Please give me: 1. Net control station — callsign and name, if identifiable. 2. Stations that checked in, in order, with names where mentioned. Reconstruct each call sign as best you can. Mark any you are uncertain about with a trailing question mark. 3. A summary of the net in 3-5 sentences. 4. Anything notable: announcements, technical topics, traffic passed.

Do not invent callsigns. If a station's identity is genuinely unclear, say so rather than guessing.

W6EK Coffee Break Net, Friday morning, 9/4/26

The entire AI-processed transcript is italicized below:

The Coffee Break Net was hosted by Tom, NN6H, on the W6EK repeater and associated AllStarLink/EchoLink connections. The net followed its usual informal rag-chew format, beginning with quick check-ins and later moving into longer conversations about weather, amateur-radio networking, AllStar nodes, QSO1, and personal activities. Stations checked in from across the United States and internationally, including the United Kingdom, Wales, Idaho, Pennsylvania, Oklahoma, Texas, and Hawaii. The net closed shortly after 10:00 a.m. Pacific, with Brian, AI6US, identified as the next day’s net control operator.

Announcements and Net Information

• The net is sponsored by the Sierra Foothills Amateur Radio Club.

• It normally runs every morning from 7:30 a.m. to 10:00 a.m. Pacific.

• The primary repeater is W6EK, with AllStar node 51018 and EchoLink access.

• Tom mentioned the club’s support for the Auburn food bank, in connection with National Food Bank Day.

• Brian AI6US was announced as the Saturday net control.

Technical Discussion

The most substantial technical discussion involved:

• QSO1, an application used for connecting to AllStar systems.

• Possible conflicts when running multiple AllStar nodes or applications behind the same IP address.

• The IAX port, 4569, and the need to avoid port conflicts.

• The distinction between using QSO1 in IAX/node mode versus WebRTC/web-transceiver mode.

• Aaron W1ATV was troubleshooting behavior involving his AllStar node and another node apparently using the same credentials/node number.

• Greg reported apparent audio dropouts that occurred in QSO1 while RF audio continued.

Compare that AI-cleaned summary with a raw transcript — errors and all — from the WA7ABU Tech Net from September 8, 2026. You can find that on EtherHam.com at https://etherham.com/automatic-net-logging-part-2-what-five-live-nets-taught/#what-does-a-raw-transcript-look-like.

10. Gadgets

You wouldn’t think a headset would be related to AllStar, but this one is. I bought a Retevis headset, not really knowing what would arrive. Thirty bucks later, this arrived:

Retevis EHK012 Two Way Radio Headset with Mic,for RT22 RT68 RT86,1 Pack

This was especially chancy, since Amazon notes: “Frequently Returned Item: Consider linking to similar products with lower return rates.” No affiliate link in the product link above because Amazon doesn’t like frequently returned items.

But I took a chance anyway and am not disappointed. This set of cans feels pretty robust. The microphone in the Amazon photo is not covered, but mine arrived with a foam cover over the microphone element.

The K1 connector works on my Retevis radios, of course, but also on other radios with a K1 interface. I’ve tried it on my AllStar node 588411 built on a Computer Module 4 platform with AllScan UCI90 interface and it worked fine…after I figured out I had to turn the volume up on the UCI90.

Comfortable? Not really. These firm-fitting headphones sit very securely on my medium head. They also isolate sound quite well. If you need to hear outside sounds for situational awareness, these are not for you. But if you need sound isolation and a secure fit, these are fantastic.

I get a little bit of hiss (maybe better described as grungy hum) on my transmitted signal but it is not objectionable and does not interfere. If I was working a bike race with an HT while motorized traffic was zipping by — and if I was safely positioned away from traffic — these headphones would be a top choice.

Verdict: a viable choice for a noisy environment, where sound isolation and a firm fit trumps comfort.

11. More on My FTM-300DR Shutdown Problem

The same day Random Wire 198 published, I made a trip to Port Orchard, Washington. The Yaesu FTM-300DR was set up for APRS operation on 144.390 MHz on VFO B, as always. The antenna was the temporary “Justin Case” mag-mount COMPACtenna, the one that I put into service a week earlier because with the old Comet antenna, the radio was shutting off when it beaconed.

And wouldn’t you know it, but the radio shut off when it beaconed, even with the COMPACtenna. I powered the radio up and watched it while I drove, and twice more it shut down when it beaconed.

Two completely different antennas and feedlines, and the identical problem. This points away from the antenna system and shifts my attention to the power delivery system.

Final update: it wasn’t the antenna. I even tried a third antenna with the same symptom appearing. So it was time to test the power delivery and see if that affected the radio’s behavior. That was easy to test by swapping out the 12VDC power cord. The result? Problem solved. Somewhere in the old cord there is a bad connection or corrosion I just didn’t see.

12. QRT: End Transmission

Helping a Ham Get a New AllStar Node on the Air

I was honored to help a fellow ham figure out how to load Debian on his little Dell Wyse 3040 thin client machine and get AllStar running. For those of us who have done this several/many times, it’s easy to forget how utterly daunting it is to attempt this for the first time. As the other ham and I exchanged emails, I could hear his frustration through his words. But he persevered and succeeded. I have to admit that it feels pretty good to help someone experience success.

Color me surprised when I learned that Chuck bought me some coffees!

Thank You to Hunter Inman and Steve Stroh

I have really enjoyed fiddling with Hunter’s creative solution to transcribing net traffic carried by AllStar. He is moving forward on this with a revised system that is running autonomously now. See it in action at https://kk7nqn.net/viewer.html.

A big thank you to Hunter Inman KK7NQN and Steve Stroh N8GNJ (Zero Retries newsletter) for their kind words about the work I’ve been doing with Hunter’s script (see https://www.zeroretries.org/i/212220420/update-on-kk7nqn-ai-net-logger).

#APRSThursday

I checked into #APRSThursday last week from my LoRa tracker as KJ7T-3:

HamClock OHB Beta Has APRS

Great to see APRS in the HamClock display. It even picked up my portable LoRa APRS station (KJ7T-3) on a LilyGo T-Deck Plus.

Eagle-eyed readers may notice the Starship Enterprise on the display. September 8 was Star Trek Day and the HamClock software includes a built-in easter egg to commemorate it. That was a fun discovery.

Jupiter-Moon Conjunction

If you happened to be looking at the pre-dawn sky on September 8th, you might have seen what one of my radio friends remarked on: a bright star next to the Moon. But it was actually Jupiter, not a star. If memory serves, we saw a Venus-Moon conjunction back in May. It was easy to see the Jupiter-Moon conjunction because most of the Moon’s disc was dark.

13. Closing Reflections

Amateur Radio: More Than Just a Hobby

When the attacks on September 11, 2001, knocked out cell towers, police and fire radio systems — as well as the city’s own emergency command center in 7 World Trade Center — hundreds of amateur radio operators stepped in. RACES and ARES volunteers ran health-and-welfare and medical traffic, supported the Red Cross and Salvation Army, and shadowed city officials so they could keep communicating with each other when nothing else worked. It’s one of the clearest examples of why “emergency” is built into so much of this hobby’s service tradition. We “play radio” because we enjoy it, but we also give back to the communities where we live, work, and play.

Balancing Radio and Life

When I drove to Portland on Sunday to work on putting node 588416 on my 44Net address, I had a feeling something wasn’t right back home with my wife, who needs care around the clock. Nothing to point to yet — just a feeling — so I started packing up to head back to the lake house. Before we’d wrapped up everything we needed to do that day on the node move, my daughter texted: “Dad, something’s up with Mom.” The feeling had been right.

What followed was a 911 call and another ambulance ride by Mason County’s great EMS folks to an Olympia hospital. There, the doctor was certain he needed interventional radiology to assist, but nobody was available. Then came the two-hour scramble as the ER staff looked for another hospital to treat her. Finally, a very experienced nurse popped in and asked: would you mind if I try to fix this? Please do, I said. Ten minutes later, we were arranging transport back home because the problem was fully resolved. I have to say it: nurses rule.

Next week: issue 200!

With that, I’ll say 73. Remember to touch a radio every day!

1. QRV: Are You Ready?

Welcome to meteorological fall (September 1st). Astronomical fall lands on September 22nd, so I guess this is a “take your pick” kind of thing. For me, when the school buses start to slow my rate of travel between the lake house and some barista-brewed coffee, that’s my signal fall has arrived.

I’ve been asked why I use the tagline “Remember to touch a radio every day” at the close of every Random Wire newsletter. My answer is both simple and perhaps not so simple. On the simple side, when you use a radio frequently, you tend to continue to use a radio frequently. Simple.

The more complex answer is that when you remember to incorporate radio into your everyday life in some way, it becomes more a part of who you are. It lives closer to the surface of your thoughts. You begin to see commonplace things and wonder: how could that be adapted to support my radio play?

And I think it is in that space that we become more involved, more engaged, and more excited about the many ways radio touches our lives.

My tagline is a gentle reminder to work toward having that kind of indispensable relationship with radio, because as we already know, radio touches all of us in some way, every day.

RW/EH Community Resources

• EtherHam at https://etherham.com

• EtherHam store at https://etherham.printful.me/

• Groups.io at https://groups.io/g/EtherHam

• GitHub at https://github.com/EtherHamRadio

• Random Wire at https://www.randomwire.us

• Random Wire Facebook at https://www.facebook.com/RandomWireReview

• Random Wire Search at https://etherham.com/rw_search/

And there are still some slots left in the EtherHam groups.io space. Join at https://groups.io/g/EtherHam.

2. New on EtherHam

There is some meaty content on EtherHam.com this week. First up is trying to get OpenRTX running on a Retevis C62 for M17, and unfortunately, it’s just not there yet. Then I modified my “shutdown your ASL3 node with three quick key-ups” script, based on reader input. The third item is the start of a three-part series on automatic transcribing of AllStar nets, but guess what? That really means it can capture any voice traffic on AllStar.

Flashing OpenRTX for M17 on the Retevis C62: Almost There

The Retevis C62 is one of the more interesting radios to land in the M17 space. Unlike the RT3S and other MD-UV380-class radios — where M17 requires physical hardware modifications, SMD rework and fine wire work — the C62 is a firmware-only target. No soldering. Flash it over the programming jack and you’re done.

That’s the promise. This is a field report on how far you can actually get today, written after a full day at the bench with a charged radio, three programming cables and a working build.

Short version: the flashing pipeline works and is now well understood. The firmware doesn’t boot yet. Both halves of that are worth documenting for those of us experimenting with this.

Addendum to: Shutdown an ASL3 Node with Three Key-Ups

A reader (thank you, Bill) wrote in after upgrading a SHARI Pi3U (kits4hams) node from HamVOIP to ASL3. He’d had a pushbutton triggering shutdown just fine before, and gave this script a try — but found three quick key-ups weren’t being recognized. He got it working by bumping WINDOW_SEC up to 10, and specifically by keying up, waiting for his node’s ack/courtesy tone to finish, then keying up again — repeating that three times.

The addendum documents my thoughts about the cause of this condition, and the solution. And then I did what I should have done in the first place: published the script to a proper GitHub repository.

Automatic Net Logging, Part 1: Who It’s For, and Getting Audio Out of a Hub Node

An idle AllStarLink hub node — no radio attached, nothing plugged into it but power and Ethernet — turns out to be a good place to record and transcribe net traffic. Part 1 covers three quite different people who'd want that: someone logging nets, a repeater owner who wants a searchable record of what happens on their machine, and an operator who can't follow the audio and would rather read it. They need the same pipeline set up differently — the net logger would rather it mistake a rag chew for a net than miss a real one, and the repeater owner wants exactly the reverse.

It’s built on the KK7NQN-TranscriptionLogger project by Hunter Inman KK7NQN, with the audio capture, transcription step and a web viewer added. There’s an awkward bit, too, which is how you record from a node that has no receiver and therefore never fires the event every guide tells you to watch for. Over three days my system captured five live nets across four repeaters and turned up four real bugs, one of them quietly discarding sixteen percent of everything it recorded. Parts 2 and 3 cover those. The code is on GitHub if you’d rather read Python than prose.

One thing in there is worth thirty seconds of your time even if transcription doesn’t interest you at all: check whether your node’s Asterisk Manager Interface is bound to 0.0.0.0. Mine was — port 5038 open to the internet and being actively scanned. One line in manager.conf fixes it.

Weekly Report: September 3, 2026

This week, the Short Stack from the Interwebs is added to the Weekly Report!

The higher HF bands, especially 10, 15, and 20 meters, should be in fine shape for both DX chasing and regional contacts.

AllStarLink code received a batch of stability fixes. The Hams Over IIP wiki was updated with a MicroSIP navigation page.

The top three monitored Groups.io groups are Repeater Builder (205 messages), TinySA (70 messages), and APRS (59 messages). Runners-up include: HotSpot Radios, M17 Users, SHARI, and 44Net Connect.

3. Ham Radio Workbench #269 on AllStarLink

I included the link to this podcast last week, and I include it again this week because it’s just such a great show.

• HRWB 269 - AllStarLink with Jason McCormick N8EI

George and the HRWB team kept me company on a drive from the lake house to Portland last Sunday. I’ve been playing in the AllStar space for several years, but I learned quite a few new things, and developed a better understanding of how AllStar works. If you are interested in AllStar, this is worth listening to. It has information for AllStar beginners and aficionados alike.

And Jason dropped some great gems toward the end of the show. He also mentions the Ampersand-ASL project by Bruce MacKinnon, which I’m running on a couple of different devices (but start here if you’re interested in running this software).

One tidbit I particularly enjoyed was learning how the AllStarLink system was designed to avoid a typical star topology (hub and spokes). The federated distribution style of the AllStar ecosystem appeals to me.

The show closes with a live demonstration of Mike Walker VA3MW getting his node up and running, then connecting to nodes for other show members.

AllStarLink is an all-volunteer effort and they need support:

The implementation of this system and its monthly upkeep is very costly. Any monetary help that you can and wish to give will be much appreciated. Allstarlink Inc. is a 501(c)(3) non-profit organization.

AllStarLink Donations

You’ll get a thank you when you donate:

4. FreeDV RADE: For Your FlexRadio and Your Pi

ARDC has published a great introduction to FreeDV RADE, the open-source digital voice mode that swaps the usual DSP tricks for a machine-learning “radio autoencoder.” The pitch: SSB-beating voice quality down to -2 dB SNR, in about 1.5 kHz of bandwidth — half what SSB needs. It’s now built directly into FlexRadio’s 6000/8000/Aurora line as a selectable mode, but you don’t need one of those to try it — it runs just fine on a Raspberry Pi 4 or 5.

If you’ve ever had trouble picking voices out of the noise on HF, RADE might make the band feel accessible again. Hams in Australia, Japan, Europe, and South America are already running weekly RADE nets; VK3TPM says it’s noticeably easier on the ears than analog HF.

RADE v2 is in the works, targeting sub-1kHz bandwidth!

Learn more: FreeDV RADE: A New Approach to Digital Voice Over HF

5. Hunter’s Transcription Script

I can’t always listen to a net, even when I really do want the learning that comes from hearing so many great questions and answers. Then I remembered Hunter Inman's KK7NQN Transcription Logger project from the first Zero Retries Digital Conference and decided to give it a try on a spare AllStar node. Read Hunter’s overview at https://kk7nqn.net/. It is pretty amazing stuff.

However, getting it working required inferring some information and making some choices. A key choice for me was to use regular expressions instead of an AI for some transcription tasks. The system also tries to detect whether it has captured a net. Just like me, it does struggle with call signs.

Ultimately, I forked Hunter’s code and incorporated some fixes, including some new files. One of those was creating a simple transcript viewer web page. That saves me from having to SSH into the node and run a complicated MySQL query just to see a transcript. The Transcript Viewer lets me use date selectors to set a start and end date/time for the query. The query output is parsed into a table, and the transcript is downloadable as a text file.

I tested it on Sunday evening with the Puget Sound Repeater Group’s 9 O’Clock net:

This showed the system is working. Then I tried using my local OpenWebUI machine running gemma3:4b to generate a net summary and correct some call signs, but it was slow. The call sign detection wasn’t much better than what I could do just by reading the transcript. However, I can feed that text file to an online AI (I used ChatGPT) to get an acceptable summary, if desired. With this one test, I think the RegEx transcript will usually be good enough.

I tested the logger again on Monday morning with the WA7ABU TechNet, a daily net at 10 AM Pacific that is often jam-packed with great technical information.

The script I implemented, plus the transcript viewer, are available on GitHub if someone wants to experiment with it.

As noted above in the New on EtherHam section, Part 1 is published: Automatic Net Logging, Part 1: Who It’s For, and Getting Audio Out of a Hub Node

Part 2 (Automatic Net Logging, Part 2: What Five Live Nets Taught) will publish on September 8, and Part 3 (Automatic Net Logging, Part 3: The Bug That Ate 16 Percent) on September 15.

When Making the AI Smarter Made It Worse

The net logger on AllStar node 588416 has been running well enough that I’ve moved on to its weakest part: call signs. Whisper hears “Whiskey Bravo 3, Charlie, Sierra Yankee” and writes exactly that — which is useless if what you want in the log is WB3CSY. The obvious fix is a bigger transcription model, so Wednesday I sat down to benchmark one.

It didn’t work, and neither did the next two things I tried. Whisper medium is nearly three times slower than small on that little i5 computer, and on the clips that actually contained call signs, it won one and lost one across seven tests. Where it lost, it lost badly: “Kilo foxtrot zero Sierra Mike Delta” came back as “Kilo, Flaxstrad 0, Sierra, Mike Delta.” Flaxstrad isn’t a word. Conversely, the smaller model had transcribed it correctly.

So I tried priming instead — feeding Whisper the phonetic alphabet and a list of call signs it should expect. On a transmission with nothing intelligible in it at all, the primed model produced “KJ7T-OR.” That’s my own callsign, which I had put in the primer. It hadn’t heard anything; it just gave me back what I’d told it to look for, formatted to look exactly like a real check-in. Hotwords, the third approach, mangled “Sierra Alpha Yankee” into “ALFAYANKI” — which made me laugh, and which is also unrecoverable.

The pattern took me a while to see. A bigger language model has a stronger sense of what English is supposed to sound like, and the phonetic alphabet is deliberately built from words that don’t sound like ordinary English. They are unique more than normal. That’s the whole point of it. So the model’s instincts, which help everywhere else, actively fight this particular vocabulary. Priming makes it worse, because a model told to expect call signs will manufacture one out of thin air.

What finally worked was about forty lines of Python and a lookup table. small‘s literal, unclever transcription turns out to be the most useful output available, precisely because it doesn’t try to be smart — “Whiskey Bravo 3, Charlie, Sierra Yankee” converts to WB3CSY every time, reproducibly, with no AI model involved. Running it across 1,754 transmissions found more than thirty call signs that no regex could see, because they’d only ever been spoken phonetically. It also turned up a failure mode I hadn’t noticed: the first phonetic word of a call sign goes missing constantly, almost certainly caused by PTT key-up clipping at the start of the transmission. Even the net control operator’s own call sign came through truncated three times in one net.

The best part came last. Digging through Hunter Inman’s (KK7NQN) original database schema, I found he’d already built the lookup table I needed. He included a corrections table with the phonetic alphabet in it, including “king” and “box” from the old military alphabet that still sees plenty of use on the air, plus manglings he’d collected in the field. My resolver now reads from his table. Adding a new correction is one line of SQL instead of a code change.

The code and the full write-up are in the GitHub repo, and parts 2 and 3 in the series are scheduled for publication. As additional refinements are put in play, it’s possible a part 4 will emerge.

6. DroidStar 9M2PJU Mod Update

It turns out the DroidStar 9M2PJU Mod app has an update available, but you won’t find it on the Google Play Store. Go to https://droidstar.hamradio.my/ for the link to download the APK directly (but be prepared for nag screens — I counted six popups before I could proceed).

7. New and Notable: Nexus Amateur Radio Software

I picked this up from the Tuesday Project and Ham Radio Hobby Net on the WA7ABU 145.29 MHz repeater (also on AllStar node 51018). I was driving from Portland to the lake house Tuesday evening, so I had my node 588416 connected to 51018 to capture the net and catch up on it later — see the note on Hunter’s Transcription Script above. Glad I did, because I would have missed this otherwise.

Brett KG7GDB brought up a program called Nexus Modern Operating Workstation and described it as an ambitious attempt to fold a bunch of familiar ham radio applications into one modern environment. According to the net, Nexus handles:

• Rig control

• WSJT-X-style digital modes, including FT8 and FT4

• APRS — beaconing, messaging, mapping, following other stations, weather

• Slow-scan television

• Logging

• A waterfall display and modern GUI

Most of that already exists somewhere else. What caught my ear was having it all in one place. Anyone who’s built a digital-mode station knows how the software stack creeps — one program for the radio, another for FT8, a third for logging, maybe a fourth for APRS, each one wanting its own serial port or audio device or CAT interface. It works, but it gets tangled. An integrated app could cut down on that.

The APRS talk tied back to some recent conversation the group’s had about projects for radios like the Icom IC-7100. On the SSTV side, nobody had actually put hours into it yet — this was more of a “hey, look what I found” than a review. That’s usually how these things start.

Rob AJ7HR zeroed in on two details: Nexus is GPL-3 open source, and it’s written in Rust. He’d like to see more open-source software in the hobby — a lot of what we depend on is excellent, but plenty of it is tied to one platform, one maintainer, or one development model, and open source gives the community more room to poke at it and keep it alive. Rob also admitted Nexus had already gone farther than the all-in-one app he’d once thought about building himself. I think every technically minded ham has had that “I should build something like that someday” thought, right before someone else does.

It also runs everywhere — Raspberry Pi, Linux (.deb and AppImage builds), Windows, and macOS, including Apple Silicon per Brett. For a hobby that runs on everything from Pi Zeros to Windows shacks to Macs, that cross-platform reach matters.

Nobody on the net claimed Nexus replaces WSJT-X, your logging program, or your rig control software. But it generated enough interest that I’m filing it under “worth downloading and trying.” That’s usually how it goes: one ham finds something, another notices it’s open source, somebody else wonders how it’d fit their station, and pretty soon three people are experimenting. That’s a lot of how amateur radio actually gets done.

8. Meet CORE

I was introduced to the Central Ohio Radio Enthusiasts (CORE, at https://core.radio) by Justin KF8DEU. I have to say: this sounds like my kind of radio club!

From Justin:

It’s a radio club in a very broad sense, as in we talk about not only amateur radio but pretty much ANYTHING radio (mesh technologies, digital radios, reticulum, weather balloons, SDRs, etc) and meet once per month, listen to whoever wants to present something to us, while eating pizza.

Tech talk, radios, and pizza. Sounds like a winning combination! Kudos to the CORE team. They are active on Discord.

9. Configured a Spare DMR Hotspot

Digging through some storage bins, I ran across my first homebuilt hotspot, made with a Raspberry Pi 3 board, a duplex MMDVM board, and a C4 Labs case. Cosmetically, it looks identical to the later RPi 4 hotspot I built.

After futzing with it for a while to get the configuration right, I downloaded a backup of the working RPi 4 hotspot and restored that config to the RPi 3 hotspot. That worked perfectly…probably because the MMDVM board was exactly the same.

Along the way, I realized I only want to use one hotspot for PNWDigital traffic. The Retevis RT3S is flashed with the PNWDigital codeplug, so it’s already set up that way. The hotspot is configured to reach Brandmeister first and PNWDigital second. I’m thinking now this doesn’t make a lot of sense.

10. Forgotten: My ADSB Exchange Machine

On a recent trip to the Portland, Oregon QTH, I pulled up my router admin dashboard to make sure firmware was up to date. And then I noticed a machine in my client list I had completely forgotten about, named adsbexchange.

I had covered this more than two years ago in Random Wire 87.

The other thing I had forgotten was Tailscale running on my local-to-Portland ADSB machine. So I logged in, updated the Debian operating system, and made sure Tailscale was updated.

When I got back to the Lake House, I opened the Tailscale address for the machine and there it was: my flight tracker running in Portland, showing on my laptop more than 100 miles away.

I’m surprised at the coverage I’m getting with this simple antenna, mounted inside by the sliding glass doors on the ground floor:

Upgrade Version Loop Antenna MLA-30+ Plus 0.5-30MHz Rainproof Ring Active Receive Antenna Low Noise Medium Short Wave (this is an affiliate link)

The ADSB Exchange dongle for my Raspberry Pi is no longer listed on Amazon. Try the ADSBx Hardware page if you’re interested in flight tracking.

11. Gadgets

Pocket AI Recorder

I put this off for several months, but finally pulled the trigger on the Pocket recording device (https://heypocket.com/pages/pocket). It is billed as being your personal AI assistant.

Is it life changing? No. Is it helpful? Yes. I’ve started using it to listen alongside me while I monitor nets. The post-net AI-produced summary is generally good enough to provide a solid overview of the topic discussed. Pocket doesn’t do well recognizing different voices, so when there is a statement in the summary that Tom said something, I have to take that with a big grain of salt. But overall, I’m glad I made this purchase.

The M17 Net summary below was generated by Pocket AI. It listened to the net, presented me with a written summary, and I made corrections and some edits for easier reading. Pocket AI, like other AI engines, really has difficulty with amateur radio call signs.

This session was recorded live from the Tulsa Maker Faire (Maker Fest), where Jeff (AE5ME) served as Net Control for the weekly M17 digital voice net on the Kansas Citywide system. The meeting focused on technical updates for the M17 protocol, the M7 application, and upcoming amateur radio events.

M17 Protocol & Hardware Updates

• LinHD Project: Development continues on the Linux-based handheld (LinHD). A “Revision C” design is forthcoming. The project utilizes the Retevis C62 as a donor for the case, keyboard, and display.

• Hardware Compatibility: Participants emphasized using the English version of the Retevis C62 rather than the European version to ensure compatibility.

• OpenRTX Firmware: Version 0.1 is approaching release, which will introduce packet and SMS engine capabilities. Supported hardware includes the CS750, M17 Plus, and Module 17 boards.

• Hotspot Options: For high-performance M17 hotspots, the CC1200 and SX1255 boards were recommended over standard MMDVM/Raspberry Pi hats due to superior signal purity.

M7 Application Development

Greg provided a status report on the MSeven app:

• Scan Feature: New functionality allows scanning across multiple reflectors and channels.

• Dual-Receive Modes: Users can choose between a “stop and listen” mode (full audio for a set duration) or a “priority” mode where the active channel plays at full volume while others are ducked to 30%.

• Hardware Pairing: The app successfully pairs with the Mobilinkd TNC4, enabling M17 operation on any 9600-baud capable radio.

Community & Events

• Zero Retries Conference: Scheduled for October in San Ramon (about 35 miles east of San Francisco). Jeff confirmed he will attend in person to present on M17, noting that a Zoom attendance option is available for those unable to travel.

• Maker Movement: Jeff highlighted the 10th anniversary of the Maker Faire, emphasizing the importance of organic, non-commercial development in amateur radio to attract younger generations (STEM/youth groups).

• Zero Retries Info: Registration and details are available at www.zeroretries.org/p/conference.

Net Operations

Due to the high-noise environment at the Maker Faire (35 dB to 50 dB noise floor), the National Traffic System (NTS) portion of the net was bypassed. Technical discussions and check-ins were prioritized via both RF and the netcontrol.live text stream.

I have no experience with other devices that purport to do the same thing, so I can’t make recommendations. I can tell you where Pocket falls down, and that is Bluetooth…because there is no Bluetooth. If it had Bluetooth, maybe a phone call over a headset or earbuds could be picked up. As it is, it only picks up my side of that conversation. The solution is to use the speakerphone function.

I’m not going to touch on privacy laws, since every state has something a little different. My state is a dual consent state (both sides have to agree) so I usually don’t bother with Pocket on phone calls.

Cute Little Radio Project

It’s not two-way radio, but it’s still radio. It’s an ESP32-based web radio, says this Blogspot post:

I built this ESP32 based web radio this week. I’ve used a 1.9” IPS display with ST7789 driver. For the audio I’ve used MAX98357A I2S audio amplifier. This web radio is based on the excellent yoRadio project https://github.com/e2002/yoradio

I’ve said it many times: I like small devices. This build is certainly small!

12. QRT: End Transmission

It was a hectic weekend-ish time. I made three day trips to Portland: one on Friday, one on Sunday, and one on Tuesday. Sunday was particularly long as I climbed into the pickup at 5:30 am and got back to the Lake House around 8 pm. Lots of driving, but that also meant time for audio books, listening to nets, and not-to-be-missed: listening to the Ham Radio Workbench podcast.

Debian 13

I lean heavily on Debian Linux, particularly Debian 13. That is usually my “go to” distro. Turns out I’m in good company. CERN is implementing Debian 13. I guess if it’s good enough for high-energy particle physics, it’s good enough for my home lab!

146.52

I don’t hear hams on 146.52 MHz very often up in the Olympia, Washington area, but it is quite common to hear traffic in Portland, Oregon and Vancouver, Washington. In Portland and Vancouver, 146.52 is treated more as a simplex channel for sometimes long conversations. I don’t think I’ve ever heard a contact in that area on 146.52 followed by a request to QSY to a different frequency. Different places, different customs. Always interesting.

Mobile antenna

And with three round trips, I got to test what was going on with my VHF/UHF antenna on the pickup. I’ve had good luck with Comet antennas, so the dual-bander on the truck is the Comet SS680SB. But something is wrong: when my Yaesu FTM-300DR transmits an APRS beacon, the radio shuts off. I thought: must be high SWR, I’ll check it. I pulled out my RigExpert STICK-500 analyzer and measured a very acceptable SWR below 1.3 near the APRS frequency. So I hooked up the radio again and as soon as it beaconed, it shut off.

I had a spare antenna under the seat, named for my good friend Justin Case. That antenna is a mag-mount dual-band COMPACtenna. Before connecting it to the radio, I measured the SWR and found it was well above 2…but that’s still acceptable. And here’s the part that doesn’t make any sense to me: the radio works fine with the COMPACtenna.

Of course, I’ve had that antenna on the roof of the pickup for more than two years. It’s seen a lot: rain, snow, hail, rocks, tree branches, a Washington-to-Texas road trip, and more. I live in western Washington so salt-laden moisture could be a factor. Maybe there is an intermittent connection that I missed when I tested the SWR. I’ve cleaned and tightened connections, but the radio still shuts down when it transmits an APRS beacon through the Comet antenna. I tested this over and over on my three long drives. (As I think about how the antenna is configured, I’ll bet it comes apart, which means I haven’t really cleaned all the connections yet.)

The next time I pop down to Portland, I’ll grab a spare antenna from the Justin Case antenna tube and try it on the same mount. If that works, then it’s the antenna. If the radio still shuts down, it’s the mount or feedline. In the meantime, my stubby COMPACtenna is doing the job for me.

73, and remember to touch a radio every day!

1. QRV: Are You Ready?

Last week I hit DMR topics pretty hard. Then the weekend brought us a medical issue with my spouse, and Monday I made a day-long trip to Portland and back. Add in the work I did this week on the Retevis C62 build (more on this below) and I lost about four days of potential writing time.

Fortunately, life settled back into place by mid-week, giving me some time to play with the Retevis RT3S/OpenGD77 radio on DMR. Last week, I configured my Yaesu System Fusion hotspot running WPSD software on a Raspberry Pi 4 machine to DMR. That left me without a YSF machine unless I switched the RPi4 back and forth between DMR and YSF. Instead of doing that, I plugged in my spare RPi5 hotspot and configured it for YSF. Works great.

I used the RT3S to monitor the PNWDigital Not-a-Net” gathering on Wednesday evening…with some self-created hiccups along the way. When I got set up a few hours before the gathering, I could not get reliable reception with the RT3S. I went down several rabbit holes before the light went on in my head: my DMR hotspot was using the same frequencies as my YSF hotspot. Whenever the YSF hotspot was active, my DMR reception was terrible. The fix was simple: move the DMR frequencies for TX and RX to a different pair that no longer collided with the YSF frequencies. Problem solved.

I also switched my LightAPRS Gateway antenna from a small mag-mount on a cookie sheet to an actual vertical dipole. Surprisingly, it didn’t do much. My direct connections decreased slightly while my total connections increased. Maybe in my hilly location, the more spherical pattern of the mag-mount works better than the flatter pattern of the vertical dipole. But that is purely a guess. Bottom line: both antennas work, so I’ll leave the dipole up for a while and see how it goes.

And are you ready for fall and winter? Now is the time to check your outside coax and connectors — before you notice your SWR is sky high and you have to brave that cold fall rain dripping down the back of your neck.

And speaking of antennas, my Yaesu FTM-300DR in the pickup truck started shutting itself off yesterday. My first thought was the wiring harness had gone bad…because that had happened before. But as I kept turning it on and watching as it powered down, I realized it was shutting down every time it transmitted an APRS beacon. Uh oh. I probably have a shorted antenna cable somewhere! This happened late yesterday so I’ve not had time to dig into it.

This week, I checked into #APRSThursday over LoRa APRS:

I also did some scoping of a potential project for my daughter. She likes to identify birds, so I looked at software that would allow me to identify birds by their songs. Looks like one of the most reasonable approaches is to use an old cell phone as the outdoor microphone, and have it connected wirelessly to a Raspberry Pi computer inside. More on this if/when it develops!

2. New on EtherHam

• Status of 21 AllStarLink Nodes at a Glance with a Custom TRMNL Plugin — I wrote a script to poll my AllStar nodes and give me an at-a-glance view of which nodes were up and running.

• Weekly Report: August 27, 2026 — Band Conditions This Week / Digital Radio News / Groups.io Digest. Digital Radio News is awfully light this week, with the exception of AllStarLink topics.

3. AllStarLink? Listen to Ham Radio Workbench #269

If you are into, or are interested in, AllStarLink, this is for you. Without further ado, here’s the link: HRWB 269 - AllStarLink with Jason McCormick N8EI.

N8EI is an active technical contributor on the AllStarLink Community Forum, frequently discussing system troubleshooting, software transitions, and node configuration.

4. QSO One Continues to Improve

You’ll want to take a look at QSO One, even if you don’t plan on using the software. Why? Because of the convenient Net Finder directory available on the QSO One website:

Why would you want to use QSO One? If you are looking for an all-in-one, integrated platform for all your nodes and modes, this could be what you’ve been waiting for.

For me, it looks like a great solution for my Uniwa F400. Note this excerpt from a post in the QSO One group on Facebook:

Using QSO One on a new Uniwa F400 has brought a ton of fun into my life since first installing the app. The features have helped me to gain access and experience some new-to-me digital networks (Allstar, Echolink, and YSF), and I appreciate that very much.

I wrote this early in the week and saw a few more announcements after I captured this piece. QSO One is rapidly evolving.

5. DroidStar 9M2PJU Replaced My DroidStar App

A strong alternative to QSO One is the DroidStar implementation by 9M2PJU. I’ve been testing it and finally deleted my old DroidStar app from my phone this week. The DroidStar 9M2PJU app won that battle and now reigns supreme, at least on my smartphone.

But I think I’m going to also install it on my Uniwa F400 device. Fingers crossed it works well there, too.

Learn more at https://droidstar.hamradio.my/ (but be prepared for multiple nag screens when you first open this link).

6. M17 Net

Last Saturday’s weekly M17 digital voice net on the Kansas City Wide system, led by net control Jeff AE5ME, focused on the technical evolution of the M17 protocol, upcoming firmware releases, and the protocol’s advantages over proprietary digital modes.

M17 Project & Technical Updates

M17 is a public domain digital voice and data protocol designed to eliminate the need for proprietary hardware or licensed codecs. It has received two $250,000 grants from Amateur Radio Digital Communications (ARDC) to fund its development.

• OpenRTX Firmware: Currently at version 0.4.3. The upcoming v0.5 release will be a major milestone, introducing SMS messaging and packet radio capabilities directly to radios like the MD380, MD390, and the CS7000.

• LinHT Project: A Linux-based handy talkie (HT) with a software-defined radio (SDR) core. This project enables multiple modes (M17, Tetra, DMR) and paging protocols like POCSAG to run on a single device.

• Hardware Compatibility:

  • Retevis C62: Development is ongoing for M17 support via the OpenRTX PR branch (Pull #15). Currently, it supports FM only. There was a brief discussion regarding the complexity of building the OpenRTX firmware from source for the Retevis C62. While the PR branch exists, it is not yet an “official” binary, requiring users to use a Linux command-line environment.

  • CC1200 Boards: New hats for the Pi Zero W 2 are available for M17-only hotspots.

  • Module 17: A project that allows converting existing mobile rigs into M17-capable radios.

Technical Q&A & Signal Routing

A significant portion of the net focused on how M17 signals move through different layers of infrastructure.

• SMS in QSO1: It was confirmed that the QSO1 software supports SMS text messaging via the M17 chat feature.

• Emergency Communications: The net highlighted the risks of relying on PTT over Cellular (POC) radios during disasters due to network congestion. M17 and the National Traffic System (NTS) were emphasized as more robust alternatives for handling health and welfare traffic when infrastructure fails.

7. Coming Soon: Cracking Open the Retevis C62 for M17

A $50-ish dual-band handheld built around a chip most hams have never heard of, running an open-source firmware port that’s still wet cement — that’s the Retevis C62, and it’s the next radio through my test bench. OpenRTX, the same open firmware project behind those RT3S M17 mods you’ve read about here, is now being ported to the C62’s ListenAI CSK6011B chipset, and I’ve spent the last few evenings getting a Windows toolchain to actually produce working firmware for it. Spoiler: it compiled clean, memory headroom to spare, on the first successful run — which sounds simple until you hear what it took to get there.

To be clear, what I’m trying to do is still experimental. Translation: it’s not ready for production. But I’m curious, and I know I’m not alone in trying to do this.

Well, it didn’t go smoothly. The official build instructions pointed at a Git branch that doesn’t exist where the docs say it does — turns out it only lives on a contributor’s personal fork. Then the container-based build tool quietly configured itself against the wrong internal workspace entirely, silently failing every dependency-fetch command with errors that looked like typos but weren’t — the kind of bug that eats a whole evening before you find the one diagnostic command that exposes it. I ended up manually placing four separate module repos by hand once I figured out what the build system actually wanted, and only then did the whole thing link successfully.

And that was just the build. Getting the finished firmware onto the actual radio turned into its own saga — burn mode entered fine, but the PC flatly refused to see the radio over USB, no matter what cable or computer I threw at it. Two “should’ve worked” programming cables later, and a lot of Device Manager archaeology across two completely different machines, I finally landed on the real culprit: not a driver problem, not a Windows problem, but the cable itself missing the one active chip this radio’s flashing mode actually requires. The right cable is in hand now.

I haven’t had a chance to actually flash the radio yet — that’s the next step, and I didn’t want to rush it just to hit a publishing deadline. So consider this the trailer: full build procedure, the module-workaround nobody’s documented anywhere else, the cable gotcha that cost the most time, and — assuming the C62 boots up on the other side — first impressions of OpenRTX running on genuinely new hardware. Next issue, once I’ve had the chance to actually pull the trigger.

8. PNWDigital Not-a-Net Gathering

I listened to much of the Wednesday evening “Not-a-Net” gathering held by the PNWDigital folks. I noted check-ins were made via Zumspot, Pi-Star, OpenSpot, BlueDV, and DV Mega devices, along with RF via DMR repeaters. That was a bit more texture than I expected —> many ways to get your message out on DMR.

• PNWDigital nets: https://pnwdigital.net/nets/

• PNWDigital welcome: https://pnwdigital.net/welcome-new-user/

9. Gadgets

Cardputer

I traveled a bit off the beaten path with this: the Cardputer ADV. It was about $42 from Amazon (affiliate link). As I flashed different firmwares to it and explored this tiny platform, I decided to give it a try with MeshCore. That required a special hat for the Cardputer: SX1262 LoRa Module w/GPS GNSS for Meshtastic (affiliate link).

Was this a useful purchase? Absolutely not. It was just for fun. The firmwares are interesting and I look forward to discovering what else I can do with the Cardputer.

Some people use these for hacking, but that’s not me. This is just a fun little device that slips into a shirt pocket. A word to the wise: if you use reading glasses, you might need a second pair to read the tiny screen!

I expected a fun weekend dev-platform toy. What I got instead was a proper hands-on review project, complete with a firmware bug, a Bluetooth mystery, and eventually a working MeshCore node. If you’re eyeing one of these for your own bench, here’s what actually happened, warts and all.

The keyboard takes some getting used to. There’s no touchscreen, so everything — including menus that look like they want a tap — is driven through the Fn key and a cramped arrow cluster hiding under the semicolon, comma, period, and slash keys. The keys themselves have a habit of double-registering if you’re not deliberate about your typing, which cost me a garbled WiFi password more than once.

The bigger surprise was the stock “factory” firmware — the demo suite M5Stack preloads, with its little hardware-test apps for the keyboard, IMU, SD card, and so on. The Clock app turned out to have a hardcoded UTC+8 offset that I could not override.

From there I went firmware-hopping, which turned out to be very interesting. You load firmware with the M5Burner app on your computer and a data-capable USB-C cable. M5Apps (a community launcher) fixed the keyboard quirks but couldn’t get WiFi to stick. Bruce (yes, that’s the name of the software) nailed the clock and timezone handling on the first try, confirming that the clock problem was not the hardware but the M5Stack demo firmware.

None of that was really the point, though. With a LoRa+GPS cap clipped onto the top, the real goal was turning this thing into a MeshCore node that could talk to the repeater already running on my roof and to my phone app.

That last stretch was the real adventure. Getting a MeshCore build flashed and receiving traffic on the Public channel was straightforward once the LoRa cap was installed. But getting it to join my own private #etherham channel was not easy. Bluetooth pairing failed repeatedly, even with the correct PIN. USB serial access turned out to be flash-mode-only on that particular build (a nice meshcore-cli detour taught me that the hard way). Even manually copying the channel’s secret key over didn’t get channel messages flowing.

What did work was sidestepping channels entirely. MeshCore nodes discover each other via broadcast “adverts,” and once the Cardputer and my T-Echo Plus heard each other’s adverts, direct messages worked immediately. No shared key was needed, since DMs use per-contact key exchange instead of a channel secret.

This is a genuinely capable (albeit quirky) little radio node, provided you’re willing to treat the software side as part of the hobby rather than as an inconvenience. If you’re comfortable flashing firmware, poking around GitHub issues, and treating a stuck menu as a puzzle instead of a dealbreaker, you may find the Cardputer ADV to be a fun diversion. However, if you just want a mesh terminal that works out of the box, this likely isn’t it.

Interesting: Mecha Comet

Shipping October 2026:

Mecha Comet, handheld Linux computer that's truly yours to own, build and mod.

What is it? HowToGeek has a write-up. I do like a small-but-powerful device!

New battery for Yaesu VX-6R

I mentioned last week that I bought a charger and a new battery for my Yaesu VX-6R. The original battery would not charge and was not recognized by the radio. I was hoping that putting it on a higher amperage charger might wake it up and allow it to accept a charge, but alas, that is not what happened. In fact, nothing happened. So that battery will go to hazardous waste. The new one charged swiftly and works fine. And the wall charger also works with my Yaesu FT-70D, so this is a “two-fer” for me.

TRMNL

Many moons ago, I supported a Kickstarter for a programmable display called TRMNL. I plucked it off the wall during a recent trip to the Portland QTH and brought it up to the Lake House.

It’s not doing anything fancy, like showing news or quoting famous people. I just want to see the weather at a glance, and for that, it works just fine.

The e-ink display draws very little power from the internal battery. I usually only have to charge this thing once every several months.

But I got to thinking about other ways I could use this nice screen. One thing I am always interested in is the status of my AllStar nodes. I have many because I experiment with them, but I usually only keep a handful “up” at any one time. So I wrote a custom Python script to poll the status messages at AllStarLink about my nodes. Then, with a little HTML magic, I was able to display the statuses of my nodes on the TRMNL.

Of course, it was really more complicated than that, so I’ve covered the ins and outs at EtherHam.com. That article also has the actual Python script I built to accomplish the polling of my node numbers.

10. QRT: End Transmission

Whew. Not the quality I like to share, but there is probably a little of something for everyone in this casserole-like issue of the Random Wire!

This week marked our 49th wedding anniversary. Those who have subscribed for a while know my wife has severe medical issues. She can no longer stand, sit, or walk. She can’t swallow or talk. Her disease has substantially impaired her cognition. And yet when I brought a bouquet of flowers to her today, she beamed out a great smile and her eyes told me all I needed to know. Over the past year, I’ve wondered if we’d see this milestone, but here it is: we made it to 49. Seizing these brief moments in the midst of this difficult journey is important and I’m grateful we still have time left together.

73, and remember to touch a radio every day!

I went a bit DMR crazy this week. Hit the DMR category on EtherHam and you’ll see what I mean. Here’s the elevator version: I used OpenGD77 on a $100 Retevis RT3S radio to install the PNWDigital codeplug. What I learned along the way is shared in my new DMR articles.

I also took a dive into Winlink, APRS, and EmComm. I wonder how this essay will land, especially with folks deeply experienced in search-and-rescue, incident command, and related activities. I suspect that my take on incident command may go against the grain for some folks. But maybe not.

A scripting error corrupted my work database, and that took a day to unravel the cause and another day to clean the data. Paraphrasing a database guru I learned from many years ago: there is no such thing as a perfect database, only those with an acceptable number of errors. The number of errors I had this week was unacceptable so I dove in and fixed the problem.

And that pretty much sums up my radio and technology week: a lot of digital radio and little bit of coding and cleanup.

I saw good uptake of the new EtherHam Groups.io space. Remember: in this first phase rollout, it is limited to 100 subscribers. We’re almost halfway there so sign up now if you are interested!

2. New on EtherHam

Winlink Tells You What Happened. APRS Tells You What’s Happening. — I’m afraid I went a bit overboard on this essay, simply because of my background in emergency services/management. I’ve been an EMT on a rural ambulance service, a hospital commissioner, an underground mine rescue EMT, a search-and-rescue member. I was part of an ARES group for a while and also served as a state agency representative to the state’s emergency management department. Those roles gave me deep appreciation for how incidents actually unfold and get managed in real time…and I think that biases my point of view toward those working at the forward edge rather than those in the command center. It’s a long read so I included a table of contents to help you. One of the best moments for me while I wrote this was learning more about how LoRa radio actually works to pick out signals buried in the noise.

This was “DMR week” at EtherHam, with parts 2, 3, and 4 published. Part 5 will cover on-air etiquette and troubleshooting — including PTT habits, why they matter more on digital than on FM, and the answer to: if you can’t scan the band to find people, how do you actually find someone to talk to?

Introduction to DMR, Part 2: The ID, the Radio, and the Hotspot — Part 1 promised the ID, the radio, and the hotspot before ever touching a codeplug — this is that piece, delivered after the fact. It walks through registering a free DMR ID at RadioID.net, then lays out the actual fork in the road on radio choice: the AnyTone AT-D878UVII Plus for anyone who wants a download-and-personalize codeplug the same afternoon, versus the Retevis RT3S and OpenGD77 path this series has been running on, for readers who want the talkgroup/frequency separation badly enough to tolerate a rougher first hour. From there it’s a full step-by-step Raspberry Pi hotspot build — parts, assembly, and WPSD configuration — reused and adapted from an earlier hands-on build, plus a hard look at how much hotspot hardware costs today versus when that build first went up. Read this one before Part 3, even though it was written after it.

Introduction to DMR: Part 3 — Building Your First Codeplug — I flashed a new Retevis RT3S with OpenGD77, built a codeplug from scratch pointed at my hotspot, keyed up — and got silence. Then got silence again, for an entirely different reason. This is the unvarnished version of that afternoon: what a codeplug actually becomes once the four concepts from Part 1 turn into specific numbers that have to match specific other numbers somewhere else, why DMR answers a single wrong value with total silence instead of a useful clue, and what it does to your troubleshooting when fixing a genuine problem changes nothing you can see. If you’ve been putting off building your first codeplug, or you’ve built one and can’t work out why it won’t talk to anything, this one’s for you.

I added an addendum at the end of this article, titled: The settings, field by field. The addendum gives you a screen-by-screen accounting of the settings I used in the OpenGD77 CPS.

It’s a long article, so if you want the answer to the question “does the Retevis RT3S DMR radio work when programmed with OpenGD77,” the answer is yes:

Introduction to DMR, Part 4: Loading Somebody Else’s Codeplug — Part 4 of the Introduction to DMR series takes the opposite approach from Part 3: instead of building a codeplug from scratch, I downloaded PNWDigital’s ready-made OpenGD77 codeplug — 125 channels, seven zones, someone else’s careful work — and it took longer than building one by hand. Not because the codeplug was wrong. Because a community codeplug is built for that community’s network, and my hotspot was pointed at BrandMeister. That single unasked question sent me chasing filters, timeslots, and call types for hours while the actual problem sat one layer up.

Along the way: the CPS button that’s invisible at the wrong browser zoom, why the codeplug arrives wearing another operator’s callsign, the difference between a repeater talkgroup list and a hotspot one, and talkgroups that stay asleep until you kerchunk them awake. The piece also includes something I felt would help you picture how DMR is structured — a single diagram of how zone, channel, contact, talkgroup list, and network actually chain together, and why you should build that chain backward from the network rather than forward from the CPS.

Retevis RT3S + OpenGD77 Cheat Sheet: Every Control, Remapped from the Radioddity GD-77 — OpenGD77 was written for the Radioddity GD-77, and it runs beautifully on the Retevis RT3S — but the two radios don't share a control layout. The GD-77 has four arrow keys; the RT3S has two buttons and a rotary knob, so the firmware reassigns them, and it reassigns them differently depending on whether you're sitting on a main screen or inside a menu. The result is that a documented shortcut doesn't fail cleanly, it does something else: the key combination the manual gives for changing zones will quietly change your transmit power instead. This sheet is every control translated for the RT3S, with the ones I've confirmed on my own radio marked as such and the rest flagged as untested.

Weekly Report: August 20, 2026 — Band Conditions This Week / Digital Radio News / Groups.io Digest. Summary:

• The predicted A-index of 11 suggests we’re not entirely out of the woods yet, so keep an eye on the numbers before investing an evening in a long-haul DX session.

• The MMDVM firmware for DMR received a merge (PR #362) that adds a configurable audio‑fidelity link option.

• AllStarLink’s app_rpt was updated to version 3.10.4; the patch series (PR #1205‑#1207) adds a client‑disconnect helper, removes duplicated sanity checks, disables autoservice during safe‑sleep, and fixes thread‑creation leak bugs.

• The LoRa APRS iGate repository received three commits on 2026‑08‑16 that update the T‑Deck hardware requirements, refresh the README, and add new image assets.

• Community posts on the AllStarLink forum report connection refusals from keyed nodes, intermittent telephone‑portal operation, and general remote‑node connectivity failures.

• Groups.io: 31 groups checked, 15 active, 493 total messages, 11 quiet. The most active groups in the set were Repeater Builder, APRS, and TinySA.

3. QSO One, the CGNAT Killer?

QSO One was built so hams could get on AllStarLink, EchoLink, IAX Direct, DMR, System Fusion, and M17 from a single app, without a Raspberry Pi, a radio interface, or a weekend of Linux. It's free. Sign up with your callsign, download it for Windows or Android, and you're on the air in about five minutes. More platforms are coming.

But one of the magical aspects of QSO One that we’re not hearing much about is that it works with CGNAT: “node mode and WT mode for AllStarLink are solid, with cellular and CGNAT handling that actually deals with carrier networks instead of just failing.”

As IPV4 addresses continue to become less available and CGNAT networks become more common, I suspect that QSO One’s secret sauce will be its ability to carry traffic through CGNAT networks.

4. APRS

#APRSThursday follow-up: the check-ins actually worked

In the previous issue, I mentioned that my #APRSThursday check-in attempts — from the LoRa tracker as KJ7T-3 and from APRSdroid as KJ7T-5 — went unanswered by ANSRVR and APRSPH. Turns out that wasn’t quite right. Digging through Sergei KJ5LOX’s APRS Observer dashboard, both check-ins are right there in the log, addressed to ANSRVR and timestamped clean. The messages went out fine; I just never got a reply back.

The reason surfaced in Michael Diturno’s weekly #APRSThursday recap: ANSRVR itself had been down, and Jeff W4JEW and the APRS Foundation rebooted it to get the net back on track for the 752 operators who checked in that week. So the silence wasn’t anything on my end — it was a server having a rough week, now fixed. Good reminder to double-check the infrastructure before assuming the bug is local.

One more thing that dashboard surfaced: KJ7T-5 (APRSdroid) is reporting altitude cleanly, but KJ7T-3 (the LoRa tracker) shows up as “Unknown” for altitude every time. Almost certainly a config setting I haven't dug into yet — but to even get in there, I'll need to break out the ToughBook. My regular laptop is ARM-based, and the T-Echo just won't talk to it over USB. More on that once I sort it out.

This week? I got checked in no problem:

Did you happen to notice the MeshCore checking from K7OLI? That looks interesting!

APRS OTA

A few days ago, I received a very nice email from Jared K0TFU, the ham who built https://aprsota.org. He wrote:

It’s been fun to watch hams begin to use this. One highlight for me was this string of QSOS from OE7BOE in the Tyrolean Alps https://aprsota.org/OE7BOE/ops/2.

I’ve now got a stats page up and running at https://aprsota.org/stats so everyone can see the usage of the service. We should pass 500 QSOs made using APRS OTA sometime later today, and have hams in 14 countries who have participated.

When you read his radiograms you can see this is fresh work. I predict APRS OTA will become another popular way to use radio and technology. It looks like it is off to a great start.

5. The Surprising Family Tree of Yahoo! Groups

If you’re a ham who misses the old Yahoo! Groups, here’s a piece of trivia that might reframe things: the person who built the service you’re pining for is the same person who built the one a lot of us use now.

Groups.io’s founder, Mark Fletcher, didn’t start with Yahoo! Groups — he started with a service called ONElist back in 1998, a free mailing-list host built for exactly the kind of niche system hams have always relied on. ONElist soon merged with a competitor called eGroups, and in June 2000 Yahoo! bought the combined company and rebranded it as Yahoo! Groups.

For a while it thrived. But Yahoo! management largely stopped investing in it. Over the next fifteen-plus years, the platform calcified under their watch: clunky moderation tools, a dated interface, and eventually real spam and security problems that group owners had no good way to address. Fletcher, watching from the outside as the company let his creation rot, eventually decided to build the successor himself. Groups.io launched in beta on September 23, 2014 — six years before Yahoo! finally pulled the plug on Groups on December 15, 2020.

That timing turned out to matter a lot for amateur radio. When the Yahoo! Groups shutdown was announced, hundreds of ham-related mailing lists — build groups, DX nets, kit-support forums, digital mode communities — suddenly needed somewhere to go, fast, with their years of archived messages intact. Groups.io was ready and purpose-built to catch them, and hams migrated in numbers well out of proportion to the general population of orphaned Yahoo! Groups. Today, ham radio groups punch way above their weight on the platform. By one count, 10 of Groups.io’s top 40 largest groups (out of roughly 100,000 total) are amateur radio communities, with the Softrock40 group alone landing at #4 overall with over 8,000 members, trailing only a couple of non-radio giants and IBM’s internal list. YouTuber Callum, better known as DXCommander, is often credited with giving the migration wave an extra push by publicly encouraging hold-out groups to make the jump.

We are living with the legacy of Yahoo! Groups. It didn’t vanish when Yahoo! finally killed the service in 2020. Instead, it moved, largely intact, onto Groups.io, which is why the platform now provides such outsized support to the amateur radio community specifically. The free, low-friction, member-run model that made Yahoo! Groups worth missing in the first place is exactly what its original builder set out to preserve and protect from further neglect when he built its successor.

If you’re active in a ham radio group on Groups.io today, you are standing on infrastructure with a direct lineage back to a scrappy 1998 mailing-list startup — one that Yahoo! bought, neglected for two decades, and finally killed, only for its original builder to come back and keep it going for communities like ours.

6. Old IEEE Articles on Amateur Radio & Tech

It’s been far too long since I dove into the past offerings of IEEE Spectrum. I did that this week, harvesting a handful of interesting titles for you to consider. Maybe one will spark a project idea.

• The Most Hackable Handheld Ham Radio Yet — March 27, 2024.

• Detect Quakes With “Raspberry Shakes” — September 27, 2023.

• Detect Solar Flares and Gamma-Ray Bursts for Less Than $100 — January 19, 2022.

• Hacking Ham Radio for Texting — November 15, 2021. This is the one that piqued my interest, because instead of two chips, I could probably use a single Arduino Uno Q to run it. It would cut the two-chip serial bridge in the original design down to one board's built-in RPC, gain Wi-Fi for APRS-IS gateway access, and get real Linux tooling for the UI/storage side. The tradeoffs would be battery life, needing to either port or replace MicroAPRS, and building a radio audio interface.

7. Gadgets

Yaesu VX-6R charging

I bought an $11 USB charging cable for my Yaesu VX-6R handheld radio. A side benefit: it also fits my Yaesu FT-70D handheld. I am finding that it works fine to charge the FT-70D battery but conversely, not with the VX-6R. I get a “NO BAT” message on the VX-6R’s screen when I try to charge with the USB cable. The radio operates as if it is on external power when I turn it on with the cable connected. When I disconnect the cable and try to turn on the radio: nothing.

USB Charger Cable for Yaesu Radio CD41 CD47 CD15A CD26 (this is an affiliate link)

So I’ve ordered a fresh battery and high-capacity charger, and neither are original Yaesu products. Fingers crossed on this purchase.

It may be that my original battery sat fully discharged too long and now the radio doesn’t even see it when it is connected. I’m guessing this might be the case. Perhaps fully charging it with the hi-cap charger will work. If not, I’ll still have a new battery.

Tri-Band Yaesu VX-6R Submersible Amateur Ham Radio Transceiver (144/222/440) (this is an affiliate link)

The VX-6R is a tri-band analog FM transceiver. The 220 MHz band operates at 1.5 watts out instead of the full 5 watts out on 70 cm and 2 meters. In the U.S. market, it comes with NOAA weather channels and maritime channels. But what I like most about the VX-6R is how it feels in my hand. It is a compact radio that fits my medium-sized hands just right. The case has enough texture to feel secure in my grip. And since I live in a place with a lot of winter rain, the IPX7 rating gives me some comfort when I carry this radio on my journeys.

8. Short Stack from the Interwebs

The Short Stack from the Interwebs, pulled from the aggregated feeds on EtherHam (etherham.com/feeds/), items from August 13–19.

SDR & Signal Hacking

• KrakenSDR Tested as a GNSS Jammer and Spoofer Localizer — RTL-SDR Blog — Putting the 5-channel coherent SDR to work finding the source of GPS jamming and spoofing.

• Carshepherd: An Android RTL-SDR App For the Early Awareness of Nearby Emergency-Service Vehicles — RTL-SDR Blog — A pre-release Android app that pairs an RTL-SDR dongle with your phone to flag nearby police/fire/EMS traffic.

• Detecting Dark Matter’s Mark with an RTL-SDR Based DIY Radio Telescope — RTL-SDR Blog — An IEEE Spectrum writeup on using an RTL-SDR, LNA, and homebrew horn antenna to measure the galaxy’s hydrogen line.

• VibeSDR Jr: Apple Watch RTL-SDR, KiwiSDR, UberSDR Client now Available — RTL-SDR Blog — The AI-vibecoded SDR client shrinks down to run on your wrist.

• More Information about the FrameRF Technical Surveillance Counter-Measures Platform — RTL-SDR Blog — A deeper technical follow-up on the Italian-built TSCM platform for bug-sweeping.

• AntSDR T510 Pre-launch: A 1 MHz to 6 GHz SDR with 2 GHz Bandwidth and a Built-In NVIDIA Jetson — RTL-SDR Blog — A high-end SDR platform pairing an AMD Zynq RFSoC with an onboard Jetson for AI-assisted signal work.

Digital Modes & Mesh

• Building an Off-Grid Meshcore Network, One Node at a Time — QRPer — A QRP-flavored look at building out a Meshcore network on sub-1W, 900 MHz nodes.

• LoRa APRS iGate V4.0.0: New WebUI, Live Stations Map, and Channel Activity Detection for ESP32 Digipeaters — Hamradio.my — A major update bringing a Bootstrap WebUI and live Leaflet station map to the ESP32 LoRa APRS iGate project.

• qFT8 Review: Is This the Best FT8 Android App for Portable Ham Radio? — Radio Hobbyist — Running FT8 from a park or summit without hauling a laptop.

• vBand USB Adapter vs CW Hotline as an Adapter vs Vail Adapter — With Varying Frequency — A hands-on comparison of internet-CW hardware adapters, including notes on latency while traveling.

• Ham Radio and Digital Data Modes: How Low-Power Signals Can Communicate When Voice Cannot — Amateur Radio Today — A primer on why digital modes keep working when voice comms break down.

Gear, Builds & Reviews

• AnyTone AT-779UV with UV-72 Antenna and Cable Review: A Compact 20-Watt VHF/UHF Mobile Radio — Amateur Radio Today — A mobile transceiver review aimed at operators who want more than a typical HT but don’t need a full base rig.

• A Basic Elecraft KX2 Setup & Orientation Video — QRPer — A 22-minute, no-frills walkthrough for getting a new KX2 up and running.

• CYD Ham Dashboard: Turn a $10 ESP32 Cheap Yellow Display into a Touchscreen Ham Radio Shack Monitor — Hamradio.my — A cheap ESP32 display turned standalone shack monitor with greyline, propagation, and DX spots.

• QMX QRP – It works! — With Varying Frequency — Getting the feature-packed QRP Labs QMX up and running after a firmware update.

• K9ZW 630m Station Build – a Few Steps Closer — With Varying Frequency — Sourcing the last cables, connectors, and adapters for a 630m station build.

• Time for antenna work. — Amateur Radio Weekly — Notes from replacing a radial plate on a Hustler 4BTV vertical.

• A Few Words from Momobeam about the Mechanical Design of Its HF Directional Antennas — On All Bands — A look at the mechanical engineering behind Momobeam’s HF beams, spotted at Hamvention.

• Geeky Gift Building – Sweeping radar style ADS-B traffic display — With Varying Frequency — A 3D-printed, radar-sweep-style ADS-B display built as a gift.

POTA & SOTA Field Reports

• Ham Radio Portable Operating Insights: Transitioning from a POTA Activator to Hunter — On All Bands — Lessons learned after years of activating parks, now applied to hunting instead.

• W8TMI: QRP Along the North Shore of Lake Superior — QRPer — A Michigan Upper Peninsula activation report from a self-described “frequent flyer” of the Mackinac Bridge.

• QRP Along the River: A POTA Activation along the Tweed Estuary — QRPer — An early-morning coffee-fueled activation on the Scottish coast.

• KB2PIZ: A Rough Start Turns Into an Easy POTA Activation — QRPer — A shaky beginning that turned into a smooth three-hour activation before work.

• GB1DOG Active in 26 — Ham Radio Operator M0YKS — A special-event station making noise across HF and satellite bands through the month.

Shortwave & Listening

• C.Crane Interview: Radio During Hurricane Helene — The SWLing Post — A conversation with C. Crane about the role radio played in the aftermath of Hurricane Helene.

• The New XHDATA D-226/D-228 DSP Shortwave/AM/FM/WX Portable — The SWLing Post — XHDATA is prepping two new portables, the D-228 and D-226, with NOAA weather radio built in.

• A Glimpse of Korean War Clandestine Radio in Operation Chromite — The SWLing Post — A reader spots wartime clandestine radio work in a charity-shop movie find.

• The Morrow CM-1 receiver – A relic of the cold war’s effect on amateur radio — KA7OEI — A deep dive on a CONELRAD monitor receiver born of Cold War civil defense requirements.

• Why is Lahti on the Dial of the Receiver? Where is Lahti? — Solder Smoke — Bill Meara chases down an unfamiliar city name printed on an old receiver dial.

DX, Contests, Satellites & Awards

• ANS-228 AMSAT News Service Weekly Bulletins — AmSat — This week’s bulletin covers the call for AMSAT Space Symposium presentations and a CubeSatSim feature in QST.

• AMSAT Canada Begins Offering Membership Options — Amateur Radio Daily — AMSAT-CA opens up membership to help fund its support of amateur radio in space.

• Happy 50th Anniversary to the Araucaria DX Group! — On All Bands — A tip of the hat to one of DXing’s most accomplished contesting organizations.

• Kopernik Observatory Seeks Amateur Radio Operators to Track August 19 Balloon Flight — ARRL News — An APRS- and SSTV-equipped educational balloon needs trackers across the northeast.

• ARISS Receives Challenger-7 Recognition — ARRL News — Amateur Radio on the International Space Station picks up a national honor.

• The ARRL Solar Update — ARRL News — This week’s propagation and solar activity forecast from NOAA’s Space Weather Prediction Center.

• Contesting 101: Building a Workbench & Basic Ham Radio Troubleshooting Techniques — On All Bands — A veteran contester’s series continues with workbench setup and troubleshooting basics.

• CHOTA 2026: Churches and Chapels on the Air — Amateur Radio Daily — This year’s Churches and Chapels on the Air event is set for September 12.

Podcasts, Community & Events

• AmateurLogic 220: It’s Going To Get Meshy — Amateur Radio Weekly — This episode covers mesh networking experiments, including a solar-powered mesh node build.

• Amateur Radio Weekly – Issue 434 — Amateur Radio Weekly — This week’s roundup, including a PDF/CSV FCC “Call Book” for low-bandwidth QSO chasing.

• LHS Episode #626: The Weekender CXLII — Amateur Radio Weekly — Linux in the Ham Shack’s latest weekend-project roundup.

• SolderSmoke Podcast 266: TROUBLESHOOTING! Test Gear, LA6NCA, ZIA Rig, Australia, Nuvistors, 75 AM, MAILBAG — Solder Smoke — The latest episode digs into test gear and troubleshooting war stories.

• Looking Back at Ham Radio Friedrichshafen 2026 — On All Bands — A recap from an exchange student’s visit to the biggest ham radio show in Europe.

• Recent SKs: NU2J, K3SHD, K7AJM — KB6NU — Remembering three hams who shared a passion for the hobby.

Advocacy, Licensing & Growing the Hobby

• 10-Year-Old Receives Ham License and More — ARRL News — A brand-new young Technician-class ham in Arizona gets a warm welcome to the hobby.

• Making hams of hackers — KB6NU — A retired ham’s ARDC-funded mission to turn hackers into licensed operators.

• 9/11 ‘We Do Remember’ Special Event Returns for 6th Year — Amateur Radio Daily — The Alabama Contest Group’s K4 America special event returns for its sixth year.

Software & Apps Roundup

• 9M2PJU HamClock Installer: Space Weather, VOACAP Propagation, and Shack Automation Dashboard — Hamradio.my — A modernized HamClock distribution with native OHB backend integration and multi-arch Docker support.

• Open Hamclock Backend (OHB): Keeping Thousands of HamClocks Alive with Open Source Infrastructure — Hamradio.my — A community-run replacement for the sunsetting Clear Sky Institute backend that keeps HamClocks worldwide running.

• Android SSTV Alarm: The Open-Source Ham Radio Alarm Clock That Forces You to Decode Slow-Scan Television to Wake Up — Hamradio.my — An alarm clock that won’t stop until you’ve decoded an SSTV image.

• EmComm Tools OS Community Edition: The Ultimate Turnkey Linux Distribution for Off-Grid Ham Radio and Tactical Cyberdecks — Hamradio.my — A technical breakdown of the open-source Linux platform built for off-grid emcomm.

• DXLens: An iOS App Combining Shortwave Schedules, Propagation Data and Public SDRs — RTL-SDR Blog — A new iPad/iPhone app for listening to remote SDR receivers alongside schedules and propagation data.

Linux, Homelab & Self-Hosting

• The best way to run Docker on Proxmox depends entirely on your hardware and use-case, and it took me years to realize that — XDA Developers — Docker-on-Proxmox isn’t a one-size-fits-all decision, and this breaks down when to use which approach.

• I wish I’d learned these 5 simple Proxmox skills sooner — How-To Geek — A little practice up front that could have saved much bigger headaches later.

• Luckfox Lyra PLC – A Linux-based Rockchip RK3506B industrial controller with RS232, RS422, RS485, CAN bus, and relays — CNX Software — A Linux-based PLC with the kind of I/O that suits remote station and sensor automation.

• Google Chrome is now available for Arm Linux. We tested it on a Raspberry Pi 5 — CNX Software — Chrome finally lands officially on 64-bit Arm Linux, tested on Pi OS.

• Using the Khadas Mind Graphics 2 (NVIDIA RTX 5060 Ti USB4 eGPU) on Ubuntu 26.04 — CNX Software — Getting a USB4 eGPU dock working cleanly on Ubuntu.

• Waveshare PiRack-M6F 6-node rack unit for Raspberry Pi 4/5 brings all ports to the front — CNX Software — A 2U rack-mount cluster kit for up to six Pi 4/5 boards.

• I finally self-hosted my passwords, and it’s simpler than I expected — XDA Developers — Moving off a cloud password manager and onto Vaultwarden.

• Why CachyOS is the better Arch-based distro if you’re not gaming 24/7 — How-To Geek — A case for CachyOS as a daily-driver Arch distro beyond its gaming-performance reputation.

• Pine64 hits pause on Linux devices due to RAM and eMMC shortage/high prices — CNX Software — The ongoing memory crunch forces Pine64 to pause new Linux hardware.

• Why Most Linux Users Avoid Flatpak: The Honest Technical Case Against Universal Packaging — Hamradio.my — A technically grounded look at Flatpak’s disk bloat, sandbox escapes, and stale dependencies.

• USBridge-KVM 2.0 – An open-source IP-KVM with BIOS access over SSH, OCR, and AI support — CNX Software — A compact open-source IP-KVM for remote management of servers and PCs, including systems that won’t boot.

9. QRT: End Transmission

I’m very curious how the DMR radio will work. So far, I’ve been pleased with the Retevis RT3S DMR handheld. Discovering the differences between it and the Radioddity GD-77 radio was enlightening and helpful. I’m happy I was able to map important key combinations this week.

And if DMR traffic in my neck of the woods proves interesting, I might start looking for a mobile rig to carry in the pickup truck. The PNWDigital group has a good number of DMR repeaters in the region so I would have reasonable coverage most of the places I regularly travel to and from.

On the tech and software side of the house, I’m looking at notifier systems like Pushover and Pushbullet. It would be convenient to develop a stack of circumstances that trigger automatic notifications pushed to my smartphone. My tech stack is deep enough at the house that it’s actually hard to notice if something has gone offline or if the IP address changed because the upstream provider made changes. I have a notifier set up for some websites but those “down” notices come through as emails, meaning they get swamped by all the other emails I receive. For the sites I manage, getting those notices by SMS or pushed to an app would be helpful.

And that’s it from the great Pacific Northwe(s)t, where we are actually in a drought and experiencing a record number of wildfires. I hope all who have been affected get the help they need to recover from these disasters.

73, and remember to touch a radio every day!

Windows

Last week it was a Debian 13 update with security vulnerabilities plugged. This week, it’s Windows: Microsoft Plugs Nearly 400 Security Holes. One of the most fundamental ways to protect yourself is to keep your computer updated.

August 11, 2026: Microsoft today released updates to remedy at least 398 security vulnerabilities in its Windows operating systems and supported software, including one weakness that is already being actively exploited and two others that were publicly detailed prior to today.

HamClock OHB

If the version number on your HamClock OHB display is red, an update is available. Click that red version number and follow the prompts to upgrade. Nice additions since I last upgraded:

• An email icon that presents a link to the OHB status page. Useful.

• An airplane icon that opens an ADSB flight tracker for your location. Interesting.

• A blue wind icon that opens the Windy.com website.

Screens are presented as a collage below because inserting them all here would take up too much space:

1. QRV: Are You Ready?

It’s been a rather frustrating week. Usually, I’m gleeful when I find problems to fix. This week, I just wanted things to work…but they didn’t. Resolving issues this week dramatically diluted my writing time. That I do find frustrating.

And I’ll gripe a little bit (again) about Claude’s Sonnet 5 model because it jumps to conclusions. That ended up costing me several hours of time this week as I chased a couple of long, involved issues down dark and twisty rabbit holes, when time was in short supply. The Opus 5 model does much better but it also burns through my credits much faster. The problem here is really twofold: I don’t know Sonnet is going to make mistakes until it makes them, and I’d rather not spend the money on Opus if I don’t have to.

Huh. Here I am complaining about AI. I wonder if this is going to become the new normal on repeaters. You know the drill: what’s the weather, what equipment are you running, how is your health, and now, what have you been doing with AI?

I have to say, though: it is so very easy to overlook all the great help now available to me through the many AI engines available. I have far more successes than difficult detours. It feels a tiny bit uncomfortable to say this plainly, but I will: at this moment in time, I am grateful for AI.

2. New on EtherHam

• Writing EtherHam Content: Untangling the Ball of Yarn — Meetings (and radio nets) rarely move in a straight line. Someone circles back to a point you thought was closed thirty minutes ago, and a strict outline can’t keep up. Thirty years of facilitating meetings taught me why; mind mapping taught me how to actually capture it. This piece walks through that shift — from a hallway conversation with a frustrated note-taker decades ago to the technique I still use today, turning a tangled ball of yarn of ideas into the straightened, sequential pieces you read on EtherHam.

• LoRa APRS: Part 3 — A T-Deck Plus Tracker, Offline Maps, and a Long Detour Through OpenStreetMap’s Terms of Service — A LilyGo T-Deck Plus running LoRa APRS will render an offline vector map of the terrain you’re standing in, hold threaded APRS conversations, and pass Winlink email — none of which a plain tracker does. Getting there took most of a day and five stacked failures, each one hiding the next: a wiki that contradicts the firmware it documents; an SD card in the wrong filesystem; 1,793 downloaded map tiles that turned out to be OpenStreetMap’s “Access blocked” graphic saved 1,793 times; a tile generator that had to be compiled from source inside Linux; and — after all of that — a map that had been working the whole time but wouldn’t render until I pressed the zoom button three more times. Somewhere in the middle, the tracker started reporting itself in the Southern Ocean while its own screen showed the correct coordinates. If you just want something that beacons your position, buy a T-Echo and enjoy long battery life. If you want the map and the messaging, here’s the whole path with the wrong turns left in, because the wrong turns are the part worth reading.

• Weekly Report: August 13, 2026 — Catch up on band conditions, digital radio news, and the Groups.io digest.

3. New: EtherHam Community Space

Over the years, the conversations around the intersection of amateur radio and technology have grown incredibly rich. While the newsletter is a great way to share these concepts, I want to give us a dedicated space to hold deeper, multi-sided discussions.

Today, I am excited to officially launch the EtherHam Groups.io Community.

This is our new clubhouse on the web—a text-based space where you can ask technical questions, share project updates, discuss technology integration, shape future Random Wire and EtherHam topics, and connect directly with other subscribers.

⚠️ A Note on Capacity (First-Come, First-Served)

Because we are launching on a lean, independent infrastructure, space is strictly limited to the first 100 members.

To protect our space from automated bots, spam, and bad actors, membership requires manual approval. We are prioritizing licensed radio amateurs, though tech-minded enthusiasts are welcome too.

How to Secure Your Spot:

1. Click here to visit the group homepage: groups.io

2. Click the Apply For Membership button.

3. You will receive an automated email asking for your amateur radio callsign (or an explanation of why you want to participate).

4. Reply to that email immediately to lock in your application for review.

Once we hit our 100-member cap, the doors will close while we settle into this new space. If you want to help shape the foundation of the EtherHam community from day one, please submit your application today.

See you in the ether,

Tom KJ7T
Editor, Random Wire
www.randomwire.us

4. IP400: The Story Behind This Important Project

I’m sure you’ve noticed the changes over time on VHF/UHF repeaters: coordinated frequencies sitting quiet, hardware from the 1990s doing the same voice relay job it’s always done, and a shrinking pool of operators who show up to keep it maintained. For years, my friend Steve Stroh N8GNJ has been touting a project called IP400, and for good reason. A recent section of his Zero Retries newsletter will likely convince you that IP400 really is an exciting initiative in our amateur radio hobby. Why? Because he’s right.

But where did IP400 come from? It traces back to a longtime radio amateur, Martin Alcock VE6VH — who spent years designing commercial broadband wireless systems before focusing that experience toward amateur radio. Alcock looked at what already existed — AREDN, HamWAN, New Packet Radio — and noticed they all shared the same limitation: they either ran on license-exempt spectrum with real power restrictions, or they came with enough administrative overhead that they never spread much beyond a dedicated core of builders. What amateur radio didn’t have, in his view, was a data and mesh networking system built from scratch for the hobby, on ham bands, without those constraints. That observation became IP400, developed under the Alberta Digital Radio Communications Society (ADRCS), the group Alcock helped found in 2022 and where he’s been able to line up grant funding — including a 2025 ARDC grant — to keep development moving.

As the project has developed, it became clear that IP400 is not trying to replace DMR, D-STAR, C4FM, or your local FM repeater. Instead, it sits next to them. IP400 is additive to our hobby, not subtractive. The hardware — a controller board called the AMNC — talks to a radio you already own and adds a data layer compatible with AX.25 KISS framing, with an eye toward working alongside Winlink, AllStarLink-linked repeaters, and eventually AREDN’s mesh network. The goal is to give existing infrastructure a reason to be upgraded rather than replaced.

What’s running today rides on ordinary FM audio, but that’s really just the first step. Alcock’s longer-term plan involves dedicated software-defined radios with a direct I/Q interface, aimed at speeds well beyond what’s possible when squeezing data through a mic jack. Where that lands, and how fast, is exactly the kind of thing Steve is covering well.

I think there’s another reason for this, one that’s a little harder to say out loud: a lot of newer hams just aren’t as focused on voice communications as the hams who came before them. These new hams grew up in a data-driven, IP-enabled world, and IP400 speaks that language. I’d bet this brings a fair number of tech-fluent people into the hobby who might not have bothered otherwise.

In my view, IP400 is one of the most exciting and fundamental developments in amateur radio today. I’ve not covered it in the Random Wire newsletter because Steve does such an outstanding job of keeping his subscribers updated on IP400. This project is worth digging into, getting excited about, and supporting. IP400 may well be one of the most important technology improvements we’ll see in amateur radio.

For more, I suggest following this topic in the Zero Retries newsletter where it is sure to be very well covered by the ZR team.

5. Curious About 44Net?

Here is your chance to learn about 44Net and about John Burwell KI5QKX, on Eric Guth’s great podcast series, QSO Today, in Episode 539.

John Burwell, KI5QKX, found his way into amateur radio through 44Net, the Class A public IP address space set aside for amateur radio almost 50 years ago, now managed by ARDC. John’s interest in connecting devices over the Internet led him to this remarkable ham radio resource. In this interview, we go deep into IP addressing and networking, opening the door to new ways licensed amateurs can learn, experiment, and build Internet-connected projects. KI5QKX is my QSO Today.

6. QSO One 3.8.5 — Your Update Has Arrived

3.8.5 is live for beta testers, and this one is almost entirely about audio. From the announcement:

The mic gain scale actually works now, a real 0 to 100 instead of everything living in the bottom sliver. There is a new audio test for every network, you talk, it meters you, and it grades you hot, good, or quiet while you adjust. And the clever part, once the app has heard enough stations on a network, it grades you against how that network actually sounds, not against a number from a lab. Every network also gets transmit protection now so you cannot blow anyones ears off, Windows choppy audio got a real fix, and Bluetooth PTT buttons finally respect your PTT mode setting.

Socials:

• Discord: https://discord.gg/4N6Wc3fsEv

• Facebook: https://www.facebook.com/groups/1483876283506992

• Reddit- https://www.reddit.com/r/QSOone/

It’s good to see this project moving forward.

7. POTA Heil Headset

I’ll just say this here: this new headset from Heil isn’t just for Parks On The Air, but it’s a great choice for POTA. From Michael Martens KB9VBR:

8. Waiting on Two Radios: DMR & M17

Retevis RT3S DMR Radio

I ordered this a few weeks ago:

RT3S Dual Band DMR Radio Non-GPS/Built-in GPS

Why? Because I want to try OpenGD77 as the codeplug editor, and OpenGD77 says the RT3S is compatible. In fact, there are plenty of blog posts and reviews available on this exact pairing. (I’m not hyperlinking this radio here because I’ve not received or reviewed it yet.)

I got interested in this after a subscriber asked me how to get into DMR at a reasonable cost. Of course, I do like my AnyTone 878 radio very much, but that’s a more premium option than a $100 radio and free CPS software.

I promised a part two on DMR that I’ve been picturing as a how-to on developing your own codeplug. The RT3S with OpenGD77 is going to fit right into that slot. I’m looking forward to getting this working and sharing the journey with you.

A few days ago, the RT3S radio was in Chicago. Wednesday, I received the extra bits: a speaker-microphone, antenna, and spare battery. Maybe the RT3S will arrive in time for initial impressions…but probably not.

Retevis C62 Dual-band Radio…for M17

And then I ordered another radio from Retevis:

Retevis C62 UV Dual Band AI Noise Reduction 5W Long Range Durable Business Two Way Radio

What comes up on that page is a 6-pack of radios. I ordered the single radio for $55.

Then I got an email: “We noticed that you purchased the (EU version) radios. To avoid any issues, would you like us to change your order to the US version[gmrs] instead?”

I paused and thought for a few minutes about this, then replied: no. The experimental work being done by the M17 Project with the C62 is happening — I believe — in Europe, so perhaps I should stick with that version. We’ll see, of course, if it works once it gets here and I load OpenRTX on it. If it works I’ll have an M17 handheld for $55! If it doesn’t work, I’ll have another radio for the unused radio bin.

9. APRS OTA

I’ve not tried this yet, but APRS OTA does sound interesting:

APRS OTA combines the vibe of a POTA activation with a native APRS messaging bot and a website to show what’s happening. Find an operator on the air, send one message and a position report to work them, and your contact is logged, mapped, and scored here as it happens.

A bot serves as a relay and automatically logs contacts:

APRS OTA is an activity and a bot…the OTA bot relays the exchange and logs every contact as it happens. There is nothing to install and no account to create: if you can send an APRS message, you are already in.

It’s a three-part system, with a host, a bot, and chasers.

Intrigued? Visit https://aprsota.org/ for more. If you try it, let me know what it’s like!

10. And Then I Had an APRS Messaging Moment

I was driving to get my morning coffee, watching carefully for deer. Sure enough, I had to hit the brakes so a young buck with velvet antlers could bound across the road. I’ve learned to look where the deer came from, too, and saw a doe and fawn turn back into the bushes. It was at that moment that I saw my APRS radio and a thought completely unrelated to wildlife popped into my mind.

I’ll write this up in long form and post it to EtherHam.com, but my EtherHam website is offline at the moment due to a major power loss at the web host’s Phoenix data center. No word on when services will be restored (and I hope “power loss” is not code talk for “fire in the data center” because that would be very bad).

What was that APRS thought? I wondered if I could send an APRS message from APRSdroid (I’m running the 9M2PJU Mod version) to my LoRa APRS tracker. Surely that could not work, because one system flows over cellular data and the other is LoRa radio. But the aha moment for me was realizing that both probably pass messages via APRS-IS. So I tested this by sending a message from my phone (KJ7T-5) to my tracker (KJ7T-3).

I was surprised and delighted to find this worked perfectly. Replying from the tracker to the phone also worked, so APRS messaging works in both directions.

Let me just pause and sit with that for a moment, because it was a revelation to me. We get pretty locked in about whether we’re working over RF or cell or satellite or wifi or whatever. Hung up on this, even. Lost in those details is the realization that APRS shares a common backbone: APRS-IS.

APRS-IS stands for the APRS Internet System, and it’s the quiet piece of infrastructure that ties every flavor of APRS together. Stations riding RF — my LoRa tracker included — reach it through something called an IGate: a small relay station, often nothing more than a radio and a cheap computer in someone’s attic (or in my case, the garage), that listens to local radio traffic and forwards it onto the internet. Apps like APRSdroid skip the radio step entirely and log straight into APRS-IS over cellular data.

Once a packet lands on APRS-IS, its origin stops mattering. It’s all just APRS-IS traffic from that point on — it can get relayed back out over RF somewhere else, or handed off to a site like aprs.fi to show up on a map. That’s what clicked for me on the drive: my phone and my tracker aren’t two separate systems that happen to talk to each other. They’re two different doors into the same room.

And this is the secret sauce that makes APRS such a powerful tool: different radios, different frequencies, different modes, different mechanisms can all communicate cleanly because they all use the same pipeline behind the scenes.

There is more to this test, because I also tried Winlink between my laptop and my APRSdroid app. That test yielded a surprising-but-educational result I’ll share once EtherHam.com comes back up.

Finally, in a “why not?” moment, I tried checking in to #APRSThursday from the tracker (LoRa APRS as KJ7T-3) and from APRSdroid (KJ7T-5). Unfortunately, both ANSRVR and APRSPH did not respond to messages or commands. I hope the #APRSThursday folks get that fixed.

11. Short Stack from the Interwebs

Well, with EtherHam.com offline, I had to resort to a special mega feed URL which fortunately worked. The following Short Stack items were harvested from this week’s aggregated ham radio feed, covering items from August 5–13, 2026.

SDR & Signal Hacking

• Product Spotlight: A Look at the KiwiSDR2 Receiver (Video) — OnAllBands — A walkthrough of the standalone KiwiSDR2, covering 10 kHz to 30 MHz with nothing more required than a computer and internet connection to get going.

• Demod: A New iOS/iPadOS App for Exploring Remote Receivers — The SWLing Post — A new app connecting to KiwiSDR, SpyServer, and rtl_tcp servers with a built-in directory of public receivers baked in.

• MagicSDR – IOS interface to RTLSDR version 26.04 released — Mac Ham Radio — A plug-in-architecture panadapter/waterfall app for RTL-SDR dongles, covering AM/SSB/CW/NFM/WFM demodulation from an iPhone or iPad.

• Using a 5 inch Naval Gun Mount as a Rotor and Being Asked by NASA to Listen for Artemis — SolderSmoke Daily News — Pete N0OY’s station includes a repurposed naval gun mount as an antenna rotor and a 10 GHz rainscatter contact spanning 91 miles — genuinely one of the wilder homebrew station tours out there.

• Checking your Own Signal on FlexRadio — With Varying Frequency – Amateur Radio Ponderings — A quick how-to on using FlexRadio’s built-in features to self-monitor your transmitted signal.

Digital Modes & Mesh

• Digital Voice over HF with FreeDV Information from Kirk KN6UMV — MichiganOne DMR Tech Net — Follow-up notes from a net discussion on FreeDV, with pointers on where Maidenhead grid squares fit into the picture beyond just contesting.

• DX Explorer and the Thinknode Meshcore M1 transceiver — Roger G3XBM’s (Mainly) Amateur Radio Blog — A rundown of a new video on the Thinknode M1 LoRa transceiver, with a reminder that Meshcore vs. Meshtastic popularity varies a lot by region.

• QSO One 3.8.5 – Getting closer! Your update has arrived — MichiganOne DMR Tech Net — A beta release focused almost entirely on audio fixes, including a mic gain scale that finally behaves like a real 0–10 range.

• SliceLogger — With Varying Frequency – Amateur Radio Ponderings — W4TME’s logging tool gets a rebrand and a fresh v1.0.0.0 general release on GitHub.

• Digital Mobile Radio Market Size to Hit USD 16.90 Billion by 2032 — MichiganOne DMR Tech Net — An industry market report pegs U.S. DMR growth at a 12.81% CAGR through 2032, largely driven by public-safety adoption rather than the hobby side.

• Travel Internet CW — With Varying Frequency – Amateur Radio Ponderings — A cautionary field report: internet CW over shipboard wifi via a vBand adapter proved unusably laggy, and a backup Vail Adapter hit its own snag mid-trip.

Gear, Builds & Reviews

• Pebble HF ordered — With Varying Frequency – Amateur Radio Ponderings — The Pebble HF kit opened for purchase this week, and K9ZW put in his order.

• New Product Spotlight: Hamplus AS-603WL Black Automatic Remote HF + VHF 6 x 3 Antenna Switch — OnAllBands — A look at the Brazilian-made Hamplus remote antenna switch from Celso PP5CFS and Marcus PP5MS.

• Mark’s First Impressions of the PK MW Loop — The SWLing Post — A Scotland-based listener’s first impressions of Paul Karlstrand’s PK Loop magnetic loop antenna, ordered after a chance conversation while traveling in Greece.

• QMX (not QMX+) is becoming a firm favourite — Roger G3XBM’s (Mainly) Amateur Radio Blog — A nod to QRP Labs’ tiny QMX rig, which keeps showing up as a favorite in the field despite its small footprint.

• Ford F-150 Radio Install – VGC N7600 — Above Average Terrain — Bob K0NR traded in his 2013 F-150 for a 2025 model and walks through installing a mobile rig in the new truck.

• Rob spots a rare Hygain Galaxy R-1530 on eBay — The SWLing Post — A vintage-radio spotting: a Hygain Galaxy R-1530 listed “for parts or not working” at $749.95 — buyer beware, no returns accepted.

• Book Review: VHF, Summits, and More – Having Fun with Ham Radio by Bob Witte K0NR — Q R P e r — A guest review from Jock Elliott (KB2GOM), reflecting on nearly 40 years in the hobby since his Novice days.

• Margaret - A New SOTA Machine — N1CLC — An extensive build log on outfitting a new Subaru Outback Wilderness for SOTA work: mobile radio install, dedicated power distribution, a Starlink Mini, and a full house battery/solar system.

• Silly me, did not take inventory on order arrival woes — With Varying Frequency – Amateur Radio Ponderings — A DigiKey order for a touch-paddle project turned up short a hundred MOSFETs, discovered only after months of sitting unopened.

POTA & SOTA Field Reports

• The Battle of the Bands: Activation of Saint Stanislaus Conservation Area US-10954 — Q R P e r — Mark (KB2PIZ) turns an 8-minute detour near the St. Louis airport into a quick POTA activation between flight legs.

• Meeting Friends on the Summit: A Special SOTA Activation at North Berwick Law — Q R P e r — Thomas K4SWL meets up with several UK-based ham friends for a SOTA activation during a trip to southeastern Scotland.

• Hunting Fossils and POTA Contacts on Cocklawburn Beach in Beautiful Northumberland — Q R P e r — A coastal POTA outing combining fossil hunting with contacts from a KX2 and a Packtenna random wire antenna.

• KK6IK: Summer Mornings, Iced Coffee & QRP — Q R P e r — Scott Nacey weighs the Elecraft KH1 against the KX2 for travel-friendly POTA operating during a Rhode Island visit.

• Parks on the Air (POTA) — Lincoln County Amateur Radio Club — The club has set up a POTA activation account under its call sign, aiming to give newer members an easy way to get started.

Shortwave & Listening

• A Glimpse of Korean War Clandestine Radio in Operation Chromite — The SWLing Post — A reader spots radio gear featured in a Korean production about the Incheon landings, starring Liam Neeson as General MacArthur.

• Radio Bonaire 1530: A Mediumwave Station Built for Emergencies — The SWLing Post — A new off-grid, continuously broadcasting AM station on Bonaire, purpose-built to keep residents and visitors informed during emergencies.

• Texas Radio Shortwave: Schedule for September & October 2026 — The SWLing Post — Updated broadcast schedules for the fall season on Texas Radio Shortwave via WRMI.

• Carlos’ Illustrated Radio Listening Report and Recordings (August 1 – 8, 2026) — The SWLing Post — Political cartoonist Carlos Latuff’s latest illustrated shortwave report explores Javier Milei’s Argentina through the airwaves.

• The Voice of Independent Myanmar: A new shortwave broadcast providing news to Myanmar — The SWLing Post — A weekly independent news broadcast to Myanmar, launched as a joint effort between Mizzima and Reporters Without Borders.

• Alan Roe’s A-26 Season Guide to Music on Shortwave (version 4.0) — The SWLing Post — A free, downloadable PDF guide to music programming across the shortwave dial, plus companion single-page schedule grids for major broadcasters.

• Radio Waves: Georgia LPFM Wants More Power, Radio Bulgaria QSL #8, Preserving Radio Mogadishu, Shortwave HQ Updates, and Joining the CIDX — The SWLing Post — This week’s grab-bag of reader-submitted radio news, spanning LPFM power requests to archival efforts for Radio Mogadishu.

• “Holocaust” 1978 TV Mini Series Underground Radios – Warsaw Ghetto — The SWLing Post — Screenshots of an underground receiver as depicted in the 1978 miniseries “Holocaust,” starring Meryl Streep and James Woods.

• The Very Last New Commercial AM Radio Station in the USA: Here’s What We Should Do Next — Off Grid Ham — A commentary piece on the twilight of commercial AM broadcasting and where the band goes from here.

• Sunshine and shortwave — The SWLing Post — This week’s Imaginary Stations schedule, including WHFM – Herman’s Radio and Record Room airing on WRMI.

DX, Contests, Satellites & Awards

• Happy 50th Anniversary to the Araucaria DX Group! — OnAllBands — A congratulatory nod to one of amateur radio’s most accomplished DXing and contesting organizations on its 50th year.

• DX Engineering Supports the September/October 2026 9T0MD DXpedition from the Democratic Republic of the Congo — OnAllBands — The Mediterraneo DX Club heads to Africa’s second-largest nation for a multi-operator DXpedition running Sept. 30–Oct. 11.

• Radio New Zealand Features the November DXpedition to Fakaofo — The SWLing Post — RNZ’s Dateline program covers an upcoming DXpedition to Fakaofo in the Tokelau atoll.

• Contesting 101: The Art of the Possible—Gaining Perspective — OnAllBands — Kirk Pickering K4RO continues his contesting series with a piece on setting realistic goals and perspective.

• ANS-221 AMSAT News Service Weekly Bulletins — AMSAT — This week’s bulletin covers registration for the 44th AMSAT Space Symposium, ongoing board elections, and a new ARISS associate director appointment.

• Perseid MS shower — Roger G3XBM’s (Mainly) Amateur Radio Blog — A reminder that the Perseid meteor shower peak is prime time for meteor-scatter VHF contacts, with longer-than-usual returns.

Podcasts, Community & Events

• Paul Taylor VK3HN Talks about Homebrew and SOTA — SolderSmoke Daily News — Charlie NJ7V of Red Summit RF interviews longtime SolderSmoke friend and Melbourne homebrewer Paul Taylor, VK3HN.

• A German Builder Makes a 2 Meter Receiver - Warts and All! — SolderSmoke Daily News — A refreshingly honest “blow by blow” homebrew video showing every failed attempt on the way to a working dead-bug-style 2m FM receiver.

• Chappy Happy Builds a 25 meter Direct Conversion Receiver using a PAL VFO — SolderSmoke Daily News — A repurposed CB PAL VFO becomes a direct-conversion SW broadcast receiver, with some discussion of the AM/DSB distortion inherent to the design.

• Will N5OLA (the HW-101 Guy) Interviewed by Eric 4Z1UG — SolderSmoke Daily News — A QSO Today podcast interview with Will N5OLA, known for his soap-and-water restoration approach to old Heathkit HW-101 rigs.

• Open Sauce 2026 in San Francisco — SolderSmoke Daily News — Early reports trickling in from Open Sauce, including sightings of WSPR circumnavigating balloons and homebrew CubeSats.

• Morse Code Skills Maintenance — With Varying Frequency – Amateur Radio Ponderings — Scheduling conflicts push K9ZW toward Long Island CW Club sessions in the interim before the next CWOps course opens.

• Zero Retries 0259 — Zero Retries — This issue covers OFDM-AB and a refactored IP400, new hardware and modulation aimed at making high-speed VHF/UHF mesh networking genuinely practical.

• Berryville Hamfest 2026: Wet but wonderful — News – Shenandoah Valley Amateur Radio Club — Record rainfall didn’t keep hundreds of visitors away from this year’s hamfest.

• Mods on the Air – GB64MOD Event — With Varying Frequency – Amateur Radio Ponderings — A special-event call active through all of August for fans of the Mod scene and modern hams alike.

• International Lighthouse Lightship Weekend! — MichiganOne DMR Tech Net — This year’s ILLW (Aug 15–16) will see the group operating as K8L from Michigan’s Eagle Harbor Lighthouse.

• Lighthouse Activation — Lincoln County Amateur Radio Club — The club activates the Yaquina Head Lighthouse for ILLW on Saturday, August 15, from 10am to 2pm.

Advocacy, Licensing & Growing the Hobby

• Tell Your Lawmakers to Back the Amateur Radio Preparedness Act — OnAllBands — The proposed federal bill would bar HOAs from enacting restrictive antenna rules; non-hams can now easily lend support too via a linked letter tool.

• Question pools should make teaching classes easier — KB6NU’s Ham Radio Blog — Dan KB6NU reflects on teaching a Tech class at DEFCON’s Ham Radio Village with 66 students and a freshly updated question pool.

• Ways Amateur Radio Fosters Independence in Young Hams — OnAllBands — Katie Campbell KE8LQR, licensed at age ten, on how the hobby helped a shy kid find confidence.

• Free On-line Technician Class Course starting Sept 3 — MichiganOne DMR Tech Net — A free seven-session Zoom Technician course, sponsored by the National Electronics Museum, kicks off September 3.

• Amateur Radio Has Never Been More Affordable — So Why Do Some Things Seem So Expensive? — Q R P e r — Thomas K4SWL makes the case that the hobby is more accessible than ever, even as certain gear prices climb.

• Why we had Radio Free Europe and how Ham Radio might fit in — With Varying Frequency – Amateur Radio Ponderings — A look at the winding-down of Radio Free Europe’s cross-border broadcasts and where amateur radio might step into that gap.

Software & Apps Roundup

• A Wave of Mac Ham Radio App Updates — Mac Ham Radio — Marcus, DL8MRE, pushed a coordinated round of releases this week: K4-Control for Elecraft (iOS 1.139), FT-Control for Yaesu (macOS 1.139), TS-Control for Kenwood (macOS 1.139), and SDR-Control for Icom (macOS 2.9.140), alongside SmartSDR for macOS 2.9.139. Also new: HamClock Launcher 4.28, KLog 2.5.3, QRV for iOS 1.26, and WSPR Watch for iOS 4.38.

12. QRT: End Transmission

Booking it

I finally finished editing the 17 chapters in my book on conservation district management and governance. The first draft of the content happened swiftly back in May. Then I invited some experts to review the draft chapters. Now that the review phase is over, I’ve been trying to make final edits. Editing of chapters 1 through 9 went smoothly. Then life got very busy and I set it aside for a week…then two weeks…then two months. This past weekend, I pulled it up and got through editing the remaining chapters, and then sent the manuscript to the publisher. I’m sure I will have another round (or two) of edits coming up, but the core content is complete and good.

“Writing a book” is far more complicated than I thought it would be. I thought writing would be the hardest part, but what I discovered is that when you care deeply about a topic and have solid life experience in it, the book almost writes itself. I spent months crafting a very detailed outline and that proved to be the turning point for the manuscript, allowing me to get started and stay on track. So what was difficult? All the other steps that come with it, like finding a publisher, selecting graphics, choosing a format, hiring a service to convert it for e-book publication, and more. As I travel this road, I’m learning a lot.

Along the way, I realized that a good purpose-built tool for managers to keep regular short notes on employee performance just wasn’t available. A diary-like approach can be very helpful for capturing such notes, and reviewing that history is invaluable when it comes time for performance reviews and implementing other employment-related actions. But finding nothing like that, I made one. It’s simple and rather austere, but it does the job. With a few Python commands, you can turn it into an EXE file to run on Windows or an APP file for macOS. Find it on GitHub.

I could have made a template for something like this in Notion, but then if someone used the template, their data wouldn’t be held locally. I prefer to be in 100% control of employee information at all times.

Coding

I also had some WordPress coding fun, creating a plugin that converts a text-based schedule of meetings to an online display. Some of the text descriptions are rather complicated, e.g.:

The [fill in the blank] Board meetings are on the second Wednesday of October thru May. Meetings in September, October, March, April, and May are at 7 p.m. Meetings in November, December, January, and February are at 6:00 p.m. Meetings are in the US Post Office Building Conference Room.

I built a parser to extract the key pieces and convert the data into a CSV file, then rendered the CSV in a monthly calendar format, with a list-based schedule below the calendar. When meeting dates or locations change, I simply download the CSV, update it, and upload it back to the server. I also added the ability to temporarily mark a meeting “canceled” without going through the whole CSV download-and-upload sequence.

All that is built into a custom WordPress plugin that produces a shortcode for use on any page on the website. It’s working great.

And then, since I was on a roll writing plugins, I wrote one to convert my 518-row spreadsheet of high school classmates into a database maintained on the class website. It has two roles: data admins and data reviewers/approvers. I included a real change log that allows changes to be rolled back. It renders output with shortcodes to display a full class list, our missing classmates, and classmates who have walked on before us. Fun little project.

That should do it for me for a week or two with WordPress plugins!

Home

I’m not really a big fan of tomatoes, but I make an exception for home grown tomatoes harvested on a sunny day at the peak of ripeness. Since I’m the only one who eats them, I have one plant growing in a pot on the deck. Unfortunately, a chipmunk (we named it Chippie) has decided it likes my tomatoes, and it is much faster to harvest them than I am! To try to protect them, I’ve covered the plant — ripening tomatoes and all — with a net. I left the net loose on the bottom the first day and the chipmunk got in and decimated a few almost-ripe tomatoes. The net is now tied tight, and I’m hoping it keeps Chippie out so I’ll get to enjoy the fruits of my own labor soon!

And speaking of home, my childhood home may, or may not, have been affected by the wildfires that have destroyed parts of Spokane, Washington. I wish I knew the status of the old neighborhood as I have many great memories of growing up there. I’m sure I’ll try to make a road trip this fall just to reassure myself that all is well with the old house in northwest Spokane.

Wildfire has been an active force on Pacific Northwest landscapes, particularly east of the north-south Cascade Mountain range:

Source: Washington Large Fires 1973-2025

EtherHam website down (but back up late Thursday)

Thursday morning dawned with a different kind of tech problem: a message from the EtherHam web hosting company!

We’re currently responding to an emergency caused by a power outage at our Phoenix datacenter…undergoing emergency maintenance…experiencing network issues. Websites may be slow, unavailable, or return 503 errors. Hosting panel access may also be affected.

Starting my day with a web outage is always a bit unsettling. At least it wasn’t something I caused (and yes, that has happened before, more than once).

As Thursday draws to a close, resolution is in sight, but it still hasn’t happened. By Friday morning, the EtherHam.com website should be is back online.

73, and remember to touch a radio every day!

Here’s the headline: New Debian 13 “Trixie” Kernel Security Update Fixes 68 Vulnerabilities. The takeaway: If you’re running AllStarLink (ASL) on Debian 13, it’s time to update.

1. QRV: Are You Ready?

Welcome to Random Wire issue 194. Sometime in the past week, subscriber numbers hit 2,300…and kept climbing. This was a surprise because a few dozen subscribers ended their subscriptions last week, too.

This week, I got my MeshCore repeater functioning. The problem was a simple on-off switch I failed to see when I put the repeater into service the first time.

I also got a T-Echo (not the newer Plus version) configured as a LoRa APRS Tracker. It is communicating with my LoRa APRS igate/digipeater in the garage.

2. New on EtherHam

• Building a MeshCore Node — Part 2: The Repeater That Should Have Been Easy — Part 1 ended with a MeshCore repeater configured in ten minutes and beaconing right on schedule — a clean win, or so it seemed. Part 2 is the two weeks that followed. I encountered a debugging tool that was quietly resetting the very device I was troubleshooting, my antenna’s blind spot, a paywalled feature with a free workaround that didn’t actually work, and a repeater that went dark for five days over something hiding in plain sight the whole time. By the end, the hardware and firmware check out clean. What doesn’t check out, it turns out, is the ten miles of Pacific Northwest terrain standing between me and my nearest MeshCore neighbor.

• LoRa APRS: Part 2 — LoRa APRS Tracker with a T-Echo — A brand-new LilyGo T-Echo goes dark after a routine firmware flash — no display update, a red LED blinking like an alarm, and every obvious fix leading nowhere. What follows is a genuine debugging rabbit hole: a Windows error that’s secretly good news, a bootloader chase that turns out to be a red herring, an independent firmware swap that finally proves the hardware was fine all along, and a BLE pairing quirk that ends up eating more time than everything else combined. If you’ve ever stared at a “bricked” board and had to figure out which symptoms were real and which were noise, this is that story, from first red flag to a live beacon on aprs.fi.

• Weekly Report: August 6, 2026 — Catch up on band conditions, digital radio news, and the Groups.io digest.

3. My Talk2Me Radio is Working Well

My little Talk2Me PoC (push-to-talk over cellular) radio is working quite nicely. Last Saturday, I had a long drive to a high school class reunion. Unfortunately, that drive coincided with Saturday’s weekly M17 net. The M17 net is always interesting and I learn a lot every time I tune in.

To the rescue: my Talk2Me radio. I already had it set to listen to America’s Kansas City Wide network using Hamlink PoC (programmed into the radio by the vendor). So while driving at 60 MPH toward Tacoma, Washington, I turned it on, turned up the volume a couple of notches, and slipped it into the chest pocket of my shirt. I listened to the complete net during the drive and even checked in from the pickup truck.

I usually pick up the M17 net at home over my hotspot, or with BlueDV on my laptop, or with my M17 radio and an M17 hotspot. Before the Talk2Me radio, I could not get KC Wide over RF while I’m driving in the Seattle-Tacoma area. Now I can listen in and participate, thanks to my Talk2Me STANDARD PLUS radio.

Honestly, I’m quite impressed. Because of this fabulous little radio, I was able to enjoy one of my favorite nets while I traveled to my reunion. The radio? It. Just. Worked. Isn’t that what we really want? For our devices to just work? This one does.

4. My MeshCore Repeater Made the Map

I finally got my MeshCore repeater working. I don’t know why I so often get a product without any instructions, but in this case, there was supposed to be a card inside the box…and there wasn’t. So I experimented for days, trying different things. Finally, I put my magnifying visor on and took a careful look at the boards inside, only to discover an on-off switch! It was a small little slider, hiding from my unmagnified view.

After sliding it to the on position and charging the 18650 battery, I put the repeater outside on top of the gutter. (By this time, I had been up and down the ladder at least a dozen times to place/retrieve the repeater on the roof. Testing on the gutter was a lot easier and safer than climbing up on the roof over and over.) And it worked. It beaconed on startup, but more importantly, it beaconed regularly after that.

About a day later, it showed up on the MeshCore map:

I’m still getting to know how this all works. I can’t reach other stations directly with my handheld device (T-Deck Plus), which is why I put up a repeater. Currently, my local MeshCore chain has three pieces: a repeater, a relay, and an app. The PeakMesh repeater is on the roof. A LilyGo T-Echo Plus at 910MHz with Bluetooth serves as a relay between the repeater and my phone. The MeshCore app is on my Android phone.

I also have a LilyGo T-Deck Plus at 910MHz with internal antenna that is a portable, handheld device. It isn’t a necessary part of my MeshCore chain.

If you happen to be using a MeshCore device, try adding the #etherham channel and pushing a message my way. That would be fun to try.

5. My LoRa APRS iGate/Digi Works

It works! The LoRa APRS igate/digipeater I installed in the garage actually works. The range? Minuscule, but more on that in a moment.

I bought a second LilyGo T-Deck Plus on 433MHz and configured it as a LoRa APRS tracker. Then I went for a drive. My igate/digi (KJ7T-2) picked up the mobile tracker (KJ7T-3) about 1/8 mile from the digi. It works.

But it only works for a short distance. The small external antenna on the T-Deck Plus is insufficient for much range when the igate/digi is located in a basin…and that is what a lake is: a topographic low filled with water. I’m surrounded by hills so that tiny antenna doesn’t stand much of a chance of getting a signal out.

You can actually see the signal strength (RSSI = Received Signal Strength Indicator) drop off as I drove away from my igate/digi (KJ7T-2) yesterday morning.

SNR (signal-to-noise ratio, in dB) is arguably the more meaningful number here. It describes how far above the noise floor the signal actually was, which is what determines whether the receiver can hear it well enough to decode it at all.

Looking at the photo, the oldest is at the bottom of the list of three exchanges. The signal went from -61 RSSI/SNR 7 (strong, near the start of the drive) down to -107/-5 and then to -117/-14 as I drove farther away, right before it dropped out entirely around 1/3 mile distant.

Here’s something worth noting: successfully decoding at -14 dB SNR is a real demonstration of LoRa’s advantage over conventional radio. FM APRS generally needs a positive SNR to decode anything — LoRa’s chirp spread-spectrum modulation (especially at SF12, which you’re running) has enough processing gain to pull a signal out well below the noise floor. That last successful frame wasn’t a fluke; it’s LoRa working as designed, right up until the combination of distance and terrain finally buried it.

I’m considering putting up the dual-band dipole antenna I have on order (note: ordered more than a month ago and my emails to the company are bouncing!) on a pole outside the garage. Maybe I can try a diplexer and run the LightAPRS Gateway on the VHF dipole and the LoRa APRS igate/digipeater on the UHF dipole. Two devices, one feedline, a diplexer, and the dual-band antenna. Just another 10-15 feet in clear air and I’ll bet I can reach at least a mile away on LoRa.

As noted in the New on EtherHam section above, I configured the T-Echo (not the Plus) as a LoRa APRS tracker. The advantage of the T-Echo is long battery life. It’s a small device so I can easily tuck it out of the way inside the pickup truck cab.

6. AI: Trying DeepSeek

I use Claude. I use ChatGPT. At the suggestion of a friend, I’ve started using Gemini a bit more. And now I’m exploring DeepSeek, which I’m finding to be very fast…but also more shallow than those other engines. Whether it will stand up to Claude when it comes to coding, I don’t yet know, but I doubt it. I’ve added DeepSeek to my Open Notebook instance running on my Proxmox server.

One thing to be aware of with DeepSeek: it stores API data on servers in China and its terms permit training on your inputs by default. I don’t plan to use it for anything important, but if you handle sensitive information, you’ll want to bear this in mind if you choose to use DeepSeek.

Me? I still lean toward Claude for the things I do.

7. Short Stack from the Interwebs

Pulled from the aggregated feeds on EtherHam (etherham.com/feeds/), items from July 30–August 5. This Short Stack turned into a Long Stack!

SDR & Signal Hacking

• Scanner Command: Mapping Incidents from Live Radio Calls and ADS-B to Airband Voice with AI — RTL-SDR Blog — A follow-on to DeepSDR: another public-safety-scanner-plus-LLM incident mapper, this time tied to airband/ADS-B traffic.

• Turning a Local ADS-B Feed Into an Easy to Read Dashboard — N3BKV’s Ham Radio Hacks — Building a clean dashboard on top of a SkyAware feed to see what’s flying overhead.

• Large-scale LoRaWAN deployments become easier through QR codes and relays — CNX Software — QR-code provisioning and relay support aimed at simplifying big LoRaWAN rollouts.

Digital Modes & Data

• bkjbbs: A Node.js Packet Radio BBS Library for Direwolf — Hamradio.my — A modern Node.js library for running a packet BBS on Direwolf, with full AX.25/KISS support and TypeScript types.

• Retevis C62 OpenRTX port and the cskburn update — M17 Project News — Progress notes on the OpenRTX port for the Retevis C62, alongside LinHT work.

Gear, Builds & Reviews

• Wanneton UV5F Ham Radio Handheld Dual Band Two-Way Radio Review — Amateur Radio Today — A hands-on look at a budget dual-band HT aimed at entry-level and emergency-prep users.

• The Best Inexpensive HF Antennas for Amateur Radio — Amateur Radio Today — Pushing back on the idea that HF requires an expensive antenna.

• Chameleon LEFS Feather Antenna QRP with the Elecraft KX3 — J-Pole Antenna — QRP field pairing of the Chameleon LEFS Feather with a KX3.

• Build Your Own DIY Compact FM Transmitter — Hackster.io — A step-by-step 88–108 MHz FM transmitter build.

• A Homebrew Workbench from Norway — Please Comment: What would you have done differently? — Solder Smoke — A reader’s shack workbench, with Bill Meara asking for critique.

• But did he really create this device? What do you think? — Solder Smoke — A skeptical look at a dubious “invention” video making the rounds.

POTA, SOTA & Field Ops

• A Wet POTA Experiment: Hunting, Calling CQ, and Changing Modes — QRPer — Mark (KB2PIZ) on how long to stick with a band/mode before switching things up during an activation.

• CE7ET: Mini POTA DXpedition to Rapa Nui (Easter Island) CL-0105 / 3G0YT — QRPer — A POTA activation report from one of the more remote parks you’ll see on the air.

• DF7CW: Field Testing the IC-705 and SOTAmāt in Märkische Schweiz (DE-0083) Before a Swedish Trail Adventure — QRPer — A newly-licensed German ham field-testing gear ahead of a bigger trip.

• The best-laid plans do work out, after you pivot a few times — QRPer — Vince (VE6LK) on activation plans that only came together after repeated pivots.

• More POTA notes, 7/30/26 — KB6NU — Dan’s real-world notes on running down the limits of a 9 Ahr BioEnno battery across activations.

• 9M LLOTA: Malaysia Joins Lakes and Lagoons On The Air — Hamradio.my — Malaysia’s entry into the Lakes and Lagoons On The Air program, with a growing reference list.

Shortwave & Listening

• A New Novel from DXer Ralph W. Perry: Pacific Dream — The SWLing Post — A longtime DXer’s new novel gets a nod from the SWLing community.

• Illustrated Radio Listening Report reaching Nepal — The SWLing Post — Cartoonist Carlos Latuff’s illustrated QSL-style reports have made it further than he expected.

• Radio Prague: “Microphones against tanks” — The SWLing Post — The latest in Radio Prague International’s history series on Czech broadcasting.

• BBC Radio 5 Live Closing More AM Transmitters — The SWLing Post — The BBC continues trimming its mediumwave footprint.

• Pirate Radio on the HF Bands: The Hidden World of Shortwave Broadcasting — Amateur Radio Today — A survey of the pirate shortwave scene for hams who make contacts but rarely just listen.

Podcasts & Community

• Ham College 142 — Amateur Radio Weekly — General exam prep covering transmitter power rules and 60-meter operation.

• LHS Episode #624: National Jamboree 2026 — Amateur Radio Weekly — Linux in the Ham Shack’s coverage of this year’s National Jamboree.

• Amateur Radio Weekly – Issue 432 — Amateur Radio Weekly — This week’s roundup, leading with a Kentucky family suing after a school resource officer seized a student’s radios without a warrant.

• Legendary DXer Bob Locher, W9KNI, Presents Tales from a Serial Sniper Part 2, “Looking South” — On All Bands — Part two of Bob Locher’s DXing memoirs.

• Talking to Silent Keys — With Varying Frequency — A reflective piece on how the community keeps engaging with the memory of hams who’ve become Silent Keys.

• One lump or two (or three)? — KB6NU — Dan’s take on the perennial argument over how many license classes ham radio should have.

Linux, Homelab & Self-Hosting

• Proxmox releases full support for the Arm64 architecture, with a few key caveats — XDA Developers — Arm64 support lands, but access is request-only for now.

• Proxmox ships with a broken repo by design, and here’s the 30-second fix every home user needs — XDA Developers — The rite-of-passage repo fix for every fresh Proxmox install.

• NightRun UEFI application boots a local LLM on Raspberry Pi 5 and x86 PCs without an OS — CNX Software — Running an LLM straight from firmware, no OS required — relevant if you’re squeezing extra life out of Pi-based nodes.

• 3 Raspberry Pi Projects I Use Every Day — Raspberry Tips — Practical, daily-driver Pi projects rather than one-off builds.

• Jellyfin vs Plex on Raspberry Pi: Which Is Best? — Raspberry Tips — A head-to-head for anyone running a Pi as a media server.

• A Mac Mini server is running headless in my closet — it manages my photo library and handles my backups — Tom’s Hardware — A refurbished Mac Mini pulling backup and photo-library duty.

• AppFlowy finally feels like real Notion, and self-hosting it fixed my biggest complaint — XDA Developers — A self-hosted Notion alternative that’s matured enough to switch to.

• Issue 522 – Minimus Releases Hardened Images For Free – What Does It Do Differently? — Awesome Self Hosted newsletter — Free hardened container images, and what sets them apart.

• My router was doing 5 things that I never asked it to, and I wish I had changed them earlier — XDA Developers — Default router settings worth turning off.

• This E-Ink Home Assistant display cut my phone notifications in half — How-To Geek — An always-on e-ink dashboard for Home Assistant that pulls attention off the phone.

• I turned an old Android phone into a Home Assistant voice satellite—no speaker needed — How-To Geek — A cheap way to repurpose old hardware, in the same spirit as hotspot/node builds.

Also Noted (Tech)

• AI enthusiast unlocks and mods BIOS with Claude Code — AI defeats RSA-2048 signature checks and unlocks 55 hidden settings — Tom’s Hardware — A Redditor used Claude Code to unlock a laptop’s hidden BIOS settings.

8. QRT: End Transmission

Radio history

I do enjoy reading radio history, and The Discovery of Radio Waves was an article I found very interesting.

Just proves to me once again that we all stand on the good work of those who came before us.

Claude and CSS debugging

As I was debugging a CSS load problem (the problem being a specific file was not loading) on a website, I started to use a tried-and-true method: turn off plugins one by one, test, re-enable, move to the next plugin. Well, this site has 67 plugins and that takes an awfully long time.

And then I thought: I wonder if Claude can help me with this? Using the Sonnet model, Claude had trouble understanding what I wanted and kept trying to hand it back to me. So I switched to the Opus 5 model and was delighted when — after I gave it permission — it proceeded to walk through all 67 plugins and test them, without me having to intervene.

Claude found one plugin that no longer parsed CSS after the plugin was recently updated. We rolled that back to a previous version, resolving the problem. That saved me hours of digging.

LoRa radio

I’m enjoying learning about this technology. New? Not…but it feels new to me, simply because while I’ve dabbled my toes in the LoRa waters, I haven’t taken a dive like in the past several weeks. It’s interesting stuff, especially how it is able to send and receive data way below the noise floor.

73, and remember to touch a radio every day!

The Random Wire newsletter is the journal of what I’m doing during the week, and serves as a companion to EtherHam.com where more detailed, technical content gets published. I hope you enjoy both the newsletter and the website.

I enjoy hearing from readers and hope you’ll share what is on your workbench!

KJ7T Tom

1. QRV: Are You Ready?

Coding

Not a lot of radio play this week, as I got caught up in “the zone” while coding for my day job. Two days in a row, I started in on a project and when I looked up, the clock said ten hours had elapsed. It’s been a while since I entered a flow state like this. I kind of miss it. Time flies and the work can be very satisfying. (If you code, you know.)

What did I do? First, I rebuilt an issues-and-actions tracker for work that covers a five-year rolling time period. Then I converted a +800-person directory from a PDF document to an online database embedded in a WordPress site, to help my work team keep our member information updated. This was honestly much more complicated than it sounds.

For the online directory, I also added some protection against scrapers (bots that grab everyone’s email from a website). Emails in the directory are never displayed in the public HTML page, instead being protected by signed tokens and a rate limit with a lockout if exceeded. Clicking the email link opens a “reveal page” that shows the email address as visible text (with an app-launch attempt on top). The reveal links are rate-limited per visitor, so a bot trying to harvest hundreds of addresses in bulk gets throttled and locked out — a real visitor clicking a few links will likely never notice.

And then one of my work teammates cranked up our annual conference web pages and asked for help, resulting in another day two days of revisions and coding. Along the way, I found several plugins that were weighing down every page. Click click, poof — they are gone, and what they were doing has been replaced with some custom fields, Cascading Style Sheet magic, and a few custom-built plugins. I saved a lot of memory overhead and the pages load faster. Yes, satisfying.

Ultimately, we ended up with a group of custom plugins, all nested together under “Conference” in our Dashboard menu. This will help us manage most of the content for our annual conference and business meeting. It will also greatly reduce the repetitive entries we would normally make in the actual HTML pages. That will mean fewer errors and less time spent figuring out all the little gotchas that can be so hard to find in hundreds and hundreds of lines of content.

Radio

I was able to hang out on the M17 net last Saturday, using my Talk2Me PoC radio and, out of curiosity, simultaneously listening with BlueDV on my laptop. The M17 net is always educational, and it’s fun to hear about the continued evolution of M17 as a protocol, in hardware, and in apps like MSeven.

If you click this Talk2Me PoC radio link, you’ll discover a new feature I’m just starting to build out at EtherHam.com: a compendium of the gear I’ve used, reviewed, or recommended. I’m just getting a start on this so content is light. Translation: more to do!

I also finished up my series on push-to-talk over cellular radios and started a new series on MeshCore. Still in process are some articles on DMR.

APRS continues to be on my mind. I run it in my pickup truck on my Yaesu FTM-300D mobile radio…and on my phone with APRSdroid. But I also have the LightAPRS Gateway (a VHF 1-watt fill-in digi and igate) in the garage, and now a LoRa APRS igate/digi (UHF) running about 100 milliwatts. I’m waiting on another T-Deck Plus built around 433MHz so I can play with APRS messaging over the LoRa APRS station.

In summary, it was a week of coding with some radio and writing, too. As Julie Andrews sang:

♫ These are a few of my favorite things ♫

2. New on EtherHam

• Push-to-Talk Over Cellular: The Buyer’s Checklist — Part 4 of 4. Part 1 was the lot walk. Part 2 was my own radio purchase, start to finish. Part 3 was the radio itself, on the bench and on the road. Part 4 is the short version — everything worth checking, without the weeks it took me to learn it. Three articles, several weeks, and my own money all contributed to this list. If you only read one piece in this series, spend your time with this one.

• Building a MeshCore Node — Part 1: Why, What, and How — CascadiaMesh, the MeshCore community covering the Pacific Northwest, promises you can get on the mesh in three easy steps: pick a device, flash it, pair it to your phone. I wanted to test that claim the honest way — buy the hardware, do exactly what the guide says, and see where it actually breaks. Spoiler for Part 1: it worked fine. Flashing a LilyGo T-Echo Plus turned up one genuine hardware-vs-host-computer mystery (solved), and getting a companion radio talking to a repeater took about as long as promised. Part 2, where I will cover building and configuring a MeshCore repeater, is where things promise to get more interesting.

• Expanding Technician Privileges: The Fix Needs a Push — There’s a real, already-written fix for one of Technician licensees’ most common complaints — and it’s been sitting in an FCC docket since 2018. The petition would open modern digital modes like FT8 to Technicians on 75, 40, and 15 meters, plus some phone privileges, with almost no opposition on record. Seven years later, it’s still stuck — not from pushback, but from plain bureaucratic inertia. I dig into why it hasn’t moved, what it still wouldn’t fix (including a telling admission buried in ARRL’s own petition language), and why right now — with the FCC’s current deregulatory docket wide open — is the moment to actually push it through.

• Weekly Report: July 30, 2026 — The usual: Band Conditions, Digital Radio News, Groups.io Digest.

A New “EtherHam Gear” Page

I added a gear page on the EtherHam.com website. As my content catalog grows, I am finding it harder to come back later and find the equipment I’ve reviewed or recommended. Going forward, I’ll populate the gear page with those devices, and then link to the gear listing in my articles.

This methodology should make it easier for visitors to find the items I talk about. It will also make it easier for me to maintain links to items, because those links do change at vendor sites.

The Gear page is produced by a custom WordPress plugin, which was a lot of fun to build.

Frankly, there are already plugins that will add short, custom links to an item, but as I researched them, I found them bloated and complicated. Some require a connection to a third-party service. I also don’t like using anything that says it features “link cloaking.” Even though this is actually a common practice, it just sounds and feels wrong. My plugin is trim, does only what I want, and lives entirely on EtherHam.com. If you run a WordPress site and want the code, drop me a line. It is one PHP file, 419 lines long.

3. On The Bench

Last week, I included this item in the Short Stack:

APRSdroid 9M2PJU Mod: The Enhanced APRS Companion for Android, Built by Hams, for Hams — Hamradio.my — A ham-built mod to APRSdroid. Given the LoRa APRS iGate work on EtherHam right now, this is a natural companion piece.

Well, I installed it. If you go down this road, there are a few wrinkles to be aware of. First, you must uninstall APRSdroid if that is already on your Android device. Second, the app requires granting several permissions, but fortunately, granting permissions is as easy as pushing one button, then tapping “allow” on the ensuing popups.

Enter your call sign and your APRS passcode (just search online for “APRS passcode”) and you’re ready to go.

I’ve been using it in the pickup truck as KJ7T-5 and it is working fine.

I installed this version because it offers the ability to connect with LoRa devices if they have Bluetooth low-energy (BLE) and use a KISS TNC protocol. This means that with the right LoRa tracker, I’ll be able to connect to the other APRS network most amateurs aren’t aware of that runs on LoRa radio at 433MHz. There is a clear, step-by-step guide for this at https://aprsdroid.hamradio.my/#lora.

My 433MHz LoRa device is on its way to me from across the Pacific. I’m just very curious how this will work. One surprise for me was learning that LoRa APRS stations that are igated hit APRS-IS, so they show up on sites like aprs.fi. (Click to see my LoRa APRS station on aprs.fi.)

4. M17 Net Notes

From Saturday’s M17 net on America’s Kansas City Wide network.

• M17 is a digital voice and data protocol with hardware and software solutions.

• The LinHT handheld transceiver continues to move forward. Uses GNU Radio software.

• Other software that runs M17 includes DroidStar, the MSeven app, and QSO One.

The M17-KCW reflector carries primary KC Wide network traffic on module A (M17-KCW A). The B module on M17-KCW (also called “the B side”) is for M17 only; it is not connected to the A side. In the screenshot below, you can see some stations on module A and on B in the right-hand side of the reflector dashboard.

There is also a great service offered through KC Wide: seeing your live audio level. Find this at https://level.kansascitywide.com/. The interface looks like this:

There was very interesting commentary about FreeDV on HF and 2-meter sideband. Exploring FreeDV is on my list of things to dig into.

The net closed with some conversation in the net chat about radiograms. Some of the helpful links that were shared in the chat are:

• https://nts2.arrl.org/radiogram-portal-quick-start/

• https://nts2.arrl.org/radiogram/

• https://apps.apple.com/us/app/nts-radio/id1204567739

5. Short Stack from the Interwebs

Pulled from the aggregated feeds on EtherHam (etherham.com/feeds/), items from July 28–30.

SDR

• Testing Airspy’s New WebSpy Web SDR Interface with an RTL-SDR — RTL-SDR Blog — A look at Airspy’s new browser-based SDR interface.

• Building a $50 BOM Software Defined Radio with a HT9201 20 MHz ADC and an FX2LP USB Controller Clone — RTL-SDR Blog — Budget homebrew SDR build, bill-of-materials and all.

• Radio Silence: A Native iOS App for Listening to Public KiwiSDRs — RTL-SDR Blog — A dedicated iOS client for the public KiwiSDR network.

• TunerScope: A Browser App to Help Optimize HDTV Antenna Positioning with an RTL-SDR — RTL-SDR Blog — Clever repurposing of an RTL-SDR as an antenna-aiming tool.

• DeepSDR Updates: Live Public Safety Incident Map with an RTL-SDR, Whisper and an LLM — RTL-SDR Blog — RTL-SDR plus Whisper transcription plus an LLM, mapped live. The standout item this week.

Digital Modes & RTTY

• H-Mode: An Open HF Digital Mode That Turns Errors Into Ionospheric Measurements — Hamradio.my — A new open digital mode that uses decode errors themselves as ionospheric data.

• Someone Turned a Sony PSP Into an RTTY Encoder — Hamradio.my — Exactly what it sounds like, and a fun homebrew read.

• 5D Web Programmer: A Free, In-Browser Codeplug Editor for the Yaesu FT-5D — Hamradio.my — Open-source, browser-based codeplug editing — no vendor software required.

Shortwave & Listening

• RTI French Service Announces August 2026 Shortwave Broadcasts to Europe and North Africa — The SWLing Post — Fresh broadcast schedule for shortwave listeners.

• Japan Times: The Uncertain Future of Shiokaze’s Shortwave Broadcasts — The SWLing Post — A look at the funding and future of the Shiokaze shortwave service.

• Carlos’ Illustrated Radio Listening Report and Recording of Multiple Stations (July 21–28, 2026) — The SWLing Post — A week’s worth of DX catches with recordings.

Podcasts & Community

• HRWB 268 – Diversity Reception with Dave AB7E — Ham Radio Workbench — Podcast episode on diversity reception techniques.

• Ham Radio and the Possibility of Internet Over Ham Radio — Amateur Radio Today — A think piece on running internet traffic over ham bands.

• Two Big Store Updates: Ship with DHL or UPS, and Taking PayPal Payments — TAPR — Practical update from the Tucson Amateur Packet Radio store.

Also Noted (Tech)

• Amazon Accidentally Spent $1.8 Million Using Claude for Menial Coding Task, Went 860% Over Budget — Tom’s Hardware — A cautionary tale on agentic AI cost management.

• These 3 Raspberry Pi Projects Solve Real Problems — and One Brings Back Cassette Nostalgia — How-To Geek — Relevant to anyone running Pi-based nodes or hotspots.

• PSA: Your Watch Band May Be Messing With Your Laptop — Tom’s Hardware — Magnetic clasps triggering laptop lid sensors — a weird, easy-to-miss gotcha.

6. QRT: End Transmission

Plumbing, part 3. Get a dehumidifier, the plumber said, so I did. And I went low cost:

Dehumidifiers for Home, 1000 Sq.Ft Dehumidifier with 95oz Water Tank, Quiet Dehumidifier for Basement Bathroom Bedroom with 7-Color Ambient Light & Auto Shut Off, Sliver (this is an affiliate link)

The device has been pulling about a cup-and-a-half of water out of the air daily. It’s not silent — the fan noise is like white noise in the background, not really unpleasant at all. It remains on during my Zoom calls without disturbing me or the people on the call. The good-sized water tank and the automatic shutoff were key factors in my choice.

And the new moisture meter did arrive:

Klein Tools ET140 Pinless Moisture Meter for Non-Destructive Moisture Detection in Drywall, Wood, and Masonry; Detects up to 3/4-Inch Below Surface (this is an affiliate link)

Since I’m trying to sense moisture underneath the old linoleum flooring, I’m using the drywall setting. I don’t get exact/true measurements this way, but I do get relative measurements by comparing a known dry area against a suspected damp area. A week ago, the areas affected by the leak were about 10% higher moisture than the dry areas. As of today, measurements in the damp spots show about 6% more moisture. Meanwhile, the dehumidifier continues to pull moisture out. I’m guessing I’ll be ready to try the heat gun in about a week. I’m hoping this will let me flatten the tiles, and if I’m really lucky, the existing mastic will re-adhere to those lifted edges.

And with that, it’s time to say 73 and send my best wishes to you for a great radio-focused week ahead!

Remember to touch a radio every day!

Leave a comment

I found a message from N0LSR in my junk mail folder yesterday, and it was important. It’s about the failing Clear Sky Institute server. If you are an Inovato or N0LSR HamClock customer, “all users must switch to the new OHB (Open HamClock Backend) to ensure continued updates and reliable operation.” Find more information on the N0LSR home page.

There’s a quick way to tell if you are on the correct server: “If you are currently on any version below 4.26 and do not get the upgrade offered to 4.27 then you are on the wrong backend server.”

Once upgraded, the version will say 4.27 and you’ll see an envelope just below the version number. Click on the envelope icon for a status message.

1. QRV: Are You Ready?

It may seem as if there is little radio content in this issue, but that’s because the bulk of my radio work landed on EtherHam.com this week. Specifically, I took several days to develop a detailed hands-on look at my new Talk2Me push-to-talk over cellular radio. The pointer for that is below in the New on EtherHam section. If you’re interested in PoC radios, you’ll find this worth your time.

After looking at how these radios and services are marketed, how the ordering and fulfillment process actually happens from the end-user point of view, and how the radio and service function, I’ve concluded: this is not a mature market. Several companies are vying for your dollars. The actual hardware and services offered are in a state of continuous change, so I think it is very difficult for a vendor to keep up with onboarding information, documentation, and even fulfillment steps. This shouldn’t dissuade you from entering this space if you are interested in PoC radio, but do be prepared for a rockier process, from start to finish, than you may be used to experiencing with mainstream amateur radio products. Why would you do this? Because PoC radios can offer an unprecedented level of connectivity and convenience.

2. New on EtherHam

• Push-to-Talk Over Cellular: Hands-On with a Modern PoC Radio — Part 3 in a series. My radio arrived with no instructions. I learned how to use it by pushing every button and chasing every menu. Thirty minutes to enter a WiFi password. An SOS mode hiding behind the flashlight button. A Bluetooth pairing that is not obvious how to undo. And when I finally found the official manual online, it described a radio with no WiFi and no Bluetooth — not the radio I bought. The device itself works, and it puts Kansas City Wide in my pocket, at home on my network and while I’m on the road. Should you buy it? Overall, I’m happy with the device and the service.

• Building a LoRa APRS iGate/Digipeater — Part 1: Why, What, and How — I already run conventional VHF APRS from the lake house, so when I heard about LoRa APRS, I wanted to see what it would take to get a station on the air. (LoRa APRS is a newer parallel network built on chirp spread-spectrum instead of classic AFSK packet.) When I checked the LoRa APRS live map, I found exactly one LoRa APRS station in the whole area, and it hadn’t heard anything over RF in over two months. Here’s how I turned a LilyGo T-Deck Plus into KJ7T-2 — a live 433.775 MHz iGate and digipeater — including recovering from installing the wrong firmware and the hidden BOOT button.

• Weekly Report: July 23, 2026 — Band Conditions, Digital Radio News, Groups.io Digest.

3. New on the Bench

MeshCore Repeater — I bought a MeshCore repeater from an Etsy seller. It is solar-powered with a single 18650 battery inside to keep it running in the dark times. I am halfway between two other MeshCore devices, each about 15 miles away. You can explore the worldwide MeshCore map at https://map.meshcore.io. In the screenshot below, I’ve placed a Random Wire sticker on my location. You can see I have stations to the southwest and to the northeast.

I’ve magnetically attached the repeater to the steel chimney cap.

Even though my device is up above the roofline, I’m on a lake, and that means I occupy a topographic low. I do have a 915MHz mag-mount antenna coming that I hope will extend the reach of this device, but I’m not optimistic. Still, it’s an interesting device and system to explore.

T-Deck Plus — This LilyGo device will probably arrive the day after this Random Wire issue publishes. This is a 915MHz device that I plan to flash with MeshCore firmware so I can talk to my repeater and perhaps get that repeater onto the MeshCore map. If MeshCore doesn’t work out, I can flash it with Meshtastic. I might also try a T-Echo Tracker on 915MHz, too.

T-Echo Tracker — This is a second T-Echo, but this one is configured for 433MHz. It should connect to my LoRa APRS igate/digipeater running as KJ7T-2. I want to use the T-Echo to see how far KJ7T-2 will reach.

APRS testing — I’ve been monitoring APRS on APRSdroid, aprs.fi, and my mobile radio, wanting to see if those were picking up my KJ7T LightAPRS Gateway device…and they are. What surprised me was that my LoRa APRS box, running as KJ7T-2, is also picked up by aprs.fi.

I also see that my internal battery voltage on the LightAPRS Gateway device has come up from the 4.5V range to nearly 4.7V. That’s because I changed the 1A wall charger to a 2A device.

4. Website: EtherHam CSS Cleanup with Claude

This may only be of interest to other webmasters. If you don’t manage a website, read this as: Claude can help you handle some mundane tasks…and feel free to skip it if the idea of cleaning up CSS code makes your eyes cross!

When I was first setting up EtherHam.com, I chose to use WordPress as the content management system. I’ve been working with WordPress for years. While it is a bit bloated for my needs, I know it inside and out. Just like using a favorite radio, there is a certain comfort in that.

I worked my way through several block themes, each requiring some Cascading Style Sheet (CSS) customization. Many fragments got orphaned along the way — leftover CSS doing nothing but cluttering the file.

I'd read that Claude could help manage a WordPress site, but hadn't trusted it enough to try. This week, I decided to give it a try. First, I backed up the entire site, including making a copy of the CSS file I was about to change. Then I asked Claude for help.

I installed the Claude in Chrome extension when prompted, and after that, Claude had direct access to what I had open in the browser. This process worked well. We cleaned up the CSS settings, and along the way, I identified a few plugins that I had tried but never used, so those got removed.

Since I was on a roll, I asked Claude for help making formatting consistent between the home page, sub pages, and posts. In just a few minutes, we aligned formatting in these different views.

I posted the exact CSS file Claude helped me clean up on EtherHam, if you’re interested. It is nicely organized and well commented.

If you’re curious, you can download a copy as a text file.

Bottom line: EtherHam.com looks fine and the styling is cleaned up and consistent throughout the site.

5. Vehicle Super Starter: Why I Didn’t Buy It

This isn’t amateur radio, but it could intersect with licensed operators if they run a mobile radio in their rig.

What is this about? I thought about buying a super capacitor for my truck. The sales messaging I’ve been seeing seemed compelling and I find the concept quite clever, so I gave it more than a cursory look.

Ancel sells a device called the Super Starter — a permanently installed super capacitor that wires into your battery terminals and sits under the hood, taking over most of the cranking load every time you start the engine. The pitch is straightforward: your battery stops absorbing the punishing current spike of a cold start, wear and tear drops, and the battery lasts longer. No cables, no remembering to charge a separate pack, no getting out of the truck. Connect it once, forget it exists, and let it quietly do its job for years.

I’ve had dying and weak vehicle batteries, so I really like the concept. I like anything that takes a known failure mode — batteries dying at the worst possible moment — and tries to engineer it away rather than just selling you a booster with a flashlight and jumper cables.

But a few things stopped me before I clicked buy. First, the fit-to-cost problem: the base model is rated for engines up to 3.0 liters, and my Ridgeline runs a 3.5L V6. The unit that actually matches my truck runs closer to $220 than the $150 headline price on the smaller model — a detail that’s easy to miss if you’re moving fast.

Second, the marketing language has a familiar look to it. If you’ve watched the push-to-talk-over-cellular space the way I have, you’ve seen this pattern before: a genuinely interesting piece of engineering wrapped in urgency — limited-time pricing, breathless “why didn’t this exist sooner” copy, glowing coverage that reads like it was written by someone with an affiliate link. None of that makes the underlying tech bad. But it’s usually a sign the vendor wants you to make the purchase decision before you’ve had time to ask the boring questions, like whether the battery-life claims hold up after a real winter under the hood. This product launched this year. There’s no multi-year data available yet, independent or otherwise.

However, there is a review published by Car and Driver that touches on the utility of the device for cold winter vehicle starts. It sounds solid, and it is a real-world, hands-on kind of review. If you’re interested in this tech, this is worth a read: This Clever Supercapacitor Accessory Is a Smart Fix for Cold Car Starts.

Third, and this is the part that’s specific to the Random Wire audience: if you’ve got a mobile rig hardwired into your vehicle’s electrical system, this device is doing something to your crank and start-up voltage profile that nobody’s characterized yet. It’s not a fuse-blowing concern in the classic sense — the Super Starter probably doesn’t add current through your radio’s own power leads, so an overcurrent trip on that circuit isn’t the likely failure mode. The more concerning question is voltage transients on the 12V bus itself. During the crank event, the capacitor is absorbing most of the starter’s draw and then handing off to the battery and alternator; right after start, it’s pulling current back from the alternator to refill itself. Either transition could produce a brief dip or overshoot on the bus that a normally-fed rig wouldn’t otherwise see — and mobile radios are already notoriously sensitive to exactly that kind of thing, which is why so many of us add extra transient suppression to a hardwired install in the first place. I haven’t found research measuring the 12V bus with and without one of these installed, from Ancel or anyone independent. Until someone runs that test, I wouldn’t want it anywhere near several hundred dollars of mobile radio gear.

Fourth, and the part that actually killed it for me: the thing only helps the vehicle it’s bolted to. I have kids with vehicles in various states of mechanical health, and I’m the guy who often gets the call when one of them won’t start. A device clamped to my own battery terminals is no use to them. This means I’d still need to carry a portable lithium booster in the truck regardless of whether I installed the Super Starter. And if I’m already carrying a booster that covers every situation the Super Starter covers plus the ones it doesn’t, the case for spending another $220 on a single-purpose, single-vehicle install gets thin fast.

So here’s where I landed: it’s a legitimately clever idea, and I like the concept. If you’ve got a vehicle that sits for long stretches, hauls a heavy accessory load, or otherwise chews through batteries, I understand the appeal. But for a daily-driven rig with a battery in decent shape, and a household where “helpful” means being able to jump anyone’s vehicle, not just your own, a $60 portable booster under the seat does more for less money — and doesn’t ask you to trust a new product category on faith. I’ll keep an eye on this space. If the independent, multi-season reviews start showing up and the numbers hold, I may revisit it. For now, my jumper cables and a charged lithium pack are in the truck.

6. Short Stack from the Interwebs

Pulled from the aggregated feeds on EtherHam (etherham.com/feeds/), items from July 20–23.

Antennas

• The Crown Antenna: A Wire Loop That Hugs the Roof and Works the World — Hamradio.my — A roof-hugging wire loop design for HF. Worth a look if you’re antenna-restricted.

• Part 2 of… Antenna solve one problem to only create another — Amateur Radio Weekly — the classic antenna-tinkering trap: fix one issue, discover a new one. Relatable.

Propagation & Science

• HamSCI Ray Tracing Working Group — HAMSCI.org — HamSCI’s group working on ray-tracing tools for ionospheric propagation modeling.

• The ARRL Solar Update — ARRL News — Latest solar/propagation conditions rundown.

Satellites

• UmKA-1 (RS40S) Satellite to Transmit SSTV, Audio Clips — Amateur Radio Daily — New satellite planning SSTV and audio transmissions — worth tracking if you’re into satellite work.

APRS & Digital

• APRSdroid 9M2PJU Mod: The Enhanced APRS Companion for Android, Built by Hams, for Hams — Hamradio.my — A ham-built mod to APRSdroid. Given the LoRa APRS iGate work on EtherHam right now, this is a natural companion piece.

DIY / Gadgets

• Flash a $2 Pi-hole From Your Browser: The 9M2PJU ESP32-C3 AdBlocker — Hamradio.my — Browser-flashable ad-blocker on a $2 ESP32-C3. Not radio, but exactly the kind of cheap-hardware hack that fits the workbench.

History & Culture

• How Amateur Radio Built the Indonesian Internet: PaguyubanNet, Packet Radio and the Pioneers of 1986–1994 — Hamradio.my — Deep history on how ham packet radio bootstrapped Indonesia’s early internet. Genuinely excellent long-read, easily the standout item this week — from both the curated and mega feeds.

Reference

• DXing Techniques for Amateur Radio: A Complete Guide to Working the World — Amateur Radio Today — Solid DXing primer, good bookmark-and-share material.

Community / Silent Keys

• DXer and DXpeditioner Kan Mizoguchi, JA1BK, Silent Key — ARRL News —Passing of a notable DXpeditioner.

Also Noted

• San Diego Section of IEEE Invited Talk Intersects ORI’s Antenna Work — Open Research Institute

• VHF for Parks On The Air? — Amateur Radio Weekly

• The W9IMS Brickyard 400 Special Event: Third Time’s a Certificate — The SWLing Post

• Records with Soul and a WAVE — The SWLing Post