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

Last change on this file since 7262 was 7137, checked in by weber, 9 years ago

Documentation completed

File size: 12.5 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. The configuration pulls two streams from Ntrip Broadcasters using
70Ntrip version 2 to generate 15min 1Hz RINEX Version 3 observation files.
71Note that network option 'Ignore SSL authorization errors' is set in order
72to allow pulling RINEX skeleton files via HTTPS when necessary. See
73http://igs.bkg.bund.de/ntrip/observations for observation stream resources.
74
752. File 'RinexEph.bnc'
76The purpose of this configuration is showing how to convert a RTCM stream
77carrying navigation messages to RINEX Navigation files. The configuration
78pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the
79real-time EUREF, IGS and M-GEX networks. It saves hourly RINEX Version 3
80Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further
81real-time Broadcast Ephemeris resources.
82
833. File 'BrdcCorr.bnc'
84The purpose of this configuration is to save Broadcast Corrections from RTCM
85SSR messages in a plain ASCII format as hourly files. Depending on the
86Broadcast Corrections stream the file may contain orbit and clock
87corrections as well as code and phase biases. Information on correction
88streams from IGS and EUREF resources is available from
89http://igs.bkg.bund.de/ntrip/orbits.
90
914. File 'RinexConcat.bnc'
92The purpose of this configuration is to concatenate RINEX Version 3 files to
93produce a concatenated file and edit the marker name in the file header. The
94sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the
95documentation for examples on how to call BNC from command line in 'no window'
96mode for RINEX file editing, concatenation and quality checks.
97
985. File 'RinexQC.bnc'
99The purpose of this configuration is to check the quality of a RINEX Version 3
100file through a multipath analysis. The results is saved in disk in terms of a
101plot in PNG format. See section 'RINEX Editing & QC' in the documentation for
102examples on how to call BNC from command line in 'no window' mode for RINEX
103file editing, concatenation and quality checks.
104
1056. File 'RTK.bnc'
106The purpose of this configuration is to feed a serial connected receiver with
107observations from a reference station for conventional RTK. The stream is
108scanned for RTCM messages. Message type numbers and latencies of incoming
109observation are reported in BNC's logfile.
110
1117. File 'FeedEngine.bnc'
112The purpose of this configuration is to feed a real-time GNSS engine with
113observations from a remote reference stations. The configuration pulls a single
114stream from an NTRIP Broadcasters. It would of course be possible to pull
115several streams from different casters. Incoming observations are decoded,
116synchronized and output through a local IP port and saved into a file. Failure
117and recovery thresholds are specified to inform about outages.
118
1198. File 'PPP.bnc'
120The purpose of this configuration is Precise Point Positioning from
121observations of a rover receiver. The configuration reads RTCM Version 3
122observations, a Broadcast Ephemeris stream and a stream with Broadcast
123Corrections. Positions are saved in the logfile.
124
1259. File 'PPPNet.bnc'
126The purpose of this configuration is to demonstrate siumultaneous Precise
127Point Positioning for several rovers or several receivers from a network of
128reference stations in one BNC job. The possible maximum number of PPP solutions
129per job depends on the processing power of the hosting computer. This example
130configuration reads two RTCM Version 3 observation streams, a Broadcast
131Ephemeris stream and a stream with Broadcast Corrections. PPP Results for the
132two stations are saved in PPP logfiles.
133
13410. File 'PPPQuickStart.bnc'
135The purpose of this configuration is Precise Point Positioning in Quick-Start
136mode from observations of a static receiver with precisely known position. The
137configuration reads RTCM Version 3 observations, Broadcast Corrections and a
138Broadcast Ephemeris stream. Positions are saved in NMEA format on disc.
139Positions are also output through IP port for real-time visualization with
140tools like RTKPLOT. Positions are also saved in the logfile.
141
14211. File 'PPPPostProc.bnc'
143The purpose of this configuration is Precise Point Positioning in Post
144Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation
145files and a Broadcast Corrections file. PPP processing options are set to
146support the Quick-Start mode. The output is saved in a specific Post Processing
147logfile and contains the coordinates derived over time following the
148implemented PPP filter algorithm.
149
15012. File 'PPPGoogleMaps.bnc'
151The purpose of this configuration is to track BNC's point positioning
152solution using Google Maps or Open StreetMap as background. BNC reads a
153RINEX Observation file and a RINEX Navigation file to carry out a
154'Standard Point Positioning' solution in post-processing mode. Although
155this is not a real-time application it requires the BNC host to be connected
156to the Internet. Specify a computation speed, then hit button 'Open Map'
157to open the track map, then hit 'Start' to visualize receiver positions
158on top of GM/OSM maps.
159
16013. File 'SPPQuickStartGal.bnc'
161The purpose of this configuration is Single Point Positioning in Quick-Start
162mode from observations of a static receiver with precisely known position. The
163configuration uses GPS, GLONASS and Galileo observations and a Broadcast
164Ephemeris stream.
165
16614. File 'SaveSp3.bnc'
167The purpose of this configuration is to produce SP3 files from a Broadcast
168Ephemeris stream and a Broadcast Corrections stream. The Broadcast Corrections
169stream is formally introduced in BNC's 'Combine Corrections' table. Note that
170producing SP3 requires an ANTEX file because SP3 file contents should be
171referred to CoM.
172
17315. File 'Sp3ETRF2000PPP.bnc'
174The purpose of this configuration is to produce SP3 files from a Broadcast
175Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The
176Broadcast Corrections stream is formally introduced in BNC's 'Combine
177Corrections' table. This leads to an SP3 file containing orbits referred also
178to ETRF2000. Pulling in addition observations from a reference station at
179precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution
180with ETRF2000 reference coordinates.
181
18216. File 'Upload.bnc'
183The purpose of this configuration is to upload orbits and clocks from a
184real-time GNSS engine to an NTRIP Broadcaster. For that the configuration reads
185precise orbits and clocks in RTNET format. It also reads a stream carrying
186Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast
187Corrections and encodes them in RTCM Version 3 SSR messages to upload them to
188an NTRIP Broadcaster. The Broadcast Corrections stream is referred to satellite
189Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format
190and clocks in Clock RINEX format.
191
19217. File 'UploadPPP.bnc'
193This configuration equals the 'Upload.bnc' configuration. However, the
194Broadcast Corrections are in addition used for an 'INTERNAL' PPP solution based
195on observations from a static reference station with known precise coordinates.
196This allows a continuous quality check of the Broadcast Corrections through
197observing coordinate displacements.
198
19918. File 'Combi.bnc'
200The purpose of this configuration is to pull several streams carrying Broadcast
201Corrections and a Broadcast Ephemeris stream from an NTRIP Broadcaster to
202produce a combined Broadcast Corrections stream. BNC encodes the combination
203product in RTCM Version 3 SSR messages and uploads that to an Ntrip
204Broadcaster. The Broadcast Corrections stream is not referred to satellite
205Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format
206and clocks in Clock RINEX format.
207
20819. File 'CombiPPP.bnc'
209This configuration equals the 'Combi.bnc' configuration. However, the combined
210Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions
211based on observations from a static reference station with known precise
212coordinates. This allows a continuous quality check of the combination product
213through observing coordinate displacements.
214
21520. File 'UploadEph.bnc'
216The purpose of this configuration is to pull a number of streams from reference
217stations to get hold of contained Broadcast Ephemeris messages. These are
218encoded then in a RTCM Version 3 stream which only provides Broadcast Ephemeris
219with an update rate of 5 seconds.
220
22121. File 'CompareSp3.bnc'
222The purpose of this configuration is to compare two SP3 files to calculate
223RMS values for orbit and clock differences. GPS satellite G05 and GLONASS
224satellite R18 are excluded from this comparison. Comparison results are saved
225in a logfile.
226
22722. File 'Empty.bnc'
228The purpose of this example is to provide an empty configuration file for BNC
229which only contains the default settings.
230
231Georg Weber, BKG
232Frankfurt, August 2015
233igs-ip@bkg.bund.de
Note: See TracBrowser for help on using the repository browser.