phillydjdan
Member
- Joined
- Jan 27, 2011
- Messages
- 2,075
Bob, the only thing I think you and I would be interested in is the PennDOT patrol tow trucks on 95. They should end up on this system eventually...
- Joined
- Feb 22, 2007
- Messages
- 5,638
That sounds interesting.
WB3DYE
Silent Key
I remember a few years ago the state called a news conference to "announce" how PSP choppers could talk to PSP ground units using Open Sky. A majority went with the states information without checking further. PSP choppers had a second programable transceiver onboard for years and routinely talked to PSP and local first responders ground units using their VHF system.
ChrisRupert
Member
That could be possible, depends if they keep everything on a unified dispatch as they do now. Besides local fire and EMS the local tow truck companies have radios too.
If they are building a completely separate isolated system just for the turnpike, that sounds wasteful and counterproductive. If they built a series of 700 sites that optimize coverage for the turnpike and connect to STARNet that would make more sense. More coverage for the state system users and easier interop.
1.65 has lost another neighbor, IDK what's going on.. first 1.69 Oxford, now 1.70 Devault...
Something must be up/changing? Hmm..
Something must be up/changing? Hmm..
Makes sense to me.1.65 has lost another neighbor, IDK what's going on.. first 1.69 Oxford, now 1.70 Devault...
Something must be up/changing? Hmm..
69 Oxford is not currently on the air, correct? No point in having an inactive site as a neighbor.
70 Devault is further away from Truce to the east than both 76 Morgantown and 79 Hibernia Park, so it makes sense to remove that as a neighbor.
The only site I'm a little surprised is not currently a neighbor to Truce is 56 Red Lion, which is just to the west.
Map Legend
Green = 65 Truce
Purple = Current neighbor sites of 65 Truce
Orange = Nearby sites that are not a neighbor of 65 Truce
Yep, (here goes)
1.56 was a neighbor for a few days, then removed again.
1.70 has been a neighbor since the site came online.. Why bother removing it now?
Same for 1.69 (which was never online). Sooo.. Why now? What up? Does anyone know? Has anyone seen similar activity on other sites?Just housekeeping? Why not correct the BSI?
Why? Why? Why? Very nice map..
LOL you're too much sometimes!Yep, (here goes)
1.56 was a neighbor for a few days, then removed again.
1.70 has been a neighbor since the site came online.. Why bother removing it now?
Just housekeeping? Why not correct the BSI?
Very nice map..
In reality, none of this shuffling around is unexpected. It's all part of letting the dust settle and determining the best configurations. Frankly, you'll only drive yourself crazy trying to keep up with some of the changes they'll be making as more sites come online. New sites = potentially reshuffled neighbor lists, which is to be expected especially if a newer site is closer than an existing site.
Just because Devault has been a neighbor of Truce since the site came online, doesn't mean it's a good idea for it to remain that way. There are two sites in between Truce and Devault, and so you want to encourage radios heading east that go out of range of Truce to affiliate with those two sites, rather than looking for Devault.
I've actually got a map created that shows different colors for the frequencies at each site (FCC VHF, NTIA VHF, UHF, 800).
Thanks Buddy!LOL you're too much sometimes!
Just because Devault has been a neighbor of Truce since the site came online, doesn't mean it's a good idea for it to remain that way. There are two sites in between Truce and Devault, and so you want to encourage radios heading east that go out of range of Truce to affiliate with those two sites, rather than looking for Devault.
I didn't think the real radios actually looked at the NL's transmitted by sites.. Technically they are not needed, (Was my understanding anyway). IDK
If so; For instance, How would PECO radios know where to look for a CC? Their sites don't transmit one at all.. Sorry.. Off topic..
The subscriber radios do receive and process any adjacent site list being broadcast. The contents of that list is stored in the radio's memory, so that if they lose the control channel of the site they're currently on, the first thing they will do is check the frequencies of those adjacent sites looking for an active control channel. This can occur if they go out of range, or if the RSSI value drops below a certain threshold and one of the adjacent sites has a stronger signal.Thanks Buddy!
I didn't think the real radios actually looked at the NL's transmitted by sites.. Technically they are not needed, (Was my understanding anyway). IDK
If so; For instance, How would PECO radios know where to look for a CC? Their sites don't transmit one at all.. Sorry.. Off topic..
That is the first preference, to look at the adjacent site list. If no control channels are found that way, then the radio will start to look at all of the control channels programmed into the codeplug. That's obviously not as quick or efficient. If no control channels are found at that point, the radio may optionally perform a "full spectrum scan" looking for any control channel that matches the programmed system (that option has to be enabled in the codeplug, it's normally not the default).
If no adjacent site list is broadcast, then the radio is only able to look at the control channels that are programmed into the codeplug, otherwise it simply goes out of range.
While adjacent site lists broadcast over the control channels may not be fundamentally necessary, they certainly increase efficiency. It's much easier for a radio to check 4-5 announced active neighbor control channels than it is to start hunting through a long list of programmed control channels (which includes all of the alternate control frequencies).
One of these days I may actually give a short answer to one of these questions.
Is anyone interested in logs for this system anymore? I haven't seen any posted in a while.
Here is some logging from monitoring Stroudsburg Site 96 over the past few days. @u2brent if you want to see how this fits into the wiki, you're more than welcome...I'm just too lazy to get into editing that at the moment.
Here is some logging from monitoring Stroudsburg Site 96 over the past few days. @u2brent if you want to see how this fits into the wiki, you're more than welcome...I'm just too lazy to get into editing that at the moment.
Code:
10001 0 0000/00/00
10030 0 0000/00/00
10053 0 0000/00/00
10054 1 2019/06/22
10101 2 2019/06/21 PSP A1 Greensburg
10147 0 0000/00/00 PSP G5 McConnellsburg
10151 6 2019/06/20 PSP H1 Harrisburg
10163 0 0000/00/00 PSP K1 Philadelphia
10165 5 2019/06/21 PSP K3 Skippack
10173 1799 2019/06/22 PSP M1 Bethlehem
10174 69 2019/06/22 PSP M2 Dublin
10176 709 2019/06/22 PSP M5 Fogelsville
10177 1000 2019/06/22 PSP M6 Belfast
12042 0 0000/00/00
12043 0 0000/00/00
12044 0 0000/00/00
12051 145 2019/06/22 PGC SE Disp 1
Code:
10030
1201328 6 2019/06/13
10151 PSP H1 Harrisburg
80 3 2019/06/20
1201016 1 2019/06/20
10163 PSP K1 Philadelphia
1201360 0 0000/00/00
10165 PSP K3 Skippack
107 1 2019/06/21
1201404 2 2019/06/14
1201460 0 0000/00/00
1201463 2 2019/06/21
10173 PSP M1 Bethlehem
117 482 2019/06/22
118 208 2019/06/22
1201315 2 2019/06/21
1201318 42 2019/06/21
1201487 1 2019/06/20
1201490 35 2019/06/22
1201491 15 2019/06/21
1201492 45 2019/06/22
1201493 21 2019/06/22
1201494 27 2019/06/22
1201495 17 2019/06/21
1201496 42 2019/06/22
1201497 20 2019/06/22
1201498 27 2019/06/22
1201499 65 2019/06/22
1201500 107 2019/06/22
1201501 15 2019/06/22
1201502 57 2019/06/22
1201503 26 2019/06/22
1201504 25 2019/06/21
1201505 6 2019/06/20
1201507 4 2019/06/20
1201508 31 2019/06/21
1201509 7 2019/06/21
1201510 7 2019/06/21
1201513 16 2019/06/22
1201515 9 2019/06/21
1201516 12 2019/06/22
1201521 23 2019/06/22
1201525 23 2019/06/22
1201526 10 2019/06/20
1201571 5 2019/06/21
1201593 18 2019/06/22
1204878 3 2019/06/21
1204879 34 2019/06/22
1204881 19 2019/06/22
1204882 3 2019/06/21
1204883 33 2019/06/22
1204884 52 2019/06/21
1204885 14 2019/06/21
1204886 5 2019/06/21
1204887 8 2019/06/22
1204888 16 2019/06/22
1204890 34 2019/06/22
1204891 6 2019/06/22
1204892 7 2019/06/22
1204894 5 2019/06/21
1204896 32 2019/06/21
1204897 5 2019/06/22
1204898 8 2019/06/22
1204899 8 2019/06/22
1204900 12 2019/06/22
1204902 11 2019/06/21
1204905 19 2019/06/22
1204913 29 2019/06/22
1204914 7 2019/06/21
10174 PSP M2 Dublin
113 26 2019/06/22
1200812 8 2019/06/21
1201572 11 2019/06/21
1201573 1 2019/06/21
1201575 8 2019/06/22
1201577 24 2019/06/21
1201580 6 2019/06/22
1201584 1 2019/06/21
1204936 4 2019/06/22
1204940 1 2019/06/20
10176 PSP M5 Fogelsville
120 240 2019/06/22
121 37 2019/06/22
1201238 5 2019/06/21
1201319 1 2019/06/21
1201596 25 2019/06/22
1201597 8 2019/06/21
1201599 7 2019/06/21
1201600 18 2019/06/22
1201602 12 2019/06/21
1201603 22 2019/06/22
1201604 35 2019/06/21
1201605 27 2019/06/21
1201607 36 2019/06/22
1201608 4 2019/06/22
1201609 23 2019/06/22
1201610 4 2019/06/21
1201611 0 0000/00/00
1201612 30 2019/06/22
1201620 6 2019/06/21
1204961 7 2019/06/22
1204963 13 2019/06/22
1204967 2 2019/06/21
1204968 2 2019/06/21
1204971 3 2019/06/22
1204974 2 2019/06/21
1204975 1 2019/06/21
1204982 2 2019/06/21
1204985 1 2019/06/21
1204990 1 2019/06/22
1204991 7 2019/06/22
1204993 12 2019/06/21
10177 PSP M6 Belfast
115 392 2019/06/22
116 9 2019/06/22
1201551 40 2019/06/22
1201552 46 2019/06/21
1201553 60 2019/06/22
1201554 9 2019/06/21
1201556 73 2019/06/22
1201557 103 2019/06/22
1201558 42 2019/06/21
1201559 46 2019/06/21
1201560 12 2019/06/21
1201561 118 2019/06/22
1201563 3 2019/06/21
1201564 31 2019/06/21
1201565 10 2019/06/22
1201567 25 2019/06/22
1201568 36 2019/06/22
1201601 0 0000/00/00
1201616 24 2019/06/22
1203060 6 2019/06/22
1204995 0 0000/00/00
1204997 4 2019/06/21
1204998 0 0000/00/00
1204999 59 2019/06/22
1205000 1 2019/06/21
1205001 48 2019/06/21
1205002 35 2019/06/22
1205003 33 2019/06/22
1205005 75 2019/06/22
1205006 48 2019/06/22
1205007 5 2019/06/14
1205008 11 2019/06/21
1205009 21 2019/06/20
1205010 1 2019/06/22
1205011 54 2019/06/22
1205012 8 2019/06/22
12042
1230116 0 0000/00/00
12044
1230104 0 0000/00/00
12051 PGC SE Disp 1
1230004 2 2019/06/13
1230082 3 2019/06/13
1230086 10 2019/06/20
1230089 17 2019/06/21
1230095 2 2019/06/22
1230096 6 2019/06/14
1233004 29 2019/06/22
1234035 6 2019/06/13
1234487 12 2019/06/14
1234488 4 2019/06/14
1234679 7 2019/06/13128 ID's addedIs anyone interested in logs for this system anymore? I haven't seen any posted in a while.
Here is some logging from monitoring Stroudsburg Site 96 over the past few days. @u2brent if you want to see how this fits into the wiki, you're more than welcome...I'm just too lazy to get into editing that at the moment.
Been picking up P25 data transmissions on some of those DVRS frequencies.. NAC 100 770.9187 for one..
From the Chester/Lancaster/York group..
769.43125
770.19375
770.21875
770.69375
770.91875
773.04375
Last edited:
Kind of off-topic, but meh...I was going through all of the PSP barracks last night, and it seems that N6 PSP Swiftwater is now PSP Stroudsburg, and C5 PSP Kane is now PSP Lewis Run. I made the changes on two of the PSP wiki pages, but it probably affects some of the trunked system wiki pages also.
EDIT: All instances in the wiki changed
EDIT: All instances in the wiki changed
Thanks!
One thing though.. You say you "Fix link to Fact Sheet" But it ain't working for me (now that it's fixed) Pennsylvania Statewide Radio Network (PA-STARNet) P25 IDK?
hundeesport412
Member
Just wondering if anyone entering the DOT Tg information is looking at what they are entering. This is what I downloaded tonight. The TG County name is cut off. Could Someone please correct these.
Actually, the issue is on your end, not with the database. You're having ProScan import the Channel Description field instead of the Alpha Tag (Display Name).
Uncheck that option when importing and it will use the 16 character Alpha Tags instead.
hundeesport412
Member
Thank You and I apologize To Data base people !!
