DSD FME

[ki4hyf]

But it is hard to set the RF gain correctly.

I always use "0" to let DSD-FME automatically adjust the gain. In most cases, it works extremely well for me.

 

[ki4hyf]

When I decode a conventional DMR repeater, I get a black screen with scrolling data. Is this what I'm supposed to see? Or is there a screen with more detail?

Looks normal to me. Use -Z for more information.

 

[lwvmobile]

Is there any ways to use GNURadio TCP sink to pipe audio into DSD-FME instead of SDR++?
For trunking system, I'm implementing some new feature for my DSD-FME like neighbour site roaming and new site hunting, to make it more like a real trunk radio that enable us to automatically discover and roam to neighbour site when we travel. To achieve that, I need to use GNURadio to measure neighbour channel's signal strength in the background, to find the best neighbour to camp on, then feed the audio to DSD-FME for decoding.
And here is the problem, I tried with GNURadio TCP sink to pipe my demodulated audio into DSD-FME, but DSD-FME cannot get a sync to the signal. Instead, if I replace the TCP sink with audio sink and pipe with virtual audio cable, it work flawlessly. I prefer to use TCP sink as the input to DSD-FME because it enables us to monitor multiple channel within the entire SDR baseband simutaniously. I'm a beginner to GNURadio, is there anyone succeessfully pipe audio into DSD-FME through GNURadio's TCP Sink?

Did you ever find an acceptable solution for this? Sorry about not replying, had a death in the family around this time, so didn't have a good opurtunity to ever investigate this, but I think there is a TCP sink in GNURadio, maybe if you send it short type NFM demodulated audio, but not sure if those types of blocks connect to one another or not.

 

[lwvmobile]

Without quoting a single reply, but regarding using SDR++ and a single dongle, another method to using DSD-FME, particularly useful if you can cluster a lot of digital signals into the bandwidth of one device (airspy and so on with larger sampling would probably be better), but if you can fit it all with in a range, you can create multiple 'radios' from within SDR++, and send them out the TCP sink to different ports, and start a unique DSD-FME session for each of those, so instead of trunking and listening to the control channel, if all the traffic channels fit within a continuous range of frequency, you can just listen to all of those all at once instead.

 

[ki4hyf]

you can create multiple 'radios' from within SDR++, and send them out the TCP sink to different ports

That's good to know. I'm going to try that.

 

[W4KRR]

I've got DMR and NXDN decoding, both conventional and trunking, working well. But P25 trunking I can't get to work. Best case scenario, a talk group will pop up once in a while, but no audio, and the "Call History" at the bottom never populates.

I am using DSD++ with RIGCTL. This is the command line:

dsd-fme.exe -ft -i tcp:localhost:7355 -U 4532 -T -G 997-groups.csv -N 2> 997log.ans

Problem with the command line, or maybe DSD++ setting?

 

[TheButcher]

W4KRR, do you have these arguments in your batch file ?? ...

dsd-fme.exe -Z -N 2> log.ans

If not, then you will see more detail. And the 'NCurses Terminal' will show.

Thanks.

 

[lwvmobile]

Problem with the command line, or maybe DSD++ setting?

Without seeing what your set up is, I can only offer a few suggestions, but considering you have trunking NXDN and/or DMR working, I don't believe its a configuration issue. The command you are using seems fine. It might be worth looking into the 997log.ans file (Notepad++ or similar in Windows) and see if the CC is decoding properly or not.

First, if the site is simulcast, then decoding of the control channel and traffic channels may be poor. If that is the case, not much I can do. Other than that, for P25, I find using 12,000 BW and the Low Pass filter on SDR++ to work well together, so that might be worth a shot to see what happens.

 

[BinaryMode]

I've got DMR and NXDN decoding, both conventional and trunking, working well. But P25 trunking I can't get to work. Best case scenario, a talk group will pop up once in a while, but no audio, and the "Call History" at the bottom never populates.

I am using DSD++ with RIGCTL. This is the command line:

dsd-fme.exe -ft -i tcp:localhost:7355 -U 4532 -T -G 997-groups.csv -N 2> 997log.ans

Problem with the command line, or maybe DSD++ setting?

Might need the -W there.

-W Use Imported Group List as a Trunking Allow/White List -- Only Tune with Mode A

Try this:

dsd-fme.exe -ft -i tcp:localhost:7355 -U 4532 -T -W -G 997-groups.csv -N 2> 997log.ans

Also, instead of -ft you could use -f1 for P25 phase 1 or -f2 for P25 phase 2.

 

[W4KRR]

Might need the -W there.



Try this:

dsd-fme.exe -ft -i tcp:localhost:7355 -U 4532 -T -W -G 997-groups.csv -N 2> 997log.ans

Also, instead of -ft you could use -f1 for P25 phase 1 or -f2 for P25 phase 2.

I now have it working pretty well. Problem was user error. Thanks to all who helped.

If I use the "-f2" switch, it didn't work at all. It's a P2 system, but the control channel is not TDMA.
Here is what now works:

dsd-fme.exe -ft -i tcp:localhost:7355 -U 4532 -T -W -G 997-groups.csv -N 2> 997log.ans

I found out a big issue was in my 997-groups.csv file: I had most of the talkgroups set to "Block".

One last question: Is there an ideal "In Level" percentage that I should shoot for?

(My log is attached in case anyone would like to review for errors)

 

[Freemor]

Without quoting a single reply, but regarding using SDR++ and a single dongle, another method to using DSD-FME, particularly useful if you can cluster a lot of digital signals into the bandwidth of one device (airspy and so on with larger sampling would probably be better), but if you can fit it all with in a range, you can create multiple 'radios' from within SDR++, and send them out the TCP sink to different ports, and start a unique DSD-FME session for each of those, so instead of trunking and listening to the control channel, if all the traffic channels fit within a continuous range of frequency, you can just listen to all of those all at once instead.

I am currently using a variation of this. several CC's and their respective talk frequencies fit in the bandwidth of my rtlsdr. At first i was doing what you suggest. (setting up 3 VFOs (radios) to cover the 3 talk frequencies of the local tower/CC but then I realized that I could also set up multiple RIGCTL ports.

So now I've set up 2 VFO (radios) and 2 RIGCTLs, That way I can run 2 DSD-FME instances (one for each radio/ctl) and monitor both the local area P25 Tower and a Local Province wide P25 tower. Yeah, lots of Duplicate traffic but it has filled in a lot of holes compared to just monitoring the local area tower.

 

[W4KRR]

Is it possible to assign a name / alias to a conventional DMR frequency?

 

[W4KRR]

I think I have found a bug within the scanning feature.
The "examples" file recommends this command to scan NXDN 96:

dsd-fme -fn -i tcp -C channel_map.csv -Y -U 4532 -N 2> log.ans

However, if you use the required -fn switch to decode NXDN 96, it won't scan. It will just decode whatever frequency that SDR++ is tuned to.
If you change the -fn switch to something else, like -fa or -fs or -ft, then it will scan, although it won't decode any NXDN. I believe that NXDN cannot be auto detected. So this may be an issue for anyone wanting to scan conventional NXDN frequencies.

This setup uses SDR++ and RIGCTL.

 

[ki4hyf]

Is it possible to assign a name / alias to a conventional DMR frequency?

There is in SDR++, but not that I know of in DSD-FME. Maybe it's just me, but I've never found a need for it.

 

[ki4hyf]

I think I have found a bug within the scanning feature.
The "examples" file recommends this command to scan NXDN 96:

dsd-fme -fn -i tcp -C channel_map.csv -Y -U 4532 -N 2> log.ans

That exact command line works for me. Could you please post the contents of your equivalent channel map csv?

 

[W4KRR]

That exact command line works for me. Could you please post the contents of your equivalent channel map csv?

Yes, that command line works for me too. It just won't scan. If I change the -fn switch to -fs or -fa, it will scan, but not decode.
I have attached my NXDN channel map .csv.

 

[ki4hyf]

It scans for me. Now, I wonder if it's a "windows thing"? I'll try it when I get a chance to run a win10 VM.

 

[W4KRR]

It scans for me. Now, I wonder if it's a "windows thing"? I'll try it when I get a chance to run a win10 VM.

I have another list that I scan, combination of P25 and DMR, using the -ft switch. It scans and decodes just fine. However, if I change the -ft switch to -fn, it won't scan. Just sits on whatever frequency is in SDR++. Changing the switch back to -ft, it will then scan. I realize that -fn won't decode DMR or P25, but I would assume it should still scan.

 

[radioopperator]

I need a little help?
I'm using: set "options= -ft -T -U 4532 -i tcp -G group.csv -K multi_key_hex.csv -L lrrp.csv -N -Z 2> log.ans"

I use to have in the log files the IMBE stacks but I either clicked something or removed something from the string?

Thanks.

 

[ki4hyf]

The -Z switch should show the IMBE voice frames for P25 P1. The options line looks ok to me. Can you post a few lines of captured voice from your log file, where you think the IMBE frames should be?