Tag: digital voice

  • Yaesu System Fusion Made Easy: Step-by-Step Setup and First Contact

    Yaesu System Fusion Made Easy: Step-by-Step Setup and First Contact

    Yaesu System Fusion is Yaesu’s amateur-radio digital voice system built around C4FM digital modulation. It is designed to make it easy to move between conventional analog FM and digital voice on compatible Yaesu radios and repeaters. The basic idea is simple: program your callsign, tune a compatible repeater or simplex frequency, choose the correct digital mode, and operate. Internet linking through Yaesu’s WIRES-X network adds access to remote nodes and rooms, but WIRES-X and third-party YSF/FCS hotspot networks are not the same thing.

    NJ2RQ Yaesu FTX-1 Optima C4FM System Fusion radio
    NJ2RQ’s Yaesu FTX-1 Optima, a current C4FM/System Fusion-capable transceiver.

    What System Fusion Actually Is

    System Fusion uses C4FM 4-level FSK digital modulation for amateur-radio voice and data. Compatible repeaters can support both C4FM digital and conventional analog FM. One of the system’s most useful features is AMS — Automatic Mode Select. On radios that support it, AMS recognizes whether the incoming signal is analog FM or C4FM digital and can select the appropriate receive and transmit mode according to the radio’s AMS settings.

    That does not mean every repeater automatically converts every analog transmission into digital or vice versa. Repeater configuration matters. Think of System Fusion as a family of C4FM-capable radios and repeaters, with AMS helping analog and digital users share compatible systems more easily.

    DN, VW and FM: The Modes You Will See

    For most everyday C4FM operation, DN is the standard digital voice mode. Yaesu calls it V/D, or Voice/Data simultaneous mode. Part of the 12.5 kHz channel is used for digital voice while the remainder is used for error correction and other data. On radios equipped for it, position information can be included with a DN voice transmission.

    VW, also called Voice FR or Voice Full Rate, uses the full 12.5 kHz channel for digital voice. It can provide higher-quality voice audio, but it does not carry position information in the same way as DN. Not every radio, repeater or operating situation uses VW, so DN is generally the safest starting point for a new Fusion operator.

    FM is ordinary analog FM. AMS can make switching between FM and C4FM easier when a compatible repeater and radio are configured for both.

    WIRES-X: Internet Linking for System Fusion

    WIRES-X is Yaesu’s Internet linking system. A WIRES-X node connects radio traffic to other nodes and rooms through the Internet. When you access a compatible local WIRES-X node with a C4FM radio, you can search for and connect to other nodes or rooms and communicate far beyond the local repeater’s RF coverage.

    The exact button sequence varies by radio. Older radios may use a DX or X key; newer touchscreen models may present WIRES-X controls in a menu. Always use the instructions for your specific model rather than assuming the same key sequence applies to every Yaesu radio.

    Important: WIRES-X Is Not the Same as a YSF Hotspot

    This is one of the most common sources of confusion. A third-party MMDVM hotspot running Pi-Star or WPSD can support YSF and FCS reflectors, but Yaesu specifically notes that these hotspots do not directly connect you to the WIRES-X network. That is why the radio’s WIRES-X button and WIRES-X room functions may not behave as expected when you are using an MMDVM hotspot.

    So there are two related but distinct ways to use C4FM over the Internet:

    • Yaesu WIRES-X: uses Yaesu-compatible WIRES-X nodes, rooms and supported node/PDN configurations.
    • YSF/FCS hotspot networks: commonly use an MMDVM hotspot and reflector system. They carry C4FM digital voice, but they are not the WIRES-X network.

    Some systems may be bridged by their operators, but a bridge does not make YSF/FCS and WIRES-X the same network.

    DG-ID: What It Does

    DG-ID means Digital Group ID. It is not the same thing as a DMR talkgroup. On compatible Fusion radios and repeaters, DG-ID can be used to control which digital group or repeater functions respond to a transmission. The correct DG-ID depends on how the repeater or WIRES-X node is configured.

    Many open systems use DG-ID 00, but you should not assume 00 is correct everywhere. Yaesu’s WIRES-X instructions specifically say that the radio’s DG-ID must match the DG-ID required by the node. Check the repeater owner’s instructions or local club information before changing it.

    Step-by-Step: Your First Fusion Contact

    1. Program Your Callsign

    Enter your amateur-radio callsign in the radio’s MY CALL or callsign setting. C4FM radios include the programmed callsign in their digital identification data. The exact menu location varies by model.

    2. Find a C4FM/System Fusion Repeater

    Use a current repeater directory or your local club’s information to find a repeater that supports C4FM/System Fusion. Record its output frequency, input offset, any required tone settings, and any published DG-ID instructions. Do not rely on a generic offset value when the repeater listing gives specific information.

    3. Program the Repeater Correctly

    Enter the repeater frequency and its exact offset. If the system requires a tone for analog access, save that as well. For digital operation, select DN or an appropriate AMS setting. If the repeater publishes a DG-ID requirement, match it.

    4. Listen First

    Before transmitting, listen long enough to make sure the repeater is not already in use. This is particularly important on a repeater that may be connected to WIRES-X, because changing a room can affect everyone using that local repeater.

    5. Make a Local C4FM Contact

    You do not need WIRES-X simply to make a C4FM contact. If another station is using the same local C4FM repeater or simplex frequency, transmit normally, identify with your callsign, and have the QSO just as you would on FM.

    6. Access WIRES-X if the Repeater Supports It

    If the repeater or node is WIRES-X enabled, use your radio’s model-specific WIRES-X control to access the node. Once connected, compatible radios can display node information and allow searches for available nodes or rooms. Follow the repeater owner’s policies before changing rooms.

    7. Return the Repeater to Its Normal State

    If you connected the repeater to a different room, follow the local system’s instructions when you are finished. Some repeaters automatically return to their home room after a timeout; others expect the operator to disconnect or reconnect the normal room.

    Using an MMDVM Hotspot Instead

    If you cannot reach a local Fusion repeater, an MMDVM hotspot can still be a useful way to operate C4FM. Configure the hotspot for YSF or FCS operation, select the desired reflector in the hotspot software, and tune the radio to the hotspot’s simplex frequency in DN mode. The hotspot receives your low-power C4FM RF signal and sends it through the selected reflector network.

    Remember: on this type of setup you generally control the reflector from the hotspot dashboard or supported commands, not by treating the hotspot as a genuine WIRES-X node.

    The FTX-1 Optima and System Fusion

    The Yaesu FTX-1 series supports C4FM digital operation in addition to HF, 6 meters, 2 meters and 70 centimeters. Yaesu has also released WIRES-X support and current WIRES-X documentation for the FTX-1 series. With the proper current firmware and WIRES-X PC software, the FTX-1 can also be used in supported WIRES-X node configurations; Yaesu documents direct USB-C connection to a Windows PC for this purpose.

    Quick Troubleshooting

    • No digital audio: Confirm that you are actually on a C4FM-capable repeater and that the radio is in DN or the correct AMS mode.
    • Repeater will not respond: Recheck the frequency, offset, DG-ID and any locally required settings.
    • WIRES-X button does nothing on a hotspot: If it is an MMDVM hotspot using YSF/FCS, that behavior is expected; it is not a native WIRES-X node.
    • Cannot connect to a WIRES-X room: Confirm that the local node is online and that your radio, node type and room are compatible with the connection method being used.
    • Analog and digital users are confusing each other: Verify the repeater’s AMS and operating policy. Local repeater configuration determines how analog and digital traffic are handled.

    Bottom Line

    For a first System Fusion contact, keep it simple: program your callsign, find a C4FM repeater, use the repeater’s exact settings, start in DN or the proper AMS mode, listen, and make a normal contact. Add WIRES-X only after you understand the local repeater’s rules. If you use an MMDVM hotspot, remember that YSF/FCS reflectors are a separate network from native Yaesu WIRES-X.

    Technical audit based on current Yaesu System Fusion, WIRES-X and FTX-1 documentation.

  • M17 Explained: What It Is and an Easy Step-by-Step Setup

    M17 Explained: What It Is and an Easy Step-by-Step Setup

    M17 is an open-source digital voice and data protocol built for amateur radio. Its defining feature is that the protocol and the Codec2 speech codec are open, so experimenters can study, implement, modify, and build compatible hardware and software without depending on a proprietary AMBE-family voice codec.

    Photo note: the featured image on this post is an authentic NJ2RQ amateur-radio equipment photo used as general station context. M17 compatibility is model-specific; do not assume every radio shown supports M17.

    What M17 actually is

    M17 is not simply another internet linking system and it is not a variation of DMR, D-STAR, or System Fusion. It has its own RF air interface, framing, addressing, voice encoding, error correction, and reflector network. The current published M17 air-interface specification, version 2.0.4 dated January 21, 2026, defines 4-level frequency-shift keying (4FSK) at 4,800 symbols per second. Because each 4FSK symbol represents two bits, the raw data rate is 9,600 bits per second. The specification targets about a 9 kHz occupied bandwidth with 12.5 kHz minimum channel spacing.

    For voice, M17 uses the open-source Codec2 vocoder. In the stable version 2 specification, voice-only operation uses Codec2 at 3,200 bits per second. The protocol also includes forward error correction, packet mode, and metadata capabilities such as text and GNSS position information.

    Why hams are interested in it

    DMR, D-STAR, and System Fusion are well-established systems, but common implementations rely on licensed AMBE-family vocoders. M17 takes a different approach: the protocol is designed around open specifications and open-source software. That makes it especially attractive to operators who enjoy firmware, software-defined radio, custom hotspots, modem boards, and experimentation.

    M17 is also still evolving. The M17 Project has been discussing a future version 3 specification, so a beginner should always check current project documentation before flashing firmware or following an older setup video. This guide deliberately sticks to the stable concepts that are useful today.

    Ways to get on M17

    1. Use a radio with direct M17 support

    The easiest RF path is a radio that already supports M17. Current OpenRTX development information lists the Connect Systems CS7000-M17 and CS7000-M17 Plus as supporting M17 transmit and receive. OpenRTX also supports M17 on some TYT/Retevis models, but support differs by exact model and band. For example, the development-status page lists M17 transmit and receive on the MD-UV380/390 family, while some older MD-380/390 variants have model-specific limitations.

    Important: do not flash a radio just because the model name appears in an old guide. Check the current OpenRTX support table first.

    2. Use Module17 with a compatible analog radio

    Module17 is an open-source M17 modem designed to turn a compatible 9,600-baud-capable transceiver into an M17 station. This is not the same thing as feeding digital audio through an ordinary microphone jack. M17 needs a sufficiently flat baseband/data path, so radio compatibility and cabling matter.

    3. Use an M17-capable hotspot or gateway

    M17 can also be used through hotspot and gateway software with compatible modem hardware. MMDVM-class hardware and dedicated M17 gateway projects can connect local RF users to M17 reflectors. The exact menu names vary between Pi-Star, WPSD, M17 Gateway, and other distributions, so follow the documentation for the software actually installed on your hotspot.

    4. Use software for internet-side experimentation

    Software such as DroidStar supports M17 reflector connections in addition to several other digital voice networks. That can be useful for learning the reflector/module structure before building an RF station. If you transmit through any system that ultimately places your audio on amateur radio RF, normal licensing and identification rules still apply.

    How M17 addressing works

    M17 is callsign-oriented. The air-interface specification encodes source and destination addresses in a 48-bit address field that can represent amateur callsigns and reflector destinations. A DMR Radio ID is not the basic identity used by the M17 air interface. For a normal amateur station, configure your callsign exactly as your radio, hotspot, or client documentation requires.

    Reflectors commonly use names in the form M17-XXX and can provide modules or channels identified by letters. The specification itself gives reflector-style destinations such as “M17-M17 C” as an example. Do not assume one reflector or one module is the universal worldwide calling channel; reflector use and activity change over time.

    Step-by-step: a safe beginner setup

    Step 1: Choose your path

    Decide whether you are using a native M17 radio, an OpenRTX-supported radio, Module17 with a compatible transceiver, a hotspot/gateway, or an internet client. Do not mix instructions from two different platforms.

    Step 2: Update firmware and host files

    Use the current release recommended by the project or manufacturer. Back up your existing radio codeplug or hotspot configuration before flashing anything. On experimental firmware, read the release notes because some functions may still be incomplete.

    Step 3: Enter your callsign and RF settings

    Configure your amateur callsign, frequency, power, and any required channel-access settings. If a radio requires OpenRTX or hardware modification, verify that the exact model and band support both M17 transmit and receive before attempting an on-air test.

    Step 4: Configure the reflector and module

    Select a current M17 reflector from your software’s host list and choose a module. UDP port 17000 is commonly used by M17 reflector software such as mrefd, but it is configurable and is not a magic value that every server must use.

    For an ordinary hotspot or client, you generally should not start by opening inbound router ports manually. Most clients initiate outbound connections and receive replies through the existing NAT session. Only change firewall or port-forwarding rules when the documentation for your specific server or gateway tells you to.

    Step 5: Listen before transmitting

    Connect, confirm that the reflector/module shows the expected state, and listen for activity. When the channel is clear, make a short identification such as your callsign and that you are testing M17. Keep the first transmission brief so you can confirm that audio and routing are correct.

    Step 6: Test locally when possible

    Some reflector software provides a parrot or echo function. On mrefd, for example, a client can use a parrot destination to receive its own short voice stream back. This is an excellent way to check audio without repeatedly calling on a busy module.

    Common M17 problems

    • No transmit audio: a modified radio or external modem may not have the required flat baseband/data path.
    • Receive works but transmit does not: some OpenRTX targets have model- or band-specific TX limitations. Check the current support matrix.
    • Hotspot will not link: refresh reflector host files, confirm DNS and internet access, and verify the reflector name/module.
    • Wrong identity: make sure your amateur callsign is entered correctly; do not substitute a DMR Radio ID where an M17 callsign is expected.
    • Choppy audio: check RF level into the hotspot, frequency calibration/offset, packet loss, and CPU/network load.
    • An old tutorial disagrees with your screen: hotspot dashboards and M17 software change. Use the current project documentation rather than forcing an old menu sequence.

    What I corrected from the original draft

    The earlier draft incorrectly mixed IAX Direct and a supposed “D-Link” mechanism into M17. Those are not core M17 protocol features and have been removed. It also described 9,600 as a baud rate without distinguishing it from the 4,800-symbol-per-second 4FSK symbol rate, treated a DMR-style Radio ID as required M17 identity, claimed a specific reflector/module was the universal calling channel, and told readers to open UDP 17000 on their router as a general client requirement. Those points have been corrected.

    Bottom line

    M17 is one of the most interesting open digital-radio projects because both the protocol and its Codec2 voice technology are available for experimentation. The practical entry points today are a native M17 radio, an OpenRTX-supported radio, Module17 with a compatible 9,600-baud-capable transceiver, or an M17-capable hotspot/gateway. Start with current hardware support information, use your callsign, choose a reflector/module from a current host list, and test with short transmissions before building a more complex station.

    Primary references

  • D-STAR Made Easy: Step-by-Step Setup and Your First Contact

    Want to try D-STAR but aren’t sure where to start? You don’t need a complicated Internet setup just to make your first local contact. Start with a compatible D-STAR radio, find a nearby D-STAR repeater, enter your call sign, and make a local call. Once that works, explore worldwide gateway contacts and reflectors.

    What is D-STAR?

    D-STAR (Digital Smart Technologies for Amateur Radio) is a digital amateur-radio protocol developed by the Japan Amateur Radio League. Its digital voice (DV) mode works by radio directly between stations or through compatible repeaters. Internet-connected gateways can extend conversations to distant repeaters and networks. D-STAR is different from DMR and Yaesu System Fusion: a radio supporting one format does not automatically transmit the others.

    Step 1: Gather the essentials

    • A properly licensed amateur-radio operator and a D-STAR-capable transceiver. Examples include compatible Icom ID-series handhelds and mobiles and other radios specifically supporting D-STAR DV.
    • An antenna suitable for the chosen frequency and an adequately charged battery or power supply.
    • A nearby D-STAR repeater’s current frequency, offset, module/band, and access instructions, or a second D-STAR radio for simplex testing.
    • Your radio’s manual. Menu names vary by model, so use the manual rather than entering somebody else’s radio-specific settings blindly.

    Find a repeater using a local club or the D-STAR repeater directory. Confirm that it is actually operating and accepts local D-STAR traffic. A hotspot can be useful later, but it isn’t required for a local repeater or simplex contact.

    Step 2: Enter your amateur call sign

    In your radio’s call-sign settings, enter your own licensed call sign under MY or MYCALL (the exact label depends on the radio). Check every letter and digit. Digital transmissions include this call-sign information, but you must still follow your jurisdiction’s station-identification rules.

    Step 3: Start with a local D-STAR repeater

    1. Put the radio in DV (digital voice), not ordinary analog FM.
    2. If your radio offers DR (D-STAR Repeater) mode, open it and select FROM. Choose your nearby repeater from the radio’s list, updating the repeater database if needed.
    3. Set TO to Local CQ or the equivalent local-repeater option. Avoid choosing a distant gateway route until your local setup works.
    4. Verify the correct repeater frequency, offset and module from the local operator’s published instructions. Listen first to avoid interrupting an ongoing conversation.
    5. Make a brief call, such as: “This is [your call sign], testing D-STAR through [repeater call sign]. Can anyone give me a signal report?” Release PTT and listen.

    For an initial simplex test, both stations should use the same permitted simplex frequency and DV mode, without repeater routing. Check your local band plan before transmitting.

    Step 4: Register only when you’re ready for gateway features

    You do not need Internet gateway registration for direct simplex or ordinary local repeater contacts. For gateway routing over the Internet, registration may be required. If your local repeater participates in the US Trust system, follow its gateway registration link, request registration for your call sign, wait for the administrator’s approval, and complete any requested terminal or equipment information. Other networks have different procedures; follow your gateway administrator’s directions. Do not create multiple conflicting registrations.

    Official starting point: Icom’s D-STAR overview. Icom’s detailed manuals provide model-specific call-sign registration and gateway procedures.

    Step 5: Try a gateway contact or reflector

    1. After confirming that your gateway registration and local repeater routing work, select the local repeater in FROM.
    2. In TO, choose the radio’s gateway CQ, destination repeater, or reflector-link function supported by your repeater. Not every repeater supports every linking command; consult its published instructions and confirm the current reflector and module identifier.
    3. Listen before calling CQ. Once linked, make a short call including your call sign and location, then allow time for responses.
    4. Follow the repeater operator’s instructions for disconnecting or restoring its normal link when you finish.

    A personal D-STAR hotspot offers another path to Internet-connected conversations when there is no RF repeater nearby; hotspot configuration depends on the hardware and network and belongs in a separate tutorial.

    Common problems and easy fixes

    • No response? Verify DV rather than FM, the right frequency and offset, adequate signal, your MYCALL entry, and that the repeater is operational.
    • Local calls work but Internet routing fails? Check whether the repeater supports the chosen gateway network, whether your registration is complete and whether TO is set to the intended route.
    • Wrong destination? Return TO to Local CQ and confirm FROM points to the correct repeater.
    • Hotspot doesn’t connect? Check its Internet connection, configured call sign, network selection, frequency and radio’s DV settings without assuming that hotspot instructions apply to your local repeater.

    Your first D-STAR checklist

    Compatible radio? Correct antenna and band? MYCALL entered? Nearby active repeater? DV/DR mode selected? FROM set to your repeater and TO set to Local CQ? If so, listen and make your first call. Add gateway registration, routing, and reflectors one feature at a time.

    Further reading: Icom’s D-STAR FAQ and system introduction and D-STAR repeater directory.

  • From Mountain-Top Repeaters to Apps in Your Pocket: How Amateur Radio Learned to Link the World

    By NJ2RQ

    One of the most interesting stories in Amateur Radio is not simply how the radio itself evolved, but how hams learned to make one radio site talk to another. What began as a way to extend the range of a mobile or handheld signal became a worldwide web of repeaters, RF links, microwave paths, telephone interfaces, Internet gateways, digital reflectors, talkgroups, rooms, nodes and now smartphone applications.

    Today an operator can stand in a parking lot with a five-watt handheld, key a local repeater, enter a node number and come out through another station hundreds or thousands of miles away. Another operator can do nearly the same thing through D-STAR, DMR, Yaesu System Fusion, AllStarLink, a hotspot, or even an app running on a phone. To understand how we got here, it helps to start long before the Internet.

    The repeater idea came first

    Repeaters are much older than many operators realize. Experimental amateur relay stations existed on the old 5-meter band in the 1930s, and AM repeaters began appearing in the 1950s. The idea was simple: put a receiver and transmitter at a favorable location—often a hill, tower or tall building—so a weak mobile or handheld station could cover a much larger area.

    The real explosion came in the 1960s and 1970s with FM. Commercial land-mobile systems had already proven the value of channelized FM, and changing commercial channel requirements left large quantities of usable VHF and UHF equipment available as surplus. Hams converted that gear, developed duplexers and controllers, standardized repeater pairs and built networks on 2 meters, 70 centimeters and other bands. By the 1970s, the FM repeater had become one of the defining technologies of local Amateur Radio.

    A conventional repeater is still fundamentally local RF. You transmit on one frequency, the repeater receives you, and it retransmits your audio on another. Duplexers allow the receiver and transmitter to operate at the same site at the same time. A good location gives that modest handheld the coverage of a much larger station.

    Then repeaters started talking to repeaters

    Once clubs had reliable repeaters, the next question was obvious: why stop at one coverage area?

    Early linked systems used dedicated RF links, often on UHF or microwave frequencies, to carry audio and control signals between repeater sites. A city repeater could be tied to a mountaintop repeater, which could be tied to another site farther away. Statewide and regional systems became possible without asking every user to own a high-power station.

    Controllers became more sophisticated. DTMF touch tones could command links on and off. Autopatch systems let repeater users place telephone calls. Remote receivers, voting systems and microwave backbones improved coverage. In a sense, these systems were an early form of networking: RF sites were becoming nodes.

    The arrival of inexpensive Internet connectivity changed the architecture completely. Instead of leasing a telephone line or building a dedicated microwave path between every site, repeater audio could be digitized and transported as data. The Internet did not replace the repeater; it became another path between repeaters.

    IRLP and the beginning of Internet-era repeater linking

    One important bridge into the Internet era was the Internet Radio Linking Project, or IRLP, which began in the late 1990s. IRLP connected radio nodes through the Internet while preserving a radio-oriented operating style. It helped prove that reliable voice-over-IP could become part of everyday repeater operation.

    That concept opened the door for systems that were easier to access, more flexible and eventually usable from computers and smartphones as well as radios.

    EchoLink: the gateway that put the world behind a DTMF keypad

    EchoLink, developed by Jonathan Taylor, K1RFD, arrived in 2002 and became one of the most recognizable names in Amateur Radio VoIP.

    There is an important distinction here: EchoLink is best understood as a gateway system, not as a traditional RF link between two repeater sites. The Internet portion is carrying audio between authenticated EchoLink stations. A radio-connected EchoLink station provides the gateway between RF and that IP network. EchoLink identifies repeater gateways with an -R suffix and simplex RF links with an -L suffix.

    Every EchoLink station is assigned a unique node number. That number exists specifically so a radio user can control a gateway with DTMF tones. On a properly configured EchoLink repeater or simplex gateway, you can key your radio, send the DTMF digits for a desired node, and the EchoLink computer makes the Internet connection.

    Take WS2Q as an example. If WS2Q is operating as an EchoLink-accessible station or gateway, the live EchoLink directory identifies the station and its assigned node number. From an RF gateway that permits DTMF control, you can enter the node number and ask the gateway to connect. The exact control sequence can vary because sysops can customize DTMF commands, but the basic EchoLink model is simple: radio → local gateway → EchoLink network → distant node → radio.

    This was revolutionary because the user did not need to know IP addresses, server names or routing tables. A handheld and a numeric keypad could reach the world.

    D-STAR: digital voice designed for Amateur Radio

    D-STAR took a different path. The project grew from work by the Japan Amateur Radio League beginning in the late 1990s, with Icom helping turn the concept into working equipment. Unlike commercial systems later adopted by hams, D-STAR was conceived specifically around Amateur Radio digital voice and data.

    Its major advantage was that identity and routing were built into the system. Your callsign could travel with the digital transmission. Gateways could connect repeaters through the Internet. Reflectors allowed many repeaters and hotspots to meet in a common virtual space. Callsign routing made it possible to think in terms of reaching an operator rather than merely dialing a frequency.

    D-STAR also combined voice with low-speed data and location information, and the system included higher-speed data capability on 1.2 GHz. For hams accustomed to analog FM, it introduced a new idea: the repeater was no longer just retransmitting audio—it was participating in a digital network.

    DMR: commercial efficiency becomes an amateur worldwide network

    Digital Mobile Radio, or DMR, was first ratified as an ETSI standard in 2005. It was designed primarily for professional land-mobile radio, not Amateur Radio. That commercial origin is important because it explains both its strengths and its learning curve.

    DMR Tier II uses two-slot TDMA, allowing two logical conversations in one 12.5 kHz RF channel. Amateur operators adopted DMR radios and repeaters and then built enormous Internet-connected networks around them. Instead of simply linking repeater A to repeater B, DMR users select talkgroups. A talkgroup may be local, statewide, nationwide, worldwide or organized around a special interest.

    The result is extremely efficient and scalable. One repeater can participate in many different communities. The tradeoff is complexity: radio IDs, color codes, time slots, talkgroups and codeplugs can make a first DMR setup feel more like network administration than traditional FM.

    C4FM and Yaesu System Fusion: making digital migration easier

    Yaesu introduced System Fusion in 2013 using C4FM digital modulation. One of its most practical ideas was Automatic Mode Select. A compatible repeater could recognize analog FM or C4FM digital operation, helping clubs move toward digital without immediately abandoning every analog user.

    Through WIRES-X, System Fusion repeaters and nodes can connect over the Internet to rooms and other nodes around the world. For the operator, the experience is usually less dependent on manually building huge codeplugs than DMR. Digital voice, callsign information and data functions are integrated into the Yaesu ecosystem.

    System Fusion represents an important stage in repeater history: rather than replacing the analog repeater overnight, it offered a bridge where analog and digital users could coexist while the networking layer grew around them.

    NXDN: narrowband digital from Icom and Kenwood

    The correct name is NXDN. Icom and Kenwood began collaborating on the technology in 2003, announced it in 2005 and released the first conventional products in 2006. It was designed for narrowband land-mobile use and supports 6.25 and 12.5 kHz FDMA operation.

    Like DMR, NXDN came from the professional-radio world and later found an amateur following. Its narrow channel efficiency and strong commercial equipment heritage make it attractive, although its Amateur Radio footprint is smaller than DMR, D-STAR or System Fusion. It is another example of a recurring pattern in our hobby: professional communications technology becomes a new laboratory for amateur experimentation.

    AllStarLink: turn the repeater controller into an Internet PBX

    AllStarLink approached the problem from yet another direction. It is built around the open-source Asterisk telephone PBX and the app_rpt application. Instead of treating Internet linking as an accessory attached to a repeater, AllStar can become part of the repeater controller itself.

    An AllStar node may be a repeater, a remote base, a simplex node or a hotspot-style station. Nodes can connect to other nodes through VoIP, and DTMF commands provide control. The architecture is flexible enough to support large hubs, private networks and cross-links to other systems.

    AllStar is also known for very good audio when a system is configured well. Modern clients can use high-quality audio codecs, and because the network is carrying voice as IP data between nodes, the result can sound fuller and more natural than some heavily compressed digital-voice systems. That is not automatic—microphone level, RF deviation, codec choice, Internet quality and node configuration still matter—but a properly engineered AllStar path can sound excellent.

    PoC: when the “handy-talkie” starts using the cellular network

    Push-to-Talk over Cellular, usually abbreviated PoC, takes the familiar handheld-radio experience and moves the transport layer to LTE, 5G and Wi-Fi. The device may look and feel like an HT, complete with a side PTT button, loud speaker and rugged case, but the voice path is traveling through a cellular data network and a server rather than directly through an amateur repeater.

    The idea has roots in commercial push-to-talk cellular services such as Nextel and has matured into modern nationwide PTT systems. PoC devices can offer group calling, private calling, GPS, messaging and dispatch features over enormous geographic areas.

    For Amateur Radio, the interesting part is the user interface. Hams clearly like the immediacy of push-to-talk. PoC proves that the “radio experience” can exist even when RF is only at the cellular-network layer. That does not automatically make a PoC conversation Amateur Radio; the service, users and connection into amateur systems determine that. But the form factor is influencing how modern ham apps and network clients are being used.

    Zello: push-to-talk culture without a repeater

    Zello grew from an earlier product called LoudTalks and brought walkie-talkie-style voice to computers and smartphones. Press the button, talk, release and listen. That operating rhythm is instantly familiar to any radio operator.

    Zello itself is not an Amateur Radio repeater network. It is an Internet PTT platform. But it demonstrates why radio-style communication remains attractive even in a smartphone world. Groups can create channels, users can carry a Bluetooth PTT button, and the experience begins to resemble a networked HT.

    For hams, Zello is best viewed as a parallel development: it shows that the push-to-talk concept survived the transition from RF to apps and helped normalize the idea of carrying “radio-like” communications on a phone.

    RepeaterPhone: EchoLink and AllStarLink on Apple devices

    RepeaterPhone brings the concept back into the Amateur Radio networks themselves. It is an Apple-platform app for licensed operators that can connect to EchoLink and AllStarLink nodes. It provides a large PTT interface, directory searching, favorites, Bluetooth audio support and Apple Watch integration.

    As of this writing, RepeaterPhone is offered for the Apple ecosystem—iPhone, iPad and Apple Watch—not Android. For AllStarLink it supports high-quality audio codecs, which is one reason smartphone audio can be surprisingly good when the network path is configured properly.

    Think about how far that is from the 1970s repeater user. The old operator needed a radio, an RF path to the local machine and perhaps an autopatch. The modern operator can carry a network client in the same device used for maps, email and phone calls, yet still connect into repeater infrastructure built and maintained by hams.

    QSO One: the next step toward a universal amateur-radio network client

    QSO One is one of the newest developments in this story. Launched in 2026, it is designed as a modern client that brings multiple networks into one application. It currently supports Windows and Android, with additional platforms planned.

    The remarkable part is the scope: AllStarLink, EchoLink, IAX Direct, DMR, System Fusion and M17 are presented inside one software environment. That attacks one of the biggest problems created by decades of innovation—fragmentation. We gained many excellent digital systems, but each developed its own terminology, credentials, software and operating habits.

    If this model continues, the future operator may care less about which network is under the hood. The experience could become: choose the person, room, reflector, talkgroup or node you want, press PTT, and let the software handle the transport.

    So what is a repeater now?

    That question used to have an easy answer. A repeater was a receiver and transmitter on a tower.

    Now it may also be an RF endpoint in a worldwide network. It may route by callsign, node number, reflector, room or talkgroup. It may bridge analog FM into VoIP. It may accept traffic from a handheld, hotspot, computer or phone. A “node” may be a rack of equipment on a mountain—or an application running in somebody’s pocket.

    And yet the core idea has not changed at all.

    Amateur Radio has always been about extending communication beyond what one station could do alone. The relay operators of the earliest years did it manually. Repeaters automated it. RF links expanded it. The Internet globalized it. Digital voice organized it. Smartphones are now making it portable in a completely different way.

    Where the future is going

    The next phase will probably be less about inventing one more isolated network and more about connecting the networks we already have. Cross-mode gateways, software-defined radios, open protocols, better codecs, smarter routing and unified applications are already moving in that direction.

    There will always be operators who prefer a completely RF path, and there is real value in systems that continue working when commercial infrastructure fails. There will also be operators who enjoy worldwide linked systems, digital reflectors and smartphone clients. Those are not mutually exclusive versions of Amateur Radio. They are different layers of the same century-long experiment.

    From a converted commercial FM radio on a mountaintop to EchoLink node numbers, D-STAR callsign routing, DMR talkgroups, C4FM rooms, NXDN narrowband channels, AllStar nodes, PoC handhelds, Zello, RepeaterPhone and QSO One, the pattern is remarkably consistent:

    Hams find a new communications technology, take it apart, connect it to something else, and ask one question: “How far can we make this go?”

    Sources and further reading