source: ntrip/trunk/BNC/Example_Configs/00_Readme.txt@ 7744

Last change on this file since 7744 was 7744, checked in by weber, 7 years ago

Documentation completed

File size: 13.0 KB
1Configuration Examples
3BNC comes with a number of configuration examples which can be used on all
4operating systems. Copy the complete directory 'Example_Configs' which comes
5with the software including sub-directories 'Input' and 'Output' to your disc.
6There are several ways to start BNC using one of the example configurations:
8* On graphical systems (except for Mac systems) you may use the computer mouse
9 to 'drag' a configuration file icon and 'drop' it on top of BNC's program icon.
11* You could also start BNC using a command line for naming a specific
12 configuration file (suggested e.g. for Mac systems):
13 bnc --conf <configFileName>
15* On non-graphical systems or when running BNC in batch mode in the background
16 you may start the program using a command line with a configuration file
17 option in 'no window' mode (example for Windows systems):
18 bnc.exe --conf <configFileName> --nw
20Although it's not a must, we suggest that you always create BNC configuration
21files with the filename extension '.bnc'.
23We furthermore suggest for convenience reasons that you configure your system
24to automatically start BNC when you double-click a file with the filename
25extension '.bnc'. The following describes what to do on Windows systems to
26associate the BNC program to such configuration files:
291. Right-click a file that has the extension '.bnc' and then click 'Open'. If
30 the 'Open' command is not available, click 'Open With' or double-click the
31 file.
332. Windows displays a dialog box that says that the system cannot open this
34 file. The dialog box offers several options for selecting a program.
363. Click 'Select the program from a list', and then click 'OK'.
384. The 'Open With' dialog box is displayed. Click 'Browse', locate and then
39 click the BNC program, and then click 'Open'.
415. Click to select the 'Always use the selected program to open this kind
42 of file' check box.
446. Click 'OK'.
46Some of the presented example configuration files contain a user ID 'Example'
47with a password 'Configs' for accessing a few GNSS streams from public Ntrip
48Broadcasters. This generic account is arranged for convenience reasons only.
49Please be so kind as to replace the generic account details as well as the
50place holders 'User' and 'Pass' by the personal user ID and password you
51receive following an online registration through
54Note that the account for an Ntrip Broadcaster is usually limited to
55pulling a specified maximum number of streams at the same time. As running
56some of the example configurations requires pulling several streams, it
57is suggested to make sure that you don't exceed your account's limits.
59Make also sure that sub-directories 'Input' and 'Output' which are part of
60the example configurations exist on your system or adjust the affected
61example configuration options according to your needs.
63Some BNC options require antenna phase center variations as made available
64from IGS through so-called ANTEX files at
65An example ANTEX file 'igs08.atx' is part of the BNC package for convenience.
67The example configurations assume that no proxy protects your BNC host.
68Should a proxy be operated in front of BNC then you need to introduce its
69name or IP and port number in the 'Network' panel.
71You should be able to run all configuration file examples without changing
72contained options. However, configurations 'Upload.bnc' and 'UploadPPP.bnc' are
73exceptions because they require an input stream from a connected network engine.
751. Configuration File 'RinexObs.bnc'
76Purpose: Convert RTCM streams to RINEX Observation files. The configuration
77pulls streams from Ntrip Broadcasters using Ntrip Version 1 to generate 15min
781Hz RINEX Version 3 Observation files. See
79 for observation stream resources.
812. Configuration File 'RinexEph.bnc'
82Purpose: Convert a RTCM stream with navigation messages to RINEX Navigation
83files. The configuration pulls a RTCM Version 3 stream with Broadcast Ephemeris
84coming from the real-time EUREF and IGS networks and saves hourly RINEX Version
853 Navigation files. See for further
86real-time Broadcast Ephemeris resources.
883. Configuration File 'BrdcCorr.bnc'
89Purpose: Save Broadcast Corrections from RTCM SSR messages in hourly plain
90ASCII files. See for various real-time IGS
91or EUREF orbit/clock correction products.
934. Configuration File 'RinexConcat.bnc'
94Purpose: Concatenate several RINEX Version 3 files to produce one compiled file
95and edit the marker name in the file header. The sampling interval is set to 30
96seconds. See section 'RINEX Editing & QC' in the documentation for examples on
97how to call BNC from command line in 'no window' mode for RINEX file editing,
98concatenation and quality check.
1005. Configuration File 'RinexQC.bnc'
101Purpose: Check the quality of a RINEX Version 3 file by means of a multipath
102analysis. Results are saved on disk in terms of a plot in PNG format. See
103section 'RINEX Editing & QC' in the documentation for examples on how to call
104BNC from command line in 'no window' mode for RINEX file editing, concatenation
105and quality check.
1076. Configuration File 'RTK.bnc'
108Purpose: Feed a serial connected receiver with observations from a nearby
109reference station for conventional RTK. The stream is scanned for RTCM
110messages. Message type numbers and latencies of incoming observations are
111reported in BNC's logfile.
1137. Configuration File 'FeedEngine.bnc'
114Purpose: Feed a real-time GNSS engine with observations from remote reference
115stations. The configuration pulls a single stream from an Ntrip Broadcaster.
116You could also pull several streams from different casters. Incoming
117observations are decoded, synchronized, output through a local IP port and also
118saved into a file. Failure and recovery thresholds are specified to inform
119about outages.
1218. Configuration File 'PPP.bnc'
122Purpose: Precise Point Positioning from observations of a rover receiver. The
123configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream
124and a stream with Broadcast Corrections. Positions are saved in the logfile.
1269. Configuration File 'PPPNet.bnc'
127Purpose: Precise Point Positioning for several rovers or receivers from an
128entire network of reference stations in one BNC job. The possible maximum
129number of PPP solutions per job depends on the processing power of the hosting
130computer. This example configuration reads two RTCM Version 3 observation
131streams, a Broadcast Ephemeris stream and a stream with Broadcast Corrections.
132PPP Results for the two stations are saved in PPP logfiles.
13410. Configuration File 'PPPQuickStart.bnc'
135Purpose: Precise Point Positioning in Quick-Start mode from observations of a
136static receiver with precisely known position. The configuration reads RTCM
137Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream.
138Positions are saved in NMEA format on disc. They are also output through IP
139port for real-time visualization with tools like RTKPLOT. Positions are saved
140in the logfile.
14211. Configuration File 'PPPPostProc.bnc'
143Purpose: Precise Point Positioning in post processing mode. BNC reads RINEX
144Version 3 Observation and 3 Navigation files and a Broadcast Correction file.
145PPP processing options are set to support the Quick-Start mode. The output is
146saved in a specific post processing logfile and contains coordinates derived
147over time following the implemented PPP filter algorithm.
14912. Configuration File 'PPPGoogleMaps.bnc'
150Purpose: Track BNC's point positioning solutions using Google Maps or
151OpenStreetMap as background. BNC reads a RINEX Observation file and a RINEX
152Navigation file to carry out a 'Standard Point Positioning' solution in post
153processing mode. Although this is not a real-time application it requires the
154BNC host to be connected to the Internet. Specify a computation speed, then hit
155button 'Open Map' to open the track map, then hit 'Start' to visualize receiver
156positions on top of GM/OSM maps.
15813. Configuration File 'SPPQuickStartGal.bnc'
159Purpose: Single Point Positioning in Quick-Start mode from observations of a
160static receiver with quite precisely known position. The configuration uses
161GPS, GLONASS and Galileo observations and a Broadcast Ephemeris stream.
16314. Configuration File 'SaveSp3.bnc'
164Purpose: Produces SP3 files from a Broadcast Ephemeris stream and a Broadcast
165Correction stream. The Broadcast Correction stream is formally introduced in
166BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX
167file because SP3 file content should be referred to CoM.
16915. Configuration File 'Sp3ETRF2000PPP.bnc'
170Purpose: Produce SP3 files from a Broadcast Ephemeris stream and a stream
171carrying ETRF2000 Broadcast Corrections. The Broadcast Correction stream is
172formally introduced in BNC's 'Combine Corrections' table. The configuration
173leads to a SP3 file containing orbits also referred to ETRF2000. Pulling in
174addition observations from a reference station at precisely known ETRF2000
175position allows comparing an 'INTERNAL' PPP solution with a known ETRF2000
176reference coordinate.
17816. Configuration File 'Upload.bnc'
179Purpose: Upload orbits and clocks from a real-time GNSS engine to an Ntrip
180Broadcaster. For that the configuration reads precise orbits and clocks in
181RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts
182the orbits and clocks into Broadcast Corrections and encodes them to RTCM
183Version 3 SSR messages to finally upload them to an Ntrip Broadcaster. The
184Broadcast Correction stream is referred to satellite Antenna Phase Center (APC)
185and reference system IGS08. Orbits are saved on disk in SP3 format and clocks
186are saved in Clock RINEX format.
18817. Configuration File 'Combi.bnc'
189Purpose: Pull several streams carrying Broadcast Corrections and a Broadcast
190Ephemeris from an Ntrip Broadcaster to produce a combined Broadcast Correction
191stream. BNC encodes the combination product in RTCM Version 3 SSR messages and
192uploads that to an Ntrip Broadcaster. The Broadcast Correction stream is
193referred to satellite Antenna Phase Center (APC) and not to satellite Center of
194Mass (CoM). Its reference system is IGS08. Orbits are saved in SP3 format
195(referred to CoM) and clocks in Clock RINEX format.
19718. Configuration File 'CombiPPP.bnc'
198Purpose: This configuration equals the 'Combi.bnc' configuration. However, the
199combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP
200solutions based on observations from a static reference station with known
201precise coordinates. This allows a continuous quality check of the combination
202product through observing coordinate displacements.
20419. Configuration File 'UploadEph.bnc'
205Purpose: Pull a number of streams from reference stations to get hold of
206contained Broadcast Ephemeris messages. They are encoded to RTCM Version 3
207format and uploaded for the purpose of providing a Broadcast Ephemeris stream
208with an update rate of 5 seconds.
21020. Configuration File 'CompareSp3.bnc'
211Purpose: Compare two SP3 files to calculate RMS values for orbit and clock
212differences. GPS satellite G05 and GLONASS satellite R18 are excluded from this
213comparison. Comparison results are saved in a logfile.
21521. Configuration File 'Empty.bnc'
216Purpose: Provide an empty example configuration file for BNC which only
217contains the default settings.
219The following configuration examples make use of BNC's 'Command Line Interface'
220(CLI). Configuration options are exclusively specified via command line. No
221configuration file is used. Examples are provided as shell scripts for a Linux
222system. They call BNC in 'no window' batch mode (command line option -nw).
223The scripts expect 'Example_Configs' to be the current working directory.
22522. Shell Script ''
226Purpose: Equals configuration file example 'RinexQC.bnc', checks the quality of
227a RINEX Version 3 file by means of a multipath analysis. Virtual X-Server
228'Xvfb' is operated while producing plot files in PNG format. BNC is offline.
229All results are saved on disk.
23123. Shell Script ''
232Purpose: Equals configuration file example 'RinexConcat.bnc', concatenates
233several RINEX Version 3 files to produce one compiled file and edit the marker
234name in the file header. The sampling interval is set to 30 seconds. BNC is
23724. Shell Script ''
238Purpose: Equals configuration file example 'RinexEph.bnc', converts a RTCM
239stream with navigation messages to RINEX Navigation files. The configuration
240pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the
241real-time EUREF and IGS networks and saves hourly RINEX Version 3 Navigation
242files. BNC runs online till it's terminated after 10 seconds. See
243 for further real-time Broadcast
244Ephemeris resources.
24625. Shell Script ''
247Purpose: Scan an observation stream for contained RTCM message types, print
248observation latencies. The output is saved in a logfile. Latencies are
249reported every 10 seconds. BNC runs online till it's terminated after 20
252Georg Weber, BKG
253Frankfurt, January 2016
Note: See TracBrowser for help on using the repository browser.