unknown SNACC and NSRS ID's

Hello guys,

Does anyone know these trunk ID's?, I have them auto logged with butel
as being in use (I was not listening at the time) but they are not listed in last edition of SNRS Book.

Rich

SNACC 30640
SNACC 35249
SNACC 41015
SNACC 41079
SNACC 41111
SNACC 41143
SNACC 42679
SNACC 46096
SNACC 46448
SNACC 57623

NSRS/ 05-001
NSRS/ 15-155

Unknown Talk Groups For SNACC & NSRS

First of all on a Motorola Type II TRS if your ID that you are receiving is not divisible by 8 it is most likely not a valid talkgroup ID. Most IDs' on the SNACC system are divisible by 16 which is very common. From time to time a strange number or ID like that might pop up on your display and you might even hear something over the radio. From time to time on a Uniden BR330 I have heard some IDs' come up with a number that I have never seen before and they never reappeared. As for your list I come to the following conclusions.

ID 30640 Unknown
ID 35249 Invalid ID; Might be ID 35248 NLVPD North Patrol
ID 41015 Invalid ID
ID 41079 Invalid ID
ID 41111 Invalid ID
ID 41143 Invalid ID
ID 42679 Invalid ID
ID 46096 Unknown
ID 46448 LV City PWD Sewer Plant Ops (In the 5th Edition)
ID 57623 Invalid ID

ID 05-001 DPS Patch Sometimes Used To Route Reno NHP Traffic To LV NHP Dspatch)
In the 5th Edition

ID 15-155 DPS Patch Often Used For LV NHP Traffic (In the 5th Edition)

Hope this helps you. I am awaiting the 6th edition of the book whenever it comes out, hopefully soon.

TL

runkjunk said:

Hello guys,

Does anyone know these trunk ID's?, I have them auto logged with butel
as being in use (I was not listening at the time) but they are not listed in last edition of SNRS Book.

Rich

SNACC 30640
SNACC 35249
SNACC 41015
SNACC 41079
SNACC 41111
SNACC 41143
SNACC 42679
SNACC 46096
SNACC 46448
SNACC 57623

NSRS/ 05-001
NSRS/ 15-155

Click to expand...

My suggestion would be that you set Status Bit to 0 / OFF in your system for a while and monitor. For instance, most of those IDs are not divisible by 16 - but this does not mean they are invalid. Most of those IDs are +7 from a valid ID. +7 is multi-select. 41015 would be 41008 multi-select, 41079 would be 41072 multiselect, 41111 would be 41104 muliselect.

35249 is probably 35248 with +1 bit (+1 being all talkgroup).

If you want to leave Status Bit set to 1 / ON, then when you see an ID you don't recognize, first see if it is evenly divisible by 16. If it is but it is not a documented ID, you may have found a new one - or it could have been false. If it is _not_ evenly divisible by 16, then divide by 16 and round off the result so you just have a whole number. Then multiply that whole number again by 16 and you'll have the base TGID minus any status bits.

CAVEAT: I don't know what happens if you are running in ID Scan mode versus ID Search mode and a transmission with a status bit is set and you have Status Bits turned off. You may not hear the call at all if you have Status Bits off and are running in ID Scan mode - Actually you probably will. But I suspect that if you have Status Bits ON and are running in ID Scan mode, you will not receive talk groups with status bits set unless you actually have those odd TGIDs programmed in. On the systems I monitor, I do not see enough traffic with any status bits present to recall correctly.

Mike

30640 30640
35249 35248 (+1 all-talk)
41015 41008 (+7 multiselect)
41079 41072 (+7 multiselect)
41111 41104 (+7 multiselect)
41143 41136 (+7 multiselect)
42679 42672 (+7 multiselect)
46096 46096
46448 46448
57623 57616 (+7 multiselect)

Multiselect is most often seen in EMS/Fire tone-outs / alarms are paged out - It's dispatcher-initiated. Notice most of those multiselects are on Fire / EMS talk groups.

Check this Wiki writeup for a description of the status bits:

http://wiki.radioreference.com/index.php/Motorola_Talkgroups

thanks TOUGHLIFE & mtindor.Multi-select explains alot. Sorry, I grabbed older version of listing from shelf, I do have 5th edition.

Rich

TOUGHLIFE said:

First of all on a Motorola Type II TRS if your ID that you are receiving is not divisible by 8 it is most likely not a valid talkgroup ID.
TL

Click to expand...

To be more accurate wouldn't you want to say the talkgroup must be divisible by 16? If you start with the lowest talkgroup it would be numbered 16, with the next one up being 32, then 48, etc. There are not talk groups of 8, 24, 40, and 56 if I remember correctly. Dividing by 8 could validate talkgroups that do not exist, or am I missing something here?