SDS100/SDS200: UID lockout/avoid?

[kittrav]

I'm monitoring a CAP+ system with multiple business users. There's a particular Talk Group with a particular UID that only transmits periodic noise bursts.

Is there a way to lockout/avoid that UID?

I realize I could erase that UID and then toggle ID Search off, but I would like to retain the ID Search function.

Any suggestions?

 

[GTR8000]

There is no way to avoid a UID. Even if you were to delete that UID and turn ID Search off, scanning that talkgroup would still result in you hearing the noise from that particular UID. You can only avoid entire talkgroups, not specific users.

 

[richardbritt]

I have a related question, is there a way to flag a specific uid like using an audio alert for a particular radio id on a trunking system?

Thanks

Regards Richard

 

[sonm10]

I have a related question, is there a way to flag a specific uid like using an audio alert for a particular radio id on a trunking system?

Thanks

Regards Richard

Yes - you can do this but I can't remember how lol
There is a section somewhere to add RIDs. You can set a custom alert.

 

[nessnet]

Easier to Read SDS100/200 Digital Scanner Manual

 

[Ubbe]

I'm monitoring a CAP+ system with multiple business users. There's a particular Talk Group with a particular UID that only transmits periodic noise bursts.

That would make other users monitoring that TG go crazy. It's probably some sort of data info transmitted to be received by another device that collects the data. Are you sure you have other users on that TG that use voice communication? I wonder how that would be technically possible.

Maybe it's an encrypted call that then isn't fully detected by the scanner and it mutes too late? Can you make a video of the display when that noise burst happens?

/Ubbe

 

[kittrav]

That would make other users monitoring that TG go crazy. It's probably some sort of data info transmitted to be received by another device that collects the data. Are you sure you have other users on that TG that use voice communication? I wonder how that would be technically possible.

Maybe it's an encrypted call that then isn't fully detected by the scanner and it mutes too late? Can you make a video of the display when that noise burst happens?

/Ubbe

It's a -- an? -- university security Talk Group. Law enforcement functions are on a separate P25 County system.

Regular voice traffic, I've identified the primary dispatch UID. The bursts, consistent in audio content, are only a few seconds long and occur perhaps every ten minutes. Haven't actually timed them. Always the same UID displayed.

I did change the digital signal time delay, with no effect.

Not sure I'm smart enough to be able to capture, and then upload, a video of the display. I'm using ProScan, and I do have some NooElec and RTL SDRs. Perhaps I could use SDR# to record the waterfall display?

Instructions?

 

[ofd8001]

Yes - you can do this but I can't remember how lol
There is a section somewhere to add RIDs. You can set a custom alert.

If you edit the applicable Favorites List in Sentinel, while on the desired system, look at the right pane. You will see a tab "Unit IDs". You can add an Alpha Tag, the Unit ID, Alert Tone and Alert Light.

 

[Ubbe]

It's a -- an? -- university security Talk Group.

Digital waiting time are only in use if you have programmed a single conventional DMR frequency and have chosen to run it as both analog and digital. It is only used while in analog mode. Trunked Cap+ cannot be programmed to use analog so that timer will have no function.

As it is the same UID sending noise bursts, that probably are high speed data, it might be connected to the universitys security system to alert about doors that open and close and that kind of events.

I have a univerisity security system that sends pocsag to alert a pager and show a text message what event that have triggered and then it is followed by a couple of seconds of a high speed data burst. That burst cannot be received by the pager so probably goes to some other receiver that listens to the frequency and logs the events.

Can you post the audio file to let us hear if it is data or just noise? I haven't found a way to avoid a specific UID to not be monitored by a Uniden scanner but I believe I did that with Whistlers TRX scanners, that operates in a different way on trunked DMR systems. As I remember how Unidens operating system works you cannot use lights and alerts for a UID while on a DMR TG, it's only for private calls UID to UID without using a TG. So their firmware code can then neither handle UID avoids on a TG or any other actions besides displaying the UID number and its text tag, it is only the configuration for the TG that controls lights and alerts and avoids.

It's not much you can do to avoid listening to those noise bursts.

/Ubbe

 

[kittrav]

Digital waiting time are only in use if you have programmed a single conventional DMR frequency and have chosen to run it as both analog and digital. It is only used while in analog mode. Trunked Cap+ cannot be programmed to use analog so that timer will have no function.

As it is the same UID sending noise bursts, that probably are high speed data, it might be connected to the universitys security system to alert about doors that open and close and that kind of events.

I have a univerisity security system that sends pocsag to alert a pager and show a text message what event that have triggered and then it is followed by a couple of seconds of a high speed data burst. That burst cannot be received by the pager so probably goes to some other receiver that listens to the frequency and logs the events.

Can you post the audio file to let us hear if it is data or just noise? I haven't found a way to avoid a specific UID to not be monitored by a Uniden scanner but I believe I did that with Whistlers TRX scanners, that operates in a different way on trunked DMR systems. As I remember how Unidens operating system works you cannot use lights and alerts for a UID while on a DMR TG, it's only for private calls UID to UID without using a TG. So their firmware code can then neither handle UID avoids on a TG or any other actions besides displaying the UID number and its text tag, it is only the configuration for the TG that controls lights and alerts and avoids.

It's not much you can do to avoid listening to those noise bursts.

/Ubbe

So, several things.
1st, the "noise bursts" are infrequent now.
2nd, what I was describing as "noise bursts" are better described as "dead air" -- carrier with no modulation -- for a second or two, followed by a sound similar to that I believe is called a squelch tail.
3rd, there are automated voice announcements of alerts from emergency call boxes, that are then confirmed with voice traffic between a dispatcher and campus security personnel. I have not yet seen a correlation between these and what I described above.
4th, by chance, from listening to both the campus law enforcement TG on the County's P25 system and the campus security TG on a business CAP+ system, there is apparently a cross-patch. Some P25 conversations, with various UIDs, are being heard on a single UID on the CAP+ system, a different CAP+ UID than the dead air/squelch tails.
5th, if the dead air/squelch tail phenomenon returns with any regularity, I will attempt to record a sample.

Thanks all for the help.

 

[Ubbe]

2nd, what I was describing as "noise bursts" are better described as "dead air" -- carrier with no modulation -- for a second or two, followed by a sound similar to that I believe is called a squelch tail.

As squelch tails can't exists in digital modulation in either system it has to be a patch between an analog repeater and either the Cap+ system or to the P25 system that then has one additional patch to the Cap+ system.

It's common to patch from an old analog repeater to a new digital system while replacing old radios with new. So it can still be in operation as long as someone doesn't put resources and time to decommission that old analog site.

I installed a repeater 30 years ago for a money transport company that ceased to exist after 10 years and they plainly abandon their repeater and it remained at its location and I can still hear today that it keys up for two seconds maybe once a month or so when the squelch reacts to some interference as it doesn't use any subtone control for its receiver.

/Ubbe