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