Changeset 952 in ntrip
- Timestamp:
- Jul 13, 2008, 9:51:58 AM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r951 r952 408 408 Specify 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 409 </p> 410 <p> 411 The file name convention for Ephemeris Correction files follows the convention for RINEX files except for the last character of the file name suffix which is set to "C". 412 </p> 410 413 411 414 <p><a name="corrint"><h4>3.8.2 Interval - mandatory if 'Directory' is set</h4></p> … … 419 422 </p> 420 423 <p> 421 The 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. I ts ASCII output display comprises records carrying the following set of parameters:424 The 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. In case of a stream carrying message types 4056 and 4057, the script produces ASCII records containing the following set of parameters: 422 425 </p> 423 426 <p> … … 426 429 <li>GPS Week</li> 427 430 <li>Second in GPS Week</li> 428 <li> PRN</li>429 <li> Broadcast Ephemeris IOD</li>431 <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li> 432 <li>IOD refering to Broadcast Ephemeris set</li> 430 433 <li>Clock Correction to Broadcast Ephemeris [m]</li> 431 434 <li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li> … … 435 438 </p> 436 439 <p> 437 The output is synchronized epoch by epoch with a leading "A" indicating the begin of an epochand 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:440 The output is synchronized epoch by epoch with a leading "A" indicating the begin 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 441 <pre> 439 442 A
Note:
See TracChangeset
for help on using the changeset viewer.