New DSD+ 2.464

[Muxlow]

DSD+ 2.464

Removed Scroll of Death.

More DMR messages decoded.

More P25 LRRP messages decoded.

Added menu options to tune to trunked repeater inputs when following voice or data calls.
Performance on input frequencies may be improved by selecting only a single protocol
in the DSD+ Decoder menu. For non-P25, non-DFA systems, input frequencies will need to be
added to the relevant DSDPlus.frequencies file entries.

Added proper decoding of inbound P25 trunking control channel messages (ISPs).
When monitoring inbound P25 control channels, only P25 decoding should be selected
in the DSD+ Decoder menu. All other protocols must be deselected.
Currently, only a limited set of ISPs are fully decoded. Decoding of additional ISPs
will be added as users submit raw source audio recordings of unhandled ISPs.
File sizes can be minimized by enabling Only Record During Sync in the DSD+ Input menu.

 

[dave3825]

Get this on one P25 Phase 2 site (for logging) with a weak signal. Never did that before.

 

[vince48]

I too have the "unhandled TSDU inbound p_parm_req" what does this mean?

 

[RaleighGuy]

On newest version has anyone else noticed it not logging TG's properly... Below are screenshots from three different systems and all have talkgroups monitored but not in logging window.



Also on NXDN system Radio logging has no scroll and only shows the last 6 RIDs seen.

 

[Muxlow]

Yeah for sure need little more info on what this new feature does/means

 

[RaleighGuy]

I too have the "unhandled TSDU inbound p_parm_req" what does this mean?

Yeah for sure need little more info on what this new feature does/means

I'm trying to get the message, but on a NXDN, a P25 P1 Simulcast, and P25 P2 Harris system I have not seen it yet.

 

[vince48]

i'm getting it on a P251 TDMA. Not alot, but it pops up once in awhile

 

[TheButcher]

Monitoring a Tait TIII site. I can report no more "Scroll of Death" with the latest version, "2.464". Thanks !

 

[slicerwizard]

Also on NXDN system Radio logging has no scroll and only shows the last 6 RIDs seen.

View attachment 157079

Because, via the Seen Groups Window, you told DSD+ to only show you that group's radios...

 

[RaleighGuy]

Because, via the Seen Groups Window, you told DSD+ to only show you that group's radios...

Thank you hadn't noticed I changed that setting

 

[slicerwizard]

On newest version has anyone else noticed it not logging TG's properly... Below are screenshots from three different systems and all have talkgroups monitored but not in logging window.

View attachment 157074View attachment 157076View attachment 157077

Why are there no radio IDs showing on those calls?

 

[RaleighGuy]

Why are there no radio IDs showing on those calls?

External messages usually don't show the RID, like VOIP I guess. It is the Duke Harris TDMA CC system

 

[TheButcher]

With TIII Standard CPS-P3 names wont show....




And there is "?" where in this case "H" should show. "H2" is set in all of the data files.




Shot of the CC part of it...

 

[slicerwizard]

External messages usually don't show the RID, like VOIP I guess. It is the Duke Harris TDMA CC system

Well, wild guess here, but if no radio IDs are currently associated to a group, i.e. affiliated to or transmitting on that group, is DSD+ going to see that group as "active"?

 

[RaleighGuy]

Well, wild guess here, but if no radio IDs are currently associated to a group, i.e. affiliated to or transmitting on that group, is DSD+ going to see that group as "active"?

It has in the past

 

[slicerwizard]

With TIII Standard CPS-P3 names wont show....




And there is "?" where in this case "H" should show. "H2" is set in all of the data files.




Shot of the CC part of it...

I take it the first screen shot is the VC side of a dual receiver CC/VC setup? If VC DSD+ doesn't know the network model, I doubt that it's going to use the "H2" radio entries in your .radios file, so I'd expect that no radio aliases from those entries are going to be displayed. The problem/bug isn't "not displaying aliases", it's "not picking up the network model" from wherever it's supposed to get it.

 

[LimaZulu]

Still haven't tested it yet. How about "tuning to xxx.xxx MHz" but it never tunes to anything, issue?

 

[LimaZulu]

Just did the update and unfortunately the answer to my question is NO. This bug is not resolved yet!

 

[dave3825]

Just did the update and unfortunately the answer to my question is NO. This bug is not resolved yet!

The tuning bug you were seeing here?

NXDN system here and I am also observing this on my side.

Mine is not doing that any longer.

 

[TheButcher]

I take it the first screen shot is the VC side of a dual receiver CC/VC setup? If VC DSD+ doesn't know the network model, I doubt that it's going to use the "H2" radio entries in your .radios file, so I'd expect that no radio aliases from those entries are going to be displayed. The problem/bug isn't "not displaying aliases", it's "not picking up the network model" from wherever it's supposed to get it.

Yes. (the first screen shot is the VC side of a dual receiver CC/VC setup).

So, I might try and drop the Network Model in the radios file (Change H2 to 2) and see how that goes... I will report back with results.