M17 Project (Unofficial) / M17 Project (Unofficial) is on Nostr

Unofficial automated RSS/Atom links from the source M17 Project, covering M17 digital voice radio and open communication. Original creators are credited at the source; follow original links. Zaps support the independent feed operator, not the source creators.

Last Notes

2026-10-18 12:56:49 GMT

Neural Codec2 decoding for DroidStar
Our experimental fork of DroidStar can now decode M17 voice with a neural vocoder. The new decoder comes from Codec2-mod-neural, which uses the FARGAN network from the Opus project. It takes the same Codec2 3200 frames every M17 radio already sends and turns them into wideband 16 kHz speech instead of the classic 8 kHz sinusoidal synthesis. Nothing changes on the transmitting side, the bitstream is untouched, so you get the improvement on every 3200 bps M17 stream you receive, no matter who is talking.
Installing
Download the zipped APK file below.
Unpack it and open the DroidStar.apk file. Android will ask you to allow installs from your browser or file manager – allow it.
If you already have DroidStar installed and Android refuses to update it, uninstall the old version first and install again. Your settings (callsign, hosts) will need to be entered again.
Download DroidStar with Codec2 neural enhancer
To enable the neural synthesizer, go to Settings and scroll down to “Neural Codec2 decoder (M17 3200)” – tick it. Connect to a reflector afterwards, as usual.
Tell us how it sounds and which phone you use. Waiting for comments!
https://m17project.org/2026/10/18/neural-codec2-decoding-for-droidstar/
#neural #droidstar #download #settings #khz #opus #apk #installingdownload
#rss #feeds #linksharing #qwibbit

2026-10-17 16:01:54 GMT

Codec2 3200 meets FARGAN
Codec2 3200 carries M17 voice, and its classic decoder is the weak spot. It’s limited to 8 kHz and has that recognizable buzzy, synthetic sound. Instead of designing a new codec, I wanted to know how far a better receiver could go with exactly the same bits on the air.
The answer is FARGAN, the low-complexity neural vocoder from Xiph’s Opus codec (Valin et al.). The idea is simple. The Codec2-mod decoder unpacks each 8-byte frame into its usual parameters: pitch, voicing, energy and LSPs. Instead of feeding those to the sinusoidal synthesizer, we map them to 20 features per 10 ms and let FARGAN generate 16 kHz speech.
Data: the Opus speech corpus, processed with Opus’s own augmentation recipe, but with features computed by the real Codec2-mod encoder and decoder. An important early lesson: never pair noisy features with a clean target. The network can’t denoise, and my first attempts sounded like speech through a pipe.
Training: Opus’ two stage recipe on rented GPUs1. Stage 1 was 400 epochs (about 14.5 hours), and stage 2 was 50 adversarial epochs (about 37 hours on an RTX 5090). The adversarial stage made a clearly audible difference from its first few epochs.
C library: the model uses about 818,000 parameters, runs on Opus’ own C inference code, and takes about 1.6 ms of CPU time per 20 ms frame on a single x86 core. The ARM64 NEON build compiles and produces matching output, real hardware timing test will follow.
The result is Codec2-mod-neural, a drop-in alternative to codec2_decode(): 8 bytes in, 320 samples at 16 kHz out. Nothing changes for transmitters, and every existing Codec2 decoder still works on the same stream.
Code, training scripts, and the model: https://github.com/M17-Project/Codec2-mod-neural
Next up: integration into DroidStar and mvoice, and later a look at running it on LinHT. ViSQOL benchmarks will also be ran along with synthetic BER tests to assess synthesizer’s noise immunity.
M17 Foundation covered the expense (200 USD) with most of it left for future runs. ︎
https://m17project.org/2026/10/17/codec2-3200-meets-fargan/
https://s.w.org/images/core/emoji/17.0.2/72x72/21a9.png
#fargan #opus #stage #khz #instead #training #valin
#rss #feeds #linksharing #qwibbit

2026-10-16 19:28:48 GMT

libm17 updates
Two recent commits make libm17 (versions 1.4.0 and 1.4.1) a better fit for small microcontrollers, such as the Cortex-M4-based radios OpenRTX runs on.
The first, 5214d99, reduces memory and code size without changing any output. The receive front-end and the Viterbi depuncturing now work in a single pass, and the four convolutional encoders became one. On a Cortex-M4F this reduced the Viterbi decoder context from 1,596 to 620 bytes, decoder stack from about 1.5 KB to 800 bytes, and flash by about 840 bytes. The decoder context changed size, so this is a slight ABI change.
The second, 0c92621, replaces the soft Golay(24,12) decoder used for the LICH with a Chase-II decoder that rejects ambiguous codewords. In simulation, LICH sensitivity improved by about 1 dB, and wrong LICH chunks are accepted 20–80x less often. As a result, decode_str_frame() will report a failed LICH (lich_cnt = 0xFF) more often at low signal levels. On a Cortex-M4, decoding a stream frame takes roughly 30-40% more CPU than before, which is still less than OpenRTX’s own decoder. The same commit uses a hardware popcount where the target has one and makes the unit tests compile without warnings.
LSF, payload and transmit output are unchanged, and the public API is the same. In simulated tests against OpenRTX’s hard-decision frame decoder, libm17 needed about 3 dB less SNR for a successful decode.
https://m17project.org/2026/10/16/libm17-updates/
#lich #viterbi #openrtx #golay #abi #lsf
#rss #feeds #linksharing #qwibbit

2026-10-16 19:00:03 GMT

LinHT Rev C – ready for tests!
Vlastimil OK5VAS just sent me a nice set of photos (click to enlarge).
Coffee and a PCB – such a great combo
Front side
Back side
Standby for test results!
The LinHT project is proudly supported by the M17 Foundation and their generous donors.
https://m17project.org/2026/10/16/linht-rev-c-ready-for-tests/
https://m17project.org/wp-content/uploads/2026/10/rev_c_1-768x1024.jpg
https://s.w.org/images/core/emoji/17.0.2/72x72/1f600.png
https://m17project.org/wp-content/uploads/2026/10/rev_c_2-768x1024.jpg
#linhtrev #pcb #back #front #coffee
#rss #feeds #linksharing #qwibbit

2026-10-16 04:30:22 GMT

M17 WPSD fork now supports SMS
In July 2025, G4KLX removed M17 from MMDVMHost and M17 was removed from WPSD. The M17 Project responded by creating forks of the code that kept M17 working, but those forks had fallen behind upstream. Working with Claude Code, I (Jim Ancona N1ADJ) brought the underlying code up to date. With these updates, the M17 Project forks of MMDVMHost and M17Gateway are now current with the upstream repositories. In addition, M17 packet mode (SMS) works from end to end: radio, hotspot, gateway, reflector and dashboard. WPSD users will see the changes with their next nightly update or they can trigger a manual update to get them sooner.
MMDVMHost Branches
Earlier this year, upstream started to add MQTT functionality to MMDVMHost. Those changes broke backwards compatibility, so the last compatible release is tagged as v1.0. Dashboard software like WPSD and Pi-Star hasn’t moved to the MQTT release yet. The M17 Project’s MMDVMHost has these branches:
v1.0: G4KLX’s last release before the move to MQTT, with M17 restored. It still talks to dashboards through log files, which is what WPSD uses. It also includes a set of bug and security fixes backported from G4KLX’s current code.
master: G4KLX’s current code, with M17 restored. This is the version with MQTT (next section).
archived-master: The fork’s previous code. We don’t plan to modify this branch. If you cloned the repo before October 2026 you should review the README.
Each branch is G4KLX’s code plus a small set of M17 commits. That makes future upstream updates straightforward and easy to review.
The M17 WPSD fork now uses the v1.0 branch. If you’re running a custom hotspot or repeater setup and want to try the MQTT approach, master is the branch to use. On master, MMDVMHost publishes its status and activity as JSON over MQTT instead of writing log files for dashboards to parse. M17-related messages are documented in the repository’s schema.json. They include:
M17: voice and data activity including callsigns, source (RF/network), action (start/end/lost…), type (voice, data or packet), duration, ber, and rssi with min/max/average.
M17Packet (new): one message per packet, with protocol, length, and text for SMS or data (hex) for anything else.
M17 Packet Mode (SMS)
M17 packet mode allows sending SMS messages and other data over the air with M17. It’s been in the M17 spec and supported in other software for a while, but now it’s available in MMDVMHost-based software like WPSD.
The new code:
receives and decodes M17 packet transmissions, including SMS
repeats them on repeaters and duplex hotspots
forwards them to reflectors on the network
transmits packets received from the network
You need SMS-capable radio firmware to use this. The OpenRTX developers are working on it, so keep an eye out for a release.
M17Gateway
M17Gateway, the component that communicates with M17 reflectors like mrefd, got some updates as well:
Packet support: carries packets (M17P) between the hotspot and reflectors that support it, and ECHO returns packets as well as voice.
Reflector protocol update: We now support both legacy and current releases of mrefd along with urfd and other reflectors that support the M17 INet spec. (Thanks to Tom, N7TAE for his help with the design!)
Voice announcements: give the full reflector name and module letter for all reflectors.
WPSD
The updates to M17 are live now. New binaries arrive through WPSD’s normal nightly update, and the dashboard will show SMS in the last heard list. The binaries are now built automatically with GitHub Actions from the M17 Project repositories, so future fixes will reach users quickly and easily.
One caveat: SMS also needs modem firmware with M17 packet support. For MMDVM_HS_Hat, Dual Hat, generic GPIO and MMDVM repeater boards, you will need to update the firmware with WPSD’s firmware updater, unless you’ve already done that using m17-hotspot-installer. Other hotspot boards (ZUMspot, Nano hotSPOT, NanoDV, SkyBridge…) don’t have packet-capable firmware yet.
Another known limitation: ADF7021 hotspot boards (ZUMspot, MMDVM_HS_Hat, the dual hats…) can only listen for one mode at a time. With multiple modes enabled, they take turns, so they hear M17 only part of the time. M17 voice can recover from a late start, but a short SMS can be lost completely. So our recommendation is that for reliable SMS you only enable M17. Full MMDVM repeater boards don’t have this problem.
The code is on GitHub in the M17-Project organization:
MMDVMHost: https://github.com/M17-Project/MMDVMHost
M17Gateway: https://github.com/M17-Project/M17Gateway
WPSD-Binaries: https://github.com/M17-Project/WPSD-Binaries
WPSD-WebCode: https://github.com/M17-Project/WPSD-WebCode
I’ve tested the v1.0 branch on M17 and DMR, but the community can help a lot by trying different branches, modes and hardware. If something doesn’t work or you have questions, we’d like to hear about them on the M17 Discord or by creating an issue in the corresponding GitHub repository.
Acknowledgements
Thanks to the developers and projects that this work builds on, including:
G4KLX for MMDVMHost and M17Gateway
CA6JAU for the MMDVM_HS firmware
W0CHP and the WPSD developers
The OpenRTX developers
KD0OSS for the original packet work, which the firmware support builds on
Ember for the backported MMDVMHost fixes
https://m17project.org/2026/10/13/m17-wpsd-fork-now-supports-sms/