Hi all,
Sorry - it wouldn't let me post to the Uniden section. I was wondering how the SDS100/200 compares to Unication in handling of patched or multi-selected talkgroup activity. On my Unication G5 if a dispatcher has talkgroups patched, it appears to "behave" as it does on actual radios.. I can be locked on ID 1007 and hear radio traffic patched or multi-selected to ID's 1001, 1004, and 1007.. (so theoretically I could also be locked on 1001 and 1004 and hear the patched/multi-selected traffic).
I was wondering if the Uniden SDS100/200 behaves any differently.. I believe non-Type II on Uniden requires scanning all talkgroups involved in a patch and the patch radio traffic will 'randomly' pick one of the talkgroups its patched/multi-selected to - to carry the audio.
Obviously, in the old days - for type II systems you can use the status bits to better "catch" hot tones that are multi-selected (ID + 7).
Hope this makes sense.. Thanks in advance!
azhummer
Sorry - it wouldn't let me post to the Uniden section. I was wondering how the SDS100/200 compares to Unication in handling of patched or multi-selected talkgroup activity. On my Unication G5 if a dispatcher has talkgroups patched, it appears to "behave" as it does on actual radios.. I can be locked on ID 1007 and hear radio traffic patched or multi-selected to ID's 1001, 1004, and 1007.. (so theoretically I could also be locked on 1001 and 1004 and hear the patched/multi-selected traffic).
I was wondering if the Uniden SDS100/200 behaves any differently.. I believe non-Type II on Uniden requires scanning all talkgroups involved in a patch and the patch radio traffic will 'randomly' pick one of the talkgroups its patched/multi-selected to - to carry the audio.
Obviously, in the old days - for type II systems you can use the status bits to better "catch" hot tones that are multi-selected (ID + 7).
Hope this makes sense.. Thanks in advance!
azhummer