DSDPlus 1p101 Trunking Help

[kh6sz]

I've just downloaded the new public version of DSDPlus, which they say will track trunking. I'm trying to set it up for the Harrison County Public Service Network here in Mississippi. I'm trying to to this without having to use Unitrunker. I wonder if someone can take a look at my bat files and my DSDPlus.frequencies file to see if they see something I got wrong. The updated dsdplus program says you can do it without using virtual audio cable or VB-Cable, so that's what I'm trying to do. I'm using 2 SDR USB dongles.

CC.Bat
DSDPlus -rc -i20001 -v3 -wsl400.2 -wss100.200 -wel0.1 -wcl0.445 -wes400.520 >>CC.log

FMP-CC.Bat
FMP -i1 -o20001 -P55.0 -f851.400

VC.Bat
DSDPlus -rv -Pwav -i20002 -v3 -wsl400.210 -wss100.200 -wel172.522 -wcl528.0 >>VC.log

FMP-VC.Bat
FMP -i2 -o20002 -P55.0 -rv


My DSDPlus.frequencies

; DSD+ frequency file
;
; you can edit this file while DSD+ is running
;
; line format:
;
; protocol, networkID, siteNumber, OTAchannelNumber, TXfrequency, RXfrequency, sortOrder
;
; for TIII, siteNumber format = area.site
;
;
; use site number = 0 for network-wide definition
;
; use 0.0 for unknown frequencies
;
; use sort order = 0 to sort by OTA channel number
;
;
; protocols:
;
; D-Star
; IDAS
; NEXEDGE48
; NEXEDGE96
; dPMR
; DMR
; Cap+
; Con+
; TIII
; P25
; ProVoice

ProVoice, 977, 1, 1, 851.15000, 851.15000, 0
ProVoice, 977, 1, 2, 851.40000, 851.40000, 0
ProVoice, 977, 1, 3, 851.67500, 851.67500, 0
ProVoice, 977, 1, 4, 851.95000, 851.95000, 0
ProVoice, 977, 1, 5, 852.20000, 852.20000, 0
ProVoice, 977, 1, 6, 852.56250, 852.56250, 0
ProVoice, 977, 1, 7, 852.85000, 852.85000, 0
ProVoice, 977, 1, 8, 853.10000, 853.10000, 0
ProVoice, 977, 1, 9, 853.51250, 853.51250, 0
ProVoice, 977, 1, 10, 853.76250, 853.76250, 0
ProVoice, 977, 1, 11, 851.81250, 851.81250, 0
ProVoice, 977, 1, 12, 852.27500, 852.27500, 0
ProVoice, 977, 1, 13, 853.38750, 853.38750, 0
ProVoice, 977, 1, 14, 853.65000, 853.65000, 0
ProVoice, 977, 1, 15, 852.33750, 852.33750, 0
ProVoice, 977, 1, 16, 852.78750, 852.78750, 0
ProVoice, 977, 1, 17, 853.26250, 853.26250, 0
ProVoice, 977, 1, 18, 851.88750, 851.88750, 0
ProVoice, 977, 1, 19, 852.67500, 852.67500, 0
ProVoice, 977, 1, 20, 851.21250, 851.21250, 0

Here is also my CC.log and VC.log files.

CC.Log

DSD+ 1.101pt
Program role is control/rest channel decoder
Source audio waveform window origin set to (400,2)
Source audio waveform window dimensions set to 100x200
Event log window origin set to (0,1)
Channel window origin set to (0,445)
Event log window dimensions set to 400x520
Appending synthesized audio to file 'CC-DSDPlus.wav'
20 frequency records loaded
0 radio records loaded
0 group records loaded
0 site records loaded
1 network record loaded


Initiating TCP connection to 127.0.0.1:20001...
Connected to 127.0.0.1:20001
audio output device #1 = 'Speakers (Realtek High Definiti'
audio output device #2 = 'LCD TV-4 (NVIDIA High Definitio'
audio output device #3 = 'CABLE-A Input (VB-Audio Cable A'
audio output device #4 = 'Realtek Digital Output (Realtek'
audio output device #5 = 'CABLE-B Input (VB-Audio Cable B'
audio output device #6 = 'CABLE Input (VB-Audio Virtual C'

audio output device #1 (Speakers (Realtek High Definiti) initialized

D-STAR decoding enabled
NXDN4800 decoding enabled
NXDN9600 decoding enabled
DMR/MotoTRBO decoding enabled
P25 Phase 1 decoding enabled
X2-TDMA decoding enabled
ProVoice decoding enabled
TCP cleanup

*partial* decoding score = 0



VC.Log

DSD+ 1.101pt
Program role is voice channel decoder; audio modes set to mono
Assuming FMP is signal source; auto polarity detect is disabled
Writing synthesized audio to per-call wav files
Source audio waveform window origin set to (400,210)
Source audio waveform window dimensions set to 100x200
Event log window origin set to (172,522)
Channel window origin set to (528,0)
Appending synthesized audio to file 'VC-DSDPlus.wav'
20 frequency records loaded
0 radio records loaded
0 group records loaded
0 site records loaded
1 network record loaded


Initiating TCP connection to 127.0.0.1:20002...
Connected to 127.0.0.1:20002
audio output device #1 = 'Speakers (Realtek High Definiti'
audio output device #2 = 'LCD TV-4 (NVIDIA High Definitio'
audio output device #3 = 'CABLE-A Input (VB-Audio Cable A'
audio output device #4 = 'Realtek Digital Output (Realtek'
audio output device #5 = 'CABLE-B Input (VB-Audio Cable B'
audio output device #6 = 'CABLE Input (VB-Audio Virtual C'

audio output device #1 (Speakers (Realtek High Definiti) initialized

D-STAR decoding enabled
NXDN4800 decoding enabled
NXDN9600 decoding enabled
DMR/MotoTRBO decoding enabled
P25 Phase 1 decoding enabled
X2-TDMA decoding enabled
ProVoice decoding enabled
TCP cleanup

*partial* decoding score = 0


Thanks in advance.

 

[natedawg1604]

So, what type of computer are you running? Are you using virtualization software?

AFAIK, DSD+ does NOT support EDACS (no matter what version you have). Rather, it ONLY supports decoding digital audio from provoice talkgroups, but the Provoice audio stream must be piped from another program.

I'm not sure why you want to avoid using Unitrunker, it works great for monitoring EDACS systems. You can easily monitor Provoice talkgroups by setting the output of Unitrunker's voice receiver to a Virtual Cable piped to DSD+. Notably, with this setup, DSD+ ONLY decodes the provoice audio, it doesn't display/log any information whatsoever.

Edit: When I said "it doesn't display/log any information", that was somewhat inaccurate: It does show some signal decoding info (i.e. if you have a lot of errors) and timestamps, but that's it. It doesn't show you any TGID', RID's etc., that is all displayed/logged in Unitrunker.

 

[kh6sz]

So, what type of computer are you running? Are you using virtualization software?

AFAIK, DSD+ does NOT support EDACS (no matter what version you have). Rather, it ONLY supports decoding digital audio from provoice talkgroups, but the Provoice audio stream must be piped from another program.

I'm not sure why you want to avoid using Unitrunker, it works great for monitoring EDACS systems. You can easily monitor Provoice talkgroups by setting the output of Unitrunker's voice receiver to a Virtual Cable piped to DSD+. Notably, with this setup, DSD+ ONLY decodes the provoice audio, it doesn't display/log any information whatsoever.

Thank you for the info natedawg1604.
I guess I assumed that with the new version that came out that said it did trunking, that it would work since it does work with unitrunker. After looking in the trunking text file, it reads:

NEXEDGE, Con+ and TIII (Hytera) trunking are fully supported
Cap+ trunking is less supported (no rest channel following)

I wonder if a future version of DSD+ will do EDACS decoding all by itself. Does the fast lane versions do it?

I do have the EDACS system programmed into unitrunker and use dsd+ to decode it and it works very well, I was just experimenting to see if dsd+ did it alone. I guess not. Thanks again for the reply.

 

[LosPirate]

Full support of EDACS trunking would be very nice. Are there any plans to include it in future versions?

I would like to avoid Unitrunker too. Mainly because in this setup, I am not able to record decoded audio with all details necessary for offline monitoring. All I can get from DSD+ is an audio stream in one file. Per-call recording is exactly what I need, but it require trunking support in DSD+.

One more question. Is there a plan to support SDRplay?

 

[KD8DVR]

Yeah...well... Dsd+ doesn't and never will support edacs. Why? Because EDACS is analog.

Dsd+ is used to decode digital.

Unitrunker has a companion program that will record for you. You could also use a virtual audio cable to pipe the unitrunker output to another recording program, such as Scanner Recorder (scanrec). Scanrec is evidently difficult to find these days. Fortunately, it made the cut for my archive dvd series.

Sent from my LG-D631 using Tapatalk

 

[LosPirate]

Agree. Plain EDACS is analog, but it can be expanded with digital ProVoice. If DSD+ is able to decode ProVoice, which is used in EDACS only, why not support EDACS trunking to monitor whole system, instead just decode voice channels?

Regarding the Unitrunker, it is not so simple in my case. My gear is RTL-SDR and SDRplay. The second one is not compatible with Unitrunker so my setup looks as follows: Unitrunker with RTL-SDR is used to monitor CC only and activity in the system. With it I can exclude groups or users from monitoring, assign priorities, etc. SDRplay with SDR# and separate antenna is used to feed DSD+ with voice data. Applications are connected with "SDR# Unitrunker plugin", where Unitrunker works as a controller for SDR#. At the end of this line, DSD+ act as digital voice decoder only. To be honest, I don't see any option to record decoded audio (available form DSD+ only) with transmission details (groups, RID's, time, etc.) which are available only in Unitrunker or correlate the data form those two sources.

I'd love to get rid of this mess and get one application to monitor the system. My dream is DSD+ with full EDACS and SDRplay support.

 

[Forts]

DSD+ doesn't currently trunk P25 systems either... If anything was to be added I'd think that would be much higher up on the things to do list vs a trunking format that's on it's way out.

 

[R0am3r]

Using only one RTL-SDR, I have the DSD+ 1.101 (public release) software decoding the Rome NY NXDN system control channel. Unfortunately I cannot (yet) decode the audio channels because my HackRF isn't supported and the two new RTL-SDR sticks I just received have a MCX antenna connector. I need to wait a few more days for MCX adapters to arrive so I can hook up a second RTL-SDR stick and decode the audio channels. So close...

Thanks to the authors of this amazing tool. Great software!

 

[slicerwizard]

Can't you use the HackRF for the control channel side and the RTL SDR dongle for the voice side?

 

[R0am3r]

I read in one of the documents (or here in this forum) that Airspy was supported for the control channel side. I don't recall seeing anything about the HackRF. Hmmm.

 

[slicerwizard]

You can use anything for the control channel side. Whatever it is, just tune it to the control channel...

 

[ak4fn]

Unitrunker has a companion program that will record for you. You could also use a virtual audio cable to pipe the unitrunker output to another recording program, such as Scanner Recorder (scanrec). Scanrec is evidently difficult to find these days. Fortunately, it made the cut for my archive dvd series.

Trunking Recorder - Recording audio from trunked radio systems monitored by Unitrunker

 

[dave3825]

My DSDPlus.frequencies

; DSD+ frequency file
;
; you can edit this file while DSD+ is running
;
; line format:
;
; protocol, networkID, siteNumber, OTAchannelNumber, TXfrequency, RXfrequency, sortOrder
;
; for TIII, siteNumber format = area.site
;
;
; use site number = 0 for network-wide definition
;
; use 0.0 for unknown frequencies
;
; use sort order = 0 to sort by OTA channel number
;
;
; protocols:
;
; D-Star
; IDAS
; NEXEDGE48
; NEXEDGE96
; dPMR
; DMR
; Cap+
; Con+
; TIII
; P25
; ProVoice

ProVoice, 977, 1, 1, 851.15000, 851.15000, 0
ProVoice, 977, 1, 2, 851.40000, 851.40000, 0
ProVoice, 977, 1, 3, 851.67500, 851.67500, 0
ProVoice, 977, 1, 4, 851.95000, 851.95000, 0
ProVoice, 977, 1, 5, 852.20000, 852.20000, 0
ProVoice, 977, 1, 6, 852.56250, 852.56250, 0
ProVoice, 977, 1, 7, 852.85000, 852.85000, 0
ProVoice, 977, 1, 8, 853.10000, 853.10000, 0
ProVoice, 977, 1, 9, 853.51250, 853.51250, 0
ProVoice, 977, 1, 10, 853.76250, 853.76250, 0
ProVoice, 977, 1, 11, 851.81250, 851.81250, 0
ProVoice, 977, 1, 12, 852.27500, 852.27500, 0
ProVoice, 977, 1, 13, 853.38750, 853.38750, 0
ProVoice, 977, 1, 14, 853.65000, 853.65000, 0
ProVoice, 977, 1, 15, 852.33750, 852.33750, 0
ProVoice, 977, 1, 16, 852.78750, 852.78750, 0
ProVoice, 977, 1, 17, 853.26250, 853.26250, 0
ProVoice, 977, 1, 18, 851.88750, 851.88750, 0
ProVoice, 977, 1, 19, 852.67500, 852.67500, 0
ProVoice, 977, 1, 20, 851.21250, 851.21250, 0

.

Where does this info come from?

I would like to run the prog on a Motorola Type II SmartZone Analog and APCO-25 Common Air Interface

Suffolk County Trunking System, Suffolk County, New York - Scanner Frequencies

Will it work?


Will it work with this?

 

[kh6sz]

Where does this info come from?

I would like to run the prog on a Motorola Type II SmartZone Analog and APCO-25 Common Air Interface

Suffolk County Trunking System, Suffolk County, New York - Scanner Frequencies

Will it work?


Will it work with this?

The info came from the DSD+ 1p101 frequencies file when I was experimenting, not knowing that DSD+ would not trunk EDACS Provoice.

 

[dave3825]

The info came from the DSD+ 1p101 frequencies file when I was experimenting, not knowing that DSD+ would not trunk EDACS Provoice.

I understand that. I want to monitor the system mentioned above. I was asking where the following is obtained from

protocol, networkID, siteNumber, OTAchannelNumber, TXfrequency, RXfrequency, sortOrder

Note: In order for trunk voice following to work, your DSDPlus.frequencies
file *must* contain correct channel information for the systems / sites
you wish to monitor. If you have not done this, DSD+ cannot translate
the over-the-air channel numbers into RF channel frequencies. If you
do not provide correct information, DSD+ will steer FMP to incorrect
voice frequencies or do no tuning at all.

 

[slicerwizard]

Where does this info come from?

I would like to run the prog on a Motorola Type II SmartZone Analog and APCO-25 Common Air Interface

Suffolk County Trunking System, Suffolk County, New York - Scanner Frequencies

Will it work?


Will it work with this?

I'm assuming you'll be using RTL SDR dongles.

To monitor a mixed mode Type II system, use TRUNK88 or Unitrunker along with DSD+.

The frequency information comes from the control channel. You just have to select the correct bandplan in TRUNK88 (and I assume the same is true for Unitrunker)

Talkgroup names can be loaded into TRUNK88 using the RR2T88 program. With Unitrunker, you need to be an RR premium subscriber or you could type them in manually. To display talkgroup names in DSD+, it's manual typing time...

 

[dave3825]

I'm assuming you'll be using RTL SDR dongles.

To monitor a mixed mode Type II system, use TRUNK88 or Unitrunker along with DSD+.

The frequency information comes from the control channel. You just have to select the correct bandplan in TRUNK88 (and I assume the same is true for Unitrunker)

Talkgroup names can be loaded into TRUNK88 using the RR2T88 program. With Unitrunker, you need to be an RR premium subscriber or you could type them in manually. To display talkgroup names in DSD+, it's manual typing time...

I was under the impression that the latest release of dsd plus would follow trunking systems . With that said, I figured since the system was a mixed mode system, it would only decode the digital transmissions with out the need for any other programs other than fmp and dsd plus.

And yes, I am using 2 dongles..

Currently I can use unitrunker with dsd and it all works.

Also, I can use sdsharp and dsd because there seem to be dedicated freqs that the system uses for digital. The system only has 8 digital talkgroups.

 

[R0am3r]

Ok, I am stuck. I have successfully decoded the local (Rome NY) NXDN 4800 control channel using FMP-CC.bat and CC.bat. When remove the FMP tuner and use the SDR# application, I cannot decode the audio. What is the trick to make DSDPlus decode the audio from another application? FMP does this via an audio TCP port 20001. Is there such a thing as this option in SDR# or am I on the wrong track?

Here is my batch file:
DSDPlus -rc -fn -v3 -wsl400.2 -wss100.200 -wel0.1 -wcl0.445 -wes400.520 >>CC.log

Please note that SDRSharp sees the control channel signal and it sounds (to my ears) like a normal CC signal. Any help/insight with this matter is very much appreciated.

 

[slicerwizard]

I was under the impression that the latest release of dsd plus would follow trunking systems

The DSD+ Trunking.txt file says it follows NXDN NEXEDGE and DMR Connect Plus and Tier III trunking systems. Nothing mentioned about other system types.

Ok, I am stuck. I have successfully decoded the local (Rome NY) NXDN 4800 control channel using FMP-CC.bat and CC.bat. When remove the FMP tuner and use the SDR# application, I cannot decode the audio. What is the trick to make DSDPlus decode the audio from another application? FMP does this via an audio TCP port 20001. Is there such a thing as this option in SDR# or am I on the wrong track?

Here is my batch file:
DSDPlus -rc -fn -v3 -wsl400.2 -wss100.200 -wel0.1 -wcl0.445 -wes400.520 >>CC.log

Please note that SDRSharp sees the control channel signal and it sounds (to my ears) like a normal CC signal. Any help/insight with this matter is very much appreciated.

Download and install VB-Cable.

Tell SDR# to send the audio to VB-Cable.

Tell DSD+ to listen to VB-Cable (you probably need to add -i2 to your batch file). DSD+ lists the audio devices and their numbers at startup.

 

[R0am3r]

Download and install VB-Cable.

Tell SDR# to send the audio to VB-Cable.

Tell DSD+ to listen to VB-Cable (you probably need to add -i2 to your batch file). DSD+ lists the audio devices and their numbers at startup.

Works perfect! Slicer - Thanks for the insight. I am now decoding the Control Channel from SDR#. Onto the next step...