Seattle Area WA State Patrol Phase 2 Trunking System - Some Verification Needed Please

[RBMTS]

Washington monitors - can anyone please verify what you see the WA State Patrol 700Mhz trunking system showing as the SystemID? The system was reported as showing a SysID of 715 which is the same as JIWN. The 700Mhz system was showing a RFSS site as 2 whereas the VHF system was showing an RFSS as 1. We ultimately combined the two into a single entity in the database to avoid duplication since all the info was the same.

We now have a user reporting that the 700Mhz system is showing a SysID of 9CC. As such I need to verify from others what is being shown. SysID and RFSS info for sites would be greatly appreciated. If the 700Mhz system is different now, I will bring back the WA State Patrol system into the active listing.

Your help is appreciated. Thank you.

 

[nessnet]

I was able to pick up the King Lake site just now. It was 9CC

 

[gmclam]

I believe they are TWO separate systems. I've always seen the WSP TG IDs to be the same on each system, but certainly everything on the WSP system is not on JIWN.

 

[nessnet]

I drove up to FEMA NW, which is located at top of the hill in Bothell. For those familiar, a pretty good line of sight spot.

Turned off location control, then ran through analyze on an SDS100. The only site I could decode was my previous post - King Lake. None others, including King Simulcast, which I find interesting.

The FEMA compound, where I was, is (was??) a WSP700 site. I used to get a strong signal from it at the house, now absolutely no signal while standing looking at the tower.

I ask - could y'all living in Puget Sound, post what they are seeing / hearing so we can get RR correct?

 

[MtnBiker2005]

Someone else reported site 201(King County Simulcast) was off the air on Saturday night. Maybe it’s not back on the air yet.

 

[freqseeker]

Washington monitors - can anyone please verify what you see the WA State Patrol 700Mhz trunking system showing as the SystemID? The system was reported as showing a SysID of 715 which is the same as JIWN. The 700Mhz system was showing a RFSS site as 2 whereas the VHF system was showing an RFSS as 1. We ultimately combined the two into a single entity in the database to avoid duplication since all the info was the same.

We now have a user reporting that the 700Mhz system is showing a SysID of 9CC. As such I need to verify from others what is being shown. SysID and RFSS info for sites would be greatly appreciated. If the 700Mhz system is different now, I will bring back the WA State Patrol system into the active listing.

Your help is appreciated. Thank you.

I can confirm King Simulcast is down.
Tacoma Simulcast is up. Showing Site 2 and System ID 9CC. South King 59210 is active on Tacoma Simulcast.
I will monitor both sites and log with ProScan.
These are not JIWN systems. Please put them back the way they were. The confusion is the talkgroup numbers are the same, that's it. SysID's are different. The NAC is 710.
Thanks.

 

[devicelab]

Someone else reported site 201(King County Simulcast) was off the air on Saturday night. Maybe it’s not back on the air yet.

Nope it's not back on the air yet.

 

[devicelab]

SysID's are different. The NAC is 710.

What NAC is 710? Not WSP700...

 

[devicelab]

We now have a user reporting that the 700Mhz system is showing a SysID of 9CC.

The WSP700 sites (201-205) are all BEE00.9CC with a NAC of 9C0

Please update the database -- there should be no other sites shown except 201-205. That other site belongs in the WSDOT entry. Just hide everything but 201-205.

 

[RBMTS]

Trunking system restored and updated SysID info. Thanks for everyone's help!

 

[freqseeker]

What NAC is 710? Not WSP700...

I have had my SDS200 for a few weeks now. It shows two NAC codes. 710 then a flashing 9C0. I will research this.

 

[freqseeker]

Trunking system restored and updated SysID info. Thanks for everyone's help!

Thanks for restoring. Please disregard my incorrect post of the 710 NAC code. 9C0 is the correct NAC. See previous screen shot. I'm researching why two codes are shown.

 

[GTR8000]

Thanks for restoring. Please disregard my incorrect post of the 710 NAC code. 9C0 is the correct NAC. See previous screen shot. I'm researching why two codes are shown.

710 is the NAC you have programmed; 9C0 is the actual NAC that the scanner is decoding.

 

[freqseeker]

710 is the NAC you have programmed; 9C0 is the actual NAC that the scanner is decoding.

That's what I suspected so I looked at my programming and NAC is set to search. I read from radio and 710 was set. Not sure where it came from.
Thanks for the help. I will fix it now.

 

[devicelab]

Yes and don't bother to enable P25 NAC enforcement on this system as I've seen several units register a 000 NAC. You'll miss traffic if it's enabled.

 

[devicelab]

Site 201 is back up.

 

[RBMTS]

Is it showing 9CC and 9C0 ?

 

[devicelab]

Yes

 

[RBMTS]

Thanks so very much.

 

[roaddog328]

I apologize in advance if this is not the best thread to ask this question about reception of WSP radio traffic. I receive WSP transmissions fine on my Uniden BCD 536 and 436 HP radios, but have been unable to get them on my new BCD 996P2 radio after downloading the WSP P25 frequencies listed under Snohomish County using my RadioReference subscription and programming the 996 with them. I'm located at the Snohomish/King County line, at about 400', and using the same types of antennas on all radios. Reception of other trunked law enforcement transmissions on the new BCD 996P2 programmed using RR frequency databases and Freescan software is fine.