Changeset 2230 in ntrip for trunk/BNC

Timestamp:

Jan 12, 2010, 10:14:01 AM (15 years ago)

Author:

weber

Message:

* empty log message *

File:

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

trunk/BNC/bnchelp.html

@@ -61 +61 @@
 <p><a name="resources"><h3>2. Modes &amp; Resources</h3></p>
 <p>
-Although BNC is a real-time tool to be operated in online mode, it can be run offline for post processing of data made availabe from a file. Furthermore, apart from its regular window mode, BNC can be run as a batch/background job in a 'no window' mode using processing options from previously saved configuration.
+Although BNC is a real-time tool to be operated in online mode, it can be run offline for post processing of data made availabe from a single file. Furthermore, apart from its regular window mode, BNC can be run as a batch/background job in a 'no window' mode using processing options from a previously saved configuration.
 </p>
 <p>
@@ -75 +75 @@
 <p><a name="options"><h3>3. Options</h3></p>
 <p>
-This section describes BNC's top menu bar, its processing options and bottom menu bar.
-</p>
-<p>
-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 tabs to select a combination of input, processing and output options before you start the program ('Start'). Records of BNC's activities are shown in the 'Log' tab and bandwidth consumtion per stream in the 'Throughput' tab on the bottom of the main window.
+This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar.
+</p>
+<p>
+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 tabs to select a combination of input, processing and output options before you start the program ('Start'). Records of BNC's activities are shown in the 'Log' tab. The bandwidth consumtion per stream, the latency of incoming observations and PPP time series for coordinate components are shown in the 'Throughput', 'Latency' and 'PPP' tabs of the main window.
 </p>
 <p>
@@ -380 +380 @@
 </ul> 
 
+<p>
+Note that streams dedicated to carry Broadcst Ephemeris messages in RTCM v3 format in high repetition rates are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>.
+</p>
+
 <p><a name="ephdir"><h4>3.5.1 Directory - optional</h4></p>
 <p>
@@ -939 +943 @@
 <p><a name="pppclient"><h4>3.11. PPP Client</h4></p>
 <p>
-BNC can derive coordinates for a rover position following the Precise Point Positioning (PPP) approach. It uses either code or phase data in ionosphere free linear combinations P3 or L3. Besides pulling a stream of observations from a receiver, this also requires pulling a stream of 
-<ul>
-<li>satellite orbit and clock corrections to Broadcast Ephemeris in the form of 'State Space Representation' (SSR) messages as proposed by RTCM (i.e. premature message type 1060). Note that for BNC these correctors need to be referred to the satellite's Antenna Phase Center (APC). Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/orbits</u>. Stream www.igs-ip.net:2101/CLK10 can be understood as an example.</li>
-<li>Broadcast Ephemeris available as RTCM Version 3 message types 1019 and 1020. This is a must when the stream coming from the receiver does not contain Broadcast Ephemeris or provides them only at low repetition rate. Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>. Stream www.igs-ip.net:2101/RTCM3EPH can be understood as an example.</li>
+BNC can derive coordinates for a rover position following the Precise Point Positioning (PPP) approach. It uses either code or code plus phase data in ionosphere free linear combinations P3 or L3. Besides pulling a stream of observations from a receiver, this also requires pulling in addition
+<ul>
+<li>a stream carrying satellite orbit and clock corrections to Broadcast Ephemeris in the form of 'State Space Representation' (SSR) messages as proposed by RTCM (i.e. premature message type 1060). Note that for BNC these correctors need to be referred to the satellite's Antenna Phase Center (APC). Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/orbits</u>. Stream www.igs-ip.net:2101/CLK10 is an example.</li>
+<li>a stream carrying Broadcast Ephemeris available as RTCM Version 3 message types 1019 and 1020. This is a must when the stream coming from the receiver does not contain Broadcast Ephemeris or provides them only at low repetition rate. Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>. Stream www.igs-ip.net:2101/RTCM3EPH is an example.</li>
 </ul>
 </p>
@@ -1106 +1110 @@
 <p><a name="ppptab"><h4>3.13.4 PPP</h4></p>
 <p>
-Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in the 'PPP' tab. Values are either referred to reference coordinates (if specified) or referred to the first estimated coordinate components. The time as given in format [hh:mm] refers to GPS Time. The sliding PPP time series window covers a period of 5 minutes. Note that it may take up to 30 seconds or more till the first PPP solutions becomes available.
+Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in the 'PPP' tab. Values are either referred to reference coordinates (if specified) or referred to the first estimated set of coordinate components. The time as given in format [hh:mm] refers to GPS Time. The sliding PPP time series window covers a period of 5 minutes. Note that it may take up to 30 seconds or more till the first PPP solutions becomes available.
 </p>