If you use FF for the RFSS and Site, you will roam to any other available site when your signal drops below a certain threshold...as long as you have the control channel for those other sites in your frequency list. What you should be doing it using the actual RFSS and Site numbers. So if you want to automatically roam to Ramapo when getting out of West Orange coverage areas, program both sites control channels (and alternate controls), then under the site list you would have two rows, RFSS 1 Site 1 Alias West Orange and RFSS 1 Site 22 Alias Ramapo.
For example, I always hear Newark Fire and Elizabeth talkgroups on both West Orange and Union Simulcasts. So, I have one system as NJICS WO/UC. I have both those sites programmed in, and the I have all those talk groups assigned to a knob position labeled NEWARK/ELIZ. So as I drove all over Passaic, Bergen, Essex, Morris, Union etc Counties, I never lose reception and hear everything as it switches between Sites 1 and 7. Now I’d obviously have much better coverage in Oakland, NJ with Site 22 (Ramapo) programmed in and it could easily roam to that site. But those talkgroups hardly ever appear on that site. So if I allow it to switch, yes I’ll have a great signal BUT I won’t hear a peep. You have to know what sites carry what traffic “on a daily basis.”
Now let’s say you ONLY want to hear one site. I have another “system” as NJICS WO. It’s is only the West Orange Site. As you see I have it as a separate system completely. I assign that to a knob position and then add NJSP talkgroups such as B2-4 for Netcong/Totowa and B2-14/B2-15 for Turnpike and GSP North. The reason I don’t add other sites is because if it roams to another site, I won’t hear those talkgroups.
Sent from my iPhone using Tapatalk
