DSD+ Fastlane Audio Deficient

[rkillins]

I'm unable to figure this out without some help from the experienced folk. I am trying to monitor both a CAP+ and NXDN NexEdge system. Everything decodes properly (I can see the group calls populate the channel activity window and event log., I just can't hear the audio transmissions. Using DSD+ updated Fastlane.

Speakers work, I can easily hear PC system sounds and audio media.
My VC Event Window, Output menu has Speakers (Realtek(r) Audio) checked.

Here is the contents of my VC.bat for the NXDN system:
DSDPlus -rv -Pwav -i20002 -v3 >>VC_OnQ.log

and the CAP+ system:
DSDPlus -rv -Pwav -i20002 >>VC_Prairie (158).log

And for comparison, here is my VC.bat of a P25P2 system that I can hear the audio from:
DSDPlus -rv -Pwav -i20002 -v3 >>VC_LMRN (AD9).log

Here is the vc.log contents for the NXDN system on last execution:

2026.01.02 10:14:45
2026.01.02 10:14:45 DSD+ 2.523
2026.01.02 10:14:45 Current working directory is "c:\radio\DSD+ OnQ Network (202) NXDN NexEdge 4800"
2026.01.02 10:14:45 Program role is voice channel decoder; audio modes set to mono
2026.01.02 10:14:45 The -P command line parameter is no longer supported.
2026.01.02 10:14:45 Use the DSD+ menus to adjust this parameter.
2026.01.02 10:14:45 The -v command line parameter is no longer supported.
2026.01.02 10:14:45 Use the DSD+ menus to adjust this parameter.
2026.01.02 10:14:45 Appending synthesized audio to file 'VC-DSDPlus.wav'
2026.01.02 10:14:45
2026.01.02 10:14:45 Assuming FMPA/FMPP/FMP24 is signal source; auto polarity detect is disabled
2026.01.02 10:14:45
2026.01.02 10:14:45 audio output device #1 = 'Speakers (Realtek(R) Audio)'
2026.01.02 10:14:45 audio output device #2 = 'Realtek Digital Output (Realtek'
2026.01.02 10:14:45
2026.01.02 10:14:45 audio output device #1 (Speakers (Realtek(R) Audio)) initialized
2026.01.02 10:14:45
2026.01.02 10:14:45
2026.01.02 10:14:45 Testing Base Files:
2026.01.02 10:14:45
2026.01.02 10:14:45 File: FMP24.exe PASS
2026.01.02 10:14:45 File: FMPA.exe NOT FOUND
2026.01.02 10:14:45 File: FMPP.exe NOT FOUND
2026.01.02 10:14:45 File: FMP-Map.exe PASS
2026.01.02 10:14:45 File: LRRP.exe PASS
2026.01.02 10:14:45 File: Survey.exe PASS
2026.01.02 10:14:45 File: airspy.dll PASS
2026.01.02 10:14:45 File: lame_enc.dll PASS
2026.01.02 10:14:45 File: libfftw3f-3.dll PASS
2026.01.02 10:14:45 File: libusb-1.0.dll PASS
2026.01.02 10:14:45 File: msvcr90.dll PASS
2026.01.02 10:14:45 File: msvcr100.dll PASS
2026.01.02 10:14:45 File: msvcrt.dll PASS
2026.01.02 10:14:45 File: pthreadVCE2.dll PASS
2026.01.02 10:14:45 File: rtlsdr.dll PASS
2026.01.02 10:14:45 File: rtlsdr_FC0012.dll PASS
2026.01.02 10:14:45 File: rtlsdr_V4.dll PASS
2026.01.02 10:14:46 File: sdrplay_api.dll PASS
2026.01.02 10:14:46
2026.01.02 10:14:46 18 files checked
2026.01.02 10:14:46 16 files passed
2026.01.02 10:14:46 2 files not found
2026.01.02 10:14:46
2026.01.02 10:14:46 Base files test: 16 files passed; 2 files not found
2026.01.02 10:14:46 Use [DSD+ Misc menu] / [Download Newest Base Files] to correct
2026.01.02 10:14:46
2026.01.02 10:14:46 P25 data loaded; 0 networks, 0 sites, 0 channels
2026.01.02 10:14:46 24 frequency records loaded
2026.01.02 10:14:46 121 radio records loaded
2026.01.02 10:14:46 40 group records loaded
2026.01.02 10:14:46 7 site records loaded
2026.01.02 10:14:46 1 network record loaded
2026.01.02 10:14:46 0 site loader records loaded
2026.01.02 10:14:46 DMR/MotoTRBO decoding enabled

Mono audio decoding initiated; press Esc to exit...
2026.01.02 10:14:46 Initiating FMPx link using link ID 20002...
2026.01.02 10:14:46 FMPx link error = -5
2026.01.02 10:14:46 [Server is not listening on selected link ID]
2026.01.02 10:14:51 Initiating FMPx link using link ID 20002...
2026.01.02 10:14:51 FMPx link established; link ID = 20002
2026.01.02 10:14:51 FMPx link established
2026.01.02 10:14:53 0 P25 records saved
2026.01.02 10:14:59 P25 data loaded; 0 networks, 0 sites, 0 channels
2026.01.02 10:18:23 122 radio records loaded
2026.01.02 10:18:31 40 group records loaded
2026.01.02 10:19:52 123 radio records loaded
2026.01.02 10:21:52 124 radio records loaded
2026.01.02 10:21:53 125 radio records loaded
2026.01.02 10:22:59 40 group records loaded
2026.01.02 10:23:07 125 radio records loaded
2026.01.02 10:23:58 126 radio records loaded
2026.01.02 10:24:11 40 group records loaded
2026.01.02 10:30:11 127 radio records loaded
2026.01.02 10:31:00 128 radio records loaded
2026.01.02 10:31:22 129 radio records loaded
2026.01.02 10:32:56 129 radio records loaded
2026.01.02 10:33:04 40 group records loaded
2026.01.02 10:33:41 130 radio records loaded
2026.01.02 10:33:55 131 radio records loaded
2026.01.02 10:34:02 132 radio records loaded
2026.01.02 10:34:07 133 radio records loaded
2026.01.02 10:34:12 134 radio records loaded
2026.01.02 10:35:01 40 group records loaded
2026.01.02 10:35:16 134 radio records loaded
2026.01.02 10:35:42 135 radio records loaded
2026.01.02 10:35:51 136 radio records loaded
2026.01.02 10:36:12 40 group records loaded
2026.01.02 10:36:53 136 radio records loaded
2026.01.02 10:37:22 40 group records loaded
2026.01.02 10:37:41 137 radio records loaded
2026.01.02 10:37:48 138 radio records loaded
2026.01.02 10:38:33 40 group records loaded
2026.01.02 10:38:52 138 radio records loaded
2026.01.02 10:39:45 40 group records loaded
2026.01.02 10:46:17 138 radio records loaded
2026.01.02 10:46:20 139 radio records loaded
2026.01.02 10:46:22 40 group records loaded
2026.01.02 10:46:24 140 radio records loaded
2026.01.02 10:46:48 141 radio records loaded

 

[mtindor]

Is there any reason why you feel you must create your own custom batch files to run things. Out of hte box, running FMP24-CC.bat and 1R.bat is all you need to get going. I know, you are using a different linkID (20002). But I also notice you are using switches/options on CLI that aren't even supported on the recent version. Is that stopping you from getting audio? no. But you really still should actual clean things up and actually attempt to use FMP24-CC.bat / 1R.bat and the DSDPlus menu system to do everything.

And how about some screenshots of the channel activity window when you are monitoring the DMR and NXDN systems. Maybe you don't have the DSDPlus.Networks, DSDPlus.Sites, DSDPlus.frequencies files set up properly. Maybe LCNs / Channel IDs on the affected systems are not correct and thus the voice calls cannot be directed to a proper legitimate frequency.

I guess I misunderstood a bit. You're running two dongles / two instances of FMP24 / two instances of DSDPlus?

Assuming all of your information in DSDPlus.networks / .sites / .frequencies is correct, if you just run FMP24-CC.bat and 1R.bat and then use the menu system and under CTRL make sure you are set to combined CC/VC monitor, that would be a good test. Sure, that's using a single dongle . But always good to revert to single dongle and default batch files when you run into issues.

Since you get audio out of P25, I suspect your NXDN/DMR systems aren't configured properly in DSDPlus.networks / .sites / .frequencies for the voice calls to be directed to the proper frequency. It's definitely not an issue with the app itself (your lack of audio on DMR/NXDN) if you can pick up audio on P25.

 

[rkillins]

Is there any reason why you feel you must create your own custom batch files to run things.

If you must know, it's because I run a custom application which allows me to select which system at any one given time I want to monitor. A GUI that allows me to select the system rather that having to access directories for bats or type out commands. Simple really.

For space, I will share for just the CAP+ system.

Networks:
; DSD+ networks file
CON+, 158, "Prairie Communications (MRC Con+)"

Sites:
; DSD+ sites file
; Prairie Communications (Con+)
CON+, 158, 15, "Wilmot"
CON+, 158, 5, "London"
CON+, 158, 8, "Stratford"
CON+, 158, 16, "Kitchener"
CON+, 158, 22, "Cambridge"
CON+, 158, 23, "Brantford"
CON+, 158, 17, "Unknown17"
CON+, 158, 19, "Unknown19"

Frequencies
; DSD+ frequency file
; Prairie Communications (CON+)
CON+, 158, 15, 3, 420.5500, 0.0, 0 ;Wilmot
CON+, 158, 15, 5, 420.6500, 0.0, 0
CON+, 158, 15, 9, 420.9500, 0.0, 0
CON+, 158, 5, 0, 420.2000, 0.0, 0 ;London
CON+, 158, 5, 0, 420.5750, 0.0, 0
CON+, 158, 5, 0, 420.8625, 0.0, 0
CON+, 158, 8, 0, 420.2750, 0.0, 0 ;Stratford
CON+, 158, 8, 0, 420.1750, 0.0, 0
CON+, 158, 8, 0, 420.3750, 0.0, 0
CON+, 158, 16, 0, 453.7125, 0.0, 0 ;Kitchener
CON+, 158, 16, 0, 452.0375, 0.0, 0
CON+, 158, 16, 0, 452.6625, 0.0, 0
CON+, 158, 16, 0, 462.9375, 0.0, 0
CON+, 158, 17, 0, 0.0, 0.0, 0 ;unknown 17
CON+, 158, 19, 0, 0.0, 0.0, 0 ;unknown 19
CON+, 158, 22, 0, 422.3250, 0.0, 0 ;Cambridge
CON+, 158, 22, 0, 420.6000, 0.0, 0
CON+, 158, 23, 0, 422.2500, 0.0, 0 ;Brantford
CON+, 158, 23, 0, 422.6500, 0.0, 0

 

[mtindor]

Almost all of those entries in the dot frequencies file have missing LCN’s, listed as zero. DSD plus would have no idea where to divert voice to.

 

[Whiskey3JMC]

If you must know, it's because I run a custom application which allows me to select which system at any one given time I want to monitor. A GUI that allows me to select the system rather that having to access directories for bats or type out commands. Simple really.

Care to share said app?

 

[mtindor]

Do you know for a fact that these LSNs are correct?

CON+, 158, 15, 3, 420.5500, 0.0, 0 ;Wilmot
CON+, 158, 15, 5, 420.6500, 0.0, 0
CON+, 158, 15, 9, 420.9500, 0.0, 0

And you're missing an LSN / freq pair for LSN 7/8. So you will miss any traffic for ch=7 and ch=8.

You should go into your CC copy menu, CTRL, and make sure it is set to CC monitor and then go into your VC copy CTRL menu and make sure that it is set to VC Monitor. And then you should go to the CTRL menu on them and make sure that voice following is enabled and that your Monitor Threshold is set to 100.

 

[rkillins]

Almost all of those entries in the dot frequencies file have missing LCN’s, listed as zero. DSD plus would have no idea where to divert voice to.

Those with zero in the LCN's I can't monitor, I don't try. They are just essentially placeholders. Ignore them. The only site I can monitor from my location is Wilmot, site 15.

 

[mtindor]

Interestingly, the DB says that Wilmot Site 15 has:

1,420.55
3,420.65
5,420.95

And it doesn't even have a 7 (7/8 LSN pair) and frequency listed. So you'll miss traffic because you don't know what freq is LSN 7/8 (LCN 4) or what freq is LSN 9/10 (LCN 5). And you might not have proper traffic if the LSNs you have listed are wrong and the DB is right.

Your Event Window shows voice activity on the following LSNs:

LSN 4 (LCN 2)
LSN 7,8 (LCN 4)
LSN 9,10 (LCN 5)

So the database is missing information, and what you have in your file may also not be correct. You won't hear any traffic on 7,8 since that entry doesn't even exist in your file (or the DB). And if you have the wrong frequency mapped to 9/10, then that wont produce audio either.

Mike

 

[mtindor]

And if you are hearing ZERO voice calls on Site 15, then 420.55 is likely not LSN 3 in your frequencies file.

 

[rkillins]

Do you know for a fact that these LSNs are correct?

CON+, 158, 15, 3, 420.5500, 0.0, 0 ;Wilmot
CON+, 158, 15, 5, 420.6500, 0.0, 0
CON+, 158, 15, 9, 420.9500, 0.0, 0

And you're missing an LSN / freq pair for LSN 7/8. So you will miss any traffic for ch=7 and ch=8.

You should go into your CC copy menu, CTRL, and make sure it is set to CC monitor and then go into your VC copy CTRL menu and make sure that it is set to VC Monitor. And then you should go to the CTRL menu on them and make sure that voice following is enabled and that your Monitor Threshold is set to 100.

I don't think enough people locally monitor this system (I'm in a radio dead zone ... nothing worth monitoring anymore really, so not much RR database contributions, corrections), so I'm only going on what's provided in the RR Database (re LCN order). I've been searching for the missing frequency (not a super active system) , and consulting our governement TAFL hasn't really provided much in narrowing the missing frequency down. (It may be because I don't know how to read the info properly, and the number of trunked systems off that physical tower with the same callsign).
Screenies attached. Threshold monitoring is at default 100.

 

[mtindor]

It looks like you’re doing everything right, it’s just that without knowing all of the active frequencies and their proper LSN/LCN, it’s just not going to trunk track

 

[rkillins]

And if you are hearing ZERO voice calls on Site 15, then 420.55 is likely not LSN 3 in your frequencies file.

I get messed up with the relationship between LSN, LCN and channel number (in DSD+). Right now the CC is on 420.55 (LCN 1, LSN 1/2 and channel 3 in DSD+). 420.95 (LCN 3, LSN 5/6, and channel 9 in DSD+) is in my Channel activity window, and in addition to 420.55 the only frequency in which voice calls have been observed. I have yet to see 420.650 (LCN 2, LSN 3/4, channel 7) pop up with any voice activity.
How do I know if these are the proper LCNs? What do I need to change to experiment? Is it the CC that broadcasts the channel numbers (and frequencies)?

 

[mtindor]

The frequencies you have to work with are probably:

420.55
420.65
420.75
420.85
420.95

(I dont know which are repeater outputs here)
422 / 427.775
422 / 427.900
423 / 428.025

I'd guess that some combination of 420s will be LSN 1 / 3 / 5 / 7 / 9

 

[mtindor]

I get messed up with the relationship between LSN, LCN and channel number (in DSD+). Right now the CC is on 420.55 (LCN 1, LSN 1/2 and channel 3 in DSD+). 420.95 (LCN 3, LSN 5/6, and channel 9 in DSD+) is in my Channel activity window, and in addition to 420.55 the only frequency in which voice calls have been observed. I have yet to see 420.650 (LCN 2, LSN 3/4, channel 7) pop up with any voice activity.
How do I know if these are the proper LCNs? What do I need to change to experiment? Is it the CC that broadcasts the channel numbers (and frequencies)?

That doesn't make sense. First off, lets forget about the DB. Then lets forget about LCNs (since DSDPlus works with LSNs)

LSNs are paired.

LSN 1/2 (LCN 1)
LSN 3/4 (LCN 2)
LSN 5/6 (LCN 3)
LSN 7/8 (LCN 4)
LSN 9/10 (LCN 5)

You are seeing voice traffic on AT LEAST 4, 7, 8, 9, 10. So three frequencies.

The goal is to figure out which of those 5 420 freqs is paired with each line above

420.55
420.65
420.75
420.85
420.95

Maybe they are in order? If they were, you'd be lucky. They aren't guaranteed to be in order though. So you are just going to have to fiddle around. And keep in mind that what you see displayed in the channel activity window is there because of what have entered in your DSDplus.frequencies file. So if you enter the wrong info there, then the wrong info shows up in the Channel Activity Window. You can't count on what you see there.

You should be able to watch / see enough of the spectrum in FMP24. You park on the CC. Then when you see there is a group call, look in FMP24 and see what "other" signal just popped up while the voice call is active. And if that transmission disappears from the Channel Activity Window / the group call ends and that spike in FMP24 for the other frequency disappears, then you know that the frequency that spiked up during hte voice call is tied to the LSN (ch=#) that is shown in the Event window at that time.

 

[rkillins]

Thank you for the support. I will watch the spectrum, but is there anything conclusive we can claim about the Control channel being identified on 420.55? I guess there's nothing to say what LSN it is as I'm just currently assuming whats in the DB. So if that's the case, how do you even determine the LSN of even just one frequency (I may not even be asking the right question). Does DSD+ provide the LSN at any point on it's own, or does everything depend on the user's system files?

I managed to find this from the government records regarding this licensee and assigned frequencies (5 vs the three known). I'm assuming its all the same system. Does it help sorting out any info?

 

[mtindor]

How do I know if these are the proper LCNs? What do I need to change to experiment? Is it the CC that broadcasts the channel numbers (and frequencies)?

You don't know. you are going to have to figure it out manually.

The CC is what tells you what LSN is active but doesn't broadcast a frequency. That is why you have to map LSN <--> frequency in the DSDPlus.frequencies file in order for it to work. It's not like the vast majority of P25 systems, which broadcast the bandplan over the control channel. Con+ does not do that.

So you know the five likely frequencies (those 420 freqs). And you know that there are likely some number of 10 LSNs in use.

LSN 1/2 (LCN1 ) -- your event window didn't show anything for this, but may have when you monitored in the past
LSN 3/4 (LCN 2) -- your event window showed activity on the LSN 3/4 pair
LSN 5/6 (LCN 3) -- your event window didn't show anything for this, but may have when you monitored in the past
LSN 7/8 (LCN 4) -- your event window showed activity on the LSN 7/8 pair
LSN 9/10 (LCN 5) -- your event window showed activity on the LSN 9/10 pair

So at the very least you have three active frequencies on that site (which may or may not include the CC). There can be voice on the CC, but only on one timeslot.

 

[mtindor]

Thank you for the support. I will watch the spectrum, but is there anything conclusive we can claim about the Control channel being identified on 420.55? I guess there's nothing to say what LSN it is as I'm just currently assuming whats in the DB. So if that's the case, how do you even determine the LSN of even just one frequency (I may not even be asking the right question). Does DSD+ provide the LSN at any point on it's own, or does everything depend on the user's system files?

I managed to find this from the government records regarding this licensee and assigned frequencies. I'm assuming its all the same system. Does it help sorting out any info?

View attachment 194817

I already posted the very same thing (the results) from my TAFL lookup.

So, as I said, the frequencies you will likely be working with are those ones listed by you above in the 420 band.

There are at least 3 active freqs (maybe four). You need to figure out which are are paired with LSN1/2, LSN 3/4, LSN 7/8 and LSN 9/10 at least, as well as LSN 1/2 and LSN 5/6 if you can. I described how you an do that.

In the DSDPlus Event Windows it shows what LSN the voice ccall is on (but calls it "ch=##') ch=## is the LSN. So from your event window that is LSN 4, LSN 7/8 , LSN 9/10. That's at least 3 active frequencies. LSN3/4 MAY be the control channel (420.55), but based upon you saying that you have NEVER heard any voice on the system, I can't say for sure that LSN 3/4 is the control channel (420.55)

 

[mtindor]

Also, on BOTH of your DSDPlus copies, for now, you need to make sure that under OUTPUT you enable "Synthesize All Digital Voice"

IF 420.55 (the control channel) is LSN 3/4, then when you see ch=4 during a group call in the channel window, you should hear audio coming from the copy that is monitoring the control channel.

If you park on the CC with FMP24, and your .frequencies file lists 420.55 as LSN 3, then IF you hear audio when ch=4 group calls show up, you know that 420.55 is LSN 3/4 and is correct in the file.

If you park on the CC with FMP24, and your .frequencies file lists 420.55 as LSN 3 and you do NOT hear audio when ch=4 group calls show up, then it is likely that 420.55 is NOT LSN 3.

In the .frequencies file you list the LSNs (not the LCNs). the LSNs are paired. But you are NOT required to list both LSNs of a pair, only one.

So for LSN 1/LSN2 -- you only have a line for LSN1, and for LSN3/4 you only have to have a line for LSN 3, and for LSN 5/6 you only have to have a line for LSN5, et.

If we assume everything below is correct (and we should not assume that), then you can have your .frequencies file set up either way:

CON+, 158, 15, 3, 420.5500, 0.0, 0 ;Wilmot
CON+, 158, 15, 5, 420.6500, 0.0, 0
CON+, 158, 15, 9, 420.9500, 0.0, 0

OR

CON+, 158, 15, 3, 420.5500, 0.0, 0 ;Wilmot
CON+, 158, 15, 4, 420.5500, 0.0, 0 ; Wilmot
CON+, 158, 15, 5, 420.6500, 0.0, 0
CON+, 158, 15, 6, 420.6500, 0.0, 0
CON+, 158, 15, 9, 420.9500, 0.0, 0
CON+, 158, 15,10, 420.9500, 0.0, 0

It's just easier / leaner to list one LSN from each LSN pair.

So five freqs:
420.55
420.65
420.75
420.85
429.95

Figure out which ones are mapped to:

LSN 1/2 <--> frequency
LSN 3/4 <--> frequency
LSN 5/6 <--> frequency
LSN 7/8 <--> frequency
LSN 9/10 <--> frequency


Mike

 

[mtindor]

If you must know, it's because I run a custom application which allows me to select which system at any one given time I want to monitor. A GUI that allows me to select the system rather that having to access directories for bats or type out commands. Simple really.

For space, I will share for just the CAP+ system.

Networks:
; DSD+ networks file
CON+, 158, "Prairie Communications (MRC Con+)"

Sites:
; DSD+ sites file
; Prairie Communications (Con+)
CON+, 158, 15, "Wilmot"
CON+, 158, 5, "London"
CON+, 158, 8, "Stratford"
CON+, 158, 16, "Kitchener"
CON+, 158, 22, "Cambridge"
CON+, 158, 23, "Brantford"
CON+, 158, 17, "Unknown17"
CON+, 158, 19, "Unknown19"

Frequencies
; DSD+ frequency file
; Prairie Communications (CON+)
CON+, 158, 15, 3, 420.5500, 0.0, 0 ;Wilmot
CON+, 158, 15, 5, 420.6500, 0.0, 0
CON+, 158, 15, 9, 420.9500, 0.0, 0
CON+, 158, 5, 0, 420.2000, 0.0, 0 ;London
CON+, 158, 5, 0, 420.5750, 0.0, 0
CON+, 158, 5, 0, 420.8625, 0.0, 0
CON+, 158, 8, 0, 420.2750, 0.0, 0 ;Stratford
CON+, 158, 8, 0, 420.1750, 0.0, 0
CON+, 158, 8, 0, 420.3750, 0.0, 0
CON+, 158, 16, 0, 453.7125, 0.0, 0 ;Kitchener
CON+, 158, 16, 0, 452.0375, 0.0, 0
CON+, 158, 16, 0, 452.6625, 0.0, 0
CON+, 158, 16, 0, 462.9375, 0.0, 0
CON+, 158, 17, 0, 0.0, 0.0, 0 ;unknown 17
CON+, 158, 19, 0, 0.0, 0.0, 0 ;unknown 19
CON+, 158, 22, 0, 422.3250, 0.0, 0 ;Cambridge
CON+, 158, 22, 0, 420.6000, 0.0, 0
CON+, 158, 23, 0, 422.2500, 0.0, 0 ;Brantford
CON+, 158, 23, 0, 422.6500, 0.0, 0

In your screenshot above (specifically the FMP24 window and the first copy of DSDPlus):

1. FMP24 indicates you are on 420.55 (the control channel)
2. DSDPlus indicates are monitoring the control channel, and that the control channel is seeing an active group call on ch=7 (LSN 7)

If you look at the FMP24, you'lll see two signals of similar strength right above the control channel. One of those two would be LSN 7.

You can hover over those other frequenccy spikes (without clicking) and you will see a visual indicator stating what frequency you are hovering over.






So, going forward, while you are parked on the control channel with FMP24, ANY time you see an active group all, note the ch= and then cross reference it with the other signal of similar height above the control channel that shows up in FMP24. That's how you can determine what LSN is paired with what frequency.

I can tell just by looking at the screenshot above that when ch=7 was active, both 420.65 and 420.75 was active. Those are the two directly to the right of the CC.

In the future, pay attention to the voice calls noted in DSDPlus. When one is active, look at your FMP24 screen, find the "other" signal of same height that isn't the CC, hover over it and gets it frequency. Yes, there could be more than one active (like in the above screenshot) because there was probably data being sent over the other one above. But just watch FMP24 while the voice call is active, and then as soon as you see that the voice call has stopped in DSDPlus, look over and verify that the frequency you were looking at has disappeared. Then you can match that frequency up with whatever ch=## was showing when the group call was active.

 

[dave3825]

If you must know, it's because I run a custom application which allows me to select which system at any one given time I want to monitor.

A GUI that allows me to select the system rather that having to access directories for bats or type out commands. Simple really.

DSDPlus has something simple to do that.

Added DSDPlus.siteLoader file and site loader window.

This feature adds a simple method to directly tune to trunked sites or conventional channels.
Users add trunked site and conventional channel entries to the DSDPlus.siteLoader file
and then use the site loader window to select a site or channel, which is then tuned to
by FMP24, FMPA or FMPP. TCP linking is required.

The format of the DSDPlus.siteLoader file mimics the DSDPlus.sites file.
Trunked site entries may be directly copied from the .sites file to the .siteLoader file.

Like the .sites file, the line format is protocol, network ID, site number, "alias text"

Trunked:

Additional "header" entries can be created to identify/name networks.
Use a site number value of zero for network header/name entries.

Conventional:

Entries can be created for direct tuning to conventional channels.
Use a protocol type of "Conv" or "Conventional" for conventional channel entries.
Typically, you should use unique network ID and site number values on conventional entries.
This lets DSD+ maintain separate talkgroup and radio records for each conventional digital
voice channel.

Both digital voice and analog voice conventional channel tuning is supported.
AM analog entries are supported when DSD+ is linked to FMP24.
FMPA and FMPP do not currently support AM demodulation.

Frequency and mode/protocol are specified in the alias text for each conventional entry.
The frequency value must appear first, then the analog mode or digital voice protocol,
then an identifying channel name.

For analog FM entries, only frequency and channel name are required.

For analog AM entries, use "AM" as the mode text.

For digital voice entries, use the appropriate protocol name. Choices are "ProVoice",
"P25", "D-Star", "Fusion", "DMR", "DCDM", "dPMR", "NXDN48" and "NXDN96".

DSD+ uses the mode/protocol values to select appropriate bandwidth, demodulation
and monitoring mode settings.

Entries of any type can appear more than once in the file, i.e. you can copy some
favorite / commonly used entries from elsewhere in the file to the top for quick access.

Sample DSDPlus.siteLoader file contents:

P25, BEE11.123, 0, "Mulberry PS"
P25, BEE11.123, 1.1, "North"
P25, BEE11.123, 2.2, "South"

Con+, 1234, 0, "ACME"
Con+, 1234, 1, "Site 1"
Con+, 1234, 1, "Site 2"

Conv, 1, 1, "162.550 WX1"
Conv, 1, 2, "119.150 AM ATIS"
Conv, 1, 3, "163.830 P25 FBI"

Press L in DSD+ to open the Network/Site Loader window.
With the sample file above, the window would look like:

P25 Mulberry PS
North
South
Con+ ACME
Site 1
Site 2
Conv 162.550 WX1
Conv 119.150 AM ATIS
Conv 163.830 P25 FBI

Use the Up/Down and PageUp/PageDown keys to highlight a trunked site or a conventional channel.
Press Enter to tune to the selected site/channel or press Esc to close the window.

If an entry is displayed in red, DSD+ does not have any frequency information to work with:

For trunked P25 sites, manually tune to them or their neighbors and monitor for a while;
DSD+ will record control channel information in the DSDPlus.P25data file.

For other trunked sites, edit the DSDPlus.frequencies file and add site frequencies.

If a conventional entry is red, something is wrong with the frequency information
in the entry's alias text.

The location and size of the network/site loader window and the size of the text
are adjusted in the same manner as the event log window.

A high contrast mode can be selected by pressing H, but the red color used to warn
of a lack of frequency information will not be displayed in high contrast modes.

If, after loading a trunking site, extra/erroneous channels/frequencies are displayed in
the channel window, press D to force DSD+ to discard all system information and rebuild it.

Care to share said app?

I am also interested in the app.