source: ntrip/branches/BNC_2.12/Example_Configs/00_Readme.txt @ 7881

Last change on this file since 7881 was 7881, checked in by stuerze, 3 years ago

minor changes

File size: 14.3 KB
Line 
1Configuration Examples
2
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:
7
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.
10
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>
14
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
19
20Although it's not a must, we suggest that you always create BNC configuration
21files with the filename extension '.bnc'.
22
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:
27
28
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.
32
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.
35
363. Click 'Select the program from a list', and then click 'OK'.
37
384. The 'Open With' dialog box is displayed. Click 'Browse', locate and then
39   click the BNC program, and then click 'Open'.
40
415. Click to select the 'Always use the selected program to open this kind
42   of file' check box.
43
446. Click 'OK'.
45
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
52http://register.rtcm-ntrip.org.
53
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.
58
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.
62
63Some BNC options require antenna phase center variations as made available
64from IGS through so-called ANTEX files at ftp://igs.org/pub/station/general.
65An example ANTEX file 'igs08.atx' is part of the BNC package for convenience.
66
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.
70
71(A) Working with Configuration Files
72
73You should be able to run all configuration file examples without changing
74contained options. However, configurations 'Upload.bnc' and 'UploadPPP.bnc' are
75exceptions because they require an input stream from a connected network engine.
76
771. Configuration File 'RinexObs.bnc'
78Purpose: Convert RTCM streams to RINEX Observation files. The configuration
79pulls streams from Ntrip Broadcasters using Ntrip Version 1 to generate 15min
801Hz RINEX Version 3 Observation files. See
81http://igs.bkg.bund.de/ntrip/observations for observation stream resources.
82
832. Configuration File 'RinexEph.bnc'
84Purpose: Convert a RTCM stream with navigation messages to RINEX Navigation
85files. The configuration pulls a RTCM Version 3 stream with Broadcast Ephemeris
86coming from the real-time EUREF and IGS networks and saves hourly RINEX Version
873 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further
88real-time Broadcast Ephemeris resources.
89
903. Configuration File 'BrdcCorr.bnc'
91Purpose: Save Broadcast Corrections from RTCM SSR messages in hourly plain
92ASCII files. See http://igs.bkg.bund.de/ntrip/orbits for various real-time IGS
93or EUREF orbit/clock correction products.
94
954. Configuration File 'RinexConcat.bnc'
96Purpose: Concatenate several RINEX Version 3 files to produce one compiled file
97and edit the marker name in the file header. The sampling interval is set to 30
98seconds. See section 'RINEX Editing & QC' in the documentation for examples on
99how to call BNC from command line in 'no window' mode for RINEX file editing,
100concatenation and quality check.
101
1025. Configuration File 'RinexQC.bnc'
103Purpose: Check the quality of a RINEX Version 3 file by means of a multipath
104analysis. Results are saved on disk in terms of a plot in PNG format. See
105section 'RINEX Editing & QC' in the documentation for examples on how to call
106BNC from command line in 'no window' mode for RINEX file editing, concatenation
107and quality check.
108
1096. Configuration File 'RTK.bnc'
110Purpose: Feed a serial connected receiver with observations from a nearby
111reference station for conventional RTK. The stream is scanned for RTCM
112messages. Message type numbers and latencies of incoming observations are
113reported in BNC's logfile.
114
1157. Configuration File 'FeedEngine.bnc'
116Purpose: Feed a real-time GNSS engine with observations from remote reference
117stations. The configuration pulls a single stream from an Ntrip Broadcaster.
118You could also pull several streams from different casters. Incoming
119observations are decoded, synchronized, output through a local IP port and also
120saved into a file. Failure and recovery thresholds are specified to inform
121about outages.
122
1238. Configuration File 'PPP.bnc'
124Purpose: Precise Point Positioning from observations of a rover receiver. The
125configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream
126and a stream with Broadcast Corrections. Positions are saved in the logfile.
127
1289. Configuration File 'PPPNet.bnc'
129Purpose: Precise Point Positioning for several rovers or receivers from an
130entire network of reference stations in one BNC job. The possible maximum
131number of PPP solutions per job depends on the processing power of the hosting
132computer. This example configuration reads two RTCM Version 3 observation
133streams, a Broadcast Ephemeris stream and a stream with Broadcast Corrections.
134PPP Results for the two stations are saved in PPP logfiles.
135
13610. Configuration File 'PPPQuickStart.bnc'
137Purpose: Precise Point Positioning in Quick-Start mode from observations of a
138static receiver with precisely known position. The configuration reads RTCM
139Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream.
140Positions are saved in NMEA format on disc. They are also output through IP
141port for real-time visualization with tools like RTKPLOT. Positions are saved
142in the logfile.
143
14411. Configuration File 'PPPPostProc.bnc'
145Purpose: Precise Point Positioning in post processing mode. BNC reads RINEX
146Version 3 Observation and 3 Navigation files and a Broadcast Correction file.
147PPP processing options are set to support the Quick-Start mode. The output is
148saved in a specific post processing logfile and contains coordinates derived
149over time following the implemented PPP filter algorithm.
150
15112. Configuration File 'PPPGoogleMaps.bnc'
152Purpose: Track BNC's point positioning solutions using Google Maps or
153OpenStreetMap as background. BNC reads a RINEX Observation file and a RINEX
154Navigation file to carry out a 'Standard Point Positioning' solution in post
155processing mode. Although this is not a real-time application it requires the
156BNC host to be connected to the Internet. Specify a computation speed, then hit
157button 'Open Map' to open the track map, then hit 'Start' to visualize receiver
158positions on top of GM/OSM maps.
159
16013. Configuration File 'SPPQuickStartGal.bnc'
161Purpose: Single Point Positioning in Quick-Start mode from observations of a
162static receiver with quite precisely known position. The configuration uses
163GPS, GLONASS and Galileo observations and a Broadcast Ephemeris stream.
164
16514. Configuration File 'SaveSp3.bnc'
166Purpose: Produces SP3 files from a Broadcast Ephemeris stream and a Broadcast
167Correction stream. The Broadcast Correction stream is formally introduced in
168BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX
169file because SP3 file content should be referred to CoM.
170
17115. Configuration File 'Sp3ETRF2000PPP.bnc'
172Purpose: Produce SP3 files from a Broadcast Ephemeris stream and a stream
173carrying ETRF2000 Broadcast Corrections. The Broadcast Correction stream is
174formally introduced in BNC's 'Combine Corrections' table. The configuration
175leads to a SP3 file containing orbits also referred to ETRF2000. Pulling in
176addition observations from a reference station at precisely known ETRF2000
177position allows comparing an 'INTERNAL' PPP solution with a known ETRF2000
178reference coordinate.
179
18016. Configuration File 'Upload.bnc'
181Purpose: Upload orbits and clocks from a real-time GNSS engine to an Ntrip
182Broadcaster. For that the configuration reads precise orbits and clocks in
183RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts
184the orbits and clocks into Broadcast Corrections and encodes them to RTCM
185Version 3 SSR messages to finally upload them to an Ntrip Broadcaster. The
186Broadcast Correction stream is referred to satellite Antenna Phase Center (APC)
187and reference system IGS08. Orbits are saved on disk in SP3 format and clocks
188are saved in Clock RINEX format.
189
19017. Configuration File 'Combi.bnc'
191Purpose: Pull several streams carrying Broadcast Corrections and a Broadcast
192Ephemeris from an Ntrip Broadcaster to produce a combined Broadcast Correction
193stream. BNC encodes the combination product in RTCM Version 3 SSR messages and
194uploads that to an Ntrip Broadcaster. The Broadcast Correction stream is
195referred to satellite Antenna Phase Center (APC) and not to satellite Center of
196Mass (CoM). Its reference system is IGS08. Orbits are saved in SP3 format
197(referred to CoM) and clocks in Clock RINEX format.
198
19918. Configuration File 'CombiPPP.bnc'
200Purpose: This configuration equals the 'Combi.bnc' configuration. However, the
201combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP
202solutions based on observations from a static reference station with known
203precise coordinates. This allows a continuous quality check of the combination
204product through observing coordinate displacements.
205
20619. Configuration File 'UploadEph.bnc'
207Purpose: Pull a number of streams from reference stations to get hold of
208contained Broadcast Ephemeris messages. They are encoded to RTCM Version 3
209format and uploaded for the purpose of providing a Broadcast Ephemeris stream
210with an update rate of 5 seconds.
211
21220. Configuration File 'CompareSp3.bnc'
213Purpose: Compare two SP3 files to calculate RMS values for orbit and clock
214differences. GPS satellite G05 and GLONASS satellite R18 are excluded from this
215comparison. Comparison results are saved in a logfile.
216
21721. Configuration File 'Empty.bnc'
218Purpose: Provide an empty example configuration file for BNC which only
219contains the default settings.
220
221(B) Working with Command Line configuration options
222
223The following configuration examples make use of BNC's 'Command Line Interface'
224(CLI). Configuration options are exclusively specified via command line. No
225configuration file is used. Examples are provided as shell scripts for a Linux
226system. They call BNC in 'no window' batch mode (command line option -nw).
227The scripts expect 'Example_Configs' to be the current working directory.
228
22922. Shell Script 'RinexQC.sh'
230Purpose: Equals configuration file example 'RinexQC.bnc', checks the quality of
231a RINEX Version 3 file by means of a multipath analysis. Virtual X-Server
232'Xvfb' is operated while producing plot files in PNG format. BNC is offline.
233All results are saved on disk.
234
23523. Shell Script 'RinexConcat.sh'
236Purpose: Equals configuration file example 'RinexConcat.bnc', concatenates
237several RINEX Version 3 files to produce one compiled file and edit the marker
238name in the file header. The sampling interval is set to 30 seconds. BNC is
239offline.
240
24124. Shell Script 'RinexEph.sh'
242Purpose: Equals configuration file example 'RinexEph.bnc', converts a RTCM
243stream with navigation messages to RINEX Navigation files. The configuration
244pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the
245real-time EUREF and IGS networks and saves hourly RINEX Version 3 Navigation
246files. BNC runs online until it's terminated after 10 seconds.  See
247http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast
248Ephemeris resources.
249
25025. Shell Script 'ScanLate.sh'
251Purpose: Scan an observation stream for contained RTCM message types, print
252observation latencies. The output is saved in a logfile. Latencies are
253reported every 10 seconds. BNC runs online until it's terminated after 20
254seconds.
255
25626. Shell Script 'RinexObs.sh'
257Purpose: Equals configuration file example 'RinexObs.bnc', converts RTCM
258streams to RINEX Observation files. The configuration pulls streams from two
259Ntrip Broadcasters using Ntrip Version 1 to generate 15min 1Hz RINEX Version 3
260Observation files. See http://igs.bkg.bund.de/ntrip/observations for
261observation stream resources. BNC runs online until it's terminated after 30
262seconds.
263
264(C) Command Line configuration options overwriting Configuration File options
265
266For specific applications you may like to use your own set of standard
267configuration options from a configuration file and update some of its content
268via command line. When using a configuration file and command line configuration
269options together in one BNC call, the command line configuration options will
270always overrule options contained in the configuration file.
271
27227. Shell Script 'CompareSp3.sh'
273Purpose: Equals configuration file example 'CompareSp3.bnc', compares two SP3
274files to calculate RMS values for orbit and clock differences. However, instead
275of excluding GPS satellite G05 and GLONASS satellite R18 from the comparison as
276specified in 'CompareSp3.bnc', GPS satellite G06 and all GLONASS satellites are
277excluded via command line option. BNC runs offline. Comparison results are saved
278in a logfile.
279
280Georg Weber, BKG
281Frankfurt, April 2016
282igs-ip@bkg.bund.de
283
Note: See TracBrowser for help on using the repository browser.