DSDPlus Differentiating T3 DMR Systems

[Kazzaw]

Hi,

I have read the instructions in the file but I'm still trying to make sense of how it works.

From the DSDPLUS file

"The next set of digits encodes the network ID. A zero value is used for NID 1,
so here, 1100 = 12 = NID 13."

I have 2 systems, both report Network of L1

Obviously, if I have 2 systems both under L1, DSDplus can't differentiate

I have Network A,
10.0000.00011110
and Network B
10.0001.00010101

I don't understand how the network ID encoding works... If anyone could give me some pointers, I'd really appreciate it.

 

[Kazzaw]

Any suggestions or what I should be reading? Or any T3 Databases that have the same issue? I read some more documentation last night about trying to get this work but I think its just fried my head more... I'll keep soldiering on

 

[slicerwizard]

What version of DSD+ are you using?

 

[Kazzaw]

The latest fastlane

 

[slicerwizard]

Not helpful.

 

[Kazzaw]

Sorry.

2.242

 

[slicerwizard]

I have 2 systems, both report Network of L1

Obviously, if I have 2 systems both under L1, DSDplus can't differentiate

I have Network A,
10.0000.00011110
and Network B
10.0001.00010101

I don't understand how the network ID encoding works... If anyone could give me some pointers, I'd really appreciate it.

Normally, I'd expect those networks to have IDs 1 and 2, but DSD+ is using ID 1 instead of 2 for the second one. Is it being reported as a Motorola (Capacity Max) system?

To differentiate TIII networks, you have to be using TCP linking with FMPA or FMPP or FMP24 and you have to choose (different) network ID prefixes, like 111 and 222, for each network and you have to add records to the .networks and .frequencies files.

 

[Kazzaw]

One is a Motorola system, the other is a Tait

 

[slicerwizard]

I guess that explains the different network ID syscodes being interpreted as the same network ID. Use prefixes to differentiate them.

 

[Kazzaw]

Thanks, I'll give that a whirl

 

[Kazzaw]

I'm still not getting something right.

Network A - Tait System

.frequencies file
TIII, 66 4.7, 16, 418.2875, 0.0, 0
TIII, 66, 4.7, 2, 418.1125, 0.0, 0
TIII, 66, 5.8, 24, 418.3875, 0.0, 0
TIII, 66, 5.8, 28, 418.4375, 0.0, 0
.networks file
TIII, 66, "Network A"

Network B - MOT System
.frequencies file
TIII, 67, 21, 109, 462.86250, 0.0, 0
TIII, 67, 21, 133, 463.162500, 0.0, 0
TIII, 67, 22, 139, 463.23750, 0.0, 0
TIII, 67, 22, 163, 463.53750, 0.0, 0
.networks file
TIII, 67, "Network B"

 

[slicerwizard]

Straight from the notes file:

Added optional network ID prefix for iDAS and TIII systems.

These systems do not use unique network IDs. When FMPA/FMP24 are TCP linked to DSD+,
iDAS or TIII systems that broadcast identical network IDs can be differentiated
by adding user-selected network ID prefixes to iDAS/TIII DSDPlus.frequencies records.

DSDPlus.frequencies examples:

TIII, 13, 1.1, 413, 450.0125, 0.0, 0 ; ACME Inc TIII; NID conflict
TIII, 13, 1.1, 117, 462.6000, 0.0, 0 ; Road Runner TIII; NID conflict

TIII, 1:13, 1.1, 413, 450.0125, 0.0, 0 ; ACME Inc TIII; NID conflict resolved
TIII, 2:13, 1.1, 117, 462.6000, 0.0, 0 ; Road Runner TIII; NID conflict resolved

 

[Kazzaw]

Thanks, thats sovled it. I think I was too busy looking into small things I kept overlooking what I actually needed to do.

 

[Kazzaw]

Okay, after a little more touching up today I think I have it, but still having the occasional issue where DSDPLUS will not grab the correct information unless programmed in.

I'm going to throw my files in here to see if anyone can pick up what it going on.

dsdplus.networks
TIII, 1:1, "Network A"
TIII, 1, "Network B".

dsdplus.sites
TIII, 1:1, 4.7, "Location A"
TIII, 1:1, 5.8, "Location B"
TIII, 1, 21, "Location A"
TIII, 1, 22, "Location B"
TIII, 1, 23, "Location C"

dsdplus.frequencies
TIII, 1:1, 4.7, 16, 418.28750, 0.0, 0
TIII, 1:1, 4.7, 2, 418.11250, 0.0, 0
TIII, 1:1, 5.8, 24, 418.38750, 0.0, 0
TIII, 1:1, 5.8, 28, 418.43750, 0.0, 0
TIII, 1, 21, 109, 462.86250, 0.0, 0
TIII, 1, 21, 133, 463.16250, 0.0, 0
TIII, 1, 22, 139, 463.23750, 0.0, 0
TIII, 1, 22, 163, 463.53750, 0.0, 0
TIII, 1, 23, 105, 462.81250, 0.0, 0
TIII, 1, 23, 129, 463.11250, 0.0, 0

With this, whenever I am programming around Network A and I stumble across a site that doesn't have entries in .frequencies (new site), its coming up as Network B

Likewise, I am seeing Network A show up when I am tuning around Network B - Both are very different frequency ranges.

Out of interest, I also have another network (lets call it C), which even through is a 2 network, sometimes get automatically listed as Network B yet no correlation (that I can see)

Is this how DSDPlus works, or am I doing something wrong.

Assistance appreciated!

 

[slicerwizard]

With this, whenever I am programming around Network A and I stumble across a site that doesn't have entries in .frequencies (new site), its coming up as Network B

Well, how would it know that it's a network A site? How would you know if you didn't already know?

 

[Kazzaw]

That makes sense

 

[TheButcher]

Deleted (mods please delete this post)...