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

[slicerwizard]

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!

FMP24 gets the same error if the .cfg file has a bad search origin. What's your FMPA.cfg file look like?

 

[CanesFan95]

Please delete.

 

[CanesFan95]

Here's the FMPA.cfg file:

 

[garys]

I checked and No Source Audio Monitoring is selected. It only happens when DSD-CC thinks it's lost the Rest Channel. Sometimes it is still locked on the Rest Channel, but chimes anyway. The Event Window shows "lost rest channel, tuning to 45x.xxx and keeps doing that even as it goes past the Rest Channel. I don't know if there is a decoding level setting that I'm missing or something else.

This started only with the latest version.

Gary,

Im not aware of a "chime". There might be one. But, is there any chance that you have some sort of sourcce monitoring enabled under the INPUT menu?

Your source monitoring should be turned off -- "No source audio monitoring"

If you happen to have it set to "1" or "Monitor Source Audio if no Sync and Signal Present" enabled, then it would make some sort of noise (that might be misconstrued as a chime) as it goes searching for the new rest channel.

Mike

 

[BM82557]

Here's the FMPA.cfg file:

From FMPA.txt -

Airspy device numbers are based on Airspy serial numbers;
lowest serial number = device #1, next highest serial number = #2, etc.

Try putting a comma after the first one, see post linked below -

DSDPlus - FMPA with 2 x Airspy R2

 

[BM82557]

V2.228 does tighter checking than previous versions, it might be upset about something in your FMPA config file. I only use one Airspy on this machine but you can compare your setup against mine -

 

[Airspy-US]

Just curious. Are you accessing the machine running DSDPlus remotely (using RDP, or Teamviewer, etc) ? Or are you only accessing that machine via local monitor/keyboard/mouse? I ask because I've reported the same thing, although I access the DSDPlus PC remotely over RDP.

I have reported this to the author.

Mike

Hi, Mike. Long time no post. Yes, the avatar needs updated.

We are receiving these very consistently on PCs used for calibrations.

IF we do not start an instance of SDR# the DSD works fine (Two Airspy R2s, FL 228, FMPA on both, CC and VC decode).

IF we then start SDR# with a third dongle, the errors start any time there is decode activity.

IF we then restart DSD+, everything works fine again until we start another instance of SDR#.

Not sure if this will help the diagnosis, but it is quite annoying, as we are constantly starting SDR# on those PCs.

We are running VNC on them (beats a dozen keyboards, mice, and monitors on the desk) but that does not seem to be directly related to the issue.

It's suspected that somehow DSD is seeing the activity on the PC from the 'third airspy' and that data is conflicting with the decode.

BTW, never heard a peep about the request to add the date so we know that a decode window has been inactive for 2 hours, or a day and two hours, or a month and two hours. No acknowledgement, no 'get lost', nothing. Other than the dead end email, is there any way to report this?

P.S. The same issue happens in the same way with a 'conventional DMR decode only' PC.

 

[Airspy-US]

From FMPA.txt -

Airspy device numbers are based on Airspy serial numbers;
lowest serial number = device #1, next highest serial number = #2, etc.

Try putting a comma after the first one, see post linked below -

DSDPlus - FMPA with 2 x Airspy R2

The missing comma is definitely an issue. You need it there.

 

[mtindor]

Hi, Mike. Long time no post. Yes, the avatar needs updated.

We are receiving these very consistently on PCs used for calibrations.

IF we do not start an instance of SDR# the DSD works fine (Two Airspy R2s, FL 228, FMPA on both, CC and VC decode).

IF we then start SDR# with a third dongle, the errors start any time there is decode activity.

IF we then restart DSD+, everything works fine again until we start another instance of SDR#.

Not sure if this will help the diagnosis, but it is quite annoying, as we are constantly starting SDR# on those PCs.

We are running VNC on them (beats a dozen keyboards, mice, and monitors on the desk) but that does not seem to be directly related to the issue.

It's suspected that somehow DSD is seeing the activity on the PC from the 'third airspy' and that data is conflicting with the decode.

BTW, never heard a peep about the request to add the date so we know that a decode window has been inactive for 2 hours, or a day and two hours, or a month and two hours. No acknowledgement, no 'get lost', nothing. Other than the dead end email, is there any way to report this?

In my case, the PC in question only has one Airspy R2 connected and no other Airspys or dongles. SDR# is never opened.

In my case, this strictly happens with the latest DSDPLus and FMPA combination, TCP-Linked -- and appears to occur when I use Remote Desktop to remotely access the computer.

Lots of remote access products "fudge" with the audio input/output devices when you log into a remote PC, and I think it has something to do with that.

Mike

 

[Airspy-US]

In my case, the PC in question only has one Airspy R2 connected and no other Airspys or dongles. SDR# is never opened.

In my case, this strictly happens with the latest DSDPLus and FMPA combination, TCP-Linked -- and appears to occur when I use Remote Desktop to remotely access the computer.

Lots of remote access products "fudge" with the audio input/output devices when you log into a remote PC, and I think it has something to do with that.

Mike

It could, but we are getting these errors about 50 times a second when we take the actions described and RealVNC does not support audio AFAIK. (at least not the version we are using)

Also if it were 'fudged up' audio the issue would exist anytime that connection is active (nearly always active but usually minimized). If we restart DSD+, it works without those errors until we start SDR# again - even if the window is still active. In fact, that's the recent SOP - start SDR#, RESTART DSD so we don't lose the data, then go back and use SDR#. Again, suspect the additional Airspy is being seen as another TCP link or something (although it would not be in the config file).

Regardless, it's a good test to try to see if that creates the issue more often. If it helps determine the cause then the report serves the purpose.

Also avatar updated.

 

[mtindor]

It could, but we are getting these errors about 50 times a second when we take the actions described and RealVNC does not support audio AFAIK. (at least not the version we are using)

Regardless, it's a good test to try to see if that creates the issue more often. If it helps determine the cause then the report serves the purpose.

Also avatar updated.

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

 

[jdolina]

When you remote desktop have you tried changing the audio setting (show options) from local resources to play on remote computer. It should then not change the audio devices on the remote system when you connect.

 

[Airspy-US]

Never saw them here before 2.228 either.

LOVE the new menu structure even though we had to change the window sizing on all the PCs. (with menu is about 30 pixels higher on each of the event windows)

Also love the DMR affiliations being listed now.

Perhaps a way to hide that menu list would save valuable window space. Even auto-hide if the author wants to get fancy.

 

[Airspy-US]

Here is a chunk of what the decode window shows when this is happening: (you might not see it this bad if you only get occasional discards)

As you can see, it's not totally fudged. It knows there is a grant there, but it cannot get the voice data. The VC FMPA window seems to be acting normally.

MAC_ACTIVE Group Voice Channel User Slot#1 ENC PRI4 TG=1751 RID=60419
(F0S1-4V)
MAC_IDLE Null Information
Sync:+P25p2 (F2S1-4V)
MAC_IDLE Null Information
(F4S1-4V)
MAC_IDLE Null Information
(F6S1-4V)
MAC_IDLE Null Information
(F8S1-2V)
MAC_IDLE Null Information
MAC_IDLE Group Voice Channel Grant Update [TG=1751 ch=858.0125-1]
MAC_ACTIVE Group Voice Channel User Slot#1 ENC PRI4 TG=1751 RID=60419
(F0S1-4V)
MAC_IDLE Null Information
Sync:+P25p2 (F2S1-4V)
MAC_IDLE Null Information
(F4S1-4V)
MAC_IDLE Null Information
(F6S1-4V)
MAC_IDLE Null Information
(F8S1-2V)
MAC_IDLE Null Information
MAC_IDLE Group Voice Channel Grant Update [TG=1751 ch=858.0125-1]
MAC_ACTIVE Group Voice Channel User Slot#1 ENC PRI4 TG=1751 RID=60419
(F0S1-4V)
MAC_IDLE Null Information
Sync:+P25p2 (F2S1-4V)
MAC_IDLE Null Information
(F4S1-4V)
MAC_IDLE Null Information
(F6S1-4V)
MAC_IDLE Null Information
(F8S1-2V)
MAC_IDLE Null Information
MAC_IDLE Group Voice Channel Grant Update [TG=1751 ch=858.0125-1]
MAC_ACTIVE Group Voice Channel User Slot#1 ENC PRI4 TG=1751 RID=60419
(F0S1-4V)
MAC_IDLE Null Information
Sync:+P25p2 (F2S1-4V)
MAC_IDLE Null Information
(F4S1-4V)
MAC_IDLE Null Information
(F6S1-4V)
MAC_IDLE Null Information
(F8S1-2V)
MAC_IDLE Null Information
MAC_IDLE Group Voice Channel Grant Update [TG=1751 ch=858.0125-1]
MAC_ACTIVE Group Voice Channel User Slot#1 ENC PRI4 TG=1751 RID=60419
(F0S1-4V)

 

[CanesFan95]

From FMPA.txt -

Airspy device numbers are based on Airspy serial numbers;
lowest serial number = device #1, next highest serial number = #2, etc.

Try putting a comma after the first one, see post linked below -

DSDPlus - FMPA with 2 x Airspy R2

Well, I tried adding a comma with and without a space after it and still get errors.

 

[mtindor]

When you remote desktop have you tried changing the audio setting (show options) from local resources to play on remote computer. It should then not change the audio devices on the remote system when you connect.

Yes, that's how I always run it. To be clear, I am only running one SDR device (an Airspy R2), and am only running the latest FMPA+DSDPlus TCP linked. It's the same setup I've been running for ages. And I've never had an issue with these errors before the latest DSDPlus version came out. So I'm gonna fingerpoint at DSDPlus/FMPA associated stuff.

Mike

 

[mtindor]

My FMPA.cfg (with serial numbers obscured):

NOTE: do not add 0x before each serial. That line is simply SERIAL#1 COMMA SERIAL#2 SPACE SPACE SEMICOLON SPACE COMMENT . And it works for me.

<quote>
558466DC2CZZZZZZ,573064DC30ZZZZZZ ; Airspy serial number list
10.0 ; sampling rate (2.5 or 10)
1024 ; spectrum window width
32 ; FFT size (8k, 16k, 32k, 64k)
5 ; 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
19.7163 -155.6241 ; search origin
</quote>

 

[CanesFan95]

Went ahead and tried that, but still getting errors:

 

[machinegeek]

DSD 1.101 has been working fine. Purchased Fastlane and get this error:

"DSD+ 2.228
DSDPlus -h for help summary

Appending synthesized audio to file '1R-DSDPlus.wav'
Current working directory is "C:\Users\Me\Desktop\DSDPlus"

Assuming FMPA/FMPP/FMP24 is signal source; auto polarity detect is disabled

audio output device #1 = 'Speakers (High Definition Audio'
audio output device #2 = 'CABLE Input (VB-Audio Virtual C'

audio output device #1 (Speakers (High Definition Audio) initialized
DSDPlus.networks file not found in working folder
DSDPlus.sites file not found in working folder
DSDPlus.frequencies file not found in working folder
DSDPlus.groups file not found in working folder
DSDPlus.radios file not found in working folder
Required data files not found in working folder"

It's the last part about the missing "DSDPlus." files that I don't get. Where do I find these?

 

[CanesFan95]

Those files should be in the same folder / directory as your DSDPlus.exe file. Do you see them there?