Changeset 1235 in ntrip for trunk/BNC/bnchelp.html
- Timestamp:
- Nov 24, 2008, 3:20:06 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r1234 r1235 618 618 <p><a name="messtypes"><h4>3.10. RTCM Scan</h4></p> 619 619 <p> 620 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 Version 3.xstreams 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.620 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. 621 621 </p> 622 622 623 623 <p><a name="messmount"><h4>3.10.1 Mountpoint - optional</h4></p> 624 624 <p> 625 Specify the mountpoint of an RTCM Version 3.x stream to scan it and log 625 Specify the mountpoint of an RTCM Version 3.x stream to scan it and log all contained 626 626 </p> 627 627 <ul> 628 628 <li>numbers of incoming message types</li> 629 629 <li>Antenna Reference Point (ARP) coordinates in ITRF reference system</li> 630 <li>antenna height </li>630 <li>antenna height above ARP</li> 631 631 <li>antenna descriptor.</li> 632 632 </ul> 633 <p>Logged time stamps refer to message reception time and allow to understand repetition rates. Enter 'ALL' if you want to log this information from all configured streams. Beware that the size of the logfile can rapidly increase depending on the number of incoming RTCM Version 3.x streams. 634 </p> 635 <p>This option is primarily meant for testing and evaluation. Use it to figure out what exactly is produced by a specific GNSS receiver's configuration. An empty option field (default) means that you don't want BNC to print the message type numbers carried in RTCM Version 3.x streams. 633 </p> 634 <p> 635 Specify the mountpoint of an RTCM Version 2.x stream and the 'RINEX Observations' directory to scan the stream and log the very first incoming 636 </p> 637 <ul> 638 <li>Antenna Reference Point (ARP) coordinates</li> 639 <li>ECEF corrections to ARP for the L1 Antenna Phase Center (APC)</li> 640 <li>ECEF corrections to ARP for the L2 Antenna Phase Center (APC).</li> 641 </ul> 642 <p> 643 644 <p>Logged time stamps refer to message reception time and - in case of an RTCM Version 3.x stream - allow to understand repetition rates. Enter 'ALL' if you want to log this information from all configured streams. Beware that the size of the logfile can rapidly increase depending on the number of incoming RTCM streams. 645 </p> 646 <p>This option is primarily meant for testing and evaluation. Use it to figure out what exactly is produced by a specific GNSS receiver's configuration. An empty option field (default) means that you don't want BNC to print the message type numbers and antenna information carried in RTCM streams. 636 647 </p> 637 648
Note:
See TracChangeset
for help on using the changeset viewer.