DSDPlus DSD+ 2.516 Released Sunday, January 12, 2025

[CanesFan95]

Change Log
----------

DSD+ 2.516

*** Make a backup copy of your DSDPlus.radios file. ***

Due to a file format change, this update will discard
all Motorola talker alias data that is present in your DSDPlus.radios file.
This update will reacquire your talker alias data from the DSD+ talker alias server.

Removed -t -T and -E command line parameters.

Added menu controls for console window and console log file.

Added some additional entries to the Call Priorities menu.

Added decoding of more DMR AVL messages.

Added option to include current site's neighbor list during control channel hunts.
This should enable auto-roaming when the current control channel becomes too weak to decode.
DSD+ will not use neighbor entries that have system IDs different than the current site.
This feature does not support all trunking types. It will work on P25 trunking sites and
is also likely to work on NEXEDGE DFA sites and TIII DFA sites.

Implemented a simplified version of the Motorola Trunking Talker Alias
decoding algorithm that Ilya Smirnov generously donated to the DSD+ project.
Motorola talker alias decoding is now done in DSD+ itself.

Decoded Harris trunking talker aliases and Motorola trunking talker aliases are
uploaded to the DSD+ talker alias server and are made available to other DSD+ users.

This update will query the DSD+ talker alias server for alias data.
This means that your copy of DSD+ does not need to see and decode every talker alias;
if another DSD+ FL user has already monitored transmissions from a given P25 trunking radio,
its alias data will be available to your copy of DSD+.
This can be helpful with radios that rarely transmit.

 

[dave3825]

Been going for almost 8 minutes downloading one after another. This is a real nice feature especially for those who travel.

edit
ran 26 minutes, downloaded and wrote 1300+ aliases

 

[BM82557]

Downloading once I disabled my VPN

 

[mtindor]

I did notice that after the initial time re-fetching the cleartext that was stored on the server, I have gotten a few new ones back from the server that filled in radios I had that never transmitted. If a radio transmitted on a site that user A monitors but only registered on a site that user B monitors, then once user A's instance sends the alias to the server, the server will send it back out to user B when user B's DSDPlus polls for it. Nice. I've often had a couple dozen RIDs for a particular system with no alias simply because the radios never transmitted while I was monitoring.

Keep in mind you won't get all known radio IDs from the server, only those that match radios you have in your .radios file. If somebody else monitored another site on the other end of a state and captured 3000 aliases and sent them to the server, those wont automatically get fetched into your radios file if you never personally monitored the radios on the site(s) that you monitor.

So for a system like Starcom21, with something like 18,000 aliases or more now, if somebody monitors a single site and has only ever "seen" 3000 radios on the system, they are only going to get the aliases for those 3000 aliases. 2.516 isn't going to miraculously send their instance all 18,000 aliases. After all, the server only sends them after DSDPlus contacts the server and says it needs them, to my knowledge. And a person's DSDPlus would only request ones that it already has radio IDs for it the DSDPlus.radios files.



Mike