-=> Quoting Joe Nicholson to Pete Hopping <=-
 -=> Quoting Pete Hopping to All <=-
 PH> can't figure out what this signal is. Due to the length of
 PH> the transmission it might be fire dispatch, but the talk
 PH> group code doesn't display and I can't tell. I'm also only
 PH> monitoring fire most of the time and mobile units don't tend
 PH> to transmit for the long periods that this signal exhibits.
 PH> Even fire scene status reports are pretty well clipped and
 PH> short.
 JN> Pete, have you ever heard fire dispatch reading off a long list
 JN> to an IC, telling him the complete makeup of a task force that
 JN> is enroute to save his butt?  
 JN> Then we have had the guy sitting on his radio and depressing the
 JN> talk button every time he shifts to reach behind and scratch.
Heh heh...yeah. I know about THAT problem. It used to happen
frequently on the old VHF system that some nincompoop would
throw the mic on the seat in such a way as to depress the
key. Only fire dispatch, to make it worse, would send,
"All units, check your mic switch." As if the nincompoop
would actually HEAR that!
The new trunked mobiles and handhelds now have time-out timers
on them, I think, and they DO have unit IDs so the nincompoops
can be identified and lectured next time it happens.
This signal dropping in and out sounds like it's fire. I don't have
the police telemetry or teletype codes entered into the scanner, so
it's not them. I don't have the admin codes entered either, so it
can't be the chiefs ratchet-jawing with each other. All I have
programmed in is dispatch, fireground, EMS tactical and 3 PD
tactical groups for my immediate area of the county/city. Between
those, it keeps the scanner pretty busy. I keep fireground and
EMS tactical locked-out and don't activate them until I hear something
from dispatch that sounds like I'd want to check out.
___ Blue Wave/QWK v2.12
---
---------------