- Timestamp:
- Jul 11, 2008, 3:20:58 PM (17 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (11 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r841 r950 81 81 3.7.3. <a href=#syncfile>File</a><br> 82 82 3.7.4. <a href=#syncsample>Sampling</a><br> 83 3.8. <a href=#advnote>Monitor</a><br> 84 3.8.1. <a href=#obsrate>Observation Rate</a><br> 85 3.8.2. <a href=#advfail>Failure Threshold</a><br> 86 3.8.3. <a href=#advreco>Recovery Threshold</a><br> 87 3.8.4. <a href=#pause>Pause</a><br> 88 3.8.5. <a href=#advscript>Advisory Script</a><br> 89 3.8.6. <a href=#perflog>Performance Log</a><br> 90 3.9. <a href=#mountpoints>Mountpoints</a><br> 91 3.9.1. <a href=#mountadd>Add Mountpoints</a><br> 92 3.9.2. <a href=#mounthost>Broadcaster Host and Port</a><br> 93 3.9.3. <a href=#mountuser>Broadcaster User and Password</a><br> 94 3.9.4. <a href=#mounttable>Get Table</a><br> 95 3.9.5. <a href=#mountdelete>Delete Mountpoints</a><br> 96 3.9.6. <a href=#mountedit>Edit Mountpoints</a><br> 97 3.10. <a href=#start>Start</a><br> 98 3.11. <a href=#stop>Stop</a><br> 99 3.12. <a href=#nw>No Window</a> 83 3.8. <a href=#correct>Ephemeris Corrections</a><br> 84 3.8.1. <a href=#corrdir>Directory</a><br> 85 3.8.2. <a href=#corrint>Interval</a><br> 86 3.8.3. <a href=#corrport>Port</a><br> 87 3.8.4. <a href=#corrwait>Wait for Full Epoch</a><br> 88 3.9. <a href=#advnote>Monitor</a><br> 89 3.9.1. <a href=#obsrate>Observation Rate</a><br> 90 3.9.2. <a href=#advfail>Failure Threshold</a><br> 91 3.9.3. <a href=#advreco>Recovery Threshold</a><br> 92 3.9.4. <a href=#pause>Pause</a><br> 93 3.9.5. <a href=#advscript>Advisory Script</a><br> 94 3.9.6. <a href=#perflog>Performance Log</a><br> 95 3.10. <a href=#mountpoints>Mountpoints</a><br> 96 3.10.1. <a href=#mountadd>Add Mountpoints</a><br> 97 3.10.2. <a href=#mounthost>Broadcaster Host and Port</a><br> 98 3.10.3. <a href=#mountuser>Broadcaster User and Password</a><br> 99 3.10.4. <a href=#mounttable>Get Table</a><br> 100 3.10.5. <a href=#mountdelete>Delete Mountpoints</a><br> 101 3.10.6. <a href=#mountedit>Edit Mountpoints</a><br> 102 3.11. <a href=#start>Start</a><br> 103 3.12. <a href=#stop>Stop</a><br> 104 3.13. <a href=#nw>No Window</a> 100 105 </p> 101 106 … … 381 386 <p> 382 387 383 <p><a name="advnote"><h4>3.8. Monitor</h4></p> 388 <p><a name="correct"><h4>3.8. Ephemeris Corrections</h4></p> 389 <p> 390 </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: 392 <ul> 393 <li>Message type 4050: GPS orbit corrections to Broadcast Ephemeris</li> 394 <li>Message type 4051: GPS clock corrections to Broadcast Ephemeris</li> 395 <li>Message type 4052: GPS code bias</li> 396 <li>Message type 4053: GLONASS orbit corrections to Broadcast Ephemeris</li> 397 <li>Message type 4054: GLONASS clock corrections to Broadcast Ephemeris</li> 398 <li>Message type 4055: GLONASS code bias</li> 399 <li>Message type 4056: Combined GPS and GLONASS orbit corrections to Broadcast Ephemeris</li> 400 <li>Message type 4057: Combined GPS and GLONASS clock corrections to Broadcast Ephemeris</li> 401 </ul> 402 <p> Note that orbit corrections are provided through radial, along-track, and cross-track components of the satellite position. 403 </p> 404 405 <p><a name="advnote"><h4>3.9. Monitor</h4></p> 384 406 385 407 <p> … … 396 418 </p> 397 419 398 <p><a name="obsrate"><h4>3. 8.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', 'Pause' and 'Advisory Script' is set</h4></p>420 <p><a name="obsrate"><h4>3.9.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', 'Pause' and 'Advisory Script' is set</h4></p> 399 421 <p> 400 422 BNC can collect all returns (success or failure) coming from a decoder within a certain short time span to then decide whether a stream has an outage or its content is corrupted. This procedure needs a rough a priory estimate of the expected observation rate of the incoming streams.</p><p>An empty option field (default) means that you don't want an explicit information from BNC about stream outages and incoming streams that can not be decoded and that the special procedure for handling of corrupted streams is by-passed (decoding attempt will never get paused). 401 423 </p> 402 424 403 <p><a name="advfail"><h4>3. 8.2 Failure Threshold - optional</h4></p>425 <p><a name="advfail"><h4>3.9.2 Failure Threshold - optional</h4></p> 404 426 <p> 405 427 Event 'Begin_Failure' will be reported if no data is received continuously for longer than the 'Failure threshold' time. Similarly, event 'Begin_Corrupted' will be reported when corrupted data is detected by the decoder continuously for longer than this 'Failure threshold' time. The default value is set to 15 minutes and is recommended so not to innundate user with too many event reports. … … 409 431 </p> 410 432 411 <p><a name="advreco"><h4>3. 8.3 Recovery Threshold - optional</h4></p>433 <p><a name="advreco"><h4>3.9.3 Recovery Threshold - optional</h4></p> 412 434 <p> 413 435 Once a 'Begin_Failure' or 'Begin_Corrupted' event has been reported, BNC will check for when the stream again becomes available or uncorrupted. Event 'End_Failure' or 'End_Corrupted' will be reported as soon as valid observations are again detected continuously throughout the 'Recovery threshold' time span. The default value is set to 5 minutes and is recommended so not to innundate users with too many event reports. … … 417 439 </p> 418 440 419 <p><a name="pause"><h4>3. 8.4 Pause - optional</h4></p>441 <p><a name="pause"><h4>3.9.4 Pause - optional</h4></p> 420 442 <p> 421 443 In case of a corrupted stream, the decoding process can be paused and decodings are then attempted again at decreasing rate. BNC will first attempt to decode again after a 30 second lag and if unsuccessful, make another attempt within 60 seconds after the previous attempt. If it is still unsuccessful, it will make another attempt to decode within 120 seconds after the previous attempt and so on. Each decoding attempt doubles the wait time since the previous attempt. The maximum wait time between attempts is limited to 960 seconds. Tick 'Pause' to activate this function. Note that it is only effective if an 'Observation rate' is specified. … … 425 447 </p> 426 448 427 <p><a name="advscript"><h4>3. 8.5 Advisory Script - optional </h4></p>449 <p><a name="advscript"><h4>3.9.5 Advisory Script - optional </h4></p> 428 450 <p> 429 451 As mentioned previously, BNC can trigger a shell script or a batch file to be executed when one of the events described are reported. This script can be used to email an advisory note to network operator or stream providers. To enable this feature, specify the full path to the script or batch file in the 'Script' field. The affected mountpoint and type of event reported ('Begin_Outage', 'End_Outage', 'Begin_Corrupted' or 'End_Corrupted') will then be passed on to the script as command line parameters (%1 and %2 on Windows systems or $1 and $2 on Unix/Linux systems) together with date and time information. … … 454 476 </p> 455 477 456 <p><a name="perflog"><h4>3. 8.6 Performance Log - optional </h4></p>478 <p><a name="perflog"><h4>3.9.6 Performance Log - optional </h4></p> 457 479 <p> 458 480 <u>Latency:</u> Latency is defined in BNC by the following equation: … … 481 503 </p> 482 504 483 <p><a name="mountpoints"><h4>3. 9. Mountpoints</h4></p>505 <p><a name="mountpoints"><h4>3.10. Mountpoints</h4></p> 484 506 <p> 485 507 Each stream on an NTRIP broadcaster is defined using a unique source ID called mountpoint. An NTRIP client like BNC access the desired data stream by referring to its mountpoint. Information about mountpoints is available through the source-table maintained by the NTRIP broadcaster. Note that mountpoints could show up in BNC more than once when retrieving streams from several NTRIP broadcasters. … … 498 520 </table> 499 521 500 <p><a name="mountadd"><h4>3. 9.1 Add Mountpoints</h4></p>522 <p><a name="mountadd"><h4>3.10.1 Add Mountpoints</h4></p> 501 523 <p> 502 524 Button 'Add Mountpoints' opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints. 503 525 </p> 504 526 505 <p><a name="mounthost"><h4>3. 9.2 Broadcaster Host and Port - required</h4></p>527 <p><a name="mounthost"><h4>3.10.2 Broadcaster Host and Port - required</h4></p> 506 528 <p> 507 529 Enter the NTRIP broadcaster host IP and port number. <u>http://www.rtcm-ntrip.org/home</u> provides information about known NTRIP broadcaster installations. Note that EUREF and IGS operate NTRIP broadcasters at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u>. 508 530 </p> 509 531 510 <p><a name="mountuser"><h4>3. 9.3 Broadcaster User and Password - required for protected streams</h4></p>532 <p><a name="mountuser"><h4>3.10.3 Broadcaster User and Password - required for protected streams</h4></p> 511 533 <p> 512 534 Some streams on NTRIP broadcasters may be restricted. Enter a valid 'User' ID and 'Password' for access to protected streams. Accounts are usually provided per NTRIP broadcaster through a registration procedure. Register through <u>http://igs.bkg.bund.de/index_ntrip_reg.htm</u> for access to protected streams on <u>www.euref-ip.net</u> and <u>www.igs-ip.net</u>. 513 535 </p> 514 536 515 <p><a name="mounttable"><h4>3. 9.4 Get Table</h4></p>537 <p><a name="mounttable"><h4>3.10.4 Get Table</h4></p> 516 538 <p> 517 539 Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. … … 524 546 </p> 525 547 526 <p><a name="mountdelete"><h4>3. 9.5 Delete Mountpoints</h4></p>548 <p><a name="mountdelete"><h4>3.10.5 Delete Mountpoints</h4></p> 527 549 <p> 528 550 To remove a stream from the 'Mountpoints' list in the main window, highlight it by clicking on it and hit the 'Delete Mountpoints' button. You can also remove multiple mountpoints simultaneously by highlighting them using +Shift and +Ctrl.</p> 529 551 530 <p><a name="mountedit"><h4>3. 9.6 Edit Mountpoints</h4></p>552 <p><a name="mountedit"><h4>3.10.6 Edit Mountpoints</h4></p> 531 553 <ul> 532 554 <li> … … 543 565 </ul> 544 566 545 <p><a name="start"><h4>3.1 0. Start</h4></p>567 <p><a name="start"><h4>3.11. Start</h4></p> 546 568 <p> 547 569 Hit 'Start' to start retrieving, decoding, and converting GNSS data streams in real-time. Note that 'Start' generally forces BNC to begin with fresh RINEX which might overwrite existing files when necessary unless the option 'Append files' is ticked. 548 570 </p> 549 571 550 <p><a name="stop"><h4>3.1 1. Stop</h4></p>572 <p><a name="stop"><h4>3.12. Stop</h4></p> 551 573 <p> 552 574 Hit the 'Stop' button in order to stop BNC. 553 575 </p> 554 576 555 <p><a name="nw"><h4>3.1 2. No Window - optional</h4></p>577 <p><a name="nw"><h4>3.13. No Window - optional</h4></p> 556 578 <p> 557 579 On all systems BNC can be started in batch mode with the command line option '-nw'. BNC will then run in 'no window' mode, using options from the configuration file ${HOME}/.config/BKG/BNC_NTRIP_Client.conf (Unix/Linux, see Config File example in the Annex) or from the register BKG_NTRIP_Client (Windows).
Note:
See TracChangeset
for help on using the changeset viewer.
