PSERN live

Tortue

Member
Joined
Jan 10, 2010
Messages
70
Location
Seattle
UPDATE.
Got it to work this afternoon. Just had to adjust my squelch a notch. So far all the talk groups are broadcasting in Phase 2.

Just curious, can we expect the patching (I.e. Auburn to Algona-Pacific PD) to continue on PSERN ? Never heard of status bits on P-25.
Pretty sure Auburn/Algona have to stay with the King County PSERN system, unless they develop their own system$$$$$.
If they're not online (PSERN) yet, they will be when the next phase is enacted
 

maus92

Member
Premium Subscriber
Joined
Jun 23, 2004
Messages
8,377
Location
The OP
If you're having simulcast issues, then use only one site at a time. Choose the site and it's control frequency(s) that's closest to you.
If you need to travel to another part of the county, set a different site (same system) on a knob/button position that covers the geographic area that you want covered.
Make sense?
This is a fundamental misunderstanding of what a simulcast site (aka simulcast cell) is. A simulcast cell consists of two or more physically distant tower sites that transmit on the same frequency at (essentially) the same time and identify by a single RFSS and Site number combination. You cannot "use one site at a time" within a simulcast cell - the prime site and the subsites of a simulcast cell all transmit on the same frequency which can cause reception issues with radios not specifically designed to receive simulcast signaling. Bottom line is you cannot avoid simulcast issues by using "one site at a time" if your selected site happens to be a simulcast cell. Looking over the FCC data, there appears to be several simulcast cells in the PSERN system.
 

Tortue

Member
Joined
Jan 10, 2010
Messages
70
Location
Seattle
This is a fundamental misunderstanding of what a simulcast site (aka simulcast cell) is. A simulcast cell consists of two or more physically distant tower sites that transmit on the same frequency at (essentially) the same time and identify by a single RFSS and Site number combination. You cannot "use one site at a time" within a simulcast cell - the prime site and the subsites of a simulcast cell all transmit on the same frequency which can cause reception issues with radios not specifically designed to receive simulcast signaling. Bottom line is you cannot avoid simulcast issues by using "one site at a time" if your selected site happens to be a simulcast cell. Looking over the FCC data, there appears to be several simulcast cells in the PSERN system.
You are absolutely correct!
My point is, by using the closest site, ie the strongest signal, should keep the scanner (in this case) from locking into a more distant signal (site) source.
My Unicaton G5 will sometimes "lock on" to one of four different sites (so far), with various degrees of decoding success. By limiting its reception to one site, it receives/decodes flawlessly.
My Uniden 325p2 won't lock onto any site consistently, if I give it a choice of sites.
By limiting it to one site, it keeps up with the G5 in decoding TGID/voice transmissions , although the voice can sometimes be a bit garbled from multi-path distortion.
I'm sure everyone's mileage may vary. Just sharing what's working for me...
 

scannerizer

Member
Premium Subscriber
Joined
Aug 7, 2009
Messages
524
Location
Wherever I may roam
Pretty sure Auburn/Algona have to stay with the King County PSERN system, unless they develop their own system$$$$$.
If they're not online (PSERN) yet, they will be when the next phase is enacted
Right, but are the TGs going to be patched together like they are now, or is each agency going to have their own set of talk groups - broadcasting independently of each other. That is, will we still be hearing Algona patrol cars on Auburn’s dispatch channel and Vice verse ?
 

nessnet

Member
Premium Subscriber
Joined
Jan 22, 2007
Messages
2,013
Location
Eastside of Lake WA
Right, but are the TGs going to be patched together like they are now, or is each agency going to have their own set of talk groups - broadcasting independently of each other. That is, will we still be hearing Algona patrol cars on Auburn’s dispatch channel and Vice verse ?
We will know when they go live...
Until then, who knows?

I suspect it'll be the same, because personnel/dispatch centers snd operations probably are not changing.
 

Tortue

Member
Joined
Jan 10, 2010
Messages
70
Location
Seattle
You are absolutely correct!
My point is, by using the closest site, ie the strongest signal, should keep the scanner (in this case) from locking into a more distant signal (site) source.
My Unicaton G5 will sometimes "lock on" to one of four different sites (so far), with various degrees of decoding success. By limiting its reception to one site, it receives/decodes flawlessly.
My Uniden 325p2 won't lock onto any site consistently, if I give it a choice of sites.
By limiting it to one site, it keeps up with the G5 in decoding TGID/voice transmissions , although the voice can sometimes be a bit garbled from multi-path distortion.
I'm sure everyone's mileage may vary. Just sharing what's working for me...
A little nugget from the scanner guys, might help with avoiding multi path issues....
Forward to 31:01
 

Gsaxton

Newbie
Premium Subscriber
Joined
Feb 22, 2019
Messages
2
Location
Puyallup
I have some of the talk groups for Seattle fire and pd here is Seattle fire 109 is sfd disp 113 is channel 6 for aid resp 111 is sfd 1 105 is sfd 2 123 is sfd to amr

Then here is what I have for Seattle pd so far 205 is spd north dispatch 207 is spd south 209 is east dis spd and 203 is spd downtown and sw

We will know when they go live...
Until then, who knows?

I suspect it'll be the same, because personnel/dispatch centers snd operations probably are not changing.
I have some of the Seattle fire and Seattle pd talk groups I put on here
 

scannerizer

Member
Premium Subscriber
Joined
Aug 7, 2009
Messages
524
Location
Wherever I may roam
We will know when they go live...
Until then, who knows?

I suspect it'll be the same, because personnel/dispatch centers snd operations probably are not changing.
Right. Literally the talkgroup names are still the same. As is the (obnoxious?) locution on SFD's main dispatch. It is super loud and there seem to not be any more (also obnoxious?) open mikes.

Any idea of when KCSO will move?
 

devicelab

Whacker Extraordinaire
Joined
Jul 18, 2016
Messages
1,695
Location
Nowhere in WA
Did some ProScan logging
Below was submitted to RR this morning.

229​
3664​
11​
Puget Sound Emergency Radio Network (PSERN) / West King CountySeattle PoliceSEATTLE PD TAC SOUTH
231​
3696​
5​
Puget Sound Emergency Radio Network (PSERN) / West King CountySeattle PoliceSEATTLE PD TAC NORTH
233​
3728​
5​
Puget Sound Emergency Radio Network (PSERN) / Seattle/EastsideSeattle PoliceSEATTLE PD TAC WEST
You need to do your research. Those haven't been assigned that way in a couple of years.

229 3664 SPD SW
231 3696 SPD NW
233 3728 SPD PTAC
 

jondeaux

Member
Joined
Sep 13, 2004
Messages
81
Location
Seattle / U-District
Right. Literally the talkgroup names are still the same. As is the (obnoxious?) locution on SFD's main dispatch. It is super loud and there seem to not be any more (also obnoxious?) open mikes.

Any idea of when KCSO will move?
There are times I turn the Channel 4 SFD dispatcher off (avoid) and just catch the other fire information on the other channels. I really wish they did something about those tones.. also Seattle is a busy city overall and sometimes, its dispatching calls back to back..
 

scannerizer

Member
Premium Subscriber
Joined
Aug 7, 2009
Messages
524
Location
Wherever I may roam
You need to do your research. Those haven't been assigned that way in a couple of years.

229 3664 SPD SW
231 3696 SPD NW
233 3728 SPD PTAC
And we should label (on the SFD side of things).

109 = Fire Dispatch 4
111 listed above 103 in the database should be removed, and the 111 below 109 should be labelled Dispatch 5 (Alternate - Trucks to FAC).

On a side note, I just caught KC Sheriff on 1459, but they appear to be Phase 1.
 

tvengr

Well Known Member
Joined
Feb 10, 2019
Messages
10,730
Location
Baltimore County, MD
On the latest RR database update, PSERN lists Seattle Fire TGID 111 twice with different alpha tags:
11106fTSFD Disp AltSFD Alternate Dispatch (Trucks to FAC)Fire Dispatch
11106fTSFD 5Seattle Fire 5Fire-Tac
 

devicelab

Whacker Extraordinaire
Joined
Jul 18, 2016
Messages
1,695
Location
Nowhere in WA
On the latest RR database update, PSERN lists Seattle Fire TGID 111 twice with different alpha tags:
11106fTSFD Disp AltSFD Alternate Dispatch (Trucks to FAC)Fire Dispatch
11106fTSFD 5Seattle Fire 5Fire-Tac
It's just a secondary SFD dispatch channel. The old numbering scheme called it CH 5. 109 is SFD Primary (CH 4.)
 
Top