I s anyone (else) keeping a list of users on the P25 system? If so, would you like to share/swap files?
List of users/RIDs
- Thread starter gldavis
- Start date
Maybe if you started a RR Wiki page other people would contribute to it. I did it for the NC statewide VIPER system and it has grown a lot since I first started it.
I have some coming from dsdplus , it seems to have been added by others . since it uses some internet connection to get the info... I've got my own list from unitrunker, but I've been busy and not kept on top of it for a couple of months since yard work season started
I have (at this time) a total of 8510 users. Of those, about 1200 I have confirmed user info (Medic Ambulance 42 for example); about 2k I have the department (City/county/ect); the rest I haven't a clue (yet). A lot of work involved. (P.S. I have 1433 listed Channels/Talkgroups)
I have about 450 or so from Summit and Wasatch counties from when I visited family for a couple of days. I was unable to get SDRTrunk to do any recording for some reason, but was able get them from the SDS200.
Last update, I now have 13,984 individual radio IDs. This is just covering SL/Davis County area. (at $29/month per radio, that is a lot of income 
)
)
If anyone is following/tracking radio Alias's, I gotta question. Have you noticed that a lot of UDOT radios, are being programmed with 2 different Alias's? (I wonder how that works? )
)
Two ID numbers for the same alpha tag, or previously identified RID's showing up with different tags?
I'm sure that a lot of 9A units are carrying a portable, so that explains two radios for the same user. My thoughts about the previously identified ones displaying a different user is that it has something to do with logging into an MDT. I noticed the latter while collecting ID's for Summit & Wasatch counties.
I'm sure that a lot of 9A units are carrying a portable, so that explains two radios for the same user. My thoughts about the previously identified ones displaying a different user is that it has something to do with logging into an MDT. I noticed the latter while collecting ID's for Summit & Wasatch counties.
Same Radio ID (RID) "8581224", with 2 different interchangeable Alias's (9A-515-M or 9A-518-M). Sometimes one alias is used, sometimes the other. Both using the same RID. There are several UDOT radios with this (to me) issue. Normally "-P" = portable/handheld, and "-M" = Mobile/car unit. (or so I've led myself to believe.)
That just looks like a different user logged into the same vehicle's MDT. Same radio ID, but alpha tag gets updated for dispatching or tracking purposes. It is very frustrating, and ! Im almost to the point of just naming them all XX-UNIT, XX-PD, and XX-DEPUTY, unless it's a dispatch console or portable.
Oh, well that makes some sense. So the Alpha Numeric "Alias" is set by the MDT at each log-in, and not programmed into the radio? I wonder how that works with portable/handheld units? (I have copied some radios with 3 different Alias's. Could be explained by the MDT.)
PMJ2kx
Curious Onlooker
Ha...I just have the entire range tagged as "9A UDOT Radio" - too difficult to keep up with everyone. Same with UHP...not even going to try!
Thankfully 8J doesn't do that to their radios. I am, however, having the opposite problem of yours.
Supposedly there is one RID (14670027) that is actually physically two different radios - one is a base / mobile for fire in one of their stations, and the other is (assumed) a portable for PD. I didn't think this was possible because it would create a bunch of problems, but a casual query suggests "It's possible, but not recommended" - I wish SDR Trunk had more granular logging where you could track affiliations or registrations for singular RIDs or ranges instead of having to navigate literal gigabytes of logged output.
Thankfully 8J doesn't do that to their radios. I am, however, having the opposite problem of yours.
Supposedly there is one RID (14670027) that is actually physically two different radios - one is a base / mobile for fire in one of their stations, and the other is (assumed) a portable for PD. I didn't think this was possible because it would create a bunch of problems, but a casual query suggests "It's possible, but not recommended" - I wish SDR Trunk had more granular logging where you could track affiliations or registrations for singular RIDs or ranges instead of having to navigate literal gigabytes of logged output.
I have ran into the issue of actual duplicate RID's in my county here in WY. At first, I thought my town was literally running the wheels off of one of the PD vehicles. Two different radios, but turns out they do indeed have the same ID. There is also a brush truck and one of the engines that share an ID. Dispatch doesn't seem to care, but it drives me crazy!
As for logging with SDRTrunk, one way I did find to get info from SDRTrunk directly was kind of a pain, but did work. If you click on one of the "control" boxes to highlight the channel, you can then click on the details tab. When you scroll to the bottom, you'll see a list of active radios listed, along with all of the details. You can highlight the data and copy it via keyboard (Cntrl+C), and then paste into a spreadsheet. Once you have them in a spreadsheet, it's easy to import them into Sentinel, ProScan, or even into Unication PPS
My screenshot doesn't show anything, but if you take a look at yours, you'll get the idea.
If i could manage to get audio recordings working, it would be much easier to extract data since you can simply highlight, copy, and past from Trunking Recorder. If memory serves, the recording feature worked in the past when I was running a beta version of SDRTrunk that was released in April of '24, but will not work with the current official release. I suppose I could download a few of the older beta versions to test out next time I head to UT to visit family.
For clarification, (and please correct me if I am wrong), to operate on "The System", each radio must be programmed with an approved Radio ID that is affiliated with a user (PD/FD/EMS/ect) and entered into the main UCA computer. Some recommend that an "Alias" also be programmed in the radio, for user display convivence. (is that correct?)
Up until now, I had assumed that each RID that I saw/heard was a unique radio. Now I'm wondering if maybe there are 2 (or more) radios programmed with duplicate RID, but different Alias's? side note, there was a report of a department programming 1 radio, then cloning the info to all their other radios. The UCA system denied them when they tried to communicate.
Up until now, I had assumed that each RID that I saw/heard was a unique radio. Now I'm wondering if maybe there are 2 (or more) radios programmed with duplicate RID, but different Alias's? side note, there was a report of a department programming 1 radio, then cloning the info to all their other radios. The UCA system denied them when they tried to communicate.
P.S. I use SDRTrunk, Unitrunker, and ProScan for collection purposes. Each has its advantages and disadvantages.
PMJ2kx
Curious Onlooker
Yeah, so looking into this further, supposedly Link Layer Authentication should prevent this from happening (just read a white paper on this). The master site controller should be preventing dupes from registering not only to prevent radio conflicts, but also as a security measure to prevent unauthorized access.
So your side note tracks, and I would conclude this should be the norm for the entire system. It also could be an issue with the way SDR Trunk or other software tracks and records RIDs. The program took a nose dive for me yesterday and decided it didn't like my SDRs. Decode was awful, and my computer was doing some weird things. Couldn't figure it out - reset everything, reinstalled SDR drivers, new USB hub, etc. Ended up downloading the latest nightly release to test, and so far, so good, so something went south somewhere for me.
Considering that I had to refresh my entire setup, and reading what I did about LLA, now I'm not convinced there are duplicates - rather it was a software error on my end. So I'll have to wait and see...
To be fair, I'm sure only the nerdiest of nerdy dispatchers would care, along with the system techs. The stories I've heard from my friends back home in Oregon who are either system users or dispatchers themselves...let's just say that some struggle just to use a computer, let alone know where to look at what radio is keying up and talking to them (and seeing that it's a dupe)...I have ran into the issue of actual duplicate RID's in my county here in WY. At first, I thought my town was literally running the wheels off of one of the PD vehicles. Two different radios, but turns out they do indeed have the same ID. There is also a brush truck and one of the engines that share an ID. Dispatch doesn't seem to care, but it drives me crazy!
After starting over with SDRTrunk, are you able to record audio? I didn't have any success the last two times I went to UT. It works perfectly on WyoLink, and also on other systems in my area.
I had to go up to the top and see if we are still n topic, and we are, sortof. UCA, VECC, and UPD (among others) have been talking/concerned about Field programing of RIDs. The rules say, 1 RID = 1 radio. Reality often does not follow the rules. I have confirmed over 100 RIDs that are assigned 2 (or more) Alias's. As long as only 1 radio is on at a time, the system will work.
I primarily use SDRTrunk for recording RID-Alias data. (I have noticed some AES Keys. very odd)
I use ProScan to record Audio, that I can then match RID to Talk Group use (very time consuming)
I use Unitrunker to monitor Control channel usage.
(Now up to 14,486 individual RIDs)
I have confirmed over 100 RIDs that are assigned 2 (or more) Alias's. As long as only 1 radio is on at a time, the system will work.I primarily use SDRTrunk for recording RID-Alias data. (I have noticed some AES Keys. very odd)
I use ProScan to record Audio, that I can then match RID to Talk Group use (very time consuming)
I use Unitrunker to monitor Control channel usage.
(Now up to 14,486 individual RIDs)
I keep them stored in my brain lol. I can remember hex/decs code and who they belong to but not where I left my car keys lol. Weird!
Similar threads
