Changeset 6833 in ntrip


Ignore:
Timestamp:
May 12, 2015, 1:52:12 PM (5 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/src/bnchelp.html

    r6832 r6833  
    122122
    123123<p>
    124 BNC supports decoding the following GNSS stream formats and message types:
     124BNC supports the following GNSS stream formats and message types:
    125125</p>
    126126<p>
     
    140140<p><a name="suppGNSS"><h3>1.1 Supported Systems</h3></p>
    141141<p>
    142 BNC is continuously completed in order to support all existing GNSS systems throughout all features of the program. The table below shows in detail which GNSS systems are so far supported by particular applications when using the latest BNC version. The applications named here are
     142BNC is continuously completed in order to support all existing GNSS systems throughout all features of the program. The table below shows in detail which GNSS systems are so far supported by particular applications when using the latest BNC version. Applications fields named here are:
    143143<ul>
    144144<li>Decoding of RTCM or RTNET streams</li>
     
    147147<li>Upload of SSR and ephemeris messages</li>
    148148<li>PPP (Precise Point Positioning)</li>
    149 <li>Combination of SSR or ephemeris messages from various real-time sources</li>
    150 </ul>
    151 The table mentions if the Navigation, Observation, or SSR message implementation in BNC could so far only be based on a 'RTCM Proposal'.
     149<li>Combination/merging of SSR or ephemeris messages from various real-time sources</li>
     150</ul>
     151The table mentions if the message implementation in BNC could so far only be based on a 'RTCM Proposal'.
    152152</p>
    153153<p><u>Table:</u> Status of RTCM Version 3 message implementation in BNC supporting various GNSS systems</p>
     
    156156<table border="1" frame="box" rules="rows" bgcolor="#FFF5EE" style="font-size:13">
    157157
    158 <tr><td><b>Message<br>Type</b></td> <td><b>Description</b></td> <td><b>System</b></td> <td><b>RTCM<br>Proposal&nbsp;</b></td> <td><b>Decoding&nbsp;</b></td> <td><b>&nbsp;RINEX/&nbsp;<br>&nbsp;SP3</b></td> <td><b>Encoding&nbsp;</b></td> <td><b>Upload&nbsp;</b></td> <td><b>&nbsp;PPP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</b></td> <td><b>Combin.&nbsp;</b></td> </tr>
     158<tr><td><b>Message<br>Type #</b></td> <td><b>Description</b></td> <td><b>System</b></td> <td><b>RTCM<br>Proposal&nbsp;</b></td> <td><b>Decoding&nbsp;</b></td> <td><b>&nbsp;RINEX/&nbsp;<br>&nbsp;SP3</b></td> <td><b>Encoding&nbsp;</b></td> <td><b>Upload&nbsp;</b></td> <td><b>&nbsp;PPP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</b></td> <td><b>Combin.&nbsp;</b></td> </tr>
    159159
    160160<tr> <td><b><br>General</b></td> <td></td> <td></td> <td></td> <td></td> <td></td> <td></td> </tr>
     
    235235
    236236<p>
    237 BNC can be used in different contexts with varying data flows. The first of the following figures shows a flow chart of BNC connected to a GNSS receiver providing observations via serial or TCP communication link for the purpose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX files. The third figure shows a flow chart of BNC feeding a real-time GNSS engine which estimates precise orbits and clocks. BNC is used in this scenario to encode correctors to RTCM Version 3 and upload them to an NTRIP Broadcaster. The fourth figure shows BNC combining several Broadcast Correction streams to disseminate the combination product while saving results in SP3 and Clock RINEX files.
     237BNC can be used in different contexts with varying data flows. Typical real-time communication follows the Ntrip protocol over TCP/IP (probably via SSL), RTSP/RTP or UDP, plain TCP/IP protocol, or serial communication links. Stream contents could be observations, ephemeris, satellite orbit/clock products or NMEA sentences.
     238</p>
     239<p>
     240 The first of the following figures shows a flow chart of BNC connected to a GNSS receiver providing observations via serial or TCP communication link for the purpose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX files. The third figure shows a flow chart of BNC feeding a real-time GNSS engine which estimates precise orbits and clocks. BNC is used in this scenario to encode correctors to RTCM Version 3 and upload them to an NTRIP Broadcaster. The fourth figure shows BNC combining several Broadcast Correction streams to disseminate the combination product while saving results in SP3 and Clock RINEX files.
    238241</p>
    239242<p><img src="IMG/screenshot10.png"/></p>
Note: See TracChangeset for help on using the changeset viewer.