C4FM looks like a single thing — a Yaesu radio mode — but it is really a stack of layers, built by different people over more than a decade, each one a response to the limits of the layer beneath it. This page traces that stack from the raw modulation up to the routed networks that ham digital voice runs on today.
C4FM stands for Continuous 4-level Frequency Modulation: a four-state form of 4FSK that carries digital bits as four discrete frequency shifts. It is a physical-layer modulation, not a network and not a brand. It predates amateur Fusion by years — the same modulation family underpins P25 Phase 1, in public-safety use since the 1990s, and it reappears in NXDN and, more recently, in M17. C4FM runs in a 12.5 kHz channel and carries data at up to 9600 bps.
In everyday conversation "C4FM" has become shorthand for Yaesu System Fusion, but the modulation itself is older and broader than anything Yaesu built. Yaesu's contribution was to pair C4FM with the AMBE+2 voice codec and wrap it in a complete, consumer-ready system.
Yaesu introduced System Fusion in 2013. Its defining feature was not raw audio quality but Automatic Mode Select (AMS): a Fusion repeater or radio senses whether an incoming signal is analog FM or C4FM and matches it automatically, so digital and FM users can share one machine without anyone flipping a switch. That backward compatibility is the main reason Fusion spread as quickly as it did.
Linking between Fusion repeaters was handled by WIRES-X, Yaesu's own internet "rooms" network, accessed through the HRI-200 node interface. WIRES-X was — and remains — closed: it accepts only registered Yaesu hardware, and hotspots cannot join it. The first Fusion repeater was the DR-1X. The closed nature of WIRES-X is the single fact that motivated almost everything that came afterward.
Hams wanted an open alternative to WIRES-X, and it arrived through Jonathan Naylor, G4KLX, and his MMDVM project. MMDVM let inexpensive modems and hotspots speak Fusion among other modes, and G4KLX wrote the matching server side: the YSFReflector, plus the YSFGateway, YSFParrot, and later the DG-ID Gateway — collectively the "YSFClients" suite. In hotspot parlance, a "YSF reflector" means this open, community system, not anything sold by Yaesu.
Reflector listings and host files were maintained for years by Kim Hübel, DG9VH, at ysfreflector.de. On 1 June 2025 that registry was handed to the DVRef team (Steve Miller, KC1AWV), which now serves the host files that Pi-Star, WPSD, and similar software rely on to find each other.
A second, parallel reflector system grew up alongside G4KLX's YSF reflectors: FCS. It came not from a reflector project but from a hotspot product — the DV4mini, a USB stick built in 2015 by a German team led by Torsten Schultze (DG1HT), with Stefan Reimann (DG8FAC) and Kurt Moraw (DJ0ABR), and contributions from Michael Peil (DJ2VA), Meinhard "Mike" Guenther (DL2MF), Klaus Woerner (DL5KV), and Hans-Jürgen Barthen (DL5DI).
On 29 July 2015, DG1HT brought up FCS001, the first FCS reflector. The system uses rooms numbered 0–99 within named servers (FCS001, FCS002, and so on), with FCS002 becoming an early US C4FM reflector. FCS and YSF are different systems with different architectures, but both are open to hotspots, and software like Pi-Star and WPSD speaks both — which is why a Fusion user has to know whether a given destination is a "YSF" room or an "FCS" room.
Yaesu's second-generation repeater, the DR-2X, arrived around 2017 and brought two ideas that shaped everything downstream.
The first was DG-ID (Digital Group ID), a 00–99 group tag carried in every transmission. DG-ID 00 monitors everything; other values partition users into groups and, on networks, select rooms. DG-ID replaced the older digital-squelch scheme and became the addressing primitive that later networks would lean on.
The second was IMRS (Internet-linked Multi-site Repeater System), Yaesu's own repeater-to-repeater linking over IP. With the optional LAN-01A board, a DR-2X can be configured with up to about 100 partner repeaters, with DG-ID controlling how calls route between them. IMRS is a peer mesh between DR-2X machines — no central server, no hotspot access, and independent of WIRES-X.
The last major piece tied DG-ID together with the multiprotocol idea. YCS, written by Kurt Baumann (OE1KBC) — also the author of IPSC2, the software at the core of the DMR+ and DMR-MARC networks — was the first C4FM network with its own routing matrix, DVMatrix. Each YCS server offers 100 digital groups, every one addressable straight from the radio's DG-ID, and through DVMatrix it bridges Fusion into the DMR and D-Star worlds, so a DG-ID can map onto a DMR talkgroup.
A single YCS server can speak FCS, YSF, IMRS, and Fusion II at once, letting repeaters, hotspots, and DR-2X machines all meet in the same place. On the hotspot side, G4KLX's DG-ID Gateway is the enabler: the radio's DG-ID setting picks which room you land on. This DG-ID-as-router idea is the model behind multiprotocol C4FM gateways generally.
It helps to remember that these are separate networks, not one interoperable cloud. WIRES-X (closed, Yaesu), IMRS (Yaesu's repeater mesh), and the open hotspot world (YSF, FCS, YCS) are independent systems: a station on one cannot talk to a station on another unless someone has deliberately bridged them. Hotspots can reach only the open three. A great deal of the cross-mode bridging in the hobby exists precisely to stitch these otherwise-separate worlds back together.
| Layer / system | Builder(s) |
|---|---|
| C4FM modulation | P25 lineage (1990s); adopted by Yaesu for System Fusion, 2013 |
| System Fusion, WIRES-X, DR-1X / DR-2X, DG-ID, IMRS | Yaesu Musen Co., Ltd. |
| YSFReflector, YSFGateway, DG-ID Gateway (MMDVM) | Jonathan Naylor, G4KLX |
| YSF reflector registry → DVRef | Kim Hübel, DG9VH → Steve Miller, KC1AWV |
| DV4mini, FCS reflector system | Torsten Schultze, DG1HT; Stefan Reimann, DG8FAC; Kurt Moraw, DJ0ABR (with DJ2VA, DL2MF, DL5KV, DL5DI) |
| YCS server / DVMatrix | Kurt Baumann, OE1KBC |