-Fig. 1 shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link. -
-
- -
-Fig. 2 shows a flow chart of BNC feeding a real-time GNSS engine. The engine estimates satellite orbit and clock correctors. -
-
- - -
BNC supports decoding the following GNSS data formats:
@@ -73,4 +60,15 @@ BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files. + ++Fig. 1 shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link. Fig. 2 shows a flow chart of BNC feeding a real-time GNSS engine. The engine then estimates satellite orbit and clock correctors. The 'BKG Ntrip Server' (BNS) is used in this scenariy to encode correctors to RTCMv3. +
+
Fig. 1: BNC connected to a GNSS receiver.
+ ++
+
Fig. 2: BNC feeding a real-time GNSS engine.
@@ -967,4 +965,9 @@ ++Fig. 3. provides the screenshot of an example PPP session with BNC. +
+
Fig. 3: Precise Point Positioning (PPP) with BNC.
@@ -1159,11 +1162,21 @@
-The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). -
+The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 4 shows the bandwidth comsumption of a number of incoming streams. + + ++
+
Fig. 4: Bandwidth consumption of a number of incoming streams.
-The latency of observations in each incoming stream is shown in the 'Latency' tab in milliseconds or seconds. Streams not carrying observations (i.e. those providing only broadcast ephemeris messages) are not considered here. Note that the calculation of correct latencies requires the clock of the host computer to be properly synchronized. -
+The latency of observations in each incoming stream is shown in the 'Latency' tab in milliseconds or seconds. Streams not carrying observations (i.e. those providing only broadcast ephemeris messages) are not considered here and shown in read color. Note that the calculation of correct latencies requires the clock of the host computer to be properly synchronized. Fig. 5. shows the latency of a number of incoming streams. + + ++
+
Fig. 5: Latency of incoming streams.
@@ -1178,6 +1191,13 @@3.14.1 Add Stream - Coming from Caster
-Button 'Add Stream' > 'Coming from Caster' opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints. + +
+Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 6. +
+
Fig. 6: Steam input communication links.
+ ++Button 'Add Stream' > 'Coming from Caster' then opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints.
@@ -1189,6 +1209,9 @@3.14.1.2 Casters Table - optional
-It may be that your are not sure about your NTRIP broadcasters host and port number or you are interested in other broadcaster installations operated elsewhere. Hit 'Show' for a table of known broadcasters maintained at www.rtcm-ntrip.org/home. A window opens which allows to select a broadcaster for stream retrieval. -
+It may be that your are not sure about your NTRIP broadcasters host and port number or you are interested in other broadcaster installations operated elsewhere. Hit 'Show' for a table of known broadcasters maintained at www.rtcm-ntrip.org/home. A window opens which allows to select a broadcaster for stream retrieval, see Fig. 7. + + +
Fig. 7: Casters table.
3.14.1.3 User and Password - mandatory for protected streams
-Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. +Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. Fig. 8 provides an example source-table.
@@ -1207,4 +1230,8 @@ Hit 'OK' to return to the main window. If you wish you can click on 'Add Stream' and repeat the process again to retrieve streams from different casters.
+ + +
Fig. 8: Broadcaster source-table.