Interesting reply given my statement "Granted, the TOC could false a 131.8 Hz decoder"
You're describing a problem that may exist regardless of the dual CTCSS/CDCSS encode (the topic of this thread). Also note that it will still not interfere with each other. There will merely be a 'kerchunk' of the 131.8 Hz decoder from the 134 Hz (not 131 or 132 Hz) TOC of the CDCSS. Oh, and it would be just as annoying for hams as for business users. Joe M. Steve S. Bosshard (NU5D) wrote: > > It would be a problem my friend because the 132.0 will cause the > repeater to decode 131.8 during the turn off interval and ker chunk that > tone briefly, with out any reverse burst. > > When the DPL radio releases the PTT it does not immediately quit > sending, but instead sends a burst of 131 hz turn off code. If your > panel is equipped for 131.8 it will ker chunk just a moment - no problem > for hams, but on a business repeater the 131.8 guy will get annoyed. > Wish I could remember if TOC is 131 or 132 - the data rate is 134, but > thats another story - Seems like Ferritronics had an application not for > this, if they were still in business. > > Have your self a super 4th, Steve NU5D > > mch wrote: > > A problem? Why? > > > > When the turn-off code is sent *after* you have unkeyed. Who cares what > > stops decoding after you've stopped transmitting, as any decoder should > > stop decoding then. > > > > Granted, the TOC could false a 131.8 Hz decoder, but not while the > > person is transmitting. > > > > Joe M. > > > > Steve S. Bosshard (NU5D) wrote: > > > >> The DCS turn off code is 132 hz. So, 131.8 hz ctcss and dcs could be a > >> problem. > >> > > > > > > > Yahoo! Groups Links > > >
