State Police Talk Group 33271

[Scanner-geek]

Anyone know this one? I have noted what sounds like State Police B.O.L.O.s being broadcast opn this TG on several occasions, but no other traffic. Is this some king of an all-talk-group (ATG) channel? (I don't see it in the database or on the Scanboston lists)
Thanks.

Scannergeek

 

[garys]

It would seem to be an ATG, but of what I don't know. The closest talk group would be 33264, which is H Patrol 1. You might try resuming scan next time you hear this and see if you hear it on any other talk group. That might give you an idea of what area it's being used in.

Gary

 

[mrsvensven]

Talkgroups have to be multiples of 32. If you see a talkgroup that isn't a multiple of 32, there may be some 'status bits' set. I would assume that you are hearing h-ptl-1 with some special status bit set. It's also possible that you are getting an error. Sometimes my scanner makes an error when getting the TGID, and I will hear A or H troop on my scanner even though all their channels are locked out.

 

[unleashedff248]

Based on the numbering scheme used by the system, it seems to be in the Troop H talkgroup area. According to the status bit (+7), it is H-PTL-1 multi-select. That's probably why you're hearing BOLO's transmitted. The dispatcher is selecting multiple talkgroups at once to transmit the BOLO's on.

 

[Junior08]

If someone in the Zone 3 or 5 areas runs Unitrunker maybe they can confirm this talkgroup?

 

[unleashedff248]

I'm in zone 3, I'll run it for a while and see what I get.

Also, is there any way to see my logs from unitruker Scott? I've run it for weeks on end on the system on a number of zones, but I can't seem to get the logged data to show unless I run it on the control channel.

 

[ecps92]

Unleashed is correct, based upon the status bit, H-PTL-1 simulcast with another T/G.

Probably H-PTL-1 and H-PTL-2 sometimes also [3] H-PTL-3

http://www.scandiego.com/motorola_type_ii_trunking_status.htm
TTID + # 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

If someone in the Zone 3 or 5 areas runs Unitrunker maybe they can confirm this talkgroup?

 

[garys]

Based on what Bill posted the correct TG is 33264. Which is H Patrol 1. That's assuming it's dispatcher initiated multi select.

Gary

 

[ecps92]

Typically [viewed thru Trunker] I do see many MultiSelects being used by the various HQ Dispatch centers.

AHQ - Danvers
CHQ - Holden
DHQ - Middleboro
GHQ - Framingham

Trunker shows

;VER=3
;ID_hex,COLOR_dec,PRIO_dec,TITLE_str,LASTNOTED_hex,HITS_hex,USAGE_hex,ID_dec,ID_str,LASTNOTED_mm/dd/yyyy,LASTNOTED_hh:mm
1819,1,0,"A-PTL-1 A-North etc",47d99fde,cf,0,6169,Patch= 6169,03/13/2008,16:42
181b,1,0,"A-PTL-2 A-South etc",47d9e072,83,0,6171,Patch= 6171,03/13/2008,21:18
181d,1,0,"A-PTL-3 etc",47d70006,551,0,6173,Patch= 6173,03/11/2008,16:56
181f,1,0,"H-PTL-1 H-North etc",47d895d7,1a5,0,6175,Patch= 6175,03/12/2008,21:47
1821,1,0,"H-PTL-2 H-South etc",47cb5e02,141,0,6177,Patch= 6177,03/02/2008,21:10
1823,1,0,"H-PTL-3 etc",47da774e,e8,0,6179,Patch= 6179,03/14/2008,08:02
1839,14,0,"SOPS 3 / 1B etc",478cb834,1,0,6201,Patch= 6201,01/15/2008,08:42
183f,1,0,"C-PTL-1 North etc",47d7440f,136,0,6207,Patch= 6207,03/11/2008,21:46
1841,1,0,"C-PTL-2 Alt-Nort etc",47d6dcfe,1,0,6209,Patch= 6209,03/11/2008,14:26
1843,1,0,"C-PTL-1 North etc",47d9e1b8,ee,0,6211,Patch= 6211,03/13/2008,21:23
184b,1,0,"H-PTL-2 H-South etc",47da4d85,169,0,6219,Patch= 6219,03/14/2008,05:03
184d,1,0,"D-PTL-1 North etc",47da16dd,38,0,6221,Patch= 6221,03/14/2008,01:10
184f,1,0,"D-PTL-1 North etc",47d8fe26,16,0,6223,Patch= 6223,03/13/2008,05:12
1853,1,0,"D-PTL-1 North etc",40f8d1b3,0,0,6227,Patch= 6227,07/17/2004,03:13
18a9,1,0,"MSP STATEWIDE 1 etc",47d754ae,13,0,6313,Patch= 6313,03/11/2008,22:57
18df,5,0,"LOC-PS-01 A/H Tr etc",47d671a2,25,0,6367,Patch= 6367,03/11/2008,06:48

Based on what Bill posted the correct TG is 33264. Which is H Patrol 1. That's assuming it's dispatcher initiated multi select.

Gary

 

[ScannerGeek]

So I'm gonna revisit this question.

I understand the concept of the multiselect for transmissions to patched to multiple talkgroups (for example, a BOLO on H-patrol-1 and H-patrol-2).

What I don't understand is why while searching the MSP trunk, I will occasionally hear BOLOs on some of these apparent multiselect talkgroups. When I resume search, there is no activity on any of my programmed talkgroups such as H-patrol-1. The scanner searches and locks in again on the multiselect talkgroup. This leads me to believe that I am missing this traffic when I am in scan mode since the multiselect IDs aren't in my scan list.

Should these "multiselect" variations (like the ones outlined by ecps92) be programmed in so I don't miss BOLOs? Should I stay in search mode? I would assume that an ATG--or multiselect--broadcast should also come up on the individual talkgroups selected, but this did not seem to be the case, at least in search mode on my 996t.

As an aside, I have never heard any activity on any of the "all talk groups" IDs listed in the database. Am I missing something?

Scannergeek

 

[Nascar18]

Sometimes when listening to H Patrol I will hear a cruiser tell the dispatch to go up to "3". That could be that same TG.

 

[RKG]

1) "Go to 3" means go to X-PTL-3, which, for all zones but D Troop, is the "talk around" TG.

2) A "Multi-Select" is not a patch. Rather, it is a function such that, transmitting on the main Xmit button causes the dispatcher's traffic to be broadcast simultaneously on multiple channels (or talkgroups). Subscriber traffic on any of the Multi-Select constituents is not, however, broadcast on the other constituents.

3) Multi-Selects are common on the MSP system, especially for BOLOs by GHQ and for the roll calls on the last half.

 

[DaveNF2G]

Try experimenting with the "ignore status bit" setting on your scanner. You should hear multi-selects and patches on at least one of the involved talkgroups as if they were normal traffic if this setting is correct. I forget which way it's supposed to be, but I believe it should be ON.

 

[ecps92]

Not all Dispatchers use the ATG, all the time.

It you run trunker or any of the other software monitoring versions, let it run for a day or two and you will begin to see [depending on your zone] the various ATG's used, it could take a week of logging.

So I'm gonna revisit this question.

I understand the concept of the multiselect for transmissions to patched to multiple talkgroups (for example, a BOLO on H-patrol-1 and H-patrol-2).



As an aside, I have never heard any activity on any of the "all talk groups" IDs listed in the database. Am I missing something?

Scannergeek

 

[Scanner-geek]

So I tried an experiment. I created a bank with only "multiselect" talkgroups. These consisted of the patrol talk groups +7. Not much activity yet. I thought this might be a good way of selecting some priority traffic such as BOLOs, but so far low yield. I'll keep listening and post what I hear.

Scannergeek

 

[ecps92]

Would you update your profile to indicate where you are....

Also what Zone are you trying this on, that might make a difference as well

So I tried an experiment. I created a bank with only "multiselect" talkgroups. These consisted of the patrol talk groups +7. Not much activity yet. I thought this might be a good way of selecting some priority traffic such as BOLOs, but so far low yield. I'll keep listening and post what I hear.

Scannergeek

 

[DaveNF2G]

A correction to my earlier comment about Ignore Status Bit.

This seems to be a feature of Uniden scanners only. The GRE models don't have this setting.

 

[Scanner-geek]

I'm in Boston and Monitor the boston metro simulcast

 

[ecps92]

So you mean Zone 5

You should see the A, C, D, E or H ATG's in use.

E was used on 11.08.2009 @ 1252 hrs

I have only had trunker running for the past 2 days, so my files are stale
but......

A was caught on 05.18.2009
C was caught on 05.04.2009
D was caught on 07.13.2009
H was caught on 05.15.2009

All depends on the Dispatchers on the console.

I'm in Boston and Monitor the boston metro simulcast

 

[Scanner-geek]

BOLO today on 33271

This morning I heard a BOLO put out on 33271 for a man with a knife in Quincy. I found no simultaneous broadcast on the H-Patrol-1 or H-Patrol-2 talk groups (I locked out 33271, hit search mode, got nothing, and unlocked the group and transmission on 33271 was still going).

My interpretation of this is that if you don't have these "mulitselect" talk groups in your scan list, and you are in scan mode, you will miss some interesting traffic. Clearly not all BOLOs are put out on multiselect, but rather these TGs are used at the discretion of the dispatcher. Multiselect may not be used that often, but seems important nevertheless.

I now have these talk groups in my list (patrol talkgroups +7) for all troops. Perhaps these TGs should be in the RRDB, as they seem to be used more than the ATGs listed. What I have done is created a separate system with only multiselect channels as a way of filtering out most of the routine patrol radio traffic. Clearly, any BOLOs put out on a single patrol TG will be missed.

Correct me if I'm wrong fellas. Interested in your thoughts. Anyone else have these TGs in their lists?

Scannergeek