Changeset 957 in ntrip


Ignore:
Timestamp:
Jul 20, 2008, 8:17:14 PM (16 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNS/bnshelp.html

    r954 r957  
    4444</p>
    4545<p>
    46 Note that running BNS requires the clock of the host computer to be properly synchronized.
     46Running BNS requires the clock of the host computer to be properly synchronized.
    4747</p>
    4848
    … …  
    51513.1. <a href=#file>File</a><br>
    52523.2. <a href=#help>Help</a><br>
    53 3.3. <a href=#basics>Basic Options</a><br>
    54 &nbsp; &nbsp; &nbsp; 3.3.1. <a href=#ephport>Ephemeris Input Port</a><br>
    55 &nbsp; &nbsp; &nbsp; 3.3.2. <a href=#ephlog>Ephemeris Logfile</a><br>
    56 &nbsp; &nbsp; &nbsp; 3.3.3. <a href=#clkport>Clocks Input Port</a><br>
    57 &nbsp; &nbsp; &nbsp; 3.3.4. <a href=#clklog>Clocks Logfile</a><br>
    58 3.4. <a href=#rinex>NTRIP Caster</a><br>
    59 &nbsp; &nbsp; &nbsp; 3.4.1. <a href=#rnxname>Host</a><br>
    60 &nbsp; &nbsp; &nbsp; 3.4.2. <a href=#rnxdir>Port</a><br>
    61 &nbsp; &nbsp; &nbsp; 3.4.3. <a href=#rnxinterval>Mountpoint</a><br>
    62 &nbsp; &nbsp; &nbsp; 3.4.4. <a href=#rnxsample>Password</a><br>
    63 3.5. <a href=#ephemeris>RINEX and SP3</a><br>
    64 &nbsp; &nbsp; &nbsp; 3.5.1. <a href=#clkdir>Clocks Directory</a><br>
    65 &nbsp; &nbsp; &nbsp; 3.5.2. <a href=#clkint>Clocks Interval</a><br>
    66 &nbsp; &nbsp; &nbsp; 3.5.3. <a href=#clksamp>Clocks Sampling</a><br>
    67 &nbsp; &nbsp; &nbsp; 3.5.4. <a href=#ephdir>Ephemeris Directory</a><br>
    68 &nbsp; &nbsp; &nbsp; 3.5.5. <a href=#ephint>Ephemeris Interval</a><br>
    69 &nbsp; &nbsp; &nbsp; 3.5.6. <a href=#ephsamp>Ephemeris Sampling</a><br>
    70 3.6. <a href=#start>Start</a><br>
    71 3.7. <a href=#stop>Stop</a><br>
    72 3.8. <a href=#stop>Help=Shift+F1</a><br>
    73 3.9. <a href=#nw>No Window</a>
     533.3. <a href=#proxy>Proxy</a><br>
     543.4. <a href=#general>General</a><br>
     55&nbsp; &nbsp; &nbsp; 3.4.1. <a href=#logfile>Logfile</a><br>
     56&nbsp; &nbsp; &nbsp; 3.4.2. <a href=#appfile>Append Files</a><br>
     573.5. <a href=#input>Input</a><br>
     58&nbsp; &nbsp; &nbsp; 3.5.1. <a href=#ephemeris>Ephemeris</a><br>
     59&nbsp; &nbsp; &nbsp; 3.5.2. <a href=#clocks>Clocks</a><br>
     603.6. <a href=#caster>NTRIP Caster</a><br>
     61&nbsp; &nbsp; &nbsp; 3.6.1. <a href=#cashost>Host</a><br>
     62&nbsp; &nbsp; &nbsp; 3.6.2. <a href=#casport>Port</a><br>
     63&nbsp; &nbsp; &nbsp; 3.6.3. <a href=#casproxy>Use Proxy</a><br>
     64&nbsp; &nbsp; &nbsp; 3.6.4. <a href=#casmount>Mountpoint</a><br>
     65&nbsp; &nbsp; &nbsp; 3.6.5. <a href=#caspass>Password</a><br>
     66&nbsp; &nbsp; &nbsp; 3.6.6. <a href=#casdata>Data</a><br>
     673.7. <a href=#clocks>RINEX Clocks</a><br>
     68&nbsp; &nbsp; &nbsp; 3.7.1. <a href=#clkdir>Directory</a><br>
     69&nbsp; &nbsp; &nbsp; 3.7.2. <a href=#clkint>Interval</a><br>
     70&nbsp; &nbsp; &nbsp; 3.7.3. <a href=#clksamp>Sampling</a><br>
     713.8. <a href=#orbits>SP3 Orbits</a><br>
     72&nbsp; &nbsp; &nbsp; 3.8.1. <a href=#orbdir>Directory</a><br>
     73&nbsp; &nbsp; &nbsp; 3.8.2. <a href=#orbint>Interval</a><br>
     74&nbsp; &nbsp; &nbsp; 3.8.3. <a href=#orbsamp>Sampling</a><br>
     753.9 <a href=#start>Start</a><br>
     763.10. <a href=#stop>Stop</a><br>
     773.11. <a href=#nw>No Window</a>
    7478</p>
    7579
    … …  
    114118
    115119<p>
    116 If you are running BNC within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNC. If you don't know the IP and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.</p>
    117 <p>
    118 Note that IP streaming is often not allowed in a LAN. In this case you need to ask your network administrator for an appropriate modification of the local security policy or for the installation of a TCP relay to the NTRIP broadcasters. If these are not possible, you might need to run BNC outside your LAN on a host that has unobstructed connection to the Internet.
    119 </p>
    120 <p><a name="general"><h4>3.4. General</h4></p>
    121 
    122 <p><a name="genlog"><h4>3.4.1 Logfile - optional</h4></p>
     120If you are running BNS within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNC. If you don't know the IP and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.</p>
     121<p>
     122Note that IP streaming is often not allowed in a LAN. In this case you need to ask your network administrator for an appropriate modification of the local security policy or for the installation of a TCP relay to the NTRIP broadcasters. If these are not possible, you might need to run BNS outside your LAN on a host that has unobstructed connection to the Internet.
     123</p>
     124<p><a name="general"><h4>3.4. General Options</h4></p>
     125
     126<p><a name="logfile"><h4>3.4.1 Logfile - optional</h4></p>
    123127<p>
    124128Records of BNC's activities are shown in the Log section on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Log (full path)' field. The message log covers the communication status between BNC and the NTRIP broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Log (full path)' is an empty option field, meaning that BNC logs will not saved into a file.
    125129</p>
    126130
    127 <p><a name="genapp"><h4>3.4.2 Append Files</h4></p>
    128 <p>
    129 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.
     131<p><a name="appfile"><h4>3.4.2 Append Files</h4></p>
     132<p>
     133When BNS 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 BNS, a system crash or when BNS 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 BNS.
    130134</p>
    131135
    132 <p><a name="rinex"><h4>3.5. RINEX - Observations</h4></p>
    133 <p>
    134 Observations will be converted to RINEX if they come in either RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. BNC's RINEX Observation files generally contain C1, C2, P1, P2, L1, L2, S1, and S2 observations. In case an observation is unavailable, its value is set to zero '0.000'. Note that the 'RINEX TYPE' field in the RINEX Observation file header is always set to 'M(MIXED)' even if the file does not contain any GLONASS or SABAS data.
     136<p><a name="input"><h4>3.5. Input</h4></p>
     137<p>
     138BNS needs GNSS clock and orbit corrections in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and Broadcast Ephemeris in RINEX Navigation file format.
     139</p>
     140
     141<p><a name="ephemeris"><h4>3.5.1 Ephemeris - mandatory</h4></p>
     142<p>
     143BNS reads GNSS Broadcast Ephemeris in RINEX Version3 Navigation file format from an IP address and port. This information can be provided in real-time by the 'BKG Ntrip Client' (BNC) program. Enter the respective servers IP address and port number. Make sure that this server is up and running before you start BNS. If a prosy server is operated between BNS and the server providing the Broadcast Ephemeris, you may need to use the proxy server settings you have specified. Tick 'Use proxy' to use it for stream upload.
     144</p>
     145
     146<p><a name="clocks"><h4>3.5.2 Clocks - mandatory</h4></p>
     147<p>
     148BNS reads GNSS clock and orbit corrections in a plain ASCII format from an IP address and port. These corrections can be provided by a real-time GNSS engine like RTNet. They are expected to refer to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. Enter the respective servers IP address and port number. Make sure that this server is up and running. If a prosy server is operated between BNS and the server providing the clock and orbit corrections, you may need to use the proxy server settings you have specified. Tick 'Use proxy' to use it for stream upload.
     149</p>
     150
     151<p><a name="caster"><h4>3.6. NTRIP Caster</h4></p>
     152<p>
     153BNS can upload the resulting stream of cock and orbit corrections (refering to Broadcast Ephemeris) to an Ntrip Broadcaster. For that EUREF and IGS operate NTRIP broadcasters at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u> which might be used for stream upload. The stream format follows RTCM Version 3 currently transmitting thentative message types 4056 and 4057.
    135154</p>
    136155
    137 <p><a name="rnxname"><h4>3.5.1 RINEX File Names</h4></p>
    138 <p>
    139 RINEX file names are derived by BNC from the first 4 characters of the corresponding mountpoint (4Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named</p>
    140 <p>
    141 FRAN{ddd}{h}.{yy}O<br>
    142 WETT{ddd}{h}.{yy}O
    143 </p>
    144 <p>
    145 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.
    146 </p>
    147 <p>
    148 If there are more than one stream with identical 4Char Station ID (same first 4 characters for their mountpoints), the mountpoint strings are split into two sub-strings and both become part of the RINEX file name. For example, when simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX Observation files are named as</p>
    149 <p>
    150 FRAN{ddd}{h}_KFURT.{yy}O<br>
    151 FRAN{ddd}{h}_CE.{yy}O.
    152 </p>
    153 <p>
    154 If several streams show exactly the same mountpoint name (example: BRUS0 from <u>www.euref-ip.net</u> and BRUS0 from <u>www.igs-ip.net</u>), BNC adds an integer number to the file name leading i.e. to hourly RINEX Observation files like</p>
    155 <p>
    156 BRUS{ddd}{h}_0.{yy}O<br>
    157 BRUS{ddd}{h}_1.{yy}O.
    158 </p>
    159 <p>
    160 Note that RINEX file names for all intervals less than 1 hour follow the file name convention for 15 minutes RINEX Observation files i.e.</p>
    161 <p>
    162 FRAN{ddd}{h}{mm}.{yy}O
    163 </p>
    164 <p>
    165 where 'mm' is the starting minute within the hour.
    166 </p>
    167 
    168 <p><a name="rnxdir"><h4>3.5.2 Directory - optional</h4></p>
    169 <p>
    170 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.
    171 </p>
    172 
    173 <p><a name="rnxinterval"><h4>3.5.3 File Interval - mandatory if 'Directory' is set</h4></p>
    174 <p>
    175 Select the length of the RINEX Observation file generated. The default value is 15 minutes.
    176 </p>
    177 
    178 <p><a name="rnxsample"><h4>3.5.4 Sampling - mandatory if 'Directory' is set </h4></p>
    179 <p>
    180 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.
    181 </p>
    182 
    183 <p><a name="rnxskl"><h4>3.5.5 Skeleton Extension - optional</h4></p>
    184 <p>
    185 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.
    186 </p>
    187 <p>
    188 However, sometimes public RINEX header skeleton files are not available, its contents is not up to date, or you need to put additional/optional records in the RINEX header. For that BNC allows using personal skeleton files that contain the header records you would like to include. You can derive a personal RINEX header skeleton file from the information given in an up to date sitelog. A file in the RINEX 'Directory' with a 'Skeleton extension' is interpreted by BNC as a personal RINEX header skeleton file for the corresponding stream.
    189 </p>
    190 <p>
    191 Examples for personal skeleton file name convention: RINEX Observation files for mountpoints WETTZELL, FRANKFURT and FRANCE (same 4Char Station ID), BRUS0 from <u>www.euref-ip.net</u> and BRUS0 from <u>www.igs-ip.net</u> (same 4Char Station ID, identical mountpoint stings) would accept personal skeleton files named</p>
    192 <p>
    193 WETT.skl<br>
    194 FRAN_KFURT.skl<br>
    195 FRAN_CE.skl<br>
    196 BRUS_0.skl<br>
    197 BRUS_1.skl</p>
    198 <p>
    199 if RINEX 'Skeleton extension' is set to 'skl'.
    200 </p>
    201 <p>
    202 Note the following regulations regarding personal RINEX header skeleton files:
    203 <ul>
    204 <li>If such a file exists in the 'RINEX directory', the corresponding public RINEX header skeleton file is ignored. The RINEX header is generated solely from the contents of the personal skeleton.</li>
    205 <li>Personal skeletons should contain a complete first header record of type</li>
    206 <br>- &nbsp; RINEX VERSION / TYPE
    207 <li>They should then contain an empty header record of type</li>
    208 <br>- &nbsp; PGM / RUN BY / DATE
    209 <br>BNC will complete this line and include it in the actual RINEX file header.
    210 <li>They should further contain complete header records of type</li>
    211 <br>- &nbsp; MARKER NAME
    212 <br>- &nbsp; OBSERVER / AGENCY
    213 <br>- &nbsp; REC # / TYPE / VERS
    214 <br>- &nbsp; ANT # / TYPE
    215 <br>- &nbsp; APPROX POSITION XYZ
    216 <br>- &nbsp; ANTENNA: DELTA H/E/N
    217 <br>- &nbsp; WAVELENGTH FACT L1/2
    218 <li>They may contain any other optional complete header record as defined in the RINEX documentation.</li>
    219 <li>They should then contain empty header records of type</li>
    220 <br>- &nbsp; # / TYPES OF OBSERV
    221 <br>- &nbsp; TIME OF FIRST OBS
    222 <br>BNC will include these lines in the final RINEX file header together with an additional
    223 <br>- &nbsp; COMMENT
    224 <br>line describing the source of the stream.
    225 <li>They should finally contain an empty header record of type</li>
    226 <br>- &nbsp; END OF HEADER (last record)
    227 </ul>
    228 <p>
    229 If neither a public nor a personal RINEX header skeleton file is available for BNC, a default header will be used.
    230 </p>
    231 
    232 <p><a name="rnxscript"><h4>3.5.6 Script - optional</h4></p>
    233 <p>
    234 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 systems).
    235 </p>
    236 <p>
    237 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.
    238 </p>
    239 <p>
    240 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 2 or 3 minutes after the end of each RINEX file 'Interval'.
    241 </p>
    242 
    243 <p><a name="rnxvers"><h4>3.5.7 Version - optional</h4></p>
    244 <p>
    245 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.
    246 </p>
    247 
    248 <p><a name="ephemeris"><h4>3.6. Ephemeris</h4></p>
    249 <p>
    250 Broadcast ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3.x as message types 1019 (GPS) and 1020 (GLONASS) or via RTIGS records type 300. The file name convention follows the details given in section 'RINEX File Names' except that the first four characters are 'BRDC' and the last character is
    251 </p>
    252 <ul>
    253 <li>'N' or 'G' for GPS or GLONASS ephemeris in two separate RINEX Version 2.11 Navigation files, or</li>
    254 <li>'P' for GPS plus GLONASS ephemeris saved together in one RINEX Version 3 Navigation file.
    255 </ul>
    256 
    257 <p><a name="ephdir"><h4>3.6.1 Directory - optional</h4></p>
    258 <p>
    259 Specify the 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.
    260 </p>
    261 
    262 <p><a name="ephint"><h4>3.6.2 Interval - mandatory if 'Directory' is set</h4></p>
    263 <p>
    264 Select the length of the RINEX Navigation file generated. The default value is 1 day.
    265 </p>
    266 
    267 <p><a name="ephport"><h4>3.6.3 Port - optional</h4></p>
    268 <p>
    269 BNC can output broadcast ephemeris in RINEX ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number to activate this function. The default is an empty option field, meaning that no ASCII ephemeris output via IP port is generated.
    270 </p>
    271 <p>
    272 The source code for BNC comes with an example perl script 'test_bnc_eph.pl' that allows you to read BNC's ASCII ephemeris output from the IP port.
    273 </p>
    274 
    275 <p><a name="ephvers"><h4>3.6.4 Version - optional</h4></p>
    276 <p>
    277 Default format for RINEX Navigation files containing broadcast ephemeris is RINEX Version 2.11. Select 'Version 3' if you want to save the ephemeris in RINEX Version 3 format.
    278 </p>
    279 
    280 <p><a name="syncout"><h4>3.7. Synchronized Observations</h4></p>
    281 <p>
    282 BNC can generate synchronized epoch by epoch observations from all stations and satellites. The output can be in either a plain ASCII format and/or a binary format. It comprises the following observations where available:</p>
    283 <p>
    284 StatID, SVPRN, GPSWeek, GPSWeeks, C1, C2, P1, P2, L1, L2, S1, S2, SNR1, SNR2
    285 </p>
    286 <p>
    287 Note that SNR stands for the signal-to-noise ratio 'S' mapped to integer numbers 1 to 9. In case an observation is not available, its value is set to zero '0.000'.
    288 </p>
    289 
    290 <p><a name="syncport"><h4>3.7.1 Port - optional</h4></p>
    291 <p>
    292 BNC can produce synchronized observations in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary output is generated.</p>
    293 <p>The binary output is a continuous stream in the following order:</p>
    294 <pre>
    295 begEpoch
    296 begObs
    297 Observation
    298 begObs
    299 Observation
    300 begObs
    301 Observation
    302 ...
    303 endEpoch
    304 begEpoch
    305 ...
    306 </pre>
    307 <p>with the corresponding structures defined as follow:</p>
    308 <pre>
    309 const char begEpoch = 'A';
    310 const char begObs   = 'B';
    311 const char endEpoch = 'C';
    312 struct Observation {
    313   int    flags;
    314   char   StatID[20+1];// Station ID
    315   char   satSys;      // Satellite System ('G' or 'R')
    316   int    satNum;      // Satellite Number (PRN for GPS NAVSTAR)
    317   int    slot;        // Slot Number (for Glonass)
    318   int    GPSWeek;     // Week of GPS-Time
    319   double GPSWeeks;    // Second of Week (GPS-Time)
    320   double C1;          // CA-code pseudorange (meters)
    321   double C2;          // CA-code pseudorange (meters)
    322   double P1;          // P1-code pseudorange (meters)
    323   double P2;          // P2-code pseudorange (meters)
    324   double L1;          // L1 carrier phase (cycles)
    325   double L2;          // L2 carrier phase (cycles)
    326   double S1;          // L1 signal-to noise ratio
    327   double S2;          // L2 signal-to noise ratio
    328   int    SNR1;        // L1 signal-to noise ratio (mapped to integer)
    329   int    SNR2;        // L2 signal-to noise ratio (mapped to integer)
    330 } ;
    331 </pre>
    332 <p>
    333 The source code for BNC comes with an example program called 'test_bnc_qt.cpp' that allows you to read BNC's binary observation output from the IP port (hard-coded to 1968) and save the observations in file 'obs.txt'.
    334 </p>
    335 <p>
    336 Note that any socket connection of an application to BNC's Synchronized Observations Port is recorded in the Log section on the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'.
    337 </p>
    338 
    339 <p><a name="syncwait"><h4>3.7.2 Wait for Full Epoch - mandatory if 'Port' is set</h4></p>
    340 <p>
    341 When feeding a real-time GNSS engine waiting for input epoch by epoch, BNC drops whatever is received later than 'Wait for full epoch' seconds. A value of 3 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming streams and the delay acceptable for your real-time GNSS product. Default value for 'Wait for full epoch' is 5 seconds.
    342 </p>
    343 <p>
    344 Note that 'Wait for full epoch' does not effect the RINEX Observation file content. Observations received later than 'Wait for full epoch' seconds will still be included in the RINEX Observation files.
    345 </p>
    346 
    347 <p><a name="syncfile"><h4>3.7.3 File - optional</h4></p>
    348 <p>
    349 Specifies the full path to a 'File' where synchronized observations are saved in plain ASCII format. The default value is an empty option field, meaning that no ASCII output file is created.
    350 </p>
    351 <p>
    352 Beware that the size of this file can rapidly increase depending on the number of incoming streams. This option is primarily meant for testing and evaluation.
    353 </p>
    354 
    355 <p><a name="syncsample"><h4>3.7.4 Sampling - mandatory if 'File' or 'Port' is set</h4></p>
    356 <p>
    357 Select the observation output sampling interval in seconds. A value of zero '0' tells BNC to send/store all received epochs. This is the default value.
    358 <p>
    359 
    360 <p><a name="correct"><h4>3.8. Ephemeris Corrections</h4></p>
    361 <p>
    362 </p>
    363 RTCM is in the process of developing new Version 3 messages to transport satellite clock and orbit corrections in real-time. Based on the latest available proposal, the following tentative messages currently under discussion have been implemented in BNC:
    364 <ul>
    365 <li>Message type 4050: GPS orbit corrections to Broadcast Ephemeris</li>
    366 <li>Message type 4051: GPS clock corrections to Broadcast Ephemeris</li>
    367 <li>Message type 4052: GPS code biases</li>
    368 <li>Message type 4053: GLONASS orbit corrections to Broadcast Ephemeris</li>
    369 <li>Message type 4054: GLONASS clock corrections to Broadcast Ephemeris</li>
    370 <li>Message type 4055: GLONASS code biases</li>
    371 <li>Message type 4056: Combined GPS and GLONASS orbit corrections to Broadcast Ephemeris</li>
    372 <li>Message type 4057: Combined GPS and GLONASS clock corrections to Broadcast Ephemeris</li>
    373 </ul>
    374 <p>
    375 RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications.
    376 </p>
    377 
    378 <p><a name="corrdir"><h4>3.8.1 Directory - optional</h4></p>
    379 <p>
    380 Specify a directory for saving Ephemeris Corrections in files. If the specified directory does not exist, BNC will not create Ephemeris Correction files. Default value for Ephemeris Corrections 'Directory' is an empty option field, meaning that no Ephemeris Correction files will be created.
    381 </p>
    382 <p>
    383 The file name convention for Ephemeris Correction files follows the convention for RINEX files except for the last character of the file name suffix which is set to "C".
    384 </p>
    385 
    386 <p><a name="corrint"><h4>3.8.2 Interval - mandatory if 'Directory' is set</h4></p>
    387 <p>
    388 Select the length of the Ephemeris Correction files. The default value is 1 day.
    389 </p>
    390 
    391 <p><a name="corrport"><h4>3.8.3 Port - optional</h4></p>
    392 <p>
    393 BNC can output Ephemeris Corrections in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number to activate this function. The default is an empty option field, meaning that no Ephemeris Correction output via IP port is generated.
    394 </p>
    395 <p>
    396 The source code for BNC comes with an example perl script 'test_bnc_eph.pl' that allows you to read BNC's Ephemeris Corrections from the IP port. In case of a stream carrying message types 4056 and 4057, the script produces ASCII records containing the following set of parameters:
     156<p><a name="cashost"><h4>3.6.1 Host - optional</h4></p>
     157Enter the NTRIP broadcaster 'Host' IP name or number for stream upload.
     158</p>
     159
     160<p><a name="casport"><h4>3.6.2 Port - mandatory if 'Host' is set</h4></p>
     161<p>
     162Enter the NTRIP broadcaster IP 'Port' number for stream upload. Note that NTRIP Broadcaster installations often provide access through more than one port, usually ports 80 and 2101. In case you experience communication problems on port 80, you may like to use the alternative port(s).
     163</p>
     164
     165<p><a name="casproxy"><h4>3.6.3 Use Proxy - optional if 'Host' and 'Proxy' is set</h4></p>
     166<p>
     167In case BNS is operated in a protected LAN, you may need to use the proxy server protecting your network. Once you have specified your proxies host and port, you can tick 'Use proxy' to use it for stream upload.
     168</p>
     169
     170<p><a name="casmount"><h4>3.6.4 Mountpoint - mandatory if 'Host' is set</h4></p>
     171<p>
     172Each stream on an NTRIP broadcaster is defined using a unique source ID called mountpoint. An NTRIP server like BNS can upload its stream to the broadcaster by referring to a specific mountpoint established by the broadcaster operator. Specify the mountpoint you receive from the operator for your stream. Note that it usually is a four character ID (capital letters) plus an integer number.
     173</p>
     174
     175<p><a name="caspass"><h4>3.6.5 Password - mandatory if 'Host' is set</h4></p>
     176<p>
     177In NTRIP Version 1.0 stream upload ist protected through a generic upload 'Password'. Enter the password you received from the broadcaster operator along with the mounpoint.
     178</p>
     179
     180<p><a name="casdata"><h4>3.6.6 Data - optional</h4></p>
     181<p>
     182The clock and orbit corrections streamed by BNS to an NTRIP broadcaster can recorded. Specify the full 'Data' path here to save this information in a local file. Default value for 'Data' path is an empty option field, meaning that the upload stream contents will not be saved locally.
    397183</p>
    398184<p>
    … …  
    410196</p>
    411197<p>
    412 The output is synchronized epoch by epoch with a leading "A" indicating the begin and a trailing "C" indicating the end of an epoch. The following is an example output from two RTCM Version 3 streams (CLCK1 and CLCK4) containing message types 4056 and 4057:
    413198<pre>
    414 A
    415 CLCK1 1487 547554.0 G27    57     12.219      1.241    0.495    0.002
    416 CLCK1 1487 547554.0 G29   101     -0.086      0.008   -0.429    0.675
    417 CLCK1 1487 461154.0 R06    18      5.192      2.390   -1.915   -6.734
    418 CLCK1 1487 461154.0 R07    18     -1.619      2.827    0.901    0.280
    419 CLCK4 1487 547554.0 G27    57     12.218      1.242    0.496    0.003
    420 CLCK4 1487 547554.0 G29   101     -0.087      0.007   -0.427    0.673
    421 CLCK4 1487 461154.0 R06    18      5.191      2.389   -1.914   -6.735
    422 CLCK4 1487 461154.0 R07    18     -1.618      2.826    0.900    0.281
    423 C
    424 A
    425 CLCK1 1487 547555.0 G27    57     12.216      1.241    0.494    0.003
    426 CLCK1 1487 547555.0 G29   101     -0.084      0.009   -0.428    0.675
    427 ...
    428 ...
     1991487 547554.0 G27    57     12.219      1.241    0.495    0.002
     2001487 547554.0 G29   101     -0.086      0.008   -0.429    0.675
     2011487 461154.0 R06    18      5.192      2.390   -1.915   -6.734
     2021487 461154.0 R07    18     -1.619      2.827    0.901    0.280
     2031487 547554.0 G27    57     12.218      1.242    0.496    0.003
     2041487 547554.0 G29   101     -0.087      0.007   -0.427    0.673
     2051487 461154.0 R06    18      5.191      2.389   -1.914   -6.735
     2061487 461154.0 R07    18     -1.618      2.826    0.900    0.281
    429207</pre>
    430208</p>
    431209
    432 <p><a name="corrwait"><h4>3.8.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p>
    433 <p>
    434 When feeding a real-time GNSS engine waiting for Ephemeris Corrections, BNC drops whatever is received later than 'Wait for full epoch' seconds. A value of 2 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming Ephemeris Corrections stream and the delay acceptable by your application. Default value for 'Wait for full epoch' is 5 seconds.
    435 </p>
    436 
    437 <p><a name="advnote"><h4>3.9. Monitor</h4></p>
    438 
    439 <p>
    440 At various times, the incoming stream might become unavailable or corrupted. In such cases, it is important that the BNC operator and/or the stream providers become aware of the situation so that necessary measures can be taken to restore the stream. Furthermore, continuous attempts to decode corrupted stream(s) can generate unnecessary workload for BNC. Outages and corruptions are handled by BNC as follows:
    441 </p>
    442 <p>
    443 <u>Stream outages:</u> BNC considers a connection to be broken when there are no incoming data detected for more than 20 seconds. When this occurs, BNC will attempt to reconnect at a decreasing rate. It will first try to reconnect with 1 second delay, and again in 2 seconds if the previous attempt failed. If the attempt is still unsuccessful, it will try to reconnect within 4 seconds after the previous attempt and so on. The wait time doubles each time with a maximum wait time of 256 seconds.
    444 </p>
    445 <p>
    446 <u>Stream corruption:</u> Not all bits chunk transfers to BNC's internal decoders return valid observations. Sometimes several chunks might be needed before the next observation can be properly decoded. BNC buffers all the outputs (both valid and invalid) from the decoder for a short time span (size derived from the expected 'Observation rate') and then determines whether a stream is valid or corrupted.
    447 </p>
    448 <p>
    449 Outage and corruption events are reported in the Log file/section. They can also be passed on as parameters to a shell script or batch file to generate an advisory note to BNC operator or affected stream providers. This functionality lets users utilise BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations.
    450 </p>
    451 
    452 <p><a name="obsrate"><h4>3.9.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', 'Pause' and 'Advisory Script' is set</h4></p>
    453 <p>
    454 BNC can collect all returns (success or failure) coming from a decoder within a certain short time span to then decide whether a stream has an outage or its content is corrupted. This procedure needs a rough a priory estimate of the expected observation rate of the incoming streams.</p><p>An empty option field (default) means that you don't want an explicit information from BNC about stream outages and incoming streams that can not be decoded and that the special procedure for handling of corrupted streams is by-passed (decoding attempt will never get paused).
     210<p><a name="rinex"><h4>3.7. RINEX Clocks</h4></p>
     211<p>
     212The clock corrections generated by BNS can be saved in Clock RINEX files. The file names follow the RINEX convention.
     213</p>
     214
     215<p><a name="clkdir"><h4>3.7.1 Directory - optional</h4></p>
     216<p>
     217Here you can specify the path to where the Clock RINEX files will be stored. If the specified directory does not exist, BNC will not create Clock RINEX files. Default value for 'Directory' is an empty option field, meaning that no Clock RINEX files will be written.
     218</p>
     219
     220<p><a name="clkint"><h4>3.7.2 Interval - mandatory if 'Directory' is set</h4></p>
     221<p>
     222Select the length of the Clock RINEX file generated. The default value is 1 day.
     223</p>
     224
     225<p><a name="clksamp"><h4>3.7.3 Sampling - mandatory if 'Directory' is set</h4></p>
     226<p>
     227Select the Clock RINEX sampling interval in seconds. A value of zero '0' tells BNS to store all received epochs into Clock RINEX. This is the default value.
     228</p>
     229
     230<p><a name="orbits"><h4>3.8. SP3 Orbits</h4></p>
     231<p>
     232The orbit corrections generated by BNS can be saved in SP3 orbit files. The file names follow the RINEX convention.
     233</p>
     234
     235<p><a name="orbdir"><h4>3.8.1 Directory - optional</h4></p>
     236<p>
     237Here you can specify the path to where the SP3 orbit files will be stored. If the specified directory does not exist, BNC will not create SP3 orbit files. Default value for 'Directory' is an empty option field, meaning that no SP3 orbit files will be written.
     238</p>
     239
     240<p><a name="orbint"><h4>3.8.2 Interval - mandatory if 'Directory' is set</h4></p>
     241<p>
     242Select the length of the SP3 orbit file generated. The default value is 1 day.
     243</p>
     244
     245<p><a name="orbsamp"><h4>3.8.3 Sampling - mandatory if 'Directory' is set</h4></p>
     246<p>
     247Select the SP3 orbit file sampling interval in seconds. A value of zero '0' tells BNS to store all received epochs into SP3 orbit files. This is the default value.
     248</p>
     249
     250<p><a name="start"><h4>3.9. Start</h4></p>
     251<p>
     252Hit 'Start' to start receiving IGS corbit and clock corrections and convert them into corrections to Broadcast Ephemeris. Note that 'Start' generally forces BNS to begin with fresh files which might overwrite existing files when necessary unless the option 'Append files' is ticked.
    455253</p>
    456254
    457 <p><a name="advfail"><h4>3.9.2 Failure Threshold - optional</h4></p>
    458 <p>
    459 Event 'Begin_Failure' will be reported if no data is received continuously for longer than the 'Failure threshold' time. Similarly, event 'Begin_Corrupted' will be reported when corrupted data is detected by the decoder continuously for longer than this 'Failure threshold' time. The default value is set to 15 minutes and is recommended so not to innundate user with too many event reports.
    460 </p>
    461 <p>
    462 Note that specifying a value of zero '0' for the 'Failure threshold' will force BNC to report any stream failure immediately. Note also that for using this function you need to specify the 'Observation rate'.
    463 </p>
    464 
    465 <p><a name="advreco"><h4>3.9.3 Recovery Threshold - optional</h4></p>
    466 <p>
    467 Once a 'Begin_Failure' or 'Begin_Corrupted' event has been reported, BNC will check for when the stream again becomes available or uncorrupted. Event 'End_Failure' or 'End_Corrupted' will be reported as soon as valid observations are again detected continuously throughout the 'Recovery threshold' time span. The default value is set to 5 minutes and is recommended so not to innundate users with too many event reports. 
    468 </p>
    469 <p>
    470 Note that specifying a value of zero '0' for the 'Recovery threshold' will force BNC to report any stream recovery immediately. Note also that for using this function you need to specify the 'Observation rate'.
    471 </p>
    472 
    473 <p><a name="pause"><h4>3.9.4 Pause - optional</h4></p>
    474 <p>
    475 In case of a corrupted stream, the decoding process can be paused and decodings are then attempted again at decreasing rate. BNC will first attempt to decode again after a 30 second lag and if unsuccessful, make another attempt within 60 seconds after the previous attempt. If it is still unsuccessful, it will make another attempt to decode within 120 seconds after the previous attempt and so on. Each decoding attempt doubles the wait time since the previous attempt. The maximum wait time between attempts is limited to 960 seconds. Tick 'Pause' to activate this function. Note that it is only effective if an 'Observation rate' is specified.
    476 </p>
    477 <p>
    478 Do not tick 'Pause' if you want to prevent BNC from making any decoding pause. Be aware that this may incur an unnecessary workload.
    479 </p>
    480 
    481 <p><a name="advscript"><h4>3.9.5 Advisory Script - optional </h4></p>
    482 <p>
    483 As mentioned previously, BNC can trigger a shell script or a batch file to be executed when one of the events described are reported. This script can be used to email an advisory note to network operator or stream providers. To enable this feature, specify the full path to the script or batch file in the 'Script' field. The affected mountpoint and type of event reported ('Begin_Outage', 'End_Outage', 'Begin_Corrupted' or 'End_Corrupted') will then be passed on to the script as command line parameters (%1 and %2 on Windows systems or $1 and $2 on Unix/Linux systems) together with date and time information.
    484 </p>
    485 <p>
    486 Leave the 'Script' field empty if you do not wish to use this option. An invalid path will also disable this option.
     255<p><a name="stop"><h4>3.10. Stop</h4></p>
     256<p>
     257Hit the 'Stop' button in order to stop BNS.
    487258</p>
    488 <p>
    489 Examples for command line parameter strings passed on to the advisory 'Script' are:
    490 <pre>
    491 FFMJ0 Begin_Outage 08-02-21 09:25:59
    492 FFMJ0 End_Outage 08-02-21 11:36:02 Begin was 08-02-21 09:25:59
    493 </pre>
    494 Sample script for Unix/Linux systems:
    495 <pre>
    496 #!/bin/bash
    497 sleep $((60*RANDOM/32767))
    498 cat | mail -s "NABU: $1" email@address &lt;&lt;!
    499 Advisory Note to BNC User,
    500 Please note the following advisory received from BNC.
    501 Stream: $*
    502 Regards, BNC
    503 !
    504 </pre>
    505 </p>
    506 <p>
    507 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 avoids overloading your mail server in case of a simultaneous failure of many streams.
    508 </p>
    509 
    510 <p><a name="perflog"><h4>3.9.6 Performance Log - optional </h4></p>
    511 <p>
    512 <u>Latency:</u> Latency is defined in BNC by the following equation:
    513 </p>
    514 <pre>
    515     UTC time provided by BNC's host
    516   - GPS time of currently processed epoch
    517   + Leap seconds between UTC and GPS time, hard-coded to 14
    518   --------------
    519   = Latency
    520 </pre>
    521 <p>
    522  BNC can average the latencies per stream over a certain period of GPS time, the 'Performance log' interval. Mean latencies are calculated from the individual latencies of at most one (first incoming) observation per second. Note that computing correct latencies requires the clock of the host computer to be properly synchronized.
    523 </p>
    524 <p>
    525 <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 'Performance log' interval. Based on this rate, BNC estimates the number of data gaps when appearing in subsequent intervals.
    526 </p>
    527 <p>
    528 Latencies and statistical information can be recorded in the Log file/section at the end of each 'Performance log' interval. A typical output from a 1 hour 'Performance log' interval would be:
    529 </p>
    530 <pre>
    531 08-03-17 15:59:47 BRUS0: Mean latency 1.47 sec, min 0.66, max 3.02, 3585 epochs, 15 gaps
    532 </pre>
    533 <p>
    534 Select a 'Performance log' interval to activate this function or select the empty option field if you do not want BNC to log latencies and statistical information.
    535 </p>
    536 
    537 <p><a name="mountpoints"><h4>3.10. Mountpoints</h4></p>
    538 <p>
    539 Each stream on an NTRIP broadcaster is defined using a unique source ID called mountpoint. An NTRIP client like BNC access the desired data stream by referring to its mountpoint. Information about mountpoints is available through the source-table maintained by the NTRIP broadcaster. Note that mountpoints could show up in BNC more than once when retrieving streams from several NTRIP broadcasters.
    540 </p>
    541 
    542 Streams selected for retrieval are listed under the 'Mountpoints' section on BNC's main window. The list provides the following information extracted from source-table(s) produced by the NTRIP broadcasters:
    543  
    544 <table>
    545 <tr></tr>
    546 <tr><td>'mountpoint' &nbsp;</td><td>NTRIP broadcaster URL, port, and mountpoint.</td></tr>
    547 <tr><td>'decoder' &nbsp;</td><td>Type of decoder used to handle the incoming stream content according to its format; editable.</td></tr>
    548 <tr><td>'lat' &nbsp;</td><td>Approximate latitude of reference station, in degrees, north; editable if 'nmea' = 'yes'.</td></tr>
    549 <tr><td>'long' &nbsp;</td><td>Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'.</td></tr>
    550 <tr><td>'nmea' &nbsp;</td><td>Indicates whether or not streaming needs to be initiated by BNC through sending NMEA-GGA message carrying position coordinates in 'lat' and 'long'.</td></tr>
    551 <tr><td>'bytes' &nbsp;</td><td>Number of bytes retrieved.
    552 </table>
    553 
    554 <p><a name="mountadd"><h4>3.10.1 Add Mountpoints</h4></p>
    555 <p>
    556 Button 'Add Mountpoints' opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints.
    557 </p>
    558 
    559 <p><a name="mounthost"><h4>3.10.2 Broadcaster Host and Port - required</h4></p>
    560 <p>
    561 Enter the NTRIP broadcaster host IP and port number. <u>http://www.rtcm-ntrip.org/home</u> provides information about known NTRIP broadcaster installations. Note that EUREF and IGS operate NTRIP broadcasters at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u>.
    562 </p>
    563 
    564 <p><a name="mountuser"><h4>3.10.3 Broadcaster User and Password - required for protected streams</h4></p>
    565 <p>
    566 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/index_ntrip_reg.htm</u> for access to protected streams on <u>www.euref-ip.net</u> and <u>www.igs-ip.net</u>.
    567 </p>
    568 
    569 <p><a name="mounttable"><h4>3.10.4 Get Table</h4></p>
    570 <p>
    571 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.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see 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.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary.
    572 </p>
    573 <p>
    574 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 position coordinates (virtual reference station).
    575 </p>
    576 <p>
    577 Hit 'OK' to return to the main window. If you wish you can click on 'Add Mountpoints' and repeat the process again to retrieve mountpoints from different casters.
    578 </p>
    579 
    580 <p><a name="mountdelete"><h4>3.10.5 Delete Mountpoints</h4></p>
    581 <p>
    582 To remove a stream from the 'Mountpoints' list in the main window, highlight it by clicking on it and hit the 'Delete Mountpoints' button. You can also remove multiple mountpoints simultaneously by highlighting them using +Shift and +Ctrl.</p>
    583 
    584 <p><a name="mountedit"><h4>3.10.6 Edit Mountpoints</h4></p>
    585 <ul>
    586 <li>
    587 BNC automatically allocates one of its internal decoders to a stream based on the stream's 'format' and 'format-details' as given in the source-table. However, there might be cases where you need to override the automatic selection due to incorrect source-table for example. BNC allows users to manually select the required decoder by editing the decoder string. Double click on the 'decoder' field, enter your preferred decoder and then hit Enter. The accepted decoder strings are 'RTCM_2.x', 'RTCM_3.x', and 'RTIGS'.
    588 </li>
    589 <li>
    590 In case you need to log the raw data as is, BNC allows users to by-pass its decoders and and directly save the input in daily log files. To do this specify the decoder string as 'ZERO'. The generated file names are created from the characters of the mountpoints plus two-digit numbers each for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and running BNC on March 29, 2007 would save the raw data in a file named WTZZ0_070329.
    591 </li>
    592 <li>
    593 BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA format to the NTRIP broadcaster. In return, a user-specific data stream is generated, typically by a Network-RTK software. This stream is customized to the exact latitude and longitude as shown in the 'lat' and 'long' columns under 'Mountpoints'. These VRS streams are indicated by a 'yes' in the 'nmea' column under 'Mountpoints' as well as in the source-table.
    594 <br>The default 'lat' and 'long' values are taken from the source-table however in most cases you would probably want to change this according to your requirement. Double-click on 'lat' and 'long' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only mountpoints with a 'yes' in its 'nmea' column can be edited. The position must preferably be a point within the service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'long' used.
    595 <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.
    596 </li>
    597 </ul>
    598 
    599 <p><a name="start"><h4>3.11. Start</h4></p>
    600 <p>
    601 Hit 'Start' to start retrieving, decoding, and 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.
    602 </p>
    603 
    604 <p><a name="stop"><h4>3.12. Stop</h4></p>
    605 <p>
    606 Hit the 'Stop' button in order to stop BNC.
    607 </p>
    608 
    609 <p><a name="nw"><h4>3.13. No Window - optional</h4></p>
    610 <p>
    611 On all systems BNC can be started in batch mode with the command line option '-nw'. BNC will then run in 'no window' mode, using options from the configuration file ${HOME}/.config/BKG/BNC_NTRIP_Client.conf (Unix/Linux, see Config File example in the Annex) or from the register BKG_NTRIP_Client (Windows).
    612 </p>
    613 <p>
    614 Note that the self-explaining contents of the configuration file or the Windows register can easily be edited. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems.
     259
     260<p><a name="nw"><h4>3.11. No Window - optional</h4></p>
     261<p>
     262On all systems BNS can be started in batch mode with the command line option '-nw'. BNS will then run in 'no window' mode, using options from the configuration file ${HOME}/.config/BKG/BNC_NTRIP_Server.conf (Unix/Linux, see Config File example in the Annex) or from the register BKG_NTRIP_Server (Windows).
     263</p>
     264<p>
     265Note that the self-explaining contents of the configuration file or the Windows register can easily be edited. Terminate BNS using Windows Task Manager when running it in 'no window' mode on Windows systems.
    615266</p>
    616267<p><a name="limits"><h3>4. Limitations</h3></p>
    617268<ul>
    618269<li>
    619 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.
     270In Qt-based desktop environments (like KDE) on Unix/Linux platforms it may happen that you experience a crash of BNS 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 BNS. Entering the command 'unset SESSION_MANAGER' before running BNS may help as a work-around.
    620271</li>
    621272<li>
    622 Currently BNC only handles GPS, SBAS and GLONASS data. Galileo is not yet supported.
     273Currently BNS will only generate the tentative RTCM Version 3.x message types 4056 and 4057.
    623274</li>
    624275<li>
    625 BNC currently will only handle C1, C2, P1, P2, L1, L2, S1, and S2 observations. Which observables are available on a particular stream will depend on the setup of source receiver and the data format used. RTCM Version 2.x streams do not carry signal-to-noise ratio 'S' values while RTCM Version 3.x streams can only transport one code observable per frequency. Note that signal-to-noise ratios 'S' are also logged mapped to integer numbers 1 to 9.
     276We experienced a limitation of the Standard Version of Microsoft Windows related to socket communication where sockets are not always handled properly. Since BNS makes intensive use of communication through sockets, we recommend to use the Server Version of Microsoft Windows when running BNS continuously for extended on a Windows platform.
    626277</li>
    627278<li>
    628 Using RTCM Version 2.x, BNC will only handle message types 18 and 19. Using RTCM Version 3.x, BNC will properly handle message types 1002, 1004, 1010, and 1012. Note that when handling message types 1001, 1003, 1009 and 1011 where the ambiguity field is not set, the output will be no valid RINEX. All values will be stored modulo 299792.458 (speed of light).
    629 </li>
    630 <li>
    631 Streams coming in RTIGS format carry only GPS data.
    632 </li>
    633 <li>
    634 BNC's 'Get Table' function only shows the STR records of a source-table. You can use an Internet browser to download the full source-table contents of any NTRIP broadcaster by simply entering its URL in the form of http://host:port. Data field number 8 in the NET records may provide information about where to register for an NTRIP broadcaster account.
    635 </li>
    636 <li>
    637 EUREF as well as IGS adhere to an open data policy. Streams are made available through NTRIP broadcasters at <u>www.euref-ip.net</u> and <u>www.igs-ip.net</u> free of charge to anyone for any purpose. There is no indication up until now how many users will need to be supported simultaneously. The given situation may develop in such a way that it might become difficult to serve all registered users at the same times. In cases where limited resources on the NTRIP broadcaster side (software restrictions, bandwidth limitation etc.) dictates, first priority in stream provision will be given to stream providers followed by re-broadcasting activities and real-time analysis centers while access to others might be temporarily denied.
    638 </li>
    639 <li>
    640 We experienced a limitation of the Standard Version of Microsoft Windows related to socket communication where sockets are not always handled properly. Since BNC makes intensive use of communication through sockets, we recommend to use the Server Version of Microsoft Windows when running BNC continuously for extended on a Windows platform.
    641 </li>
    642 <li>
    643 The source code provided by NRCan for decoding RTIGS streams is 32-bit dependent. Hence the BNC executable generated for 64-bit Linux systems would only run when compiled using the -m32 compiler option.
    644 </li>
    645 <li>
    646 Once BNC has been started, its configuration can not be changed as long as it is stopped. A reconfiguration on-the-fly is not implemented.
     279Once BNS has been started, its configuration can not be changed as long as it is stopped. A reconfiguration on-the-fly is not implemented.
    647280</li>
    648281<br>
    … …  
    650283<p><a name="authors"><h3>5. Authors</h3></p>
    651284<p>
    652 The BKG Ntrip Client (BNC) Qt Graphic User Interface (GUI) has been developed for the Federal Agency for Cartography and Geodesy (BKG) by Leos Mervart, Czech Technical University Prague, Department of Geodesy. BNC includes the following GNU GPL software components:
    653 <ul>
    654 <li> RTCM 2.x decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen</li>
    655 <li> RTCM 3.x decoder, written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld</li>
    656 <li> RTIGS decoder, written by Ken MacLeod, Natural Resources, Canada.</li>
    657 </ul>
    658 </p>
    659 <p>
    660 Please ensure that you have installed the latest version of BNC available from <u>http://igs.bkg.bund.de/index_ntrip_down.htm</u>. We are continuously working on the program and would appreciate if you could send any comments, suggestions, or bug reports to:
     285The BKG Ntrip Server (BNS) Qt Graphic User Interface (GUI) has been developed for the Federal Agency for Cartography and Geodesy (BKG) by Leos Mervart, Czech Technical University Prague, Department of Geodesy. BNS includes a GNU GPL open source RTCM 3.x encoder, written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld.
     286</p>
     287<p>
     288Please ensure that you have installed the latest version of BNS available from <u>http://igs.bkg.bund.de/index_ntrip_down.htm</u>. We are continuously working on the program and would appreciate if you could send any comments, suggestions, or bug reports to:
    661289</p>
    662290<p>
    … …  
    666294euref-ip@bkg.bund.de or igs-ip@bkg.bund.de
    667295</p>
    668 <p>
    669 <b>Acknowledgements</b><br>
    670 BNC's Help Contents has been proofread by Thomas Yan, University of New South Wales, Australia.<br>
    671 Scott Glazier, OmniSTAR Australia, included the decoding of broadcast ephemeris from RTIGS streams and has been helpful in finding BNC's bugs.<br>
    672 James Perlt, BKG, helped fixing bugs and redesigned BNC's main window.<br>
    673 Andre Hauschild, German Space Operations Center, DLR, revised the RTCMv2 decoder.
    674 </p>
    675 
    676 <p><a name="annex"><h3>8. Annex</h3></p>
    677 <p>
    678 8.1. <a href=#history>History</a><br>
    679 8.2. <a href=#ntrip>NTRIP</a><br>
    680 &nbsp; &nbsp; &nbsp; 8.2.1 <a href=#source>Source-table</a><br>
    681 8.3. <a href=#rtcm>RTCM</a><br>
    682 &nbsp; &nbsp; &nbsp; 8.3.1 RTCM <a href=#rtcm2> Version 2.x</a><br>
    683 &nbsp; &nbsp; &nbsp; 8.3.2 RTCM <a href=#rtcm3> Version 3.x</a><br>
    684 8.4. <a href=#rtigs>RTIGS</a><br>
    685 &nbsp; &nbsp; &nbsp; 8.4.1 <a href=#soc>SOC</a><br>
    686 8.5. <a href=#config>Config File</a><br>
    687 8.6. <a href=#links>Links</a><br>
    688 </p>
    689 
    690 <p><a name=history><h3>8.1 History</h3></p>
     296
     297<p><a name="annex"><h3>6. Annex</h3></p>
     298<p>
     2996.1. <a href=#history>History</a><br>
     3006.2. <a href=#ntrip>NTRIP</a><br>
     3016.3. <a href=#rtcm>RTCM</a><br>
     302&nbsp; &nbsp; &nbsp; 6.3.1 RTCM <a href=#rtcm3> Version 3.x</a><br>
     3036.4. <a href=#config>Config File</a><br>
     3046.5. <a href=#links>Links</a><br>
     305</p>
     306
     307<p><a name=history><h3>6.1 History</h3></p>
    691308<table>
    692309<tr></tr>
    693 <tr><td>Dec 2006 &nbsp;</td><td>Version 1.0b &nbsp;</td><td>[Add] First Beta Binaries published based on Qt 4.2.3.</td></tr>
    694 <tr><td>Jan 2007 &nbsp;</td><td>Version 1.1b &nbsp;</td><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></tr>
    695 <tr><td>Apr 2007 &nbsp;</td><td>Version 1.2b &nbsp;</td><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></tr>
    696 <tr><td>May 2007 &nbsp;</td><td>Version 1.3 &nbsp;</td><td>[Add] Source code published.
    697 <tr><td>Jul 2007 &nbsp;</td><td>Version 1.4 &nbsp;</td><td>[Bug] Skip messages from proxy server<br> [Bug] Call RINEX script through 'nohup'</td></tr>
    698 <tr><td>Apr 2008 &nbsp;</td><td>Version 1.5 &nbsp;</td><td>[Add] Handle ephemeris from RTCM Version 3.x 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 systems<br> [Bug] Fixed problem with PRN 32 in RTCMv2 decoder<br> [Bug] Fix for Trimble 4000SSI receivers in RTCMv2 decoder<br> [Mod] Major revision of input buffer in RTCMv2 decoder</td></tr>
    699 <tr><td>May 2008 &nbsp;</td><td>Version 1.6 &nbsp;</td><td>[Mod] Fill blanc columns in RINEXv3 with 0.000</td></tr>
     310<tr><td>August 2008 &nbsp;</td><td>Version 1.0 &nbsp;</td><td>[Add] First Beta Binaries published based on Qt 4.2.3.</td></tr>
    700311</table>
    701312</p>
    702313
    703 <p><a name="ntrip"><h4>8.2. NTRIP</h4></p>
     314<p><a name="ntrip"><h4>6.2. NTRIP</h4></p>
    704315
    705316<p>
    … …  
    712323
    713324<p>
    714 NTRIP is implemented in three system software components: NTRIP clients, NTRIP servers and NTRIP broadcasters. The NTRIP broadcaster is the actual HTTP server program whereas NTRIP client and NTRIP server are acting as HTTP clients.
     325NTRIP is implemented in three system software components: NTRIP clients, NTRIP servers and NTRIP broadcasters. The NTRIP broadcaster is the actual HTTP server program whereas NTRIP client and NTRIP server are acting as HTTP clients. The NTRIP broadcaster maintains a source-table containing information on available NTRIP streams, networks of NTRIP streams and NTRIP broadcasters. The source-table is sent to an NTRIP client on request.
    715326</p>
    716327
    … …  
    726337</p>
    727338
    728 <p><a name="source"><h4>8.2.1 Source-table</h4></p>
    729 
    730 <p>
    731 The NTRIP broadcaster maintains a source-table containing information on available NTRIP streams, networks of NTRIP streams and NTRIP broadcasters. The source-table is sent to an NTRIP client on request. Source-table records are dedicated to one of the following: Data Streams (record type STR), Casters (record type CAS), or Networks of streams (record type NET).
    732 </p>
    733 
    734 <p>
    735 Source-table records of type STR contain the following data fields: 'mountpoint', 'identifier', 'format', 'format-details', 'carrier', 'nav-system', 'network', 'country', 'latitude', 'longitude', 'nmea', 'solution', 'generator', 'compr-encryp', 'authentication', 'fee', 'bitrate', 'misc'.
    736 </p>
    737 <p>
    738 Source-table records of type NET contain the following data fields: 'identifiey', 'operator', 'authentication', 'fee', 'web-net', 'web-str', 'web-reg', 'misc'.
    739 </p>
    740 <p>
    741 Source-table records of type CAS contain the following data fields: 'host', 'port', 'identifier', 'operator', 'nmea', 'country', 'latitude', 'longitude', 'misc'.
    742 </p>
    743 
    744 <p><a name="rtcm"><h4>8.3. RTCM</h4></p>
     339<p>
     340</p>
     341
     342<p><a name="rtcm"><h4>6.3. RTCM</h4></p>
    745343
    746344<p>
    … …  
    750348</p>
    751349
    752 <p><a name="rtcm2"><h4>8.3.1 RTCM Version 2.x</h4></p>
    753 <p>
    754 Transmitting GNSS carrier phase data can be done through RTCM Version 2.x messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of some interest here are:
    755 </p>
    756 
    757 <ul>
    758 <li>
    759 Type 1 message is the range correction message and is the primary message in code-phase differential positioning (DGPS). It is computed in the base receiver by computing the error in the range measurement for each tracked SV.
    760 </li>
    761 <li>
    762 Type 2 message is automatically generated when a new set of satellite ephemeris is downloaded to the base receiver. It is the computed difference between the old ephemeris and the new ephemeris. Type 2 messages are used when the base station is transmitting Type 1 messages.
    763 </li>
    764 <li>
    765 Type 3 and 22 messages are the base station position and the antenna offset. Type 3 and 22 are used in RTK processing to perform antenna reduction.
    766 </li>
    767 <li>
    768 Type 6 message is a null frame filler message that is provided for data links that require continuous transmission of data, even if there are no corrections to send. As many Type 6 messages are sent as required to fill in the gap between two correction messages (type 1). Message 6 is not sent in burst mode.
    769 </li>
    770 <li>
    771 Type 9 message serves the same purpose as Type 1, but does not require a complete satellite set. As a result, Type 9 messages require a more stable clock than a station transmitting Type 1 's, because the satellite corrections have different time references.
    772 </li>
    773 <li>
    774 Type 16 message is simply a text message entered by the user that is transmitted from the base station to the rover. It is used with code-phase differential.
    775 </li>
    776 <li>
    777 Type 18 and 20 messages are RTK uncorrected carrier phase data and carrier phase corrections.
    778 </li>
    779 <li>
    780 Type 19 and 21 messages are the uncorrected pseudo-range measurements and pseudo-range corrections used in RTK.
    781 </li>
    782 <li>
    783 Type 23 message provides the information on the antenna type used on the reference station.
    784 </li>
    785 <li>
    786 Type 24 message carries the coordinates of the installed antenna's ARP in the GNSS coordinate system coordinates.
    787 </li>
    788 </ul>
    789 
    790 <p><a name="rtcm3"><h4>8.3.2 RTCM Version 3.x</h4></p>
    791 <p>
    792 RTCM Version 3.x has been developed as a more efficient alternative to RTCM Version 2.x. 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.x standard is intended to correct these weaknesses.
    793 </p>
    794 <p>
    795 RTCM Version 3.x defines a number of message types. Messages that may be of interest here are:
    796 </p>
    797 <ul>
    798 <li>Type 1001, GPS L1 code and phase.</li>
    799 <li>Type 1002, GPS L1 code and phase and ambiguities and carrier to noise ratio.</li>
    800 <li>Type 1003, GPS L1 and L2 code and phase.</li>
    801 <li>Type 1004, GPS L1 and L2 code and phase and ambiguities and carrier to noise ratio.</li>
    802 <li>Type 1005, Station coordinates XZY for antenna reference point.</li>
    803 <li>Type 1006, Station coordinates XYZ for antenna reference point and antenna height.</li>
    804 <li>Type 1007, Antenna descriptor and ID.</li>
    805 <li>Type 1008, Antenna serial number.</li>
    806 <li>Type 1009, GLONASS L1 code and phase.</li>
    807 <li>Type 1010, GLONASS L1 code and phase and ambiguities and carrier to noise ratio.</li>
    808 <li>Type 1011, GLONASS L1 and L2 code and phase.</li>
    809 <li>Type 1012, GLONASS L1 and L2 code and phase and ambiguities and carrier to noise ratio.</li>
    810 <li>Type 1013, Modified julian date, leap second, configured message types and interval.</li>
    811 <li>Type 1014 and 1017, Network RTK (MAK) messages (under development).</li>
    812 <li>Type 1019, GPS ephemeris.</li>
    813 <li>Type 1020, GLONASS ephemeris.</li>
    814 <li>Type 4088 and 4095, Proprietary messages (under development).
    815 </li>
    816 </ul>
    817 
    818 <p><a name="rtigs"><h4>8.4. RTIGS</h4></p>
    819 <p>
    820 RTIGS stands for a data format and transport protocol for GPS observations. It was defined by the Real-Time IGS Working Group (RTIGS WG). Its definition is based on the SOC format. Every RTIGS record has one of the following numbers:
    821 </p>
    822 <p>
    823 Station record number 100<br>
    824 Observation record (O_T) number 200<br>
    825 Ephemeris record (E_T) number 300<br>
    826 Meteorological record (M_T) number 400
    827 </p>
    828 <p>
    829 Every station has one of the following unique numbers:
    830 </p>
    831 <p>
    832 1-99 reserved for JPL<br>
    833 100-199 reserved for NRCan<br>
    834 200-299 reserved for NGS<br>
    835 300-399 reserved for ESOC<br>
    836 400-499 reserved for GFZ<br>
    837 500-599 reserved for BKG<br>
    838 600-699 reserved for GEOSCIENCE AUS<br>
    839 700-799 others<br>
    840 etc
    841 </p>
    842 <p>
    843 The number of bytes in each real time message includes the header as well as the data content, but NOT the pointer.
    844 </p>
    845 <p>
    846 For example:
    847 </p>
    848 <ul>
    849 <li>A station message is output once per hour and is 20 bytes.</li>
    850 <li>An observation message is output once per second. The header is 12 bytes long and the SOC data is 21 bytes per PRN. So a typical RTIGSO_T message will be 390 bytes if 8 sats are being tracked.</li>
    851 <li>An ephemeris message is output when the ephemeris is decoded by the GPS receiver. The time in the ephemeris header is the collected time. Only one ephemeris can be bundled in a RTIGSE_T message.<br>
    852 A RTIGSE_T message contains one eph. The message consists of 12 header bytes and 72 ephemeris bytes, for a total of 84 bytes.</li>
    853 <li>The RTIGSM_T (met) message should be issued once every 15 minutes. A basic met message consists of a 12 byte header and 3 longs (temp, press and relative humidity) for a total of 24 bytes.</li>
    854 </ul>
    855 <p>
    856 All records are related to a station configuration indicated by the Issue of Data Station (IODS). The IODS will enable the user to identify the equipment and software that was used to derive the observation data.
    857 </p>
    858 <p>
    859 Each record header contains the GPS Time in seconds which flows continuously from 6 Jan-1980 onwards.
    860 </p>
    861 <p>
    862 The data payload of each record consists of observations. The structures indicate a pointer to data but in fact the broadcast messages do not contain the pointer, only the data. Users will have to manage the data and the pointer is shown in order to illustrate where the data is located in the message and one possible data management option.
    863 </p>
    864 <p>
    865 All record data are in network byte order (Big Endian), i.e. IA32 users have to swap bytes.
    866 </p>
    867 <p>
    868 Visit <u>http://igscb.jpl.nasa.gov/mail/igs-rtwg/2004/msg00001.html</u> for further details.
    869 </p>
    870 
    871 <p><a name="soc"><h4>8.4.1 SOC</h4></p>
    872 <p>
    873 The SOC format has been designed in July 1999 by the Jet Propulsion Laboratory (JPL) and the California Institute of Technology (CalTech) to transport 1Hz GPS data with minimal bandwidth over the open Internet. SOC follows the 'little-endian' byte order meaning that the low-order byte of a number is stored in memory at the lowest address, and the high-order byte at the highest address. Because the transport layer is UDP, the format does not include sync bits, a checksum, or cyclic redundancy checksum (CRC). SOC allows to transport the GPS observable CA, P1, P2, L1, and L2, efficiently compressed down to 14 bytes with 1 mm range resolution and 0.02 mm phase resolution. SOC contains epochs for cycle slips, a stand-alone time-tag per epoch, a minimum representation of the receiver's clock solution, 3 SNR numbers, a unique site id, a modulo 12 hour sequence number and flags for receiver type and GPS health. SOC's simple structure comprises an 8 byte header, a 9 byte overhead for timetag, number of gps, etc., plus 21 data bytes per gps.
    874 </p>
    875 <p>
    876 Visit <u>http://gipsy.jpl.nasa.gov/igdg/papers/SOC_FORMAT.ppt</u> for further details.
    877 </p>
    878 <p>
    879 </p>
    880 <p><a name="config"><h4>8.5. Config File</h4></p>
    881 <p>
    882 The following is an example for the contents of a Unix/Linux configuration file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. It enables the retrieval of stream ACOR0 form www.euref-ip.net and FFMJ3 from www.igs-ip.net for the generation of 15 min RINEX files. RINEX files are uploaded to an archive using script 'up2archive' :
     350<p><a name="rtcm3"><h4>6.3.1 RTCM Version 3.x</h4></p>
     351<p>
     352RTCM Version 3.x has been developed as a stream format alternative to RTCM Version 2.x. Service providers and vendors have asked for a standard that would be efficient, easy to use, and easily adaptable to new situations.
     353</p>
     354
     355<p>
     356RTCM is in the process of developing new Version 3 messages types to transport satellite clock and orbit corrections in real-time. Based on the latest available proposal, the following tentative messages currently under discussion are of interest here:
     357<ul>
     358<li>Message type 4050: GPS orbit corrections to Broadcast Ephemeris</li>
     359<li>Message type 4051: GPS clock corrections to Broadcast Ephemeris</li>
     360<li>Message type 4052: GPS code biases</li>
     361<li>Message type 4053: GLONASS orbit corrections to Broadcast Ephemeris</li>
     362<li>Message type 4054: GLONASS clock corrections to Broadcast Ephemeris</li>
     363<li>Message type 4055: GLONASS code biases</li>
     364<li>Message type 4056: Combined GPS and GLONASS orbit corrections to Broadcast Ephemeris</li>
     365<li>Message type 4057: Combined GPS and GLONASS clock corrections to Broadcast Ephemeris</li>
     366</ul>
     367</p>
     368<p>
     369RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications following the 'state space' approach.
     370</p>
     371
     372<p><a name="config"><h4>6.4. Config File</h4></p>
     373<p>
     374The following is an example for the contents of a Unix/Linux configuration file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. It enables the upload of stream CLCK1 to www.euref-ip.net. Clock RINEX files and SP3 orbit files are uploaded to a directory /home/weber/rinex :
    883375<pre>
    884376[General]
    885 adviseFail=15
    886 adviseReco=5
    887 adviseScript=
    888 binSampl=0
    889 casterHost=www.euref-ip.net
    890 casterPassword=pass
    891 casterPort=80
    892 casterUser=user
    893 ephIntr=1 day
    894 ephPath=/home/user/rinex
    895 ephV3=2
    896 logFile=/home/user/log.txt
    897 makePause=0
    898 mountPoints=//user:pass@www.euref-ip.net:2101/ACOR0 RTCM_2.3 43.36 351.60 no, //user:pass@www.igs-ip.net:2101/FFMJ3 RTCM_3.0 41.58 1.40 no
    899 obsRate=
    900 outEphPort=2102
    901 outFile=/home/user/ascii
     377clkPort=2067
     378ephPort=2066
     379logFile=/home/weber/rinex/log.txt
     380mountpoint=CLCK1
     381outFile=/home/weber/rinex/data.txt
     382outHost=www.igs-ip.net
    902383outPort=2101
    903 perfIntr=
    904 proxyHost=proxyhost
    905 proxyPort=8001
    906 rnxAppend=2
    907 rnxIntr=15 min
     384password=uploadpass
     385rnxIntr=1 day
    908386rnxPath=/home/weber/rinex
    909387rnxSampl=0
    910 rnxScript=/home/weber/up2archive
    911 rnxSkel=SKL
    912 rnxV3=2
    913 waitTime=5
     388sp3Intr=1 day
     389sp3Path=/home/weber/rinex
     390sp3Sampl=0
    914391</pre>
    915392</p>
    916393
    917 <p><a name="links"><h3>8.6 Links</h3></p>
     394<p><a name="links"><h3>6.5 Links</h3></p>
    918395<table>
    919396<tr></tr>
Note: See TracChangeset for help on using the changeset viewer.