Changeset 7566 in ntrip


Ignore:
Timestamp:
Nov 3, 2015, 1:51:58 PM (7 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/src/bnchelp.html

    r7557 r7566  
    1111
    1212<p><b>Table of <a name="contents">Contents</b><br><br>
    13 <b>1.</b> <a href=#genInstruction><b>General Instructions</b></a><br><br>
     13<b>1.</b> <a href=#genInstruction><b>General Information</b></a><br><br>
    1414&nbsp; &nbsp; &nbsp; 1.1 <a href=#introPurpose>Purpose</a><br>
    1515&nbsp; &nbsp; &nbsp; 1.2 <a href=#introSystem>Supported Systems</a><br>
     
    244244<tr><td>34</td><td>Bandwidth consumption of incoming streams</td><td>2.18.2</td></tr>
    245245<tr><td>35</td><td>Latency of incoming streams</td><td>2.18.3</td></tr>
    246 <tr><td>36</td><td>Time series plot of PPP session</td><td>2.18.4</td></tr>
     246<tr><td>36</td><td>Time series plot of PPP session showing displacements</td><td>2.18.4</td></tr>
    247247<tr><td>37</td><td>Steam input communication links</td><td>2.19</td></tr>
    248248<tr><td>38</td><td>Casters table</td><td>2.19.1.1.2</td></tr>
     
    260260</p>
    261261
    262 <p><h3>1. <a name="genInstruction">General Instructions</h3></p>
     262<p><h3>1. <a name="genInstruction">General Information</h3></p>
    263263<p>
    264264The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding, converting and processing or analyzing real-time GNSS data streams applying the 'Networked Transport of RTCM via Internet Protocol' (Ntrip) standard. It has been developed within the framework of the IAG sub-commission for Europe (EUREF) and the International GNSS Service (IGS). Although meant as a real-time tool, it comes with some Post Processing functionality. You may like to use it for data coming from Ntrip Broadcasters like
     
    304304
    305305<p>
    306 BNC provides context-sensitive online help (<i>What's This</i>) related to specific objects. It furthermore comes with the here presented documentation, available as an integral part of the software and as a PDF file. Responsible for online and offline documentation, example configurations (and till February 2014 the overall BNC policy concept) is Dr. Georg Weber [georg.weber@bkg.bund.de].
     306BNC provides context-sensitive help (<i>What's This</i>) related to specific objects. It furthermore comes with the here presented documentation, available as part of the software and as a PDF file. Responsible for online and offline documentation, example configurations (and till February 2014 the overall BNC policy concept) is Dr. Georg Weber [georg.weber@bkg.bund.de].
    307307</p>
    308308
     
    16081608<br>
    16091609<pre>
    1610 C:2&7 E:1&5 G:1&2 J:1&2 R:1&2 S:1&5
    1611 </pre>
    1612 This default configuration will present;
     1610   C:2&7 E:1&5 G:1&2 J:1&2 R:1&2 S:1&5
     1611</pre>
     1612This default configuration will present:
    16131613<ul>
    16141614<li>BDS plots for L2 and L7,</li>
     
    16921692</p>
    16931693<pre>
    1694    ./bnc --nw --conf rnx.conf --key reqcAction Edit/Concatenate --key reqcObsFile "tlse119b00.12o,tlse119b15.12o,tlse119b30.12o,tlse119b45.12o" --key reqcOutObsFile tlse119b.12o --key reqcRnxVersion 3 --key reqcSampling 30
     1694   ./bnc --nw --conf rnx.conf --key reqcAction Edit/Concatenate --key reqcObsFile
     1695   "tlse119b00.12o,tlse119b15.12o,tlse119b30.12o,tlse119b45.12o" --key
     1696   reqcOutObsFile tlse119b.12o --key reqcRnxVersion 3 --key reqcSampling 30
    16951697</pre>
    16961698<p>
     
    17051707<p>The following Linux command line produces RINEX QC plots (see Estey and Meertens 1999) offline in 'no window' mode and saves them in directory '/home/user'. Introducing a dummy configuration file /dev/null makes sure that no configuration options previously saved on disc are used:</p>
    17061708<pre>
    1707    /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key reqcPlotDir /home/user --nw
     1709   /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile
     1710   CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key
     1711   reqcPlotDir /home/user --nw
    17081712</pre>
    17091713</p>
     
    17111715</p>
    17121716<pre>
    1713    /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key --key startTab 4 --key autoStart 2
     1717   /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile
     1718   CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key
     1719   --key startTab 4 --key autoStart 2
    17141720</pre>
    17151721</p>
     
    34763482</p>
    34773483<p>
     3484<ul>
    34783485<li>Satellite specific parameters </li>
    3479 </p>
    3480 <ul>
     3486</ul>
     3487</p>
     3488<p>
    34813489A set of parameters can be defined for each satellite as follows:
    3482 <p>
    3483 &lt;SatelliteID&gt; &lt;key&gt; &lt;numValues&gt; &lt;value1 value2 ...&gt; &lt;key&gt; &lt;numValues&gt; &lt;value1 value2 ...&gt; ...
     3490<pre>
     3491&lt;SatelliteID&gt; &lt;key&gt; &lt;numValues&gt; &lt;value1 value2 ...&gt; &lt;key&gt; &lt;numValues&gt;
     3492&lt;value1 value2 ...&gt; ...
    34843493&nbsp;
    3485 </p>
    3486 <p>
    3487 The following satellite specific keys and values are currently specified in BNC:
    3488 </p>
     3494</pre>
     3495The following satellite specific keys and values are currently specified in BNC:<br><br>
    34893496<table>
    34903497<tr><td><i>Key&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</i></td><td><i>Values</i></td></tr>
     
    34983505<tr><td>PhaseBias</td><td>Satellite Phase Biases in meters with two characters for frequency and tracking mode per bias as defined in RINEX 3, preceded by total number of biases and followed by Signal Wilde-Lane Integer Indicator as well as Signal Discontinuity Counter</td></tr>
    34993506</table>
    3500 </p>
    3501 </ul>
     3507<ul>
    35023508<li> Non-satellite specific parameters
    3503 <ul>
    3504 The following non-satellite specific keys and values are currently specified in BNC:
    3505 </p>
     3509</ul>
     3510The following non-satellite specific keys and values are currently specified in BNC:<br><br>
    35063511<table>
    35073512<tr><td><i>Key&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</i></td><td><i>Values</i></td></tr>
     
    35093514<tr><td>VTEC</td><td>Stands for Vertical TEC information and is followed by Update Interval and Number of Ionospheric Layers</td></tr>
    35103515</table>
    3511 </p>
     3516<br>
    35123517If the key VTEC is specified, a data set for each layer contains within its first line the Layers Number, followed by Maximum Degree, Maximum Order and Layer Height. After that follow Cosine and Sinus Spherical Harmonic Coefficients, one block each.
    3513 </ul>
     3518</p>
    35143519<p>
    35153520Because each keyword is associated to a certain number of values, an 'old' BNC could be operated with an incoming 'new' RTNET stream containing so far unknown keys - they would just be skipped in BNC.
     
    37473752
    37483753<p><h4>2.15.5 <a name="upsp3">SP3 File - optional</h4></p>
    3749 <p>Specify a path for saving the generated orbit corrections as SP3 orbit files. If the specified directory does not exist, BNC will not create SP3 orbit files. The following is a path example for a Linux system:<br>/home/user/BNC${GPSWD}.sp3<br>Note that '${GPSWD}' produces the GPS Week and Day number in the filename.</p>
     3754<p>Specify a path for saving the generated orbit corrections as SP3 orbit files. If the specified directory does not exist, BNC will not create SP3 orbit files. The following is a path example for a Linux system:
     3755
     3756<pre>
     3757   /home/user/BNC${GPSWD}.sp3
     3758</pre>
     3759
     3760Note that '${GPSWD}' produces the GPS Week and Day number in the filename.</p>
    37503761<p>
    37513762Default is an empty option field, meaning that you don't want BNC to save the uploaded stream contents in daily SP3 files.
     
    38713882<p>
    38723883BNC uploads a stream to the Ntrip Broadcaster by referring to a dedicated mountpoint that has been set by its operator. Specify the mountpoint based on the details you received for your stream from the operator. It is often a four character ID (capital letters) plus an integer number.</p>
    3873 <p>The stream upload may be protected through an upload 'Password'. Enter the password you received from the Ntrip Broadcaster operator along with the mountpoint.</p>
     3884<p>The stream upload follows Ntrip Version 1 and may be protected through an upload 'Password'. Enter the password you received from the Ntrip Broadcaster operator along with the mountpoint.</p>
    38743885</p>
    38753886
     
    39623973
    39633974<p><img src="IMG/screenshot13.png"/></p>
    3964 <p><u>Figure 36:</u> Time series plot of PPP session.</p>
     3975<p><u>Figure 36:</u> Time series plot of PPP session showing displacements.</p>
    39653976
    39663977<p><h4>2.19 <a name="bottom">Bottom Menu Bar</h4></p>
Note: See TracChangeset for help on using the changeset viewer.