DSDPlus DSDPlus Fastlane Update V2.228 on 12/21/2019

[mtindor]

Went ahead and tried that, but still getting errors:

Ok forget about the unrecoverable until all else is fixed. If there is an invalid command line parameters "-i2", then go into your batch file that you run FMPA from and remove the damned -i2 and try it. Or, post all of your commandlines that you use.

 

[CanesFan95]

Here's what's in the .bat file:

START CMD /c "FMPA -rc -i1 -o20001 -f464.2000 -wsl0.-1 >FMPA-CC.log -b12.5 -L15 -M15 -V15"

START CMD /c "FMPA -rv -i2 -o20002 -wsl0.-1 >FMPA-VC.log -b12.5 -L15 -M15 -V15"

START CMD /c "DSDPlus -rc -i20001 -v2 >CC.log -wsl25.964 -wss114.313 -wel0.1 -wes657.1276 -weh18 -wcl24.1 -wch20 -T -E -e"

START CMD /c "DSDPlus -rv -i20002 -v2 >VC.log -wsl164.964 -wss114.313 -wel0.1 -wes657.1276 -weh18 -wcl304.776 -wch20 -T -E -e"

 

[CanesFan95]

If I run it without the -i2:

START CMD /c "FMPA -rc -i1 -o20001 -f464.2000 -wsl0.-1 >FMPA-CC.log -b12.5 -L15 -M15 -V15"

START CMD /c "DSDPlus -rc -i20001 -v2 >CC.log -wsl25.964 -wss114.313 -wel0.1 -wes657.1276 -weh18 -wcl24.1 -wch20 -T -E -e"

Then I still get this error:

 

[Airspy-US]

Here's what's in the .bat file:

START CMD /c "FMPA -rc -i1 -o20001 -f464.2000 -wsl0.-1 >FMPA-CC.log -b12.5 -L15 -M15 -V15"

START CMD /c "FMPA -rv -i2 -o20002 -wsl0.-1 >FMPA-VC.log -b12.5 -L15 -M15 -V15"

START CMD /c "DSDPlus -rc -i20001 -v2 >CC.log -wsl25.964 -wss114.313 -wel0.1 -wes657.1276 -weh18 -wcl24.1 -wch20 -T -E -e"

START CMD /c "DSDPlus -rv -i20002 -v2 >VC.log -wsl164.964 -wss114.313 -wel0.1 -wes657.1276 -weh18 -wcl304.776 -wch20 -T -E -e"

It looks like there is a lot of 'extra' in your command lines. Try creating a batch file for EACH of the commands and use a master BAT file to call those. One we use looks like this (called RUN ICORRS.BAT): (timeouts are to give time to minimize the DOS windows)

RUN ICORRS.BAT:
start FMPA-CC-ICORRS.bat
timeout 8
start CC-ICORRS.bat
timeout 8
start FMPA-VC-ICORRS.bat
timeout 8
start VC-ICORRS.bat

And here are the four BAT files for the commands:

FMPA-CC-ICORRS.BAT:
cd c:\sdr\dsd - ICORRS\
FMPa -i1 -o20001 -f859.9625 -V13 -M15 -L15 -b12.5

CC-ICORRS.BAT:
cd c:\sdr\dsd - ICORRS\
DSDPlus.exe -rc -i20001 -v4 -wel0.0 -wcl442.0 -wsl450.0 -wss200.300 -wsp100 -wes400.700 -weh15 -wch15 >>CC.log

FMPA-VC-ICORRS.BAT:
cd c:\sdr\dsd - ICORRS\
FMPa -rv -i2 -o20002 -V13 -M15 -L15

VC-ICORRS.BAT:
cd c:\sdr\dsd - ICORRS\
DSDPlus.exe -rv -i20002 -v4 -wel490.0 -wcl910.0 -wsl940.0 -wss700.300 -wsp100 -wes378.700 -weh15 -wch15

And here is the FMPA CFG file (SN obscured):
910865xxxxxxxxxx, 910865xxxxxxxxxx ; Airspy serial number list
2.5 ; sampling rate (2.5 or 10)
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
.\FMPA-FreqList.csv ; primary frequency list CSV path\filename
.\FMPA-FreqList2.csv ; auxiliary frequency list CSV path\filename
miles ; miles or kilometers
99.9 ; search distance
40.1163 -80.1241 ; search origin

 

[Airspy-US]

Avatar looks magnitudes better Yes, it would be a good test. All I can say is that hte only thing that changed on my setup (one R2, no dongles) was an update to the latest DSDPlus/FMPA. I had been remoting into that same machine forever without those errors in the past.

The author is aware, as I whined immediately

Mike

A little more info. You don't even need a third SDR connected. Just running SDR# (no receiver and not hitting the start button) is enough to trigger the situation. This SDR# has no DSD plugin on it, and I tried changing the audio output but that did not solve it.

I also tested running then closing SDR# before there was VC activity, but that did not matter either. Once the situation starts, the only solution is to close then restart the VC instance of DSD+.

 

[thewraith2008]

And I also get 2 of this error for both AirSpy dongles. Any ideas what this means or how to fix it? Are there any guides that explain what all the codes mean to try and troubleshoot this? I don't understand the part about dividing by zero because I'm not using any calculator with this program!

Here's the FMPA.cfg file:

While I don't have an Airspy, I tried your 'search origin' line in my FMP24.cfg and I get your error.
For some reason "28.042000 -82.482500" is causing an error.

Change line in your FMPA.cfg to the following and it should work (does in FMP24 anyway).

28.0420 -82.482500                 ; search origin

You should report this to DSDPlus as this maybe a bug in the processing of the LAT/LONG in the .cfg across FMPx programs.

 

[CanesFan95]

Figured it out. The search origin coordinates can no longer have any extra zeros at the end of the coordinates, or else you get that divide by 0 error. So you can use:

28.042 -82.4825 ; search origin

but not:

28.04200 -82.482500 ; search origin.

And for the serial numbers, using a comma also gives the invalid '-i2' error, but a space works okay. So you can use:

26A464DC28423E93 26A464DC28694393 ; Airspy serial number list

but not:

26A464DC28423E93,26A464DC28694393 ; Airspy serial number list.

I've made both of these corrections and now all the errors have gone away. Not sure why some people can use a comma and it works fine. But the comma gives me an error. I've gone ahead and e-mailed DSD+ about this. Once again, I'm always the guy that gets the wierdest problems that no one else gets. Thanks to all for all the help.

 

[thewraith2008]

Figured it out. The search origin coordinates can no longer have any extra zeros at the end of the coordinates, or else you get that divide by 0 error. So you can use:

28.042 -82.4825 ; search origin

but not:

28.04200 -82.482500 ; search origin.

FMPx does this with no consistency. In my test, I had to change LAT: "28.042000" to "28.0420" and I left your value at LONG: "-82.482500".
Works for one and not the other, That's why I think it's a bug.

And for the serial numbers, using a comma also gives the invalid '-i2' error, but a space works okay. So you can use:

26A464DC28423E93 26A464DC28694393 ; Airspy serial number list

but not:

26A464DC28423E93,26A464DC28694393 ; Airspy serial number list.

I've made both of these corrections and now all the errors have gone away. Not sure why some people can use a comma and it works fine. But the comma gives me an error. I've gone ahead and e-mailed DSD+ about this. Once again, I'm always the guy that gets the wierdest problems that no one else gets. Thanks to all for all the help.

People are most likely using comma and a space.

26A464DC28423E93 26A464DC28694393 ; Airspy serial number list - (SPACE) Works
26A464DC28423E93, 26A464DC28694393 ; Airspy serial number list - (COMMA SPACE) Works
26A464DC28423E93,26A464DC28694393 ; Airspy serial number list - (COMMA) Not work

The comma is most likely ignored as the .cfg file seems to use SPACE as a delimiter. (like in step size, miles kilometers, search origin)
Don't use commas.

 

[CanesFan95]

And something else. It looks like DSD+ remembers your window sizes and positions now. So you don't need all the wsl wch etc. command arguments anymore. You just drag and size the windows where you want and it'll remember it for next time. The only thing I can't figure out now is how the numbering works form minimizing. Not sure "bitmapped" means.

 

[thewraith2008]

And something else. It looks like DSD+ remembers your window sizes and positions now. So you don't need all the wsl wch etc. command arguments anymore. You just drag and size the windows where you want and it'll remember it for next time. The only thing I can't figure out now is how the numbering works form minimizing. Not sure "bitmapped" means.

DSDPlus has remembered windows for a while now, it's stored in DSDPlus.bin
wsl wch is still good to use if you wish to arrange windows for different types of sessions.

Here bitmapped means that each bit affects a certain window in DSDPlus.
The value used to minimize "-_<num>" is 8 bits - 00000000 (0 to 255) each bit from right to left is 2 x previous bit in value. 128, 64, 32, 16, 8, 4, 2, 1

    Bit value:
     0 = Window normal
     1 = Window minimized

    Bit Allocation:
     7 = 0  N/A
     6 = 0  N/A
     5 = 0  N/A
     4 = 0  N/A 
     3 = Event Log window
     2 = Channel activity window
     1 = Source Audio window
     0 = Console window

So if you want Source Audio window and Console window minimized, then it would be:
Set bits to '1' to minimize that window.

76543210 - bit number
00000011 = 2 + 1 = 3

-_<num> is command line option the minimize so using:

-_3

Will minimize 'Source Audio' window and 'Console' window.

 

[slicerwizard]

The comma is most likely ignored as the .cfg file seems to use SPACE as a delimiter. (like in step size, miles kilometers, search origin)
Don't use commas.

^ What he said. ^

DSDPlus has remembered windows for a while now, it's stored in DSDPlus.bin

^ What he said. ^

 

[CanesFan95]

Excellent explanation wraith. It took me a moment to grasp it, but now I can make it do exactly what windows and sizes / positions I want. I'm noting now that instead of getting 2 Source Audio Windows, you only get the VC one and not the CC one. Is this a change that was made?

And I thought there used to be a hot key that would clear the data in the status bar in the Event Log and make DSD+ re-aqcuire the info, like color codes, site #'s, etc. You know how DSD+ would keep displaying an old color code and if you scan around with your discriminator tap, that would trick into getting the wrong color code. So you had to hit that hot key on the keyboard to make DSD+ refresh the status bar. I can't seem to find that hot key anymore. Anyone remember what it was?

 

[mtindor]

Excellent explanation wraith. It took me a moment to grasp it, but now I can make it do exactly what windows and sizes / positions I want. I'm noting now that instead of getting 2 Source Audio Windows, you only get the VC one and not the CC one. Is this a change that was made?

And I thought there used to be a hot key that would clear the data in the status bar in the Event Log and make DSD+ re-aqcuire the info, like color codes, site #'s, etc. You know how DSD+ would keep displaying an old color code and if you scan around with your discriminator tap, that would trick into getting the wrong color code. So you had to hit that hot key on the keyboard to make DSD+ refresh the status bar. I can't seem to find that hot key anymore. Anyone remember what it was?

"d"

 

[CanesFan95]

It doesn't seem to work anymore.

 

[mtindor]

It doesn't seem to work anymore.

Did you go into the menu system and enable the hotkeys? They are disabled by default and you are to use the menu system by default. If you want hotkeys turn them on.

 

[CanesFan95]

That did it, thanks.

 

[Steve999]

When I run dsd from the windows batch file I can select the input as VAC. But since this upgrade I cant select the input in dsdplus.exe which is what I've always ran dsd from. In dsdplus.exe that option is not selectable from the new menu system its greyed out? How do I change that please?

 

[mtindor]

When I run dsd from the windows batch file I can select the input as VAC. But since this upgrade I cant select the input in dsdplus.exe which is what I've always ran dsd from. In dsdplus.exe that option is not selectable from the new menu system its greyed out? How do I change that please?

And if you read through this thread, you'd have read the answer to your problem -- probably a half dozen times. RIF - reading is fundamental. I remember that PSA on television back in the 70s/80s.

The DSDPlus Event Log window has a menu system now. Use your mouse to navigate to Control, and select Passive Digital Monitor. Then go over and click on Input and your vacs will be available to you.

Mike

 

[Steve999]

And if you read through this thread, you'd have read the answer to your problem -- probably a half dozen times. RIF - reading is fundamental. I remember that PSA on television back in the 70s/80s.

The DSDPlus Event Log window has a menu system now. Use your mouse to navigate to Control, and select Passive Digital Monitor. Then go over and click on Input and your vacs will be available to you.

Mike

Mike thank you, I must look on a PC not a mobile and I may actually find what i'm looking for

 

[garys]

I seem to have done something dumb regarding audio output. In the Control column there are five choices for "Group Voice Calls"

Group Voice Calls
L/O
Low Priority
Normal Handling
Incl Radio Priority
High Priority

When I select "Normal Handling" any Talk Group set to "Low" is muted. If set that to 95 or higher, audio is processed properly. If I set it L/O all of the Lock Outs are turned off. I'm not clear on how this is supposed to function.

Also, I had to change to a different set of speakers and for some reason, I now get Audio for the odd numbered LCN on one side and for the even on the other. I'm pretty sure that before I switched to the new speakers all audio came out of both speakers. Both sets of speakers are stereo, I have no idea why that's happening.

If anyone can help me out with either or both issues, I'd appreciate it.