As a default, configuration files for running BNC on Unix/Linux/Mac systems are saved in directory '${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'. The default configuration file name is 'BNC.bnc'.
@@ -187,4 +189,8 @@ The default file name 'BNC.bnc' can be changed and the file contents can easily be edited. On graphical user interfaces it is possible to Drag & Drop a configuration file icon to start BNC (not on Mac systems). Some configuration options can be changed on-the-fly. See annexed 'Configuration Examples' for a complete set of configuration options. It is also possible to start and configure BNC via command line. + +
Figure 6: Management of configuration options in BNC.
+@@ -475,5 +481,5 @@
Figure 6: BNC translating incoming streams to 15 min RINEX Version 3 files.
+Figure 7: BNC translating incoming streams to 15 min RINEX Version 3 files.
@@ -698,5 +704,5 @@
Figure 7: Example for 'RINEX Editing Options' window.
+Figure 8: Example for 'RINEX Editing Options' window.
3.6.3 Input Files - mandatory if 'Action' is set
Figure 8: Example for RINEX file editing with BNC in Post Processing mode.
+Figure 9: Example for RINEX file editing with BNC in Post Processing mode.
@@ -742,8 +748,8 @@
Figure 9: Example for RINEX quality check graphics output with BNC. A multipath and a signal-to-noise ratio analysis are presented in terms of a sky plot.
+Figure 10: Example for RINEX quality check graphics output with BNC. A multipath and a signal-to-noise ratio analysis are presented in terms of a sky plot.
Figure 10: Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check with BNC.
+Figure 11: Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check with BNC.
3.6.6 Command Line, No Window - optional
Figure 11: Synchronized BNC output via IP port to feed a GNSS real-time engine.
+Figure 12: Synchronized BNC output via IP port to feed a GNSS real-time engine.
@@ -1149,5 +1155,5 @@
Figure 12: BNC pulling a VRS stream to feed a serial connected RTK rover.
+Figure 13: BNC pulling a VRS stream to feed a serial connected RTK rover.
@@ -1300,5 +1306,5 @@
Figure 13: RTCM message numbers, latencies and observation types.
+Figure 14: RTCM message numbers, latencies and observation types.
@@ -1379,8 +1385,8 @@
Figure 14: Precise Point Positioning with BNC, PPP Panel 1.
+Figure 15: Precise Point Positioning with BNC, PPP Panel 1.
Figure 15: Precise Point Positioning with BNC, PPP Panel 2.
+Figure 16: Precise Point Positioning with BNC, PPP Panel 2.
@@ -1669,8 +1675,8 @@
Figure 16: BNC in 'Quick-Start' mode (PPP, Panel 1)
+Figure 17: BNC in 'Quick-Start' mode (PPP, Panel 1)
Figure 17: BNC in 'Quick-Start' mode (PPP, Panel 2)
+Figure 18: BNC in 'Quick-Start' mode (PPP, Panel 2)
3.12.7.8 Maximal Solution Gap - optional if Quick-Start is set
Figure 18: BNC combining Broadcast Correction streams.
+Figure 19: BNC combining Broadcast Correction streams.
Figure 19: BNC uploading the combined Broadcast Corrections stream.
+Figure 20: BNC uploading the combined Broadcast Corrections stream.
Figure 20: 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.
+Figure 21: 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.
3.13.1.2 Method - mandatory if 'Combine Corrections' table is populated
Figure 21: Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.
+Figure 22: Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.
@@ -2181,5 +2187,5 @@
Figure 22: Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an NTRIP Broadcaster.
+Figure 23: Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an NTRIP Broadcaster.
@@ -2248,5 +2254,5 @@
Figure 23: Bandwidth consumption of incoming streams.
+Figure 24: Bandwidth consumption of incoming streams.
@@ -2256,5 +2262,5 @@
Figure 24: Latency of incoming streams.
+Figure 25: Latency of incoming streams.
@@ -2264,5 +2270,5 @@
Figure 25: Time series plot of PPP session.
+Figure 26: Time series plot of PPP session.
@@ -2272,5 +2278,5 @@
Figure 26: Steam input communication links.
+Figure 27: Steam input communication links.
@@ -2297,5 +2303,5 @@
Figure 27: Casters table.
+Figure 28: Casters table.
3.18.1.1.3 User and Password - mandatory for protected streams
Figure 28: Broadcaster source-table.
+Figure 29: Broadcaster source-table.
3.18.1.1.5 NTRIP Version - mandatory
Figure 29: Stream distribution map derived from NTRIP Broadcaster source-table.
+Figure 30: Stream distribution map derived from NTRIP Broadcaster source-table.
3.18.1.2 Add Stream - Coming from TCP/IP Port
Figure 30: BNC setup for pulling a stream via serial port.
+Figure 31: BNC setup for pulling a stream via serial port.