DSD+ update 2.384

[pctek961]

I'm not getting that with 2.384. I run my trunked using R1 and I set, "Hiding all background events and traffic below monitoring threshold"



Scanlist been around for a while. What's new? What version did not work? 2.383 or 2.384? Mine is working fine with my airband scanlist.

2p383 & 2p384 both have this problem, NOT trunk tracking, just scanning Amateur radio repeaters.
It doesn't stop long enough to decode digital (DMR/D-Star/Fusion).

 

[dave3825]

Can you post your scanlist? I use my scanlist all the time for air freqs, conventional P25 freqs and Uhf freqs. Mine has run good the last few years without any issues.

 

[deathtone]

Which update? 2.383 or 2.384? One was June 1st and the other was June 2nd.

I downloaded the 2.384 update only, and then downloaded newest base files.

 

[dachomk]

Hi, where can I download the latest version of dsd+ ?

 

[mtindor]

Hi, where can I download the latest version of dsd+ ?

Are you a subscriber to DSDPlus Fast Lane? If so, you can download it from within DSDPlus FL if you have a fairly recent version. Otherwise, you may have to email dsdplusfastlane@gmail.com. Of course, if you didn't subscribe, then the only available option for you is the free version at https://www.dsdplus.com

 

[DeaconHarry16]

2.384 = no neighbor repeats for me

 

[iscottybotty]

I notice in this update the MI/ PI information is passed. Is there a way for the scroll to show actual voice headers/ frames?

 

[iscottybotty]

I downloaded the Update 30 mints ago and notice it is showing [clear] don't see ENC/KID I know Hardee Highland uses ENC.

View attachment 122356

Yes. I noticed this also and hope it’s a bug. Although that said, I notice the PI/ MI info is showing in the scroll, I can’t recall seeing that before.

 

[u2brent]

I keep losing a neighbor from the Event Window

No biggie, but annoying.

Just have to keep hitting "N" to reset it, then it mysteriously disappears again.
Not sure if this is an issue with just one system or is systematic as of yet.
Anyone else seeing similar activity?

 

[a417]

Interesting, I'm having the reverse effect to some of you. I see [CLEAR] now on known clear channels and much less false encryption reports on known clear channels.

I started getting spurious reports of encryption on channels that are broadcast in the clear with .383 as well. It's only showing up in the groups window, and not in the log.

 

[redbeard]

I’m not sure if this is a neighbor related bug or not, but I’m seeing a site that has a neighbor on another system that is reporting the bandplan incorrectly for that neighbor site. It shows all entries as TDMA (slots=2) when there is still FDMA traffic on that system. My .p25data file from last monitoring that neighbor site directly seems correct with its mix of FDMA & TDMA. Is it DSD+ reporting wrong or is the site? Or somehow is it supposed to be this way?

To be more specific, site 942-1.61 on PA STARNet is reporting ICORRS site 152-1.1 as a neighbor but is reporting the bandplan for the ICORRS site as being all TDMA. What should be the correct ICORRS bandplan is what is shown in the RRDB currently. Shouldn’t both systems be sending the same bandplan? Or is this something configurable at the system level when setting up the ISSI between systems?

 

[mtindor]

I’m not sure if this is a neighbor related bug or not, but I’m seeing a site that has a neighbor on another system that is reporting the bandplan incorrectly for that neighbor site. It shows all entries as TDMA (slots=2) when there is still FDMA traffic on that system. My .p25data file from last monitoring that neighbor site directly seems correct with its mix of FDMA & TDMA. Is it DSD+ reporting wrong or is the site? Or somehow is it supposed to be this way?

To be more specific, site 942-1.61 on PA STARNet is reporting ICORRS site 152-1.1 as a neighbor but is reporting the bandplan for the ICORRS site as being all TDMA. What should be the correct ICORRS bandplan is what is shown in the RRDB currently. Shouldn’t both systems be sending the same bandplan? Or is this something configurable at the system level when setting up the ISSI between systems?

I don't know the answer, but I also would not expect DSDPlus to be fully aware of the bandplan of a neighboring site. There is no reason for all of that information to be sent over the site you are directly monitoring. The limited bandplan that you might see is likely deduced (by DSDPlus) solely based upon the control channel of the neighbor.

 

[slicerwizard]

site 942-1.61 on PA STARNet is reporting ICORRS site 152-1.1 as a neighbor but is reporting the bandplan for the ICORRS site as being all TDMA. What should be the correct ICORRS bandplan is what is shown in the RRDB currently. Shouldn’t both systems be sending the same bandplan? Or is this something configurable at the system level when setting up the ISSI between systems?

Have you looked at the console log to determine what bandplan information the STARNet site is broadcasting?

 

[GTR8000]

Shouldn’t both systems be sending the same bandplan? Or is this something configurable at the system level when setting up the ISSI between systems?

Not necessarily. ASTRO 25 systems allow for an ISSI Foreign Site to have a band plan manually programmed, which may a) differ from the Home system's band plan and b) may even differ from the original system's band plan as seen on it's own sites.

In other words, ICORRS could well have a unique band plan for the ISSI connect vs both the STARNet band plan as well as its own native band plan when looking at ICORRS sites.

To rule out a bug with DSD+, I would look at the raw control channel data for the Allegheny cell in Unitrunker or whatever, and see exactly what it's broadcasting as far as its own band plan as well as any ISSI peer site band plans.

 

[slicerwizard]

To rule out a bug with DSD+, I would look at the raw control channel data for the Allegheny cell in Unitrunker or whatever, and see exactly what it's broadcasting as far as its own band plan as well as any ISSI peer site band plans.

Why wouldn't you just look at the DSD+ console log? All of the IDEN_UP messages will be there.

 

[a417]

Anyone running 2.384 start seeing intermittent recordings from channels that are locked out?

 

[redbeard]

Not necessarily. ASTRO 25 systems allow for an ISSI Foreign Site to have a band plan manually programmed, which may a) differ from the Home system's band plan and b) may even differ from the original system's band plan as seen on it's own sites.

In other words, ICORRS could well have a unique band plan for the ISSI connect vs both the STARNet band plan as well as its own native band plan when looking at ICORRS sites.

To rule out a bug with DSD+, I would look at the raw control channel data for the Allegheny cell in Unitrunker or whatever, and see exactly what it's broadcasting as far as its own band plan as well as any ISSI peer site band plans.

I had a hunch it was decoded and displayed properly by DSD+ and that it was done on purpose by the system admins. From their point of view if the STARNet system is already 100% TDMA then they might as well stay that way and reduce system load when roaming on the foreign system.

 

[monstermatt2]

how do i get the dsd+ fastpass, i havn't gotten a email sisnce 2019, how do i get re-added to it

 

[mtindor]

how do i get the dsd+ fastpass, i havn't gotten a email sisnce 2019, how do i get re-added to it

It's Fast Lane, not fastpass. And you email dsdplusfastlane@gmail.com (using the same email address that you signed up with).

Mike

 

[RaleighGuy]

how do i get the dsd+ fastpass, i havn't gotten a email sisnce 2019, how do i get re-added to it

They do not send out emails anymore, except for the initial join, updates are done through the program. Make sure you save your password as you will need that same password for future updates.