--- In [email protected], Nate Duehr <[EMAIL PROTECTED]> wrote: ... > Do users REALLY remotely command remote repeaters they're not even > on? Really? Mine don't, but we'd never program anything to do > that... other than "features" like an autopatch or a remote base (we > don't have any of those around here, really), or an internet link or
That's the problem. Most of the large systems Ed and I have been talking about are remote bases. The commands a "user" would send to the system would turn the remotes on and off, select frequencies, antennas, PLs, etc. > something like that. But standard repeater controls -- like PL? > Nah. What for? > Consider a network of dozens of linked repeaters which are linked *BUT NOT ON LINK* 24/7. i.e. the repeaters have more than one link and the links are connected to each other 24/7 but the repeater itself is normally separated from the links unless someone is using the link. When you want to talk to a friend in another area you would prefix his system and then command it to connect to the link and then call him. If he doesn't answer you'd probably return his repeater to it's normal operating condition by turning the link back off. You're right you probably won't blindly turn the repeater PL on or off. But if the repeater was on link in carrier squelch and grudge was hitting it's input you certainly might turn PL on! (And be damn happy you knew the command code since it was the same one your local machine uses). 73's Skip WB6YMH
