Hello, I guess it's my history from my days in a two way radio shop, I think everything needs CTCSS encode and decode on it unless there is a control operator that has it disabled on a temporary basis. The only down side that I can see is people that don't have a repeater directory in front of them would not be able to talk on the repeater. A ID with a voice announcement about the CTCSS tone frequency would/and is going to fix that problem on my repeaters. My 2 meter and 440 machines do not have a CTCSS disable and both send out CTCSS tone that is muted with COS in the repeater hang time.
Paul -----Original Message----- From: Q [mailto:[EMAIL PROTECTED] Sent: Friday, December 03, 2004 7:29 PM To: Repeater-Builder@yahoogroups.com Subject: Re: [Repeater-Builder] Requiring CTCSS Or do like I do,encode 71.9 and decode 141.3 just to confuse the automatic feature in most riceboxes! Seriously folks,this is the 21st century! If your radio wont encode AND decode CTCSS,you are behind the times. It is a necessary evil when the bands get crowded.There are no available 2 meter pairs within 100 miles of any population center around the Great Lakes.... Jeff Otterson wrote: >Hey! That's pretty funny. > >I remember driving to work one day, and hearing a same-channel distant >repeater after the local repeater dropped, due to a band opening. So I >turned off my tone encode (so I would not bring up the local machine) and >had a QSO on a repeater 200 miles away. > >If they had tone access, I would not have gotten in at all. > >On the other hand, if they had tone access, my QSO through the local >repeater would not have interfered with their system. > > > > > > Yahoo! Groups Links Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/Repeater-Builder/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
