adsbgreenock
Member
Are you definitely receiving a transmission on the SDR++? I was using an SDR blog v3 and swapped over to an RSP1A device and both worked. Perhaps someone else can chime in who has more experience.
Regards
DSD FME
- Thread starter lwvmobile
- Start date
Are you definitely receiving a transmission on the SDR++? I was using an SDR blog v3 and swapped over to an RSP1A device and both worked. Perhaps someone else can chime in who has more experience.
Regards
Yes. I thought I read somewhere that DSD-FME won't work with an Airspy; only with RTL-SDR sticks.
adsbgreenock
Member
I think that only applies to the built in rtl sdr decoder which only works with such..it doesn't matter using a tcp audio input.
Regards
lwvmobile
DSD-FME
Did you set the Radio on the frequency you want to decode? For P25, you want NFM and 9000-1200 Bandwidth, only enable the Low Pass Filter, uncheck any others.
P25 Phase 1 CC with QPSK: dsd-fme -i tcp -U 4532 -T -mq -N 2> log.ans
Here is an example with a Phase 2 Control Channel: dsd-fme -i tcp -U 4532 -T -f2 -m2 -N 2> log.ans
Using SDR++, I got it working with the first example shown above (Phase 1). To get it to work, I had to increase the gain in SDR++ to stop the program from flashing between white and green "Audio Decode" and "Call Info".
Audio is okay, but sometimes drops out.
Using your example above for phase 2 decoding, the program opens and then does nothing. Yes, I programmed the correct control channel frequency. I guess more experimentation is needed.
Audio is okay, but sometimes drops out.
Using your example above for phase 2 decoding, the program opens and then does nothing. Yes, I programmed the correct control channel frequency. I guess more experimentation is needed.
lwvmobile
DSD-FME
It would only work if it were a Phase 2 Control Channel, or a single frequency that uses Phase 2. A lot of systems that are labeled as P25 Phase 2 still use the Phase 1 Control Channel, but have Phase 2 Traffic Channels that can revert to Phase 1 Channels if a Phase 1 only SU is on it/when needed, etc.
The new Duke Energy system is a good example of a large Phase 2 only system, including the Phase 2 MAC_SIGNAL or TDMA CC, no phase 1 anything on it.
lwvmobile
DSD-FME
I knew I saw this comment earlier, but couldn't find it again to reply to it until now. Thanks, I'm glad you like it and find that part useful. Sometimes I worry that I might put too much information in some places, but I do try to make the site info and channel info presentable.
There is no such thing as "too much information" when you try to discover a new network for example
If you are still worried, just put a switch to toggle on/off I think your piece of software added a lot of missing parts that every software so far had and really like the way you continue to develop new options and how you care of users! That's the right attitude for a developer to create cool stuff! Keep the flow!
Last edited:
I notice that sometimes the "Audio Decode" "In Level" exceeds 140 to 150%. How do I adjust this?
Just lower the sink volume
adsbgreenock
Member
Hi again guys so I'm running just the basic :
dsd-fme-aero.exe -i tcp 7355
command via sdr++ sink
I have a VHF trunked Cap+ system on 165mhz and have all the frequencies and lcns from my scanner.
How would I go about scanning those frequencies and logging the data from them? I edited the cap+ csv with the frequencies and I'm getting an error similar to cannot find channel_map.csv (which I'm sure I had to create and fill with the said Cap+ freqs.
Just getting the feel for this.. I keep trying different commands but resorting back to just clicking on one channel DMR trunked stuff.
As @LimaZulu said there can never be too much information. I've spent ages here in Scotland UK (without the help of a database) with my uniden SDS200e trying to discover various CAP+ and XPT systems and only wish the uniden gave half the data this program does.
Kind Regards
dsd-fme-aero.exe -i tcp 7355
command via sdr++ sink
I have a VHF trunked Cap+ system on 165mhz and have all the frequencies and lcns from my scanner.
How would I go about scanning those frequencies and logging the data from them? I edited the cap+ csv with the frequencies and I'm getting an error similar to cannot find channel_map.csv (which I'm sure I had to create and fill with the said Cap+ freqs.
Just getting the feel for this.. I keep trying different commands but resorting back to just clicking on one channel DMR trunked stuff.
As @LimaZulu said there can never be too much information. I've spent ages here in Scotland UK (without the help of a database) with my uniden SDS200e trying to discover various CAP+ and XPT systems and only wish the uniden gave half the data this program does.
Kind Regards
lwvmobile
DSD-FME
What I would do is make your csv file (see the cap sample in the examples folder) with your LSNs enumerated in it and save it in the examples folder. I find its easier to just save all your csv files in there since all the bat file examples show how to link to that directory, and just call it with the -C examples\capacity_plus_chan.csv (backslash in windows, forward slash in linux) or whatever you end up naming the file. For Capacity Plus, make sure that channels 1 and 2 are the same frequency (they are LSN based and not LCN), 3 and 4 the same, up to how many logical slots that system has.
For trunking it, I would make sure the rigctl server is turned on inside of SDR++ running on its default port of 4532, and then run the command, or just copy and paste it into your bat file.
dsd-fme-aero.exe -i tcp:localhost:7355 -U 4532 -T -t 2 -C examples\capacity_plus.chan.csv
A lot of the trunking examples are found in the 'start with pulse audio' bat file. While using pulse audio isn't required, if its a busy TDMA system where you may often get voice on both slots simultaneously, I would recommend using it. The OSS implementation can't do both voices at the same time (it stutters if allowed to try) the pulse audio backend can do it just fine, it just requires the user to start the pulse audio backend first, then launch dsd-fme from the bat file with pulse audio (or by using the command switch '-o pulse' after the pulse audio server backend is started.
EDIT: Added the `-t 2` option to tell it to hold on an RF frequency for 2 seconds of hangtime, the default is 1, but some capacity plus systems have a longer interval between beaconing and need to dwell a little longer before jumping to the next channel looking for the rest channel.
Last edited:
lwvmobile
DSD-FME
Yeah, if you got those bin files, you can just PM them to me and I'll take a look at them. I was wondering if that system shows up as DFA, or not, is that the same one that was just the single frequency listed in the database?
As for remoting in, I may have to take a rain check and get back with you on it, haven't had much time to do anything on it lately, let alone code or do anything other than simple observation for current behavior on different systems.
Got the program up and running very well on P25 Phase 1, DMR Connect Plus, and DMR conventional. P25 Phase 2 still has garbled audio at best. However, the phase 1 talkgroups on the phase 2 system sound fine. I have tried using Pulse Audio, but it doesn't seem to make a difference. Both P25 Phase 2 systems within my range are very busy.
Another issue I have found is that the talkgroup alpha tags don't match the talkgroup shown.
Example:
Note above that talkgroup 5081 is not CS Parks; CS Parks is actually 5063. The .csv file is correct, the display is not. This is an intermittent problem.
Example:
Note above that talkgroup 5081 is not CS Parks; CS Parks is actually 5063. The .csv file is correct, the display is not. This is an intermittent problem.
lwvmobile
DSD-FME
Okay, so, what is happening is that that label belongs to the current call in progress, 5063, which is different than the group that is listed under active channel. The channel/group listed there can update itself more often depending on whether or not any additional channels/groups are decoded in the embedded LCW for Phase 1 or any Phase 2 non-voice timeslots. This can be a bit confusing on the 84 build, and if you update to the 95 build, it should separate that out a bit better, make it so that the alpha tag is shown for the current call in progress, and the channel activity or update on it is only for that channel reflected (which shouldn't display an alpha tag since its just a string).
If you get the dsd-fme-aero-v2.0.0-95-win32.zip file, and just copy your csv/bat files into it where your current ones are and run it, it will make that distinction a bit clearer in the ncurses terminal.
Release DSD-FME-AERO V2.0.0-95 Windows 32-bit · lwvmobile/dsd-fme
95: This update includes a user toggle for enabling/disabling P25 Encrypted Voice Channel Grants when trunking/tuning (only on applicable voice grants, no MFID90, toggle on on ncurses terminal 'e' ...
github.com
Thanks for your help Iwvmobile; I will try your suggestion about using v2.0.0-95.
Similar threads
