-BNC provides context-sensitive online help (Shift+F1: 'What's This') related to specific objects. It furthermore comes with this software documentation, available as an integral part of the software and as a PDF file. Responsible for online and offline documentation, example configurations (and till February 2014 the overall BNC concept) is Dr. Georg Weber [georg.weber@bkg.bund.de]. +BNC provides context-sensitive online help (Shift+F1: What's This) related to specific objects. It furthermore comes with the here presented documentation, available as an integral part of the software and as a PDF file. Responsible for online and offline documentation, example configurations (and till February 2014 the overall BNC policy concept) is Dr. Georg Weber [georg.weber@bkg.bund.de].
@@ -361,7 +361,7 @@-The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various configuration panels to select a combination of input, processing and output options before you start the program ('Start'). Most configuration panels are dedicated to a certain functionality of BNC. If the first option field on such a configuration panel is empty, the affected functionality is - apart from a few exceptions - deactivated.
- -Records of BNC's activities are shown in the 'Log' tab. The bandwidth consumption per stream, the latency of incoming observations and a PPP time series for coordinates are shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs. +The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various configuration panels to set a combination of input, processing and output options before you start the program ('Start'). Most configuration panels are dedicated to a certain functionality of BNC. If the first option field on such a configuration panel is empty, the affected functionality is deactivated. + +Records of BNC's activities are shown in the 'Log' tab whis is part of the 'Log' canvas. The bandwidth consumption per stream, the latency of incoming observations and a PPP time series for coordinate displacements are also part of that canvas and shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs. @@ -586,5 +586,5 @@-The top menu bar allows selecting a font for the BNC windows, save configured options, or quit the program execution. It also provides access to program documentation. +The top menu bar allows selecting a font for the BNC windows, save configured options, or quit the program execution. It also provides access to the program's documentation.
@@ -624,5 +624,5 @@-BNC comes with a help system providing online information about its functionality and usage. Short descriptions are available for any widget. Focus to the relevant widget and press Shift+F1 to request help information. A help text appears immediately; it disappears as soon as the user does something else. The dialogs on some operating systems may provide a "?" button that users can click; click the relevant widget to pop up the help text. +BNC comes with a What's This help system providing online information about its functionality and usage. Short descriptions are available for any widget and program option. Focus to the relevant object and press Shift+F1 to request help information. A help text appears immediately; it disappears as soon as the user does something else. The dialogs on some operating systems may provide a '?' button that users can click; click the relevant widget to pop up the help text.
@@ -654,4 +654,7 @@ Tick 'Ignore SSL authorization errors' if you generally trust the server and don't want to be bothered with this. Note that SSL communication is usually done over port 443. + +
Figure 7: BNC's 'Network' panel configured to ignore eventually occuring SSL error messages.
@@ -725,18 +728,16 @@-Observations will be converted to RINEX if they come in either RTCM Version 2 or RTCM Version 3 format. Depending on the RINEX version and incoming RTCM message types, files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS and/or BDS (BeiDou). In case an observation type is listed in the RINEX header but the corresponding observation is unavailable, its value is set to zero '0.000'. Note that the 'RINEX TYPE' field in the RINEX Version 3 Observation file header is always set to 'M(MIXED)' or 'Mixed' even if the file only contains data from one system. -
--It is important to understand that converting RTCM streams to RINEX files requires a priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension' and 'Skeleton Mandatory') and switch to a default selection of observation types when such skeleton file is not available or does not contain the required information. The following is a default selection of observation types specified for a RINEX Version 3 file: +Observations will be converted to RINEX if they come in either RTCM Version 2 or RTCM Version 3 format. Depending on the RINEX version and incoming RTCM message types, files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS and/or BDS (BeiDou). In case an observation type is listed in the RINEX header but the corresponding observation is unavailable, its value is set to zero '0.000' or left blank. Note that the 'RINEX TYPE' field in the RINEX Version 3 Observation file header is always set to 'M(MIXED)' or 'Mixed' even if the file only contains data from one system. +
++It is important to understand that converting RTCM streams to RINEX files requires a priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension' and 'Skeleton Mandatory') and switch to a default selection of observation types when such skeleton file is not available or does not contain the required information. The following is the default selection of observation types specified for a RINEX Version 3 file:
-C 9 C2I L2I S2I C6I L6I S6I C7I L7I S7I SYS / # / OBS TYPES -E 12 C1X L1X SX1 C5X L5X SX5 C7X L7X SX7 C8X L8X SX8 SYS / # / OBS TYPES -G 15 C1C L1C S1C C1W L1W S1W C2X L2X S2X C2W L2W S2W C5X SYS / # / OBS TYPES -L5X S5X SYS / # / OBS TYPES -J 15 C1C L1C S1C C1W L1W S1W C2X L2X S2X C2W L2W S2W C5X SYS / # / OBS TYPES -L5X S5X SYS / # / OBS TYPES -R 6 C1C L1C S1C C2P L2P S2P SYS / # / OBS TYPES -S 9 C1C L1C S1C C5I L5I S5I C5Q L5Q S5Q SYS / # / OBS TYPES +C 8 C1 C1P L1 S1 C2 C2P L2 S2 SYS / # / OBS TYPES +E 8 C1 C1P L1 S1 C2 C2P L2 S2 SYS / # / OBS TYPES +G 8 C1 C1W L1 S1 C2 C2W L2 S2 SYS / # / OBS TYPES +J 8 C1 C1P L1 S1 C2 C2P L2 S2 SYS / # / OBS TYPES +R 8 C1 C1P L1 S1 C2 C2P L2 S2 SYS / # / OBS TYPES +S 8 C1 C1P L1 S1 C2 C2P L2 S2 SYS / # / OBS TYPES@@ -745,10 +746,9 @@
-The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from various NTRIP Broadcasters as well as from a serial communication link. Specifying a decoder string 'ZERO' means to not convert the affected stream but save its contents as received. +The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from various NTRIP Broadcasters as well as from a serial communication link. Specifying a decoder string 'ZERO' means to not convert the affected stream but save its contents as received. The 'SSL Error' recorded in the 'Log' tab is caused by the fact that observation stream downloads from IGS and MGEX Broadcasters initiate the download of a RINEX skeleton file from a HTTPS (TLS/SSL) website and BNC has been configured in this example to ignore SSL errors as shown in the preceding 'Network' panel sreenshot.
Figure 7: BNC translating incoming streams to 15 min RINEX Version 3 files.
- +Figure 8: BNC translating incoming streams to 15 min RINEX Version 3 files.
@@ -855,11 +855,11 @@
- OBSERVATION DATA M (MIXED) RINEX VERSION / TYPE + OBSERVATION DATA M (MIXED) RINEX VERSION / TYPE CUT0 MARKER NAME 59945M001 MARKER NUMBER 5023K67889 TRIMBLE NETR9 5.01 REC # / TYPE / VERS 4928353386 TRM59800.00 SCIS ANT # / TYPE --2364337.2699 4870285.5624 -3360809.8398 APPROX POSITION XYZ -0.0000 0.0000 0.0000 ANTENNA: DELTA H/E/N + -2364337.2699 4870285.5624 -3360809.8398 APPROX POSITION XYZ + 0.0000 0.0000 0.0000 ANTENNA: DELTA H/E/N gnss@curtin.edu.au CUT OBSERVER / AGENCY C 10 C1I L1I D1I S1I C6I L6I S6I C7I L7I S7I SYS / # / OBS TYPES @@ -867,10 +867,10 @@ G 13 C1C L1C D1C S1C C2W L2W S2W C2X L2X S2X C5X L5X S5X SYS / # / OBS TYPES J 19 C1C L1C D1C S1C C1X L1X S1X C1Z L1Z S1Z C2X L2X S2X SYS / # / OBS TYPES -C5X L5X S5X C6L L6L S6L SYS / # / OBS TYPES + C5X L5X S5X C6L L6L S6L SYS / # / OBS TYPES R 13 C1C L1C D1C S1C C1P L1P S1P C2C L2C S2C C2P L2P S2P SYS / # / OBS TYPES S 7 C1C L1C D1C S1C C5I L5I S5I SYS / # / OBS TYPES PORTIONS OF THIS HEADER GENERATED BY THE IGS CB FROM COMMENT SITELOG cut0_20150507.log COMMENT - END OF HEADER + END OF HEADER
@@ -1211,20 +1211,20 @@
Figure 8: Example for 'RINEX Editing Options' window.
+Figure 9: Example for 'RINEX Editing Options' window.
Figure 9: Example for RINEX file concatenation with BNC.
+Figure 10: Example for RINEX file concatenation with BNC.
Figure 10: Example for creating RINEX quality check analysis graphics output with BNC.
+Figure 11: Example for creating RINEX quality check analysis graphics output with BNC.
Figure 11: Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC.
+Figure 12: Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC.
Figure 12: Sky plot examples for multipath, part of RINEX quality check analysis with BNC.
+Figure 13: Sky plot examples for multipath, part of RINEX quality check analysis with BNC.
Figure 13: Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC.
+Figure 14: Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC.
3.6.8 Command Line, No Window - optional
Figure 14: BNC configuration example for comparing two SP3 files with satellite orbit and clock data.
+Figure 15: BNC configuration example for comparing two SP3 files with satellite orbit and clock data.
@@ -1762,5 +1762,5 @@
Figure 15: BNC configuration example for pulling, saving and output of Broadcast Corrections.
+Figure 16: BNC configuration example for pulling, saving and output of Broadcast Corrections.
@@ -1843,5 +1843,5 @@
Figure 16: Synchronized BNC output via IP port to feed a GNSS real-time engine.
+Figure 17: Synchronized BNC output via IP port to feed a GNSS real-time engine.
@@ -1885,5 +1885,5 @@
Figure 17: Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams.
+Figure 18: Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams.
@@ -1892,5 +1892,5 @@
Figure 18: BNC pulling a VRS stream to feed a serial connected RTK rover.
+Figure 19: BNC pulling a VRS stream to feed a serial connected RTK rover.
@@ -2051,5 +2051,5 @@
Figure 19: RTCM message numbers, latencies and observation types.
+Figure 20: RTCM message numbers, latencies and observation types.
@@ -2174,5 +2174,5 @@
Figure 20: Real-time Precise Point Positioning with BNC, PPP Panel 1.
+Figure 21: Real-time Precise Point Positioning with BNC, PPP Panel 1.
3.13.1.1 Data Source - optional
Figure 21: Precise Point Positioning with BNC, PPP Panel 2.
+Figure 22: Precise Point Positioning with BNC, PPP Panel 2.
@@ -2614,5 +2614,5 @@
Figure 22: Precise Point Positioning with BNC, PPP Panel 3.
+Figure 23: Precise Point Positioning with BNC, PPP Panel 3.
3.13.3.1 Linear Combinations - mandatory
Figure 23: BNC in 'Quick-Start' mode (PPP, Panel 2)
+Figure 24: BNC in 'Quick-Start' mode (PPP, Panel 2)
3.13.3.NN Averaging - optional if XYZ is set
Figure 24: Track of positions from BNC with Google Maps in the background.
+Figure 25: Track of positions from BNC with Google Maps in the background.
3.13.4.3.1 Google/OSM - mandatory before pushing 'Open Map'
Figure 25: BNC combining Broadcast Correction streams.
+Figure 26: BNC combining Broadcast Correction streams.
Figure 26: BNC uploading the combined Broadcast Corrections stream.
+Figure 27: BNC uploading the combined Broadcast Corrections stream.
Figure 27: 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.
+Figure 28: 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.
3.13.1.2 Method - mandatory if 'Combine Corrections' table is populated
Figure 28: Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94'.
+Figure 29: Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94'.
3.15.4 Center of Mass - optional
Figure 29: Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.
+Figure 30: Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.
3.15.10 ANTEX File - mantatory if 'SP3 File' is specified
Figure 30: 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 31: 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.
@@ -3385,5 +3385,5 @@
Figure 31: Bandwidth consumption of incoming streams.
+Figure 32: Bandwidth consumption of incoming streams.
@@ -3393,5 +3393,5 @@
Figure 32: Latency of incoming streams.
+Figure 33: Latency of incoming streams.
@@ -3401,5 +3401,5 @@
Figure 33: Time series plot of PPP session.
+Figure 34: Time series plot of PPP session.
@@ -3409,5 +3409,5 @@
Figure 34: Steam input communication links.
+Figure 35: Steam input communication links.
@@ -3434,5 +3434,5 @@
Figure 35: Casters table.
+Figure 36: Casters table.
3.19.1.1.3 User and Password - mandatory for protected streams
Figure 36: Broadcaster source-table.
+Figure 37: Broadcaster source-table.
3.19.1.1.5 NTRIP Version - mandatory
Figure 37: Stream distribution map derived from NTRIP Broadcaster source-table.
+Figure 38: Stream distribution map derived from NTRIP Broadcaster source-table.
3.19.1.2 Add Stream - Coming from TCP/IP Port
Figure 38: BNC setup for pulling a stream via serial port.
+Figure 39: BNC setup for pulling a stream via serial port.