1 | Configuration Examples
|
---|
2 |
|
---|
3 | BNC comes with a number of configuration examples which can be used on all
|
---|
4 | operating systems. Copy the complete directory 'Example_Configs' which comes
|
---|
5 | with the software including sub-directories 'Input' and 'Output' to your disc.
|
---|
6 | There 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 |
|
---|
20 | Although it's not a must, we suggest that you always create BNC configuration
|
---|
21 | files with the filename extension '.bnc'.
|
---|
22 |
|
---|
23 | We furthermore suggest for convenience reasons that you configure your system
|
---|
24 | to automatically start BNC when you double-click a file with the filename
|
---|
25 | extension '.bnc'. The following describes what to do on Windows systems to
|
---|
26 | associate the BNC program to such configuration files:
|
---|
27 |
|
---|
28 |
|
---|
29 | 1. 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 |
|
---|
33 | 2. 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 |
|
---|
36 | 3. Click 'Select the program from a list', and then click 'OK'.
|
---|
37 |
|
---|
38 | 4. The 'Open With' dialog box is displayed. Click 'Browse', locate and then
|
---|
39 | click the BNC program, and then click 'Open'.
|
---|
40 |
|
---|
41 | 5. Click to select the 'Always use the selected program to open this kind
|
---|
42 | of file' check box.
|
---|
43 |
|
---|
44 | 6. Click 'OK'.
|
---|
45 |
|
---|
46 | Some of the presented example configuration files contain a user ID 'Example'
|
---|
47 | with a password 'Configs' for accessing a few GNSS streams from public Ntrip
|
---|
48 | Broadcasters. This generic account is arranged for convenience reasons only.
|
---|
49 | Please be so kind as to replace the generic account details as well as the
|
---|
50 | place holders 'User' and 'Pass' by the personal user ID and password you
|
---|
51 | receive following an online registration through
|
---|
52 | http://register.rtcm-ntrip.org.
|
---|
53 |
|
---|
54 | Note that the account for an Ntrip Broadcaster is usually limited to
|
---|
55 | pulling a specified maximum number of streams at the same time. As running
|
---|
56 | some of the example configurations requires pulling several streams, it
|
---|
57 | is suggested to make sure that you don't exceed your account's limits.
|
---|
58 |
|
---|
59 | Make also sure that sub-directories 'Input' and 'Output' which are part of
|
---|
60 | the example configurations exist on your system or adjust the affected
|
---|
61 | example configuration options according to your needs.
|
---|
62 |
|
---|
63 | Some BNC options require antenna phase center variations as made available
|
---|
64 | from IGS through so-called ANTEX files at
|
---|
65 | https://files.igs.org/pub/station/general/igs20.atx
|
---|
66 | An example ANTEX file 'igs20.atx' is part of the BNC package for convenience.
|
---|
67 |
|
---|
68 | The example configurations assume that no proxy protects your BNC host.
|
---|
69 | Should a proxy be operated in front of BNC then you need to introduce its
|
---|
70 | name or IP and port number in the 'Network' panel.
|
---|
71 |
|
---|
72 | (A) Working with Configuration Files
|
---|
73 |
|
---|
74 | You should be able to run all configuration file examples without changing
|
---|
75 | contained options. However, configurations 'Upload.bnc' and 'UploadEPH.bnc' are
|
---|
76 | exceptions because they require an input stream from a connected network engine.
|
---|
77 |
|
---|
78 | 1. Configuration File 'RinexObs.bnc'
|
---|
79 | Purpose: Convert RTCM streams to RINEX Observation files.
|
---|
80 | The configuration pulls RTCM Version 3 streams from Ntrip Broadcasters using
|
---|
81 | Ntrip Version 2 to generate 15min 1Hz RINEX Version 4 Observation files. See
|
---|
82 | https://igs.bkg.bund.de/ntrip/#rtcm-obs for observation stream resources.
|
---|
83 |
|
---|
84 | 2. Configuration File 'RinexEph.bnc'
|
---|
85 | Purpose: Convert a RTCM stream with navigation messages to RINEX Navigation
|
---|
86 | files. The configuration pulls a RTCM Version 3 stream with Broadcast Ephemeris
|
---|
87 | coming from the real-time EUREF and IGS networks and saves hourly RINEX Version
|
---|
88 | 4 Navigation files. See https://igs.bkg.bund.de/ntrip/#rtcm-eph for further
|
---|
89 | real-time Broadcast Ephemeris resources.
|
---|
90 |
|
---|
91 | 3. Configuration File 'BrdcCorr.bnc'
|
---|
92 | Purpose: Save Broadcast Corrections from RTCM SSR messages in hourly plain
|
---|
93 | ASCII files. See https://igs.bkg.bund.de/ntrip/#rtcm-corr for various real-time IGS
|
---|
94 | or EUREF orbit/clock correction products.
|
---|
95 |
|
---|
96 | 4. Configuration File 'RinexConcat.bnc'
|
---|
97 | Purpose: Concatenate several RINEX Version 3 files to produce one compiled file
|
---|
98 | and edit the marker name in the file header. The sampling interval is set to 30
|
---|
99 | seconds. See section 'RINEX Editing & QC' in the documentation for examples on
|
---|
100 | how to call BNC from command line in 'no window' mode for RINEX file editing,
|
---|
101 | concatenation and quality check.
|
---|
102 |
|
---|
103 | 5. Configuration File 'RinexQC.bnc'
|
---|
104 | Purpose: Check the quality of a RINEX Version 4 file by means of a multipath
|
---|
105 | analysis. Results are saved on disk in terms of a plot in PNG format. See
|
---|
106 | section 'RINEX Editing & QC' in the documentation for examples on how to call
|
---|
107 | BNC from command line in 'no window' mode for RINEX file editing, concatenation
|
---|
108 | and quality check.
|
---|
109 |
|
---|
110 | 6. Configuration File 'RTK.bnc'
|
---|
111 | Purpose: Feed a serial connected receiver with observations from a nearby
|
---|
112 | reference station for conventional RTK. The stream is scanned for RTCM
|
---|
113 | messages. Message type numbers and latencies of incoming observations are
|
---|
114 | reported in BNC's logfile.
|
---|
115 |
|
---|
116 | 7. Configuration File 'FeedEngine.bnc'
|
---|
117 | Purpose: Feed a real-time GNSS engine with observations from remote reference
|
---|
118 | stations. The configuration pulls a single stream from an Ntrip Broadcaster.
|
---|
119 | You could also pull several streams from different casters. Incoming
|
---|
120 | observations are decoded, synchronized, output through a local IP port and also
|
---|
121 | saved into a file. Failure and recovery thresholds are specified to inform
|
---|
122 | about outages.
|
---|
123 |
|
---|
124 | 8. Configuration File 'PPP.bnc'
|
---|
125 | Purpose: Precise Point Positioning from observations of a rover receiver. The
|
---|
126 | configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream
|
---|
127 | and a stream with Broadcast Corrections. Positions are saved in the logfile.
|
---|
128 | More detailed PPP results are saved in the PPP logfile.
|
---|
129 |
|
---|
130 | 9. Configuration File 'PPPNet.bnc'
|
---|
131 | Purpose: Precise Point Positioning for several rovers or receivers from an
|
---|
132 | entire network of reference stations in one BNC job. The possible maximum
|
---|
133 | number of PPP solutions per job depends on the processing power of the hosting
|
---|
134 | computer. This example configuration reads two RTCM Version 3 observation
|
---|
135 | streams, a Broadcast Ephemeris stream and a stream with Broadcast Corrections.
|
---|
136 | Detailed PPP Results for the two stations are saved in PPP logfiles.
|
---|
137 |
|
---|
138 | 10. Configuration File 'PPPQuickStart.bnc'
|
---|
139 | Purpose: Precise Point Positioning in Quick-Start mode from observations of a
|
---|
140 | static receiver with precisely known position. The configuration reads RTCM
|
---|
141 | Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream.
|
---|
142 | Positions are saved in NMEA format on disc. They are also output through IP
|
---|
143 | port for real-time visualization with tools like RTKPLOT. Positions are saved
|
---|
144 | in the logfile.
|
---|
145 |
|
---|
146 | 11. Configuration File 'PPPPostProc.bnc'
|
---|
147 | Purpose: Precise Point Positioning in post processing mode. BNC reads RINEX
|
---|
148 | Version 3 Observation and Navigation files and a Broadcast Correction file.
|
---|
149 | Optionally, an Ionosphere file containing VTEC informations can be used. If such
|
---|
150 | a file is not specified, VTEC informations from the Broadcast Corrections file
|
---|
151 | are used. PPP processing options are set to support the Quick-Start mode.
|
---|
152 | The output is saved in a specific post processing logfile and contains
|
---|
153 | coordinates derived over time following the implemented PPP filter algorithm.
|
---|
154 |
|
---|
155 | 12. Configuration File 'PPPOsm.bnc'
|
---|
156 | Purpose: Track BNC's point positioning solutions using OpenStreetMap as background.
|
---|
157 | BNC reads a RINEX Observation file and a RINEX Navigation file to carry out
|
---|
158 | a 'Standard Point Positioning' solution in post processing mode.
|
---|
159 | Although this is not a real-time application it requires the BNC host to be
|
---|
160 | connected to the Internet. Specify a computation speed, then hit button 'Open Map'
|
---|
161 | to open the track map, then hit 'Start' to visualize receiver positions on top
|
---|
162 | of OSM maps.
|
---|
163 |
|
---|
164 | 13. Configuration File 'SPPQuickStartGal.bnc'
|
---|
165 | Purpose: Single Point Positioning in Quick-Start mode from observations of a
|
---|
166 | static receiver with quite precisely known position. The configuration uses
|
---|
167 | Galileo observations only and a Broadcast Ephemeris stream.
|
---|
168 |
|
---|
169 | 14. Configuration File 'SaveSp3.bnc'
|
---|
170 | Purpose: Produces SP3 files from a Broadcast Ephemeris stream and a Broadcast
|
---|
171 | Correction stream. The Broadcast Correction stream is formally introduced in
|
---|
172 | BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX
|
---|
173 | file because SP3 file content should be referred to CoM.
|
---|
174 |
|
---|
175 | 15. Configuration File 'Sp3ETRF2000PPP.bnc'
|
---|
176 | Purpose: Produce SP3 files from a Broadcast Ephemeris stream and a stream
|
---|
177 | carrying ETRF2000 Broadcast Corrections. The Broadcast Correction stream is
|
---|
178 | formally introduced in BNC's 'Combine Corrections' table. The configuration
|
---|
179 | leads to a SP3 file containing orbits also referred to ETRF2000. Pulling in
|
---|
180 | addition observations from a reference station at precisely known ETRF2000
|
---|
181 | position allows comparing an 'INTERNAL' PPP solution with a known ETRF2000
|
---|
182 | reference coordinate.
|
---|
183 |
|
---|
184 | 16. Configuration File 'Upload.bnc'
|
---|
185 | Purpose: Upload orbits and clocks from a real-time GNSS engine to an Ntrip
|
---|
186 | Broadcaster. For that the configuration reads precise orbits and clocks in
|
---|
187 | RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts
|
---|
188 | the orbits and clocks into Broadcast Corrections and encodes them to
|
---|
189 | IGS-SSR messages to finally upload them to an Ntrip Broadcaster. The
|
---|
190 | Broadcast Correction stream is referred to satellite Antenna Phase Center (APC)
|
---|
191 | and reference system IGS20. Orbits are saved on disk in SP3 format and clocks
|
---|
192 | are saved in Clock RINEX format.
|
---|
193 |
|
---|
194 | 17. Configuration File 'Combi.bnc'
|
---|
195 | Purpose: Pull 2 streams carrying Broadcast Corrections, and Satellite Code Biases
|
---|
196 | together with Broadcast Ephemeris from an Ntrip Broadcaster
|
---|
197 | to produce a combined Broadcast Correction stream.
|
---|
198 | BNC encodes the combination product in IGS-SSR messages and uploads them to
|
---|
199 | an Ntrip Broadcaster. The Broadcast Correction stream is referred to
|
---|
200 | satellite Antenna Phase Center (APC) and not to satellite Center of
|
---|
201 | Mass (CoM). Its reference system is IGS20. Orbits are saved in SP3 format
|
---|
202 | (referred to CoM) and clocks in Clock RINEX format.
|
---|
203 |
|
---|
204 | 18. Configuration File 'CombiPPP.bnc'
|
---|
205 | Purpose: This configuration equals the 'Combi.bnc' configuration. However, the
|
---|
206 | combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP
|
---|
207 | solutions based on observations from a static reference station with known
|
---|
208 | precise coordinates. This allows a continuous quality check of the combination
|
---|
209 | product through observing coordinate displacements.
|
---|
210 |
|
---|
211 | 19. Configuration File 'UploadEph.bnc'
|
---|
212 | Purpose: Pull a number of streams from reference stations to get the
|
---|
213 | contained Broadcast Ephemeris messages. They are encoded to RTCM Version 3
|
---|
214 | format and uploaded for the purpose of providing a Broadcast Ephemeris stream
|
---|
215 | with an update rate of 5 seconds.
|
---|
216 |
|
---|
217 | 20. Configuration File 'CompareSp3.bnc'
|
---|
218 | Purpose: Compare two SP3 files to calculate RMS values for orbit and clock
|
---|
219 | differences. GPS satellite G05 and GLONASS satellite R18 are excluded from this
|
---|
220 | comparison. Comparison results are saved in a logfile.
|
---|
221 |
|
---|
222 | 21. Configuration File 'Empty.bnc'
|
---|
223 | Purpose: Provide an empty example configuration file for BNC which only
|
---|
224 | contains the default settings.
|
---|
225 |
|
---|
226 | (B) Working with Command Line configuration options
|
---|
227 |
|
---|
228 | The following configuration examples make use of BNC's 'Command Line Interface'
|
---|
229 | (CLI). Configuration options are exclusively specified via command line. No
|
---|
230 | configuration file is used. Examples are provided as shell scripts for a Linux
|
---|
231 | system. They call BNC in 'no window' batch mode (command line option -nw).
|
---|
232 | The scripts expect 'Example_Configs' to be the current working directory.
|
---|
233 |
|
---|
234 | 22. Shell Script 'RinexQC.sh'
|
---|
235 | Purpose: Equals configuration file example 'RinexQC.bnc', checks the quality of
|
---|
236 | a RINEX Version 4 file by means of a multipath analysis. The platform offscreen
|
---|
237 | is used while producing plot files in PNG format. BNC is offline.
|
---|
238 | All results are saved on disk.
|
---|
239 |
|
---|
240 | 23. Shell Script 'RinexConcat.sh'
|
---|
241 | Purpose: Equals configuration file example 'RinexConcat.bnc', concatenates
|
---|
242 | several RINEX Version 3 files to produce one compiled file and edit the marker
|
---|
243 | name in the file header. The sampling interval is set to 30 seconds. BNC is
|
---|
244 | offline.
|
---|
245 |
|
---|
246 | 24. Shell Script 'RinexEph.sh'
|
---|
247 | Purpose: Equals configuration file example 'RinexEph.bnc', converts a RTCM
|
---|
248 | stream with navigation messages to RINEX Navigation files. The configuration
|
---|
249 | pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the
|
---|
250 | real-time EUREF and IGS networks and saves hourly RINEX Version 4 Navigation
|
---|
251 | files. BNC runs online until it's terminated after 10 seconds. See
|
---|
252 | https://igs.bkg.bund.de/ntrip/#rtcm-eph for further real-time Broadcast
|
---|
253 | Ephemeris resources.
|
---|
254 |
|
---|
255 | 25. Shell Script 'ScanLate.sh'
|
---|
256 | Purpose: Scan an observation stream for contained RTCM message types, print
|
---|
257 | observation latencies. The output is saved in a logfile. Latencies are
|
---|
258 | reported every 10 seconds. BNC runs online until it's terminated after 20
|
---|
259 | seconds.
|
---|
260 |
|
---|
261 | 26. Shell Script 'RinexObs.sh'
|
---|
262 | Purpose: Equals configuration file example 'RinexObs.bnc', converts RTCM
|
---|
263 | streams to RINEX Observation files. The configuration pulls streams from two
|
---|
264 | Ntrip Broadcasters using Ntrip Version 2 to generate 15min 1Hz RINEX Version 4
|
---|
265 | Observation files. See https://igs.bkg.bund.de/ntrip/#rtcm-obs for
|
---|
266 | observation stream resources. BNC runs online until it's terminated after 30
|
---|
267 | seconds.
|
---|
268 |
|
---|
269 | (C) Command Line configuration options overwriting Configuration File options
|
---|
270 |
|
---|
271 | For specific applications you may like to use your own set of standard
|
---|
272 | configuration options from a configuration file and update some of its content
|
---|
273 | via command line. When using a configuration file and command line configuration
|
---|
274 | options together in one BNC call, the command line configuration options will
|
---|
275 | always overrule options contained in the configuration file.
|
---|
276 |
|
---|
277 | 27. Shell Script 'CompareSp3.sh'
|
---|
278 | Purpose: Equals configuration file example 'CompareSp3.bnc', compares two SP3
|
---|
279 | files to calculate RMS values for orbit and clock differences. However, instead
|
---|
280 | of excluding GPS satellite G05 and GLONASS satellite R18 from the comparison as
|
---|
281 | specified in 'CompareSp3.bnc', GPS satellite G06 and all GLONASS satellites are
|
---|
282 | excluded via command line option. BNC runs offline. Comparison results are saved
|
---|
283 | in a logfile.
|
---|
284 |
|
---|
285 | Andrea Stuerze, BKG
|
---|
286 | Frankfurt, September 2022
|
---|
287 | igs-ip@bkg.bund.de
|
---|
288 |
|
---|