Changeset 2475 in ntrip


Ignore:
Timestamp:
May 7, 2010, 4:46:19 PM (8 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/bnchelp.html

    r2473 r2475  
    6464The first of the following figures shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link for the pupose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX batches. The third figure 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="IMG/screenshot10.png"/></p>
     66<p><img src=":bnchelp/screenshot10.png"/></p>
    6767<p><u>Figure:</u> Flowchart, BNC connected to a GNSS receiver for Precise Point Positioning.</p>
    6868
    6969<p>
    7070</p>
    71 <p><img src="IMG/screenshot01.png"/></p>
     71<p><img src=":bnchelp/screenshot01.png"/></p>
    7272<p><u>Figure:</u> Flowchart, BNC converting RTCM streams to RINEX batches.</p>
    7373
    7474<p>
    7575</p>
    76 <p><img src="IMG/screenshot02.png"/></p>
     76<p><img src=":bnchelp/screenshot02.png"/></p>
    7777<p><u>Figure:</u> Flowchart, BNC feeding a real-time GNSS engine.</p>
    7878
     
    9595The main window of BNC shows a top menu bar section, a sections for tabs to set processing options, a 'Streams' section and a section for 'Log' tabs, and a bottom menu bar section, see figure below.
    9696</p>
    97 <p><img src="IMG/screenshot09.png"/></p>
     97<p><img src=":bnchelp/screenshot09.png"/></p>
    9898<p><u>Figure:</u> Sections on BNC's main window.</p>
    9999
     
    300300The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming in from various NTRIP broadcasters as well as via a plain UDP and a serial communication link. Decoder 'ZERO' has been selected for one stream to not convert its contents but save it in original format.
    301301</p>
    302 <p><img src="IMG/screenshot16.png"/></p>
     302<p><img src=":bnchelp/screenshot16.png"/></p>
    303303<p><u>Figure:</u> BNC translating incoming streams to 15 min RINEX Version 3 files.</p>
    304304
     
    759759The following figure shows the screenshot of a BNC configuration where a number if streams is pulled from different NTRIP broadcasters to feed a GNSS engine via IP port output.
    760760</p>
    761 <p><img src="IMG/screenshot12.png"/></p>
     761<p><img src=":bnchelp/screenshot12.png"/></p>
    762762<p><u>Figure:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p>
    763763
     
    798798</p>
    799799</p>
    800 <p><img src="IMG/screenshot11.png"/></p>
     800<p><img src=":bnchelp/screenshot11.png"/></p>
    801801<p><u>Figure:</u> BNC pulling a VRS stream to feed a serial connected rover.</p>
    802802
     
    946946The following figure shows RTCM message numbers contained in stream 'CONZ0' and the message latencies recorded every 10 seconds.
    947947</p>
    948 <p><img src="IMG/screenshot14.png"/></p>
     948<p><img src=":bnchelp/screenshot14.png"/></p>
    949949<p><u>Figure:</u> RTCM message numbers and latencies.</p>
    950950
     
    10201020The following figure provides the screenshot of an example PPP session with BNC.
    10211021</p>
    1022 <p><img src="IMG/screenshot03.png"/></p>
     1022<p><img src=":bnchelp/screenshot03.png"/></p>
    10231023<p><u>Figure:</u> Precise Point Positioning (PPP) with BNC.</p>
    10241024
     
    12321232<p>
    12331233</p>
    1234 <p><img src="IMG/screenshot08.png"/></p>
     1234<p><img src=":bnchelp/screenshot08.png"/></p>
    12351235<p><u>Figure:</u> Bandwidth consumption of incoming streams.</p>
    12361236
     
    12421242<p>
    12431243</p>
    1244 <p><img src="IMG/screenshot07.png"/></p>
     1244<p><img src=":bnchelp/screenshot07.png"/></p>
    12451245<p><u>Figure:</u> Latency of incoming streams.</p>
    12461246
     
    12521252<p>
    12531253</p>
    1254 <p><img src="IMG/screenshot13.png"/></p>
     1254<p><img src=":bnchelp/screenshot13.png"/></p>
    12551255<p><u>Figure:</u> Time series plot of PPP session.</p>
    12561256
     
    12601260</p>
    12611261
    1262 <p><img src="IMG/screenshot06.png"/></p>
     1262<p><img src=":bnchelp/screenshot06.png"/></p>
    12631263<p><u>Figure:</u> Steam input communication links.</p>
    12641264
     
    12791279</p>
    12801280</p>
    1281 <p><img src="IMG/screenshot04.png"/></p>
     1281<p><img src=":bnchelp/screenshot04.png"/></p>
     1282
    12821283<p><u>Figure:</u> Casters table.</p>
    12831284
     
    12991300</p>
    13001301</p>
    1301 <p><img src="IMG/screenshot05.png"/></p>
     1302<p><img src=":bnchelp/screenshot05.png"/></p>
    13021303<p><u>Figure:</u> Broadcaster source-table.</p>
    13031304
     
    13941395The following figure shows a BNC example setup for pulling a stream via serial port on a Linux operating system.
    13951396</p>
    1396 <p><img src="IMG/screenshot15.png"/></p>
     1397<p><img src=":bnchelp/screenshot15.png"/></p>
    13971398<p><u>Figure:</u> BNC setup for pulling a stream via serial port.</p>
    13981399
Note: See TracChangeset for help on using the changeset viewer.