skips in the tallkgroups#

[frank125]

hello just wanted to know has anybody noticed this iam entering by hand the delaware trunked system. scanlist 1- dsp it starts of at 10 for my ist trunkgroup then goes normall to 11-12-13 on up to 17, know when i put ncc in scanlist-2 it starts off at 28 why wouldnt it start at 18 whats up with that, why would this not go in order, i know these are not banks if they were it would be right. my next scanlist-3 skips 13
numbers can someone shed some lite on this as to why this does this with the skipping, why does my first scanlist start at 10 and not 1. any thoughts/help on this i can live with this just thought it was very strange, of corse if there is a way to fix this i would like to, thanks for any help .

 

[Hoofy]

It seems to be the way that the scanner likes to do it. It just picks numbers and assigns them.

 

[frank125]

hello just wanted to know has anybody noticed this iam entering by hand the delaware trunked system. scanlist 1- dsp it starts of at 10 for my ist trunkgroup then goes normall to 11-12-13 on up to 17, know when i put ncc in scanlist-2 it starts off at 28 why wouldnt it start at 18 whats up with that, why would this not go in order, i know these are not banks if they were it would be right. my next scanlist-3 skips 13
numbers can someone shed some lite on this as to why this does this with the skipping, why does my first scanlist start at 10 and not 1. any thoughts/help on this i can live with this just thought it was very strange, of corse if there is a way to fix this i would like to, thanks for any help .

this is for the psr-500 thanks again

 

[davidbond21]

The PSR, when scanning through everything in a single scanlist, I believe goes by the order of the talkgroups' Object IDs assigned to them, not the actual talkgroup numbers. Object IDs are assigned in sequential order as they are entered into the scanner, so if the talkgroups you are mentioning weren't programmed in one after the other in the same sitting, they might not be consecutively numbered and won't be consecutively scanned. If this is a problem for you though, you can reassign Object IDs.

 

[fmon]

You can't reassign Object ID's after SAVE w/o software.

The OP likely has set two or more TSYS Objects. I.e., the first TSYS consumes Object ID 0-9 (normal for TSYS). Then enters 10-17 as TGRP Objects. However, the skip to Object 28 may be because a second TSYS Object was entered prior to entering additional TGRP Objects for the first TSYS Object.