The not-locked-out CONV object (without the specific "privacy tone squelch") will continue to receive all traffic that contains that specific "privacy tone squelch". CONV objects as you describe do not work like TGRP objects (wildcard + specific locked-out TGIDs).You might be monitoring a specific conventional frequency. There is interference that you don't want coming from a specific privacy tone. Simply create a new object, that is locked out, with the offending privacy tone squelch, and then your other object will continue to play all other traffic on the frequency.
Yes, same for NXDN talkgroups. CONV objects are completely independent of each other. Locking out one CONV object has no effect on any other CONV object.Thanks for the correction. I suppose that makes sense why there is an "exclude" option in the conventional object squelch settings.
I assume the same holds true for NXDN talkgroups programmed conventionally? If so, I need to issue a correction on another thread.
I've also noted that when you set your object to 'reject' a certain squelch tone/code, it doesn't record the squelch codes of the objects that it does allow. Would love to see this updated at some point.The not-locked-out CONV object (without the specific "privacy tone squelch") will continue to receive all traffic that contains that specific "privacy tone squelch". CONV objects as you describe do not work like TGRP objects (wildcard + specific locked-out TGIDs).