DSDPlus Causes of unrecoverable NID

[jets1961]

Like subject says: What are some causes of "unrecoverable NID" in DSD+.

I am running latest version of DSD+ (2p368) the system is 99.5% encrypted with AES256. The signal is very good and I have gain at 16.6.

I am noticing that some TG report weird Algorithm ID's when it should all be AES-256. The system is a Motorola phase 1 system.

 

[a417]

is it consistent with a particular TGID?

 

[jets1961]

I have not observed closely enough to say. But the I do know that currently the radio system might be patched to the next province over that being MB and SK.

As for the weird aglo ID's it's on a bunch of TG's all the weird aglos being reported are on a few TG's.

I use different folders for different systems in my setup. I update the base files at one point in one folder because I had a problem. I think I will try that for the system that is acting up. I know it used to work just fine a few months ago.

 

[AM909]

If you're using FMP24 as your tuner/demodulator, try adding option "-e1" to the command-line. If you're not using FMP24, try using it.

 

[jets1961]

Using FMP24, I will update base files tomorrow see if it fixes it then if not I will try "-e1". What is it's usage?

 

[rivardj]

From the Notes file:

FMP24 2.74

Added automatic detection of I/Q stream dropouts.
Added automatic enabling of extra CPU loading to stop I/Q stream dropouts.

Command line change:

-e0: Extra CPU loading disabled; FMP24 will report I/Q stream dropouts in console window
-e1: Extra CPU loading enabled
-e2: Automatic enabling of extra CPU loading if I/Q stream dropouts are detected

Default is -e2

Active key change:

Pressing E will cycle through the above three modes