Index: trunk/BNC/src/bnchelp.html
===================================================================
--- trunk/BNC/src/bnchelp.html	(revision 5651)
+++ trunk/BNC/src/bnchelp.html	(revision 5662)
@@ -50,7 +50,7 @@
 </p>
 <p>
-BNC includes the following GNU GPL software components: 
-<ul>
-<li> RTCM 2 decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, Germany;</li> 
+BNC includes the following GNU GPL software components:
+<ul>
+<li> RTCM 2 decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, Germany;</li>
 <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>
 </ul>
@@ -126,5 +126,5 @@
 <p>
 <ul>
-<li>RTCM Version 2 message types for GPS and GLONASS observations; </li> 
+<li>RTCM Version 2 message types for GPS and GLONASS observations; </li>
 <li>RTCM Version 3 'conventional' message types for observations and Broadcast Ephemeris for GPS and GLONASS;</li>
 <li>RTCM Version 3 'State Space Representation' (SSR) messages for GPS and GLONASS;</li>
@@ -424,10 +424,10 @@
 <li> select an appropriate font.<br>
 Use smaller font size if the BNC main window exceeds the size of your screen.
-</li> 
+</li>
 <li> reread and save selected options in configuration file.<br>
 When using 'Reread &amp; 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.
 </li>
 <li> quit the BNC program.
-</li> 
+</li>
 </ul>
 </p>
@@ -441,5 +441,5 @@
 help contents.<br>
 You may keep the 'Help Contents' window open while configuring BNC.
-</li> 
+</li>
 <li>
 a 'Flow Chart' showing BNC linked to a real-time GNSS network engine such as RTNet.
@@ -448,5 +448,5 @@
 general information about BNC.<br>
 Close the 'About BNC' window to continue working with BNC.
-</li> 
+</li>
 </ul>
 </p>
@@ -483,10 +483,10 @@
 <p>
 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.
-</p> 
+</p>
 
 <p><a name="genconf"><h4>3.3.3 Reread Configuration - optional</h4></p>
 <p>
 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.
-</p> 
+</p>
 
 <p><a name="genstart"><h4>3.3.4 Auto Start - optional</h4></p>
@@ -518,5 +518,5 @@
 <p>
 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.
-</p> 
+</p>
 <p>
 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,5 +550,5 @@
 </p>
 <p>
-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. 
+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.
 </p>
 <p>
@@ -576,19 +576,19 @@
 <p>
 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.
-</p> 
+</p>
 
 <p><a name="rnxinterval"><h4>3.4.3 File Interval - mandatory if 'Directory' is set</h4></p>
 <p>
 Select the length of the RINEX Observation file generated. The default value is 15 minutes.
-</p> 
+</p>
 
 <p><a name="rnxsample"><h4>3.4.4 Sampling - mandatory if 'Directory' is set </h4></p>
 <p>
 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.
-</p> 
+</p>
 
 <p><a name="rnxskl"><h4>3.4.5 Skeleton Extension - optional</h4></p>
 <p>
-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. 
+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.
 </p>
 <p>
@@ -605,6 +605,6 @@
 <p>
 if 'Skeleton extension' is set to 'skl'.
-</p> 
-<p> 
+</p>
+<p>
 Note the following regulations regarding personal RINEX header skeleton files:
 <ul>
@@ -628,5 +628,5 @@
 <br>- &nbsp; # / TYPES OF OBSERV (only RINEX Version 2, will be ignored when writing RINEX Version 3 files)
 <br>BNC will include these lines in the final RINEX file header together with an additional
-<br>- &nbsp; COMMENT 
+<br>- &nbsp; COMMENT
 <br>line describing the source of the stream.</li>
 <li>They should finally contain an empty header record of type
@@ -669,16 +669,16 @@
 <p>
 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).
-</p> 
-<p> 
+</p>
+<p>
 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.
-</p> 
-<p> 
+</p>
+<p>
 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'.
-</p> 
+</p>
 
 <p><a name="rnxvers"><h4>3.4.7 Version - optional</h4></p>
 <p>
 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.
-</p> 
+</p>
 
 <p><a name="ephemeris"><h4>3.5. RINEX Ephemeris</h4></p>
@@ -689,5 +689,5 @@
 <li>'N' or 'G' for GPS or GLONASS ephemeris in two separate RINEX Version 2.11 Navigation files, or</li>
 <li>'P' for GPS plus GLONASS plus Galileo ephemeris saved together in one RINEX Version 3 Navigation file.
-</ul> 
+</ul>
 
 <p>
@@ -698,10 +698,10 @@
 <p>
 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.
-</p> 
+</p>
 
 <p><a name="ephint"><h4>3.5.2 Interval - mandatory if 'Directory' is set</h4></p>
 <p>
 Select the length of the RINEX Navigation file generated. The default value is 1 day.
-</p> 
+</p>
 
 <p><a name="ephport"><h4>3.5.3 Port - optional</h4></p>
@@ -719,5 +719,5 @@
 <p>
 Note that this does not concern the Broadcast Ephemeris output through IP port which is always in RINEX Version 3 format.
-</p> 
+</p>
 
 <p><a name="reqc"><h4>3.6. RINEX Editing & QC</h4></p>
@@ -784,12 +784,12 @@
 <p><a name="reqcinput"><h4>3.6.4 Input Files - mandatory if 'Action' is set</h4></p>
 <p>
-Specify full path to input RINEX Observation file(s), and<br> 
+Specify full path to input RINEX Observation file(s), and<br>
 specify full path to input RINEX Navigation file(s).
-</p> 
+</p>
 <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>
 
 <p><a name="reqcoutput"><h4>3.6.5 Output Files - mandatory if 'Action' is set</h4></p>
 <p>
-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> 
+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>
 
 <p><img src="IMG/screenshot25.png"/></p>
@@ -824,5 +824,5 @@
 <p><a name="reqcplots"><h4>3.6.6 Directory for Plots - optional if 'Action' is set</h4></p>
 <p>
-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> 
+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>
 
 <p><img src="IMG/screenshot29.png"/></p>
@@ -898,8 +898,8 @@
 <p><a name="correct"><h4>3.7. Broadcast Corrections</h4></p>
 <p>
-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). 
-</p>
-<p>
-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. 
+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).
+</p>
+<p>
+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.
 </p>
 <p>
@@ -914,5 +914,5 @@
 </ul>
 <p>
-RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications. 
+RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications.
 </p>
 <p>
@@ -944,5 +944,5 @@
 ! Orbits/Clocks: 0 GPS 19 Glonass CLK11
 <p>
-Such line informs you about the number of records (here 30 and 19) carrying GPS or GLONASS related parameters you should receive next. 
+Such line informs you about the number of records (here 30 and 19) carrying GPS or GLONASS related parameters you should receive next.
 </p>
 <p>
@@ -1072,5 +1072,5 @@
 <pre>
 ...
-1059 0 1538 211151.0 G18 2 0   -0.010 11   -0.750 
+1059 0 1538 211151.0 G18 2 0   -0.010 11   -0.750
 1059 0 1538 211151.0 G16 2 0   -0.040 11   -0.430
 1059 0 1538 211151.0 G22 2 0   -0.630 11   -2.400
@@ -1238,5 +1238,5 @@
 <p>
 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.
-</p> 
+</p>
 
 <p><a name="syncsample"><h4>3.8.3 Sampling - mandatory if 'File' or 'Port' is set</h4></p>
@@ -1247,5 +1247,5 @@
 <p><a name="syncfile"><h4>3.8.4 File - optional</h4></p>
 <p>
-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. 
+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.
 </p>
 <p>
@@ -1260,5 +1260,5 @@
 <p><a name="serial"><h4>3.9. Serial Output</h4></p>
 <p>
-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. 
+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.
 </p>
 <p><img src="IMG/screenshot11.png"/></p>
@@ -1355,5 +1355,5 @@
 <p>
 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.
-</p> 
+</p>
 
 <p><a name="advfail"><h4>3.10.2 Failure Threshold - optional</h4></p>
@@ -1379,5 +1379,5 @@
 <p>
 Leave the 'Script' field empty if you do not wish to use this option. An invalid path will also disable this option.
-</p> 
+</p>
 <p>
 Examples for command line parameter strings passed on to the advisory 'Script' are:
@@ -1400,8 +1400,8 @@
 !
 </pre>
-</p> 
-<p> 
+</p>
+<p>
 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.
-</p> 
+</p>
 
 <p><a name="misc"><h4>3.11. Miscellaneous</h4></p>
@@ -1437,5 +1437,5 @@
 </pre>
 <p>
-<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. 
+<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.
 </p>
 <p>
@@ -1475,7 +1475,7 @@
 <p>
 
-<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. 
-</p>
-<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. 
+<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.
+</p>
+<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.
 </p>
 
@@ -1526,6 +1526,6 @@
 <li>code and phase residuals for GPS and GLONASS and Galileo in [m], </li>
 <li>receiver clock errors in [m], </li>
-<li>a-priori and correction values of tropospheric zenith delay in [m], 
-<li>time offset between GPS time and Galileo time in [m], 
+<li>a-priori and correction values of tropospheric zenith delay in [m],
+<li>time offset between GPS time and Galileo time in [m],
 <li>L3 biases, also known as 'floated ambiguities', given per satellite.
 </ul>
@@ -1606,5 +1606,5 @@
 
 <p>
-Note that for debugging or Post Processing purposes BNC's 'PPP' functionality option can also be used offline. 
+Note that for debugging or Post Processing purposes BNC's 'PPP' functionality option can also be used offline.
 <ul>
 <li>
@@ -1646,5 +1646,5 @@
 <p><a name="pppobsmount"><h4>3.12.1.2 Obs Mountpoint - optional</h4></p>
 <p>
-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. 
+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.
 </p>
 
@@ -1656,5 +1656,5 @@
 <p><a name="pppxyz"><h4>3.12.2 Marker Coordinates - optional</h4></p>
 <p>
-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. 
+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.
 </p>
 <p>
@@ -1675,5 +1675,5 @@
 <p><a name="pppoutput"><h4>3.12.4 NMEA Output - optional</h4></p>
 <p>
-BNC allows to output results from Precise Point Positioning in NMEA format. 
+BNC allows to output results from Precise Point Positioning in NMEA format.
 </p>
 <p>
@@ -1683,5 +1683,5 @@
 <p><a name="pppnmeafile"><h4>3.12.4.1 NMEA File - optional</h4></p>
 <p>
-The NMEA sentences generated about once per second are pairs of 
+The NMEA sentences generated about once per second are pairs of
 <ul>
 <li> GPGGA sentences which mainly carry the estimated latitude, longitude, and height values, plus</li>
@@ -1695,5 +1695,5 @@
 <p><a name="pppnmeaport"><h4>3.12.4.2 NMEA Port - optional</h4></p>
 <p>
-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. 
+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.
 </p>
 <p>
@@ -1929,5 +1929,5 @@
 <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>
 <li>Outages of single AC product streams can be mitigated through merging several incoming streams into a combined product;</li>
-<li>Generating a combination product from several AC products allows detecting and rejecting outliers;</li> 
+<li>Generating a combination product from several AC products allows detecting and rejecting outliers;</li>
 <li>A Combination Center (CC) can operate BNC to globally disseminate a combination product via NTRIP broadcast;</li>
 <li>An individual AC could prefer to disseminate a stream combined from primary and backup IT resources to reduce outages;</li>
@@ -1950,5 +1950,5 @@
 </p>
 <p>
-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. 
+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.
 </p>
 <p>
@@ -1996,5 +1996,5 @@
 
 <p>
-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. 
+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.
 </p>
 
@@ -2026,5 +2026,5 @@
 <p><a name="upclk"><h4>3.14. Upload Corrections</h4></p>
 <p>
-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> 
+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>
 <li>
 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,5 +2036,5 @@
 <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>
 </ul>
-Then, epoch by epoch: 
+Then, epoch by epoch:
 <ul>
 <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,12 +2053,12 @@
 </p>
 <p>
-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. 
+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.
 </p>
 <p>
 <u>'RTNET' Stream Format</u><br>
-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. 
-</p>
-<p>
-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: 
+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.
+</p>
+<p>
+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:
 </p>
 <p>
@@ -2087,5 +2087,5 @@
 <p>
 <pre>
-*  2013  3 21  7 19 55.00000000 
+*  2013  3 21  7 19 55.00000000
 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
 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,5 +2107,5 @@
 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
 EOE
-*  2013  3 21  7 20  0.00000000 
+*  2013  3 21  7 20  0.00000000
 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
 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,5 +2136,5 @@
 <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>
 <p>
-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. 
+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.
 </p>
 
@@ -2162,5 +2162,5 @@
 </pre>
 <p>
-where s is the transformation scale, c is the speed of light, and &rho; are the topocentric distance between an (approximate) center of the transformation's validity area and the satellite. 
+where s is the transformation scale, c is the speed of light, and &rho; are the topocentric distance between an (approximate) center of the transformation's validity area and the satellite.
 </p>
 <p>
@@ -2186,5 +2186,5 @@
 Rotation in Y at epoch To:  5.390 mas
 Rotation in Z at epoch To: -8.712 mas
-Rotation rate in X:  0.081 mas/y 
+Rotation rate in X:  0.081 mas/y
 Rotation rate in Y:  0.490 mas/y
 Rotation rate in Z: -0.792 mas/y
@@ -2209,5 +2209,5 @@
 Rotation in Y at epoch To:  -9.42645 mas
 Rotation in Z at epoch To: -11.59935 mas
-Rotation rate in X: -0.06667 mas/y 
+Rotation rate in X: -0.06667 mas/y
 Rotation rate in Y:  0.75744 mas/y
 Rotation rate in Z:  0.05133 mas/y
@@ -2232,5 +2232,5 @@
 Rotation in Y at epoch To: -2.2578 mas
 Rotation in Z at epoch To: -2.4015 mas
-Rotation rate in X: -1.5461 mas/y 
+Rotation rate in X: -1.5461 mas/y
 Rotation rate in Y: -1.1820 mas/y
 Rotation rate in Z: -1.1551 mas/y
@@ -2255,8 +2255,8 @@
 Rotation in Y at epoch To: -0.030 mas
 Rotation in Z at epoch To:  0.070 mas
-Rotation rate in X:  0.000 mas/y 
+Rotation rate in X:  0.000 mas/y
 Rotation rate in Y:  0.000 mas/y
 Rotation rate in Z:  0.000 mas/y
-Scale at epoch To : 0.000000000000
+Scale at epoch To : -0.000000001000
 Scale rate: 0.000000000000 /y
 To: 0000.0
@@ -2278,5 +2278,5 @@
 Rotation in Y at epoch To:  0.000 mas
 Rotation in Z at epoch To: -0.003 mas
-Rotation rate in X:  0.000 mas/y 
+Rotation rate in X:  0.000 mas/y
 Rotation rate in Y:  0.000 mas/y
 Rotation rate in Z:  0.000 mas/y
@@ -2288,5 +2288,5 @@
 
 <p>
-<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: 
+<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:
 </p>
 <p>
@@ -2301,5 +2301,5 @@
 Rotation in Y at epoch To:   6.190 mas
 Rotation in Z at epoch To: -11.012 mas
-Rotation rate in X:  0.081 mas/y 
+Rotation rate in X:  0.081 mas/y
 Rotation rate in Y:  0.490 mas/y
 Rotation rate in Z: -0.792 mas/y
@@ -2325,5 +2325,5 @@
 </p>
 <p>
-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. 
+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.
 </p>
 <p>
@@ -2335,5 +2335,5 @@
 
 <p>
-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. 
+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.
 </p>
 
@@ -2372,5 +2372,5 @@
 
 <p>
-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'. 
+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'.
 </p>
 <p><img src="IMG/screenshot26.png"/></p>
@@ -2438,5 +2438,5 @@
 <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..
 </li>
-</ul> 
+</ul>
 
 <p><a name="streamdelete"><h4>3.16.2 Delete Stream</h4></p>
@@ -2504,15 +2504,15 @@
 <p>
 Button 'Add Stream' &gt; '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.
-</p> 
+</p>
 
 <p><a name="streamhost"><h4>3.18.1.1.1 Caster Host and Port - mandatory</h4></p>
 <p>
 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>.
-</p> 
+</p>
 
 <p><a name="streamtable"><h4>3.18.1.1.2 Casters Table - optional</h4></p>
 <p>
 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.
-</p> 
+</p>
 </p>
 <p><img src="IMG/screenshot04.png"/></p>
@@ -2523,10 +2523,10 @@
 <p>
 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.
-</p> 
+</p>
 
 <p><a name="gettable"><h4>3.18.1.1.4 Get Table</h4></p>
 <p>
 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.
-</p> 
+</p>
 <p>
 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,5 +2534,5 @@
 <p>
 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.
-</p> 
+</p>
 <p><img src="IMG/screenshot05.png"/></p>
 <p><u>Figure 30:</u> Broadcaster source-table.</p>
@@ -2629,5 +2629,5 @@
 </p>
 <p>
-When selecting one of the serial communication options listed above, make sure that you pick those configured to the serial connected GNSS receiver. 
+When selecting one of the serial communication options listed above, make sure that you pick those configured to the serial connected GNSS receiver.
 </p>
 
@@ -2655,21 +2655,21 @@
 <p>
 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.
-</p> 
+</p>
 
 <p><a name="stop"><h4>3.18.5 Stop</h4></p>
 <p>
-Hit the 'Stop' button in order to stop BNC. 
-</p> 
+Hit the 'Stop' button in order to stop BNC.
+</p>
 
 <p><a name="cmd"><h4>3.19. Command Line Options</h4></p>
-<p> 
+<p>
 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'.
-</p> 
+</p>
 
 <p><a name="nw"><h4>3.19.1 No Window Mode - optional</h4></p>
 <p>
 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.
-</p> 
-<p> 
+</p>
+<p>
 Example:<br><br>
 bnc.exe -nw
@@ -2716,5 +2716,5 @@
 </p>
 <p>Note further that option '--file' forces BNC to appy the '-nw' option for running in 'no window' mode.
-</p> 
+</p>
 
 <p><a name="conffile"><h4>3.19.3 Configuration File - optional</h4></p>
@@ -2724,11 +2724,11 @@
 Example:<br><br>
 ./bnc --conf MyConfig.bnc
-</p> 
-<p> 
+</p>
+<p>
 This leads to a BNC job using configuration file 'MyConfig.bnc'. The configuration file will be saved in the current working directory.
-</p> 
+</p>
 
 <p><a name="confopt"><h4>3.19.4 Configuration Options - optional</h4></p>
-<p> 
+<p>
 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
 </p>
@@ -2747,10 +2747,10 @@
 <p>
 ./bnc --conf CONFIG.bnc --key proxyPort 8001 --key rnxIntr "1 day"
-</p> 
+</p>
 
 <p><a name="limits"><h3>4. Limitations</h3></p>
 <ul>
 <li>
-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. 
+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.
 </li>
 
@@ -3006,5 +3006,5 @@
 </li>
 <li>
-Type 23 message provides the information on the antenna type used on the reference station. 
+Type 23 message provides the information on the antenna type used on the reference station.
 </li>
 <li>
@@ -3119,5 +3119,5 @@
 
 <p>
-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: 
+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:
 </p>
 <ul>
@@ -3135,5 +3135,5 @@
 
 <p>
-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: 
+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:
 </p>
 
@@ -3148,21 +3148,21 @@
 
 <p>
-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>. 
-</p>
-
-<p>
-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. 
-</p>
-
-<p>
-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. 
-</p>
-
-<p>
-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. 
-</p>
-
-<p>
-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. 
+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>.
+</p>
+
+<p>
+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.
+</p>
+
+<p>
+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.
+</p>
+
+<p>
+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.
+</p>
+
+<p>
+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.
 </p>
 
@@ -3173,33 +3173,33 @@
 
 <li>File 'RinexObs.bnc'<br>
-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. 
+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.
 </li><br>
 
 <li>File 'RinexEph.bnc'<br>
-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. 
+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.
 </li><br>
 
 <li>File 'BrdcCorr.bnc'<br>
-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. 
+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.
 </li><br>
 
 <li>File 'RinexConcat.bnc'<br>
-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. 
+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.
 </li><br>
 
 <li>File 'RinexQC.bnc'<br>
-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. 
+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.
 </li><br>
 
 <li>File 'RTK.bnc'<br>
-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. 
+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.
 </li><br>
 
 <li>File 'FeedEngine.bnc'<br>
-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. 
+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.
 </li><br>
 
 <li>File 'PPP.bnc'<br>
-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. 
+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.
 </li><br>
 
@@ -3209,5 +3209,5 @@
 
 <li>File 'PPPPostProc.bnc'<br>
-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. 
+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.
 </li><br>
 
@@ -3221,13 +3221,13 @@
 
 <li>File 'Sp3.bnc'<br>
-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. 
+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.
 </li><br>
- 
+
 <li>File 'Sp3ETRF2000PPP.bnc'<br>
-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. 
+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.
 </li><br>
 
 <li>File 'Upload.bnc'<br>
-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. 
+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.
 </li><br>
 
@@ -3235,15 +3235,15 @@
 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.
 </li><br>
- 
+
 <li>File 'Combi.bnc'<br>
-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. 
+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.
 </li><br>
 
 <li>File 'CombiPPP.bnc'<br>
-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. 
+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.
 </li><br>
 
 <li>File 'UploadEph.bnc'<br>
-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. 
+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.
 </li>
 
@@ -3415,5 +3415,5 @@
 </p>
 <p>
-Note that the following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data: 
+Note that the following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data:
 </p>
 <p>
@@ -3422,5 +3422,5 @@
 <li>'waitTime' to change the 'Wait for full obs epoch' option, see section 'Feed Engine';</li>
 <li>'binSampl' to change the 'Sampling' option, see section 'Feed Engine'.</li>
-<li>'outFile' to change the 'File' name where synchronized observations are saved in plain ASCII format.</li> 
+<li>'outFile' to change the 'File' name where synchronized observations are saved in plain ASCII format.</li>
 </ul>
 </p>
@@ -3470,3 +3470,3 @@
 </table>
 
- 
+
