Chester County P25 System

bberns22

Member
Premium Subscriber
Joined
Sep 30, 2007
Messages
141
Location
West Chester PA
Just had TG 5536 pop up a couple of times - Seemed like public works or possibly fire ground. Has anyone else come across it???
 

u2brent

Member
Premium Subscriber
Joined
Jul 17, 2010
Messages
2,091
Location
KRWDPAXKRS1
Last edited:

royldean

Member
Joined
Jan 30, 2016
Messages
416
Location
Schwenksville, PA
5536 is busy....
If Chester county is anything like Montco right now, there are TONS of electrical fires going on (I imagine wind related). In the span of an hour I heard like 5 or 6 different calls for "outdoor brush fires" and "electrical fires" with lots of "wires down" follow ups!
 

u2brent

Member
Premium Subscriber
Joined
Jul 17, 2010
Messages
2,091
Location
KRWDPAXKRS1
I'll try to pay more attention to those series of TG's.
I couldn't swear that they are only/always Lancaster patches but maybe..
I have
5532 pegged as the Bolo TG
and
5546 as the Covid-19 TG (But primarily because it was first observed during this pandemic and for no other reason :rolleyes:)
Need to wait for another cross border call/patch to happen..

Depending on the how's & why's of which scanner is used (& or software) and decodes those calls, they can come up as the intended destination TG name or as the console ID as well. Can get confusing. Using DSD+ tells the story very well..
 
Last edited:

HM1529

Pennsylvania DB Admin
Database Admin
Joined
Jul 16, 2003
Messages
2,587
Location
West of the Atlantic Ocean
I'll try to pay more attention to those series of TG's.
I couldn't swear that they are only/always Lancaster patches but maybe..
I have
5532 pegged as the Bolo TG
and
5546 as the Covid-19 TG (But primarily because it was first observed during this pandemic and for no other reason :rolleyes:)
Need to wait for another cross border call/patch to happen..

Depending on the how's & why's of which scanner is used (& or software) and decodes those calls, they can come up as the intended destination TG name or as the console ID as well. Can get confusing. Using DSD+ tells the story very well..
Yeah, the whole patching thing can be a pain. There are system ID's assigned to certain items available at the consoles (like VLAW31, PSP, Lancaster Co, Cecil Co, etc). When those items get patched to other system talkgroups, you also get those dynamic Harris IDs that rotate through that 100 number long list dynamically.

As you said, depending on what folks are using to monitor, they are only seeing part of the picture.

The fixed IDs would be listed in the database. Dynamic IDs would not be.
 

wa8pyr

Technischer Guru
Lead Database Admin
Joined
Sep 22, 2002
Messages
4,927
Location
Ohio
The fixed IDs would be listed in the database. Dynamic IDs would not be.
Actually, I amended the rules awhile back to allow listing of patch talkgroups on Harris systems. Since they're dynamic they have to be listed generically in a dedicated "Patch Talkgroups" category as "Patch XXXX" where XXXX is the talkgroup number.

So if you want to add a Patch talkgroup category for that system, knock yourself out.
 

u2brent

Member
Premium Subscriber
Joined
Jul 17, 2010
Messages
2,091
Location
KRWDPAXKRS1
Just noticed a 3 way patch was active around 9 PM between 65101/5543/2350 W Fire Ops1.
it was an assist in Newcastle County DE so 5543 may be that... Will have to see if this recurs..
 

u2brent

Member
Premium Subscriber
Joined
Jul 17, 2010
Messages
2,091
Location
KRWDPAXKRS1
Tonight, just caught another 3 way patch 65102/5542/2350 West Fire Disp.
Accident with NB 19 (assuming Newcastle Box 19/ Amb19).
5542 and 5543 appear to be Newcastle County DE related :unsure:
Code:
2020/05/22  18:35:03  Freq=771.568750  NAC=00A  Current network:  92466.00A  Chester Co PA
2020/05/22  18:35:04  Freq=771.568750  NAC=00A  Patch Supergroup: TG=65102
2020/05/22  18:35:04  Freq=771.568750  NAC=00A      Patch Subgroup: TG=2350 [W Fire Resp]
2020/05/22  18:35:04  Freq=771.568750  NAC=00A  Patch Supergroup: TG=65102
2020/05/22  18:35:04  Freq=771.568750  NAC=00A      Patch Subgroup: TG=5542 [App Patch 5542]
2020/05/22  18:35:04  Freq=771.568750  NAC=00A  Current site:  92466.00A-30.30  West Simulcast
2020/05/22  18:35:05  Freq=771.568750  NAC=00A  Patch Supergroup: TG=65102
2020/05/22  18:35:05  Freq=771.568750  NAC=00A      Patch Subgroup: TG=5542 [App Patch 5542]
2020/05/22  18:35:06  Freq=771.568750  NAC=00A  Patch Supergroup: TG=65102
2020/05/22  18:35:06  Freq=771.568750  NAC=00A      Patch Subgroup: TG=2350 [W Fire Resp]
 
Last edited:

u2brent

Member
Premium Subscriber
Joined
Jul 17, 2010
Messages
2,091
Location
KRWDPAXKRS1
Just noticed a 3 way patch was active around 9 PM between 65101/5543/2350 W Fire Ops1.
it was an assist in Newcastle County DE so 5543 may be that... Will have to see if this recurs..
2350 should have been 2351 from the day before. Just noticed the typo.. No Biggy..
Any help would be appreciated :)
Here's a tentative list of possibilities. IDK..
  • 5531 VLAW31/Law Enforcement? (09-08-2019)
  • 5532 PSP/Law Enforcement?
  • 5533 Law Enforcement?/Formerly West Chester PD UHF
  • 5535 Lancaster County EMS? (08-08-2017)
  • 5536 Lancaster County Fire? (08-08-2017)
  • Berks County may fall in here??
  • 5539 Cecil County MD EMS? (02-22-2017)
  • 5540 Cecil County MD Fire? (06-03-2017)
  • 5541 Delaware County?? (12-14-2018)
  • 5542 New Castle County DE EMS? (03-29-2018)
  • 5543 New Castle County DE Fire? (04-04-2018)
  • 5544 Montgomery County?? (06-16-2018)
  • 5546 ?? (03-19-2020)
Just gotta wait for them to occur and repeat
 

wa8pyr

Technischer Guru
Lead Database Admin
Joined
Sep 22, 2002
Messages
4,927
Location
Ohio
2350 should have been 2351 from the day before. Just noticed the typo.. No Biggy..
Any help would be appreciated :)
Here's a tentative list of possibilities. IDK..
  • 5531 VLAW31/Law Enforcement? (09-08-2019)
  • 5532 PSP/Law Enforcement?
  • 5533 Law Enforcement?/Formerly West Chester PD UHF
  • 5535 Lancaster County EMS? (08-08-2017)
  • 5536 Lancaster County Fire? (08-08-2017)
  • Berks County may fall in here??
  • 5539 Cecil County MD EMS? (02-22-2017)
  • 5540 Cecil County MD Fire? (06-03-2017)
  • 5541 Delaware County?? (12-14-2018)
  • 5542 New Castle County DE EMS? (03-29-2018)
  • 5543 New Castle County DE Fire? (04-04-2018)
  • 5544 Montgomery County?? (06-16-2018)
  • 5546 ?? (03-19-2020)
Just gotta wait for them to occur and repeat
Be careful about assigning specific functions to specific patch talkgroups; while patch talkgroups on Harris systems can be permanently assigned to specific uses, in most cases the pool of patch talkgroups (100, if I recall correctly) is simply assigned dynamically. So what comes up as TG A + TG B = Patch C one day can show up as TG A + TG B = Patch J the next day. It can take a lot of monitoring to make sure patches show up consistently as A + B = C.

This is why patch talkgroups in the database are generally just labeled "PATCH XXXX."
 

u2brent

Member
Premium Subscriber
Joined
Jul 17, 2010
Messages
2,091
Location
KRWDPAXKRS1
Thank You for the info,
This is an exercise that could use some more observers, hence posting in the forum to try and drum up at least a tiny bit of interest.
Please view the wiki..
It is understood about the dynamic and ever changing rotating & ascending sequentially by +1 list of 100 TG's in the 65xxx range.

That is not what we (or maybe just me :rolleyes:) are determining here..
In order to determine if the currently unidentified 55xx series TG's are indeed static or have a fixed function they need to be documented.
This is just in the beginning phase. Although those TG's have been observed in use and posted to the wiki for quite a while I never attempted to pin them down, That list could be different tomorrow or next week based on observations, but if nobody documents this we'll (or at least I) may never know.
If they flip back and forth and do not continue to match up we'll know in time.
The items I highlighted in bold seem correct, but that needs tested along with the more speculative non-bold notations that have a question mark following them.
Labeling them XX Patch 1 or XX Patch 2 is a safer bet and may actually be correct IDK, but they may indeed be fixed. I personally don't know, I may learn it was an exercise doomed to failure, but won't know until I try ;)

It's this guys fault
@bberns22 :LOL:
 
Last edited:

bberns22

Member
Premium Subscriber
Joined
Sep 30, 2007
Messages
141
Location
West Chester PA
Thank You for the info,
This is an exercise that could use some more observers, hence posting in the forum to try and drum up at least a tiny bit of interest.
Please view the wiki..
It is understood about the dynamic and ever changing rotating & ascending sequentially by +1 list of 100 TG's in the 65xxx range.

That is not what we (or maybe just me :rolleyes:) are determining here..
In order to determine if the currently unidentified 55xx series TG's are indeed static or have a fixed function they need to be documented.
This is just in the beginning phase. Although those TG's have been observed in use and posted to the wiki for quite a while I never attempted to pin them down, That list could be different tomorrow or next week based on observations, but if nobody documents this we'll (or at least I) may never know.
If they flip back and forth and do not continue to match up we'll know in time.
The items I highlighted in bold seem correct, but that needs tested along with the more speculative non-bold notations that have a question mark following them.
Labeling them XX Patch 1 or XX Patch 2 is a safer bet and may actually be correct IDK, but they may indeed be fixed. I personally don't know, I may learn it was an exercise doomed to failure, but won't know until I try ;)

It's this guys fault
@bberns22 :LOL:
Ha Ha - blame the company I work for. Working from home and have the scanner sitting on my desk...
 
Top