Repeater Controllers
Using Repeaters
A repeater controller is the brain of a repeater system. It manages the repeater's behavior — when to transmit, how to identify, what tones to play, and how to respond to commands. Without a controller, a repeater is just two radios passing audio back and forth with no intelligence.
What a controller does
- Station identification: the FCC requires repeaters to identify with their callsign at least every 15 minutes during use and at the end of each communication. The controller handles this automatically, transmitting the callsign in CW (Morse code) or synthesized/recorded voice
- Courtesy tone: a short beep played after each user's transmission ends. This signals to other users that the repeater is ready for the next transmission and provides a brief pause for others to break in
- Timeout timer (TOT): limits how long a single transmission can last — typically 3-5 minutes. If someone accidentally sits on their PTT button or gets long-winded, the timer cuts them off. This protects the repeater's transmitter from overheating
- CTCSS/DCS decoding: some controllers handle tone squelch decoding rather than relying on the receiver radio, giving more flexibility in access control
- DTMF command processing: lets authorized users control the repeater remotely by sending DTMF tones from their radio. Commands might include enabling/disabling the repeater, adjusting settings, or activating linking
Basic vs. advanced controllers
Controllers range from simple to highly sophisticated:
- Basic controllers: handle ID, courtesy tone, timeout timer, and CW identification. These are affordable and sufficient for most GMRS repeaters. Some are small enough to fit inside the repeater radio housing
- Advanced controllers: add features like voice synthesis, multiple access levels, weather alert integration (NOAA weather radio rebroadcast), EchoLink or AllStar linking support, telemetry monitoring (temperature, voltage, battery status), and remote diagnostics via phone or internet
For a first repeater, start simple. A basic controller that handles ID, courtesy tone, and timeout is all you need. You can always upgrade later as you learn what features you actually want. Over-engineering the controller before the repeater is even on the air is a common way to stall a project.
CW vs. voice identification
The FCC requires identification but doesn't specify the method. The two common approaches:
- CW (Morse code): the controller sends your callsign in Morse code. Simple, reliable, and uses very little bandwidth. The traditional choice. Most listeners recognize it as the repeater IDing and tune it out
- Voice ID: the controller plays a recorded or synthesized voice announcement with your callsign. Sounds more professional and is easier for casual listeners to understand. Requires more controller capability
DTMF remote control
Most controllers accept DTMF commands from authorized users. Common remote-control functions include:
- Turning the repeater on or off
- Enabling or disabling linking to other repeaters
- Changing the CTCSS/DCS access tone
- Requesting status information (battery voltage, temperature)
- Playing pre-recorded announcements
Access to DTMF commands is typically restricted by a PIN code or access level programmed into the controller. Only the repeater owner and designated operators should have control access.
Integration with a repeater system
The controller sits between the receiver and transmitter radios. Audio from the receiver passes through the controller, which decides whether to retransmit it based on squelch, tone, and timer settings. The controller adds the courtesy tone and ID before passing audio to the transmitter. For more on building a complete repeater system, see Setting Up a Repeater.