DSDPlus DSD+ two dongle decoding issue

[W4KRR]

I am using DSD+ Fastlane, using two Airspy receivers, one for control channel, one for voice. Here is the .BAT file I use:

start FMPA -i1 -o20003 -rc -f774.90625 -_1 -wsl15.43
start DSDPlus -i20003 -rc -O NUL -wes400.800
start FMPA -i2 -rv -o20002 -wsl240.43
start DSDPlus -rv -i20002 -O NUL -wes400.800

This setup works just fine on P-25 phase1 and phase 2; DMR Connect Plus systems; NXDN48 trunking systems. I just change the control channel to the system I want to monitor.
Except, when I try to use this same .bat file on a Tier III DMR system, it doesn't work. The only way it will work is if I go into the DSD+ CC Event Log window and change the role from "CC Monitor" to "Combined CC/VC Monitor". It then will work, but using only a single dongle.

Any ideas on why this might be?

This is what I see if I try to use the above .bat file on a DMR Tier III system:
Just scrolls this info over and over; CC activity doesn't populate and no audio.

 

[mwjones]

I am using DSD+ Fastlane, using two Airspy receivers, one for control channel, one for voice. Here is the .BAT file I use:

start FMPA -i1 -o20003 -rc -f774.90625 -_1 -wsl15.43
start DSDPlus -i20003 -rc -O NUL -wes400.800
start FMPA -i2 -rv -o20002 -wsl240.43
start DSDPlus -rv -i20002 -O NUL -wes400.800

This setup works just fine on P-25 phase1 and phase 2; DMR Connect Plus systems; NXDN48 trunking systems. I just change the control channel to the system I want to monitor.
Except, when I try to use this same .bat file on a Tier III DMR system, it doesn't work. The only way it will work is if I go into the DSD+ CC Event Log window and change the role from "CC Monitor" to "Combined CC/VC Monitor". It then will work, but using only a single dongle.

Any ideas on why this might be?

This is what I see if I try to use the above .bat file on a DMR Tier III system:
Just scrolls this info over and over; CC activity doesn't populate and no audio.
View attachment 142752

I have monitored several Tier III "Capacity Max" systems with a nearly identical configuration. You've got a mis-match with your Frequencies and Sites file (and also what is in RRDB) versus what is going over the air. This results in DSD Saying "this frequency is this site" whereas over the air is receiving the repeater broadcasting "no I'm actually this site" and thus the ping-pong back and forth between the two.

Change the Site ID from 1.2 to 0.2, that likely will fix the problem you're seeing.

So, for example, this would be my DSDPlus.sites file for "Broward County Local Government" (The system ID I use consists of the last 3 digits of the URL for the system, and the spacing is intentional for ease of reading):

TIII, 234:1, 0.1, "Fort Lauderdale"
TIII, 234:1, 0.2, "Coconut Creek"
TIII, 234:1, 0.3, "Pembroke Park"
TIII, 234:1, 0.4, "Sunrise"
TIII, 234:1, 0.5, "Miramar"

Likewise, here would be my DSDPlus.frequencies for the Coconut Creek site:

TIII, 234:1, 0.2, 361, 453.23750, 458.23750, 0, 1
TIII, 234:1, 0.2, 371, 453.30000, 458.30000, 0, 1
TIII, 234:1, 0.2, 391, 453.42500, 458.42500, 0, 1
TIII, 234:1, 0.2, 413, 453.56250, 458.56250, 0, 1
TIII, 234:1, 0.2, 419, 453.60000, 458.60000, 0, 1
TIII, 234:1, 0.2, 1531, 460.55000, 465.55000, 0, 1

Once you've got those validated and working, be sure to submit the corrections to RRDB to help others.

 

[W4KRR]

I changed the site numbers from 1.x to 0.x, and now it's working. Same thing with the frequencies file; changed the sites from 1.x to 0.x.

But DSD reports the site numbers are 1.x and not 0.x.

 

[mwjones]

I changed the site numbers from 1.x to 0.x, and now it's working. Same thing with the frequencies file; changed the sites from 1.x to 0.x.

But DSD reports the site numbers are 1.x and not 0.x.

I suspect you're reading the System ID in there. Where it says, "Current Site: S1-2" is actually System "S1", Site 0.2. If it was region 1 (the part of the site before the period), it would read "S1-1.2". The line where you're seeing that in the Ping-Pong is what is being populated from your DSDPlus files, not over the air.

Likewise, what is in RRDB is incorrectly showing the Region as 1 (along with the system type being a "DMR Tier III Standard", instead of "DMR Tier III Capacity Max", but that's minor compared to the Region issue).

Likewise, every Capacity Max system I've seen is using Region 0, so this would be consistent with that observation. Unfortunately, I'm not in range of a Capacity Max system from my base station so I can't screen grab an example at the moment.

 

[W4KRR]

Here is what this one is reporting:

 

[mwjones]

Here is what this one is reporting:

View attachment 142754

Correct, Site: S1-1 is System ID: S1, Site 0.1, while the neighbors are Sites 0.2, 0.3, 0.4 and 0.5. Keep in mind Motorola's implementation of Tier III (what they market as "Capacity Max" has some proprietary bits, so its behavior is a bit different than a typical Tier III system. This includes the format of the site ID's in the Over the Air transmission. That's why the region will almost always be 0.

Here's what a normal Tier III system (in this case from Hytera) would look like (which I am in range of):

You can see the difference in the format of the Site number.