Advertisement
Guest User

Untitled

a guest
Sep 3rd, 2015
2,413
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 16.88 KB | None | 0 0
  1.  
  2.  
  3. DSD+ 1.074 User Guide
  4. ---------------------
  5.  
  6.  
  7. Installation
  8. ------------
  9.  
  10. This application can create many audio files and log files,
  11. so consider using a dedicated folder to run it from.
  12.  
  13. The folder can be on your desktop (desktop\DSDPlus) or
  14. off the root folder (C:\DSDPlus), for example.
  15.  
  16. After copying the zip file contents to the installation folder,
  17. you should probably create a shortcut on your desktop.
  18. The shortcut should run cmd.exe in the installation folder
  19.  
  20. Shortcut properties:
  21.  
  22. Target: %windir%\system32\cmd.exe
  23.  
  24. Start in: <your DSDPlus folder>
  25.  
  26. Layout / Window size: Width should be about 100 (120 if displaying timestamps)
  27.  
  28.  
  29.  
  30. Usage/Options Summary
  31. ---------------------
  32.  
  33. Usage:
  34. DSDPlus [options] Decode from audio stream
  35. DSDPlus [options] ? file Decode from .wav file
  36. DSDPlus -h Show help
  37.  
  38. Options ( [...] = default value):
  39.  
  40. Display/Logging options:
  41. -- Show command line options in window title
  42. >file Create log file
  43. >>file Append to log file
  44. -t Time stamp log file entries
  45. -T Time stamp log file entries and on screen data
  46. -v<num> Frame information verbosity (0-4) [-v2]
  47.  
  48. -wsl<v>.<h> Source audio waveform window location [10.10]
  49. -wss<h>.<w> Source audio waveform window size (min 50.200; 0 blocks) [200.300]
  50. -wsp<num> Source audio waveform window update period (10-1000) [100]
  51.  
  52. -wel<v>.<h> Event log window location [50.50]
  53. -wes<h>.<w> Event log window size (min ?) [400.500]
  54. -weh<num> Event log window font height [15]
  55.  
  56. -wcl<v>.<h> Channel window location [90.90]
  57. -wch<num> Channel window font height [15]
  58.  
  59. Input/Output options:
  60. -i<spec> Input audio device (1-255) and channel (M/L/R) [-i1M]
  61.  
  62. -g<num> Output audio gain (0.001-999; 0=auto) [-g0]
  63.  
  64. -o<spec> Output audio device (1-255; 0=none) and channel (M/L/R) [-o1]
  65. in/out channels are optional; default=in:mono, out:mode based
  66.  
  67. -Och <file> Output audio file channel count and name/type [-O DSDPlus.wav]
  68. ch: M=mono,S=stereo,blank=auto; file: .wav or .mp3 (NUL=none)
  69.  
  70. -I<num> Create new wav/mp3 file every <num> minutes (1440=daily) [-I0]
  71.  
  72. -M<num> MP3 ABR kbps per channel (8-32) [-M15]
  73.  
  74. Decoder options:
  75. -p Invert signal polarity (may be required for X2-TDMA and dPMR)
  76. -mp optimize for PSK modulation (will not decode non-PSK)
  77.  
  78. -fa Auto-detect all protocols / frame types except dPMR [-fa]
  79. -fd Decode D-STAR (no audio)
  80. -fn Decode NXDN4800 (Kenwood NEXEDGE and Icom IDAS)
  81. -fN Decode NXDN9600 (Kenwood NEXEDGE)
  82. -fr Decode DMR/MotoTRBO (TDMA inputs + both output slots)
  83. -f1 Decode P25 Phase 1
  84. -fx Decode X2-TDMA
  85. -fp Decode ProVoice
  86. -fm Enable dPMR decoding (no audio)
  87.  
  88. -1 Synthesize audio for first DMR timeslot
  89. -2 Synthesize audio for second DMR timeslot
  90.  
  91. -u<num> Unvoiced speech quality (1-64) [-u3]
  92. -e Auto-mute encrypted voice
  93.  
  94. Advanced decoder options:
  95. -dr<num> Rolloff filter (1-11; 0=auto) [-dr0]
  96. -dh<num> Hotspot size (1-8; 0=auto) [-dh0]
  97. -ds<num> Scaling factor (55-75; not used with D-Star or ProVoice) [-ds64]
  98. -dd<num> Damping level (1-100; not used with D-Star or ProVoice) [-dd10]
  99. -dv<num> Viewport size (1-30; not used with D-Star or ProVoice) [-dv20]
  100.  
  101. Active keys:
  102. ? Display active keys list in event log window
  103. 1 Synthesize audio for first DMR timeslot
  104. 2 Synthesize audio for second DMR timeslot
  105. 3 Synthesize audio for both DMR timeslots
  106. - Toggle command line options display
  107. | Toggle symbol phase display
  108. B Show/hide background events in event log window
  109. E Toggle auto-muting of encrypted voice
  110. F Forget current system information
  111. N Reset/redisplay neighbor list
  112. P Toggle signal polarity
  113. R Start/stop recording of raw source audio to wav file
  114. S Close/reopen source audio waveform display
  115. W Display window locations
  116. Esc End program
  117.  
  118. Source Audio:
  119. Right click Pause/unpause source audio waveform display
  120.  
  121.  
  122.  
  123. Run Modes
  124. ---------
  125.  
  126. The program can decode live discriminator audio or recorded .wav files.
  127. Recorded audio files must be 48 or 96 kHz 16 bit mono PCM .wav files.
  128.  
  129.  
  130.  
  131. Logging
  132. -------
  133.  
  134. -v
  135. -v0 generates minimal output.
  136. Use -v3 or -v4 for maximum data logging.
  137. Program output can be sent to a log file ( DSDPlus >logfile )
  138.  
  139.  
  140.  
  141. Input/Output
  142. ------------
  143.  
  144. -i -o
  145. WaveIn/Out devices are listed at program startup.
  146. Select your devices if you don't want to use the defaults.
  147. Use -o0 to disable output audio.
  148.  
  149. -O
  150. By default, all synthesized audio is written/appended to DSDPlus.wav
  151. Use -O name.ext to write synthesized audio to another .wav or .mp3 file.
  152. Use -O NUL to disable recording of synthesized audio.
  153.  
  154. -I
  155. Use -I# to start a new synthesized audio recording file every # minutes.
  156.  
  157.  
  158.  
  159. Decoder Options
  160. ---------------
  161.  
  162. -fa
  163. Using -fa (or nothing) will (usually) auto-decode all supported protocols.
  164. Polarity of signals is auto-detected.
  165. Note: -fa does not enable dPMR detection; -fm must be used to enable dPMR
  166.  
  167. -fd -fn -fN -fr -f1 -fx -fp -fm
  168. When monitoring a single type of traffic, locking the protocol can provide
  169. slightly better decoding results.
  170. Note: more than one protocol can be enabled via the command line.
  171.  
  172. -u
  173. Lower values (slightly) reduce CPU load.
  174.  
  175. -e
  176. Use to enable auto-muting of encrypted voice traffic
  177.  
  178.  
  179.  
  180. Advanced Decoder Options
  181. ------------------------
  182.  
  183. Fine tuning the advanced decoder options can greatly increase decoding rates.
  184.  
  185. Different systems, protocols, receivers and PC sound devices require unique
  186. fine tuning values.
  187.  
  188. A 15 to 60 second recording of voice traffic on a target system should be made
  189. and used as the input for tuning runs. Use the 'R' key to make recordings.
  190. Recordings of control channels or rest channels are also useable.
  191.  
  192. To speed up the tuning process, audio synthesis should be disabled
  193. and the protocol should be locked correctly:
  194.  
  195. DSDPlus ? rawAudio.wav -o0 -O NUL -f1
  196.  
  197. A decoding score will be displayed.
  198.  
  199. Pressing the up arrow will redisplay the previous command line,
  200. which you can then edit and re-run.
  201.  
  202. Adjust a single parameter to determine which value produces the highest score:
  203.  
  204. DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr1
  205. DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr2
  206. DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr3
  207. DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr4
  208.  
  209. When the optimal value for a tuning parameter is determined,
  210. use that value (#) and add another parameter and repeat the tuning steps:
  211.  
  212. DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr# -dh1
  213. DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr# -dh2
  214. DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr# -dh3
  215. ...
  216.  
  217. Repeat until all advanced decoding options have been fine tuned.
  218.  
  219.  
  220. The recommended order for adjusting tuning parameters is:
  221.  
  222. 1: Rolloff filtering (-dr)
  223. 2: Hotspot size (-dh)
  224. 3: Scaling factor (-ds)
  225. 4: Damping level (-dd)
  226.  
  227. Viewport tuning is rarely worth bothering with.
  228.  
  229. Damping settings do not affect D-Star or ProVoice,
  230. so don't bother tweaking them for those protocols.
  231.  
  232.  
  233. You do NOT have to try every value for a tuning parameter:
  234.  
  235. Rolloff: start at 1 and go up by 1 until the score starts trending down
  236.  
  237. Hotspot: most signals prefer an even hotspot size (usually 2, sometimes 4);
  238. a few signals prefer an odd hotspot size; testing 2, 3 and 4 will
  239. settle the odd/even question; continue until the score trends down
  240.  
  241. Scaling: test only 55, 60, 65, 70, 75; best is usually in the 60-65 range
  242.  
  243. Damping: start testing at 5; increment by 5 or 10; watch the trend...
  244.  
  245.  
  246. Check your tuning by re-enabling voice synthesis:
  247.  
  248. DSDPlus ? rawAudio.wav -f1 -dr# -dh# -ds# -dd# -dv#
  249.  
  250.  
  251. -or-
  252.  
  253. Just use the third party program - dsdtune.
  254.  
  255.  
  256. When the optimal values for a system + receiver + sound input is determined,
  257. consider creating a batch file to store the settings:
  258.  
  259. Local-PD.bat:
  260.  
  261. DSDPlus -f1 -dr1 -dh3 -ds66 -dd40 -dv20 -O PD.mp3
  262.  
  263. DMR.bat:
  264.  
  265. DSDPlus -fd -d21 -dh2 -ds58 -dd5 -dv20 -O DMR.mp3
  266.  
  267. Then to monitor a specific system, run its batch file.
  268.  
  269. If you prefer, instead of batch files, you can create desktop shortcuts.
  270.  
  271.  
  272. If you scan multiple systems and protocols with a single receiver,
  273. you can run multiple copies of DSDPlus in parallel with each one
  274. protocol-locked and fine tuned as required. Each copy of the program
  275. should write synthesized audio to separate files.
  276.  
  277.  
  278.  
  279. Active Keys
  280. -----------
  281.  
  282. ?
  283.  
  284. '?' generates a list of keyboard commands in the event log window.
  285.  
  286. 1
  287. 2
  288. 3
  289.  
  290. When monitoring conventional DMR systems, you may want to block voice
  291. synthesis for one timeslot. Press 1 or 2 to enable only one timeslot.
  292. Press 3 to enable both timeslots.
  293.  
  294. -
  295. Display of the command line parameters in the console window title
  296. is enabled/disabled by pressing the '-' key.
  297.  
  298. |
  299. The symbol phase display in the console window title
  300. is enabled/disabled by pressing the '|' key.
  301.  
  302. B
  303. The display of background events (like LRRP updates) in the event log window
  304. is enabled/disabled by pressing the 'B' key.
  305.  
  306. E
  307. Use to enable or disable auto-muting of encrypted voice traffic.
  308.  
  309. F
  310. Use when switching from monitoring a trunking system to a conventional system,
  311. for example from DMR Con+ to DMR conventional.
  312.  
  313. N
  314. Press 'N' to force DSD+ to regather and display the current trunking site's
  315. neighbor list in the event log window. Useful for when the neighbor list has
  316. scrolled off the window.
  317.  
  318. P
  319. Press 'P' to toggle the raw signal polarity. You may need to do this when
  320. decoding X2-TDMA or dPMR signals.
  321.  
  322. R
  323. 'R' starts/stops recording of discriminator audio. Use 'R' to make 60
  324. second source recordings of tuning data. Rename the files to identify
  325. what they are.
  326.  
  327. S
  328. If the source audio window has been closed, this key will reopen it.
  329.  
  330. W
  331. When the source audio, event log and channel activity windows have been
  332. placed onscreen where you want them, this key will display their current
  333. locations in the event log window. You can copy these locations to
  334. a batch file or shortcut.
  335.  
  336. Esc
  337. To terminate real time decoding or .wav file processing, press Esc.
  338.  
  339.  
  340.  
  341. Window Title
  342. ------------
  343.  
  344. The window title area shows the command line parameters used (unless -- specified),
  345. symbol tracking/centering, auto-scaling factor, output audio gain,
  346. symbol rate (2400/4800/9600), and protocol.
  347.  
  348. During raw audio recording, "<REC>" is displayed.
  349.  
  350.  
  351.  
  352. Data files
  353. ----------
  354.  
  355. DSDPlus.networks
  356.  
  357. You can populate the DSDPlus.networks file with the network IDs and
  358. network names for NEXEDGE, Connect Plus and Tier III trunking systems.
  359. DSD+ will display the network names when those networks are monitored.
  360. You can add or edit network entries in this file while DSD+ is running.
  361.  
  362. DSDPlus.sites
  363.  
  364. The names for each site on a network can be stored in this file.
  365. Some non-networked DMR systems also broadcast system IDs,
  366. so entries for them can also be added to this file.
  367. DSD+ will use the contents of this file to display the name of the
  368. currently monitored site as well as the names of sites in neighbor lists.
  369. You can add or edit site entries in this file while DSD+ is running.
  370.  
  371. DSDPlus.groups
  372.  
  373. DSD+ will auto-populate this file with every group ID that is seen.
  374. You can edit this file while DSD+ is running and add names/aliases to
  375. group records.
  376.  
  377. DSDPlus.radios
  378.  
  379. DSD+ will auto-populate this file with every radio ID that is seen.
  380. You can edit this file while DSD+ is running and add names/aliases to
  381. radio records. This file replaces the DSDPlus.aliases file; if you
  382. already have a large aliases file, you can use a text editor's
  383. search/replace functionality to convert the contents of your aliases file
  384. to match the format used in the radios file.
  385.  
  386. DSDPlus.frequencies
  387.  
  388. DSD+ uses this file to display frequency information when DSD+ is monitoring
  389. a rest channel or control channel. The frequency records will also be
  390. used to control channel steering for trunked voice following.
  391.  
  392. Note:
  393.  
  394. DSD+ uses two channel numbers for each DMR RF channel:
  395.  
  396. Channel #1 = first RF channel, timeslot 1
  397. Channel #2 = first RF channel, timeslot 2
  398. Channel #3 = second RF channel, timeslot 1
  399. Channel #4 = second RF channel, timeslot 2
  400. Channel #5 = third RF channel, timeslot 1
  401. Channel #6 = third RF channel, timeslot 2
  402. ...
  403.  
  404. For all DMR systems (DMR, Cap+, Con+, TIII), only one channel record has
  405. to be added to the DSDPlus.frequencies file for each RF channel.
  406. You can use the channel number that corresponds to timeslot 1 or 2 and
  407. DSD+ will use the same frequency information for the other timeslot.
  408.  
  409.  
  410. All of the records in these data files have a protocol field;
  411. DSD+ recognizes the following protocol name strings:
  412.  
  413. D-Star
  414. IDAS
  415. NEXEDGE48
  416. NEXEDGE96
  417. dPMR
  418. DMR
  419. Cap+
  420. Con+
  421. TIII
  422. P25
  423. ProVoice
  424.  
  425.  
  426.  
  427. DMR TIII handling
  428. -----------------
  429.  
  430. Tier III control channels broadcast a 14 bit identifier that indicates
  431. the network model (tiny/small/large/huge), network ID, service area
  432. and site number for the current site and for neighboring sites.
  433.  
  434. Many TIII DMR systems are set up using these programming defaults:
  435.  
  436. large network (uses a 4 bit NID field)
  437.  
  438. NID = 13
  439.  
  440. Service area field length: 5 bits
  441.  
  442. Site number field length: 3 bits
  443.  
  444. Physical sites are typically assigned unique area numbers (1, 2, 3, ...)
  445. while their site numbers are all set to 1. So odds are good that any network
  446. you find will have sites with area.site values of 1.1, 2.1, 3.1, etc.
  447.  
  448. When -v3 or higher is used, DSD+ will display a site's 14 bit "SysCode" in binary.
  449.  
  450. Example:
  451.  
  452. CSBK Aloha SysCode=10.1100.00010000
  453.  
  454. The first two bits encode the network model value. Here, 10 = large model.
  455.  
  456. The next set of digits encodes the network ID. A zero value is used for NID 1,
  457. so here, 1100 = 12 = NID 13.
  458.  
  459. The last set of digits encodes the area number and the site number.
  460. Since these two fields do not have a fixed length, DSD+ cannot automatically
  461. decode them. The dividing line between the two fields is selected when the
  462. network is created. This is similar to the variability found in Motorola Type I
  463. fleetmaps.
  464.  
  465. To determine the correct field sizes, gather as many SysCodes as possible
  466. by monitoring system sites and examining their neighbor lists.
  467.  
  468. Example:
  469.  
  470. CSBK Bcast SysCode=10.1100.00010000 Neighbor SysCode=10.1100.00000000, CC=600
  471. CSBK Bcast SysCode=10.1100.00010000 Neighbor SysCode=10.1100.00001000, CC=622
  472.  
  473. From this small sample we have these SysCodes:
  474.  
  475. 10.1100.00000000
  476. 10.1100.00001000
  477. 10.1100.00010000
  478.  
  479. It becomes clear that the SysCodes should be decoded as:
  480.  
  481. 10.1100.00000 000 Model=large NID=13 Area=1 Site=1
  482. 10.1100.00001 000 Model=large NID=13 Area=2 Site=1
  483. 10.1100.00010 000 Model=large NID=13 Area=3 Site=1
  484.  
  485. So here, the area length is 5 and the site length is 3.
  486.  
  487. In the DSDPlus.networks file, an area length value can be appended to TIII
  488. network records, so if the following line is added
  489.  
  490. TIII, 13, "network name goes here", 5
  491.  
  492. DSD+ will use the supplied area length value to properly decode this system's
  493. SysCode fields.
  494.  
  495. These TIII sites can be added to the DSDPlus.sites file as:
  496.  
  497. TIII, 13, 1.1, "site name goes here"
  498. TIII, 13, 2.1, "site name goes here"
  499. TIII, 13, 3.1, "site name goes here"
  500.  
  501. The records in the DSDPlus.frequencies file also reference site numbers;
  502. for TIII sites, use the same area.site format:
  503.  
  504. TIII, 13, 1.1, 600, 462.0, 0.0, 0
  505. TIII, 13, 2.1, 622, 462.3, 0.0, 0
  506.  
  507.  
  508.  
  509. DSD+ Fast Lane
  510. --------------
  511.  
  512. Early access to features is being offered through the DSD+ Fast Lane program.
  513.  
  514. Fast Lane updates are expected to be released every 7 to 30 days.
  515.  
  516. Some Fast Lane updates WILL have issues/bugs. That is the nature of alpha software.
  517.  
  518. These are a few of the features that are being worked on:
  519.  
  520. better tablet support
  521.  
  522. IDAS/NEXEDGE/Cap+/Con+/TIII trunk voice following
  523.  
  524. per-call audio recordings
  525.  
  526. other needed DSD+ upgrades
  527.  
  528. FMP upgrades
  529.  
  530. squelch
  531.  
  532. drift tracking
  533.  
  534. selectable sampling rates
  535.  
  536. adjustable windows sizes
  537.  
  538. TCP client/server mode (eliminates VAC / VB-C)
  539.  
  540. multiple VFOs
  541.  
  542. Airspy support
  543.  
  544. Fully tested public releases will continue, but less frequently,
  545. probably every 4 to 6 months.
  546.  
  547.  
  548. In light of the extra workload the Fast Lane program will create,
  549. the DSD+ team is asking Fast Laners for:
  550.  
  551. US$10 for one year of Fast Lane updates
  552.  
  553. US$25 for unlimited Fast Lane updates
  554.  
  555. Donations above these amounts are welcomed, but it's up to you.
  556. We're not looking to get rich here. Funds will be used for things like
  557. needed hardware upgrades.
  558.  
  559. Funds can be sent our Paypal account (dsdplusfastlane@gmail.com)
  560.  
  561. Please include a comment that specifies the email address that
  562. your Fast Lane updates should be sent to.
  563.  
  564. --
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement