Could Someone Explain Patching In Relation to Trunking?
Posted: Sun Feb 27, 2005 4:34 pm
OK ... I've been following the various trunked systems around town for a number of years now (since the BC235 came out). There's something I just don't get in relation to following trunked systems on scanners - That is when talkgroups are patched together. Maybe I'm missing something easy, but I just don't understand
Now, I would assume that I should be able to hear traffic on BOTH of the patched talkgroups when that happens, but that is not necessarily the case. For example, when the SO has Poway and Rural patched (as is often the case), I will either hear traffic on Rural Disp or Poway Disp, but never both. The same goes for the recent fluctuation in SDFD dispatch talkgroups and SO Lemon Grove and Imperial Beach dispatches.
That said, the other day SDPD Mid-City patched with City Tac 3 and I heard traffic on BOTH talkgroups.
I would assume the units in the field are just on whatever channel they're normally on and not flipping to the various dispatches ... Is this just a side effect of how the current trunking scanners decode the data? Can it be fixed? Or is it just me?
I assume I have the Status Bit options set correctly on my scanners (the current ones I use mainly are a BC296 and a BC246T) otherwise I wouldn't hear traffic on the patched channels in the first place.
Help?
- Mike
Now, I would assume that I should be able to hear traffic on BOTH of the patched talkgroups when that happens, but that is not necessarily the case. For example, when the SO has Poway and Rural patched (as is often the case), I will either hear traffic on Rural Disp or Poway Disp, but never both. The same goes for the recent fluctuation in SDFD dispatch talkgroups and SO Lemon Grove and Imperial Beach dispatches.
That said, the other day SDPD Mid-City patched with City Tac 3 and I heard traffic on BOTH talkgroups.
I would assume the units in the field are just on whatever channel they're normally on and not flipping to the various dispatches ... Is this just a side effect of how the current trunking scanners decode the data? Can it be fixed? Or is it just me?
I assume I have the Status Bit options set correctly on my scanners (the current ones I use mainly are a BC296 and a BC246T) otherwise I wouldn't hear traffic on the patched channels in the first place.
Help?
- Mike