Index: /trunk/BNC/bnchelp.html =================================================================== --- /trunk/BNC/bnchelp.html (revision 2444) +++ /trunk/BNC/bnchelp.html (revision 2445) @@ -64,15 +64,15 @@ Fig. 1 shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link for the pupose of Precise Point Positioning. Fig. 2 shows the conversion of RTCM streams to RINEX batches. Fig. 3 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 scenario to encode correctors to RTCMv3.
- +Fig. 1: BNC connected to a GNSS receiver for Precise Point Positioning.
- +
Fig. 2: BNC converting RTCM streams to RINEX batches.
- +
Fig. 3: BNC feeding a real-time GNSS engine.
@@ -96,5 +96,5 @@ This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar, see Fig. 4. - +Fig. 4: Sections on BNC's main window.
@@ -978,5 +978,5 @@ Fig. 5. provides the screenshot of an example PPP session with BNC. - +Fig. 5: Precise Point Positioning (PPP) with BNC.
@@ -1172,20 +1172,20 @@-The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 6 shows the bandwidth comsumption of a number of incoming streams. -
- --
- -Fig. 6: Bandwidth consumption of a number of incoming streams.
+The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 6 shows the bandwidth comsumption of incoming streams. + + ++
+ +Fig. 6: Bandwidth consumption 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 and shown in read color. Note that the calculation of correct latencies requires the clock of the host computer to be properly synchronized. Fig. 7. shows the latency 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 and shown in read color. Note that the calculation of correct latencies requires the clock of the host computer to be properly synchronized. Fig. 7. shows the latency of incoming streams. + + ++
+Fig. 7: Latency of incoming streams.
@@ -1205,5 +1205,5 @@ Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 8. - +Fig. 8: Steam input communication links.
@@ -1222,5 +1222,5 @@ - +Fig. 9: Casters table.
@@ -1242,5 +1242,5 @@ - +Fig. 10: Broadcaster source-table.