DSD Plus Console Window query

Status
Not open for further replies.

EI8EJB

Member
Joined
Oct 25, 2016
Messages
4
Location
Ireland
Hi, can anyone post what exactly is the information that is displayed in the DSD Plus 1.101 Console window? I know some of the basic information, but is there an actual list as to what is displayed in each column? Especially as to what values are usable for decode and what values are classed as errors.

Thanks in advance for any help,

Brian
 

mtindor

OH/WV DB Admin
Database Admin
Joined
Dec 5, 2006
Messages
10,394
Location
Carroll Co OH / EN90LN
Hi, can anyone post what exactly is the information that is displayed in the DSD Plus 1.101 Console window? I know some of the basic information, but is there an actual list as to what is displayed in each column? Especially as to what values are usable for decode and what values are classed as errors.

Thanks in advance for any help,

Brian

Why don't you download it from DSDPlus – Digital Decoder and run it in a console yourself. Certainly much easier.

Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\DSDPlusRocks>cd\dsdplus101

C:\DSDPlus101>dsdplus -h

DSD+ 1.101pt

Usage:
  DSDPlus [options]            Decode from audio stream
  DSDPlus [options] ? file     Decode from .wav file
  DSDPlus -h                   Show help

Options ( [...] = default value):

Display/Logging options:
  >file       Create log file
  >>file      Append to log file
  -_<num>     Minimize selected windows at startup (bitmapped, 0-15) [-_0]
  --          Show command line options in console window title
  -t          Time stamp console log file entries
  -T          Time stamp console log file entries and console screen data
  -E          Add NAC/RAN/DCC/RAS data to event log file entries
  -H<num>     High contrast mode (bitmapped, 0-63) [-H0]
  -v<num>     Frame information verbosity (0-4) [-v2]

  -wsl<v>.<h> Source audio waveform window location [-wsl10.10]
  -wss<h>.<w> Source audio waveform window size (0.0 blocks) [-wss200.300]
  -wsp<num>   Source audio waveform window update period (10-1000) [-wsp100]

  -wel<v>.<h> Event log window location [-wel50.50]
  -wes<h>.<w> Event log window size (min ?) [-wes400.500]
  -weh<num>   Event log window font height [-weh15]

  -wcl<v>.<h> Channel window location [-wcl90.90]
  -wch<num>   Channel window font height [-wch15]

Input/Output options:
  -i<spec>    Input audio device (1-255) and channel (M/L/R) [-i1M]
  -i<[addr:]port> FMP TCP link IPv4 address and port number

  -g<num>     Output audio gain (0.001-999; 0=auto) [-g0]

  -o<spec>    Output audio device (1-255; 0=none) and channel (M/L/R) [-o1]
                in/out channels are optional; default=in:mono, out:mode based

  -Och <file> Output audio file channel count and name/type [-O DSDPlus.wav]
                ch: M=mono,S=stereo,blank=auto; file: .wav or .mp3 (NUL=none)

  -I<num>     Create new wav/mp3 file every <num> minutes (1440=daily) [-I0]

  -P<wav|mp3> Also create per-call wav or mp3 files

  -M<num>     MP3 ABR kbps per channel (8-32) [-M15]

Decoder options:
  -rc         role is control/rest channel decoder
  -rv         role is voice channel decoder

  -p          Invert signal polarity (may be required for X2-TDMA and dPMR)
  -mp         optimize for PSK modulation (will not decode non-PSK)

  -fa         Auto-detect all protocols / frame types except dPMR [-fa]
  -fd         Decode D-STAR (no audio)
  -fn         Decode NXDN4800 (Kenwood NEXEDGE and Icom IDAS)
  -fN         Decode NXDN9600 (Kenwood NEXEDGE)
  -fr         Decode DMR/MotoTRBO (TDMA inputs + both output slots)
  -f1         Decode P25 Phase 1
  -fx         Decode X2-TDMA
  -fp         Decode ProVoice
  -fm         Enable dPMR decoding (no audio)

  -1          Synthesize audio for first DMR timeslot
  -2          Synthesize audio for second DMR timeslot

  -UA<num>    AMBE unvoiced speech level (0-100) [-UA50]
  -UI<num>    IMBE unvoiced speech level (0-100) [-UI50]
  -u<num>     Unvoiced speech quality (1-64) [-u3]
  -e          Auto-mute encrypted voice

Advanced decoder options:
  -dr<num>    Rolloff filter (1-11; 0=auto) [-dr0]
  -dh<num>    Hotspot size (1-8; 0=auto) [-dh0]
  -ds<num>    Scaling factor (55-75; not used with D-Star or ProVoice) [-ds64]
  -dd<num>    Damping level (1-100; not used with D-Star or ProVoice) [-dd10]
  -dv<num>    Viewport size (1-30; not used with D-Star or ProVoice) [-dv20]

Active keys:
  ?           Display active keys list in event log window
  1           Synthesize audio for first DMR timeslot
  2           Synthesize audio for second DMR timeslot
  3           Synthesize audio for both DMR timeslots
  -           Toggle command line options display
  |           Toggle symbol phase display
  A/a         Adjust AMBE unvoiced audio level
  B           Show/hide background events in event log window
  E           Toggle auto-muting of encrypted voice
  F           Forget current system information
  H           Cycle high contrast modes
  I/i         Adjust IMBE unvoiced audio level
  N           Reset/redisplay neighbor list
  P           Toggle signal polarity
  R           Start/stop recording of raw source audio to wav file
  S           Close/reopen source audio waveform display
  V           Toggle voice call start alerts
  W           Display window locations and high contrast value
  Spacebar    Hold on current call
  Esc         End program

Source Audio Window:
  Right click   Pause/unpause source audio waveform display

Channel Activity Window:
  Left click on priority    Increase traffic priority
  Right click on priority   Decrease traffic priority
  Left click on target      Increase priority override
  Right click on target     Decrease priority override
  Left click on headings    Clear all lockouts
  Right click on headings   Clear hold

C:\DSDPlus101>

Mike
 

EI8EJB

Member
Joined
Oct 25, 2016
Messages
4
Location
Ireland
Hi Mike,

Many thanks for taking the time to reply! What I was more interested in (and probably phrased it badly in my question) was when DSD+ 1.101 is running and actively decoding DMR for instance, I was just wondering what exactly is the information that scrolls in the Console Window and and can I utilise that information to enhance my use of DSD+ 1.101?

Once again I do appreciate the help,

Regards,

Brian
 

jkraemer

Member
Premium Subscriber
Joined
Jun 30, 2015
Messages
57
Location
BEE00
Hi Mike,

Many thanks for taking the time to reply! What I was more interested in (and probably phrased it badly in my question) was when DSD+ 1.101 is running and actively decoding DMR for instance, I was just wondering what exactly is the information that scrolls in the Console Window and and can I utilise that information to enhance my use of DSD+ 1.101?

Once again I do appreciate the help,

Regards,

Brian

Brian - hopefully the attached is what you're looking for.
 

Attachments

  • DSD_Activity.jpg
    DSD_Activity.jpg
    10.7 KB · Views: 622
  • DSD_Console.jpg
    DSD_Console.jpg
    62.8 KB · Views: 693
Last edited:

EI8EJB

Member
Joined
Oct 25, 2016
Messages
4
Location
Ireland
Hi, Thanks for that.

Yes, this is the active Console window that I'm talking about, but unfortunately some of the information in the script is unclear to me. Such as in your instance, Slots are self explanatory, as are the DCC for Colour Codes, BS for Base Stations and TG for Talk Groups, but what about the other heading such as CSBKO, FID, v16, id1 and id2? Its these, and other such data abbreviations that I cannot find any description for! Is there any listing that gives a breakdown of these abbreviations formats?

Much appreciated,

Brian
 

slicerwizard

Member
Joined
Sep 19, 2002
Messages
7,643
Location
Toronto, Ontario
No, I doubt you'll find a listing anywhere.

CSBKO is something like control signaling block opcode, i.e. the message type.

FID = feature ID; IIRC, 16 means Motorola.

v16, id1 and id2: these are portions of the message and sometimes hold talkgroup or radio ID values.
 

EI8EJB

Member
Joined
Oct 25, 2016
Messages
4
Location
Ireland
Thanks Slicerwizard for the info.

I guess trial and error and "working-it-out-as-you-go-along" is the rule?

Thanks to all who replied to my query,

Brian
 
Status
Not open for further replies.
Top