Lots of Tulsa TGs heard in OKC on DPS this morning

[Gilligan]

Well I was listening to the OKC DPS site this morning and picked up about twenty new talkgroups. I read up on the status bit for motorola systems last night, then I think I made a mistake by changing the Emergency Alert option on the 246T to ON instead of OFF. As a result, I got a bunch of talkgroups this morning that are 16 up from regular TGs. So some are surely a mistake.

But for some reason, I copied a bunch of Tulsa TGs:
Tulsa County Sheriff 7A, 7B, & 7C (40976, 41008, 41040)
Tulsa City/County Health Dept A (33936)
Tulsa DPW Inspectors (39952)

Then how about this:
analog on 12416 (16 more than 12400), which is Tulsa EMSA 7A
analog on 12432, which is Tulsa EMSA 7B
And I thought Tulsa EMSA was supposed to be all digital & encrypted.

Lots of P25 found as well:
4912
13936
14960
29296
62064

And more unidentified analog TGs:
6768
24576
40960 (16 more than a "regular" TG)
41488
44528
45872
56304
59632 - sounded like police dispatch
60048

Can anyone confirm that the emergency alert can add 16 to regular talkgroups on a Uniden scanner?

This may seem like an unusual question but does anyone have a list (maybe from unitrunker or something) of all the talkgroups that have been present at one time or another (recently) on the OKC site. I am trying to lock out all of the regular TGs used on the OKC site so I can just search for new ones -- unfortunately the 200 TG limit on my 246T is causing me problems, as now I am picking up irregular Tulsa TGs as well. So I don't know which ones to put into the scanner (to lock out). But if there was a master list of, say, 150 TGs that have been used in the last month, I could program them in and still have 50 to spare. Like, SMA 5 may not ever be used -- but it's taking up memory right now because it could be used... Thanks.

 

[plaws]

Can anyone confirm that the emergency alert can add 16 to regular talkgroups on a Uniden scanner?

Right from the wiki:

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

The 16 possibilities (including 0) use four bits. The Uniden talkgroup format is really the 12 bits of the talk group plus the 4 status bits. This gives 16 bits total, or a possible 2^16 = 65536 talkgroups.

Except the last 4 bits don't really figure into the talkgroup number, so if you take those off (equivalent to dividing by 16), you end up with 4096 actual talkgroups.

Now, there was a thread here ... or somewhere ... about how you actually need to divide by 32 (or 2^5, giving 2048 total). Something to do with not being able to assign priority to a talkgroup on those "in between" channels.

Sure enough, if you look at the DB, the DPS system channels are all a multiple of 32 starting at 16 ...

So, in answer to your actual question ... no, I don't think pressing the emergency button would add 16 to the talkgroup.

If the BC246T is like the BCD396T, you can do a couple of things on a trunked system. First, you can Set Status Bit to Ignore, which means regardless of what status bits may be on from the list above, you see the "base" talkgroup. Second, you can set an Emergency Alert tone. That tone will activate if someone punches their emergency button. I assume this is done by looking for the 2 bit to be flipped on.

 

[loumaag]

...Now, there was a thread here ... or somewhere ... about how you actually need to divide by 32 (or 2^5, giving 2048 total). Something to do with not being able to assign priority to a talkgroup on those "in between" channels. ...

Here is the reference you must have read:
http://www.radioreference.com/forums/showthread.php?p=598065

 

[Gilligan]

So any ideas on the wierd talkgroups on 16 intervals instead of 32?

 

[woodyrr]

So any ideas on the wierd talkgroups on 16 intervals instead of 32?

The only thing that I can offer is that I use a BCD996T with the status bit set to "Ignore" and emergency alert set to "ON". I was searching the OKC site all day and noticed no unusual talkgroups.

EDIT: Did you actually hear voice traffic on the Tulsa talkgroups - If there was, I missed it.

 

[Gilligan]

The only thing that I can offer is that I use a BCD996T with the status bit set to "Ignore" and emergency alert set to "ON". I was searching the OKC site all day and noticed no unusual talkgroups.

I'm wondering if you didn't hear any of these new talkgroups and somehow I did, if maybe the signal level wasn't good enough and so it could have been reading the wrong TGs or something. But five Tulsa TGs does make me think something was going on... Maybe I can devote my BC246T to just the EDACS system (which has a very strong signal) and the Pro-97 to DPS. On second thought, the 97 only allows for 150 talkgroups, so I guess not.

Did you actually hear voice traffic on the Tulsa talkgroups - If there was, I missed it.

Yes I did. And it checked out okay as well. Kelly and Zebra units on TCSO Dispatch. When I first heard it, I wasn't sure who it was but I thought it must be a fairly large department to have that many unit designators (...k...z).

 

[plaws]

Here is the reference you must have read:
http://www.radioreference.com/forums/showthread.php?p=598065

That's the one - thanks!

 

[fast2okc]

mysterious talkgroups

Just my two cents:

Talkgroup 40976, Tulsa County Sheriff's Disptach was active on site 8 this morning. There was quite a bit of traffic on that talkgroup.

I was running UniTrunker all day on the system. Unitrunker logs system activity.
It shows activity on tg 40976 until 12:30 this afternoon.
There was NO traffic on 41008, 41040, 33936 or 39952.
No traffic on 12416 (I show the last traffic on tg 12400 -- EMSA Tulsa Dispatch on July 18).
No traffic on tg 12432 --EMSA Tulsa Service Side since December 16 of 2006.
No traffic on tg 4912 at all.
I have heard encrypted traffic of 13936, but the last traffic was Oct. 3.
No traffic on tg 14960.
Last traffic shown on tg 29296 was on Oct 1.
No traffic on tg 62064.

In fact, no traffic shown on any of the other talkgroups you show:

6768
24576
40960
41488
44528
45872
56304
59632
60048

Perhaps you need to keep the scanner a little farther away from the crack pipe.

Sorry, bad joke. Seriously, there must be something interfering with the control channel at your location

--fast2okc

 

[peterjmag]

I bet it was all the ducting that has been occuring on the 800 band these past few nights. I have been hearing CCs out of Kansas and fair away DPS sites here in Tulsa on my RS 800 duck. Ducting can sometimes play havoc even on a TRS.

P.J.

 

[Gilligan]

I've got my Pro-97 w/ me at work today so I can do some investigating. And I'm going to start using a different antenna for listening to DPS.

 

[Gilligan]

Just my two cents:

Talkgroup 40976, Tulsa County Sheriff's Disptach was active on site 8 this morning.
I was running UniTrunker all day on the system. Unitrunker logs system activity.
It shows activity on tg 40976 until 12:30 this afternoon.
There was NO traffic on 41008, 41040, 33936 or 39952.
No traffic on 12416 (I show the last traffic on tg 12400 -- EMSA Tulsa Dispatch on July 18).
No traffic on tg 12432 --EMSA Tulsa Service Side since December 16 of 2006.
No traffic on tg 4912 at all.
I have heard encrypted traffic of 13936, but the last traffic was Oct. 3.
No traffic on tg 14960.
Last traffic shown on tg 29296 was on Oct 1.
No traffic on tg 62064.

--fast2okc

Do you have a list of talkgroups that have at one time or another been active on the OKC site? Or even a text file that I could pull the TGs out myself?