DSDPlus DSD+ 2.457 Available

[mtindor]

DSDPlus.Networks
TIIInonStd,L6,"name of system"

DSDPlus.Sites
TIIInonStd,L6,13,"name of site"

DSDPlus.Frequencies
TIIInonStd,L6,13,1383,422.65,0.0,0

You have L6-13 in your file instead of L6,13

 

[icarus1963]

DSDPlus.Networks
TIIInonStd,L6,"name of system"

DSDPlus.Sites
TIIInonStd,L6,13,"name of site"

DSDPlus.Frequencies
TIIInonStd,L6,13,1383,422.65,0.0,0

You have L6-13 in your file instead of L6,13

Thanks for the help. Changed everything over, and all is as it should be.

Andy

 

[Fredo68]

If you utilize the find/replace feature in Notepad++, even hundreds of lines can be changed in no time.

Backup your data files prior.

I'm aware of the replace function but would need to establish whether each network is 'std' or 'nonstd'. I replaced in the .frequencies files for the largest network with no problem but a text replace of the 10200 TIII radios in the .radios files has destroyed it. Yes it's backed up so I can restore it back to the version that gives a 1000 errors a minute.

Some of the networks are local and some are from servers. Without deleting everything and starting again, I'm not sure I can establish what every setting should be? If I don't delete I'm back to the constant stream of errors.

 

[Fredo68]

Just send a message through the ticketing system and ask the admin to update the LSNs for each site. Those are LSNs that you submitted. So just go to your ticket in RR and add note requesting that the admin add the associated LSNs for each site.

I previously sent everything I had spent a lot of time working on. Control channels Network IDs, LSNs and LCNs. If they didn't want it then, why would they want it now?

 

[seagravebuff60]

Hi All
Can anybody help me get with my DSD+ FL frequency file. Since the update , I cant seem to configure my frequency file correctly.
I keep receiving the error below. Any help would be appreciated.

Andy

View attachment 153738

Yeah. Looks like you have 6 as the site and the Network format is wrong

Try this:

TIIInonStd, L6, 13, 1383, 422.6500, 0.0, 0

 

[bravo14]

Around 130 am bands were open and I was picking up a T3 system from Gainesville (Clay Electric). It showed TIII no TIIIStd or TIIInonStd. I don't have any TIII in my area expect 1 county north of me I'm too far to pick up the 800 unless I drive like 20-30 miles to see if shows TIII or TIIIStd or TIIInonStd.

 

[cg]

How do you determine which is correct? Is what Uniden shows for system ID ever wrong?

I used my 996P2 (which still has the Control Channel Only option for searching) for testing. I go to each CC frequency of the TierIII systems that I can receive and ran each on the 996P2 and on DSDPlus v2.457 (I have run them on all the previous DSDPlus versions).

If I go by Uniden having it correct, then Tait, Hytera, and Motorola CapMax system that I have here would all be non standard in order to get DSDPlus to report the same info.
The Tait system (Eversource) shows no system ID on the Uniden. In DSDPlus, to match the site number, I use TIIInonStd and it shows L0, 38

The Hytera and the Tait under the old versions of DSDPlus did not have a Site 1.1, it always started at 1.2 which I thought was strange.

 

[slicerwizard]

How do you determine which is correct? Is what Uniden shows for system ID ever wrong?

What Uniden shows for TIII network IDs and site numbers is going to be correct for nonstandard systems (Motorola and Selex ES) and incorrect for standard systems (Hytera, Tait, ...)

The Tait system (Eversource) shows no system ID on the Uniden. In DSDPlus, to match the site number, I use TIIInonStd and it shows L0, 38

Which is a clear indicator that it's a standard system. No-one uses a network ID of zero. The TIII standard doesn't allow it and the nonstandard vendors (like Motorola) don't support it. Which means no vendor allows TIII NID 0.

Surely Motorola had a seat at the table when the TIII standard was being hashed out? So why are they deviating from it? Twenty years ago, I saw some really moronic ****e come from Mother Moto with their PassPort radios and Harmony systems, largely due to noob engineers/coders and it seems that little has changed over the years.

BTW, I've run into the same problem as another poster - there are some TIII systems that are too far away for me to check their model type; that'll take a drive some day. So for now, I've just edited all of their data entries as TIIIStd and Tiny and made a todo list to fix them when I can. Finally back to zero errors at startup.

 

[cg]

It still makes me wonder why two different manufacturer's systems would not have a site 1.1 (or why would they use x.y as a way to number a site?).

 

[bravo14]

@cg not sure if this helps.
On Clay Electric System in FL. TIII DSD > SDS
dsd Site 1.2 > sds site 1
dsd Site 1.3 > sds site 2
dsd Site 2.2 > sds site 5
dsd Site 2.3 > sds site 6

 

[slicerwizard]

It still makes me wonder why two different manufacturer's systems would not have a site 1.1 (or why would they use x.y as a way to number a site?).

P25 systems use x.y (RFSS.site). Same deal with TIII's (service?)area.site, so doesn't seem to be particularly odd.

 

[aps_ak]

Anyone else getting a trojan alert/quarantine from this version on Windows 10 OS? I have had to revert back for now.

 

[KevinC]

What Uniden shows for TIII network IDs and site numbers is going to be correct for nonstandard systems (Motorola and Selex ES) and incorrect for standard systems (Hytera, Tait, ...)


Which is a clear indicator that it's a standard system. No-one uses a network ID of zero. The TIII standard doesn't allow it and the nonstandard vendors (like Motorola) don't support it. Which means no vendor allows TIII NID 0.

Surely Motorola had a seat at the table when the TIII standard was being hashed out? So why are they deviating from it? Twenty years ago, I saw some really moronic ****e come from Mother Moto with their PassPort radios and Harmony systems, largely due to noob engineers/coders and it seems that little has changed over the years.

BTW, I've run into the same problem as another poster - there are some TIII systems that are too far away for me to check their model type; that'll take a drive some day. So for now, I've just edited all of their data entries as TIIIStd and Tiny and made a todo list to fix them when I can. Finally back to zero errors at startup.

I'd blame Trident Microsystems for PassPort.

 

[RaleighGuy]

Anyone else getting a trojan alert/quarantine from this version on Windows 10 OS? I have had to revert back for now.View attachment 153782

Those pop up from time to time false positives, there is no issue with it.

 

[dave3825]

Anyone else getting a trojan alert/quarantine from this version on Windows 10 OS?

Yes, but I trust the author so I ignore

I have had to revert back for now.

no need.

 

[slicerwizard]

I'd blame Trident Microsystems for PassPort.

Trident didn't create Motorola's subscriber radio firmware. For starters, bugs that would cause the radios to auto-key over other system users. Rather similar to the local losers that have nothing better to do than harass and jam hams and commercial system operators.

 

[fozz3d]

Anyone else seeing an issue with TIII sites in CC Monitor (1 of 2) mode, where the Current site: messages scroll endlessly? I have to switch to Combined CC/VC Monitor mode to get it to stop. This is occurring with both TIIIStd as well as TIIInonStd system types, and yes all of my files have been updated to account for the new changes in 2.457, so that's not the issue. And yes, I know about the DSD+ email address and will report the bug once I get confirmation that others are seeing the same results. Jeez, all these disclaimers just to ward off the inevitable "Did you try this???" posts. 🤦‍♂️

2023/12/27  12:56:10  Freq=478.825000  DCC=1  Found control channel
2023/12/27  12:56:10  Freq=478.825000  Current network:  L5  OneVoice MAX
2023/12/27  12:56:10  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:10  Freq=478.825000  Current network:  L6
2023/12/27  12:56:10  Freq=478.825000  Current site:  L6-14.8
2023/12/27  12:56:10  Freq=478.825000  From .frequencies file, line 57: Forcing TIII network type; Setting network ID, site number.
2023/12/27  12:56:10  Freq=478.825000  Current network:  L5  OneVoice MAX
2023/12/27  12:56:10  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:10  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:10  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:10  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:10  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:10  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:11  Freq=478.825000  Current site:  L5-111  Pomona
2023/12/27  12:56:12  Freq=478.825000  Current site:  L5-111  Pomona

2023/12/27  12:56:44  Freq=452.625000  DCC=1  Found control channel
2023/12/27  12:56:44  Freq=452.625000  Current network:  L13  East Mountain
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  From .frequencies file, line 70: Forcing TIII network type; Setting network ID, site number.
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:44  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:45  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:46  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:46  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:46  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:46  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:46  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:46  Freq=452.625000  Current site:  L13-1.2  Esopus
2023/12/27  12:56:46  Freq=452.625000  Current site:  L13-1.2  Esopus

I too have the Current Site scroll of death. Checked and double checked everything, no errors in event log.
Is anyone from DSD on here or just send an email to them (with logs etc of course)

 

[radionut44]

Just updated to version 457. FFmp24-cc.bat works fine. When I run 1R.bat I get a Win10 message that This app cannot run on your PC. Contact software publisher for another version or words to that effect. Pasted in the DsdPlus.exe from version 448 and all is happy. Has anyone else had this problem and found a solution?

 

[mtindor]

Just updated to version 457. FFmp24-cc.bat works fine. When I run 1R.bat I get a Win10 message that This app cannot run on your PC. Contact software publisher for another version or words to that effect. Pasted in the DsdPlus.exe from version 448 and all is happy. Has anyone else had this problem and found a solution?

Your AV software is probably preventing the newer version of DSDPlus.exe from running. You should probably put the newest DSDPlus.exe file in your DSDPlus folder, and then just navigate directly to DSDPlus.exe and click on it. Then you will know for sure if that is what the problem is -- and you'll be able to tell it to run on the PC. After that it'll remember (or should) that you want to allow it to run on the PC.

 

[DaveNF2G]

I plan to either hold on the current version of DSDPlus (2.448) or only update to the new version in the directories with TIII systems. Or maybe I'll just wait until another debugged version is released.