American Electric Power (AEP) P25 WACN 92715

[mtindor]

FYI - Wheeling is 1F7-32.32. Dresden is 1F6-32.32. That's the difference. It almost appears as if the guts in Wheeling may have been in Dresden at some point and then moved to Wheeling. For a week or two, Wheeling was reporting all of its neighbors as central Ohio neighbors. They finally fixed that. And Newcomerstown/Cambridge had shown Wheeling as a neighbor (with the Wheeling CC) for a period of time, and then those erroneous neighbors disappeared from Cambridge/Newcomerstown.

I suspect the neighbor list on Dresden will change / be updated in the near future. There are sites in that neighbor list that probably don't belong (like Bucyrus). So, in a week or so you should check Dresden site neighbors again and see if anything has changed.

Mike

 

[mtindor]

@phask -- And, with Pro96Com not running, you might want to check your Pro96Com folder and just remove any tower site files that reference 3232. Then fire up Pro96Com on the Dresden CC again and see if it shows all the same info.

Mike

 

[mtindor]

@phask Can you copy Mount Perry direct with Pro96Com running? If so, can you get the current neighbor list for it?

Thanks

Mike

 

[phask]

@phask Can you copy Mount Perry direct with Pro96Com running? If so, can you get the current neighbor list for it?

Thanks

Mike

I can - will do so later today.

 

[phask]

@phask -- And, with Pro96Com not running, you might want to check your Pro96Com folder and just remove any tower site files that reference 3232. Then fire up Pro96Com on the Dresden CC again and see if it shows all the same info.

Mike

This is with all sites removed. After importing site data from RR looks as it did before.

 

[phask]

I can - will do so later today.

Mt Perry

 

[mtindor]

@phask Thank you. Looks like no new sites close to/to the south of Mt Perry (yet). Keep in mind that both the Site Information screen and the System Activity screen are useful for any screenshots. The System Activity screen shows primary cc / alt CCs / and voice channels (if they were active during monitoring).

And if you are monitoring a site for which you are not getting a real good decode, you will want to monitor it for a longer period of time. For a strong site, all relevant info will ccome up in a matter of seconds. But for a site that is decoding poorly, it will take much longer for all information to populate.

Again, thanks for the update. Dresden is now in the DB.

And the Site 32 screenshot looks better now that it doesn't suggest that it is Wheeling.

Mike

 

[RakkFO]

It is weird that @phask is showing different neighbors than I am for Mt. Perry.

2020/03/15 18:29:50 Current site: 99.99
2020/03/15 18:29:51 Current network: 92715.1F6 American Electric Power (P25)
2020/03/15 18:29:52 Current site: 92715.1F6-99.99 Mount Perry (Perry)
2020/03/15 18:29:53 92715.1F6-99.99 neighbor: Site 92715.1F6-42.42; CC=0-453 856.6625 Zanesville (Muskingum)
2020/03/15 18:29:54 92715.1F6-99.99 neighbor: Site 92715.1F6-32.32; CC=0-327 855.0875
2020/03/15 18:29:56 92715.1F6-99.99 neighbor: Site 92715.1F6-84.84; CC=0-289 854.6125
2020/03/15 18:29:57 92715.1F6-99.99 neighbor: Site 92715.1F6-33.33; CC=0-331 855.1375 Etna (Licking)
2020/03/15 18:29:58 92715.1F6-99.99 neighbor: Site 92715.1F6-72.72; CC=0-253 854.1625 Lancaster (Fairfield)
2020/03/15 18:29:59 92715.1F6-99.99 neighbor: Site 92715.1F6-35.35; CC=0-241 854.0125 Newark (Licking)

---------------------------

Site: 99.99 NAC=063 ; Mount Perry (Perry)

Neighbor: 92715.1F6-32.32
Neighbor: 92715.1F6-33.33 ; Etna (Licking)
Neighbor: 92715.1F6-35.35 ; Newark (Licking)
Neighbor: 92715.1F6-42.42 ; Zanesville (Muskingum)
Neighbor: 92715.1F6-72.72 ; Lancaster (Fairfield)
Neighbor: 92715.1F6-84.84

Channel 0-347: 855.3375 SCC
Channel 0-521: 857.5125 SCC
Channel 0-605: 858.5625 CC

 

[mtindor]

It is weird that @phask is showing different neighbors than I am for Mt. Perry.

2020/03/15 18:29:50 Current site: 99.99
2020/03/15 18:29:51 Current network: 92715.1F6 American Electric Power (P25)
2020/03/15 18:29:52 Current site: 92715.1F6-99.99 Mount Perry (Perry)
2020/03/15 18:29:53 92715.1F6-99.99 neighbor: Site 92715.1F6-42.42; CC=0-453 856.6625 Zanesville (Muskingum)
2020/03/15 18:29:54 92715.1F6-99.99 neighbor: Site 92715.1F6-32.32; CC=0-327 855.0875
2020/03/15 18:29:56 92715.1F6-99.99 neighbor: Site 92715.1F6-84.84; CC=0-289 854.6125
2020/03/15 18:29:57 92715.1F6-99.99 neighbor: Site 92715.1F6-33.33; CC=0-331 855.1375 Etna (Licking)
2020/03/15 18:29:58 92715.1F6-99.99 neighbor: Site 92715.1F6-72.72; CC=0-253 854.1625 Lancaster (Fairfield)
2020/03/15 18:29:59 92715.1F6-99.99 neighbor: Site 92715.1F6-35.35; CC=0-241 854.0125 Newark (Licking)

---------------------------

Site: 99.99 NAC=063 ; Mount Perry (Perry)

Neighbor: 92715.1F6-32.32
Neighbor: 92715.1F6-33.33 ; Etna (Licking)
Neighbor: 92715.1F6-35.35 ; Newark (Licking)
Neighbor: 92715.1F6-42.42 ; Zanesville (Muskingum)
Neighbor: 92715.1F6-72.72 ; Lancaster (Fairfield)
Neighbor: 92715.1F6-84.84

Channel 0-347: 855.3375 SCC
Channel 0-521: 857.5125 SCC
Channel 0-605: 858.5625 CC

Thank you. I suspect his shows different because Pro96Com seems to keep / add to potentially outdated information. That is why, for site 32.32, I had asked him to clear out his tower-site files for that site.

Mike

 

[RakkFO]

91 is on line!

2020/03/15 18:23:22 Current site: 91.91
2020/03/15 18:23:22 Current network: 92715.1F6 American Electric Power (P25)
2020/03/15 18:23:22 Current site: 92715.1F6-91.91
2020/03/15 18:23:23 92715.1F6-91.91 neighbor: Site 92715.1F6-35.35; CC=0-241 854.0125 Newark (Licking)
2020/03/15 18:23:23 92715.1F6-91.91 neighbor: Site 92715.1F6-42.42; CC=0-453 856.6625 Zanesville (Muskingum)
2020/03/15 18:23:24 92715.1F6-91.91 neighbor: Site 92715.1F6-44.44; CC=0-313 854.9125 Johnstown (Licking)
2020/03/15 18:23:24 92715.1F6-91.91 neighbor: Site 92715.1F6-46.46; CC=0-297 854.7125 Leonardsburg (Delaware)
2020/03/15 18:23:24 92715.1F6-91.91 neighbor: Site 92715.1F6-30.30; CC=0-509 857.3625 FAILED, Info Outdated, ISOLATED
2020/03/15 18:23:25 92715.1F6-91.91 neighbor: Site 92715.1F6-32.32; CC=0-327 855.0875
2020/03/15 18:23:25 92715.1F6-91.91 neighbor: Site 92715.1F6-33.33; CC=0-331 855.1375 Etna (Licking)

------------------

Site: 91.91 NAC=05B

Neighbor: 92715.1F6-30.30
Neighbor: 92715.1F6-32.32
Neighbor: 92715.1F6-33.33 ; Etna (Licking)
Neighbor: 92715.1F6-35.35 ; Newark (Licking)
Neighbor: 92715.1F6-42.42 ; Zanesville (Muskingum)
Neighbor: 92715.1F6-44.44 ; Johnstown (Licking)
Neighbor: 92715.1F6-46.46 ; Leonardsburg (Delaware)

Channel 0-261: 854.2625 CC
Channel 0-387: 855.8375 SCC
Channel 0-549: 857.8625 SCC

 

[mtindor]

91 is on line!

2020/03/15 18:23:22 Current site: 91.91
2020/03/15 18:23:22 Current network: 92715.1F6 American Electric Power (P25)
2020/03/15 18:23:22 Current site: 92715.1F6-91.91
2020/03/15 18:23:23 92715.1F6-91.91 neighbor: Site 92715.1F6-35.35; CC=0-241 854.0125 Newark (Licking)
2020/03/15 18:23:23 92715.1F6-91.91 neighbor: Site 92715.1F6-42.42; CC=0-453 856.6625 Zanesville (Muskingum)
2020/03/15 18:23:24 92715.1F6-91.91 neighbor: Site 92715.1F6-44.44; CC=0-313 854.9125 Johnstown (Licking)
2020/03/15 18:23:24 92715.1F6-91.91 neighbor: Site 92715.1F6-46.46; CC=0-297 854.7125 Leonardsburg (Delaware)
2020/03/15 18:23:24 92715.1F6-91.91 neighbor: Site 92715.1F6-30.30; CC=0-509 857.3625 FAILED, Info Outdated, ISOLATED
2020/03/15 18:23:25 92715.1F6-91.91 neighbor: Site 92715.1F6-32.32; CC=0-327 855.0875
2020/03/15 18:23:25 92715.1F6-91.91 neighbor: Site 92715.1F6-33.33; CC=0-331 855.1375 Etna (Licking)

------------------

Site: 91.91 NAC=05B

Neighbor: 92715.1F6-30.30
Neighbor: 92715.1F6-32.32
Neighbor: 92715.1F6-33.33 ; Etna (Licking)
Neighbor: 92715.1F6-35.35 ; Newark (Licking)
Neighbor: 92715.1F6-42.42 ; Zanesville (Muskingum)
Neighbor: 92715.1F6-44.44 ; Johnstown (Licking)
Neighbor: 92715.1F6-46.46 ; Leonardsburg (Delaware)

Channel 0-261: 854.2625 CC
Channel 0-387: 855.8375 SCC
Channel 0-549: 857.8625 SCC

Sweet! Thank you

Mike

 

[RakkFO]

also have 32!

2020/03/15 18:23:51 Current site: 32.32
2020/03/15 18:23:53 Current site: 32.32
2020/03/15 18:23:54 Current network: 92715.1F6 American Electric Power (P25)
2020/03/15 18:23:55 Current site: 92715.1F6-32.32
2020/03/15 18:23:58 92715.1F6-32.32 neighbor: Site 92715.1F6-99.99; CC=0-605 858.5625 Mount Perry (Perry)
2020/03/15 18:23:58 92715.1F6-32.32 neighbor: Site 92715.1F6-3.3; CC=0-827 861.3375 Bucyrus (Crawford)
2020/03/15 18:23:59 92715.1F6-32.32 neighbor: Site 92715.1F6-35.35; CC=0-241 854.0125 Newark (Licking)
2020/03/15 18:23:59 92715.1F6-32.32 neighbor: Site 92715.1F6-36.36; CC=0-355 855.4375 Newcomerstown (Tuscarawas)
2020/03/15 18:24:00 92715.1F6-32.32 neighbor: Site 92715.1F6-40.40; CC=0-381 855.7625 Cambridge (Guernsey)
2020/03/15 18:24:00 92715.1F6-32.32 neighbor: Site 92715.1F6-42.42; CC=0-453 856.6625 Zanesville (Muskingum)
2020/03/15 18:24:00 92715.1F6-32.32 neighbor: Site 92715.1F6-44.44; CC=0-313 854.9125 Johnstown (Licking)
2020/03/15 18:24:01 92715.1F6-32.32 neighbor: Site 92715.1F6-77.77; CC=0-491 857.1375 McConnellsville (Morgan)
2020/03/15 18:24:01 92715.1F6-32.32 neighbor: Site 92715.1F6-91.91; CC=0-261 854.2625

---------------

Site: 32.32 NAC=020

Neighbor: 92715.1F6-3.3 ; Bucyrus (Crawford)
Neighbor: 92715.1F6-35.35 ; Newark (Licking)
Neighbor: 92715.1F6-36.36 ; Newcomerstown (Tuscarawas)
Neighbor: 92715.1F6-40.40 ; Cambridge (Guernsey)
Neighbor: 92715.1F6-42.42 ; Zanesville (Muskingum)
Neighbor: 92715.1F6-44.44 ; Johnstown (Licking)
Neighbor: 92715.1F6-77.77 ; McConnellsville (Morgan)
Neighbor: 92715.1F6-91.91
Neighbor: 92715.1F6-99.99 ; Mount Perry (Perry)

Channel 0-327: 855.0875 CC
Channel 0-345: 855.3125 SCC
Channel 0-427: 856.3375 SCC

 

[mtindor]

91 is on line!

2020/03/15 18:23:24 92715.1F6-91.91 neighbor: Site 92715.1F6-30.30; CC=0-509 857.3625 FAILED, Info Outdated, ISOLATED

I see this often, where a new site is going to come online but the referenced freq in the neighbor's neighbor list shows a frequency that is/was never FCC-assigned to the site. And when that site ends up coming online it's using a valid FCC-licensed freq for the site and not hte one listed in the neighbor.

So, for 30.30, we probably won't be able to identify the site until it's online and reflected as online when monitoring Utica. I don't know if you can pull in Utica directly or if you have to do some wardriving. But it would pay to check Utica whenever you can in a week or two and see if the 30.30 neighbor ends up being connected. Once it is, I imagine it will list the proper frequency and we'll be able to identify it.

Mike

 

[n8jsw]

Sounds like Philo came online today. Anyone in that area able to confirm?

 

[mtindor]

Sounds like Philo came online today. Anyone in that area able to confirm?

For those who might investigate Philo:

854.7125
856.8375
857.8875
858.4125
859.3375

m

 

[mtindor]

@phask Paul, Josh (@n8jsw) picked up radio techs talking about the fact that they turned up Philo -- currently running "hybrid" with three P25 channels and two EDACS channels.

I don't know if you could pull in Philo directly or not. Could you check? If you can, please screenshot and post both relevant tabs in Pro96Com. if you are unable to pull in Philo, the Zanesville, Dresden and Mount Perry sites (among others) should eventually be listing a new site neighbor that would likely be Philo. So you may want to check those sites for a new site neighbor if you can't pull in Philo directly.

The Philo control channel would likely be one of these freqs:

854.7125
856.8375
857.8875
858.4125
859.3375

Thanks!

Mike

 

[phask]

@phask Paul, Josh (@n8jsw) picked up radio techs talking about the fact that they turned up Philo -- currently running "hybrid" with three P25 channels and two EDACS channels.

I don't know if you could pull in Philo directly or not. Could you check? If you can, please screenshot and post both relevant tabs in Pro96Com. if you are unable to pull in Philo, the Zanesville, Dresden and Mount Perry sites (among others) should eventually be listing a new site neighbor that would likely be Philo. So you may want to check those sites for a new site neighbor if you can't pull in Philo directly.

The Philo control channel would likely be one of these freqs:

854.7125
856.8375
857.8875
858.4125
859.3375

Thanks!

Mike

I get a strong carrier (and digital noise) on 857.8875, but no decode. That might still be the EDACS/ I could get the EDACS before.

I'll keep checking. It might show better on dongle and Unitrunker, but I just have oo many issues when I try and run it.

 

[mtindor]

I get a strong carrier (and digital noise) on 857.8875, but no decode. That might still be the EDACS/ I could get the EDACS before.

I'll keep checking. It might show better on dongle and Unitrunker, but I just have oo many issues when I try and run it.

Hi Paul,

You are probably copying the EDACS control channel. ALthough, if you are doing this on a scanner in Search mode, I would think that it would come up and display something about the control channel whether it were EDACS or P25. I'm fairly certain that the P25 is up and online though, and it would be on one of the frequencies above. So just check them all whenever you are able with Unitrunker.... if you are able.

Good luck, and thanks for being willing to check!

Mike

 

[n8jsw]

Also Philo should be a peer with Zanesville and should give you a frequency there as what they are using on P25.

 

[phask]

854.7125 shows as P25 (using search).
FWIW - I'm scanning Mt Perry , Zville , Dresden and Philo. Only actual traffic I've seen (logging also) is Zville.