DSDPlus DSD+ 2.457 Available

dave3825

dave3825

* * * * * * * * * * * *
Premium Subscriber
Joined
Feb 17, 2003
Messages
8,197
Location
Suffolk County NY
DSD+ 2.457

All "TIII" support has been excised from DSD+. The program now red-flags
any data file entry that has "TIII" as the protocol string.
No DMR system/site will be reported as "TIII".

When a TIII site is monitored, DSD+ will make a determination as to whether
a system is following the TIII standards. Most systems follow the standards and
DSD+ will display the system type as "TIIIStd (Auto)".

For Motorola CapMAX systems, which do not follow the TIII standards,
DSD+ will display the system type as "TIIInonStd (Auto)".

The "(Auto)" notation shows that DSD+ has automatically made the system type classification.

For non-standard TIII systems that DSD+ does not correctly classify,
such as those made by SELEX, the DSD+ Control menu provides a mechanism
to force the system type to "TIIInonStd", or back to "TIIIStd", if desired.

The proper method to force the use of the correct TIII system type by DSD+ is to feed
signals to DSD+ via an FMPx direct link or TCP link and to load the DSDPlus.frequencies file
with accurate system type, system ID and site frequency data for every monitored TIII site.
If this is done, DSD+ will use the data to reliably select TIII system types.
Also, the DSDPlus.frequencies file data will override the TIII system type selection option
in the DSD+ Control menu.

The system type being used by DSD+ controls how DSD+ interprets the 14 bit SysCode values
that TIII systems broadcast.

Standards-compliant systems use the full addressing space provided by the bit fields
embedded in a TIII SysCode and support an "Area" field.
DSD+ displays TIIIStd site numbers as area#.site# (examples: 1.1, 1.2, 2.1, ...)

Systems that do not adhere to the TIII standards do not use the full address space
that SysCode bit fields provide, nor do they support an "Area" value.
DSD+ displays TIIInonStd site numbers as site# only (examples: 1, 2, 3, ...)

All data file entries for TIII systems should include network model information.
This takes the form of a single character - T, S, L, H (Tiny, Small, Large, Huge)
and is the same as the network model code that DSD+ displays in the event log window
while monitoring a TIII system. The network model code should be entered in all
TIII-related data file entries immediately before the network ID value.

Network ID prefixes can be used to disambiguate TIII networks that use the same network ID.
Prefix values should be in the range 1 to 4095. We recommend using the first three or four
digits of the page number of the Radioreference.com database entry for a given network.

Network ID values should match those displayed by DSD+ when monitoring a system.

Site number values should match those displayed by DSD+ when monitoring a system.
TIIIStd site numbers must include an area value. TIIInonStd site numbers must not.

Example .networks, .sites and .frequencies entries:

TIIIStd L13 "Coyote LLC" ; Protocol NetworkModel&ID NetworkAlias
TIIIStd L13 1.1 "HQ" ; Protocol NetworkModel&ID Area.Site SiteAlias
TIIIStd L13 1.1 1 454.7 0.0 0 ; Protocol NetworkModel&ID Area.Site Chan# ...
TIIIStd L13 1.1 2 454.8 0.0 0 ; Protocol NetworkModel&ID Area.Site Chan# ...

TIIInonStd L1234:13 "Road Runner Inc" ; Protocol NetworkModel&ID NetworkAlias
TIIInonStd L1234:13 1 "Home Base" ; Protocol NetworkModel&ID Area.Site SiteAlias
TIIInonStd L1234:13 1 57 462.0125 0.0 0 ; Protocol NetworkModel&ID Area.Site Chan# ...
TIIInonStd L1234:13 9 84 464.9500 0.0 0 ; Protocol NetworkModel&ID Area.Site Chan# ...

In order to comply with the above rules, ALL data file entries relating to TIII systems
will need to be edited by the user. Before commencing, YOU SHOULD BACK UP ALL DATA FILES.
This includes the following files:

DSDPlus.networks
DSDPlus.sites
DSDPlus.siteLoader
DSDPlus.frequencies
DSDPlus.groups
DSDPlus.radios

These files can be edited while DSD+ is running, preferably while DSD+ is not monitoring
any signals. Pay close attention to the error messages that DSD+ writes to the console log
when you save an edited file. They will guide you in your editing efforts.


FMPP 1.24

Fixed stalling at startup when using RSP1A devices.
 
dave3825

dave3825

* * * * * * * * * * * *
Premium Subscriber
Joined
Feb 17, 2003
Messages
8,197
Location
Suffolk County NY
dave3825 said:
In order to comply with the above rules, ALL data file entries relating to TIII systems
will need to be edited by the user. Before commencing, YOU SHOULD BACK UP ALL DATA FILES.
This includes the following files:

DSDPlus.networks
DSDPlus.sites
DSDPlus.siteLoader
DSDPlus.frequencies
DSDPlus.groups
DSDPlus.radios

These files can be edited while DSD+ is running, preferably while DSD+ is not monitoring
any signals. Pay close attention to the error messages that DSD+ writes to the console log
when you save an edited file. They will guide you in your editing efforts.
Click to expand...

Those files above all have new wording in them as far as line formatting for TIII related entries so be sure to download the newest base files and have a look at them. Obviously do not overwrite your data files and backup all of them before making changes....

1703690489146.png
 
M

morfis

Member
Joined
Jan 24, 2004
Messages
1,669
mtindor said:
There is sure to be some botching (of the files), and b*tching as well :)
Click to expand...
There is :(

So far it's also causing problems for one of my TIII networks as it mostly says it's nonStd but has around 50 radios which it's also flicking between that and Std giving a whole host of log erros due to ambiguity.

More testing when my blood sugar is better....
 
F

Fredo68

Member
Joined
Jun 7, 2020
Messages
36
The trunked systems around here are mostly TierIII. I typed in hundreds of lines manually as my country isn't really on the RR database. (And again with SDRTrunk when they changed to LCNs.) Dull, but I only had to do it once, right?

If I update will I have to manually modify the same hundreds of lines?

(I did send full details of a busy 140 channel network to the database. It's a shame they only added the 10 control channels. I had hoped my labours would help others to avoid repeating them.)
 
seagravebuff60

seagravebuff60

Office Assistant
Feed Provider
Joined
Jun 11, 2016
Messages
967
Location
New York State
I just Updated to the new version. Got hundreds of Errors in the DSD Window when starting, Maybe even thousands. It took a full minute and a half to auto-scroll through the errors. It looks like I have to update all my DSD+ files again with the correct info.

So far, there have been no issues with the 3 DMR T3 systems I'm monitoring.
 
dave3825

dave3825

* * * * * * * * * * * *
Premium Subscriber
Joined
Feb 17, 2003
Messages
8,197
Location
Suffolk County NY
Fredo68 said:
I typed in hundreds of lines manually as my country isn't really on the RR database.
Click to expand...

Fredo68 said:
If I update will I have to manually modify the same hundreds of lines?
Click to expand...

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

Backup your data files prior.
 
mtindor

mtindor

OH/WV DB Admin
Database Admin
Joined
Dec 5, 2006
Messages
10,728
Location
Carroll Co OH / EN90LN
Fredo68 said:
The trunked systems around here are mostly TierIII. I typed in hundreds of lines manually as my country isn't really on the RR database. (And again with SDRTrunk when they changed to LCNs.) Dull, but I only had to do it once, right?

If I update will I have to manually modify the same hundreds of lines?

(I did send full details of a busy 140 channel network to the database. It's a shame they only added the 10 control channels. I had hoped my labours would help others to avoid repeating them.)
Click to expand...

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.
 
GTR8000

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
15,857
Location
BEE00
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. 🤦‍♂️

Code: 
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

Code: 
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
 
mcjones2013

mcjones2013

Radio Communications Enthusiast
Premium Subscriber
Joined
Sep 15, 2012
Messages
754
Location
Sacramento, CA
Just to confirm, there's no way to no which specific flavor of Tier III (i.e. Motorola) is broadcasting via DSDPlus after this update?
 
S

scottjpalmer

Member
Joined
May 4, 2020
Messages
48
So far, using a clean install with blank data files I'm seeing the 3 Motorola systems here identify as TIIInonStd [Auto] (MOT). Of the 3 other systems, I know all 3 are Tait however 2 are identifying as TIIIStd [Auto] and 1 is identifying as TIIIStd [Auto] (Tait).

Great to see the auto functionality getting it right!
 
T

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,857
Is classifying TIII as standard or non-standard really needed?
Wouldn't it be easier to just state it's "Trunking" which is all TIII really is.

The DMR "Standards" allow for many varied ways to implement any type of DMR TIII (Trunking) system which is what we see out there:
  • CON+
  • CAP+
  • CapMax
  • Tait (Full, Express6(20), Access)
  • XPT
  • Motorola TIII
  • Other?
Most of these variations (if not all) require a separate propriety "standards" to correctly implement.
Identifying any of the manufacturer specific implementations is where is becoming trickier to do. You just can't always use the ShortLC to do this.
 
GTR8000

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
15,857
Location
BEE00
thewraith2008 said:
Is classifying TIII as standard or non-standard really needed?
Click to expand...
Yes, it is. Why? Because of the way the Site ID's are presented. For example a "standard" Hytera T3 system uses the Area.Site format, (e.g. 1.7). Contrast that with a "non-standard" Selex brand T3 system, which does not use the Area as part of the Site ID instead opting for a simple integer (e.g. 101). DSD+ was previously applying the "standard" formatting to all T3 systems, resulting in data that wasn't quite accurate.

It's all explained in the release notes for 2.457.
 
N

noamlivne

Member
Joined
Sep 7, 2012
Messages
183
GTR8000 said:
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. 🤦‍♂️

Code: 
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

Code: 
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
Click to expand...
Yep.
I see it too unfortunately.
 
icarus1963

icarus1963

Member
Premium Subscriber
Joined
Dec 13, 2009
Messages
182
Location
Brantford, Ontario
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

1703770934057.png
 
You must log in or register to reply here.

Similar threads

VA3ADP
DSDPlus DSD+ FL 2.465 and TIII Error
Replies
8
Views
769
mtindor
mtindor
P
Crazy with TIII systems, need help
Replies
8
Views
748
cg
C
A
DSDPlus FL & DMR Cap+ MOTOTRBO woes
Replies
6
Views
615
CanesFan95
C
N9JIG
Scanner Tales: Chasing Trunking Systems
Replies
5
Views
1K
K9JDN
K9JDN
F
DSDPlus Please make suggestions or corrections to my "Capacity Max Discovery Process"
Replies
1
Views
664
cg
C
Top