DSDPlus FMP24, NXDN96, and rotating control frequencies

[NPC411]

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:

; 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:

   ;; 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.

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.

My apologies for the delay in following up; I have just now gotten some time to input this new information. Thank you all for your invaluable advice and for the amount of time you've each taken to help me.

mwjones, regarding my FMP24-CC.bat file, do I need the -f argument at the end of the file? If so, which frequency should go there to account for the rotating control channel for Andalusia? Also, under the "Control > Call Priorites" sections of CC and VC, should I have "Set High Priority Override for New Talkgroups" checkmarked?

I'm sure I will have more questions as I test everything out; I greatly appreciate this friendly and helpful community!

 

[dave3825]

FMP24-CC.bat file, do I need the -f argument at the end of the file? If so, which frequency should go there to account for the rotating control channel for Andalusia?

If you have the site picker set up, you can stick any freq in the bat file as the site picker will scroll thru all freqs until it finds an active control channel. My bat file is set to a conventional p25 freq that sometimes I monitor. If I want a trunked system, I just use the site picker

 

[NPC411]

If you have the site picker set up, you can stick any freq in the bat file as the site picker will scroll thru all freqs until it finds an active control channel. My bat file is set to a conventional p25 freq that sometimes I monitor. If I want a trunked system, I just use the site picker

That makes sense! Is this how the Site Loader should usually look? I wasn't sure if the numbers in the left column should look like that of if they are supposed to be sequential.

Also, do you have any insights on the necessity of "Set High Priority Override for New Talkgroups"?

 

[dave3825]

I do not utilize any of the priority settings so I will let someone else respond to that.

The numbers in the site loader, Not really sure but it looks like the 3 digit number listed next to each site represents the first freq of the freq associated with that site.

So if you look in your freqs file, Andalusias first listed freq would be 154. something. And OPP's first freq would be 152. something. I do not believe they should be in any order. You can however arrange your sites in alphabetical order if you wish by editing the order the sites are listed in the site loader file. You can have any order you wish or completely random.

 

[mwjones]

That makes sense! Is this how the Site Loader should usually look? I wasn't sure if the numbers in the left column should look like that of if they are supposed to be sequential.
View attachment 144093
Also, do you have any insights on the necessity of "Set High Priority Override for New Talkgroups"?

The site loader is appearing as expected. As @dave3825 mentioned, it is the first part of the first frequency in the site. You can select the intended site, and it will start searching all of the frequencies for that site looking for the control channel.

As far as "Set High Priority Override for New Talkgroups", I don't have that set, as it's looking for traffic that hasn't previously been identified. When I am working to identify unknown talkgroups, I want to capture any that are active, I'll sort out the recordings later, and once positively identified, will lock that talkgroup out completely so I can continue to focus on other unidentified ones.

 

[NPC411]

The site loader is appearing as expected. As @dave3825 mentioned, it is the first part of the first frequency in the site. You can select the intended site, and it will start searching all of the frequencies for that site looking for the control channel.

As far as "Set High Priority Override for New Talkgroups", I don't have that set, as it's looking for traffic that hasn't previously been identified. When I am working to identify unknown talkgroups, I want to capture any that are active, I'll sort out the recordings later, and once positively identified, will lock that talkgroup out completely so I can continue to focus on other unidentified ones.

Thank you, @dave3825 and @mwjones! Also, thanks for explaining "High Priority Override"; I cleared out my DSDplus.groups file just to make sure my previous tinkering wasn't affecting the new setup. Regarding Site Loader, when I want to utilize it, do I need to make the selection on both CC and VC, or only CC?

 

[dave3825]

I utilize site loader thru the main DSDPlus window and select the system of choice. I also run DSDPlus in single dongle mode. but think that it does not make a difference for anyone running 2 dongles.

 

[mwjones]

Thank you, @dave3825 and @mwjones! Also, thanks for explaining "High Priority Override"; I cleared out my DSDplus.groups file just to make sure my previous tinkering wasn't affecting the new setup. Regarding Site Loader, when I want to utilize it, do I need to make the selection on both CC and VC, or only CC?

When using Site Loader on a 2-dongle set up, only change it on the CC, the VC will follow on its own (the VC tuner window will be blank when there's no traffic being received and will then auto-tune when a channel goes active).

 

[NPC411]

When using Site Loader on a 2-dongle set up, only change it on the CC, the VC will follow on its own (the VC tuner window will be blank when there's no traffic being received and will then auto-tune when a channel goes active).

Thanks, everyone! As a result of everyone's advice, I am now getting the most traffic I have ever received at the highest quality, and the control channel is being followed flawlessly without manual tuning. Your help was critical to making it all happen, and I greatly appreciate it.

One thing I have noticed is that DSD+ CC and DSD+ VC do not always remember my settings; sometimes, I have to go in and recheck "Synthesize All Digital Voice" and turn off per-call recording again (due to storage limits, I am not concerned with saving the recordings). Are there arguments I could add to the CC.bat file and VC.bat file to always have those settings checked?

My final task will be building a .bat file to easily open CC.bat, VC.bat, FMP24-CC.bat, and FMP24-VC.bat at the same time. If anyone has any advice on properly structuring that .bat file, that would be excellent!

Thanks again for everyone's wonderful assistance!

 

[mwjones]

Thanks, everyone! As a result of everyone's advice, I am now getting the most traffic I have ever received at the highest quality, and the control channel is being followed flawlessly without manual tuning. Your help was critical to making it all happen, and I greatly appreciate it.

One thing I have noticed is that DSD+ CC and DSD+ VC do not always remember my settings; sometimes, I have to go in and recheck "Synthesize All Digital Voice" and turn off per-call recording again (due to storage limits, I am not concerned with saving the recordings). Are there arguments I could add to the CC.bat file and VC.bat file to always have those settings checked?

My final task will be building a .bat file to easily open CC.bat, VC.bat, FMP24-CC.bat, and FMP24-VC.bat at the same time. If anyone has any advice on properly structuring that .bat file, that would be excellent!

Thanks again for everyone's wonderful assistance!

Glad to hear of your success!

DSD+ CC and DSD+ VC will write their settings to a DSDPlus.bin file in your installation directory. Make sure you're closing the application (and not the command line window), and it should update that file. Likewise make sure you're not deleting that file (for example when deleting log files). That should preserve your settings.

I don't have a .bat file that launches DSDPlus, as my primary rig is mobile, and sometimes one of the receivers will disconnect and reconnect after going over a bump, leaving the app in error - by launching each separately, I can reset one component without having to close everything and restarting it. I know others have done exactly what you're looking for, so you might search the forum here for examples, or someone else might chime in and share a .bat file that they use.

 

[NPC411]

Glad to hear of your success!

DSD+ CC and DSD+ VC will write their settings to a DSDPlus.bin file in your installation directory. Make sure you're closing the application (and not the command line window), and it should update that file. Likewise make sure you're not deleting that file (for example when deleting log files). That should preserve your settings.

I don't have a .bat file that launches DSDPlus, as my primary rig is mobile, and sometimes one of the receivers will disconnect and reconnect after going over a bump, leaving the app in error - by launching each separately, I can reset one component without having to close everything and restarting it. I know others have done exactly what you're looking for, so you might search the forum here for examples, or someone else might chime in and share a .bat file that they use.

Thanks, @mwjones ! I will do some more research on the .bat configuration. Regarding closing the applications, what are the best practices and proper order for doing so? I have DSD+ CC, DSD+VC, FMP24-CC, and FMP24-VC all opened at once, and while I'm avoiding closing the command prompts, I don't really know how to close the others besides clicking "X" or pressing "Esc".

Also, while I'm adjusting priorities for certain talkgroups, the two main talkgroups that interest me (Andalusia Police and Covington County Sheriff's Office) will occasionally overlap their calls, which can result in missing calls for either one. Is that just the nature of the beast with monitoring two talkgroups with equal priority, or is there some sort of "delay" feature to hear every call?

 

[mwjones]

Thanks, @mwjones ! I will do some more research on the .bat configuration. Regarding closing the applications, what are the best practices and proper order for doing so? I have DSD+ CC, DSD+VC, FMP24-CC, and FMP24-VC all opened at once, and while I'm avoiding closing the command prompts, I don't really know how to close the others besides clicking "X" or pressing "Esc".

Also, while I'm adjusting priorities for certain talkgroups, the two main talkgroups that interest me (Andalusia Police and Covington County Sheriff's Office) will occasionally overlap their calls, which can result in missing calls for either one. Is that just the nature of the beast with monitoring two talkgroups with equal priority, or is there some sort of "delay" feature to hear every call?

As far as closing the apps, there's no specific sequence of shutting them down. As I mentioned previously. Sometimes my FMP24 instances will get stuck in "error" because of a momentary disconnect/reconnect of my RTL-SDR radios from the hub they're connected to. I will close only the affected instance, and relaunch it, and the DSD+ instances will pick right back up (although if it is the FMP24-CC instance I might have to re-enter the frequency or re-select the site I'm trying to monitor).

For shutting down all the apps, it again depends on the need, sometimes I'll leave the DSD+ instances running so I can note something on the screen, before they get shut down, but will close the FMP24 instances so that I can disconnect the USB cable from the laptop and not get inundated with the error messages when the receivers go away. Other times, I'll close the DSD+ instances first, then the FMP24 instances (and in those cases out of habit I will close the DSD+ VC instance, then the DSD+ CC instance, followed by the FMP24 instances, with VC first and CC last. (my startup order is FMP24 CC, DSD+ CC, FMP24 VC, DSD+ VC)

In regards to the monitoring, DSD+ can only follow one voice channel at a time (the advantage of the dual receiver setup is that you can see all activity based on the control channel, even when a voice channel is being actively monitored). If both talk groups are active at the same time, the receiver will lock on the first and remain on that talk group until the communication ends and the frequency released. It will then jump to another active talk group. If they have differing priorities, the one with the higher priority will take precedence over the lower priority.

While there are other SDR monitoring applications that can monitor multiple talk groups/frequencies at once using a single SDR, they currently don't support NexEDGE systems, and they have other shortcomings and limitations that make their use difficult (for example a P25 system that I used to monitor required three SDR's to monitor all the traffic on the system because of the frequency spacing - you can now understand why I'm up to 6 RTL-SDR radios)

 

[cg]

There was an issue early on with shut down and loss of data but that was addressed. If you right click the black icon on the taskbar, there is a "close all windows" option that works fine.

 

[NPC411]

As far as closing the apps, there's no specific sequence of shutting them down. As I mentioned previously. Sometimes my FMP24 instances will get stuck in "error" because of a momentary disconnect/reconnect of my RTL-SDR radios from the hub they're connected to. I will close only the affected instance, and relaunch it, and the DSD+ instances will pick right back up (although if it is the FMP24-CC instance I might have to re-enter the frequency or re-select the site I'm trying to monitor).

For shutting down all the apps, it again depends on the need, sometimes I'll leave the DSD+ instances running so I can note something on the screen, before they get shut down, but will close the FMP24 instances so that I can disconnect the USB cable from the laptop and not get inundated with the error messages when the receivers go away. Other times, I'll close the DSD+ instances first, then the FMP24 instances (and in those cases out of habit I will close the DSD+ VC instance, then the DSD+ CC instance, followed by the FMP24 instances, with VC first and CC last. (my startup order is FMP24 CC, DSD+ CC, FMP24 VC, DSD+ VC)

In regards to the monitoring, DSD+ can only follow one voice channel at a time (the advantage of the dual receiver setup is that you can see all activity based on the control channel, even when a voice channel is being actively monitored). If both talk groups are active at the same time, the receiver will lock on the first and remain on that talk group until the communication ends and the frequency released. It will then jump to another active talk group. If they have differing priorities, the one with the higher priority will take precedence over the lower priority.

While there are other SDR monitoring applications that can monitor multiple talk groups/frequencies at once using a single SDR, they currently don't support NexEDGE systems, and they have other shortcomings and limitations that make their use difficult (for example a P25 system that I used to monitor required three SDR's to monitor all the traffic on the system because of the frequency spacing - you can now understand why I'm up to 6 RTL-SDR radios)

Thank you for this great explanation, @mwjones , and thank you, @cg , for that hint about "close all windows". I have two more questions:

1) When I start up FMP24-CC (along with everything else), the "synthesize all digital voice" option is selected (as well as in FMP24-VC). However, right after I select a site and receive a call, FMP24-CC automatically swaps to "no digital voice synthesis" (FMP24-VC maintains "synthesize all digital voice" and doesn't change). It appears I am still receiving audio when FMP24-CC has "no digital voice synthesis" selected; is that normal behavior since FMP24-VC is the voice channel?

2) I've seen some back-and-forth regarding the proper bandwidth for NXDN96. FMP24-CC and FMP24-VC are using a bandwidth of 9.5 (I did not select that myself; that is just the default for my setup). As long as I am getting the traffic I want, is a bandwidth of 9.5 okay, or is there a better bandwidth setting?

Thanks again for everyone's help!

 

[LimaZulu]

1) When I start up FMP24-CC (along with everything else), the "synthesize all digital voice" option is selected (as well as in FMP24-VC). However, right after I select a site and receive a call, FMP24-CC automatically swaps to "no digital voice synthesis" (FMP24-VC maintains "synthesize all digital voice" and doesn't change). It appears I am still receiving audio when FMP24-CC has "no digital voice synthesis" selected; is that normal behavior since FMP24-VC is the voice channel?

That's perfectly fine. CC instance is not supposed to synthesize any voice. It's role is to listen to control channel and control VC instance to jump to voice channels.

2) I've seen some back-and-forth regarding the proper bandwidth for NXDN96. FMP24-CC and FMP24-VC are using a bandwidth of 9.5 (I did not select that myself; that is just the default for my setup). As long as I am getting the traffic I want, is a bandwidth of 9.5 okay, or is there a better bandwidth setting?

Default values are 9.5 for NXDN96 and 4 for NXDN48 and they are set by the developers. Even if you change it will automatically revert back to 9.5 when moved to next voice channel. That's when in trunk tracking mode. When you free tune you can set whatever bandwidth you want.

 

[NPC411]

That's perfectly fine. CC instance is not supposed to synthesize any voice. It's role is to listen to control channel and control VC instance to jump to voice channels.


Default values are 9.5 for NXDN96 and 4 for NXDN48 and they are set by the developers. Even if you change it will automatically revert back to 9.5 when moved to next voice channel. That's when in trunk tracking mode. When you free tune you can set whatever bandwidth you want.

@LimaZulu , all of this makes perfect sense, and I appreciate you clarifying it all. While I could use some stronger antennas since the default RTL-SDR ones are not picking up well through a metal structure, the setup as a whole is functioning.

As a token of my appreciation to all of you, I managed to build a .bat file to open DSD+ CC, DSD+ VC, FMP24-CC, and FMP24-VC in staggered five-second intervals (the number of seconds and the program opening sequence can be easily changed). Open up Notepad, name the document anything as long as it ends in .bat and is saved on the top of your DSDPlus folder, and copy, paste, and save the following into the .bat file:

Start cc.bat
timeout /t 5 /nobreak > NUL
Goto :1
:1
Start vc.bat
timeout /t 5 /nobreak > NUL
Goto :2
:2
Start FMP24-CC.bat
timeout /t 5 /nobreak > NUL
Goto :3
:3
Start FMP24-VC.bat

Once again, thanks to everyone for your invaluable help, and if I need further assistance, I will be sure to let you know! God bless!!

 

[LimaZulu]

@LimaZulu , all of this makes perfect sense, and I appreciate you clarifying it all. While I could use some stronger antennas since the default RTL-SDR ones are not picking up well through a metal structure, the setup as a whole is functioning.

As a token of my appreciation to all of you, I managed to build a .bat file to open DSD+ CC, DSD+ VC, FMP24-CC, and FMP24-VC in staggered five-second intervals (the number of seconds and the program opening sequence can be easily changed). Open up Notepad, name the document anything as long as it ends in .bat and is saved on the top of your DSDPlus folder, and copy, paste, and save the following into the .bat file:

Start cc.bat
timeout /t 5 /nobreak > NUL
Goto :1
:1
Start vc.bat
timeout /t 5 /nobreak > NUL
Goto :2
:2
Start FMP24-CC.bat
timeout /t 5 /nobreak > NUL
Goto :3
:3
Start FMP24-VC.bat

Once again, thanks to everyone for your invaluable help, and if I need further assistance, I will be sure to let you know! God bless!!

You can simplify things even more if you put everything in one bat file, remove those timeouts (or at least lower them to 1 second, 15 seconds in total to run all is a waste of time) and goto. Something like that:

start FMP24 -i2 -a0 -o20004 -b4 -g32.8 -q1 -z0 -P41.7
timeout /t 1 /nobreak >nul
start DSDPlus -i20004 -o1 -O NUL -fa -fm -E -m1 -v4 -T

The above example is for a single dongle setup with automatic selection of protocol so you have to adapt it to your needs

 

[NPC411]

You can simplify things even more if you put everything in one bat file, remove those timeouts (or at least lower them to 1 second, 15 seconds in total to run all is a waste of time) and goto. Something like that:

start FMP24 -i2 -a0 -o20004 -b4 -g32.8 -q1 -z0 -P41.7
timeout /t 1 /nobreak >nul
start DSDPlus -i20004 -o1 -O NUL -fa -fm -E -m1 -v4 -T

The above example is for a single dongle setup with automatic selection of protocol so you have to adapt it to your needs

That .bat file is great for a single-dongle setup; thank you!! I should have clarified that the .bat file I posted is intended for use as a single file; manually opening four files for my dual-dongle setup was tiring, so that one .bat file opens them all in sequence. I wasn't sure if each app needed a bit of breathing room between opening, but I may lower the number of seconds and check my results.

Thanks again for your help!!

 

[Reconrider]

That .bat file is great for a single-dongle setup; thank you!! I should have clarified that the .bat file I posted is intended for use as a single file; manually opening four files for my dual-dongle setup was tiring, so that one .bat file opens them all in sequence. I wasn't sure if each app needed a bit of breathing room between opening, but I may lower the number of seconds and check my results.

Thanks again for your help!!

Letting dsd fully load before loading another dsd instance is a good idea. I've went clicking to quickly and dsd was confused and decided not to decode anything. Took me a day before i realized it as I clicked and left

 

[NPC411]

Letting dsd fully load before loading another dsd instance is a good idea. I've went clicking to quickly and dsd was confused and decided not to decode anything. Took me a day before i realized it as I clicked and left

I feel like I had a similar quirk with even the five second intervals, so I will keep a watch on it and may expand it to a bit longer. Once everything is running, it runs amazingly well, but getting there is 99% of the battle!