Like HM1529 said, this does have to live in the Wiki until it is confirmed. But it does look good and is likely mostly correct.
The actual submission I filed was as confirmed a submission as is ever likely to occur concerning the specs..
I did not submit the whole template!
actual text from submission..
Hello Admin,
I have been monitoring these TG's and am convinced of the accuracy of the info.
It's ready for primetime!
All are LAW DISPATCH / All are FULL TIME ENC
TG 10151 PSP Troop H1 Harrisburg (Dauphin County)
TG 10152 PSP Troop H2 Carlisle (Cumberland County)
TG 10153 PSP Troop H3 Chambersburg (Franklin County)
TG 10154 PSP Troop H4 Lykens (Dauphin County)
TG 10155 PSP Troop H5 Newport (Perry County)
TG 10156 PSP Troop H6 Gettysburg (Adams County)
TG 10159 PSP Troop J1 Lancaster (Lancaster County)
TG 10160 PSP Troop J2 Avondale (Chester)
TG 10161 PSP Troop J3 Embreeville (Chester County)
TG 10157 PSP Troop J4 York (York County)
additional info can be found on the following wiki page.
https://wiki.radioreference.com/ind...o_Network_(PA-STARNet)_PSP_Talkgroup_Template
Thank You,
Brent
This certainly can't be right.
A site covering Chester, Lancaster, and York Counties wouldn't ever see activity such as this, Besides 10160 was reported in use in the Erie area when the system was just starting up, There is simply
No way a talkgroup assigned to Avondale would have been used up there, Heck there was 0 chance of someone replying from there.. Thus it couldn't be that now? Right? gotta be something else. JUST DOESN'T MAKE SENSE.
Same probably goes for the quandary with TG 10138 the template would indicate that it's F5 Mansfield, but there isn't anybody up there now. Just like back at the start with 10160 if you follow the analogy, Another member is certain it's some other type of TAC CH.
P25, BEE00.942, 10138, 302, 50, Normal, 1712, 2019/01/10 13:25, "PSP PW/E5/F5/J2 Disp 10012/10131/10138/10160"
P25, BEE00.942, 10138, 1200008, 60, Normal, 1626, 2019/01/10 13:25, "PSP E1/F5/H1/J2 Unit 10127/10138/10151/10160"
P25, BEE00.942, 10138, 1200015, 60, Normal, 977, 2019/01/10 13:25, "PSP E5/F5/J2 Unit 10131/10138/10160"
P25, BEE00.942, 10138, 1200016, 60, Normal, 59, 2019/01/09 13:22, "PSP E5/F5 Unit 10131/10138"
P25, BEE00.942, 10138, 1200094, 60, Normal, 1492, 2019/01/10 13:25, "PSP F5/H1/J2 Unit 10138/10151/10160"
I'm sure if I'd had the luxury of monitoring up there as I have down here I'd have seen similar strange and unexplained TG appearances.
Also the TAC's in the template could be terribly wrong.
The sequence may have potentially started with a TAC first, Meaning the A TAC could have been 10100 instead of 10106 which would be B TAC and so on down the list. Then the issue with what to do with 10149 and 10150.. OH it's hopeless, useless, epic fail here. The resistance is strong and may have more to do with exterior images and motivations beyond the fear of tainting something in the DB or being the first to break the ice. The thought crossed my mind to delete the whole TG Template as garbage through and through, But then I couldn't entertain the thought of some Hburg bigwig getting a sniff of the TG info posted here, Then presenting it to a radio head with the info displayed on some tablet. And thus the radio tech takes a gander and says "Yeah that looks right" and hands back the tablet. Then the Bigwig spins around in a huff and says "change the whole thing around, Some barefoot hillbilly figured this out on his own and we need to revamp the whole line from scratch"... BWAA HAA HAA HAA!
Never gonna happen..
WHAT ever.
I'm going to bed Ben.