In fact, this is usually more helpful since it's the offending TX they are looking for. IF you have multiple IDs, how do you know which TX is causing the interference?
If each TX ID is unique to that TX, you know which one it is. This is also an issue with multiple repeaters TXing the same callsign. "I heard callsign W3XYZ getting into our repeater last night". If there are 10 repeaters using that callsign, it's not all that helpful. Joe M. Nate Duehr wrote: > > On Nov 8, 2007, at 7:39 PM, John Barrett wrote: > > > besides the fact that a person using a repeater is still bound to > > the 10 minute ID rule, so some of the input must be mixed to the > > output or the user would never be heard to ID on the output while > > the patch was in operation. > > Another fun debate topic: I'm required to ID my transmitter. I'm NOT > required to be heard through the repeater's output, however. Just > from a legal point of view. :-) > > Example: If a repeater requires CTCSS access, and I unkey every 10 > minutes, turn off my CTCSS encoder and ID, and then turn it back on > and start talking again... no one listening to the output will think I > ever ID'ed properly -- but it's 100% legal. > > (In fact many repeater linking systems take advantage of this > particular example to suppress having multiple ID's showing up on all > the linked repeater outputs.) > > Of course, if such a practice by a user were to trouble a repeater > owner/operator, the FCC almost always sides on the side of the > repeater trustee if a trustee has published additional rules for using > their system and asked any Amateur not complying with those rules, not > to use the system. > > -- > Nate Duehr, WY0X > [EMAIL PROTECTED] > > > Yahoo! Groups Links > > >
