Changeset 1359 in ntrip
- Timestamp:
- Dec 27, 2008, 4:45:48 PM (16 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (29 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r1322 r1359 70 70 <p><a name="options"><h3>3. Options</h3></p> 71 71 <p> 72 The usual handling of BNC is that you first select a number of streams from NTRIP broadcasters ('Add Streams'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various tabs to select a combination of processing options before you start the program ('Start'). Records of BNC's activities are shown in the 'Log' canvas on the bottom of the main window. 73 </p> 74 <p> 72 75 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. Some options can be changed on-the-fly. 73 76 </p> … … 79 82 3.4.1. <a href=#genlog>Logfile</a><br> 80 83 3.4.2. <a href=#genapp>Append Files</a><br> 81 3.4.3. <a href=#reconf>Reread Configuration</a><br> 82 3.5. <a href=#rinex>RINEX - Observations</a><br> 84 3.4.3. <a href=#genconf>Reread Configuration</a><br> 85 3.4.4. <a href=#genstart>Auto Start</a><br> 86 3.5. <a href=#rinex>RINEX Observations</a><br> 83 87 3.5.1. <a href=#rnxname>File Names</a><br> 84 88 3.5.2. <a href=#rnxdir>Directory</a><br> … … 88 92 3.5.6. <a href=#rnxscript>Script</a><br> 89 93 3.5.7. <a href=#rnxvers>Version</a><br> 90 3.6. <a href=#ephemeris>RINEX -Ephemeris</a><br>94 3.6. <a href=#ephemeris>RINEX Ephemeris</a><br> 91 95 3.6.1. <a href=#ephdir>Directory</a><br> 92 96 3.6.2. <a href=#ephint>Interval</a><br> 93 97 3.6.3. <a href=#ephport>Port</a><br> 94 98 3.6.4. <a href=#ephvers>Version</a><br> 95 3.7. <a href=#syncout>Feed Engine</a><br> 96 3.7.1. <a href=#syncport>Port (synchronized)</a><br> 97 3.7.2. <a href=#syncwait>Wait for Full Epoch</a><br> 98 3.7.3. <a href=#syncuport>Port (unsynchronized)</a><br> 99 3.7.4. <a href=#syncfile>File</a><br> 100 3.7.5. <a href=#syncsample>Sampling</a><br> 101 3.8. <a href=#correct>Ephemeris Corrections</a><br> 102 3.8.1. <a href=#corrdir>Directory</a><br> 103 3.8.2. <a href=#corrint>Interval</a><br> 104 3.8.3. <a href=#corrport>Port</a><br> 105 3.8.4. <a href=#corrwait>Wait for Full Epoch</a><br> 106 3.9. <a href=#advnote>Outages</a><br> 107 3.9.1. <a href=#obsrate>Observation Rate</a><br> 108 3.9.2. <a href=#advfail>Failure Threshold</a><br> 109 3.9.3. <a href=#advreco>Recovery Threshold</a><br> 110 3.9.4. <a href=#pause>Pause</a><br> 111 3.9.5. <a href=#advscript>Script</a><br> 112 3.10. <a href=#misc>Miscellaneous</a><br> 113 3.10.1. <a href=#mountpoint>Mountpoint</a><br> 114 3.10.2. <a href=#perflog>Log Latency</a><br> 115 3.10.3. <a href=#scanrtcm>Scan RTCM</a><br> 116 3.11. <a href=#mountpoints>Mountpoints</a><br> 117 3.11.1. <a href=#mountadd>Add Mountpoints</a><br> 118 3.11.2. <a href=#mounthost>Broadcaster Host and Port</a><br> 119 3.11.3. <a href=#mountuser>Broadcaster User and Password</a><br> 120 3.11.4. <a href=#mounttable>Get Table</a><br> 121 3.11.5. <a href=#mountdelete>Delete Mountpoints</a><br> 122 3.11.6. <a href=#mountedit>Edit Mountpoints</a><br> 123 3.11.7. <a href=#mountconf>Reconfigure Mountpoints On-the-fly</a><br> 124 3.12. <a href=#start>Start</a><br> 125 3.13. <a href=#stop>Stop</a><br> 126 3.14. <a href=#cmd>Command Line Options</a><br> 127 3.14.1. <a href=#nw>No Window Mode</a><br> 128 3.14.2. <a href=#post>Offline Mode</a><br> 99 3.7. <a href=#correct>Ephemeris Corrections</a><br> 100 3.7.1. <a href=#corrdir>Directory</a><br> 101 3.7.2. <a href=#corrint>Interval</a><br> 102 3.7.3. <a href=#corrport>Port</a><br> 103 3.7.4. <a href=#corrwait>Wait for Full Epoch</a><br> 104 3.8. <a href=#syncout>Feed Engine</a><br> 105 3.8.1. <a href=#syncport>Port (synchronized)</a><br> 106 3.8.2. <a href=#syncwait>Wait for Full Epoch</a><br> 107 3.8.3. <a href=#syncuport>Port (unsynchronized)</a><br> 108 3.8.4. <a href=#syncfile>File</a><br> 109 3.8.5. <a href=#syncsample>Sampling</a><br> 110 3.9. <a href=#serial>Serial Link</a><br> 111 3.9.1. <a href=#sermount>Mountpoint</a><br> 112 3.9.2. <a href=#serport>Port Name</a><br> 113 3.9.3. <a href=#serbaud>Baud Rate</a><br> 114 3.9.4. <a href=#serparity>Parity</a><br> 115 3.9.5. <a href=#serdata>Data Bits</a><br> 116 3.9.6. <a href=#serstop>Stop Bits</a><br> 117 3.9.7. <a href=#serauto>Auto NMEA</a><br> 118 3.10. <a href=#advnote>Outages</a><br> 119 3.10.1. <a href=#obsrate>Observation Rate</a><br> 120 3.10.2. <a href=#advfail>Failure Threshold</a><br> 121 3.10.3. <a href=#advreco>Recovery Threshold</a><br> 122 3.10.4. <a href=#pause>Pause</a><br> 123 3.10.5. <a href=#advscript>Script</a><br> 124 3.11. <a href=#misc>Miscellaneous</a><br> 125 3.11.1. <a href=#miscmount>Mountpoint</a><br> 126 3.11.2. <a href=#miscperf>Log Latency</a><br> 127 3.11.3. <a href=#miscscan>Scan RTCM</a><br> 128 3.12. <a href=#streams>Streams</a><br> 129 3.12.1. <a href=#streamadd>Add Streams</a><br> 130 3.12.2. <a href=#streamhost>Broadcaster Host and Port</a><br> 131 3.12.3. <a href=#streamuser>Broadcaster User and Password</a><br> 132 3.12.4. <a href=#streamtable>Get Table</a><br> 133 3.12.5. <a href=#streamdelete>Delete Streams</a><br> 134 3.12.6. <a href=#streamedit>Edit Streams</a><br> 135 3.12.7. <a href=#streamconf>Reconfigure Streams On-the-fly</a><br> 136 3.13. <a href=#start>Start</a><br> 137 3.14. <a href=#stop>Stop</a><br> 138 3.15. <a href=#cmd>Command Line Options</a><br> 139 3.15.1. <a href=#nw>No Window Mode</a><br> 140 3.15.2. <a href=#post>Offline Mode</a><br> 129 141 </p> 130 142 … … 183 195 <p><a name="genlog"><h4>3.4.1 Logfile - optional</h4></p> 184 196 <p> 185 Records of BNC's activities are shown in the Log sectionon 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.197 Records of BNC's activities are shown in the 'Log' canvas 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. 186 198 </p> 187 199 … … 191 203 </p> 192 204 193 <p><a name=" reconf"><h4>3.4.3 Reread Configuration - optional</h4></p>205 <p><a name="genconf"><h4>3.4.3 Reread Configuration - optional</h4></p> 194 206 <p> 195 207 When operating BNC online in 'no window' mode (command line option -nw), some configuration options can nevertheless be changed on-the-fly without interrupting the running process. For that you force the program to reread parts of its configuration in pre-defined intervals. Select '1 min', '1 hour', or '1 day' to let BNC reread on-the-fly changeable configuration options every full minute, hour, or day. This lets in between edited options become effective without interrupting uninvolved threads. See annexed section 'Configuration File' for a Unix/Linux/Mac configuration file example and a list of on-the-fly changeable options. 196 208 </p> 197 209 198 <p><a name="rinex"><h4>3.5. RINEX - Observations</h4></p> 210 <p><a name="genstart"><h4>3.4.4 Auto Start - optional</h4></p> 211 <p> 212 You may like to auto-start BNC at startup time in window mode with preassigned configuration options. This may be required i.e. immediately after booting your system. Tick 'Auto start' to supersede the usage of the 'Start' button. Make sure that you maintain a link to BNC for that in your Autostart directory (Windows systems) or call BNC in a script below directory /etc/init.d (Unix/Linux/Mac systems). 213 </p> 214 <p> 215 See BNC's command line option -nw for an auto-start of BNC in 'no window' mode. 216 </p> 217 218 <p><a name="rinex"><h4>3.5. RINEX Observations</h4></p> 199 219 <p> 200 220 Observations will be converted to RINEX if they come in either RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. BNC's RINEX Observation files generally contain C1, C2, P1, P2, L1, L2, S1, and S2 observations. In case an observation is unavailable, its value is set to zero '0.000'. Note that the 'RINEX TYPE' field in the RINEX Observation file header is always set to 'M(MIXED)' even if the file does not contain any GLONASS or SABAS data. … … 203 223 <p><a name="rnxname"><h4>3.5.1 RINEX File Names</h4></p> 204 224 <p> 205 RINEX file names are derived by BNC from the first 4 characters of the corresponding mountpoint (4Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named</p>225 RINEX file names are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named</p> 206 226 <p> 207 227 FRAN{ddd}{h}.{yy}O<br> … … 312 332 </p> 313 333 314 <p><a name="ephemeris"><h4>3.6. Ephemeris</h4></p>334 <p><a name="ephemeris"><h4>3.6. RINEX Ephemeris</h4></p> 315 335 <p> 316 336 Broadcast ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3.x as message types 1019 (GPS) and 1020 (GLONASS) or via RTIGS records type 300. The file name convention follows the details given in section 'RINEX File Names' except that the first four characters are 'BRDC' and the last character is … … 347 367 </p> 348 368 349 <p><a name="syncout"><h4>3.7. Feed Engine</h4></p> 369 <p><a name="correct"><h4>3.7. Ephemeris Corrections</h4></p> 370 <p> 371 </p> 372 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 premature messages currently under discussion have been implemented in BNC: 373 <ul> 374 <li>Message type 4050: GPS orbit corrections to Broadcast Ephemeris</li> 375 <li>Message type 4051: GPS clock corrections to Broadcast Ephemeris</li> 376 <li>Message type 4052: GPS code biases</li> 377 <li>Message type 4053: GLONASS orbit corrections to Broadcast Ephemeris</li> 378 <li>Message type 4054: GLONASS clock corrections to Broadcast Ephemeris</li> 379 <li>Message type 4055: GLONASS code biases</li> 380 <li>Message type 4056: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li> 381 <li>Message type 4057: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li> 382 </ul> 383 <p> 384 RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications. 385 </p> 386 <p> 387 When using clocks from Broadcast Ephemeris (with or without corrections) and clocks from SP3 files in the same application, it is important to understand that Broadcast Ephemeris clocks - according to the Interface Control Documents (ICD) - are corrected for the 2nd-order relativistic effect whereas clocks from SP3 files are not. The 2nd-order relativistic effect is a priodic time correction defined as -2 (R * V) / c^2 and includes the scalar product of satallite position and velocity divided by the speed of light raised to the second power. 388 </p> 389 390 <p><a name="corrdir"><h4>3.7.1 Directory - optional</h4></p> 391 <p> 392 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. 393 </p> 394 <p> 395 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". 396 </p> 397 398 <p><a name="corrint"><h4>3.7.2 Interval - mandatory if 'Directory' is set</h4></p> 399 <p> 400 Select the length of the Ephemeris Correction files. The default value is 1 day. 401 </p> 402 403 <p><a name="corrport"><h4>3.7.3 Port - optional</h4></p> 404 <p> 405 BNC can output epoch by epoch synchronized Ephemeris Corrections in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number to activate this function. The default is an empty option field, meaning that no Ephemeris Correction output via IP port is generated. 406 </p> 407 <p> 408 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: 409 </p> 410 <p> 411 <ul> 412 <li>GPS Week</li> 413 <li>Second in GPS Week</li> 414 <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li> 415 <li>IOD refering to Broadcast Ephemeris set</li> 416 <li>Clock Correction to Broadcast Ephemeris [m]</li> 417 <li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li> 418 <li>Along-track Component of Orbit Correction to Broadcast Ephemeris [m]</li> 419 <li>Cross-track Component of Orbit Correction to Broadcast Ephemeris [m]</li> 420 <li>Mountpoint</li> 421 </ul> 422 </p> 423 <p> 424 The following is an example output from two RTCM Version 3 streams (CLCK1 and CLCK4) containing message types 4056 and 4057: 425 <pre> 426 ... 427 1490 115710.0 R17 18 -1.903 2.348 -1.343 -1.403 CLCK1 428 1490 115710.0 R10 18 -4.131 2.416 -0.646 -1.054 CLCK1 429 1490 115710.0 G27 97 5.291 1.201 -1.964 0.821 CLCK4 430 1490 115710.0 G26 14 -11.247 1.003 -1.168 0.074 CLCK4 431 ... 432 1490 115711.0 R17 18 -1.902 2.349 -1.342 -1.403 CLCK1 433 1490 115711.0 R10 18 -4.131 2.415 -0.647 -1.052 CLCK1 434 1490 115711.0 G27 97 5.288 1.200 -1.964 0.820 CLCK4 435 1490 115711.0 G26 14 -11.246 1.004 -1.168 0.074 CLCK4 436 ... 437 </pre> 438 </p> 439 440 <p><a name="corrwait"><h4>3.7.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p> 441 <p> 442 When feeding a real-time GNSS engine waiting epoch by epoch for synchronized Ephemeris Corrections, BNC drops (only concering IP port output) whatever is received later than 'Wait for full epoch' seconds. A value of 2 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming Ephemeris Corrections stream and the delay acceptable by your application. A message such as "COCK1: Correction overaged by 5 sec" shows up in BNC's logfile if 'Wait for full epoch' is exceeded. 443 </p> 444 445 <p><a name="syncout"><h4>3.8. Feed Engine</h4></p> 350 446 <p> 351 447 BNC can generate synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed a real-time GNSS engine. The output can be produced in a binary format through an IP port and/or a plain ASCII format to save the observations in a local file. It comprises the following observations where available:</p> … … 357 453 </p> 358 454 359 <p><a name="syncport"><h4>3. 7.1 Port (synchronized) - optional</h4></p>455 <p><a name="syncport"><h4>3.8.1 Port (synchronized) - optional</h4></p> 360 456 <p> 361 457 BNC can produce synchronized observations in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary output is generated.</p> … … 409 505 </p> 410 506 <p> 411 Note that any socket connection of an application to BNC's synchronized observations 'Port' is recorded in the Log sectionon the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'.412 </p> 413 414 <p><a name="syncwait"><h4>3. 7.2 Wait for Full Epoch - mandatory if 'Port (synchronized)' is set</h4></p>507 Note that any socket connection of an application to BNC's synchronized observations 'Port' is recorded in the 'Log' canvas on the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'. 508 </p> 509 510 <p><a name="syncwait"><h4>3.8.2 Wait for Full Epoch - mandatory if 'Port (synchronized)' is set</h4></p> 415 511 <p> 416 512 When feeding a real-time GNSS engine waiting for synchronized input epoch by epoch, BNC drops whatever is received later than 'Wait for full epoch' seconds. A value of 3 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming streams and the delay acceptable for your real-time GNSS product. Default value for 'Wait for full epoch' is 5 seconds. … … 420 516 </p> 421 517 422 <p><a name="syncuport"><h4>3. 7.3 Port (unsynchronized) - optional</h4></p>518 <p><a name="syncuport"><h4>3.8.3 Port (unsynchronized) - optional</h4></p> 423 519 An application may want to receive unsynchronized observations from reference stations. If so, BNC can produce such unsynchronized observations in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary unsynchronized output is generated.</p> 424 520 … … 427 523 </p> 428 524 <p> 429 Note that any socket connection of an application to BNC's unsynchronized observations 'Port' is recorded in the Log sectionon the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'.430 </p> 431 432 433 <p><a name="syncfile"><h4>3. 7.4 File - optional</h4></p>525 Note that any socket connection of an application to BNC's unsynchronized observations 'Port' is recorded in the 'Log' canvas on the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'. 526 </p> 527 528 529 <p><a name="syncfile"><h4>3.8.4 File - optional</h4></p> 434 530 <p> 435 531 Specifies the full path to a 'File' where synchronized or unsynchronized observations are saved in plain ASCII format. The default value is an empty option field, meaning that no ASCII output file is created. … … 439 535 </p> 440 536 441 <p><a name="syncsample"><h4>3. 7.5 Sampling - mandatory if 'File' or 'Port' is set</h4></p>537 <p><a name="syncsample"><h4>3.8.5 Sampling - mandatory if 'File' or 'Port' is set</h4></p> 442 538 <p> 443 539 Select the observation output sampling interval in seconds. A value of zero '0' tells BNC to send/store all received epochs. This is the default value. 444 <p> 445 446 <p><a name="correct"><h4>3.8. Ephemeris Corrections</h4></p> 447 <p> 448 </p> 449 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 premature messages currently under discussion have been implemented in BNC: 450 <ul> 451 <li>Message type 4050: GPS orbit corrections to Broadcast Ephemeris</li> 452 <li>Message type 4051: GPS clock corrections to Broadcast Ephemeris</li> 453 <li>Message type 4052: GPS code biases</li> 454 <li>Message type 4053: GLONASS orbit corrections to Broadcast Ephemeris</li> 455 <li>Message type 4054: GLONASS clock corrections to Broadcast Ephemeris</li> 456 <li>Message type 4055: GLONASS code biases</li> 457 <li>Message type 4056: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li> 458 <li>Message type 4057: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li> 459 </ul> 460 <p> 461 RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications. 462 </p> 463 <p> 464 When using clocks from Broadcast Ephemeris (with or without corrections) and clocks from SP3 files in the same application, it is important to understand that Broadcast Ephemeris clocks - according to the Interface Control Documents (ICD) - are corrected for the 2nd-order relativistic effect whereas clocks from SP3 files are not. The 2nd-order relativistic effect is a priodic time correction defined as -2 (R * V) / c^2 and includes the scalar product of satallite position and velocity divided by the speed of light raised to the second power. 465 </p> 466 467 <p><a name="corrdir"><h4>3.8.1 Directory - optional</h4></p> 468 <p> 469 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. 470 </p> 471 <p> 472 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". 473 </p> 474 475 <p><a name="corrint"><h4>3.8.2 Interval - mandatory if 'Directory' is set</h4></p> 476 <p> 477 Select the length of the Ephemeris Correction files. The default value is 1 day. 478 </p> 479 480 <p><a name="corrport"><h4>3.8.3 Port - optional</h4></p> 481 <p> 482 BNC can output epoch by epoch synchronized Ephemeris Corrections in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number to activate this function. The default is an empty option field, meaning that no Ephemeris Correction output via IP port is generated. 483 </p> 484 <p> 485 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: 486 </p> 487 <p> 488 <ul> 489 <li>GPS Week</li> 490 <li>Second in GPS Week</li> 491 <li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li> 492 <li>IOD refering to Broadcast Ephemeris set</li> 493 <li>Clock Correction to Broadcast Ephemeris [m]</li> 494 <li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li> 495 <li>Along-track Component of Orbit Correction to Broadcast Ephemeris [m]</li> 496 <li>Cross-track Component of Orbit Correction to Broadcast Ephemeris [m]</li> 497 <li>Mountpoint</li> 498 </ul> 499 </p> 500 <p> 501 The following is an example output from two RTCM Version 3 streams (CLCK1 and CLCK4) containing message types 4056 and 4057: 540 </p> 541 542 <p><a name="serial"><h4>3.9. Serial Link</h4></p> 543 <p> 544 You may use BNC to feed a serial connected device like an GNSS rover. For that one of the incoming streams can be forwarded to a serial port. 545 </p> 546 547 <p><a name="sermount"><h4>3.9.1 Mountpoint - optional</h4></p> 548 <p> 549 Enter a 'Mountpoint' to forward its corresponding stream to a serial connected device. 550 </p> 551 <p> 552 When selecting the serial communication options listed below, make sure that you pick those confiured to the serial connected device. 553 </p> 554 555 <p><a name="serport"><h4>3.9.2 Port Name - mandatory if 'Mountpoint' is set</h4></p> 556 <p> 557 Enter the serial 'Port name' selected on your host for communication with the serial connected device. Valid port names are 558 </p> 502 559 <pre> 503 ... 504 1490 115710.0 R17 18 -1.903 2.348 -1.343 -1.403 CLCK1 505 1490 115710.0 R10 18 -4.131 2.416 -0.646 -1.054 CLCK1 506 1490 115710.0 G27 97 5.291 1.201 -1.964 0.821 CLCK4 507 1490 115710.0 G26 14 -11.247 1.003 -1.168 0.074 CLCK4 508 ... 509 1490 115711.0 R17 18 -1.902 2.349 -1.342 -1.403 CLCK1 510 1490 115711.0 R10 18 -4.131 2.415 -0.647 -1.052 CLCK1 511 1490 115711.0 G27 97 5.288 1.200 -1.964 0.820 CLCK4 512 1490 115711.0 G26 14 -11.246 1.004 -1.168 0.074 CLCK4 513 ... 560 Windows: COM1, COM2 561 Linux: /dev/ttyS0, /dev/ttyS1 562 FreeBSD: /dev/ttyd0, /dev/ttyd1 563 Digital Unix: /dev/tty01, /dev/tty02 564 HP-UX: /dev/tty1p0, /dev/tty2p0 565 SGI/IRIX: /dev/ttyf1, /dev/ttyf2 566 SunOS/Solaris: /dev/ttya, /dev/ttyb 514 567 </pre> 515 </p> 516 517 <p><a name="corrwait"><h4>3.8.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p> 518 <p> 519 When feeding a real-time GNSS engine waiting epoch by epoch for synchronized Ephemeris Corrections, BNC drops (only concering IP port output) whatever is received later than 'Wait for full epoch' seconds. A value of 2 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming Ephemeris Corrections stream and the delay acceptable by your application. A message such as "COCK1: Correction overaged by 5 sec" shows up in BNC's logfile if 'Wait for full epoch' is exceeded. 520 </p> 521 522 <p><a name="advnote"><h4>3.9. Outages</h4></p> 568 569 <p><a name="serbaud"><h4>3.9.3 Baud Rate - mandatory if 'Mountpoint' is set</h4></p> 570 <p> 571 Select a 'Baud rate' for the serial link. Note that using a high baud rate is recommended. 572 </p> 573 574 <p><a name="serparity"><h4>3.9.4 Parity - mandatory if 'Mountpoint' is set</h4></p> 575 <p> 576 Select the 'Parity' for the serial link. Note that parity is often set to 'NONE'. 577 </p> 578 579 <p><a name="serdata"><h4>3.9.5 Data Bits - mandatory if 'Mountpoint' is set</h4></p> 580 <p> 581 Select the number of 'Data bits' for the serial link. Note that often '8' data bits are used. 582 </p> 583 584 <p><a name="serstop"><h4>3.9.6 Stop Bits - mandatory if 'Mountpoint' is set</h4></p> 585 <p> 586 Select the number of 'Stop bits' for the serial link. Note that often '1' stop bit is used. 587 </p> 588 589 <p><a name="serauto"><h4>3.9.7 Auto NMEA - optional</h4></p> 590 <p> 591 Tick 'Auto NMEA' to forward NMEA-GGA messages (or any other message) coming from your serial connected device to the NTRIP brodacaster.</p> 592 <p> 593 This option replaces BNC's simulation of an initial NMEA-GGA message based on approximate latitude/longitude from the broadcaster's source-table. Note that sending valid NMEA-GGA strings (simulated or coming from your serial connected device) to the NTRIP broadcaster is required for receiving virtual reference station (VRS) streams. 594 </p> 595 596 <p><a name="advnote"><h4>3.10. Outages</h4></p> 523 597 524 598 <p> … … 532 606 </p> 533 607 <p> 534 Outage and corruption events are reported in the Log file/section. They can also be passed on as parameters to a shell script or batch file to generate an advisory note to BNC operator or affected stream providers. This functionality lets users utilise BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations.535 </p> 536 537 <p><a name="obsrate"><h4>3. 9.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', 'Pause' and 'Script' is set</h4></p>608 Outage and corruption events are reported in the 'Log' file/canvas. They can also be passed on as parameters to a shell script or batch file to generate an advisory note to BNC operator or affected stream providers. This functionality lets users utilise BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations. 609 </p> 610 611 <p><a name="obsrate"><h4>3.10.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', 'Pause' and 'Script' is set</h4></p> 538 612 <p> 539 613 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). 540 614 </p> 541 615 542 <p><a name="advfail"><h4>3. 9.2 Failure Threshold - optional</h4></p>616 <p><a name="advfail"><h4>3.10.2 Failure Threshold - optional</h4></p> 543 617 <p> 544 618 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. … … 548 622 </p> 549 623 550 <p><a name="advreco"><h4>3. 9.3 Recovery Threshold - optional</h4></p>624 <p><a name="advreco"><h4>3.10.3 Recovery Threshold - optional</h4></p> 551 625 <p> 552 626 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. … … 556 630 </p> 557 631 558 <p><a name="pause"><h4>3. 9.4 Pause - optional</h4></p>632 <p><a name="pause"><h4>3.10.4 Pause - optional</h4></p> 559 633 <p> 560 634 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. … … 564 638 </p> 565 639 566 <p><a name="advscript"><h4>3. 9.5 Script - optional </h4></p>567 <p> 568 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.640 <p><a name="advscript"><h4>3.10.5 Script - optional </h4></p> 641 <p> 642 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 stream's 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. 569 643 </p> 570 644 <p> … … 593 667 </p> 594 668 595 <p><a name="misc"><h4>3.1 0. Miscellaneous</h4></p>669 <p><a name="misc"><h4>3.11. Miscellaneous</h4></p> 596 670 <p> 597 671 This section describes a number of miscellaneous options which can be applied for a single stream (mountpoint) or for all configured streams. 598 672 </p> 599 673 600 <p><a name="m ountpoint"><h4>3.10.1 Mountpoint - optional </h4></p>674 <p><a name="miscmount"><h4>3.11.1 Mountpoint - optional </h4></p> 601 675 <p> 602 676 Specify a mountpoint to apply one or several of the 'Miscellaneous' options to the corresponding stream. Enter 'ALL' if you want to apply these options to all configured streams. An empty option field (default) means that you don't want BNC to apply any of these options. 603 677 </p> 604 678 605 <p><a name=" perflog"><h4>3.10.2 Log Latency - optional </h4></p>679 <p><a name="miscperf"><h4>3.11.2 Log Latency - optional </h4></p> 606 680 <p> 607 681 BNC can average latencies per stream over a certain period of GPS time, the 'Performance log' interval. Mean latencies are calculated from the individual latencies of at most one (first incoming) observation or correction to Broadcast Ephemeris per second. Note that computing correct latencies requires the clock of the host computer to be properly synchronized. … … 621 695 </p> 622 696 <p> 623 Latencies of observations or corrections to Broadcast Ephemeris and statistical information can be recorded in the Log file/sectionat the end of each 'Performance log' interval. A typical output from a 1 hour 'Performance log' interval would be:697 Latencies of observations or corrections to Broadcast Ephemeris and statistical information can be recorded in the 'Log' file/canvas at the end of each 'Performance log' interval. A typical output from a 1 hour 'Performance log' interval would be: 624 698 </p> 625 699 <pre> … … 631 705 632 706 633 <p><a name=" scanrtcm"><h4>3.10.3 Scan RTCM - optional</h4></p>634 <p> 635 When configuring a GNSS receiver for RTCM stream generation, the setup interface may not provide details about RTCM message types. As reliable information concerning stream contents should be available i.e. for NTRIP broadcaster operators to maintain the broadcaster's source table, BNC allows to scan RTCM streams for incoming message types and printout some of the contained meta-data. The idea for this option arose from 'InspectRTCM', a comprehensive stream analyzing tool written by D. Stoecker.707 <p><a name="miscscan"><h4>3.11.3 Scan RTCM - optional</h4></p> 708 <p> 709 When configuring a GNSS receiver for RTCM stream generation, the setup interface may not provide details about RTCM message types. As reliable information concerning stream contents should be available i.e. for NTRIP broadcaster operators to maintain the broadcaster's source-table, BNC allows to scan RTCM streams for incoming message types and printout some of the contained meta-data. The idea for this option arose from 'InspectRTCM', a comprehensive stream analyzing tool written by D. Stoecker. 636 710 </p> 637 711 <p> … … 657 731 </p> 658 732 659 <p><a name=" mountpoints"><h4>3.11. Mountpoints</h4></p>660 <p> 661 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.662 </p> 663 664 Streams selected for retrieval are listed under the ' Mountpoints'section on BNC's main window. The list provides the following information extracted from source-table(s) produced by the NTRIP broadcasters:733 <p><a name="streams"><h4>3.12. Streams</h4></p> 734 <p> 735 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 streams and their 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. 736 </p> 737 738 Streams selected for retrieval are listed under the 'Streams' canvas section on BNC's main window. The list provides the following information extracted from source-table(s) produced by the NTRIP broadcasters: 665 739 666 740 <table> … … 675 749 </table> 676 750 677 <p><a name=" mountadd"><h4>3.11.1 Add Mountpoints</h4></p>678 <p> 679 Button 'Add Mountpoints' opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints.680 </p> 681 682 <p><a name=" mounthost"><h4>3.11.2 Broadcaster Host and Port - required</h4></p>751 <p><a name="streamadd"><h4>3.12.1 Add Streams</h4></p> 752 <p> 753 Button 'Add Streams' opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints. 754 </p> 755 756 <p><a name="streamhost"><h4>3.12.2 Broadcaster Host and Port - mandatory</h4></p> 683 757 <p> 684 758 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>. 685 759 </p> 686 760 687 <p><a name=" mountuser"><h4>3.11.3 Broadcaster User and Password - requiredfor protected streams</h4></p>761 <p><a name="streamuser"><h4>3.12.3 Broadcaster User and Password - mandatory for protected streams</h4></p> 688 762 <p> 689 763 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>. 690 764 </p> 691 765 692 <p><a name=" mounttable"><h4>3.11.4 Get Table</h4></p>766 <p><a name="streamtable"><h4>3.12.4 Get Table</h4></p> 693 767 <p> 694 768 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 or 20 and 21 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. 695 769 </p> 696 770 <p> 697 The contents of data field 'nmea' tells you whether a stream retrieval needs to be initiated by BNC through sending an NMEA-GGA message carrying position coordinates (virtual reference station).698 </p> 699 <p> 700 Hit 'OK' to return to the main window. If you wish you can click on 'Add Mountpoints' and repeat the process again to retrieve mountpoints from different casters.701 </p> 702 703 <p><a name=" mountdelete"><h4>3.11.5 Delete Mountpoints</h4></p>704 <p> 705 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>706 707 <p><a name=" mountedit"><h4>3.11.6 Edit Mountpoints</h4></p>771 The contents of data field 'nmea' tells you whether a stream retrieval needs to be initiated by BNC through sending an NMEA-GGA message carrying approximate position coordinates (virtual reference station). 772 </p> 773 <p> 774 Hit 'OK' to return to the main window. If you wish you can click on 'Add Streams' and repeat the process again to retrieve streams from different casters. 775 </p> 776 777 <p><a name="streamdelete"><h4>3.12.5 Delete Streams</h4></p> 778 <p> 779 To remove a stream from the 'Streams' canvas in the main window, highlight it by clicking on it and hit the 'Delete Streams' button. You can also remove multiple streams simultaneously by highlighting them using +Shift and +Ctrl.</p> 780 781 <p><a name="streamedit"><h4>3.12.6 Edit Streams</h4></p> 708 782 <ul> 709 783 <li> … … 711 785 </li> 712 786 <li> 713 In case you need to log the raw data as is, BNC allows users to by-pass its decoders and and directly save the input in daily log files. To do this specify the decoder string as 'ZERO'. The generated file names are created from the characters of the mountpoints plus two-digit numbers each for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and running BNC on March 29, 2007 would save the raw data in a file named WTZZ0_070329.714 </li> 715 <li> 716 BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA format to the NTRIP broadcaster. In return, a user-specific data stream is generated, typically by a Network-RTK software. This stream is customized to the exact latitude and longitude as shown in the 'lat' and 'long' columns under 'Mountpoints'. These VRS streams are indicated by a 'yes' in the 'nmea' column under 'Mountpoints' as well as in the source-table.717 <br> The default 'lat' and 'long' values are taken from the source-table however in most cases you would probably want to change this according to your requirement. Double-click on 'lat' and 'long' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only mountpoints with a 'yes' in its 'nmea' column can be edited. The position must preferably be a point within the service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'long' used.787 In case you need to log the raw data as is, BNC allows users to by-pass its decoders and and directly save the input in daily log files. To do this specify the decoder string as 'ZERO'. The generated file names are created from the characters of the streams mountpoints plus two-digit numbers each for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and running BNC on March 29, 2007 would save the raw data in a file named WTZZ0_070329. 788 </li> 789 <li> 790 BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA format to the NTRIP broadcaster. In return, a user-specific data stream is generated, typically by a Network-RTK software. VRS streams are indicated by a 'yes' in the source-table as well as in the 'nmea' column on the 'Streams' canvas in BNC's main window. They are customized exactly to the latitude and longitude transmitted to the NTRIP broadcaster via NMEA-GGA messages. 791 <br>If NMEA-GGA messages are not coming from a serial connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'lon' columns on the 'Streams' canvas. However, in most cases you would probably want to change these defaults according to your requirement. Double-click on 'lat' and 'lon' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only streams with a 'yes' in their 'nmea' column can be edited. The position must preferably be a point within the VRS service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'lon' used. 718 792 <br>Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner. 719 793 </li> 720 794 </ul> 721 795 722 <p><a name=" mountconf"><h4>3.11.7 Reconfigure Mountpoints On-the-fly</h4></p>723 <p> 724 The mountpoints selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process.725 </p> 726 <p> 727 <u>Window mode:</u> Hit 'Save & Activate Options' while BNC is in window mode and already processing data to let changes of your mountpoints selection immediately become effective.728 <p> 729 <u>No window mode:</u> When operating BNC online in 'no window' mode (command line option -nw), you force BNC to reread its 'mountPoints' configuration option in pre-defined intervals. Select '1 min', '1 hour', or '1 day' as 'Reread configuration' option to reread the 'mount points' option every full minute, hour, or day. This lets a 'mountPoints' option edited in between in the configuration file or Windows register become effective without terminating uninvolved threads. See annexed section 'Configuration File' for a Unix/Linux/Mac configuration file example and a list of other on-the-fly changeable options.730 </p> 731 732 <p><a name="start"><h4>3.1 2. Start</h4></p>796 <p><a name="streamconf"><h4>3.12.7 Reconfigure Streams On-the-fly</h4></p> 797 <p> 798 The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process. 799 </p> 800 <p> 801 <u>Window mode:</u> Hit 'Save & Activate Options' while BNC is in window mode and already processing data to let changes of your streams selection immediately become effective. 802 <p> 803 <u>No window mode:</u> When operating BNC online in 'no window' mode (command line option -nw), you force BNC to reread its 'mountPoints' configuration option in pre-defined intervals. Select '1 min', '1 hour', or '1 day' as 'Reread configuration' option to reread the 'mountPoints' option every full minute, hour, or day. This lets a 'mountPoints' option edited in between in the configuration file or Windows register become effective without terminating uninvolved threads. See annexed section 'Configuration File' for a Unix/Linux/Mac configuration file example and a list of other on-the-fly changeable options. 804 </p> 805 806 <p><a name="start"><h4>3.13. Start</h4></p> 733 807 <p> 734 808 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. 735 809 </p> 736 810 737 <p><a name="stop"><h4>3.1 3. Stop</h4></p>811 <p><a name="stop"><h4>3.14. Stop</h4></p> 738 812 <p> 739 813 Hit the 'Stop' button in order to stop BNC. 740 814 </p> 741 815 742 <p><a name="cmd"><h4>3.1 4. Command Line Options</h4></p>816 <p><a name="cmd"><h4>3.15. Command Line Options</h4></p> 743 817 <p> 744 818 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. 745 819 </p> 746 820 747 <p><a name="nw"><h4>3.1 4.1 No Window Mode - optional</h4></p>821 <p><a name="nw"><h4>3.15.1 No Window Mode - optional</h4></p> 748 822 <p> 749 823 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. … … 754 828 </p> 755 829 756 <p><a name="post"><h4>3.1 4.2 Offline Mode - optional</h4></p>830 <p><a name="post"><h4>3.15.2 Offline Mode - optional</h4></p> 757 831 <p> 758 832 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: … … 862 936 <tr><td>Dec 2008 </td><td>Version 1.6 </td><td>[Mod] Fill blanc columns in RINEXv3 with 0.000<br> [Add] RTCMv3 decoder for clock and orbit corrections<br>[Add] Check RTCMv3 streams for incoming message types<br> [Add] Decode RTCMv2 message types 3, 20, 21, and 22<br> [Add] Loss of lock and lock time indicator<br> [Bug] Rounding error in RTCMv3 decoder concerning GLONASS height<br> [Mod] Accept GLONASS in RTCMv3 when transmitted first<br> [Add] Leap second 1 January 2009<br> [Add] Offline mode, read data from file<br> [Add] Output antenna descriptor, coordinates and excentricities from RTCMv3<br> [Add] Reconfiguration on-the-fly<br> [Mod] Binary ouput of synchronized observations<br> [Add] Binary output of unsynchronized observations<br> [Bug] Fixed problem with joined RTCMv3 blocks</td></tr> 863 937 <tr><td>Jan 2009 </td><td>Version 1.7 </td><td> 864 [Add] Full proxy support<br> [Mod] Ntrip source table request<br> [Bug] RINEX navigation file format<br> [Add] Support of NTRIP v2<br> [Add] Rover support via serial port</td></tr>938 [Add] Full proxy support<br> [Mod] Ntrip source-table request<br> [Bug] RINEX navigation file format<br> [Add] Support of NTRIP v2<br> [Add] Rover support via serial port</td></tr> 865 939 </table> 866 940 </p> … … 1050 1124 adviseReco=5 1051 1125 adviseScript= 1126 autoStart=0 1052 1127 binSampl=0 1053 1128 casterHost=www.euref-ip.net … … 1063 1138 ephPath=/home/user/rinex 1064 1139 ephV3=2 1140 font="Helvetica [Adobe],9,-1,5,50,0,0,0,0,0" 1065 1141 logFile=/home/user/log.txt 1066 1142 makePause=0 1143 miscMount= 1067 1144 mountPoints=//user:pass@www.euref-ip.net:2101/ACOR0 RTCM_2.3 43.36 351.60 no, //user:pass@www.igs-ip.net:2101/FFMJ3 RTCM_3.0 41.58 1.40 no 1068 1145 obsRate= … … 1082 1159 rnxSkel=SKL 1083 1160 rnxV3=2 1161 scanRTCM=0 1162 serialAutoNMEA=0 1163 serialBaudRate=9600 1164 serialDataBits=8 1165 serialMountPoint= 1166 serialParity=NONE 1167 serialPortName= 1168 serialStopBits=1 1084 1169 waitTime=5 1085 1170 </pre> … … 1093 1178 <p> 1094 1179 <ul> 1095 <li>'mountPoints' to change the selection of streams to be processed, see section ' Mountpoints',</li>1180 <li>'mountPoints' to change the selection of streams to be processed, see section 'Streams',</li> 1096 1181 <li>'waitTime' to change the 'Wait for full epoch' option, see section 'Synchronized Observations', and</li> 1097 1182 <li>'binSampl' to change the 'Sampling' option, see section 'Synchronized Observations'.</li>
Note:
See TracChangeset
for help on using the changeset viewer.
