Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Repeater access, CTCSS tones and linked systems: where do new users usually go wrong?

ci_cover.jpg

I'd like to collect the practical points that trip people up when they start using FM repeaters, especially now that so many repeaters are tied into linked networks. The basics are easy to state. You set the output frequency, the offset and direction, and a tone. Then you listen before you talk. In practice, though, the details differ from one system to the next.

The first problem is the tone. A new user programs a repeater from a directory, hears the repeater fine, keys up and gets nothing back. Often the cause is the tone setting. Some radios call the mode "Tone", which only encodes CTCSS on transmit. Others call it "TSQL" or "Tone Squelch", which encodes on transmit and also requires the tone on received audio. Some repeaters need a tone on the input to open them but send no tone on the output, and some send a different one. Directory entries are also sometimes wrong or out of date.

The second problem is linking. When a repeater is connected to others by RF links, IRLP, EchoLink, AllStar or a digital reflector or talkgroup, the timing changes. There can be extra delay, longer squelch tails and a change in who is actually listening. A pause that feels long on a standalone machine may be about right on a linked one.

The third is plain etiquette: kerchunking, over-long transmissions, IDing, and when to move to simplex. Everyone seems to have a slightly different idea of what counts as polite.

What would you tell a new user to check first when they can hear a repeater but can't get into it? And how would you explain linked-system manners without making it sound like a rulebook?

  • Replies 2
  • Views 58
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

For access problems I'd go in this order. First, confirm the input frequency. Check the offset size and the direction (+ or −), because on a repeater with a non-standard split the radio's automatic offset can be wrong. Second, check the tone you're transmitting. Third, check whether your radio is also decoding a tone on receive. If you have TSQL on and the repeater's output has no tone or a different one, you'll hear silence even though the machine is working. If you're unsure, turn off tone squelch while you troubleshoot, so you can at least confirm you hear the repeater.

Most radios also have a reverse or input-monitor function. It swaps your receive frequency to the repeater input. If you can hear the other person well on the input, you're probably in direct simplex range and could move to a simplex frequency, which frees the repeater for people who need it.

It also helps to know that CTCSS is sub-audible tone signalling, normally in the range of roughly 67 to 254 Hz. It is not a privacy feature. It only controls which signals the repeater, or your receiver, will act on. Many repeaters use it to keep out interference and distant co-channel signals. Some systems use DCS instead, which is a digital code rather than a tone, so check which one the owner specifies. When in doubt, the listing from your local coordinator or the repeater owner's own page beats a generic directory.

  • Moderators

On linked systems, the biggest habit to build is leaving a gap between transmissions. Wait a second or two after the other station finishes before you key up. That gives anyone who wants to break in a chance, and it gives the link time to drop and reset. It also helps to key up, wait for the repeater to come up, and then start speaking. Otherwise the first word or two get cut off, and the fix is not to talk louder.

Keep each transmission short, and remember the audience may be bigger than it sounds. A linked repeater can reach other cities or countries, and some nodes may be running a net or a scheduled event. If the system has a stated purpose, such as a regional net, an emergency-communications resource or a social chat, follow that. If you're just testing, say your callsign and that you're checking in. Saying "test" and then hanging on the key does nothing useful. You don't need to call CQ on a repeater either. Giving your callsign and saying you're listening is enough, and so is a general call like "anyone around for a chat".

Identification rules depend on your country and licence, so check your own regulator's requirements. In many places you must identify at intervals and at the end of a contact. Also, a repeater's timeout timer is not a target. If you keep hitting it, you're probably talking too long. Finally, if the owner or control operator posts rules about courtesy tones, hang time, link behaviour or open versus closed access, follow those even if they differ from what you're used to elsewhere.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.