Walk into any digital voice conversation in ham radio and there's a near certainty that at least one station got there through MMDVM. The little hotspot on the shelf, the club repeater on the hill, the dashboard you check on your phone — under the hood, it's usually the same project. (New to digital voice? Start with the digital modes guide. For the server side of the link, see Understanding HBlink3.)
MMDVM stands for Multi-Mode Digital Voice Modem, an open-source creation of Jonathan Naylor, G4KLX, and it did for digital voice what the soundcard did for digital HF: it replaced a closet of single-purpose commercial boxes with one piece of hardware anyone can afford and one stack of free software anyone can run.
The name covers an ecosystem with three layers, and the easiest way to understand it is to follow a transmission from your radio to the internet.
At the bottom of the stack is the modem itself: a small circuit board with a microcontroller and a radio chip, running the MMDVM firmware. Its job is the physical layer — listening to RF and turning the incoming digital waveform back into a stream of bits, and doing the reverse when it's time to transmit. What made it revolutionary is the multi-mode part: the same board demodulates D-STAR, DMR, System Fusion, P25, NXDN, and M17, switching between them on the fly. Before MMDVM, each of those modes meant separate, mode-locked, often commercial hardware. After it, they meant a firmware update.
The modem hands its bits up a serial link to MMDVMHost, a program running on a small computer — almost always a Raspberry Pi. MMDVMHost is the traffic cop: it figures out which mode is active, decodes the headers (whose callsign, which talkgroup or reflector), lights up the dashboard, and decides where the traffic goes next. It's also where your station's identity lives — callsign, DMR ID, frequencies.
MMDVMHost doesn't talk to the networks directly. For each mode there's a gateway program — one for DMR, one for YSF, one for NXDN, P25, M17, D-STAR — that speaks that network's internet protocol and maintains the connection to a reflector or master server. This is where MMDVM shakes hands with everything else on this site: the DMR gateway speaks the HomeBrew protocol to servers like the ones described in Understanding HBlink3, the YSF gateway connects to YSF reflectors, and so on. The modem speaks radio; the gateways speak internet; MMDVMHost stands in the middle translating.
Put all three layers in one small package and you get the device that made digital voice personal: the hotspot. A Raspberry Pi, a modem board riding on its GPIO pins, and a distribution like Pi-Star or WPSD that bundles MMDVMHost, all the gateways, and a web dashboard into something you configure from a browser. Your handheld talks to the hotspot across the room on a few milliwatts; the hotspot carries the conversation to the world. The same stack scales up, too — swap the tiny hotspot board for a full MMDVM modem wired to real transmitters and receivers, and the identical software becomes a repeater.
Before MMDVM, each digital mode lived behind its own wall: proprietary hardware, mode-locked repeaters, networks that couldn't see each other. MMDVM knocked the walls down from below. Once one cheap board could speak every mode, and one free program could route them all, the interesting questions stopped being “which mode should our repeater be?” and became “why not all of them?”
The big idea
Every multi-mode reflector, cross-mode bridge, and seven-network hotspot in the hobby today stands on that foundation — one modem, many modes, and software anyone can read.
A noncommercial hobby reference compiled by N6JET, gathered from public sources and shared freely for anyone interested in amateur digital voice.