Changeset 429 in ntrip
- Timestamp:
- Mar 29, 2007, 2:39:29 PM (18 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (15 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r415 r429 8 8 </p> 9 9 <p> 10 BNC has been written under GNU General Public License (GPL). Binaries for BNC are available for Windows, Linux, and Solaris systems. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4. 0.1are installed.10 BNC has been written under GNU General Public License (GPL). Binaries for BNC are available for Windows, Linux, and Solaris systems. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.2.3 are installed. 11 11 <table> 12 12 <tr></tr> 13 13 <tr><td><b>History</b></td></tr> 14 <tr><td>Dec 1,2006 </td><td>Version 1.0b </td><td>Binaries of first beta version published.</td></tr>15 <tr><td>Jan 20 , 2007 </td><td>Version 1.1b </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>16 <tr><td> Feb 1, 2007 </td><td>Version 1.2b </td><td>[Bug] Output only through IP port<br>[Bug] Method 'reconnecting' now thread-save14 <tr><td>Dec 2006 </td><td>Version 1.0b </td><td>Binaries of first beta version published.</td></tr> 15 <tr><td>Jan 2007 </td><td>Version 1.1b </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> 16 <tr><td>Apr 2007 </td><td>Version 1.2b </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' 17 17 </table> 18 18 </p> … … 28 28 </h4> 29 29 </p> 30 <br>31 30 32 31 <p><a name="purpose"><h3>A - Purpose</h3></p> … … 39 38 <li>output synchronize observations epoch by epoch through an IP port to support real-time GNSS engines.</li> 40 39 </ul> 40 </p> 41 41 <p> 42 42 BNC decodes and converts GNSS data streams carrying code and phase data coming in 43 43 </p> 44 <p> 44 45 <ul> 45 46 <li>RTCM Version 2.x format containing message types 18 and 19 (GPS and GLONASS), </li> 46 47 <li>RTCM Version 3 format containing message types 1002 or 1004 (GPS), and 1010 or 1012 (GLONASS),</li> 47 <li>RTIGS format (only GPS).</li> 48 </ul> 48 <li>RTIGS format (only GPS).</li> 49 </ul> 50 Furthermore, BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files. 49 51 </p> 50 52 <p><b>Warning</b><br> … … 61 63 B - 4.3. <a href=#binary>Port for Binary Output</a><br> 62 64 B - 5. <a href=#rinex>RINEX</a><br> 63 B - 5.1. <a href=#rnxpath>RINEX Directory</a><br> 64 B - 5.2. <a href=#rnxscript>RINEX Script</a><br> 65 B - 5.3. <a href=#rnxinterval>RINEX File Interval</a><br> 66 B - 5.4. <a href=#rnxsample>RINEX Sampling</a><br> 67 B - 5.5. <a href=#rnxskeleton>RINEX Skeleton Extension</a><br> 68 B - 5.6. <a href=#rnxappend>Append Files</a><br> 65 B - 5.1. <a href=#rnxname>RINEX File Names</a><br> 66 B - 5.2. <a href=#rnxpath>RINEX Directory</a><br> 67 B - 5.3. <a href=#rnxscript>RINEX Script</a><br> 68 B - 5.4. <a href=#rnxinterval>RINEX File Interval</a><br> 69 B - 5.5. <a href=#rnxsample>RINEX Sampling</a><br> 70 B - 5.6. <a href=#rnxskeleton>RINEX Skeleton Extension</a><br> 71 B - 5.7. <a href=#rnxappend>Append Files</a><br> 69 72 B - 6. <a href=#mountpoints>Mountpoints</a><br> 70 73 B - 6.1. <a href=#AddMounts>Add Mountpoints</a><br> … … 195 198 <p><a name="rinex"><h4>B - 5. RINEX</h4></p> 196 199 <p> 197 Observations are converted to RINEX Version 2.11. RINEX file names are derived by BNC from the first 4 characters of the corresponding mountpoint (4Char Station ID) while omitting the residual part of the mountpoint string. Thus, retrieving data from mountpoints FRANKFURT and WETTZELL leads to hourly RINEX observation files named</p> 200 Observations will be converted to RINEX Version 2.11 if they come in either RTCM Version 2.x, RTCM Version 3, 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 even if a RINEX file does not contain GLONASS data, the 'RINEX TYPE' field in the RINEX file header may be set to 'M (MIXED)'. 201 </p> 202 <p><a name="rnxname"><h4>B - 5.1 RINEX File Names</h4></p> 203 <p> 204 RINEX file names are derived by BNC from the first 4 characters of the corresponding mountpoint (4Char Station ID) while omitting the residual part of the mountpoint string. Thus, retrieving data from mountpoints FRANKFURT and WETTZELL leads to hourly RINEX observation files named</p> 198 205 <p> 199 206 FRAN{ddd}{h}.{yy}O<br> … … 223 230 where 'mm' is the starting minute within the hour. 224 231 </p> 225 <p> 226 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 even if a RINEX file does not contain GLONASS data, the 'RINEX TYPE' field in the RINEX file header may be set to 'M (MIXED)'. 227 </p> 228 229 <p><a name="rnxpath"><h4>B - 5.1 RINEX Directory - optional</h4></p> 232 233 <p><a name="rnxpath"><h4>B - 5.2 RINEX Directory - optional</h4></p> 230 234 <p> 231 235 Enter a path for saving the RINEX files in a directory. If this directory does not exist, BNC will not create RINEX files. Default value for 'RINEX directory' is an empty option field, meaning that streams are not converted to RINEX. 232 236 </p> 233 237 234 <p><a name="rnxscript"><h4>B - 5. 2RINEX Script - optional</h4></p>238 <p><a name="rnxscript"><h4>B - 5.3 RINEX Script - optional</h4></p> 235 239 <p> 236 240 Whenever a RINEX file is saved, you may like to compress, copy or upload it immediately via FTP. For that you enter the full path of a script or batch file which is then called to carry out these operations. The RINEX file path will be passed to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux systems). … … 240 244 </p> 241 245 242 <p><a name="rnxinterval"><h4>B - 5. 3RINEX File Interval - mandatory if 'RINEX directory' set</h4></p>246 <p><a name="rnxinterval"><h4>B - 5.4 RINEX File Interval - mandatory if 'RINEX directory' set</h4></p> 243 247 <p> 244 248 Select the interval for the RINEX file generation. Default for 'RINEX file interval' is 15 minutes. 245 249 </p> 246 250 247 <p><a name="rnxsample"><h4>B - 5. 4RINEX Sampling - mandatory if 'RINEX directory' set </h4></p>251 <p><a name="rnxsample"><h4>B - 5.5 RINEX Sampling - mandatory if 'RINEX directory' set </h4></p> 248 252 <p> 249 253 Select the RINEX sample interval in seconds. Zero '0' stands for converting all incoming epochs to RINEX. Default for RINEX 'Sampling' is '0'. 250 254 </p> 251 255 252 <p><a name="rnxskeleton"><h4>B - 5. 5RINEX Skeleton Extension - optional</h4></p>253 <p> 254 Whenever BNC generates a new RINEX file, it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. An 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 for a public RINEX header skeleton file concerning the EPN station Brussels.256 <p><a name="rnxskeleton"><h4>B - 5.6 RINEX Skeleton Extension - optional</h4></p> 257 <p> 258 Whenever BNC starts generating RINEX 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. An 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 for a public RINEX header skeleton file concerning the EPN station Brussels. 255 259 </p> 256 260 <p> … … 301 305 <p> 302 306 303 <p><a name="rnxappend"><h4>B - 5. 6Append Files</h4></p>307 <p><a name="rnxappend"><h4>B - 5.7 Append Files</h4></p> 304 308 <p> 305 309 When starting BNC, new RINEX files are created by default. Probably existing files will be overwritten. However, it may be desirable to append observations to already existing RINEX files following a restart of BNC after an intentional 'Stop', a system crash or a crash of BNC. Hit 'Append files' to continue with already existing files and thus save what has been recorded so far. Note that option 'Append files' also concerns the 'ASCII output file' and the 'Log' file. … … 339 343 <p><a name="GetTable"><h4>B - 6.4 Get Table</h4></p> 340 344 <p> 341 Hit button 'Get Table' 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 2.x, RTCM 3, or RTIGS format s. RTCM 2.x streams must contain message types 18 and 19 while RTCM 3 streams must contain GPS 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. Select your streams line by line, use +Shift and +Ctrl when necessary.345 Hit button 'Get Table' 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 2.x, RTCM 3, or RTIGS format. RTCM 2.x streams must contain message types 18 and 19 while RTCM 3 streams must contain GPS 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. Select your streams line by line, use +Shift and +Ctrl when necessary. 342 346 </p> 343 347 <p> … … 355 359 <ul> 356 360 <li> 357 BNC automatically selects one out of several internal decoders for a stream based on its 'format' and 'format-details' as given in the source-table. It may happen that you need to overrule the automated decoder selection because of source-table setup deficiencies. Therefore BNC allows to edit the decoder string (first double-click, then edit field 'decoder', then hit Enter) for the streams shown under 'Mountpoints'. Accepted decoder strings allowed to be introduced are 'RTCM_2.x', 'RTCM_3', and 'RTIGS'. 361 BNC automatically selects one out of several internal decoders for a stream based on its 'format' and 'format-details' as given in the source-table. It may happen that you need to overrule the automated decoder selection because of source-table setup deficiencies. Therefore BNC allows to edit the decoder string (first double-click, then edit field 'decoder', then hit Enter) for the streams shown under 'Mountpoints'. Accepted decoder strings allowed to be introduced for stream decoding and conversion are 'RTCM_2.x', 'RTCM_3', and 'RTIGS'. 362 </li> 363 <li> 364 BNC allows to by-pass its stream decoding and conversion algorithms, leave whatever is received untouched and save it in daily named files. To activate this functionality you need to enter the decoder string 'ZERO'. The generated file names are build from the characters of the affected mountpoints plus the two-digit numbers for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and runnign BNC on March 29, 2007 to save incoming data untouched in a file would lead to a file name WTZZ0_070329. 358 365 </li> 359 366 <li> … … 386 393 Note that the self-explaining contents of the configuration file or the Windows register can easily be edited. Terminate BNC using the Windows Task Manager when running it in 'no window' mode on Windows systems. 387 394 </p> 388 <br>389 395 <p><a name="limits"><h3>C - Limitations</h3></p> 390 396 <ul> … … 431 437 Federal Agency for Cartography and Geodesy (BKG)<br> 432 438 Frankfurt, Germany<br> 433 euref-ip@bkg.bund.de 434 </p> 435 <br> 439 euref-ip@bkg.bund.de 440 </p> 436 441 437 442 <p><a name="links"><h3>E - Links</h3></p> … … 445 450 <tr><td>Radio Technical Commission<br>for Maritime Services </td><td><u>http://www.rtcm.org</u> 446 451 </table> 447 <br>448 452 449 453 <p><a name="annex"><h3>F - Annex</h3></p> … … 458 462 F - 4. <a href=#config>Config File</a> 459 463 </p> 460 <br>461 464 462 465 <p><a name="ntrip"><h4>F - 1. NTRIP</h4></p> … … 508 511 Copies of RTCM Recommended Standards can be ordered through <u>http://www.rtcm.org/orderinfo.php</u>. 509 512 </p> 510 <br>511 513 512 514 <p><a name="rtcm2"><h4>F - 2.1 RTCM Version 2.x</h4></p>
Note:
See TracChangeset
for help on using the changeset viewer.
