Using the latest release of DSDPlus Fastlane, and working on a few trunked systems, where I've encountered three problems and wonder if anyone has any ideas how to address this, or if it is a bug in the software.
Problem 1:
There is a DMR Tier 3 system in the region, Azle Communications (Tier 3), that I have entered into the networks, sites and frequencies files identical to what is shown in RRDB (and identical to what my Uniden SDS100/200 reports). When I connect to a site on this system in DSD, it reports that the System ID is 13 (the other sources say its 12) and the site number is one higher than the other sources (1.2 instead of 1.1, etc.).
Here's my DSDPlus.networks:
Here's my DSDPlus.sites:
And finally here's my DSDPlus.frequencies (there are extra frequencies on site 3 as the original control channel has changed, and I was pinning down which is the new control channel):
Problem 2:
As you can see in my above example on Site 3, I have commented out 2 frequencies. This is because I've noticed an odd behavior where if I have a long list of frequencies with an LSN of 0, the program will loop on the first 2-3 frequencies and not go down the list any longer, even if there are frequencies with valid LSNs. I have experienced this not only on this Tier 3 system but on other Capacity Plus and Connect Plus systems as well.
Problem 3:
I have had multiple instances where DSDPlus will drift from one system to another. I was parked about 1/3 of a mile (.5 KM) from the Capacity Plus repeater on a campus, and there would be times when the "rest" channel would be on the same frequency as a Connect Plus control channel some 37 Miles (60 KM) away. With my mobile rig, there was just enough signal that it would switch to the Connect Plus system, dropping what I was trying to monitor. Once the "rest" channel on the Capacity Plus system shifted to another frequency, the behavior stopped (sadly there was only two frequencies on the Capacity Plus system, so I was still having the problem rather frequently). I have also seen similar behavior between Capacity Plus systems, if two of them are on a common frequency, that it will reload the other system configuration, which can throw of LSN's and groups.
The only way I can tell these systems apart is by their Color Codes (which are clearly different), but I can't see any way to "lock" DSDPlus to a specific Color Code.
If anyone can provide some input of how to workaround these problems, it would be appreciated.
Problem 1:
There is a DMR Tier 3 system in the region, Azle Communications (Tier 3), that I have entered into the networks, sites and frequencies files identical to what is shown in RRDB (and identical to what my Uniden SDS100/200 reports). When I connect to a site on this system in DSD, it reports that the System ID is 13 (the other sources say its 12) and the site number is one higher than the other sources (1.2 instead of 1.1, etc.).
Here's my DSDPlus.networks:
Code:
TIII, 12, "Azle Communications (Tier 3)"Here's my DSDPlus.sites:
Code:
TIII, 12, 1.1, "Weatherford"
TIII, 12, 1.2, "DFW Airport"
TIII, 12, 1.3, "Site 3"
TIII, 12, 1.4, "Dallas"
TIII, 12, 1.5, "Cleburne"And finally here's my DSDPlus.frequencies (there are extra frequencies on site 3 as the original control channel has changed, and I was pinning down which is the new control channel):
Code:
; Azle Communications (Tier 3)
TIII, 13, 1.1, 0, 464.8375, 0.0, 0
TIII, 12, 1.2, 0, 454.1625, 0.0, 0
TIII, 12, 1.3, 0, 454.3000, 0.0, 0
; TIII, 12, 1.3, 0, 451.1625, 0.0, 0
; TIII, 12, 1.3, 0, 464.2875, 0.0, 0
TIII, 12, 1.3, 0, 464.4500, 0.0, 0
TIII, 12, 1.4, 0, 484.8000, 0.0, 0
TIII, 12, 1.4, 0, 464.4625, 0.0, 0
TIII, 12, 1.5, 0, 461.4125, 0.0, 0Problem 2:
As you can see in my above example on Site 3, I have commented out 2 frequencies. This is because I've noticed an odd behavior where if I have a long list of frequencies with an LSN of 0, the program will loop on the first 2-3 frequencies and not go down the list any longer, even if there are frequencies with valid LSNs. I have experienced this not only on this Tier 3 system but on other Capacity Plus and Connect Plus systems as well.
Problem 3:
I have had multiple instances where DSDPlus will drift from one system to another. I was parked about 1/3 of a mile (.5 KM) from the Capacity Plus repeater on a campus, and there would be times when the "rest" channel would be on the same frequency as a Connect Plus control channel some 37 Miles (60 KM) away. With my mobile rig, there was just enough signal that it would switch to the Connect Plus system, dropping what I was trying to monitor. Once the "rest" channel on the Capacity Plus system shifted to another frequency, the behavior stopped (sadly there was only two frequencies on the Capacity Plus system, so I was still having the problem rather frequently). I have also seen similar behavior between Capacity Plus systems, if two of them are on a common frequency, that it will reload the other system configuration, which can throw of LSN's and groups.
The only way I can tell these systems apart is by their Color Codes (which are clearly different), but I can't see any way to "lock" DSDPlus to a specific Color Code.
If anyone can provide some input of how to workaround these problems, it would be appreciated.
