Changeset 2472 in ntrip for trunk/BNC/bnchelp.html

Timestamp:

May 5, 2010, 3:02:38 PM (14 years ago)

Author:

weber

Message:

* empty log message *

File:

• trunk/BNC/bnchelp.html (modified) (16 diffs)

trunk/BNC/bnchelp.html

@@ -64 +64 @@
 The first of the following figures shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link for the pupose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX batches. The third figure 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.
 </p>
-<p><img src=":/bnchelp/screenshot10.png"/></p>
+<p><img src="IMG/screenshot10.png"/></p>
 <p><u>Figure:</u> Flowchart, BNC connected to a GNSS receiver for Precise Point Positioning.</p>
 
 <p>
 </p>
-<p><img src=":/bnchelp/screenshot01.png"/></p>
+<p><img src="IMG/screenshot01.png"/></p>
 <p><u>Figure:</u> Flowchart, BNC converting RTCM streams to RINEX batches.</p>
 
 <p>
 </p>
-<p><img src=":/bnchelp/screenshot02.png"/></p>
+<p><img src="IMG/screenshot02.png"/></p>
 <p><u>Figure:</u> Flowchart, BNC feeding a real-time GNSS engine.</p>
 
@@ -95 +95 @@
 The main window of BNC shows a top menu bar section, a sections for tabs to set processing options, a 'Streams' section and a section for 'Log' tabs, and a bottom menu bar section, see figure below.
 </p>
-<p><img src=":/bnchelp/screenshot09.png"/></p>
+<p><img src="IMG/screenshot09.png"/></p>
 <p><u>Figure:</u> Sections on BNC's main window.</p>
 
@@ -299 +299 @@
 The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming in from various NTRIP broadcasters as well as via a plain UDP and a serial communication link. Decoder 'ZERO' has been selected for one stream to not convert its contents but save it in original format.
 </p>
-<p><img src=":/bnchelp/screenshot16.png"/></p>
+<p><img src="IMG/screenshot16.png"/></p>
 <p><u>Figure:</u> BNC translating incoming streams to 15 min RINEX Version 3 files.</p>
 
@@ -494 +494 @@
 
 <p>
-Saved files contain blocks of records in plain ASCII format where - separate for GPS, GLONASS, message types, and streams - the end of a block is indicated by a line like (examples):
+Saved files contain blocks of records in plain ASCII format where - separate for GPS, GLONASS, message types, streams, and epochs - the begin of a block is indicated by a line like (examples):
 </p>
 <p>
@@ -501 +501 @@
 ! Orbits/Clocks: 0 GPS 19 Glonass CLK11
 <p>
-Such line informs you about the number of records (here 30 and 19) carrying GPS or GLONASS related parameters you should have received so far within a certain stream. It therefore indicates the end of an epoch with respect to a specific GNSS, message type and stream.
+Such line informs you about the number of records (here 30 and 19) carrying GPS or GLONASS related parameters you should receive next as part of a certain stream. 
 </p>
 <p>
@@ -758 +758 @@
 The following figure shows the screenshot of a BNC configuration where a number if streams is pulled from different NTRIP broadcasters to feed a GNSS engine via IP port output.
 </p>
-<p><img src=":/bnchelp/screenshot12.png"/></p>
+<p><img src="IMG/screenshot12.png"/></p>
 <p><u>Figure:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p>
 
@@ -797 +797 @@
 </p>
 </p>
-<p><img src=":/bnchelp/screenshot11.png"/></p>
+<p><img src="IMG/screenshot11.png"/></p>
 <p><u>Figure:</u> BNC pulling a VRS stream to feed a serial connected rover.</p>
 
@@ -945 +945 @@
 The following figure shows RTCM message numbers contained in stream 'CONZ0' and the message latencies recorded every 10 seconds.
 </p>
-<p><img src=":/bnchelp/screenshot14.png"/></p>
+<p><img src="IMG/screenshot14.png"/></p>
 <p><u>Figure:</u> RTCM message numbers and latencies.</p>
 
@@ -1019 +1019 @@
 The following figure provides the screenshot of an example PPP session with BNC.
 </p>
-<p><img src=":/bnchelp/screenshot03.png"/></p>
+<p><img src="IMG/screenshot03.png"/></p>
 <p><u>Figure:</u> Precise Point Positioning (PPP) with BNC.</p>
 
@@ -1218 +1218 @@
 <p>
 </p>
-<p><img src=":/bnchelp/screenshot08.png"/></p>
+<p><img src="IMG/screenshot08.png"/></p>
 <p><u>Figure:</u> Bandwidth consumption of incoming streams.</p>
 
@@ -1228 +1228 @@
 <p>
 </p>
-<p><img src=":/bnchelp/screenshot07.png"/></p>
+<p><img src="IMG/screenshot07.png"/></p>
 <p><u>Figure:</u> Latency of incoming streams.</p>
 
@@ -1238 +1238 @@
 <p>
 </p>
-<p><img src=":/bnchelp/screenshot13.png"/></p>
+<p><img src="IMG/screenshot13.png"/></p>
 <p><u>Figure:</u> Time series plot of PPP session.</p>
 
@@ -1246 +1246 @@
 </p>
 
-<p><img src=":/bnchelp/screenshot06.png"/></p>
+<p><img src="IMG/screenshot06.png"/></p>
 <p><u>Figure:</u> Steam input communication links.</p>
 
@@ -1265 +1265 @@
 </p> 
 </p>
-<p><img src=":/bnchelp/screenshot04.png"/></p>
+<p><img src="IMG/screenshot04.png"/></p>
 <p><u>Figure:</u> Casters table.</p>
 
@@ -1285 +1285 @@
 </p> 
 </p>
-<p><img src=":/bnchelp/screenshot05.png"/></p>
+<p><img src="IMG/screenshot05.png"/></p>
 <p><u>Figure:</u> Broadcaster source-table.</p>
 
@@ -1380 +1380 @@
 The following figure shows a BNC example setup for pulling a stream via serial port on a Linux operating system.
 </p>
-<p><img src=":/bnchelp/screenshot15.png"/></p>
+<p><img src="IMG/screenshot15.png"/></p>
 <p><u>Figure:</u> BNC setup for pulling a stream via serial port.</p>