Changeset 1742 in ntrip


Ignore:
Timestamp:
Mar 6, 2009, 5:31:49 PM (15 years ago)
Author:
weber
Message:

* empty log message *

Location:
trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r1693 r1742  
    5151<ul>
    5252<li>RTCM Version 2.x containing message types 18 and 19 or 20 and 21 together with 3 and 22 (GPS and GLONASS), </li>
    53 <li>RTCM Version 3.x containing message types 1002 (GPS, SBAS) or 1004 (GPS), 1010 or 1012 (GLONASS), 1019 or 1020 (broadcast ephemeris), 4060-4071 (premature messages for combined orbit and clock corrections to GPS and GLONASS broadcast ephemeris)</li>
     53<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>
    5454<li>RTIGS containing GPS record types 200 (observations) and 300 (ephemeris).</li>
    5555</ul>
    … …  
    389389RTCM 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:
    390390<ul>
    391 <li>Message type 4060: GPS orbit corrections to Broadcast Ephemeris</li>
    392 <li>Message type 4061: GPS clock corrections to Broadcast Ephemeris</li>
    393 <li>Message type 4062: GPS code biases</li>
    394 <li>Message type 4063: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
    395 <li>Message type 4064: GPS User Range Accuracy (URA)</li>
    396 <li>Message type 4065: High-rate GPS clock corrections to Broadcast Ephemeris</li>
    397 <li>Message type 4066: GLONASS orbit corrections to Broadcast Ephemeris</li>
    398 <li>Message type 4067: GLONASS clock corrections to Broadcast Ephemeris</li>
    399 <li>Message type 4068: GLONASS code biases</li>
    400 <li>Message type 4069: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
    401 <li>Message type 4070: GLONASS User Range Accuracy (URA)</li>
    402 <li>Message type 4071: High-rate GLONASS clock corrections to Broadcast Ephemeris</li>
     391<li>Message type 3000: GPS orbit corrections to Broadcast Ephemeris</li>
     392<li>Message type 3001: GPS clock corrections to Broadcast Ephemeris</li>
     393<li>Message type 3002: GPS code biases</li>
     394<li>Message type 3003: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
     395<li>Message type 3004: GPS User Range Accuracy (URA)</li>
     396<li>Message type 3005: High-rate GPS clock corrections to Broadcast Ephemeris</li>
     397<li>Message type 3006: GLONASS orbit corrections to Broadcast Ephemeris</li>
     398<li>Message type 3007: GLONASS clock corrections to Broadcast Ephemeris</li>
     399<li>Message type 3008: GLONASS code biases</li>
     400<li>Message type 3009: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
     401<li>Message type 3010: GLONASS User Range Accuracy (URA)</li>
     402<li>Message type 3011: High-rate GLONASS clock corrections to Broadcast Ephemeris</li>
    403403</ul>
    404404<p>
    … …  
    454454</p>
    455455<p>
    456 The following is an example output from two RTCM Version 3 streams (CLCK1 and CLCK4) containing message types 4063 and 4069:
     456The following is an example output from two RTCM Version 3 streams (CLCK1 and CLCK4) containing message types 3004 and 3010:
    457457<pre>
    458458...
    … …  
    966966Using 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).
    967967</li>
    968 Concerning the RTCM Version 3.x premature message types 4060-4071 (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.
     968Concerning 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.
    969969<li>
    970970Using 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).

  • trunk/BNS/bnshelp.html

    r1728 r1742  
    393393</p>
    394394<p>
    395 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 4063 and 4069:
     395The 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:
    396396</p>
    397397<p>
    … …  
    506506</li>
    507507<li>
    508 Currently BNS can only generate premature RTCM Version 3.x message Type 4060-4071 (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.
     508Currently 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.
    509509</li>
    510510<li>
    … …  
    600600<p>
    601601<ul>
    602 <li>Message type 4060: GPS orbit corrections to Broadcast Ephemeris</li>
    603 <li>Message type 4061: GPS clock corrections to Broadcast Ephemeris</li>
    604 <li>Message type 4062: GPS code biases</li>
    605 <li>Message type 4063: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
    606 <li>Message type 4064: GPS User Range Accuracy (URA)</li>
    607 <li>Message type 4065: High-rate GPS clock corrections to Broadcast Ephemeris</li>
    608 <li>Message type 4066: GLONASS orbit corrections to Broadcast Ephemeris</li>
    609 <li>Message type 4067: GLONASS clock corrections to Broadcast Ephemeris</li>
    610 <li>Message type 4068: GLONASS code biases</li>
    611 <li>Message type 4069: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
    612 <li>Message type 4070: GLONASS User Range Accuracy (URA)</li>
    613 <li>Message type 4071: High-rate GLONASS clock corrections to Broadcast Ephemeris</li>
     602<li>Message type 3001: GPS orbit corrections to Broadcast Ephemeris</li>
     603<li>Message type 4002: GPS clock corrections to Broadcast Ephemeris</li>
     604<li>Message type 3003: GPS code biases</li>
     605<li>Message type 3004: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
     606<li>Message type 3005: GPS User Range Accuracy (URA)</li>
     607<li>Message type 3006: High-rate GPS clock corrections to Broadcast Ephemeris</li>
     608<li>Message type 3007: GLONASS orbit corrections to Broadcast Ephemeris</li>
     609<li>Message type 3008: GLONASS clock corrections to Broadcast Ephemeris</li>
     610<li>Message type 3009: GLONASS code biases</li>
     611<li>Message type 3010: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
     612<li>Message type 3011: GLONASS User Range Accuracy (URA)</li>
     613<li>Message type 4012: High-rate GLONASS clock corrections to Broadcast Ephemeris</li>
    614614</ul>
    615615</p>
Note: See TracChangeset for help on using the changeset viewer.