New P25 System, LA City

I'm hearing two new P25 sites up in the Santa Clarita Valley - mostly simulcast traffic from LA City's (EDACS) System 2.


866.6125 (Control Channel)
System: 0D5 Site: 001
WACN: 92605 NAC: 0D6


866.3625 (Control Channel)
System: 0D5 Site: 008
WACN: 92065 NAC: 0DD

Good find!

If anyone has a scanner that can be used with Pro96com.
Please post the Tower*.txt log on the thread.

1.) It might log the "FCC license ID" for each site.
2.) Find the alternate control channels for each site.

Plus all the other info you can read on that software...

http://www.psredit.com/pro96com/

bcorbin said:

I'm hearing two new P25 sites up in the Santa Clarita Valley - mostly simulcast traffic from LA City's (EDACS) System 2.


866.6125 (Control Channel)
System: 0D5 Site: 001
WACN: 92605 NAC: 0D6


866.3625 (Control Channel)
System: 0D5 Site: 008
WACN: 92065 NAC: 0DD

Click to expand...

I can confirm some (EDACS) System 3 traffic as well, now, too...

The P25 Callsign Decoder comes up with WNVL7M. Searching by WNVL7 doesn't equate to anything useful. Sometimes the callsign decoder comes up with all or a portion of a valid callsign, sometimes it doesn't - usually when the sysid and WACN are something other than the "garden variety" BEE00 etc., you'd expect to find something meaningful there, even if it's a "vanity" response... for example, 580A0-001 comes up with "NCR A" - the 580A0 WACN is used by the National Capital Region system.

Maybe WNVL means something to the region or system builder.

EDIT: You've got two WACNs there. The above is for 92065. If you put in 92605, the result is WP2L7M which is even less helpful in an FCC license search.

WNVL470 (LOS ANGELES, CITY OF) FCC Callsign Details

WQPI386 (LOS ANGELES, CITY OF) FCC Callsign Details

It's probably one of those two licenses, both in the area and both have those two frequencies licensed.

Depending on the system manufacturer, WACN has nothing to do with the FCC call sign. For example, Motorola systems are almost always BEE00. Harris systems seem to be 9xxxx. EFJohnson lets the customer pick the WACN and system ID.

About 2-years ago LA City started a path to upgrade of the EDACS system. It will indeed become P25.

As I recall the timeframe was not till 2014 however.

Here is thread about the news:
http://forums.radioreference.com/gr...lans-p25-trunked-system-option-lafd-lapd.html


Also, LA County is going to do the same with its EDACS system. They were working with Sprint/Nextel on the agreement last time I heard.

Here is that thread:
http://forums.radioreference.com/gr...on/222842-laco-update-cwirs-p25-standard.html

=

Jay911 said:

The P25 Callsign Decoder comes up with WNVL7M. Searching by WNVL7 doesn't equate to anything useful. Sometimes the callsign decoder comes up with all or a portion of a valid callsign, sometimes it doesn't - usually when the sysid and WACN are something other than the "garden variety" BEE00 etc., you'd expect to find something meaningful there, even if it's a "vanity" response... for example, 580A0-001 comes up with "NCR A" - the 580A0 WACN is used by the National Capital Region system.

Maybe WNVL means something to the region or system builder.

EDIT: You've got two WACNs there. The above is for 92065. If you put in 92605, the result is WP2L7M which is even less helpful in an FCC license search.

Click to expand...

Ooops - the second WACN was a typo. Both should read 92065

Ran Unitrunker got following LCN line up:

Site 001:
866.1125 Alt Control
866.1375
866.3875 Alt Control
866.4125
866.6125 Control
866.6375
866.6875 Alt Control
867.1125 Alt Control

Site 008:
866.1875 Alt Control
866.3375
866.3625 Control
866.6875
866.8375 Alt Control
866.8625
867.1875 Alt Control
867.3375
867.3625 Alt Control
867.6875
867.8375


If anyone has time, be interesting to listen to EDACS also and compared TGs. Noted new system TG seem to be 20xxx and 65xxx series.

Once we get some more info, I'll build the system in the Db, so please submit your findings.

I managed to match up following TGs so far. Its definitely set up as a patch at the moment. Once can clearly hear the delay on the P25 system.

EDACS TG / new P25 TG
01-046 = 20166
01-047 = 65350, 65364, 65366
01-050 = 65360
01-051 = 20169
01-065 = 20181
01-066 = 20182
01-167 = 65343
04-090 = 20584
04-094 = 20588
04-121 = 20609
04-127 = 20615

I only noted DOT, GenSvc and Zoo TG activity. None for Sanitation, Animal Control, etc.


Regarding the sites and trolling the FCC licences looks there could be 6 eventual sites.

Baldwin Hills
WQPI387 (LOS ANGELES, CITY OF) FCC Callsign Details

Mount Lukens
WQPI386 (LOS ANGELES, CITY OF) FCC Callsign Details

Mount Lee
WNVL468 (LOS ANGELES, CITY OF) FCC Callsign Details

Rolling Hills
WNVL469 (LOS ANGELES, CITY OF) FCC Callsign Details

Oat Mountain
WNVL470 (LOS ANGELES, CITY OF) FCC Callsign Details

Mount Washington
WPFN690 (LOS ANGELES, CITY OF) FCC Callsign Details

=

LAflyer said:

I managed to match up following TGs so far. Its definitely set up as a patch at the moment. Once can clearly hear the delay on the P25 system.

EDACS TG / new P25 TG
01-046 = 20166
01-047 = 65350, 65364, 65366
01-050 = 65360
01-051 = 20169
01-065 = 20181
01-066 = 20182
01-167 = 65343
04-090 = 20584
04-094 = 20588
04-121 = 20609
04-127 = 20615

Click to expand...

If you use the EDACS DEC TGID instead of AFS, you'll see that many of them match up to the new P25 TGID:

AFS = EDACS DEC = P25 DEC
01-046 = 166 = 20166
01-051 = 169 = 20169
01-065 = 181 = 20181
01-066 = 182 = 20182
04-090 = 584 = 20584
04-094 = 588 = 20588
04-121 = 609 = 20609
04-127 = 615 = 20615

Looks like they've made the conversion pretty easy for you guys to map out.

Thanks for that help Chauffeur.



Also if there is anyone out there that can help ID the transmission location of Site 001 and 008, that be helpful.

For info, from the MidCity/Beverly Hills area I manage to receive both sites about 80-85% with 008 slightly stronger. So I doubt either one is Mt. Lee or Baldwin Hills sites due closeness.

Be interesting to see how others in the basin receive the control channels.

One of the sites is going to be Oat. Anyone's guess where the other one is, but both sound pretty good up in the SCV - and that's not easy for most of LA City's sites.

I did manage to get Pro96Com up and working (anyone have any tips for Unitrunker with a Pro-197?)... Was going to report the frequency list, and saw LAFlyer beat me to it. 8*)

From what I can tell, the 20### tg's are authentic tg's and the 65###'s are patches. The 65###'s appear to be dynamically-assigned, so don't take any EDACS<-> 65### map too seriously just yet.

EDIT: Pro96Com is reporting 866.8875 as an alternate CC (System 001), not 866.6875 --> Any chance that was a typo??

Correct 866.6875 was a typo -- 866.8875 is correct one.

Merry Xmas all.

Built the new P25 system in Db.
Los Angeles City (Municipal Services) P25 Trunking System, Los Angeles, California - Scanner Frequencies


Please submit updates for additional sites, confirmed TGs etc.

Yes appears the 65xxx series seem to be the same as the 15-xxx cross patch TGs that are utilized between the two EDACS systems.

I'm going to be a little too busy to follow up on this until after the new year, but here are some random thoughts that might be useful...

Pro96Com does a pretty good job mapping the assignment of primary (20###) talkgroups to patch talkgroups (65###). If you leave it running long enough, you'll probably get a decent starter-list of primary talkgroups (well, for those that are patched, anyway). If there is a way to generate a general list of talkgroup hits in Pro96Com, I haven't seen it (I think it can be done in Unitrunker) - but it would be useful to see which primary talkgroups are appearing where... It would be interesting to see if systems 001 and 008 are actually both on Oat, and dividing traffic like Sys 2 and Sys3. I think the presence of the patch groups has obfuscated that to some extent.

It might also be worth making a quick cheat-sheet from Chauffeur's EDACS-DEC->P25-DEC hint and using that as a starting point for confirming the identity of the P25 talkgroups. If I can steal a few minutes, I'll try to put something together...

EDIT: Alrighty - I put together a quick cheat-sheet, culled from the information that was available for the EDACS system, with the information from this thread folded in - it should be attached...

bcorbin said:

It might also be worth making a quick cheat-sheet from Chauffeur's EDACS-DEC->P25-DEC hint and using that as a starting point for confirming the identity of the P25 talkgroups. If I can steal a few minutes, I'll try to put something together...

Click to expand...

Ask, and ye shall receive.

Out of curiosity, how are you guys dealing with the frequencies that conflict between the EDACS and P25 systems? I notice some of them now in use for the P25 system are (or were) control channels for the EDACS system. 866.6125, for example, is a control channel on the P25 system and is also flagged as a control channel for System 2 of the EDACS system.

Thanks 8*) You beat me to it 8*)

My guess would be the control channels have been taken out of service for the EDACS system. I'm assuming the voice channels have as well, but I haven't bothered to confirm it.

I'll get the unitrunker running on both 001 and 008 for a few hours on Thursday see what TGs we capture on each.