Changeset 1307 in ntrip for trunk/BNC/bnchelp.html
- Timestamp:
- Dec 19, 2008, 12:41:07 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
TabularUnified trunk/BNC/bnchelp.html ¶
r1302 r1307 104 104 3.8.3. <a href=#corrport>Port</a><br> 105 105 3.8.4. <a href=#corrwait>Wait for Full Epoch</a><br> 106 3.9. <a href=#advnote> Monitor</a><br>106 3.9. <a href=#advnote>Outages</a><br> 107 107 3.9.1. <a href=#obsrate>Observation Rate</a><br> 108 108 3.9.2. <a href=#advfail>Failure Threshold</a><br> … … 110 110 3.9.4. <a href=#pause>Pause</a><br> 111 111 3.9.5. <a href=#advscript>Script</a><br> 112 3.9.6. <a href=#perflog>Performance Log</a><br> 113 3.10. <a href=#messtypes>RTCM Scan</a><br> 114 3.10.1. <a href=#messmount>Mountpoint</a><br> 112 3.10. <a href=#misc>Miscellaneous</a><br> 113 3.10.1. <a href=#mountpoint>Mountpoint</a><br> 114 3.10.2. <a href=#perflog>Log Latency</a><br> 115 3.10.3. <a href=#scanrtcm>Scan RTCM</a><br> 115 116 3.11. <a href=#mountpoints>Mountpoints</a><br> 116 117 3.11.1. <a href=#mountadd>Add Mountpoints</a><br> … … 519 520 </p> 520 521 521 <p><a name="advnote"><h4>3.9. Monitor</h4></p>522 <p><a name="advnote"><h4>3.9. Outages</h4></p> 522 523 523 524 <p> … … 592 593 </p> 593 594 594 <p><a name="perflog"><h4>3.9.6 Performance Log - optional </h4></p> 595 <p><a name="misc"><h4>3.10. Miscellaneous</h4></p> 596 <p> 597 This section describes a number of miscellaneous options which can be applied per stream (mountpoint) or for all configured streams. 598 </p> 599 600 <p><a name="mountpoint"><h4>3.10.1 Mountpoint - optional </h4></p> 601 <p> 602 Specify a mountpoint to apply one or several of the 'Miscellaneous' options to the corresponding stream. Enter 'ALL' if you want to apply these options to all configured streams. An empty option field (default) means that you don't want BNC to apply any of these options. 603 </p> 604 605 <p><a name="perflog"><h4>3.10.2 Log Latency - optional </h4></p> 606 <p> 607 BNC can average latencies per stream over a certain period of GPS time, the 'Performance log' interval. Mean latencies are calculated from the individual latencies of at most one (first incoming) observation or correction to Broadcast Ephemeris per second. Note that computing correct latencies requires the clock of the host computer to be properly synchronized. 608 </p> 595 609 <p> 596 610 <u>Latency:</u> Latency is defined in BNC by the following equation: … … 604 618 </pre> 605 619 <p> 606 BNC can average the latencies per stream over a certain period of GPS time, the 'Performance log' interval. Mean latencies are calculated from the individual latencies of at most one (first incoming) observation or correction to Broadcast Ephemeris per second. Note that computing correct latencies requires the clock of the host computer to be properly synchronized.607 </p>608 <p>609 620 <u>Statistics:</u> BNC counts the number of GPS seconds covered by at least one observation. It also estimates an observation rate (independent from the a priory specified 'Observation rate') from all observations received throughout the first full 'Performance log' interval. Based on this rate, BNC estimates the number of data gaps when appearing in subsequent intervals. 610 621 </p> … … 619 630 </p> 620 631 621 <p><a name="messtypes"><h4>3.10. RTCM Scan</h4></p> 632 633 <p><a name="scanrtcm"><h4>3.10.3 Scan RTCM - optional</h4></p> 622 634 <p> 623 635 When configuring a GNSS receiver for RTCM stream generation, the setup interface may not provide details about RTCM message types. As reliable information concerning stream contents should be available i.e. for NTRIP broadcaster operators to maintain the broadcaster's sourcetable, BNC allows to scan RTCM streams for incoming message types and printout some of the contained meta-data. The idea for this option arose from 'InspectRTCM', a comprehensive stream analyzing tool written by D. Stoecker. 624 636 </p> 625 626 <p><a name="messmount"><h4>3.10.1 Mountpoint - optional</h4></p> 627 <p> 628 Specify the mountpoint of an RTCM Version 2.x or 3.x stream to scan it and log all contained 637 <p> 638 Tick 'Scan RTCM' to scan RTCM Version 2.x or 3.x streams and log all contained 629 639 </p> 630 640 <ul>
Note:
See TracChangeset
for help on using the changeset viewer.