oakland trunk Switching to Rebanded System tomorrow

Status
Not open for further replies.

officer_415

Member
Database Admin
Joined
Jun 29, 2008
Messages
1,326
Location
SF Bay Area
You may be out of luck on this one, except for the fact that everything on OAK P25 is simulcast to Edacs. (you know the handheld system) :)

Everything except fire, which is the only thing I really care to listen to. Oakland 1 seems to be simulcast pretty reliably on Seneca, but pretty sporadically on APL. I don't hear the tactical channels on EDACS much either. Oh well, at least my scanner still works great on MERA...
 

Retired911Guy

Member
Joined
Sep 24, 2009
Messages
156
Location
Sonoma CO, CA
OK Guys,

Big changes currently going on with Oak.

The so called citywide/areawide whatever wide they were, are NOT being used now and have not all afternoon.

2 days ago I installed Pro96com and first want to mention what a EASY program to opererate, about 5 mins I was up and running. I tried Unitrunker first because I wanted to try decoding both the Edacs and P25 sytems (Pro96com decodes only P25), anyway I messed (not using a different word because this is a G rated site) around with Unitrunker for about 2.5 hrs and NEVER got it to ever see the system. I may have done something wrong, it may not have the software but like I said Pro96com was running within 5 minutes.

I let it run for about 18 hrs collecting data, the first data chl shown in the P25 db is now a V chl and the 2nd chl list is the only data chl shown by Pro96com.

Also NONE of the PATROL chls were showing up on the TGs on the P25 freqs listed (except Patrol 3 now used as Car-car). It showed ALL of the patches for ALL the other Patrol cls to the so called citywide TGs, but they did NOT show up on the P25 cls as being used. The control chl would lite up and the patches would show up in the patch section, but none of them on the P25 Freqs. I would see up SIX DIFFERENT TGs going with 2 or 3 more DIFFERENT TGs that matched what I think were the Citywide TGs in the patches section, and then 2 or 3 MORE TGs would show up on the P25 Freqs list and again were NOT the same TGs as listed in the Patch section.

This afternoon the City-Area wide TGs are NOT being used and ALL the Patrol TGS ARE showing up on the P25 Freqs as being used and active.

Were/are the city-area wide TGs temporary for coverage purposes while the techs set up other areas of town for the P25 system? I don't know, just reporting what was going on 2 days ago and now.

HOWEVER I fing it very interesting that the P25 control cl was reporting patches that were NOT on the P25 system, but were on the Edacs system.

I will continue to monitor and report.

Also just to verify the data channel report here is the site data page from Pro96com, a very easy program to operate if anyone else wants try it. (I'm NOT related in ANY manner with Pro96com).

FileVersion:6
-TowerInfo
#This section is here for information only. With the exception
#of the Call Sign(s), This data is not Read back into the program at all.
System ID : 136
System Name :
WACN : 92556
Tower Number (Decimal): 202
Tower Number (Hex) : T0202
Tower Description : (null)
Control Capabilities : Voice,Registration
Call Sign(s) :
Timestamp : Tue Jul 12 01:10:30 2011

-Tables
#Format: Table ID,Base Freq,Spacing,Input Offset,Assumed/Confirmed,BandWidth,Slots
00,851.01250,0.01250,-45.00000,"Confirmed",0.00625,1

-Frequencies
#Format: Channel,Usage,Frequency(/Slot),Input Frequency(/Slot),Hit Count
"00-0013","v",851.17500,806.17500,1082 <-- Hit Count
"00-0102","v",852.28750,807.28750,755
"00-0150","c",852.88750,807.88750,0 <-- Control Chl
"00-0186","v",853.33750,808.33750,1125
"00-0226","v",853.83750,808.83750,1061
"00-0254","v",854.18750,809.18750,1113
"00-0272","v",854.41250,809.41250,1100

-Neighbors
#Format: TowerID,TowerIDHex,System ID,Channel,Frequency,Tower Name
101,"T0101",136,"00-0260",854.26250,""
303,"T0303",136,"00-0088",852.11250,""

Dave
 
Last edited:

officer_415

Member
Database Admin
Joined
Jun 29, 2008
Messages
1,326
Location
SF Bay Area
I observed the EDACS system just now. Only Patrol 1 and Patrol 5 were being used for dispatch, and Patrol 3 for car-to-car. Service 1 & 2 were patched together on 15-155.
 

inigo88

California DB Admin
Database Admin
Joined
Oct 31, 2004
Messages
1,999
Location
San Diego, CA
2 days ago I installed Pro96com and first want to mention what a EASY program to opererate, about 5 mins I was up and running. I tried Unitrunker first because I wanted to try decoding both the Edacs and P25 sytems (Pro96com decodes only P25), anyway I messed (not using a different word because this is a G rated site) around with Unitrunker for about 2.5 hrs and NEVER got it to ever see the system. I may have done something wrong, it may not have the software but like I said Pro96com was running within 5 minutes.

Unitrunker requires a scanner with an extra "discriminator tap" audio jack. I had to solder a resistor and an extra audio jack into the back of an old Radioshack Pro-93 I had. But it works great! Some base scanners come with the discriminator audio jack so you don't have to do it yourself. Pro96Com is great because it uses the stock PC/IF port (different than a discriminator audio jack) and is very easy to get up and running, but the downside is it only works on P25 systems.

Do you have any other log files of the talkgroup IDs logged over that 18 hour period? (It's in TalkGroups.txt)
Also:

Retired911Guy said:
-Neighbors
#Format: TowerID,TowerIDHex,System ID,Channel,Frequency,Tower Name
101,"T0101",136,"00-0260",854.26250,""
303,"T0303",136,"00-0088",852.11250,""

Can you hear a control channel on either 854.2625 or 852.1125 with the squelch down? We have been wondering if these sites actually exist (if so where?) or if the system is just announcing sites that haven't been built yet (I'm not even sure if that's possible).

Edit: Martin can't hear either of the neighbor sites. I don't think they actually exist, but I don't know what condition the system would be in that it would still announce them.
 
Last edited:

Retired911Guy

Member
Joined
Sep 24, 2009
Messages
156
Location
Sonoma CO, CA
Do you have any other log files of the talkgroup IDs logged over that 18 hour period? (It's in TalkGroups.txt)
Also:

Yep, they're pretty large, probably can't post them but could pm you.(can't remember do pms allow attachments, or or would I have to paste to the body of pm?


Can you hear a control channel on either 854.2625 or 852.1125 with the squelch down? We have been wondering if these sites actually exist (if so where?) or if the system is just announcing sites that haven't been built yet (I'm not even sure if that's possible).

Edit: Martin can't hear either of the neighbor sites. I don't think they actually exist, but I don't know what condition the system would be in that it would still announce them.

In the actual software says that they are connected and active, the data dump doesn't show that. No don't hear any data on those two freqs.

I thinking along the same lines that maybe after they get the main P25 system running they may start changing over radios at sites 101 & 202. However the one freq at each site may be relaying some edacs data to the P25 system combining the two system to provide better coverage citywide.

I did look at the TG logs and it did show the Patrol TGs as being used but having zero hits on the P25 Freqs, and again the patches showed the P25 TGs for Patrol but none on them showed up as active P25 freqs. The only thing I can think is the the edacs may be reporting (via those two freqs?) to the main P25 site and system controller.

Dave
 

Retired911Guy

Member
Joined
Sep 24, 2009
Messages
156
Location
Sonoma CO, CA
Inigo,

Tried to send PM with TalkGroup info, error to many characters.

Do you still the same Email as when in SA? or pm me your email, I can send attachments...

Dave
 

Retired911Guy

Member
Joined
Sep 24, 2009
Messages
156
Location
Sonoma CO, CA
Well,

It's doing it again, Showing patches from from Patrol to citywide, but no Patrol on P25 Freqs... look below the patch list

7/13/2011 3:22 Added Patch: 31557 () --> 65525 ()
7/13/2011 3:22 Added Patch: 31558 () --> 65517 ()
7/13/2011 3:22 Added Patch: 31559 () --> 65517 ()
7/13/2011 3:22 Added Patch: 31553 () --> 65525 ()
7/13/2011 3:23 Removed Patch: 31553 () --> 65525 ()
7/13/2011 3:23 Removed Patch: 31553 () --> 65525 ()
7/13/2011 3:23 Removed Patch: 31553 () --> 65525 ()
7/13/2011 3:23 Removed Patch: 31553 () --> 65525 ()
7/13/2011 3:24 Added Patch: 31553 () --> 65525 ()
7/13/2011 3:24 Added Patch: 31557 (T: 202 DT: 7/13/11@3:23) --> 65525 ()
7/13/2011 3:24 Added Patch: 31558 (T: 202 DT: 7/13/11@3:23) --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:24 Added Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:24 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:24 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:24 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:24 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:24 Added Patch: 31558 (T: 202 DT: 7/13/11@3:23) --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:24 Added Patch: 31553 () --> 65525 ()
7/13/2011 3:24 Added Patch: 31557 (T: 202 DT: 7/13/11@3:23) --> 65525 ()
7/13/2011 3:24 Added Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:25 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:25 Added Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:25 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:25 Removed Patch: 31557 (T: 202 DT: 7/13/11@3:23) --> 65525 ()
7/13/2011 3:25 Removed Patch: 31557 (T: 202 DT: 7/13/11@3:23) --> 65525 ()
7/13/2011 3:25 Removed Patch: 31557 (T: 202 DT: 7/13/11@3:23) --> 65525 ()
7/13/2011 3:25 Added Patch: 31558 (T: 202 DT: 7/13/11@3:23) --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:25 Added Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:26 Added Patch: 31557 (T: 202 DT: 7/13/11@3:23) --> 65525 ()
7/13/2011 3:26 Removed Patch: 31557 (T: 202 DT: 7/13/11@3:23) --> 65525 ()
7/13/2011 3:26 Removed Patch: 31557 (T: 202 DT: 7/13/11@3:23) --> 65525 ()
7/13/2011 3:26 Added Patch: 31553 () --> 65525 ()
7/13/2011 3:26 Added Patch: 31558 (T: 202 DT: 7/13/11@3:23) --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:26 Added Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:26 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:26 Added Patch: 31553 (T: 202 DT: 7/13/11@3:26) --> 65525 (T: 202 DT: 7/13/11@3:26)
7/13/2011 3:26 Removed Patch: 31553 (T: 202 DT: 7/13/11@3:26) --> 65525 (T: 202 DT: 7/13/11@3:26)
7/13/2011 3:26 Added Patch: 31558 (T: 202 DT: 7/13/11@3:23) --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:27 Removed Patch: 31558 (T: 202 DT: 7/13/11@3:23) --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:27 Removed Patch: 31558 (T: 202 DT: 7/13/11@3:23) --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:27 Added Patch: 31553 (T: 202 DT: 7/13/11@3:26) --> 65525 (T: 202 DT: 7/13/11@3:26)
7/13/2011 3:27 Added Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:27 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:27 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:27 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:27 Removed Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:27 Added Patch: 31553 (T: 202 DT: 7/13/11@3:26) --> 65525 (T: 202 DT: 7/13/11@3:26)
7/13/2011 3:27 Added Patch: 31557 (T: 202 DT: 7/13/11@3:23) --> 65525 (T: 202 DT: 7/13/11@3:26)
7/13/2011 3:27 Added Patch: 31558 (T: 202 DT: 7/13/11@3:23) --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:27 Added Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)

The TalkGroup list shows Patrol TGs coming through the control chl but NOT listing as hits on the P25 freqs, See the Zeros

# Talkgroup List for this system
# Format: Talkgroup,Priority,Description,Lastseen(Unix),LastSeen(Human m/dd/yyyy),FirstSeen(Unix),FirstSeen(Human),FG Color,BG Color,EncSeen,Hits
# Priority Values: 0=Ignore, 1=Highest priority, 99= Lowest Priority
31553,50,"T: 202 DT: 7/13/11@3:26",1310552788,"07/13/2011 @ 03:26",1310552788,"07/13/2011 @ 03:26","#000000","#000000","N",0 <-----
31557,50,"T: 202 DT: 7/13/11@3:23",1310552601,"07/13/2011 @ 03:23",1310552601,"07/13/2011 @ 03:23","#000000","#000000","N",0 <-----
31557,50,"T: 202 DT: 7/13/11@3:23",1310552601,"
31558,50,"T: 202 DT: 7/13/11@3:23",1310552603,"07/13/2011 @ 03:23",1310552603,"07/13/2011 @ 03:23","#000000","#000000","N",0 <-----
31557,50,"T: 202 DT: 7/13/11@3:23",1310552601,"
65517,50,"T: 202 DT: 7/13/11@3:23",1310552615,"07/13/2011 @ 03:23",1310552615,"07/13/2011 @ 03:23","#000000","#000000","N",1
65525,50,"T: 202 DT: 7/13/11@3:26",1310552824,"07/13/2011 @ 03:27",1310552771,"07/13/2011 @ 03:26","#000000","#000000","N",7
 

officer_415

Member
Database Admin
Joined
Jun 29, 2008
Messages
1,326
Location
SF Bay Area
Edit: Martin can't hear either of the neighbor sites. I don't think they actually exist, but I don't know what condition the system would be in that it would still announce them.

I'm not an expert on this stuff, but what if they have active equipment at those sites, and they just haven't hooked them up to an antenna yet? Would the system still announce the frequencies?

On another note, OPD channel usage seems to have settled into the following:

Patrol 1 - BFO 1 (West)
Patrol 2 - none
Patrol 3 - Car-to-Car
Patrol 4 - none
Patrol 5 - BFO 2 (East)

There is no more patching of patrol talkgroups on EDACS, but Service 1 & 2 are still sometimes patched together. 15-153, 15-154, and 15-155 have all been used recently to patch various talkgroups together.
 

inigo88

California DB Admin
Database Admin
Joined
Oct 31, 2004
Messages
1,999
Location
San Diego, CA
Dave, thank you for attaching the patch log. That cleared up basically all my confusion. :)

You aren't seeing any of the 31xxx OPD talkgroups on the P25 frequencies, because they were being patched full time to the two 65xxx talkgroups. You got zero hits because the program not only keeps track of channel grants (when they actually talk) but also radio affiliations (when a radio turns on, turns off or changes channels).

The 31xxx and 65xxx talkgroups have nothing to do with linking the EDACS system and the P25 system, they are simply two sets of talkgroups on the P25 system. The linking between the P25 and EDACS system is done completely on the back end, with routers and ethernet cable and T1 line or point to point microwave - IT stuff that's above my pay grade.

Also, EDACS (being a very old system) would have to create a temporary talkgroup when two of the regular system talkgroups were patched together (which creates all the confusion with the 15-xxx talkgroups on the EDACS system), but Motorola and P25 don't need to do this. A patch on a Motorola or P25 system is simply a re-direct. The dispatcher can select Patrol 1 and Patrol 5 and patch them together, and one group becomes the "Supergroup" (the one that shows up on the system voice frequencies) while the other sub-groups are slaved to it. Lets say Patrol 1 is the supergroup, and Patrol 1 and 5 are patched together. Anyone on Patrol 1 would transmit and receive on the Patrol 1 talkgroup. However everyone "affiliated" to Patrol 5 (the radio display says Patrol 5) would be redirected to transmit and receive on Patrol 1, without them knowing it. Therefore Patrol 5 would show up in the affiliations log (tons of people's radios are on the Patrol 5 channel) but since it was slaved to the Patrol 1 supergroup you would never get a voice hit on it, since they would all be on Patrol 1. The above is hypothetical for the purpose of explaining how patching works. Another example with MERA: Fairfax PD & San Anselmo PD might patch their dispatch channels together. You observe Fairfax PD's talkgroup fall silent, but hear both Fairfax PD AND San Anselmo PD dispatchers on the San Anselmo PD talkgroup. That's because San Anselmo became the "supergroup," and everyone on the Fairfax channel was slaved to the San Anselmo talkgroup without knowing it.

That's all hypothetical, but what Oakland actually did was create two extra talkgroups, 65525 and 65517, that would be the supergroup destinations for patches. This is unnecessary with P25, but used to be necessary on the EDACS system, so I think the techs are just stuck in the old EDACS mindset. :)

Your log found three new talkgroups. Here is my guess both on the talkgroups and on what they're doing with the system (made from 500 miles away haha):

31553 - Patrol 1
31554 - Patrol 2
31555 - Patrol 3
31556 - Patrol 4
31557 - Patrol 5
31558 - Service 1
31559 - Service 2


65517 - Service 1 & 2 Patch
65525 - Patrol 1 & 5 Patch

Notice the following:

7/13/2011 3:24 Added Patch: 31553 () --> 65525 ()
7/13/2011 3:24 Added Patch: 31557 (T: 202 DT: 7/13/11@3:23) --> 65525 ()

Anyone with their radios set to either Patrol 1 or 5 will end up on talkgroup 65525 (without knowing it - for all they know they are on Patrol 1 or Patrol 5).

7/13/2011 3:24 Added Patch: 31558 (T: 202 DT: 7/13/11@3:23) --> 65517 (T: 202 DT: 7/13/11@3:23)
7/13/2011 3:24 Added Patch: 31559 () --> 65517 (T: 202 DT: 7/13/11@3:23)

Anyone on Service 1 or 2 will actually end up on 65517.

Therefore you could think of 65525 as "Citywide Dispatch" (since it's both BFO areas on one channel) or "Citywide Patrol Patch," and 65517 as "Service 1 & 2 Patch."

All that extra junk in the patch log is just the dispatcher selecting and unselecting channels as needed on the radio screen. Also if this was at 3 am that would make a lot of sense because they reduce the staffing down to only one dispatcher on Patrol and one on Service (or at least they used to).

EDIT: There may actually be a reason why they needed 65525 and 65517, because in order to link the two systems together they would need to account for the fact that EDACS uses the separate 15-153, 15-154 and 15-155 while any EDACS talkgroups are patched together (stand alone P25 does not need this). Say on the EDACS system they patch Patrol 1 and 5 together and it ends up on 15-153. Now instead of worrying about which Patrol talkgroup on the P25 they need to link it to, they just link 15-153 to 65525. Finally they patch 31553 and 31557 to 65525, and viola - everyone can hear eachother on both systems. :)
 
Last edited:

Retired911Guy

Member
Joined
Sep 24, 2009
Messages
156
Location
Sonoma CO, CA
Here's another TG Log for about 12-13 hrs, started this am around 3-4 am (maybe 5am, I wasn't quite awake)(not quite awake now either)

It may show some more new TGs.

FileVersion:6
# Talkgroup List for this system
# Format: Talkgroup,Priority,Description,Lastseen(Unix),LastSeen(Human m/dd/yyyy),FirstSeen(Unix),FirstSeen(Human),FG Color,BG Color,EncSeen,Hits
# Priority Values: 0=Ignore, 1=Highest priority, 99= Lowest Priority
31553,50,"T: 202 DT: 7/13/11@3:26",1310599427,"07/13/2011 @ 16:23",1310552788,"07/13/2011 @ 03:26","#000000","#000000","N",1188
31554,50,"T: 202 DT: 7/13/11@5:35",1310598748,"07/13/2011 @ 16:12",1310560518,"07/13/2011 @ 05:35","#000000","#000000","N",8
31555,50,"T: 202 DT: 7/13/11@5:00",1310597700,"07/13/2011 @ 15:55",1310558405,"07/13/2011 @ 05:00","#000000","#000000","N",96
31556,50,"T: 202 DT: 7/13/11@7:34",1310567648,"07/13/2011 @ 07:34",1310567648,"07/13/2011 @ 07:34","#000000","#000000","N",0
31557,50,"T: 202 DT: 7/13/11@3:23",1310599309,"07/13/2011 @ 16:21",1310552601,"07/13/2011 @ 03:23","#000000","#000000","N",727
31558,50,"T: 202 DT: 7/13/11@3:23",1310592128,"07/13/2011 @ 14:22",1310552603,"07/13/2011 @ 03:23","#000000","#000000","N",120
31559,50,"T: 202 DT: 7/13/11@8:56",1310592064,"07/13/2011 @ 14:21",1310572608,"07/13/2011 @ 08:56","#000000","#000000","N",113
31561,50,"T: 202 DT: 7/13/11@12:17",1310596321,"07/13/2011 @ 15:32",1310584665,"07/13/2011 @ 12:17","#000000","#000000","N",19
31569,50,"T: 202 DT: 7/13/11@7:41",1310568145,"07/13/2011 @ 07:42",1310568065,"07/13/2011 @ 07:41","#000000","#000000","N",8
31572,50,"T: 202 DT: 7/13/11@8:22",1310595358,"07/13/2011 @ 15:15",1310570566,"07/13/2011 @ 08:22","#000000","#000000","N",20
31573,50,"T: 202 DT: 7/13/11@13:26",1310596274,"07/13/2011 @ 15:31",1310588770,"07/13/2011 @ 13:26","#000000","#000000","N",3
31577,50,"T: 202 DT: 7/13/11@14:50",1310593838,"07/13/2011 @ 14:50",1310593838,"07/13/2011 @ 14:50","#000000","#000000","N",0
31681,50,"T: 202 DT: 7/13/11@3:28",1310599441,"07/13/2011 @ 16:24",1310552881,"07/13/2011 @ 03:28","#000000","#000000","N",547
31682,50,"T: 202 DT: 7/13/11@10:02",1310598700,"07/13/2011 @ 16:11",1310576578,"07/13/2011 @ 10:02","#000000","#000000","N",37
31683,50,"T: 202 DT: 7/13/11@16:05",1310598339,"07/13/2011 @ 16:05",1310598339,"07/13/2011 @ 16:05","#000000","#000000","N",0
31688,50,"T: 202 DT: 7/13/11@7:40",1310576609,"07/13/2011 @ 10:03",1310568058,"07/13/2011 @ 07:40","#000000","#000000","N",3
31692,50,"T: 202 DT: 7/13/11@9:48",1310596819,"07/13/2011 @ 15:40",1310575737,"07/13/2011 @ 09:48","#000000","#000000","N",19
31693,50,"T: 202 DT: 7/13/11@8:42",1310594841,"07/13/2011 @ 15:07",1310571721,"07/13/2011 @ 08:42","#000000","#000000","N",28
31857,50,"T: 202 DT: 7/13/11@7:32",1310589592,"07/13/2011 @ 13:39",1310567541,"07/13/2011 @ 07:32","#000000","#000000","N",58
31921,50,"T: 202 DT: 7/13/11@9:06",1310599426,"07/13/2011 @ 16:23",1310573182,"07/13/2011 @ 09:06","#000000","#000000","N",435
31922,50,"T: 202 DT: 7/13/11@14:26",1310595269,"07/13/2011 @ 15:14",1310592371,"07/13/2011 @ 14:26","#000000","#000000","N",3
32001,50,"T: 202 DT: 7/13/11@5:34",1310597341,"07/13/2011 @ 15:49",1310560489,"07/13/2011 @ 05:34","#000000","#000000","N",31
32002,50,"T: 202 DT: 7/13/11@13:22",1310588554,"07/13/2011 @ 13:22",1310588554,"07/13/2011 @ 13:22","#000000","#000000","N",0
65500,50,"T: 202 DT: 7/13/11@4:57",1310566273,"07/13/2011 @ 07:11",1310558266,"07/13/2011 @ 04:57","#000000","#000000","N",340
65515,50,"T: 202 DT: 7/13/11@4:56",1310558182,"07/13/2011 @ 04:56",1310558182,"07/13/2011 @ 04:56","#000000","#000000","N",1
65517,50,"T: 202 DT: 7/13/11@3:23",1310583409,"07/13/2011 @ 11:56",1310552615,"07/13/2011 @ 03:23","#000000","#000000","N",469
65520,50,"T: 202 DT: 7/13/11@14:31",1310598503,"07/13/2011 @ 16:08",1310592676,"07/13/2011 @ 14:31","#000000","#000000","N",194
65525,50,"T: 202 DT: 7/13/11@3:26",1310557955,"07/13/2011 @ 04:52",1310552771,"07/13/2011 @ 03:26","#000000","#000000","N",93
65532,50,"T: 202 DT: 7/13/11@7:12",1310573911,"07/13/2011 @ 09:18",1310566350,"07/13/2011 @ 07:12","#000000","#000000","N",302

Also have affiliation Log

Timestamp Function TalkGroup RadioID Comments
7/13/2011 4:37 Unaffiliate 0 12154 TG: 31681 DT: 7/13/11@3:35
7/13/2011 4:39 Unaffiliate 0 12839
7/13/2011 4:42 Unaffiliate 0 10753
7/13/2011 4:49 Unaffiliate 0 10939
7/13/2011 5:09 Unaffiliate 0 10279
7/13/2011 5:10 Unaffiliate 0 11034
7/13/2011 5:10 Unaffiliate 0 14731
7/13/2011 5:19 Unaffiliate 0 11971
7/13/2011 5:24 Unaffiliate 0 14623
7/13/2011 5:38 Unaffiliate 0 11934 TG: 65500 DT: 7/13/11@5:07
7/13/2011 5:50 Unaffiliate 0 11118
7/13/2011 6:05 Unaffiliate 0 10279 TG: 65500 DT: 7/13/11@5:36
7/13/2011 6:08 Unaffiliate 0 12839
7/13/2011 6:15 Unaffiliate 0 11257 TG: 65525 DT: 7/13/11@3:29
7/13/2011 6:16 Unaffiliate 0 10904 TG: 65500 DT: 7/13/11@6:14
7/13/2011 6:53 Unaffiliate 0 12164
7/13/2011 6:54 Unaffiliate 0 11654 TG: 65500 DT: 7/13/11@6:09
7/13/2011 6:56 Unaffiliate 0 10788
7/13/2011 7:00 Unaffiliate 0 10991
7/13/2011 7:11 Unaffiliate 0 10788
7/13/2011 7:11 Unaffiliate 0 12060
7/13/2011 7:17 Unaffiliate 0 12174
7/13/2011 7:26 Unaffiliate 0 12177
7/13/2011 7:29 Unaffiliate 0 10492 TG: 65500 DT: 7/13/11@5:11
7/13/2011 7:30 Unaffiliate 0 11401
7/13/2011 7:38 Unaffiliate 0 14681
7/13/2011 7:40 Unaffiliate 0 11678
7/13/2011 7:51 Unaffiliate 0 10218 TG: 65500 DT: 7/13/11@6:55
7/13/2011 7:56 Unaffiliate 0 10937
7/13/2011 8:01 Unaffiliate 0 10514
7/13/2011 8:06 Unaffiliate 0 12041
7/13/2011 8:13 Unaffiliate 0 10810 TG: 65532 DT: 7/13/11@7:47
7/13/2011 8:13 Unaffiliate 0 12842
7/13/2011 8:14 Unaffiliate 0 10931
7/13/2011 8:14 Unaffiliate 0 10999
7/13/2011 8:16 Unaffiliate 0 11567
7/13/2011 8:30 Unaffiliate 0 10817
7/13/2011 8:39 Unaffiliate 0 12165 TG: 31681 DT: 7/13/11@8:38
7/13/2011 8:41 Unaffiliate 0 11567
7/13/2011 8:41 Unaffiliate 0 12266 TG: 31681 DT: 7/13/11@4:57
7/13/2011 8:47 Unaffiliate 0 14445
7/13/2011 8:49 Unaffiliate 0 11110
7/13/2011 8:51 Unaffiliate 0 11208
7/13/2011 8:54 Unaffiliate 0 10673
7/13/2011 8:55 Unaffiliate 0 11046
7/13/2011 9:00 Unaffiliate 0 12098
7/13/2011 9:01 Unaffiliate 0 12135
7/13/2011 9:01 Unaffiliate 0 11257 TG: 65525 DT: 7/13/11@3:29
7/13/2011 9:02 Unaffiliate 0 12496
7/13/2011 9:05 Unaffiliate 0 12032
7/13/2011 9:06 Unaffiliate 0 11371
7/13/2011 9:07 Unaffiliate 0 12029
7/13/2011 9:17 Unaffiliate 0 14433
7/13/2011 9:19 Unaffiliate 0 10894 TG: 65500 DT: 7/13/11@6:14
7/13/2011 9:23 Unaffiliate 0 10411 TG: 65532 DT: 7/13/11@9:10
7/13/2011 9:23 Unaffiliate 0 11233 TG: 31553 DT: 7/13/11@9:20
7/13/2011 9:26 Unaffiliate 0 12324
7/13/2011 9:26 Unaffiliate 0 12140
7/13/2011 9:27 Unaffiliate 0 10895
7/13/2011 9:29 Unaffiliate 0 12268
7/13/2011 9:30 Unaffiliate 0 11924
7/13/2011 9:31 Unaffiliate 0 13861
7/13/2011 9:38 Unaffiliate 0 12285
7/13/2011 9:39 Unaffiliate 0 14452
7/13/2011 9:47 Unaffiliate 0 11101 TG: 65525 DT: 7/13/11@3:33
7/13/2011 9:52 Unaffiliate 0 12185
7/13/2011 9:54 Unaffiliate 0 12204
7/13/2011 10:00 Unaffiliate 0 12281
7/13/2011 10:04 Unaffiliate 0 11207
7/13/2011 10:04 Unaffiliate 0 12107
7/13/2011 10:14 Unaffiliate 0 10829
7/13/2011 10:31 Unaffiliate 0 12206
7/13/2011 10:34 Unaffiliate 0 15257 TG: 31555 DT: 7/13/11@7:34
7/13/2011 10:35 Unaffiliate 0 10627 TG: 65532 DT: 7/13/11@7:17
7/13/2011 10:42 Unaffiliate 0 12097
7/13/2011 10:48 Unaffiliate 0 12280
7/13/2011 11:10 Affiliate 31921 T: 202 DT: 7/13/11@9:06 14483 TG: 31921 DT: 7/13/11@10:45
7/13/2011 11:19 Unaffiliate 0 11100
7/13/2011 11:35 Unaffiliate 0 12104
7/13/2011 11:36 Unaffiliate 0 12152 TG: 31681 DT: 7/13/11@8:12
7/13/2011 11:38 Unaffiliate 0 12051
7/13/2011 11:56 Unaffiliate 0 12209
7/13/2011 12:09 Unaffiliate 0 10850
7/13/2011 12:10 Unaffiliate 0 13761 TG: 65532 DT: 7/13/11@9:11
7/13/2011 12:15 Unaffiliate 0 11977
7/13/2011 12:34 Unaffiliate 0 12155
7/13/2011 12:59 Unaffiliate 0 11778
7/13/2011 13:07 Unaffiliate 0 10939
7/13/2011 13:09 Unaffiliate 0 10908 TG: 65500 DT: 7/13/11@5:34
7/13/2011 13:16 Unaffiliate 0 11094 TG: 65517 DT: 7/13/11@10:35
7/13/2011 13:25 Unaffiliate 0 12017
7/13/2011 13:27 Unaffiliate 0 11924
7/13/2011 13:35 Unaffiliate 0 10395 TG: 31553 DT: 7/13/11@12:03
7/13/2011 13:37 Unaffiliate 0 12017
7/13/2011 13:43 Unaffiliate 0 11060
7/13/2011 14:17 Unaffiliate 0 10980
7/13/2011 14:20 Unaffiliate 0 12478
7/13/2011 14:22 Unaffiliate 0 10514
7/13/2011 14:25 Unaffiliate 0 15775
7/13/2011 14:35 Unaffiliate 0 11851
7/13/2011 14:54 Unaffiliate 0 12349
7/13/2011 15:20 Unaffiliate 0 10395 TG: 31553 DT: 7/13/11@12:03
7/13/2011 15:25 Unaffiliate 0 12020
7/13/2011 15:28 Unaffiliate 0 11547 TG: 31557 DT: 7/13/11@10:18
7/13/2011 15:28 Unaffiliate 0 10514
7/13/2011 15:37 Unaffiliate 0 11395
7/13/2011 15:44 Unaffiliate 0 11629
7/13/2011 15:58 Unaffiliate 0 12249
7/13/2011 16:01 Unaffiliate 0 10891
7/13/2011 16:11 Unaffiliate 0 11119 TG: 31553 DT: 7/13/11@10:17
7/13/2011 16:13 Unaffiliate 0 11116

Just a brief snip of the tower data for purposes seeing Freq distribution and control chl

-Frequencies
#Format: Channel,Usage,Frequency(/Slot),Input Frequency(/Slot),Hit Count
"00-0013","v",851.17500,806.17500,823
"00-0102","v",852.28750,807.28750,837
"00-0150","c",852.88750,807.88750,0
"00-0186","v",853.33750,808.33750,823
"00-0226","v",853.83750,808.83750,807
"00-0254","vp",854.18750,809.18750,769 (VP means Voice and Private call for those who don't know)
"00-0272","v",854.41250,809.41250,803

And the patch log is over 6000 lines, so can't post it.

The site status for site 101 & 303 has changed from a couple of days ago as "Connected-Active" to "Connected-Current".

Don't know what this really means, other than we know the definition of "Active" & "Current", but in this context who knows. Maybe some P25 guru out the may know....

Dave
 

MtnBiker2005

Member
Premium Subscriber
Joined
Dec 19, 2002
Messages
3,566
Location
San Diego County, California
Found this on the Pro96com YahooGroup.

_______________________________________________
Connected - The site is connected to the network
Failed - Site is not connected to the network
Current - Site status was recently updated on the system
Stale - Site status has not been checked in awhile
http://groups.yahoo.com/group/PRO96COM/message/3012
_______________________________________________
 

officer_415

Member
Database Admin
Joined
Jun 29, 2008
Messages
1,326
Location
SF Bay Area
OPD channel usage seems to have settled into the following:

Patrol 1 - BFO 1 (West)
Patrol 2 - none
Patrol 3 - Car-to-Car
Patrol 4 - none
Patrol 5 - BFO 2 (East)

I spoke too soon. At night, patrol talkgroups are still patched together:

Patrol 1 - BFO 1 (patched with Patrol 2)
Patrol 2 - BFO 1 (patched with Patrol 1)
Patrol 3 - Car-to-Car
Patrol 4 - BFO 2 (patched with Patrol 5)
Patrol 5 - BFO 2 (patched with Patrol 4)

Because the talkgroups are patched together, I don't know what determines which channel in each pair an officer uses. Maybe someone with some inside info can help.
 

Retired911Guy

Member
Joined
Sep 24, 2009
Messages
156
Location
Sonoma CO, CA
I think the patches are used during busy times (Fri-Sat Nights, Etc) and other occasions.

Just heard a pursuit of TWO CARS from a 207pc (kidnapping) on Edacs Patrol 1 (West or what ever it is now) and after BOTH cars were lost the SGT told the dispatcher to "end the patch and go back to VEHICLE ONE" the dispatcher said copy and repeated "ending the patch and returning to VEHICLE ONE" I did NOT scan through the Citywides-BFOWides or what they are called because I didn't want to miss any part of the pursuit on Patrol 1.

So again there is that "VEHICLE ONE" term being used on Patrol 1. Just wondering if Edacs could be being used as a Handheld System and feeding the Handheld traffic to the P25 System via those 2 single freqs at site 101 & 303.

Broadway and Seneca would most likely be better Handheld coverage than the P25 in the downtown and far south areas. With mobiles putting out 100watts on P25 the may be better able to hit the P25 site than a Hanheld with 5watts on P25, However 5watts Analog going to more local sites MAY work better.

Just thinking....

Dave
 
Last edited:

Retired911Guy

Member
Joined
Sep 24, 2009
Messages
156
Location
Sonoma CO, CA
Found this on the Pro96com YahooGroup.

_______________________________________________
Connected - The site is connected to the network
Failed - Site is not connected to the network
Current - Site status was recently updated on the system
Stale - Site status has not been checked in awhile
Yahoo! Groups
_______________________________________________

Hi MtnBiker,

Thanks for your info on this, sorry for late reply, had the BLUE SCREEN of DEATH occur and took a few days to trouble shoot and fix...

Dave
 

Retired911Guy

Member
Joined
Sep 24, 2009
Messages
156
Location
Sonoma CO, CA
Broadway and Seneca would most likely be better Handheld coverage than the P25 in the downtown and far south areas. With mobiles putting out 100watts on P25 the may be better able to hit the P25 site than a Hanheld with 5watts on P25, However 5watts Analog going to more local sites MAY work better.

May have just shot myself in the foot...

Just heard Patrol 1 try to reach 3L9 (beat 9 east of Lake Merritt and North boarder of Piedmont). No Answer 3 times, dispatch sends another unit.

3L9 comes up and says I heard all your calls and tried to answer but was on portable at Chabot Rec Center and couldn't get out, in my car now and responding.

Chabot Rec Center is directly under the Grizzly Peak set of ridges about 1/4 mi west of Caldecott Tunnel.

If he was on a Edacs Portable he may have been able to hit Broadway, but with P25 on Grizzly Peak and he being directly under the ridge on portable he couldn't get out. OR maybe his Edacs portable couldn't hit Broadway from that location...Who Knows ??

Have know idea what/why the dispatchers and SGTs are taking about when they say return to "VEHICLE ONE"

Dave
(Confuses the heck out of me, drinking a beer, going to bed !!)
 
Last edited:
Status
Not open for further replies.
Top