Changeset 3121 in ntrip for trunk

Timestamp:

Mar 23, 2011, 12:26:08 PM (14 years ago)

Author:

weber

Message:

Introduced '0' as option for 'Wait for full Epoch'

File:

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

trunk/BNC/bnchelp.html

@@ -747 +747 @@
 When feeding a real-time GNSS network engine waiting epoch by epoch for synchronized Broadcast Corrections, BNC drops (only concerning IP port output) whatever is received later than 'Wait for full epoch' seconds. A value of 2 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming Broadcast Corrections stream and the delay acceptable by your application. A message such as "COCK1: Correction overaged by 5 sec" shows up in BNC's logfile if 'Wait for full epoch' is exceeded.
 </p>
+<p>
+Specifying a value of '0' means that BNC immediately outputs all incoming Broadcast Epemeris Corrections and does not drop any of them for latency reasions.
+</p>
 
 <p><a name="syncout"><h4>3.7. Feed Engine</h4></p>