I apologize guys, I guess I am just from the old days when all you needed to worry about was frequencies and talkgroups when programming trunked systems I didn't even know what RFSS was until recently. Anyway I did submit the correction to radio reference.
Excellent. Thanks.
BTW - the nice thing about Unication using more than just the frequency is that it gives you more control over which site(s) you might allow your Gx to try to find and monitor... this is particularly important on large (e.g. statewide) systems where there is lots of frequency reuse. I'd encountered situations for NC VIPER where the area seems like a dead zone. I had the entire system programmed into my G5 and the radio tried so hard, it ended up locking onto a site that was almost 60 miles away (the radio tells you which RFSS/site is currently receiving).
Additionally, these little radios can pick up signals at fairly long distances and in some places there is even frequency reuse in other states not that far away (probably not an issue in central Florida but a big deal in small states). In fact, for a time, there were two systems in Maryland (one state and one county but with towers at opposite ends of the county) in the same county that were using a common 700mhz frequency. On the scanners, it appeared that county talkgroups were appearing on the state system -- but only because none of the scanners used the system parms to keep them separate (note: I believe they've recently swapped out that common frequency).
The nice thing is that users have the option to use the actually values or simply wildcard...
