Do you get a CC on 159.3225 could have been a typo when discovered online, of course the FCC could have a mistake as wellAlthough I have Scenery Hill (Washington County) programmed in my BCD996P2 along with Claysville, I never heard from the site yet. I noticed the RadioReference lists the control channel for Scenery Hill as 159.3325 MHz but when I referenced the WQVVF847 FCC data it listed the frequency 159.3225 MHz. I am confused at the discrepancy. Just was wondering if anyone in Washington County ever monitored the Scenery Hill site.
I uploaded the PA StarNet P25 with 159.3225 MHz for Scenery Hill and still get "Finding CtrlChannel". I might be out-of-range for reception.I am changing the frequency to 159.3225 in ARCXT PRO to see if that makes a difference then I will upload it to the scanner.
Try direct frequency entry as I suggested above, adjust squelch to 1 or 2. If you don't hear or see anything then yes, you could be out of rangeI uploaded the PA StarNet P25 with 159.3225 MHz for Scenery Hill and still get "Finding CtrlChannel". I might be out-of-range for reception.
This is pretty much how it is going to be for a lot of folks...one day you may hear traffic and another day, none at all (even if there is still traffic on that talkgroup). Since most of the system is made up of standalone Astro Site Repeaters, you will usually only hear radio traffic if there is a user radio affiliated to the talkgroups you are trying to hear. No PGC radio affiliated? No PGC traffic. For the hobbyist, it can be frustrating because there may not be any consistency to what you can and cannot hear, especially in more rural locations with fewer radios within a particular tower's coverage area. But, still more fun than OpenSky....The other day I did here the State Game Commission on the McDonald 800 MHz site most of the day but the site is silent now. I will keep trying to see if I can hear Scenery Hill while awaiting the long-waited return of First Energy whenever they show up. Thanks for the quick reply - Appreciate it.
I've changed the frequency for the time being since the other one isn't a valid allocation.159.3325 is not a valid frequency by FCC standards, so it appears that jiminpgh had a typo in his post and it found its way into the database.
159.3225 is the correct frequency.