-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, the files generated by BNC may contain data from GPS, GLONASS, Galileo and SBAS (coming soon: QZSS and COMPASS). 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. +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, the files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS and COMPASS. 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.
@@ -657,5 +657,8 @@
Figure 7: Example for RINEX file editing with BNC in Post Processing mode.
+Figure 8: Example for RINEX file editing with BNC in Post Processing mode.
+ +
Figure 9: Example for RINEX quality check output with BNC in Post Processing mode. A multi-path analysis is presented in terms of a sky plot.
3.6.5 Command Line, No Window - optional
Figure 8: Synchronized BNC output via IP port to feed a GNSS real-time engine.
+Figure 10: Synchronized BNC output via IP port to feed a GNSS real-time engine.
@@ -1049,5 +1052,5 @@
Figure 9: BNC pulling a VRS stream to feed a serial connected RTK rover.
+Figure 11: BNC pulling a VRS stream to feed a serial connected RTK rover.
@@ -1200,5 +1203,5 @@
Figure 10: RTCM message numbers and latencies.
+Figure 12: RTCM message numbers and latencies.
@@ -1275,8 +1278,8 @@
Figure 11: Precise Point Positioning with BNC, PPP Panel 1.
+Figure 13: Precise Point Positioning with BNC, PPP Panel 1.
Figure 12: Precise Point Positioning with BNC, PPP Panel 2.
+Figure 14: Precise Point Positioning with BNC, PPP Panel 2.
@@ -1565,8 +1568,8 @@
Figure 13: BNC in 'Quick-Start' mode (PPP, Panel 1)
+Figure 15: BNC in 'Quick-Start' mode (PPP, Panel 1)
Figure 14: BNC in 'Quick-Start' mode (PPP, Panel 2)
+Figure 16: BNC in 'Quick-Start' mode (PPP, Panel 2)
3.12.7.8 Maximal Solution Gap - optional if Quick-Start is set
Figure 15: BNC combining Broadcast Correction streams.
+Figure 17: BNC combining Broadcast Correction streams.
Figure 16: BNC uploading the combined Broadcast Corrections stream.
+Figure 18: BNC uploading the combined Broadcast Corrections stream.
Figure 17: 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.
+Figure 19: 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.
3.13.1.2 Method - mandatory if 'Combine Corrections' table is populated
Figure 18: Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.
+Figure 20: Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.
@@ -2065,5 +2068,5 @@
Figure 28: 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 21: 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.
@@ -2132,5 +2135,5 @@
Figure 19: Bandwidth consumption of incoming streams.
+Figure 22: Bandwidth consumption of incoming streams.
@@ -2140,5 +2143,5 @@
Figure 20: Latency of incoming streams.
+Figure 23: Latency of incoming streams.
@@ -2148,5 +2151,5 @@
Figure 21: Time series plot of PPP session.
+Figure 24: Time series plot of PPP session.
@@ -2156,5 +2159,5 @@
Figure 22: Steam input communication links.
+Figure 25: Steam input communication links.
3.18.1 Add Stream - Coming from Caster
Figure 23: Casters table.
+Figure 26: Casters table.
3.18.1.3 User and Password - mandatory for protected streams
Figure 24: Broadcaster source-table.
+Figure 27: Broadcaster source-table.
Button 'Map' leads to the presentation of a map showing the distribution of streams offered through the downloaded source-table.
@@ -2225,5 +2228,5 @@
Figure 25: Stream distribution map derived from NTRIP Broadcaster source-table.
+Figure 28: Stream distribution map derived from NTRIP Broadcaster source-table.
3.18.2 Add Stream - Coming from TCP/IP Port
Figure 26: BNC setup for pulling a stream via serial port.
+Figure 29: BNC setup for pulling a stream via serial port.
@@ -2379,5 +2382,4 @@ -[Bug] Bug in on-the-fly configuration fixed
[Add] Clock RINEX file header extended
[Add] Decoding/converting COMPASS and QZSS added
[Add] Work on RINEX quality check started
[Bug] Bug in on-the-fly configuration fixed
[Add] Clock RINEX file header extended
[Add] Decoding/converting COMPASS and QZSS added
[Add] Work on RINEX v2 and v3 quality check started
[Mod] Source code completely re-arranged
[Add] QWT and QWTPOLAR graphics libraries added
[Add] RINEX v2 and v3 quality check through multi-path analysis and sky plot