Changeset 2445 in ntrip for trunk


Ignore:
Timestamp:
Apr 21, 2010, 9:40:28 AM (15 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/bnchelp.html

    r2444 r2445  
    6464Fig. 1 shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link for the pupose of Precise Point Positioning. Fig. 2 shows the conversion of RTCM streams to RINEX batches. Fig. 3 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 scenario to encode correctors to RTCMv3.
    6565</p>
    66 <p><img src=":/bnchelp/screenshot10.png"/></p>
     66<p><img src="IMG/screenshot10.png"/></p>
    6767<p><u>Fig. 1:</u> BNC connected to a GNSS receiver for Precise Point Positioning.</p>
    6868
    6969<p>
    7070</p>
    71 <p><img src=":/bnchelp/screenshot01.png"/></p>
     71<p><img src="IMG/screenshot01.png"/></p>
    7272<p><u>Fig. 2:</u> BNC converting RTCM streams to RINEX batches.</p>
    7373
    7474<p>
    7575</p>
    76 <p><img src=":/bnchelp/screenshot02.png"/></p>
     76<p><img src="IMG/screenshot02.png"/></p>
    7777<p><u>Fig. 3:</u> BNC feeding a real-time GNSS engine.</p>
    7878
     
    9696This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar, see Fig. 4.
    9797</p>
    98 <p><img src=":/bnchelp/screenshot09.png"/></p>
     98<p><img src="IMG/screenshot09.png"/></p>
    9999<p><u>Fig. 4:</u> Sections on BNC's main window.</p>
    100100
     
    978978Fig. 5. provides the screenshot of an example PPP session with BNC.
    979979</p>
    980 <p><img src=":/bnchelp/screenshot03.png"/></p>
     980<p><img src="IMG/screenshot03.png"/></p>
    981981<p><u>Fig. 5:</u> Precise Point Positioning (PPP) with BNC.</p>
    982982
     
    11721172<p><a name="throughput"><h4>3.13.2 Throughput</h4></p>
    11731173<p>
    1174 The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 6 shows the bandwidth comsumption of a number of incoming streams.
    1175 </p>
    1176 
    1177 <p>
    1178 </p>
    1179 <p><img src=":/bnchelp/screenshot08.png"/></p>
    1180 <p><u>Fig. 6:</u> Bandwidth consumption of a number of incoming streams.</p>
     1174The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 6 shows the bandwidth comsumption of incoming streams.
     1175</p>
     1176
     1177<p>
     1178</p>
     1179<p><img src="IMG/screenshot08.png"/></p>
     1180<p><u>Fig. 6:</u> Bandwidth consumption of incoming streams.</p>
    11811181
    11821182<p><a name="latency"><h4>3.13.3 Latency</h4></p>
    11831183<p>
    1184 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. 7. shows the latency of a number of incoming streams.
    1185 </p>
    1186 
    1187 <p>
    1188 </p>
    1189 <p><img src=":/bnchelp/screenshot07.png"/></p>
     1184The 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. 7. shows the latency of incoming streams.
     1185</p>
     1186
     1187<p>
     1188</p>
     1189<p><img src="IMG/screenshot07.png"/></p>
    11901190<p><u>Fig. 7:</u> Latency of incoming streams.</p>
    11911191
     
    12051205Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 8.
    12061206</p>
    1207 <p><img src=":/bnchelp/screenshot06.png"/></p>
     1207<p><img src="IMG/screenshot06.png"/></p>
    12081208<p><u>Fig. 8:</u> Steam input communication links.</p>
    12091209
     
    12221222</p>
    12231223</p>
    1224 <p><img src=":/bnchelp/screenshot04.png"/></p>
     1224<p><img src="IMG/screenshot04.png"/></p>
    12251225<p><u>Fig. 9:</u> Casters table.</p>
    12261226
     
    12421242</p>
    12431243</p>
    1244 <p><img src=":/bnchelp/screenshot05.png"/></p>
     1244<p><img src="IMG/screenshot05.png"/></p>
    12451245<p><u>Fig. 10:</u> Broadcaster source-table.</p>
    12461246
Note: See TracChangeset for help on using the changeset viewer.