Ken Arck wrote: > Unless the IRLP connection is made directly to one of the Ports. Then > CTCSS is irrelevent.... > > <---Actually, I want to clarify this a bit. If he plans on using a > radio link between the controller and IRLP Node itself, CTCSS control > is still irrelevant as we're not dealing with a repeating radio > therefore there should be no hang time. In which case, the link xmtr > can encode continuously without any "outside" control needed.
Not true, that transmitter needs to be ID'ed. To keep that ID from being "heard" by the receiver at the IRLP node, CTCSS control is required. (Or other cheesy solutions like audio notch filters, but even then you have "quiet" key-ups being seen by the IRLP receiver, which isn't "right" either.) > Then all that matters is that the controller controlling the link > radio (at the repeater end) doesn't pass IDs or courtesy tones down > the link. And just about any controller will do that properly. One *must* ID the transmitter on the link radio toward the IRLP node and away from it both, for it to be a legal link. Away from it's easy, just mix in the CW ID's at the soundcard of the node, but from the repeater down to the node, you gotta jump through hoops. If you want it "done right" anyway... Nate WY0X
