My question is for the 396. Will the radio scan through all talkgroups even if it cant lock onto a control ch? The reason I ask is when scanning the display seems to pass over systems that are out of range, But in the event it still goes through the list of tg's I dont want to leave them active when I know they are out of range (nothing like scanning 50 tg's you know you cant get, vs the radio just checking one cc each time around).
Trunk Systems out of Range
- Thread starter ems170
- Start date
- Status
No, it should look for the control channel first, then if it's not active, move on to the next system. If you hold on an inactive system and scroll to a talkgroup, you should see it display finding control channel until it finds one.
duped, post.
"Will the radio scan through all talkgroups even if it cant lock onto a control ch?"
The radio never scans through all the talkgroups, regardless of the control channel.
When it gets a control channel, it checks every talkgroup that it receives on the CC and if it is in your scanlist - you hear it. It does not scan each talkgroup.
The radio never scans through all the talkgroups, regardless of the control channel.
When it gets a control channel, it checks every talkgroup that it receives on the CC and if it is in your scanlist - you hear it. It does not scan each talkgroup.
So in your opinion would you agree that the radio passes over out of range systems faster than if a cc is detected. In my case there are about 10 trunked systems in my state all but one are isolated to single cities. Each one only has between 1-3 possible cc's. How signifigant would the delay be if I just left all out of range systems active vs disabling them?
rdale said:
Unless you use ID Search
ems170 said:
You can do that, it would slow the time between systems while it checks for the control channel, and if you have more than just the control channels programmed in the system, it will check each frequency for a control channel.
DaveIN said:Unless you use ID Search
Incorrect - it never scans all talkgroups. Talkgroups don't operate like frequencies do when it comes to scanning...
rdale said:
When you use ID Search it looks for *all* talkgroups from that control channel, unlike ID Scan where it looks for ID's in you scan list.
• ID Scan – the scanner only stops on talk group
ID’s that you have programmed into the system
• ID Search – the scanner stops on any unlocked
talk group that becomes active.
Last edited:
You aren't following this thread correctly, and giving out what could be read as incorrect information.
He is worried that if the scanner is out of range, it will still "scan" the talkgroups and waste time. The scanner never "scans" the talkgroups like it scans conventional frequencies, so if it is out of range of the control channel it is not taking up time to scan.
He is worried that if the scanner is out of range, it will still "scan" the talkgroups and waste time. The scanner never "scans" the talkgroups like it scans conventional frequencies, so if it is out of range of the control channel it is not taking up time to scan.
LarrySC
Member
Our state has 62 towers. Most everone PGM's at least 3 towers for whatever talkgroups they have. People that travel up and down the interstate may have have 10 or more towers. These may be in one or more banks. The scanner does not do anything unless it locks onto the controller. Therefore it does not slow down to run thru your list, unless it locks onto controller.
Thank you all very much for your help on this issue.
jonny290
Member
LarrySC said:
On a motorola system, for example, do you just punch in all the possible frequencies? I was wondering if I'd have to program a new System for each tower site (and frequency set) for our statewide p25 system.
jonny290 said:
If your using the 396 or 996, just the control channels (and possible alternates) are needed for control channel only.
whacker
Member
When I enable (with Quick Key) trunked systems that are out of range, and am also monitoring other systems, the scanner doesn't even show that system's name unless it detects a control channel (unless it is the only system enabled). Makes sense to me.
- Status
