Changeset 2440 in ntrip


Ignore:
Timestamp:
Apr 20, 2010, 12:20:03 PM (7 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/bnchelp.html

    r2439 r2440  
    5050
    5151<p>
    52 Fig. 1 shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link.
    53 </p>
    54 <p><img src=":/bnchelp/screenshot01.png"/></p>
    55 </p>Fig. 1: BNC connected to a GNSS receiver.<p>
    56 
    57 <p>
    58 Fig. 2 shows a flow chart of BNC feeding a real-time GNSS engine. The engine estimates satellite orbit and clock correctors.
    59 </p>
    60 <p><img src=":/bnchelp/screenshot02.png"/></p>
    61 </p>Fig. 2: BNC feeding a real-time GNSS engine.<p>
    62 
    63 
    64 <p>
    6552BNC supports decoding the following GNSS data formats:
    6653</p>
     
    7360BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files.
    7461</p>
     62
     63<p>
     64Fig. 1 shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link. Fig. 2 shows a flow chart of BNC feeding a real-time GNSS engine. The engine then estimates satellite orbit and clock correctors. The 'BKG Ntrip Server' (BNS) is used in this scenariy to encode correctors to RTCMv3.
     65</p>
     66<p><img src=":/bnchelp/screenshot01.png"/></p>
     67<p><u>Fig. 1:</u> BNC connected to a GNSS receiver.</p>
     68
     69<p>
     70</p>
     71<p><img src=":/bnchelp/screenshot02.png"/></p>
     72<p><u>Fig. 2:</u> BNC feeding a real-time GNSS engine.</p>
    7573
    7674<p><a name="resources"><h3>2. Modes &amp; Resources</h3></p>
     
    967965</ul>
    968966</p>
     967<p>
     968Fig. 3. provides the screenshot of an example PPP session with BNC.
     969</p>
     970<p><img src=":/bnchelp/screenshot03.png"/></p>
     971<p><u>Fig. 3:</u> Precise Point Positioning (PPP) with BNC.</p>
    969972
    970973<p>
     
    11591162<p><a name="throughput"><h4>3.13.2 Throughput</h4></p>
    11601163<p>
    1161 The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps).
    1162 </p>
     1164The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 4 shows the bandwidth comsumption of a number of incoming streams.
     1165</p>
     1166
     1167<p>
     1168</p>
     1169<p><img src=":/bnchelp/screenshot08.png"/></p>
     1170<p><u>Fig. 4:</u> Bandwidth consumption of a number of incoming streams.</p>
    11631171
    11641172<p><a name="latency"><h4>3.13.3 Latency</h4></p>
    11651173<p>
    1166 The latency of observations in each incoming stream is shown in the 'Latency' tab in milliseconds or seconds. Streams not carrying observations (i.e. those providing only broadcast ephemeris messages) are not considered here. Note that the calculation of correct latencies requires the clock of the host computer to be properly synchronized.
    1167 </p>
     1174The latency of observations in each incoming stream is shown in the 'Latency' tab in milliseconds or seconds. Streams not carrying observations (i.e. those providing only broadcast ephemeris messages) are not considered here and shown in read color. Note that the calculation of correct latencies requires the clock of the host computer to be properly synchronized. Fig. 5. shows the latency of a number of incoming streams.
     1175</p>
     1176
     1177<p>
     1178</p>
     1179<p><img src=":/bnchelp/screenshot07.png"/></p>
     1180<p><u>Fig. 5:</u> Latency of incoming streams.</p>
    11681181
    11691182<p><a name="ppptab"><h4>3.13.4 PPP Plot</h4></p>
     
    11781191
    11791192<p><a name="streamadd"><h4>3.14.1 Add Stream - Coming from Caster</h4></p>
    1180 <p>
    1181 Button 'Add Stream' &gt; 'Coming from Caster' opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints.
     1193
     1194<p>
     1195Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 6.
     1196</p>
     1197<p><img src=":/bnchelp/screenshot06.png"/></p>
     1198<p><u>Fig. 6:</u> Steam input communication links.</p>
     1199
     1200<p>
     1201Button 'Add Stream' &gt; 'Coming from Caster' then opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints.
    11821202</p>
    11831203
     
    11891209<p><a name="streamtable"><h4>3.14.1.2 Casters Table - optional</h4></p>
    11901210<p>
    1191 It may be that your are not sure about your NTRIP broadcasters host and port number or you are interested in other broadcaster installations operated elsewhere. Hit 'Show' for a table of known broadcasters maintained at <u>www.rtcm-ntrip.org/home</u>. A window opens which allows to select a broadcaster for stream retrieval.
    1192 </p>
     1211It may be that your are not sure about your NTRIP broadcasters host and port number or you are interested in other broadcaster installations operated elsewhere. Hit 'Show' for a table of known broadcasters maintained at <u>www.rtcm-ntrip.org/home</u>. A window opens which allows to select a broadcaster for stream retrieval, see Fig. 7.
     1212</p>
     1213</p>
     1214<p><img src=":/bnchelp/screenshot04.png"/></p>
     1215<p><u>Fig. 7:</u> Casters table.</p>
    11931216
    11941217<p><a name="streamuser"><h4>3.14.1.3 User and Password - mandatory for protected streams</h4></p>
     
    11991222<p><a name="gettable"><h4>3.14.1.4 Get Table</h4></p>
    12001223<p>
    1201 Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary.
     1224Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. Fig. 8 provides an example source-table.
    12021225</p>
    12031226<p>
     
    12071230Hit 'OK' to return to the main window. If you wish you can click on 'Add Stream' and repeat the process again to retrieve streams from different casters.
    12081231</p>
     1232</p>
     1233</p>
     1234<p><img src=":/bnchelp/screenshot05.png"/></p>
     1235<p><u>Fig. 8:</u> Broadcaster source-table.</p>
    12091236
    12101237<p><a name="ntripv"><h4>3.14.1.5 NTRIP Version - mandatory</h4></p>
Note: See TracChangeset for help on using the changeset viewer.