What are the best settings? Should I use multisite roaming? Not sure if or how I should program in the entire state system so all I need to do is add talkgroups when needed. Scanners and radio systems have come a long way since the last time I programmed a scanner. Any help would be appreciated.
I'd recommend using Win500 for the programming task itself (
Win500: PSR-500, PSR-600, PRO-106, PRO-197, PSR-310, PSR-410 Scanner Software for Data Management, Monitoring, and Control ). It will allow you to tweak just about every knob on the radio, and makes the site programming a lot easier.
You'll no doubt get lots of advice from the folks down in the Springs about what you'll need to program specific to the area, but thought I'd pass along some 'generic' thoughts on managing this incredible DTRS mess we have here in Colorado. Having started with one approach a few months back, I opted for a whole new approach a couple of weeks ago... all due to that 'multisite roaming' business you mentioned. I suspect there are other options that I haven't considered, but the following two seem to be the two major ways to slice and dice this project. (and FWIW, unless you resort to the "v-scanner" approach, "Colorado" is too much to hold all at once - you'd need to pare that down a bit). It's getting the DTRS down that's important. The conventional stuff is easy to add on top of that.
The question that may drive the approach -- a) how many DTRS sites am I going to have to deal with, and b) will I run out of scan list numbers as I assign one to each 'agency' of listening interest? (there are only 20) It's hard enough to flip through the scan lists while you're driving -- trying to keep track of and selection of new v-scanners while driving isn't so trivial.
The first approach is to program a TSYS for each major DTRS site that you'll need for coverage of the agencies you want to hear. The TSYS contains only the control channel information for that one site. Within that TSYS, you then add the talk groups of interest that affiliate with that site, and assign each talk group to a preferred scan list. You will, of course, be listening by scan list in any case. You'd create a scan list for each geographic area and perhaps break that down into one for FD/EMS and one for LEO. Each of those will have several talk groups of their own. For example, the local LEO may have a couple of dispatch talk groups and a couple of tactical talk groups. So scan lists might be 1 = townA LEO, 2 = townA FD/EMS, 3 = townB LEO, 4 = townB FD/EMS. One scan list per area per major 'agency' or activity or whatever you want to call it. Repeat with more TSYS because your agencies will be hitting more than one DTRS site. When you scan, the scan list controls which sites are being scanned since the scan list number(s) that you select will only appear within certain of your TSYS lists, and hence, only on certain sites.
Plan B: Set up TSYS by agency of interest. The TSYS contains information only for a specific scan list rather than information for all talk groups on the DTRS site as was done above. So in this case, townA's LEO talk groups all appear in their own TSYS. And this time, you program in not just one site's control channel frequency, but instead, all of the control channel frequencies for sites with which the agency in question might (within reason - these guys do wander around the state at times) affiliate. Could be as many as three or four of them for good coverage. THAT provides a convenient way of setting up the 'roaming' feature that you mentioned. Since all of an agency's talk group entries are within one TSYS, it's easy to set up roaming within a single TSYS by setting thresholds for that TSYS. As the scanner is being confined to that TSYS by the scan list selected, the scanner will cycle through the control channels (DTRS sites) assigned to that TSYS if necessary, looking for one that's good enough in a given moment per your threshold criteria. In essence, the radio attempts to keep 'listening' to your agency of interest by dumping one site in favor of another if the quality drops sufficiently on one DTRS site to force it to look for a better one.
The "roaming" feature seems to work OK, but I'm still struggling to decide what the appropriate decode thresholds are for a PRO106/PRO197 radio.