Changeset 2447 in ntrip for trunk


Ignore:
Timestamp:
Apr 21, 2010, 12:07:32 PM (15 years ago)
Author:
weber
Message:

* empty log message *

Location:
trunk/BNC
Files:
3 added
5 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnc.qrc

    r2444 r2447  
    1717    <file alias="screenshot09.png">IMG/screenshot09.png</file>
    1818    <file alias="screenshot10.png">IMG/screenshot10.png</file>
     19    <file alias="screenshot11.png">IMG/screenshot11.png</file>
     20    <file alias="screenshot12.png">IMG/screenshot12.png</file>
     21    <file alias="screenshot13.png">IMG/screenshot13.png</file>
    1922</qresource>
    2023</RCC>

  • trunk/BNC/bnchelp.html

    r2446 r2447  
    6262
    6363<p>
    64 Fig. 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.
     64The 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>
    6666<p><img src="IMG/screenshot10.png"/></p>
    67 <p><u>Fig. 1:</u> BNC connected to a GNSS receiver for Precise Point Positioning.</p>
     67<p><u>Figure:</u> BNC connected to a GNSS receiver for Precise Point Positioning.</p>
    6868
    6969<p>
    7070</p>
    7171<p><img src="IMG/screenshot01.png"/></p>
    72 <p><u>Fig. 2:</u> BNC converting RTCM streams to RINEX batches.</p>
     72<p><u>Figure:</u> BNC converting RTCM streams to RINEX batches.</p>
    7373
    7474<p>
    7575</p>
    7676<p><img src="IMG/screenshot02.png"/></p>
    77 <p><u>Fig. 3:</u> BNC feeding a real-time GNSS engine.</p>
     77<p><u>Figuge:</u> BNC feeding a real-time GNSS engine.</p>
    7878
    7979
    … …  
    9494<p><a name="options"><h3>3. Options</h3></p>
    9595<p>
    96 This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar, see Fig. 4.
     96This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar, see figure below.
    9797</p>
    9898<p><img src="IMG/screenshot09.png"/></p>
    99 <p><u>Fig. 4:</u> Sections on BNC's main window.</p>
     99<p><u>Figure:</u> Sections on BNC's main window.</p>
    100100
    101101</p>
    … …  
    729729</p>
    730730
     731</p>
     732The 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.
     733</p>
     734<p><img src="IMG/screenshot12.png"/></p>
     735<p><u>Figure:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p>
     736
    731737<p><a name="syncport"><h4>3.7.1 Port - optional</h4></p>
    732738<p>
    … …  
    763769<p><a name="serial"><h4>3.8. Serial Output</h4></p>
    764770<p>
    765 You may use BNC to feed a serial connected device like an GNSS receiver. For that one of the incoming streams can be forwarded to a serial port.
    766 </p>
     771You may use BNC to feed a serial connected device like an GNSS receiver. For that one of the incoming streams can be forwarded to a serial port. The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an NTRIP broadcaster to feed a serial connected rover.
     772</p>
     773</p>
     774<p><img src="IMG/screenshot11.png"/></p>
     775<p><u>Figure:</u> BNC pulling a VRS to feed a serial connected rover.</p>
    767776
    768777<p><a name="sermount"><h4>3.8.1 Mountpoint - optional</h4></p>
    … …  
    976985</p>
    977986<p>
    978 Fig. 5. provides the screenshot of an example PPP session with BNC.
     987The following figure provides the screenshot of an example PPP session with BNC.
    979988</p>
    980989<p><img src="IMG/screenshot03.png"/></p>
    981 <p><u>Fig. 5:</u> Precise Point Positioning (PPP) with BNC.</p>
     990<p><u>Figure:</u> Precise Point Positioning (PPP) with BNC.</p>
    982991
    983992<p>
    … …  
    11721181<p><a name="throughput"><h4>3.13.2 Throughput</h4></p>
    11731182<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 incoming streams.
     1183The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). The following figure shows the bandwidth comsumption of incoming streams.
    11751184</p>
    11761185
    … …  
    11781187</p>
    11791188<p><img src="IMG/screenshot08.png"/></p>
    1180 <p><u>Fig. 6:</u> Bandwidth consumption of incoming streams.</p>
     1189<p><u>Figure:</u> Bandwidth consumption of incoming streams.</p>
    11811190
    11821191<p><a name="latency"><h4>3.13.3 Latency</h4></p>
    11831192<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 incoming streams.
     1193The 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) or having an outage 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. The next figure shows the latency of incoming streams.
    11851194</p>
    11861195
    … …  
    11881197</p>
    11891198<p><img src="IMG/screenshot07.png"/></p>
    1190 <p><u>Fig. 7:</u> Latency of incoming streams.</p>
     1199<p><u>Figure:</u> Latency of incoming streams.</p>
    11911200
    11921201<p><a name="ppptab"><h4>3.13.4 PPP Plot</h4></p>
    11931202<p>
    1194 Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in the 'PPP Plot' tab when a 'Plot origin' option is defined. Values are either referred to reference coordinates (if specified) or referred to the first estimated set of coordinate components. The time as given in format [hh:mm] refers to GPS Time. The sliding PPP time series window covers a period of 5 minutes. Note that it may take up to 30 seconds or more till the first PPP solutions becomes available.
    1195 </p>
     1203Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in the 'PPP Plot' tab when a 'Plot origin' option is defined. Values are either referred to reference coordinates (if specified) or referred to the first estimated set of coordinate components. The time as given in format [hh:mm] refers to GPS Time. The sliding PPP time series window covers a period of 5 minutes. Note that it may take up to 30 seconds or more till the first PPP solutions becomes available. The following figure shows the screenshot of a PPP time series plot of North, East and Up coordiate components.
     1204</p>
     1205
     1206<p>
     1207</p>
     1208<p><img src="IMG/screenshot13.png"/></p>
     1209<p><u>Figure:</u> Time series plot of PPP session.</p>
    11961210
    11971211<p><a name="bottom"><h4>3.14. Bottom Menu Bar</h4></p>
    … …  
    12031217
    12041218<p>
    1205 Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 8.
     1219Button 'Add Stream' opens a window that allows user to select one of several input communication links, see figure below.
    12061220</p>
    12071221<p><img src="IMG/screenshot06.png"/></p>
    1208 <p><u>Fig. 8:</u> Steam input communication links.</p>
     1222<p><u>Figure:</u> Steam input communication links.</p>
    12091223
    12101224<p>
    … …  
    12191233<p><a name="streamtable"><h4>3.14.1.2 Casters Table - optional</h4></p>
    12201234<p>
    1221 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. 9.
     1235It 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 figure below.
    12221236</p>
    12231237</p>
    12241238<p><img src="IMG/screenshot04.png"/></p>
    1225 <p><u>Fig. 9:</u> Casters table.</p>
     1239<p><u>Figure:</u> Casters table.</p>
    12261240
    12271241<p><a name="streamuser"><h4>3.14.1.3 User and Password - mandatory for protected streams</h4></p>
    … …  
    12321246<p><a name="gettable"><h4>3.14.1.4 Get Table</h4></p>
    12331247<p>
    1234 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. 10 provides an example source-table.
     1248Use 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. The figure below provides an example source-table.
    12351249</p>
    12361250<p>
    … …  
    12431257</p>
    12441258<p><img src="IMG/screenshot05.png"/></p>
    1245 <p><u>Fig. 10:</u> Broadcaster source-table.</p>
     1259<p><u>Figure:</u> Broadcaster source-table.</p>
    12461260
    12471261<p><a name="ntripv"><h4>3.14.1.5 NTRIP Version - mandatory</h4></p>
Note: See TracChangeset for help on using the changeset viewer.