Changeset 2842 in ntrip

Timestamp:

Dec 28, 2010, 7:54:31 PM (14 years ago)

Author:

weber

Message:

SlipCount explained

File:

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

trunk/BNC/bnchelp.html

@@ -474 +474 @@
 </p>
 <p>
-The source code for BNC comes with an example perl script 'test_bnc_eph.pl' that allows you to read BNC's ASCII ephemeris output from the IP port.
+The source code for BNC comes with an example perl script 'test_tcpip_client.pl' that allows you to read BNC's ASCII ephemeris output from the IP port.
 </p>
 
@@ -718 +718 @@
 </p>
 <p>
-The source code for BNC comes with an example perl script 'test_bnc_eph.pl' that allows you to read BNC's Broadcast Corrections from the IP port.
+The source code for BNC comes with an example perl script 'test_tcpip_client.pl' that allows you to read BNC's Broadcast Corrections from the IP port.
 </p>
 
@@ -737 +737 @@
 In case an observation is not available, its value is set to zero '0.000'.
 </p>
-
-<p>
-The following is an output examples for GPS, GLONASS and Galileo satellites and a geostationary payload signal:
+<p>Note on SlipCounts:<br>
+It is the current understanding of BNC's authors that different slip counts could be referred to different phase measurements (i.e. L1C and L1P). The 'loss-of-lock' flags in RINEX are an example for making such kind of information available per phase measurement. However, it looks like we do have only one slip count in RTCM Version 3 for all phase measurements. As it could be that a receiver generates different slip counts for different phase measurements, we forward one slip count per phase measurement to the real-time GNSS network engine.
+</p>
+
+<p>
+The following is an output examples for GPS, GLONASS and Galileo observations and observations obtained from a geostationary payload signal:
 <pre>
 ...