-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.
@@ -718,5 +718,5 @@-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.
@@ -737,7 +737,10 @@ In case an observation is not available, its value is set to zero '0.000'. - --The following is an output examples for GPS, GLONASS and Galileo satellites and a geostationary payload signal: +
Note on SlipCounts:
+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.
+
+The following is an output examples for GPS, GLONASS and Galileo observations and observations obtained from a geostationary payload signal:
...