Changeset 5662 in ntrip for trunk/BNC/src/bnchelp.html
- Timestamp:
- May 8, 2014, 3:22:32 PM (11 years ago)
- File:
-
- 1 edited
-
trunk/BNC/src/bnchelp.html (modified) (76 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r5651 r5662 50 50 </p> 51 51 <p> 52 BNC includes the following GNU GPL software components: 53 <ul> 54 <li> RTCM 2 decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, Germany;</li> 52 BNC includes the following GNU GPL software components: 53 <ul> 54 <li> RTCM 2 decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, Germany;</li> 55 55 <li> RTCM 3 decoder for conventional and MSM observation messages and a RTCM 3 encoder & decoder for SSR messages, both written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld, Germany.</li> 56 56 </ul> … … 126 126 <p> 127 127 <ul> 128 <li>RTCM Version 2 message types for GPS and GLONASS observations; </li> 128 <li>RTCM Version 2 message types for GPS and GLONASS observations; </li> 129 129 <li>RTCM Version 3 'conventional' message types for observations and Broadcast Ephemeris for GPS and GLONASS;</li> 130 130 <li>RTCM Version 3 'State Space Representation' (SSR) messages for GPS and GLONASS;</li> … … 424 424 <li> select an appropriate font.<br> 425 425 Use smaller font size if the BNC main window exceeds the size of your screen. 426 </li> 426 </li> 427 427 <li> reread and save selected options in configuration file.<br> 428 428 When using 'Reread & Save Configuration' while BNC is already processing data, some configuration options become immediately effective on-the-fly without interrupting uninvolved threads while all of them are saved on disk. See annexed section 'Configuration Examples' for a list of on-the-fly changeable configuration options. 429 429 </li> 430 430 <li> quit the BNC program. 431 </li> 431 </li> 432 432 </ul> 433 433 </p> … … 441 441 help contents.<br> 442 442 You may keep the 'Help Contents' window open while configuring BNC. 443 </li> 443 </li> 444 444 <li> 445 445 a 'Flow Chart' showing BNC linked to a real-time GNSS network engine such as RTNet. … … 448 448 general information about BNC.<br> 449 449 Close the 'About BNC' window to continue working with BNC. 450 </li> 450 </li> 451 451 </ul> 452 452 </p> … … 483 483 <p> 484 484 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. 485 </p> 485 </p> 486 486 487 487 <p><a name="genconf"><h4>3.3.3 Reread Configuration - optional</h4></p> 488 488 <p> 489 489 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. See annexed section 'Configuration Examples' for a configuration file example and a list of on-the-fly changeable options. 490 </p> 490 </p> 491 491 492 492 <p><a name="genstart"><h4>3.3.4 Auto Start - optional</h4></p> … … 518 518 <p> 519 519 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 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'. 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. 520 </p> 520 </p> 521 521 <p> 522 522 It is important to understand that converting RTCM streams to RINEX files requires a-priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension') and switch to a default selection of observation types when such skeleton file is not available or it does not contain the required information. The 'Default selection of observation types specified' for a RINEX Version 3 file would be as follows: … … 550 550 </p> 551 551 <p> 552 where 'ddd' is the day of year, 'h' is a letter which corresponds to an hour long UTC time block and 'yy' is the year. 552 where 'ddd' is the day of year, 'h' is a letter which corresponds to an hour long UTC time block and 'yy' is the year. 553 553 </p> 554 554 <p> … … 576 576 <p> 577 577 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. 578 </p> 578 </p> 579 579 580 580 <p><a name="rnxinterval"><h4>3.4.3 File Interval - mandatory if 'Directory' is set</h4></p> 581 581 <p> 582 582 Select the length of the RINEX Observation file generated. The default value is 15 minutes. 583 </p> 583 </p> 584 584 585 585 <p><a name="rnxsample"><h4>3.4.4 Sampling - mandatory if 'Directory' is set </h4></p> 586 586 <p> 587 587 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. 588 </p> 588 </p> 589 589 590 590 <p><a name="rnxskl"><h4>3.4.5 Skeleton Extension - optional</h4></p> 591 591 <p> 592 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 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 the Brussels EPN station. 592 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 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 the Brussels EPN station. 593 593 </p> 594 594 <p> … … 605 605 <p> 606 606 if 'Skeleton extension' is set to 'skl'. 607 </p> 608 <p> 607 </p> 608 <p> 609 609 Note the following regulations regarding personal RINEX header skeleton files: 610 610 <ul> … … 628 628 <br>- # / TYPES OF OBSERV (only RINEX Version 2, will be ignored when writing RINEX Version 3 files) 629 629 <br>BNC will include these lines in the final RINEX file header together with an additional 630 <br>- COMMENT 630 <br>- COMMENT 631 631 <br>line describing the source of the stream.</li> 632 632 <li>They should finally contain an empty header record of type … … 669 669 <p> 670 670 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). 671 </p> 672 <p> 671 </p> 672 <p> 673 673 The triggering event for calling the script or batch file is the end of a RINEX Observation file 'Interval'. If that is overridden by a stream outage, the triggering event is the stream reconnection. 674 </p> 675 <p> 674 </p> 675 <p> 676 676 As an alternative to initiating file uploads through BNC, you may like to call an upload script or batch file through your crontable or Task Scheduler (independent from BNC) once every one or two minutes after the end of each RINEX file 'Interval'. 677 </p> 677 </p> 678 678 679 679 <p><a name="rnxvers"><h4>3.4.7 Version - optional</h4></p> 680 680 <p> 681 681 The default format for RINEX Observation files is RINEX Version 2.11. Select 'Version 3' if you would like to save observations in RINEX Version 3 format. 682 </p> 682 </p> 683 683 684 684 <p><a name="ephemeris"><h4>3.5. RINEX Ephemeris</h4></p> … … 689 689 <li>'N' or 'G' for GPS or GLONASS ephemeris in two separate RINEX Version 2.11 Navigation files, or</li> 690 690 <li>'P' for GPS plus GLONASS plus Galileo ephemeris saved together in one RINEX Version 3 Navigation file. 691 </ul> 691 </ul> 692 692 693 693 <p> … … 698 698 <p> 699 699 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. 700 </p> 700 </p> 701 701 702 702 <p><a name="ephint"><h4>3.5.2 Interval - mandatory if 'Directory' is set</h4></p> 703 703 <p> 704 704 Select the length of the RINEX Navigation file generated. The default value is 1 day. 705 </p> 705 </p> 706 706 707 707 <p><a name="ephport"><h4>3.5.3 Port - optional</h4></p> … … 719 719 <p> 720 720 Note that this does not concern the Broadcast Ephemeris output through IP port which is always in RINEX Version 3 format. 721 </p> 721 </p> 722 722 723 723 <p><a name="reqc"><h4>3.6. RINEX Editing & QC</h4></p> … … 784 784 <p><a name="reqcinput"><h4>3.6.4 Input Files - mandatory if 'Action' is set</h4></p> 785 785 <p> 786 Specify full path to input RINEX Observation file(s), and<br> 786 Specify full path to input RINEX Observation file(s), and<br> 787 787 specify full path to input RINEX Navigation file(s). 788 </p> 788 </p> 789 789 <p>When specifying several input files BNC will concatenate their contents. Note that you may specify several RINEX Version 2 Navigation files for GPS and GLONASS.</p> 790 790 791 791 <p><a name="reqcoutput"><h4>3.6.5 Output Files - mandatory if 'Action' is set</h4></p> 792 792 <p> 793 If 'Edit/Concatenate' is selected, specifying the a path to output RINEX Observation file(s) and specifying a full path to output RINEX Navigation file(s) is mandatory.</p> 793 If 'Edit/Concatenate' is selected, specifying the a path to output RINEX Observation file(s) and specifying a full path to output RINEX Navigation file(s) is mandatory.</p> 794 794 795 795 <p><img src="IMG/screenshot25.png"/></p> … … 824 824 <p><a name="reqcplots"><h4>3.6.6 Directory for Plots - optional if 'Action' is set</h4></p> 825 825 <p> 826 If 'Analyze' is selected, specifying the path to a directory where plot files will be saved is optional. File names will be composed from the RINEX input file name(s) plus suffix 'PNG' to indicate the plot file format in use. </p> 826 If 'Analyze' is selected, specifying the path to a directory where plot files will be saved is optional. File names will be composed from the RINEX input file name(s) plus suffix 'PNG' to indicate the plot file format in use. </p> 827 827 828 828 <p><img src="IMG/screenshot29.png"/></p> … … 898 898 <p><a name="correct"><h4>3.7. Broadcast Corrections</h4></p> 899 899 <p> 900 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). 901 </p> 902 <p> 903 An alternative to the observation space approach is the so called 'sate space' approach. The principle here is to provide information on individual error sources. It can be called 'State Space Representation' (SSR). For a rover position, state space information concerning precise satellite clocks, orbits, ionosphere, troposphere et cetera can be converted into observation space and used to correct the rover observables for more accurate positioning. Alternatively the state information can directly be used in the rover's processing or adjustment model. 900 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). 901 </p> 902 <p> 903 An alternative to the observation space approach is the so called 'sate space' approach. The principle here is to provide information on individual error sources. It can be called 'State Space Representation' (SSR). For a rover position, state space information concerning precise satellite clocks, orbits, ionosphere, troposphere et cetera can be converted into observation space and used to correct the rover observables for more accurate positioning. Alternatively the state information can directly be used in the rover's processing or adjustment model. 904 904 </p> 905 905 <p> … … 914 914 </ul> 915 915 <p> 916 RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications. 916 RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications. 917 917 </p> 918 918 <p> … … 944 944 ! Orbits/Clocks: 0 GPS 19 Glonass CLK11 945 945 <p> 946 Such line informs you about the number of records (here 30 and 19) carrying GPS or GLONASS related parameters you should receive next. 946 Such line informs you about the number of records (here 30 and 19) carrying GPS or GLONASS related parameters you should receive next. 947 947 </p> 948 948 <p> … … 1072 1072 <pre> 1073 1073 ... 1074 1059 0 1538 211151.0 G18 2 0 -0.010 11 -0.750 1074 1059 0 1538 211151.0 G18 2 0 -0.010 11 -0.750 1075 1075 1059 0 1538 211151.0 G16 2 0 -0.040 11 -0.430 1076 1076 1059 0 1538 211151.0 G22 2 0 -0.630 11 -2.400 … … 1238 1238 <p> 1239 1239 Note that 'Wait for full obs epoch' does not affect the RINEX Observation file content. Observations received later than 'Wait for full obs epoch' seconds will still be included in the RINEX Observation files. 1240 </p> 1240 </p> 1241 1241 1242 1242 <p><a name="syncsample"><h4>3.8.3 Sampling - mandatory if 'File' or 'Port' is set</h4></p> … … 1247 1247 <p><a name="syncfile"><h4>3.8.4 File - optional</h4></p> 1248 1248 <p> 1249 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. 1249 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. 1250 1250 </p> 1251 1251 <p> … … 1260 1260 <p><a name="serial"><h4>3.9. Serial Output</h4></p> 1261 1261 <p> 1262 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. 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 RTK rover. 1262 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. 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 RTK rover. 1263 1263 </p> 1264 1264 <p><img src="IMG/screenshot11.png"/></p> … … 1355 1355 <p> 1356 1356 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 explicit information from BNC about stream outages and incoming streams that cannot be decoded. 1357 </p> 1357 </p> 1358 1358 1359 1359 <p><a name="advfail"><h4>3.10.2 Failure Threshold - optional</h4></p> … … 1379 1379 <p> 1380 1380 Leave the 'Script' field empty if you do not wish to use this option. An invalid path will also disable this option. 1381 </p> 1381 </p> 1382 1382 <p> 1383 1383 Examples for command line parameter strings passed on to the advisory 'Script' are: … … 1400 1400 ! 1401 1401 </pre> 1402 </p> 1403 <p> 1402 </p> 1403 <p> 1404 1404 Note the sleep command in this script which causes the system to wait for a random period of up to 60 seconds before sending the email. This should avoid overloading your mail server in case of a simultaneous failure of many streams. 1405 </p> 1405 </p> 1406 1406 1407 1407 <p><a name="misc"><h4>3.11. Miscellaneous</h4></p> … … 1437 1437 </pre> 1438 1438 <p> 1439 <u>Statistics:</u> BNC counts the number of GPS seconds covered by at least one observation. It also estimates an observation rate (independent from the a priory specified 'Observation rate') from all observations received throughout the first full 'Log latency' interval. Based on this rate, BNC estimates the number of data gaps when appearing in subsequent intervals. 1439 <u>Statistics:</u> BNC counts the number of GPS seconds covered by at least one observation. It also estimates an observation rate (independent from the a priory specified 'Observation rate') from all observations received throughout the first full 'Log latency' interval. Based on this rate, BNC estimates the number of data gaps when appearing in subsequent intervals. 1440 1440 </p> 1441 1441 <p> … … 1475 1475 <p> 1476 1476 1477 <p>Logged time stamps refer to message reception time and allow understanding repetition rates. Enter 'ALL' if you want to log this information from all configured streams. Beware that the size of the logfile can rapidly increase depending on the number of incoming RTCM streams. 1478 </p> 1479 <p>This option is primarily meant for testing and evaluation. Use it to figure out what exactly is produced by a specific GNSS receiver's configuration. An empty option field (default) means that you don't want BNC to print the message type numbers and antenna information carried in RTCM streams. 1477 <p>Logged time stamps refer to message reception time and allow understanding repetition rates. Enter 'ALL' if you want to log this information from all configured streams. Beware that the size of the logfile can rapidly increase depending on the number of incoming RTCM streams. 1478 </p> 1479 <p>This option is primarily meant for testing and evaluation. Use it to figure out what exactly is produced by a specific GNSS receiver's configuration. An empty option field (default) means that you don't want BNC to print the message type numbers and antenna information carried in RTCM streams. 1480 1480 </p> 1481 1481 … … 1526 1526 <li>code and phase residuals for GPS and GLONASS and Galileo in [m], </li> 1527 1527 <li>receiver clock errors in [m], </li> 1528 <li>a-priori and correction values of tropospheric zenith delay in [m], 1529 <li>time offset between GPS time and Galileo time in [m], 1528 <li>a-priori and correction values of tropospheric zenith delay in [m], 1529 <li>time offset between GPS time and Galileo time in [m], 1530 1530 <li>L3 biases, also known as 'floated ambiguities', given per satellite. 1531 1531 </ul> … … 1606 1606 1607 1607 <p> 1608 Note that for debugging or Post Processing purposes BNC's 'PPP' functionality option can also be used offline. 1608 Note that for debugging or Post Processing purposes BNC's 'PPP' functionality option can also be used offline. 1609 1609 <ul> 1610 1610 <li> … … 1646 1646 <p><a name="pppobsmount"><h4>3.12.1.2 Obs Mountpoint - optional</h4></p> 1647 1647 <p> 1648 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. 1648 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. 1649 1649 </p> 1650 1650 … … 1656 1656 <p><a name="pppxyz"><h4>3.12.2 Marker Coordinates - optional</h4></p> 1657 1657 <p> 1658 Enter the reference coordinate XYZ of the receiver's position in meters if known. This option makes only sense for static observations. Defaults are empty option fields, meaning that the antenna's XYZ position is unknown. 1658 Enter the reference coordinate XYZ of the receiver's position in meters if known. This option makes only sense for static observations. Defaults are empty option fields, meaning that the antenna's XYZ position is unknown. 1659 1659 </p> 1660 1660 <p> … … 1675 1675 <p><a name="pppoutput"><h4>3.12.4 NMEA Output - optional</h4></p> 1676 1676 <p> 1677 BNC allows to output results from Precise Point Positioning in NMEA format. 1677 BNC allows to output results from Precise Point Positioning in NMEA format. 1678 1678 </p> 1679 1679 <p> … … 1683 1683 <p><a name="pppnmeafile"><h4>3.12.4.1 NMEA File - optional</h4></p> 1684 1684 <p> 1685 The NMEA sentences generated about once per second are pairs of 1685 The NMEA sentences generated about once per second are pairs of 1686 1686 <ul> 1687 1687 <li> GPGGA sentences which mainly carry the estimated latitude, longitude, and height values, plus</li> … … 1695 1695 <p><a name="pppnmeaport"><h4>3.12.4.2 NMEA Port - optional</h4></p> 1696 1696 <p> 1697 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. 1697 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. 1698 1698 </p> 1699 1699 <p> … … 1929 1929 <li>The software with its Graphic User Interface and wide range of supported Operating Systems represents a perfect platform to process many Broadcast Correction streams in parallel;</li> 1930 1930 <li>Outages of single AC product streams can be mitigated through merging several incoming streams into a combined product;</li> 1931 <li>Generating a combination product from several AC products allows detecting and rejecting outliers;</li> 1931 <li>Generating a combination product from several AC products allows detecting and rejecting outliers;</li> 1932 1932 <li>A Combination Center (CC) can operate BNC to globally disseminate a combination product via NTRIP broadcast;</li> 1933 1933 <li>An individual AC could prefer to disseminate a stream combined from primary and backup IT resources to reduce outages;</li> … … 1950 1950 </p> 1951 1951 <p> 1952 This comment applies in situations where we have a limited number of solutions to combine and their quality varies significantly. The situation may be different when the total number of ACs is larger and the range of AC variation is smaller. In that case, a standard full combination is probably the best. 1952 This comment applies in situations where we have a limited number of solutions to combine and their quality varies significantly. The situation may be different when the total number of ACs is larger and the range of AC variation is smaller. In that case, a standard full combination is probably the best. 1953 1953 </p> 1954 1954 <p> … … 1996 1996 1997 1997 <p> 1998 The following screenshots describe an example setup of BNC when combining Broadcast Correction streams and uploading them to an NTRIP Broadcaster. Note that it requires specifying options under tabs 'Combine Corrections' and 'Upload Corrections'. The example uses the combination product to simultaneously carry out an 'INTERNAL' PPP solution in 'Quick-Start' mode which allows monitoring the quality of the combination product in the space domain. 1998 The following screenshots describe an example setup of BNC when combining Broadcast Correction streams and uploading them to an NTRIP Broadcaster. Note that it requires specifying options under tabs 'Combine Corrections' and 'Upload Corrections'. The example uses the combination product to simultaneously carry out an 'INTERNAL' PPP solution in 'Quick-Start' mode which allows monitoring the quality of the combination product in the space domain. 1999 1999 </p> 2000 2000 … … 2026 2026 <p><a name="upclk"><h4>3.14. Upload Corrections</h4></p> 2027 2027 <p> 2028 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> 2028 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> 2029 2029 <li> 2030 2030 either generated by BNC as a combination of several individual Broadcast Correction streams coming from an number of real-time Analysis Centers (ACs), see section 'Combine Corrections',</li> … … 2036 2036 <li>Continuously receive up-to-date Broadcast Ephemeris carrying approximate orbits and clocks for all satellites. Read new Broadcast Ephemeris immediately whenever they become available. This information may come via a stream of RTCM messages generated from another BNC instance.</li> 2037 2037 </ul> 2038 Then, epoch by epoch: 2038 Then, epoch by epoch: 2039 2039 <ul> 2040 2040 <li>Continuously receive the best available orbit and clock estimates for all satellites in XYZ Earth-Centered-Earth-Fixed IGS08 reference system. Receive them every epoch in plain ASCII format as provided by a real-time GNSS engine such as RTNet or generate them following a combination approach. </li> … … 2053 2053 </p> 2054 2054 <p> 2055 The usual handling of BNC when uploading a stream with Broadcast Corrections is that you first specify Broadcast Ephemeris and Broadcast Correction streams. You then specify an NTRIP Broadcaster for stream upload before you start the program. 2055 The usual handling of BNC when uploading a stream with Broadcast Corrections is that you first specify Broadcast Ephemeris and Broadcast Correction streams. You then specify an NTRIP Broadcaster for stream upload before you start the program. 2056 2056 </p> 2057 2057 <p> 2058 2058 <u>'RTNET' Stream Format</u><br> 2059 When uploading an SSR stream generated according to b. then BNC requires precise GNSS orbits and clocks in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and in a specific ASCII format named 'RTNET' because the data may come from a real-time engine such as RTNet. The sampling interval for data transmission should not exceed 15 sec. Note that otherwise tools involved in IP streaming such as NTRIP Broadcasters or NTRIP Clients may respond with a timeout. 2060 </p> 2061 <p> 2062 Below you find an example for the 'RTNET' ASCII format coming from a real-time GNSS engine. Each epoch begins with an asterisk character followed by the time as year, month, day of month, hour, minute and second. Subsequent records provide the following set of parameters for each satellite: 2059 When uploading an SSR stream generated according to b. then BNC requires precise GNSS orbits and clocks in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and in a specific ASCII format named 'RTNET' because the data may come from a real-time engine such as RTNet. The sampling interval for data transmission should not exceed 15 sec. Note that otherwise tools involved in IP streaming such as NTRIP Broadcasters or NTRIP Clients may respond with a timeout. 2060 </p> 2061 <p> 2062 Below you find an example for the 'RTNET' ASCII format coming from a real-time GNSS engine. Each epoch begins with an asterisk character followed by the time as year, month, day of month, hour, minute and second. Subsequent records provide the following set of parameters for each satellite: 2063 2063 </p> 2064 2064 <p> … … 2087 2087 <p> 2088 2088 <pre> 2089 * 2013 3 21 7 19 55.00000000 2089 * 2013 3 21 7 19 55.00000000 2090 2090 G01 APC 3 19869258.4381 9158001.1526 15095321.8460 Clk 1 2755.5447 Vel 3 977.3298 1661.2202 -2283.9009 CoM 3 19869259.6565 9158001.3302 15095322.8837 CodeBias 2 1C .3149 2P -11.7432 2091 2091 G02 APC 3 -13043930.7341 -22955958.1832 4995469.3779 Clk 1 126894.0959 Vel 3 601.6561 298.3845 3009.2928 CoM 3 -13043931.1120 -22955958.8484 4995469.5227 CodeBias 2 1C -.8828 2P 1.7301 … … 2107 2107 R24 APC 3 21300823.5162 8426171.8952 -11241665.2306 Clk 1 -27112.9305 Vel 3 -1498.4393 -376.6107 -3125.3066 CoM 3 21300825.4800 8426173.2206 -11241666.1521 2108 2108 EOE 2109 * 2013 3 21 7 20 0.00000000 2109 * 2013 3 21 7 20 0.00000000 2110 2110 G01 APC 3 19874144.1634 9166303.6499 15083898.3374 Clk 1 2755.5498 Vel 3 976.9602 1659.7789 -2285.5025 CoM 3 19874145.3821 9166303.8281 15083899.3746 CodeBias 2 1C .3151 2P -11.7430 2111 2111 G02 APC 3 -13040919.4263 -22954462.9892 5010514.5569 Clk 1 126894.1080 Vel 3 602.8672 299.6930 3008.7787 CoM 3 -13040919.8041 -22954463.6543 5010514.7021 CodeBias 2 1C -.8829 2P 1.7303 … … 2136 2136 <p>The stream upload may be protected through an upload 'Password'. Enter the password you received from the NTRIP Broadcaster operator along with the mountpoint(s).</p> 2137 2137 <p> 2138 If 'Host', 'Port', 'Mountpoint' and 'Password' are set, the stream will be encoded in RTCM's 'State Space Representation' (SSR) messages and uploaded to the specified broadcaster following the NTRIP Version 1 transport protocol. 2138 If 'Host', 'Port', 'Mountpoint' and 'Password' are set, the stream will be encoded in RTCM's 'State Space Representation' (SSR) messages and uploaded to the specified broadcaster following the NTRIP Version 1 transport protocol. 2139 2139 </p> 2140 2140 … … 2162 2162 </pre> 2163 2163 <p> 2164 where s is the transformation scale, c is the speed of light, and ρ are the topocentric distance between an (approximate) center of the transformation's validity area and the satellite. 2164 where s is the transformation scale, c is the speed of light, and ρ are the topocentric distance between an (approximate) center of the transformation's validity area and the satellite. 2165 2165 </p> 2166 2166 <p> … … 2186 2186 Rotation in Y at epoch To: 5.390 mas 2187 2187 Rotation in Z at epoch To: -8.712 mas 2188 Rotation rate in X: 0.081 mas/y 2188 Rotation rate in X: 0.081 mas/y 2189 2189 Rotation rate in Y: 0.490 mas/y 2190 2190 Rotation rate in Z: -0.792 mas/y … … 2209 2209 Rotation in Y at epoch To: -9.42645 mas 2210 2210 Rotation in Z at epoch To: -11.59935 mas 2211 Rotation rate in X: -0.06667 mas/y 2211 Rotation rate in X: -0.06667 mas/y 2212 2212 Rotation rate in Y: 0.75744 mas/y 2213 2213 Rotation rate in Z: 0.05133 mas/y … … 2232 2232 Rotation in Y at epoch To: -2.2578 mas 2233 2233 Rotation in Z at epoch To: -2.4015 mas 2234 Rotation rate in X: -1.5461 mas/y 2234 Rotation rate in X: -1.5461 mas/y 2235 2235 Rotation rate in Y: -1.1820 mas/y 2236 2236 Rotation rate in Z: -1.1551 mas/y … … 2255 2255 Rotation in Y at epoch To: -0.030 mas 2256 2256 Rotation in Z at epoch To: 0.070 mas 2257 Rotation rate in X: 0.000 mas/y 2257 Rotation rate in X: 0.000 mas/y 2258 2258 Rotation rate in Y: 0.000 mas/y 2259 2259 Rotation rate in Z: 0.000 mas/y 2260 Scale at epoch To : 0.0000000000002260 Scale at epoch To : -0.000000001000 2261 2261 Scale rate: 0.000000000000 /y 2262 2262 To: 0000.0 … … 2278 2278 Rotation in Y at epoch To: 0.000 mas 2279 2279 Rotation in Z at epoch To: -0.003 mas 2280 Rotation rate in X: 0.000 mas/y 2280 Rotation rate in X: 0.000 mas/y 2281 2281 Rotation rate in Y: 0.000 mas/y 2282 2282 Rotation rate in Z: 0.000 mas/y … … 2288 2288 2289 2289 <p> 2290 <u>DREF91:</u> 'Referenzkoordinaten für SAPOS, Empfehlungen der Projektgruppe SAPOS-Koordinatenmonitoring 2008', Personal communication with Peter Franke, BKG, Germany. The following 14 Helmert Transformation Parameters were introduced: 2290 <u>DREF91:</u> 'Referenzkoordinaten für SAPOS, Empfehlungen der Projektgruppe SAPOS-Koordinatenmonitoring 2008', Personal communication with Peter Franke, BKG, Germany. The following 14 Helmert Transformation Parameters were introduced: 2291 2291 </p> 2292 2292 <p> … … 2301 2301 Rotation in Y at epoch To: 6.190 mas 2302 2302 Rotation in Z at epoch To: -11.012 mas 2303 Rotation rate in X: 0.081 mas/y 2303 Rotation rate in X: 0.081 mas/y 2304 2304 Rotation rate in Y: 0.490 mas/y 2305 2305 Rotation rate in Z: -0.792 mas/y … … 2325 2325 </p> 2326 2326 <p> 2327 As an SP3 file contents should be referred to the satellites Center of Mass (CoM) while Broadcast Corrections are referred to the satellites APC, an offset has to be applied which is available from an IGS ANTEX file (see section 'ANTEX File'). You should therefore specify the 'ANTEX File' path under tab 'PPP (2)' if you want to save the stream contents in SP3 format. If you don't specify an 'ANTEX File' path there, the SP3 file contents will be referred to the satellites APCs. 2327 As an SP3 file contents should be referred to the satellites Center of Mass (CoM) while Broadcast Corrections are referred to the satellites APC, an offset has to be applied which is available from an IGS ANTEX file (see section 'ANTEX File'). You should therefore specify the 'ANTEX File' path under tab 'PPP (2)' if you want to save the stream contents in SP3 format. If you don't specify an 'ANTEX File' path there, the SP3 file contents will be referred to the satellites APCs. 2328 2328 </p> 2329 2329 <p> … … 2335 2335 2336 2336 <p> 2337 Note that BNC outputs a complete list of SP3 'Epoch Header Records' even if no 'Position and Clock Records' are available for certain epochs because of stream outages. Note further that the 'Number of Epochs' in the first SP3 header record may not be correct because that number is not available when the file is created. Depending on your processing software (e.g. Bernese GNSS Software, BSW) it could therefore be necessary to correct an incorrect 'Number of Epochs' in the file before you use in Post Processing. 2337 Note that BNC outputs a complete list of SP3 'Epoch Header Records' even if no 'Position and Clock Records' are available for certain epochs because of stream outages. Note further that the 'Number of Epochs' in the first SP3 header record may not be correct because that number is not available when the file is created. Depending on your processing software (e.g. Bernese GNSS Software, BSW) it could therefore be necessary to correct an incorrect 'Number of Epochs' in the file before you use in Post Processing. 2338 2338 </p> 2339 2339 … … 2372 2372 2373 2373 <p> 2374 The following screenshot shows the encoding and uploading of a stream of precise orbits and clocks coming from a real-time engine in 'RTNET' ASCII format. The stream is uploaded to NTRIP Broadcaster 'products.igs-ip.net'. It is referred to APC and IGS08. Uploaded data are locally saved in SP3 and Clock RINEX format. The SSR Provider ID is set to 3. The SSR Solution ID is and the Issue of Data SSR are set to 1. Required Broadcast Ephemeris are received via stream 'RTCM3EPH'. 2374 The following screenshot shows the encoding and uploading of a stream of precise orbits and clocks coming from a real-time engine in 'RTNET' ASCII format. The stream is uploaded to NTRIP Broadcaster 'products.igs-ip.net'. It is referred to APC and IGS08. Uploaded data are locally saved in SP3 and Clock RINEX format. The SSR Provider ID is set to 3. The SSR Solution ID is and the Issue of Data SSR are set to 1. Required Broadcast Ephemeris are received via stream 'RTCM3EPH'. 2375 2375 </p> 2376 2376 <p><img src="IMG/screenshot26.png"/></p> … … 2438 2438 <br>Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner when not using the NTRIP Version 2 transport protocol.. 2439 2439 </li> 2440 </ul> 2440 </ul> 2441 2441 2442 2442 <p><a name="streamdelete"><h4>3.16.2 Delete Stream</h4></p> … … 2504 2504 <p> 2505 2505 Button 'Add Stream' > 'Coming from Caster' then opens a window that allows user to select data streams from an NTRIP Broadcaster according to their mountpoints and show a distribution map of offered streams. 2506 </p> 2506 </p> 2507 2507 2508 2508 <p><a name="streamhost"><h4>3.18.1.1.1 Caster Host and Port - mandatory</h4></p> 2509 2509 <p> 2510 2510 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>. 2511 </p> 2511 </p> 2512 2512 2513 2513 <p><a name="streamtable"><h4>3.18.1.1.2 Casters Table - optional</h4></p> 2514 2514 <p> 2515 2515 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. 2516 </p> 2516 </p> 2517 2517 </p> 2518 2518 <p><img src="IMG/screenshot04.png"/></p> … … 2523 2523 <p> 2524 2524 Some streams on NTRIP Broadcasters may be restricted. Enter a valid 'User' ID and 'Password' for access to protected streams. Accounts are usually provided per NTRIP Broadcaster through a registration procedure. Register through <u>http://igs.bkg.bund.de/ntrip/registeruser</u> for access to protected streams from EUREF and IGS. 2525 </p> 2525 </p> 2526 2526 2527 2527 <p><a name="gettable"><h4>3.18.1.1.4 Get Table</h4></p> 2528 2528 <p> 2529 2529 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 1045, 1046 (Galileo) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example source-table. 2530 </p> 2530 </p> 2531 2531 <p> 2532 2532 The contents of data field 'nmea' tells you whether a stream retrieval needs to be initiated by BNC through sending an NMEA-GGA message carrying approximate position coordinates (virtual reference station). … … 2534 2534 <p> 2535 2535 Hit 'OK' to return to the main window. If you wish you can click on 'Add Stream' and repeat the process again to retrieve streams from different casters. 2536 </p> 2536 </p> 2537 2537 <p><img src="IMG/screenshot05.png"/></p> 2538 2538 <p><u>Figure 30:</u> Broadcaster source-table.</p> … … 2629 2629 </p> 2630 2630 <p> 2631 When selecting one of the serial communication options listed above, make sure that you pick those configured to the serial connected GNSS receiver. 2631 When selecting one of the serial communication options listed above, make sure that you pick those configured to the serial connected GNSS receiver. 2632 2632 </p> 2633 2633 … … 2655 2655 <p> 2656 2656 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. 2657 </p> 2657 </p> 2658 2658 2659 2659 <p><a name="stop"><h4>3.18.5 Stop</h4></p> 2660 2660 <p> 2661 Hit the 'Stop' button in order to stop BNC. 2662 </p> 2661 Hit the 'Stop' button in order to stop BNC. 2662 </p> 2663 2663 2664 2664 <p><a name="cmd"><h4>3.19. Command Line Options</h4></p> 2665 <p> 2665 <p> 2666 2666 Command line options are available to run BNC in 'no window' mode or let it read data offline from one or several files for debugging or Post Processing purposes. BNC will then use processing options from the involved configuration file. Note that the self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration file name instead of using the default name 'BNC.bnc'. 2667 </p> 2667 </p> 2668 2668 2669 2669 <p><a name="nw"><h4>3.19.1 No Window Mode - optional</h4></p> 2670 2670 <p> 2671 2671 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. 2672 </p> 2673 <p> 2672 </p> 2673 <p> 2674 2674 Example:<br><br> 2675 2675 bnc.exe -nw … … 2716 2716 </p> 2717 2717 <p>Note further that option '--file' forces BNC to appy the '-nw' option for running in 'no window' mode. 2718 </p> 2718 </p> 2719 2719 2720 2720 <p><a name="conffile"><h4>3.19.3 Configuration File - optional</h4></p> … … 2724 2724 Example:<br><br> 2725 2725 ./bnc --conf MyConfig.bnc 2726 </p> 2727 <p> 2726 </p> 2727 <p> 2728 2728 This leads to a BNC job using configuration file 'MyConfig.bnc'. The configuration file will be saved in the current working directory. 2729 </p> 2729 </p> 2730 2730 2731 2731 <p><a name="confopt"><h4>3.19.4 Configuration Options - optional</h4></p> 2732 <p> 2732 <p> 2733 2733 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 2734 2734 </p> … … 2747 2747 <p> 2748 2748 ./bnc --conf CONFIG.bnc --key proxyPort 8001 --key rnxIntr "1 day" 2749 </p> 2749 </p> 2750 2750 2751 2751 <p><a name="limits"><h3>4. Limitations</h3></p> 2752 2752 <ul> 2753 2753 <li> 2754 In Qt-based desktop environments (like KDE) on Unix/Linux platforms it may happen that you experience a crash of BNC at startup even when running the program in the background using the '-nw' option. This is a known bug most likely resulting from an incompatibility of Qt libraries in the environment and in BNC. Entering the command 'unset SESSION_MANAGER' before running BNC may help as a work-around. 2754 In Qt-based desktop environments (like KDE) on Unix/Linux platforms it may happen that you experience a crash of BNC at startup even when running the program in the background using the '-nw' option. This is a known bug most likely resulting from an incompatibility of Qt libraries in the environment and in BNC. Entering the command 'unset SESSION_MANAGER' before running BNC may help as a work-around. 2755 2755 </li> 2756 2756 … … 3006 3006 </li> 3007 3007 <li> 3008 Type 23 message provides the information on the antenna type used on the reference station. 3008 Type 23 message provides the information on the antenna type used on the reference station. 3009 3009 </li> 3010 3010 <li> … … 3119 3119 3120 3120 <p> 3121 BNC comes with a number of configuration examples which can be used on all operating systems. Copy the complete directory 'Example_Configs' which comes with the software including sub-directories 'Input' and 'Output' to your disc. There are two ways to start BNC using one of the example configurations: 3121 BNC comes with a number of configuration examples which can be used on all operating systems. Copy the complete directory 'Example_Configs' which comes with the software including sub-directories 'Input' and 'Output' to your disc. There are two ways to start BNC using one of the example configurations: 3122 3122 </p> 3123 3123 <ul> … … 3135 3135 3136 3136 <p> 3137 We furthermore suggest for convenience reasons that you configure your system to automatically start BNC when you double-click a file with the file name extension '.bnc'. The following describes what to do on Windows systems to associate the BNC program to such configuration files: 3137 We furthermore suggest for convenience reasons that you configure your system to automatically start BNC when you double-click a file with the file name extension '.bnc'. The following describes what to do on Windows systems to associate the BNC program to such configuration files: 3138 3138 </p> 3139 3139 … … 3148 3148 3149 3149 <p> 3150 Some of the presented example configuration files contain a user ID 'Example' with a password 'Configs' for accessing a few GNSS streams from public Ntrip Broadcasters. This generic account is arranged for convenience reasons only. Please be so kind as to replace the generic account details as well as the place holders 'User' and 'Pass' by the personal user ID and password you receive following an online registration through <u>http://register.rtcm-ntrip.org</u>. 3151 </p> 3152 3153 <p> 3154 Note that the account for an Ntrip Broadcaster is usually limited to pulling a specified maximum number of streams at the same time. As running some of the example configurations requires pulling several streams, it is suggested to make sure that you don't exceed your account's limits. 3155 </p> 3156 3157 <p> 3158 Make also sure that sub-directories 'Input' and 'Output' which are part of the example configurations exist on your system or adjust the affected example configuration options according to your needs. 3159 </p> 3160 3161 <p> 3162 Some BNC options require antenna phase center variations as made available from IGS through so-called ANTEX files at <u>ftp://igs.org/pub/station/general</u>. An example ANTEX file 'igs08.atx' is part of the BNC package for convenience. 3163 </p> 3164 3165 <p> 3166 The example configurations assume that no proxy protects your BNC host. Should a proxy be operated in front of BNC then you need to introduce its IP and port in the 'Network' tab. 3150 Some of the presented example configuration files contain a user ID 'Example' with a password 'Configs' for accessing a few GNSS streams from public Ntrip Broadcasters. This generic account is arranged for convenience reasons only. Please be so kind as to replace the generic account details as well as the place holders 'User' and 'Pass' by the personal user ID and password you receive following an online registration through <u>http://register.rtcm-ntrip.org</u>. 3151 </p> 3152 3153 <p> 3154 Note that the account for an Ntrip Broadcaster is usually limited to pulling a specified maximum number of streams at the same time. As running some of the example configurations requires pulling several streams, it is suggested to make sure that you don't exceed your account's limits. 3155 </p> 3156 3157 <p> 3158 Make also sure that sub-directories 'Input' and 'Output' which are part of the example configurations exist on your system or adjust the affected example configuration options according to your needs. 3159 </p> 3160 3161 <p> 3162 Some BNC options require antenna phase center variations as made available from IGS through so-called ANTEX files at <u>ftp://igs.org/pub/station/general</u>. An example ANTEX file 'igs08.atx' is part of the BNC package for convenience. 3163 </p> 3164 3165 <p> 3166 The example configurations assume that no proxy protects your BNC host. Should a proxy be operated in front of BNC then you need to introduce its IP and port in the 'Network' tab. 3167 3167 </p> 3168 3168 … … 3173 3173 3174 3174 <li>File 'RinexObs.bnc'<br> 3175 The purpose of this configuration is showing how to convert RTCM streams to RINEX Observation files. The configuration pulls streams from Ntrip Broadcasters using Ntrip version 1 to generate 15min 1Hz RINEX Version 3 Observation files. See http://igs.bkg.bund.de/ntrip/observations for observation stream resources. 3175 The purpose of this configuration is showing how to convert RTCM streams to RINEX Observation files. The configuration pulls streams from Ntrip Broadcasters using Ntrip version 1 to generate 15min 1Hz RINEX Version 3 Observation files. See http://igs.bkg.bund.de/ntrip/observations for observation stream resources. 3176 3176 </li><br> 3177 3177 3178 3178 <li>File 'RinexEph.bnc'<br> 3179 The purpose of this configuration is showing how to convert a RTCM stream carrying navigation messages to a RINEX Navigation files. The configuration pulls an RTCM Version 3 stream with Broadcast Ephemeris coming from the real-time EUREF and IGS networks. It saves hourly RINEX Version 3 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast Ephemeris resources. 3179 The purpose of this configuration is showing how to convert a RTCM stream carrying navigation messages to a RINEX Navigation files. The configuration pulls an RTCM Version 3 stream with Broadcast Ephemeris coming from the real-time EUREF and IGS networks. It saves hourly RINEX Version 3 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast Ephemeris resources. 3180 3180 </li><br> 3181 3181 3182 3182 <li>File 'BrdcCorr.bnc'<br> 3183 The purpose of this configuration is to save Broadcast Corrections from RTCM SSR messages in a plain ASCII format as hourly files. See http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF orbit/clock products. 3183 The purpose of this configuration is to save Broadcast Corrections from RTCM SSR messages in a plain ASCII format as hourly files. See http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF orbit/clock products. 3184 3184 </li><br> 3185 3185 3186 3186 <li>File 'RinexConcat.bnc'<br> 3187 The purpose of this configuration is to concatenate RINEX Version 3 files to produce a concatenated file and edit the marker name in the file header. The sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the documentation for examples on how to call BNC from command line in 'no window' mode for RINEX file editing, concatenation and quality checks. 3187 The purpose of this configuration is to concatenate RINEX Version 3 files to produce a concatenated file and edit the marker name in the file header. The sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the documentation for examples on how to call BNC from command line in 'no window' mode for RINEX file editing, concatenation and quality checks. 3188 3188 </li><br> 3189 3189 3190 3190 <li>File 'RinexQC.bnc'<br> 3191 The purpose of this configuration is to check the quality of a RINEX Version 3 file through a multipath analysis. The results is saved in disk in terms of a plot in PNG format. See section 'RINEX Editing & QC' in the documentation for examples on how to call BNC from command line in 'no window' mode for RINEX file editing, concatenation and quality checks. 3191 The purpose of this configuration is to check the quality of a RINEX Version 3 file through a multipath analysis. The results is saved in disk in terms of a plot in PNG format. See section 'RINEX Editing & QC' in the documentation for examples on how to call BNC from command line in 'no window' mode for RINEX file editing, concatenation and quality checks. 3192 3192 </li><br> 3193 3193 3194 3194 <li>File 'RTK.bnc'<br> 3195 The purpose of this configuration is to feed a serial connected receiver with observations from a reference station for conventional RTK. The stream is scanned for RTCM messages. Message type numbers and latencies of incoming observation are reported in BNC's logfile. 3195 The purpose of this configuration is to feed a serial connected receiver with observations from a reference station for conventional RTK. The stream is scanned for RTCM messages. Message type numbers and latencies of incoming observation are reported in BNC's logfile. 3196 3196 </li><br> 3197 3197 3198 3198 <li>File 'FeedEngine.bnc'<br> 3199 The purpose of this configuration is to feed a real-time GNSS engine with observations from a remote reference stations. The configuration pulls a single stream from an NTRIP Broadcasters. It would of course be possible to pull several streams from different casters. Incoming observations are decoded, synchronized and output through a local IP port and saved into a file. Failure and recovery thresholds are specified to inform about outages. 3199 The purpose of this configuration is to feed a real-time GNSS engine with observations from a remote reference stations. The configuration pulls a single stream from an NTRIP Broadcasters. It would of course be possible to pull several streams from different casters. Incoming observations are decoded, synchronized and output through a local IP port and saved into a file. Failure and recovery thresholds are specified to inform about outages. 3200 3200 </li><br> 3201 3201 3202 3202 <li>File 'PPP.bnc'<br> 3203 The purpose of this configuration is Precise Point Positioning from observations of a rover receiver. The configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream and a stream with Broadcast Corrections. Positions are saved in the logfile. 3203 The purpose of this configuration is Precise Point Positioning from observations of a rover receiver. The configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream and a stream with Broadcast Corrections. Positions are saved in the logfile. 3204 3204 </li><br> 3205 3205 … … 3209 3209 3210 3210 <li>File 'PPPPostProc.bnc'<br> 3211 The purpose of this configuration is Precise Point Positioning in Post Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation files and a Broadcast Corrections files. PPP processing options are set to support the Quick-Start mode. The output is saved in a specific Post Processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm. 3211 The purpose of this configuration is Precise Point Positioning in Post Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation files and a Broadcast Corrections files. PPP processing options are set to support the Quick-Start mode. The output is saved in a specific Post Processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm. 3212 3212 </li><br> 3213 3213 … … 3221 3221 3222 3222 <li>File 'Sp3.bnc'<br> 3223 The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a Broadcast Corrections stream. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX file because SP3 file contents should be referred to CoM. 3223 The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a Broadcast Corrections stream. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX file because SP3 file contents should be referred to CoM. 3224 3224 </li><br> 3225 3225 3226 3226 <li>File 'Sp3ETRF2000PPP.bnc'<br> 3227 The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. This leads to an SP3 file containing orbits referred also to ETRF2000. Pulling in addition observations from a reference station at precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution with ETRF2000 reference coordinates. 3227 The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. This leads to an SP3 file containing orbits referred also to ETRF2000. Pulling in addition observations from a reference station at precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution with ETRF2000 reference coordinates. 3228 3228 </li><br> 3229 3229 3230 3230 <li>File 'Upload.bnc'<br> 3231 The purpose of this configuration is to upload orbits and clocks from a real-time GNSS engine to an NTRIP Broadcaster. For that the configuration reads precise orbits and clocks in RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast Corrections and encodes them in RTCM Version 3 SSR messages to upload them to an NTRIP Broadcaster. The Broadcast Corrections stream is referred to satellite Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format and clocks in Clock RINEX format. 3231 The purpose of this configuration is to upload orbits and clocks from a real-time GNSS engine to an NTRIP Broadcaster. For that the configuration reads precise orbits and clocks in RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast Corrections and encodes them in RTCM Version 3 SSR messages to upload them to an NTRIP Broadcaster. The Broadcast Corrections stream is referred to satellite Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format and clocks in Clock RINEX format. 3232 3232 </li><br> 3233 3233 … … 3235 3235 This configuration equals the 'Upload.bnc' configuration. However, the Broadcast Corrections are in addition used for an 'INTERNAL' PPP solution based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the Broadcast Corrections through observing coordinate displacements. 3236 3236 </li><br> 3237 3237 3238 3238 <li>File 'Combi.bnc'<br> 3239 The purpose of this configuration is to pull several streams carrying Broadcast Corrections and a Broadcast Ephemeris stream from an NTRIP Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the combination product in RTCM Version 3 SSR messages and uploads that to an Ntrip Broadcaster. The Broadcast Corrections stream is not referred to satellite Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format and clocks in Clock RINEX format. 3239 The purpose of this configuration is to pull several streams carrying Broadcast Corrections and a Broadcast Ephemeris stream from an NTRIP Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the combination product in RTCM Version 3 SSR messages and uploads that to an Ntrip Broadcaster. The Broadcast Corrections stream is not referred to satellite Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format and clocks in Clock RINEX format. 3240 3240 </li><br> 3241 3241 3242 3242 <li>File 'CombiPPP.bnc'<br> 3243 This configuration equals the 'Combi.bnc' configuration. However, the combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the combination product through observing coordinate displacements. 3243 This configuration equals the 'Combi.bnc' configuration. However, the combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the combination product through observing coordinate displacements. 3244 3244 </li><br> 3245 3245 3246 3246 <li>File 'UploadEph.bnc'<br> 3247 The purpose of this configuration is to pull a number of streams from reference stations to get hold of contained Broadcast Ephemeris messages. These are encoded then in a RTCM Version 3 stream which only provides Broadcast Ephemeris with an update rate of 5 seconds. 3247 The purpose of this configuration is to pull a number of streams from reference stations to get hold of contained Broadcast Ephemeris messages. These are encoded then in a RTCM Version 3 stream which only provides Broadcast Ephemeris with an update rate of 5 seconds. 3248 3248 </li> 3249 3249 … … 3415 3415 </p> 3416 3416 <p> 3417 Note that the following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data: 3417 Note that the following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data: 3418 3418 </p> 3419 3419 <p> … … 3422 3422 <li>'waitTime' to change the 'Wait for full obs epoch' option, see section 'Feed Engine';</li> 3423 3423 <li>'binSampl' to change the 'Sampling' option, see section 'Feed Engine'.</li> 3424 <li>'outFile' to change the 'File' name where synchronized observations are saved in plain ASCII format.</li> 3424 <li>'outFile' to change the 'File' name where synchronized observations are saved in plain ASCII format.</li> 3425 3425 </ul> 3426 3426 </p> … … 3470 3470 </table> 3471 3471 3472 3472
Note:
See TracChangeset
for help on using the changeset viewer.
