Foxtrot Radios

[doctordave]

Foxtrot involved in a high speed chase on BPD 7A Western.....interesting that they made mention of talking directly to Toll Facilities Police....perhaps they now have Wulfberg or similar radios, much like MSP? Previously, Foxtrot could only comm w/ BPD & BCoPD (and aircraft comms, of course).

 

[mlevin]

I was listening to the same thing you where. I was just about to post the same thing. This was another example why there needs to be one common frequency for situations like this. Also, the City really needs to upgrade their portables to the 255 channel model.

They wound up not needing to communicate with the toll facilities being that they got on to 95S below the tunnel.

 

[Chris5]

I was lisening to A.A County Fire and they were talking to them on 154.010 ''Alpha'' because they did not have A.A police in there system.

 

[doctordave]

Indeed. Unfortunate thing is that, even if all Balt City/Co units had access to the 800-CALL & 800-TAC freqs, MSP cars do not have the ability to hit those freqs....yet. Maybe some fixed patch between an 800-TAC and a designated low-band freq would do the trick.

 

[mlevin]

I've heard MSP patched into Baltimore Co. TGs in the past. However I can't recall what freq they utilized for the patch.

 

[doctordave]

39.56 - into the TG of choice....usually, by the time the Co thinks to create the patch, the chase is over. 39.72 is an alternate. 46.28 for patches into the FD trunked TGs.

 

[n3bxv]

I posted a bit on the "foxtrot" helo the other night not being able to talk to AACo Police and having to have AACO Fire alarm relay. I got the sense that it wasn't a question of equipment, but rather training and procedures so that they could make that equipment work.

The officer on Foxtrot attempted to find the correct TG a number of times, but ended up on TG 16 or 154.01 each time with Fire Alarm. So it would appear they had both Trunked and non-trunked capability, but just couldn't put it to use. I also (too) briefly saw his radio ID come up on a 237xx Talkgroup as he attempted to change TG's , sorry I missed the complete TG id.


I didn't realize that Fort Smallwood Park was in Baltimore City's jurisdiction until the other night.....

 

[TinEar]

During that chase last night, Foxtrot talked directly to McHenry on 453.10 and had them relay to the State Police via phone. The chase ended at Route 100 and Snowden River Parkway with the Waterloo Barrack on 39.42 and on the Howard County system.

It would make sense that Foxtrot had the "Toll Facilities" freq installed - just from a quick look at a map. McHenry had two base ops talking with him - both the regular controller (the C.O.) and the Duty Officer (identified as D.O.) The TC units were anxious to get into the chase but the target vehicle (a Ford Expedition) had passed them before they could react.

[Edit] Chuck, ref that 237xx TG that you mentioned. If you're using a Uniden radio, the Eastern TG1648 produces a false TG at times of 23766. Someone else on AA's system produces 41008 when they talk. Those "phony" TGs can't be seen on the Radio Shack radios.

 

[n3bxv]

Chuck, ref that 237xx TG that you mentioned. If you're using a Uniden radio, the Eastern TG1648 produces a false TG at times of 23766. Someone else on AA's system produces 41008 when they talk. Those "phony" TGs can't be seen on the Radio Shack radios.

I'm using a BC895 tap output to Trunker, would it still produce false TG's?

I remember the Helicopter having an 8000? series radio id while on TG 16, and an obvious(at the time) console/external patch ID when he was on 154.01. Unfortunately, while I attempted to save the ID's in Trunker, my trusty "assistant" Sam Adams seems to have prevented me from doing so properly...

Is the 41008 a radio ID that external to the network radios default to?

Chuck

 

[TinEar]

Be careful of Sam..he can't be trusted.

I honestly don't know if your setup with the 895 will/could/should produce that "phony" talkgroup. I know that it appears very often in conjunction with TG1648. In fact, I entered the 23766 TG into my scanner and it will stop on it and hear the Eastern District. I remember when they first switched over to this new system that I reported this and only those with Uniden scanners could see it so we determined it's something caused by the scanner and not real. I'm very unclear about the 41008 talkgroup. I feel fairly sure it's another phony one that mirrors a valid TG but I haven't made the match yet. The bottom line is that neither is real. They are anomalies produced in Uniden scanners by a process that no one can explain.

 

[Llwellyn]

I'm using a BC895 tap output to Trunker, would it still produce false TG's?

Chuck

You shouldn't get this problem if you're not using the 895 to do the trunking. From your description, your 895 is the input receiver and trunker is doing the decoding, therefore you shouldn't have this happen.

It only happens occasionally when using a trunktracker itself, some problem with the trunking software that's causing false TG ID's. Just about anyone with any Uniden TT will have this happen at one time or another, just depends on the TG and the system. Radio Shack scanners do not have this problem, ever, either, making it 99% positive it's a Uniden problem.