So you are with Cashion F.D. I take it?
phil_smith said:why?how often does a volunteer firefighter using VHF need to talk on the radio to another firefighter that uses 800?
xerb1962 said:So you are with Cashion F.D. I take it?
plaws said:You're kidding, right? Norman's neighbors to the north, Moore and OKC, are 800, though only recently for Moore. But ALL their other neighbors are on hi-band. Little Axe VFD is on Norman's system and there is a patch now, supposedly to Lexington (though I can't find the VHF side), for those folks.
But that still leaves Noble, PInk, Slaughterville, Goldsby, Newcastle ...
phil_smith said:A problem I always saw when you give every FF their own radio is, the seem to spend more time talking on it then fighting fire. :wink:
StormCrusader said:PB, a "hard" patch generally means a patch that is hardwired, and therefore active 24/7. There normally isn't a need for that, as departments on separate bands typically don't work together on EVERY call.
As noted by others, you certainly don't want to hard patch channels in widespread use. Imagine for a momeny a hard patch between say, OCFD (800 EDACS) and SFMA (VHF-hi). Every time OCFD made a ride there would be radio traffic on a widely used VHF channel - unnessary traffic unless there was a ride involving both OCFD and someone on the VHF channel.
Console patches are typically temporary patches set up by a dispatch center between two channels. These can generally be easily set up on the fly, as needed to support an event in progress. On a Motorola Gold Elite console, patching involves about four keystrokes.
Field patches are about the same as a console patch, involving the use of a patch box (ACU-1000 and TCBs are typical) and dedicated radios. Again, done only to support an acutal event.
I know hard patches into the 800 systems are discouraged, as they tend to take up a lot of system resources. That is one reason the OKC EDACS channels aren't hard patched to the State TRS.