DSDPlus DSDPlus 2.289 incorrectly assumes same bandplan for all sites in a system

[AM909]

WACN: BEE00
System: 14C
RFSS: 5
Site: 23 (NAC: 140)
has the bandplan:
Bandplan #0: Base=851.006250 Offset=-45 Spacing=6.25 BW=12.5
Bandplan #1: Base=762.006250 Offset=+30 Spacing=6.25 BW=12.5
Bandplan #2: Base=380.000000 Offset=+10 Spacing=6.25 BW=12.5
Bandplan #3: Base=406.000000 Offset=+9 Spacing=6.25 BW=12.5
Bandplan #4: Base=380.000000 Offset=+10 Spacing=6.25 BW=12.5 Slots=2
Bandplan #5: Base=406.000000 Offset=+9 Spacing=6.25 BW=12.5 Slots=2
Bandplan #6: Base=136.000000 Offset=-8.6 Spacing=6.25 BW=12.5 Slots=2
Bandplan #7: Base=380.000000 Offset=+10 Spacing=12.5 BW=12.5
Bandplan #8: Base=136.000000 Offset=-8.6 Spacing=12.5 BW=12.5
Bandplan #9: Base=136.000000 Offset=+4.6 Spacing=12.5 BW=12.5
Bandplan #10: Base=380.000000 Offset=+9 Spacing=12.5 BW=12.5

Starting with an empty DSDPlus.P25data file and then listening to the CC 385.9125 yields these (correct) entries in the file:
Site: 5.23 NAC=140
Channel 2-856: 385.350000 SCC
Channel 2-946: 385.912500 CC

------------------------------------------------
WACN: BEE00
System: 14C
RFSS: 5
Site: 6 (NAC: 14C)
(another site of the same system) has the different bandplan (with 12.5 kHz spacing for channel prefix 2):
Bandplan #0: Base=851.006250 Offset=-45 Spacing=6.25 BW=12.5
Bandplan #1: Base=762.006250 Offset=+30 Spacing=6.25 BW=12.5
Bandplan #2: Base=380.000000 Offset=+10 Spacing=12.5 BW=12.5
Bandplan #3: Base=380.000000 Offset=+10 Spacing=6.25 BW=12.5 Slots=2

Starting with an empty DSDPlus.P25data file and then listening to the CC 386.0625 yields these (correct) entries in the file:
Site: 5.6 NAC=14C
Channel 2-485: 386.062500 CC
Channel 2-497: 386.212500 SCC
Channel 2-667: 388.337500 SCC

------------------------------------------------
However, if you start with an empty DSDPlus.P25data file, then first listen to site BEE000.14C-5.23, it writes the first bandplan table to the file to be used for all of system BEE00-14C, with channel prefix #2 using 6.25 kHz spacing. If you then, without restarting DSDPlus, listen to site BEE000.14C-5.6 CC (on 386.062500), it incorrectly assumes the same 6.25 kHz channel numbers and displays the following in the Channel Activity window:
Ch Freq Target
2-485 383.03125 CC
2-497 383.10625 scc
2-667 384.16875 scc

(displaying the wrong frequencies for site 6).

Further, it does the opposite thing when writing the DSDPlus.P25data file, overwriting and using bandplan #2 with that received from site 6 (with 12.5 kHz spacing) and recalculating site 23's frequencies incorrectly (but site 6's correctly):

Network: BEE00.14C

Bandplan #0: Base=851.006250 Offset=-45 Spacing=6.25 BW=12.5
Bandplan #1: Base=762.006250 Offset=+30 Spacing=6.25 BW=12.5
Bandplan #2: Base=380.000000 Offset=+10 Spacing=12.5 BW=12.5
Bandplan #3: Base=380.000000 Offset=+10 Spacing=6.25 BW=12.5 Slots=2
Bandplan #4: Base=380.000000 Offset=+10 Spacing=6.25 BW=12.5 Slots=2
Bandplan #5: Base=406.000000 Offset=+9 Spacing=6.25 BW=12.5 Slots=2
Bandplan #6: Base=136.000000 Offset=-8.6 Spacing=6.25 BW=12.5 Slots=2
Bandplan #7: Base=380.000000 Offset=+10 Spacing=12.5 BW=12.5
Bandplan #8: Base=136.000000 Offset=-8.6 Spacing=12.5 BW=12.5
Bandplan #9: Base=136.000000 Offset=+4.6 Spacing=12.5 BW=12.5
Bandplan #10: Base=380.000000 Offset=+9 Spacing=12.5 BW=12.5

Site: 5.6 NAC=14C

Channel 2-485: 386.062500 CC
Channel 2-497: 386.212500 SCC
Channel 2-667: 388.337500 SCC
Channel 2-703: 388.787500 VOICE

Site: 5.23 NAC=140

Channel 2-856: 390.700000 SCC
Channel 2-946: 391.825000 CC

(I've eliminated unrelated neighbor information. Also note that it over-wrote bandplan prefix #3 with the (380 MHz) range from site 6 (the one from site 23 is for 406 MHz).)

If you restart after it writes the file, the Channel Activity window then does the same thing as the file, displaying the wrong frequencies for site 23 instead of site 6.

------------------------------------------------
In summary, the problem appears to be that DSDPlus assumes the same bandplan table for all sites in a system (unique key of WACN.System) instead of allowing separate bandplan tables for each site (unique key of WACN.System.RFSS.Site), and handles conflicts between information sent by the sites differently in the Channel Activity window than it does in the DSDPlus.P25data file.

(I have raw audio files and DSDPlus.P25data files of these tests if necessary)

P.S.: I don't know how old this problem is. I haven't used DSDPlus in a long time, and don't know if the issue existed back then.

 

[GTR8000]

The larger issue is that a Motorola ASTRO 25 system (which is what 14C is) is not supposed to allow different band plans per site. The screenshot below is straight out of the latest Fleetmapping and Band Plan Management Feature Guide.

Clearly something weird is going on with the 14C system, and they've somehow managed to apply a different band plan to some sites. Perhaps the system is fractured and some sites are on a different core/zone controller, even though they all use the BEE00-14C WACN/SysID.

 

[GTR8000]

Clearly something weird is going on with the 14C system, and they've somehow managed to apply a different band plan to some sites. Perhaps the system is fractured and some sites are on a different core/zone controller, even though they all use the BEE00-14C WACN/SysID.

One other possibility is the following, which I hadn't even thought of originally, but was subsequently emailed to me:

The band plan is a system wide setting, so every site connected to the core will broadcast the same one. If a site is in site trunking it will broadcast the band plan that’s programmed in the site controller.

I “suspect” the sites broadcasting a different one are in site trunking and have a different band plan in the site controller.

Of course that doesn't do much good if DSD+ is unwilling to accommodate multiple band plans per system, which while technically correct, would inhibit some functionality when you run into an oddball situation like this.

 

[AM909]

There are a number of these multi-state systems that I'd bet don't all share the same controller. It should not be hard to find other instances like this. It's not unusual to find systems that implement things differently than the original design spec, and the tools should probably follow the implementation unless there is a good reason (like the implementation doesn't work and is going to be fixed soon – apparently not so in this case). I'll note that UniTrunker associates the band plan table with the site:

 

[GTR8000]

It's the exception, not the rule. And yes, I'm aware that Unitrunker stores the band plan on a per-site basis. Perhaps you need to reach out to the DSD+ authors directly to request a change in the software's behavior to accommodate these rare instances.