Changeset 2096 in ntrip

Timestamp:

Dec 7, 2009, 12:25:33 PM (15 years ago)

Author:

weber

Message:

* empty log message *

File:

• trunk/BNC/bnchelp.html (modified) (1 diff)

trunk/BNC/bnchelp.html

@@ -931 +931 @@
 <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
+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
 <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 refer to the satellite's Antenna Phase Center (APC).</li>
 <li>Broadcast Ephemeris available as RTCM Version 3 message types 1019 and 1020. Note that a stream dedicated to providing these messages is 'RTCM3EPH" on NTRIP broadcaster www.igs-ip.net.</li>
 </ul>
+</p>
+
+<p>
+PPP results are saved in BNC's logfile. Depending on processing options, the following values are recorded every second (example):
+</p>
+<pre>
+09-12-07 11:01:50     PPP ZIM20 11:02:03.0 8    4331302.284      567537.941     4633134.936    -5.669    -0.155
+</pre>
+<p>
+The 'PPP' string in that is followed by the selected mounpoint, a PPP time stamp, the number of processed satellites, XYZ coordinates in [m], clock correction in [m], and the estimated troposphere correction in [m].
 </p>