Changeset 951 in ntrip


Ignore:
Timestamp:
Jul 13, 2008, 12:33:29 AM (16 years ago)
Author:
weber
Message:

* empty log message *

Location:
trunk/BNC
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r950 r951  
    7272&nbsp; &nbsp; &nbsp; 3.5.7. <a href=#rnxvers>Version</a><br>
    73733.6. <a href=#ephemeris>RINEX - Ephemeris</a><br>
    74 &nbsp; &nbsp; &nbsp; 3.6.3. <a href=#ephdir>Directory</a><br>
    75 &nbsp; &nbsp; &nbsp; 3.6.1. <a href=#ephint>File Interval</a><br>
    76 &nbsp; &nbsp; &nbsp; 3.6.2. <a href=#ephport>Output Port</a><br>
     74&nbsp; &nbsp; &nbsp; 3.6.1. <a href=#ephdir>Directory</a><br>
     75&nbsp; &nbsp; &nbsp; 3.6.2. <a href=#ephint>Interval</a><br>
     76&nbsp; &nbsp; &nbsp; 3.6.3. <a href=#ephport>Port</a><br>
    7777&nbsp; &nbsp; &nbsp; 3.6.4. <a href=#ephvers>Version</a><br>
    78783.7. <a href=#syncout>Synchronized Observations</a><br>
    … …  
    291291</p>
    292292
    293 <p><a name="ephint"><h4>3.6.2 File Interval - mandatory if Ephemeris 'Directory' is set</h4></p>
     293<p><a name="ephint"><h4>3.6.2 Interval - mandatory if 'Directory' is set</h4></p>
    294294<p>
    295295Select the length of the RINEX Navigation file generated. The default value is 1 day.
    296296</p>
    297297
    298 <p><a name="ephport"><h4>3.6.3 Output Port - optional</h4></p>
    299 <p>
    300 BNC can output broadcast ephemeris in RINEX ASCII format on your local host (IP 127.0.0.1) through an IP port. Specify an IP port number to activate this function. The default is an empty option field, meaning that no ASCII ephemeris output via IP port is generated.
    301 </p>
    302 <p>
    303 The source code for BNC comes with an example perl script called 'test_bnc_eph.pl' that allows you to read BNC's ASCII ephemeris output from the IP port.
     298<p><a name="ephport"><h4>3.6.3 Port - optional</h4></p>
     299<p>
     300BNC can output broadcast ephemeris in RINEX ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number to activate this function. The default is an empty option field, meaning that no ASCII ephemeris output via IP port is generated.
     301</p>
     302<p>
     303The source code for BNC comes with an example perl script 'test_bnc_eph.pl' that allows you to read BNC's ASCII ephemeris output from the IP port.
    304304</p>
    305305
    … …  
    365365</p>
    366366
    367 <p><a name="syncwait"><h4>3.7.2 Wait for Full Epoch - mandatory if 'File' or 'Port' is set</h4></p>
     367<p><a name="syncwait"><h4>3.7.2 Wait for Full Epoch - mandatory if 'Port' is set</h4></p>
    368368<p>
    369369When feeding a real-time GNSS engine waiting for input epoch by epoch, BNC drops whatever is received later than 'Wait for full epoch' seconds. A value of 3 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming streams and the delay acceptable for your real-time GNSS product. Default value for 'Wait for full epoch' is 5 seconds.
    … …  
    389389<p>
    390390</p>
    391 RTCM 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 tentative messages currently under discussion in RTCM have in implemented in BNC:
     391RTCM 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 tentative messages currently under discussion have been implemented in BNC:
    392392<ul>
    393393<li>Message type 4050: GPS orbit corrections to Broadcast Ephemeris</li>
    394394<li>Message type 4051: GPS clock corrections to Broadcast Ephemeris</li>
    395 <li>Message type 4052: GPS code bias</li>
     395<li>Message type 4052: GPS code biases</li>
    396396<li>Message type 4053: GLONASS orbit corrections to Broadcast Ephemeris</li>
    397397<li>Message type 4054: GLONASS clock corrections to Broadcast Ephemeris</li>
    398 <li>Message type 4055: GLONASS code bias</li>
     398<li>Message type 4055: GLONASS code biases</li>
    399399<li>Message type 4056: Combined GPS and GLONASS orbit corrections to Broadcast Ephemeris</li>
    400400<li>Message type 4057: Combined GPS and GLONASS clock corrections to Broadcast Ephemeris</li>
    401401</ul>
    402 <p> Note that orbit corrections are provided through radial, along-track, and cross-track components of the satellite position.
     402<p>
     403RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications.
     404</p>
     405
     406<p><a name="corrdir"><h4>3.8.1 Directory - optional</h4></p>
     407<p>
     408Specify a directory for saving Ephemeris Corrections in files. If the specified directory does not exist, BNC will not create Ephemeris Correction files. Default value for Ephemeris Corrections 'Directory' is an empty option field, meaning that no Ephemeris Correction files will be created.
     409</p>
     410
     411<p><a name="corrint"><h4>3.8.2 Interval - mandatory if 'Directory' is set</h4></p>
     412<p>
     413Select the length of the Ephemeris Correction files. The default value is 1 day.
     414</p>
     415
     416<p><a name="corrport"><h4>3.8.3 Port - optional</h4></p>
     417<p>
     418BNC can output Ephemeris Corrections in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number to activate this function. The default is an empty option field, meaning that no Ephemeris Correction output via IP port is generated.
     419</p>
     420<p>
     421The source code for BNC comes with an example perl script 'test_bnc_eph.pl' that allows you to read BNC's Ephemeris Corrections from the IP port. Its ASCII output display comprises records carrying the following set of parameters:
     422</p>
     423<p>
     424<ul>
     425<li>Mountpoint</li>
     426<li>GPS Week</li>
     427<li>Second in GPS Week</li>
     428<li>PRN</li>
     429<li>Broadcast Ephemeris IOD</li>
     430<li>Clock Correction to Broadcast Ephemeris [m]</li>
     431<li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li>
     432<li>Along-track Component of Orbit Correction to Broadcast Ephemeris [m]</li>
     433<li>Cross-track Component of Orbit Correction to Broadcast Ephemeris [m]</li>
     434</ul>
     435</p>
     436<p>
     437The output is synchronized epoch by epoch with a leading "A" indicating the begin of an epoch and a trailing "C" indicating the end of an epoch. The following is an example output from two RTCM Version 3 streams (CLCK1 and CLCK4) containing message types 4056 and 4057:
     438<pre>
     439A
     440CLCK1 1487 547554.0 G27    57     12.219      1.241    0.495    0.002
     441CLCK1 1487 547554.0 G29   101     -0.086      0.008   -0.429    0.675
     442CLCK1 1487 461154.0 R06    18      5.192      2.390   -1.915   -6.734
     443CLCK1 1487 461154.0 R07    18     -1.619      2.827    0.901    0.280
     444CLCK4 1487 547554.0 G27    57     12.218      1.242    0.496    0.003
     445CLCK4 1487 547554.0 G29   101     -0.087      0.007   -0.427    0.673
     446CLCK4 1487 461154.0 R06    18      5.191      2.389   -1.914   -6.735
     447CLCK4 1487 461154.0 R07    18     -1.618      2.826    0.900    0.281
     448C
     449A
     450CLCK1 1487 547555.0 G27    57     12.216      1.241    0.494    0.003
     451CLCK1 1487 547555.0 G29   101     -0.084      0.009   -0.428    0.675
     452...
     453...
     454</pre>
     455</p>
     456
     457<p><a name="corrwait"><h4>3.8.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p>
     458<p>
     459When feeding a real-time GNSS engine waiting for Ephemeris Corrections, BNC drops whatever is received later than 'Wait for full epoch' seconds. A value of 2 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming Ephemeris Corrections stream and the delay acceptable by your application. Default value for 'Wait for full epoch' is 5 seconds.
    403460</p>
    404461

  • trunk/BNC/bncmain.cpp

    r937 r951  
    7979    settings.setValue("rnxIntr",    "15 min");
    8080    settings.setValue("ephIntr",    "1 day");
     81    settings.setValue("corrIntr",   "1 day");
    8182    settings.setValue("rnxSkel",    "SKL");
    8283    settings.setValue("waitTime",   5);

  • trunk/BNC/bncwindow.cpp

    r938 r951  
    293293  _outPortLineEdit->setWhatsThis(tr("BNC can produce synchronized observations in binary format on your local host through an IP port. Specify a port number here to activate this function."));
    294294  _outEphPortLineEdit->setWhatsThis(tr("BNC can produce ephemeris data in RINEX ASCII format on your local host through an IP port. Specify a port number here to activate this function."));
    295   _corrPortLineEdit->setWhatsThis(tr("BNC can produce ephemeris corrections on your local host through an IP port. Specify a port number here to activate this function."));
     295  _corrPortLineEdit->setWhatsThis(tr("BNC can produce Broadcast Ephemeris Corrections on your local host through an IP port. Specify a port number here to activate this function."));
    296296  _rnxPathLineEdit->setWhatsThis(tr("Here you specify the path to where the RINEX Observation files will be stored. If the specified directory does not exist, BNC will not create RINEX Observation files."));
    297297  _ephPathLineEdit->setWhatsThis(tr("Specify the path for saving Broadcast Ephemeris data as RINEX Navigation files. If the specified directory does not exist, BNC will not create RINEX Navigation files."));
    298   _corrPathLineEdit->setWhatsThis(tr("Specify the path for saving Broadcast Ephemeris corrections. If the specified directory does not exist, BNC will not create the files."));
     298  _corrPathLineEdit->setWhatsThis(tr("Specify a directory for saving Broadcast Ephemeris correction files. If the specified directory does not exist, BNC will not create the files."));
    299299  _rnxScrpLineEdit->setWhatsThis(tr("<p>Whenever a RINEX Observation file is saved, you might want to compress, copy or upload it immediately via FTP. BNC allows you to execute a script/batch file to carry out these operations. To do that specify the full path of the script/batch file here. BNC will pass the full RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 onUnix/Linux systems).</p><p>The triggering event for calling the script or batch file is the end of a RINEX Observation file 'Interval'. If that is overridden by a stream outage, the triggering event is the stream reconnection.</p>"));
    300300  _rnxSkelLineEdit->setWhatsThis(tr("<p>Whenever BNC starts generating RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. However, sometimes public RINEX header skeleton files are not available, its contents is not up to date, or you need to put additional/optional records in the RINEX header.</p><p>For that BNC allows using personal skeleton files that contain the header records you would like to include. You can derive a personal RINEX header skeleton file from the information given in an up to date sitelog. A file in the RINEX 'Directory' with the RINEX 'Skeleton extension' is interpreted by BNC as a personal RINEX header skeleton file for the corresponding stream.</p>"));
    … …  
    302302  _rnxIntrComboBox->setWhatsThis(tr("<p>Select the length of the RINEX Observation file.</p>"));
    303303  _ephIntrComboBox->setWhatsThis(tr("<p>Select the length of the RINEX Navigation file.</p>"));
    304   _corrIntrComboBox->setWhatsThis(tr("<p>Select the length of the correction file.</p>"));
     304  _corrIntrComboBox->setWhatsThis(tr("<p>Select the length of the Broadcast Ephemeris Correction files.</p>"));
    305305  _rnxSamplSpinBox->setWhatsThis(tr("<p>Select the RINEX Observation sampling interval in seconds. A value of zero '0' tells BNC to store all received epochs into RINEX.</p>"));
    306306  _binSamplSpinBox->setWhatsThis(tr("<p>Select the Observation sampling interval in seconds. A value of zero '0' tells BNC to send/store all received epochs.</p>"));
Note: See TracChangeset for help on using the changeset viewer.