Changeset 8058 in ntrip


Ignore:
Timestamp:
Sep 28, 2016, 2:32:50 PM (13 months ago)
Author:
wiese
Message:

REMOVE: Revision History from bnchelp

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/BNC_2.12/src/bnchelp.html

    r8052 r8058  
    217217&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.20.6 <a href=#confopt>Configuration Options</a><br><br>
    218218<b>3.</b> <a href=#annex><b>Annex</b></a><br><br>
    219 &nbsp; &nbsp; &nbsp; 3.1 <a href=#history>Revision History</a><br>
    220 &nbsp; &nbsp; &nbsp; 3.2 <a href=#rtcm>RTCM Standards</a><br>
    221 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.2.1 <a href=#ntrip1>Ntrip Version 1</a><br>
    222 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.2.2 <a href=#ntrip2>Ntrip Version 2</a><br>
    223 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.2.3 <a href=#rtcm2>RTCM Version 2</a><br>
    224 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.2.4 <a href=#rtcm3>RTCM Version 3</a><br>
    225 &nbsp; &nbsp; &nbsp; 3.3 <a href=#confList>Command Line Help</a><br>
    226 &nbsp; &nbsp; &nbsp; 3.4 <a href=#links>Further Reading</a><br>
    227 &nbsp; &nbsp; &nbsp; 3.5 <a href=#abbrev>Abbreviations</a>
     219&nbsp; &nbsp; &nbsp; 3.1 <a href=#rtcm>RTCM Standards</a><br>
     220&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.1 <a href=#ntrip1>Ntrip Version 1</a><br>
     221&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.2 <a href=#ntrip2>Ntrip Version 2</a><br>
     222&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.3 <a href=#rtcm2>RTCM Version 2</a><br>
     223&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.1.4 <a href=#rtcm3>RTCM Version 3</a><br>
     224&nbsp; &nbsp; &nbsp; 3.2 <a href=#confList>Command Line Help</a><br>
     225&nbsp; &nbsp; &nbsp; 3.3 <a href=#links>Further Reading</a><br>
     226&nbsp; &nbsp; &nbsp; 3.4 <a href=#abbrev>Abbreviations</a>
    228227</p>
    229228
     
    624623
    625624<p><h4>1.5 <a name="introInst">Installation</h4></p>
    626 <p> 
    627 Precompiled builds of BNC are available for MS Windows, Linux, and Mac OS X systems. They can be downloaded for installation from <u>http://igs.bkg.bund.de/ntrip/download</u>. Please ensure that you always use the latest released version of the program. 
    628 </p> 
    629 <p>
    630 <u>MS Windows Build:</u> A dynamically compiled shared library build for Mircrosoft Windows systems is provided as Microsoft Installer (MSI) file. MSI files are used for installation, storage, and removal of programs. The BNC files are contained in a MSI package, which is used with the program's client-side installer service, an .EXE file, to open and install the program. We used the MinGW Version 4.4.0 compiler to create BNC for Windows. After installation your 'bnc.exe' file shows up e.g. under 'All Programs'. 
     625<p>
     626Precompiled builds of BNC are available for MS Windows, Linux, and Mac OS X systems. They can be downloaded for installation from <u>http://igs.bkg.bund.de/ntrip/download</u>. Please ensure that you always use the latest released version of the program.
     627</p>
     628<p>
     629<u>MS Windows Build:</u> A dynamically compiled shared library build for Mircrosoft Windows systems is provided as Microsoft Installer (MSI) file. MSI files are used for installation, storage, and removal of programs. The BNC files are contained in a MSI package, which is used with the program's client-side installer service, an .EXE file, to open and install the program. We used the MinGW Version 4.4.0 compiler to create BNC for Windows. After installation your 'bnc.exe' file shows up e.g. under 'All Programs'.
    631630</p>
    632631
     
    636635
    637636<p>
    638 <u>Mac OS X Build:</u> 
     637<u>Mac OS X Build:</u>
    639638A shared library 'Disk iMaGe' (DMG) file is provided for BNC on OS X systems; it also comes in a ZIP archive. The DMG file format is used in the Mac for distributing software. Mac install packages appear as a virtual disk drive. After download, when the DMG file icon is double clicked, the virtual drive is 'mounted' on the desktop. Install BNC by dragging the 'bnc.app' icon to your '/Applications' folder. To start BNC, double click on '/Applications/bnc.app'. You could also start BNC via Command Line Interface (CLI) using command '/Applications/bnc.app/Contents/MacOS/bnc'.
    640639</p>
     
    642641<p><h4>1.5.1 <a name="introCompile">Compilation</h4></p>
    643642
    644 <p> 
     643<p>
    645644BNC has been written as Open Source and published under GNU General Public License (GPL). The latest source code can be checked out from Subversion repository <u>http://software.rtcm-ntrip.org/svn/trunk/BNC</u>. A ZIP archive available from <u>http://igs.bkg.bund.de/ntrip/download</u> provides the source code for BNC Version 2.12.0, developed using Qt Version 4.8.5.
    646645</p>
    647 <p>The following describes how you can produce your own builds of BNC on MS Windows, Linux, and Mac systems. It is likely that BNC can also be compiled on other systems where a GNU compiler and Qt Version 4.8.5 or any later version is installed. 
     646<p>The following describes how you can produce your own builds of BNC on MS Windows, Linux, and Mac systems. It is likely that BNC can also be compiled on other systems where a GNU compiler and Qt Version 4.8.5 or any later version is installed.
    648647</p>
    649648
     
    664663
    665664<li>Download file 'qt-win-opensource-4.8.5-mingw.exe' (317 MB) e.g. from <u>https://download.qt.io/archive/qt/4.8/4.8.5/</u>. Execute this file to install a pre-compiled shared Qt library.</li>
    666      
     665
    667666<li>Download file 'qt-everywhere-opensource-src-4.8.5.zip' (269 MB) e.g. from <u>https://download.qt.io/archive/qt/4.8/4.8.5/</u></li>
    668667
     
    722721Download file 'qt-everywhere-opensource-src-4.8.5.tar.gz' (230 MB) available from <u>https://download.qt.io/archive/qt/4.8/4.8.5/</u>. Unzip file, extract tar archive and change to directory 'qt-everywhere-opensource-src-4.8.5'. Run commands
    723722<pre>
    724   ./configure -fast -webkit -nomake examples -nomake tutorial 
     723  ./configure -fast -webkit -nomake examples -nomake tutorial
    725724              -prefix /usr/local/Trolltech/Qt-4.8.5
    726725  gmake
     
    780779As a default, configuration files for running BNC on Unix/Linux/Mac OS X systems are saved in directory '${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'. The default configuration filename is 'BNC.bnc'.</p>
    781780<p>
    782 The default filename 'BNC.bnc' can be changed and the file content can easily be edited. On graphical user interfaces it is possible to Drag &amp; Drop a configuration file icon to start BNC (not on Mac OS X systems). It is also possible to start and configure BNC via command line. Some configuration options can be changed on-the-fly. See annexed 'Command Line Help' for a complete set of configuration options. 
     781The default filename 'BNC.bnc' can be changed and the file content can easily be edited. On graphical user interfaces it is possible to Drag &amp; Drop a configuration file icon to start BNC (not on Mac OS X systems). It is also possible to start and configure BNC via command line. Some configuration options can be changed on-the-fly. See annexed 'Command Line Help' for a complete set of configuration options.
    783782</p>
    784783
     
    877876
    878877<li>Configuration File 'RinexObs.bnc'<br>
    879 Purpose: Convert RTCM streams to 
    880 RINEX Observation files. The configuration pulls streams from Ntrip 
    881 Broadcasters using Ntrip Version 1 to generate 15min 1Hz RINEX Version 3 
    882 Observation files. See <u>http://igs.bkg.bund.de/ntrip/observations</u> for observation 
    883 stream resources. 
     878Purpose: Convert RTCM streams to
     879RINEX Observation files. The configuration pulls streams from Ntrip
     880Broadcasters using Ntrip Version 1 to generate 15min 1Hz RINEX Version 3
     881Observation files. See <u>http://igs.bkg.bund.de/ntrip/observations</u> for observation
     882stream resources.
    884883</li><br>
    885884
    886885<li>Configuration File 'RinexEph.bnc'<br>
    887 Purpose: Convert a RTCM stream 
     886Purpose: Convert a RTCM stream
    888887with navigation messages to RINEX Navigation files. The configuration
    889 pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the 
    890 real-time EUREF and IGS networks and saves hourly RINEX Version 3 Navigation 
    891 files. See <u>http://igs.bkg.bund.de/ntrip/ephemeris</u> for further real-time 
    892 Broadcast Ephemeris resources. 
     888pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the
     889real-time EUREF and IGS networks and saves hourly RINEX Version 3 Navigation
     890files. See <u>http://igs.bkg.bund.de/ntrip/ephemeris</u> for further real-time
     891Broadcast Ephemeris resources.
    893892</li><br>
    894893
    895894<li>Configuration File 'BrdcCorr.bnc'<br>
    896 Purpose: Save Broadcast Corrections from RTCM 
    897 SSR messages in hourly plain ASCII files. See 
    898 <u>http://igs.bkg.bund.de/ntrip/orbits</u> for various real-time IGS or EUREF 
    899 orbit/clock correction products. 
     895Purpose: Save Broadcast Corrections from RTCM
     896SSR messages in hourly plain ASCII files. See
     897<u>http://igs.bkg.bund.de/ntrip/orbits</u> for various real-time IGS or EUREF
     898orbit/clock correction products.
    900899</li><br>
    901900
    902901<li>Configuration File 'RinexConcat.bnc'<br>
    903 Purpose: Concatenate several RINEX Version 3 files to 
    904 produce one compiled file and edit the marker name in the file header. The 
    905 sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the 
    906 documentation for examples on how to call BNC from command line in 'no window' 
    907 mode for RINEX file editing, concatenation and quality check. 
     902Purpose: Concatenate several RINEX Version 3 files to
     903produce one compiled file and edit the marker name in the file header. The
     904sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the
     905documentation for examples on how to call BNC from command line in 'no window'
     906mode for RINEX file editing, concatenation and quality check.
    908907</li><br>
    909908
    910909<li>Configuration File 'RinexQC.bnc'<br>
    911 Purpose: Check the quality of a RINEX Version 3 
    912 file by means of a multipath analysis. Results are saved on disk in terms of a 
    913 plot in PNG format. See section 'RINEX Editing & QC' in the documentation for 
    914 examples on how to call BNC from command line in 'no window' mode for RINEX 
    915 file editing, concatenation and quality check. 
     910Purpose: Check the quality of a RINEX Version 3
     911file by means of a multipath analysis. Results are saved on disk in terms of a
     912plot in PNG format. See section 'RINEX Editing & QC' in the documentation for
     913examples on how to call BNC from command line in 'no window' mode for RINEX
     914file editing, concatenation and quality check.
    916915</li><br>
    917916
    918917<li>Configuration File 'RTK.bnc'<br>
    919 Purpose: Feed a serially connected receiver with 
    920 observations from a nearby reference station for conventional RTK. The stream is 
    921 scanned for RTCM messages. Message type numbers and latencies of incoming 
    922 observations are reported in BNC's logfile. 
     918Purpose: Feed a serially connected receiver with
     919observations from a nearby reference station for conventional RTK. The stream is
     920scanned for RTCM messages. Message type numbers and latencies of incoming
     921observations are reported in BNC's logfile.
    923922</li><br>
    924923
    925924<li>Configuration File 'FeedEngine.bnc'<br>
    926 Purpose: Feed a real-time GNSS engine with 
    927 observations from remote reference stations. The configuration pulls a single 
    928 stream from an Ntrip Broadcaster. You could also pull 
    929 several streams from different casters. Incoming observations are decoded, 
    930 synchronized, output through a local IP port and also saved into a file. Failure 
    931 and recovery thresholds are specified to inform about outages. 
     925Purpose: Feed a real-time GNSS engine with
     926observations from remote reference stations. The configuration pulls a single
     927stream from an Ntrip Broadcaster. You could also pull
     928several streams from different casters. Incoming observations are decoded,
     929synchronized, output through a local IP port and also saved into a file. Failure
     930and recovery thresholds are specified to inform about outages.
    932931</li><br>
    933932
    934933<li>Configuration File 'PPP.bnc'<br>
    935 Purpose: Precise Point Positioning from 
    936 observations of a rover receiver. The configuration reads RTCM Version 3 
    937 observations, a Broadcast Ephemeris stream and a stream with Broadcast 
    938 Corrections. Positions are saved in the logfile. 
     934Purpose: Precise Point Positioning from
     935observations of a rover receiver. The configuration reads RTCM Version 3
     936observations, a Broadcast Ephemeris stream and a stream with Broadcast
     937Corrections. Positions are saved in the logfile.
    939938</li><br>
    940939
    941940<li>Configuration File 'PPPNet.bnc'<br>
    942 Purpose: Precise 
    943 Point Positioning for several rovers or receivers from an entire network of 
    944 reference stations in one BNC job. The possible maximum number of PPP solutions 
    945 per job depends on the processing power of the hosting computer. This example 
    946 configuration reads two RTCM Version 3 observation streams, a Broadcast 
    947 Ephemeris stream and a stream with Broadcast Corrections. PPP Results for the 
    948 two stations are saved in PPP logfiles. 
     941Purpose: Precise
     942Point Positioning for several rovers or receivers from an entire network of
     943reference stations in one BNC job. The possible maximum number of PPP solutions
     944per job depends on the processing power of the hosting computer. This example
     945configuration reads two RTCM Version 3 observation streams, a Broadcast
     946Ephemeris stream and a stream with Broadcast Corrections. PPP Results for the
     947two stations are saved in PPP logfiles.
    949948</li><br>
    950949
    951950<li>Configuration File 'PPPQuickStart.bnc'<br>
    952 Purpose: Precise Point Positioning in Quick-Start 
    953 mode from observations of a static receiver with precisely known position. The 
    954 configuration reads RTCM Version 3 observations, Broadcast Corrections and a 
    955 Broadcast Ephemeris stream. Positions are saved in NMEA format on disc. 
    956 They are also output through IP port for real-time visualization with tools 
    957 like RTKPLOT. Positions are saved in the logfile. 
     951Purpose: Precise Point Positioning in Quick-Start
     952mode from observations of a static receiver with precisely known position. The
     953configuration reads RTCM Version 3 observations, Broadcast Corrections and a
     954Broadcast Ephemeris stream. Positions are saved in NMEA format on disc.
     955They are also output through IP port for real-time visualization with tools
     956like RTKPLOT. Positions are saved in the logfile.
    958957</li><br>
    959958
    960959<li>Configuration File 'PPPPostProc.bnc'<br>
    961 Purpose: Precise Point Positioning in post 
    962 processing mode. BNC reads RINEX Version 3 Observation and Navigation files 
    963 and a Broadcast Correction file. PPP processing options are set to support 
    964 the Quick-Start mode. The output is saved in a specific post processing 
    965 logfile and contains coordinates derived over time following the 
    966 implemented PPP filter algorithm. 
     960Purpose: Precise Point Positioning in post
     961processing mode. BNC reads RINEX Version 3 Observation and Navigation files
     962and a Broadcast Correction file. PPP processing options are set to support
     963the Quick-Start mode. The output is saved in a specific post processing
     964logfile and contains coordinates derived over time following the
     965implemented PPP filter algorithm.
    967966</li><br>
    968967
     
    971970solutions using Google Maps or OpenStreetMap as background. BNC reads a
    972971RINEX Observation file and a RINEX Navigation file to carry out a
    973 'Standard Point Positioning' solution in post processing mode. Although 
     972'Standard Point Positioning' solution in post processing mode. Although
    974973this is not a real-time application, it requires the BNC host to be connected
    975974to the Internet. Specify a computation speed, then hit button 'Open Map'
     
    979978
    980979<li>Configuration File 'SPPQuickStartGal.bnc'<br>
    981 Purpose: Single Point Positioning in Quick-Start mode from observations of a static 
     980Purpose: Single Point Positioning in Quick-Start mode from observations of a static
    982981receiver with quite precisely known position.
    983 The configuration uses GPS, GLONASS and Galileo observations and a Broadcast 
    984 Ephemeris stream. 
     982The configuration uses GPS, GLONASS and Galileo observations and a Broadcast
     983Ephemeris stream.
    985984</li><br>
    986985
    987986<li>Configuration File 'SaveSp3.bnc'<br>
    988 Purpose: Produces SP3 files from a Broadcast 
    989 Ephemeris stream and a Broadcast Correction stream. The Broadcast Correction 
    990 stream is formally introduced in BNC's 'Combine Corrections' table. Note that 
    991 producing SP3 requires an ANTEX file because SP3 file content should be 
    992 referred to CoM. 
     987Purpose: Produces SP3 files from a Broadcast
     988Ephemeris stream and a Broadcast Correction stream. The Broadcast Correction
     989stream is formally introduced in BNC's 'Combine Corrections' table. Note that
     990producing SP3 requires an ANTEX file because SP3 file content should be
     991referred to CoM.
    993992</li><br>
    994993
    995994<li>Configuration File 'Sp3ETRF2000PPP.bnc'<br>
    996 Purpose: Produce SP3 files from a Broadcast 
    997 Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The 
    998 Broadcast Correction stream is formally introduced in BNC's 'Combine 
    999 Corrections' table. The configuration leads to a SP3 file containing orbits also referred 
    1000 to ETRF2000. Pulling in addition observations from a reference station at 
    1001 precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution 
    1002 with a known ETRF2000 reference coordinate. 
     995Purpose: Produce SP3 files from a Broadcast
     996Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The
     997Broadcast Correction stream is formally introduced in BNC's 'Combine
     998Corrections' table. The configuration leads to a SP3 file containing orbits also referred
     999to ETRF2000. Pulling in addition observations from a reference station at
     1000precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution
     1001with a known ETRF2000 reference coordinate.
    10031002</li><br>
    10041003
    10051004<li>Configuration File 'Upload.bnc'<br>
    1006 Purpose: Upload orbits and clocks from a 
    1007 real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads 
    1008 precise orbits and clocks in RTNET format. It also reads a stream carrying 
    1009 Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast 
    1010 Corrections and encodes them to RTCM Version 3 SSR messages to finally upload them to 
    1011 an Ntrip Broadcaster. The Broadcast Correction stream is referred to satellite 
    1012 Antenna Phase Center (APC) and reference system IGS08. Orbits are saved on disk 
    1013 in SP3 format and clocks are saved in Clock RINEX format. 
     1005Purpose: Upload orbits and clocks from a
     1006real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads
     1007precise orbits and clocks in RTNET format. It also reads a stream carrying
     1008Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast
     1009Corrections and encodes them to RTCM Version 3 SSR messages to finally upload them to
     1010an Ntrip Broadcaster. The Broadcast Correction stream is referred to satellite
     1011Antenna Phase Center (APC) and reference system IGS08. Orbits are saved on disk
     1012in SP3 format and clocks are saved in Clock RINEX format.
    10141013</li><br>
    10151014
    10161015<li>Configuration File 'Combi.bnc'<br>
    1017 Purpose: Pull several streams carrying Broadcast 
    1018 Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to 
    1019 produce a combined Broadcast Correction stream. BNC encodes the combination 
    1020 product in RTCM Version 3 SSR messages and uploads that to an Ntrip 
    1021 Broadcaster. The Broadcast Correction stream is referred to satellite Antenna Phase Center (APC) and not to satellite 
    1022 Center of Mass (CoM). Its reference system is IGS08. Orbits are saved in SP3 
    1023 format (referred to CoM) and clocks in Clock RINEX format. 
     1016Purpose: Pull several streams carrying Broadcast
     1017Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to
     1018produce a combined Broadcast Correction stream. BNC encodes the combination
     1019product in RTCM Version 3 SSR messages and uploads that to an Ntrip
     1020Broadcaster. The Broadcast Correction stream is referred to satellite Antenna Phase Center (APC) and not to satellite
     1021Center of Mass (CoM). Its reference system is IGS08. Orbits are saved in SP3
     1022format (referred to CoM) and clocks in Clock RINEX format.
    10241023</li><br>
    10251024
    10261025<li>Configuration File 'CombiPPP.bnc'<br>
    1027 Purpose: This configuration equals the 'Combi.bnc' configuration. However, the combined 
    1028 Broadcast Corrections are in addition used for an 'INTERNAL' PPP solution 
    1029 based on observations from a static reference station with known precise 
    1030 coordinates. This allows a continuous quality check of the combination product 
    1031 through observing coordinate displacements. 
     1026Purpose: This configuration equals the 'Combi.bnc' configuration. However, the combined
     1027Broadcast Corrections are in addition used for an 'INTERNAL' PPP solution
     1028based on observations from a static reference station with known precise
     1029coordinates. This allows a continuous quality check of the combination product
     1030through observing coordinate displacements.
    10321031</li><br>
    10331032
    10341033<li>Configuration File 'UploadEph.bnc'<br>
    1035 Purpose: Pull a number of streams from reference 
    1036 stations to get hold of contained Broadcast Ephemeris messages. They are 
    1037 encoded to RTCM Version 3 format and uploaded for the purpose of providing 
    1038 a Broadcast Ephemeris stream with an update rate of 5 seconds. 
     1034Purpose: Pull a number of streams from reference
     1035stations to get hold of contained Broadcast Ephemeris messages. They are
     1036encoded to RTCM Version 3 format and uploaded for the purpose of providing
     1037a Broadcast Ephemeris stream with an update rate of 5 seconds.
    10391038</li><br>
    10401039
    10411040<li>Configuration File 'CompareSp3.bnc'<br>
    1042 Purpose: Compare two SP3 files to calculate 
    1043 RMS values for orbit and clock differences. GPS satellite G05 and GLONASS 
    1044 satellite R18 are excluded from this comparison. Comparison results are saved 
    1045 in a logfile. 
     1041Purpose: Compare two SP3 files to calculate
     1042RMS values for orbit and clock differences. GPS satellite G05 and GLONASS
     1043satellite R18 are excluded from this comparison. Comparison results are saved
     1044in a logfile.
    10461045</li><br>
    10471046
     
    10581057<li>Shell Script 'RinexQC.sh'<br>
    10591058Purpose: Equals configuration file example 'RinexQC.bnc', checks the quality of
    1060 a RINEX Version 3 file by means of a multipath analysis. Virtual X-Server 
     1059a RINEX Version 3 file by means of a multipath analysis. Virtual X-Server
    10611060'Xvfb' is operated while producing plot files in PNG format. BNC is offline. All
    1062 results are saved on disk. 
     1061results are saved on disk.
    10631062</li><br>
    10641063
     
    10801079
    10811080<li>Shell Script 'ScanLate.sh'<br>
    1082 Purpose: Scan an observation stream for contained RTCM message types, print 
    1083 observation latencies. The output is saved in a logfile. Latencies are 
    1084 reported every 10 seconds. BNC runs online until it's terminated after 20 
     1081Purpose: Scan an observation stream for contained RTCM message types, print
     1082observation latencies. The output is saved in a logfile. Latencies are
     1083reported every 10 seconds. BNC runs online until it's terminated after 20
    10851084seconds.
    10861085</li><br>
     
    10901089streams to RINEX Observation files. The configuration pulls streams from two
    10911090Ntrip Broadcasters using Ntrip Version 1 to generate 15min 1Hz RINEX Version 3
    1092 Observation files. See <u>http://igs.bkg.bund.de/ntrip/observations</u> for 
     1091Observation files. See <u>http://igs.bkg.bund.de/ntrip/observations</u> for
    10931092observation stream resources. BNC runs online until it's terminated after 30
    10941093seconds.
     
    10971096
    10981097<b>(C) Command Line configuration options overwriting Configuration File options</b><br><br>
    1099 For specific applications you may like to use your own set of standard configuration options from a configuration file and update some of its content via command line. When using a configuration file together with command line configuration options in one BNC call, the command line configuration options will always overrule options contained in the configuration file. 
     1098For specific applications you may like to use your own set of standard configuration options from a configuration file and update some of its content via command line. When using a configuration file together with command line configuration options in one BNC call, the command line configuration options will always overrule options contained in the configuration file.
    11001099
    11011100<ol start="27">
     
    12821281<p><h4>2.3.3 <a name="genconf">Reread Configuration - optional</h4></p>
    12831282<p>
    1284 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 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. 
     1283When 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 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.
    12851284</p>
    12861285
     
    14841483                    OBSERVATION DATA    M (MIXED)           RINEX VERSION / TYPE
    14851484                                                            PGM / RUN BY / DATE
    1486 CUT0                                                        MARKER NAME         
    1487 59945M001                                                   MARKER NUMBER       
    1488 5023K67889          TRIMBLE NETR9       5.01                REC # / TYPE / VERS 
    1489 4928353386          TRM59800.00     SCIS                    ANT # / TYPE       
    1490  -2364337.2699  4870285.5624 -3360809.8398                  APPROX POSITION XYZ 
     1485CUT0                                                        MARKER NAME
     148659945M001                                                   MARKER NUMBER
     14875023K67889          TRIMBLE NETR9       5.01                REC # / TYPE / VERS
     14884928353386          TRM59800.00     SCIS                    ANT # / TYPE
     1489 -2364337.2699  4870285.5624 -3360809.8398                  APPROX POSITION XYZ
    14911490        0.0000        0.0000        0.0000                  ANTENNA: DELTA H/E/N
    1492 gnss@curtin.edu.au  CUT                                     OBSERVER / AGENCY   
     1491gnss@curtin.edu.au  CUT                                     OBSERVER / AGENCY
    14931492C   10 C1I L1I D1I S1I C6I L6I S6I C7I L7I S7I              SYS / # / OBS TYPES
    14941493E   13 C1X L1X D1X S1X C5X L5X S5X C7X L7X S7X C8X L8X S8X  SYS / # / OBS TYPES
     
    14981497R   13 C1C L1C D1C S1C C1P L1P S1P C2C L2C S2C C2P L2P S2P  SYS / # / OBS TYPES
    14991498S    7 C1C L1C D1C S1C C5I L5I S5I                          SYS / # / OBS TYPES
    1500 PORTIONS OF THIS HEADER GENERATED BY THE IGS CB FROM        COMMENT             
    1501 SITELOG cut0_20150507.log                                   COMMENT             
     1499PORTIONS OF THIS HEADER GENERATED BY THE IGS CB FROM        COMMENT
     1500SITELOG cut0_20150507.log                                   COMMENT
    15021501                                                            END OF HEADER
    15031502</pre>
     
    15241523<p><h4>2.4.8 <a name="rnxvers2">Version 2 - optional</h4></p>
    15251524<p>
    1526 GNSS observation data are generally hold available within BNC according to attributes as defined in RINEX Version 3. These attributes describe the tracking mode or channel when generating the observation signals. Capital letters specifying signal generation attributes are A, B, C, D, I, L, M, N, P, Q, S, W, X, Y, and Z, see RINEX Version 3 documentation. Although RINEX Version 3 with its signal generation attributes is the internal default processing format for BNC, there are two applications where the program is explicitly required to produce data files in RINEX Version 2 format: 
     1525GNSS observation data are generally hold available within BNC according to attributes as defined in RINEX Version 3. These attributes describe the tracking mode or channel when generating the observation signals. Capital letters specifying signal generation attributes are A, B, C, D, I, L, M, N, P, Q, S, W, X, Y, and Z, see RINEX Version 3 documentation. Although RINEX Version 3 with its signal generation attributes is the internal default processing format for BNC, there are two applications where the program is explicitly required to produce data files in RINEX Version 2 format:
    15271526<ol type=1>
    15281527<li>When saving the content of incoming observation streams in RINEX Version 2 files as described in this section.</li>
     
    15401539</p>
    15411540<p>
    1542 The default 'Signal priority' list is defined as follows: 
     1541The default 'Signal priority' list is defined as follows:
    15431542<ul>
    15441543 <li>'G:12&PWCSLXYN G:5&IQX R:12&PC R:3&IQX E:16&BCX E:578&IQX J:1&SLXCZ J:26&SLX J:5&IQX C:IQX I:ABCX S:1&C S:5&IQX'</li>
    15451544</ul>
    15461545
    1547 As an example the 'Signal priority' of 'CWPX_?' is explained in more detail: 
     1546As an example the 'Signal priority' of 'CWPX_?' is explained in more detail:
    15481547<ul>
    15491548<li>Signals with attribute 'C' enjoy the highest priority. If such a Version 3 observation becomes available, it is presented as RINEX Version 2 observation if that is the format you wish to see. Observations with other attributes are being ignored.</li>
     
    16691668</p>
    16701669<p>
    1671 Note that you may specify several RINEX Version 2 Navigation files for GPS and GLONASS. 
     1670Note that you may specify several RINEX Version 2 Navigation files for GPS and GLONASS.
    16721671</p>
    16731672
     
    18991898<p><h4>2.6.5 <a name="reqcplots">Plots for Signals - mandatory if 'Action' is set to 'Analyze'</h4></p>
    19001899<p>
    1901 Multipath and signal-to-noise sky plots as well as plots for satellite availability, elevation and PDOP are produced per GNSS system and frequency with the multipath analysis based on CnC observation types (n = band / frequency). The 'Plots for signals' option lets you exactly specify the observation signals to be used for that and also enables the plot production. You can specify the navigation system (C = BDS, E = Galileo, G = GPS, J = QZSS, R = GLONASS, S = SBAS), the frequency, and the tracking mode or channel as defined in RINEX Version 3. Specifications for frequency and tracking mode or channel must be separated by ampersand character '&'. Specifications for each navigation systems must be separated by blank character ' '. The following string is an example for option field 'Plots of signals': 
     1900Multipath and signal-to-noise sky plots as well as plots for satellite availability, elevation and PDOP are produced per GNSS system and frequency with the multipath analysis based on CnC observation types (n = band / frequency). The 'Plots for signals' option lets you exactly specify the observation signals to be used for that and also enables the plot production. You can specify the navigation system (C = BDS, E = Galileo, G = GPS, J = QZSS, R = GLONASS, S = SBAS), the frequency, and the tracking mode or channel as defined in RINEX Version 3. Specifications for frequency and tracking mode or channel must be separated by ampersand character '&'. Specifications for each navigation systems must be separated by blank character ' '. The following string is an example for option field 'Plots of signals':
    19021901<br>
    19031902<pre>
     
    19381937</p>
    19391938<p>
    1940 The default 'Signal priority' list is defined as follows: 
     1939The default 'Signal priority' list is defined as follows:
    19411940<ul>
    19421941 <li>'G:12&PWCSLXYN G:5&IQX R:12&PC R:3&IQX E:16&BCX E:578&IQX J:1&SLXCZ J:26&SLX J:5&IQX C:IQX I:ABCX S:1&C S:5&IQX'</li>
     
    19531952
    19541953<p>
    1955 You can specify a list of observation codes in field 'Use Obs. Types' to limit the output file content to specific observation codes. GNSS system characters in that list are followed by a colon and a 2- or 3-Character observation code. A 2-Character observation code would mean that all available tracking modes of the affected observation type and frequency will be accepted as part of the RINEX output file. Observation codes are separated by a blank character. Default is an empty option field, meaning that any input observation code will become part of the RINEX output file. 
     1954You can specify a list of observation codes in field 'Use Obs. Types' to limit the output file content to specific observation codes. GNSS system characters in that list are followed by a colon and a 2- or 3-Character observation code. A 2-Character observation code would mean that all available tracking modes of the affected observation type and frequency will be accepted as part of the RINEX output file. Observation codes are separated by a blank character. Default is an empty option field, meaning that any input observation code will become part of the RINEX output file.
    19561955</p>
    19571956
     
    19951994</p>
    19961995<pre>
    1997    ./bnc --nw --conf rnx.conf --key reqcAction Edit/Concatenate --key reqcObsFile 
    1998    "tlse119b00.12o,tlse119b15.12o,tlse119b30.12o,tlse119b45.12o" --key 
     1996   ./bnc --nw --conf rnx.conf --key reqcAction Edit/Concatenate --key reqcObsFile
     1997   "tlse119b00.12o,tlse119b15.12o,tlse119b30.12o,tlse119b45.12o" --key
    19991998   reqcOutObsFile tlse119b.12o --key reqcRnxVersion 3 --key reqcSampling 30
    20001999</pre>
     
    20102009<p>The following Linux command line produces RINEX QC plots (see Estey and Meertens 1999) offline in 'no window' mode and saves them in directory '/home/user'. Introducing a dummy configuration file /dev/null makes sure that no configuration options previously saved on disc are used:</p>
    20112010<pre>
    2012    /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile 
     2011   /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile
    20132012   CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key
    20142013   reqcPlotDir /home/user --nw
     
    20182017</p>
    20192018<pre>
    2020    /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile 
     2019   /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile
    20212020   CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key
    20222021   --key startTab 4 --key autoStart 2
     
    20672066<p><h4>2.7 <a name="sp3comp">SP3 Comparison</h4></p>
    20682067<p>
    2069 BNC allows to compare the contents of two files with GNSS orbit and clock data in SP3 format. SP3 ASCII files basically contain a list of records over a certain period of time. Each record carries a time tag, the XYZ position of the satellite's Center of Mass at that time and the corresponding satellite clock value. Both SP3 files may contain some records for different epochs. If so, then BNC only compares records for identical epochs. BNC accepts that a specific GNSS system or a specific satellite is only available from one of the SP3 files. Note that BNC does not interpolate orbits when comparing SP3 files. 
     2068BNC allows to compare the contents of two files with GNSS orbit and clock data in SP3 format. SP3 ASCII files basically contain a list of records over a certain period of time. Each record carries a time tag, the XYZ position of the satellite's Center of Mass at that time and the corresponding satellite clock value. Both SP3 files may contain some records for different epochs. If so, then BNC only compares records for identical epochs. BNC accepts that a specific GNSS system or a specific satellite is only available from one of the SP3 files. Note that BNC does not interpolate orbits when comparing SP3 files.
    20702069</p>
    20712070<p>
     
    22152214<pre>
    22162215 &nbsp; &nbsp; dt =  -2 (R * V) / c<sup>2</sup>
    2217 </pre> 
     2216</pre>
    22182217
    22192218<p>
     
    25192518> VTEC 2015 06 19 16 41 00.0 6 1 CLK93
    25202519 1  6  6   450000.0
    2521    16.7450     0.0000     0.0000     0.0000     0.0000     0.0000     0.0000 
    2522     4.9300     8.1600     0.0000     0.0000     0.0000     0.0000     0.0000 
    2523    -4.4900     0.2550     1.0950     0.0000     0.0000     0.0000     0.0000 
    2524    -2.2450    -1.9500    -0.7950    -0.4700     0.0000     0.0000     0.0000 
    2525     1.0250    -0.9000    -0.0900     0.1050     0.1450     0.0000     0.0000 
    2526     1.5500     0.9750    -0.8150     0.3600     0.0350    -0.0900     0.0000 
    2527    -0.4050     0.8300     0.0800    -0.0650     0.2200     0.0150    -0.1600 
    2528     0.0000     0.0000     0.0000     0.0000     0.0000     0.0000     0.0000 
    2529     0.0000    -0.1250     0.0000     0.0000     0.0000     0.0000     0.0000 
    2530     0.0000     1.0050    -0.7750     0.0000     0.0000     0.0000     0.0000 
    2531     0.0000    -0.2300     0.7150     0.7550     0.0000     0.0000     0.0000 
    2532     0.0000    -0.4100    -0.1250     0.2400     0.2700     0.0000     0.0000 
    2533     0.0000     0.0850    -0.3400    -0.0500    -0.2200    -0.0750     0.0000 
    2534     0.0000     0.2000    -0.2850    -0.0150    -0.0250     0.0900     0.0650 
     2520   16.7450     0.0000     0.0000     0.0000     0.0000     0.0000     0.0000
     2521    4.9300     8.1600     0.0000     0.0000     0.0000     0.0000     0.0000
     2522   -4.4900     0.2550     1.0950     0.0000     0.0000     0.0000     0.0000
     2523   -2.2450    -1.9500    -0.7950    -0.4700     0.0000     0.0000     0.0000
     2524    1.0250    -0.9000    -0.0900     0.1050     0.1450     0.0000     0.0000
     2525    1.5500     0.9750    -0.8150     0.3600     0.0350    -0.0900     0.0000
     2526   -0.4050     0.8300     0.0800    -0.0650     0.2200     0.0150    -0.1600
     2527    0.0000     0.0000     0.0000     0.0000     0.0000     0.0000     0.0000
     2528    0.0000    -0.1250     0.0000     0.0000     0.0000     0.0000     0.0000
     2529    0.0000     1.0050    -0.7750     0.0000     0.0000     0.0000     0.0000
     2530    0.0000    -0.2300     0.7150     0.7550     0.0000     0.0000     0.0000
     2531    0.0000    -0.4100    -0.1250     0.2400     0.2700     0.0000     0.0000
     2532    0.0000     0.0850    -0.3400    -0.0500    -0.2200    -0.0750     0.0000
     2533    0.0000     0.2000    -0.2850    -0.0150    -0.0250     0.0900     0.0650
    25352534</pre>
    25362535</p>
     
    25622561<p><u>Table 2:</u> Contents and format of synchronized output of observations feeding a GNSS engine</p>
    25632562<p>
    2564 <table> 
     2563<table>
    25652564<tr><td></td><td><b>Example</b></td><td><b>Format</b></td></tr>
    25662565
     
    30163015<p>
    30173016<u>RINEX Files</u><br>
    3018 This input mode allows to specify RINEX Observation, RINEX Navigation and Broadcast Correction files. BNC accepts RINEX Version 2 as well as RINEX Version 3 Observation or Navigation file formats. Files carrying Broadcast Corrections must have the format produced by BNC through the 'Broadcast Corrections' panel. 
     3017This input mode allows to specify RINEX Observation, RINEX Navigation and Broadcast Correction files. BNC accepts RINEX Version 2 as well as RINEX Version 3 Observation or Navigation file formats. Files carrying Broadcast Corrections must have the format produced by BNC through the 'Broadcast Corrections' panel.
    30193018</p>
    30203019<p>
     
    30293028</li>
    30303029</ul>
    3031 </p> 
     3030</p>
    30323031
    30333032<p><h4>2.13.1.2 <a name="ppprnxobs">RINEX Observation File - mandatory if 'Data source' is set to 'RINEX Files'</h4></p>
     
    30943093</p>
    30953094<p>
    3096 The following is the content of an example 'Coordinates file'. Here each record describes the mountpoint of a stream available from the global IGS real-time reference station network. A priori coordinates are followed by North/East/Up eccentricity components of the ARP 
     3095The following is the content of an example 'Coordinates file'. Here each record describes the mountpoint of a stream available from the global IGS real-time reference station network. A priori coordinates are followed by North/East/Up eccentricity components of the ARP
    30973096followed by the antenna name and radome in use.
    30983097</p>
     
    33233322<p><h4>2.13.1.10 <a name="pppnmeafile">NMEA Directory - optional</h4></p>
    33243323<p>
    3325 You can specify a 'NMEA directory' to save daily NMEA files with Point Positioning results recorded as NMEA sentences. Such sentences are usually generated about once per second with pairs of 
     3324You can specify a 'NMEA directory' to save daily NMEA files with Point Positioning results recorded as NMEA sentences. Such sentences are usually generated about once per second with pairs of
    33263325</p>
    33273326<p>
     
    33683367   T(z) = T_apr(z) + dT / cos(z)
    33693368</pre>
    3370 where T_apr is the a priori tropospheric delay derived from Saastamoinen model. 
     3369where T_apr is the a priori tropospheric delay derived from Saastamoinen model.
    33713370</p>
    33723371
     
    33763375
    33773376<pre>
    3378 %=TRO 2.00 BKG 16:053:42824 BKG 16:053:42824 16:053:43199 P 00376 0  T 
     3377%=TRO 2.00 BKG 16:053:42824 BKG 16:053:42824 16:053:43199 P 00376 0  T
    33793378+FILE/REFERENCE
    33803379 DESCRIPTION        BNC generated SINEX TRO file
     
    35673566<p><h4>2.13.3.4 <a name="pppeleweight">Elevation Dependent Weighting - mandatory</h4></p>
    35683567<p>
    3569 BNC allows elevation dependent weighting when processing GNSS observations. A weight function 
     3568BNC allows elevation dependent weighting when processing GNSS observations. A weight function
    35703569</p>
    35713570
     
    36183617
    36193618<p>
    3620 'Seeding' has also a function for <u>bridging gaps</u> in PPP solutions from failures caused e.g. by longer lasting outages. Should the time span between two consecutive solutions exceed the limit of 60 seconds (maximum solution gap, hard-wired), the algorithm fixes the latest derived coordinate for a period of 'Seeding' seconds. This option avoids time-consuming reconvergences and makes especially sense for stationary operated receivers where convergence can be enforced because a good approximation for the receiver position is known. 
     3619'Seeding' has also a function for <u>bridging gaps</u> in PPP solutions from failures caused e.g. by longer lasting outages. Should the time span between two consecutive solutions exceed the limit of 60 seconds (maximum solution gap, hard-wired), the algorithm fixes the latest derived coordinate for a period of 'Seeding' seconds. This option avoids time-consuming reconvergences and makes especially sense for stationary operated receivers where convergence can be enforced because a good approximation for the receiver position is known.
    36213620</p>
    36223621
     
    37223721
    37233722<p>
    3724 A combination is carried out following a specified sampling interval. BNC waits for incoming Broadcast Corrections for the period of one such interval. Corrections received later than that will be ignored. If incoming streams have different rates, only epochs that correspond to the sampling interval are used. 
     3723A combination is carried out following a specified sampling interval. BNC waits for incoming Broadcast Corrections for the period of one such interval. Corrections received later than that will be ignored. If incoming streams have different rates, only epochs that correspond to the sampling interval are used.
    37253724</p>
    37263725
     
    37543753<p></p>
    37553754<p>
    3756 Note that BNC can produce an internal PPP solution from combined Broadcast Corrections. For that you have to specify the keyword 'INTERNAL' as 'Corrections stream' in the PPP (1) panel. The following example combines correction streams IGS01 and IGS02 and simultaneously carries out a PPP solution with observations from stream FFMJ1 to allow monitoring the quality of the combination product in the space domain. 
     3755Note that BNC can produce an internal PPP solution from combined Broadcast Corrections. For that you have to specify the keyword 'INTERNAL' as 'Corrections stream' in the PPP (1) panel. The following example combines correction streams IGS01 and IGS02 and simultaneously carries out a PPP solution with observations from stream FFMJ1 to allow monitoring the quality of the combination product in the space domain.
    37573756</p>
    37583757<p><img src="IMG/screenshot23.png"/></p>
     
    37613760<p><h4>2.14.1 <a name="combimounttab">Combine Corrections Table - optional</h4></p>
    37623761<p>
    3763 Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Correction mountpoint from the 'Streams' section and hit Enter. Then double click on the 'AC Name' field to enter your choice of an abbreviation for the Analysis Center (AC) providing the Antenna Phase Center (APC) related correction stream. Finally, double click on the 'Weight' field to enter a weight to be applied to this stream in the combination. 
     3762Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Correction mountpoint from the 'Streams' section and hit Enter. Then double click on the 'AC Name' field to enter your choice of an abbreviation for the Analysis Center (AC) providing the Antenna Phase Center (APC) related correction stream. Finally, double click on the 'Weight' field to enter a weight to be applied to this stream in the combination.
    37643763</p>
    37653764<p>
     
    38323831</p>
    38333832<p>
    3834 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 can provide 
     3833Below 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 can provide
    38353834</p>
    38363835<p>
     
    38423841A set of parameters can be defined for each satellite as follows:
    38433842<pre>
    3844 &lt;SatelliteID&gt; &lt;key&gt; &lt;numValues&gt; &lt;value1 value2 ...&gt; 
     3843&lt;SatelliteID&gt; &lt;key&gt; &lt;numValues&gt; &lt;value1 value2 ...&gt;
    38453844              &lt;key&gt; &lt;numValues&gt; &lt;value1 value2 ...&gt; ... &nbsp;
    38463845</pre>
     
    38893888<pre>
    38903889* 2015 6 11 15 10 40.000000
    3891 VTEC 0 1 0 6 6 450000.0 20.4660 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 5.3590 9.6580 0.0000 0.0000 0.0000 0.0000 0.0000 -6.3610 -0.1210 1.1050 0.0000 0.0000 0.0000 0.0000 -2.7140 -1.8200 -0.9920 -0.6430 0.0000 0.0000 0.0000 1.9140 -0.5180 0.2530 0.0870 -0.0110 0.0000 0.0000 2.2950 1.0510 -0.9540 0.6220 -0.0720 -0.0810 0.0000 -0.9760 0.7570 0.2320 -0.2520 0.1970 -0.0680 -0.0280 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.2720 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 1.1100 -1.0170 0.0000 0.0000 0.0000 0.0000 0.0000 -1.1500 0.5440 0.9890 0.0000 0.0000 0.0000 0.0000 -0.3770 -0.1990 0.2670 -0.0470 0.0000 0.0000 0.0000 0.6550 -0.0130 -0.2310 -0.4810 -0.3510 0.0000 0.0000 0.2360 -0.0710 0.0280 0.1900 -0.0810 0.0710 
     3890VTEC 0 1 0 6 6 450000.0 20.4660 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 5.3590 9.6580 0.0000 0.0000 0.0000 0.0000 0.0000 -6.3610 -0.1210 1.1050 0.0000 0.0000 0.0000 0.0000 -2.7140 -1.8200 -0.9920 -0.6430 0.0000 0.0000 0.0000 1.9140 -0.5180 0.2530 0.0870 -0.0110 0.0000 0.0000 2.2950 1.0510 -0.9540 0.6220 -0.0720 -0.0810 0.0000 -0.9760 0.7570 0.2320 -0.2520 0.1970 -0.0680 -0.0280 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.2720 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 1.1100 -1.0170 0.0000 0.0000 0.0000 0.0000 0.0000 -1.1500 0.5440 0.9890 0.0000 0.0000 0.0000 0.0000 -0.3770 -0.1990 0.2670 -0.0470 0.0000 0.0000 0.0000 0.6550 -0.0130 -0.2310 -0.4810 -0.3510 0.0000 0.0000 0.2360 -0.0710 0.0280 0.1900 -0.0810 0.0710
    38923891IND 0 1
    38933892G01 APC 3   -14442611.532   -13311059.070   -18020998.395 Clk 1   -1426.920500 Vel 3  2274.647600   -28.980300 -1787.861900 CoM 3   -14442612.572   -13311059.518   -18020999.539 CodeBias 6 1W -3.760000 1C -3.320000 2W -6.200000 2X -5.780000 1H -3.350000 5I -5.430000 YawAngle 1 -0.315600 YawRate 1 0.0 PhaseBias 3 1C  3.9473 1 2 4 2W  6.3143 1 2 4 5I 6.7895 1 2 4
     
    41924191<br>
    41934192<li>With 'Sampling Orb' set to '5' BNC will produce</li>
    4194 <ul> 
     4193<ul>
    41954194<li>Every 5 sec a 1057 message for GPS orbit corrections to Broadcast Ephemeris,</li>
    41964195<li>Every 5 sec a 1058 message for GPS clock corrections to Broadcast Ephemeris,</li>
     
    41994198<br>
    42004199<li>With 'Sampling Orb' set to '10' BNC will produce</li>
    4201 <ul> 
     4200<ul>
    42024201<li>Every 10 sec a 1057 message for GPS orbit corrections to Broadcast Ephemeris,</li>
    42034202<li>Every 5 sec a 1058 message for GPS clock corrections to Broadcast Ephemeris,</li>
     
    42474246<li>QZSS ephemeris will be interpreted as outdated and ignored when older than 4 hours.</li>
    42484247</ul>
    4249 A note 'OUTDATED EPHEMERIS' will be given in the logfile and the data will be disregarded when necessary. 
     4248A note 'OUTDATED EPHEMERIS' will be given in the logfile and the data will be disregarded when necessary.
    42504249</p>
    42514250<p>
     
    45464545<p><h4>2.20 <a name="cmd">Command Line Options</h4></p>
    45474546<p>
    4548 Command line options are available to run BNC in 'no window' mode or let it read previously recorded input offline from one or several files for debugging or post processing purposes. It is also possible to introduce a specific configuration filename instead of using the default filename 'BNC.bnc'. The self-explaining content of the configuration file can easily be edited. 
     4547Command line options are available to run BNC in 'no window' mode or let it read previously recorded input offline from one or several files for debugging or post processing purposes. It is also possible to introduce a specific configuration filename instead of using the default filename 'BNC.bnc'. The self-explaining content of the configuration file can easily be edited.
    45494548</p>
    45504549<p>
     
    46564655</p>
    46574656<p>
    4658 Values for configuration options can be introduced via command line exactly as they show up in the configuration file. However, any value containing one or more blank characters must be enclosed by quotation marks when specified on command line. 
     4657Values for configuration options can be introduced via command line exactly as they show up in the configuration file. However, any value containing one or more blank characters must be enclosed by quotation marks when specified on command line.
    46594658</p>
    46604659
    46614660<p><h3>3. <a name="annex">Annex</h3></p>
    46624661
    4663 <p><h4>3.1 <a name=history>Revision History</h3></p>
    4664 <table>
    4665 <tr></tr>
    4666 
    4667 <tr>
    4668 <td>Dec 2006 &nbsp;</td><td>Version 1.0b &nbsp;</td>
    4669 <td>[Add] First Beta Binaries published based on Qt 4.2.3.</td>
    4670 </tr>
    4671 
    4672 <tr>
    4673 <td>Jan 2007 &nbsp;</td><td>Version 1.1b &nbsp;</td>
    4674 <td>[Add] Observables C2, S1, and S2<br>[Add] Virtual reference station access<br>[Bug] RTCM2 decoder time tag fixed<br>[Mod] Small letters for public RINEX skeleton files<br>[Add] Online help through Shift+F1</td>
    4675 </tr>
    4676 
    4677 <tr>
    4678 <td>Apr 2007 &nbsp;</td><td>Version 1.2b &nbsp;</td>
    4679 <td>[Bug] Output only through IP port<br>[Bug] Method 'reconnecting' now thread-save<br> [Add] ZERO decoder added<br> [Mod] Download public RINEX skeletons once per day<br> [Mod] Upgrade to Qt Version 4.2.3<br> [Mod] Replace 'system' call for RINEX script by 'QProcess'<br> [Add] HTTP Host directive for skeleton file download<br> [Add] Percent encoding for user IDs and passwords<br> [Bug] Exit execution of calling thread for RTCM3 streams<br> [Bug] Signal-slot mechanism for threads</td>
    4680 </tr>
    4681 
    4682 <tr>
    4683 <td>May 2007 &nbsp;</td><td>Version 1.3 &nbsp;</td>
    4684 <td>[Add] Source code published.</td>
    4685 </tr>
    4686 
    4687 <tr>
    4688 <td>Jul 2007 &nbsp;</td><td>Version 1.4 &nbsp;</td>
    4689 <td>[Bug] Skip messages from proxy server<br> [Bug] Call RINEX script through 'nohup'</td>
    4690 </tr>
    4691 
    4692 <tr>
    4693 <td>Apr 2008 &nbsp;</td><td>Version 1.5 &nbsp;</td>
    4694 <td>[Add] Handle ephemeris from RTCM Version 3 streams<br> [Add] Upgrade to Qt Version 4.3.2<br> [Add] Optional RINEX v3 output<br> [Add] SBAS support<br> [Bug] RINEX skeleton download following stream outage<br> [Add] Handle ephemeris from RTIGS streams<br> [Add] Monitor stream failure/recovery and latency<br> [Mod] Redesign of main window<br> [Bug] Freezing of About window on Mac OS X<br> [Bug] Fixed problem with PRN 32 in RTCM v2 decoder<br> [Bug] Fix for Trimble 4000SSI receivers in RTCM v2 decoder<br> [Mod] Major revision of input buffer in RTCM v2 decoder</td>
    4695 </tr>
    4696 
    4697 <tr>
    4698 <td>Dec 2008 &nbsp;</td><td>Version 1.6 &nbsp;</td>
    4699 <td>[Mod] Fill blank columns in RINEX v3 with 0.000<br> [Add] RTCM v3 decoder for orbit and clock corrections<br>[Add] Check RTCM v3 streams for incoming message types<br> [Add] Decode RTCM v2 message types 3, 20, 21, and 22<br> [Add] Loss of lock and lock time indicator<br> [Bug] Rounding error in RTCM v3 decoder concerning GLONASS height<br> [Mod] Accept GLONASS in RTCM v3 when transmitted first<br> [Add] Leap second 1 January 2009<br> [Add] Offline mode, read data from file<br> [Add] Output antenna descriptor, coordinates and eccentricities from RTCM v3<br> [Add] Reconfiguration on-the-fly<br> [Mod] Binary output of synchronized observations<br> [Add] Binary output of unsynchronized observations<br> [Bug] Fixed problem with joined RTCM v3 blocks</td>
    4700 </tr>
    4701 
    4702 <tr>
    4703 <td>Dec 2008 &nbsp;</td><td>Version 1.6.1 &nbsp;</td>
    4704 <td>[Mod] HTTP GET when no proxy in front</td>
    4705 </tr>
    4706 
    4707 <tr>
    4708 <td>Nov 2009 &nbsp;</td><td>Version 1.7 &nbsp;</td>
    4709 <td>[Bug] RINEX Navigation file format<br> [Add] Upgrade to Qt Version 4.5.2<br> [Add] Support of Ntrip v2<br> [Add] Rover support via serial port<br> [Add] Show broadcaster table from www.rtcm-ntrip.org<br> [Add] Enable/disable panel widgets<br> [Add] User defined configuration filename<br> [Mod] Switch to configuration files in ini-Format<br> [Add] Daily logfile rotation<br> [Add] Read from TCP/IP port, by-pass Ntrip transport protocol<br> [Add] Save NMEA sentences coming from rover<br> [Add] Auto start<br> [Add] Drag and drop ini files<br> [Add] Read from serial port, by-pass Ntrip transport protocol<br> [Mod] Update of SSR messages following RTCM 091-2009-SC104-542<br> [Add] Read from UPD port, by-pass Ntrip transport protocol<br> [Mod] Output format of Broadcast Corrections<br> [Add] Throughput plot<br> [Add] Latency plot</td>
    4710 </tr>
    4711 
    4712 <tr>
    4713 <td>Nov 2009 &nbsp;</td><td>Version 1.8 &nbsp;</td>
    4714 <td>[Mod] On-the-fly reconfiguration of latency and throughput plots</td>
    4715 </tr>
    4716 
    4717 <tr>
    4718 <td>Feb 2010 &nbsp;</td><td>Version 2.0 &nbsp;</td>
    4719 <td>[Mod] Change sign of Broadcast Corrections<br> [Add] Real-time PPP option</td>
    4720 </tr>
    4721 
    4722 <tr>
    4723 <td>Jun 2010 &nbsp;</td><td>Version 2.1 &nbsp;</td>
    4724 <td>[Bug] SSR GLONASS message generation<br> [Add] PPP in post processing mode<br> [Mod] Update of SSR messages following draft dated 2010-04-12<br> [Mod] Generating error message when observation epoch is wrong</td>
    4725 </tr>
    4726 
    4727 <tr>
    4728 <td>Jul 2010 &nbsp;</td><td>Version 2.2 &nbsp;</td>
    4729 <td>[Bug] GLONASS ephemeris time</td>
    4730 </tr>
    4731 
    4732 <tr>
    4733 <td>Aug 2010 &nbsp;</td><td>Version 2.3 &nbsp;</td>
    4734 <td>[Mod] Internal format for saving raw streams<br> [Bug] Outlier detection in GLONASS ambiguity resolution<br> [Mod] Format of PPP logs in logfile<br> [Bug] Complete acceleration terms for GLONASS ephemeris<br> [Bug] Handling ephemeris IOD's in PPP mode</td>
    4735 </tr>
    4736 
    4737 <tr>
    4738 <td>Dec 2010 &nbsp;</td><td>Version 2.4 &nbsp;</td>
    4739 <td>[Add] Output of averaged positions when in PPP mode<br> [Mod] Use always the latest received set of Broadcast Ephemeris<br> [Add] QuickStart PPP option<br> [Mod] Improvement of data sharing efficiency among different threads<br> [Mod] Design of PPP panel section<br> [Add] Sigmas for observations and parameters<br> [Add] Stream distribution map<br> [Bug] GPS Ephemeris in RINEX v3 format</td>
    4740 </tr>
    4741 
    4742 <tr>
    4743 <td>Feb 2011 &nbsp;</td><td>Version 2.5 &nbsp;</td>
    4744 <td>[Add] PPP option for sync of clock observations and corrections<br> [Add] Drafted RTCM v3 Galileo ephemeris messages 1045<br> [Add] Drafted RTCM v3 Multiple Signal Messages<br> [Add] Optional specification of sigmas for coordinates and troposphere in PPP<br> [Add] Include Galileo in SPP<br> [Add] Include Galileo observations in output via IP port<br> [Add] Include Galileo observations in output via RINEX v3 files<br> [Mod] Interface format for feeding a real-time engine with observations<br> [Add] Correct observations for Antenna Phase Center offsets<br> [Add] Combine orbit/clock correction streams<br> [Add] Specify corrections mountpoint in PPP panel</td>
    4745 </tr>
    4746 
    4747 <tr>
    4748 <td>Apr 2011 &nbsp;</td><td>Version 2.6 &nbsp;</td>
    4749 <td>[Add] Complete integration of BNS in BNC<br> [Add] SP3 and Clock RINEX output<br> [Add] PPP in post processing Mode<br> [Add] Some RINEX editing & QC functionality<br> [Add] Threshold for orbit outliers in combination solution<br> [Add] Real-time engine becomes orbit/clock server instead of client<br> [Mod] 'EOE' added to orbit/clock stream from engine<br> [Add] Correction for antenna eccentricities<br> [Add] Quick start mode for PPP<br> [Mod] Design of format for feeding engine changed to follow RINEX v3<br> [Mod] Implementation of SSR message encoding modified according to standard<br> [Add] SSL/TLS Support of Ntrip Version 2<br> [Mod] Switch to Qt version 4.7.3<br> [Add] RINEX editing, concatenation and quality check<br> [Add] Reading all configuration options from command line<br> [Mod] RTCM v3 Galileo Broadcast Ephemeris message 1045<br> [Mod] Change default configuration file suffix from 'ini' to 'bnc'<br> [Add] Specific rates for orbits and clocks in streams and SP3/RNX files</td>
    4750 </tr>
    4751 
    4752 <tr>
    4753 <td>May 2012 &nbsp;</td><td>Version 2.6 &nbsp;</td>
    4754 <td>[Add] Version 2.6 published</td>
    4755 </tr>
    4756 
    4757 <tr>
    4758 <td>Sep 2012 &nbsp;</td><td>Version 2.7 &nbsp;</td>
    4759 <td>[Bug] Bug in L5 decoding fixed<br> [Bug] Bug in on-the-fly configuration fixed<br> [Add] Clock RINEX file header extended<br> [Add] Decoding/converting BeiDou and QZSS added<br> [Add] Work on RINEX v2 and v3 quality check started<br> [Mod] Source code completely re-arranged<br> [Add] QWT and QWTPOLAR graphics libraries added<br> [Add] RINEX QC through multipath analysis sky plot<br> [Add] RINEX QC through signal-to-noise ratio sky plot<br> [Add] RINEX QC through satellite availability plot<br> [Add] RINEX QC through satellite elevation plot<br> [Add RINEX QC through PDOP plot<br> [Bug] Short periodic outages in PPP time series when 'Sync Corr' set to zero<br> |Add] Log observation types contained in RTCM Version 3 MSM streams<br> [Add] Reading RINEX v3 observation type header records from RINEX skeleton files<br> [Add] Logfile for RINEX file editing and concatenation<br>[Add] Save PNG plot files on disk<br> [Mod] Plot stream distribution map from Ntrip Broadcaster source-table<br> [Add] Plot stream distribution map from selected sources<br> [Add] Version 2.7 published</td>
    4760 </tr>
    4761 
    4762 <tr>
    4763 <td>Mar 2013 &nbsp;</td><td>Version 2.8 &nbsp;</td>
    4764 <td>[Mod] Started work on new version in Sep 2012<br> [Bug] Epoch special event flag in RINEX concatenation<br> [Bug] Limit RINEX v2 records length to 80 characters<br> [Bug] SSR message update interval indicator<br> [Bug] Fixed SSR stream encoding and upload<br> [Add] Concatenate RINEX v3 navigation files containing Galileo ephemeris<br> [Mod] Plausibility check of GLONASS ephemeris<br> [Add] Correcting clocks for scale factor involved in transformation<br> [Mod] Orbit/clock interpolation in SSR stream encoding and upload to caster<br> [Add] Version 2.8 published</td>
    4765 </tr>
    4766 
    4767 <tr>
    4768 <td>Jul 2013 &nbsp;</td><td>Version 2.9 &nbsp;</td>
    4769 <td>[Add] Started work on new version in Mar 2013<br>[Bug] SSR stream upload buffering disabled<br>[Mod] Format for feeding a connected GNSS engine<br>[Mod] RTNET format for receiving data from a connected GNSS engine<br>[Add] Include Galileo in SPP<br>[Add] RINEX QC multipath an SNR sky plots for GLONASS and Galileo<br>[Add] Bias estimation for GLONASS clocks in PPP<br>[Add] Trace positions on GM or OSM maps<br>[Add] Version 2.9 published</td>
    4770 </tr>
    4771 
    4772 <tr>
    4773 <td>Dec 2013 &nbsp;</td><td>Version 2.10 &nbsp;</td>
    4774 <td>[Add] Started work on new version in Aug 2013<br>[Bug] Clock RINEX und SP3 file generation on Windows systems<br>[Bug] Broadcast Ephemeris generation<br>[Add] Transformation ITRF2008 to NAD83 and DREF91<br>[Add] CodeBias added to RTNET stream format<br>[Bug] GPS L2 in 'Feed Engine' output<br>[Mod] Made C1 in BeiDou default observation type instead of C2<br>[Add] Feed engine output sorted per stream<br>[Add] Feed engine output filename change on-the-fly<br>[Add] 'Append files' option for RINEX observation files<br>[Mod] Broadcast Correction ASCII file output for message 1058 &amp; 1064 modified<br>[Bug] GPS L2 phase data in RINEX2<br>[Bug] GLONASS frequency numbers<br>[Add] RTCM v3 Galileo Broadcast Ephemeris message 1046<br>[Add] Reset ambiguities in PPP when orbit/clock correction IDs change<br>[Add] Satellite clock offsets are reset in adjustment for combination when orbit/clock correction IDs change<br>[Add] Version 2.10 published</td>
    4775 </tr>
    4776 
    4777 <tr>
    4778 <td>Sep 2014 &nbsp;</td><td>Version 2.11 &nbsp;</td>
    4779 <td>[Add] Started work on new version in Dec 2013<br>[Mod] SIRGAS transformation parameters adjusted<br>[Mod] ANTEX file updated<br>[Mod] RTCM SSR messages updated<br>[Bug] GLONASS code biases<br>[Mod] Maximum number of GNSS observations increased<br>[Mod] Loss of lock handling changed<br>[Add] Raw stream output through TCP/IP port<br>[Add] Version 2.11.0 published</td>
    4780 </tr>
    4781 
    4782 <tr>
    4783 <td>Mar 2016 &nbsp;</td><td>Version 2.12 &nbsp;</td><td>
    4784 [Add] Started work on new version in Sep 2014<br>
    4785 [Mod] RINEX file concatenation<br>
    4786 [Add] Observation code selection in RINEX file editing<br>
    4787 [Mod] Routine handling of data input and output in RINEX format re-written<br>
    4788 [Mod] QC routines re-written with the goal of handling all signal types<br>
    4789 [Add] Machine-readable output of RINEX QC<br>
    4790 [Add] PPP client functionality for parallel processing of an arbitrary number of stations in separate threads<br>
    4791 [Bug] Receiver antenna PCO in ionosphere-free PPP mode<br>
    4792 [Add] NMEA output for any station processed in PPP mode<br>
    4793 [Add] PPP processing of any number of linear combinations of GNSS measurements selected by user<br>
    4794 [Add] Encoding/Decoding RTCM SSR I messages for Galileo, BDS, SBAS and QZSS<br>
    4795 [Add] Encoding/Decoding RTCM SSR phase bias messages<br>
    4796 [Add] Encoding/Decoding RTCM SSR ionospheric model messages, single-layer model for total electron content<br>
    4797 [Add] RTCM SSR I messages for Galileo, BDS, SBAS and QZSS support from RTNET interface<br>
    4798 [Add] RTCM SSR II messages (phase biases and SSR ionospheric model) support from RTNET interface<br>
    4799 [Add] Computataion of VTEC and STEC from SSR ionospheric model messages for usage in PPP mode<br>
    4800 [Add] Handle old-fashioned SNR values in RINEX<br>
    4801 [Mod] SNR and MP visualization depending on RINEX observation attribute<br>
    4802 [Bug] Saastamoinen tropospheric correction for very high elevation receivers<br>
    4803 [Add] Comparison of SP3 files<br>
    4804 [Add] Encoding/Decoding of RTCM v3 proposal for Galileo Broadcast Ephemeris message 1046<br>
    4805 [Add] Encoding/Decoding of RTCM v3 QZSS Broadcast Ephemeris message 1044<br>
    4806 [Add] Encoding/Decoding of RTCM v3 SBAS Broadcast Ephemeris message 1043<br>
    4807 [Add] Encoding/Decoding of RTCM v3 BDS Broadcast Ephemeris message 63<br>
    4808 [Add] RINEX v3 support of Galileo, BDS, SBAS and QZSS Broadcast Ephemerides<br>
    4809 [Add] Consideration of the aspect that Galileo NAV message can be providet for the same epoch but with different flags (I/NAV, F/NAV, DVS)<br>
    4810 [Bug] VRS support in sending NMEA in Auto/Manual mode to Ntrip Broadcaster<br>
    4811 [Add] Forwarding NMEA GNGGA to Ntrip Broadcaster<br>
    4812 [Bug] Stream failure/recovery reports<br>
    4813 [Add] Compute IODs for BDS and SBAS from CRC over broadcast ephemeris and clock parameters<br>
    4814 [Mod] PPP default options<br>
    4815 [Add] Example configuration for SP3 file comparison<br>
    4816 [Add] Choose between code and phase observations when in PPP SSR I mode<br>
    4817 [Bug] Reset time series plot when restarting PPP in post processing mode<br>
    4818 [Add] Broadcast ephemeris check regarding allowed age of data sets<br>
    4819 [Add] Code bias usage for PPP SSR I mode<br>
    4820 [Add] Code bias, phase bias and VTEC usage in extended PPP mode<br>
    4821 [Mod] Consideration of the full antenna PCO vector in all PPP modes<br>
    4822 [Add] Allow GPS-only and GLONASS-only RINEX v2 Navigation files<br>
    4823 [Mod] SSR clock correction converted to seconds to be consistent with broadcast values<br>
    4824 [Add] Support Galileo I/NAV broadcast ephemeris<br>
    4825 [Add] Extended RINEX v3 filenames<br>
    4826 [Add] Stream's country added to configuration string 'mountPoints'<br>
    4827 [Add] destinction of GEO/MEO satellites during BDS velocity derermination <br>
    4828 [Bug] Velocity determination for geostationary BDS satellites<br>
    4829 [Add] Set TOE from BDS week and second<br>
    4830 [Add] Use BDS observations and ephemerides in PPP SSR I mode<br>
    4831 [Add] Considering that yaw angle restricted to -180 to +180 deg<br>
    4832 [Mod] Read local RINEX skeleton files<br>
    4833 [Add] Update interval for VTEC in RTNET stream format<br>
    4834 [Bug] SBAS IODN<br>
    4835 [Bug] Galileo week number<br>
    4836 [Add] Phase shift records in RINEX v3 headers<br>
    4837 [Add] Output GLONASS slot numbers from scanning stream content<br>
    4838 [Add] Decoder interface for PPP SSR I+II messages for Galileo/QZSS/SBAS/BDS<br>
    4839 [Mod] Renaming BDS first frequency from '1' to '2'<br>
    4840 [Add] RINEX QC, receiver/antenna information editable<br>
    4841 [Add] Support of new RINEX header lines regarding phase shifts, GLONAQSS slots and GLONASS biases during file merging<br>
    4842 [Add] Switch to port 443 for skeleton file download from https website<br>
    4843 [Mod] Default observation types for RINEX v3 files<br>
    4844 [Bug] RTCM v2 decoder<br>
    4845 [Add] SINEX Troposphere file output<br>
    4846 [Add] Comments with respect to RINEX v3 to RINEX v2 observation file conversion
    4847 [Add] String for Operating System in logfile output<br>
    4848 [Add] Full integration of 'rtcm3torinex'<br>
    4849 [Add] Extended command line help<br>
    4850 [Add] Version 2.12.0 published<br>
    4851 
    4852 </td>
    4853 </tr>
    4854 
    4855 </table>
    4856 </p>
    4857 
    4858 <p><h4>3.2 <a name="rtcm">RTCM Standards</h4></p>
     4662<p><h4>3.1 <a name="rtcm">RTCM Standards</h4></p>
    48594663
    48604664<p>
     
    48644668</p>
    48654669
    4866 <p><h4>3.2.1 <a name="ntrip1">Ntrip Version 1</h4></p>
     4670<p><h4>3.1.1 <a name="ntrip1">Ntrip Version 1</h4></p>
    48674671
    48684672<p>
     
    49034707</p>
    49044708
    4905 <p><h4>3.2.2 <a name="ntrip2">Ntrip Version 2</h4></p>
     4709<p><h4>3.1.2 <a name="ntrip2">Ntrip Version 2</h4></p>
    49064710
    49074711<p>
     
    49214725</p>
    49224726
    4923 <p><h4>3.2.3 <a name="rtcm2">RTCM Version 2</h4></p>
     4727<p><h4>3.1.3 <a name="rtcm2">RTCM Version 2</h4></p>
    49244728<p>
    49254729Transmitting GNSS carrier phase data can be done through RTCM Version 2 messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of interest here are:
     
    49594763</ul>
    49604764
    4961 <p><h4>3.2.4 <a name="rtcm3">RTCM Version 3</h4></p>
     4765<p><h4>3.1.4 <a name="rtcm3">RTCM Version 3</h4></p>
    49624766<p>
    49634767RTCM Version 3 has been developed as a more efficient alternative to RTCM Version 2. Service providers and vendors have asked for a standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the Version 2 parity scheme was wasteful of bandwidth. Another complaint was that the parity is not independent from word to word. Still another was that even with so many bits devoted to parity, the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. The Version 3 standard is intended to correct these weaknesses.
     
    51024906</p>
    51034907
    5104 <p><h4>3.3 <a name="confList">Command Line Help</h3></p>
     4908<p><h4>3.2 <a name="confList">Command Line Help</h3></p>
    51054909
    51064910<p>
     
    51334937   rnxPath        {Directory [character string]}
    51344938   rnxIntr        {File interval [character string: 1 min|2 min|5 min|10 min|15 min|30 min|1 hour|1 day]}
    5135    rnxSampl       {File sampling rate [integer number of seconds: 0,5|10|15|20|25|30|35|40|45|50|55|60]} 
     4939   rnxSampl       {File sampling rate [integer number of seconds: 0,5|10|15|20|25|30|35|40|45|50|55|60]}
    51364940   rnxSkel        {RINEX skeleton file extension [character string]}
    51374941   rnxOnlyWithSKL {Using RINEX skeleton file is mandatory [integer number: 0=no,2=yes]}
     
    52145018
    52155019<b>Outages Panel keys:</b>
    5216    adviseObsRate {Stream observation rate [character string: 0.1 Hz|0.2 Hz|0.5 Hz|1 Hz|5 Hz]} 
     5020   adviseObsRate {Stream observation rate [character string: 0.1 Hz|0.2 Hz|0.5 Hz|1 Hz|5 Hz]}
    52175021   adviseFail    {Failure threshold [integer number of minutes: 0-60]}
    52185022   adviseReco    {Recovery threshold [integer number of minutes: 0-60]}
     
    53255129
    53265130<b>Note:</b>
    5327 The syntax of some command line configuration options slightly differs from that 
     5131The syntax of some command line configuration options slightly differs from that
    53285132used in configuration files: Configuration file options which contain one or more
    53295133blank characters or contain a semicolon separated parameter list must be enclosed
     
    53355139(3) /home/weber/bin/bnc --conf /home/weber/MyConfigFile.bnc
    53365140(4) bnc --conf /Users/weber/.config/BKG/BNC.bnc -nw
    5337 (5) bnc --conf /dev/null --key startTab 4 --key reqcAction Edit/Concatenate --key reqcObsFile AGAR.15O --key reqcOutObsFile AGAR_X.15O 
     5141(5) bnc --conf /dev/null --key startTab 4 --key reqcAction Edit/Concatenate --key reqcObsFile AGAR.15O --key reqcOutObsFile AGAR_X.15O
    53385142        --key reqcRnxVersion 2 --key reqcSampling 30 --key reqcV2Priority CWPX_?
    53395143(6) bnc --key mountPoints "//user:pass@mgex.igs-ip.net:2101/CUT07 RTCM_3.0 ETH 9.03 38.74 no 2;
     
    53455149                            CUT07,100.0,100.0,100.0,100.0,100.0,100.0,0.1,3e-6,7778"
    53465150</pre>
    5347 <p><h4>3.4 <a name="links">Further Reading</h3></p>
     5151<p><h4>3.3 <a name="links">Further Reading</h3></p>
    53485152
    53495153<table>
     
    53985202</table>
    53995203
    5400 <p><h4>3.5 <a name="abbrev">Abbreviations</h3></p>
     5204<p><h4>3.4 <a name="abbrev">Abbreviations</h3></p>
    54015205<table>
    54025206
Note: See TracChangeset for help on using the changeset viewer.