Changeset 1691 in ntrip


Ignore:
Timestamp:
Mar 3, 2009, 12:35:24 PM (15 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNS/bnshelp.html

    r1685 r1691  
    1010
    1111<p>
    12 BNS is released under the GNU General Public License (GPL). Binaries for BNS are available for Windows, 32-bit and 64-bit Linux (compiled under -m32 32-bit compatibility mode), Solaris, and Mac OS X systems. The MinGW compiler (Version 5.3.1) is used to produce the Windows binary. It is likely that BNS can be compiled on other systems where a GNU compiler and Qt Version 4.3.2 are available.
     12BNS is released under the GNU General Public License (GPL). Binaries for BNS are available for Windows, 32-bit and 64-bit Linux (compiled under -m32 32-bit compatibility mode), Solaris, and Mac OS X systems. The MinGW compiler (Version 5.3.1) is used to produce the Windows binary. It is likely that BNS can be compiled on other systems where a GNU compiler and Qt Version 4.4.3 are available.
    1313</p>
    1414
    … …  
    2222<a href=#purpose>1. Purpose</a><br>
    2323<a href=#function>2. Functioning</a><br>
    24 <a href=#resources>3. Resources</a><br>
     24<a href=#resources>3. Modes & Resources</a><br>
    2525<a href=#options>4. Options</a><br>
    2626<a href=#limits>5. Limitations</a><br>
    … …  
    7979</p>
    8080
    81 <p><a name="resources"><h3>3. Resources</h3></p>
    82 <p>
    83 The current size of the real-time stream produced by BNS is in the order of 5 kbits/sec depending on the number of visible satellites. When uploading the stream to an NTRIP Broadcaster, user needs to ensure that the connection used can sustain the required bandwidth.
    84 </p>
    85 <p>
    86 Running BNS requires the clock of the host computer to be properly synchronized.
     81<p><a name="resources"><h3>3. Modes & Resources</h3></p>
     82<p>
     83Apart from its regular window mode, BNS can be run as a background job in a 'no window' mode using processing options from previously saved configuration.
     84</p>
     85<p>
     86BNS requires access to the Internet with a minimum of about 1 kbits/sec per stream depending on the stream format and the number of visible satellites. You need to make sure that the connection can sustain the required bandwidth.
     87</p>
     88<p>
     89It requires the clock of the host computer to be properly synchronized.
    8790</p>
    8891
    … …  
    9093
    9194<p>
    92 All options for running BNS on Unix/Linux/Mac systems are saved in file ${HOME}/.config/BKG/BKG_NTRIP_Server.conf, see annexed 'Configuration File' example. On Windows systems options are saved in register BKG_NTRIP_Server. The self-explaining contents of the configuration file or the Windows register can easily be edited.
    93 </p>
    94 
    95 <p>
    96 4.1. <a href=#file>File</a><br>
    97 4.2. <a href=#help>Help</a><br>
    98 4.3. <a href=#proxy>Proxy</a><br>
    99 4.4. <a href=#general>General</a><br>
    100 &nbsp; &nbsp; &nbsp; 4.4.1. <a href=#logfile>Logfile</a><br>
    101 &nbsp; &nbsp; &nbsp; 4.4.2. <a href=#appfile>Append Files</a><br>
    102 4.5. <a href=#eph>RINEX Ephemeris</a><br>
    103 &nbsp; &nbsp; &nbsp; 4.5.1. <a href=#ephserver>Host & Port</a><br>
    104 &nbsp; &nbsp; &nbsp; 4.5.2. <a href=#ephsave>Save</a><br>
    105 4.6. <a href=#co>Clocks & Orbits</a><br>
    106 &nbsp; &nbsp; &nbsp; 4.6.1. <a href=#coport>Listening Port</a><br>
    107 &nbsp; &nbsp; &nbsp; 4.6.2. <a href=#cosave>Save</a><br>
    108 4.7. <a href=#ephc>Ephemeris Corrections</a><br>
    109 &nbsp; &nbsp; &nbsp; 4.7.1. <a href=#ephcserver>Host & Port</a><br>
    110 &nbsp; &nbsp; &nbsp; 4.7.2. <a href=#ephcmount>Mountpoint & Password</a><br>
    111 &nbsp; &nbsp; &nbsp; 4.7.3. <a href=#ephcsys>System</a><br>
    112 &nbsp; &nbsp; &nbsp; 4.7.4. <a href=#ephcsave>Save</a><br>
    113 4.8. <a href=#clkrnx>RINEX Clocks</a><br>
    114 &nbsp; &nbsp; &nbsp; 4.8.1. <a href=#clkdir>Directory</a><br>
    115 &nbsp; &nbsp; &nbsp; 4.8.2. <a href=#clkint>Interval & Sampling</a><br>
    116 4.9. <a href=#orb>SP3 Orbits</a><br>
    117 &nbsp; &nbsp; &nbsp; 4.9.1. <a href=#orbdir>Directory</a><br>
    118 &nbsp; &nbsp; &nbsp; 4.9.2. <a href=#orbint>Interval & Sampling</a><br>
    119 4.10. <a href=#start>Start</a><br>
    120 4.11. <a href=#stop>Stop</a><br>
    121 4.12. <a href=#nw>No Window</a>
    122 </p>
    123 
    124 <p><a name="file"><h4>4.1. File</h4></p>
     95This section describes BNS's top menu bar, its processing options and its bottom menu bar.
     96</p>
     97
     98<p>
     99The usual handling of BNS is that you first select severs for 'RINEX Ephemeris' and 'Clocks & Orbits'. You then select an NTRIP broadcaster for stream upload ('Broadcast Corrections') before you start the program ('Start'). Records of BNS's activities are shown in the'Logs' canvas in the middle of the main window.
     100</p>
     101
     102<p>
     103As a default, configuration files for running BNS on Unix/Linux/Mac systems are saved in directory '${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'. The default configuration file name is 'BNS.ini'.
     104</p>
     105
     106<p>
     107The default file name 'BNS.ini' can be changed and the file contents can easily be edited. On graphical user interfaces it is possible to Drag & Drop a configuration file icon to start BNS. See annexed 'Configuration Example' for a complete set of configuration options.
     108</p>
     109
     110<p>
     1114.1. <a href=#topmenu>Top Menu Bar</a><br>
     1124.1.1 <a href=#file>File</a><br>
     1134.1.2 <a href=#help>Help</a><br>
     1144.2. <a href=#proxy>Proxy</a><br>
     1154.3. <a href=#general>General</a><br>
     116&nbsp; &nbsp; &nbsp; 4.3.1. <a href=#logfile>Logfile</a><br>
     117&nbsp; &nbsp; &nbsp; 4.3.2. <a href=#appfile>Append Files</a><br>
     118&nbsp; &nbsp; &nbsp; 4.3.3. <a href=#genstart>Auto Start</a><br>
     1194.4. <a href=#eph>RINEX Ephemeris</a><br>
     120&nbsp; &nbsp; &nbsp; 4.4.1. <a href=#ephserver>Host & Port</a><br>
     121&nbsp; &nbsp; &nbsp; 4.4.2. <a href=#ephsave>Save</a><br>
     1224.5. <a href=#co>Clocks & Orbits</a><br>
     123&nbsp; &nbsp; &nbsp; 4.5.1. <a href=#coport>Listening Port</a><br>
     124&nbsp; &nbsp; &nbsp; 4.5.2. <a href=#cosave>Save</a><br>
     1254.6. <a href=#ephc>Broadcast Corrections</a><br>
     126&nbsp; &nbsp; &nbsp; 4.6.1. <a href=#ephcserver>Host & Port</a><br>
     127&nbsp; &nbsp; &nbsp; 4.6.2. <a href=#ephcmount>Mountpoint & Password</a><br>
     128&nbsp; &nbsp; &nbsp; 4.6.3. <a href=#ephcsys>System</a><br>
     129&nbsp; &nbsp; &nbsp; 4.6.4. <a href=#ephcsave>Save</a><br>
     1304.7. <a href=#clkrnx>RINEX Clocks</a><br>
     131&nbsp; &nbsp; &nbsp; 4.7.1. <a href=#clkdir>Directory</a><br>
     132&nbsp; &nbsp; &nbsp; 4.7.2. <a href=#clkint>Interval & Sampling</a><br>
     1334.8. <a href=#orb>SP3 Orbits</a><br>
     134&nbsp; &nbsp; &nbsp; 4.8.1. <a href=#orbdir>Directory</a><br>
     135&nbsp; &nbsp; &nbsp; 4.8.2. <a href=#orbint>Interval & Sampling</a><br>
     1364.9. <a href=#bottom>Bottom Menu Bar</a><br>
     1374.9.1 <a href=#start>Start</a><br>
     1384.9.2 <a href=#stop>Stop</a><br>
     1394.10. <a href=#cmd>Command Line Options</a><br>
     1404.10.1 <a href=#nw>No Window</a><br>
     1414.10.2 <a href=#conffile>Configuration File</a>
     142</p>
     143
     144<p><a name="topmenu"><h4>4.1. Top Menu Bar</h4></p>
     145<p>
     146The top menu bar allows to select a font for the BNS windows, save configured options or quit
     147 the program execution. It also provides access to a program documentation.
     148</p>
     149
     150<p><a name="file"><h4>4.1.1 File</h4></p>
    125151
    126152<p>
    … …  
    131157Use smaller font size if the BNS main window extends beyond the size of your screen.
    132158</li>
    133 <li> save selected options.<br>
    134 Note that on Windows systems options are saved in register BKG_NTRIP_Server. On Unix/Linux/Mac systems options are saved in file ${HOME}/.config/BKG/BKG_NTRIP_Server.conf.
     159<li> save selected options in configuration file.
    135160</li>
    136161<li>
    … …  
    140165</p>
    141166
    142 <p><a name="help"><h4>4.2. Help</h4></p>
     167<p><a name="help"><h4>4.1.2 Help</h4></p>
    143168
    144169<p>
    … …  
    162187</p>
    163188
    164 <p><a name="proxy"><h4>4.3. Proxy - for usage in a protected LAN</h4></p>
    165 
    166 <p>
    167 If you are running BNS within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNC. If you don't know the address and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.
     189<p><a name="proxy"><h4>4.2. Proxy - for usage in a protected LAN</h4></p>
     190
     191<p>
     192If you are running BNS within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNS. If you don't know the address and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.
    168193</p>
    169194<p>
    170195Note that IP streaming is often not allowed in a LAN. In this case you need to ask your network administrator for an appropriate modification of the local security policy or for the installation of a TCP relay to the NTRIP Casters. If these are not possible, you might need to run BNS outside your LAN on a host that has unobstructed connection to the Internet.
    171196</p>
    172 <p><a name="general"><h4>4.4. General Options</h4></p>
    173 
    174 <p><a name="logfile"><h4>4.4.1 Logfile - optional</h4></p>
    175 <p>
    176 Records of BNC's activities are shown in the Log section on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Log (full path)' field. The message log covers the communication status between BNC and the NTRIP broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Log (full path)' is an empty option field, meaning that BNC logs will not saved into a file.
    177 </p>
    178 
    179 <p><a name="appfile"><h4>4.4.2 Append Files</h4></p>
     197<p><a name="general"><h4>4.3. General Options</h4></p>
     198<p>
     199The following describes general settings for BNC's logfile, file handling and auto-start.
     200</p>
     201
     202<p><a name="logfile"><h4>4.3.1 Logfile - optional</h4></p>
     203<p>
     204Records of BNS's activities are shown in the Log section on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Log (full path)' field. The message log covers the communication status between BNS and the NTRIP broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Log (full path)' is an empty option field, meaning that BNS logs will not saved into a file.
     205</p>
     206
     207<p><a name="appfile"><h4>4.3.2 Append Files</h4></p>
    180208<p>
    181209When BNS is started, new files are created by default and any existing files with the same name will be overwritten. However, users might want to append existing files following a restart of BNS, a system crash or when BNS had crashed. Tick 'Append files' to continue with existing files and keep what has been recorded so far. Note that option 'Append files' affects all types of files created by BNS.
    182210</p>
    183211
    184 <p><a name="eph"><h4>4.5. RINEX Ephemeris</h4></p>
     212<p><a name="genstart"><h4>4.3.3 Auto Start - optional</h4></p>
     213<p>
     214You may like to auto-start BNS at startup time in window mode with preassigned configuration options. This may be required i.e. immediately after booting your system. Tick 'Autostart' to supersede the usage of the 'Start' button. Make sure that you maintain a link to BNS for that in your Autostart directory (Windows systems) or call BNS in a script below directory /etc/init.d (Unix/Linux/Mac systems).
     215</p>
     216
     217<p><a name="eph"><h4>4.4. RINEX Ephemeris</h4></p>
    185218<p>
    186219BNS requires GNSS Broadcast Ephemeris in RINEX Version 3 Navigation file format from an IP address and port. This information can be provided in real-time by the 'BKG Ntrip Client' (BNC) program. Note that whenever a new set of Broadcast Ephemeris becomes available, BNS needs it immediately.
    … …  
    208241</p>
    209242
    210 <p><a name="ephserver"><h4>4.5.1 Host & Port - mandatory</h4></p>
     243<p><a name="ephserver"><h4>4.4.1 Host & Port - mandatory</h4></p>
    211244<p>
    212245Enter the IP address and port number of a Broadcast Ephemeris server like BNC to establish a persistent socket connection, see section 'Flow Chart' under 'Help' for socket communication details. If BNS runs on the same host as BNC, 127.0.0.1 should be used as the server's IP address. Make sure that this server is up and running before you start BNS.
    213246</p>
    214247
    215 <p><a name="ephsave"><h4>4.5.2 Save - optional</h4></p>
     248<p><a name="ephsave"><h4>4.4.2 Save - optional</h4></p>
    216249</p>
    217250Specify the full path to a file where received Broadcast Ephemeris will be logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
    218251</p>
    219252
    220 <p><a name="co"><h4>4.6. Clocks & Orbits</h4></p>
     253<p><a name="co"><h4>4.5. Clocks & Orbits</h4></p>
    221254<p>
    222255BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system in SP3 format. They can be provided by a real-time GNSS engine such as RTNet. The sampling rate should not be much greater than 10 sec. Note that otherwise in IP streaming involved tools on the NTRIP Broadcaster or client side may respond with a timeout.
    … …  
    263296</p>
    264297
    265 <p><a name="coport"><h4>4.6.1 Listening Port - mandatory</h4></p>
     298<p><a name="coport"><h4>4.5.1 Listening Port - mandatory</h4></p>
    266299<p>
    267300BNS is listening at an IP port for incoming GNSS clocks and orbits in SP3 format. Enter the respective IP port number to setup a server socket for incoming data, see section 'Flow Chart' under 'Help' for socket communication details. Make sure that the software providing clocks and orbits is up and running before you start BNS.
    268301</p>
    269302
    270 <p><a name="cosave"><h4>4.6.2 Save - optional</h4></p>
     303<p><a name="cosave"><h4>4.5.2 Save - optional</h4></p>
    271304<p>
    272305Specify the full path to a file where received clocks and orbits from a real-time engine will be logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
    273306</p>
    274307
    275 <p><a name="ephc"><h4>4.7. Ephemeris Corrections</h4></p>
     308<p><a name="ephc"><h4>4.6. Broadcast Corrections</h4></p>
    276309<p>
    277310BNS 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.
    278311</p>
    279312<p>
    280 BNS allows to configure two Ephemeris Corrections streams refering do different reference systems for upload to different NTRIP broadcasters. You may use this functionality for parallel support of a backup NTRIP broadcaster or for simultaneous support of two reference systems.
     313BNS allows to configure two Broadcast Corrections streams refering do different reference systems for upload to different NTRIP broadcasters. You may use this functionality for parallel support of a backup NTRIP broadcaster or for simultaneous support of two reference systems.
    281314</p>
    282315
    … …  
    285318</p>
    286319
    287 <p><a name="ephcserver"><h4>4.7.1 Host & Port - optional</h4></p>
     320<p><a name="ephcserver"><h4>4.6.1 Host & Port - optional</h4></p>
    288321<p>
    289322Enter the NTRIP Caster's 'Host' IP name or number for stream upload.
    … …  
    293326</p>
    294327
    295 <p><a name="ephcmount"><h4>4.7.2 Mountpoint & Password - mandatory if 'Host' is set</h4></p>
     328<p><a name="ephcmount"><h4>4.6.2 Mountpoint & Password - mandatory if 'Host' is set</h4></p>
    296329<p>
    297330Each stream on an NTRIP Caster is defined using a unique source ID called mountpoint. An NTRIP Server like BNS upload a stream to the Caster by referring to a dedicated mountpoint that has been set by the Caster operator. Specify here the mountpoint based on the detail you received from the operator for your stream. It is often a four character ID (capital letters) plus an integer number.
    … …  
    301334</p>
    302335
    303 <p><a name="ephcsys"><h4>4.7.3 System - mandatory if 'Host' is set</h4></p>
     336<p><a name="ephcsys"><h4>4.6.3 System - mandatory if 'Host' is set</h4></p>
    304337<p>
    305338BNS refers its clock and orbit corrections to a specific reference system. Available options are
    … …  
    341374
    342375
    343 <p><a name="ephcsave"><h4>4.7.4 Save - optional</h4></p>
     376<p><a name="ephcsave"><h4>4.6.4 Save - optional</h4></p>
    344377<p>
    345378The clock and orbit corrections streamed by BNS to the NTRIP Caster can be logged locally. Specify a full 'Save stream' path here to save this information to a local file. Default value for 'Save stream' is an empty option field, meaning that logging is disabled.
    … …  
    378411</p>
    379412
    380 <p><a name="clkrnx"><h4>4.8. RINEX Clocks</h4></p>
     413<p><a name="clkrnx"><h4>4.7. RINEX Clocks</h4></p>
    381414<p>
    382415The clock corrections generated by BNS can be logged separately in Clock RINEX format. The file naming follows the RINEX convention.
    383 </p>
    384 
    385 <p><a name="clkdir"><h4>4.8.1 Directory - optional</h4></p>
     416<p>
     417
     418</p>
     419Note that clocks in the Clock RINEX files are not corrected for the 2nd-order relativistic effect.
     420</p>
     421
     422<p><a name="clkdir"><h4>4.7.1 Directory - optional</h4></p>
    386423<p>
    387424Here you can specify the path to where the Clock RINEX files will be stored. If the specified directory does not exist, BNS will not create Clock RINEX files. Default value for 'Directory' is an empty option field, meaning that logging of Clock RINEX files is disabled.
    388425</p>
    389426
    390 <p><a name="clkint"><h4>4.8.2 Interval & Sampling - mandatory if 'Directory' is set</h4></p>
     427<p><a name="clkint"><h4>4.7.2 Interval & Sampling - mandatory if 'Directory' is set</h4></p>
    391428<p>
    392429Select the length of the Clock RINEX file generated. The default value is 1 day.
    … …  
    397434</p>
    398435
    399 <p><a name="orb"><h4>4.9. SP3 Orbits</h4></p>
     436<p><a name="orb"><h4>4.8. SP3 Orbits</h4></p>
    400437<p>
    401438The orbit corrections generated by BNS can be logged separately in SP3 Orbit files. The file naming follows the IGS convention.
    402439</p>
    403 
    404 <p><a name="orbdir"><h4>4.9.1 Directory - optional</h4></p>
     440</p>
     441Note that clocks in the SP3 Orbit files are not corrected for the 2nd-order relativistic effect.
     442</p>
     443
     444<p><a name="orbdir"><h4>4.8.1 Directory - optional</h4></p>
    405445<p>
    406446Here you can specify the path to where the SP3 Orbit files will be stored. If the specified directory does not exist, BNS will not create SP3 Orbit files. Default value for 'Directory' is an empty option field, meaning that logging of SP3 Orbit files is disabled.
    407447</p>
    408448
    409 <p><a name="orbint"><h4>4.9.2 Interval & Sampling - mandatory if 'Directory' is set</h4></p>
     449<p><a name="orbint"><h4>4.8.2 Interval & Sampling - mandatory if 'Directory' is set</h4></p>
    410450<p>
    411451Select the length of the SP3 Orbit file generated. The default value is 1 day.
    … …  
    415455</p>
    416456
    417 <p><a name="start"><h4>4.10. Start</h4></p>
     457<p><a name="bottom"><h4>4.9. Bottom Menu Bar</h4></p>
     458<p>
     459The bottom menu bar allows to start or stop the execution of BNS and provides access the BNC's online help funtion.
     460</p>
     461
     462<p><a name="start"><h4>4.9.1 Start</h4></p>
    418463<p>
    419464Hit 'Start' to start receiving IGS orbits and clocks and convert them into corrections to Broadcast Ephemeris. Note that when started BNS by default will begin with new files which might overwrite existing files when necessary unless the option 'Append files' is ticked.
    420465</p>
    421466
    422 <p><a name="stop"><h4>4.11. Stop</h4></p>
     467<p><a name="stop"><h4>4.9.2 Stop</h4></p>
    423468<p>
    424469Hit the 'Stop' button in order to stop BNS.
    425470</p>
    426471
    427 <p><a name="nw"><h4>4.12. No Window - optional</h4></p>
    428 <p>
    429 On all systems BNS can be started in batch mode with the command line option '-nw'. BNS will then run in 'no window' mode, using options from the configuration file ${HOME}/.config/BKG/BNC_NTRIP_Server.conf (Unix/Linux/Mac, see 'Configuration File' example in the Annex) or from the register BKG_NTRIP_Server (Windows).
    430 </p>
    431 <p>
    432 The self-explanatory contents of the configuration file or the Windows registry can easily be edited. Before editing, terminate BNS first using Windows Task Manager when running it in 'no window' mode on Windows systems.
     472<p><a name="cmd"><h4>4.10. Command Line Options</h4></p>
     473<p>
     474Command line options are available to run BNS in 'no window' mode or let it read a specific configuration file. Note that the self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration file name instead of using the default name 'BNS.ini'.
     475</p>
     476
     477<p><a name="nw"><h4>4.10.1 No Window - optional</h4></p>
     478<p>
     479Apart from its regular windows mode, BNS can be started on all systems as a background/batch job with command line option '-nw'. BNS will then run in 'no window' mode, using processing options from its configuration file on disk. Terminate BNS using Windows Task Manager when running it in 'no window' mode on Windows systems.
     480</p>
     481<p>
     482Example:<br><br>
     483bns.exe -nw
     484</p>
     485
     486<p><a name="conffile"><h4>4.10.2 Configuration File - optional</h4></p>
     487The default configuration file name is 'BNS.ini'. You may change this name at startup time using the command line option '--conf &#060;<u>confFileName</u>&#062;'. This allows to run several BNS jobs in parallel on the same host using different sets of configuration options. <u>confFileName</u> stands either for the full path to a configuration file or just for a file name. If you introduce only a filename, the corresponding file will be saved in the current working directory from where BNS is started.
     488</p>
     489<p>
     490Example:<br><br>
     491./bns --conf MyConfig.ini
     492</p>
     493<p>
     494This leads to a BNS job using configuration file 'MyConfig.ini'. The configuration file will be saved in the current working directory.
     495</p>
     496
     497
    433498</p>
    434499<p><a name="limits"><h3>5. Limitations</h3></p>
    … …  
    465530&nbsp; &nbsp; &nbsp; 7.2.1 RTCM <a href=#ntrip>NTRIP</a><br>
    466531&nbsp; &nbsp; &nbsp; 7.2.2 RTCM <a href=#rtcm3>Version 3.x</a><br>
    467 7.3. <a href=#config>Configuration File</a><br>
     5327.3. <a href=#config>Configuration Example</a><br>
    4685337.4. <a href=#links>Links</a><br>
    469534</p>
    … …  
    473538<table>
    474539<tr></tr>
    475 <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>
     540
     541<tr>
     542<td>Dec 2008 &nbsp;</td><td>Version 1.0 &nbsp;</td>
     543<td>[Add] Source code and binaries published.</td>
     544</tr>
     545
     546<tr>
     547<td>Mar 2009 &nbsp;</td><td>Version 1.1 &nbsp;</td>
     548<td>[Add] New messages for URA and high-rate clocks.<br> [Add] Upgrade to Qt Version 4.4.3<br> [Add] Enable/disable tab widgets<br> [Add] User defined configuration file name<br> [mod] Switch to configuration files in ini-Format<br> [Add] Auto start<br> [Add] Drag and drop ini files</td>
     549</tr>
     550
    477551</table>
    478552</p>
    … …  
    537611</p>
    538612
    539 <p><a name="config"><h4>7.3. Configuration File</h4></p>
    540 <p>
    541 The following is an example of the contents of a Unix/Linux/Mac configuration file ${HOME}/.config/BKG/BKG_NTRIP_Server.conf. It enables the upload of streams CLCK1 and CLCK2 to www.igs-ip.net. Clock RINEX files and SP3 Orbit files are saved to a directory /home/weber/rinex :
    542 </p>
    543 <p>
    544 <pre>
    545 [General]
    546 clkPort=7000
    547 ephEcho=/home/weber/rinex/eph.rnx
    548 ephHost=clock-ip.bkg.bund.de
    549 ephPort=6000
    550 fileAppend=0
    551 font="Helvetica [Adobe],8,-1,5,75,0,0,0,0,0"
    552 inpEcho=/home/weber/rinex/ClocksOrbits.dat
    553 logFile=/home/weber/rinex/bns.log
    554 mountpoint_1=CLCK1
    555 mountpoint_2=CLCK2
    556 outFile_1=/home/weber/rinex/CLCK1
    557 outFile_2=/home/weber/rinex/CLCK2
    558 beClocks1=
    559 beClocks2=
    560 outHost=www.igs-ip.net
    561 outPort=2101
    562 password=serverPass
    563 proxyHost=
    564 proxyPort=
    565 refSys_1=IGS05
    566 refSys_2=ETRS89
    567 rnxIntr=1 day
    568 rnxPath=/home/weber/rinex
    569 rnxSampl=30
    570 sp3Intr=1 day
    571 sp3Path=/home/weber/rinex
    572 sp3Sampl=300
     613<p><a name="config"><h4>7.3. Configuration Example</h4></p>
     614<p>
     615The following table's left column is an example for the contents of a configuration file 'BNS.ini'. It enables the upload of streams CLCK1 and CLCK2 to www.igs-ip.net. Clock RINEX files and SP3 Orbit files are saved to a directory /home/weber/rinex :
     616</p>
     617<table>
     618<tr></tr>
     619<tr><td><b>Option</b></td><td><b>Affiliation</b></td></tr>
     620<tr><td>[General]</td><td>Settings: Group</td></tr>
     621<tr><td>proxyHost=</td><td>Proxy: Host</td></tr>
     622<tr><td>proxyPort=</td><td>Proxy: Port</td></tr>
     623<tr><td>logFile=/home/weber/rinex/bns.log</td><td>General: Logfile (full path)</td></tr>
     624<tr><td>fileAppend=0</td><td>General: Append files</td></tr>
     625<tr><td>font="Helvetica [Adobe],8,-1,5,75,0,0,0,0,0"</td><td>Internal memory: Used font</td></tr>
     626<tr><td>refSys_1=IGS05</td><td>Broadcast Corrections I: System</td></tr>
     627<tr><td>refSys_2=ETRF2000</td><td>Broadcast Corrections II: System</td></tr>
     628<tr><td>inpEcho=/home/weber/rinex/ClocksOrbits.dat</td><td>Clocks & Orbits: Save (full path)</td></tr>
     629<tr><td>ephHost=clock-ip.bkg.bund.de</td><td>RINEX Ephemeris: Host</td></tr>
     630<tr><td>ephPort=6000</td><td>RINEX Ephemeris: Port</td></tr>
     631<tr><td>ephEcho=/home/weber/rinex/eph.rnx</td><td>RINEX Ephemeris: Save (full path)</td></tr>
     632<tr><td>clkPort=7000</td><td>Clocks & Orbits: Listening port</td></tr>
     633<tr><td>outHost1=www.igs-ip.net</td><td>Broadcast Corrections I: Host</td></tr>
     634<tr><td>outPort1=2101</td><td>Broadcast Corrections I: Port</td></tr>
     635<tr><td>outHost2=www.euref-ip.net</td><td>Broadcast Corrections II: Host</td></tr>
     636<tr><td>outPort2=2101</td><td>Broadcast Corrections II: Port</td></tr>
     637<tr><td>mountpoint_1=CLCK1</td><td>Broadcast Corrections I: Mountpoint</td></tr>
     638<tr><td>mountpoint_2=CLCK2</td><td>Broadcast Corrections II: Mountpoint</td></tr>
     639<tr><td>outFile_1=/home/weber/rinex/CLCK1</td><td>Broadcast Corrections I: Save (full path)</td></tr>
     640<tr><td>outFile_2=/home/weber/rinex/CLCK2</td><td>Broadcast Corrections II: Save (full path)</td></tr>
     641<tr><td>password1=pw1</td><td>Broadcast Corrections I: Password</td></tr>
     642<tr><td>password2=pw2</td><td>Broadcast Corrections I: Password</td></tr>
     643<tr><td>rnxPath=/home/weber/rinex</td><td>RINEX Clocks: Directory</td></tr>
     644<tr><td>rnxIntr=1 day</td><td>RINEX Clocks: Interval</td></tr>
     645<tr><td>rnxSampl=30</td><td>RINEX Clocks: Sampling</td></tr>
     646<tr><td>sp3Path=/home/weber/rinex</td><td>SP3 Orbits: Directory</td></tr>
     647<tr><td>sp3Intr=1 day</td><td>SP3 Orbits: Interval</td></tr>
     648<tr><td>sp3Sampl=300</td><td>SP3 Orbits: Sampling</td></tr>
     649<tr><td>startTab=0</td><td>Internal memory: Top tab</td></tr>
     650<tr><td>autoStart=0</td><td>General: Auto start</td></tr>
     651<tr><td>beClocks1=0</td><td>Broadcast Corrections I: Broadcast clocks</td></tr>
     652<tr><td>beClocks2=0</td><td>Broadcast Corrections I: Broadcast clocks</td></tr>
    573653</pre>
    574654</p>
Note: See TracChangeset for help on using the changeset viewer.