Changeset 2443 in ntrip for trunk/BNC/bnchelp.html


Ignore:
Timestamp:
Apr 20, 2010, 3:35:09 PM (15 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r2442 r2443  
    8888<p><a name="options"><h3>3. Options</h3></p>
    8989<p>
    90 This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar.
     90This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar, see Fig. 3.
     91</p>
     92<p><img src=":/bnchelp/screenshot09.png"/></p>
     93<p><u>Fig. 3:</u> Sections on BNC's main window.</p>
     94
    9195</p>
    9296<p>
    … …  
    966970</p>
    967971<p>
    968 Fig. 3. provides the screenshot of an example PPP session with BNC.
     972Fig. 4. provides the screenshot of an example PPP session with BNC.
    969973</p>
    970974<p><img src=":/bnchelp/screenshot03.png"/></p>
    971 <p><u>Fig. 3:</u> Precise Point Positioning (PPP) with BNC.</p>
     975<p><u>Fig. 4:</u> Precise Point Positioning (PPP) with BNC.</p>
    972976
    973977<p>
    … …  
    11621166<p><a name="throughput"><h4>3.13.2 Throughput</h4></p>
    11631167<p>
    1164 The 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.
     1168The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 5 shows the bandwidth comsumption of a number of incoming streams.
    11651169</p>
    11661170
    … …  
    11681172</p>
    11691173<p><img src=":/bnchelp/screenshot08.png"/></p>
    1170 <p><u>Fig. 4:</u> Bandwidth consumption of a number of incoming streams.</p>
     1174<p><u>Fig. 5:</u> Bandwidth consumption of a number of incoming streams.</p>
    11711175
    11721176<p><a name="latency"><h4>3.13.3 Latency</h4></p>
    11731177<p>
    1174 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 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.
     1178The 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. 6. shows the latency of a number of incoming streams.
    11751179</p>
    11761180
    … …  
    11781182</p>
    11791183<p><img src=":/bnchelp/screenshot07.png"/></p>
    1180 <p><u>Fig. 5:</u> Latency of incoming streams.</p>
     1184<p><u>Fig. 6:</u> Latency of incoming streams.</p>
    11811185
    11821186<p><a name="ppptab"><h4>3.13.4 PPP Plot</h4></p>
    … …  
    11931197
    11941198<p>
    1195 Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 6.
     1199Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 7.
    11961200</p>
    11971201<p><img src=":/bnchelp/screenshot06.png"/></p>
    1198 <p><u>Fig. 6:</u> Steam input communication links.</p>
     1202<p><u>Fig. 7:</u> Steam input communication links.</p>
    11991203
    12001204<p>
    … …  
    12091213<p><a name="streamtable"><h4>3.14.1.2 Casters Table - optional</h4></p>
    12101214<p>
    1211 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, see Fig. 7.
     1215It 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. 8.
    12121216</p>
    12131217</p>
    12141218<p><img src=":/bnchelp/screenshot04.png"/></p>
    1215 <p><u>Fig. 7:</u> Casters table.</p>
     1219<p><u>Fig. 8:</u> Casters table.</p>
    12161220
    12171221<p><a name="streamuser"><h4>3.14.1.3 User and Password - mandatory for protected streams</h4></p>
    … …  
    12221226<p><a name="gettable"><h4>3.14.1.4 Get Table</h4></p>
    12231227<p>
    1224 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. Fig. 8 provides an example source-table.
     1228Use 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. 9 provides an example source-table.
    12251229</p>
    12261230<p>
    … …  
    12331237</p>
    12341238<p><img src=":/bnchelp/screenshot05.png"/></p>
    1235 <p><u>Fig. 8:</u> Broadcaster source-table.</p>
     1239<p><u>Fig. 9:</u> Broadcaster source-table.</p>
    12361240
    12371241<p><a name="ntripv"><h4>3.14.1.5 NTRIP Version - mandatory</h4></p>
Note: See TracChangeset for help on using the changeset viewer.