DSDPlus FMP24, NXDN96, and rotating control frequencies

Status
Not open for further replies.

NPC411

Member
Joined
Jun 2, 2023
Messages
26
Disclaimer: I am brand new to the SDR realm, and while I have an extensive background in information technology, SDR feels like an entirely different language. I know enough to be dangerous, but even then, the danger is as threatening as a toothpick! I welcome simpler explanations and ample patience!

I have two official RTL-SDR V3 dongles, and I have a lifetime subscription for DSD+ Fastlane. I am decoding a NXDN96 system with two control frequencies, and the control frequencies rotate every night at midnight (please see attached image for the full list of frequencies).Radio Frequencies - 06-02-2023.PNG
I have both RTL-SDR V3 dongles connected to my computer, and I have added all of the frequency and site information into FMP24's files (the guides suggested using FMP24; if there is a better way, I am open to suggestions). I am tuning to one of the control frequencies, and I am following the DSD+ Fastlane notes for dual-dongle monitoring: I run the CC.bat file and the VC.bat file to start two copies of DSD+, and then I run FMP24-CC.bat and FMP24-VC.bat files to start two copies of FMP24. I'm assuming things are working correctly since I am hearing back-and-forth radio chatter, though it isn't always the clearest.

My issue is with the rotating control frequencies; I would love to stream the audio to Broadcastify, but manually changing the control frequency at midnight each night is neither practical nor desirable. What is the best workaround? Should I create a duplicate working folder of DSD+ Fastlane that is customized for the other control frequency and run both working folders at the same time? If I were to do that, would I have to have four RTL-SDR V3 dongles instead of two? Is there any way to just automatically change the control frequency at a set time?

Better yet, if there is an easier way to do all of this for an NXDN96 system with rotating control frequencies, I'm all ears; you have the list of frequencies and my current hardware/software setup, and I would appreciate an expert's opinion on the most streamlined setup. I'm only using two dongles and FMP24 because that's what various forum posts and help articles told me; however, it does lead to a lot of clutter on both my screen and my desk.

Two more questions: Do I need "Set High Priority Override for New Talkgroups" enabled, and would "Combined CC/VC Monitor" help consolidate this setup? Honestly, I don't know what either of those settings mean or what they mean for NXDN96, but a few forum posts mentioned them as possibly important.

Thank you for reading my long and winding post, and I eagerly await your sage advice!
 
Last edited:

NPC411

Member
Joined
Jun 2, 2023
Messages
26
Can you share the appropriate section of the DSDPlus.frequencies file?
NEXEDGE96, 337, 1, 1, 154.75625,0.0,0
NEXEDGE96, 337, 1, 2, 154.15250,0.0,0
NEXEDGE96, 337, 1, 3, 155.09250,0.0,0
NEXEDGE96, 337, 1, 4, 155.95500,0.0,0
NEXEDGE96, 337, 1, 5, 153.65000,0.0,0
NEXEDGE96, 337, 1, 6, 153.29750,0.0,0
NEXEDGE96, 337, 1, 7, 151.58750,0.0,0
NEXEDGE96, 337, 1, 8, 159.10500,0.0,0
NEXEDGE96, 337, 1, 9, 151.71500,0.0,0
NEXEDGE96, 337, 1, 10, 153.28250,0.0,0
NEXEDGE96, 337, 7, 71, 152.97500,0.0,0
NEXEDGE96, 337, 7, 72, 151.86500,0.0,0
NEXEDGE96, 337, 13, 131, 153.60500,0.0,0
NEXEDGE96, 337, 13, 132, 153.20750,0.0,0
 

cg

Member
Premium Subscriber
Joined
Dec 13, 2000
Messages
4,817
Location
Connecticut
That setting is supposed to find the active control channel in a system when it is lost. The default is .75 seconds. So when the signal drops for that time period, the program goes looking for the new control channel. I can't say that I have ever used it on NEXEDGE but it works fine on a P25 TRS. I also only use single SDR trunktracking so not sure if that makes a difference.
There is no reason to see the setting on the VC side as it is to chase a changing control channel.
 

NPC411

Member
Joined
Jun 2, 2023
Messages
26
That setting is supposed to find the active control channel in a system when it is lost. The default is .75 seconds. So when the signal drops for that time period, the program goes looking for the new control channel. I can't say that I have ever used it on NEXEDGE but it works fine on a P25 TRS. I also only use single SDR trunktracking so not sure if that makes a difference.
There is no reason to see the setting on the VC side as it is to chase a changing control channel.
Thank you for explaining it to me; that makes perfect sense! How should CC.bat, VC.bat, FMP24-CC.bat, and FMP24-VC.bat be configured to account for the two changing control channels? I wasn't sure if FMP24-CC.bat could accept more than one frequency in the -f parameter, and every time I open FMP24-VC.bat, it is inactive until I manually tune it to a control channel. From what you're saying, it should already chase the changing control channel, so there must be something wrong in my setup with regards to the control channels.
 

dave3825

* * * * * * * * * * * *
Premium Subscriber
Joined
Feb 17, 2003
Messages
8,471
Location
Suffolk County NY
NEXEDGE96, 337, 1, 1, 154.75625,0.0,0
NEXEDGE96, 337, 1, 2, 154.15250,0.0,0
NEXEDGE96, 337, 1, 3, 155.09250,0.0,0
NEXEDGE96, 337, 1, 4, 155.95500,0.0,0
NEXEDGE96, 337, 1, 5, 153.65000,0.0,0
NEXEDGE96, 337, 1, 6, 153.29750,0.0,0
NEXEDGE96, 337, 1, 7, 151.58750,0.0,0
NEXEDGE96, 337, 1, 8, 159.10500,0.0,0
NEXEDGE96, 337, 1, 9, 151.71500,0.0,0
NEXEDGE96, 337, 1, 10, 153.28250,0.0,0
NEXEDGE96, 337, 7, 71, 152.97500,0.0,0
NEXEDGE96, 337, 7, 72, 151.86500,0.0,0
NEXEDGE96, 337, 13, 131, 153.60500,0.0,0
NEXEDGE96, 337, 13, 132, 153.20750,0.0,0

Do you have a site defined for each site in your sites file? I do not think I have ever seen freqs from multiple sites laid out like yours. Maybe its my ocd but I have always done like below and do not have issues.




sites file
NEXEDGE48, 246, 1, "Farmingville"
NEXEDGE48, 246, 2, "Plainview"
NEXEDGE48, 246, 3, "North Shore Towers"
NEXEDGE48, 246, 4, "Loomis"

freqs file
; 246 1 Farmingville
NEXEDGE48, 246, 1, 0, 463.56250, 0.0, 0 cc

; 246 2 Plainview
NEXEDGE48, 246, 2, 0, 451.01875, 0.0, 0 cc
NEXEDGE48, 246, 2, 0, 451.20625, 0.0, 0
NEXEDGE48, 246, 2, 0, 461.53125, 0.0, 0
NEXEDGE48, 246, 2, 0, 461.66875, 0.0, 0

; 246 3 North Shore Towers
NEXEDGE48, 246, 3, 0, 461.41875, 0.0, 0
NEXEDGE48, 246, 3, 0, 462.73750, 0.0, 0
NEXEDGE48, 246, 3, 0, 463.49375, 0.0, 0
NEXEDGE48, 246, 3, 0, 463.90625, 0.0, 0

; 246 4 Loomis
NEXEDGE48, 246, 4, 604, 462.53750, 462.53750, 0 cc



What happens if you go with this?

freqs file,

; Andalusia
NEXEDGE96, 337, 1, 1, 154.75625,0.0,0
NEXEDGE96, 337, 1, 2, 154.15250,0.0,0
NEXEDGE96, 337, 1, 3, 155.09250,0.0,0
NEXEDGE96, 337, 1, 4, 155.95500,0.0,0
NEXEDGE96, 337, 1, 5, 153.65000,0.0,0
NEXEDGE96, 337, 1, 6, 153.29750,0.0,0
NEXEDGE96, 337, 1, 7, 151.58750,0.0,0
NEXEDGE96, 337, 1, 8, 159.10500,0.0,0
NEXEDGE96, 337, 1, 9, 151.71500,0.0,0
NEXEDGE96, 337, 1, 10, 153.28250,0.0,0

; South West Covington
NEXEDGE96, 337, 7, 71, 152.97500,0.0,0
NEXEDGE96, 337, 7, 72, 151.86500,0.0,0

; North Covington
NEXEDGE96, 337, 13, 131, 153.60500,0.0,0
NEXEDGE96, 337, 13, 132, 153.20750,0.0,0



sites file

NEXEDGE96, 337, 1, "Andalusia"
NEXEDGE96, 337, 7, "South West Covington"
NEXEDGE96, 337, 13, "North Covington"
 

NPC411

Member
Joined
Jun 2, 2023
Messages
26
Thanks f
Do you have a site defined for each site in your sites file? I do not think I have ever seen freqs from multiple sites laid out like yours. Maybe its my ocd but I have always done like below and do not have issues.








What happens if you go with this?

freqs file,

; Andalusia
NEXEDGE96, 337, 1, 1, 154.75625,0.0,0
NEXEDGE96, 337, 1, 2, 154.15250,0.0,0
NEXEDGE96, 337, 1, 3, 155.09250,0.0,0
NEXEDGE96, 337, 1, 4, 155.95500,0.0,0
NEXEDGE96, 337, 1, 5, 153.65000,0.0,0
NEXEDGE96, 337, 1, 6, 153.29750,0.0,0
NEXEDGE96, 337, 1, 7, 151.58750,0.0,0
NEXEDGE96, 337, 1, 8, 159.10500,0.0,0
NEXEDGE96, 337, 1, 9, 151.71500,0.0,0
NEXEDGE96, 337, 1, 10, 153.28250,0.0,0

; South West Covington
NEXEDGE96, 337, 7, 71, 152.97500,0.0,0
NEXEDGE96, 337, 7, 72, 151.86500,0.0,0

; North Covington
NEXEDGE96, 337, 13, 131, 153.60500,0.0,0
NEXEDGE96, 337, 13, 132, 153.20750,0.0,0



sites file

NEXEDGE96, 337, 1, "Andalusia"
NEXEDGE96, 337, 7, "South West Covington"
NEXEDGE96, 337, 13, "North Covington"
Thank you for your reply! Regarding the sites file, I had entered NXDN96 instead of NEXEDGE96, so I updated to your version. I also updated to your version of the frequencies file, though I believe anything prefaced by a semicolon is just considered a note.

However, I noticed some inconsistency in the DSD+ protocol formats. For instance, the siteloader file notes state to use NXDN96 instead of NEXEDGE96, but the networks file notes do not mention which protocol to use. Are the NXDN96 and NEXEDGE96 protocols interpreted the same across all DSD+ files, or does NEXEDGE96 need to be used regardless of what the specific notes say (or don't say) for a DSD+ file?

Also, I believe my cc.bat, vc.bat, and FMP24-VC.bat are still at their default settings, but I originally edited FMP24-CC.bat as follows:

FMP24 -rc -i1 -o20001 -P0.0 -f153.650

Could this be causing an issue with the rotating control channels by tuning to one specific control channel by default? Should the other .bat files be edited with specific information?

I will also list my FMP24.cfg file; the only change I made was updating the search origin for my area (which I think I typed correctly), though the FMP24.SurveyList file stated to change FFT size to 16 for "best performance" (I don't know if that applies to NXDN96):

2.4 ; sampling rate (2.4 Msps)
1024 ; spectrum window width
32 ; FFT size (16k, 32k, 64k)
10 ; spectrum update rate in Hz
5000 -6250 7500 12500 15000 25000 100000 ; step size table; units = Hz; negate default
. ; DSD+ path
.\FreqList.csv ; primary frequency list CSV path\filename
.\FreqList2.csv ; auxiliary frequency list CSV path\filename
miles and bearing ; search units (miles or kilometers)
99.9 ; search distance
31.3085 -86.4833 ; search origin

I truly appreciate everyone's insights thus far!
 
Last edited:

NPC411

Member
Joined
Jun 2, 2023
Messages
26
Thanks f

Thank you for your reply! Regarding the sites file, I had entered NXDN96 instead of NEXEDGE96, so I updated to your version. I also updated to your version of the frequencies file, though I believe anything prefaced by a semicolon is just considered a note.

However, I noticed some inconsistency in the DSD+ protocol formats. For instance, the siteloader file notes state to use NXDN96 instead of NEXEDGE96, but the networks file notes do not mention which protocol to use. Are the NXDN96 and NEXEDGE96 protocols interpreted the same across all DSD+ files, or does NEXEDGE96 need to be used regardless of what the specific notes say (or don't say) for a DSD+ file?

Also, I believe my cc.bat, vc.bat, and FMP24-VC.bat are still at their default settings, but I originally edited FMP24-CC.bat as follows:

FMP24 -rc -i1 -o20001 -P0.0 -f153.650

Could this be causing an issue with the rotating control channels by tuning to one specific control channel by default? Should the other .bat files be edited with specific information?

I will also list my FMP24.cfg file; the only change I made was updating the search origin for my area (which I think I typed correctly), though the FMP24.SurveyList file stated to change FFT size to 16 for "best performance" (I don't know if that applies to NXDN96):

2.4 ; sampling rate (2.4 Msps)
1024 ; spectrum window width
32 ; FFT size (16k, 32k, 64k)
10 ; spectrum update rate in Hz
5000 -6250 7500 12500 15000 25000 100000 ; step size table; units = Hz; negate default
. ; DSD+ path
.\FreqList.csv ; primary frequency list CSV path\filename
.\FreqList2.csv ; auxiliary frequency list CSV path\filename
miles and bearing ; search units (miles or kilometers)
99.9 ; search distance
31.3085 -86.4833 ; search origin

I truly appreciate everyone's insights thus far!
Also, it would probably be useful if I posted the contents of all of my .bat files. As stated previously, the only one I recall editing is FMP24-CC.bat, so I don't actually know if the others are configured correctly for two dongles and two rotating NXDN96 control channels:

CC.bat:
DSDPlus -rc -i20001 -v3 -wsl400.2 -wss100.200 -wel0.1 -wcl0.445 -wes400.520 >>CC.log

VC.bat:
DSDPlus -rv -Pwav -i20002 -v3 -wsl400.210 -wss100.200 -wel172.522 -wcl528.0 >>VC.log

FMP24-CC.bat:
FMP24 -rc -i1 -o20001 -P0.0 -f153.650 (note: -f is only one of the control channels)

FMP24-VC.bat:
FMP24 -rv -i2 -o20002 -P0.0

Also, if I can do a NXDN96 rotating control channel setup with one dongle, I'm open to that; I do not know if the system I'm trying to monitor is so complicated that I actually need two dongles. It's all a bit overwhelming, but I trust all of your expertise!
 
Last edited:

dave3825

* * * * * * * * * * * *
Premium Subscriber
Joined
Feb 17, 2003
Messages
8,471
Location
Suffolk County NY
Also, I believe my cc.bat, vc.bat, and FMP24-VC.bat are still at their default settings, but I originally edited FMP24-CC.bat as follows:

FMP24 -rc -i1 -o20001 -P0.0 -f153.650

Could this be causing an issue with the rotating control channels by tuning to one specific control channel by default?
I have what I want to listen to entered in the site picker file. So when picking a system that way, it will rotate thru the freqs until it sees a control channel.

I use the single dongle method.
1Rbat file to open dsdplus "DSDPlus -r1 -E -T -Pwav -O NUL -v3 -i20001"

fmp24-cc to open Fmp24 "FMP24 -i0 -o20001 -v3 -a1 -b12.5 -f169.8875 -_3"

In either situation, it will sit on whatever freq is entered in the bat file. If it's not an active cc, it will just sit. If it is an active cc it should follow. If using site loader, it will cycle until cc is found.
 

NPC411

Member
Joined
Jun 2, 2023
Messages
26
I have what I want to listen to entered in the site picker file. So when picking a system that way, it will rotate thru the freqs until it sees a control channel.

I use the single dongle method.
1Rbat file to open dsdplus "DSDPlus -r1 -E -T -Pwav -O NUL -v3 -i20001"

fmp24-cc to open Fmp24 "FMP24 -i0 -o20001 -v3 -a1 -b12.5 -f169.8875 -_3"

In either situation, it will sit on whatever freq is entered in the bat file. If it's not an active cc, it will just sit. If it is an active cc it should follow. If using site loader, it will cycle until cc is found.
This single-dongle method sounds promising, and I will edit 1R.bat and FMP24-CC.bat and customize it to the currently active control frequency. Here is how my siteLoader file is currently set up:

NXDN96, 337, 0, "S and P Communications"
NXDN96, 337, 1, "Andalusia"
NXDN96, 337, 7, "South West Covington"
NXDN96, 337, 13, "North Covington"

How should siteLoader be configured to account for the rotating control channels and this particular system? Would I need to use Conv protocols?

UPDATE: Those particular edits to 1R.bat and FMP24-CC.bat (with the control channel customized) and a single dongle are resulting in silence. With my dual-dongle setup, I was getting back-and-forth chatter consistently, though I couldn't tell you if it was picking up everything or if everything was configured correctly.
 
Last edited:

dave3825

* * * * * * * * * * * *
Premium Subscriber
Joined
Feb 17, 2003
Messages
8,471
Location
Suffolk County NY
How should siteLoader be configured to account for the rotating control channels and this particular system?
If all your files are set up correctly, it will follow the control channel on its own. It will, upon loss of the cc, it will scan the rest of the site freqs until it finds one.


UPDATE: Those particular edits to 1R.bat and FMP24-CC.bat (with the control channel customized) and a single dongle are resulting in silence.

Are the settings set like this? Combined cc/vc monitor? Voice / data call following? Hunt for cc should be checked.



1685745814429-png.142950
 

NPC411

Member
Joined
Jun 2, 2023
Messages
26
If all your files are set up correctly, it will follow the control channel on its own. It will, upon loss of the cc, it will scan the rest of the site freqs until it finds one.




Are the settings set like this? Combined cc/vc monitor? Voice / data call following? Hunt for cc should be checked.



1685745814429-png.142950
This morning, the single-dongle method that you suggested kind of worked (and all the settings you mentioned are enabled), but I don't know that I am picking up all the traffic; it did sound clearer than the dual-dongle method. Also, it is worth mentioning that today's control channel is 153.650, which has seemingly always worked; 154.1525 seems to be the one I have issues with on its active days.

I must be missing something. Here's the full reference link of the system in question; I assumed that sites 001, 007, and 013 would be the only relevant ones for me (Andalusia city police and Covington County sheriff's office), but I could be misreading the system entirely and just have no idea what I'm doing (as if that wasn't apparent!): S and P Communications Trunking System, Various, Alabama

I would be glad to share any of the relevant DSD+ and FMP24 files to see if they are set up correctly; just let me know what files to share that I haven't already shared. Earlier, I had mentioned some confusion on whether I should be typing NXDN96 or NEXEDGE96 in all of these files; can anyone offer some clarification on that?

Finally, I'm not stuck on single-dongle vs. dual-dongle; I just want whichever is going to work best for this particular NXDN96 system. Dual-dongle seemed to offer me the most traffic, but single-dongle seemed to be a bit clearer. I would be fine to pick a lane and stay in it, but I just have to know which lane is best and how to properly configure it. Thanks for sticking with me thus far!
 
Last edited:

mwjones

Member
Premium Subscriber
Joined
Apr 9, 2003
Messages
674
Location
Van Alstyne, TX
This morning, the single-dongle method that you suggested kind of worked (and all the settings you mentioned are enabled), but I don't know that I am picking up all the traffic; it did sound clearer than the dual-dongle method. Also, it is worth mentioning that today's control channel is 153.650, which has seemingly always worked; 154.1525 seems to be the one I have issues with on its active days.

I must be missing something. Here's the full reference link of the system in question; I assumed that sites 001, 007, and 013 would be the only relevant ones for me (Andalusia city police and Covington County sheriff's office), but I could be misreading the system entirely and just have no idea what I'm doing (as if that wasn't apparent!): S and P Communications Trunking System, Various, Alabama

I would be glad to share any of the relevant DSD+ and FMP24 files to see if they are set up correctly; just let me know what files to share that I haven't already shared. Earlier, I had mentioned some confusion on whether I should be typing NXDN96 or NEXEDGE96 in all of these files; can anyone offer some clarification on that?

Finally, I'm not stuck on single-dongle vs. dual-dongle; I just want whichever is going to work best for this particular NXDN96 system. Dual-dongle seemed to offer me the most traffic, but single-dongle seemed to be a bit clearer. I would be fine to pick a lane and stay in it, but I just have to know which lane is best and how to properly configure it. Thanks for sticking with me thus far!
We all were beginners in this hobby at some point, so while it's frustrating in these early days, once its dialed in and working you'll have countless hours of enjoyment.

You said you want to listen to Andalusia Police Department and Covington County Sheriff. Are you located in Andalusia, or are you elsewhere in the County?

Let's take a skilled approach to this to get it working. I have a dual-dongle setup identical to what you're trying to get working (and I have had multiple NXDN systems that it has worked successfully on following the rotating control channel, so I know mine works).

Batch Files
The FMP24-cc.bat and FMP24-vc.bat you posted previously are identical to mine, so no changes are recommended.

CC.bat is somewhat different (I know some of those calls are for window position, but they are actaully saved in the app, so it shouldn't be needed), and this may be part of it, here's mine:

DSDPlus -rc -T -E -Pmp3 -i20001 >>CC.log

VC.bat also is different enough to warrant correcting:

DSDPlus -rv -T -E -Pmp3 -i20002 >>VC.log

Menu Options
Once both instances of DSDPlus are running, here's what my menus look like:

Input (Identical on both instances):
cc-input.png

Output (Also identical on both instances):
cc-output.png

Control on the CC instance:
cc-control.png

Control on the VC instance:
vc-control.png

In the next post, I'll create the text files, using a known working configuration as a starting point.
 

mwjones

Member
Premium Subscriber
Joined
Apr 9, 2003
Messages
674
Location
Van Alstyne, TX
Now that we have the applications configured from my previous post, let's get focused on the system specific parameters. You will note that I input all sites in the sites and frequencies lists, as it makes the neighbor lists easier to read. I also add spacing just to make the text files easier to read:

DSDPlus.networks:
For the DSDPlus.networks, a good place to start is the National list Wiki page. It has most of the systems in the US and Canada and has been tested and known working. Here's the relevant line from that page:

NEXEDGE96, 337, "S & P Comm-AL"

DSDPlus.sites:

Code:
; S and P Communications

NXDN96,    337,        1,        "Andalusia"
NXDN96,    337,        2,        "Opp"
NXDN96,    337,        3,        "Florala"
NXDN96,    337,        4,        "Dozier"
NXDN96,    337,        5,        "Luverne"
NXDN96,    337,        6,        "Lapine"
NXDN96,    337,        7,        "South West Covington County"
NXDN96,    337,        8,        "Elba"
NXDN96,    337,        9,        "Enterprise PD"
NXDN96,    337,        10,        "Troy"
NXDN96,    337,        13,        "North Covington County"
NXDN96,    337,        15,        "Enterprise HS"
NXDN96,    337,        16,        "Red Level"
NXDN96,    337,        17,        "Kinston"

DSDPlus.frequencies:

Code:
   ;; S and P Communications
   


; Andalusia

NEXEDGE96,    337,    1,    1,    154.75625,    0.0,    0
NEXEDGE96,    337,    1,    2,    154.15250,    0.0,    0 ; CC
NEXEDGE96,    337,    1,    3,    155.09250,    0.0,    0
NEXEDGE96,    337,    1,    4,    155.95500,    0.0,    0
NEXEDGE96,    337,    1,    5,    153.65000,    0.0,    0 ; CC
NEXEDGE96,    337,    1,    6,    153.29750,    0.0,    0
NEXEDGE96,    337,    1,    7,    151.58750,    0.0,    0
NEXEDGE96,    337,    1,    8,    159.10500,    0.0,    0
NEXEDGE96,    337,    1,    9,    151.71500,    0.0,    0
NEXEDGE96,    337,    1,    10,   153.28250,    0.0,    0


; Opp

NEXEDGE96,    337,    2,    11,    152.88500,    0.0,    0 ; CC
NEXEDGE96,    337,    2,    12,    153.12500,    0.0,    0 ; CC
NEXEDGE96,    337,    2,    13,    151.55000,    0.0,    0
NEXEDGE96,    337,    2,    14,    151.71500,    0.0,    0
NEXEDGE96,    337,    2,    15,    153.28250,    0.0,    0
NEXEDGE96,    337,    2,    16,    153.71000,    0.0,    0


; Florala

NEXEDGE96,    337,    3,    18,    152.91500,    0.0,    0
NEXEDGE96,    337,    3,    19,    153.66500,    0.0,    0
NEXEDGE96,    337,    3,    20,    153.17000,    0.0,    0 ; CC
NEXEDGE96,    337,    3,    21,    153.23000,    0.0,    0 ; CC
NEXEDGE96,    337,    3,    22,    153.56000,    0.0,    0


; Dozier

NEXEDGE96,    337,    4,    41,    151.89500,    0.0,    0 ; CC
NEXEDGE96,    337,    4,    42,    153.53000,    0.0,    0
NEXEDGE96,    337,    4,    43,    154.49000,    0.0,    0
NEXEDGE96,    337,    4,    44,    151.65500,    0.0,    0


; Luverne

NEXEDGE96,    337,    5,    51,    152.93750,    0.0,    0
NEXEDGE96,    337,    5,    52,    153.34250,    0.0,    0
NEXEDGE96,    337,    5,    53,    151.52750,    0.0,    0
NEXEDGE96,    337,    5,    54,    151.66250,    0.0,    0


; Lapine

NEXEDGE96,    337,    6,    ?,    152.90000,    0.0,    0
NEXEDGE96,    337,    6,    ?,    153.30500,    0.0,    0
NEXEDGE96,    337,    6,    ?,    153.59000,    0.0,    0


; South West Covington County

NEXEDGE96,    337,    7,    71,    152.97500,    0.0,    0
NEXEDGE96,    337,    7,    72,    151.86500,    0.0,    0


; Elba

NEXEDGE96,    337,    8,    81,    151.77500,    0.0,    0
NEXEDGE96,    337,    8,    82,    153.01250,    0.0,    0
NEXEDGE96,    337,    8,    83,    152.36000,    0.0,    0
NEXEDGE96,    337,    8,    84,    153.36500,    0.0,    0


; Enterprise PD

NEXEDGE96,    337,    9,    91,    154.37000,    0.0,    0 ; CC
NEXEDGE96,    337,    9,    92,    156.19500,    0.0,    0
NEXEDGE96,    337,    9,    93,    154.44500,    0.0,    0
NEXEDGE96,    337,    9,    94,    155.70000,    0.0,    0
NEXEDGE96,    337,    9,    95,    155.62500,    0.0,    0


; Troy 

NEXEDGE96,    337,    10,    101,    152.30000,    0.0,    0
NEXEDGE96,    337,    10,    102,    153.18500,    0.0,    0
NEXEDGE96,    337,    10,    103,    153.03500,    0.0,    0
NEXEDGE96,    337,    10,    104,    151.83500,    0.0,    0


; North Covington County

NEXEDGE96,    337,    13,    131,    153.60500,    0.0,    0
NEXEDGE96,    337,    13,    132,    153.20750,    0.0,    0


; Enterprise HS

NEXEDGE96,    337,    15,    ?,      153.05000,    0.0,    0 ; CC
NEXEDGE96,    337,    15,    151,    153.26000,    0.0,    0 ; CC
NEXEDGE96,    337,    15,    152,    153.48500,    0.0,    0
NEXEDGE96,    337,    15,    153,    152.28500,    0.0,    0
NEXEDGE96,    337,    15,    154,    152.96000,    0.0,    0


; Red Level

NEXEDGE96,    337,    16,    ?,        152.37500,    0.0,    0 ; CC
NEXEDGE96,    337,    16,    ?,        153.73250,    0.0,    0


; Kinston

NEXEDGE96,    337,    17,    ?,        154.43000,    0.0,    0 ; CC
NEXEDGE96,    337,    17,    ?,        159.44250,    0.0,    0

DSDPlus.siteloader:

This file is optional, but it populates the "Open Network/Site Loader Window" in the Control menu on the CC instance, so you can quickly select between sites without having to manually tune the FMP24 instance or edit its batch file.

Code:
NXDN96,    337,        0,      "S and P Communications"
NXDN96,    337,        1,        "Andalusia"
NXDN96,    337,        2,        "Opp"
NXDN96,    337,        3,        "Florala"
NXDN96,    337,        4,        "Dozier"
NXDN96,    337,        5,        "Luverne"
NXDN96,    337,        6,        "Lapine"
NXDN96,    337,        7,        "South West Covington County"
NXDN96,    337,        8,        "Elba"
NXDN96,    337,        9,        "Enterprise PD"
NXDN96,    337,        10,        "Troy"
NXDN96,    337,        13,        "North Covington County"
NXDN96,    337,        15,        "Enterprise HS"
NXDN96,    337,        16,        "Red Level"
NXDN96,    337,        17,        "Kinston"

Please let us know if this gets your system monitoring correctly. As I reviewed the system data, I saw a lot of missing information, which once you get it dialed in you might be able to contribute to the RRDB to help others.
 

millam

Old Radio Guy
Premium Subscriber
Joined
Jan 18, 2005
Messages
722
Here is what I have in my DSDPlus.frequencies file for this system. I mapped it out
years ago and submitted lots of changes. I lost the time to submit the rest of the
system and haven't, to be honest, had a desire to update it. Skip or night time monitoring
is what I need to hear most of the sites. The one in Red Level is on the edge of my
range. Sites 29 and 30 need mapping. I use Airspy's so the batch files aren't the same but if
someone wants to see them, no problem. NPC411 I disconnect the antenna for a couple of seconds
to see if the CC search is working, it will show the freqs that it is looking for to find a CC freq, it should
return to the current CC if all is working.

Mil

You can cut and paste this into your
DSDPlus.frequencies file. Have not verified in a few years tho.

NEXEDGE96, 337, 1, 1, 154.7550, 0.0, 1
NEXEDGE96, 337, 1, 2, 154.1525, 0.0, 2
NEXEDGE96, 337, 1, 3, 155.0925, 0.0, 3
NEXEDGE96, 337, 1, 4, 155.9550, 0.0, 4
NEXEDGE96, 337, 1, 5, 153.6500, 0.0, 5
NEXEDGE96, 337, 1, 6, 158.9850, 0.0, 6
NEXEDGE96, 337, 1, 7, 151.5875, 0.0, 7
NEXEDGE96, 337, 1, 8, 159.1050, 0.0, 8
;
NEXEDGE96, 337, 2, 11, 152.8850, 0.0, 11
NEXEDGE96, 337, 2, 12, 153.1250, 0.0, 12
NEXEDGE96, 337, 2, 13, 151.5500, 0.0, 13
NEXEDGE96, 337, 2, 14, 151.7150, 0.0, 14
NEXEDGE96, 337, 2, 15, 153.2825, 0.0, 15
NEXEDGE96, 337, 2, 16, 153.7100, 0.0, 16
;
NEXEDGE96, 337, 3, 21, 153.2300, 0.0, 21
NEXEDGE96, 337, 3, 22, 153.5600, 0.0, 22
NEXEDGE96, 337, 3, 23, 152.9150, 0.0, 23
NEXEDGE96, 337, 3, 24, 153.6650, 0.0, 24
;
NEXEDGE96, 337, 4, 41, 151.8950, 0.0, 41
NEXEDGE96, 337, 4, 42, 153.5300, 0.0, 42
NEXEDGE96, 337, 4, 43, 154.4900, 0.0, 43
NEXEDGE96, 337, 4, 44, 151.6550, 0.0, 44
;
NEXEDGE96, 337, 5, 51, 152.9375, 0.0, 51
NEXEDGE96, 337, 5, 52, 153.3425, 0.0, 52
NEXEDGE96, 337, 5, 53, 151.5275, 0.0, 53
NEXEDGE96, 337, 5, 54, 151.6625, 0.0, 54
;
NEXEDGE96, 337, 6, 61, 153.3050, 0.0, 61
NEXEDGE96, 337, 6, 62, 153.5900, 0.0, 62
NEXEDGE96, 337, 6, 63, 152.9000, 0.0, 63
NEXEDGE96, 337, 6, 64, 154.4825, 0.0, 64
;
NEXEDGE96, 337, 7, 71, 152.9750, 0.0, 71
NEXEDGE96, 337, 7, 72, 151.8650, 0.0, 72
;
NEXEDGE96, 337, 8, 81, 151.7750, 0.0, 81
NEXEDGE96, 337, 8, 82, 153.0125, 0.0, 82
NEXEDGE96, 337, 8, 83, 152.3600, 0.0, 83
NEXEDGE96, 337, 8, 84, 153.3650, 0.0, 84
NEXEDGE96, 337, 8, 85, 152.2700, 0.0, 85
;Enterprise
NEXEDGE96, 337, 9, 91, 154.3700, 0.0, 0
NEXEDGE96, 337, 9, 92, 156.1950, 0.0, 0
NEXEDGE96, 337, 9, 93, 154.4450, 0.0, 0
NEXEDGE96, 337, 9, 94, 155.7000, 0.0, 0
NEXEDGE96, 337, 9, 95, 155.6250, 0.0, 0
;
NEXEDGE96, 337, 10, 101, 152.3000, 0.0, 101
NEXEDGE96, 337, 10, 102, 153.1850, 0.0, 102
NEXEDGE96, 337, 10, 103, 153.0350, 0.0, 103
NEXEDGE96, 337, 10, 104, 151.8350, 0.0, 104
;
NEXEDGE96, 337, 13, 131, 153.6050, 0.0, 131
NEXEDGE96, 337, 13, 132, 153.2075, 0.0, 132
NEXEDGE96, 337, 13, 134, 153.4175, 0.0, 134
NEXEDGE96, 337, 13, 133, 152.3900, 0.0, 133
;
NEXEDGE96, 337, 15, 65, 153.0500, 0.0, 65 ; not a error
NEXEDGE96, 337, 15, 151, 153.2600, 0.0, 151
NEXEDGE96, 337, 15, 152, 153.4850, 0.0, 152
NEXEDGE96, 337, 15, 153, 152.2850, 0.0, 153
NEXEDGE96, 337, 15, 154, 152.9600, 0.0, 154
;
NEXEDGE96, 337, 16, 161, 152.3750, 0.0, 161
NEXEDGE96, 337, 16, 162, 153.7325, 0.0, 162
;
NEXEDGE96, 337, 17, 171, 154.4300, 0.0, 171
NEXEDGE96, 337, 17, 174, 159.4425, 0.0, 174
;
NEXEDGE96, 337, 21, 211, 153.4475, 0.0, 211
NEXEDGE96, 337, 21, 212, 153.4025, 0.0, 212
NEXEDGE96, 337, 21, 213, 152.4125, 0.0, 213
;
NEXEDGE96, 337, 22, 221, 153.6950, 0.0, 221
NEXEDGE96, 337, 22, 222, 154.5475, 0.0, 222
NEXEDGE96, 337, 22, 223, 153.7175, 0.0, 223
;
NEXEDGE96, 337, 23, 231, 151.6475, 0.0, 231
NEXEDGE96, 337, 23, 232, 151.5575, 0.0, 232
NEXEDGE96, 337, 23, 233, 151.9250, 0.0, 233
NEXEDGE96, 337, 23, 234, 153.3800, 0.0, 234
NEXEDGE96, 337, 23, 235, 153.2150, 0.0, 235
;
NEXEDGE96, 337, 29, 291, 151.5450, 0.0, 291
;
NEXEDGE96, 337, 30, 301, 152.3975, 0.0, 301
 

NPC411

Member
Joined
Jun 2, 2023
Messages
26
We all were beginners in this hobby at some point, so while it's frustrating in these early days, once its dialed in and working you'll have countless hours of enjoyment.

You said you want to listen to Andalusia Police Department and Covington County Sheriff. Are you located in Andalusia, or are you elsewhere in the County?

Let's take a skilled approach to this to get it working. I have a dual-dongle setup identical to what you're trying to get working (and I have had multiple NXDN systems that it has worked successfully on following the rotating control channel, so I know mine works).

Batch Files
The FMP24-cc.bat and FMP24-vc.bat you posted previously are identical to mine, so no changes are recommended.

CC.bat is somewhat different (I know some of those calls are for window position, but they are actaully saved in the app, so it shouldn't be needed), and this may be part of it, here's mine:

DSDPlus -rc -T -E -Pmp3 -i20001 >>CC.log

VC.bat also is different enough to warrant correcting:

DSDPlus -rv -T -E -Pmp3 -i20002 >>VC.log

Menu Options
Once both instances of DSDPlus are running, here's what my menus look like:

Input (Identical on both instances):
View attachment 143051

Output (Also identical on both instances):
View attachment 143052

Control on the CC instance:
View attachment 143055

Control on the VC instance:
View attachment 143056

In the next post, I'll create the text files, using a known working configuration as a starting point.
Wow! Thank you, mwjones and millam! I will plan on checking and updating all of this information in the next day or so, and I will report back with my results. To answer your question, the setup will be within 2 miles of the downtown Andalusia tower, so it will be close. At first, I assumed that Andalusia Police and Covington County Sheriff's Office were the only two of interest, but anything within the county itself (Red Level, Opp, Florala, perhaps Dozier) would probably be useful. Would the setup location preclude me from picking up all of those departments using the default extra-long RTL-SDR V3 antennas?
 

dave3825

* * * * * * * * * * * *
Premium Subscriber
Joined
Feb 17, 2003
Messages
8,471
Location
Suffolk County NY
If those departments (talk groups) affiliate with the Andalusia site, you should be good. If they affiliate with different sites, and those sites are not that close, you may need to step up the antenna. Those antennas that come with the dongles are, well, crap. Since your 2 miles from Andalusia's site, you should yield good results with anything on that site.
 

millam

Old Radio Guy
Premium Subscriber
Joined
Jan 18, 2005
Messages
722
There is a typo:
;
NEXEDGE96, 337, 29, 291, 15 "1" .5450, 0.0, 291
should be
NEXEDGE96, 337, 29, 291, 153.5450, 0.0, 291

NPC411 I am in western Houston county, but I do have an antenna up 40 feet. I received all the
sites good enough except Red Level to decode this morning before the sun faded them away so
you should be able to receive them. I have a list of neighbors for each site I will post when I clear
it up so someone with knowledge of them can tell you who hears who. I also have a Google Earth
map showing the locations (correct I hope) and will post a link to it. As you can tell I have to much
time to kill, but what the heck, I enjoy it, beats working for a living.

Mil

site neighbors location
1 2 3 4 7 13 Andalusia
2 1 3 4 8 NW of Opp
3 1 2 7 Florala
4 1 2 5 8 13 16 N Covington S Crenshaw
5 4 6 10 Luverne
6 4 5 10 N Crenshaw
7 1 3 SW Covington
8 2 4 9 10 17 Elba
9 8 15 17 Enterprise
10 5 6 8 9 29 30 Troy
13 1 4 16 N Covington
15 8 9 17 Enterprise High School (?)
16 1 4 13 Red Level (Can't find where tower is)
17 8 9 15 Kinston
21 8 9 10 15 17 Victoria (N Coffee county)
22 none Chancellor (Coffee County)
23 none Enterprise (East on Rucker Blvd)
29 10 21 30 Brundidge
30 10 29 NE of Troy 13 miles (?)
 
Status
Not open for further replies.
Top