Changeset 7473 in ntrip

Timestamp:

Sep 28, 2015, 11:47:49 AM (9 years ago)

Author:

weber

Message:

Documentation completed

File:

• trunk/BNC/src/bnchelp.html (modified) (4 diffs)

trunk/BNC/src/bnchelp.html

@@ -994 +994 @@
 </p>
 
+<p>
+Note further that BNC will ignore incorrect or outdated Broadcast Ephemeris data when necessary, leaving a note 'WRONG EPHEMERIS' or 'OUTDATED EPHEMERIS' in the logfile.
+</p>
+
 <p><a name="ephdir"><h4>3.5.1 Directory - optional</h4></p>
 <p>
@@ -2219 +2223 @@
 <li>May require pulling a stream carrying Broadcast Ephemeris available as RTCM Version 3 message types 1019, 1020, 1043, 1044, 1045, 1046 and 63 (tentative). This becomes a must only when the stream coming from the receiver does not contain Broadcast Ephemeris or provides them only at very low repetition rate. Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>. Stream 'RTCM3EPH' on caster 'products.igs-ip.net:2101' is an example.</li>
 </ul>
+Note that broadcast ephemeris parameters pass through a plausibility check in BNC which allows to ignore incorrect or outdated ephemeris data when necessary, leaving a note 'WRONG EPHEMERIS' or 'OUTDATED EPHEMERIS' in the logfile.
 </p>
 
@@ -2893 +2898 @@
 </p>
 <p>
-Note that the combination process requires real-time access to Broadcast Ephemeris. So, in addition to the orbit and clock correction streams BNC must pull a stream carrying Broadcast Ephemeris in the form of RTCM Version 3 messages. Stream 'RTCM3EPH' on caster <u>products.igs-ip.net</u> is an example for that.
+Note that the combination process requires real-time access to Broadcast Ephemeris. So, in addition to the orbit and clock correction streams BNC must pull a stream carrying Broadcast Ephemeris in the form of RTCM Version 3 messages. Stream 'RTCM3EPH' on caster <u>products.igs-ip.net</u> is an example for that. Note further that BNC will ignore incorrect or outdated Broadcast Ephemeris data when necessary, leaving a note 'WRONG EPHEMERIS' or 'OUTDATED EPHEMERIS' in the logfile.
 </p>
 
@@ -3379 +3384 @@
 <p><a name="upeph"><h4>3.16. Upload Ephemeris</h4></p>
 <p>
-BNC can upload a stream carrying Broadcast Ephemeris in RTCM Version 3 format to an Ntrip Broadcaster.
+BNC can generate a stream carrying only Broadcast Ephemeris in RTCM Version 3 format and upload it to an Ntrip Broadcaster.
+</p>
+
+<p>
+Note that broadcast ephemeris received in real-time have a system specific period of validity in BNC which is defined in accordance with the update rates of the navigation messages.
+<ul>
+<li>GPS ephemeris will be interpreted as outdated and ignored when older than 4 hours.</li>
+<li>GLONASS ephemeris will be interpreted as outdated and ignored when older than 1 hour.</li>
+<li>Galileo ephemeris will be interpreted as outdated and ignored when older than 4 hours.</li>
+<li>BDS ephemeris will be interpreted as outdated and ignored when older than 6 hours.</li>
+<li>SBAS ephemeris will be interpreted as outdated and ignored when older than 10 minutes.</li>
+<li>QZSS ephemeris will be interpreted as outdated and ignored when older than 30 minutes.</li>
+</ul>
+A note 'OUTDATED EPHEMERIS' will be given in the logfile and the data will be disregarded when necessary. 
+</p>
+<p>
+Furthermore, received broadcast ephemeris parameters pass through a plausibility check in BNC which allows to ignore incorrect ephemeris data when necessary, leaving a note 'WRONG EPHEMERIS' in the logfile.
 </p>