DSDPlus TIII issue with 2.457.

[ScanRite]

2.457 no longer reports/tracks the below system. Below is a screenshot using .395.
It shows the TIII (MOT) current system as H1-4.4, along with its various neighbors with .395.
Yet when loading with .457, it reports as H0 and no variations in the .frequencies file using H0, H1 or the various sites will work. For a brief moment, .457 does show H1-4.4, but then immediately switches to H0-27. Very odd.

 

[mwjones]

There was extensive changes to the TIII implementation in 2.457, which requires changes to your configuration files. For more details, read the release notes (and the subsequent thread)

DSDPlus - DSD+ 2.457 Available

DSD+ 2.457 All "TIII" support has been excised from DSD+. The program now red-flags any data file entry that has "TIII" as the protocol string. No DMR system/site will be reported as "TIII". When a TIII site is monitored, DSD+ will make a determination as to whether a...

forums.radioreference.com

 

[dave3825]

Did you read the recent changes in the notes.txt and edit your files to reflect all the TIII changes?

 

[ScanRite]

Yes, the necessary changes were made. This doesn't reflect that the system was once identified has H1-4.4 and is now showing H0. Completely different issue. It's, so far, just this one system.

Further, if the system is changed to H0 in the frequencies file, if it was in fact correct, causes DSD+ to go into an infinite loop of reading the .frequencies file.

 

[mwjones]

You indicated that the system is reporting as TIII (MOT) - that's a Motorola Capacity Max, which should be entered in the updated config files as TIIInonStd (but the initial load looks like it's trying to come up as a TIIIStd).

Also, are you using two SDR's (one for CC and one for VC)? There's a bug some of us have encountered that it goes into a loop when decoding a TIII site in that mode, switching to single SDR mode stops the loop. Awaiting updates on a fix for that issue from the developers.

 

[ScanRite]

You indicated that the system is reporting as TIII (MOT) - that's a Motorola Capacity Max, which should be entered in the updated config files as TIIInonStd (but the initial load looks like it's trying to come up as a TIIIStd).

Also, are you using two SDR's (one for CC and one for VC)? There's a bug some of us have encountered that it goes into a loop when decoding a TIII site in that mode, switching to single SDR mode stops the loop. Awaiting updates on a fix for that issue from the developers.

All data has been entered as TIIInonStd, so should be correct. Just one SDR. It only goes into the loop when the .frequencies file is set to H0 (as status window is showing) instead of H1 (which it should be). I don't believe 0 is a valid number for this.

 

[mwjones]

All data has been entered as TIIInonStd, so should be correct. Just one SDR. It only goes into the loop when the .frequencies file is set to H0 (as status window is showing) instead of H1 (which it should be). I don't believe 0 is a valid number for this.

Can you share the relevant lines from .networks, .sites and .frequencies files?

 

[mtindor]

Yes, the necessary changes were made. This doesn't reflect that the system was once identified has H1-4.4 and is now showing H0. Completely different issue. It's, so far, just this one system.

Further, if the system is changed to H0 in the frequencies file, if it was in fact correct, causes DSD+ to go into an infinite loop of reading the .frequencies file

Do this:
1. Park on the control channel in question
2. In the DSDPlus menu go to INPUT --> Start Source Audio Recording
3. Let it record for one minute
4. Go to INPUT --> Stop Source Audio recording

The DSDPLus Event window will tell you the name of the raw audio file that was recorded. It will be in your folder where all of your DSDPlus stuff is. Grab that file and either upload it to some free file upload facility and provide a link where we can download it, or email it to my username @gmail.com . It would be most helpful for all of us who are trying to help you if we are able to see what the control channel is reporting ourselves. And we can do that if you capture raw audio and make it available to us.

mike

 

[ScanRite]

Do this:
1. Park on the control channel in question
2. In the DSDPlus menu go to INPUT --> Start Source Audio Recording
3. Let it record for one minute
4. Go to INPUT --> Stop Source Audio recording

The DSDPLus Event window will tell you the name of the raw audio file that was recorded. It will be in your folder where all of your DSDPlus stuff is. Grab that file and either upload it to some free file upload facility and provide a link where we can download it, or email it to my username @gmail.com . It would be most helpful for all of us who are trying to help you if we are able to see what the control channel is reporting ourselves. And we can do that if you capture raw audio and make it available to us.

mike

Will do. Thanks

 

[kd7jfv]

Good afternoon, Duane started this thread to help me figure this out. I'll be sending you the raw audio files. Thanks for your quick response!

Ben

 

[mtindor]

Good afternoon, Duane started this thread to help me figure this out. I'll be sending you the raw audio files. Thanks for your quick response!

Ben

I know that the DSDPlus Author is Anti Network ID 0 / Site ID 0 -- meaning he says such network IDs and site IDs simply don't exist. So, if plain vanilla DSDPLus FL of the latest version (with empty networks, sites, frequencies files) is reporting a CAPMAX site as H0, he's gonna have to have a look at the raw audio.

 

[mtindor]

Good afternoon, Duane started this thread to help me figure this out. I'll be sending you the raw audio files. Thanks for your quick response!

Ben

This is the first that we've seen a CAPMAX system with a Network ID of 0. It used to be believed that no DMR TIII system could have a network ID of 0. But the system is transmitting stuff with a Motorola MFID, so it is CAPMAX. You would want to use one of the two methods listed below in your DSDPlus.* files. If it were me I'd use TIIInonStd,H0 with simple site numbers (like 27). But it's your choice how you want to handle it. CAPMAX systems don't have Area IDs.

Either use:
TIIInonStd,H0 and simple numbers
OR
TIIIStd,H1 and sites with decimals (AreaID.SiteID)

DSDPlus.networks
TIIInonStd,H0,"Day Wireless"

DSDPlus.sites
TIIInonStd,H0,27,"Site 27 (4.4)"

DSDPlus.frequencies
TIIInonStd,H0,27,255,451.575,456.575,1
TIIInonStd,H0,27,1847,461.525,466.525,2
TIIInonStd,H0,27,2183,463.625,468.625,3
TIIInonStd,H0,27,2391,464.925,469.925,4

DSDPlus.networks
TIIIStd,H1,"Day Wireless"

DSDPlus.sites
TIIIStd,H1,4.4,"Site 4.4 (27)"

DSDPlus.frequencies
TIIIStd,H1,4.4,255,451.575,456.575,1
TIIIStd,H1,4.4,1847,461.525,466.525,2
TIIIStd,H1,4.4,2183,463.625,468.625,3
TIIIStd,H1,4.4,2391,464.925,469.925,4

And of course you would also have to update all of the associated DSDPlus.groups and DSDPlus.radios entries that you have in those files so that they align with whatever method you choose.

 

[Marco192]

I had a similar problem were DSD+ could not identify a known T3 network.
Try to change the network ID just in .networks file ... change it to just 0 (not H0, but just 0). Leave everything else as it is with H0
That helped in my case

 

[mtindor]

I had a similar problem were DSD+ could not identify a known T3 network.
Try to change the network ID just in .networks file ... change it to just 0 (not H0, but just 0). Leave everything else as it is with H0
That helped in my case

You were obviously using an older version of FastLane. The latest version requires that you include the Network Model (T/S/L/H) in the files, such as H0 or S1.

 

[Marco192]

You were obviously using an older version of FastLane. The latest version requires that you include the Network Model (T/S/L/H) in the files, such as H0 or S1.

no, the current version. network association breaks down when I use H (T/S/L/H)

 

[kd7jfv]

The fix for the "loop" was to change the control channel from CC Monitor to Combined VC CC monitor. Single dongle...

 

[mtindor]

no, the current version. network association breaks down when I use H (T/S/L/H)

Using the latest version (2p457), just setting a Network ID of 0 (or any number) without the Network model results in a warning in the Event window / Event log -- because you need to include the Network Model (T/S/L/H). This is only for TIII systems.

As @kd7jfv pointed out, and others before him, there is an issue in 2p457 whereby if you are running Passive Digital Monitor or CC monitoring mode, you may see the continous scrolling. And the workaround (until DSDPlus is fixed) is to run one dongle in Combined CC/VC mode.