Official PRWN Talkgroups Thread

AZScanner · #1 (**permalink**) 05-19-2006, 08:04 PM

I saw a thread along these lines in the California forum and thought "Hey, good idea". Yes of course we have the database, and people should be submitting the data there, but let's start putting it here too so as new talkgroups get discovered, everyone can immediately start enjoying the benefit of knowing them without having to wait for the db admin to add them.

I'll put up a couple that I don't think are here yet:

1769 - Phoenix FD - Blue Deck 1 - Chandler FD ops
1768 - Phoenix FD - Blue Deck 2 - Chandler FD ops

I'll post more as I identify them.

Oops, forgot to add this: Can we make this a sticky? I've always wanted to start a sticky thread.

-AZ

ctrl · #2 (**permalink**) 05-19-2006, 08:50 PM

Good idea.

However I actually have:

Simulcast B
Tac-A:
A12 Chandler Blue 1 1784
A13 Chandler Blue 2 1783
A14 Buckeye Valley 1782

Tac-B:
B12 Chandler Blue 1 1770
B13 Chandler Blue 2 1769
B14 Buckeye Valley 1768

... I am not 100% sure of these, just what I've come across

The other day, I heard some commucations on Simulcast - A, Talk group: 2862
It was a patch between phoenix/peoria, during that ordeal up by the lake.

AZScanner · #3 (**permalink**) 05-23-2006, 07:28 PM

Got another one... Units are working an Alert 2 on TG 1190. Unk channel designation.

EDIT: I should be more specific... this is Phoenix FD working an Alert 2 (plane inbound with problem) at Sky Harbor airport. CC is the Sky Harbor intellirepeater.

-AZ

Duditz511 · #4 (**permalink**) 05-24-2006, 01:22 AM

Quote:

Originally Posted by AZScanner

Got another one... Units are working an Alert 2 on TG 1190. Unk channel designation.

-AZ

Thats probably channel 2 considering that thats usually where Alert 2's are worked off of.

AZScanner · #5 (**permalink**) 05-24-2006, 01:29 PM

Alright then, designate that one as Sky Harbor IMS-2.

Does that mean IMS-1 is 1189? I'm going to monitor the airport system exclusively today and try to confirm that, as well as log some additional talkgroups on that CC.

-AZ

jasonpeoria911 · #6 (**permalink**) 05-25-2006, 03:27 AM

I think he meant Phoenix dispatch channel 2. Which is used for Sky Harbor/Deer Valley airport alerts, Violent assaults, shootings and stabbings in Phoenix.

Jason

AZScanner · #7 (**permalink**) 05-25-2006, 01:51 PM

Ah... no that's different. Phx works alerts on the IMS talkgroups, then alarm is notified of any status changes after the fact on A2.

Did some monitoring yesterday and noted the following that are currenly not listed in the RRDB:

1186 - Facilities?
1183 - Airport Ops
1181 - Airport Ops
1170 - Unknown
1153 - Unknown, ENC
1174 - Unknown, ENC
1169 - Facilities or maintenance.

Will listen some more today and see if I can nail these down.

-AZ

Duditz511 · #8 (**permalink**) 05-27-2006, 11:12 PM

Quote:

Originally Posted by jasonpeoria911

I think he meant Phoenix dispatch channel 2. Which is used for Sky Harbor/Deer Valley airport alerts, Violent assaults, shootings and stabbings in Phoenix.

Jason

Yea thats what I meant.

hulka · #9 (**permalink**) 05-28-2006, 10:05 AM

I thought Buckeye FD was on B-12?

jasonpeoria911 · #10 (**permalink**) 05-29-2006, 02:46 AM

Yes Buckeye and Buckeye valley area is on Blue12- 154.085

Jason

PHOENIX_SCANNER · #11 (**permalink**) 11-10-2006, 08:45 PM

I don't understand why phoenix uses A1, or A16, etc. so much. Somtimes very common (seemingly) traffic is worked on these encrypted TG's. If you listed to Glendale for example, they almost never use encryption. I guess it is just a matter of department policy.

Duditz511 · #12 (**permalink**) 11-11-2006, 12:05 PM

Quote:

Originally Posted by PHOENIX_SCANNER

I don't understand why phoenix uses A1, or A16, etc. so much. Somtimes very common (seemingly) traffic is worked on these encrypted TG's. If you listed to Glendale for example, they almost never use encryption. I guess it is just a matter of department policy.

Are you talking about Phoenix FD??

AZScanner · #13 (**permalink**) 11-13-2006, 11:54 AM

No, I know what he's talking about - PhoenixPD. Geez, I've never come across so many encrypted talkgroups in my life. It's not just A Deck, it's most of the system. And yeah, they do move alot of stuff over to A16 or A1 for little more reason than "Hey the media just showed up." We need the media to jump up and down and ***** about it again, maybe then something will be done about it. Until then, not much we can do about it.

-AZ

sniperbob · #14 (**permalink**) 11-30-2006, 01:05 AM

I put these in the database submision thread. I don't know if they go here or there.

These are all talkgroups in the PRWN on Simulcast D.

These ones appear to be Mesa city utilitys on Simulcast D:
3700
3705
3714
3715
3716 gas?
3722
3725
3730
3732 trash?
3733
3734
3735
3738
3740
3744

These are PD channels that show up on Simulcast D.
2915 Encrypted
2921 Encrypted
2928
2930
2944
2945 Encrypted
2954 Encrypted
2956
2959
2963
2964
2971
2977 Encrypted
3046 Encrypted
3083
3104 Encrypted

enjoy

AZScanner · #15 (**permalink**) 11-30-2006, 11:44 AM

Nice! Thanks!

-AZ

ICP963 · #16 (**permalink**) 12-03-2006, 04:15 PM

So far, using a RS PRO-28096 and PRO96COMM I have logged 322 talkgroups and 7,222 radio ID's on the Phoenix/Mesa System. Mostly by mnitoring Simulcast A & D, with a little time on B & C. I am constantly amazed mow much they use patches on A, probably 10-15 times as often as they do on B, C & D.

The 322 talkgroups covers everything on the system, and I have only ID'd some of FD stuff so far. Lots of it is city workers as well. Will post an update as I try and ID what I can when I can.

sniperbob · #17 (**permalink**) 12-04-2006, 10:05 PM

Some more I've heard on Simulcast D:

3813
3711
3741
3745
3813

I also heard 1775 which is a Phoenix Fire talkgroup, either it's patched through or the frequencies on the database are outdated and this is now a Simulcast B channel.

wlmr · #18 (**permalink**) 12-05-2006, 11:09 AM

Quote:

Originally Posted by ICP963

I am constantly amazed mow much they use patches on A, probably 10-15 times as often as they do on B, C & D.

In case you didn't know, not only Talkgroup to Talkgroup patches show up. Anytime a dispatcher selects multiple talkgroups and transmits a patch is set up for those talkgroups & then taken down when the dispatcher unkeys.

AZScanner · #19 (**permalink**) 12-05-2006, 11:51 AM

Quote:

Originally Posted by sniperbob

Some more I've heard on Simulcast D:

3813
3711
3741
3745
3813

I also heard 1775 which is a Phoenix Fire talkgroup, either it's patched through or the frequencies on the database are outdated and this is now a Simulcast B channel.

When I lived in Mesa I noticed that whenever there was a large incident working in Phoenix (1st alarm or better) the PFD talkgroups would come alive - I think it's because someone in Mesa FD is tuning in to listen.

-AZ

sniperbob · #20 (**permalink**) 12-06-2006, 10:58 AM

Quote:

Originally Posted by AZScanner

When I lived in Mesa I noticed that whenever there was a large incident working in Phoenix (1st alarm or better) the PFD talkgroups would come alive - I think it's because someone in Mesa FD is tuning in to listen.

-AZ

That's interesting you would say that, when the talkgroup came up I heard Tempe units on scene of a fire.