Changeset 1839 in ntrip


Ignore:
Timestamp:
May 8, 2009, 1:49:57 PM (15 years ago)
Author:
weber
Message:

* empty log message *

Location:
trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/bnchelp.html

    r1821 r1839  
    5252<ul>
    5353<li>RTCM Version 2.x containing message types 18 and 19 or 20 and 21 together with 3 and 22 (GPS and GLONASS), </li>
    54 <li>RTCM Version 3.x containing message types 1002 (GPS, SBAS) or 1004 (GPS), 1010 or 1012 (GLONASS), 1019 or 1020 (broadcast ephemeris), 3001-3012 (premature messages for combined orbit and clock corrections to GPS and GLONASS broadcast ephemeris)</li>
     54<li>RTCM Version 3.x containing message types 1002 (GPS, SBAS) or 1004 (GPS), 1010 or 1012 (GLONASS), 1019 or 1020 (broadcast ephemeris), 1057-1068 (premature State Space Representation messages for GPS and GLONASS)</li>
    5555<li>RTIGS containing GPS record types 200 (observations) and 300 (ephemeris).</li>
    5656</ul>
     
    393393RTCM is in the process of developing new Version 3 messages to transport satellite clock and orbit corrections in real-time. Based on the latest available proposal, the following premature messages currently under discussion have been implemented in BNC:
    394394<ul>
    395 <li>Message type 3001: GPS orbit corrections to Broadcast Ephemeris</li>
    396 <li>Message type 3002: GPS clock corrections to Broadcast Ephemeris</li>
    397 <li>Message type 3003: GPS code biases</li>
    398 <li>Message type 3004: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
    399 <li>Message type 3005: GPS User Range Accuracy (URA)</li>
    400 <li>Message type 3006: High-rate GPS clock corrections to Broadcast Ephemeris</li>
    401 <li>Message type 3007: GLONASS orbit corrections to Broadcast Ephemeris</li>
    402 <li>Message type 3008: GLONASS clock corrections to Broadcast Ephemeris</li>
    403 <li>Message type 3009: GLONASS code biases</li>
    404 <li>Message type 3010: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
    405 <li>Message type 3011: GLONASS User Range Accuracy (URA)</li>
    406 <li>Message type 3012: High-rate GLONASS clock corrections to Broadcast Ephemeris</li>
     395<li>Message type 1057: GPS orbit corrections to Broadcast Ephemeris</li>
     396<li>Message type 1058: GPS clock corrections to Broadcast Ephemeris</li>
     397<li>Message type 1059: GPS code biases</li>
     398<li>Message type 1060: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
     399<li>Message type 1061: GPS User Range Accuracy (URA)</li>
     400<li>Message type 1062: High-rate GPS clock corrections to Broadcast Ephemeris</li>
     401<li>Message type 1063: GLONASS orbit corrections to Broadcast Ephemeris</li>
     402<li>Message type 1064: GLONASS clock corrections to Broadcast Ephemeris</li>
     403<li>Message type 1065: GLONASS code biases</li>
     404<li>Message type 1066: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
     405<li>Message type 1067: GLONASS User Range Accuracy (URA)</li>
     406<li>Message type 1068: High-rate GLONASS clock corrections to Broadcast Ephemeris</li>
    407407</ul>
    408408<p>
     
    458458</p>
    459459<p>
    460 The following is an example output from two RTCM Version 3 streams (CLCK1 and CLCK4) containing message types 3004 and 3010:
     460The following is an example output from two RTCM Version 3 streams (CLCK1 and CLCK4) containing message types 1060 and 1066:
    461461<pre>
    462462...
     
    10261026Using RTCM Version 3.x, BNC will properly handle message types 1002, 1004, 1010, and 1012. Note that when handling message types 1001, 1003, 1009 and 1011 where the ambiguity field is not set, the output will be no valid RINEX. All values will be stored modulo 299792.458 (speed of light).
    10271027</li>
    1028 Concerning the RTCM Version 3.x premature message types 3001-3012 (see RTCM document 012-2009-SC104-528 'Proposed SSR Messages for SV Orbit, Clock, Code Biases, URA prepared by Geo++'), a final decision is not yet made. Note the what's implemented in BNC is just a temporary solutions.
     1028Concerning the RTCM Version 3.x premature message types 1057-1068 (see RTCM document 091-2009-SC104-542 'Version 3 Proposed Messages – Set 10'), a final decision is not yet made. Note the what's implemented in BNC is just a temporary solutions.
    10291029<li>
    10301030Using RTCM Version 2.x, BNC will only handle message types 18 and 19 or 20 and 21 together with position and the antenna offset information carried in types 3 and 22. Note that processing carrier phase corrections and pseudo-range corrections contained in message types 20 and 21 needs access to broadcast ephemeris. Hence, whenever dealing with message types 20 and 21, make sure that broadcast ephemeris become available for BNC through also retrieving at least one RTCM Version 3.x stream carrying message types 1019 (GPS ephemeris) and 1020 (GLONASS ephemeris).
     
    11341134<tr>
    11351135<td>May 2009 &nbsp;</td><td>Version 1.7 &nbsp;</td>
    1136 <td>[Bug] RINEX navigation file format<br> [Add] Upgrade to Qt Version 4.4.3<br> [Add] Support of NTRIP v2<br> [Add] Rover support via serial port<br> [Add] Show broadcaster table from www.rtcm-ntrip.org<br> [Add] Enable/disable tab widgets<br> [Add] User defined configuration file name<br> [mod] Switch to configuration files in ini-Format<br> [Add] Daily logfile rotation<br> [Add] Read from TCP/IP port, by-pass NTRIP transport protocol<br> [Add] Save NMEA messages coming from rover<br> [Add] Auto start<br> [Add] Drag and drop ini files<br> [Add] Read from serial port, by-pass NTRIP transport protocol<br> [Mod] Update following RTCM 012-2009-SC104-528 document</td>
     1136<td>[Bug] RINEX navigation file format<br> [Add] Upgrade to Qt Version 4.4.3<br> [Add] Support of NTRIP v2<br> [Add] Rover support via serial port<br> [Add] Show broadcaster table from www.rtcm-ntrip.org<br> [Add] Enable/disable tab widgets<br> [Add] User defined configuration file name<br> [mod] Switch to configuration files in ini-Format<br> [Add] Daily logfile rotation<br> [Add] Read from TCP/IP port, by-pass NTRIP transport protocol<br> [Add] Save NMEA messages coming from rover<br> [Add] Auto start<br> [Add] Drag and drop ini files<br> [Add] Read from serial port, by-pass NTRIP transport protocol<br> [Mod] Update following RTCM 091-2009-SC104-542 document</td>
    11371137</tr>
    11381138
  • trunk/BNS/bnshelp.html

    r1821 r1839  
    397397</p>
    398398<p>
    399 The following is an example file contents based on combined orbit and clock corrections for GPS and GLONASS carried in RTCM Version 3.x message Type 3004 and 3010:
     399The following is an example file contents based on combined orbit and clock corrections for GPS and GLONASS carried in RTCM Version 3.x message Type 1060 and 1066:
    400400</p>
    401401<p>
     
    528528</li>
    529529<li>
    530 Currently BNS can only generate premature RTCM Version 3.x message Type 3001-3012 (see RTCM document 012-2009-SC104-528 'Proposed SSR Messages for SV Orbit, Clock, Code Biases, URA prepared by Geo++'). Note that what is implemented in BNS is just a temporary solution.
     530Currently BNS can only generate premature RTCM Version 3.x message Type 1057-1068 (see RTCM document 091-2009-SC104-542 'Version 3 Proposed Messages – Set 10') . Note that what is implemented in BNS is just a temporary solution.
    531531</li>
    532532<li>
     
    571571<tr>
    572572<td>May 2009 &nbsp;</td><td>Version 1.1 &nbsp;</td>
    573 <td>[Add] Upgrade to Qt Version 4.4.3<br> [Add] Enable/disable tab widgets<br> [Add] User defined configuration file name<br> [mod] Switch to configuration files in ini-Format<br> [Add] Auto start<br> [Add] Drag and drop ini files<br> [Add] Send broadcast clocks<br> [Mod] Update following RTCM 012-2009-SC104-528 document</td>
     573<td>[Add] Upgrade to Qt Version 4.4.3<br> [Add] Enable/disable tab widgets<br> [Add] User defined configuration file name<br> [mod] Switch to configuration files in ini-Format<br> [Add] Auto start<br> [Add] Drag and drop ini files<br> [Add] Send broadcast clocks<br> [Mod] Update following RTCM 091-2009-SC104-542 document</td>
    574574</tr>
    575575
     
    622622<p>
    623623<ul>
    624 <li>Message type 3001: GPS orbit corrections to Broadcast Ephemeris</li>
    625 <li>Message type 3002: GPS clock corrections to Broadcast Ephemeris</li>
    626 <li>Message type 3003: GPS code biases</li>
    627 <li>Message type 3004: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
    628 <li>Message type 3005: GPS User Range Accuracy (URA)</li>
    629 <li>Message type 3006: High-rate GPS clock corrections to Broadcast Ephemeris</li>
    630 <li>Message type 3007: GLONASS orbit corrections to Broadcast Ephemeris</li>
    631 <li>Message type 3008: GLONASS clock corrections to Broadcast Ephemeris</li>
    632 <li>Message type 3009: GLONASS code biases</li>
    633 <li>Message type 3010: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
    634 <li>Message type 3011: GLONASS User Range Accuracy (URA)</li>
    635 <li>Message type 3012: High-rate GLONASS clock corrections to Broadcast Ephemeris</li>
     624<li>Message type 1057: GPS orbit corrections to Broadcast Ephemeris</li>
     625<li>Message type 1058: GPS clock corrections to Broadcast Ephemeris</li>
     626<li>Message type 1059: GPS code biases</li>
     627<li>Message type 1060: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
     628<li>Message type 1061: GPS User Range Accuracy (URA)</li>
     629<li>Message type 1062: High-rate GPS clock corrections to Broadcast Ephemeris</li>
     630<li>Message type 1063: GLONASS orbit corrections to Broadcast Ephemeris</li>
     631<li>Message type 1064: GLONASS clock corrections to Broadcast Ephemeris</li>
     632<li>Message type 1065: GLONASS code biases</li>
     633<li>Message type 1066: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
     634<li>Message type 1067: GLONASS User Range Accuracy (URA)</li>
     635<li>Message type 1068: High-rate GLONASS clock corrections to Broadcast Ephemeris</li>
    636636</ul>
    637637</p>
Note: See TracChangeset for help on using the changeset viewer.