DSD improvements I am working on

[EricCottrell]

One more thing to add Eric,
The frequencies for this trunk system use the Part 22 Pager freqs. Here is a link describing the channel layout:
http://forums.radioreference.com/te...ounty-public-service-systems.html#post2249464

I do have a question, when looking at the data, I see these words: TX_REL_EX, Cause: 2-15, and DISC in the datastream. I see no mention of those in the Read Me file and was just curious to what those mean.
Thanks

Hello,

TX_REL_EX is Transmitter Release Extended. DISC is Disconnect.
Cause in the DISC message is the reason for the disconnection.

1-0 User Disconnect
1-1 PSTN Disconnect
1-4 Timeout (Radio)
1-15 Other Disconnect (Radio)

2-0 Timeout (Traffic Channel)
2-15 Other disconnect (Traffic Channel)

5-0 Channel Unavailable
5-1 Network Failure
5-2 Temporary Failure
5-3 Equipment Congestion
5-15 Other Resource Unavailable

6-0 Service Unavailable
6-1 Service Unsupported
6-15 Other Service Unavailable or Unsupported

7-0 Lack of Information
7-1 Invalid Information
7-15 Other Procedure Error

73 Eric

 

[RonnieUSA]

This is what I am getting, but I would also like to decoe NXDN9600, P25, and DMR also, I I just add the switches for them also?

Thank You for any help on this.

 

[EricCottrell]

Hello,

If you eliminate the -fi option on the command line, dsd will automatically decode NXDN96, P25, and DMR. You need to specify the -fi option to decode NXDN48 because dsd does not detect it automatically.

73 Eric

 

[RonnieUSA]

Hello,

If you eliminate the -fi option on the command line, dsd will automatically decode NXDN96, P25, and DMR. You need to specify the -fi option to decode NXDN48 because dsd does not detect it automatically.

73 Eric

Thank You very much.

 

[kd7kdc]

I got my install to work using the -fi option. The program seems to still take up a lot of computer resources. However it dose seem to decode info correctly on nx 4800 systems. I have not tried the other modes

 

[moonbounce]

Perfect decode on AP 25, and DMR. Thanks for all the hard work Eric.

Moonbounce

 

[RonnieUSA]

Hello,

If you eliminate the -fi option on the command line, dsd will automatically decode NXDN96, P25, and DMR.

So I don't need a switch to listen to these 3 modes?

You need to specify the -fi option to decode NXDN48 because dsd does not detect it automatically.

This mode must be listened to alone, not mixed with the 3 above modes, correct?

Sorry if I'm a little slow about trying to understand your software.

 

[Forts]

I'm trying to give this software a look, but I can't get it to run.. On multiple PC's all I get is:

ERROR: Requested device 2 is not an output device.

If I try to specify another output device with -o I always get an invalid device error. Suggestions?

 

[RonnieUSA]

I'm trying to give this software a look, but I can't get it to run.. On multiple PC's all I get is:

ERROR: Requested device 2 is not an output device.

If I try to specify another output device with -o I always get an invalid device error. Suggestions?

I had the same problem to start with, It turned out my speakers were 4.
So it would look like this, -o pa:4

Hope this helps.

 

[Forts]

ahha! I wasn't using the 'pa' bit. Thanks!!

 

[RonnieUSA]

ahha! I wasn't using the 'pa' bit. Thanks!!

Glad I could be of help.

 

[EricCottrell]

So I don't need a switch to listen to these 3 modes?


This mode must be listened to alone, not mixed with the 3 above modes, correct?

Sorry if I'm a little slow about trying to understand your software.

Hello,

Yes. It works the same as the Linux version of dsd. The base code is dsd, with some options disabled. Supporting all the options would require writing code to support the Windows method of things.

The portaudio support and the requirement to enter pa: is also in the latest Linux dsd code.

I get audio input overruns just by holding the thumb on the window scrollbar. That is a problem with programs using one thread of program execution. The overruns were likely hidden in previous window ports because the error was not detected and displayed. One method of fixing this is to separate program into two or more threads.

DOS and Linux programs ported to Windows console can seem like resource hogs. DOS program assume they are the only program running so will do idle loops waiting for something to happen. It is not much of a concern under Linux due to how the OS works. Windows schedules programs differently and it is easier for a program to take all the free CPU time.

I have seen DOS programs take nearly 100 percent of CPU time, but the system remained responsive. Time was taken away from the DOS program when the other tasks needed CPU time. The 100 percent problem can be fixed by adding system calls to give up CPU time inside idle loops or using Windows event processing.

I am currently improving the NXDN decoding by decoding more messages and elements. Group calls will use the GI: identifier instead of either the GI: or DI: identifier. I am also rearranging the display order of the elements to be more consistent.

73 Eric

 

[RonnieUSA]

Thank You for the answer.
I don't use Linux, and have never tried DSD using Linux.

It's not what I wanted to hear, but will live with it.

Again Thank You for the great work.

 

[n4yek]

Eric,
Here is another word in the NXDN Data stream i didn't find in the readme file: scram <3>
Info???
Danny

 

[EricCottrell]

Eric,
Here is another word in the NXDN Data stream i didn't find in the readme file: scram <3>
Info???
Danny

Hello,

That would be Scrambled Voice.

Clear(0) - Clear (Unencrypted)
Scram - Scramble 15 Bit Encryption n = key id
DES - DES 56 Bit Encryption n = key id
AES - AES 256 Bit Encryption n = key id

73 Eric

 

[RonnieUSA]

Eric,

I have been bored today, and tried a new switch with your copy of DSD, and I'm wonder what I'm seeing.
The switch is -v4, and the sample output is listed below.

Sync: -NXDN48 o: 18 mod: GFSK g: 12.682599 inlvl: 2% Repeater Ch VOICE e:
Sync: -NXDN48 o: 18 mod: GFSK g: 14.588017 inlvl: 2% Repeater Ch VOICE e:
Sync: -NXDN48 o: 18 mod: GFSK g: 15.317417 inlvl: 2% Repeater Ch VOICE e:
Sync: -NXDN48 o: 18 mod: GFSK g: 18.618416 inlvl: 2% Repeater Ch VOICE e:
SACCH: RAN:32 VCALL GC SI:803 DI:0 Clear(0)

Sync: -NXDN48 o: 18 mod: GFSK g: 9.382007 inlvl: 2% Repeater Ch VOICE e:=
Sync: -NXDN48 o: 18 mod: GFSK g: 11.403888 inlvl: 2% Repeater Ch VOICE e:
Sync: -NXDN48 o: 18 mod: GFSK g: 13.861497 inlvl: 2% Repeater Ch VOICE e:
Sync: -NXDN48 o: 18 mod: GFSK g: 16.848736 inlvl: 2% Repeater Ch VOICE e:
SACCH: RAN:32 VCALL GC SI:1000 DI:0 Clear(0)

 

[W4KRR]

DSD works fine decoding DMR, but I can't get it to decode NXDN48 at all.

I launch it from the command line using the -fi switch. Nothing. Yet DSD Plus works fine on NXDN48. I am using the same audio settings for both. Ideas?

 

[RonnieUSA]

DSD works fine decoding DMR, but I can't get it to decode NXDN48 at all.

I launch it from the command line using the -fi switch. Nothing. Yet DSD Plus works fine on NXDN48. I am using the same audio settings for both. Ideas?

I use a tapped scanner to listen to NXDN48 just fine, just don't forget the switches for input, and output. -i pa: and -o pa:

Good Luck

 

[W4KRR]

Ronnie, I don't use the switches for input/output when decoding DMR; do I need them for NXDN?

 

[RonnieUSA]

Ronnie, I don't use the switches for input/output when decoding DMR; do I need them for NXDN?

With WinDSD You do need those switches, also You will need the -fi to decode NXDN48, but not with DSD+ .