DSDPlus Two Local Systems Using the Same System ID?

[Facsimile]

Two local systems are using the same System ID of 10. Is there a way to differentiate them in DSDPlus so my .groups and .radios files don't get messed up?

The two systems in question are below:

ERS Wireless Indiana Trunking System, Various, Indiana

ERS Wireless Indiana Trunking System Profile

www.radioreference.com

Northern Indiana Public Service Company Trunking System, Multiple, Indiana

Northern Indiana Public Service Company Trunking System Profile

www.radioreference.com

Thanks

 

[mwjones]

Indeed there is. DSDPlus Fastlane supports a Virtual Prefix as part of the System/Network ID on Tier III and iDAS systems:

Here's some examples from my DSDPlus.networks file:

TIIIStd, L699:1, "Wise Electric Cooperative"
TIIIStd, T947:1, "Wise Health System"
TIIInonStd, H10:1, "Crosspoint Communications (Tier 3)"
TIIInonStd, S433:1, "Spirit Aviation"
TIIInonStd, L775:1, "Empire Liberty Electric"

The format of the entry is the Letter Indicating the System Size (Tiny, Small, Large, Huge), followed by the prefix (which can be 1-4096), a colon and the System/Network ID. As long as your networks, sites, and frequencies files all use that same prefix, the system will write the same prefix in the groups and radios files. What those prefixes are is your preference (mine are based on the URL of the system in RadioReference)

 

[cg]

If you look in the Notes file, the information is described within with DSD+ version 2.457, roughly line 278 in the document.

 

[Facsimile]

Here's some examples from my DSDPlus.networks file:

The format of the entry is the Letter Indicating the System Size (Tiny, Small, Large, Huge), followed by the prefix (which can be 1-4096), a colon and the System/Network ID. As long as your networks, sites, and frequencies files all use that same prefix, the system will write the same prefix in the groups and radios files. What those prefixes are is your preference (mine are based on the URL of the system in RadioReference)

Awesome, thank you. That worked perfectly for me. Do you happen to know if there is a way to determine whether TIIIStd or TIIInonStd is correctly auto selected in DSDPlus? I noticed that there is a Force TIII Std option so I figured DSDPlus might get it wrong sometimes. Plus, if you look at the Northern Indiana Public Service Company (NIPSCO 900MHz) Trunking System, Multiple, Indiana link, the system is listed at DMR Tier 3 Standard. Just wanted to make sure I'm not confusing the standard listed there with the TIIIStd/nonStd.

Also, I noticed your .networks file doesn't have the [, TIIIareaLength] at the end. Is that not needed?

If you look in the Notes file, the information is described within with DSD+ version 2.457, roughly line 278 in the document.

!!! You can laugh at me. My notes.txt was only updated to version 2.395! It's now updated. Thanks!

 

[mwjones]

Awesome, thank you. That worked perfectly for me. Do you happen to know if there is a way to determine whether TIIIStd or TIIInonStd is correctly auto selected in DSDPlus? I noticed that there is a Force TIII Std option so I figured DSDPlus might get it wrong sometimes. Plus, if you look at the Northern Indiana Public Service Company (NIPSCO 900MHz) Trunking System, Multiple, Indiana link, the system is listed at DMR Tier 3 Standard. Just wanted to make sure I'm not confusing the standard listed there with the TIIIStd/nonStd.

The system defaults to Auto-detect. It will first start in TIIIStd, but if it detects non-standard bits it will switch over, for example here's the event window of a Motorola Capacity Max (which is Non-Standard) being found but not in the DSDPlus.frequences file:



You can see the Network ID and Site number both changed once it made the switch. Once I load the frequencies file, you'll still see the switch, but it will tell you that it is being forced (You'll also notice in my sample screen the prefix showing up when the system tunes in).



I've looked at more than two-dozen systems (both standard and non-standard) since this update to TIII for Standard and Non-Standard was released and have yet to have a bad match.

When I look at the NIPSCO system, the System Size is unknown, and the fact that there is no "region" (standard Tier III site numbers are formatted as <region>.<site>, while Capacity Max/non-Standard just has a numeric Site number) leads me to believe it is a Capacity Max (which doesn't use Regions) and is labeled incorrectly in RRDB. If you tune to it, DSDPlus will complain if you're wrong, but both items should be discovered and submitted as updates if necessary (especially since missing the System Size in the config files will create errors when you launch DSDPlus) - once you connect to the system and receive some data we can fill in those blanks.

Also, I noticed your .networks file doesn't have the [, TIIIareaLength] at the end. Is that not needed?

I have yet to see TIIIareaLength come into play in non-Standard systems, but I do have it on a couple of Standard systems that weren't in my examples (I have 20 Tier III systems in my active networks file of nearly 200 systems so what I posted is only a snippet), likewise the same for systems using CPS-P3 talkgroup and radio numbering.

 

[cg]

Notes file says
TIIIStd site numbers must include an area value. TIIInonStd site numbers must not.