If you’re getting “washed out” by your repeater ID, you definitely bought the wrong controller or have it programmed wrong. :-)
It shouldn’t be ID’ing as soon as it comes on the air, it should ID on the UNKEY event after the kerchunk. Some controllers are smart, some controllers are stupid… time to upgrade… Nate WY0X From: Repeater-Builder@yahoogroups.com [mailto:repeater-buil...@yahoogroups.com] On Behalf Of whensle...@comcast.net Sent: Monday, March 16, 2009 8:37 AM To: Repeater-Builder@yahoogroups.com Subject: Re: [Repeater-Builder] Repeater Kerchunk My thoughts would be... let it be. Do NOT let anybody know it may bother you. If they know it bothers you, they will keep doing it. As a long time ham I do kerchunk repeaters, especially my local one. Why? To check the status and cycle of the I.D. If the repeater has been inactive for a while, when it first transmits it sends its I.D. Since I don't want to be 'washed out' by the I.D., I kerchunk the repeater. Once the I.D. has finished, or the I.D. has not been sent, I will then put out my call to see if anybody's on the air. On the road, traveling... I will kerchunk a repeater to see if I can reach it. There's also the other side of the coin to this. You think kerchunking is bothersome? How bothersome is it to be mobile, you bring up a repeater, and you try to use it. You try several times putting your call out there. Several miles later, several attempts later, you discover your audio wasn't getting through. The repeater's "ears" weren't as good as its mouth. Give me kerchunking any day over that. 73, Kim - WG8S
