Changeset 1192 in ntrip
- Timestamp:
- Nov 13, 2008, 3:57:52 PM (15 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (17 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r1191 r1192 21 21 <h4> 22 22 <a href=#purpose>1. Purpose</a><br> 23 <a href=#resources>2. Resources</a><br>23 <a href=#resources>2. Modes & Resources</a><br> 24 24 <a href=#options>3. Options</a><br> 25 25 <a href=#limits>4. Limitations</a><br> … … 38 38 <li>generate ephemeris and synchronized observations epoch by epoch through an IP port to support real-time GNSS engines, and/or</li> 39 39 <li>generate clock and orbit corrections to broadcast ephemeris through an IP port to support real-time Precise Point Positioning on GNSS rovers, and/or</li> 40 <li>generate synchronized clock and orbit corrections to broadcast ephemeris epoch by epoch through an IP port to support the combination of such streams coming from variousproviders, and/or</li>40 <li>generate synchronized clock and orbit corrections to broadcast ephemeris epoch by epoch through an IP port to support the combination of such streams as coming from various correction providers, and/or</li> 41 41 <li>monitor the performance of a network of real-time GNSS reference stations to generate advisory notes, and/or</li> 42 42 <li>check RTCM streams for incoming message types and their repetition rates.</li> … … 54 54 BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files. 55 55 </p> 56 <p><a name="resources"><h3>2. Modes andResources</h3></p>57 <p> 58 Although BNC is a real-time tool to be operated in online mode, it can be run offline for post processing of data made availabe from a file. Furthermore, besides its regular window mode, BNC can be started as a batch/background job in a 'no window' mode using processing options from previously saved configuration parameters.56 <p><a name="resources"><h3>2. Modes & Resources</h3></p> 57 <p> 58 Although BNC is a real-time tool to be operated in online mode, it can be run offline for post processing of data made availabe from a file. Furthermore, apart from its regular window mode, BNC can be run as a batch/background job in a 'no window' mode using processing options from previously saved configuration. 59 59 </p> 60 60 <p> … … 69 69 70 70 <p><a name="options"><h3>3. Options</h3></p> 71 <p> 72 All options for running BNC on Unix/Linux/Mac systems are saved in file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf, see annexed 'Configuration File' example. On Windows systems options are saved in register BKG_NTRIP_Client. The self-explaining contents of the configuration file or the Windows register can easily be edited. 73 </p> 71 74 <p> 72 75 3.1. <a href=#file>File</a><br> … … 118 121 3.12. <a href=#start>Start</a><br> 119 122 3.13. <a href=#stop>Stop</a><br> 120 3.14. <a href=#cmd>Command Line </a><br>121 3.14.1. <a href=#nw>No Window </a><br>122 3.14.2. <a href=#post>Offline </a><br>123 3.14. <a href=#cmd>Command Line Options</a><br> 124 3.14.1. <a href=#nw>No Window Mode</a><br> 125 3.14.2. <a href=#post>Offline Mode</a><br> 123 126 </p> 124 127 … … 132 135 Use smaller font size if the BNC main window exceeds the size of your screen. 133 136 </li> 134 <li> save selected options.<br> 135 Note that on Windows systems options are saved in register BKG_NTRIP_Client. On Unix/Linux systems options are saved in file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. 137 <li> save selected options in configuration file resp. Windows register.<br> 136 138 </li> 137 139 <li> … … 185 187 </p> 186 188 187 <p><a name="reconf"><h4>3.4.3 Reread Configuration - mandatory</h4></p>188 <p> 189 When operating BNC in online mode, some configuration parameters can be changed on-the-fly without interrupting the running process. For that BNC rereads parts of its configuration (see section 'Config File') in pre-defined intervals. Configuration parameters that can be changed on-the-fly are189 <p><a name="reconf"><h4>3.4.3 Reread Configuration - optional</h4></p> 190 <p> 191 When operating BNC online in window or 'no window' mode, some configuration options can be changed on-the-fly without interrupting the running process. Configuration options that can be changed on-the-fly are 190 192 </p> 191 193 <p> 192 194 <ul> 193 195 <li>'mountPoints' to change the selection of streams to be processed, see section 'Mountpoints',</li> 194 <li>'waitTime' to change the 'Wait for full epoch' parameter, see section 'Synchronized Observations', and</li>195 <li>'binSample' to change the 'Sampling' parameter, see section 'Synchronized Observations'.</li>196 <li>'waitTime' to change the 'Wait for full epoch' option, see section 'Synchronized Observations', and</li> 197 <li>'binSample' to change the 'Sampling' option, see section 'Synchronized Observations'.</li> 196 198 </ul> 197 199 </p> 198 200 <p> 199 Select '1 min', '1 hour', or '1 day' to let BNC reread the above mentioned configuration parameters every full minute, hour, or day and thus avoid usage of 'Start', 'Stop', or 'Quit' buttons. 201 <u>Window mode:</u> For changes while running BNC in window mode you interactively modify one of the above mentioned options and then hit 'Save Options'. Changes will immediately become effective without interrupting uninvolved threads. 202 </p> 203 <p> 204 <u>'No window' mode:</u> For changes while running BNC in 'no window' mode you force the program to rereads parts of its configuration in pre-defined intervals. Select '1 min', '1 hour', or '1 day' to let BNC reread the above mentioned configuration options every full minute, hour, or day. This avoids interrupting BNC through usage of 'Start', 'Stop', or 'Quit' buttons and lets probably edited configuration options become effective on-the-fly without interrupting uninvolved threads. See annexed section 'Configuration File' for a Unix/Linux/Mac configuration file example. 200 205 </p> 201 206 … … 302 307 <p><a name="rnxscript"><h4>3.5.6 Script - optional</h4></p> 303 308 <p> 304 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 RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux systems).309 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 RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux/Mac systems). 305 310 </p> 306 311 <p> … … 550 555 <p><a name="advscript"><h4>3.9.5 Advisory Script - optional </h4></p> 551 556 <p> 552 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.557 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/Mac systems) together with date and time information. 553 558 </p> 554 559 <p> … … 561 566 FFMJ0 End_Outage 08-02-21 11:36:02 Begin was 08-02-21 09:25:59 562 567 </pre> 563 Sample script for Unix/Linux systems:568 Sample script for Unix/Linux/Mac systems: 564 569 <pre> 565 570 #!/bin/bash … … 696 701 </p> 697 702 698 <p><a name="cmd"><h4>3.14. Command Line </h4></p>703 <p><a name="cmd"><h4>3.14. Command Line Options</h4></p> 699 704 <p> 700 Command line options are available to run BNC in 'no window' mode or let it read data from a file in 'offline' mode. 701 BNC will then use processing 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 that the self-explaining contents of the configuration file or the Windows register can easily be edited. 702 </p> 703 704 <p><a name="nw"><h4>3.14.1 No Window - optional</h4></p> 705 <p> 706 On all systems BNC can be started as a batch job with the command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems. 705 Command line options are available to run BNC in 'no window' mode or let it read data from a file in offline mode. BNC will then use processing options from the configuration file (Unix/Linux/Mac) or from the register BKG_NTRIP_Client (Windows). Note that the self-explaining contents of the configuration file or the Windows register can easily be edited. 706 </p> 707 708 <p><a name="nw"><h4>3.14.1 No Window Mode - optional</h4></p> 709 <p> 710 Apart from its regular windows mode, BNC can be started on all systems as a background/batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems. 707 711 </p> 708 712 <p> … … 711 715 </p> 712 716 713 <p><a name="post"><h4>3.14.2 Offline - optional</h4></p>714 <p> 715 Although BNC is a real-time tool, it can be run in 'offline'mode to read data from a file for post processing purposes. Enter the following four command line options for that:717 <p><a name="post"><h4>3.14.2 Offline Mode - optional</h4></p> 718 <p> 719 Although BNC is primarily a real-time online tool, it can be run in offline mode to read data from a file for post processing purposes. Enter the following four command line options for that: 716 720 </p> 717 721 <p> … … 727 731 </p> 728 732 <p> 729 Note that it is necessary to define a date and time for the first epoch because RTCM streams do not contain complete time stamps as needed for RINEX. Note further that when running BNC in 'offline'mode, it will use options for file saving, interval, sampling etc. from its configuration file.733 Note that it is necessary to define a date and time for the first epoch because RTCM streams do not contain complete time stamps as needed for RINEX. Note further that when running BNC in offline mode, it will use options for file saving, interval, sampling etc. from its configuration file. 730 734 </p> 731 735 … … 764 768 </li> 765 769 <li> 766 Once BNC has been started, its configuration can not be changed as long as it is stopped. A reconfiguration on-the-fly is not implemented.770 Once BNC has been started, many of its configuration options can not be changed as long as it is stopped. See chapter 'Reread Configuration' for on-the-fly configuration exceptions. 767 771 </li> 768 772 <br> … … 801 805 8.3. <a href=#rtigs>RTIGS</a><br> 802 806 8.3.1 <a href=#soc>SOC</a><br> 803 8.4. <a href=#config>Config File</a><br>807 8.4. <a href=#config>Configuration File</a><br> 804 808 8.5. <a href=#links>Links</a><br> 805 809 </p> … … 994 998 <p> 995 999 </p> 996 <p><a name="config"><h4>8.4. Config File</h4></p>997 <p> 998 The following is an example for the contents of a Unix/Linux configuration file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. It enables the retrieval of stream ACOR0 form www.euref-ip.net and FFMJ3 from www.igs-ip.net for the generation of 15 min RINEX files. RINEX files are uploaded to an archive using script 'up2archive' :1000 <p><a name="config"><h4>8.4. Configuration File</h4></p> 1001 <p> 1002 The following is an example for the contents of a Unix/Linux/Mac configuration file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. It enables the retrieval of stream ACOR0 form www.euref-ip.net and FFMJ3 from www.igs-ip.net for the generation of 15 min RINEX files. RINEX files are uploaded to an archive using script 'up2archive' : 999 1003 <pre> 1000 1004 [General] … … 1036 1040 </p> 1037 1041 <p> 1038 Note that on Windows systems configuration parameters are saved in register BKG_NTRIP_Client.1042 Note that on Windows systems configuration options are saved in register BKG_NTRIP_Client. 1039 1043 <p> 1040 1044
Note:
See TracChangeset
for help on using the changeset viewer.
