Table of Contents
-1. General Instructions
+1. General Information
1.1 Purpose
1.2 Supported Systems
@@ -244,5 +244,5 @@
The 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 @@ -304,5 +304,5 @@
-BNC provides context-sensitive online help (What's This) 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]. +BNC provides context-sensitive help (What's This) 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].
@@ -1608,7 +1608,7 @@-C:2&7 E:1&5 G:1&2 J:1&2 R:1&2 S:1&5 --This default configuration will present; + C:2&7 E:1&5 G:1&2 J:1&2 R:1&2 S:1&5 + +This default configuration will present:
- ./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 + ./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
@@ -1705,5 +1707,7 @@
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:
- /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 + /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@@ -1711,5 +1715,7 @@
- /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 + /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@@ -3476,15 +3482,16 @@
+
A set of parameters can be defined for each satellite as follows: -
-<SatelliteID> <key> <numValues> <value1 value2 ...> <key> <numValues> <value1 value2 ...> ... +
+<SatelliteID> <key> <numValues> <value1 value2 ...> <key> <numValues> +<value1 value2 ...> ... - -+The following satellite specific keys and values are currently specified in BNC:-The following satellite specific keys and values are currently specified in BNC: -
+
| Key | Values |
| PhaseBias | 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 |
| Key | Values |
| VTEC | Stands for Vertical TEC information and is followed by Update Interval and Number of Ionospheric Layers |
Because 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. @@ -3747,5 +3752,11 @@
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:
/home/user/BNC${GPSWD}.sp3
Note that '${GPSWD}' produces the GPS Week and Day number in the filename.
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: + +
+ /home/user/BNC${GPSWD}.sp3
+
+
+Note that '${GPSWD}' produces the GPS Week and Day number in the filename.
Default is an empty option field, meaning that you don't want BNC to save the uploaded stream contents in daily SP3 files. @@ -3871,5 +3882,5 @@
BNC 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.
-The stream upload may be protected through an upload 'Password'. Enter the password you received from the Ntrip Broadcaster operator along with the mountpoint.
+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.
@@ -3962,5 +3973,5 @@
Figure 36: Time series plot of PPP session.
+Figure 36: Time series plot of PPP session showing displacements.