Changeset 3907 in ntrip
- Timestamp:
- Apr 17, 2012, 11:00:34 PM (13 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (35 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r3898 r3907 161 161 3.5.3. <a href=#ephport>Port</a><br> 162 162 3.5.4. <a href=#ephvers>Version</a><br> 163 3.6. <a href=#correct>Broadcast Corrections</a><br> 164 3.6.1. <a href=#corrdir>Directory, ASCII</a><br> 165 3.6.2. <a href=#corrint>Interval</a><br> 166 3.6.3. <a href=#corrport>Port</a><br> 167 3.6.4. <a href=#corrwait>Wait for Full Epoch</a><br> 168 3.7. <a href=#syncout>Feed Engine</a><br> 169 3.7.1. <a href=#syncport>Port</a><br> 170 3.7.2. <a href=#syncwait>Wait for Full Epoch</a><br> 171 3.7.3. <a href=#syncsample>Sampling</a><br> 172 3.7.4. <a href=#syncfile>File</a><br> 173 3.7.5. <a href=#syncuport>Port (unsynchronized)</a><br> 174 3.8. <a href=#serial>Serial Output</a><br> 175 3.8.1. <a href=#sermount>Mountpoint</a><br> 176 3.8.2. <a href=#serport>Port Name</a><br> 177 3.8.3. <a href=#serbaud>Baud Rate</a><br> 178 3.8.4. <a href=#serflow>Flow Control</a><br> 179 3.8.5. <a href=#serparity>Parity</a><br> 180 3.8.6. <a href=#serdata>Data Bits</a><br> 181 3.8.7. <a href=#serstop>Stop Bits</a><br> 182 3.8.8. <a href=#serauto>NMEA</a><br> 183 3.8.9. <a href=#serfile>File</a><br> 184 3.8.10. <a href=#serheight>Height</a><br> 185 3.9. <a href=#advnote>Outages</a><br> 186 3.9.1. <a href=#obsrate>Observation Rate</a><br> 187 3.9.2. <a href=#advfail>Failure Threshold</a><br> 188 3.9.3. <a href=#advreco>Recovery Threshold</a><br> 189 3.9.4. <a href=#advscript>Script</a><br> 190 3.10. <a href=#misc>Miscellaneous</a><br> 191 3.10.1. <a href=#miscmount>Mountpoint</a><br> 192 3.10.2. <a href=#miscperf>Log Latency</a><br> 193 3.10.3. <a href=#miscscan>Scan RTCM</a><br> 194 3.11. <a href=#pppclient>PPP Client</a><br> 195 3.11.1 <a href=#pppmode>Mode & Mountpoints</a><br> 196 3.11.1.1 <a href=#pppmodus>Mode</a><br> 197 3.11.1.2 <a href=#pppobsmount>Obs Mountpoint</a><br> 198 3.11.1.3 <a href=#pppcorrmount>Corr Mountpoint</a><br> 199 3.11.2 <a href=#pppxyz>Marker Coordinates</a><br> 163 3.6. <a href=#reqc>RINEX Editing & QC</a><br> 164 3.6.1 <a href=#reqcact>Action</a><br> 165 3.6.2 <a href=#reqcedit>Set Edit Options</a><br> 166 3.6.3 <a href=#reqcinput>Input files</a><br> 167 3.6.4 <a href=#reqcoutput>Output files</a><br> 168 3.7. <a href=#correct>Broadcast Corrections</a><br> 169 3.7.1. <a href=#corrdir>Directory, ASCII</a><br> 170 3.7.2. <a href=#corrint>Interval</a><br> 171 3.7.3. <a href=#corrport>Port</a><br> 172 3.7.4. <a href=#corrwait>Wait for Full Epoch</a><br> 173 3.8. <a href=#syncout>Feed Engine</a><br> 174 3.8.1. <a href=#syncport>Port</a><br> 175 3.8.2. <a href=#syncwait>Wait for Full Epoch</a><br> 176 3.8.3. <a href=#syncsample>Sampling</a><br> 177 3.8.4. <a href=#syncfile>File</a><br> 178 3.8.5. <a href=#syncuport>Port (unsynchronized)</a><br> 179 3.9. <a href=#serial>Serial Output</a><br> 180 3.9.1. <a href=#sermount>Mountpoint</a><br> 181 3.9.2. <a href=#serport>Port Name</a><br> 182 3.9.3. <a href=#serbaud>Baud Rate</a><br> 183 3.9.4. <a href=#serflow>Flow Control</a><br> 184 3.9.5. <a href=#serparity>Parity</a><br> 185 3.9.6. <a href=#serdata>Data Bits</a><br> 186 3.9.7. <a href=#serstop>Stop Bits</a><br> 187 3.9.8. <a href=#serauto>NMEA</a><br> 188 3.9.9. <a href=#serfile>File</a><br> 189 3.9.10. <a href=#serheight>Height</a><br> 190 3.10. <a href=#advnote>Outages</a><br> 191 3.10.1. <a href=#obsrate>Observation Rate</a><br> 192 3.10.2. <a href=#advfail>Failure Threshold</a><br> 193 3.10.3. <a href=#advreco>Recovery Threshold</a><br> 194 3.10.4. <a href=#advscript>Script</a><br> 195 3.11. <a href=#misc>Miscellaneous</a><br> 196 3.11.1. <a href=#miscmount>Mountpoint</a><br> 197 3.11.2. <a href=#miscperf>Log Latency</a><br> 198 3.11.3. <a href=#miscscan>Scan RTCM</a><br> 199 3.12. <a href=#pppclient>PPP Client</a><br> 200 3.12.1 <a href=#pppmode>Mode & Mountpoints</a><br> 201 3.12.1.1 <a href=#pppmodus>Mode</a><br> 202 3.12.1.2 <a href=#pppobsmount>Obs Mountpoint</a><br> 203 3.12.1.3 <a href=#pppcorrmount>Corr Mountpoint</a><br> 204 3.12.2 <a href=#pppxyz>Marker Coordinates</a><br> 200 205 3.11.3 <a href=#pppneu>Antenna Excentricity</a><br> 201 3.11.4 <a href=#pppoutput>NMEA & Plot Output</a><br> 202 3.11.4.1 <a href=#pppnmeafile>NMEA File</a><br> 203 3.11.4.2 <a href=#pppnmeaport>NMEA Port</a><br> 204 3.11.4.3 <a href=#pppplot>PPP Plot</a><br> 205 3.11.5 <a href=#ppppost>Post Processing</a><br> 206 3.11.6 <a href=#ppprecant>Antennas</a><br> 207 3.11.6.1 <a href=#pppantex>ANTEX File</a><br> 208 3.11.6.2 <a href=#ppprecantenna>Antenna Name</a><br> 209 3.11.6.3 <a href=#pppsatant>Apply Satellite Antenna Offsets</a><br> 210 3.11.7 <a href=#pppopt>PPP Options</a><br> 211 3.11.7.1 <a href=#pppphase>Use Phase Obs</a><br> 212 3.11.7.2 <a href=#ppptropo>Estimate Tropo</a><br> 213 3.11.7.3 <a href=#pppglo>Use GLONASS</a><br> 214 3.11.7.4 <a href=#pppgal>Use Galileo</a><br> 215 3.11.7.5 <a href=#pppsync>Sync Corr</a><br> 216 3.11.7.6 <a href=#pppaverage>Averaging</a><br> 217 3.11.7.7 <a href=#pppquick>Quick-Start</a><br> 218 3.11.7.8 <a href=#pppgap>Maximal Solution Gap</a><br> 219 3.11.8 <a href=#pppsigmas>Sigmas</a><br> 220 3.11.8.1 <a href=#pppsigc>Code</a><br> 221 3.11.8.2 <a href=#pppsigp>Phase</a><br> 222 3.11.8.3 <a href=#pppsigxyzi>XYZ Init</a><br> 223 3.11.8.4 <a href=#pppsigxyzn>XYZ White Noise</a><br> 224 3.11.8.5 <a href=#pppsigtrpi>Tropo Init</a><br> 225 3.11.8.6 <a href=#pppsigtrpn>Tropo White Noise</a><br> 226 3.12. <a href=#reqc>Reqc</a><br> 227 3.12.1 <a href=#reqcact>Action</a><br> 228 3.12.2 <a href=#reqcedit>Set Edit Options</a><br> 229 3.12.3 <a href=#reqcinput>Input files</a><br> 230 3.12.4 <a href=#reqcoutput>Output files</a><br> 206 3.12.4 <a href=#pppoutput>NMEA & Plot Output</a><br> 207 3.12.4.1 <a href=#pppnmeafile>NMEA File</a><br> 208 3.12.4.2 <a href=#pppnmeaport>NMEA Port</a><br> 209 3.12.4.3 <a href=#pppplot>PPP Plot</a><br> 210 3.12.5 <a href=#ppppost>Post Processing</a><br> 211 3.12.6 <a href=#ppprecant>Antennas</a><br> 212 3.12.6.1 <a href=#pppantex>ANTEX File</a><br> 213 3.12.6.2 <a href=#ppprecantenna>Antenna Name</a><br> 214 3.12.6.3 <a href=#pppsatant>Apply Satellite Antenna Offsets</a><br> 215 3.12.7 <a href=#pppopt>PPP Options</a><br> 216 3.12.7.1 <a href=#pppphase>Use Phase Obs</a><br> 217 3.12.7.2 <a href=#ppptropo>Estimate Tropo</a><br> 218 3.12.7.3 <a href=#pppglo>Use GLONASS</a><br> 219 3.12.7.4 <a href=#pppgal>Use Galileo</a><br> 220 3.12.7.5 <a href=#pppsync>Sync Corr</a><br> 221 3.12.7.6 <a href=#pppaverage>Averaging</a><br> 222 3.12.7.7 <a href=#pppquick>Quick-Start</a><br> 223 3.12.7.8 <a href=#pppgap>Maximal Solution Gap</a><br> 224 3.12.8 <a href=#pppsigmas>Sigmas</a><br> 225 3.12.8.1 <a href=#pppsigc>Code</a><br> 226 3.12.8.2 <a href=#pppsigp>Phase</a><br> 227 3.12.8.3 <a href=#pppsigxyzi>XYZ Init</a><br> 228 3.12.8.4 <a href=#pppsigxyzn>XYZ White Noise</a><br> 229 3.12.8.5 <a href=#pppsigtrpi>Tropo Init</a><br> 230 3.12.8.6 <a href=#pppsigtrpn>Tropo White Noise</a><br> 231 231 3.13. <a href=#combi>Combination</a><br> 232 232 3.13.1 <a href=#combimounttab>Combination Table</a><br> … … 546 546 </p> 547 547 548 <p><a name="correct"><h4>3.6. Broadcast Corrections</h4></p> 548 <p><a name="reqc"><h4>3.6. RINEX Editing & QC</h4></p> 549 <p> 550 BNC allows to concatenate RINEX files and edit their contents. Observation and navigation files can be handled. BNC can also carry out a quality check of the contents of RINEX files. This functionality in BNC stands for 551 <ul> 552 <li>t = translation (from RTCM to RINEX)</li> 553 <li>e = editing and concatenation</li> 554 <li>qc = quality check</li> 555 </ul> 556 to follow UNAVCO's famous 'teqc' program. The remarkable thing about BNC in this context is that it supports RINEX Version 3 under GNU General Public License. 557 558 <p><a name="reqcact"><h4>3.6.1 Action - optional</h4></p> 559 <p>Select an action. Options are 'Edit/Concatenate' and 'Analyze'. 560 <ul> 561 <li>Select 'Edit/Concatenate' of you want to edit RINEX file contents according to options specified under 'Set Edit Options' or if you want to concatenate several RINEX files.</li> 562 <li>Select 'Analyze' if you are interested in a quality controle of your RINEX file contents.</li> 563 </ul> 564 </p> 565 566 <p><a name="reqcedit"><h4>3.6.2 Set Edit Options - mandatory if 'Edit/Concatenate' is set</h4></p> 567 <p>Once action 'Edit/Concationate' is selected, you have to specify editing options. BNC lets you specify the RINEX version, sampling rate, begin and end of file and marker, antenna or receiver details. 568 </p> 569 570 <p><a name="reqcinput"><h4>3.6.3 Input Files - mandatory if 'Action' is set</h4></p> 571 <p> 572 Specify full path to input RINEX observation file(s), and<br> 573 specify full path to input RINEX navigation file(s). 574 </p> 575 576 <p><a name="reqcoutput"><h4>3.6.4 Output Files - mandatory if 'Action' is set</h4></p> 577 <p> 578 Mandatory if 'Edit/Concatenate' selected:<br> 579 Specify full path to output RINEX observation file(s), and<br> 580 specify full path to output RINEX navigation file(s). 581 </p> 582 583 <p> 584 Mandatory if 'Analyze' selected:<br> 585 Specify logfile(s) to output analysis results.<br> 586 </p> 587 588 <p><a name="correct"><h4>3.7. Broadcast Corrections</h4></p> 549 589 <p> 550 590 Differential GNSS and RTK operation using RTCM streams is currently based on corrections and/or raw measurements from single or multiple reference stations. This approach to differential positioning is using 'observation space' information. The representation with the RTCM standard can be called 'ObservationSpace Representation' (OSR). … … 726 766 </pre> 727 767 728 <p><a name="corrdir"><h4>3. 6.1 Directory, ASCII - optional</h4></p>768 <p><a name="corrdir"><h4>3.7.1 Directory, ASCII - optional</h4></p> 729 769 <p> 730 770 Specify a directory for saving Broadcast Corrections in files. If the specified directory does not exist, BNC will not create Broadcast Correction files. Default value for Broadcast Corrections 'Directory' is an empty option field, meaning that no Broadcast Correction files will be created. 731 771 </p> 732 772 733 <p><a name="corrint"><h4>3. 6.2 Interval - mandatory if 'Directory, ASCII' is set</h4></p>773 <p><a name="corrint"><h4>3.7.2 Interval - mandatory if 'Directory, ASCII' is set</h4></p> 734 774 <p> 735 775 Select the length of the Broadcast Correction files. The default value is 1 day. 736 776 </p> 737 777 738 <p><a name="corrport"><h4>3. 6.3 Port - optional</h4></p>778 <p><a name="corrport"><h4>3.7.3 Port - optional</h4></p> 739 779 <p> 740 780 BNC can output epoch by epoch synchronized Broadcast 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 Broadcast Correction output via IP port is generated. … … 781 821 </p> 782 822 783 <p><a name="corrwait"><h4>3. 6.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p>823 <p><a name="corrwait"><h4>3.7.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p> 784 824 <p> 785 825 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. … … 789 829 </p> 790 830 791 <p><a name="syncout"><h4>3. 7. Feed Engine</h4></p>831 <p><a name="syncout"><h4>3.8. Feed Engine</h4></p> 792 832 <p> 793 833 BNC can generate synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed a real-time GNSS network engine. Observations can be streamed out through an IP port and/or saved in a local file. The output is always in plain ASCII format and comprises the following parameters: … … 847 887 <p><u>Figure:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p> 848 888 849 <p><a name="syncport"><h4>3. 7.1 Port - optional</h4></p>889 <p><a name="syncport"><h4>3.8.1 Port - optional</h4></p> 850 890 <p> 851 891 BNC can produce synchronized observations in ASCII 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> 852 892 </p> 853 893 854 <p><a name="syncwait"><h4>3. 7.2 Wait for Full Epoch - mandatory if 'Port' is set</h4></p>894 <p><a name="syncwait"><h4>3.8.2 Wait for Full Epoch - mandatory if 'Port' is set</h4></p> 855 895 <p> 856 896 When feeding a real-time GNSS network 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. … … 860 900 </p> 861 901 862 <p><a name="syncsample"><h4>3. 7.3 Sampling - mandatory if 'File' or 'Port' is set</h4></p>902 <p><a name="syncsample"><h4>3.8.3 Sampling - mandatory if 'File' or 'Port' is set</h4></p> 863 903 <p> 864 904 Select the synchronized observation output sampling interval in seconds. A value of zero '0' tells BNC to send/store all received epochs. This is the default value. 865 905 </p> 866 906 867 <p><a name="syncfile"><h4>3. 7.4 File - optional</h4></p>907 <p><a name="syncfile"><h4>3.8.4 File - optional</h4></p> 868 908 <p> 869 909 Specifies the full path to a 'File' where synchronized observations are saved in plain ASCII format. The default value is an empty option field, meaning that no ASCII output file is created. … … 873 913 </p> 874 914 875 <p><a name="syncuport"><h4>3. 7.5 Port (unsynchronized) - optional</h4></p>915 <p><a name="syncuport"><h4>3.8.5 Port (unsynchronized) - optional</h4></p> 876 916 <p> 877 917 BNC can produce unsynchronized observations from all configured streams in ASCII 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> 878 918 <p> 879 919 880 <p><a name="serial"><h4>3. 8. Serial Output</h4></p>920 <p><a name="serial"><h4>3.9. Serial Output</h4></p> 881 921 <p> 882 922 You may use BNC to feed a serial connected device like an GNSS receiver. For that one of the incoming streams can be forwarded to a serial port. The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an NTRIP broadcaster to feed a serial connected rover. … … 885 925 <p><u>Figure:</u> BNC pulling a VRS stream to feed a serial connected rover.</p> 886 926 887 <p><a name="sermount"><h4>3. 8.1 Mountpoint - optional</h4></p>927 <p><a name="sermount"><h4>3.9.1 Mountpoint - optional</h4></p> 888 928 <p> 889 929 Enter a 'Mountpoint' to forward its corresponding stream to a serial connected GNSS receiver. … … 893 933 </p> 894 934 895 <p><a name="serport"><h4>3. 8.2 Port Name - mandatory if 'Mountpoint' is set</h4></p>935 <p><a name="serport"><h4>3.9.2 Port Name - mandatory if 'Mountpoint' is set</h4></p> 896 936 <p> 897 937 Enter the serial 'Port name' selected on your host for communication with the serial connected receiver. Valid port names are … … 910 950 </p> 911 951 912 <p><a name="serbaud"><h4>3. 8.3 Baud Rate - mandatory if 'Mountpoint' is set</h4></p>952 <p><a name="serbaud"><h4>3.9.3 Baud Rate - mandatory if 'Mountpoint' is set</h4></p> 913 953 <p> 914 954 Select a 'Baud rate' for the serial output link. Note that using a high baud rate is recommended. 915 955 </p> 916 956 917 <p><a name="serflow"><h4>3. 8.4 Flow Control - mandatory if 'Mountpoint' is set</h4></p>957 <p><a name="serflow"><h4>3.9.4 Flow Control - mandatory if 'Mountpoint' is set</h4></p> 918 958 <p> 919 959 Select a 'Flow control' for the serial output link. Note that your selection must equal the flow control configured to the serial connected device. Select 'OFF' if you don't know better. 920 960 </p> 921 961 922 <p><a name="serparity"><h4>3. 8.5 Parity - mandatory if 'Mountpoint' is set</h4></p>962 <p><a name="serparity"><h4>3.9.5 Parity - mandatory if 'Mountpoint' is set</h4></p> 923 963 <p> 924 964 Select the 'Parity' for the serial output link. Note that parity is often set to 'NONE'. 925 965 </p> 926 966 927 <p><a name="serdata"><h4>3. 8.6 Data Bits - mandatory if 'Mountpoint' is set</h4></p>967 <p><a name="serdata"><h4>3.9.6 Data Bits - mandatory if 'Mountpoint' is set</h4></p> 928 968 <p> 929 969 Select the number of 'Data bits' for the serial output link. Note that often '8' data bits are used. 930 970 </p> 931 971 932 <p><a name="serstop"><h4>3. 8.7 Stop Bits - mandatory if 'Mountpoint' is set</h4></p>972 <p><a name="serstop"><h4>3.9.7 Stop Bits - mandatory if 'Mountpoint' is set</h4></p> 933 973 <p> 934 974 Select the number of 'Stop bits' for the serial output link. Note that often '1' stop bit is used. 935 975 </p> 936 976 937 <p><a name="serauto"><h4>3. 8.8 NMEA - mandatory for VRS streams</h4></p>977 <p><a name="serauto"><h4>3.9.8 NMEA - mandatory for VRS streams</h4></p> 938 978 <p> 939 979 Select 'Auto' to automatically forward all NMEA-GGA messages coming from your serial connected GNSS receiver to the NTRIP broadcaster and/or save them in a file. … … 946 986 </p> 947 987 948 <p><a name="serfile"><h4>3. 8.9 File - optional if 'Auto' NMEA is set</h4></p>988 <p><a name="serfile"><h4>3.9.9 File - optional if 'Auto' NMEA is set</h4></p> 949 989 <p>Specify the full path to a file where NMEA messages coming from your serial connected receiver are saved. 950 990 </p> 951 <p><a name="serheight"><h4>3. 8.10 Height - mandatory if 'Manual' NMEA is set</h4></p>991 <p><a name="serheight"><h4>3.9.10 Height - mandatory if 'Manual' NMEA is set</h4></p> 952 992 <p> 953 993 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. … … 957 997 </p> 958 998 959 <p><a name="advnote"><h4>3. 9. Outages</h4></p>999 <p><a name="advnote"><h4>3.10. Outages</h4></p> 960 1000 961 1001 <p> … … 972 1012 </p> 973 1013 974 <p><a name="obsrate"><h4>3. 9.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', and 'Script' is set</h4></p>1014 <p><a name="obsrate"><h4>3.10.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', and 'Script' is set</h4></p> 975 1015 <p> 976 1016 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. 977 1017 </p> 978 1018 979 <p><a name="advfail"><h4>3. 9.2 Failure Threshold - optional</h4></p>1019 <p><a name="advfail"><h4>3.10.2 Failure Threshold - optional</h4></p> 980 1020 <p> 981 1021 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. … … 985 1025 </p> 986 1026 987 <p><a name="advreco"><h4>3. 9.3 Recovery Threshold - optional</h4></p>1027 <p><a name="advreco"><h4>3.10.3 Recovery Threshold - optional</h4></p> 988 1028 <p> 989 1029 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. … … 993 1033 </p> 994 1034 995 <p><a name="advscript"><h4>3. 9.4 Script - optional </h4></p>1035 <p><a name="advscript"><h4>3.10.4 Script - optional </h4></p> 996 1036 <p> 997 1037 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. … … 1022 1062 </p> 1023 1063 1024 <p><a name="misc"><h4>3.1 0. Miscellaneous</h4></p>1064 <p><a name="misc"><h4>3.11. Miscellaneous</h4></p> 1025 1065 <p> 1026 1066 This section describes several miscellaneous options which can be applied for a single stream (mountpoint) or for all configured streams. … … 1034 1074 1035 1075 1036 <p><a name="miscmount"><h4>3.1 0.1 Mountpoint - optional </h4></p>1076 <p><a name="miscmount"><h4>3.11.1 Mountpoint - optional </h4></p> 1037 1077 <p> 1038 1078 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. 1039 1079 </p> 1040 1080 1041 <p><a name="miscperf"><h4>3.1 0.2 Log Latency - optional </h4></p>1081 <p><a name="miscperf"><h4>3.11.2 Log Latency - optional </h4></p> 1042 1082 <p> 1043 1083 BNC can average latencies per stream over a certain period of GPS time, the 'Log latency' interval. Mean latencies are calculated from the individual latencies of at most one (first incoming) observation or correction to Broadcast Ephemeris per second. The mean latencies are then saved in BNC's logfile. Note that computing correct latencies requires the clock of the host computer to be properly synchronized. Note further that the latencies available from the 'Latency' tab on the bottom of the main window represent individual latencies and not the mean latencies for the logfile. … … 1067 1107 1068 1108 1069 <p><a name="miscscan"><h4>3.1 0.3 Scan RTCM - optional</h4></p>1109 <p><a name="miscscan"><h4>3.11.3 Scan RTCM - optional</h4></p> 1070 1110 <p> 1071 1111 When configuring a GNSS receiver for RTCM stream generation, the firmware's 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. … … 1093 1133 </p> 1094 1134 1095 <p><a name="pppclient"><h4>3.1 1. PPP Client</h4></p>1135 <p><a name="pppclient"><h4>3.12. PPP Client</h4></p> 1096 1136 <p> 1097 1137 BNC can derive coordinates for a rover position following the Precise Point Positioning (PPP) approach. It uses either code or code plus phase data in ionosphere free linear combinations P3 or L3. Besides pulling a stream of observations from a dual frequency receiver, this also … … 1214 1254 </p> 1215 1255 1216 <p><a name="pppmode"><h4>3.1 1.1 Mode & Mountpoints - optional</h4></p>1256 <p><a name="pppmode"><h4>3.12.1 Mode & Mountpoints - optional</h4></p> 1217 1257 <p> 1218 1258 Specify the Point Positioning mode you want to apply and the mountpoints for observations and Broadcast Ephemeris corrections. 1219 1259 </p> 1220 1260 1221 <p><a name="pppmodus"><h4>3.1 1.1.1 Mode - optional</h4></p>1261 <p><a name="pppmodus"><h4>3.12.1.1 Mode - optional</h4></p> 1222 1262 <p>Choose between plain Single Point Positioning (SPP) and Precise Point Positioning (PPP) in 'Realtime' or 'Post-Processing' mode.</p> 1223 1263 1224 <p><a name="pppobsmount"><h4>3.1 1.1.2 Obs Mountpoint - optional</h4></p>1264 <p><a name="pppobsmount"><h4>3.12.1.2 Obs Mountpoint - optional</h4></p> 1225 1265 <p> 1226 1266 Specify an 'Observations Mountpoint' from the list of selected 'Streams' you are pulling if you want BNC to derive coordinates for the affected rover position through a Point Positioning solution. 1227 1267 </p> 1228 1268 1229 <p><a name="pppcorrmount"><h4>3.1 1.1.3 Corr Mountpoint - optional</h4></p>1269 <p><a name="pppcorrmount"><h4>3.12.1.3 Corr Mountpoint - optional</h4></p> 1230 1270 <p> 1231 1271 Specify a Broadcast Ephemeris 'Corrections Mountpoint' from the list of selected 'Streams' you are pulling if you want BNC to correct your positioning solution accordingly. 1232 1272 </p> 1233 1273 1234 <p><a name="pppxyz"><h4>3.1 1.2 Marker Coordinates - optional</h4></p>1274 <p><a name="pppxyz"><h4>3.12.2 Marker Coordinates - optional</h4></p> 1235 1275 <p> 1236 1276 Enter the reference coordinate components X,Y,Z of the receiver's position in meters if known. This option makes only sense for static observations. Default are empty option fields, meaning that the antenna's XYZ position is unknown. … … 1246 1286 </p> 1247 1287 1248 <p><a name="pppneu"><h4>3.1 1.3 Antenna Excentricity - optional</h4></p>1288 <p><a name="pppneu"><h4>3.12.3 Antenna Excentricity - optional</h4></p> 1249 1289 <p> 1250 1290 You may like to specify North, East and Up compoments of an antenna excentricity which is the difference between a nearby marker position and the antenna phase center. If you do so BNC will produce coordinates referring to the marker position and not referring to the antenna phase center.. 1251 1291 </p> 1252 1292 1253 <p><a name="pppoutput"><h4>3.1 1.4 NMEA & Plot Output - optional</h4></p>1293 <p><a name="pppoutput"><h4>3.12.4 NMEA & Plot Output - optional</h4></p> 1254 1294 <p> 1255 1295 BNC allows to output results from Precise Point Positioning in NMEA format. It can also plot a time series of North, East and UP displacements of coordinate components. 1256 1296 </p> 1257 1297 1258 <p><a name="pppnmeafile"><h4>3.1 1.4.1 NMEA File - optional</h4></p>1298 <p><a name="pppnmeafile"><h4>3.12.4.1 NMEA File - optional</h4></p> 1259 1299 <p> 1260 1300 The NMEA sentences generated about once per second are pairs of … … 1271 1311 </p> 1272 1312 1273 <p><a name="pppnmeaport"><h4>3.1 1.4.2 NMEA Port - optional</h4></p>1313 <p><a name="pppnmeaport"><h4>3.12.4.2 NMEA Port - optional</h4></p> 1274 1314 <p> 1275 1315 Specify the IP port number of a local port where Point Positioning results become available as NMEA messages. The default value for 'NMEA Port' is an empty option field, meaning that BNC does not provide NMEA messages vi IP port. Note that the NMEA file output and the NMEA IP port output are the same. … … 1279 1319 </p> 1280 1320 1281 <p><a name="pppplot"><h4>3.1 1.4.3 PPP Plot - optional</h4></p>1321 <p><a name="pppplot"><h4>3.12.4.3 PPP Plot - optional</h4></p> 1282 1322 <p> 1283 1323 PPP time series of North (red), East(green) and Up (blue) coordinate components will be plotted in the 'PPP Plot' tab when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified) or referred to the first estimated XYZ coordinate. The sliding PPP time series window will cover the period of the latest 5 minutes. … … 1287 1327 </p> 1288 1328 1289 <p><a name="ppppost"><h4>3.1 1.5 Post Processing - optional</h4></p>1329 <p><a name="ppppost"><h4>3.12.5 Post Processing - optional</h4></p> 1290 1330 <p>When in 'Post-Processing mode<ul><li>specifying a RINEX Observation, a RINEX Navigation and a Broadcast Ephemeris corrections file leads to a PPP solution.</li><li>specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Ephemeris corrections file leads to a SPP solution.</ul></p> 1291 1331 <p>BNC accepts RINEX v2 as well as RINEX v3 observation or navigation file formats. Files carrying Broadcast Ephemeris corrections must have the format produced by BNC in the 'Broadcast Corrections' option. … … 1294 1334 </p> 1295 1335 1296 <p><a name="ppprecant"><h4>3.1 1.6 Antennas - optional</h4></p>1336 <p><a name="ppprecant"><h4>3.12.6 Antennas - optional</h4></p> 1297 1337 <p> 1298 1338 BNC allows to correct observations for antenna phase center offsets and variations. 1299 1339 </p> 1300 1340 1301 <p><a name="pppantex"><h4>3.1 1.6.1 ANTEX File - optional</h4></p>1341 <p><a name="pppantex"><h4>3.12.6.1 ANTEX File - optional</h4></p> 1302 1342 <p> 1303 1343 IGS provides a file containing absolute phase center corrections for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required for correcting observations for antenna phase center offsets and variations. It allows you to specify the name of your receiver's antenna (as contained in the ANTEX file) to apply such corrections. … … 1307 1347 </p> 1308 1348 1309 <p><a name="ppprecantenna"><h4>3.1 1.6.2 Receiver Antenna Name - optional if 'ANTEX File' is set</h4></p>1349 <p><a name="ppprecantenna"><h4>3.12.6.2 Receiver Antenna Name - optional if 'ANTEX File' is set</h4></p> 1310 1350 <p> 1311 1351 Specify the receiver's antenna name as defined in your ANTEX file. Observations will be corrected for the antenna phase center's offset which may result in a reduction of a few centimeters at max. Corrections for phase center variations are not yet applied by BNC. The specified name must consist of 20 characters. Add trailing blanks if the antenna name has less then 20 characters. Examples: … … 1320 1360 </p> 1321 1361 1322 <p><a name="pppsatant"><h4>3.1 1.6.3 Apply Satellite Antenna Offsets - optional if 'ANTEX File' is set</h4></p>1362 <p><a name="pppsatant"><h4>3.12.6.3 Apply Satellite Antenna Offsets - optional if 'ANTEX File' is set</h4></p> 1323 1363 <p> 1324 1364 BNC allows to correct observations for satellite antenna phase center offsets. (This option is not yet implemented.) … … 1330 1370 </p> 1331 1371 1332 <p><a name="pppopt"><h4>3.1 1.7 PPP Options</h4></p>1372 <p><a name="pppopt"><h4>3.12.7 PPP Options</h4></p> 1333 1373 <p>BNC allows to use different Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows to introduce specific sigmas for code and phase observations as well as for reference coordinates and troposphere estimates. You may also like to carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold. 1334 1374 </p> 1335 1375 1336 <p><a name="pppphase"><h4>3.1 1.7.1 Use Phase Obs - optional</h4></p>1376 <p><a name="pppphase"><h4>3.12.7.1 Use Phase Obs - optional</h4></p> 1337 1377 <p> 1338 1378 By default BNC applies a Point Positioning solution using an ionosphere free P3 linear combination of code observations. Tick 'Use phase obs' for an ionosphere free L3 linear combination of phase observations. 1339 1379 </p> 1340 1380 1341 <p><a name="ppptropo"><h4>3.1 1.7.2 Estimate Tropo - optional</h4></p>1381 <p><a name="ppptropo"><h4>3.12.7.2 Estimate Tropo - optional</h4></p> 1342 1382 <p> 1343 1383 BNC estimates the tropospheric delay according to equation … … 1351 1391 </p> 1352 1392 1353 <p><a name="pppglo"><h4>3.1 1.7.3 Use GLONASS - optional</h4></p>1393 <p><a name="pppglo"><h4>3.12.7.3 Use GLONASS - optional</h4></p> 1354 1394 <p> 1355 1395 By default BNC does not process GLONASS but only GPS observations when in Point Positioning mode. Tick 'Use GLONASS' to use GLONASS observations in addition to GPS (and Galileo if specified) for estimating coordinates in Point Positioning mode. 1356 1396 </p> 1357 1397 1358 <p><a name="pppgal"><h4>3.1 1.7.4 Use Galileo - optional</h4></p>1398 <p><a name="pppgal"><h4>3.12.7.4 Use Galileo - optional</h4></p> 1359 1399 <p> 1360 1400 By default BNC does not process Galileo but only GPS observations when in Point Positioning mode. Tick 'Use Galileo' to use Galileo observations in addition to GPS (and GLONASS if specified) for estimating coordinates in Point Positioning mode. 1361 1401 </p> 1362 1402 1363 <p><a name="pppsync"><h4>3.1 1.7.5 Sync Corr - optional</h4></p>1403 <p><a name="pppsync"><h4>3.12.7.5 Sync Corr - optional</h4></p> 1364 1404 <p> 1365 1405 Zero value (or empty field) means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value 'Sync Corr' means that the epochs of data are buffered and the processing of each epoch is postponed till the satellite clock corrections not older than 'Sync Corr' are available. Specifying a value of half the update rate of the clock corrections as 'Sync Corr' (i.e. 5 sec) may be appropriate. Note that this causes an additional delay of the PPP solutions in the amount of the update rate. … … 1372 1412 </p> 1373 1413 1374 <p><a name="pppaverage"><h4>3.1 1.7.6 Averaging - optional if XYZ is set</h4></p>1414 <p><a name="pppaverage"><h4>3.12.7.6 Averaging - optional if XYZ is set</h4></p> 1375 1415 <p> 1376 1416 Enter the length of a sliding time window in minutes. BNC will continuously output moving average values ns and their RMS as computed from those individual values obtained most recently throughout this period. RMS values presented for XYZ coordinates and tropospheric zenit path delays are bias reduced while RMS values for Nort/East/Up (NEU) displacements are not. Averaged values for XYZ coordinates and their RMS are marked with string "AVE-XYZ" in BNC's log file and 'Log' section while averaged values for NEU displacements and their RMS are marked with string "AVE-NEU" and averaged values for the tropospheric delays and their RMS are marked with string "AVE-TRP". Example: … … 1385 1425 </p> 1386 1426 1387 <p><a name="pppquick"><h4>3.1 1.7.7 Quick-Start - optional if XYZ is set</h4></p>1427 <p><a name="pppquick"><h4>3.12.7.7 Quick-Start - optional if XYZ is set</h4></p> 1388 1428 <p> 1389 1429 Enter the lenght of a startup period in seconds for which you want to fix the PPP solution to a known XYZ coordinate. Constraining coordinate components is done in BNC through setting the 'XYZ White Noise' temporarily to zero. … … 1398 1438 <p><u>Figure:</u> BNC in 'Quick-Start' mode</p> 1399 1439 1400 <p><a name="pppgap"><h4>3.1 1.7.8 Maximal Solution Gap - optional if Quick-Start is set</h4></p>1440 <p><a name="pppgap"><h4>3.12.7.8 Maximal Solution Gap - optional if Quick-Start is set</h4></p> 1401 1441 <p> 1402 1442 Specify a 'Maximum Solution Gap' in seconds. Should the time span between two consecutive solutions exceed this limit, the algorithm returns into the Quick-Start mode and fixes the introduced reference coordinate for the specified Quick-Start period. A value of '120' seconds could be an appropriate choice. … … 1406 1446 </p> 1407 1447 1408 <p><a name="pppsigmas"><h4>3.1 1.8 Sigmas</h4></p>1448 <p><a name="pppsigmas"><h4>3.12.8 Sigmas</h4></p> 1409 1449 <p> 1410 1450 You may like to introduce specific sigmas for code and phase observations and for the estimation of troposphere parameters. … … 1423 1463 </p> 1424 1464 1425 <p><a name="pppsigp"><h4>3.1 1.8.2 Phase - mandatory if 'Use Phase Obs' is set</h4></p>1465 <p><a name="pppsigp"><h4>3.12.8.2 Phase - mandatory if 'Use Phase Obs' is set</h4></p> 1426 1466 <p> 1427 1467 Specify a sigma for phase observations. Default is 0.02 m. 1428 1468 </p> 1429 1469 1430 <p><a name="pppsigxyzi"><h4>3.1 1.8.3 XYZ Init - mandatory</h4></p>1470 <p><a name="pppsigxyzi"><h4>3.12.8.3 XYZ Init - mandatory</h4></p> 1431 1471 <p> 1432 1472 Enter a sigma in meters for the initial XYZ coordinate componentes. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with known XZY position in Quick-Start mode. 1433 1473 </p> 1434 1474 1435 <p><a name="pppsigxyzn"><h4>3.1 1.8.4 XYZ White Noise - mandatory</h4></p>1475 <p><a name="pppsigxyzn"><h4>3.12.8.4 XYZ White Noise - mandatory</h4></p> 1436 1476 <p> 1437 1477 Enter a sigma in meters for the 'White Noise' of estimated XYZ coordinate components. A value of 100.0 (default) may be appropriate considering the potential movement of a rover. 1438 1478 </p> 1439 1479 1440 <p><a name="pppsigtrpi"><h4>3.1 1.8.5 Tropo Init - mandatory if 'Estimate tropo' is set</h4></p>1480 <p><a name="pppsigtrpi"><h4>3.12.8.5 Tropo Init - mandatory if 'Estimate tropo' is set</h4></p> 1441 1481 <p> 1442 1482 Enter a sigma in meters for the a-priory model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice. 1443 1483 </p> 1444 1484 1445 <p><a name="pppsigtrpn"><h4>3.1 1.8.6 Tropo White Noise - mandatory if 'Estimate tropo' is set</h4></p>1485 <p><a name="pppsigtrpn"><h4>3.12.8.6 Tropo White Noise - mandatory if 'Estimate tropo' is set</h4></p> 1446 1486 <p> 1447 1487 Enter a sigma in meters per second to describe the expected variation of the tropospheric effect. Supposing 1Hz observation data, a value of 3e-6 (default) would mean that the tropospheric effect may vary for 3600 * 3e-6 = 0.01 meters per hour. 1448 1488 </p> 1449 1450 <p><a name="reqc"><h4>3.12. Reqc</h4></p>1451 <p>1452 BNC allows to concatenate RINEX files and edit their contents. Observation and navigation files can be handled. BNC can also carry out a quality check of the contents of RINEX files. This functionality in BNC stands for1453 <ul>1454 <li>t = translation (from RTCM to RINEX)</li>1455 <li>e = editing and concatenation</li>1456 <li>qc = quality check</li>1457 </ul>1458 to follow UNAVCO's famous 'teqc' program. The remarkable thing about BNC in this context is that it supports RINEX Version 3 under GNU General Public License.1459 1460 <p><a name="reqcact"><h4>3.12.1 Action - optional</h4></p>1461 <p>Select an action. Options are 'Edit/Concatenate' and 'Analyze'.1462 <ul>1463 <li>Select 'Edit/Concatenate' of you want to edit RINEX file contents according to options specified under 'Set Edit Options' or if you want to concatenate several RINEX files.</li>1464 <li>Select 'Analyze' if you are interested in a quality controle of your RINEX file contents.</li>1465 </ul>1466 </p>1467 1468 <p><a name="reqcedit"><h4>3.12.2 Set Edit Options - mandatory if 'Edit/Concatenate' is set</h4></p>1469 <p>Once action 'Edit/Concationate' is selected, you have to specify editing options. BNC lets you specify the RINEX version, sampling rate, begin and end of file and marker, antenna or receiver details.1470 </p>1471 1472 <p><a name="reqcinput"><h4>3.12.3 Input Files - mandatory if 'Action' is set</h4></p>1473 <p>1474 Specify full path to input RINEX observation file(s), and<br>1475 specify full path to input RINEX navigation file(s).1476 </p>1477 1478 <p><a name="reqcoutput"><h4>3.12.4 Output Files - mandatory if 'Action' is set</h4></p>1479 <p>1480 Mandatory if 'Edit/Concatenate' selected:<br>1481 Specify full path to output RINEX observation file(s), and<br>1482 specify full path to output RINEX navigation file(s).1483 </p>1484 1485 <p>1486 Mandatory if 'Analyze' selected:<br>1487 Specify logfile(s) to output analysis results.<br>1488 </p>1489 1489 1490 1490 <p><a name="combi"><h4>3.13. Combination</h4></p>
Note:
See TracChangeset
for help on using the changeset viewer.
