devicelab
Whacker Extraordinaire
Bear with me there's a lot of info to digest here... So my local DoD P25 system changed their band plan from this:
to this:
Prior to realizing this change, I tried loading up DSD+ to monitor the trunk system via my usual scripts. It started out fine but then the CC changed to an obviously incorrect frequency. Here's the DSD live output:
So I just wanted to make sure this wasn't a bug. Shouldn't DSD+ be able to update the band plan (or at least verify if it has changed) so the end user doesn't have to figure this out manually..?
FWIW, I've seen this happen with other P25 systems and I always have to create a new P25data file. I don't mind doing this but this has to be fixable in code, no..?
Code:
Network: BEE00.14C ; DoD
Bandplan #0: Base=851.00625 Offset=-45 Spacing=6.25 BW=12.5
Bandplan #1: Base=762.00625 Offset=+30 Spacing=6.25 BW=12.5
Bandplan #2: Base=380. Offset=+10 Spacing=6.25 BW=12.5
Bandplan #3: Base=406. Offset=+9 Spacing=6.25 BW=12.5
Bandplan #4: Base=380. Offset=+10 Spacing=6.25 BW=12.5 Slots=2
Bandplan #5: Base=406. Offset=+9 Spacing=6.25 BW=12.5 Slots=2
Bandplan #6: Base=136. Offset=-8.6 Spacing=6.25 BW=12.5 Slots=2
Bandplan #7: Base=380. Offset=+10 Spacing=12.5 BW=12.5
Bandplan #8: Base=136. Offset=-8.6 Spacing=12.5 BW=12.5
Bandplan #9: Base=136. Offset=+4.6 Spacing=12.5 BW=12.5
Bandplan #10: Base=380. Offset=+9 Spacing=12.5 BW=12.5
to this:
Code:
Network: BEE00.14C ; DoD
Bandplan #0: Base=851.00625 Offset=-45 Spacing=6.25 BW=12.5
Bandplan #1: Base=762.00625 Offset=+30 Spacing=6.25 BW=12.5
Bandplan #2: Base=380.0125 Offset=+9.95 Spacing=25 BW=12.5
Bandplan #3: Base=380. Offset=+10 Spacing=12.5 BW=12.5
Prior to realizing this change, I tried loading up DSD+ to monitor the trunk system via my usual scripts. It started out fine but then the CC changed to an obviously incorrect frequency. Here's the DSD live output:
Code:
2022.12.31 12:59:57 Initiating FMPx link using link ID 20001...
2022.12.31 12:59:57 FMPx link established; link ID = 20001
2022.12.31 12:59:57 FMPx link established
2022.12.31 12:59:58 Sync:+P25p1 TSDU CRC FAIL
2022.12.31 12:59:59 Sync:+P25p1 TSDU ERR6 IDEN_UP ID=0 Base=851.00625 Offset=-45 Spacing=6.25 BW=12.5
2022.12.31 12:59:59 ERR17 IDEN_UP ID=1 Base=762.00625 Offset=+30 Spacing=6.25 BW=12.5
2022.12.31 12:59:59 ERR8 Opcode= 9 MFID=90 89 90 0F 00 00 00 00 00 00 00
2022.12.31 12:59:59 Sync:+P25p1 NAC:140 TSDU ERR2 SYNC_BCST US=0 IST=0 MMU=0 MC=0 VL=1 LTO=-5h 2022/12/31 20:58 uSlot=7460
2022.12.31 12:59:59 ERR6 NET_STS_BCST WACN ID=BEE00 SysID=14C LRA=0 CC=3-17 SC=70
2022.12.31 12:59:59 ERR6 SCCB RFSS=1 Site=2 [ch=3-44 SSC=04] [ch=3-44 SSC=04]
2022.12.31 12:59:59 Sync:+P25p1 TSDU ERR4 RFSS_STS_BCST SysID=14C LRA=0 RFSS=1 Site=2 CC=3-17 SC=70
2022.12.31 12:59:59 ERR6 SN-DATA_CHN_ANN_EXP DSO=00 TXch=none RXch=none DAC=0001
2022.12.31 12:59:59 ERR4 Opcode= 5 MFID=90 85 90 00 00 00 00 00 00 00 00
2022.12.31 12:59:59 Sync: no sync
2022.12.31 12:59:59 Sync:+P25p1 TSDU ERR5 NET_STS_BCST WACN ID=BEE00 SysID=14C LRA=0 CC=3-17 SC=70
2022.12.31 12:59:59 ERR6 SCCB RFSS=1 Site=2 [ch=406.275 SSC=04] [ch=406.275 SSC=04]
2022.12.31 12:59:59 ERR3 RFSS_STS_BCST SysID=14C LRA=0 RFSS=1 Site=2 CC=406.10625 SC=70
2022.12.31 12:59:59 Sync:+P25p1 TSDU ERR7 SN-DATA_CHN_ANN_EXP DSO=00 TXch=none RXch=none DAC=0001
2022.12.31 12:59:59 ERR9 Opcode= 5 MFID=90 05 90 00 00 00 00 00 00 00 00
2022.12.31 12:59:59 ERR12 ADJ_STS_BCST SysID=14C LRA=0 RFSS=1 Site=9 CC=409.1125 SC=70 CFVA=3: Networked
2022.12.31 13:00:00 Sync:+P25p1 TSDU CRC FAIL
2022.12.31 13:00:00 CRC FAIL
2022.12.31 13:00:00 CRC FAIL
2022.12.31 13:00:00 Sync:+P25p1 TSDU ERR8 ADJ_STS_BCST SysID=14C LRA=0 RFSS=1 Site=1 CC=406.0375 SC=70 CFVA=3: Networked
2022.12.31 13:00:00 ERR8 IDEN_UP ID=0 Base=851.00625 Offset=-45 Spacing=6.25 BW=12.5
2022.12.31 13:00:00 ERR10 IDEN_UP ID=1 Base=762.00625 Offset=+30 Spacing=6.25 BW=12.5
2022.12.31 13:00:00 Sync:+P25p1 TSDU ERR8 SCCB RFSS=1 Site=2 [ch=406.275 SSC=04] [ch=406.275 SSC=04]
2022.12.31 13:00:00 ERR6 RFSS_STS_BCST SysID=14C LRA=0 RFSS=1 Site=2 CC=406.10625 SC=70
2022.12.31 13:00:00 CRC FAIL
2022.12.31 13:00:00 Sync: no sync
So I just wanted to make sure this wasn't a bug. Shouldn't DSD+ be able to update the band plan (or at least verify if it has changed) so the end user doesn't have to figure this out manually..?
FWIW, I've seen this happen with other P25 systems and I always have to create a new P25data file. I don't mind doing this but this has to be fixable in code, no..?