BM82557
Member
Mike, thanks for the Google map of the system. I see the site 1.95 info has already been updated!
1.95 has been added. If someone can grab a site NAC, we can update that.
BM82557
Member
!.95 is using NAC 948, I just submitted it.
An update for 1.65 LANC33 Truce.
New LCN active/BSI too! 154.4075 BSI 4-1763 (VC 8-3524/8-3525) WGVG945 (which is an obvious typo)
New LCN active/BSI too! 154.4075 BSI 4-1763 (VC 8-3524/8-3525) WGVG945 (which is an obvious typo)
Hours of back and forth today on 10138. This was seen in the Philly VHF site. Anyone log it elsewhere? Activity was logged from about noon to about 1600. Unitrunker never shows 302 with a "Joins" action, just the other two RIDs.
RIDS 302, 1200015, 1200008.
Anyone have these RIDS appearing on other talkgroups?
I've seen traffic like this before on other sites, also with 302...not sure if the 120xxxx RIDS are the same as before as I didn't write it down anywhere.
This activity is the one main thing that makes me still doubt the speculative talkgroup IDs. A lot of things seem to fall into place with our guesses, but I dont see why a few units would keep operating on PSP Mansfield dispatch (speculative ID for 10138) when there are so many talkgroup options for them.
RIDS 302, 1200015, 1200008.
Anyone have these RIDS appearing on other talkgroups?
I've seen traffic like this before on other sites, also with 302...not sure if the 120xxxx RIDS are the same as before as I didn't write it down anywhere.
This activity is the one main thing that makes me still doubt the speculative talkgroup IDs. A lot of things seem to fall into place with our guesses, but I dont see why a few units would keep operating on PSP Mansfield dispatch (speculative ID for 10138) when there are so many talkgroup options for them.
For whatever it's worth, Motorola loves to give the MCC 7500 system consoles three-digit IDs by default. Obviously they can be set to whatever the customer desires, but if not specified, you'll usually see the first consoles online start at 101 and go up from there. You'll also see where multiple dispatch centers might wind up with 1xx for one center, 2xx for another, 3xx for a third, and so on.
You will never see registration/affiliation (aka Login and Joins) for system consoles, even when the same console transmits on different talkgroups.
I'm not saying definitively that you're seeing a system console with 302, but it is something to keep in mind, especially if you see 302 on multiple talkgroups with no indication of an affiliation.
You will never see registration/affiliation (aka Login and Joins) for system consoles, even when the same console transmits on different talkgroups.
I'm not saying definitively that you're seeing a system console with 302, but it is something to keep in mind, especially if you see 302 on multiple talkgroups with no indication of an affiliation.
Good info. I had previously speculated the couple 3xx IDs I saw as consoles because of what you said (i.e. not affiliating), but I did not definitively know the info you shared.
So, if it is a console, what are they doing?
Looking back in the forum, 302 has also been reported on 10012 and 10131.
I suppose it could be possible they're using this talkgroup for some testing knowing that Mansfield will be one of the last stations transitioned and that TG will likely not be in anyone's scan group right now.
Hmmm.....
BM82557
Member
I've had 1200015 affiliate with TG 10160 the other day
302 TG 10012 10131 10138 10160
1200008 TG 10127 10138 10151 10160
1200009 TG 10001 10138 10159
1200015 TG 10131 10138 10160
1200016 TG 10131 10138
1200094 TG 10138 10151 10159 10160
Just makes me think this is the current favorite TG for integration activity, When F5 actually goes live they will have moved on or actually be finished...
Groups of 16:
Group 1
A1 Greensburg (Westmoreland)-10101
A2 Ebensburg (Cambria)-10102
A3 Indiana (Indiana)-10103
A4 Kiski Valley (Westmoreland)-10104
A6 Somerset (Somerset)-10105
B1 Washington (Washington)-10107
B2 Belle Vernon (Westmoreland)-10108
B3 Pittsburgh (Allegheny)-10109
B4 Uniontown (Fayette)-10110
B5 Waynesburg (Greene)-10111
C1 Punxsutawney (Jefferson)-10113
C2 Clarion (Clarion)-10114
C3 Clearfield (Clearfield)-10115
C4 DuBois (Jefferson)-10116
C5 Kane (McKean)-10117
C6 Ridgway (Elk)-10118
Group 2
C7 Marienville (Forest)-10119
D1 Butler (Butler)-10121
D2 Kittanning (Armstrong)-10122
D3 Mercer (Mercer)-10123
D4 Beaver (Beaver)-10124
D6 New Castle (Lawrence)-10125
E1 Erie (Erie)-10127
E2 Corry (Erie)-10128
E3 Franklin (Venango)-10129
E4 Girard (Erie)-10130
E5 Meadville (Crawford)-10131
E6 Warren (Warren)-10132
F1 Montoursville (Lycoming)-10134
F2 Coudersport (Potter)-10135
F3 Emporium (Cameron)-10136
F4 Lamar (Clinton)-10137
Group 3
F5 Mansfield (Tioga)-10138
F6 Milton (Northumberland)-10139
F7 Selinsgrove (Snyder)-10140
F8 Stonington (Northumberland)-10141
G1 Hollidaysburg (Blair)-10143
G2 Bedford (Bedford)-10144
G3 Huntingdon (Huntingdon)-10145
G4 Lewistown (Mifflin/Juniata)-10146
G5 McConnellsburg (Fulton)-10147
G7 Rockview (Centre)-10148
H1 Harrisburg (Dauphin)-10151
H2 Carlisle (Cumberland)-10152
H3 Chambersburg (Franklin)-10153
H4 Lykens (Dauphin)-10154
H5 Newport (Perry)-10155
H6 Gettysburg (Adams)-10156
Group 4
J4? York (York) [Formerly H7]-10157
J1 Lancaster (Lancaster)-10159
J2 Avondale (Chester)-10160
J3 Embreeville (Chester)-10161
K1 Philadelphia (Philadelphia)-10163
K2 Media (Delaware)-10164
K3 Skippack (Montgomery)-10165
L1 Reading (Berks)-10167
L2 Jonestown (Lebanon)-10168
L3 Frackville (Schuylkill)-10169
L4 Hamburg (Berks)-10170
L7 Schuylkill Haven (Schuylkill)-10171
M1 Bethlehem (Lehigh/Northampton)-10173
M2 Dublin (Bucks)-10174
M3 Trevose (Bucks)-10175
M5 Fogelsville (Lehigh)-10176
Group 5
M6 Belfast (Northampton)-10177
N1 Hazleton (Luzerne)-10179
N2 Bloomsburg (Columbia)-10180
N3 Fern Ridge (Monroe)-10181
N4 Lehighton (Carbon)-10182
N6 Stroudsburg (Monroe) [Swiftwater?]-10183
P1 Wyoming (Wyoming/Luzerne?)-10185
P2 Laporte (Sullivan)-10186
P4 Shickshinny (Luzerne)-10187
P5 Towanda (Bradford)-10188
P6 Tunkhannock (Wyoming)-10189
R1 Dunmore (Lackawanna)-10191
R3 Honesdale (Wayne)-10192
R4 Blooming Grove (Pike)-10193
R5 Gibson (Susquehanna)-10194
Don't know if there is a significance aside from my love of cutting pasting and hitting return.....
But there it is..
I wonder if he meant affiliation, or activity in general.
A bit of a disclaimer to my previous post, which is to say that obviously with such a large multi-site system, it's possible that you'd never see that 302 ID affiliating with a talkgroup depending on what site(s) you're monitoring (if it happens not to be a system console). Could very well be a portable in Harrisburg that's affiliating with particular talkgroups on the site local to that area, which of course could carry traffic 100 miles away on the Philly site. Someone looking at the Harrisburg site might see 302 affiliating, but you would not when looking at the Philly site.
True! It does make for some good entertainment, though. As long as all of the speculation is in good, clean fun and not taken as gospel until the facts prove things out, I think it's rather nice. Brings a lot of people together towards a common goal in mapping the system out. I suppose it bears gentle reminding that the wiki is for speculation, the database is for confirmation!
After reviewing today's 1.65 LANC33 event log; I can confirm the activity mentioned above on PHIL02 was on this site today as well.
in additional to those listed above another rid was discovered:
1200195 TG 10138 10159 10160
There was never an affiliation or registration request from 302 on 1.65 FWIW.
That's entertainment!
in additional to those listed above another rid was discovered:
1200195 TG 10138 10159 10160
There was never an affiliation or registration request from 302 on 1.65 FWIW.
That's entertainment!
FWIW, I have been seeing RID 9000022 get Registration: REFUSED on the regular on the Allegheny Simulcast. I think it must be something local that was misconfigured some time ago and has never been sorted out. I don't see it once and a while, I see it all the time. Sometimes all day long, sometimes in batches of 4 or 5 then not again until the next day.
BM82557
Member
There are two sites noted for CUMB04 in the FCC database. One appears to be the old site near the fire tower in Cumberland County (WPQE516), the other appears to be a new site with a much larger tower about a mile to the south in Adams County (WRAD754).
Obviously these are both 800 MHz licenses, but it is interesting to note that the newer license shows P25 emissions on 800 MHz. They filed a notice of construction last July for the new site.
https://www.radioreference.com/apps/db/?fccCallsign=WPQE516
https://www.radioreference.com/apps/db/?fccCallsign=WRAD754
The entry in the database shows the coordinates and county assignment for the old site. Perhaps someone in the area can check out the new site to verify if that's where the 171.6875 control channel is coming from.
the WRAD754 location info is correct, I hate to be the hair splitter, but both the NTIA 1.95 & new 800 (presumably 1.59) [note the number swap] are just inside Adams County (just as the license indicates). Also of note https://www.radioreference.com/apps/db/?fccCallsign=WQXY484 is at the same (Newer) location. BUT does it really matter much?
I believe the wiki is correct.. https://wiki.radioreference.com/ind..._Radio_Network_(PA-STARNet)_P25_Site_ResearchI reckon it needs further investigation & verification to be thorough.