Repeater access, CTCSS tones and linked systems: where do new users usually go wrong?
- Replies 2
- Views 58
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Lee 1 post
-
Mod_Chrissy 1 post
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
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?
Link to comment
https://www.hamradiobase.com/forums/topic/10752-repeater-access-ctcss-tones-and-linked-systems-where-do-new-users-usually-go-wrong/Share on other sites