DSD+ Status

[joeuser]

Announcing the new and improved DSD+ 1.51!

Zippyshare.com - DSDPlus-1.51.zip

Irresponsible parties sacked. Again...

Its like Christmas around here!

 

[joeuser]

FYI, both versions worked fine. I'm on the latest. P25 system. Great new features! Does it auto detect the input & output now? Seemed to set itself right up! Even seems to have a better sound, if that's possible.

One minor request, & I would be fine without it. I'd like to be able to resize the DSD+ Event Log window while not changing the font size. Font size is great! Just want to be able to trim off the extra window space on the right.

 

[Forts]

On Eric's WinDSD it shows 454.2750 as channel 1 and 454.2625 as channel 2. Grants are shown to channels as channel # and slot #. Such as a grant goes to channel 2, slot 2.

On DSDPlus 454.2750 shows as channel 1 and 2 (where channel 1 is the Control channel in slot 1 and channel 2 is traffic activity in slot 2). And 454.2625 is channel 3 (slot 1 traffic) and channel 4 (slot 2 traffic).

What is the correct per standards?

thanks,

Joe

DSD+ refers to the LCN slot for Capacity Plus/Connect Plus... Which is what the CPS refers to.

 

[jcardani]

Thanks Forts!

Also for standards sake, should the slots be 0 for the first & 1 for the second. or 1 for the first & 2 for the second?

thanks!

Joe

 

[Forts]

Once again if we go by the CPS, Motorola and Hytera both refer to Slot 1 and 2.

Sent from my SGH-I337M using Tapatalk

 

[jcardani]

DSDPlus:

While we are on feature requests my #1 request would have to be trunk following. Now that the pertinent info such as talk group and channel information and disconnect is known, it should be easy to implement. I would suggest possibly using the Hamlib radio comms library since it supports many different radios.

thanks,

Joe

 

[jcardani]

Thanks! So it's the control channel that is displaying the 0 and 1 while in CPS it is referred to 1 & 2?

Once again if we go by the CPS, Motorola and Hytera both refer to Slot 1 and 2.

Sent from my SGH-I337M using Tapatalk

 

[EricCottrell]

Hi All,

Nice job DSDPlus!

Working well here so far for Trbo. Some issues for NXDN IDAS trunked but will discuss later.

I did notice on a local 2 channel Con+ Motortbo system (Sys 141, site 18 - Philadelphia)

454.2750 (control)
454.2625 (traffic)

On Eric's WinDSD it shows 454.2750 as channel 1 and 454.2625 as channel 2. Grants are shown to channels as channel # and slot #. Such as a grant goes to channel 2, slot 2.

On DSDPlus 454.2750 shows as channel 1 and 2 (where channel 1 is the Control channel in slot 1 and channel 2 is traffic activity in slot 2). And 454.2625 is channel 3 (slot 1 traffic) and channel 4 (slot 2 traffic).

What is the correct per standards?

thanks,

Joe

Hello,

The dsd program refers to the slots as zero and one, so that convention is followed in my additions, but maybe a slipped and used one and two in places. WinDSD is nothing more than the stock dsd code, minus some code that prevents windows compilation, and plus my additions for DMR/Nxdn decoding. It is more a means to test things. WinDSD is not really a separate product so I refer to it as dsd since my changes will eventual get added to dsd if the author approves.

On Capacity Plus systems the channel numbers as per Motorola are used, so the outputs from dsd and dsd+ should be the same.

On DMR Tier 3 systems, the slot is a separate field from the channel number. So you would see a separate channel with the zero based slot number.

The Connect Plus Option Board CPS uses a Network Frequency File to define the channel number to frequency mapping for a radio. A frequency is entered for each Radio ID (1 - 15) of the repeaters used at each site. So the Capacity Plus channel scheme is not used. The dsd program follows the same convention for Connect Plus as it does for DMR Tier 3 as it is similar to that format.

73 Eric

 

[jcardani]

Thanks Eric for the clarification!

 

[jcardani]

Guys,

I'm getting some dotting in the SrcAlias. It seems as though I am getting parts of the alias most of the time with dots instead of some letters. Is this due to bad decode? My signal for the system is good but not sure of quality. Any idea what is going on?

thanks!

 

[Markb]

1. Is there a list that shows a frequency for the channel number on Cap+ and/or NXDN systems? In the 700/800 band, the channel numbers are a set frequency. Am I off base with this assumption?

2. I see that on Nexedge systems there is a blank column for TG aliasing. Is this a future feature or what?

 

[blantonl]

With this release - we are now tracking NEXEDGE System IDs (called NIDs) - go ahead and submit them for the systems that you are tracking.

All reports and database pages have been updated to account for NEXEDGE system NIDs now..

Thanks,

 

[jcardani]

Hi Markb,

As far as I know the frequency for those systems are not broadcast over the control channel so it needs to to be mapped in the .frequency file. You would need to edit the file per instructions at the top of the sample file.

Aliasing is working for me on both NX48 and NX96 systems. I get OK decoding on this but it seems to eventually figure it out. It is saved in the alias file.

1. Is there a list that shows a frequency for the channel number on Cap+ and/or NXDN systems? In the 700/800 band, the channel numbers are a set frequency. Am I off base with this assumption?

2. I see that on Nexedge systems there is a blank column for TG aliasing. Is this a future feature or what?

 

[jcardani]

Hi Lindsay,

I feel like a kid in a candy store figuring out Nexedge and Mototrbo trunked radio info in the Philly metro area. There's plenty to work with here!

With this release - we are now tracking NEXEDGE System IDs (called NIDs) - go ahead and submit them for the systems that you are tracking.

All reports and database pages have been updated to account for NEXEDGE system NIDs now..

Thanks,

 

[jcardani]

Further use reveals that the program figures out the correct alias for each rid and saves it to a file.
This makes things really easy to figure out talk groups and users!

Having a blast listening to wreck chasers right now!

 

[jcardani]

IDAS issues

Having no decode on the IDAS "status messages" that are broadcast every few seconds like analog LTR
systems. Does the program decode there? Have not heard any voice on the system yet.

thanks

 

[W4KRR]

Thanks for the efforts put into this! Seems to work well.

Is there a help file or documentation explaining the contents of the event log, the difference between green and purple text, etc?

 

[joeuser]

Man, you get purple?! I only get green! :-(

 

[EricCottrell]

With this release - we are now tracking NEXEDGE System IDs (called NIDs) - go ahead and submit them for the systems that you are tracking.

All reports and database pages have been updated to account for NEXEDGE system NIDs now..

Thanks,

Hello,

Are you supporting the Category (Local, Regional, Global) part of the system id?

I have submitted several Quebec NexEdge systems last August. The System IDs are only listed in the Misc System Info section.

73 Eric

 

[CqDx]

Versions of DSD+ that auto-decrypt MotoTRBO basic/enhanced privacy and P25 ADP have been created, but there are no plans to release these. They would only increase the use of real encryption. The team debated whether LRRP (GPS) functionality should be released as some public safety systems use it, but those agencies have the option of encrypting their data, and should be, so LRRP is ok. Same thing for text messaging.

First of all, thank you for all your hard work.

Is the LRRP decoding for MOTOTRBO only or for p25 as well?