2025-01-10 — What’s New at DLARC 2025-01, 2400+ Email Subscribers, HF Signals zBitx, SignalSDR Pro, DRATS2 Project, GLnet, New APRSdroid, ka9q-radio Video Series, Bald Yak Series (on GNU Radio)
Zero Retries is an independent newsletter promoting technological innovation that is occurring in 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 fourth year of publication, with 2300+ 2400+ subscribers.
My thanks to Prefers to Remain Anonymous 19 for renewing as a Founding Member Subscriber to Zero Retries recently!
Founding members are listed in every issue of Zero Retries!
My thanks to Gerry Brown KK7GAB for renewing as an Annual Paid Subscriber to Zero Retries recently!
My thanks to Bill Kreutinger KM6SLF for one year of being a Paid Subscriber to Zero Retries!
My thanks to Prefers to Remain Anonymous 61 for upgrading from a free subscriber to Zero Retries to a Paid Subscriber recently! PTRA 61 said: Interest in Ham radio learning / experiencing more about it.
Financial support from Zero Retries readers is a significant vote of support for the continued publication of Zero Retries.
2400+ Email Subscribers to Zero Retries!
At the end of 2024, the email subscriber count of Zero Retries ticked up past 2400. Each time I update the “century” metric of Zero Retries email subscribers, I disclaim that it’s an imperfect metric of actual readership of Zero Retries. One recent issue is that there are folks subscribing to receive Zero Retries via email (and “followers” on Substack) that, from a quick glance at their areas of interest, don’t seem to have any connection with Amateur Radio, or radio technology. I think there is some implied quid pro quo amongst Substack creators and readers that if someone subscribes to Zero Retries, I’ll automatically subscribe to them (I don’t). Or there’s some kind of positive feedback within the Substack ecosystem from recommending a Substack publication like Zero Retries… even if your Substack publication has nothing to do with the one you recommended. Or something. “Followers” on Substack mystify me, and I’ve neve posted anything to those who “follow” Zero Retries (and I cannot delete “followers” as I can with email subscribers). Frankly, all the social media gamification that’s going on within Substack is something that I look forward to leaving behind when I do transition Zero Retries off Substack.
Another factor is that a lot of folks don’t want to subscribe to Zero Retries because of the “Substack issue”, which is heard and understood and to be rectified in the near term. Another is that many folks read Zero Retries via RSS feed, or only after I post mentions of a new issue on Mastodon and Bluesky social media platforms, which are impossible to quantify, other than having 300+ followers on Mastodon and 100+ followers on Bluesky, both of which I use exclusively for Zero Retries notifications and very minor interaction.
Nonetheless, the steadily increasing email subscription count does reflect that readership of Zero Retries is continuing to grow, overall, and for that I’m gratified. Thank you, Zero Retries readers! Without you readers, there would be little point in throwing text into the bitstream about all of the technological innovation that I find and share within and adjacent to Amateur Radio, which I delight in sharing with you here in Zero Retries.
Transition from Substack to Ghost - Still in Progress
I had hoped that this issue of Zero Retries would be the first to be published on the Ghost email newsletter platform. But truth be told, I enjoyed my recent two-week Holiday hiatus and relaxed and did very little Zero Retries work other than continuing to read and discover cool stuff about technological innovation in and adjacent to Amateur Radio, and bookmark such discoveries, as you’ll read in this issue.
Be assured that my intention to transition Zero Retries from Substack to Ghost is still in progress… just delayed a bit.
And to the advice of a trusted advisor to Zero Retries, I won’t be apologizing / explaining each week that the transition hasn’t happened. At most there will be one issue’s notice where I explain that the next issue will be published on Ghost, and any transition instructions if you want to keep receiving Zero Retries via email.
Intended Attendance at 2025 Amateur Radio Conferences
Tina KD7WSF and I have been discussing our / my attendance at various events in 2025, and here’s a terse list of our plans as of early January. More details as the events get closer (and our plans firm up).
SEA-PAC 2025, 2025-05-30 thru 06-01 in Seaside, Oregon, USA
Pacificon 2025, 2025-10-10, 11, 12 in San Ramon, California, USA
This year, Tina and I hope to be semi-organized enough to designate a place and time during these events to do informal Zero Retries meetups.
Neat Hack for Amateur Radio Email Lists Overloading One’s Inbox
Google is threatening dire consequences now that my paid storage space exceeds 85% of the online storage tier I’m currently paying for. Some of that is from my extensive use of Google Drive (which really needs a good cleaning / reorganization). But most of it is from more than a decade now of intense use of Gmail, and my decision to move most of my Amateur Radio email list subscriptions to my primary Gmail address.
But recently, I discovered a neat hack to reducing my “Inbox Overfloweth with Amateur Radio email lists” issue - many groups.io email lists have an RSS feed!
For example, the “pretty active” 44net@ardc.groups.io email list has an RSS feed (listed under Group Information on the left sidebar):
The advantage is that I can set my subscription to the 44net email list to:
Special Notices Only Receive only special notices sent by the moderators. (Go to the group's website to view other messages.)
or
No Email Receive no group messages by email but remain subscribed so you can view content on the group's website.
… and in changing to either of those settings, I won’t be filling up my email inbox with all of the messages of that email list, but I will I retain my “full privileges” as a subscribed (and approved) member of that email list. If I see something from that email list in my RSS feed that I want to comment on, I can go to the web page of that thread and post a reply there.
Not every groups.io email list has an RSS feed - I’m not sure what the differentiation is between those that do, and those that don’t.
Disclaimer - I haven’t yet implemented this idea, but I think this will be a very handy tool and a significant reduction in my email inbox overload.
In This Issue…
I had intended to offer two articles - Trends I Hope to See in 2025 (and Beyond) and Explaining the Use Case for Data Over Repeater - Part 4. But as I stated earlier, I enjoyed my Holiday Hiatus and neither article progressed much beyond an outline during my Holiday hiatus. That coincided with a lot of developments and news that occurred during my Holiday hiatus period. Thus I’m deferring those articles to (hopefully) a future issue(s) of Zero Retries and devote most of the space in this issue to catching up with an “excess” of ZR > BEACON items. And, of course, the latest goodies that have been made available in DLARC, courtesy of Kay Savetz K6KJN.
Even with those two articles deferred, this issue is going to ridiculously overflow your email reader, thus I suggest just clicking this link to read this issue in a web browser.
Big Project In The Works
There is a big Zero Retries Interesting project in development that there simply isn’t time, or room, to properly cover in this issue. This big project will be revealed in Zero Retries 0185 next week, and there will be a role for Zero Retries readers, especially software / firmware developers.
I haven’t been this jazzed about an Amateur Radio development for a long time, and can’t wait to reveal it in partnership with my co-conspirator on the project.
Regarding the FreeDV HF Digital Voice Mode…
In ZR > BEACON in this issue, the lead story is about the new zBitx, a $150 Software Defined HF Radio. One standard feature of the zBitx leaped out at me:
The zBitx comes bundled with … FreeDV…
Thus I find it ironic that the $3649 FlexRadio FLEX-8400M Software Defined HF Radio features these modes:
SSB, CW, AM, SAM, FM, RTTY, DIGITAL
Note what’s missing in the list of modes that the 8400M is capable of? Yep. It doesn’t include the FreeDV HF Digital Voice Mode.
The FLEX-8400M that’s “Software Defined”… costing 24x as much as the zBitx… presumably far more capable and sophisticated than the zBitx… does not include the mature, capable, high performance open source FreeDV HF digital voice mode as a standard feature.
If I were FlexRadio, or a FlexRadio owner, I’d be a bit embarrassed that the zBitx is outclassing FlexRadio by including FreeDV as a standard feature.
‘Nuff said.
Have a great weekend, all of you co-conspirators in Zero Retries Interesting Amateur Radio activities!
What’s New at Digital Library of Amateur Radio & Communications — January 2025
By Kay Savetz K6KJN
Happy new year from DLARC, your free online ham radio library. What’s old is new again.
On January 1, a trove of old material entered the public domain in the United States. Written works from 1929 and sound recordings from 1924 are now free for everyone to copy, share, and adapt, including the cartoon characters Popeye and Tintin, and musical compositions Singin’ in the Rain and Boléro. This page at Duke University’s Center for the Study of the Public Domain has a great rundown of general-interest items that are newly free.
DLARC has newly added material from Techcon, the ARRL West Central Florida Section Technical Conference. Since 2015 the annual conference has specialized in technical talks including antenna design, digital voice modes, DSP, and APRS. I’ve added presentation slide decks, videos, and proceedings documents from the conference. (The 2025 conference is next month, you can attend in person or online.)
Turning to newsletters. DLARC has added 159 issues of ATCO Newsletter, the journal of Amateur Television in Central Ohio. The newsletter has been published quarterly since 1982, promoting ATV knowledge and activities.
We’ve also added 159 issues of INDEXA, the newsletter of the International DX Association — a non-profit organization devoted to the enhancement of amateur radio, worldwide peace, and friendship. Founded in 1983, the group has sponsored hundreds of DXpeditions to rare and semi-rare countries.
And, DLARC now has 495 issues of The North Shore Amateur Radio Club newsletter. NSARC is based in Oshawa, Ontario, Canada. They’ve done an admirable job of scanning back issues of their newsletter, which has been published since 1968.
As we enter the new year, I’d like to remind you that anyone can upload material to Internet Archive, to make that material available to everyone. All it takes is a free account. Feel free to upload something that you create or curate, then e-mail me if you think it’s a fit for DLARC. Just this week, Dick H. uploaded hundreds of newspaper clippings about WNTC Radio, which was a college radio station that he DJ’d at once upon a time. WNTC was the shared station of Clarkson College (now Clarkson University) and Potsdam State Teachers College (now SUNY Potsdam). Dick invested hours of his time to research and collect more than 500 news clippings, uploaded them to Internet Archive, and now the WNTC Clippings collection is part of the college radio collection.
Digital Library of Amateur Radio & Communications is funded by a grant from Amateur Radio Digital Communications (ARDC) to create a free digital library for the radio community, researchers, educators, and students. If you have questions about the project or material to contribute, contact me at kay@archive.org.
Editor’s Note - As always, see the DLARC Want List for Amateur Radio material that is known to have existed, but to date hasn’t been made available / donated to DLARC. For example, I hope to see the entire run of Digital Digest magazine in DLARC for my ongoing education of the history of Amateur Radio data communications.
The zBitx is path breaking 5 watts, 64-bit integrated SDR radio. It covers 80M to 10, on CW/SSB/AM/FreeDV/FT8/SSTV with a 480×320 touch screen. It measures just 6.5”x3”x1.5” and it can run off two LiPo batteries (battery case included in the cost).
Take it everywhere!
It measures 5.5 inches x 3 inches x 1.25 inches, 250 gms/9 ounces! The zBitx is so small, you can slip it into your pocket! Yet, it is capable of 101 watts of power from two standard 18650 batteries. The touch screen provides you with an on-screen keyboard for logging and CW operation even if you don’t have a CW paddle! Use the built-in mic for SSB operation. Work the world on FT8 without a computer from your window sill with your zBitx and a length of wire
All bands, All modes, All things
The zBitx will run every mode from CW to FT8 to FreeDV. With the built-in, N1MM style logger, macros, QSO recording and more, it is an integrated station that just works.
It gets better and better
The sBitx software that runs on the zBitx has the best-in-class open source software that keeps getting better all the time. With a large community of developers, hackers and experimenters working together, the zBitx never ages.
CW Deluxe
The zBitx is a CW dream machine for base station or field operations.
Operation is so pleasing with the ringless CW filtering down to 50 Hz. Without the noisy Transmit/Receive relays,
The on-screen keyboard with large keys on the 480×320 display makes typing CW a breeze.
Excellent, sensitive CW decoder
In-built, N1MM style logger exports to ADIF format
Editable CW macros
Integrated FT8
The zBitx is a complete FT8 station. Just switch it on and start working FT8! Forget about the mess of wires, audio level settings and confusing settings. Just tune to the FT8 frequencies and tap on the callsign to complete a QSO!
Voice Modes
SSB and AM modes are with integrated voice equalizer. Variable voice bandwidth makes operation fatigue free in noisy conditions
Preloaded Apps
The zBitx comes bundled with Fldigi, FreeDV, QSSTV. Any RigCtrl compatible, Linux software will work with the zBitx.
Everything is included:
Insert two 18650 LiPo batteries (not supplied) and you are ready to hit the field. At home plug in a 9v power supply and work it from your monitor/keyboard/mouse. It has an in-built microphone and a high quality speaker.
Remote into it with just the web-browser on your phone/tablet/laptop.
Specifications
Size: 156mm x 80mm x 35mm (including the battery case)
Weight: 415 grams including two LiPo batteries
Display: 480×320 resistive touch screen display with an independent
Preloaded Apps: FreeDV, QSSTV, Fldigi and more are coming
This unit… is amazing! Not just for the price, but for the overall functionality! Not stated in the above, but it’s built around a Raspberry Pi Zero (the specific variant isn’t mentioned). This radio is running 64-bit Linux! You can connect it to an external display, keyboard, pointing device, and probably Ethernet (via a USB to Ethernet adapter).
There’s more details about the zBitx in an announcement thread on the BITX20 email list in replies by HF Signals’ founder Ashhar Farhan VU2ESE. Some highlights that leaped out at me:
Deliveries start in February.
The last 4 years of experience with sBitx has shown that we have truly moved to being software defined. Most hacks are in software now. It then became imperative that software parts are easier to understand and to change.
512MB is enough for every conceivable linux software. There is nothing to be gained with even going from 1GB to 2 GB. The software resides on the SD card, not in the memory. Only the required software is brought into the RAM. None of our software is RAM intensive. Some like the FT8 are CPU intensive but it is well within the capability of all the Raspberry Pis.
I really love the idea of a portable HF radio small enough to slip into a jacket pocket, and a wire antenna and coax into the other pocket, that can run sophisticated data modes and optionally can connect to a tablet computer. And that it’s running 64-bit Linux… and upgrading it to new (software) capabilities is as easy as flashing a new MicroSD card and swapping it into the radio. And that, all in, it’s under $200.
I’ll be placing my order for a zBitx when ordering reopens in February.
Kudos to VU2ESE and the HF Signals team. This is incredible technological innovation in Amateur Radio!
Post Publication Update:
My thanks to Peter Li K6PLI for the extended email discussion about the zBitx, extending back to its first mention at the Four Days In May 2024 conference when VU2ESE first teased some details about it. K6PLI kept an eye on the zBitx development much more closely than I could.
In crowdfunding at Crowd Supply through 2025-01-30, but currently “1040% funded”, planned to ship 2025-04-15.
SignalSDR Pro combines portability and performance. With roughly the footprint of a credit card or a Raspberry Pi SBC, SignalSDR Pro is the perfect companion for anyone who needs powerful tools without the bulk. From signal processing and spectrum analysis to communication systems and beyond, SignalSDR Pro allows you to tackle complex SDR projects quickly.
Unmatched Compatibility & Software Support
With a simple change in jumper settings and a swap of the microSD card, SignalSDR Pro becomes fully compatible with leading SDR hardware like ADALM-PLUTO and USRP B210, among other examples, so it can be integrate seamlessly into existing workflows.
As for software, SignalSDR Pro operates smoothly with GNU Radio, MATLAB, LabView, DragonOS, LTE Sniffer, Open5GS, srsRAN, GPS-Sim-SDR, OpenBTS, GQRX, and other popular platforms…
(Promised) compatibility with GNU Radio for ease of experimentation
Frequency range encompasses five of the six popular Amateur Radio VHF / UHF bands (including 222-225 MHz in US and Canada),
It’s a transceiver with separate TX / RX ports and can operate full duplex,
Two transmitters and two receivers!
I saw this unit mentioned at the same time I was writing up my SuperPeater concept… and this unit, with two transmitters and two (wide band) receivers could potentially be the core of a SuperPeater with the additions of a transmit power amplifier(s) and of course, the (to be written) SuperPeater software.
Turn your Android phone into a modern ham radio transceiver. kv4p HT is an open source VHF radio that makes your phone capable of voice and text communication. The radio simply plugs into the USB C port on your Android smartphone and transforms it into a fully-fledged handheld radio transceiver. It’s completely open source. It’s small enough to fit in your pocket and take anywhere.
Again, this is a kit, and some components are optional / additional cost (including the radio module), and some assembly (soldering) is required. I’m sure there are other sources for this project’s components, but I’m highlighting this unit being available from Halibut Electronics because HE is a reliable vendor, motivated for customer satisfaction, and based in the US.
Kenwood 222-225 MHz Radios and Repeaters
As far as I could tell, these are new units - not used / refurbished / modified / surplus.
I may be one of the last to know this, but Kenwood manufactures radios and a repeater that operate in the US / Canada Amateur Radio 222-225 MHz band. I don’t remember where I saw mention of this, but such units are available for sale from RHE Communications Radio in Richmond (Vancouver), British Columbia, Canada. In their Fall 2024 “Hot-List”:
Kenwood TK-285 220MHz Portable 5W, 250CH Amateur-ized Portable, uses accessories common to TK-280/380/480
Kenwood TK-785-RPTR 220MHz 15W Repeater/Exciter assembled with rack mount, I/O connectors and modifications for repeater/duplex use
Confusingly, these units are not listed in the Winter 2025 version of the “Hot-List” that is currently online. Thus if you’re interested in these units, all I can suggest is to contact RHE at sales@rhecomm.com or by phone at 604-277-5020.
Our own Wiki instance is up and running with open registration. Please help us with the effort to improve M17-related documentation. The journey begins here!
All accounts have to be approved to receive editing privileges.
Emphasis on new, and equal emphasis on M17 Foundation. This wiki is under the stewardship of the new M17 Foundation. The previous M17 website, and the previous M17 Wiki, were not being maintained.
To request an editing account for the M17 Wiki, see the Request Account link in the upper right corner of the wiki.
I’ve been asked to help contribute content to M17 Foundation, Wiki, a News page, etc. which I will be honored to help with in the coming months.
I have just created a new repository for rewrite of D-Rats.
I think this re-write is needed for several reasons.
Most of D-rats users are using Microsoft Windows and the use of GTK+ makes it hard to provide an easy to install package.
GTK+ is continuing to make incompatible changes with new versions making it harder make enhancements. The Glade editor for designing GTK+ layouts actually making things harder as it does not seem to be keeping up with GTK.
The config subsystem needs a rewrite to fix existing problems and requested features, the existing code structure makes that very difficult.
It may be a while before I get something ready for testing, and most of those tests will be of the "hello world" type packages at first just to make sure that everything can install and run.
As this will be being brought up in sections, hopefully it will help someone learn programming and packaging processes.
The original project was called D-RATS, but WB8TYW chose the name DRATS2 for this project. D-RATS is software / protocol to take full advantage of the 900 bps data channel (streaming, no framing, no error correction, etc.) that’s built into all D-Star radios. The name D-RATS is wordplay on the name D-STAR. While D-RATS was an entirely independent development originally by Dan Smith KK7DS, it was promoted by Icom because D-RATS enabled data communications on D-Star radios (and repeaters) somewhat equivalent to packet radio.
While there are only a few Icom D-Star radios that implement the “DV Fast Data” mode2, hopefully DRATS2 can take advantage of DV Fast Data mode in those few Icom D-Star radios to do a 4500 bps data stream versus the original 900 bps data stream.
I know this will not come as an easy pill to swallow for most people who come across this blog post. I implore you to read with an open mind. Hear me out and then build your argument in the comment section. This post is an effort to help guide those who may be looking into packet radio, to help steer them into the direction of the future. Hardware TNCs are an aspect of packet radio that people can’t just let go. While they can certainty be used, there is almost no reason to get one today with the software options that are available. There are a few exceptions we’ll get into. Let’s start off by talking about the reason for their existence.
In addition to his Modern Ham Blog, KN4MKB is the creator of the Modern Ham YouTube channel (also Zero Retries Interesting).
Overall this article is an excellent treatment of the advantages of “Software TNCs”3 (which is kind of a contradiction in terms) versus (legacy) Hardware TNCs.
KN4MKB has been doing a great job of explaining Packet Radio in this era with solid, well-explained hands-on experiences in his series Packet Radio 101.
I have two minor quibbles with the article. The first is the origin of the “TNC” which is an acronym for Terminal Node Controller. When Amateur Radio Packet Radio was first being developed in approximately 1978, “dumb terminals” were the primary display and input devices for any digital system. At that time, microcomputers existed (the MITS Altair debuted in January 1975), but cost thousands of dollars (for a realistically usable unit). Dumb (video) terminals were available surplus for a few hundred dollars. Thus for Amateur Radio Packet Radio, all of the networking, protocols, modem, user interface, etc. was incorporated into a standalone unit - the TNC. Of course, within a few years, inexpensive consumer computers became available, and those became the preferred display / input device for Amateur Radio Packet Radio. Another reason for the name Terminal Node Controller was to distinguish it from the “in development, available real soon now” (but never quite happened) Network Node Controller (NNC)… which is another story for an another time.
My second minor quibble with this article is the section Some Exceptions. In addition to some specific uses cases for the NinoTNC and the “mobilinkd” (that’s actually the company name; the actual current product is called the TNC4) hardware TNCs, I would add the venerable Kantronics KPC-3+ for the specific application of a standalone, remote APRS digipeater.
That the KPC-3+ is an old design is, in that specific application, makes it a solid choice. The KPC-3+ has been refined over a couple of decades now, especially its firmware, and is a solid, reliable unit for standalone, remote applications to provide an APRS digipeater.
And… a very, very minor quibble, that’s admittedly pretty “deep in the weeds” of terminology and Amateur Radio Packet Radio technology is that modern “TNCs” are all KISS TNCs and are built around modern microcontrollers which are capable of easily being updated and their capabilities expanded, such as been the case with the NinoTNC that has is in a state of continual evolution4. The use of the KISS protocol for communicating between the TNC and the host computer means that “most of the intelligence” of the TNC resides in an application running on the host computer, not the TNC itself, as was the case with legacy hardware TNCs (such as the KPC-3+… though that unit does have the ability to be used as a KISS device).
For those quibbles, I don’t fault KN4MKB for that lack of context. For a long time, a lot of Packet Radio history had lapsed into tribal knowledge, with only scattered historical packet radio information available online. Fortunately, that’s begun to change with the advent of the Digital Library of Amateur Radio & Communications, and the availability of material like the Vancouver Amateur Digital Communications Group’s newsletter “The Packet” and the first book published on Amateur Radio Packet Radio in 1981 - PACKET RADIO by Robert Rouleau VE2PY and Ian Hodgson VE2BEN.
I stumbled upon this interesting, deep, scholarly examination of the vagaries of APRS by Kenneth Finnegan W6KWF as his 2014 MSEE thesis.
The Automatic Packet Reporting System (APRS) is an amateur radio packet network that has evolved over the last several decades in tandem with, and then arguably beyond, the lifetime of other VHF/UHF amateur packet networks, to the point where it is one of very few packet networks left on the amateur VHF/UHF bands. This is proving to be problematic due to the loss of institutional knowledge as older amateur radio operators who designed and built APRS and other AX.25-based packet networks abandon the hobby or pass away. The purpose of this document is to collect and curate a sufficient body of knowledge to ensure the continued usefulness of the APRS network, and re-examining the engineering decisions made during the network’s evolution to look for possible improvements and identify deficiencies in documentation of the existing network.
This might be newly relevant for the new effort underway in APRSF to update APRS standards, protocol, etc.
John Langner WB2OSZ replied:
Thank you bringing this to our attention.
Kenneth was absolutely correct in his assessment of the problem. Unfortunately, he made many mistakes in collecting and curating some of the institutional knowledge. The result could be spreading misinformation which others will then propagate. I would like to offer some corrections.
mistakes in collecting and curating some of the institutional knowledge
in 2014. There were then, and now, widely varying implementations of APRS; for example, Amateur Radio APRS operating on the LoRa Chirp Spread Spectrum modulation. The APRS documentation / specifications then available were (in my opinion)… “eclectic and fragmented”. In my opinion, correcting that situation is one of the prime and most immediate tasks of the APRS Foundation - to create an up to date APRS Protocol Specification incorporating all the proposed changes / additions / corrections proposed (and or widely agreed upon) since the previous formal APRS Protocol Specification that was created by TAPR.
Continuing the discussion on the APRS Foundation email list, WB2OSZ said:
The APRS Protocol Reference, affectionately known as APRS101.pdf, is from a quarter century ago. Bob WB4APR (SK) collected voluminous notes about corrections, clarifications, and new features for over 20 years. Unfortunately these were not merged into the original, making it very difficult for developers. I've conversed with multiple developers than didn't even know there were later updates. It is very important that all developers are working from the same specification so that all implementations will interoperate with each other.
My own personal, unofficial, compilation of the original and decades of updates can be found [at]
The expectation is for the APRS Foundation to become the new custodian for the "official" version of the standard.
This is the kind of detailed discussion about sorting out lingering ambiguities in APRS that I hope the APRS Foundation will tackle to move APRS forward into the late 2020s.
Kudos to W6KWF for tackling this as a Master’s Thesis - another example of radio technology technological innovation occurring in Amateur Radio.
And kudos to WB2OSZ for his solo (as far as I can tell) work on pulling together all the disparate bits from a quarter century (?!?!?!) of evolution of APRS into what will hopefully become the APRS Specification v1.2, and that that updated specification will soon be formally within the custody of the APRS Foundation (currently it’s in the custody of TAPR). And, of course, be more regularly updated.
Followup to Zero Retries Mention of TEXNET - GLnet (Great Lakes Network)
That article was mentioned on the TAPR xNOS email list, and Jay Nugent WB8TK posted a great followup about GLnet, a network in the midwest US that used TEXNET nodes.
I was a (distant) member of the Texas Packet Radio Society TPRS, living in Michigan but commuting each year to their annual meeting in Texas. It was always the weekend before or the weekend after the TAPR meeting in Tucson, so it was a fun WEEK for me hitting each organizations annual meeting!
Along with several others, we ran the "GLnet" (Great Lakes Net) network of TexNet nodes throughout Michigan, Indiana, a bit of Ohio and a bit of Illinois. They were linked together at 9600 baud using old UHF RCA radios, and one 6-meter link (that was always so-so depending upon the time of day).
I still have *several* TexNet nodes stacked up in my basement. They were Z80 based with one 9800 modem and two 1200 baud modems on a single PC board. It was designed and coded by the "Tom Tom" team. One "Tom" designed the hardware and the other "Tom" coded ALL of the AX.25, memory management, timing, and PMS (Packet Mail Server) code in Z80 Assembly! The code was burned onto an EPROM, including any configuration information - so it wasn't for the faint of heart. I still have the source code somewhere in my archives.
The user interface was SO incredibly easy for the users to connect to any station at any node with a single command. There were also Sysop commands (password protected) that allowed for diagnostics and remote reboots, and PMS message management.
The 'networking' code was build around a MESH model where they automatically detected one another and set up Primary, Secondary, and Tertiary route tables. So should a link go down or become congested, packets would take alternate routes to their destinations. This was FAR more efficient and much faster than anything Software-2000 put out with their NetROM offering.
Any node could have a hard drive attached and serve as a "PMS" packet mail server. There was NO NEED to do Heirarchical mail forwarding as you simply used the network to get to the PMS, wherever it was, and read/post email and bulletins.
One serial port on a TexNet board could be assigned to watch the NWS weather teletype wire. It would store select, pre-determined, weather PRODUCTS to SPECIFIC message numbers on the PMS hard disk.
The Tom-Tom team knew what they were doing and were FAR ahead of their time! Makes me want to fire up a couple of those nodes and refresh a few crusty brain cells remembering the past :)
I’m kind of bummed to read that GLnet extended into Ohio and I missed participating in that as an advanced packet radio network. But perhaps GLnet developed after my time living in the Cleveland, Ohio area (1984 through 1987) and then moved to the Seattle, Washington area. I got to know some of the folks that developed TEXNET and I agree with WB8TK that TEXNET was way ahead of its time. I’m delighted that such a thorough explanation of it survived (the Ham Radio series) and perhaps some of the best of TEXNET could be incorporated into a future Amateur Radio network system - it’s all just software now… right?
Post Publication Update:
Tom McDermott N5EG followed up on the mention of TEXNET in an email:
Also - you mentioned TEXNET in the same issue. The two Tom's that are described were:
1. Tom Aschenbrenner (then WB5PUC, now WA9EXS) who wrote the NCP (node) software (Z80 assembly), and
2. myself (the other Tom) who did the hardware, Layer 3 routing protocols, the network management system, and the automatic AMTOR bulletin data.
We had a contiguous system from northern Mexico through Texas, Louisiana, Oklahoma, Arkansas, and Missouri all linked with 9600-baud 70cm radio links. It provided DXcluster linkage for many clusters before the internet.
Texnet had network-wide (redundant) BBSes where you could log into any node and just type BBS and you would be automatically linked to the nearest reachable BBS. The system automatically received AMTOR W1AW bulletins on 20m and put them on the BBS without human intervention. The system kept track of the number of AMTOR character errors in each bulletin, and as propagation provided a better version at certain times of day, the BBS would auto replace a lower-quality (high character error count) bulletin with one that had a higher quality (lower number of character errors). So within about 24 hours there were usually zero-character-error versions for all the bulletins on the network BBSes. It used the old Technical Material Corp (TMC) crystal-controlled single channel SSB 1U-rack receivers.
It had a full graphical network management system, with mouse-click display of link status, node parameters, etc. It was possible to display full network statistics from the GUI. That was pretty cool in the 1980's. It was connected to the National Weather Service office in Tulsa, and forwarded the old ASCII-encoded doppler weather maps anywhere in the network.
You had to have an offline map background on each client computer (due to the otherwise large number of bytes) but the NWS ASCII would draw the weather features onto that map in real time - that data was only about 1kB or so.
The maps were pretty coarse by today's standards.
My thanks to N5EG for that additional context on TEXNET!
Today marks the 15th year since APRSdroid began. Thanks for DO1GL for creating such a wonderful app, as well as all those who have contributed to it!
As a birthday present, I have a major release today with many enhancements, and one complete overhaul of offline mapping! Feel free to grab this birthday release!
APRSdroid is an Android application for Amateur Radio operators. It allows reporting your position to the APRS (Automatic Packet Reporting System) network, displaying of nearby amateur radio stations and the exchange of APRS messages.
APRSdroid is Open Source Software written in Scala and licensed under the GPLv2.
Features
You can use APRSdroid to connect to the APRS network via different means:
APRS-IS via Internet (WiFi or mobile data connection)
AFSK (audio connection between your radio and the smartphone)
Once connected, you can beacon your presence, see which stations (amateurs and repeaters) are around and send/receive APRS messages.
This isn’t just impressive for the new, updated features, but for the stability and longevity of APRSdroid as the APRS app for Android devices. I’m primarily an IOS device user (iPhone, iPad) and even I’m well aware, from long reputation, of APRSdroid.
Kudos to DO1GL and NA7Q for this new APRSdroid version, and the longevity of APRSdroid. An app doesn’t live a useful life for this long without careful design and patient maintenance to deal with continual changes and updates to platform.
David Rowe VK5DGR on the ARDC Community email list:
We are looking for people to join our Project Leadership Team (PLT). The attached document explains what we are a looking for.
Please feel free to forward this to any people you think might be interested, or good candidates for the FreeDV PLT, however we would prefer the document is not placed on any public web sites or mailing lists.
The FreeDV project is looking for new members for our Project Leadership team.
FreeDV is at an inflection point. After two years of R&D (kindly supported by an ARDC grant) our new RADE technology has demonstrated HF digital voice performance highly competitive with SSB over HF radio at a range of SNRs. In VHF/UHF applications Codec 2 is a viable replacement for close source codecs (M17). There is a growing community of Radio Amateurs using RADE every day. After a quarter of a century of being tied to closed source vocoders, the Amateur radio and commercial communities are attracted to open source vocoders for next generation radio systems.
…
To achieve our goals we need to expand our leadership team (PLT):
Help us manage the project, for example discuss and set goals for the project,
approval of expenditure, best way to direct resources.
Time commitments are a 1 hour Google meeting, and a few hours of email every month.
You can leave at any time with 30 days notice.
It is an unpaid (volunteer) position.
Being on the committee does not imply you need to work on any other activity on the project (e.g. coding or promotional tasks) - unless you want to.
We are particularly interested in people with any of these skills/attributes:
People that live outside of North America, e.g. in Asia or Europe, that are comfortable with English language Google meetings and email. We’d like to represent all Hams in the world!
Radio sales and marketing experience, strong people skills, to help us bring RADE technology to Hams of the world, and work with radio manufacturers.
Project management experience to help us manage our grant.
Writing skills, comfortable in Google docs.
Radio, signal processing, or software development professionals to assist with technical mentoring/review.
In addition to the PLT role, enough time and motivation to get "hands on", and complement/assist the current developers, e.g. in marketing, conference attendance, website content, posting to social media, signal processing review (in a paid or volunteer role).
If you believe in what we are doing, and would like to help - please reach out to us on freedv-project-leadership-team@googlegroups.com and tell us a little about yourself.
FreeDV (and the earlier, related development of the free, open source Codec 2), is a signature achievement of Technological Innovation in Amateur Radio. If you have some of the skills that are requested, this is a great opportunity to materially contribute to Amateur Radio’s future.
Interesting discussion thread on Reddit r/amateurradio:
I want to talk and learn. I want to bust through the ham stagnation/segmentation of spendy vendor-specific solutions and try something new. M17 checks the boxes, but I'm a total noob in this space. What I have gleaned so far from other threads and sites:
We can buy a CS7000 HT with M17 support or modify hardware like the TYT MD380. Are there other HT's that noobs should be looking at with full support to get started?
Are Handsets that run OpenRTX and M17 the only way forward? Are there other ways or cross-mode methods to use M17? For example are there MMDVM bridges that can connect DMR/YSF/D* etc to M17?
Similar to the above question, I think I saw that DVSwitch could support USRP2M17? Does this require a specific hotspot or does it give analog guys like me a path?
It's no fun if we can't talk. What's the best active channel/TalkGroup/Reflector to use once we get there?
Anyone else want to join/help/guide us on this endeavor? TIA
I particularly enjoyed the comments of grouchy_ham:
One of, maybe even the biggest, roadblock is repeaters. The usefulness of V/UHF radios is massively increased by repeaters. Without repeaters capable of use with a new protocol, it’s a really tough sell. Why would I, as a repeater owner (if that were the case) be interested in “upgrading” my system to accommodate a new protocol that may or may not take off?
As an end user, why would I buy a radio, especially an HT, with a digital protocol that isn’t supported by a local repeater or preferably, a network of repeaters, that it can be utilized with? I have a D-Star capable radio in an area without a single D-Star repeater in range. Thankfully, D-Star is not why I bought the radio.
Yep! grumpy_ham’s perspective supports the concept of a SuperPeater, which will support M17 as the primary digital voice mode.
Peter Marks VK3TPM on his marxy's musing on technology blog:
I'm sure [VarAC] works well as there are enthusiastic users but it seems to me that it's a proprietary version of an OFDM modem hosting a proprietary chat protocol. Also, VARA only runs on a proprietary commercial operating system from Microsoft.
The authors are clearly in this to make money, for example an alert is shown every time I do anything asking me to either transfer 68 euros or "continue evaluating" it. I pushed the Tune button in VARAC and it shows an alert saying that to Tune you must pay.
This all seems to go against the open philosophy of amateur radio.
First, VK3TPM makes a fundamental mistake in the premise of this article, conflating VarAC with VARA. The former is a sophisticated chat / email (and many other features) application by Irad Deutsch 4Z1AC that runs on the VARA modem platform developed by Jose Alberto Nieto Ros EA5HVK. Note that EA5HVK also offers applications equivalent to VarAC - VARA Chat and VARA Terminal.
Thus, any discussion about the “legality” of the usage of “VarAC” on Amateur Radio bands should be directed toward VARA as that is the system that actually transmits on Amateur Radio spectrum. VarAC (and VARA Chat and VARA Terminal) is an application that “rides on top of VARA”.
This “issue” of “proprietary” modes / software / operating systems used on Amateur Radio going against the “open philosophy” of Amateur Radio flares up every so often. Such discussions seem to quickly subside when it’s pointed out that there are many “proprietary” technologies widely in use in Amateur Radio, including all the digital voice modes that use the proprietary DVSI (AMBE) CODEC (DMR, D-Star, System Fusion, etc.), data modems such as Pactor 4, and even the wide use of LoRa which is a proprietary implementation of Chirp Spread Spectrum. All of these systems are used widely in Amateur Radio. In my interpretation, as long as such systems are widely available for purchase and use, enabling easy monitoring / participation of communications on Amateur Radio spectrum, it seems a hard case to make that they should be considered illegal, or implementations of “encryption”.
I, for one, am glad that these proprietary systems are in use in Amateur Radio as they provide an example of what’s possible to accomplish in Amateur Radio:
The digital voice modes that use the proprietary DVSI (AMBE) CODEC have proven the utility of digital voice in Amateur Radio VHF / UHF bands. Those systems gave rise to M17 as an open source equivalent system developed within Amateur Radio, for Amateur Radio that is now gaining significant traction, such as one (and soon, more) radio that incorporates M17 (not requiring modification).
Pactor 4 is a proprietary data mode for HF that provides up to 10.5 kbps data rate in a 2.4 kHz channel. That’s a benchmark that can be aspired to by open source developers. For example, VARA HF (software only, using existing audio interfaces, running on a Windows PC), achieves 6.7 kbps in a 2.4 kHz channel… which has given rise to an open source equivalent of VARA HF called Rhizomatica Mercury which also achieves 6.7 kbps in a standard HF channel.
VARA FM is capable of up to 25 kbps in a standard VHF / UHF FM channel, using a Windows computer, a high bandwidth audio interface, and a radio with a flat audio connection (bypasses the pre-emphasis / de-emphasis stages). Even using microphone and speaker connections on a standard FM radio, VARA FM can achieve nearly 13 kbps and most notably, VARA FM can auto-negotiate a connection between a fast (“wide”) VARA FM station and a slow (“narrow”) VARA FM station. The equivalent in (non-proprietary) packet radio of sharing a channel between 1200 bps and 9600 bps stations simply isn’t possible as there is no negotiation between a 1200 bps and a 9600 bps station.
The example of VARA FM’s speed and reliability (using OFDM techniques, Forward Error Correction - FEC, channel sounding, negotiation of best common speeds, etc.) have revitalized the use of data communications on Amateur Radio VHF / UHF, with up to nearly 21x the usual 1200 bps data rate (and error prone due to no FEC). But some progress is being made to develop non-proprietary systems such as MMDVM-TNC which implements various speed tiers from 9600 bps up to 38400 bps5 with integral Forward Error Correction.
LoRa is a proprietary implementation of Chirp Spread Spectrum. LoRa is extremely popular because its developer, Semtech, has made LoRa (radio) modules very inexpensive, enabling many new use cases such as Meshtastic. In the US, LoRa is widely usable by hobbyists because it is implemented for the license-exempt 902-928 MHz band. Because 433 MHz is a license-exempt portion of spectrum in Europe, LoRa can be used within the Amateur Radio 420-450 MHz band in the US. In using LoRa, spread spectrum technology is finally becoming widely used in Amateur Radio. As discussed in Zero Retries 0113 - LoRa Implemented in GNU Radio Environment, the proven utility of LoRa has given rise to an open source implementation of LoRa within the GNU Radio Environment.
Recall that UNIX and DOS and Windows were / are proprietary computer operating systems, wholly owned by various corporations, but those examples gave rise to open source operating systems such as BSD, Minix, and Linux.
Thus I posit, that proprietary systems in Amateur Radio are useful in showcasing how much can be accomplished in Amateur Radio and thus inspiring those that are so inclined, and capable, to create alternatives to proprietary systems, perhaps open source alternatives.
And, if the proprietary systems persist indefinitely, like DMR is likely to for VHF / UHF repeaters… lets just enjoy and use our amazing capabilities that are possible within Amateur Radio, proprietary systems, or open source systems.
John Desmond EI7GL on his EI7GL....A diary of amateur radio activity blog:
Rattlegram is an app for a smartphone and it allows users to send short text messages over the radio. The beauty of the app is its simplicity. There is no need for wires or interfaces, the user just needs to hold their smartphone next to the microphone and loudspeaker of their radio.
The burst of data from the Rattlegram app only lasts for about two seconds. It's really simple to use. You just compile a short message on the app, press PTT on the radio and tell the other person you're sending a message, hold the microphone of the radio next to the smartphone and press 'TRANSMIT' on the app. The person on the receiving end gets the error free message on their app a second or two later.
Good to see Rattlegram get some attention / activity. Rattlegram is the “beta” implementation of the Ribbit project.
In saying:
I get the feeling that Rattlegram is a bit like a solution looking for a problem. It's a tool that I'm sure some resourceful operators will find a use for.
I don’t think EI7GL quite understands the intended use case for Rattlegram / Ribbit… which was not intended for Amateur Radio (though Amateur Radio isn’t precluded from using it).
Rattlegram / Ribbit is designed for individuals that have access to portable radios (and mobile phones) to send and receive text messages off-grid via personal portable radios. No built-in data communications hardware or software in the portable radios is required (though it would be cool to see if Ribbit / Rattlegram could be adapted to use some of the new Bluetooth linking available in the newest portable radios). The use case of Rattlegram / Ribbit is short messages via personal communications (voice) radios such as:
Family Radio Service (FRS)
PMR446 (Europe)
Citizens Band (should work great with FM now enabled in US Citizens Band)
Multi Use Radio Service (MURS)
Maybe even General Mobile Radio Service (GMRS)
To proactively address the plaint that data / messaging is prohibited / restricted on these radio services / devices… how can it be prevented / regulated against when you’re just transmitting audio tones acoustically between a mobile phone and a portable radio - not even connecting via external microphone / speaker connection?
I’ve made the case that while there are various personal radio services available for voice communications… there is no Citizens Data Radio Service6 available… but there should be. This is the 21st century where text messaging is more prevalent than voice phone calls.
Radio spectrum regulators should really catch up with this trend of the past 25 years, and thus I applaud the developers of Ribbit / Rattlegram for addressing this use case.
I hope that N5EG will proceed on in this series to setting up the ka9q-web variant of ka9q-radio.
Post publication update per N5EG:
Part 5 does actually discuss setting up ka9q-web plus ka9q-radio to provide a fully functional spectrum server.
reachable over the LAN network using http.
Kudos to N5EG for creating this series!
Bald Yak Education Series (on GNU Radio)
Speaking of step by step education on a Zero Retries Interesting topic…
Onno Benschop VK6FLAB has begun a series he’s simply called Bald Yak7 (which I find hilarious) on his weekly podcast Foundations of Amateur Radio. Delightfully, for me, VK6FLAB makes each podcast available as full text, though VK6FLAB admirably keeps his podcast audio short and well-organized and thus easy to listen to.
TL:DR - The Bald Yak series is a tutorial about, in the end, learning to use GNU Radio.
In the process of developing something from scratch there are a great number of things that need doing. When you start it's unclear what's the most important thing, but experience has told me that starting, anywhere, is the best way to get runs on the board.
Here's a smattering of what I'm talking about. What do we call this thing? How will we license it? What does it do? How will we determine what is required and what is nice to have? How will we avoid reinventing the wheel and how will we make sure that it's something that people want, rather than yet another solution looking for a problem?
I started by looking at what else is going on. Specifically, the Software Defined Radio or SDR world isn't something that arrived yesterday. There's lots of stuff around and plenty of it is open source, so we can look inside and learn.
I asked around to see if there was a table that compares how the various SDR tools talk to the world, or rather what protocol they use. Think about how you'd get the data from a radio to a computer and how you'd control the radio and the data flow. Now imagine that neither are in the same room, or even in the same country. I started writing down what I think is needed, and then realised that this replicates stuff that has already been done. Tools like rtl_sdr, soapy, OpenHPSDR and spyserver already do some or all of this, there are others. Thus the request for the table.
This resulted in no table, but plenty of questions, including a discussion about protocols versus drivers, which lead me to the realisation that I'm going to be doing a lot of yak shaving before this project has anything to show for itself.
This neatly prompted the idea that by the time I was done, the yak was going to be well and truly shaved and now the project has a name, "Bald Yak".
I confess I haven’t read the entire series, but the subtitle of “Scene 6” intrigued me so I scanned it and I’ll offer this snippet:
GNU Radio is a complex beast. The latest release has 5,570 files, making nearly 80,000 lines of source and related code. The git repository shows 579 authors and I will point out that it's likely there are more, since the project was first released in 2001, but the git repository only goes back to 2006.
Said differently this is a big project that nobody is likely to hold entirely inside their brain. It means that things change without everyone involved knowing about it. I'm raising this because we're diving into a complex environment that we're using to build ourselves a new thing.
At this point you might want to run for the hills. I understand.
VK6FLAB is an artist with words, and he cuts through the felgerkarb of the reverence of GNU Radio… which makes me admire his work even more. If I’m ever going to actually use GNU Radio (and I have not, to date) it will be thanks to courageous folks like VK6FLAB who waded deep into GNU Radio and reported back with great skill to educate the rest of us poor schlubs who don’t live in the bowels of software defined radio code.
Speaking of GNU Radio, I found this when doing a brief visit to its website for the previous article. From the GNU Radio website News section:
FOSDEM
Stop by our booth!
GRCon25 Announcement
We are very close to announcing our location for GRCon25 - so please start thinking about the work you want to come present this coming year
Native Installers
This has been in the works as part of the ARDC grant, but we hope to make the end result of this public very soon
New Developments, OOTs, Academic Research, etc
The great thing about an open source project and ecosystem is that we don’t know what types of project will transpire in the community. We love to hear how GNU Radio is being used, OOTs that have been developed, and look forward to all the incredible work in the ecosystem in 2025 that can be used to enable innovation in scientific applications
GR4 Advancement
GR4 has made great progress the last couple of years especially in its use at FAIR, but in 2025 we hope to continue adoption into the broader community.
It has been fairly quiet in Architecture Working Group, but we met one last time in 2024 very productively - prioritizing features that we should pursue in the near term, and are planning to have a standing monthly meeting to maintain consistency
wsjt-x_improved is an enhanced version ("the DG2YCB edition") of the excellent WSJT-X software by Joe Taylor K1JT, Steve Franke K9AN, Bill Somerville G4WJS, me and others (https://sourceforge.net/projects/wsjt/). Sometimes, however, even good things can be improved …
Notes: wsjt-x_improved is experimental and is licensed under GNU GPL v3 (https://www.gnu.org/licenses/gpl-3.0.txt). I am not aware of any adverse effects. However, use it at your own risk!
(A subset of the full feature set of wsjtx_improved follows.)
Available with 3 different GUIs: WSJT-X's standard GUI, an alternative layout ("AL") and a widescreen version. The latter two provide a larger Band Activity window. "AL" is optimized for small screens and laptops.
Mode buttons make it easy to switch between the frequently used modes (useful when menus are hidden). For Hound mode, simply set your rig's VFO to the correct DXp frequency. When you hear the fox, just press the "H" button and make your QSO. Press the "H" button again to return to normal FT8 mode.
Band Hopping for FT8, FT4, Q65 and MSK144! A new Tab has checkboxes for the most important frequencies. Just select the bands/modes you want and push the "Band Hopping" button. Automatic band hopping takes place every other full minute. (Very useful together with PSKReporter.)
Full Duplex Mode (useful when working via satellite)
Read and display PWR and SWR values during transmission.
Stop TX automatically if SWR > 2.5.
New: Band select buttons.
A few pretty cool additions!
New Developments in Personal Compute Capabilities - Opposite Ends
These two developments aren’t exactly related directly to Amateur Radio, but I think that they’re “tools” which can be applied to radio technology. Really - in this era, radios are computers - with antennas… and those computers are getting more powerful (and capable, and usable, seemingly by the day). Thus the potential improvements in radio technology increase in potential in lockstep with compute capabilities.
The first such development this week is the announcement of the Raspberry Pi 5 with 16 GB of RAM for $120. Previously the maximum RAM available on a Raspberry Pi (5) was 8 GB. I don’t know if applications in Amateur Radio can take advantage of that additional 8 GB… but I bet there are some, such as ka9q-radio, and perhaps some artificial intelligence / machine learning applications. The 16 GB variant is slightly faster than the 8 GB version because of minor process (die change) optimizations. There was no corresponding announcement of 16 GB versions of the Raspberry Pi Compute Module 5, or the Raspberry Pi 500, but I’ll guess that those will emerge soon.
Yes, there’s an argument to be made that inexpensive Windows / X86 appliances are a “better deal” than high end Raspberry Pi units such as the Raspberry Pi 5, but I posit that the Raspberry Pi ecosystem, the hardware expandability, the “built from scratch for Linux”, and the well-supported Raspberry Pi OS tips the scales, for me, to use Raspberry Pi units for Amateur Radio use whenever Windows isn’t required.
The second development of note this week for Personal Compute Capabilities is NVIDIA Project DIGITS:
… a personal AI supercomputer that provides AI researchers, data scientists and students worldwide with access to the power of the NVIDIA Grace Blackwell platform.
Project DIGITS features the new NVIDIA GB10 Grace Blackwell Superchip, offering a petaflop of AI computing performance for prototyping, fine-tuning and running large AI models.
With Project DIGITS, users can develop and run inference on models using their own desktop system, then seamlessly deploy the models on accelerated cloud or data center infrastructure.
“AI will be mainstream in every application for every industry. With Project DIGITS, the Grace Blackwell Superchip comes to millions of developers,” said Jensen Huang, founder and CEO of NVIDIA. “Placing an AI supercomputer on the desks of every data scientist, AI researcher and student empowers them to engage and shape the age of AI.”
One… petaflop… on a desktop, with up to 128 GB of RAM, powered by a typical AC power outlet (and ambient temperature air), capable of running NVIDIA’s AI software, for a starting price of US$3000.
Or, if that’s a bit too high end, in mid-December, NVIDIA announced its Jetson Orin Nano Super Developer Kit - for $249. It looks like a beefy Raspberry Pi!
The NVIDIA Jetson Orin Nano™ Super Developer Kit is a compact, yet powerful computer that redefines generative AI for small edge devices. It delivers up to 67 TOPS of AI performance—a 1.7X improvement over its predecessor—to seamlessly run the most popular generative AI models, like vision transformers, large language models, vision-language models, and more. At just $249, it provides developers, students, and makers with the most affordable and accessible platform with the support of the NVIDIA AI software and a broad AI software ecosystem. Existing Jetson Orin Nano Developer Kit users can experience this performance boost with just a software upgrade, so everyone can now unlock new possibilities with generative AI.
I don’t know what can be done with all this compute capability… but we’ll do something! I think this might be a fun (fantasy) core to my SuperPeater concept. But a bit more real world, here are just two examples from my personal experience…
Orthogonal Frequency Division Multiplexing (OFDM) was developed more than a decade before it was first deployed for real use in radio systems. But when it was developed, it required a computer as capable as a DEC VAX to do the complex calculations necessary. Within that decade, such calculations could be done on a chipset. Use of OFDM has changed the world of radio communications.
The Starlink antenna that I’m using to connect to the Internet and edit these words on a Substack server in a web browser works as well as it does only because it incorporates a phased array antenna to track the path of a Starlink satellite in Low Earth Orbit - with no moving parts. (The motors in my Starlink antenna only position the antenna initially for the most optimal part of the sky with the most satellites in view. Newer Starlink antennas don’t even have motors.) As far as I’m aware, that Starlink phased array antenna is the first use of phased array antenna technology that’s cost effective enough to be purchased by a consumer. Doing so required huge computational power, that had to be made “consumer affordable”.
It’s easy for me to recall when “workstations” were similarly highly optimized for various specialized workloads, networking, with customized software, and sold for very high prices. Within a few years, those same workloads were being run on “slightly better than commodity” personal computers at a tenth of the price of the workstations.
Here’s one last thought from the previous articles in this issue… imagine someone like me who “knows enough radio technology to be dangerous” with a Project DIGITS unit on my desktop. The unit is loaded with a generative AI “engine”… and everything I can find related to GNU Radio. Then I start “explaining” to the AI how a new radio system that I want to develop “should” work, and that I want the AI to create new code for GNU Radio to accomplish that. Then, that code gets downloaded into a Software Defined Transceiver that supports GNU Radio. I used to joke that “it’s a simple matter of software”. It may soon be “a simple matter of a good idea, and enough background material for an AI to help you”.
Feedback on SuperPeater from the Perspective of AllStarLink
I was corresponding with David Gleason NR9V regarding one of his products and to my delight, he’s a reader of Zero Retries and had some substantive thoughts on my SuperPeater concept. He agreed to let me share his thoughts from his email.
BTW was just reading your newsletter, and was great to see your discussion of data over repeaters, and your mentions of cross-band repeaters and of Phil KA9Q (who's a couple miles away from me, though I've never met him). There are indeed quite a lot of underutilized repeaters and it would be great to do something truly innovative with all that bandwidth, that retains all the original functionality and level of audio quality while adding significant new features. I wrote the following on my QRZ page a couple years ago:
To sum things up, I'm not a fan of low-bitrate digital modes. They can give better audio quality in limited circumstances ... but the majority of the time the audio is not as good as analog FM or AllStar and is often much worse. Hopefully someday a new digital mode will be adopted by hams that actually has the same or better quality than analog – which could be done by combining analog FM with a digital subcarrier / separate channel providing audio enhancement / error correction features while having real analog as a fallback.
There is plenty of unused bandwidth on VHF & UHF and no reason we couldn't do standard 5KHz-deviation analog FM with a ~9600bps digital subcarrier / separate channel. This would provide 2 redundant audio streams and essentially twice the resistance to noise. This would guarantee that audio quality would never be significantly lower than analog while providing the benefits of digital and being backwards compatible with existing analog radios.
...People have a misconception that OTA digital modulation needs to be narrow-band, which may be true in some cases, but is not true on the VHF & UHF ham bands, where we have 10+ MHz of space but rarely more than a couple dozen repeaters active at any one time in one area. And in non-ham spectrum we have GHz of spectrum. 1 GHz of spectrum divided into 50KHz channels could accommodate 20,000 Hi-Def Analog + 9600bps Digital channels per metro area... Once we can start to take the approach of improving audio quality and functionality rather than reducing it or thinking we have to stay in some arbitrarily small bandwidth, there can be a real future for digital where it can sound as good or better than analog while providing added features.
In addition, I'm a big fan of Full-Duplex communication, and of ASL and its extensive features and full-duplex support. From myAllStar How-To Guide -Full-Duplex Communication Benefits:
...FM sounds better than AM because of its better noise resistance, but it is less energy efficient than SSB due to having a constant power regardless of modulation level. And unlike SSB where you can unkey briefly with no audible effect, if you unkey on FM it results in squelch drops for listeners (unless their radio has unusually good squelch or they have tone squelch properly set up), thus there is a slight disincentive on FM to pay attention to the channel while you're transmitting.
Due to the FM capture effect, multiple people can't transmit at the same time or the signals interfere destructively or one covers up the other. With SSB that's not an issue and multiple signals combine linearly. One might be louder than the other or you might not be able to follow what either is saying very well but at least you'll be able to tell that there are 2 people talking, vs. FM doubling which can sound like a train wreck. Thus when FM first started being used on repeaters 60+ years ago it sounded great but also had some limitations that earlier modes did not.
...repeaters don't need to only use FM (or PSK digital equivalents). They could also support SSB without a huge amount of effort. Squelch would be a little more complicated because you don't have a constant carrier to reference, but DSP techniques have come a long way since the days of the first FM repeaters. It would not be hard to set up a repeater with separate FM and SSB inputs and repeat the audio on separate FM and SSB outputs. This would for the first time (that I know of) enable the advantages of SSB to be achieved on a repeater, namely SSB's inherent resistance to destructive interference and thus the ability to support multiple signals on a single frequency, and SSB's greater power efficiency...
With the above in mind I would like to see added to the SuperPeater requirements the following:
[AllStarLink] integration
True multi-user cross-band Full-duplex support as described in my link above, which can be achieved with:
Independent inputs and outputs for analog FM, SSB, 9600bps digital voice, and 9600bps data. i.e. 4 input channels on 70cm and 4 output channels on 2m. The 3 independent voice inputs would be mixed / voted based on SNR/BER. (The data channel would be totally separate but could be used for voice channel metadata.)
Such a system could provide equal or better audio quality than analog FM in all cases and be fully compatible with existing equipment. Someday I'd like to put together this sort of system as an experiment. I have a little different perspective than most because high-quality voice and full-duplex support are my primary interests in what I see as the next generation in repeater tech, but this would also accommodate separate data channels very easily and thus probably all the other requirements you mentioned. The data side of it could get complicated, but the voice channels as described above would be relatively simple to set up.
With a SuperPeater being largely software defined, and transmitting a wide bandwidth signal, I don’t see many issues in accommodating NR9V’s goals.
If you’re not yet licensed as an Amateur Radio Operator, and would like to join the fun by literally having a license to experiment with radio technology, check out Join the Fun on Amateur Radio for some pointers.
In its mission to highlight technological innovation in Amateur Radio, promote Amateur Radio to techies as a literal license to experiment with radio technology, and make Amateur Radio more relevant to society in the 2020s and beyond, Zero Retries is published via email and web, and is available to everyone at no cost. Zero Retries is proud not to participate in the Amateur Radio Publishing Industrial Complex, which hides Amateur Radio content behind paywalls.
My ongoing Thanks to:
Tina Stroh KD7WSF for, well, everything!
Annual Founding Members who generously support Zero Retries financially: Founding Member 0000 - Steven Davidson K3FZT (Renewed 2024)
Founding Member 0001 - Randy Smith WU2S (Renewed 2024) Founding Member 0002 - Chris Osburn KD7DVD (Renewed 2024) Founding Member 0003 - Don Rotolo N2IRZ (Renewed 2024) Founding Member 0004 - William Arcand W1WRA (Renewed 2024) Founding Member 0006 - Todd Willey KQ4FID (Renewed 2024) Founding Member 0007 - Merik Karman VK1DF / VK2MKZ (Renewed 2024 with two Founding Member subscriptions!) Founding Member 0008 - Prefers to Remain Anonymous 14 (Renewed 2024) Founding Member 0009 - Prefers to Remain Anonymous 19 (Renewed 2025) Founding Member 0011 - Rick Prelinger W6XBE (New 2024) Founding Member 0012 - Ryan Tolboom N2BP (New 2024)
Numerous Annual and Monthly subscribers who also generously support Zero Retries financially!
Want to Support Zero Retries?
The most effective way to support Zero Retries is to simply mention Zero Retries to your co-conspirators that are also interested in knowing more about technological innovation that is occurring in Amateur Radio and encourage them to become a fellow subscriber.
One particularly effective method of promoting Zero Retries is to add a mention of Zero Retries to your QRZ page (or other web presence) and include a link:
If you’d like to financially support Zero Retries, becoming a paid subscriber is greatly appreciated and helps offset expenses incurred in publishing Zero Retries. Paid subscriptions for Zero Retries are entirely optional, as explained in this special issue of ZR: Zero Retries Administrivia - Activating Payment Options.
These blogs and newsletters regularly feature Zero Retries Interesting content:
Dan Romanchik KB6NU mentions “Zero Retries Interesting” topics so regularly on his blog (that I otherwise wouldn’t know about) that I’ve bestowed on him the honorific of Pseudostaffer.
Jeff Davis KE9V also mentions “Zero Retries Interesting” topics so regularly on his blog (that I otherwise wouldn’t know about) that I’ve bestowed on him the honorific of Pseudostaffer.
Amateur Radio Weekly by Cale Mooth K4HCK is a weekly anthology of links to interesting Amateur Radio stories that often feature “Zero Retires Interesting” topics.
Experimental Radio News by Bennet Z. Kobb AK4AV discusses (in detail) Experimental (Part 5) licenses issued by the US FCC. It’s a must-read-now for me!
RTL-SDR Blog - Excellent coverage of Software Defined Radio units.
If you’re reading this issue on the web and you’d like to see Zero Retries in your email Inbox every Friday afternoon, just click below to join 2300+ 2400+ other subscribers:
Please tell your co-conspirators about Zero Retries — just click:
Email issues of Zero Retries are “instrumented” by Substack to gather basic statistics about opens, clicking links, etc.
More bits from Steve Stroh N8GNJ:
SuperPacket blog — Discussing new generations of Amateur Radio Data Communications - beyond Packet Radio (a precursor to Zero Retries)
N8GNJ blog — Amateur Radio Station N8GNJ and the mad science experiments at N8GNJ Labs in Bellingham, Washington, USA
Thanks for reading! Steve Stroh N8GNJ / WRPS598 (He / Him / His) These bits were handcrafted (by a mere human, not an Artificial Intelligence bot) in beautiful Bellingham (The City of Subdued Excitement), Washington, USA, and linked to the Internet via Starlink Satellite Internet Access.
2025-01-10
Blanket permission is granted for Amateur Radio use of any Steve Stroh content in Zero Retries for Amateur Radio newsletters and distribution via Amateur Radio such as (but not limited to) Packet Radio Networks, Packet Radio Bulletin Board Systems, Repeater Nets, etc. Specific blanket permission is granted to TAPR to use any Steve Stroh content in Zero Retries for the TAPR Packet Status Register (PSR) newsletter (I owe them from way back).
In such usage, please provide appropriate authorship credit for the content.
If you’d like to republish an article in this issue for other uses, just ask.
All excerpts from other authors or organizations, including images, are intended to be fair use. Unless otherwise noted in the article, there are no paid promotional items in any Zero Retries articles.
This is in the quoted text of the zBitx product page (and thus I’m not going to “correct” it editorially), but I believe this is a typo or perhaps written very early in the development when the zBitx was hoped to achieve 10 watts transmit power. Every other reference (that I saw) of the maximum transmit power of the zBitx says 5 watts, not 10 watts.
DV Fast Data flips a bit in the D-Star data stream to use the D-Star 2400 bps digitized voice stream, and the 1200 bps Forward Error Correction stream, for data in addition to the 900 bps data stream, for an ~ 4500 bps data stream. Unfortunately, only a few Icom D-Star radios include DV Fast Data mode. In the original announcements of DV Fast Data, even the oldest D-Star repeaters support DV Fast Data, so it seems that Icom could have incorporated DV Fast Data into D-Star radios from the beginning… but didn’t, thus DV Fast Data mode is barely known and poorly supported.
If we ever meet in person, I’d enjoy having a discussion with Nino Carrillo KK4HEJ (the primary developer of the NinoTNC) that I consider the NinoTNC to be an embedded “Software TNC” because it has a flexible modem (various speeds available in the same unit) and a flexible embedded processor that can be easily updated to provide new capabilities (as has often been done). One such impressive added capability of the NinoTNC is the IL2P Forward Error Correction capability developed by KK4HEJ.
Post Publication Update - Despite the name, the Citizens Broadband Radio Service (CBRS)isn’t relevant in the context of this discussion. CBRS operates in the 3.5 GHz range, and there are no user-to-user capabilities within CBRS. CBRS is structured to be used by service providers (such as Internet Service Providers), mobile telephone companies, enterprises, and conceivably, small businesses. For person to person data use, Wi-Fi and similar services are far more useful than CBRS.
This was a great issue. So much good stuff over the past few weeks.
HFSignals BitX40 was my first real introduction to HF (well, I had a Heath SB104 that breaks every other QSO so I don't count that). The first time I got it on the air I heard a QSO with an antarctic station during solar minimum. I own two Bitx40s, one with the analog VFO and the second with the DDS VFO using an Arduino. I also built a very early revision uBitx as a portable radio (including DIY Li-Ion battery packs) to take up to the Boundary Waters. That rig has been through several cases and many upgrades to resolve the hardware issues on the older variants. It was a great learning experience. I never bought an sBitx, mainly due to the cost and redundant functionality. The xBitx looks awesome though. With the easily changeable standard batteries it looks like it's designed exactly for what I was trying to achieve with the uBitx.
I liked your mention of hardware TNCs being good for APRS digipeaters too. I'm a fan of software TNCs for ax.25, Direwolf in particular, but there's nothing like being able to extend a network (APRS, Packet, etc...) with no more complication than pressing the power button on the TNC and radio. My local club supports a large bike race in some rough terrain and fill-in APRS digipeaters are critical for tracking. Hardware TNCs meet the KISS principal here and are the perfect solution.
You are probably aware, but you don't need to write code to use GNURadio. Most of my GNURadio experimentation has been ore of a professional (infosec) interest, but I found this blog post extremely helpful in getting started with it: https://www.blackhillsinfosec.com/how-to-replay-rf-signals-using-sdr/ There was also a more basic post earlier that covered just listening and combining multiple audio streams, but I can't seem to find it anymore. They have some other interesting GNURadio posts here: https://www.blackhillsinfosec.com/tag/gnuradio/
Thanks for mentioning wsjtx_improved. I had not seen this before and I have some small-display use cases for this. I will be trying it out!
You mentioned StarLink being the first consumer product using phased array antennas. Wifi has used this for beam forming since 802.11n.
I'm excited for the 16gb version of the RPi. You really can't beat an ARM-based SBC for power efficiency in "appliance" applications, and the GPIO ports give hardware interfacing flexibility that higher-power, similarly priced x86 machines can't match.
Nice to subtly discover another Battlestar Galactica fan... One of the few TV shows where the remake was better than the original in my opinion. :-)
This was a great issue. So much good stuff over the past few weeks.
HFSignals BitX40 was my first real introduction to HF (well, I had a Heath SB104 that breaks every other QSO so I don't count that). The first time I got it on the air I heard a QSO with an antarctic station during solar minimum. I own two Bitx40s, one with the analog VFO and the second with the DDS VFO using an Arduino. I also built a very early revision uBitx as a portable radio (including DIY Li-Ion battery packs) to take up to the Boundary Waters. That rig has been through several cases and many upgrades to resolve the hardware issues on the older variants. It was a great learning experience. I never bought an sBitx, mainly due to the cost and redundant functionality. The xBitx looks awesome though. With the easily changeable standard batteries it looks like it's designed exactly for what I was trying to achieve with the uBitx.
I liked your mention of hardware TNCs being good for APRS digipeaters too. I'm a fan of software TNCs for ax.25, Direwolf in particular, but there's nothing like being able to extend a network (APRS, Packet, etc...) with no more complication than pressing the power button on the TNC and radio. My local club supports a large bike race in some rough terrain and fill-in APRS digipeaters are critical for tracking. Hardware TNCs meet the KISS principal here and are the perfect solution.
You are probably aware, but you don't need to write code to use GNURadio. Most of my GNURadio experimentation has been ore of a professional (infosec) interest, but I found this blog post extremely helpful in getting started with it: https://www.blackhillsinfosec.com/how-to-replay-rf-signals-using-sdr/ There was also a more basic post earlier that covered just listening and combining multiple audio streams, but I can't seem to find it anymore. They have some other interesting GNURadio posts here: https://www.blackhillsinfosec.com/tag/gnuradio/
Thanks for mentioning wsjtx_improved. I had not seen this before and I have some small-display use cases for this. I will be trying it out!
You mentioned StarLink being the first consumer product using phased array antennas. Wifi has used this for beam forming since 802.11n.
I'm excited for the 16gb version of the RPi. You really can't beat an ARM-based SBC for power efficiency in "appliance" applications, and the GPIO ports give hardware interfacing flexibility that higher-power, similarly priced x86 machines can't match.