How long do the Whistler scanners take to scan a control channel on a trunked system?
slow scan
- Thread starter Mason69
- Start date
How long do the Whistler scanners take to scan a control channel on a trunked system?
- Joined
- Jan 5, 2003
- Messages
- 14,062
- Reaction score
- 9,913
- Location
- Retired 40 Year Firefighter NW Tenn
If I remember correctly, on my TRX's Frequencies, Systems take the most time with looking up TG's to see if it is on the list and who it is not taking as long.
no it doesn’t. the only thing that adds scan time is how many entities you have programmed. such as trunked systems, take more time to scan because it has to scan all the tgrp’s and sites. it scans conventional frequencies faster because it doesn’t have to scan anything extra.
- Joined
- Jan 5, 2003
- Messages
- 14,062
- Reaction score
- 9,913
- Location
- Retired 40 Year Firefighter NW Tenn
So you are an expert after Whistler Support told you.
what’s your problem dude i was just telling him chill out you are literally no help ever
- Joined
- Jan 5, 2003
- Messages
- 14,062
- Reaction score
- 9,913
- Location
- Retired 40 Year Firefighter NW Tenn
Dude the problem is you cannot help yourself and you are trying help others where you should be learning not trying help at this point in you have no idea how things work.
Programming Alpha Tags does NOT add to the scan time.
Please post your configuration for review
Please post your configuration for review
well i was right wasnt i? 😝
My TRX_1 file.
Any changes to make it better please advice.
Daleb49, try this. You had several talkgroups set to Priority that could have chipped away at the time it took to complete a full scan of your configuration.
I removed all the Priorities then resaved and attached to this post.
Please upload this Daleb49.zip file to EZ Scan then to your TRX-1 and let me know if this addresses your scan speed.
I removed all the Priorities then resaved and attached to this post.
Please upload this Daleb49.zip file to EZ Scan then to your TRX-1 and let me know if this addresses your scan speed.
Many thanks for your help. I will load this up tonight.
Boy much improved scan speed. I didn't think Priority would slow the scan speed up that much.
Thanks again for your great support.
Ubbe
Member
"Boy much improved scan speed. I didn't think Priority would slow the scan speed up that much."
@Whistler_Support Could you please explain how the TG prio works and why it will slow down scanning. The help text says:
There was one P25 system having six TGs set to prio and another P25 system had two prio TGs. There where two other P25 trunked systems and one DMR trunked system, 5 trunked systems in total.
The two systems had their dwell timer set to 0,8 sec. If no activity are decoded in the control channel data, it does that check during the 0,8 sec time, it goes to next system. If a TG are set to prio it doesn't need to be involved as no TG's are active.
If there are TG activity decoded from the control channel it has to check if those TG's are programmed and if no match are found it goes to the next system. If there's a TG match it stops scanning and starts to monitor that call. It might decode the slow speed data of the voice channel for any prio TG and if the call drops back to the control channel between PTT it tries to catch any late entry info about active TG's at the site and if any of those will match a prio TG.
Where in this process are the TG prio adding a delay to the scan cycle? It seems important to us users to know how the scanner operates with prio TG's if that has a huge impact on scan speed.
/Ubbe
@Whistler_Support Could you please explain how the TG prio works and why it will slow down scanning. The help text says:
| If the channel is a talkgroup or radio ID, the priority check is done as a part of the decode of the control channel data and in some cases low speed data transmitted on the voice channel. |
There was one P25 system having six TGs set to prio and another P25 system had two prio TGs. There where two other P25 trunked systems and one DMR trunked system, 5 trunked systems in total.
The two systems had their dwell timer set to 0,8 sec. If no activity are decoded in the control channel data, it does that check during the 0,8 sec time, it goes to next system. If a TG are set to prio it doesn't need to be involved as no TG's are active.
If there are TG activity decoded from the control channel it has to check if those TG's are programmed and if no match are found it goes to the next system. If there's a TG match it stops scanning and starts to monitor that call. It might decode the slow speed data of the voice channel for any prio TG and if the call drops back to the control channel between PTT it tries to catch any late entry info about active TG's at the site and if any of those will match a prio TG.
Where in this process are the TG prio adding a delay to the scan cycle? It seems important to us users to know how the scanner operates with prio TG's if that has a huge impact on scan speed.
/Ubbe
Per the user guide, "Setting any object as a priority can cause normal scanner interruption"
Without getting into the weeds with a long response, if a Priority is set, the scanner frequently checks priority channels for activity.
Multiple Priorities simply adds to the number of Priority checks that can occur allowing for more opportunities for interruption before eventually completing the scan configuration and starting over.
Without getting into the weeds with a long response, if a Priority is set, the scanner frequently checks priority channels for activity.
Multiple Priorities simply adds to the number of Priority checks that can occur allowing for more opportunities for interruption before eventually completing the scan configuration and starting over.
Ubbe
Member
But please do. There's lots of free space to type a lot of words here in the forum.
Daleb49 had a couple of conventional channels but no priority where set to them.
Are your explanation that the scanner goes to those two systems control channels, that had TG prio set to them, at the time interval set for the prio check and stays there long enough on each system to catch any late entry TG information and then continues its normal scan cycle?
So this is much better than Unidens trunked prio system as this allows a check on TG's in different trunked system while scanning other systems. But you will have to be careful as it takes a long time on each control channel to sync and decode any TG info. It doesn't matter how many TG prio you set in a system, it is the sync and decode of data that takes time. What are the time penalty for each trunked system that has a prio for a TG?
If it is using the dwell timer set by the user that now are 0,8 sec, then if the prio timer are set to 3 sec, then it scans four trunked systems and then do a prio check of two systems that takes 1,6 sec and then scans the fifth trunked system followed by the conventional channels and then three more trunked systems and do its prio check again.
So with prio set to 3 sec it will take 6 sec for a scan cycle and without priority 4 sec?
Or is it enough to check one superframe at 360ms time plus the time it takes to sync, or TG prio are done in a totally different way?
/Ubbe
Setting one priority within one object type is pretty straight forward but setting multiple priorities over multiple objects can really complicate things. Priority timing varies slightly to best fit the individualized rules assigned to Conventional, Trunking, DMR, and NXDN systems.
Yes there is a lot of free space to type a lot of words but in the end it all comes down to the general statement I quoted from the user guide.
"Setting any object as a priority can cause normal scanner interruption"
I am just happy that we were able to resolve the customers issue quickly and that others may learn from this.
Yes there is a lot of free space to type a lot of words but in the end it all comes down to the general statement I quoted from the user guide.
"Setting any object as a priority can cause normal scanner interruption"
I am just happy that we were able to resolve the customers issue quickly and that others may learn from this.
Ubbe
Member
We are trying to learn but you do not tell us the function of the prio system so we can avoid falling in its traps. We would like to use the functions available in the scanner, like TG priority, but if it is almost impossible to use because it slows down scanning so much that it makes us miss calls, it was only two systems that had TG prio set, then we will need to learn exactly how it works and how to use it, limit to just one TG for each system or several TG's in one system depending of how the firmware developers have design the software.
/Ubbe
Ubbe, I believe I have given everyone a general understanding (setting objects as Priority can cause scanner interruptions)
The function of Priority is just as is sounds. It has priority over non-priority objects (even if currently providing audio from a non-priority object) of non priority objects.
If your scanner is currently producing voice on a non priority system and you have Priority set on another object, the scanner will release the non priority object to check for the Priority object and utilize any dwell/delay settings, then will resume.
If there are numerous Priorities, the scanner must do its best to maintain a balance of scanning the non-priority objects and addressing the Priority Objects.
Please understand and respect the decision not to provide timing variables.
The function of Priority is just as is sounds. It has priority over non-priority objects (even if currently providing audio from a non-priority object) of non priority objects.
If your scanner is currently producing voice on a non priority system and you have Priority set on another object, the scanner will release the non priority object to check for the Priority object and utilize any dwell/delay settings, then will resume.
If there are numerous Priorities, the scanner must do its best to maintain a balance of scanning the non-priority objects and addressing the Priority Objects.
Please understand and respect the decision not to provide timing variables.
Ubbe
Member
It's a corporate secret so I understand. But inform us if it will slow down scan a different amount if we have one or five TG's set to prio in the same trunked site. Removing TG prio from two sites made it have a "much improved scan speed" so it seems vital for us users to understand when it will be a bad idea to add one prio TG or several or never use it if it has such a bad impact on scan speed.
/Ubbe
