Tier III System ID's?

[mwjones]

With the recent update to DSDPlus 2.457, Tier III entries in its configuration files now require the Letter prefix on the System ID - T, S, L, H (Tiny, Small, Large and Huge respectively). What I've noticed is that the systems in RRDB seem to be inconsistent with how that prefix is shown (if at all, which is acceptable if the submitter is not using DSDPlus).

Some examples:

Correct System ID shown in System Notes: Arlington I.S.D. Trunking System, Arlington, Texas

System ID Hex value includes the Prefix (even though that value is the Decimal value, for scanners that don't use the prefix the Hex value without it is fine): Crosspoint Communications Tier 3 Trunking System, Dallas, Texas

No prefix at all (I am the submitter of this system so I know the prefix is "S"): General Motors Arlington Assembly Plant Trunking System, Arlington, Texas

It would be nice if the System ID field could be updated to support these prefixes properly, and likewise the System Reports for Tier 3 (both Standard and Capacity Max) be updated to show them as well.

 

[mtindor]

With the recent update to DSDPlus 2.457, Tier III entries in its configuration files now require the Letter prefix on the System ID - T, S, L, H (Tiny, Small, Large and Huge respectively). What I've noticed is that the systems in RRDB seem to be inconsistent with how that prefix is shown (if at all, which is acceptable if the submitter is not using DSDPlus).

Some examples:

Correct System ID shown in System Notes: Arlington I.S.D. Trunking System, Arlington, Texas

System ID Hex value includes the Prefix (even though that value is the Decimal value, for scanners that don't use the prefix the Hex value without it is fine): Crosspoint Communications Tier 3 Trunking System, Dallas, Texas

No prefix at all (I am the submitter of this system so I know the prefix is "S"): General Motors Arlington Assembly Plant Trunking System, Arlington, Texas

It would be nice if the System ID field could be updated to support these prefixes properly, and likewise the System Reports for Tier 3 (both Standard and Capacity Max) be updated to show them as well.

If that were allowed, then the allowance would have to include the same for NXDN trunking as well. And if that were to happen, my suggestion would be to allow the networkID/systemID search to allow either A### or just ### in as a partial search to produce a list of trunked systems that contain ###. Why? Because by now everyone is used to only using the RR search to search ###.

And then admins would have to go back and touch every system that they know the Network Model for an add that to the NetworkID.

Not saying it shouldn't be done. Just saying if it is done, attempts should be made to update that field on all NXDN/DMR TIII systems -- and we should be able to search for either S10 or L110 or 10 or 110

Mike

 

[UAT_978]

What function does this information serve to the user? I am not as familiar with Tier III as I am with other flavors of trunking. Is this something that is needed to program a receiver? A transceiver?

 

[mtindor]

What function does this information serve to the user? I am not as familiar with Tier III as I am with other flavors of trunking. Is this something that is needed to program a receiver? A transceiver?

• For scanners, it makes no difference.
• For DSDPlus, it's useful to know this information since the DSDPlus files want the Network Model information
• For general searching of the RRDB "Query by System ID" it is useful

- RRDB | Trunking Data | Query

Admins are currently not supposed to add the Network Model (T/S/L/H) to a Network/SystemID. So most if not all database entries do not list T/S/L/H. If somebody types in a search for L110 and the NetworkID/SystemID is only 110 in the DB, then it doesn't display a system for them via the search. If it were changed to include T/S/L/H (and admins went and updated all relevant systems so that the NetworkID/SystemID were included), then you could search for S10 or L183 or something like that and get a result.

 

[UAT_978]

Awesome! Thank you for that explanation. Makes sense. The more data points to have on a system the better. I have been going back and running unitrunker on systems to get the bandplans and site NACs for P25 TRS systems for the same reasons.

 

[theaton]

In Utah there's a NXDN system with a SysID of R64. I don't know what the "R" stand for. It's a DFA system, and the company has an older non-DFA system with a SysID of L64. Listing the Model letter would help distinguish them.

Peak Wireless Services (DFA)

 

[GTR8000]

Memory is fuzzy, but I believe the NEXEDGE size codes are Global, Regional, Local. I'm sure @mtindor will correct me if I'm wrong. DMR is Huge, Large, Small, Tiny.

 

[theaton]

Where will we enter a Global system in the DB?

 

[mtindor]

Memory is fuzzy, but I believe the NEXEDGE size codes are Global, Regional, Local. I'm sure @mtindor will correct me if I'm wrong. DMR is Huge, Large, Small, Tiny.

Been a while, so I don't remember the knowledge to confirm. But sounds good to me. I recognize those now that you say them.