Changeset 1666 in ntrip


Ignore:
Timestamp:
Feb 27, 2009, 10:41:19 AM (15 years ago)
Author:
weber
Message:

* empty log message *

Location:
trunk
Files:
5 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r1665 r1666  
    950950Using 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).
    951951</li>
    952 Concerning the length of data fields in RTCM Version 3.x premature message types 4063 and 4069 (combined orbit and clock corrections to GPS and GLONASS Broadcast Ephemeris, see RTCM document 012-2009-SC104-528 'Proposed SSR Messages for SV Orbit, Clock, Code Biases, URA prepared by Geo++'). A final decision on his is not yet available. Note the what's implemented in BNC is just a temporary solutions.
     952Concerning 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.
    953953<li>
    954954Using 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/bns.pro

    r1661 r1666  
    44CONFIG += release
    55#CONFIG += debug
     6CONFIG += OLD
    67
    78RESOURCES += bns.qrc

  • trunk/BNS/bnsabout.html

    r1249 r1666  
    2121The Bundesamt fuer Geodaesie und Kartographie (BKG) may not be held liable for damages of any kind, direct or consequential, which may result from the use of this software.<br>
    2222<br>
    23 BKG, Frankfurt, Germany, December 2008<br>
     23BKG, Frankfurt, Germany, March 2009<br>
    2424E-Mail: <a><u>euref-ip@bkg.bund.de</u></a>.<br>
    2525</p>

  • trunk/BNS/bnshelp.html

    r1656 r1666  
    1 <h3>BKG Ntrip State Space Server (BNS) Version 1.0</h3>
     1<h3>BKG Ntrip State Space Server (BNS) Version 1.1</h3>
    22
    33<p>
    … …  
    5151</p>
    5252<p>
    53 Note that BNS currently only generates premature RTCM Version 3.x message types 4056 for combined GPS orbit and clock corrections and 4057 for combined GLONASS orbit and clock corrections to Broadcast Ephemeris.
     53Note that BNS currently only generates premature RTCM Version 3.x message types 4063 for combined GPS orbit and clock corrections and 4069 for combined GLONASS orbit and clock corrections to Broadcast Ephemeris.
    5454</p>
    5555
    … …  
    275275<p><a name="ephc"><h4>4.7. Ephemeris Corrections</h4></p>
    276276<p>
    277 BNS can upload the resulting stream(s) of clock and orbit corrections to Broadcast Ephemeris to an NTRIP Broadcaster. Both EUREF and IGS operate an NTRIP broadcaster at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u> which can be used for stream upload. The stream's format is RTCM Version 3.x. Note that it only carries the premature message Types 4056 and 4057 for combined orbit and clock corrections to GPS and GLONASS Broadcast Ephemeris.
     277BNS can upload the resulting stream(s) of clock and orbit corrections to Broadcast Ephemeris to an NTRIP Broadcaster. Both EUREF and IGS operate an NTRIP broadcaster at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u> which can be used for stream upload. The stream's format is RTCM Version 3.x. Note that it only carries the premature message Types 4063 and 4069 for combined orbit and clock corrections to GPS and GLONASS Broadcast Ephemeris.
    278278</p>
    279279<p>
    … …  
    362362</p>
    363363<p>
    364 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 4056 and 4057:
     364The 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:
    365365</p>
    366366<p>
    … …  
    438438</li>
    439439<li>
    440 Currently BNS can only generate premature RTCM Version 3.x message Type 4056 and 4057 for combined GPS and GLONASS orbit and clock corrections, see RTCM document 026-2008-SC104-429 'Version 1 Proposed SSR Messages prepared by Geo++'. Note that the length of data fields in these messages is not yet standardized. What's implemented in BNS is just a temporary solution.
     440Currently 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.
    441441</li>
    442442<li>
    … …  
    474474<tr></tr>
    475475<tr><td>Dec 2008 &nbsp;</td><td>Version 1.0 &nbsp;</td><td>[Add] Source code and binaries published.</td></tr>
     476<tr><td>Mar 2009 &nbsp;</td><td>Version 1.1 &nbsp;</td><td>[Add] New messages for URA and high-rate clocks.</td></tr>
    476477</table>
    477478</p>
    … …  
    518519<p>
    519520<ul>
    520 <li>Message type 4050: GPS orbit corrections to Broadcast Ephemeris</li>
    521 <li>Message type 4051: GPS clock corrections to Broadcast Ephemeris</li>
    522 <li>Message type 4052: GPS code biases</li>
    523 <li>Message type 4053: GLONASS orbit corrections to Broadcast Ephemeris</li>
    524 <li>Message type 4054: GLONASS clock corrections to Broadcast Ephemeris</li>
    525 <li>Message type 4055: GLONASS code biases</li>
    526 <li>Message type 4056: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
    527 <li>Message type 4057: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
     521<li>Message type 4060: GPS orbit corrections to Broadcast Ephemeris</li>
     522<li>Message type 4061: GPS clock corrections to Broadcast Ephemeris</li>
     523<li>Message type 4062: GPS code biases</li>
     524<li>Message type 4063: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
     525<li>Message type 4064: GPS User Range Accuracy (URA)</li>
     526<li>Message type 4065: High-rate GPS clock corrections to Broadcast Ephemeris</li>
     527<li>Message type 4066: GLONASS orbit corrections to Broadcast Ephemeris</li>
     528<li>Message type 4067: GLONASS clock corrections to Broadcast Ephemeris</li>
     529<li>Message type 4068: GLONASS code biases</li>
     530<li>Message type 4069: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
     531<li>Message type 4070: GLONASS User Range Accuracy (URA)</li>
     532<li>Message type 4071: High-rate GLONASS clock corrections to Broadcast Ephemeris</li>
    528533</ul>
    529534</p>

  • trunk/BNS/bnswindow.cpp

    r1267 r1666  
    4242  img->setPixmap(QPixmap(":ntrip-logo.png"));
    4343  dlgLayout->addWidget(img, 0,0);
    44   dlgLayout->addWidget(new QLabel("BKG Ntrip State Space Server (BNS) Version 1.0"), 0,1);
     44  dlgLayout->addWidget(new QLabel("BKG Ntrip State Space Server (BNS) Version 1.1"), 0,1);
    4545  dlgLayout->addWidget(tb,1,0,1,2);
    4646  dlgLayout->addWidget(_closeButton,2,1,Qt::AlignRight); 
    … …  
    9999  int ww = QFontMetrics(this->font()).width('w');
    100100  setMinimumSize(77*ww, 65*ww);
    101   setWindowTitle(tr("BKG Ntrip State Space Server (BNS) Version 1.0"));
     101  setWindowTitle(tr("BKG Ntrip State Space Server (BNS) Version 1.1"));
    102102  setWindowIcon(QPixmap(":ntrip-logo.png"));
    103103
Note: See TracChangeset for help on using the changeset viewer.