DSDPlus Sites/SiteLoader Files & iDAS NXDN - SOLVED/FIXED!!

[kg6nlw]

As the subject says, I am asking about the Sites/SiteLoader Files with an iDAS NXDN system ( Signature Wireless Group iDAS Multitrunk (Bay Area) Trunking System, San Rafael, California - Scanner Frequencies ).

I can not get the Sites/SiteLoader files to properly recognize the sites I have entered as data. This is from my SiteLoader file. I have tried all sorts of combo and even asked for help with a Discord group I'm in who have some good DSD guys in there. None of us can figure out why it isn't loading. I have tried all obvious protocols (dPMR, NXDN48, NXDN96, DCDM, ProVoice).

NXDN48, 1, 10, "Sig.Wireless - Cobb Mt (Lake Co)"
NXDN48, 1, 12, "Sig.Wireless - Geyser Peak (Sonoma Co)"

Does anyone here have an idea or answer so the sites will show up in those two files?

EDIT: Apparently I had to use NEXEDGE48 not NXDN48!!

Regards,

-Frank C.

 

[AM909]

@franks_ham: Do I understand correctly that Notes.txt and comments in DSDPlus.siteLoader are wrong – that the protocol needs to be NEXEDGE48 instead of NXDN48?

 

[BM82557]

In the DSDPlus.txt file it has --

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

 

[BM82557]

An email has been sent to DSDPlus.

 

[kg6nlw]

@franks_ham: Do I understand correctly that Notes.txt and comments in DSDPlus.siteLoader are wrong – that the protocol needs to be NEXEDGE48 instead of NXDN48?

Yes that is correct, the Notes.txt and comments for DSDPlus.SiteLoader/DSDPlus.Sites has it wrong and it should be NEXEDGE48 for iDAS Type D systems.

An email has been sent to DSDPlus.

Thank you. I was going to do that this morning.

Regards,

-Frank C.

 

[slicerwizard]

Never had an issue with iDAS and site loader, although there isn't much iDAS around here, so I don't use it very often. It certainly worked tonight though with no need to use some other protocol name. It tuned through the site channels until it caught an idle burst.


DSDPlus.networks

IDAS, 60:1.1, "WA iDAS" ; Airtime, iCOM, Communitronics, Ernie's, Quinte Comm


DSDPlus.sites

IDAS, 60:1.1, 3, "iCOM Canada, 38 Dixon Road"
...


DSDPlus.siteLoader

IDAS, 60:1.1, 3, "iCOM Canada, 38 Dixon Road"
...


DSDPlus.frequencies

IDAS, 60:1.1, 3, ?, 452.6375, 0.0, 0 ; Icom Canada, 380 Dixon Road
IDAS, 60:1.1, 3, ?, 452.6750, 0.0, 0 ; Icom Canada, 380 Dixon Road
IDAS, 60:1.1, 3, 1, 453.6125, 0.0, 0 ; Icom Canada, 380 Dixon Road
...

 

[mrscanner2008]

I have a problem with 2 IDAS systems near my home, none of them shows network number, sites, etc., how can I configure my DSD files (Network, frequencies, siteloader)?

 

[kg6nlw]

I have a problem with 2 IDAS systems near my home, none of them shows network number, sites, etc., how can I configure my DSD files (Network, frequencies, siteloader)?
View attachment 111391

It should be easy enough. Load all the frequencies from the site you're listening to in the frequencies file using the format listed. In Sites/SiteLoader use the proper format there and load it up with the site names.

Regards,

-Frank C.

 

[mrscanner2008]

ok but how can I differentiate the 2 systems if they don't have a network id?

 

[kg6nlw]

Do they have RadioReference DB entries? If so, please link them so I can take a look.

Regards,

-Frank C.

 

[mrscanner2008]

Do they have RadioReference DB entries? If so, please link them so I can take a look.

Regards,

-Frank C.

no not in RR DB yet.

 

[kg6nlw]

Okay, that will be a little harder for me. What does it show along the bottom line of the DSD+ screen when listening to the rest/control channel?

Regards,

-Frank C.

 

[mrscanner2008]

the 2 systems only show IDAS ID at the bottom of DSD Windows.

if I enter the frequencies of the 2 sites separately, dsd does not differentiate and displays the wrong frequency. I must add ";" ahead of the frequencies of the other site that I don't want to listen to.

 

[kg6nlw]

the 2 systems only show IDAS ID at the bottom of DSD Windows.

if I enter the frequencies of the 2 sites separately, dsd does not differentiate and displays the wrong frequency. I must add ";" ahead of the frequencies of the other site that I don't want to listen to.

Send me a PM and I think we can get this squared away...Takes up fewer comments here that way.

Regards,

-Frank C.

 

[AM909]

You make up your own network IDs for systems of a type that does not support them. From Notes.txt:

Added optional network ID prefix for iDAS and TIII systems.

These systems do not use unique network IDs. When FMPA/FMP24 are TCP linked to DSD+,
iDAS or TIII systems that broadcast identical network IDs can be differentiated
by adding user-selected network ID prefixes to iDAS/TIII DSDPlus.frequencies records.

DSDPlus.frequencies examples:

TIII, 13, 1.1, 413, 450.0125, 0.0, 0 ; ACME Inc TIII; NID conflict
TIII, 13, 1.1, 117, 462.6000, 0.0, 0 ; Road Runner TIII; NID conflict

TIII, 1:13, 1.1, 413, 450.0125, 0.0, 0 ; ACME Inc TIII; NID conflict resolved
TIII, 2:13, 1.1, 117, 462.6000, 0.0, 0 ; Road Runner TIII; NID conflict resolved


IDAS, 1.1, 1, 1, 450.2250, 0.0, 0 ; ACME Inc iDAS; NID conflict
IDAS, 1.1, 1, 1, 462.4725, 0.0, 0 ; Road Runner iDAS; NID conflict

IDAS, 123:1.1, 1, 1, 450.2250, 0.0, 0 ; ACME Inc iDAS; NID conflict resolved
IDAS, 456:1.1, 1, 1, 462.4725, 0.0, 0 ; Road Runner iDAS; NID conflict resolved

Network ID prefixes should be selected from the range 1 to 4095.
Records in the .networks and .sites files should be edited to match the .frequencies file data.

 

[mrscanner2008]

You make up your own network IDs for systems of a type that does not support them. From Notes.txt:

Already tried but not working for me.

 

[mcjones2013]

If two or more systems of the same system-type have the same network ID (common in IDAS and TIII), you can append a number at the beginning of the network ID in all instances of that network ID appearing in DSDPlus files (networks, sites, frequencies, groups, radios, etc.).

For example:

IDAS, 1:1.1, "Signature Wireless IDAS MultiTrunk"
IDAS, 2:1.1, "Example IDAS System 2"
IDAS, 3:1.1, "Example IDAS System 3"

TIII, 1:9, "Apple Inc"
TIII, 2:9, "Example TIII 2"
TIII, 3:9, "Example TIII 3"

If you're trying to save systems which do not use network IDs (such as Capacity Plus), I would recommend saving the system in DSDPlus with a network ID matching the "sid=" of the system URL in the RRDB:

Example: Arden Fair Mall (Capacity Plus)
Cap+, 8935, "Arden Fair Mall"

 

[mrscanner2008]

If two or more systems of the same system-type have the same network ID (common in IDAS and TIII), you can append a number at the beginning of the network ID in all instances of that network ID appearing in DSDPlus files (networks, sites, frequencies, groups, radios, etc.).

For example:

IDAS, 1:1.1, "Signature Wireless IDAS MultiTrunk"
IDAS, 2:1.1, "Example IDAS System 2"
IDAS, 3:1.1, "Example IDAS System 3"

TIII, 1:9, "Apple Inc"
TIII, 2:9, "Example TIII 2"
TIII, 3:9, "Example TIII 3"

If you're trying to save systems which do not use network IDs (such as Capacity Plus), I would recommend saving the system in DSDPlus with a network ID matching the "sid=" of the system URL in the RRDB:

Example: Arden Fair Mall (Capacity Plus)
Cap+, 8935, "Arden Fair Mall"

View attachment 111403

Hi thanks for the info, for CAP+ it's working fine, but not for TIII, IDAS or XPT, but don't know why, I follow your example to the letter, but without success. For the TIII, the 2 networks are T1-1.2, I add 1: in front but without success.

For IDAS All I have in DSD is IDAS ID, nothing more is received.

 

[W4WMH]

I have the same issues with 2 DMRT3 systems in my area. They are both network 1 Site 1. Has anyone else had any success in appending the Network number with a prefix to differentiate?

I answered my own question. Add the network in DSDPlus.networks, append it there. Carry it through sites and frequencies, and it works now. Leaving this for future people to see a resolution.

 

[slicerwizard]

Your solution exactly matches what the Notes.txt file says...


Added optional network ID prefix for iDAS and TIII systems.

These systems do not use unique network IDs. When FMPA/FMP24 are TCP linked to DSD+,
iDAS or TIII systems that broadcast identical network IDs can be differentiated
by adding user-selected network ID prefixes to iDAS/TIII DSDPlus.frequencies records.

DSDPlus.frequencies examples:

TIII, 13, 1.1, 413, 450.0125, 0.0, 0 ; ACME Inc TIII; NID conflict
TIII, 13, 1.1, 117, 462.6000, 0.0, 0 ; Road Runner TIII; NID conflict

TIII, 1:13, 1.1, 413, 450.0125, 0.0, 0 ; ACME Inc TIII; NID conflict resolved
TIII, 2:13, 1.1, 117, 462.6000, 0.0, 0 ; Road Runner TIII; NID conflict resolved


IDAS, 1.1, 1, 1, 450.2250, 0.0, 0 ; ACME Inc iDAS; NID conflict
IDAS, 1.1, 1, 1, 462.4725, 0.0, 0 ; Road Runner iDAS; NID conflict

IDAS, 123:1.1, 1, 1, 450.2250, 0.0, 0 ; ACME Inc iDAS; NID conflict resolved
IDAS, 456:1.1, 1, 1, 462.4725, 0.0, 0 ; Road Runner iDAS; NID conflict resolved

Network ID prefixes should be selected from the range 1 to 4095.
Records in the .networks and .sites files should be edited to match the .frequencies file data.