Homeland Defense Network Radio ID's

[PurityControl2]

After sitting empty and lifeless for a couple years, we've got some data! I've added each alias I could so far and will be helping to maintain the list going forward. I have some unconfirmed ID's I'll be adding to that section later today. Thanks to @adamfancher , I may or may not have gleaned your template from the CLMRN Radio ID's but either way nice to get this data added to the list! Another thanks to @cg , I would not have gotten DSDPlus working without you. Thank you!

Homeland Defense Network Radio IDs - The RadioReference Wiki

 

[smartconnect]

After sitting empty and lifeless for a couple years, we've got some data! I've added each alias I could so far and will be helping to maintain the list going forward. I have some unconfirmed ID's I'll be adding to that section later today. Thanks to @adamfancher , I may or may not have gleaned your template from the CLMRN Radio ID's but either way nice to get this data added to the list! Another thanks to @cg , I would not have gotten DSDPlus working without you. Thank you!

Homeland Defense Network Radio IDs - The RadioReference Wiki

i hear they use the clmrn id scheme

 

[PurityControl2]

i hear they use the clmrn id scheme

Marcus should really try doing some organizing, their RID's are sloppy. Lazy techs assigning ID's mostly randomly? Sure seems like it, it's a mess as well with Talker Aliases. CLMRN is much more organized and professional. The Marcus techs could learn a thing or two from CTS I'm sure! Of course, this whole reply is in my mere humble opinion.

 

[GraniteScanner]

Marcus should really try doing some organizing, their RID's are sloppy. Lazy techs assigning ID's mostly randomly? Sure seems like it, it's a mess as well with Talker Aliases. CLMRN is much more organized and professional. The Marcus techs could learn a thing or two from CTS I'm sure! Of course, this whole reply is in my mere humble opinion.

 

[Sys_Admin]

Marcus should really try doing some organizing, their RID's are sloppy. Lazy techs assigning ID's mostly randomly? Sure seems like it, it's a mess as well with Talker Aliases. CLMRN is much more organized and professional. The Marcus techs could learn a thing or two from CTS I'm sure! Of course, this whole reply is in my mere humble opinion.

Marcus UIDs and GIDs are actually very well organized, if you know what you are looking at. Marcus Hytera system is programmed with the Fleet dialing plan. I.E, Marcus internal talkgroup is 500-20-901, with internal UID starting at 500-20-200. Further example, Greater Hartford Transit District Group A is 500-88-900, Group B is 500-88-901, and so on, With UIDs starting at 500-88-200. For customers that they serve, it leaves plenty of room for expansion for both units and groups.

If you just look at the converted DMR flat ID, you might think its a mess...

 

[PurityControl2]

You mean to tell me Marcus doesn't actually use the CLMRN ID scheme? But but but how will the Homeland be Defended?? What is the Homeland Defense Network defending against??The nation relies on the Homeland Defense Network for safety and defense of our homeland, in my mere humble opinion! Defend defend defend the Homeland!

 

[APX7500X2]

Marcus should really try doing some organizing, their RID's are sloppy. Lazy techs assigning ID's mostly randomly? Sure seems like it, it's a mess as well with Talker Aliases. CLMRN is much more organized and professional. The Marcus techs could learn a thing or two from CTS I'm sure! Of course, this whole reply is in my mere humble opinion.

FOOT=MOUTH

 

[PurityControl2]

FOOT=MOUTH

Lol it ain't that serious man. I wanted some info about the system and RID's because it fascinates me how all this works not only for the HDN but also CLMRN and so on. If I just straight up asked some questions nicely the info certainly would not have been forthcoming, hence smartconnect's erroneous reply. Info wouldn't come nearly in such a timely manner either. Don't take it personally.

 

[seagravebuff60]

Ive seen some public safety systems with a more disorganized scheme for their radio IDs.

But for real, the DEC TGs and RIDs may seem unusual, but that's because of the CPS-P3 or dialing scheme they employ.
In CPS-P3 Values, a TG or RID is formatted as"Net-Fleet-Sub". Let's take Trinity as an example: 500-33-900. Anything with a 500-33-### (33 being the TG fleet) will be a Trinity TG, with a capacity for 99 TGs or "Sub". With each Fleet of TGs, there is a corresponding Fleet of RIDs. For Trinity, anything in the TG fleet (33) has a RID Fleet of 33 as well, so all the RIDs for Trinity are 500-33-###. Additionally, only RIDs with this scheme would be reserved for Trinity. I think for the RIDs, they have to start at ###-##-200 or something like that. Additionally, another TG Fleet, such as GTHD (88), cannot be part of the same RID Fleet (33). Meaning RID 500-33-232 can't be a GTHD assigned Radio.

There's a specific calculation to determine which RIDs are assigned to which TG fleet, but it involves a complex mathematical equation that only a rocket surgeon can figure out. It may seem confusing, but DSD+ has this feature built in and automatically calculates the CPS-P3 Values. I don't think unidens can yet comprehend the CPS-P3 structure.

Once you see all the talkgroups and Radio IDs in CPS-P3 format with Net-Fleet-Sub in DSD+, it will seem much more organized. What makes it look sloppy is the conversion back from CPS-P3 to DEC.

 

[cg]

I was keeping all my files in CPS-P3 format but once Uniden got the scanners going, I moved them back to the DEC format. It is fairly easy and you can go back and forth with DSDPlus with a semicolon just before the CPS-P3 to block it. Once voice activity is logged it switched all the GROUPS and RADIOS to whichever is set.
TIIIStd, L1501:13, "Marcus TierIII", 5 , CPS-P3; custom NetID
TIIIStd, L1501:13, "Marcus TierIII", 5; , CPS-P3; custom NetID

 

[seagravebuff60]

TIIIStd, L1501:13, "Marcus TierIII", 5 , CPS-P3; custom NetID
TIIIStd, L1501:13, "Marcus TierIII", 5; , CPS-P3; custom NetID

What are the extra parameters here, such as the "5" before "CPS-P3" and "Custom Net ID" ?

I only have: (In my .networks file)

TIIIStd, L2:13, "L2:13 Marcus HDN", CPS-P3

 

[PurityControl2]

Ive seen some public safety systems with a more disorganized scheme for their radio IDs.

But for real, the DEC TGs and RIDs may seem unusual, but that's because of the CPS-P3 or dialing scheme they employ.
In CPS-P3 Values, a TG or RID is formatted as"Net-Fleet-Sub". Let's take Trinity as an example: 500-33-900. Anything with a 500-33-### (33 being the TG fleet) will be a Trinity TG, with a capacity for 99 TGs or "Sub". With each Fleet of TGs, there is a corresponding Fleet of RIDs. For Trinity, anything in the TG fleet (33) has a RID Fleet of 33 as well, so all the RIDs for Trinity are 500-33-###. Additionally, only RIDs with this scheme would be reserved for Trinity. I think for the RIDs, they have to start at ###-##-200 or something like that. Additionally, another TG Fleet, such as GTHD (88), cannot be part of the same RID Fleet (33). Meaning RID 500-33-232 can't be a GTHD assigned Radio.

There's a specific calculation to determine which RIDs are assigned to which TG fleet, but it involves a complex mathematical equation that only a rocket surgeon can figure out. It may seem confusing, but DSD+ has this feature built in and automatically calculates the CPS-P3 Values. I don't think unidens can yet comprehend the CPS-P3 structure.

Once you see all the talkgroups and Radio IDs in CPS-P3 format with Net-Fleet-Sub in DSD+, it will seem much more organized. What makes it look sloppy is the conversion back from CPS-P3 to DEC.

Hey man, thanks a ton for that information! I'll have to switch over DSD to the CPS-P3 format and check that out, still very much a beginner with DSD but it's a fantastic program. Being able to receive talker alias is the cherry on top for me lol. Having to manually maintain a list of RID's in the scanner got old pretty quick. Thank you again and thanks to cg as well. I appreciate you guys sharing the knowledge. Thanks

 

[cg]

the 5 is area length, I believe it corresponds to the Large. To be honest, I have had in there since the beginning of TierIII
; line format: protocol, networkID, "network name"[, TIIIareaLength]

I have my own custom Net IDs (vs over the air distinctive SYSIDs) to separate various systems such as conventional P25 and conventional DMR channels as well as the common L13 DMR TierIII. I started it well before the use of RR system entries for custom IDs. In short, that means State (1-CT), Type system (DMR TIII=5) and system (01 is first CT DMR Tier III)