Cosumnes CSD Fire Department, Elk Grove

[gmclam]

Metro Fire channel usage

i have a bc246t, and nothing comes up on A3, only A2

I was under the understanding that when a command channel is needed, the "next" available command channel is assigned, starting with A2. When A2 is being used and another command channel is needed, A3 is assigned. Which seems to be how the tac channels (A6-A11) are assigned.

Regarding only seeing A2 on your scanner; try reversing the order they are programmed in your TG list. If they are "linked", then only the first one in the list will typically be found.

 

[inigo88]

Actually, if you run a program like Unitrunker on SRRCS, it will identify in use patches for you. The way I understand group patches are done on Motorola systems is that multiple talkgroup IDs are all slaved to one talkgroup ID (of the several in the patch). In this example, I believe A2 and A3 are both assigned to A2. Therefore, the scanner will only ever stop on A2 because traffic from both A2 and A3 are being carried on A2. I wonder if someone in Sacramento with Unitrunker could confirm this?

 

[sacscan]

When the SRRCS went through changes ( mid 2006 ) they didn't originally have A2/A3 and B2/B3 patched. I don't know exactly why - but I can find out - Regional Fire changed up the way they did things. Full time Talk Group patches appeared and B6 was patched into another Talk Group ( I believe to a Site 2 Talk Group ) in an effort to assist in site affiliation coverage. I heard they had some reception issues.

I remember the old system having some sort of patch for A2/A3 and B2/B3, because the first few trunktrackers made (BC235XLT, BC895XLT, Pro-90, Pro-2050, Pro-91, Pro-2066) didn't have the capability to ignore status bits. That meant I had to program them like this for PD:
48 SP 1
50 SP 1 Emergency mode
51 SP 1 Patch
55 SP 1 Multi-select

New system on same scanners:
60304 SP 1
60306 SP 1 Emergency mode
60307 SP 1 Patch
60311 SP 1 Multi-select

Fire on the old system was programmed like this:
3152 B2
3155 B2 Patch
2640 A2
2643 A2 Patch
2672 A3
2675 A3 Patch

Fire on the new system:
59280 B2
59283 B2 Patch
47667, 59411 B6 Patch (confirmed during search)
59410 B6 Emergency (found during search when no traffic heard on other B6 talkgroups I had programmed)
53232 A2
53235 A2 Patch
53264 A3
53267 A3 Patch

Again, this is only for the older trunktrackers that don't have the capability to ignore status bits. If I had never programmed an older scanner I may never have found out that there was a patch back then.

 

[Sac916]

I remember the old system having some sort of patch for A2/A3 and B2/B3, because the first few trunktrackers made (BC235XLT, BC895XLT, Pro-90, Pro-2050, Pro-91, Pro-2066) didn't have the capability to ignore status bits. That meant I had to program them like this for PD:
48 SP 1
50 SP 1 Emergency mode
51 SP 1 Patch
55 SP 1 Multi-select

New system on same scanners:
60304 SP 1
60306 SP 1 Emergency mode
60307 SP 1 Patch
60311 SP 1 Multi-select

Fire on the old system was programmed like this:
3152 B2
3155 B2 Patch
2640 A2
2643 A2 Patch
2672 A3
2675 A3 Patch

Fire on the new system:
59280 B2
59283 B2 Patch
47667, 59411 B6 Patch (confirmed during search)
59410 B6 Emergency (found during search when no traffic heard on other B6 talkgroups I had programmed)
53232 A2
53235 A2 Patch
53264 A3
53267 A3 Patch

Again, this is only for the older trunktrackers that don't have the capability to ignore status bits. If I had never programmed an older scanner I may never have found out that there was a patch back then.

Yup. Back in the late 90's I remember having all sorts of Talk Groups programmed into my BC-245 to accomodate for all the patch variables.

 

[sacscan]

Yup. Back in the late 90's I remember having all sorts of Talk Groups programmed into my BC-245 to accomodate for all the patch variables.

245? Those could ignore status bits. Do you mean the 235?

 

[Sac916]

245? Those could ignore status bits. Do you mean the 235?

Oh ya, my bad - It was like 12 years ago Ha!
BC-235 was a god send back then.

A bit, on status bits

http://wiki.radioreference.com/index.php/Motorola_Type_II

 

[sacscan]

Oh ya, my bad - It was like 12 years ago Ha!
BC-235 was a god send back then.

A bit, on status bits

http://wiki.radioreference.com/index.php/Motorola_Type_II

And how! It sure beat programming my Pro-51, Pro-62, Pro-46, Pro-2030, etc. in conventional mode and having to press 'SCAN' all the time to follow a conversation. Also, remember how the stupid cellular block started after 868.9375 and prevented one from programming the last frequency in the County system (868.9625)?

I just checked that Wiki page. Yup, same info as the piece of paper I printed out 10 years ago with all the different ID combinations. That piece of paper came in handy several times when I found unusual ID's during search. All the patched PD and fire ID's I listed in my original post were found during search.

 

[clanusb]

I was under the understanding that when a command channel is needed, the "next" available command channel is assigned, starting with A2. When A2 is being used and another command channel is needed, A3 is assigned. Which seems to be how the tac channels (A6-A11) are assigned.
.

negative. A2 all units north of the american river. Battalions 5, 7, 12, 13, and some of battalion 14. and of course folsoms battalion 15.

A3 all units south of the american river. Battalions 9, 10, 37, 81, 95, and some of 14. i have a list of each battalion and the stations in that battalion, if you want it posted, let me know.

A2 and A3 are used a command channel for small incidents, such as medical aids, public assists, small car accidents, etc.

see my earlier post about tac and command channels for large incidents.

now the tac channels. A6 - A12 are tac channels. NOT A6 - A11. A12 IS a tac channel, however since it is rarely used, units use it to have convo's about misc. subjects, instead of tying up A2 or A3. it is a "non emergency" use channel. A2 and A3 are for ACTIVE incidents.