Unknown Talkgroups-SLC Public Safety

[gldavis]

Here's the unknowns for Salt Lake CIty Public Safety system. At least unknown to me.

Talkgroup,User,Hits
2144,,28
3744,,11
3808,,3
21328,,10
53056,,48
55184,,2

Gary

 

[qlajlu]

From the same old dusty list

When we hosted the Olympics, they designated several "Event Channels" specifically available for SLC PD to use like at the Medals Ceremonies and other downtown events. TGID 2144 was one of them. Those Event TGIDs were as follows:

TGID - EVENT CHANNEL
2144 - #9
2176 - #10
2208 - #11
2240 - #12
2272 - #13
2304 - #14
2336 - #15
2368 - #16

I suppose they could recycle those TGIDs and fodbuster has already warned us that SLC Public Safety and the Airport Authority systems were going to be integrated. We have also heard several SLC FD apparatus being taken out of service one by one for "rebanding." This could very easily be the part of that change.

Unfortunately, Gary, I cannot identify any of those other TGIDs, only that one, and I have no idea who the TG is now, but 28 hits makes it moderately active. Maybe we can identify it fairly easily. [Ya, ya, I know, I know, but I still have that bridge for sale!]

 

[gldavis]

Thanks for your input. It is a start. And (hopefully) now there is more than just me listening for these IDs.
I will be out in the valley tommorrow, and I'll see if I can find any new control channels operating.

Gary

 

[bneilson]

Tg: 1191

I don't listen to AC33 (SLC TRS) all that often but on the way in today I caught TG: 1191.

Looks like it is SLC Fire Dispatch. You only hear the page out traffic no response units. I sent this into the admin so it would get posted...

 

[Utah_Viper]

I will add these in and monitor them tonight while camping for the parade. I think this would qualify as a event LOL. I am sure to hear a lot of talk on all of the SLC TG's

TGID - EVENT CHANNEL
2144 - #9
2176 - #10
2208 - #11
2240 - #12
2272 - #13
2304 - #14
2336 - #15
2368 - #16

 

[gldavis]

TG 1191 is TG 1184 with the staus bit of 7, indicating a Multi-select conversation. In other words, going to more than one group. attached is the listing for the staus bits:
Dec ID + # Usage
-------------------------------------------------------
ID+0 Normal Talkgroup
ID+1 All Talkgroup
ID+2 Emergency
ID+3 Talkgroup patch to another
ID+4 Emergency Patch
ID+5 Emergency multi-group
ID+6 Not assigned
ID+7 Multi-select (initiated by dispatcher)
ID+8 DES Encryption talkgroup
ID+9 DES All Talkgroup
ID+10 DES Emergency
ID+11 DES Talkgroup patch
ID+12 DES Emergency Patch
ID+13 DES Emergency multi-group
ID+14 Not assigned
ID+15 Multi-select DES TG
-------------------------------------------------------------
These indicate the same talkgroup, just an additional status. Confused? Wikipedia has an explaination of this. Just keep the staus bit function on your scanner turned on, and you'll only see the main TG number.
Gary

 

[Rolfman]

OK so now for the $64 Dumb Guy Question:

After reading the Wiki it would seem that if I turn my Status Bit from Ignore to Yes I will basically get the 15 other possible TGID's for each TGID programed?

 

[bneilson]

TG 1191 is TG 1184 with the staus bit of 7, indicating a Multi-select conversation.

Good call!

I have never played with the status bit setting before. On my AC33 system it is set to "On"...

If I understand correctly, setting it to "Ignore" would allow me to just hear all of the traffic as if it were on TG: 1184.

Right?

I think I am asking the same thing as Rolfman, just opposite....

 

[Rolfman]

No I am sure it's me that is asking it backwards.

 

[qlajlu]

Status Bits & "Events Channels"

I don't listen to AC33 (SLC TRS) all that often but on the way in today I caught TG: 1191.

Looks like it is SLC Fire Dispatch. You only hear the page out traffic no response units. I sent this into the admin so it would get posted...

So according to the chart posted by gldavis, TGID 1191 is actually the "Multi-Select" Status Bit channel for TGID 1184 which is SLC FD's main fire dispatch TG. Did I get this right?

EDITED TO ADD: Well, Duh! That is exactly what he said, but I had to do the math because I didn't see that.

~~~~~ooOoo~~~~~​

I will add these in and monitor them tonight while camping for the parade. I think this would qualify as a event LOL. I am sure to hear a lot of talk on all of the SLC TG's

Originally Posted by qlajlu
TGID - EVENT CHANNEL
2144 - #9
2176 - #10
2208 - #11
2240 - #12
2272 - #13
2304 - #14
2336 - #15
2368 - #16

Viper, to my knowledge, those TGIDs are not necessarily currently assigned to SLC PD as "Events Channels." That was their use during the Olympics.

 

[bneilson]

TGID 1191 is actually the "Multi-Select" Status Bit channel for TGID 1184 which is SLC FD's main fire dispatch TG. Did I get this right?

That is my understanding... I would have picked up 1191 as I had Status Bit set to "ON".

I am monitoring now to see...

 

[bneilson]

Confirmed

With Status Bit "ON"
TGID 1191 is used for dispatch (Page outs) traffic

With Status Bit "OFF/IGNORE"
TGID 1184 carries all traffic

Thanks GLDAVIS for the pointers....

 

[LGLHOOK]

WOW, i am still confused

 

[gldavis]

According to the BC785D, the BC296D, and the RS PRO-2052 manuals, the Status Bit is a "Status Bit Ignore" fuction. So, for normal operation, you want the "Staus Bit" Ignore function "On". This way all the comms for a talkgroup will be shown on it's primary assignment. If your radio is set to ignore the status bit, then all the talkgroups that are displayed will be divisible by 16. If you are seeing any odd numbered talkgroups, then you should toggle the status bit setting.

A bit clearer I hope.
Gary

 

[LGLHOOK]

Does this feature work with the Pro-96 and Pro-2096 if you manually program in the TG's "status bit" ID and what is the advantage to this if any?? thanks.

 

[Utah_Viper]

When I try to program a "status bit" TG into my Pro-95 I get a error. I am not sure if it is able to be turned off/on.

 

[qlajlu]

From the BC780XLT owner's manual
On Type II trunking systems there is a method by which specialized types of communications utilize talkgroup numbers. An emergency call will occur on a unique talkgroup from its primary assignment, for example. Because the BC780XLT defaults to Status-Bit On mode, you never need to worry about missing these transmissions. If you have programmed talkgroup 33264 into Scan List memory, for example, and there is an emergency call within the group, you will hear it on 33264.

The only time you may wish to turn Status Bit off is if you're trying to figure out the proper fleet map of a Type 1 trunking system.

Okay, my BC780XLT runs the status bit "ON" as a default setting. I can just leave it there and will, according to the owner's manual, not miss any emergency traffic in that talk group. TG 1191 is NOT evenly divisible by 16 so I should just keep the status bit toggled "ON" and forget it.

Whew! I sure hope that is right. I think I'll just leave things I don't totally understand in the default position. I've had these scanners since 2001 and I never missed TG 1191, so I guess I won't start worrying about it now.

 

[LGLHOOK]

I've had these scanners since 2001 and I never missed TG 1191, so I guess I won't start worrying about it now.

I have to agree with you, I did not even know that there was a TG 1191. Hehe

 

[gldavis]

Does this feature work with the Pro-96 and Pro-2096 if you manually program in the TG's "status bit" ID and what is the advantage to this if any?? thanks.

I checked out the on-line PRO-96 manual, and found no mention of the status bit. My guess is that the "Status Bit Ignore" is always on. That way you will not miss any of the traffic for that talkgroup. The only advantage of turning off the ignore feature is if you only want to hear selected uses of the talkgroup; i.e. only hear patches, emergency calls, ect.

Gary

 

[bneilson]

The only advantage of turning off the ignore feature is if you only want to hear selected uses of the talkgroup; i.e. only hear patches, emergency calls, ect.

Right... It is really something the geeks that like watching the system (Unitrunker) and what it is doing would use. If you are just into listening to the calls, then there is no reason to have the ignore function deactivated...