SDS programing uid as tg question

[bravo14]

A few days ago I made a Dept for UID/RID to listen to certain UID/RID instead of listening to all uid/rid. Example I put in a i in front the uid in the TG section and I made a few and did a test nothing happen just scans. Is there something I'm missing I looked around didn't see much.

 

[jonwienke]

That only works for private calls. You can't filter general traffic by radio ID.

 

[bravo14]

That only works for private calls. You can't filter general traffic by radio ID.

Dang. Thanks for the info. I was hoping just filter out certain traffic.

 

[ofd8001]

In addition to the above, you do not need to add the "i" on Radio ID numbers. They are entered from the System portion, just beside Sites where it says "Unit IDs",

I suspect the purpose of not being able to filter transmissions by transmitting radio is that folks only hear half the conversation. You could do Alert Tone and/or Alert Light for specific Unit IDs if that is helpful to you.

 

[bravo14]

In addition to the above, you do not need to add the "i" on Radio ID numbers. They are entered from the System portion, just beside Sites where it says "Unit IDs",

I suspect the purpose of not being able to filter transmissions by transmitting radio is that folks only hear half the conversation. You could do Alert Tone and/or Alert Light for specific Unit IDs if that is helpful to you.

I was trying to listen to Disp only. I know about the Alert Tone/Lights.

 

[jonwienke]

In addition to the above, you do not need to add the "i" on Radio ID numbers.

Actually you do, if entering a radio ID where a talkgroup ID would normally go, to monitor radio-to-radio private calls.

If dispatch uses radio ID 1234, you can create a channel entry for talkgroup i1234 to catch private calls between dispatch and other units. But that won't filter traffic to just dispatch keyups on standard calls, because the talkgroup ID is always different than the radio ID when the system is set up correctly, and for standard calls, the scanner filters traffic by talkgroup ID, not radio ID.

To do what you're proposing, you'd have to be able to enter u1234 as the talkgroup ID in a channel entry to cue the scanner to look for for normal traffic (not a private call) coming from radio ID 1234, and you'd have to figure out a conflict resolution framework to resolve what happens when you have channel entries for both unit u and talkgroup t programmed, and unit u keys up on talkgroup t. Which programmed channel would win the conflict, and why? If you say the unit channel, then you lose the talkgroup info for any transmission from unit u. If you say the talkgroup channel, then we're back to the status quo.

And for that reason, I doubt your suggestion will be implemented.