DSDPlus Network and Site Numbers DSDPlus vs Uniden DMR Type 3

[cellphone]

I'm trying to understand why DSDPlus network and site numbers are different vs what is displayed on Uniden scanners. I'm monitoring a fairly new DMR Type 3 system in Arizona:

CSW Communications DT3 Trunking System, Tucson, Arizona

CSW Communications DT3 Trunking System Profile

www.radioreference.com

Looking at the South Mountain site, here is what the BCD536HP shows:
Network 10, Site 6


Here is what the SDS200 shows:
Network Ah (10 decimal), Site 6


Here is what DSDPlus shows. I'm running the latest Fast Lane Release 2.289:


Both the network and site is 1 higher than what the Uniden's show. The neighbor sites are also showing one higher than shown on the Uniden radios.

Looking in the DSD log, this is shown:
SysCode=10.1010.00000110
This appears to translate to Network 10, Site 6 in binary.

Is there is issue with how DSDPlus displays the network and site? Which network and site is correct, DSDPlus or Uniden?

 

[enosjones]

I know here in Utah we have the same problem, uniden says a site number while dsdplus has 1.1.7 or 3.3 or something that way, Questar dominion has a tier 3 system with the same issues

 

[slicerwizard]

Your scanners are lying to you. It's similar to the bogus talkgroup values on Motorola 3600 bps trunking systems, where all talkgroups are displayed as sixteen times their true values.

A SysCode of 10.1010.00000110 means large network model, network ID 11, and 00000110 has to be split into location area and site. Hytera's default split for large network models is 5/3, which would be 00000 (area 1) / 110 (site 7). Scanners don't even know that TIII location areas exist.

1010 has to be network ID 11 because large model network IDs range from 1 (0000) to 16 (1111).

 

[enCrypt]

Thats weird!
Maybe the scanners are counting the binary as it should be... 1010 is actually 10 not 11.

 

[slicerwizard]

Of course that's what they're doing. Doesn't make it right.

 

[cellphone]

@slicerwizard Thanks for the great information!

@JoeBearcat I'm tagging you to make sure you are aware of this issue.

 

[slicerwizard]

@JoeBearcat I'm tagging you to make sure you are aware of this issue.

It's far too late to change what the scanners display.

 

[cellphone]

It's far too late to change what the scanners display.

How so? Do you not believe this can be addressed with firmware?

 

[CanesFan95]

I remember how Uniden scanners would multiply Motorola TG IDs by 16 so that there was mathematical room to add status bits to the TG ID. Back then, we had the issue of when a TG was in any status, you'd miss the voice call because of how the Uniden would change the TG ID.

 

[slicerwizard]

How so? Do you not believe this can be addressed with firmware?

What would be the point of changing firmware in multiple scanner models and modifying every Tier III system in the RR database? What benefit would Uniden, RR and most users get?

 

[mikewazowski]

The Tier III systems in the database should already be correct and modifying the firmware should make those systems listenable without any user intervention. Currently the Misc System Info for most Tier III systems in the database should have this warning:

"To monitor this system with your Uniden scanner, go to the CH ID list. You can find that listing by clicking on the Site Name.

A channel menu will appear. Subtract one (-1) from the channel ID and divide by two ( /2) This will give you the Uniden LCN.

Modify your programming with the new values and it will be monitorable with your Uniden product."

I'm sure there are some Tier III systems in the database that are still following Uniden's incorrect but hopefully they'll get corrected eventually.