Changeset 7555 in ntrip
- Timestamp:
- Oct 27, 2015, 3:52:30 PM (9 years ago)
- File:
-
- 1 edited
-
trunk/BNC/src/bnchelp.html (modified) (131 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r7554 r7555 10 10 </p> 11 11 12 <p><b> Contents</b><br><br>12 <p><b>Table of <a name="contents">Contents</b><br><br> 13 13 <b>1.</b> <a href=#genInstruction><b>General Instructions</b></a><br><br> 14 14 1.1 <a href=#introPurpose>Purpose</a><br> … … 348 348 </p> 349 349 350 <p><h 3>1.1 <a name="introPurpose">Purpose</h3></p>350 <p><h4>1.1 <a name="introPurpose">Purpose</h4></p> 351 351 352 352 <p> The purpose of BNC is to … … 402 402 </p> 403 403 404 <p><h 3>1.2 <a name="introSystem">Supported Systems</h3></p>404 <p><h4>1.2 <a name="introSystem">Supported Systems</h4></p> 405 405 <p> 406 406 BNC is permanently completed to finally support all existing GNSS systems throughout all features of the program. The table below shows in detail which GNSS systems are so far supported by particular applications when using the latest BNC version. Application areas named here are: … … 496 496 <br> 497 497 498 <p><h 3>1.3 <a name="introFlow">Data Flow</h3></p>498 <p><h4>1.3 <a name="introFlow">Data Flow</h4></p> 499 499 500 500 <p> … … 522 522 <p><u>Figure 4:</u> Flowchart, BNC combining Broadcast Correction streams.</p> 523 523 524 <p><h 3>1.4 <a name="introHandling">Handling</h3></p>524 <p><h4>1.4 <a name="introHandling">Handling</h4></p> 525 525 <p> 526 526 Although BNC is mainly a real-time tool to be operated online, it can be run offline … … 561 561 </p> 562 562 563 <p><h 3>1.5 <a name="introConf">Configuration</h3></p>563 <p><h4>1.5 <a name="introConf">Configuration</h4></p> 564 564 <p> 565 565 The following sections present information on how the BNC configuration works and provide configuration examples which can be adjusted according to specific user needs. … … 851 851 </p> 852 852 853 <p><h 3>1.6 <a name="introLimit">Limitations</h3></p>853 <p><h4>1.6 <a name="introLimit">Limitations</h4></p> 854 854 <ul> 855 855 <li> … … 877 877 </ul> 878 878 879 <p>< a name="optsettings"><h3>2.Settings Details</h3></p>879 <p><h3>2. <a name="optsettings">Settings Details</h3></p> 880 880 <p> 881 881 The following chapters describes how to set BNC program options. They explain the 'Top Menu Bar', the 'Settings Canvas' with the processing options, the contents of the 'Streams Canvas' and 'Logging Canvas', and the 'Bottom Menu Bar'. … … 883 883 <p> 884 884 885 <p>< a name="topmenu"><h4>2.1.Top Menu Bar</h4></p>885 <p><h4>2.1 <a name="topmenu">Top Menu Bar</h4></p> 886 886 <p> 887 887 The top menu bar allows selecting a font for the BNC windows, save configured options, or quit the program execution. It also provides access to the program's documentation. 888 888 </p> 889 889 890 <p>< a name="file"><h4>2.1.1File</h4></p>890 <p><h4>2.1.1 <a name="file">File</h4></p> 891 891 892 892 <p> … … 904 904 </p> 905 905 906 <p>< a name="help"><h4>2.1.2Help</h4></p>906 <p><h4>2.1.2 <a name="help">Help</h4></p> 907 907 908 908 <p> … … 923 923 </p> 924 924 925 <p>< a name="network"><h4>2.2.Network</h4></p>925 <p><h4>2.2 <a name="network">Network</h4></p> 926 926 <p> 927 927 You may need to specify a proxy when running BNC in a protected network. You may also like to use the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure Ntrip communication over the Internet. 928 928 </p> 929 <p>< a name="proxy"><h4>2.2.1Proxy - Usage in a protected LAN</h4></p>929 <p><h4>2.2.1 <a name="proxy">Proxy - Usage in a protected LAN</h4></p> 930 930 <p> 931 931 If you are running BNC within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNC. If you don't know the IP and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.</p> … … 934 934 </p> 935 935 936 <p>< a name="ssl"><h4>2.2.2SSL - Transport Layer Security</h4></p>936 <p><h4>2.2.2 <a name="ssl">SSL - Transport Layer Security</h4></p> 937 937 <p>Communication with an Ntrip Broadcaster over Secure Sockets Layer (SSL) as well as the download of RINEX skeleton files when available from HTTPS websites require the exchange of client and/or server certificates. Specify the path to a directory where you save certificates on your system. You may like to check out <u>http://software.rtcm-ntrip.org/wiki/Certificates</u> for a list of known Ntrip Server certificates. You may also just try communication via SSL to check out whether this is supported by the involved Ntrip Broadcaster. </p> 938 938 <p>SSL communication may involve queries coming from the Ntrip Broadcaster or from a HTTPS website hosting RINEX skeletons. Such a query could show up under BNC's 'Log' tab as follows: … … 954 954 <p><u>Figure 7:</u> BNC's 'Network' panel configured to ignore eventually occurring SSL error messages.</p> 955 955 956 <p>< a name="general"><h4>2.3.General</h4></p>956 <p><h4>2.3 <a name="general">General</h4></p> 957 957 <p> 958 958 The following defines general settings for BNC's logfile, file handling, reconfiguration on-the-fly, and auto-start. 959 959 </p> 960 960 961 <p>< a name="genlog"><h4>2.3.1Logfile - optional</h4></p>961 <p><h4>2.3.1 <a name="genlog">Logfile - optional</h4></p> 962 962 <p> 963 963 Records of BNC's activities are shown in the 'Log' tab on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. The logfile name will automatically be extended by a string '_YYMMDD' carrying the current date. This leads to series of daily logfiles when running BNC continuously for extended. Message logs cover 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 'Logfile (full path)' is an empty option field, meaning that BNC logs will not be saved into a file. … … 987 987 </pre> 988 988 989 <p>< a name="genapp"><h4>2.3.2Append Files - optional</h4></p>989 <p><h4>2.3.2 <a name="genapp">Append Files - optional</h4></p> 990 990 <p> 991 991 When BNC is started, new files are created by default and any existing files with the same name will be overwritten. However, users might want to append existing files following a restart of BNC, a system crash or when BNC crashed. Tick 'Append files' to continue with existing files and keep what has been recorded so far. Note that option 'Append files' affects all types of files created by BNC. 992 992 </p> 993 993 994 <p>< a name="genconf"><h4>2.3.3Reread Configuration - optional</h4></p>994 <p><h4>2.3.3 <a name="genconf">Reread Configuration - optional</h4></p> 995 995 <p> 996 996 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 from the disk. 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. … … 1011 1011 </p> 1012 1012 1013 <p>< a name="genstart"><h4>2.3.4Auto Start - optional</h4></p>1013 <p><h4>2.3.4 <a name="genstart">Auto Start - optional</h4></p> 1014 1014 <p> 1015 1015 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 OS X systems). … … 1019 1019 </p> 1020 1020 1021 <p>< a name="rawout"><h4>2.3.5Raw Output File - optional</h4></p>1021 <p><h4>2.3.5 <a name="rawout">Raw Output File - optional</h4></p> 1022 1022 <p> 1023 1023 BNC can save all data coming in through various streams in one daily file. The information is recorded in the specified 'Raw output file' in the received order and format. This feature allows a BNC user to run the PPP option offline with observations, Broadcast Corrections, and Broadcast Ephemeris being read from a previously saved file. It supports the offline repetition of a real-time situation for debugging purposes and it is not meant for Post Processing. … … 1036 1036 </p> 1037 1037 1038 <p>< a name="rinex"><h4>2.4.RINEX Observations</h4></p>1038 <p><h4>2.4 <a name="rinex">RINEX Observations</h4></p> 1039 1039 <p> 1040 1040 Observations will be converted to RINEX if they come in either RTCM Version 2 or RTCM Version 3 format. Depending on the RINEX version and incoming RTCM message types, files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS and/or BDS (BeiDou). In case an observation type is listed in the RINEX header but the corresponding observation is unavailable, its value is set to zero '0.000' or left blank. Note that the 'RINEX TYPE' field in the RINEX Version 3 Observation file header is always set to 'M(MIXED)' or 'Mixed' even if the file only contains data from one system. … … 1062 1062 <p><u>Figure 8:</u> BNC translating incoming observation streams to 15 min RINEX Version 3 Observation files.</p> 1063 1063 1064 <p>< a name="rnxname"><h4>2.4.1RINEX Filenames</h4></p>1064 <p><h4>2.4.1 <a name="rnxname">RINEX Filenames</h4></p> 1065 1065 <p> 1066 1066 The default for RINEX filenames in BNC follows the convention of RINEX Version 2. However, the software provides options to alternatively follow the filename convention of RINEX Version 3. RINEX Version 2 filenames 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> … … 1120 1120 </p> 1121 1121 1122 <p>< a name="rnxdir"><h4>2.4.2Directory - optional</h4></p>1122 <p><h4>2.4.2 <a name="rnxdir">Directory - optional</h4></p> 1123 1123 <p> 1124 1124 Here you can specify the path to where the RINEX Observation files will be stored. If the specified directory does not exist, BNC will not create RINEX Observation files. Default value for 'Directory' is an empty option field, meaning that no RINEX Observation files will be written. 1125 1125 </p> 1126 1126 1127 <p>< a name="rnxinterval"><h4>2.4.3File Interval - mandatory if 'Directory' is set</h4></p>1127 <p><h4>2.4.3 <a name="rnxinterval">File Interval - mandatory if 'Directory' is set</h4></p> 1128 1128 <p> 1129 1129 Select the length of the RINEX Observation file generated. The default value is 15 minutes. 1130 1130 </p> 1131 1131 1132 <p>< a name="rnxsample"><h4>2.4.4Sampling - mandatory if 'Directory' is set </h4></p>1132 <p><h4>2.4.4 <a name="rnxsample">Sampling - mandatory if 'Directory' is set </h4></p> 1133 1133 <p> 1134 1134 Select the RINEX Observation sampling interval in seconds. A value of zero '0' tells BNC to store all received epochs into RINEX. This is the default value. 1135 1135 </p> 1136 1136 1137 <p>< a name="rnxskl"><h4>2.4.5Skeleton Extension - optional</h4></p>1137 <p><h4>2.4.5 <a name="rnxskl">Skeleton Extension - optional</h4></p> 1138 1138 <p> 1139 1139 Whenever BNC starts generating RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. A HTTP or HTTPS link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See <u>http://www.epncb.oma.be:80/stations/log/skl/brus.skl</u> for an example of a public RINEX header skeleton file for EPN station Brussels. Note that the download of RINEX skeleton files from HTTPS websites requires the exchange of client and/or server certificates. Clarify 'SSL' options offered through panel 'Network' for details. … … 1213 1213 <p> 1214 1214 1215 <p>< a name="sklMandat"><h4>2.4.6Skeleton Mandatory - optional</h4></p>1215 <p><h4>2.4.6 <a name="sklMandat">Skeleton Mandatory - optional</h4></p> 1216 1216 <p> 1217 1217 Tick check box 'Skeleton mandatory' in case you want that RINEX files are only produced if skeleton files are available for BNC. If no skeleton file is available for a particular source then no RINEX observation file will be produced from the affected stream. … … 1220 1220 </p> 1221 1221 1222 <p>< a name="rnxscript"><h4>2.4.7Script - optional</h4></p>1222 <p><h4>2.4.7 <a name="rnxscript">Script - optional</h4></p> 1223 1223 <p> 1224 1224 Whenever a RINEX Observation file is saved, you might want to compress, copy or upload it immediately via FTP. BNC allows you to execute a script/batch file to carry out these operations. To do that, specify the full path of the script/batch file here. BNC will pass the RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux/Mac OS X systems). … … 1231 1231 </p> 1232 1232 1233 <p>< a name="rnxvers2"><h4>2.4.8Version 2 - optional</h4></p>1233 <p><h4>2.4.8 <a name="rnxvers2">Version 2 - optional</h4></p> 1234 1234 <p> 1235 1235 GNSS observation data are generally hold available within BNC according to attributes as defined in RINEX Version 3. These attributes describe the tracking mode or channel when generating the observation signals. Capital letters specifying signal generation attributes are A, B, C, D, I, L, M, N, P, Q, S, W, X, Y, and Z, see RINEX Version 3 documentation. Although RINEX Version 3 with its signal generation attributes is the internal default processing format for BNC, there are two applications where the program is explicitly required to produce data in RINEX Version 2 format: … … 1262 1262 </p> 1263 1263 1264 <p>< a name="rnxvers3"><h4>2.4.9Version 3 - optional</h4></p>1264 <p><h4>2.4.9 <a name="rnxvers3">Version 3 - optional</h4></p> 1265 1265 <p> 1266 1266 The default format for RINEX Observation files is RINEX Version 2.11. Select RINEX 'Version 3' if you would like to save RTCM Version 3 observation streams in RINEX Version 3 format. … … 1271 1271 </p> 1272 1272 1273 <p>< a name="rnxvers3File"><h4>2.4.10Version 3 Filenames - optional</h4></p>1273 <p><h4>2.4.10 <a name="rnxvers3File">Version 3 Filenames - optional</h4></p> 1274 1274 <p> 1275 1275 Tick check box 'Version 3 filenames' to let BNC create so-called extended filenames following the RINEX Version 3 standard. … … 1278 1278 </p> 1279 1279 1280 <p>< a name="ephemeris"><h4>2.5.RINEX Ephemeris</h4></p>1280 <p><h4>2.5 <a name="ephemeris">RINEX Ephemeris</h4></p> 1281 1281 <p> 1282 1282 Broadcast Ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3 e.g. as message types 1019 (GPS) or 1020 (GLONASS) or 1044 (QZSS) or 1043 (SBAS) or 1045 and 1046 (Galileo) or 63 (tentative, BDS/BeiDou). The filename convention follows the details given in section 'RINEX Filenames' except that the first four characters are 'BRDC'. … … 1303 1303 </p> 1304 1304 1305 <p>< a name="ephdir"><h4>2.5.1Directory - optional</h4></p>1305 <p><h4>2.5.1 <a name="ephdir">Directory - optional</h4></p> 1306 1306 <p> 1307 1307 Specify a path for saving Broadcast Ephemeris data as RINEX Navigation files. If the specified directory does not exist, BNC will not create RINEX Navigation files. Default value for Ephemeris 'Directory' is an empty option field, meaning that no RINEX Navigation files will be created. 1308 1308 </p> 1309 1309 1310 <p>< a name="ephint"><h4>2.5.2Interval - mandatory if 'Directory' is set</h4></p>1310 <p><h4>2.5.2 <a name="ephint">Interval - mandatory if 'Directory' is set</h4></p> 1311 1311 <p> 1312 1312 Select the length of RINEX Navigation files. The default value is '1 day'. 1313 1313 </p> 1314 1314 1315 <p>< a name="ephport"><h4>2.5.3Port - optional</h4></p>1315 <p><h4>2.5.3 <a name="ephport">Port - optional</h4></p> 1316 1316 <p> 1317 1317 BNC can output Broadcast Ephemeris in RINEX Version 3 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 ASCII ephemeris output via IP port is generated. … … 1321 1321 </p> 1322 1322 1323 <p>< a name="ephvers"><h4>2.5.4Version - optional</h4></p>1323 <p><h4>2.5.4 <a name="ephvers">Version - optional</h4></p> 1324 1324 <p> 1325 1325 Default format for RINEX Navigation files containing Broadcast Ephemeris is RINEX Version 2.11. Select 'Version 3' if you want to save the ephemeris data in RINEX Version 3 format. … … 1329 1329 </p> 1330 1330 1331 <p>< a name="ephversFile"><h4>2.5.5Version 3 Filenames - optional</h4></p>1331 <p><h4>2.5.5 <a name="ephversFile">Version 3 Filenames - optional</h4></p> 1332 1332 <p> 1333 1333 Tick check box 'Version 3 filenames' to let BNC create so-called extended filenames following the RINEX Version 3 standard. … … 1339 1339 <p><u>Figure 9:</u> Converting Broadcast Ephemeris stream to RINEX Version 3 Navigation file.</p> 1340 1340 1341 <p>< a name="reqc"><h4>2.6.RINEX Editing & QC</h4></p>1341 <p><h4>2.6 <a name="reqc">RINEX Editing & QC</h4></p> 1342 1342 <p> 1343 1343 Besides stream conversion from RTCM to RINEX, BNC allows editing RINEX files or concatenate their contents. RINEX Observation and Navigation files can be handled. BNC can also carry out a RINEX file Quality Check. In summary and besides Stream <u><b>T</b></u>ranslation this functionality in BNC covers … … 1356 1356 </p> 1357 1357 1358 <p>< a name="reqcact"><h4>2.6.1Action - optional</h4></p>1358 <p><h4>2.6.1 <a name="reqcact">Action - optional</h4></p> 1359 1359 <p>Select an action. Options are 'Edit/Concatenate' and 'Analyze'. 1360 1360 <ul> … … 1364 1364 </p> 1365 1365 1366 <p>< a name="reqcinp"><h4>2.6.2Input Files - mandatory</h4></p>1366 <p><h4>2.6.2 <a name="reqcinp">Input Files - mandatory</h4></p> 1367 1367 <p> 1368 1368 Specify full path to input RINEX Observation file(s), and<br> … … 1376 1376 </p> 1377 1377 1378 <p>< a name="reqcout"><h4>2.6.3Output Files - optional if 'Action' is set to 'Edit/Concatenate'</h4></p>1378 <p><h4>2.6.3 <a name="reqcout">Output Files - optional if 'Action' is set to 'Edit/Concatenate'</h4></p> 1379 1379 <p> 1380 1380 If 'Edit/Concatenate' is selected, specifying the full path to output RINEX Observation file(s) and specifying the full path to output RINEX Navigation file(s) is optional. Default are empty option fields, meaning that no RINEX files will be saved on disk. 1381 1381 </p> 1382 1382 1383 <p>< a name="reqclog"><h4>2.6.4Logfile - optional</h4></p>1383 <p><h4>2.6.4 <a name="reqclog">Logfile - optional</h4></p> 1384 1384 <p> 1385 1385 Specify the name of a logfile to save information on RINEX file Editing/Concatenation or Analysis. Default is an empty option field, meaning that no logfile will be saved. … … 1601 1601 </p> 1602 1602 1603 <p>< a name="reqcplots"><h4>2.6.5Plots for Signals - mandatory if 'Action' is set to 'Analyze'</h4></p>1603 <p><h4>2.6.5 <a name="reqcplots">Plots for Signals - mandatory if 'Action' is set to 'Analyze'</h4></p> 1604 1604 <p> 1605 1605 Multipath and signal-to-noise sky plots as well as plots for satellite availability, elevation and PDOP are produced per GNSS system and frequency with the multipath analysis based on CnC observation types (n = band / frequency). The 'Plots for signals' option lets you exactly specify the observation signals to be used for that and also enables the plot production. You can specify the navigation system (C = BDS, E = Galileo, G = GPS, J = QZSS, R = GLONASS, S = SBAS), the frequency, and the tracking mode or channel as defined in RINEX Version 3. Specifications for frequency and tracking mode or channel must be separated by ampersand character '&'. Specifications for each navigation systems must be separated by blank character ' '. The following string is an example for option field 'Plots of signals': It lets you exactly specify the observation signals to be used and also enables the plot generation. You can specify the navigation system, the frequency, and the tracking mode or channel as defined in RINEX Version 3. Specifications for frequency and tracking mode or channel must be separated by ampersand character '&'. Specifications for each navigation systems must be separated by blank character ' '. … … 1619 1619 </p> 1620 1620 1621 <p>< a name="reqcdir"><h4>2.6.6Directory for Plots - optional if 'Action' is set to 'Analyze'</h4></p>1621 <p><h4>2.6.6 <a name="reqcdir">Directory for Plots - optional if 'Action' is set to 'Analyze'</h4></p> 1622 1622 <p> 1623 1623 If 'Analyze' is selected, specifying the path to a directory where plot files will be saved is optional. Filenames will be composed from the RINEX input filename(s) plus suffix 'PNG' to indicate the plot file format in use. Default is an empty option field, meaning that plots will not be saved on disk. 1624 1624 </p> 1625 1625 1626 <p>< a name="reqcedit"><h4>2.6.7Set Edit Options - mandatory if 'Action' is set to 'Edit/Concatenate'</h4></p>1626 <p><h4>2.6.7 <a name="reqcedit">Set Edit Options - mandatory if 'Action' is set to 'Edit/Concatenate'</h4></p> 1627 1627 <p>Once the 'Edit/Concatenate' action is selected, you have to 'Set Edit Options'. BNC lets you specify the RINEX version, a signal priority list when mapping RINEX Version 3 to Version 2, the sampling interval, begin and end of file, operator, observation types, comment lines, and marker, antenna, receiver details. Note that some of the specifications for editing and concatenation are only meaningful for RINEX Observation files but not for RINEX Navigation files. 1628 1628 </p> … … 1677 1677 <p><u>Figure 15:</u> Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC.</p> 1678 1678 1679 <p>< a name="reqccommand"><h4>2.6.8Command Line, No Window - optional</h4></p>1679 <p><h4>2.6.8 <a name="reqccommand">Command Line, No Window - optional</h4></p> 1680 1680 <p> 1681 1681 BNC applies options from the configuration file but allows updating every one of them on the command line while the contents of the configuration file remains unchanged, see section on 'Command Line Options'. The syntax for that looks as follows … … 1754 1754 </table> 1755 1755 1756 <p>< a name="sp3comp"><h4>2.7.SP3 Comparison</h4></p>1756 <p><h4>2.7 <a name="sp3comp">SP3 Comparison</h4></p> 1757 1757 <p> 1758 1758 BNC allows to compare the contents of two files containing GNSS orbit and clock data in SP3 format. SP3 ASCII files basically contain a list of records over a certain period of time. Each record carries a time tag, the XYZ position of the satellite's Center of Mass at that time and the corresponding satellite clock value. Both SP3 files may contain some records for different epochs. If so then BNC only compares records for identical epochs. BNC accepts that a specific GNSS system or a specific satellite is only available from one of the SP3 files. Note that BNC does not interpolate orbits when comparing SP3 files. … … 1762 1762 </p> 1763 1763 1764 <p>< a name="sp3input"><h4>2.7.1Input SP3 Files - optional</h4></p>1764 <p><h4>2.7.1 <a name="sp3input">Input SP3 Files - optional</h4></p> 1765 1765 <p> 1766 1766 Specify the full path of two SP3 files separated by a comma. 1767 1767 </p> 1768 1768 1769 <p>< a name="sp3exclude"><h4>2.7.2Exclude Satellites - optional</h4></p>1769 <p><h4>2.7.2 <a name="sp3exclude">Exclude Satellites - optional</h4></p> 1770 1770 <p> 1771 1771 You may want to exclude one or more satellites in your SP3 files from the comparison. Or you may like to exclude all satellites of a specific GNSS system from the comparison. The following are example strings to be entered for excluding satellites from the comparison. … … 1782 1782 </p> 1783 1783 1784 <p>< a name="sp3log"><h4>2.7.3Logfile - mandatory if 'Input SP3 Files' is set</h4></p>1784 <p><h4>2.7.3 <a name="sp3log">Logfile - mandatory if 'Input SP3 Files' is set</h4></p> 1785 1785 <p> 1786 1786 Specify a logfile name to save results of the SP3 file comparison. … … 1867 1867 <p><u>Figure 16:</u> BNC configuration example for comparing two SP3 files with satellite orbit and clock data.</p> 1868 1868 1869 <p>< a name="correct"><h4>2.8.Broadcast Corrections</h4></p>1869 <p><h4>2.8 <a name="correct">Broadcast Corrections</h4></p> 1870 1870 <p> 1871 1871 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 'Observation Space Representation' (OSR). … … 2135 2135 </p> 2136 2136 2137 <p>< a name="corrdir"><h4>2.8.1Directory, ASCII - optional</h4></p>2137 <p><h4>2.8.1 <a name="corrdir">Directory, ASCII - optional</h4></p> 2138 2138 <p> 2139 2139 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. 2140 2140 </p> 2141 2141 2142 <p>< a name="corrint"><h4>2.8.2Interval - mandatory if 'Directory, ASCII' is set</h4></p>2142 <p><h4>2.8.2 <a name="corrint">Interval - mandatory if 'Directory, ASCII' is set</h4></p> 2143 2143 <p> 2144 2144 Select the length of the Broadcast Correction files. The default value is 1 day. 2145 2145 </p> 2146 2146 2147 <p>< a name="corrport"><h4>2.8.3Port - optional</h4></p>2147 <p><h4>2.8.3 <a name="corrport">Port - optional</h4></p> 2148 2148 <p> 2149 2149 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. … … 2223 2223 <p><u>Figure 17:</u> BNC configuration example for pulling, saving and output of Broadcast Corrections.</p> 2224 2224 2225 <p>< a name="syncout"><h4>2.9.Feed Engine</h4></p>2225 <p><h4>2.9 <a name="syncout">Feed Engine</h4></p> 2226 2226 <p> 2227 2227 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 sorted per incoming stream. … … 2304 2304 <p><u>Figure 18:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p> 2305 2305 2306 <p>< a name="syncport"><h4>2.9.1Port - optional</h4></p>2306 <p><h4>2.9.1 <a name="syncport">Port - optional</h4></p> 2307 2307 <p> 2308 2308 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 observation data for any specific epoch which become available within a certain number of latency seconds (see 'Wait for Full Obs Epoch' option). It then - epoch by epoch - outputs whatever has been received. The output comes block wise per stream. 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> 2309 2309 </p> 2310 2310 2311 <p>< a name="syncwait"><h4>2.9.2Wait for Full Obs Epoch - mandatory if 'Port' is set</h4></p>2311 <p><h4>2.9.2 <a name="syncwait">Wait for Full Obs Epoch - mandatory if 'Port' is set</h4></p> 2312 2312 <p> 2313 2313 When feeding a real-time GNSS network engine waiting for synchronized observations epoch by epoch, BNC drops whatever is received later than 'Wait for full obs 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 obs epoch' is 5 seconds. … … 2317 2317 </p> 2318 2318 2319 <p>< a name="syncsample"><h4>2.9.3Sampling - mandatory if 'File' or 'Port' is set</h4></p>2319 <p><h4>2.9.3 <a name="syncsample">Sampling - mandatory if 'File' or 'Port' is set</h4></p> 2320 2320 <p> 2321 2321 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. 2322 2322 </p> 2323 2323 2324 <p>< a name="syncfile"><h4>2.9.4File - optional</h4></p>2324 <p><h4>2.9.4 <a name="syncfile">File - optional</h4></p> 2325 2325 <p> 2326 2326 Specify 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. … … 2330 2330 </p> 2331 2331 2332 <p>< a name="syncuport"><h4>2.9.5Port (unsynchronized) - optional</h4></p>2332 <p><h4>2.9.5 <a name="syncuport">Port (unsynchronized) - optional</h4></p> 2333 2333 <p> 2334 2334 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. Nevertheless, the output comes block wise per stream. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no unsynchronized output is generated. 2335 2335 </p> 2336 2336 2337 <p>< a name="serial"><h4>2.10.Serial Output</h4></p>2337 <p><h4>2.10 <a name="serial">Serial Output</h4></p> 2338 2338 <p> 2339 2339 You may use BNC to feed a serial connected device like a GNSS receiver. For that an incoming stream can be forwarded to a serial port. Depending on the stream contents the receiver may use it for Differential GNSS, Precise Point Positioning or any other purpose supported by its firmware. … … 2353 2353 <p><u>Figure 20:</u> BNC pulling a VRS stream to feed a serial connected RTK rover.</p> 2354 2354 2355 <p>< a name="sermount"><h4>2.10.1Mountpoint - optional</h4></p>2355 <p><h4>2.10.1 <a name="sermount">Mountpoint - optional</h4></p> 2356 2356 <p> 2357 2357 Enter a 'Mountpoint' to forward its corresponding stream to a serial connected GNSS receiver. … … 2361 2361 </p> 2362 2362 2363 <p>< a name="serport"><h4>2.10.2Port Name - mandatory if 'Mountpoint' is set</h4></p>2363 <p><h4>2.10.2 <a name="serport">Port Name - mandatory if 'Mountpoint' is set</h4></p> 2364 2364 <p> 2365 2365 Enter the serial 'Port name' selected on your host for communication with the serial connected receiver. Valid port names are … … 2378 2378 </p> 2379 2379 2380 <p>< a name="serbaud"><h4>2.10.3Baud Rate - mandatory if 'Mountpoint' is set</h4></p>2380 <p><h4>2.10.3 <a name="serbaud">Baud Rate - mandatory if 'Mountpoint' is set</h4></p> 2381 2381 <p> 2382 2382 Select a 'Baud rate' for the serial output link. Note that using a high baud rate is recommended. 2383 2383 </p> 2384 2384 2385 <p>< a name="serflow"><h4>2.10.4Flow Control - mandatory if 'Mountpoint' is set</h4></p>2385 <p><h4>2.10.4 <a name="serflow">Flow Control - mandatory if 'Mountpoint' is set</h4></p> 2386 2386 <p> 2387 2387 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. 2388 2388 </p> 2389 2389 2390 <p>< a name="serparity"><h4>2.10.5Parity - mandatory if 'Mountpoint' is set</h4></p>2390 <p><h4>2.10.5 <a name="serparity">Parity - mandatory if 'Mountpoint' is set</h4></p> 2391 2391 <p> 2392 2392 Select the 'Parity' for the serial output link. Note that parity is often set to 'NONE'. 2393 2393 </p> 2394 2394 2395 <p>< a name="serdata"><h4>2.10.6Data Bits - mandatory if 'Mountpoint' is set</h4></p>2395 <p><h4>2.10.6 <a name="serdata">Data Bits - mandatory if 'Mountpoint' is set</h4></p> 2396 2396 <p> 2397 2397 Select the number of 'Data bits' for the serial output link. Note that often '8' data bits are used. 2398 2398 </p> 2399 2399 2400 <p>< a name="serstop"><h4>2.10.7Stop Bits - mandatory if 'Mountpoint' is set</h4></p>2400 <p><h4>2.10.7 <a name="serstop">Stop Bits - mandatory if 'Mountpoint' is set</h4></p> 2401 2401 <p> 2402 2402 Select the number of 'Stop bits' for the serial output link. Note that often '1' stop bit is used. 2403 2403 </p> 2404 2404 2405 <p>< a name="serauto"><h4>2.10.8NMEA - mandatory if 'Mountpoint' is set</h4></p>2405 <p><h4>2.10.8 <a name="serauto">NMEA - mandatory if 'Mountpoint' is set</h4></p> 2406 2406 <p>The 'NMEA' option supports the so-called 'Virtual Reference Station' (VRS) concept which requires the receiver to send approximate position information to the Ntrip Broadcaster. Select 'no' if you don't want BNC to forward or upload any NMEA message to the Ntrip broadcaster in support of VRS. 2407 2407 </p> … … 2413 2413 </p> 2414 2414 2415 <p>< a name="serfile"><h4>2.10.9File - optional if 'NMEA' is set to 'Auto'</h4></p>2415 <p><h4>2.10.9 <a name="serfile">File - optional if 'NMEA' is set to 'Auto'</h4></p> 2416 2416 <p>Specify the full path to a file where NMEA messages coming from your serial connected receiver are saved. Default is an empty option field, meaning that no NMEA messages will be saved on disk. 2417 2417 </p> 2418 <p>< a name="serheight"><h4>2.10.10Height - mandatory if 'NMEA' is set to 'Manual'</h4></p>2418 <p><h4>2.10.10 <a name="serheight">Height - mandatory if 'NMEA' is set to 'Manual'</h4></p> 2419 2419 <p> 2420 2420 Specify an approximate 'Height' above mean sea level in meters for the reference station introduced through 'Mountpoint'. Together with the latitude and longitude from the Ntrip broadcaster source-table the height information is used to build GGA messages to be sent to the Ntrip broadcaster. … … 2425 2425 </p> 2426 2426 2427 <p>< a name="sersampl"><h4>2.10.11Sampling - mandatory if 'NMEA' is set to 'Manual'</h4></p>2427 <p><h4>2.10.11 <a name="sersampl">Sampling - mandatory if 'NMEA' is set to 'Manual'</h4></p> 2428 2428 <p> 2429 2429 Select a sampling interval in seconds for manual generation and upload of NMEA GGA sentences. … … 2433 2433 </p> 2434 2434 2435 <p>< a name="advnote"><h4>2.11.Outages</h4></p>2435 <p><h4>2.11 <a name="advnote">Outages</h4></p> 2436 2436 <p> 2437 2437 At any time an incoming stream might become unavailable or corrupted. In such cases, it is important that the BNC operator and/or the stream providers become aware of the situation so that necessary measures can be taken to restore the stream. Furthermore, continuous attempts to decode a corrupted stream can generate unnecessary workload for BNC. Outages and corruptions are handled by BNC as follows: … … 2447 2447 </p> 2448 2448 2449 <p>< a name="obsrate"><h4>2.11.1Observation Rate - optional</h4></p>2449 <p><h4>2.11.1 <a name="obsrate">Observation Rate - optional</h4></p> 2450 2450 <p> 2451 2451 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 priori estimate of the expected observation rate of the incoming streams.</p><p>An empty option field (default) means that you don't want explicit information from BNC about stream outages and incoming streams that cannot be decoded. 2452 2452 </p> 2453 2453 2454 <p>< a name="advfail"><h4>2.11.2Failure Threshold - mandatory if 'Observation rate' is set</h4></p>2454 <p><h4>2.11.2 <a name="advfail">Failure Threshold - mandatory if 'Observation rate' is set</h4></p> 2455 2455 <p> 2456 2456 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 inundate user with too many event reports. … … 2460 2460 </p> 2461 2461 2462 <p>< a name="advreco"><h4>2.11.3Recovery Threshold - mandatory if 'Observation rate' is set</h4></p>2462 <p><h4>2.11.3 <a name="advreco">Recovery Threshold - mandatory if 'Observation rate' is set</h4></p> 2463 2463 <p> 2464 2464 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 inundate users with too many event reports. … … 2468 2468 </p> 2469 2469 2470 <p>< a name="advscript"><h4>2.11.4Script - optional if 'Observation rate' is set</h4></p>2470 <p><h4>2.11.4 <a name="advscript">Script - optional if 'Observation rate' is set</h4></p> 2471 2471 <p> 2472 2472 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 OS X systems) together with date and time information. … … 2501 2501 </p> 2502 2502 2503 <p>< a name="misc"><h4>2.12.Miscellaneous</h4></p>2503 <p><h4>2.12 <a name="misc">Miscellaneous</h4></p> 2504 2504 <p> 2505 2505 This section describes several miscellaneous options which can be applied to a single stream (mountpoint) or to all configured streams. … … 2513 2513 2514 2514 2515 <p>< a name="miscmount"><h4>2.12.1Mountpoint - optional </h4></p>2515 <p><h4>2.12.1 <a name="miscmount">Mountpoint - optional </h4></p> 2516 2516 <p> 2517 2517 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. 2518 2518 </p> 2519 2519 2520 <p>< a name="miscperf"><h4>2.12.2Log Latency - optional </h4></p>2520 <p><h4>2.12.2 <a name="miscperf">Log Latency - optional </h4></p> 2521 2521 <p> 2522 2522 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 one (first incoming) observation or Broadcast Correction 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 visualized latencies from the 'Latency' tab on the bottom of the main window represent individual latencies and not the mean latencies for the logfile. … … 2546 2546 2547 2547 2548 <p>< a name="miscscan"><h4>2.12.3Scan RTCM - optional</h4></p>2548 <p><h4>2.12.3 <a name="miscscan">Scan RTCM - optional</h4></p> 2549 2549 <p> 2550 2550 When configuring a GNSS receiver for RTCM stream generation, the firmware's setup interface may not provide details about RTCM message types and observation 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. Contained observation types are also printed because such information is required a priori for the conversion of RTCM Version 3 MSM streams to RINEX Version 3 files. The idea for this option arose from 'inspectRTCM', a comprehensive stream analyzing tool written by D. Stoecker. … … 2581 2581 2582 2582 2583 <p>< a name="miscport"><h4>2.12.4Port - optional</h4></p>2583 <p><h4>2.12.4 <a name="miscport">Port - optional</h4></p> 2584 2584 <p> 2585 2585 BNC can output streams related to the above specified 'Mountpoint' through a TCP/IP port of your local host. Enter a port number to activate this function. The stream contents remains untouched. BNC does not decode or reformat the data. … … 2593 2593 2594 2594 2595 <p>< a name="pppclient"><h4>2.13.PPP Client</h4></p>2595 <p><h4>2.13 <a name="pppclient">PPP Client</h4></p> 2596 2596 <p> 2597 2597 BNC can derive coordinates for rover positions following the Precise Point Positioning (PPP) approach. It uses either code or code plus phase data from one or more GNSS systems in ionosphere-free linear combinations P3 or L3. Besides pulling streams of observations from dual frequency GNSS receiver, this also … … 2630 2630 </p> 2631 2631 2632 <p>< a name="pppInp"><h4>2.13.1PPP (1): Input and Output</h4></p>2632 <p><h4>2.13.1 <a name="pppInp">PPP (1): Input and Output</h4></p> 2633 2633 <p> 2634 2634 This panel provides options for specifying the input and output streams and files required by BNC for real-time or post processing PPP. … … 2638 2638 <p><u>Figure 22:</u> Real-time Precise Point Positioning with BNC, PPP Panel 1.</p> 2639 2639 2640 <p>< a name="pppdatasource"><h4>2.13.1.1Data Source - optional</h4></p>2640 <p><h4>2.13.1.1 <a name="pppdatasource">Data Source - optional</h4></p> 2641 2641 <p> 2642 2642 Choose between input from 'Real-time Streams' or 'RINEX Files' for PPP with BNC in real-time or post processing mode. … … 2668 2668 </p> 2669 2669 2670 <p>< a name="ppprnxobs"><h4>2.13.1.2RINEX Observation File - mandatory if 'Data source' is set to 'RINEX Files'</h4></p>2670 <p><h4>2.13.1.2 <a name="ppprnxobs">RINEX Observation File - mandatory if 'Data source' is set to 'RINEX Files'</h4></p> 2671 2671 <p> 2672 2672 Specify a RINEX Observation file. The file format can be RINEX Version 2 or RINEX Version 3. 2673 2673 </p> 2674 2674 2675 <p>< a name="ppprnxnav"><h4>2.13.1.3RINEX Navigation File - mandatory if 'Data source' is set to 'RINEX Files'</h4></p>2675 <p><h4>2.13.1.3 <a name="ppprnxnav">RINEX Navigation File - mandatory if 'Data source' is set to 'RINEX Files'</h4></p> 2676 2676 <p> 2677 2677 Specify a RINEX Navigation file. The file format can be RINEX Version 2 or RINEX Version 3. 2678 2678 </p> 2679 2679 2680 <p>< a name="pppcorrstream"><h4>2.13.1.4Corrections Stream - optional if 'Data source' is set to 'Real-Time Streams'</h4></p>2680 <p><h4>2.13.1.4 <a name="pppcorrstream">Corrections Stream - optional if 'Data source' is set to 'Real-Time Streams'</h4></p> 2681 2681 <p> 2682 2682 Specify a Broadcast 'Corrections stream' from the list of selected 'Streams' you are pulling if you want BNC to correct your satellite ephemeris accordingly. Note that the stream's orbit and clock corrections must refer to the satellite Antenna Phase Center (APC). Streams providing such corrections are made available e.g. through the International GNSS Service (IGS) and listed on <u>http://igs.bkg.bund.de/ntrip/orbits</u>. The stream format must be RTCM Version 3 containing so-called SSR messages. Streams 'IGS03' and 'CLK11' supporting GPS plus GLONASS are examples. … … 2686 2686 </p> 2687 2687 2688 <p>< a name="pppcorrfile"><h4>2.13.1.5Corrections File - optional if 'Data source' is set to 'RINEX Files'</h4></p>2688 <p><h4>2.13.1.5 <a name="pppcorrfile">Corrections File - optional if 'Data source' is set to 'RINEX Files'</h4></p> 2689 2689 <p> 2690 2690 Specify a Broadcast 'Corrections file' as saved beforehand using BNC. The file contents is basically the ASCII representation of a RTCM Version 3 Broadcast Correction (SSR) stream. … … 2694 2694 </p> 2695 2695 2696 <p>< a name="pppantexfile"><h4>2.13.1.6ANTEX File - optional</h4></p>2696 <p><h4>2.13.1.6 <a name="pppantexfile">ANTEX File - optional</h4></p> 2697 2697 <p> 2698 2698 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 in PPP for antenna phase center offsets and variations. Note that for applying such corrections you need to specify the receiver's antenna name and radome in BNC's 'Coordinates' file. … … 2702 2702 </p> 2703 2703 2704 <p>< a name="pppmarkcoor"><h4>2.13.1.7Coordinates - optional </h4></p>2704 <p><h4>2.13.1.7 <a name="pppmarkcoor">Coordinates - optional </h4></p> 2705 2705 <p> 2706 2706 Enter the full path to an ASCII file which specifies all streams or files from stationary or mobile receivers you potentially may want to process. Specifying a 'Coordinates' file is optional. If it exists, it should contain one record per stream or file with the following parameters separated by blank characters: … … 2798 2798 </p> 2799 2799 2800 <p>< a name="pppv3filename"><h4>2.13.1.8Version 3 Filenames - optional</h4></p>2800 <p><h4>2.13.1.8 <a name="pppv3filename">Version 3 Filenames - optional</h4></p> 2801 2801 <p> 2802 2802 Tick 'Version 3 filenames' to let BNC create so-called extended filenames for PPP logfiles, NMEA files and SINEX Troposphere files to follow the RINEX Version 3 standard, see section 'RINEX Filenames' for details. … … 2825 2825 </p> 2826 2826 2827 <p>< a name="ppplogfile"><h4>2.13.1.9Logfile Directory - optional</h4></p>2827 <p><h4>2.13.1.9 <a name="ppplogfile">Logfile Directory - optional</h4></p> 2828 2828 <p> 2829 2829 Essential PPP results are shown in the 'Log' tab on the bottom of BNC's main window. Depending on the processing options, the following values are presented about once per second (example): … … 2957 2957 </p> 2958 2958 2959 <p>< a name="pppnmeafile"><h4>2.13.1.10NMEA Directory - optional</h4></p>2959 <p><h4>2.13.1.10 <a name="pppnmeafile">NMEA Directory - optional</h4></p> 2960 2960 <p> 2961 2961 You can specify a 'NMEA directory' to save daily NMEA files with Point Positioning results recorded as NMEA sentences. Such sentences are usually generated about once per second with pairs of … … 2998 2998 </p> 2999 2999 3000 <p>< a name="pppsnxtrofile"><h4>2.13.1.11SNX TRO Directory - optional</h4></p>3000 <p><h4>2.13.1.11 <a name="pppsnxtrofile">SNX TRO Directory - optional</h4></p> 3001 3001 <p> 3002 3002 BNC estimates the tropospheric delay according to equation … … 3078 3078 </p> 3079 3079 3080 <p>< a name="pppsnxtrointr"><h4>2.13.1.11.1Interval - mandatory if 'SINEX TRO File' is set</h4></p>3080 <p><h4>2.13.1.11.1 <a name="pppsnxtrointr">Interval - mandatory if 'SINEX TRO File' is set</h4></p> 3081 3081 <p> 3082 3082 Select the length of SINEX Troposphere files. … … 3087 3087 3088 3088 3089 <p>< a name="pppsnxtrosampl"><h4>2.13.1.11.2Sampling - mandatory if 'SINEX TRO File' is set</h4></p>3089 <p><h4>2.13.1.11.2 <a name="pppsnxtrosampl">Sampling - mandatory if 'SINEX TRO File' is set</h4></p> 3090 3090 <p> 3091 3091 Select a 'Sampling' rate in seconds for saving troposphere parameters. … … 3095 3095 </p> 3096 3096 3097 <p>< a name="pppStation"><h4>2.13.2PPP (2): Processed Stations</h4></p>3097 <p><h4>2.13.2 <a name="pppStation">PPP (2): Processed Stations</h4></p> 3098 3098 3099 3099 <p> … … 3110 3110 <p><u>Figure 23:</u> Precise Point Positioning with BNC, PPP Panel 2.</p> 3111 3111 3112 <p>< a name="pppsite"><h4>2.13.2.1Station - mandatory</h4></p>3112 <p><h4>2.13.2.1 <a name="pppsite">Station - mandatory</h4></p> 3113 3113 <p> 3114 3114 Hit the 'Add Station' button, double click on the 'Station' field, then specify an observation's mountpoint from the 'Streams' section or introduce the 4-character Station ID of your RINEX observation file and hit Enter. BNC will only produce PPP solutions for stations listed in this table. 3115 3115 </p> 3116 3116 3117 <p>< a name="pppnehsigma"><h4>2.13.2.2Sigma North/East/Up - mandatory</h4></p>3117 <p><h4>2.13.2.2 <a name="pppnehsigma">Sigma North/East/Up - mandatory</h4></p> 3118 3118 <p> 3119 3119 Enter a sigmas in meters for the initial coordinate components. 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 well-known position - so-called Quick-Start mode. 3120 3120 </p> 3121 3121 3122 <p>< a name="pppnehnoise"><h4>2.13.2.3Noise North/East/Up - mandatory</h4></p>3122 <p><h4>2.13.2.3 <a name="pppnehnoise">Noise North/East/Up - mandatory</h4></p> 3123 3123 <p> 3124 3124 Enter a white 'Noise' in meters for estimated coordinate components. A value of 100.0 (default) may be appropriate when considering possible sudden movements of a rover. 3125 3125 </p> 3126 3126 3127 <p>< a name="ppptropsigma"><h4>2.13.2.4Tropo Sigma - mandatory</h4></p>3127 <p><h4>2.13.2.4 <a name="ppptropsigma">Tropo Sigma - mandatory</h4></p> 3128 3128 <p> 3129 3129 Enter a sigma in meters for the a priori model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice. 3130 3130 </p> 3131 3131 3132 <p>< a name="ppptropnoise"><h4>2.13.2.5Tropo Noise - mandatory</h4></p>3132 <p><h4>2.13.2.5 <a name="ppptropnoise">Tropo Noise - mandatory</h4></p> 3133 3133 <p> 3134 3134 Enter a white 'Noise' 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. 3135 3135 </p> 3136 3136 3137 <p>< a name="pppnmeaport"><h4>2.13.2.6NMEA Port - optional</h4></p>3137 <p><h4>2.13.2.6 <a name="pppnmeaport">NMEA Port - optional</h4></p> 3138 3138 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. 3139 3139 </p> … … 3145 3145 </p> 3146 3146 3147 <p>< a name="pppOptions"><h4>2.13.3PPP (3): Processing Options</h4></p>3147 <p><h4>2.13.3 <a name="pppOptions">PPP (3): Processing Options</h4></p> 3148 3148 <p>BNC allows using various Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows introducing specific sigmas for code and phase observations as well as for a priori 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. 3149 3149 </p> … … 3155 3155 <p><u>Figure 24:</u> Precise Point Positioning with BNC, PPP Panel 3.</p> 3156 3156 3157 <p>< a name="ppplinecombi"><h4>2.13.3.1Linear Combinations - mandatory</h4></p>3157 <p><h4>2.13.3.1 <a name="ppplinecombi">Linear Combinations - mandatory</h4></p> 3158 3158 <p> 3159 3159 <p> … … 3173 3173 </p> 3174 3174 3175 <p>< a name="pppcodeobs"><h4>2.13.3.2Code Observations - mandatory</h4></p>3175 <p><h4>2.13.3.1 <a name="pppcodeobs">Code Observations - mandatory</h4></p> 3176 3176 </p> 3177 3177 Enter a 'Sigma C1' for C1 code observations in meters. The bigger the sigma you enter, the less the contribution of C1 code observations to a PPP solution based on a combination of code and phase data. '2.0' meters is likely to be an appropriate choice. … … 3182 3182 3183 3183 3184 <p>< a name="pppphaseobs"><h4>2.13.3.3Phase Observations - mandatory</h4></p>3184 <p><h4>2.13.3.3 <a name="pppphaseobs">Phase Observations - mandatory</h4></p> 3185 3185 <p> 3186 3186 Enter a 'Sigma L1' for L1 phase observations in meters. The bigger the sigma you enter, the less the contribution of L1 phase observations to a PPP solutions based on a combination of code and phase data. '0.01' meters is likely to be an appropriate choice. … … 3198 3198 </p> 3199 3199 3200 <p>< a name="pppeleweight"><h4>2.13.3.4Elevation Dependent Weighting - mandatory</h4></p>3200 <p><h4>2.13.3.4 <a name="pppeleweight">Elevation Dependent Weighting - mandatory</h4></p> 3201 3201 <p> 3202 3202 BNC allows elevation dependent weighting when processing GNSS observations. A weight function … … 3216 3216 </p> 3217 3217 3218 <p>< a name="pppminobs"><h4>2.13.3.5Minimum Number of Observations - mandatory</h4></p>3218 <p><h4>2.13.3.5 <a name="pppminobs">Minimum Number of Observations - mandatory</h4></p> 3219 3219 <p> 3220 3220 Select the minimum number of observations you want to use per epoch. The minimum for parameter 'Min # of Obs' is '4'. This is also the default. 3221 3221 </p> 3222 3222 3223 <p>< a name="pppmineleva"><h4>2.13.3.6Minimum Elevation - mandatory</h4></p>3223 <p><h4>2.13.3.6 <a name="pppmineleva">Minimum Elevation - mandatory</h4></p> 3224 3224 <p> 3225 3225 Select a minimum for satellite elevation angles. Selecting '10 deg' for option 'Min Elevation' may be an appropriate choice. … … 3229 3229 </p> 3230 3230 3231 <p>< a name="pppwaitclockcorr"><h4>2.13.3.7Wait for Clock Corrections - optional</h4></p>3231 <p><h4>2.13.3.7 <a name="pppwaitclockcorr">Wait for Clock Corrections - optional</h4></p> 3232 3232 <p> 3233 3233 Zero value (or 'no') for 'Wait for clock corr.' means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value means that epochs of data are buffered and the processing of each epoch is postponed till satellite clock corrections not older than 'Wait for clock corr.' are available. Specifying a value of half the update rate of the clock corrections (i.e. 5 sec) may be appropriate. Note that this causes an additional delay of the PPP solutions in the amount of half of the update rate. … … 3240 3240 </p> 3241 3241 3242 <p>< a name="pppseeding"><h4>2.13.3.8Seeding - optional if a priori coordinates specified in 'Coordinates'</h4></p>3242 <p><h4>2.13.3.8 <a name="pppseeding">Seeding - optional if a priori coordinates specified in 'Coordinates'</h4></p> 3243 3243 <p> 3244 3244 Enter the length of a startup period in seconds for which you want to fix the PPP solution to an known position, see option 'Coordinates'. Constraining a priori coordinates is done in BNC through setting their white 'Noise' temporarily to zero. … … 3261 3261 <p><u>Figure 25:</u> BNC in 'Quick-Start' mode, PPP Panel 4.</p> 3262 3262 3263 <p>< a name="pppPlots"><h4>2.13.4PPP (4): Plots</h4></p>3263 <p><h4>2.13.4 <a name="pppPlots">PPP (4): Plots</h4></p> 3264 3264 <p> 3265 3265 This panel presents options for visualizing PPP results as a time series plot or as a track map with PPP tracks on top of OSM or Google maps. 3266 3266 </p> 3267 3267 3268 <p>< a name="ppptimeseries"><h4>2.13.4.1PPP Plot - optional</h4></p>3268 <p><h4>2.13.4.1 <a name="ppptimeseries">PPP Plot - optional</h4></p> 3269 3269 <p> 3270 3270 PPP time series of North (red), East (green) and Up (blue) displacements will be plotted under the 'PPP Plot' tab when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified, see 'Coordinates') or referred to the first estimated position. The sliding PPP time series window will cover the period of the latest 5 minutes. … … 3274 3274 </p> 3275 3275 3276 <p>< a name="pppaudioresp"><h4>2.13.4.2Audio Response - optional</h4></p>3276 <p><h4>2.13.4.2 <a name="pppaudioresp">Audio Response - optional</h4></p> 3277 3277 <p> 3278 3278 For natural hazard prediction and monitoring landslides it may be appropriate to generate audio alerts. For that you can specify an 'Audio response' threshold in meters. A beep is produced by BNC whenever a horizontal PPP coordinate component differs by more than the threshold value from the specified marker coordinate. … … 3282 3282 </p> 3283 3283 3284 <p>< a name="ppptrackmap"><h4>2.13.4.3Track Map - optional</h4></p>3284 <p><h4>2.13.4.3 <a name="ppptrackmap">Track Map - optional</h4></p> 3285 3285 <p> 3286 3286 You may like to track your rover position using Google Maps or OpenStreetMap as a background map. Track maps can be produced with BNC in 'Real-time Streams' mode or in 'RINEX Files' post processing mode with data coming from files. … … 3296 3296 <p><u>Figure 26:</u> Track of positions from BNC with Google Maps in the background.</p> 3297 3297 3298 <p>< a name="pppmaptype"><h4>2.13.4.3.1Google/OSM - mandatory before pushing 'Open Map'</h4></p>3298 <p><h4>2.13.4.3.1 <a name="pppmaptype">Google/OSM - mandatory before pushing 'Open Map'</h4></p> 3299 3299 <p> 3300 3300 Select either 'Google' or 'OSM' as the background map for your rover positions. … … 3304 3304 <p><u>Figure 27:</u> Example for a background map from Google Maps and OpenStreetMap (OSM).</p> 3305 3305 3306 <p>< a name="pppdotprop"><h4>2.13.4.4Dot-properties - mandatory before pushing 'Open Map'</h4></p>3306 <p><h4>2.13.4.4 <a name="pppdotprop">Dot-properties - mandatory before pushing 'Open Map'</h4></p> 3307 3307 <p> 3308 3308 PPP tracks are presented on maps through plotting one colored dot per observation epoch. 3309 3309 </p> 3310 3310 3311 <p>< a name="pppdotsize"><h4>2.13.4.4.1Size - mandatory before pushing 'Open Map'</h4></p>3311 <p><h4>2.13.4.4.1 <a name="pppdotsize">Size - mandatory before pushing 'Open Map'</h4></p> 3312 3312 <p> 3313 3313 Specify the size of dots showing the rover position. A dot size of '3' may be appropriate. The maximum possible dot size is '10'. An empty option field or a size of '0' would mean that you don't want BNC to show the rover's track on the map. 3314 3314 </p> 3315 3315 3316 <p>< a name="pppdotcolor"><h4>2.13.4.4.2Color - mandatory before pushing 'Open Map'</h4></p>3316 <p><h4>2.13.4.4.2 <a name="pppdotcolor">Color - mandatory before pushing 'Open Map'</h4></p> 3317 3317 <p> 3318 3318 Select the color of dots showing the rover track. 3319 3319 </p> 3320 3320 3321 <p>< a name="pppspeed"><h4>2.13.4.5Post Processing Speed - mandatory before pushing 'Open Map'</h4></p>3321 <p><h4>2.13.4.5 <a name="pppspeed">Post Processing Speed - mandatory before pushing 'Open Map'</h4></p> 3322 3322 <p> 3323 3323 With BNC in 'RINEX File' post processing mode for PPP you can specify the speed of computations as appropriate for visualization. Note that you can adjust 'Post-processing speed' on-the-fly while BNC is already processing your observations. 3324 3324 </p> 3325 3325 3326 <p>< a name="combi"><h4>2.14.Combine Corrections</h4></p>3326 <p><h4>2.14 <a name="combi">Combine Corrections</h4></p> 3327 3327 <p> 3328 3328 BNC allows processing several orbit and clock correction streams in real-time to produce, encode, upload and save a combination of Broadcast Corrections from various providers. All corrections must refer to satellite Antenna Phase Centers (APC). It is so far only the satellite clock corrections which are combined while orbit corrections in the combination product as well as the product update rates are just taken over from one of the incoming Broadcast Correction streams. Combining only clock corrections using a fixed orbit reference has the possibility to introduce some analysis inconsistencies. We may therefore eventually consider improvements on this approach. The clock combination can be based either on a plain 'Single-Epoch' or on a Kalman 'Filter' approach. … … 3384 3384 </p> 3385 3385 3386 <p>< a name="combimounttab"><h4>2.14.1Combine Corrections Table - optional</h4></p>3386 <p><h4>2.14.1 <a name="combimounttab">Combine Corrections Table - optional</h4></p> 3387 3387 <p> 3388 3388 Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Corrections mountpoint from the 'Streams' section and hit Enter. Then double click on the 'AC Name' field to enter your choice of an abbreviation for the Analysis Center (AC) providing the Antenna Phase Center (APC) related stream. Finally, double click on the 'Weight' field to enter a weight to be applied to this stream in the combination. … … 3397 3397 </p> 3398 3398 3399 <p>< a name="combiadd"><h4>2.14.1.1Add Row, Delete - optional</h4></p>3399 <p><h4>2.14.1.1 <a name="combiadd">Add Row, Delete - optional</h4></p> 3400 3400 <p> 3401 3401 Hit 'Add Row' button to add another row to the 'Combine Corrections' table or hit the 'Delete' button to delete the highlighted row(s). … … 3416 3416 <p><u>Figure 30:</u> 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.</p> 3417 3417 3418 <p>< a name="combimethod"><h4>2.14.1.2Method - mandatory if 'Combine Corrections' table is populated</h4></p>3418 <p><h4>2.14.1.2 <a name="combimethod">Method - mandatory if 'Combine Corrections' table is populated</h4></p> 3419 3419 <p> 3420 3420 Select a clock combination method. Available options are Kalman 'Filter' and 'Single-Epoch. It is suggested to use the Kalman Filter approach in case the combined stream of Broadcast Corrections is intended for Precise Point Positioning. 3421 3421 </p> 3422 3422 3423 <p>< a name="combimax"><h4>2.14.1.3Maximal Residuum - mandatory if 'Combine Corrections' table is populated</h4></p>3423 <p><h4>2.14.1.3 <a name="combimax">Maximal Residuum - mandatory if 'Combine Corrections' table is populated</h4></p> 3424 3424 3425 3425 <p>BNC combines all incoming clocks according to specified weights. Individual clock estimates that differ by more than 'Maximal Residuum' meters from the average of all clocks will be ignored.<p> … … 3427 3427 <p>Default is a 'Maximal Residuum' of 999.0 meters</p> 3428 3428 3429 <p>< a name="combismpl"><h4>2.14.1.4Sampling - mandatory if 'Combine Corrections' table is populated</h4></p>3429 <p><h4>2.14.1.4 <a name="combismpl">Sampling - mandatory if 'Combine Corrections' table is populated</h4></p> 3430 3430 <p>Specify a combination sampling interval. Orbit and clock corrections will be produced following that interval. A value of 10 sec may be an appropriate choice.</p> 3431 3431 3432 <p>< a name="combiGLO"><h4>2.14.1.5Use GLONASS - optional</h4></p>3432 <p><h4>2.14.1.5 <a name="combiGLO">Use GLONASS - optional</h4></p> 3433 3433 <p> 3434 3434 You may tick the 'Use GLONASS' option in case you want to produce a GPS plus GLONASS combination and both systems are supported by the Broadcast Correction streams participating in the combination. 3435 3435 </p> 3436 3436 3437 <p>< a name="upclk"><h4>2.15.Upload Corrections</h4></p>3437 <p><h4>2.15 <a name="upclk">Upload Corrections</h4></p> 3438 3438 <p> 3439 3439 BNC can upload streams carrying orbit and clock corrections to Broadcast Ephemeris in radial, along-track and cross-track components if they are<ol type=a> … … 3543 3543 </p> 3544 3544 3545 <p>< a name="upadd"><h4>2.15.1Add, Delete Row - optional</h4></p>3545 <p><h4>2.15.1 <a name="upadd">Add, Delete Row - optional</h4></p> 3546 3546 <p>Hit 'Add Row' button to add a row to the stream 'Upload Table' or hit the 'Delete' button to delete the highlighted row(s). 3547 3547 </p> … … 3550 3550 </p> 3551 3551 3552 <p>< a name="uphost"><h4>2.15.2Host, Port, Mountpoint, Password - optional</h4></p>3552 <p><h4>2.14.2 <a name="uphost">Host, Port, Mountpoint, Password - optional</h4></p> 3553 3553 3554 3554 <p>Specify the domain name or IP number of an Ntrip Broadcaster for uploading the stream. Furthermore, specify the caster's listening IP port, an upload mountpoint and an upload password. Note that Ntrip Broadcasters are often configured to provide access through more than one port, usually ports 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s). … … 3561 3561 </p> 3562 3562 3563 <p>< a name="upsystem"><h4>2.15.3System - mandatory if 'Host' is set</h4></p>3563 <p><h4>2.15.3 <a name="upsystem">System - mandatory if 'Host' is set</h4></p> 3564 3564 <p> 3565 3565 BNC allows configuring several Broadcast Correction streams for upload so that they refer to different reference systems and different Ntrip Broadcasters. You may use this functionality for parallel support of a backup Ntrip Broadcaster or for simultaneous support of various regional reference systems. Available options for transforming orbit and clock corrections to specific target reference systems are … … 3739 3739 <p><u>Figure 31:</u> Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94'.</p> 3740 3740 3741 <p>< a name="upcom"><h4>2.15.4Center of Mass - optional</h4></p>3741 <p><h4>2.15.4 <a name="upcom">Center of Mass - optional</h4></p> 3742 3742 <p> 3743 3743 BNC allows to either refer Broadcast Corrections to the satellite's Center of Mass (CoM) or to the satellite's Antenna Phase Center (APC). By default corrections refer to APC. Tick 'Center of Mass' to refer uploaded corrections to CoM. 3744 3744 </p> 3745 3745 3746 <p>< a name="upsp3"><h4>2.15.5SP3 File - optional</h4></p>3746 <p><h4>2.15.5 <a name="upsp3">SP3 File - optional</h4></p> 3747 3747 <p>Specify a path for saving the generated orbit corrections as SP3 orbit files. If the specified directory does not exist, BNC will not create SP3 orbit files. The following is a path example for a Linux system:<br>/home/user/BNC${GPSWD}.sp3<br>Note that '${GPSWD}' produces the GPS Week and Day number in the filename.</p> 3748 3748 <p> … … 3763 3763 </p> 3764 3764 3765 <p>< a name="uprinex"><h4>2.15.6RNX File - optional</h4></p>3765 <p><h4>2.15.6 <a name="uprinex">RNX File - optional</h4></p> 3766 3766 <p> 3767 3767 The clock corrections generated by BNC for upload can be logged in Clock RINEX format. The file naming follows the RINEX convention. … … 3778 3778 </p> 3779 3779 3780 <p>< a name="upinter"><h4>2.15.7Interval - mandatory if 'Upload Table' entries specified</h4></p>3780 <p><h4>2.15.7 <a name="upinter">Interval - mandatory if 'Upload Table' entries specified</h4></p> 3781 3781 <p> 3782 3782 Select the length of Clock RINEX files and SP3 Orbit files. The default value is 1 day. 3783 3783 </p> 3784 3784 3785 <p>< a name="upclksmpl"><h4>2.15.8Sampling</h4></p>3785 <p><h4>2.15.8 <a name="upclksmpl">Sampling</h4></p> 3786 3786 <p>BNC requires an orbit corrections sampling interval for the stream to be uploaded and sampling intervals for SP3 and Clock RINEX files. The outgoing stream's clock correction sampling interval follows that of incoming corrections and is therefore nothing to be specified here.</p> 3787 3787 3788 <p>< a name="upclkorb"><h4>2.15.8.1Orbits (Orb) - mandatory if 'Upload Table' entries specified</h4></p>3788 <p><h4>2.15.8.1 <a name="upclkorb">Orbits (Orb) - mandatory if 'Upload Table' entries specified</h4></p> 3789 3789 <p>Select the stream's orbit correction sampling interval in seconds. A value of 60 sec may be appropriate.</p> 3790 3790 <p> A value of zero '0' tells BNC to upload all orbit correction samples coming in from the real-time GNSS engine along with the clock correction samples to produce combined orbit and clock corrections to Broadcast Ephemeris (1060 for GPS, 1066 for GLONASS). … … 3817 3817 <br> 3818 3818 Note that only when specifying a value of zero '0' (default) for 'Sampling Orb', BNC produces <u>combined</u> orbit and clock correction messages. 3819 <p>< a name="upclksp3"><h4>2.15.8.2SP3 - mandatory if 'SP3 File' is specified</h4></p>3819 <p><h4>2.15.8.2 <a name="upclksp3">SP3 - mandatory if 'SP3 File' is specified</h4></p> 3820 3820 <p>Select the SP3 orbit file sampling interval in minutes. A value of 15 min may be appropriate. A value of zero '0' tells BNC to store all available samples into SP3 orbit files.</p> 3821 3821 3822 <p>< a name="upclkrnx"><h4>2.15.8.3RINEX (RNX) - mandatory if 'RNX File' is specified</h4></p>3822 <p><h4>2.15.8.3 <a name="upclkrnx">RINEX (RNX) - mandatory if 'RNX File' is specified</h4></p> 3823 3823 <p>Select the Clock RINEX file sampling interval in seconds. A value of 10 sec may be appropriate. A value of zero '0' tells BNC to store all available samples into Clock RINEX files.</p> 3824 3824 3825 <p>< a name="upcustom"><h4>2.15.9Custom Trafo - optional if 'Upload Table' entries specified</h4></p>3825 <p><h4>2.15.9 <a name="upcustom">Custom Trafo - optional if 'Upload Table' entries specified</h4></p> 3826 3826 <p>Hit 'Custom Trafo' to specify your own 14 parameter Helmert Transformation instead of selecting a predefined transformation through 'System' button.</p> 3827 3827 … … 3832 3832 <p><u>Figure 32:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster.</p> 3833 3833 3834 <p>< a name="upantex"><h4>2.15.10ANTEX File - mantatory if 'SP3 File' is specified</h4></p>3834 <p><h4>2.15.10 <a name="upantex">ANTEX File - mantatory if 'SP3 File' is specified</h4></p> 3835 3835 <p> 3836 3836 IGS provides a file containing absolute phase center variations for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required here for referring the SP3 file contents to the satellite's Center of Mass (CoM). If you don't specify a ANTEX file, the SP3 file will contain orbit information which is referred to Antenna Phase Center (APC) instead of CoM. 3837 3837 </p> 3838 3838 3839 <p>< a name="upeph"><h4>2.16.Upload Ephemeris</h4></p>3839 <p><h4>2.16 <a name="upeph">Upload Ephemeris</h4></p> 3840 3840 <p> 3841 3841 BNC can generate a stream carrying only Broadcast Ephemeris in RTCM Version 3 format and upload it to an Ntrip Broadcaster. … … 3858 3858 </p> 3859 3859 3860 <p>< a name="brdcserver"><h4>2.16.1Host & Port - optional</h4></p>3860 <p><h4>2.16.1 <a name="brdcserver">Host & Port - optional</h4></p> 3861 3861 <p> 3862 3862 Specify the 'Host' IP number or URL of an Ntrip Broadcaster to upload the stream. An empty option field means that you don't want to upload Broadcast Ephemeris. … … 3866 3866 </p> 3867 3867 3868 <p>< a name="brdcmount"><h4>2.16.2Mountpoint & Password - mandatory if 'Host' is set</h4></p>3868 <p><h4>2.16.2 <a name="brdcmount">Mountpoint & Password - mandatory if 'Host' is set</h4></p> 3869 3869 <p> 3870 3870 BNC uploads a stream to the Ntrip Broadcaster by referring to a dedicated mountpoint that has been set by its operator. Specify the mountpoint based on the details you received for your stream from the operator. It is often a four character ID (capital letters) plus an integer number.</p> … … 3872 3872 </p> 3873 3873 3874 <p>< a name="brdcsmpl"><h4>2.16.3Sampling - mandatory if 'Host' is set</h4></p>3874 <p><h4>2.16.3 <a name="brdcsmpl">Sampling - mandatory if 'Host' is set</h4></p> 3875 3875 Select the Broadcast Ephemeris repetition interval in seconds. Default is '5' meaning that a complete set of Broadcast Ephemeris is uploaded every 5 seconds. 3876 3876 </p> … … 3879 3879 <p><u>Figure 33:</u> Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an Ntrip Broadcaster.</p> 3880 3880 3881 <p>< a name="streams"><h4>2.17.Streams Canvas</h4></p>3881 <p><h4>2.17 <a name="streams">Streams Canvas</h4></p> 3882 3882 <p> 3883 3883 Each stream on an Ntrip Broadcaster (and consequently on BNC) is defined using a unique source ID called mountpoint. An Ntrip Client like BNC accesses the desired stream by referring to its mountpoint. Information about streams and their mountpoints is available through the source-table maintained by the Ntrip Broadcaster. … … 3900 3900 </p> 3901 3901 3902 <p>< a name="streamedit"><h4>2.17.1Edit Streams</h4></p>3902 <p><h4>2.17.1 <a name="streamedit">Edit Streams</h4></p> 3903 3903 <ul> 3904 3904 <li> … … 3915 3915 </ul> 3916 3916 3917 <p>< a name="streamdelete"><h4>2.17.2Delete Stream</h4></p>3917 <p><h4>2.17.2 <a name="streamdelete">Delete Stream</h4></p> 3918 3918 <p> 3919 3919 To remove a stream from the 'Streams' canvas in the main window, highlight it by clicking on it and hit the 'Delete Stream' button. You can also remove multiple streams simultaneously by highlighting them using +Shift and +Ctrl.</p> 3920 3920 3921 <p>< a name="streamconf"><h4>2.17.3Reconfigure Stream Selection On-the-fly</h4></p>3921 <p><h4>2.17.3 <a name="streamconf">Reconfigure Stream Selection On-the-fly</h4></p> 3922 3922 <p> 3923 3923 The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process. … … 3929 3929 </p> 3930 3930 3931 <p>< a name="logs"><h4>2.18.Logging Canvas</h4></p>3931 <p><h4>2.18 <a name="logs">Logging Canvas</h4></p> 3932 3932 <p> 3933 3933 The 'Logging Canvas' above the bottom menu bar on the main window labeled 'Log', 'Throughput', 'Lacenty', and 'PPP Plot' provides control of BNC's activities. Tabs are available for continuously showing logfile contents, for a plot controling the bandwidth consumption, for a plot showing stream latencies, and for time series plots of PPP results. 3934 3934 </p> 3935 <p>< a name="logfile"><h4>2.18.1Log</h4></p>3935 <p><h4>2.18.1 <a name="logfile">Log</h4></p> 3936 3936 <p> 3937 3937 Records of BNC's activities are shown in the 'Log' tab. They can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. 3938 3938 </p> 3939 3939 3940 <p>< a name="throughput"><h4>2.18.2Throughput</h4></p>3940 <p><h4>2.18.2 <a name="throughput">Throughput</h4></p> 3941 3941 <p> 3942 3942 The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilobits per second (kbps). The following figure shows an example for the bandwidth consumption of incoming streams. … … 3946 3946 <p><u>Figure 34:</u> Bandwidth consumption of incoming streams.</p> 3947 3947 3948 <p>< a name="latency"><h4>2.18.3Latency</h4></p>3948 <p><h4>2.18.3 <a name="latency">Latency</h4></p> 3949 3949 <p> 3950 3950 The latency of observations in each incoming stream is shown in the 'Latency' tab in milliseconds or seconds. Streams not carrying observations (i.e. those providing only Broadcast Ephemeris messages) or having an outage are not considered here and shown in red color. Note that the calculation of correct latencies requires the clock of the host computer to be properly synchronized. The next figure shows an example for the latency of incoming streams. … … 3954 3954 <p><u>Figure 35:</u> Latency of incoming streams.</p> 3955 3955 3956 <p>< a name="ppptab"><h4>2.18.4PPP Plot</h4></p>3956 <p><h4>2.18.4 <a name="ppptab">PPP Plot</h4></p> 3957 3957 <p> 3958 3958 Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in the 'PPP Plot' tab when a 'Origin' option is defined. Values are either referred to reference coordinates (if specified) or referred to the first estimated set of coordinate components. The time as given in format [hh:mm] refers to GPS Time. The sliding PPP time series window covers a period of 5 minutes. Note that it may take up to 30 seconds or more till the first PPP solutions becomes available. The following figure shows the screenshot of a PPP time series plot of North, East and Up coordinate components. … … 3962 3962 <p><u>Figure 36:</u> Time series plot of PPP session.</p> 3963 3963 3964 <p>< a name="bottom"><h4>2.19.Bottom Menu Bar</h4></p>3964 <p><h4>2.19 <a name="bottom">Bottom Menu Bar</h4></p> 3965 3965 <p> 3966 3966 The bottom menu bar allows to add or delete streams to BNC's configuration and to start or stop it. It also provides access to BNC's online help function. The 'Add Stream' button opens a window that allows user to select one of several input communication links, see figure below. … … 3970 3970 <p><u>Figure 37:</u> Steam input communication links.</p> 3971 3971 3972 <p>< a name="streamadd"><h4>2.19.1Add Stream</h4></p>3972 <p><h4>2.19.1 <a name="streamadd">Add Stream</h4></p> 3973 3973 <p> 3974 3974 Button 'Add Stream' allows you to pull streams either from a Ntrip Broadcaster or from a TCP/IP port, UPD port, or serial port. 3975 3975 </p> 3976 3976 3977 <p>< a name="streamcaster"><h4>2.19.1.1Add Stream - Coming from Caster</h4></p>3977 <p><h4>2.19.1.1 <a name="streamcaster">Add Stream - Coming from Caster</h4></p> 3978 3978 3979 3979 <p> … … 3981 3981 </p> 3982 3982 3983 <p>< a name="streamhost"><h4>2.19.1.1.1Caster Host and Port - mandatory</h4></p>3983 <p><h4>2.19.1.1.1 <a name="streamhost">Caster Host and Port - mandatory</h4></p> 3984 3984 <p> 3985 3985 Enter the Ntrip Broadcaster host IP and port number. Note that EUREF and IGS operate Ntrip Broadcasters at <u>http://www.euref-ip.net/home</u>, <u>http://www.igs-ip.net/home</u>, <u>http://www.products.igs-ip.net/home</u> and <u>http://mgex.igs-ip.net/home</u>. 3986 3986 </p> 3987 3987 3988 <p>< a name="streamtable"><h4>2.19.1.1.2Casters Table - optional</h4></p>3988 <p><h4>2.19.1.1.2 <a name="streamtable">Casters Table - optional</h4></p> 3989 3989 <p> 3990 3990 It may be that you are not sure about your Ntrip Broadcasters host and port number or you are interested in other broadcaster installations operated elsewhere. Hit 'Show' for a table of known broadcasters maintained at <u>www.rtcm-ntrip.org/home</u>. A window opens which allows selecting a broadcaster for stream retrieval, see figure below. … … 3995 3995 <p><u>Figure 38:</u> Casters table.</p> 3996 3996 3997 <p>< a name="streamuser"><h4>2.19.1.1.3User and Password - mandatory for protected streams</h4></p>3997 <p><h4>2.19.1.1.3 <a name="streamuser">User and Password - mandatory for protected streams</h4></p> 3998 3998 <p> 3999 3999 Streams on Ntrip Broadcasters may be protected. 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://register.rtcm-ntrip.org</u> for access to protected streams from EUREF and IGS. 4000 4000 </p> 4001 4001 4002 <p>< a name="gettable"><h4>2.19.1.1.4Get Table</h4></p>4002 <p><h4>2.19.1.1.4 <a name="gettable">Get Table</h4></p> 4003 4003 <p> 4004 4004 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, RTCM Version 3, or RTNET format. For access to observations, Broadcast Ephemeris and Broadcast Corrections in RTCM format streams must contain a selection of appropriate message types as listed in the Annex, cf. 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 streams containing message types 1019 (GPS) and 1020 (GLONASS) and 1043 (SBAS) and 1044 (QZSS) and 1045, 1046 (Galileo) and 63 (tentative, BDS/BeiDou) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example source-table. … … 4013 4013 <p><u>Figure 39:</u> Broadcaster source-table.</p> 4014 4014 4015 <p>< a name="ntripv"><h4>2.19.1.1.5Ntrip Version - mandatory</h4></p>4015 <p><h4>2.19.1.1.5 <a name="ntripv">Ntrip Version - mandatory</h4></p> 4016 4016 <p> 4017 4017 Some limitations and deficiencies of the Ntrip Version 1 stream transport protocol are solved in Ntrip Version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Version 2 is backwards compatible to Version 1. Options implemented in BNC are: … … 4042 4042 </p> 4043 4043 4044 <p>< a name="castermap"><h4>2.19.1.1.6Map - optional</h4></p>4044 <p><h4>2.19.1.1.6 <a name="castermap">Map - optional</h4></p> 4045 4045 <p> 4046 4046 Button 'Map' opens a window to show a distribution map of the caster's streams. You may like to zoom in or out using the mouse. Left button: draw a rectangle to zoom, right button: zoom out, middle button: zoom back. … … 4050 4050 <p><u>Figure 40:</u> Stream distribution map derived from Ntrip Broadcaster source-table.</p> 4051 4051 4052 <p>< a name="streamip"><h4>2.19.1.2Add Stream - Coming from TCP/IP Port</h4></p>4052 <p><h4>2.19.1.2 <a name="streamip">Add Stream - Coming from TCP/IP Port</h4></p> 4053 4053 <p> 4054 4054 Button 'Add Stream' > 'Coming from TCP/IP Port' allows to retrieve streams via TCP directly from an IP address without using the Ntrip transport protocol. For that you: … … 4069 4069 </p> 4070 4070 4071 <p>< a name="streamudp"><h4>2.19.1.3Add Stream - Coming from UDP Port</h4></p>4071 <p><h4>2.19.1.3 <a name="streamudp">Add Stream - Coming from UDP Port</h4></p> 4072 4072 <p> 4073 4073 Button 'Add Stream' > 'Coming from UDP Port' allows to pick up streams arriving directly at one of the local host's UDP ports without using the Ntrip transport protocol. For that you: … … 4084 4084 <p> 4085 4085 4086 <p>< a name="streamser"><h4>2.19.1.4Add Stream - Coming from Serial Port</h4></p>4086 <p><h4>2.19.1.4 <a name="streamser">Add Stream - Coming from Serial Port</h4></p> 4087 4087 <p> 4088 4088 Button 'Add Stream' > 'Coming from Serial Port' allows to retrieve streams from a GNSS receiver via serial port without using the Ntrip transport protocol. For that you: … … 4124 4124 <p><u>Figure 41:</u> BNC setup for pulling a stream via serial port.</p> 4125 4125 4126 <p>< a name="streamsdelete"><h4>2.19.2Delete Stream</h4></p>4126 <p><h4>2.19.2 <a name="streamsdelete">Delete Stream</h4></p> 4127 4127 <p> 4128 4128 Button 'Delete Stream' allows you to delete streams previously selected for retrieval as listed under the 'Streams' canvas on BNC's main window. 4129 4129 </p> 4130 4130 4131 <p>< a name="streamsmap"><h4>2.19.3Map</h4></p>4131 <p><h4>2.19.3 <a name="streamsmap">Map</h4></p> 4132 4132 <p> 4133 4133 Button 'Map' opens a window to show a distribution map of the streams selected for retrieval as listed under the 'Streams' canvas. You may like to zoom in or out using the mouse. Left button: draw a rectangle to zoom, right button: zoom out, middle button: zoom back. 4134 4134 </p> 4135 4135 4136 <p>< a name="start"><h4>2.19.4Start</h4></p>4136 <p><h4>2.19.4 <a name="start">Start</h4></p> 4137 4137 <p> 4138 4138 Hit 'Start' to start retrieving, decoding or 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. 4139 4139 </p> 4140 4140 4141 <p>< a name="stop"><h4>2.19.5Stop</h4></p>4141 <p><h4>2.19.5 <a name="stop">Stop</h4></p> 4142 4142 <p> 4143 4143 Hit the 'Stop' button in order to stop BNC. 4144 4144 </p> 4145 4145 4146 <p>< a name="contexthelp"><h4>2.19.6Help? = Shift+F1</h4></p>4146 <p><h4>2.19.6 <a name="contexthelp">Help? = Shift+F1</h4></p> 4147 4147 <p> 4148 4148 BNC comes with a <i>What's This</i> help system providing online information about its functionality and usage. Short descriptions are available for any widget and program option. Focus to the relevant object and press Shift+F1 to request help information. A help text appears immediately; it disappears as soon as the user does something else. The dialogs on some operating systems may provide a '?' button that users can click; click the relevant widget to pop up the help text. 4149 4149 </p> 4150 4150 4151 <p>< a name="cmd"><h4>2.20.Command Line Options</h4></p>4151 <p><h4>2.20 <a name="cmd">Command Line Options</h4></p> 4152 4152 <p> 4153 4153 Command line options are available to run BNC in 'no window' mode or let it read previously recorded input offline from one or several files for debugging purposes. It is also possible to introduce a specific configuration filename instead of using the default filename 'BNC.bnc'. The self-explaining contents of the configuration file can easily be edited. … … 4164 4164 </p> 4165 4165 4166 <p>< a name="cmdVersion"><h4>2.20.1Version - optional</h4></p>4166 <p><h4>2.20.1 <a name="cmdVersion">Version - optional</h4></p> 4167 4167 <p> 4168 4168 Command line option '--version' lets BNC print its version number. … … 4173 4173 </p> 4174 4174 4175 <p>< a name="cmdDisplay"><h4>2.20.2Display - optional</h4></p>4175 <p><h4>2.20.2 <a name="cmdDisplay">Display - optional</h4></p> 4176 4176 <p> 4177 4177 On systems which support graphics command line option '--display' forces BNC to present the BNC window on the specified display. … … 4182 4182 </p> 4183 4183 4184 <p>< a name="nw"><h4>2.20.3No Window Mode - optional</h4></p>4184 <p><h4>2.20.3 <a name="nw">No Window Mode - optional</h4></p> 4185 4185 <p> 4186 4186 Apart from its regular windows mode, BNC can be started on all systems as a batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file on disk. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems. … … 4216 4216 </pre> 4217 4217 4218 <p>< a name="post"><h4>2.20.4File Mode - optional</h4></p>4218 <p><h4>2.20.4 <a name="post">File Mode - optional</h4></p> 4219 4219 <p> 4220 4220 Although BNC is primarily a real-time online tool, for debugging purposes it can be run offline to read data from a file previously saved through option 'Raw output file'. Enter the following command line option for that … … 4233 4233 </p> 4234 4234 4235 <p>< a name="conffile"><h4>2.20.5Configuration File - optional</h4></p>4235 <p><h4>2.20.5 <a name="conffile">Configuration File - optional</h4></p> 4236 4236 The default configuration filename is 'BNC.bnc'. You may change this name at startup time using the command line option '--conf <<u>confFileName</u>>'. This allows running several BNC jobs in parallel on the same host using different sets of configuration options. <u>confFileName</u> stands either for the full path to a configuration file or just for a filename. If you introduce only a filename, the corresponding file will be saved in the current working directory from where BNC is started. 4237 4237 </p> … … 4244 4244 </p> 4245 4245 4246 <p>< a name="confopt"><h4>2.20.6Configuration Options - optional</h4></p>4246 <p><h4>2.20.6 <a name="confopt">Configuration Options - optional</h4></p> 4247 4247 <p> 4248 4248 BNC applies options from the configuration file but allows updating every one of them on the command line while the contents of the configuration file remains unchanged. The command line syntax for that looks as follows … … 4264 4264 </p> 4265 4265 4266 <p>< a name="annex"><h3>3.Annex</h3></p>4267 4268 <p>< a name=history><h4>3.1Revision History</h3></p>4266 <p><h3>3. <a name="annex">Annex</h3></p> 4267 4268 <p><h4>3.1 <a name=history>Revision History</h3></p> 4269 4269 <table> 4270 4270 <tr></tr> … … 4443 4443 </p> 4444 4444 4445 <p>< a name="rtcm"><h4>3.2.RTCM Standards</h4></p>4445 <p><h4>3.2 <a name="rtcm">RTCM Standards</h4></p> 4446 4446 4447 4447 <p> … … 4451 4451 </p> 4452 4452 4453 <p>< a name="ntrip1"><h4>3.2.1Ntrip Version 1</h4></p>4453 <p><h4>3.2.1 <a name="ntrip1">Ntrip Version 1</h4></p> 4454 4454 4455 4455 <p> … … 4490 4490 </p> 4491 4491 4492 <p>< a name="ntrip2"><h4>3.2.2Ntrip Version 2</h4></p>4492 <p><h4>3.2.2 <a name="ntrip2">Ntrip Version 2</h4></p> 4493 4493 4494 4494 <p> … … 4508 4508 </p> 4509 4509 4510 <p>< a name="rtcm2"><h4>3.2.3RTCM Version 2</h4></p>4510 <p><h4>3.2.3 <a name="rtcm2">RTCM Version 2</h4></p> 4511 4511 <p> 4512 4512 Transmitting GNSS carrier phase data can be done through RTCM Version 2 messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of interest here are: … … 4546 4546 </ul> 4547 4547 4548 <p>< a name="rtcm3"><h4>3.2.4RTCM Version 3</h4></p>4548 <p><h4>3.2.4 <a name="rtcm3">RTCM Version 3</h4></p> 4549 4549 <p> 4550 4550 RTCM Version 3 has been developed as a more efficient alternative to RTCM Version 2. Service providers and vendors have asked for a standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the Version 2 parity scheme was wasteful of bandwidth. Another complaint was that the parity is not independent from word to word. Still another was that even with so many bits devoted to parity, the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. The Version 3 standard is intended to correct these weaknesses. … … 4689 4689 </p> 4690 4690 4691 <p>< a name="confList"><h4>3.3Command Line Help</h3></p>4691 <p><h4>3.3 <a name="confList">Command Line Help</h3></p> 4692 4692 4693 4693 <p> … … 4922 4922 (8) bnc --key PPP/staTable "FFMJ1,100.0,100.0,100.0,100.0,100.0,100.0,0.1,3e-6,7777;CUT07,100.0,100.0,100.0,100.0,100.0,100.0,0.1,3e-6,7778" 4923 4923 </pre> 4924 <p>< a name="links"><h4>3.4Further Reading</h3></p>4924 <p><h4>3.4 <a name="links">Further Reading</h3></p> 4925 4925 4926 4926 <table> … … 4966 4966 </table> 4967 4967 4968
Note:
See TracChangeset
for help on using the changeset viewer.
