- Timestamp:
- Sep 2, 2008, 1:36:17 AM (16 years ago)
- File:
-
- 1 edited
-
trunk/BNS/bnshelp.html (modified) (9 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNS/bnshelp.html
r1019 r1090 98 98 4.4.1. <a href=#logfile>Logfile</a><br> 99 99 4.4.2. <a href=#appfile>Append Files</a><br> 100 4.4.3. <a href=#refsystem>Reference System</a><br> 101 4.5. <a href=#input>Input</a><br> 102 4.5.1. <a href=#ephemeris>Ephemeris</a><br> 103 4.5.2. <a href=#clocks>Clocks & Orbits</a><br> 104 4.5.3. <a href=#saveclk>Save Clocks & Orbits</a><br> 105 4.6. <a href=#caster>NTRIP Caster</a><br> 106 4.6.1. <a href=#cashost>Host & Port</a><br> 107 4.6.2. <a href=#casmount>Mountpoint & Password</a><br> 108 4.6.3. <a href=#casstream>Save Stream</a><br> 109 4.7. <a href=#rnxclk>RINEX Clocks</a><br> 110 4.7.1. <a href=#clkdir>Directory</a><br> 111 4.7.2. <a href=#clkint>Interval & Sampling</a><br> 112 4.8. <a href=#orbits>SP3 Orbits</a><br> 113 4.8.1. <a href=#orbdir>Directory</a><br> 114 4.8.2. <a href=#orbint>Interval & Sampling</a><br> 115 4.9 <a href=#start>Start</a><br> 116 4.10. <a href=#stop>Stop</a><br> 117 4.11. <a href=#nw>No Window</a> 100 4.5. <a href=#eph>RINEX Ephemeris</a><br> 101 4.5.1. <a href=#ephserver>Host & Port</a><br> 102 4.5.2. <a href=#ephsave>Save</a><br> 103 4.6. <a href=#co>Clocks & Orbits</a><br> 104 4.6.1. <a href=#coport>Listening Port</a><br> 105 4.6.2. <a href=#cosave>Save</a><br> 106 4.7. <a href=#ephc>Ephemeris Corrections</a><br> 107 4.7.1. <a href=#ephcserver>Host & Port, Password</a><br> 108 4.7.2. <a href=#ephcmount>Mountpoint</a><br> 109 4.7.3. <a href=#ephcsys>System</a><br> 110 4.7.4. <a href=#ephcsave>Save</a><br> 111 4.8. <a href=#clkrnx>RINEX Clocks</a><br> 112 4.8.1. <a href=#clkdir>Directory</a><br> 113 4.8.2. <a href=#clkint>Interval & Sampling</a><br> 114 4.9. <a href=#orb>SP3 Orbits</a><br> 115 4.9.1. <a href=#orbdir>Directory</a><br> 116 4.9.2. <a href=#orbint>Interval & Sampling</a><br> 117 4.10. <a href=#start>Start</a><br> 118 4.11. <a href=#stop>Stop</a><br> 119 4.12. <a href=#nw>No Window</a> 118 120 </p> 119 121 … … 178 180 </p> 179 181 180 <p><a name="refsystem"><h4>4.4.3 Reference System - mandatory</h4></p> 181 <p> 182 BNS refers its final clock and orbit corrections to a specific reference system. Available options are 183 <p> 184 <ul> 185 <li>IGS05 which stands for the GNSS-based IGS realization of the International Terrestrial Reference Frame (ITRF2005), and</li> 186 <li>ETRS89 which stands for the European Terrestrial Reference System 1989 adopted by EUREF.</li> 187 </ul> 188 </p> 189 <p> 190 <u>IGS05:</u> 191 As the clocks and orbits coming from real-time GNSS engine are expected to be in the IGS05 system, no transformation is carried out if this option is selected. 192 </p> 193 <p> 194 <u>ETRS89:</u> 195 From the complete transformation chain 'IGS05->ITRF2005->ITRF2000->ETRS89' only the transformation 'ITRF2000->ETRS89' has been implemented. The formulas for that are taken from 'Boucher and Altamimi 2007: Specifications for reference frame fixing in the analysis of EUREF GPS campaign', see <u>http://etrs89.ensg.ign.fr/memo2007.pdf</u>. The following 6 Helmert transformation parameters were introduced: 196 </p> 197 <p> 198 <pre> 199 Translation in X: 0.054 m 200 Translation in Y: 0.051 m 201 Translation in Z: -0.048 m 202 Rotation in X: 0.081 mas/y 203 Rotation in Y: 0.490 mas/y 204 Rotation in Z: -0.792 mas/y 205 </pre> 206 </p> 207 <p> 208 Note that the neglect of transformations 'IGS05->ITRF2005->ITRF2000' in BNS may cause discrepancies up to a maximum of 2 centimenters. 209 <p> 210 211 <p><a name="input"><h4>4.5. Input</h4></p> 212 <p> 213 BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and Broadcast Ephemeris in RINEX Navigation file format. 214 </p> 215 216 <p><a name="ephemeris"><h4>4.5.1 Ephemeris - mandatory</h4></p> 217 <p> 218 BNS reads 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, it has to be transmitted immediately. Enter the respective servers IP address and port number 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. 219 </p> 220 </p> 221 The following is an example of Broadcast Ephemeris records in RINEX Version 3 Navigation file format for satellite GPS PRN32 and GLONASS PRN04: 182 <p><a name="eph"><h4>4.5. RINEX Ephemeris</h4></p> 183 <p> 184 BNS 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. 185 </p> 186 187 <p><a name="ephserver"><h4>4.5.1 Host & Port - mandatory</h4></p> 188 <p> 189 Enter 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. 190 </p> 191 192 <p><a name="ephsave"><h4>4.5.2 Save - optional</h4></p> 193 </p> 194 Specify the full path to a file where received Broadcast Ephemeris will logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled. 195 </p> 196 <p> 197 The following is an example log of Broadcast Ephemeris records in RINEX Version 3 Navigation file format for satellite GPS PRN32 and GLONASS PRN04: 222 198 </p> 223 199 … … 239 215 </p> 240 216 241 <p><a name="clocks"><h4>4.5.2 Clocks & Orbits - mandatory</h4></p> 242 <p> 243 BNS is listening at an IP port for incoming GNSS clocks and orbits in a plain ASCII format. They can be provided by a real-time GNSS engine such as RTNet and are expected to refer to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. 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. 244 </p> 245 <p> 246 Below you will find an example of precise clocks and orbits coming in plain ASCII format from a real-time GNSS engine. Each epoch starts with an asterisk character followed by GPS Week, Second in GPS Week and Number of satellites. Subsequent records provide the following set of parameters for each satellite: 217 <p><a name="co"><h4>4.6. Clocks & Orbits</h4></p> 218 <p> 219 BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. They can be provided by a real-time GNSS engine such as RTNet and are expected to refer to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. 220 </p> 221 222 <p><a name="coport"><h4>4.6.1 Listening Port - mandatory</h4></p> 223 <p> 224 BNS is listening at an IP port for incoming GNSS clocks and orbits in a plain ASCII 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. 225 </p> 226 227 <p><a name="cosave"><h4>4.6.2 Save - optional</h4></p> 228 <p> 229 Specify the full path to a file where received clocks and orbits from a real-time engine will logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled. 230 </p> 231 232 <p> 233 Below you find an example of precise clocks and orbits coming in plain ASCII format from a real-time GNSS engine. Each epoch starts with an asterisk character followed by GPS Week, Second in GPS Week and Number of satellites. Subsequent records provide the following set of parameters for each satellite: 247 234 </p> 248 235 … … 290 277 </p> 291 278 292 <p><a name="saveclk"><h4>4.5.3 Save Clocks & Orbits - optional</h4></p> 293 <p> 294 Specify the full path to a file where received clocks and orbits from a real-time engine will logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.</p> 295 296 <p><a name="caster"><h4>4.6. NTRIP Caster</h4></p> 297 <p> 298 BNS can upload the resulting stream of cock 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 thentative message Types 4056 and 4057 for combined GPS and GLONASS clock and orbit corrections. 299 300 <p><a name="cashost"><h4>4.6.1 Host & Port - optional</h4></p> 279 <p><a name="ephc"><h4>4.7. Ephemeris Corrections</h4></p> 280 <p> 281 BNS 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 thentative message Types 4056 and 4057 for combined GPS and GLONASS clock and orbit corrections. 282 </p> 283 284 <p><a name="ephcserver"><h4>4.7.1 Host & Port, Password - optional</h4></p> 301 285 <p> 302 286 Enter the NTRIP Caster's 'Host' IP name or number for stream upload. … … 305 289 Enter the NTRIP Caster's IP 'Port' number for stream upload. Note that NTRIP Casters are often configured to provide access on more than one port, usually port 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s). 306 290 </p> 307 308 <p><a name="casmount"><h4>4.6.2 Mountpoint & Password - mandatory if 'Host' is set</h4></p> 291 </p> 292 In NTRIP Version 1.0 stream upload may be protected through an upload 'Password'. Enter the password you received from the Caster operator along with the mountpoint(s). 293 </p> 294 295 <p><a name="ephcmount"><h4>4.7.2 Mountpoint - mandatory if 'Host' is set</h4></p> 309 296 <p> 310 297 Each 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. 311 298 <p> 312 </p> 313 In NTRIP Version 1.0 stream upload is only protected through a generic upload 'Password'. Enter the password you received from the Caster operator along with the mountpoint. 314 </p> 315 316 <p><a name="casstream"><h4>4.6.3 Save Stream - optional</h4></p> 299 300 <p><a name="ephcsys"><h4>4.7.3 Reference System - mandatory if 'Host' is set</h4></p> 301 <p> 302 BNS refers its final clock and orbit corrections to a specific reference system. Available options are 303 <p> 304 <ul> 305 <li>IGS05 which stands for the GNSS-based IGS realization of the International Terrestrial Reference Frame (ITRF2005), and</li> 306 <li>ETRS89 which stands for the European Terrestrial Reference System 1989 adopted by EUREF.</li> 307 </ul> 308 </p> 309 310 <p> 311 <u>IGS05:</u> 312 As the clocks and orbits coming from real-time GNSS engine are expected to be in the IGS05 system, no transformation is carried out if this option is selected. 313 </p> 314 <p> 315 <u>ETRS89:</u> 316 From the complete transformation chain 'IGS05->ITRF2005->ITRF2000->ETRS89' only the transformation 'ITRF2000->ETRS89' has been implemented. The formulas for that are taken from 'Boucher and Altamimi 2007: Specifications for reference frame fixing in the analysis of EUREF GPS campaign', see <u>http://etrs89.ensg.ign.fr/memo2007.pdf</u>. The following 6 Helmert transformation parameters were introduced: 317 </p> 318 <p> 319 <pre> 320 Translation in X: 0.054 m 321 Translation in Y: 0.051 m 322 Translation in Z: -0.048 m 323 Rotation in X: 0.081 mas/y 324 Rotation in Y: 0.490 mas/y 325 Rotation in Z: -0.792 mas/y 326 </pre> 327 </p> 328 <p> 329 Note that the neglect of transformations 'IGS05->ITRF2005->ITRF2000' in BNS may cause discrepancies up to a maximum of 2 centimenters. 330 <p> 331 332 333 <p><a name="ephcsave"><h4>4.7.4 Save - optional</h4></p> 317 334 <p> 318 335 The 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. … … 351 368 </p> 352 369 353 <p><a name=" rnxclk"><h4>4.7. RINEX Clocks</h4></p>370 <p><a name="clkrnx"><h4>4.8. RINEX Clocks</h4></p> 354 371 <p> 355 372 The clock corrections generated by BNS can be logged separately in Clock RINEX format. The file naming follows the RINEX convention. 356 373 </p> 357 374 358 <p><a name="clkdir"><h4>4. 7.1 Directory - optional</h4></p>375 <p><a name="clkdir"><h4>4.8.1 Directory - optional</h4></p> 359 376 <p> 360 377 Here 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. 361 378 </p> 362 379 363 <p><a name="clkint"><h4>4. 7.2 Interval & Sampling - mandatory if 'Directory' is set</h4></p>380 <p><a name="clkint"><h4>4.8.2 Interval & Sampling - mandatory if 'Directory' is set</h4></p> 364 381 <p> 365 382 Select the length of the Clock RINEX file generated. The default value is 1 day. … … 370 387 </p> 371 388 372 <p><a name="orb its"><h4>4.8. SP3 Orbits</h4></p>389 <p><a name="orb"><h4>4.9. SP3 Orbits</h4></p> 373 390 <p> 374 391 The orbit corrections generated by BNS can be logged separately in SP3 Orbit files. The file naming follows the IGS convention. 375 392 </p> 376 393 377 <p><a name="orbdir"><h4>4. 8.1 Directory - optional</h4></p>394 <p><a name="orbdir"><h4>4.9.1 Directory - optional</h4></p> 378 395 <p> 379 396 Here 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. 380 397 </p> 381 398 382 <p><a name="orbint"><h4>4. 8.2 Interval & Sampling - mandatory if 'Directory' is set</h4></p>399 <p><a name="orbint"><h4>4.9.2 Interval & Sampling - mandatory if 'Directory' is set</h4></p> 383 400 <p> 384 401 Select the length of the SP3 Orbit file generated. The default value is 1 day. … … 388 405 </p> 389 406 390 <p><a name="start"><h4>4. 9. Start</h4></p>407 <p><a name="start"><h4>4.10. Start</h4></p> 391 408 <p> 392 409 Hit '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. 393 410 </p> 394 411 395 <p><a name="stop"><h4>4.1 0. Stop</h4></p>412 <p><a name="stop"><h4>4.11. Stop</h4></p> 396 413 <p> 397 414 Hit the 'Stop' button in order to stop BNS. 398 415 </p> 399 416 400 <p><a name="nw"><h4>4.1 1. No Window - optional</h4></p>417 <p><a name="nw"><h4>4.12. No Window - optional</h4></p> 401 418 <p> 402 419 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, see Config File example in the Annex) or from the register BKG_NTRIP_Server (Windows). … … 507 524 <p><a name="config"><h4>7.3. Config File</h4></p> 508 525 <p> 509 The following is an example of the contents of a Unix/Linux configuration file ${HOME}/.config/BKG/BKG_NTRIP_Server.conf. It enables the upload of stream CLCK1 to www.euref-ip.net. Clock RINEX files and SP3 Orbit files are uploaded to a directory /home/weber/rinex :526 The following is an example of the contents of a Unix/Linux 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 : 510 527 </p> 511 528 <p> 512 529 <pre> 513 530 [General] 514 clkFile=/home/weber/clocks.txt 515 clkHost=142.71.30.12 516 clkPort=2067 517 clkProxy=2 518 ephHost=141.71.30.13 519 ephPort=2066 520 ephProxy=2 531 clkPort=7000 532 ephEcho=/home/weber/rinex/eph.rnx 533 ephHost=clock-ip.bkg.bund.de 534 ephPort=6000 521 535 fileAppend=0 522 font="Andale Sans,9,-1,5,75,0,0,0,0,0" 523 logFile=/home/weber/rinex/log.txt 524 mountpoint=CLCK1 525 outFile=/home/weber/rinex/CLCK1.txt 536 font="Helvetica [Adobe],8,-1,5,75,0,0,0,0,0" 537 inpEcho=/home/weber/rinex/ClocksOrbits.dat 538 logFile=/home/weber/rinex/bns.log 539 mountpoint_1=CLCK1 540 mountpoint_2=CLCK2 541 outFile_1=/home/weber/rinex/CLCK1 542 outFile_2=/home/weber/rinex/CLCK2 526 543 outHost=www.igs-ip.net 527 544 outPort=2101 528 outProxy=2 529 password=uploadPass 530 proxyHost=gate-f 531 proxyPort=8000 532 refSys=IGS05 533 rnxAppend=2 545 password=serverPass 546 proxyHost= 547 proxyPort= 548 refSys_1=IGS05 549 refSys_2=ETRS89 534 550 rnxIntr=1 day 535 551 rnxPath=/home/weber/rinex 536 552 rnxSampl=30 537 sp3Intr=1 hour538 sp3Path=/home/weber/ sp3539 sp3Sampl= 0553 sp3Intr=1 day 554 sp3Path=/home/weber/rinex 555 sp3Sampl=300 540 556 </pre> 541 557 </p>
Note:
See TracChangeset
for help on using the changeset viewer.
