Zero Retries is an independent newsletter promoting technological innovation in and adjacent to Amateur Radio, and Amateur Radio as (literally) a license to experiment with and learn about radio technology. Radios are computers - with antennas! Now in its sixth year of publication, with 3700+ 3800+ subscribers.
Steve Stroh N8GNJ, Editor
Tina Stroh KD7WSF, Business / Conference Manager
Substack says this issue is will be truncated by some email clients. Thus, it’s easier to read in a web browser:
www.zeroretries.org/p/zero-retries-0270
It’s easy and free (choose the free option) to subscribe
to receive your own copy of Zero Retries every week via email:
In This Issue:
I-Frame
Two New Open Source Implementations of AMBE
RMS Radar - Find gateways using unofficial or experimental modems
Video - I Didn’t Like Xiegu’s SDR Software, So I Made My Own!
Founding Members Who Generously Support Zero Retries
Comments on This Issue (Redirects to Comments Page)
I-Frame
By Steve Stroh N8GNJ
Brief notes about this issue of Zero Retries.
Founding Members and Paid Subscribers Update
Optional Paid Subscriptions, and especially Founding Member subscriptions to Zero Retries not only help offset various expenses incurred in publishing Zero Retries, but also were a significant portion of the “seed capital” we needed to host Zero Retries Digital Conference (ZRDC) 2026, and future ZRDCs. Thank You!
Our thanks to Nigel Armstrong NA6D for upgrading from a free subscriber to Zero Retries to Founding Member 0028 in the past week!
NA6D included this nice note:
I truly believe in what Zero Retries has become and it aligns so well with my interests. It is basically my only must-read newsletter. Thanks, Steve, for sharing your enthusiasm for digital amateur radio!
Founding members are listed in every issue of Zero Retries!
Our thanks to Bob Kehr KA9MDP for renewing as an Annual Paid Subscriber (3rd year!) to Zero Retries in the past week!
Financial support from Zero Retries readers is a significant vote of support for the continued publication of Zero Retries.
Zero Retries Digital Conference 2026 - Release Status
I had hoped to release the videos and other material from ZRDC 2026 this week, but didn’t get it done prior to ZR publication day. But, I expect to complete that work this weekend, so keep an eye on the Conference page.
Zero Retries Won’t Publish Next Week
To fully enjoy what promises to be a houseful of guests (more than our usual) for our Thanksgiving holiday, including the most special guest of all - Grandson Noah, I don’t plan to publish Zero Retries next week (normally Friday 2026-11-27).
Happy Thanksgiving Next Week to US Readers
We have much to be thankful for this year. This has been quite a year for Tina and I with some major health issues, an unexpected trip to exhibit at Hamvention, ZRDC 2026, our first grandchild, and other issues and events.
Happy Thanksgiving, folks!
Please direct comments / feedback about I-Frame to the Zero Retries email list with the hashtag #ZR0270. Paid subscribers can comment directly on the web version of this issue.
A Cease Fire in VARA vs xara
By Steve Stroh N8GNJ
The author of VARA has reversed their stance to instigate a “poison pill” in VARA 4.x.1 versions. The only reason for that new version was (apparently - no technical explanation has been offered) to break compatibility with earlier versions of VARA, and by extension, the independently developed, interoperable xara software.
For reference, see Zero Retries 0269 - VARA vs xara - The Bigger Picture.
On 2026-11-19, new versions of VARA were released:
VARA HF v4.9.2 (High Performance HF Modem)
VARA FM v4.4.2 (VARA for FM transceivers)
A notice was posted on varamodem.com:
ATTENTION!
A new versions just released, compatible with the older versions. Replace VARA HF v4.9.1 by v4.9.2 and VARA FM v4.4.1 by v4.4.2.
The big news in this update was:
compatible with older versions.
As the day progressed, there were some issues reported with these new “.2” versions where they didn’t actually work with “older versions” or caused other issues.
On 2026-11-20, yet another new version was posted:
VARA HF v4.9.3 (High Performance HF Modem)
VARA FM v4.4.3 (VARA for FM transceivers)
With the message changed:
ATTENTION!
A new versions just released, compatible with the older versions. Replace VARA HF v4.9.1 by v4.9.3 and VARA FM v4.4.1 by v4.4.3.
Now all that remains is for all of the VARA users who installed the “.1” versions of VARA (that had the compatibility breaking “poison pill”), and the “.2” versions of VARA (with the attempted fix) to update to the “.3” versions of VARA that presumably have the final fix, returning VARA to compatibility with:
VARA HF v4.9.0 (High Performance HF Modem)
VARA FM v4.4.0 (VARA for FM transceivers)
and (some) earlier versions of VARA.
And... of course, these newest two versions of VARA restore compatibility with xara.
Brief History of xara
To date, only xara’s developer - x0rro, knows, definitively, how xara was developed. x0rro claims that xara was developed ethically and legally by using AI to examine the inputs and outputs of VARA and then developing a specification, and then the xara software.
Then xara was tested for interoperability with VARA and tweaked as necessary to achieve full interoperability. Absent a legal process (trial) of VARA’s author vs xara’s author, we’ll never know.
What little I know is that the process x0rro described about creating xara is possible. Thus I’m granting x0rro the benefit of the doubt - innocent until proven guilty.
xara has several significant departures from VARA:
xara is open source,
xara was developed to run natively on Linux,
xara is more efficient - requires fewer “compute” resources than VARA,
xara has been ported to other platforms such as Windows, MacOS, and iOS / iPadOS.
To answer a “but… but…” objection, yes, xara still exists and is available from other sources if you look around. Derivatives (forks) of xara might be called something different than xara. If it’s a software package that interoperates with VARA and it’s running under Linux, it’s almost certainly a derivative of xara.
VARA Being Developed for Linux and MacOS
One of the more interesting developments in “VARA vs xara” was another announcement on the varamodem.com page:
We are working in a VARA multiplatform to have native macOS and Linux VARA versions available with Winlink and VarAC.
Thus one positive result from this kerfuffle is that the rapid and enthusiastic adoption of xara demonstrated that there truly is significant demand for a “Linux version of VARA”. Previous requests to VARA’s developer for a Linux version of VARA were declined.
As is referenced in that announcement, part of VARA’s author’s motivation for this decision was apparently
… and VarAC.
On the Facebook group VARA operators - Digital mode for HF radio, Irad Deutsch 4Z1AC announced that VarAC (which currently runs only on Windows) is being developed for Linux and MacOS, enabled in part by using the Rust programming language.
Thus there’s some subtle “peer pressure” for VARA to similarly evolve, including from Winlink, per this message from Steve Waterman K4CJX on the Winlink Programs Group email list:
…
A macOS version of Winlink Express is nearing release, and a Linux client is being explored, currently.
…
Yet another motivation for VARA to rescind the “poison pill” version of VARA was that the many discussion threads made it clear that many potential alternatives to VARA for data communications on HF are in development. Most of these implement the VARA Protocol Native TNC Commands. Thus apps that support VARA can just as easily support other data communications systems - they’re plug and play.
Note this does not imply that other data communications systems are interoperable on the air with VARA - most are not (xara and derivatives are the exception).
As a result of those discussions, many users of VARA became aware, for the first time, that reasonable alternatives to VARA exist or are in development. “Reasonable” meaning equivalent (or superior) data speeds, equivalent robustness in the HF environment, and actively under development (versus VARA being largely static in features or performance for the past several years).
Finally, perhaps the argument that the existence of independently developed xara “grows the VARA ecosystem” and serves to “legitimize” VARA as an “industry standard” rather than a single proprietary piece of software has gotten through to VARA’s author. If there are multiple implementations of “VARA compatible” software, that increases the attraction of VARA in competition with other data communications systems.
It will be interesting to watch how this issue plays out. For the moment, not only do we have xara and derivatives to work with, there are these many other data communications systems to experiment with. A full listing of those systems is a small project that I may attempt later in this issue if there is reasonable time to do so.
Post-publication Note - There wasn’t time, thus such a list is a project for a future issue.
Please direct comments / feedback about this article to the Zero Retries email list with the hashtag #ZR0270. Paid subscribers can comment directly on the web version of this issue.
Dear New Ham
By Steve Stroh N8GNJ
I receive a monthly notice of new Amateur Radio licenses within the ARRL Northwestern Division. Earlier this month I saw another article from a newly licensed Amateur Radio Operator that said in effect “I have my license; now what?” The following is a very rough draft of a letter that I’d like to send every new licensee.
Dear New Ham:
I’m writing to you “old school”, with this paper letter because that’s the only contact info that the FCC makes publicly available for your new Amateur Radio license.
Congratulations on your new Amateur Radio license! It’s literally a license to experiment, hands-on, with radio technology. You’ll likely hear from other Hams in your area about various aspects of Amateur Radio, such as getting on HF (once you have your General license), DXing, contesting, participating in emergency communications preparedness, various modes such as SSB and CW on HF, and talking on repeaters either with FM or one of the digital voice modes.
I’m writing to you to let you know about Amateur Radio activities that you may not know about, or your local Hams might also not know about - the amazing things that are happening in Amateur Radio that are digital / data modes, and other cool activities that are “more techie”.
I’m Steve Stroh N8GNJ and I live in Bellingham, WA. I publish a newsletter called Zero Retries where I write about digital / data modes… what I consider the cool stuff in Amateur Radio. Activities like:
High speed data communications networks on microwave frequencies - AREDN and HamWAN,
New data modes on HF and VHF / UHF,
Amateur Radio activities that can be done in whole or in part over the Internet, called Amateur Radio Over Internet,
Open Source software (and hardware) development, and especially software that runs on Linux and small appliance computers such as Raspberry Pi,
Software Defined Radio and GNU Radio - if you can describe it in software, there’s SDR hardware that can translate it into radio transmissions.
In Zero Retries, I call folks that are into such activities in Amateur Radio “NewTechHams” (or, sometimes, OldTechHams). We’re a demographic that’s growing fast within Amateur Radio. We prefer to experiment with software instead of a soldering iron, we prefer to connect modems to our radios instead of microphones, and we prefer using a keyboard to using a Morse Code key.
If the above is of interest to you and you’d like some help finding out how to get plugged into such activities, just email me. It’s a misconception that to “have fun with radio” you need to find someone physically close to you, or a local club (though that helps).
Here are a few pointers:
Ham Radio for Dummies book is a fantastic overview of Amateur Radio.
Subscribe to Zero Retries - it’s free: https://www.zeroretries.org. Zero Retries has been published for several years now - the archive is also free: https://www.zeroretries.org/archive.
Another great newsletter s Random Wire (also free). It discusses digital voice and Amateur Radio Over Internet - https://www.randomwire.us.
EtherHam is a great website (related to Random Wire) which dives deep into Amateur Radio Over Internet such as Internet (repeater) talk groups, digital voice modes, and related subjects.
Building a DigiPi is a great, inexpensive way to get started on digital / data activities: https://digipi.org.
The creator of DigiPi has a great YouTube channel: https://www.youtube.com/@KM6LYW.
There are an infinite number of support groups related to Amateur Radio - email lists, Discord groups, Reddit groups. Facebook has many, many Amateur Radio pages and groups, as does Mastodon.
Digital Library of Amateur Radio & Communications (DLARC) is a project of the Internet Archive. It’s Amateur Radio’s free online library. It has a huge amount of free material - old magazines such as 73 (one of my favorites) and many others, including many club newsletters. Everything in DLARC has been digitized and thus searchable by keywords. If you’re interested in building your own antenna, just type “antenna construction”. More info at https://archive.org/details/dlarc.
In this era, there are lots of ways to connect with folks that are interested in the same things you are. No matter what interests you, there are others out there who are into the same things! Amateur Radio Over Internet is one of the easiest ways to find other folks - many “talk groups” are focused on a single topic.
The most important thing that I’d like to leave you with is that it can take time to “find your tribe” within Amateur Radio. Thus please don’t be discouraged if no one in your area isn’t into the same things you’re interested in. Like-minded folks are out there!
So, please ask for help if you’d like to learn more. There are many of us who are eager to help you “find your tribe” within Amateur Radio.
Steve Stroh N8GNJ - steve@zeroretries.net
…
There are many, many other things that I could say, but I think such a letter should be limited to one sheet of paper, fairly large type, and just enough info to encourage the new Ham to reach out if they’re interested.
It would be fantastic if this could become an organized activity by a small group or organization, but I’ve learned that advocating projects that “they” should be doing has a better chance of success if it’s first proven out on a small scale.
Please direct comments / feedback about this article to the Zero Retries email list with the hashtag #ZR0270. Paid subscribers can comment directly on the web version of this issue.
Two New Open Source Implementations of AMBE
By Steve Stroh N8GNJ
AMBE is the (heavily…) patented vocoder used in most two way radio digital voice systems including digital voice systems used in Amateur Radio (except for FreeDV / RADE, M17 and a few other open source digital voice systems).
email from x0rro (creator of xara):
i am writing to report that i recently released xombe and xombe-stick, which may be of interest to you. they are clean room MIT-licensed code, and they implement AMBE decoders/encoders/transcoders as used in D-STAR and DMR. xombe-stick is a raspberry pi pico 2 firmware that emulates a ThumbDV or USB-3000/3003 stick. it works with all the popular software.
you’ve written about the need for open source AMBE in the past and my project addresses it.
Not content to make an open source equivalent of VARA, now x0rro is making an open source equivalent of AMBE. Cool!
x0rro is in good company in seeing a need for an open source equivalent of AMBE. Bruce Perens K6BP is also doing such work. On the digital voice email list, in September:
Some recent ham radio digital voice CODEC development which I have guided the AI through:
AMBE for all ham radio modes except System Fusion: D*STAR, DMR, NXDN, etc., with the AMBE-2+ modes compiled out by default until some patents expire in another 3 years. 0.97 or better compliance validated against an AMBE 3030 chip (1.0 is best) when in chip-compatible mode, non-chip-compatible is the default and handles bad packets without squeaking and doesn't emulate chip bugs. Also IMBE for Project 25 phase 1. Both floating and fixed-point implementations in Rust:
https://github.com/BrucePerens/hams_open/tree/main/daemons/ham_digital_modes/src/ambe
Codec2 In fixed-point Rust, 0.9999 compliance with the float C version:
https://github.com/BrucePerens/hams_open/tree/main/daemons/ham_digital_modes/src/codec2_3200
1600: https://github.com/BrucePerens/hams_open/tree/main/daemons/ham_digital_modes/src/codec2_1600
C API for 3200 Rust, we can extend this for 1600: https://github.com/BrucePerens/hams_open/tree/main/daemons/codec2_3200_capi
Even if the digital voice modes that use AMBE are recreated as open source thanks to x0rro’s and K6BP’s work, I’ll still have a preference for M17 because it’s the only digital voice mode that includes data that’s not an afterthought (such as D-Star) or “left to the radio manufacturer” (such as DMR).
The situation around AMBE is complex, and unclear and there is also the “FUD1 factor”. It would be ideal if someone who had some standing in Amateur Radio could publish something unambiguous about what systems have what patents expiring exactly when, circa 2027.
But ultimately, my preferred “digital voice” mode is a data mode one that’s fast enough to transport digitized voice as “just bits” with a “realtime voice” protocol ID and be running parallel decoders for “voice mode 1”, “voice mode 2”, “data mode 1”, “data mode 2”, etc. One example is that AREDN systems treat Voice Over Internet Protocol (VOIP) telephony, as well as linking repeaters, as just a couple of data types among many that are easily transported by AREDN.
We’ll get there with “voice as just another form of data”.
Ditto video - we don’t need purpose-built video systems in this era.
In the meantime, kudos to both x0rro and K6BP chipping away at proprietary elements of Amateur Radio that are contributing to the Amateur Radio Tower of Babel. Soon enough such issues will be handled automagically behind the scenes various web standards are handled transparently by web browsers.
Please direct comments / feedback about this article to the Zero Retries email list with the hashtag #ZR0270. Paid subscribers can comment directly on the web version of this issue.
ZR > BEACON
By Steve Stroh N8GNJ
Short mentions of Zero Retries Interesting items.
New Slide Deck on Mercury Modem - November 2026
Rafael Diniz on the hermes-general email list:
I committed a "working" presentation about Mercury (LaTeX source
committed too) :
https://github.com/Rhizomatica/mercury/blob/mercuryv2/docs/presentations/2026-10-mercury/mercury.pdf
This slide deck includes 29 slides with ample technical detail on how Mercury functions. The Rhizomatica development team is working very hard, along with a number of on-air testers, to continually improve Mercury to be fully equivalent to the performance of VARA HF. Mercury isn’t there yet, but there’s no magic in VARA HF2, and I have no doubt that the Rhizomatica development team will be able to achieve performance parity in Mercury to VARA HF, and then go beyond the performance of VARA HF. See the following story about rapid iteration.
Mercury 1.9.20 released: the “2.0” architecture, Android and iOS previews (does not connect to 1.9.19)
Rafael Diniz on the hermes-general email list:
Mercury 1.9.20 is out. It is a big one: the architecture we have been calling "2.0" is in it.
https://github.com/Rhizomatica/mercury/releases/tag/v1.9.20
IMPORTANT: 1.9.20 does not connect to 1.9.19 or any older version, in either direction. The connect frames have a new packet type, and the versions refuse each other cleanly: each logs the other's CALL and never transmits, and nothing stays keyed. Please upgrade every station you talk to at the same time. Before upgrading, please read the release notes:
https://github.com/Rhizomatica/mercury/blob/v1.9.20/docs/RELEASE-1.9.20.md…
WHAT'S NEW
The speed ladder starts high and falls back fast*
Connect and disconnect*
A narrow MFSK floor for 500 Hz sessions*
High-Doppler channels (polar paths, flutter)*
Pat / Winlink and other fixes*
TECHNOLOGY PREVIEWS: ANDROID AND iOS
Both are the Mercury GUI with the modem inside. They are for trying out, not yet for relying on.
Android (64-bit ARM, sideload the .apk):
You pick the radio's USB sound card in Soundcards.
CAT and PTT go over the radio's own USB cable: Radio, method Hamlib, "Direct USB, no driver (experimental)". This works with Silicon Labs CP210x chips: IC-7100, IC-7300, FT-710 and many cables.
It is tested on Android 15 only, and the app has to stay in the
foreground.iOS (iPhone and iPad): sideload the .ipa with SideStore or AltStore Classic. Through AltStore PAL (EU, Brazil, Japan) once Apple has notarized it; that is in review now.
See the link for full details on each What’s New item. Rapid iteration with an enthusiastic user / tester base helping Rhizomatica developers test Mercury.
It was exciting to read that Mercury is now available as an app on iOS / iPadOS and Android.
Latest ARRL Handbook Has Updated Digital Networking Section
Glen Popiel KW5GP via email:
For the latest issue of the ARRL Handbook (#102), they asked me to write the digital networking section of the digital modes chapter (Section 15.6.15), and I just received my copy. Getting in the Handbook was always one of my dreams once I started writing ham radio books, and here it is now a reality. I think it looks great.
Having read KW5GP’s new ARRL book Digital Networking for Ham Radio several times now, if he’s enthusiastic about the Digital Networking section of the newest ARRL Handbook, that’s a good enough recommendation for me. The current ARRL Handbook is now on my Christmas wish list.
OpenX6X00 - Open firmware for the Xiegu X6100 and X6200
Every digital mode decoded and sent on the radio itself, FreeDV’s RADE digital voice, Winlink email over HF, read and written on the radio too, Zello and SVXConnect, the DX cluster on the waterfall, eleven activation programmes from SOTA and POTA to towers, castles, mills, lighthouses, lakes and locator squares on big outdoor tiles, TUNE for an external tuner, a 3D band scope, themes, Bluetooth, a TCI server for the VFO-Knob, and the radio worked from any browser on your network, or from anywhere over Tailscale. Forked from the last open release of the IU1WXY firmware when it went closed, cleaned of every service that phoned home, audited three times, and updated from the radio itself with automatic rollback.
My thanks to Steve Monsey N0FPF for bringing this development to my attention for inclusion in Zero Retries:
What I found interesting is this group has made the radio better because it’s an SDR. It claimed everything under the hood, no PC required, even for Winlink.
Starlink Mini 2 is Announced, Not Quite Available
The Starlink Mini 2 has been announced by Starlink. The two big innovations are that it comes with a built-in (well, snap-on) battery claimed to be good for 4.5 hours and it can be powered (claimed, again) by USB-C (60 watts USB-C power source).
Apparently you can buy additional battery packs to be able to swap in a new battery for continued operation longer than 4.5 hours. I saw a mention that the battery pack can also provide USB-C power, so that implies that you can charge a battery pack independently from the Starlink Mini 2.
Like the original Starlink Mini, Wi-Fi is built-in to the unit - nothing external is required.
Some additional detail from TechSifted:
Wi-Fi 6
Tripod mount - standard 1/4-20 camera thread
(No mention of a separate Ethernet connection that the Starlink Mini has.)
The Starlink Mini 2 isn’t quite publicly available yet. Note as of mid-November:
Preorders now open by invitation for select US customers. Coming soon to more customers and countries.
For my purposes - emergency communications in the field and when not doing that, providing independent low-bandwidth connectivity into N8GNJ / Zero Retries Labs (Starlink Standby service), I prefer my current Starlink Mini that can be powered with a long power cord and a 12 volt adapter, and Starlink Mini’s dedicated Ethernet connection.
I’ll guess that the Mini’s dedicated Ethernet connection has found a customer base for off-grid, low-cost connectivity where the Ethernet connection makes interfacing with remote equipment such as monitoring pipelines or electrical distribution trivially easy and reliable. Such use cases would not be interested in using Wi-Fi. Thus I’ll guess the Mini would continue to remain available, at least for enterprise customers.
It’s conceivable that the Starlink Mini 2 could have the capability of an Ethernet adapter via the USB-C connection, much as Starlink does with my current (home) Starlink Gen 3 where the Ethernet connection was an inline adapter between the Starlink antenna and the power supply.
But I can also see a significant use case for the Starlink Mini 2 with the improved Wi-Fi coverage of Wi-Fi 6 and the built-in battery. Imagine a hotel room or a campsite where you need to put the Mini 2 on the car and not drain the car battery. 4.5 hours is a pretty reasonable time to watch a movie on your phone or tablet and catch up on email and web browsing. Then the next day you charge up the battery and it’s ready for the next evening’s Internet access.
The camera tripod thread on the Mini 2 is a nice touch. Camera tripods are inexpensive and would make a good mount for a Mini 2, especially if you need to put it somewhere it has an unobstructed view of the sky. The built-in battery and the Wi-Fi 6 minimize the hassle of such an arrangement.
Introduction to Packet Radio Series
Doug Schafer AB7DG via email:
https://www.choisser.com/packet/
By Larry Kenney, WB9LOZ
This series of eighteen articles was originally written in 1988 to appear in Nuts & Volts, the newsletter of the San Francisco Amateur Radio Club. The series has been widely distributed since then, with revisions issued in 1991, 1993, and 1995. Occasional revisions were made to this version on the web thereafter, in the late 1990s.
The author is no longer active in packet radio and is unable to provide up to date information on packet radio; however he has left this material on the Internet for access by those who might find it helpful.
This series was a fixture on Packet Radio Bulletin Board Systems, and were, effectively, required reading for newcomers to Packet Radio. Monitoring popular packet radio frequencies, you saw these articles displayed and downloaded (being read) a lot.
What is great about this particular repository is that it’s the original author’s site, and these versions are the most up-to-date versions by the author.
I haven’t read through them all again, but I’ll guess that they largely hold up and could inspire a newer version of the same idea, updated to incorporate new Packet Radio functionality, such as in Dire Wolf, AX.25 v2.2, OpenTNC, etc. Good documentation is precious.
I sent an email to WB9LOZ thanking him for this great contribution to Packet Radio and how useful I found this series back when I was just getting started in Packet Radio.
LinHT Rev C is alive: what works and what comes next
Great status report on the state of the LinHT project as of mid-November 2026, by Vlastimil Slinták OK5VAS:
TL;DR
LinHT Rev C works. M17 TX, USB-C networking, audio, microphone, GNSS, USB boot from the side button and power management are verified.
Most of the original C62 board stays untouched. Only the display and, for now, the SMA connector come from the donor.
Seven Rev C boards exist or will exist next week, using all the SoMs we had.
Next is a production batch of at least 50 kits. We are waiting for the SoM quote from CompuLab.
Ballpark: EUR 250–400 per kit, tax included, shipping not included, to be refined within a few weeks. The donor C62 (around USD 65) is not included.
LinHT will be sold as a kit for radio amateurs. Assembly and operation according to the rules of your country are your responsibility.
How we will sell it (crowdfunding, Lectronz threshold pre-order, or Foundation-funded) will be decided by the M17 Foundation. Tell us what you prefer.
It’s a long, detailed report with lots of photos - recommended reading!
How you can help right now
Some of you already bought a C62 and are ready to test. Thank you! Keep it. You will need it as soon as boards are available. Until then:
join the #linht-dev channel on the M17 Discord and tell us which way of ordering you prefer,
look at the hardware and the software. There is a lot of work on Linux, the UI and applications that does not need a board,
tell other people about LinHT. Real interest from the community is what makes the first 50 possible.
I’m trying hard to keep getting the word out here in Zero Retries
about how exciting and revolutionary the LinHT is for Amateur Radio.
Please pass this info along to those in your circles, especially in organizations and companies that potentially could do something to help these three incredibly talented and hardworking volunteers, and the M17 Foundation (who formally sponsors the LinHT Project) to help bootstrap this project to get over the hump of getting working LinHTs into the hands of those in positions of influence.
Helpful hint that I’ve learned the hard way - Don’t forward this as an email. It just doesn’t make (enough of) an impact, especially to those who are really busy.
Instead, go to the link and print that article, preferably on a color printer, and hand it to someone you want to influence with your personal recommendation that this is worthy of consideration and support.
To the Help Needed, I’d add:
Articles on what potential use cases for a LinHT. For example, being able to use FreeDV RADE (no idea if that’s possible on the LinHT hardware) on SSB - much narrower signal using SSB than FM or digital voice.
Potential GNU Radio flowgraphs that might be interesting to use on a LinHT.
Potential financial help to M17 Foundation to bootstrap the production of a larger quantity of LinHT boards (economies of scale).
Potential help for manufacturing and distribution of LinHT boards in the US.
Potential help interesting hardware manufacturers to make turnkey versions of LinHT (probably not in the same form factor as a Retevis C62).
Kantronics Black Friday Sale
Email from Kantronics:
From now through Cyber Monday, every new Kantronics TNC is 15% off.
Use code KAN15 at shop.kantronics.com
…
HOW TO SAVE
Visit shop.kantronics.com
Add any new Kantronics TNC to your cart
Enter KAN15 at checkout for 15% off
This offer ends on Cyber Monday, November 30, at 11:59pm Central. Whether you’re setting up your first packet station, getting your emergency kit ready for winter, or adding a node to your local network, this is the best time all year to do it.
That’s a pretty reasonable discount if you’re tempted, like I was, to invest in the new Kantronics KPC-3XE.
RMS Radar - Find gateways using unofficial or experimental modems
Ben Kuhn KU0HN on the Winlink Programs Group email list:
With the xara drama coming to a close, one thing that has resulted is more widespread testing of open source modems. The developers of these modems need users to help find and debug issues. Testing also helps the WDT decide whether or not to officially include the modem.
My own BPQ node has been running Mercury for almost 18 months. Since Richard Ko0ooo started using the MERCURY service code (and others of us followed suit) I have seen more Mercury traffic in the past 4 days than I did in the prior 17 months. Several of us are now using DATA2G and VARDEFM service codes as well.
The issue with service codes is discoverability for users. I put together a little app called RMS Radar to solve that problem. It’s open source (MIT License), written in go, works offline, and can run as a desktop app, or as a server to provide a station list to an entire network. It can filter nodes by service code, and uses VOACAP to predict path quality (thanks to the PAT devs for the work on this).
The project website is here: https://ben-kuhn.github.io/rms-radar/
A public instance is available here:
The desktop versions could use more testing, especially on Windows as I don’t really use that platform outside of testing.
Any feedback is welcome. Github issues and PRs are appreciated.
This issue of actual on the air testing is the Catch 22 for new data modes. Without some reasonable amount and diversity of testing, it’s hard for new data modes to become popular. But to do some testing, you have to be able to find others who are similarly interested in doing such testing. Then there is the sheer diversity of all these new modes - test which one, where to test it, when to test it, who to test it with?
And yes, with the VARA vs xara kerfuffle (The Streisand Effect…) there’s more interest, and more motivation, than ever before about alternatives to VARA. VARA’s author provided a stellar example of why alternatives to VARA might be a good idea to investigate… just in case.
KU0HN to the rescue with RMS Radar! Kudos!
My K2K Packet radio client
Josh KK6SEN on the 145050PacketNetwork email list:
I have released a new version to tackle a few issues. I have been testing it off and on now for about a week. Let me know what you think.
https://map.kk6sen.com/downloads/
Added the ability for a direct connect mode from K2K client to client. You can also alert the remote user with a :bell or :ring command. Those sounds are configurable in settings.
Added a headless mode. You can start the app in a console with something like “k2k-packet-desktop --web” and then open the IP:port in your browser to use the client. The layout is identical to the app GUI. There is also a light weight 32bit arm installer. This works great for your pi zero 2w
Improved the error messages on different connection failure modes.
You can now send a blank CR packet. Just hit enter or send when nothing is typed in the message box
You can no longer use the same callsign-SSID combo on both the main callsign settings and the PBBS setting.
The features list now states the PBBS is a Kantronics KPC3+ inspired PBBS since I did model my layout after their layout.
Modified the NET/ROM packet decoding section. (This might not be perfect yet) IF you ever get a packet that doesn’t decode correctly, send me the unproto and the raw log. You can find those my clicking the little folder icon on the top right.
For details, feel free to check out the github. https://github.com/Josh-kk6sen/k2k-packet-desktop
Hope you like it. Thank you for letting me play packet radio with you all. :)
Sounds interesting. I gotta get a DigiPi spun up and see how NET/ROM is implemented in that software.
The Iranians Are Here
Jeff Davis KE9V on his blog:
In the 21st century it wouldn’t be unusual for one of our major technical systems to let out its magic smoke. But even the most skeptical among us must admit that so much has failed in the United States (and around the globe) in just a few days that the culprit probably isn’t a failed router in Arkansas. First the global Outlook shutdown, then all air traffic grounded, a major banking outage, our national security communications network going dark, and today a cyber attack on 178 major websites.
Microsoft says the Outlook problem was a capacity upgrade and the FAA blames a contractor’s router for the airline grounding. Maybe. But five major failures in a single week, in the middle of a war with Iran? I’m not buying it.
…
There are a lot of implausible scenarios that some people prepare for. But I agree with KE9V that a major cyber attack is now more plausible than ever. All of our major day to day infrastructure systems are interdependent. A major portion of the Internet gets hacked, and you can no longer go to the store to buy milk, bread, and TP with your credit card. The electric grid can get hacked and the distribution of natural gas is impacted because the gas pipeline pumps require electricity. Traffic light controls get hacked and gridlock ensues for hours and just in time deliveries of groceries are impacted. Etc.
One common sense thing you can do is invest in a larger battery bank that can at least power your (gas) furnace for a few days. A few hundred dollars will get you some soft solar panels that if you don’t want to use full time, can be stashed out of the way and just laid on the driveway to recharge the battery.
My opinion is that Starlink is the most hardened “consumer” Internet option. All of the mobile telephone companies have significant “legacy” systems deep in their infrastructure that are ignored as long as they keep working… until they don’t. Starlink doesn’t have such baggage - it’s a creature entirely of the 21st century with all modern systems.
Starlink has also had significant real-world experience in surviving cyber attacks from Russia because they provide services to Ukraine. Starlink has also learned from providing the hardened Starshield system / service to the US government.
Video - I Didn’t Like Xiegu’s SDR Software, So I Made My Own!
Steve McGrane KM9G on the Temporarily Offline YouTube channel:
The Xiegu G7250 supports Ethernet SDR connectivity, but its reliance on the aging HDSDR software left some amateur radio operators disappointed. Instead of complaining about Xiegu's software choices, I decided to see what I could build myself. Using Linux, Python, and a little reverse engineering, I created a browser-based SDR interface that communicates directly with the G7250 over Ethernet, without needing HDSDR or its proprietary Windows DLL.
In this video, I'll demonstrate how the G7250 Ethernet protocol works, how we built a Python web server with a documented REST API, and how we turned raw IQ data into a working 48 kHz spectrum analyzer and waterfall display. We can even tune the receiver directly from a web browser! It's an experimental proof of concept, not a complete replacement for HDSDR, but it demonstrates what's possible when amateur radio meets open development. The hardware already has capabilities worth exploring, and this is just the beginning.
This is real progress towards a software defined radio that ships with basic functionality, that can be fully customized by the user to their preferences.
The Xiegu G7250 is an HF plus 6 meters, 100 watt radio. One of these days, some hungry manufacturer will figure out there’s a market for a VHF / UHF radio with these features.
My thanks to Joe Hamelin W7COM for bringing this development to my attention for inclusion in Zero Retries.
Please direct comments / feedback about ZR > BEACON to the Zero Retries email list with the hashtag #ZR0270. Paid subscribers can comment directly on the web version of this issue.
Request To Send
By Steve Stroh N8GNJ
Editorial, Commentary, and Occasional Digressions
3800 Email Subscribers!

I have no idea where this latest wave of email subscribers came from. Some mention(s) of Zero Retries has instigated a steady stream of 5-10 new subscribers per day over the last ten days or so. Whatever the cause, I remain grateful to all of you Zero Retries readers.
N8GNJ and K4APR Not Voted Onto TAPR Board of Directors
Email from TAPR:
Stana Horzepa, WA1LOU, Darryl Smith, VK2TDS, and David Goncalves, W1EUJ win with 28.57%, 20.41%, and 17.55% of the votes each.
Details of the results can be seen here: https://secure.electionbuddy.com/results/C6QVGLZ8Z5LW
One reason I decided to run for a position on the TAPR Board of Directors is that from prior experience, my (external) inputs to the TAPR Board have been met with silence or indifference. Thus I decided to try to “influence from inside” by running for position on the TAPR Board of Directors.
Jason Rausch K4APR, as part of his TAPR election bio:
I believe a crucial part in continuing the tradition of amateur radio is by evangelizing digital modes to the younger, more IT/Networking/Computer minded sector. I intend to keep doing my part to see that happen.
I said, as part of my TAPR election bio:
I think that TAPR should (again) provide comments to the FCC when it issues NOIs, NPRMs, Reply Comments - every time.
I hope to get TAPR involved in assisting M17 Project with popularizing the LinHT project - Linux Handheld Transceiver, a fully Software Defined portable transceiver (ANY mode) operating on 70cm, at 5 watts, that runs Linux and GNU Radio.
Get TAPR involved in promoting “mostly digital” Amateur Radio to be more widely recognized as relevant to society and radio technology development in general.
Get TAPR involved (again) in standards coordination like it has done previously with AX.25 and APRS.
In addition I mentioned that Tina and I, through Zero Retries, have started the Zero Retries Digital Conference.
But, TAPR members apparently didn’t want the kind of change that K4APR and I were advocating. We both received the (same) low number of votes and thus we won’t be members of the TAPR Board of Directors to promote our perspectives within TAPR.
Moving on…
…
Have a great weekend, all of you co-conspirators in Zero Retries Interesting Amateur Radio activities!
Please direct comments / feedback about Request To Send to the Zero Retries email list with the hashtag #ZR0270. Paid subscribers can comment directly on the web version of this issue.
73,
Steve N8GNJ
Closing Thanks
My ongoing Thanks to:
Tina Stroh KD7WSF for, well, everything!
Jack Stroh, Late Night Assistant Editor Emeritus
Fiona and Shreky Stroh, Late Night Assistant Editors In Training
Founding Members Who Generously Support Zero Retries:
Founding Member 0000 - Steven Davidson K3FZT (Renewed 2026, 4th year!)
Founding Member 0001 - Randy Smith WU2S (Renewed 2026, 4th year!)
Founding Member 0002 - Chris Osburn KD7DVD (Renewed 2026, 4th year!)
Founding Member 0003 - Don Rotolo N2IRZ (Renewed 2026, 4th year!)
Founding Member 0004 - Bill Arcand W1WRA (Renewed 2026, 4th year!)
Founding Member 0005 - Ben Kuhn KU0HN (Renewed 2026, 4th year!)
Founding Member 0006 - Todd Willey KQ4FID (Renewed 2026, 4th year!)
Founding Member 0007 - Merik Karman VK1DF / VK2MKZ (Renewed 2026, 4th year!)
Founding Member 0008 - Prefers To Remain Anonymous 08 (Renewed 2026, 4th year!)
Founding Member 0009 - Prefers To Remain Anonymous 19 (Renewed 2025, 2nd year!)
Founding Member 0010 - Merik Karman VK1DF / VK2MKZ (Renewed 2026, 4th year!)
Founding Member 0011 - Rick Prelinger W6XBE (Renewed 2026, 3rd year!)
Founding Member 0012 - Ryan Tolboom N2BP (Renewed 2026, 3rd year!)
Founding Member 0013 - Newton White N4EWT (Renewed 2026, 2nd year!)
Founding Member 0014 - Joe Hamelin W7COM (Renewed 2026, 2nd year!)
Founding Member 0015 - Rich Stocking N7OP (Renewed 2026, 2nd year!)
Founding Member 0016 - Chuck Hast KP4DJT (Renewed 2026, 2nd year!)
Founding Member 0017 - Phil Karn KA9Q (Renewed 2026, 2nd year!)
Founding Member 0018 - Prefers To Remain Anonymous 47 (Renewed 2026, 2nd year!)
Founding Member 0019 - Prefers To Remain Anonymous 0108 (New 2025)
Founding Member 0020 - Prefers To Remain Anonymous 110 (New 2025)
Founding Member 0021 - Prefers To Remain Anonymous 111 (New 2025)
Founding Member 0022 - Prefers To Remain Anonymous 112 (New 2025)
Founding Member 0023 - Prefers To Remain Anonymous 116 (New 2026)
Founding Member 0024 - Rob Bowser (SPOOLTENNA) (New 2026)
Founding Member 0025 - Dave Stewart K7XST (New 2026)
Founding Member 0026 - Prefers To Remain Anonymous 32 (New 2026)
Founding Member 0027 - Mitch Hamm N8XS (New 2026)
Founding Member 0028 - Nigel Armstrong NA6D (New 2026)
Numerous Annual and Monthly subscribers who also generously support Zero Retries financially!
You thousands of readers of Zero Retries without which there would be little point in publishing this newsletter.
The Usual Administrivia
Zero Retries About - www.zeroretries.org/about
Zero Retries Digital Conference - www.zeroretries.org/p/conference
Zero Retries (Substack Blanket) Privacy Policy - substack.com/privacy
Zero Retries Reprint / Reuse Policy - www.zeroretries.org/p/reprint-reuse
Fair Use - All excerpts from other authors or organizations, including images, are intended to be fair use and are fully attributed generally by author and link (URL).
Paid Promotional Content - Unless otherwise noted in the article or item, advertisement, or sponsorship notice, Zero Retries does not include paid promotional content. Exceptions:
Advertisements in Zero Retries,
Sponsorships in Zero Retries,
Zero Retries products,
Zero Retries events
Features and content exclusive to paid subscribers.
Zero Retries 2026 Index - www.zeroretries.org/p/index-2026
Zero Retries Archive - archive.org/details/zeroretries?sort=-date
⬅️⬅️⬅️ Previous Issue of Zero Retries | Next Issue of Zero Retries ➡️➡️➡️
Zero Retries 0270 was published on 2026-11-21. This issue was 7598 words.
Footnotes For This Issue
To see the relevant sentence for the footnote, just click the footnote number.
Fear Uncertainty and Doubt - FUD was a business strategy and a core competency for some technology companies.
No magic, just clever use of multiple techniques, overlaid, such as different speed tiers interleaved with Forward Error Correction and compression, and many other techniques.


