DSDPlus Trying to figure out how to set this NXDN system up in DSD+

[rjdj2000]

I've been searching on here to see how to set this system up in DSD+: Mobiletech Communications (NXDN) Trunking System, Various, Multi-State to try to see what TG are in my area, if any.

It has been a few years since I've messed with DSD+ and I only have the v1.01 version. Where it is throwing me off is setting up the .network file? I've only used this before on my local P25 system and I'm still having a rough time trying to figure out how I had that working. The ease of use of sdrTrunk and Unitrunker sure have made things easier but I know sdrTrunk won't work on this system and while I think Unitrunker will, I can't get it to work properly or there is nothing on the system I'm trying to listen to.

Jeff

 

[RaleighGuy]

The top of the DSDPlus.Frequency file tells you how to enter it in the frequency file, what elements are needed. After that it is just about locking onto the Control Channel.

 

[sonm10]

You really need to upgrade to fastlane. $10 annual or $25 lifetime updates. The "free" version is almost a decade old at this point. Forget about feeding with SDR#. Use fmpx instead.

You will need to update the .frequencies .sites .networks files to make work. Examples are at the top of each file.

 

[rjdj2000]

The top of the DSDPlus.Frequency file tells you how to enter it in the frequency file, what elements are needed. After that it is just about locking onto the Control Channel.

Ok, will go back and check things again. I get very good signal on it as the tower is roughly 3/4 to a mile away from my house as the crow flies...

You really need to upgrade to fastlane. $10 annual or $25 lifetime updates. The "free" version is almost a decade old at this point. Forget about feeding with SDR#. Use fmpx instead.

You will need to update the .frequencies .sites .networks files to make work. Examples are at the top of each file.

Yeah I know I "should" update but I'm not about to get into this again (the free releases that were promised on the website and I've asked about in here before)

I guess where I get lost on everything is this:

in the .networks file it goes as such:

protocol, networkID, "network name"[, TIIIareaLength]

I was thinking it should go as: NXDN, 13, HOMER

I could be way out in left field also, haven't ran it since I needed it with the earlier versions of UT for a P25 system. I've tried to get this to work in UTv2 but I doubt there is anything on it. Point UT to the single control channel, have warp set right and nothing. I've let it go for awhile and got nothing on it. So not sure if it is just not used around here or what. It is why I was trying DSD to see if could get anything out of it.

 

[cg]

Following the sample at the top of each of the files that needs to be populated is correct but you need to follow a bit closer. You are missing the quote marks around the "Network Name". I always suggest to follow the same sequence when editing the files for a new system, Network, Sites, Frequencies as not to miss anything.

 

[dave3825]

The ease of use of sdrTrunk and Unitrunker sure have made things easier but I know sdrTrunk won't work on this system and while I think Unitrunker will, I can't get it to work properly

Point UT to the single control channel, have warp set right and nothing. I've let it go for awhile and got nothing on it. So not sure if it is just not used around here or what.

Unitrunker does not decode or track NXDN https://www.unitrunker.com/#:~:text=Protocols Decoded,MPT1327

I guess where I get lost on everything is this:

in the .networks file it goes as such:

protocol, networkID, "network name"[, TIIIareaLength]

I was thinking it should go as: NXDN, 13, HOMER

In FastLane versions, 48 / 96 gets specified. Honestly don't remember how it was in 1.101

; DSD+ networks file
;
; you can edit this file while DSD+ is running
;
; line format: protocol, networkID, "network name"[, TIIIareaLength]
;
; for TIIIStd and TIIInonStd, add TIII model code (T/S/L/H) before networkID
;
; for TIIIStd, siteNumber format = area.site
; for TIIInonStd, siteNumber format = site
;
;
; protocols:
;
; ProVoice
; dPMR
; IDAS
; NEXEDGE48
; NEXEDGE96
; DMR
; TIIIStd
; TIIInonStd
; DCDM
; Cap+
; Con+
; XPT
; P25
; X2-TDMA
;
;
; Example:
;
; Con+, 123, "Acme Inc."

NEXEDGE48, 13, "Homan Comm-NJ/PA"
NEXEDGE48, 13, "Mobitech Communications NXDN"

Looking thru DSDPlus.txt, it may have been NEXEDGE






So try this,
NEXEDGE, 13, "Mobitech Communications NXDN"

 

[rjdj2000]

So try this,
NEXEDGE, 13, "Mobitech Communications NXDN"

Ok. Will give it a go. I appreciate the help, after not using any of this for the past 7 or so years, it is rough to get back into.

 

[dave3825]

Ok. Will give it a go.

Wait, I did not scroll past Networks file in that text. See the bold text towards the bottom.

NEXEDGE48, 13, "Mobitech Communications NXDN"

Data files
----------
DSDPlus.networks

You can populate the DSDPlus.networks file with the network IDs and
network names for NEXEDGE, Connect Plus and Tier III trunking systems.
DSD+ will display the network names when those networks are monitored.
You can add or edit network entries in this file while DSD+ is running.

DSDPlus.sites

The names for each site on a network can be stored in this file.
Some non-networked DMR systems also broadcast system IDs,
so entries for them can also be added to this file.
DSD+ will use the contents of this file to display the name of the
currently monitored site as well as the names of sites in neighbor lists.
You can add or edit site entries in this file while DSD+ is running.

DSDPlus.groups

DSD+ will auto-populate this file with every group ID that is seen.
You can edit this file while DSD+ is running and add names/aliases to
group records.

DSDPlus.radios

DSD+ will auto-populate this file with every radio ID that is seen.
You can edit this file while DSD+ is running and add names/aliases to
radio records. This file replaces the DSDPlus.aliases file; if you
already have a large aliases file, you can use a text editor's
search/replace functionality to convert the contents of your aliases file
to match the format used in the radios file.

NOTE:

Radio aliases are auto-generated on NEXEDGE systems. DSD+ marks auto-generated
NEXEDGE radio aliases in the DSDPlus.radios file by prepending an asterisk like so:

NEXEDGE, ... yyyy/mm/dd hh:mm, *"aliastext"

If you edit a NEXEDGE alias, you must remove the asterisk; this tells DSD+ that
the new alias text is NOT auto-generated and DSD+ will not replace it with OTA alias text.


DSDPlus.frequencies

DSD+ uses this file to display frequency information when DSD+ is monitoring
a rest channel or control channel. The frequency records will also be
used to control channel steering for trunked voice following.

Note:

DSD+ uses two channel numbers for each DMR RF channel:

Channel #1 = first RF channel, timeslot 1
Channel #2 = first RF channel, timeslot 2
Channel #3 = second RF channel, timeslot 1
Channel #4 = second RF channel, timeslot 2
Channel #5 = third RF channel, timeslot 1
Channel #6 = third RF channel, timeslot 2
...

For all DMR systems (DMR, Cap+, Con+, TIII), only one channel record has
to be added to the DSDPlus.frequencies file for each RF channel.
You can use the channel number that corresponds to timeslot 1 or 2 and
DSD+ will use the same frequency information for the other timeslot.


All of the records in these data files have a protocol field;
DSD+ recognizes the following protocol name strings:

D-Star
IDAS
NEXEDGE48
NEXEDGE96
dPMR
DMR
Cap+
Con+
TIII
XPT
P25
ProVoice



DMR TIII handling
-----------------

 

[rjdj2000]

LOL yeah I missed that myself. I guess at some point I should upgrade DSD as it probably would be easier to do. I just don't use it enough to justify getting the newer version but with trying to figure out this system near me, I may have to.

I guess it comes down to the site id, system id that is confusing to me. I've tried to get this from the DB and put it in, but even in UT it pulls in everything (V2 that is) but when trying to add a channel in the system, it craps out. So that is why I was trying to see if I could get this going. I'm just going to have start fresh on it and go back through the txt files and re-read everything and go from there.

 

[cg]

There could be some NXDN systems that your version may not be able to monitor. Some use a feature called DFA (Direct Frequency Access) where the program takes the over the air channel numbers and tunes to the voice. Where I ran into problems with the early versions was the channel numbers were 5 digits and the program didn't like them in the Frequencies file.

 

[mtindor]

There could be some NXDN systems that your version may not be able to monitor. Some use a feature called DFA (Direct Frequency Access) where the program takes the over the air channel numbers and tunes to the voice. Where I ran into problems with the early versions was the channel numbers were 5 digits and the program didn't like them in the Frequencies file.

If its a DFA system (and I've never monitored one), I'm pretty sure that all you have to do is sit on the control channel and DSDPlus will gather the info and populate the channel activity windows with channel IDs and frequencies (which I guess you could subsequently put in DSDPlus.frequencies if you wanted).

DSDPlus.networks
NEXEDGE48, 13, "Mobiletech Communications (NXDN)"

DSDPlus.sites
NEXEDGE48, 13, 24, "Homer"

Mike

 

[rjdj2000]

If its a DFA system (and I've never monitored one), I'm pretty sure that all you have to do is sit on the control channel and DSDPlus will gather the info and populate the channel activity windows with channel IDs and frequencies (which I guess you could subsequently put in DSDPlus.frequencies if you wanted).

DSDPlus.networks
NEXEDGE48, 13, "Mobiletech Communications (NXDN)"

DSDPlus.sites
NEXEDGE48, 13, 24, "Homer"

Mike

Well I did try one thing and it somewhat worked. Was able to get DSD+ to run and had the FMP window going and all the other windows opened up. So getting closer. Will make sure the files are set like you said Mike and try again.

I don't know if it is a DFA system. Just noticed it in the trunked systems in my area and it had a Homer site, so thought I'd try to see what was on it.

Jeff

Edit: Here is where I'm at

 

[mtindor]

Well I did try one thing and it somewhat worked. Was able to get DSD+ to run and had the FMP window going and all the other windows opened up. So getting closer. Will make sure the files are set like you said Mike and try again.

I don't know if it is a DFA system. Just noticed it in the trunked systems in my area and it had a Homer site, so thought I'd try to see what was on it.

Jeff

Mobiletech NXDN is a DFA system. Does 1.01 handle DFA? not sure. FastLane does though.

If you park on the known active control channel with FMP, then you should see data on your DSDPlus Event Window if all goes well -- and if there is traffic you should see something show up in the Channel Activity Window.

Mike

 

[GTR8000]

Mobiletech is indeed a DFA system.

NEXEDGE DFA support was added in DSD+ Fast Lane 2.155 (Dec 2018)

If you're serious about monitoring the system, you need to be on the latest Fast Lane release. If you're unwilling to pay for it, no matter what your reasoning, then you're just wasting time trying to get the 10 year old last public release to work on this system type.

 

[rjdj2000]

Ok. Well when I get a chance to, I'll probably get a release. Just feel they didn't stay to their word on their website on free releases and that is where the rub is. I get it it takes time and $ to keep it going but I just think after they got the $ rolling in, the abandonded what they said. But that's another rabbit hole I've already been down on here so won't go no further.

Thanks for the help as at least I did see a little blurb here and there so it may warrant getting at least the year version. As I've said, the main thing I do is all P25 so UT and sdrTrunk handles that perfectly so I haven't had the need for DSD+. But to figure this one out, I may get it.

Jeff

 

[GTR8000]

Pay the $25 and get on with your life. I did so years ago and use DSD+ maybe 2 whole hours per year. I find other software like SDRTrunk and Unitrunker to be superior in most every way, however there are times where DSD+ comes in handy, and so be it. No use in complaining about "broken promises" of public releases for years when you could've been enjoying the software this whole time. 🤷🏼‍♂️

 

[rjdj2000]

Pay the $25 and get on with your life. I did so years ago and use DSD+ maybe 2 whole hours per year. I find other software like SDRTrunk and Unitrunker to be superior in most every way, however there are times where DSD+ comes in handy, and so be it. No use in complaining about "broken promises" of public releases for years when you could've been enjoying the software this whole time. 🤷🏼‍♂️

I get it GTR. But like you said, SDRTrunk and Unitrunker are superior and I thought UT V2 did decode NXDN, maybe I'm wrong but it shows up on the site for it, just can't get it to setup or show anything on it. I used to use DSD+ and the older UT v1 once I found the RTL sticks on this forum when my county went P25. Streamed it online that way until discovering SDRTrunk. So since then DSD+ has been an afterthought and I just haven't needed it. So it will be pay the 25 and mess with it on computer or buck up 50 and listen on scanner... Decisions.. Decisions... lol

 

[GTR8000]

Neither SDRTrunk nor any version of Unitrunker support NXDN decoding of any sort. I'm not sure where you think you saw NXDN listed for Unitrunker, perhaps you're confusing it with EDACS 4800? Or perhaps you're referring to the ancient v1 of Unitrunker that had the ability to display (but not decode) if a control channel signal was DMR or NXDN.

 

[rjdj2000]

Neither SDRTrunk nor any version of Unitrunker support NXDN decoding of any sort. I'm not sure where you think you saw NXDN listed for Unitrunker, perhaps you're confusing it with EDACS 4800? Or perhaps you're referring to the ancient v1 of Unitrunker that had the ability to display (but not decode) if a control channel signal was DMR or NXDN.

GTR, yes it was my mistake of taking the EDACS 4800 for the NXDN. Sorry for the confusion on that. I realized it after looking at the UT website again.

 

[rjdj2000]

So I bit the bullet and got the lifetime updates. So far it has worked great, after re-learning the program somewhat and getting used to the new window features. Getting information on this site now that I have sent into the database. One question that I haven't found answer to, can you set a TG to record? Have one on this system that is not in DB and would like to be able to go back and listen to any calls on it to determine what it is. As I leave this running all day while I am not home and would miss anyhing that would have come across the TG.