DSDPlus v2.98+ - DMR TIII Queensland Rail Fixed

[thewraith2008]

This release fixes a long term issue with DMR TIII Queensland Rail network.

You can revert your DSDPlus batch files to the default now.

The workaround was to remove -rv from VC DSDplus batch file or run VC DSDPlus from a separate folder.
This no longer needs to be done.

Happy listening.

 

[mtindor]

Can you describe in more detail what bug was existed in previous versions but has since been squashed in this release?

Mike

 

[philbert87]

I am intrigued with this as i have never had any issues decoding Queensland Rail, i will however test what your mentioning and see if there is any changes.

 

[thewraith2008]

If run DSDPlus/FMP24 with -rc -rv options set, QR DMR TIII (TAIT) network has problems with VC FMP24 locking on the frequency and VC DSDPlus looking like it's resetting.

I do have a video showing this but no where to put it long term.

Not all TIII networks do this.

To get this system working better the following had to be done:

Run DSDPlus.exe (x1) and FMP24 (x2) from CC folder
FMP CC
DSD CC (Synthesizing no audio)
FMP VC

Run DSDPlus.exe (x1) from different folder (VC folder)
DSD VC (Synthesizing all audio)

This seems to work a lot better, but some odd behavior in VC Channel Activity and VC Event Log window.

On a call, VC Channel Activity window cycles TgtAlias and SrcAlias with different values. Which seen to come from the following entries that can appear in VC Event Log window during a call:
- Group call
- Private call
- OVCM Private Call
- Emeg Private call
- Emeg Bcast Private call

Also when 2 separate calls are on a frequency that is not CC, that is on slot 1 & 2 at same time. Audio is heard at same time.
This does not seem to happen when 2 calls are on different frequencies.

Freq1 - Slot1 CALL \ both heard at same time
- Slot2 CALL /
Freq2 - Slot 1 CC
- Slot 2 call \ only one heard
Freq3 - Slot 1 call /
- Slot 2

Also if per call recording is on (-P), then an 'Over' is not one file but split over multiple files. Probably as a result of the above call type cycling.

As of v2.95 all above as been fixed. Hopefully this explains the details.

 

[mtindor]

Wraith,

Thanks for the very detailed explanation. I'm glad to hear that the issue is fixed for you in the latest version.

Mike

 

[thewraith2008]

Also of note is "Added fixes for NID prefix handling" mentioned in v2.98 notes which relates to "optional network ID prefix for iDAS and TIII systems" that was introduced in v2.84.

The files .control, .traffic, .tuned-traffic cannot be generated because of the special character ":" that is used for network ID prefix. You only see "TIII_xx" filenames been generated.

If you wish to use this feature stop using v2.84 as it's broken and use any version from v2.85.

The "Some changes made to audio AGC logic." May improve audio where some calls started low audio and slowly ramped up resulting in the first couple of seconds been hard to hear or missed.