Changeset 2444 in ntrip for trunk


Ignore:
Timestamp:
Apr 20, 2010, 4:04:10 PM (15 years ago)
Author:
weber
Message:

* empty log message *

Location:
trunk/BNC
Files:
1 added
3 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnc.qrc

    r2443 r2444  
    1616    <file alias="screenshot08.png">IMG/screenshot08.png</file>
    1717    <file alias="screenshot09.png">IMG/screenshot09.png</file>
     18    <file alias="screenshot10.png">IMG/screenshot10.png</file>
    1819</qresource>
    1920</RCC>

  • trunk/BNC/bnchelp.html

    r2443 r2444  
    6262
    6363<p>
    64 Fig. 1 shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link. The purpose could i.e. be PPP or conversion of RTCM streams to RINEX files. 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 scenario to encode correctors to RTCMv3.
     64Fig. 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.
     65</p>
     66<p><img src=":/bnchelp/screenshot10.png"/></p>
     67<p><u>Fig. 1:</u> BNC connected to a GNSS receiver for Precise Point Positioning.</p>
     68
     69<p>
    6570</p>
    6671<p><img src=":/bnchelp/screenshot01.png"/></p>
    67 <p><u>Fig. 1:</u> BNC connected to a GNSS receiver.</p>
     72<p><u>Fig. 2:</u> BNC converting RTCM streams to RINEX batches.</p>
    6873
    6974<p>
    7075</p>
    7176<p><img src=":/bnchelp/screenshot02.png"/></p>
    72 <p><u>Fig. 2:</u> BNC feeding a real-time GNSS engine.</p>
     77<p><u>Fig. 3:</u> BNC feeding a real-time GNSS engine.</p>
     78
    7379
    7480<p><a name="resources"><h3>2. Modes &amp; Resources</h3></p>
    … …  
    8894<p><a name="options"><h3>3. Options</h3></p>
    8995<p>
    90 This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar, see Fig. 3.
     96This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar, see Fig. 4.
    9197</p>
    9298<p><img src=":/bnchelp/screenshot09.png"/></p>
    93 <p><u>Fig. 3:</u> Sections on BNC's main window.</p>
     99<p><u>Fig. 4:</u> Sections on BNC's main window.</p>
    94100
    95101</p>
    … …  
    970976</p>
    971977<p>
    972 Fig. 4. provides the screenshot of an example PPP session with BNC.
     978Fig. 5. provides the screenshot of an example PPP session with BNC.
    973979</p>
    974980<p><img src=":/bnchelp/screenshot03.png"/></p>
    975 <p><u>Fig. 4:</u> Precise Point Positioning (PPP) with BNC.</p>
     981<p><u>Fig. 5:</u> Precise Point Positioning (PPP) with BNC.</p>
    976982
    977983<p>
    … …  
    11661172<p><a name="throughput"><h4>3.13.2 Throughput</h4></p>
    11671173<p>
    1168 The 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.
     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 a number of incoming streams.
    11691175</p>
    11701176
    … …  
    11721178</p>
    11731179<p><img src=":/bnchelp/screenshot08.png"/></p>
    1174 <p><u>Fig. 5:</u> Bandwidth consumption of a number of incoming streams.</p>
     1180<p><u>Fig. 6:</u> Bandwidth consumption of a number of incoming streams.</p>
    11751181
    11761182<p><a name="latency"><h4>3.13.3 Latency</h4></p>
    11771183<p>
    1178 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. 6. shows the latency of a number of incoming streams.
     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 a number of incoming streams.
    11791185</p>
    11801186
    … …  
    11821188</p>
    11831189<p><img src=":/bnchelp/screenshot07.png"/></p>
    1184 <p><u>Fig. 6:</u> Latency of incoming streams.</p>
     1190<p><u>Fig. 7:</u> Latency of incoming streams.</p>
    11851191
    11861192<p><a name="ppptab"><h4>3.13.4 PPP Plot</h4></p>
    … …  
    11971203
    11981204<p>
    1199 Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 7.
     1205Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 8.
    12001206</p>
    12011207<p><img src=":/bnchelp/screenshot06.png"/></p>
    1202 <p><u>Fig. 7:</u> Steam input communication links.</p>
     1208<p><u>Fig. 8:</u> Steam input communication links.</p>
    12031209
    12041210<p>
    … …  
    12131219<p><a name="streamtable"><h4>3.14.1.2 Casters Table - optional</h4></p>
    12141220<p>
    1215 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. 8.
     1221It 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.
    12161222</p>
    12171223</p>
    12181224<p><img src=":/bnchelp/screenshot04.png"/></p>
    1219 <p><u>Fig. 8:</u> Casters table.</p>
     1225<p><u>Fig. 9:</u> Casters table.</p>
    12201226
    12211227<p><a name="streamuser"><h4>3.14.1.3 User and Password - mandatory for protected streams</h4></p>
    … …  
    12261232<p><a name="gettable"><h4>3.14.1.4 Get Table</h4></p>
    12271233<p>
    1228 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. 9 provides an example source-table.
     1234Use 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.
    12291235</p>
    12301236<p>
    … …  
    12371243</p>
    12381244<p><img src=":/bnchelp/screenshot05.png"/></p>
    1239 <p><u>Fig. 9:</u> Broadcaster source-table.</p>
     1245<p><u>Fig. 10:</u> Broadcaster source-table.</p>
    12401246
    12411247<p><a name="ntripv"><h4>3.14.1.5 NTRIP Version - mandatory</h4></p>
Note: See TracChangeset for help on using the changeset viewer.