Changeset 2378 in ntrip
- Timestamp:
- Mar 18, 2010, 10:06:23 AM (14 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (17 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r2377 r2378 249 249 <p><a name="genstart"><h4>3.3.4 Auto Start - optional</h4></p> 250 250 <p> 251 You may like to auto-start BNC at startup time in window mode with pre assigned 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).251 You may like to auto-start BNC at startup time in window mode with pre-assigned 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). 252 252 </p> 253 253 <p> … … 381 381 382 382 <p> 383 Note that streams dedicated to carry Broad cst Ephemeris messages in RTCM v3 format in high repetition rates are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>.383 Note that streams dedicated to carry Broadacst Ephemeris messages in RTCM v3 format in high repetition rates are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>. 384 384 </p> 385 385 … … 407 407 </p> 408 408 <p> 409 Note that this does not concern the broadcast ephemeris output throug IP port which is always in RINEX Version 3 format.409 Note that this does not concern the broadcast ephemeris output through IP port which is always in RINEX Version 3 format. 410 410 </p> 411 411 … … 432 432 </p> 433 433 <p> 434 When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it may beimportant to understand that they are not corrected for the 2nd-order relativistic effect. The 2nd-order relativistic effect is a p riodic 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.434 When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it may beimportant to understand that they are not corrected for the 2nd-order relativistic effect. The 2nd-order relativistic effect is a periodic time correction defined as -2 (R * V) / c^2 and includes the scalar product of satellite position and velocity divided by the speed of light raised to the second power. 435 435 </p> 436 436 … … 448 448 449 449 <p> 450 Broadcast Corr rections can be saved by BNC in files. The file name convention for Broadcast Correction files follows the convention for RINEX files except for the last character of the file name suffix which is set to "C".450 Broadcast Corrections can be saved by BNC in files. The file name convention for Broadcast Correction files follows the convention for RINEX files except for the last character of the file name suffix which is set to "C". 451 451 </p> 452 452 … … 486 486 <p> 487 487 <ul> 488 <li>IOD refer ing to Broadcast Ephemeris set</li>488 <li>IOD referring to Broadcast Ephemeris set</li> 489 489 <li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li> 490 490 <li>Along-track Component of Orbit Correction to Broadcast Ephemeris [m]</li> … … 539 539 <p> 540 540 <ul> 541 <li>IOD refer ing to Broadcast Ephemeris set</li>541 <li>IOD referring to Broadcast Ephemeris set</li> 542 542 <li>C0 polynomial coefficient for Clock Correction to Broadcast Ephemeris [m]</li> 543 543 <li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li> … … 638 638 <p><a name="corrwait"><h4>3.6.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p> 639 639 <p> 640 When feeding a real-time GNSS network engine waiting epoch by epoch for synchronized Broadcast Corrections, BNC drops (only concer ing 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 Broadcast 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.640 When feeding a real-time GNSS network engine waiting epoch by epoch for synchronized Broadcast Corrections, BNC drops (only concerning 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 Broadcast 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. 641 641 </p> 642 642 … … 648 648 </p> 649 649 <p> 650 Note that slip_cnt stands for the cumulative loss of continuity indicator, lock_timei for the lock time indicator, and SNR for the signal-to-noise ratio 'S' mapped to integer numbers 1 to 9. In case an observation is not available, its value is set to zero '0.000'. Loss of continuity indicator and lock time indicator are set to ne dative values if undefined.650 Note that slip_cnt stands for the cumulative loss of continuity indicator, lock_timei for the lock time indicator, and SNR for the signal-to-noise ratio 'S' mapped to integer numbers 1 to 9. In case an observation is not available, its value is set to zero '0.000'. Loss of continuity indicator and lock time indicator are set to negative values if undefined. 651 651 </p> 652 652 … … 705 705 <p><a name="syncport"><h4>3.7.1 Port - optional</h4></p> 706 706 <p> 707 BNC can produce synchronized observations in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. S cynchronized means that BNC collects all data for any specific epoch which become available within a certain number of latency seconds (see 'Wait for Full Epoch' option). It then - epoch by epoch - outputs whatever has been received. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary synchronized output is generated.</p>707 BNC can produce synchronized observations in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Synchronized means that BNC collects all data for any specific epoch which become available within a certain number of latency seconds (see 'Wait for Full Epoch' option). It then - epoch by epoch - outputs whatever has been received. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary synchronized output is generated.</p> 708 708 <p> 709 709 </p> … … 732 732 <p><a name="syncuport"><h4>3.7.5 Port (unsynchronized) - optional</h4></p> 733 733 <p> 734 BNC can produce unsynchronized observations from all configured streams in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Uns cynchronized means that BNC immediately forwards any received observation to the 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>734 BNC can produce unsynchronized observations from all configured streams in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Unsynchronized means that BNC immediately forwards any received observation to the 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> 735 735 <p> 736 736 … … 798 798 </p> 799 799 <p> 800 In summary: select 'Manual' only when handling a VRS stream and your serial connected GNSS receiver doesn't generate NMEA-GGA messages. Select 'Auto' otherw eise.800 In summary: select 'Manual' only when handling a VRS stream and your serial connected GNSS receiver doesn't generate NMEA-GGA messages. Select 'Auto' otherwise. 801 801 </p> 802 802 … … 806 806 <p><a name="serheight"><h4>3.8.10 Height - mandatory if 'Manual' NMEA is set</h4></p> 807 807 <p> 808 Specify an approximate 'Height' above mean sea level in meter for your VRS to simulate an init al NMEA-GGA message. Latitude and longitude for that (editable) are taken from the broadcaster's source-table.808 Specify an approximate 'Height' above mean sea level in meter for your VRS to simulate an initial NMEA-GGA message. Latitude and longitude for that (editable) are taken from the broadcaster's source-table. 809 809 </p> 810 810 <p> … … 824 824 </p> 825 825 <p> 826 Outage and corruption events are reported in the 'Log' tab. 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 utili se BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations.826 Outage and corruption events are reported in the 'Log' tab. 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 utilize BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations. 827 827 </p> 828 828 829 829 <p><a name="obsrate"><h4>3.9.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', and 'Script' is set</h4></p> 830 830 <p> 831 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 831 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 cannot be decoded. 832 832 </p> 833 833 … … 932 932 933 933 <p> 934 Note that in RTCM Version 2.x the message types 18 and 19 carry only the observables of one frequenc e. Hence it needs two type 18 and 19 messages per epoch to transport the observations from dual frequency receivers.934 Note that in RTCM Version 2.x the message types 18 and 19 carry only the observables of one frequency. Hence it needs two type 18 and 19 messages per epoch to transport the observations from dual frequency receivers. 935 935 </p> 936 936 <p> … … 1099 1099 </li> 1100 1100 <li> 1101 In case you need to log the raw data as is, BNC allows users to by-pass its decoders and anddirectly 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.1101 In case you need to log the raw data as is, BNC allows users to by-pass its decoders 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. 1102 1102 </li> 1103 1103 <li> … … 1124 1124 <p><a name="logs"><h4>3.13. Logging</h4></p> 1125 1125 <p> 1126 A tabs section on the bottom of the main window provides online control e of BNC's activities. Tabs are available to show the records saved in a logfile, for a plot to controlethe bandwidth consumtion, for a plot showing stream latencies, and for time series plots of PPP results.1126 A tabs section on the bottom of the main window provides online control of BNC's activities. Tabs are available to show the records saved in a logfile, for a plot to control the bandwidth consumtion, for a plot showing stream latencies, and for time series plots of PPP results. 1127 1127 </p> 1128 1128 <p><a name="logfile"><h4>3.13.1 Log</h4></p>
Note:
See TracChangeset
for help on using the changeset viewer.
