DSDPlus DSD+ Fastlane updated - v2.256

[cg]

In each of the files is an outline of how to populate the fields. I don't know that software/sdr unit but t looks like you have Wide FM chosen, should be Narrow FM (NFM)
Here is what I am guessing based on your post. You need to determine the voice frequencies through FCC licensing or searching/monitoring. Once you see activity, search with a scanner or other SDR and hope you can match them up.

DSDPlus.NETWORKS
NEXEDGE96, 151, "(system/network name)"

DSDPlus.SITES
NEXEDGE96, 151, 1, "(site name)"

DSDPlus.FREQUENCIES
NEXEDGE96, 151, 1, 3, 161.9800, 0.0, 1; CC
NEXEDGE96, 151, 1, 4, 0.0, 0.0, 1;

edit: perhaps this thread may help you:

DSDPlus - DSDPlus 2.256 with SDRPlay RSP1.

Hello friends, Got DSDPlus 2.256 (Fastlane) ... With my RTL_SDR v3 Dongle it's working fine and decoding P25 Phase II. But, when i try to do it with my SDRPlay RSP1 i get the below message: --------------------------- FMPP 1.13 -i1 -o20001 ERROR --------------------------- Can't open...

forums.radioreference.com

 

[bheisner]

In each of the files is an outline of how to populate the fields. I don't know that software/sdr unit but t looks like you have Wide FM chosen, should be Narrow FM (NFM)
Here is what I am guessing based on your post. You need to determine the voice frequencies through FCC licensing or searching/monitoring. Once you see activity, search with a scanner or other SDR and hope you can match them up.

DSDPlus.NETWORKS
NEXEDGE96, 151, "(system/network name)"

DSDPlus.SITES
NEXEDGE96, 151, 1, "(site name)"

DSDPlus.FREQUENCIES
NEXEDGE96, 151, 1, 3, 161.9800, 0.0, 1; CC
NEXEDGE96, 151, 1, 4, 0.0, 0.0, 1;

edit: perhaps this thread may help you:

DSDPlus - DSDPlus 2.256 with SDRPlay RSP1.

Hello friends, Got DSDPlus 2.256 (Fastlane) ... With my RTL_SDR v3 Dongle it's working fine and decoding P25 Phase II. But, when i try to do it with my SDRPlay RSP1 i get the below message: --------------------------- FMPP 1.13 -i1 -o20001 ERROR --------------------------- Can't open...

forums.radioreference.com

I'm using SDR Console version 3 (with the SDRPlay RSP1 dongle) and the Virtual Audio Cable driver (vac415full) . I've always used Wide FM with an 8kHZ spread. This setup has worked fine with many versions of DSD+. The problem with the NEXEDGE CC surfaced when I upgraded to version 2.228. It has never worked right since that version.

All I would like to do is to obtain the same Site ID info and CC info that version 2.205 was returning.

DSD+ Version 2.205 returned this: Site: L151-1 RAN:1 NL:1.

Is it no longer possible to obtain this type of site info with versions of DSD+ greater that 2.205?

How would you determine the same Site info for NXDN site that has never been logged before with version 2.256?

 

[cg]

Fairly certain DSDPlus will not trunktrack with that setup, so simply use 2.205 to get whatever info you are looking for.
Good luck.

chris

 

[bheisner]

Fairly certain DSDPlus will not trunktrack with that setup, so simply use 2.205 to get whatever info you are looking for.
Good luck.

chris

Thanks Chris! I'm only using DSD+ to ID new NXDN and DMR systems. I'm using my SDS 100 to follow most of the new systems that I've recently discovered.

I'm just disappointed that the new versions of DSD+ have removed this feature. I guess I'll be running version 2.205 for while.

I'm actually shocked that there's no way to obtain the site IDs or CC info with new versions of DSD+. I'm hoping there's a setting in the new menu to turn this feature back on.

 

[cg]

There is a way. It works as designed if you use the programs that are made to work together. I monitor a 4 site NXDN96 trunked system and get all the talkgroups, RIDs, record the traffic, edit IDs, set priorities, etc. I use FMPx & DSDPlus.
However, you are cobbling together something that isn't designed to work together and it doesn't work 100%. Shouldn't be surprised when the SAE wrenches don't fit the metric nuts.

chris

 

[slicerwizard]

I'm just disappointed that the new versions of DSD+ have removed this feature. I guess I'll be running version 2.205 for while.

I'm actually shocked that there's no way to obtain the site IDs or CC info with new versions of DSD+. I'm hoping there's a setting in the new menu to turn this feature back on.

They haven't removed anything. You've done something, like disable NXDN decoding, auto polarity detection, or something else. Have you gone through the DSD+ menus and checked your settings?

 

[bheisner]

They haven't removed anything. You've done something, like disable NXDN decoding, auto polarity detection, or something else. Have you gone through the DSD+ menus and checked your settings?

I've checked my setting and NXDN9600 and NXDN4800 are both enabled.

I've attached the screenshots and startup logs for both 2.205 and 2.256.

I've also attached screenshots for the Decode and Control setting for 2.256

For Decode I have the following menu items checked:

Decode NXDN4800
Decode NXDN9600

For Control I have the following menu items checked:

Passive Digital Monitor
Group Voice Calls: Normal Handling
Private Voice Calls: Normal Handling
Data Calls: Normal Handling

The only systems that 2.256 are currently failing on are NXDN (both NXDN9600 and IDAS).

BTW, 2.256 is working perfectly with P25 and DMR (Cap+ Con+, TIII, etc) in my current setup.

I've been using the current setup for close to 3 years now. I've not had a single problem with NXDN until version 2.228.

P25 data loaded; 8 networks, 23 sites, 52 channels
0 frequency records loaded
14,825 radio records loaded
2518 group records loaded
0 site records loaded
0 network records loaded
22 site loader records loaded
NXDN4800 decoding enabled
NXDN9600 decoding enabled
DMR/MotoTRBO decoding enabled
P25 Phase 1 and Phase 2 decoding enabled
X2-TDMA decoding enabled
ProVoice decoding enabled

Mono audio decoding initiated; press Esc to exit...
Sync:+IDAS DATA ERR16
Sync:+IDAS DATA ERR13

 

[slicerwizard]

You've disabled DSD+'s noise filter and shaping filter. You're using WFM demodulation - I have no idea why one would choose to do that. SDR Console has settings for digital transmissions, but who knows if you're using them. You haven't shown us the audio waveform or eye pattern - that should show whether you're feeding DSD+ a good signal or garbage.

 

[bheisner]

You've disabled DSD+'s noise filter and shaping filter. You're using WFM demodulation - I have no idea why one would choose to do that. SDR Console has settings for digital transmissions, but who knows if you're using them. You haven't shown us the audio waveform or eye pattern - that should show whether you're feeding DSD+ a good signal or garbage.

It's working fine now after turning on Noise Filter and Shaping Filter. Thanks for the tip!

I'm guessing these were on by on by default with version 2.205 which didn't have the menu options that 2.228, 2.254 and 2.256 all have.

I've attached the screenshot of a NXDN IDAS control channel being decoded now with version 2.256.

 

[Mick]

You've disabled DSD+'s noise filter and shaping filter. You're using WFM demodulation - I have no idea why one would choose to do that. SDR Console has settings for digital transmissions, but who knows if you're using them. You haven't shown us the audio waveform or eye pattern - that should show whether you're feeding DSD+ a good signal or garbage.

Much gratitude slicerwizard! DSD+ is working perfectly for me now too once I enabled "noise filter" and "shaping filter." That is what was needed! Thanks bheisner for bringing up the question about this matter!

 

[mrc333777]

dsd team, maybe add an option to only show the non locked out in the current seen groups/radios windows.
i am in an area that is flooded with so much traffic and i have only my little town not locked out, yet all these other places are flooding the current seen windows. even setting the windows to max age 1 minute floods the windows. and a scroll bar for history in the event log would be nice.

 

[CanesFan95]

How do we get the password to extract from the .zip file? I've deleted my old e-mails so I no longer have it. Thanks.

 

[inside]

Use your latest passord what you get on email, with come from latest email sending DSD version.

 

[CanesFan95]

Welllll...that's the issue. I cleared out the del;eted items folder a while back since I had like 1,000 e-mails in there, my fault. So I don't have the last DSD+ e-mail.

 

[inside]

If delete then write email to DSDfasline from emaol where i got files. Hope he help you, he are normality man.

 

[bheisner]

You've disabled DSD+'s noise filter and shaping filter. You're using WFM demodulation - I have no idea why one would choose to do that. SDR Console has settings for digital transmissions, but who knows if you're using them. You haven't shown us the audio waveform or eye pattern - that should show whether you're feeding DSD+ a good signal or garbage.

Now I remember why I turned these 2 options off. For some strange reason the audio for P25 Phase 1 was very distorted when I had noise filter and shaping filter turned on. If I turn these 2 filters off, the audio for P25 Phase 1 is very clear. BTW, decoding of DMR and P25 Phase 1 & II CCs works perfectly with these 2 filters turned on or off. The only systems having decoding issues when these 2 filtering options are turned off are NXDN Systems.

 

[Kazzaw]

Now I remember why I turned these 2 options off. For some strange reason the audio for P25 Phase 1 was very distorted when I had noise filter and shaping filter turned on. If I turn these 2 filters off, the audio for P25 Phase 1 is very clear.

You must have something off with your receivers. I've not had an issue with noise filter or shaping filter settings, and I very regularly decode P25P1, P2, DMR and NXDN with no changes to settings

 

[slicerwizard]

You must have something off with your receivers. I've not had an issue with noise filter or shaping filter settings, and I very regularly decode P25P1, P2, DMR and NXDN with no changes to settings

Same situation here - no problems with leaving noise filter and shaping filter enabled for all digital protocols.

bheisner is using SDR Console and VAC; it's obviously doing something no bueno to the audio.

 

[bheisner]

Same situation here - no problems with leaving noise filter and shaping filter enabled for all digital protocols.

bheisner is using SDR Console and VAC; it's obviously doing something no bueno to the audio.

I'm thinking it's another setting that I have recently turn on or off. As mentioned earlier, the very same setup (SDR Conole + VAC) works great with version 2.205. Does anyone know what the default setting were for version 2.205? That version didn't have the menu options. I'm going to dump out the startup logs for 2.205 and 2.256 and compare them to see if I can spot the difference.

 

[mtindor]

I'm thinking it's another setting that I have recently turn on or off. As mentioned earlier, the very same setup (SDR Conole + VAC) works great with version 2.205. Does anyone know what the default setting were for version 2.205? That version didn't have the menu options. I'm going to dump out the startup logs for 2.205 and 2.256 and compare them to see if I can spot the difference.

Exit DSDPlus, rename your DSDPlus.bin file, and then restart DSDPlus. Your DSDPlus then would not be using any "stored" information and would be using all of the defaults (which includes having decoding enabled for all the typical protocols).

DSDPlus 2.x (all versions of 2.x) work just fine with SDRSharp and SDRConsole. Like Slicerwizard said, you must make sure that audio from SDR Console is making it through the virtual cable in the first place. I thought SDR Console had its own built-in version of virtual audio. Maybe I"m thinking of SDRuno. Anyway, this reallyy shouldn't be difficult to figure out. If you are running SDR Console + VAC, then you need to make sure that when you run DSDPlus it is referencing the proper audio line.

When I run DSDPlus, in the command prompt window I see the various audio inputs (yours will look different)

audio input device #1 = 'Internal Mic (IDT High Definiti'
audio input device #2 = 'Line 1 (Virtual Audio Cable)'
audio input device #3 = 'Line 3 (Virtual Audio Cable)'
audio input device #4 = 'Line 2 (Virtual Audio Cable)'
audio input device #5 = 'Jack Mic (IDT High Definition A'
audio input device #6 = 'Line 4 (Virtual Audio Cable)'

If my SDR Console audio is coming in over "Line 1 (Virtual Audio Cable)", then I need to tell DSDPlus to use audio input device #2.

dsdplus -i2 -o1

Mike