Changeset 1466 in ntrip for trunk


Ignore:
Timestamp:
Jan 13, 2009, 7:05:17 PM (16 years ago)
Author:
weber
Message:

* empty log message *

Location:
trunk/BNC
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/bnchelp.html

    r1462 r1466  
    132132&nbsp; &nbsp; &nbsp; 3.12.3. <a href=#streamtable>Caster Table</a><br>
    133133&nbsp; &nbsp; &nbsp; 3.12.4. <a href=#streamuser>User and Password</a><br>
    134 &nbsp; &nbsp; &nbsp; 3.12.5. <a href=#streamntrip>NTRIP Version</a><br>
    135 &nbsp; &nbsp; &nbsp; 3.12.6. <a href=#streamtable>Get Table</a><br>
     134&nbsp; &nbsp; &nbsp; 3.12.5. <a href=#streamtable>Get Table</a><br>
     135&nbsp; &nbsp; &nbsp; 3.12.6. <a href=#streamntrip>NTRIP Version</a><br>
    136136&nbsp; &nbsp; &nbsp; 3.12.7. <a href=#streamdelete>Delete Streams</a><br>
    137137&nbsp; &nbsp; &nbsp; 3.12.8. <a href=#streamedit>Edit Streams</a><br>
     
    774774</p>
    775775
    776 <p><a name="streamntrip"><h4>3.12.5 NTRIP Version - mandatory</h4></p>
    777 <p>
    778 Some limitations and deficiencies of the NTRIP version 1 stream transport protocol are solved in NTRIP version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Options implemented in BNC are:
    779 </p>
    780 <p>
    781 &nbsp; 1:&nbsp; NTRIP version 1 in TCP/IP mode,<br>
     776<p><a name="streamtable"><h4>3.12.5 Get Table</h4></p>
     777<p>
     778Use 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.
     779</p>
     780<p>
     781The contents of data field 'nmea' tells you whether a stream retrieval needs to be initiated by BNC through sending an NMEA-GGA message carrying approximate position coordinates (virtual reference station).
     782</p>
     783<p>
     784Hit 'OK' to return to the main window. If you wish you can click on 'Add Streams' and repeat the process again to retrieve streams from different casters.
     785</p>
     786
     787<p><a name="streamntrip"><h4>3.12.6 NTRIP Version - mandatory</h4></p>
     788<p>
     789Some limitations and deficiencies of the NTRIP version 1 stream transport protocol are solved in NTRIP version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Version 2 is backwards compatible to Version 1. Options implemented in BNC are:
     790</p>
     791<p>
     792&nbsp; 1:&nbsp; NTRIP version 1, TCP/IP.<br>
    782793&nbsp; 2:&nbsp; NTRIP version 2 in TCP/IP mode.<br>
    783794&nbsp; R:&nbsp; NTRIP version 2 in RTSP/RTP mode.
    784795</p>
    785796<p>
    786 If protocol version 2 is supported by the broadcaster:
    787 </p>
    788 <ul>
    789 <li>Try using option '2' if your streams are blocked by a proxy server operated in front of BNC.</li>
    790 <li>Option 'R' may be selected if latency is more important than completeness for your application. Note that the latency reduction is likely to be in the order of 0.5 sec. Note further that option 'R' is not accepted by proxy servers.</li>
     797If NTRIP version 2 is supported by the broadcaster:
     798</p>
     799<ul>
     800<li>Try using option '2' if your streams are otherwise blocked by a proxy server operated in front of BNC.</li>
     801<li>Option 'R' may be selected if latency is more important than completeness for your application. Note that the latency reduction is likely to be in the order of 0.5 sec or less. Note further that option 'R' (RTSP/RTP mode) is not accepted by proxy servers and a mobile Internet Service Provider may not support it.</li>
    791802</ul>
    792803<p>
    793804Select option '1' if you are not sure whether the broadcaster supports NTRIP version 2.</li>
    794805</p>
    795 
    796 <p><a name="streamtable"><h4>3.12.6 Get Table</h4></p>
    797 <p>
    798 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.
    799 </p>
    800 <p>
    801 The contents of data field 'nmea' tells you whether a stream retrieval needs to be initiated by BNC through sending an NMEA-GGA message carrying approximate position coordinates (virtual reference station).
    802 </p>
    803 <p>
    804 Hit 'OK' to return to the main window. If you wish you can click on 'Add Streams' and repeat the process again to retrieve streams from different casters.
    805 </p>
    806806
    807807<p><a name="streamdelete"><h4>3.12.7 Delete Streams</h4></p>
  • trunk/BNC/bnctabledlg.cpp

    r1465 r1466  
    114114
    115115  _buttonCasterTable->setWhatsThis(tr("<p>Hit 'Show' for a table of known NTRIP broadcaster installations as maintained at www.rtcm-ntrip.org/home.</p><p>A window opens which allows to select a broadcaster for stream retrieval.</p>"));
    116   _ntripVersionComboBox->setWhatsThis(tr("<p>Select the NTRIP transport protocol version you want to use. Implemented options are:<br>&nbsp; 1:&nbsp; NTRIP version 1, TCP/IP<br>&nbsp; 2:&nbsp; NTRIP version 2, TCP/IP<br>&nbsp; R:&nbsp; NTRIP Version 2, RTSP/RTP<br>Select option '1' if you are not sure whether the NTRIP broadcaster supports NTRIP version 2.</p>"));
     116  _ntripVersionComboBox->setWhatsThis(tr("<p>Select the NTRIP transport protocol version you want to use. Implemented options are:<br>&nbsp; 1:&nbsp; NTRIP version 1, TCP/IP<br>&nbsp; 2:&nbsp; NTRIP version 2, TCP/IP mode<br>&nbsp; R:&nbsp; NTRIP Version 2, RTSP/RTP mode<br>Select option '1' if you are not sure whether the NTRIP broadcaster supports NTRIP version 2.</p><p>Note that RTSP/RTP (option 'R') is sometimes not supported by mobile Internet Service Providers.</p>"));
    117117
    118118  _table = new QTableWidget(this);
Note: See TracChangeset for help on using the changeset viewer.