DSDPlus area.site H1-X.X format site ID vs H2-YY format

[scottjpalmer]

What determines whether a TIII system uses an area.site H1-X.X format site ID vs a H2-YY (non decimal) style?

Is it vendor specific eg Motorola and say Hytera use one style, everyone else uses the other style? Or is it related to network size huge, large, tiny etc? Or is it configurable from system to system by whoever is configuring it?

Thanks.

 

[lwvmobile]

Here you go, the cause of mass confusion in DMR T3, the Location Area (DMRLA B***S***, as I personally call it). Its a subdivision of the SITE value in SYSCode which IS NOT broadcast over the air, and is only programmed into radios.



Also of note, CapMax systems do not use the Location Area subdivision.

As far as H1 vs H2, its probably to avoid a site id of 0, which can and does occur.

 

[thewraith2008]

It is vendor specific.

The SLCO in some cases can indicate which system is been used. (and how the sitecode bits are interpreted)

1. The standard opcode values for TIII are 2,3 (*)
2. Special uses by vendors can use opcodes 4-15 (e.g. XPT = 8, CON+ = 9, 10 - CAP+ = 15) and may use non-standard sitecodes
3. 0,1 is used for conventional BS (**) - No sitecodes here

Real world DMR has many variations to how it can be implemented by vendor.
The standards are only going to get you so far.

*
Some TIII only use opcode 2 for both CC/VC channels.
Hytera only uses 2 for CC where it's traffic channels look like a conventional BS by using 0,1 opcodes.
I think Motorola CapMAX and newer TAIT "ACCESS?" are the only ones I've seen that uses both 2(CC) and 3(VC) on there channels.


**
As noted, Hytera can use these on it's traffic channels. No sitecodes here.
Hybrid (Motorola?) conventional BS (with csbko usage - i.e TIII) also seen. No sitecodes here.
CapMAX uses SLCO:2 but is further identified by seeing the CSBKO:25 FID:16 PDU (C_ALOHA).
This is only valid on the CC as VC does not carry the C_ALOHA so you need to keep track of that when switching to a traffic channel. This is why DSD+ cannot identify (sitecode) of a CapMAX traffic channel if you just tune to it.
You'll notice DSD+ decode the sitecode using two different ways at start. (H1-X.X and H2-YY)

The sitecode (14,16 bits) is found in a couple of PDUs and how these bits are truely decoded/identified outside of a "standard" TIII system, generally requires insider knowledge on what the sitecodes really are as configured in CPS.
How DSD+ does it is generally considered 'right', but it may not be 100% and it's the best theory going at the moment.