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

Last change on this file since 7089 was 5594, checked in by weber, 11 years ago

Documentation completed

File size: 11.4 KB
Line 
1Configuration Examples
2
3BNC comes with a number of configuration examples which can be used on all
4operating systems. You may use a statically linked BNC executable to run the
5configuration examples. Configuration 'PPPGoogleMaps.bnc' is an exception
6from this because it requires a shared library BNC build.
7
8If not already done then copy the complete directory 'Example_Configs' to you
9disc. It contains sub-directories 'Input' and 'Output'. There are several ways to
10start BNC using one of the example configurations:
11
12* On graphical systems (except for Mac systems) you may use the computer mouse to
13 'drag' a configuration file icon and 'drop' it on top of BNC's program icon.
14* On non-graphical systems you may start BNC using a command line with the
15 following option for a configuration file (example for Windows systems):
16 bnc.exe --conf <configFileName> --nw
17
18Although it's not a must, we suggest that you always create BNC configuration
19files with the file name extension '.bnc'.
20
21We furthermore suggest for convenience reasons that you configure your system
22to automatically start BNC when you double-click a file with the file name
23extension '.bnc'. The following describes what to do on Windows systems to
24associate the BNC program to such configuration files:
25
261. Right-click a file that has the extension '.bnc' and then click 'Open'. If the
27 'Open' command is not available, click 'Open With' or double-click the file.
282. Windows displays a dialog box that says that the system cannot open this file.
29 The dialog box offers several options for selecting a program.
303. Click 'Select the program from a list', and then click 'OK'.
314. The 'Open With' dialog box is displayed. Click 'Browse', locate and then click
32 the BNC program, and then click 'Open'.
335. Click to select the 'Always use the selected program to open this kind of file'
34 check box.
356. Click 'OK'.
36
37Some of the presented example configuration files contain a user ID 'Example'
38with a password 'Configs' for accessing a few GNSS streams from public Ntrip
39Broadcasters. This generic account is arranged for convenience reasons only.
40Please be so kind as to replace the generic account details as well as the
41place holders 'User' and 'Pass' by the personal user ID and password you
42receive following an online registration through
43http://register.rtcm-ntrip.org.
44
45Note that the account for an Ntrip Broadcaster is usually limited to pulling a
46specified maximum number of streams at the same time. As running some of the
47example configurations requires pulling several streams, it is suggested to
48make sure that you don't exceed your account's limits.
49
50Make also sure that sub-directories 'Input' and 'Output' which are part of the
51example configurations exist on your system or adjust the affected example
52configuration options according to your needs.
53
54Some BNC options require antenna phase center variations as made available from
55IGS through so-called ANTEX files at ftp://igs.org/pub/station/general. An
56example ANTEX file 'igs08.atx' is part of the BNC package for convenience.
57
58The example configurations assume that no proxy protects your BNC host. Should
59a proxy be operated in front of BNC then you need to introduce its IP and port
60in the 'Network' tab of the example configurations.
61
62You should be able to run all configuration examples without changing their
63options. However, configurations 'Upload.bnc' and 'UploadPPP.bnc' are
64exceptions because they require an input stream from a connected GNSS network
65engine.
66
671. File 'RinexObs.bnc'
68The purpose of this configuration is showing how to convert RTCM streams to
69RINEX Observation files. The configuration pulls streams from Ntrip
70Broadcasters using Ntrip version 1 to generate 15min 1Hz RINEX Version 3
71Observation files. See http://igs.bkg.bund.de/ntrip/observations for observation
72stream resources.
73
742. File 'RinexEph.bnc'
75The purpose of this configuration is showing how to convert a RTCM stream
76carrying navigation messages to a RINEX Navigation files. The configuration
77pulls an RTCM Version 3 stream with Broadcast Ephemeris coming from the
78real-time EUREF and IGS networks. It saves hourly RINEX Version 3 Navigation
79files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time
80Broadcast Ephemeris resources.
81
823. File 'BrdcCorr.bnc'
83The purpose of this configuration is to save Broadcast Corrections from RTCM
84SSR messages in a plain ASCII format as hourly files. See
85http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF
86orbit/clock products.
87
884. File 'RinexConcat.bnc'
89The purpose of this configuration is to concatenate RINEX Version 3 files to
90produce a concatenated file and edit the marker name in the file header. The
91sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the
92documentation for examples on how to call BNC from command line in 'no window'
93mode for RINEX file editing, concatenation and quality checks.
94
955. File 'RinexQC.bnc'
96The purpose of this configuration is to check the quality of a RINEX Version 3
97file through a multipath analysis. The results is saved in disk in terms of a
98plot in PNG format. See section 'RINEX Editing & QC' in the documentation for
99examples on how to call BNC from command line in 'no window' mode for RINEX
100file editing, concatenation and quality checks.
101
1026. File 'RTK.bnc'
103The purpose of this configuration is to feed a serial connected receiver with
104observations from a reference station for conventional RTK. The stream is
105scanned for RTCM messages. Message type numbers and latencies of incoming
106observation are reported in BNC's logfile.
107
1087. File 'FeedEngine.bnc'
109The purpose of this configuration is to feed a real-time GNSS engine with
110observations from a remote reference stations. The configuration pulls a single
111stream from an NTRIP Broadcasters. It would of course be possible to pull
112several streams from different casters. Incoming observations are decoded,
113synchronized and output through a local IP port and saved into a file. Failure
114and recovery thresholds are specified to inform about outages.
115
1168. File 'PPP.bnc'
117The purpose of this configuration is Precise Point Positioning from
118observations of a rover receiver. The configuration reads RTCM Version 3
119observations, a Broadcast Ephemeris stream and a stream with Broadcast
120Corrections. Positions are saved in the logfile.
121
1229. File 'PPPQuickStart.bnc'
123The purpose of this configuration is Precise Point Positioning in Quick-Start
124mode from observations of a static receiver with precisely known position. The
125configuration reads RTCM Version 3 observations, Broadcast Corrections and a
126Broadcast Ephemeris stream. Positions are saved in NMEA format on disc.
127Positions are also output through IP port for real-time visualization with
128tools like RTKPLOT. Positions are also saved in the logfile.
129
13010. File 'PPPPostProc.bnc'
131The purpose of this configuration is Precise Point Positioning in Post
132Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation
133files and a Broadcast Corrections file. PPP processing options are set to
134support the Quick-Start mode. The output is saved in a specific Post Processing
135logfile and contains the coordinates derived over time following the
136implemented PPP filter algorithm.
137
13811. File 'PPPGoogleMaps.bnc'
139The purpose of this configuration is to track BNC's point positioning
140solution using Google Maps or Open StreetMap as background. BNC reads a
141RINEX Observation file and a RINEX Navigation file to carry out a
142'Standard Point Positioning' solution in post-processing mode. Although
143this is not a real-time application it requires the BNC host to be connected
144to the Internet. Specify a computation speed, then hit button 'Open Map'
145to open the track map, then hit 'Start' to visualize receiver positions
146on top of GM/OSM maps.
147
14812. File 'SPPQuickStartGal.bnc'
149The purpose of this configuration is Single Point Positioning in Quick-Start
150mode from observations of a static receiver with precisely known position. The
151configuration uses GPS, GLONASS and Galileo observations and a Broadcast
152Ephemeris stream.
153
15413. File 'Sp3.bnc'
155The purpose of this configuration is to produce SP3 files from a Broadcast
156Ephemeris stream and a Broadcast Corrections stream. The Broadcast Corrections
157stream is formally introduced in BNC's 'Combine Corrections' table. Note that
158producing SP3 requires an ANTEX file because SP3 file contents should be
159referred to CoM.
160
16114. File 'Sp3ETRF2000PPP.bnc'
162The purpose of this configuration is to produce SP3 files from a Broadcast
163Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The
164Broadcast Corrections stream is formally introduced in BNC's 'Combine
165Corrections' table. This leads to an SP3 file containing orbits referred also
166to ETRF2000. Pulling in addition observations from a reference station at
167precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution
168with ETRF2000 reference coordinates.
169
17015. File 'Upload.bnc'
171The purpose of this configuration is to upload orbits and clocks from a
172real-time GNSS engine to an NTRIP Broadcaster. For that the configuration reads
173precise orbits and clocks in RTNET format. It also reads a stream carrying
174Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast
175Corrections and encodes them in RTCM Version 3 SSR messages to upload them to
176an NTRIP Broadcaster. The Broadcast Corrections stream is referred to satellite
177Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format
178and clocks in Clock RINEX format.
179
18016. File 'UploadPPP.bnc'
181This configuration equals the 'Upload.bnc' configuration. However, the
182Broadcast Corrections are in addition used for an 'INTERNAL' PPP solution based
183on observations from a static reference station with known precise coordinates.
184This allows a continuous quality check of the Broadcast Corrections through
185observing coordinate displacements.
186
18717. File 'Combi.bnc'
188The purpose of this configuration is to pull several streams carrying Broadcast
189Corrections and a Broadcast Ephemeris stream from an NTRIP Broadcaster to
190produce a combined Broadcast Corrections stream. BNC encodes the combination
191product in RTCM Version 3 SSR messages and uploads that to an Ntrip
192Broadcaster. The Broadcast Corrections stream is not referred to satellite
193Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format
194and clocks in Clock RINEX format.
195
19618. File 'CombiPPP.bnc'
197This configuration equals the 'Combi.bnc' configuration. However, the combined
198Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions
199based on observations from a static reference station with known precise
200coordinates. This allows a continuous quality check of the combination product
201through observing coordinate displacements.
202
20319. File 'UploadEph.bnc'
204The purpose of this configuration is to pull a number of streams from reference
205stations to get hold of contained Broadcast Ephemeris messages. These are
206encoded then in a RTCM Version 3 stream which only provides Broadcast Ephemeris
207with an update rate of 5 seconds.
208
20920. File 'Empty.bnc'
210The purpose of this example is to provide an empty configuration file for BNC
211which only contains the default settings.
212
213Georg Weber, BKG
214Frankfurt, November 2013
215igs-ip@bkg.bund.de
Note: See TracBrowser for help on using the repository browser.