SLR5500 peer doesn't repeat without master

[Zaarin]

So, this may be a stupid question.

I was setting up an IPSC system with two repeaters and a TRBONet radio server the other day. Radios were roaming fine between repeaters in the shop when I turned one off and left the other on. What surprised me is that if I turned the peer on with the master off, it wouldn't repeat any of the calls from the radios. The RX LED didn't even light up. If I left the master on while turning the peer on, let the communicate for a bit, and then turned the master off, the peer would repeat just fine. Is this normal behaviour? I've set up IPSC systems before, but I haven't bothered to test this specifically as I just assumed a peer without a master would just function as a stand-alone repeater.

One thing that occurred to me afterwards is that I had RAS enabled, but I programmed the key and accepted ID ranges into both repeaters even though the system planner says I only need to do that for the master. Perhaps the peer ignores its own RAS setup and when it fails to grab the master's, it just gives up and refuses to repeat anything? If that's the case, someone at Motorola's ****ed up.

-Z

 

[com501]

A peer must see the master for it to work. If the master goes offline, the peer(s) will continue to operate together because the 'route' is memorized. Adding a peer to a system when the master is down will not connect the peer until the master talks to it once so that the peer has a routing table to work from.

Your description is normal operation.

 

[Zaarin]

Yeah, I get that the peer won't be able to forward incoming transmissions to rest of the system if it's never gotten the peer list from the master, but it's still programmed with its own channel so why shouldn't it be able to repeat transmissions from and to radios within its own coverage area?

->

 

[Mars]

The RAS key comes from the master. When the master is down, and you cold boot, it will not work until it can cache the RAS key.