DSDPlus Interpreting error codes and other information

[KC9LQV]

Is there a primer somewhere that explains the information presented in the command window while decoding? I'm quite new to DSD+, but I've had good luck getting it up and running. Audio quality is quite good, nearly on par with my "regular" radios. But I'd like to learn more about all that "gibberish" scrolling by, and see if it will let me tweak my setup to obtain the best decodes possible.

I've found lots and lots of info on how to set up the program, and what the command/startup options are, but not so much that helps me understand what's going on once it actually starts running.

Thanks in advance.

 

[TheButcher]

Gain is important and so is a good outdoor aerial. I set gain to bring CC about half way up on the spectrum in FMP24. Too much gain and tuner overloads. Too low and signal is too weak. -Just saying...

 

[KC9LQV]

You are of course completely right on both counts.

As I experimented with my setup, I discovered that DSD+ doesn't seem to need or like nearly as much signal as other OTA data programs I use. But once I got it dialed in, the number of errors dropped dramatically and the audio quality improved.

However, there's still a lot of information flying by even when the encodes are rock solid. I'd just like to find a "beginner's guide" to what it all means. I've been able to of course glean some of the obvious stuff, like "unrecoverable NID" or "invalid DUID", but there's a lot I don't understand.

FWIW, I'm using good-old-fashioned discriminator input and Unitrunker to drive the setup.

 

[maus92]

Gain is important and so is a good outdoor aerial. I set gain to bring CC about half way up on the spectrum in FMP24. Too much gain and tuner overloads. Too low and signal is too weak. -Just saying...

I *think* he's talking about the data words that the program decodes / displays, and what they mean.

 

[TheButcher]

"once I got it dialed in, the number of errors dropped dramatically and the audio quality improved. "

That was my point!!!




"However, there's still a lot of information flying by even when the encodes are rock solid. I'd just like to find a "beginner's guide" to what it all means."

I tend to minimised that window in fear of being hypnotised.



"FWIW, I'm using good-old-fashioned discriminator input and Unitrunker to drive the setup. "

I would seriously suggest buying DSD+ FL. Then use FMP24 to feed DSD+ via it's TCP link. For $30 USD (From memory), you will have lots of fun. Many improvements have been made since the free version was released. Also, using an SDR is the way to go these days... Oh and with discriminator tap, you must set the audio level correctly (sorry if I am telling you how to suck eggs!)


"I *think* he's talking about the data words that the program decodes / displays, and what they mean. "

Yes I was aware of that. Are you running DSD+ FL ?? Mr. KC9LQV ? With good aerial and setup (gain set right and FL), one should not get too many errors.

 

[kruser]

Is there a primer somewhere that explains the information presented in the command window while decoding? I'm quite new to DSD+, but I've had good luck getting it up and running. Audio quality is quite good, nearly on par with my "regular" radios. But I'd like to learn more about all that "gibberish" scrolling by, and see if it will let me tweak my setup to obtain the best decodes possible.

I've found lots and lots of info on how to set up the program, and what the command/startup options are, but not so much that helps me understand what's going on once it actually starts running.

Thanks in advance.

Good question! I also often wonder the same. I do know a lot of the errors seem to be system type specific but then some seem common to everything.
I usually use discriminator audio to feed DSD+ FL. It works well. I use an older Icom R2500 and I can watch the main DSD+ Command window while adjusting the radios bandwidth or other settings as well as audio gain settings in the computers audio mixer controls.
I found it pretty easy to adjust for less ERR indications flying by in the DSD+ command window but there are still errors seen. Many seem to be errors maybe when DSD+ does not understand an opcode it sees possibly. That's just a guess but seems possible.
A guide of the error codes and their causes would be handy if it's something that can be put together.

And yes, I'm talking more about the error codes seen that are not caused by signal issues but are codes generated by DSD+ when it does not understand some data it sees.

 

[shajoe44]

delete

 

[KC9LQV]

Thanks for all the replies thus far. To answer some/most of the questions in no particular order:

Yes, I'm running the Fast Lane version. Partly because I want to be ahead of the curve when/if our local system switches to P25p2, but mostly because the small amount of money spent for such a useful program is a bargain, and I want to encourage its continued development.

Regarding errors: as I mentioned above, I'm really not getting that many errors. In most cases, the audio is quite good. Running DSDtune and adjusting my input levels did wonders. But even on a rock-solid, five-by-five decode, there are still a few. Im sure that when it comes right down to it, "if it sounds good, it IS good"*, but I'm still curious. What surprises me is that there isn't a simple list somewhere that states "e:12=this" or "e:Fr=this". I would have thought that part and parcel of the process.


* Cookie for the reference.

 

[slicerwizard]

What surprises me is that there isn't a simple list somewhere that states "e:12=this" or "e:Fr=this". I would have thought that part and parcel of the process.

1 = voice frame with 1 detected bit error

2 = voice frame with 2 detected bit errors

F = voice frame with 15 detected bit errors (sounds like a completely trashed IMBE [P25 Phase I] voice frame)

r = repeating previous voice frame (too many bit errors in current voice frame)

 

[TheButcher]

"FWIW, I'm using good-old-fashioned discriminator input and Unitrunker to drive the setup. "


Don't do that. Use FMP24 and pass audio via TCP/IP link. You are doing things the hard way! (Open the original .bat files with a text editor. Also, read ALL the *.txt files. very useful info, although a bit hard to get one's head around, I must admit for the first time).


ps. DSD+ FL contains FMP24 etc... Free version does not.

 

[KC9LQV]

"FWIW, I'm using good-old-fashioned discriminator input and Unitrunker to drive the setup. "


Don't do that. Use FMP24 and pass audio via TCP/IP link. You are doing things the hard way! (Open the original .bat files with a text editor. Also, read ALL the *.txt files. very useful info, although a bit hard to get one's head around, I must admit for the first time).


ps. DSD+ FL contains FMP24 etc... Free version does not.

I realize that SDR is what all the cool kids are using these days, and if I were starting over from scratch, that's certainly what I would be using. But with that said, I've got perfectly good Maxtracs, M214s, and a set of PCR100s that are working quite well, and have been for years. Considering all the confusion I see around getting SDRs to play nice with Unitrunker and DSD+, hooking everything up and selecting an iMic for audio in surely doesn't seem like the hard way.

 

[KC9LQV]

1 = voice frame with 1 detected bit error

2 = voice frame with 2 detected bit errors

F = voice frame with 15 detected bit errors (sounds like a completely trashed IMBE [P25 Phase I] voice frame)

r = repeating previous voice frame (too many bit errors in current voice frame)

Okay, now you're just teasing.

 

[TheButcher]

SDR is not that hard to set up. The version 3 ones are good. With TV type splitters with F connectors, one can set up 4 or so dongles that run from one aerial.

Benefit of dongles compared to disc-tap is, MUCH wider frequency range and more desk space, which you will appreciate is of a premium!

 

[maus92]

Yea, the SDRs are not hard to configure if you can comprehend the instructions, and have the appropriate hardware resources.