DSD-NEO help

[Marco192]

Hi guys,
first of all thanks to everyone working on this and other projects that allow all of us to have these decoding programs!

Hopefully someone can help me with an issue I noticed when testing dsd-neo:
when trying to listen to a DMR trunking network dsd-neo will not stay on the control channel. It finds the channel in the csv file, it decodes the parameters of the channel but it continues on to next channel in list (and so on in a loop. Am I missing something, some new command?

 

[Ubbe]

It probably works as a Uniden scanner, if it cannot detect any ongoing conversations it will continue to the next control channel in the list until it finds TG activity.

But perhaps you have another issue that it doesn't let you monitor any TG's you have programmed in a list that it should follow and skips all conversations that you at the same time can monitor with a scanner on that control channels site? You have the correct LCN numbers set to each voice frequency in the channel list?

/Ubbe

 

[Marco192]

It's not a problem that it will not follow, it's a problem that i will not park on the control channel.
It's a system that I now well, and have been listening using both dsd++ and dsd-fme. In dsd-fme it works as it should detecting calls and following them to the channels in the list.

 

[Ubbe]

It creates a log file, does it say anything suspicious? The t parameter are used for hangtime of TG's in trunked mode but hangtime for scan in non-trunked mode. In trunked mode it starts up by reading the channel list and then needs LCN values and also a TG list so those probably needs to exist and formatted properly.

What happens if you only have one frequency in the channel list and use non-trunk mode?

/Ubbe

 

[Marco192]

Thanks for the ideas and suggestions. I tried all of them and more.
I checked and double checked everything (channel list, group list, hangtime) - Nothing helps. Even when a call comes the "scan" continues, it is not following the call. This is my command, maybe someone can spot an error
dsd-neo -fs -i tcp -U 4532 -T -C bin\dmr_t3_chan_cn1.csv -G bin\group.csv -N -Z 2> NUL

 

[Ubbe]

I will take another look in its source code but when I looked at delay times I only found those two and it only had that t timer for a control channel in non trunked mode when it lost the sync and couldn't see any for a control channel in trunked mode.

Does it stay a second or two on the control channel, to be able to decode a couple of superframes to check for activity, or it just skip it as if it doesn't recognize the data? If you run it in non trunked mode and have all voice channels in the channel list, will it then stop on conversations?

/Ubbe

 

[Marco192]

when in trunking mode it does decode the control channel and it displays basic parameters and even call grants. But it will not stay on the CC or follow the call. Even when it hits the voice channel during a call it will not stay on the channel.

if it's not in trunked mode it stay on the manually tuned channel, it does not scan/hunt and it does not follow the call.

 

[Ubbe]

if it's not in trunked mode it stay on the manually tuned channel, it does not scan/hunt and it does not follow the call.

In conventional mode it should scan the channels in the channel list and if it detects a carrier it should at least wait for the time set at t before it continues to scan.

I assume that NEO are something that you compile yourself to get an executable file. Did you get any errors in the log from the compile process? How do you run the program, in native Windows, Linux or emulator window?

/Ubbe

 

[Marco192]

I am using a Windows version downloaded from dsd-neo github. I did not compile anything myself.
I don't know if the developer is here on the forum to try to replicate this issue. I have not found anything wrong in using the program, it just does not work in trunked mode.
dsd-fme works fine, so I will be sticking with it for now

 

[M105]

I downloaded DSD-NEO out of curiosity and have the same issue as you when trying to follow a NXDN 48 turnked system that I have monitored for years with DSD+. It is continuously scanning instead of following the voice calls. Since I know zilch about this or the FME version I wondered if I was just doing something ignorant in trying to set it up.

 

[Marco192]

It would seem that in the latest version of dsd-neo the trunking problem is fixed.
I just tried and basic call following seems to be working as should.
Thanks to the developers for this quick fix

 

[gary123]

Link to the code for those who do not have it.

GitHub - arancormonk/dsd-neo: A modern, modular, and performance enhanced C/C++ decoder for digital voice. DMR, P25, NXDN, YSF, and more.

A modern, modular, and performance enhanced C/C++ decoder for digital voice. DMR, P25, NXDN, YSF, and more. - arancormonk/dsd-neo

github.com

Here are the built binaries.

Release nightly · arancormonk/dsd-neo

Nightly Build Release Notes ⚠️ Important Notice This is an automatically generated nightly build and not an official release. Nightly builds are intended for testing, experimentation, and early fee...

github.com

A special thanks to the developers for constantly updating the builds.

 

[M105]

I see no difference with the latest build on the NXDN-48 system I am trying to monitor with it. It still jumps from frequency to frequency in the list.
Maybe I am doing something wrong. My command line is below. If I turn off trunking and just put it on a voice channel it will decode it.

dsd-neo -fi -i rtl:0:453.5375M:35:-4:8:0:2 -T -C nxdn_chan_map.csv -N

 

[ronenp]

is there a way of contacting the outhors ? or a discussion group or forum that they are there ?
I would like to ask a features to add for it

Thanks Forward
R

 

[Forts]

If you are having an issue, there is literally an Issues thread to post on at the projects Github page. The dev is very responsive and helpful to work with.

 

[Marco192]

I had another go at setting up pulse audio routing on windows, using the latest native windows version of dsd-neo.
Now dsd-neo can see all the audio devices but when selecting a specific output device it does not route the audio to that device.
I can select the device using the -o pulse:"output device name" command or using the interface in dsd-neo.
As before it will only output audio to the default device that is set in windows.

Another question: How to set the selection of a rtl-sdr stick by using it's serial number? (it works in dsd-fme but not in neo)

 

[W4KRR]

Is there a setup guide to get it working under Windows? I downloaded the Windows native .zip nightly build, and I feed it with SDR++ via TCP connection. It is hearing the control channel, but all I'm getting is a scrolling screen with system NAC, system ID, and other information, but no tracking or voice.

 

[VK5DT]

Hi W4KRR
Could be a number of things.
Are you using the "-T" switch for trunking?
P25 should be automatic, but DMR / NXDN system trunking you will probably need a channel map of frequency's.
Maybe you don't have you "-U 4532" switch to allow RIG control to set the sdr's frequency to follow the voice channel?
Whats your bat look like?

running "dsd-neo -h" in a cmd window is very useful

 

[W4KRR]

Hi W4KRR
Could be a number of things.
Are you using the "-T" switch for trunking?
P25 should be automatic, but DMR / NXDN system trunking you will probably need a channel map of frequency's.
Maybe you don't have you "-U 4532" switch to allow RIG control to set the sdr's frequency to follow the voice channel?
Whats your bat look like?

running "dsd-neo -h" in a cmd window is very useful

Thanks; I have since gotten it to work.

 

[arancormonk]

definitely submit an issue or start a discussion on github: GitHub - arancormonk/dsd-neo: A modern, modular, and performance enhanced C/C++ decoder for digital voice. DMR, P25, NXDN, YSF, and more.

i try to respond as quickly as possible if i have visibility into the problem, that said, i don't always keep track of what's going on in this forum... i prefer github, but tag/message me here in the future if problems/issues arise and nobody else can figure it out... i'm guilty of making mistake all the time.

also, realize i run pretty fast and loose with dsd-neo... it is not at all meant to be stable 100% of the time as i'm constantly adjusting/experimenting with things. any user feedback is much appreciated considering i can't reasonably test every facet of this codebase, although i do add unit tests where possible to try and catch regressions.