PA Statewide P25 Phase 2 System

PaMonitor

Member
Premium Subscriber
Joined
Apr 22, 2019
Messages
221
Location
Northern Tier of Pa.
What about PEMA? You're going to have to get a little more specific in your question.

I'm not sure either. I imagine that they'll remain on VHF for sometime yet.

While on the subject of EMA, I've observed that the Bradford County page shows 155.775 as the Rx frequency and 158.835 as Tx. On the sheet given to me by a Fire chief, it shows opposite of that. I'm fairly certain I receive it as 158.835. I'm the one who convinced our senior dispatcher to submit the contents of this sheet. Either the sheet is wrong, he submitted it incorrectly, or an administrator processed it incorrectly. As I am unsure if this is an error or not I am not going to submit it, but I'm sure receive it as 158.835.
 

mtindor

OH/WV DB Admin
Database Admin
Joined
Dec 5, 2006
Messages
11,248
Location
Carroll Co OH / EN90LN
I'm not sure either. I imagine that they'll remain on VHF for sometime yet.

While on the subject of EMA, I've observed that the Bradford County page shows 155.775 as the Rx frequency and 158.835 as Tx. On the sheet given to me by a Fire chief, it shows opposite of that. I'm fairly certain I receive it as 158.835. I'm the one who convinced our senior dispatcher to submit the contents of this sheet. Either the sheet is wrong, he submitted it incorrectly, or an administrator processed it incorrectly. As I am unsure if this is an error or not I am not going to submit it, but I'm sure receive it as 158.835.

The license ( KNHG478 (BRADFORD, COUNTY OF) FCC Callsign Details ) actually shows the 158.835 as the repeater output. So I imagine you have it right and I guess the DB has it wrong (I haven't looked). This kind of stuff happens because a lot of people who submit things end up submitting data based upon a mobile radio codeplug, where the mobile radio is transmitting on the repeater input and receiving on the repeater output -- when we (RR) want the opposite (meaning from the perspective of the repeater, not the mobile unit).

Mike
 

PaMonitor

Member
Premium Subscriber
Joined
Apr 22, 2019
Messages
221
Location
Northern Tier of Pa.
I don't know how he submitted it. It was probably from the call center. He was under the impression, as a lot of people are, that we just pulled everything from the FCC DB. And I had that printout in my possession for a year before it got submitted.
 

redbeard

OH, PA, WV Regional Admin
Database Admin
Joined
Feb 5, 2003
Messages
1,379
Location
BEE00.348-3.1
I don't know how he submitted it. It was probably from the call center. He was under the impression, as a lot of people are, that we just pulled everything from the FCC DB. And I had that printout in my possession for a year before it got submitted.
Like Mike said, a lot of frequency sheets from an agency assume mobile/portable radio programming and will have the tx/rx listed backward from what we expect to hear from the repeater. Send a submission to let an admin for that area know it's backwards.
 

PaMonitor

Member
Premium Subscriber
Joined
Apr 22, 2019
Messages
221
Location
Northern Tier of Pa.
The license ( KNHG478 (BRADFORD, COUNTY OF) FCC Callsign Details ) actually shows the 158.835 as the repeater output. So I imagine you have it right and I guess the DB has it wrong (I haven't looked). This kind of stuff happens because a lot of people who submit things end up submitting data based upon a mobile radio codeplug, where the mobile radio is transmitting on the repeater input and receiving on the repeater output -- when we (RR) want the opposite (meaning from the perspective of the repeater, not the mobile unit).

Like Mike said, a lot of frequency sheets from an agency assume mobile/portable radio programming and will have the tx/rx listed backward from what we expect to hear from the repeater. Send a submission to let an admin for that area know it's backwards.

You have both convinced me. And I imagine there are Emergency Personnel that rely on this. Consider it done.
 

PaMonitor

Member
Premium Subscriber
Joined
Apr 22, 2019
Messages
221
Location
Northern Tier of Pa.
No one should be relying on info from a hobbyist website to program mission critical info into radios, that should be coming from the dispatch center.

Probably a poor choice of words on my part. There are those that probably use it though. I was discussing this yesterday with a friend who is an EMA. Whoever programmed his had the Rx frequency as both Rx and Tx, which the talk around.
 

ka3aaa

Member
Joined
Jan 27, 2008
Messages
1,293
Location
middletown, pa.
a recieve frequency can be used to transmit on, its called simplex. why tie up a repeater if you dont need to and you are only fifty or so feet apart. Also there are some standard protocalls that exist in the radio world that are adhear to, however sometimes they are reversed or orginored all together which depends on the circumstances your dealing with.
 

PaMonitor

Member
Premium Subscriber
Joined
Apr 22, 2019
Messages
221
Location
Northern Tier of Pa.
My mistake, I see I used Rx when I should have used Tx. If his Tx is the same as Rx I don't think he's going to hit the repeater, which was the issue. And although I appreciate the input, the thread need to get back to STARNet.
 

scnrfrq

Member
Premium Subscriber
Joined
Dec 26, 2002
Messages
973
Location
Erie, PA
I've been waiting to see when the DCNR rangers at our local Presque Isle park would get the new P25 radios. I was there today and may have noticed a change in antennas on their vehicles. For years with OpenSky they just had a small black center-loaded antenna on each car. Today I saw they have added about a 2 foot silver antenna also on some cars. Not sure, but maybe this has to do with P25?

Finally got a pic of the antenna I mentioned. Any ideas?
 

Attachments

  • IMG_1703 (Large).jpg
    IMG_1703 (Large).jpg
    271.5 KB · Views: 71

n3obl

Ø
Database Admin
Joined
Dec 19, 2002
Messages
2,063
Location
PA
Front one is an Antenna Specialists VHF quarter wave. Back appears to be the 800 opensky antennas that have been used previously.
 

HM1529

Pennsylvania DB Admin
Database Admin
Joined
Jul 16, 2003
Messages
3,165
Location
West of the Atlantic Ocean
You may also see these antennas for the new system...just had one pass me the other day on Rt 23 in Valley Forge. Unmarked pickup, unknown agency.

Thats a Motorola multiband antenna. 82692
 

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
16,174
Location
BEE00
What's the deal with the PGC Fire talkgroups?

The listings in the wiki keep changing. A while back a bunch of the PGC listings were changed to "Fire Ops #" for each region, and now they've mostly all been reverted to unknown status as of about two weeks ago. Likewise, the "Fire Talkaround" talkgroups were changed to "Fire Ops 1", and now they're back to "Fire Talkaround".

Does anyone actually know what the real assignments are? :unsure:

PS - Do we really need a master Talkgroup Research page, along with multiple sub-pages for agencies like PSP, PGC, DCNR, etc.? Some of those sub-pages haven't even been updated in months, while the duplicated info on the master page has been updated. Seems like it would make more logical sense to either have only the master list on one page, or break them all out into their own pages. Don't really see the point of the duplication and having to maintain multiple pages if something needs to be updated. Also makes research tougher when the two pages have conflicting info.

PPS - I believe there's a DOT talkgroup page out there somewhere, but it appears that it was never linked on the master STARNet Wiki page, and so it's likely orphaned at this point.
 

u2brent

OAMPT
Premium Subscriber
Joined
Jul 17, 2010
Messages
3,154
Location
KRWDPAXKRS1
What's the deal with the PGC Fire talkgroups?

The listings in the wiki keep changing. A while back a bunch of the PGC listings were changed to "Fire Ops #" for each region, and now they've mostly all been reverted to unknown status as of about two weeks ago. Likewise, the "Fire Talkaround" talkgroups were changed to "Fire Ops 1", and now they're back to "Fire Talkaround".

Does anyone actually know what the real assignments are? :unsure:
NO, But this has been floated about, unconfirmed.
Could use some input.. Note the ? marks are SWAG's they could be anything. Need reports of activity and use..
The Fire Talkarounds have also been referred to as an /alternate name depending on the user..
PENNSYLVANIA GAME COMMISSION 12000-12090?
  • NW Dispatch Franklin - 12000
  • NW Dispatch 2 Secure - 12001
  • NW Region Talkaround - 12002
  • PGC Statewide - 12003
  • NW LE Tac 1 - 12004
  • NW LE Tac 2 - 12005
  • NW LE Tac 3 - 12006
  • NW Fire Talkaround/Fire Ops 1 - 12007
  • NW Admin Talkaround - 12008
  • - 12009
  • PGC Statewide Fire Ops 1 - 12010 LANC33/VENA12
  • PGC Statewide Fire Ops 2 - 12011 LANC33
  • PGC Statewide Fire Ops 3 - 12012 LANC33 (2/28/2019)
  • - 12013
  • - 12014
  • SW Dispatch Ligonier - 12015
  • SW Dispatch 2 Secure - 12016
  • SW Region Talkaround - 12017
  • SW LE Tac 1 - 12018
  • SW LE Tac 2 - 12019
  • SW LE Tac 3 - 12020
  • SW Fire Talkaround/Fire Ops 1 - 12021
  • SW Admin Talkaround - 12022
  • - 12023
  • NC Dispatch Avis - 12024
  • NC Dispatch 2 Secure - 12025
  • NC Region Talkaround - 12026
  • NC LE Tac 1 - 12027
  • NC LE Tac 2 - 12028
  • NC LE Tac 3 - 12029
  • NC Fire Talkaround/Fire Ops 1 - 12030
  • NC Admin Talkaround - 12031
  • - 12032
  • SC Dispatch Huntingdon - 12033
  • SC Dispatch 2 Secure - 12034
  • SC Region Talkaround - 12035
  • SC LE Tac 1 - 12036
  • SC LE Tac 2 - 12037
  • SC LE Tac 3 - 12038
  • SC Fire Talkaround/Fire Ops 1 - 12039
  • SC Admin Talkaround - 12040
  • - 12041
  • NE Dispatch Dallas - 12042
  • NE Dispatch 2 Secure - 12043
  • NE Region Talkaround - 12044
  • NE LE Tac 1 - 12045
  • NE LE Tac 2 - 12046 PIKE31 (03/04/2020)
  • NE LE Tac 3 - 12047
  • NE Fire Talkaround/Fire Ops 1 - 12048 PIKE31 (03/04/2020)
  • NE Admin Talkaround - 12049
  • - 12050
  • SE Dispatch Reading - 12051
  • SE Dispatch 2 Secure - 12052
  • SE Region Talkaround - 12053
  • SE LE Tac 1 - 12054
  • SE LE Tac 2 - 12055
  • SE LE Tac 3 - 12056
  • SE Fire Talkaround/Fire Ops 1 - 12057
  • SE Admin Talkaround - 12058
  • - 12059
  • SW Fire Ops 2? - 12060 CAMB02 (11/24/2019)
  • SW Fire Ops 3? - 12061
  • SW Fire Ops 4? - 12062
  • SW Fire Ops 5? - 12063
  • SW Fire Ops 6? - 12064
  • NW Fire Ops 2? - 12065
  • NW Fire Ops 3? - 12066
  • NW Fire Ops 4? - 12067
  • NW Fire Ops 5? - 12068
  • NW Fire Ops 6? - 12069
  • NC Fire Ops 2? - 12070 CHES31 (04/02/2020) [RID 1224062]
  • NC Fire Ops 3? - 12071
  • NC Fire Ops 4? - 12072
  • NC Fire Ops 5? - 12073
  • NC Fire Ops 6? - 12074
  • - 12075
  • NE Fire Ops 2 - 12076 PIKE31 (03/04/2020)
  • NE Fire Ops 3 - 12077 PIKE31 (03/04/2020)
  • NE Fire Ops 4? - 12078 PIKE31 (03/04/2020)
  • NE Fire Ops 5? - 12079
  • NE Fire Ops 6? - 12080
  • SE Fire Ops 2 - 12081 LANC33 (11/15/2019)
  • SE Fire Ops 3 - 12082 LANC33 (10/02/2019)
  • SE Fire Ops 4? - 12083
  • SE Fire Ops 5? - 12084
  • SE Fire Ops 6? - 12085 LANC33 (04/17/2019)
  • SC Fire Ops 2? - 12086 LANC33 (04/17/2019)
  • SC Fire Ops 3? - 12087
  • SC Fire Ops 4? - 12088 LANC33 (09/14/2019)
  • SC Fire Ops 5? - 12089
  • SC Fire Ops 6? - 12090 LANC33 (02/13/2020)
  • :unsure:
PS - Do we really need a master Talkgroup Research page, along with multiple sub-pages for agencies like PSP, PGC, DCNR, etc.? Some of those sub-pages haven't even been updated in months, while the duplicated info on the master page has been updated. Seems like it would make more logical sense to either have only the master list on one page, or break them all out into their own pages. Don't really see the point of the duplication and having to maintain multiple pages if something needs to be updated. Also makes research tougher when the two pages have conflicting info.
It's my opinion that the master page with all TG's listed be kept current, If someone wants all that other extra work.. It's on those that feel they're necessary to do the updates on them if they want them :LOL:
PPS - I believe there's a DOT talkgroup page out there somewhere, but it appears that it was never linked on the master STARNet Wiki page, and so it's likely orphaned at this point.
The Pertinent information was salvaged..
Scroll to the bottom of this page lately.. :unsure:
Also unconfirmed

Appears someone removed the link from the main page :oops: I fixed it..
 
Last edited:

scnrfrq

Member
Premium Subscriber
Joined
Dec 26, 2002
Messages
973
Location
Erie, PA
NO, But this has been floated about, unconfirmed.
Could use some input.. Note the ? marks are SWAG's they could be anything. Need reports of activity and use..
The Fire Talkarounds have also been referred to as an /alternate name depending on the user..
PENNSYLVANIA GAME COMMISSION 12000-12090?
  • NW Dispatch Franklin - 12000
  • NW Dispatch 2 Secure - 12001
  • NW Region Talkaround - 12002
  • PGC Statewide - 12003
  • NW LE Tac 1 - 12004
  • NW LE Tac 2 - 12005
  • NW LE Tac 3 - 12006
  • NW Fire Talkaround/Fire Ops 1 - 12007
  • NW Admin Talkaround - 12008
  • - 12009
  • PGC Statewide Fire Ops 1 - 12010 LANC33/VENA12
  • PGC Statewide Fire Ops 2 - 12011 LANC33
  • PGC Statewide Fire Ops 3 - 12012 LANC33 (2/28/2019)
  • - 12013
  • - 12014
  • SW Dispatch Ligonier - 12015
  • SW Dispatch 2 Secure - 12016
  • SW Region Talkaround - 12017
  • SW LE Tac 1 - 12018
  • SW LE Tac 2 - 12019
  • SW LE Tac 3 - 12020
  • SW Fire Talkaround/Fire Ops 1 - 12021
  • SW Admin Talkaround - 12022
  • - 12023
  • NC Dispatch Avis - 12024
  • NC Dispatch 2 Secure - 12025
  • NC Region Talkaround - 12026
  • NC LE Tac 1 - 12027
  • NC LE Tac 2 - 12028
  • NC LE Tac 3 - 12029
  • NC Fire Talkaround/Fire Ops 1 - 12030
  • NC Admin Talkaround - 12031
  • - 12032
  • SC Dispatch Huntingdon - 12033
  • SC Dispatch 2 Secure - 12034
  • SC Region Talkaround - 12035
  • SC LE Tac 1 - 12036
  • SC LE Tac 2 - 12037
  • SC LE Tac 3 - 12038
  • SC Fire Talkaround/Fire Ops 1 - 12039
  • SC Admin Talkaround - 12040
  • - 12041
  • NE Dispatch Dallas - 12042
  • NE Dispatch 2 Secure - 12043
  • NE Region Talkaround - 12044
  • NE LE Tac 1 - 12045
  • NE LE Tac 2 - 12046 PIKE31 (03/04/2020)
  • NE LE Tac 3 - 12047
  • NE Fire Talkaround/Fire Ops 1 - 12048 PIKE31 (03/04/2020)
  • NE Admin Talkaround - 12049
  • - 12050
  • SE Dispatch Reading - 12051
  • SE Dispatch 2 Secure - 12052
  • SE Region Talkaround - 12053
  • SE LE Tac 1 - 12054
  • SE LE Tac 2 - 12055
  • SE LE Tac 3 - 12056
  • SE Fire Talkaround/Fire Ops 1 - 12057
  • SE Admin Talkaround - 12058
  • - 12059
  • SW Fire Ops 2? - 12060 CAMB02 (11/24/2019)
  • SW Fire Ops 3? - 12061
  • SW Fire Ops 4? - 12062
  • SW Fire Ops 5? - 12063
  • SW Fire Ops 6? - 12064
  • NW Fire Ops 2? - 12065
  • NW Fire Ops 3? - 12066
  • NW Fire Ops 4? - 12067
  • NW Fire Ops 5? - 12068
  • NW Fire Ops 6? - 12069
  • NC Fire Ops 2? - 12070 CHES31 (04/02/2020) [RID 1224062]
  • NC Fire Ops 3? - 12071
  • NC Fire Ops 4? - 12072
  • NC Fire Ops 5? - 12073
  • NC Fire Ops 6? - 12074
  • - 12075
  • NE Fire Ops 2 - 12076 PIKE31 (03/04/2020)
  • NE Fire Ops 3 - 12077 PIKE31 (03/04/2020)
  • NE Fire Ops 4? - 12078 PIKE31 (03/04/2020)
  • NE Fire Ops 5? - 12079
  • NE Fire Ops 6? - 12080
  • SE Fire Ops 2 - 12081 LANC33 (11/15/2019)
  • SE Fire Ops 3 - 12082 LANC33 (10/02/2019)
  • SE Fire Ops 4? - 12083
  • SE Fire Ops 5? - 12084
  • SE Fire Ops 6? - 12085 LANC33 (04/17/2019)
  • SC Fire Ops 2? - 12086 LANC33 (04/17/2019)
  • SC Fire Ops 3? - 12087
  • SC Fire Ops 4? - 12088 LANC33 (09/14/2019)
  • SC Fire Ops 5? - 12089
  • SC Fire Ops 6? - 12090 LANC33 (02/13/2020)
  • :unsure:

It's my opinion that the master page with all TG's listed be kept current, If someone wants all that other extra work.. It's on those that feel they're necessary to do the updates on them if they want them :LOL:

The Pertinent information was salvaged..
Scroll to the bottom of this page lately.. :unsure:
Also unconfirmed

Appears someone removed the link from the main page :oops: I fixed it..
Why are there so many differences in confirmed TG's on the research page and what appears in the official database? I'm seeing it in the PGC TG's for sure. Not just TG's themselves, but labeling also. Shouldn't all the confirmed ones be in the database too?
 

u2brent

OAMPT
Premium Subscriber
Joined
Jul 17, 2010
Messages
3,154
Location
KRWDPAXKRS1
Why are there so many differences in confirmed TG's on the research page and what appears in the official database? I'm seeing it in the PGC TG's for sure. Not just TG's themselves, but labeling also. Shouldn't all the confirmed ones be in the database too?

Therein lies the difference between Research, Confirmation, and then Submission follows.

The wiki is that "in between place".. (Where the wild things are :)) Like opening a door to a darkened closet and shining a light in one corner..
Can't see the whole picture, just what's in the lit corner that you can observe. The wiki pages are glimpses into what another member can see in their lit corner.

Eventually enough light gets shined in the closet by different viewers (or listeners) with different perspectives and at different times, that a picture can be painted of the contents of the whole closet..

Of course two people looking in the same corner might not see/descibe the same details..

It takes time.. Sometimes years to track down a TG's proper function/name.
The more participants/reports that are shared.. All the more closer to the solution of the puzzle is at hand.

When these wiki pages were started/created there were like two confirmed TG's in the RR DB. (and 4 Sites)
See where it's at now...

Well,, Yes, but what one considers confirmed may not be by another (They get posted to the wiki so other eyes can see this info and perhaps take the ball and run with it confirming or denying it's correct)

Of course all the air is taken out of the sails when somebody obtains some official info that reveals the truth.. (Think PSP)
Until then we have the wiki and all it's different template & research pages to play with and ponder over ;)
 
Top