DSD+ and Tier 3 systems

[GTR8000]

The latest release of DSD+ Fast Lane 2.448 has changed the way some Tier 3 systems are interpreted with regard to the System/Network ID and the site numbering. So far it has been confirmed to now display the Goosetown/Triangle system parameters correctly, however there are other Tier 3 systems in NY that should also be checked by anyone who is in the vicinity and is a Fast Lane subscriber.

East Mountain Communications

East Mountain Communications (T3 Hytera)

RadioMax Communications

SolarCity (Tesla)

Wegmans Food Markets

Please remember to submit any new findings with DSD+ 2.448 to the appropriate system as listed and linked above. Thanks!

 

[k2hz]

The latest release of DSD+ Fast Lane 2.448 has changed the way some Tier 3 systems are interpreted with regard to the System/Network ID and the site numbering. So far it has been confirmed to now display the Goosetown/Triangle system parameters correctly, however there are other Tier 3 systems in NY that should also be checked by anyone who is in the vicinity and is a Fast Lane subscriber.

East Mountain Communications

East Mountain Communications (T3 Hytera)

RadioMax Communications

SolarCity (Tesla)

Wegmans Food Markets

Please remember to submit any new findings with DSD+ 2.448 to the appropriate system as listed and linked above. Thanks!

I am checking RadioMax and Wegmans and will advise results.

 

[k2hz]

I am checking RadioMax and Wegmans and will advise results.

RadioMax: L13-1.1 L13-1.2
Wegamns: L1-1 L1-2 L1-4

 

[seagravebuff60]

Ill Check East Mountain later tonight

 

[pro92b]

Here is East Mountain. DSD+ seems confused (or I am).

 

[GTR8000]

RadioMax: L13-1.1 L13-1.2
Wegamns: L1-1 L1-2 L1-4

Okay so the RadioMax T3 Standard has not changed, and Wegman's CapMax has also not changed.

 

[GTR8000]

Here is East Mountain. DSD+ seems confused (or I am).

View attachment 152449

View attachment 152448

East Mountain has two systems listed in the RRDB, one is L1 the other is L13. Your results seems to match what is already in the database.

 

[pro92b]

For L13 DSD+ also reports L12 like it doesn't know which one to settle on. My site and frequency files were unchanged and reflect L13.

 

[GTR8000]

For L13 DSD+ also reports L12 like it doesn't know which one to settle on. My site and frequency files were unchanged and reflect L13.

Ah okay I see that now. Can you temporarily rename or move your files so that DSD+ is not influenced by them when decoding?

 

[pro92b]

I had to remove East Mountain data from the files. DSD+ would not run when the files were missing. Results are the same.

 

[seagravebuff60]

I had to remove East Mountain data from the files. DSD+ would not run when the files were missing. Results are the same.

If you put a leading semicolon in any of the DSD+ files, DSD will ignore that record
Example (Networks File)

;TIII, 1:13, "1:13 East MTN Trunk"

 

[GTR8000]

I had to remove East Mountain data from the files. DSD+ would not run when the files were missing. Results are the same.

View attachment 152450

Okay so it seems that initially DSD+ wants to label this L12 Site 1, then immediately switches to L13 Site 1.2

It's consistent, which is good, and it's definitely now showing the correct info for the Goosetown/Triangle system.

To recap:

• The Goosetown/Triangle system is a Selex/Leonardo brand Tier 3 system
• It appears that both East Mountain systems are Hytera brand Tier 3 according to DSD+
• Wegman's is a MOTOTRBO Capacity Max system, a pseudo Tier 3 system

@k2hz can you confirm what RadioMax shows in DSD+ for brand, if any?

 

[pro92b]

I created a copy of the entire DSD+ folder for test purposes. The files for frequencies, sites, groups, and radios had numerous entries for East Mountain. It was easier to just block delete those entries due to the large number of lines. When there is no further use for the test folder I will just delete the whole thing.

 

[seagravebuff60]

After blocking out all my DSD+ Records for East Mountain. I turned to the active control channel of the Putnam Valley site, and this is what DSD+ is displaying. I left it running for approximately 10 minutes to see if it would change, and it didn't. SysID 12 and Site 7



I think you need to block out all of your current DSD+ Records. Otherwise, DSD+ will display the incorrect information because it is grabbing the info from the files instead of the "OTA" information.

Same is showing for the Beekman Site. SysID12 Site 5. (Altho the Negbor listing still shows area.site )


The same is also showing for the Highland site. SysID 12, Site 2


I leave them all running for a bit, but i don't think any will change the system ID or site ID

 

[k2hz]

RadioMax TIII(HYT)

 

[scottjpalmer]

This change (which curiously doesn't appear to be in the change log) is what I believe to be the fix for a long standing issue described here

It has indeed fixed the issue, the TIII (MOT) system in question now consistently identifies as H1-XX as opposed to sometimes identifying as H2-Y.Y area.site format.

What I am now seeing though is inconsistent behaviour on TIII (TAIT) systems here. One functions as it should, consistently identifying as area.site format. The other now behaves like the MOT system above used to where DSD+FL identifies it as H1-XX rather H2-Y.Y area.site format.

v2.444


v2.448

This system behaves the same as before the update


This system does not

 

[mtindor]

I had to remove East Mountain data from the files. DSD+ would not run when the files were missing. Results are the same.

View attachment 152450

That's not technically confusion. It captures the DMR sync, and it displays some generic data until it is able to identify that it is a Hytera system. As soon as it is able to identify it as a Hytera system it adjusts. This has always done this on typical TIII systems -- just sometimes it is able to detect the vendor type so fast that you don't see that confusion period.

 

[pro92b]

​

Something still does not seem right. I took all the data files from the base file zip just downloaded and put them in the DSD+ folder. That overwrote whatever was there before and essentially wiped out any stored system data I might have had. Then I shut the computer down and powered it on. Nothing changed. I still see L12 initially and it changes to L13 and stays L13. This is on the Highland site as logged in post 14 by seagravebuff60. However he never shows L13 on his screenshot - it stays at L12. I am getting the signal from a discriminator tap feeding into the mic jack on the computer. The signal looks fine on the scope display in DSD+.

 

[mtindor]

​

Something still does not seem right. I took all the data files from the base file zip just downloaded and put them in the DSD+ folder. That overwrote whatever was there before and essentially wiped out any stored system data I might have had. Then I shut the computer down and powered it on. Nothing changed. I still see L12 initially and it changes to L13 and stays L13. This is on the Highland site as logged in post 14 by seagravebuff60. However he never shows L13 on his screenshot - it stays at L12. I am getting the signal from a discriminator tap feeding into the mic jack on the computer. The signal looks fine on the scope display in DSD+.

Hmm. Well keep the reports coming. And if possible, capture raw audio and either link to it in the forums or send it directly to dsdplusfastlane@gmail.com so that the author is aware and has something to work with. But just make sure and describe what's different in DSDPlus behavior from 2p444 to 2p448 with that particular system.

 

[seagravebuff60]

I changed all my DSD+ Files with incorrect information to test and DSD+ is displaying the incorrect info that I put in my files. As soon as I deleted the incorrect info after a few minutes DSD+ went back to show the correct info.

This further supports my theory that the reason why DSD+ is showing SysID 13 is that the files reflect that and will display the incorrect information because it is grabbing the info from the files instead of the "OTA" information.