Sentinel: Questions regarding Unit ID Fields

[J-Wrock]

So I've been using Uniden radios for a little over a decade and am digging into the various items that show up on the display. My questions are in regards to the Unit ID (UID) field.

1) How widely used is this? From what I understand, it shows the ID number of each radio so would this be something that could be practical on a large city wide or state wide system or better off on a smaller system?

2) Is there a limit to how many I can name in Sentinal or on the radio itself?

3) Specific to the SDS radios, what is the difference between the fields:
* "Unit ID"
* "Unit ID Name"
* "Unit ID Name 1 (1-16)"
* "Unit ID Name 2 (17-30)"
* "Unit ID Name 3 (31-46)" and
* "Unit ID Name 4 (47-60)"

 

[Whiskey3JMC]

1) How widely used is this? From what I understand, it shows the ID number of each radio so would this be something that could be practical on a large city wide or state wide system or better off on a smaller system?

Widely used enough. There are users here who spend a great deal of their lives documenting UIDs. They're particularly useful when documenting trends on encrypted talkgroups. If a UID surfaces on encrypted talkgroup A and also on encrypted talkgroup B one could conclude these talkgroups are shared by the same agency or serve the same or a similar purpose. Some systems have OTA aliasing making the pursuit of identifying UIDs a whole lot easier via DSDPlus Fastlane for example

2) Is there a limit to how many I can name in Sentinal or on the radio itself?

See this thread

3) Specific to the SDS radios, what is the difference between the fields:
* "Unit ID"
* "Unit ID Name"
* "Unit ID Name 1 (1-16)"
* "Unit ID Name 2 (17-30)"
* "Unit ID Name 3 (31-46)" and
* "Unit ID Name 4 (47-60)"

Where are you seeing the 1-16, 17-30, etc fields? I'm only seeing the below in Sentinel

Unit ID name is the alias. Unit ID is the actual ID number

 

[J-Wrock]

Widely used enough. There are users here who spend a great deal of their lives documenting UIDs. They're particularly useful when documenting trends on encrypted talkgroups. If a UID surfaces on encrypted talkgroup A and also on encrypted talkgroup B one could conclude these talkgroups are shared by the same agency or serve the same or a similar purpose. Some systems have OTA aliasing making the pursuit of identifying UIDs a whole lot easier via DSDPlus Fastlane for example


See this thread


Where are you seeing the 1-16, 17-30, etc fields? I'm only seeing the below in Sentinel
View attachment 203668
Unit ID name is the alias. Unit ID is the actual ID number

Thanks for answering my questions! Cleared up a bit of confusion on my end, although now I'm going to have to look into getting a DSDPlus Fastlane

As for the 1-16, 17-30, etc, I'm looking at the field customization screen in Sentinel for the SDS series:

 

[Whiskey3JMC]

Got it. I think you use those if you have UID names that won't fit on a single line on the SDSx00's display. Gives you more real estate to display UIDs up to 60 characters in length

 

[werinshades]

So I've been using Uniden radios for a little over a decade and am digging into the various items that show up on the display. My questions are in regards to the Unit ID (UID) field.

1) How widely used is this? From what I understand, it shows the ID number of each radio so would this be something that could be practical on a large city wide or state wide system or better off on a smaller system?

2) Is there a limit to how many I can name in Sentinal or on the radio itself?

3) Specific to the SDS radios, what is the difference between the fields:
* "Unit ID"
* "Unit ID Name"
* "Unit ID Name 1 (1-16)"
* "Unit ID Name 2 (17-30)"
* "Unit ID Name 3 (31-46)" and
* "Unit ID Name 4 (47-60)"

I text tag many of my Unit ID's across a few systems. 1 is a Statewide, another a citywide system, and a few others I regularly monitor. My personal preference is to see who's keying up the radio, or who thinks they're on one company but makes a boo boo and says the wrong company...LOL! This debate as to it's usefullness has gone on many years, while some like myself use it, others have various reasons for not using it. I've built out many lists over the years with some containing in the 4,000 text tag ranges, while some smaller. I have the capabilities to also see Alias ID's that the system generates, and not a fan of the format they use, but save it and edit it to my liking.

If your display is in Detail Trunking, the additional unit ID with name fields can be displayed. I don't use that format due to personal preference, but some might use it.

It takes alot of dedicated listening time, fast writer, and a general knowledge of the system you're monitoring (call signs/fire companies/ambulances etc) The three P's...Pen, Paper and Patience will help you develop an accurate list. I've been at it many years, so I have my groove going!

 

[J-Wrock]

I'm beginning to see a usefulness on my end; the hard part is going to be the long and tedious process of trying to figure out which unit id belongs to which unit and hope they don't switch out radios too often I don't think I'll ever get all the uid's figured out, but at least now I have a project to work on during my "down time".

Thanks for the replies

 

[werinshades]

Many have a"pattern" that you'll be able to figure out. Fire/EMS is usually easier because radios are mounted in apparatus and the portables might be assigned to the company. Each firefighter probably has their assigned radio for the day, so those can be marked. Police might use a portable, or a mobile which you might also see a pattern. Statewide system I have tagged uses the last 4 numbers of the troopers star/badge and since they have assigned vehicles, I can text tag it. If they get promoted, or transfer, their radio signature might change, so a simple edit on my side, and my accuracy is spot on. Yes, it is a project, but if you make a mistake, you can correct it and know one else knows.

 

[nessnet]

look into getting a DSDPlus Fastlane

#1: DSD Fastlane is software - and frankly, takes some proper writing of batch files to make it work.
It is not 'plug and play' - there is a bit of a learning curve if you are not familiar.

#2 DSD Fastlane requires hardware (a radio 'dongle' or two). Some go with RTL-SDRs and use as many as 2 or 3 of them if wider bandwidth is needed.

#3: As previously stated, "Some systems have OTA aliasing..... " Key word is SOME. You may want to research this first, if UIDs are the only reason you'd be doing this.

A bit more on the subject. Using tuner dongles (like RTL-SDRs) and software is amazingly powerful. VERY useful for tasks like 'mapping' new systems, because, depending on the software, it decodes all of the control channel's data stream activity. Highly 'geek' stuff. Personally, for someone just getting into this, I'd recommend software like SDRTrunk. Instead of having to write batch files to make things work, it is a Windows program, thus has a GUI and is much easier to use.

 

[J-Wrock]

#1: DSD Fastlane is software - and frankly, takes some proper writing of batch files to make it work.
It is not 'plug and play' - there is a bit of a learning curve if you are not familiar.

#2 DSD Fastlane requires hardware (a radio 'dongle' or two). Some go with RTL-SDRs and use as many as 2 or 3 of them if wider bandwidth is needed.

#3: As previously stated, "Some systems have OTA aliasing..... " Key word is SOME. You may want to research this first, if UIDs are the only reason you'd be doing this.

A bit more on the subject. Using tuner dongles (like RTL-SDRs) and software is amazingly powerful. VERY useful for tasks like 'mapping' new systems, because, depending on the software, it decodes all of the control channel's data stream activity. Highly 'geek' stuff. Personally, for someone just getting into this, I'd recommend software like SDRTrunk. Instead of having to write batch files to make things work, it is a Windows program, thus has a GUI and is much easier to use.

As fun as the DSD Fastlane or SDRTrunk sounds, and believe me my geek side REALLY wants to play with them, the practical side of me says I should hold off for now. If / when I do eventually dip my toes into this, it won't be only for the Unit IDs

I do appreciate the feedback on all of this