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

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

Documentation completed

File size: 11.6 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
71You should be able to run all configuration examples without changing their
72options. However, configurations 'Upload.bnc' and 'UploadPPP.bnc' are
73exceptions because they require an input stream from a connected network engine.
74
751. File 'RinexObs.bnc'
76The purpose of this configuration is showing how to convert RTCM streams to
77RINEX Observation files. The configuration pulls streams from Ntrip
78Broadcasters using Ntrip version 1 to generate 15min 1Hz RINEX Version 3
79Observation files. See http://igs.bkg.bund.de/ntrip/observations for
80observation stream resources.
81
822. File 'RinexEph.bnc'
83The purpose of this configuration is showing how to convert a RTCM stream
84carrying navigation messages to a RINEX Navigation files. The configuration
85pulls an RTCM Version 3 stream with Broadcast Ephemeris coming from the
86real-time EUREF and IGS networks. It saves hourly RINEX Version 3 Navigation
87files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time
88Broadcast Ephemeris resources.
89
903. File 'BrdcCorr.bnc'
91The purpose of this configuration is to save Broadcast Corrections from
92RTCM SSR messages in a plain ASCII format as hourly files. See
93http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF
94orbit/clock products.
95
964. File 'RinexConcat.bnc'
97The purpose of this configuration is to concatenate RINEX Version 3 files
98to produce a concatenated file and edit the marker name in the file header. The
99sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the
100documentation for examples on how to call BNC from command line in 'no window'
101mode for RINEX file editing, concatenation and quality checks.
102
1035. File 'RinexQC.bnc'
104The purpose of this configuration is to check the quality of a RINEX
105Version 3 file through a multipath analysis. The results are saved on disk in
106terms of a plot in PNG format. See section 'RINEX Editing & QC' in the
107documentation for examples on how to call BNC from command line in 'no window'
108mode for RINEX file editing, concatenation and quality checks.
109
1106. File 'RTK.bnc'
111The purpose of this configuration is to feed a serial connected receiver
112with observations from a reference station for conventional RTK. The stream is
113scanned for RTCM messages. Message type numbers and latencies of incoming
114observation are reported in BNC's logfile.
115
1167. File 'FeedEngine.bnc'
117The purpose of this configuration is to feed a real-time GNSS engine with
118observations from a remote reference stations. The configuration pulls a single
119stream from an Ntrip Broadcasters. It would of course be possible to pull
120several streams from different casters. Incoming observations are decoded,
121synchronized and output through a local IP port and saved into a file. Failure
122and recovery thresholds are specified to inform about outages.
123
1248. File 'PPP.bnc'
125The purpose of this configuration is Precise Point Positioning from
126observations of a rover receiver. The configuration reads RTCM Version 3
127observations, a Broadcast Ephemeris stream and a stream with Broadcast
128Corrections. Positions are saved in the logfile.
129
1309. File 'PPPNet.bnc'
131The purpose of this configuration is to demonstrate simultaneous Precise
132Point Positioning for several rovers or several receivers from a network of
133reference stations in one BNC job. The possible maximum number of PPP solutions
134per job depends on the processing power of the hosting computer. This example
135configuration reads two RTCM Version 3 observation streams, a Broadcast
136Ephemeris stream and a stream with Broadcast Corrections. PPP Results for the
137two stations are saved in PPP logfiles.
138
13910. File 'PPPQuickStart.bnc'
140The purpose of this configuration is Precise Point Positioning in
141Quick-Start mode from observations of a static receiver with precisely known
142position. The configuration reads RTCM Version 3 observations, Broadcast
143Corrections and a Broadcast Ephemeris stream. Positions are saved in NMEA
144format on disc. Positions are also output through IP port for real-time
145visualization with tools like RTKPLOT. Positions are also saved in the logfile.
146
14711. File 'PPPPostProc.bnc'
148The purpose of this configuration is Precise Point Positioning in Post
149Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation
150files and a Broadcast Corrections file. PPP processing options are set to
151support the Quick-Start mode. The output is saved in a specific Post Processing
152logfile and contains the coordinates derived over time following the
153implemented PPP filter algorithm.
154
15512. File 'PPPGoogleMaps.bnc'
156The purpose of this configuration is to track BNC's point positioning
157solution using Google Maps or OpenStreetMap as background. BNC reads a RINEX
158Observation file and a RINEX Navigation file to carry out a 'Standard Point
159Positioning' solution in post-processing mode. Although this is not a real-time
160application it requires the BNC host to be connected to the Internet. Specify a
161computation speed, then hit button 'Open Map' to open the track map, then hit
162'Start' to visualize receiver positions on top of GM/OSM maps.
163
16413. File 'SPPQuickStartGal.bnc'
165The purpose of this configuration is Single Point Positioning in
166Quick-Start mode from observations of a static receiver with precisely known
167position. The configuration uses GPS, GLONASS and Galileo observations and a
168Broadcast Ephemeris stream.
169
17014. File 'SaveSp3.bnc'
171The purpose of this configuration is to produce SP3 files from a Broadcast
172Ephemeris stream and a Broadcast Corrections stream. The Broadcast Corrections
173stream is formally introduced in BNC's 'Combine Corrections' table. Note that
174producing SP3 requires an ANTEX file because SP3 file contents should be
175referred to CoM.
176
17715. File 'Sp3ETRF2000PPP.bnc'
178The purpose of this configuration is to produce SP3 files from a Broadcast
179Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The
180Broadcast Corrections stream is formally introduced in BNC's 'Combine
181Corrections' table. This leads to an SP3 file containing orbits referred also
182to ETRF2000. Pulling in addition observations from a reference station at
183precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution
184with ETRF2000 reference coordinates.
185
18616. File 'Upload.bnc'
187The purpose of this configuration is to upload orbits and clocks from a
188real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads
189precise orbits and clocks in RTNET format. It also reads a stream carrying
190Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast
191Corrections and encodes them in RTCM Version 3 SSR messages to upload them to
192an Ntrip Broadcaster. The Broadcast Corrections stream is referred to satellite
193Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format
194and clocks in Clock RINEX format.
195
19617. File 'Combi.bnc'
197The purpose of this configuration is to pull several streams carrying
198Broadcast Corrections and a Broadcast Ephemeris stream from an Ntrip
199Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the
200combination product in RTCM Version 3 SSR messages and uploads that to an Ntrip
201Broadcaster. The Broadcast Corrections stream is not referred to satellite
202Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format
203and clocks in Clock RINEX format.
204
20518. File 'CombiPPP.bnc'
206This configuration equals the 'Combi.bnc' configuration. However, the
207combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP
208solutions based on observations from a static reference station with known
209precise coordinates. This allows a continuous quality check of the combination
210product through observing coordinate displacements.
211
21219. File 'UploadEph.bnc'
213The purpose of this configuration is to pull a number of streams from
214reference stations to get hold of contained Broadcast Ephemeris messages. These
215are encoded then in a RTCM Version 3 stream which only provides Broadcast
216Ephemeris with an update rate of 5 seconds.
217
21820. File 'CompareSp3.bnc'
219The purpose of this configuration is to compare two SP3 files to calculate
220RMS values for orbit and clock differences. GPS satellite G05 and GLONASS
221satellite R18 are excluded from this comparison. Comparison results are saved
222in a logfile.
223
22421. File 'Empty.bnc'
225The purpose of this example is to provide an empty configuration file for
226BNC which only contains the default settings.
227
228Georg Weber, BKG
229Frankfurt, December 2015
230igs-ip@bkg.bund.de
231
Note: See TracBrowser for help on using the repository browser.