DSDPlus not pulling RAN consistently on NXDN Conventional

[mrlindstrom]

I'm on the latest fastlane and have had DSD+ scanning a list of conventional NXDN frequencies that are in use by the local fire departments. I've noticed that it is not consistently showing the proper RAN when audio is coming through. It will show a RAN of 1 instead of the actual RAN. I parked my SDS100 on the same frequency and it showed the proper RAN (63). Sometimes it does show correct RAN, but I'd say 99% of the time right now it's been showing RAN 1. Are there any known issues with DSD+ where it won't display (or tag the resulting per call audio file) with the RAN that is in use?

For clarity this is NXDN48 and the frequencies are for "North Com" on Harris County, Texas (TX) Scanner Frequencies and Radio Frequency Reference

 

[Whiskey3JMC]

So this is the frequency in question?
460.625 465.625 WQWZ977 RM 63 RAN COM 3 Fire Resp COM 3 Fire Response NXDN48 Fire-Tac

How strong is the signal? No other NXDN stations on the same frequency within range to you? Are you hearing voice transmissions from the expected fire response channel when RAN 1 is displayed?

 

[mrlindstrom]

So this is the frequency in question?
460.625 465.625 WQWZ977 RM 63 RAN COM 3 Fire Resp COM 3 Fire Response NXDN48 Fire-Tac

How strong is the signal? No other NXDN stations on the same frequency within range to you? Are you hearing voice transmissions from the expected fire response channel when RAN 1 is displayed?

Yes that is the correct frequency. Signal strength is good, I'm getting decodes of the talker aliases and the audio matches the comms I am expecting to hear. Here's a snippet from the DSDPlus.event file from overnight:

2025/05/03  22:18:31  Freq=460.625000  RAN=63  Group call; RID=3932 [....-A]
2025/05/03  22:18:34  Freq=460.625000  From .frequencies file, line 90: Setting network ID, site number.
2025/05/03  22:18:34  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:18:34  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:18:34  Freq=460.625000  RAN=1  Group call; RID=1 [NORTH COMM]    1s
2025/05/03  22:18:38  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:18:38  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:18:38  Freq=460.625000  RAN=1  Group call; RID=3932 [E302-A]    3s
2025/05/03  22:18:45  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:18:45  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:18:46  Freq=460.625000  RAN=1  Group call; RID=1 [NORTH COMM]    2s
2025/05/03  22:18:52  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:18:52  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:18:53  Freq=460.625000  RAN=1  Group call; RID=1 [NORTH COMM]    2s
2025/05/03  22:19:12  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:19:12  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:19:15  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:19:15  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:19:16  Freq=460.625000  RAN=1  Group call; RID=3932 [E302-A]    3s
2025/05/03  22:19:26  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:19:26  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:19:26  Freq=460.625000  RAN=1  Group call; RID=1 [NORTH COMM]    1s
2025/05/03  22:19:34  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:19:34  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:19:34  Freq=460.625000  RAN=1  Group call; RID=3932 [E302-A]    10s
2025/05/03  22:19:49  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:19:49  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:19:49  Freq=460.625000  RAN=1  Group call; RID=1 [NORTH COMM]    2s
2025/05/03  22:21:49  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:21:49  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:21:49  Freq=460.625000  RAN=1  Group call; RID=3932 [E302-A]
2025/05/03  22:21:53  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:21:53  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:21:53  Freq=460.625000  RAN=1  Group call; RID=1 [NORTH COMM]
2025/05/03  22:21:55  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:21:55  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:21:56  Freq=460.625000  RAN=1  Group call; RID=3932 [E302-A]    2s
2025/05/03  22:22:02  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/03  22:22:02  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/03  22:22:02  Freq=460.625000  RAN=1  Group call; RID=1 [NORTH COMM]    1s
2025/05/04  00:10:02  Freq=453.375000  Checking for updates
2025/05/04  00:10:03  Freq=453.375000  You are running the most recent copy of DSD+
2025/05/04  00:33:51  Freq=460.625000  RAN=63  Group call; RID=1 [NORTH COMM]    5s
2025/05/04  00:34:06  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/04  00:34:06  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/04  00:34:07  Freq=460.625000  RAN=1  Group call; RID=7021 [Engine 72]    3s
2025/05/04  01:29:05  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/04  01:29:05  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/04  02:37:15  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/04  02:37:15  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/04  02:37:16  Freq=460.625000  RAN=1  Group call; RID=1 [NORTH COMM]    5s
2025/05/04  04:02:24  Freq=460.625000  Current network:  1112  North COM Fire Response
2025/05/04  04:02:24  Freq=460.625000  RAN=1  Current site:  1112-1
2025/05/04  04:02:24  Freq=460.625000  RAN=1  Group call; RID=1 [NORTH COMM]    16s

Edited to add: Ignore the Network/Site numbers, those are dummy entries in my frequencies/sites files.

 

[lwvmobile]

What does the console output say? I've seen some conventional NXDN systems signal one RAN value during actual activity, and RAN 63 on the IDLE beacon bursts.

19:49:04 Sync: NXDN48  RDCH  Voice  RAN 07 PF 4/4 VCALL
 Group Call - Half Duplex 4800bps/EHR (00) - Src=238 - Dst/TG=1
19:49:04 Sync: NXDN48  RDCH  Voice  RAN 07 PF 1/4
19:49:04 Sync: NXDN48  RDCH  Voice  RAN 07 PF 2/4
19:49:04 Sync: NXDN48  RDCH  Voice  RAN 07 PF 3/4
19:49:04 Sync: NXDN48  RDCH  Voice  RAN 07 PF 4/4 VCALL
 Group Call - Half Duplex 4800bps/EHR (00) - Src=238 - Dst/TG=1
19:49:04 Sync: NXDN48  RDCH  Voice  RAN 07 PF 1/4
19:49:04 Sync: NXDN48  RDCH  Voice  RAN 07 PF 2/4
19:49:04 Sync: NXDN48  RDCH  Voice  RAN 07 PF 3/4
19:49:05 Sync: NXDN48  RDCH  Voice  RAN 07 PF 4/4 VCALL
 Group Call - Half Duplex 4800bps/EHR (00) - Src=238 - Dst/TG=1
19:49:05 Sync: NXDN48  RDCH  Data   RAN 07 PF 1/1 IDLE TX_REL
 Group Call -   Transmission Release  - Src=238 - Dst/TG=1
19:49:05 Sync: NXDN48  RDCH  Data   RAN 07 PF 1/1 IDLE IDLE
19:49:05 Sync: NXDN48  RDCH  Data   RAN 07 PF 1/1 IDLE IDLE
19:49:05 Sync: NXDN48  RDCH  Data   RAN 07 PF 1/1 IDLE IDLE
19:49:05 Sync: NXDN48  RDCH  Data   RAN 07 PF 1/1 IDLE TX_REL
 Idle -   Transmission Release  - Src=1006 - Dst/TG=0
19:49:06 Sync: NXDN48  RDCH  Data   RAN 07 PF 1/1 IDLE IDLE IDLE
19:49:06 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE
19:49:06 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE IDLE
19:49:06 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE
19:49:06 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE TX_REL
 Idle -   Transmission Release  - Src=1006 - Dst/TG=0
19:49:07 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE IDLE
19:49:07 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE IDLE
19:49:07 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE
19:49:07 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE
19:49:07 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE TX_REL
 Idle -   Transmission Release  - Src=1006 - Dst/TG=0
19:49:07 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE IDLE
19:49:08 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE
19:49:08 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE
19:49:08 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE IDLE IDLE
19:49:08 Sync: NXDN48  RDCH  Data   RAN 63 PF 1/1 IDLE TX_REL

 

[RaleighGuy]

I'm on the latest fastlane and have had DSD+ scanning a list of conventional NXDN frequencies that are in use by the local fire departments. I've noticed that it is not consistently showing the proper RAN when audio is coming through.

Just as a reminder, DSD+ isn't designed to act like a scanner, though it does scan. One possible cause may be that when scanning you are losing a Milli-second of transmission that causes the issue. Try staying on one frequency for a day and see if it is still a problem, if it displays the correct RAN then scanning is your issue.

 

[mrlindstrom]

I'd say it's definitely seeing the RAN, but it's not updating it for some reason.

2025.05.04 18:25:16  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:16  Sync:+NXDN48 CB VOICE     e:7r5r7r7m
2025.05.04 18:25:16  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:16  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:16  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:16  Sync:+NXDN48 CB VOICE        VCall  Group  RID=1
2025.05.04 18:25:16  RAN=63                 
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE        ALIAS
2025.05.04 18:25:17  RAN=63                 
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE     e:7r4r7r6m
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE     e:1
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE        ALIAS
2025.05.04 18:25:17  RAN=63                 
2025.05.04 18:25:17  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE        VCall  Group  RID=1
2025.05.04 18:25:18  RAN=63                 
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE        ALIAS
2025.05.04 18:25:18  RAN=63                 
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE        VCall  Group  RID=1
2025.05.04 18:25:18  RAN=63                 
2025.05.04 18:25:18  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE        ALIAS
2025.05.04 18:25:19  RAN=63                 
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE        VCall  Group  RID=1
2025.05.04 18:25:19  RAN=63                 
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE        ALIAS
2025.05.04 18:25:19  RAN=63                 
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:19  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE        VCall  Group  RID=1
2025.05.04 18:25:20  RAN=63                 
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE        ALIAS
2025.05.04 18:25:20  RAN=63                 
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE        VCall  Group  RID=1
2025.05.04 18:25:20  RAN=63                 
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:20  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:21  Sync:+NXDN48 CB VOICE   
2025.05.04 18:25:21  Sync:+NXDN48 CB DATA         TX_REL          Group Call Src=1
2025.05.04 18:25:21                               TX_REL          Group Call Src=1
2025.05.04 18:25:21  Sync:+NXDN48 CB DATA         TX_REL          Group Call Src=1
2025.05.04 18:25:21                               TX_REL          Group Call Src=1
2025.05.04 18:25:21  Sync:+NXDN48 CB DATA         TX_REL          Group Call Src=1
2025.05.04 18:25:21                         ERR1  TX_REL          Group Call Src=1

And here's the event log from that call:

2025/05/04  18:25:16  Freq=460.625000  RAN=1  Group call; RID=1 [NORTH COMM]    4s

 

[mtindor]

If you are scanning conventionally with DSDPlus, especially an NXDN48 freq, make sure you have the bandwidth set to 4.0 on that entry. NXDN48 is pretty picky when it comes to noise. If you've got 7.6 / 9.5 / 12.5 / 22 as a BW setting for that freq instead of 4.0, you are going to notice a difference.

 

[dave3825]

2025/05/03 22:18:31 Freq=460.625000 RAN=63 Group call; RID=3932 [....-A]
2025/05/03 22:18:34 Freq=460.625000 From .frequencies file, line 90: Setting network ID, site number.
2025/05/03 22:18:34 Freq=460.625000 Current network: 1112 North COM Fire Response
2025/05/03 22:18:34 Freq=460.625000 RAN=1 Current site: 1112-1
2025/05/03 22:18:34 Freq=460.625000 RAN=1 Group call; RID=1 [NORTH COMM] 1s

Edited to add: Ignore the Network/Site numbers, those are dummy entries in my frequencies/sites files.

If scanning conventional freqs with a scan list, you do not need dummy entries. Get rid of line 90 in your freq file and any other dummy info added (network and sites file) and see what you get.

 

[mrlindstrom]

They serve a purpose for my post processing and ingesting of the audio into other software, so for now I have to leave them.

 

[dave3825]

Understood but if you ditch line 90, and then it displays the correct Ran consistently, then you can explore other audio recording options.

 

[DaveNF2G]

They serve a purpose for my post processing and ingesting of the audio into other software, so for now I have to leave them.

Just comment it out and run a test.