WS1080: TRS long scan time with no CC data

[OregonScanner]

If a trunked system is enabled but there is no control channel present the radio takes a while to scan through the system before it moves on. It takes about 3.5 seconds per P25 or Motorola system and 2 seconds per DMR system that doesn't have any CC data (like creating a DMR system for a conventional repeater). Even if there is only one site in the system and even if there is only one frequency in the site.

Here's how you can replicate what I'm talking about:

1) Program in a trunked system with only one site that is either made up or an actual one you are out of range of and are not getting any CC data for or setup a DMR conventional repeater as DMR trunked and assign this to a scanlist.
2) Program in a NOAA Weather freq that is very strong and assign it to a scanlist.
3) Scan only the trunked system and the NOAA Wx freq.
4) When the scanner stops on the NOAA Wx freq, press the right arrow key on the kepad to force the scanner to resume scanning and you will see that it takes the radio about 3.5 seconds for P25 and Motorola systems before it stops on the NOAA Wx freq again. About 2 seconds for a DMR system. Also there are some systems that I monitor on the fringe of their coverage area and so reception goes in and out.

Messing with the system hold time does not change this. I would like to create one scanlist per county and assign the TGs from trunked systems in each county to each county's scanlist along with conventional freqs. Some trunked systems have a small footprint and don't have coverage all over a particular county. So that means I have to either put up with long scan times or I have to have different scanlists for trunked systems and remember to turn them on or off. Uniden and even my old RS PRO-106 will rapidly scan past sites with no control channel data. The radio should not spend that much time scanning a trunked site with no CC data. Anyone know why this is happening? Am I missing something in the programming software?

For my 536HP and 436HP I create a favorites list for each county and put all the trunked sites that have coverage in a particular county in that favorites list and if I'm out of range of a trunked site or I have a bunch of DMR one freq trunked systems that don't have any traffic on them, the radio just scans past them really fast. These radios are better for monitoring a system on the fringe of its coverage area because if I don't get any CC data the radio just scans past the system fast.

 

[AggieCon]

I've experienced similar. I do not know a work around other than that you are right to have only one site and frequency per system.

Unless they are really slow systems. I recommend scanning just one trunked radio system at a time per scanner. Perhaps 2 if they are slow.

I do not mix conventional and trunked on the same scanner.

Importantly, always program trunked radio systems in their own scanlist or scanlists so they can be turned off independently. I do not recommend mixing conventional frequencies and trunked talk groups on the same scan list.

I presume by hold time you meant the "Dwell" time not the "delay" setting?

Great testing setup you describe, by the way. Thanks for sharing.

 

[darunimal]

you can add a dummy frequency and or close the Data Decode Threshold to higher and tighter values for one site and open the other up 15-95, adding a dummy frquency every other site can help something like 1000mhz or something not used locally

as well as check your squelch knob on the top