private eyes on 30736

[joe3560]

Has anyone ever listen to these private eyes on channel 30736. I like listening to them, they make me laugh but the language they use really makes me mad I thought they couldn’t use language like that on the radio I must be wrong . They are supposed to be professionals but they talk like 12 yr olds on the playground.

 

[masonb]

I havn't, but on another note
CFD has an EMRG-RTT on 434

 

[DX-300]

Yup, I've been hearing them for a long time now, sometimes it gets interesting but other times they just make me shake my head lol.

 

[Jay911]

Which system are the PIs on?

masonb: That would be talkgroup 432 (B13 Inspections North). Don't forget that TG+2 = emergency in a Type II system.

We are training a new class of dispatchers all week so you will hear emergency triggers, "recall tones" (hi-lo alert tones used to clear firefighters out of a dangerous situation), etc.

 

[joe3560]

they use TAC Mobility System frequency . control channel 863.2625

 

[SCPD]

I know the fire inspectors are on 432 (B13) but are you not talking about Police PI's on a digital chan?

 

[Jay911]

30736 would not be a CPS talkgroup - as Joe said, they're on TAC. CPS talkgroups begin in the 32xxx range.

And for what it's worth, the traffic on 432 (B13) is not necessarily fire "inspectors" per se; it's not the Inspections Bureau specifically. B13 and B14 are the chat channels for the fire crews when they are out doing things that are not calls or training. Fire crews do inspections from time to time which is where the majority of this traffic comes from.

 

[SCPD]

Is that TAC digital?

 

[Jay911]

TAC has no digital talkgroups, no. They're on a Type IIi Smartnet trunk.

 

[Jay911]

they use TAC Mobility System frequency . control channel 863.2625

Are you hearing all comms on 30736 or are they spread across multiple Type II talkgroups (like 30739, 30741, etc)? If the latter, that's an indication they're a Type I talkgroup.

 

[joe3560]

All comms are on 30736 and yes they are on TAC Mobility System frequency . control channel 863.2625 and it is digital

 

[SCPD]

Now I feel like a real dummy. I'm sorry guys I thought we were talking about the Calgary Tri-services trunk ie: Fire, Ems, Police not the TAC Mobility System. I understood "TAC" as Tactical channel.

 

[Jay911]

All comms are on 30736 and yes they are on TAC Mobility System frequency . control channel 863.2625 and it is digital

Just out of curiosity, on what are you basing the declaration that they use digital comms? Is your scanner showing "P25" when they transmit? I ask because if they are digital, this is the first digital comms outside of 753f in this area - and besides, the kind of trunk that TAC uses is, AFAIK, not supposed to be able to handle digital.

Sounds like I'll have to tune in tonight on the drive to work...

 

[joe3560]

My mistake I though all frequencies in Calgary were digital its is tac (Motorola Type IIi Hybrid Analog)

 

[SCPD]

Hey guys im having some problems with programing this into my pro97 I have it in and the fleet map correct and on an open scan I can hear and see IDs but when I take a chunk of the ids in the data base ie: The security and PI section and paste it into WIN97


30736 Private Investigators
30739 Private Investigators

I get errors saying that the ID must be in the range of 0-65520 (0-FFF0 HEX), and must be a multiple of 16

I don't know why this is happening for example I can type in 30739 and it works but if I type in 30736 it gives me that error. Any Ideas?

The fleet map I have in should be working unless the B2 TT is a S10? I have it in as S01 and the rest as S00

Right now im listening to 00080 which is Lab services and it comes up fine but every so often another id comes up and its somthing like this format 2034-1 I see that nowhere on the list.

 

[Jay911]

The problem is that this is a Type IIi (which some people will tell you doesn't exist; it's actually a Type I with some Type II IDs) system, so block sizes will not be correct.

I don't know how Radio Shack scanners work in terms of trunking. It sounds like it is expecting Type II IDs (which are in multiples of 16, as far as the "decimal" notation like 30736 goes). 30736 divided by 16 is 1921. That's a valid Type II group. 30739, however, is 1921.1875 - which is an "uneven" number and is invalid as Type II. (If it was Type II, it would be 30736+3 which is "talkgroup patch to another" as per the Status Bits page on the wiki.) Since we are reasonably certain it's not a talkgroup patch, and more importantly, the voice on 30739 is usually the same person or same unit identified, this must be a Type I talkgroup.

But which Type I talkgroup?

Again referring to the wiki, there's a fairly decent explanation on how to determine which are which.

What I do for the time being, until I figure out the right Type I ID, is leave this system in Type II mode with Status Bit set to ON, and let it show me all the IDs that might match that particular fleet/group.

 

[SCPD]

well the thing is all I have the option to do is MOT, my radio I guess determines weather or not its type 1 or type 2?! The only options I have are here

you will see the list on the right hand side.

 

[SCPD]

Here is the error in action.

 

[SCPD]

So far the chat I am hearing is coming from

2034-1 - Transportation of some sort
and
00800 - Medical transport of some sort.

 

[Jay911]

Well, like I said, I don't know enough about the Radio Shack radios to know how to program them. The "fleetmap" is what determines Type II vs Type I IDs, technically speaking. Evidently your RS product is smart enough to know that 30739 is not a valid Type II group.. but I don't know how you get it to accept that. Theoretically, you should hear all the comms thru 30736, though you may occasionally get false "Emergency" alerts, etc. (because Emergency is TG+2, so if someone ever transmitted on 30738, that would be seen as an emergency alarm).