Designing a Two-Way Radio System

Two-Way Radio Concepts and Electronics Fundamentals · Last updated · About 4 min read

The decision sequence for designing (or evaluating) a professional two-way radio system, with links to the detail pages each decision depends on. Written for system designers and for anyone who needs to understand why a system was built the way it was.

1. Requirements Before Radios

Every defensible design starts from answers to these, written down:

  • Coverage: where must radios work — a building, a campus, a county? Indoors (in-building penetration is the hard case) or outdoors? Mobile-to-mobile, or always through infrastructure?
  • Capacity: how many users, in how many workgroups (talkgroups), talking how often? Peak-hour behavior matters more than averages.
  • Users and devices: portables vs. mobiles, environmental ratings (IP/MIL-STD), hazardous-location needs (intrinsically safe).
  • Features: voice only, or GPS/AVL, text, emergency alarms, encryption, phone interconnect, dispatch consoles, logging?
  • Interoperability: with neighboring agencies (mutual aid), with a phone system (integration), with remote PC/mobile users (RoIP)?
  • Constraints: budget, existing licenses, existing fleet to migrate, mandated standards (public safety usually means P25).

2. Pick the Technology Family

  • Business/enterprise/industrial → DMR (MOTOTRBO) or NXDN (NEXEDGE) — cost-effective digital voice + data. See Analog vs Digital Radio for migration framing; new systems are digital by default.
  • Public safety / mutual-aid-driven → P25 (ASTRO 25 at Motorola) — interoperability and mission-critical features at a mission-critical price.
  • Coverage-anywhere without infrastructure → consider PoC/broadband PTT as a complement (not an LMR replacement — carrier-dependent).
  • Band choice — VHF (rural/terrain-following), UHF (buildings/urban), 700/800 MHz (public-safety trunking) — is usually settled by propagation environment plus what's licensable in the area (FCC licensing, frequency coordination).

3. Architecture: How Much System Do You Need?

In increasing order of cost and capability — see Anatomy of a Two-Way Radio System for the same ladder in more detail:

  1. Simplex — radios direct, no infrastructure. Small crews, small sites.
  2. Single conventional repeater — the workhorse. One channel, real coverage. See Repeaters and Antennas Basics.
  3. Multi-channel conventional — more channels for more groups; users pick channels manually.
  4. Wide-area conventional over IP — IP Site Connect-style linking: same channel across multiple sites, radios roam between sites (each site on its own frequencies — this is not simulcast).
  5. Trunked — a channel pool shared automatically: Capacity Plus (single site) → Linked Capacity Plus (multi-site) → Capacity Max (large multi-site); NEXEDGE Type-C/Type-D; ASTRO 25 for P25. Trunking pays off when talkgroups outnumber what conventional channels can carry politely.
  6. Simulcast and voting — same-frequency multi-site coverage and talk-in balance for demanding coverage footprints (mostly public safety; adds GPS timing and comparator infrastructure).

Capacity sanity check: rough-size channel counts from users × calls-per-hour × call length; digital two-slot TDMA doubles voice paths per repeater (TDMA vs FDMA). If GPS/data volume is significant on MOTOTRBO, plan revert channels / Enhanced GPS explicitly — data load is the classic silently-underestimated item.

4. RF Engineering

  • Coverage prediction (propagation models, link budgets) before hardware; drive-test after (RF site surveys).
  • Site engineering: antennas and feedline (Repeaters and Antennas Basics), duplexers/combiners, co-location interference (desense, PIM), grounding, surge protection, backup power (batteries, generators), shelters/HVAC.
  • Backhaul between sites and to dispatch: options and requirements — simulcast/voting have far stricter timing needs than RoIP/console links.

5. The IP Layer

Modern systems are IP systems with radios attached. Plan: addressing/subnets (IP networking in radio systems), QoS for voice, latency/jitter budgets, remote access (port forwarding vs VPN — and CGNAT realities for cellular/satellite-connected users), NTP, and monitoring (SNMP, syslog).

7. Fleet Engineering

The soft infrastructure that makes or breaks daily use: fleetmap design, radio IDs, codeplug standards and programming workflow, firmware policy, scan and programming parameters, accessories and batteries, user training (etiquette).

8. Lifecycle

License renewals, maintenance contracts, spare-parts strategy (especially for anything discontinued — e.g., Connect Plus systems), a documented as-built (frequencies, IDs, IP plan, fleetmap), and a growth path: the best designs choose an architecture whose next step up is an upgrade rather than a replacement.

Common Design Mistakes

  • Sizing coverage for vehicles and forgetting portable, on-belt, indoors — the weakest real use case.
  • Ignoring talk-in (portable back to site): transmit coverage from a tall site is easy; hearing a 3-watt portable is what voting receivers exist for.
  • Treating data/GPS as free capacity on voice channels.
  • Skipping frequency coordination realities until late — available spectrum shapes the design more than brochures do.
  • No named owner for the fleetmap/codeplug after cutover, so the system decays one ad-hoc change at a time.

References

See also: CTI product documentation

This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.

Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.