Changeset 1686 in ntrip
- Timestamp:
- Mar 3, 2009, 10:36:35 AM (15 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (36 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r1684 r1686 72 72 <p><a name="options"><h3>3. Options</h3></p> 73 73 <p> 74 The usual handling of BNC is that you first select a number of streams from NTRIP broadcasters ('Add Streams'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various tabs to select a combination of processing options before you start the program ('Start'). Records of BNC's activities are shown in the 'Logs' canvas on the bottom of the main window. 74 This section describes BNC's top menu bar, its processing options and bottom menu bar. 75 </p> 76 <p> 77 The usual handling of BNC is that you first select a number of streams ('Add Streams'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various tabs to select a combination of processing options before you start the program ('Start'). Records of BNC's activities are shown in the 'Logs' canvas on the bottom of the main window. 75 78 </p> 76 79 <p> … … 80 83 </p> 81 84 <p> 82 3.1. <a href=#file>File</a><br> 83 3.2. <a href=#help>Help</a><br> 84 3.3. <a href=#proxy>Proxy</a><br> 85 3.4. <a href=#general>General</a><br> 86 3.4.1. <a href=#genlog>Logfile</a><br> 87 3.4.2. <a href=#genapp>Append Files</a><br> 88 3.4.3. <a href=#genconf>Reread Configuration</a><br> 89 3.4.4. <a href=#genstart>Auto Start</a><br> 90 3.5. <a href=#rinex>RINEX Observations</a><br> 91 3.5.1. <a href=#rnxname>File Names</a><br> 92 3.5.2. <a href=#rnxdir>Directory</a><br> 93 3.5.3. <a href=#rnxinterval>File Interval</a><br> 94 3.5.4. <a href=#rnxsample>Sampling</a><br> 95 3.5.5. <a href=#rnxskl>Skeleton Extension</a><br> 96 3.5.6. <a href=#rnxscript>Script</a><br> 97 3.5.7. <a href=#rnxvers>Version</a><br> 98 3.6. <a href=#ephemeris>RINEX Ephemeris</a><br> 99 3.6.1. <a href=#ephdir>Directory</a><br> 100 3.6.2. <a href=#ephint>Interval</a><br> 101 3.6.3. <a href=#ephport>Port</a><br> 102 3.6.4. <a href=#ephvers>Version</a><br> 103 3.7. <a href=#correct>Broadcast Corrections</a><br> 104 3.7.1. <a href=#corrdir>Directory</a><br> 105 3.7.2. <a href=#corrint>Interval</a><br> 106 3.7.3. <a href=#corrport>Port</a><br> 107 3.7.4. <a href=#corrwait>Wait for Full Epoch</a><br> 108 3.8. <a href=#syncout>Feed Engine</a><br> 109 3.8.1. <a href=#syncport>Port</a><br> 110 3.8.2. <a href=#syncwait>Wait for Full Epoch</a><br> 111 3.8.3. <a href=#syncsample>Sampling</a><br> 112 3.8.4. <a href=#syncfile>File</a><br> 113 3.8.5. <a href=#syncuport>Port (unsynchronized)</a><br> 114 3.9. <a href=#serial>Serial Link</a><br> 115 3.9.1. <a href=#sermount>Mountpoint</a><br> 116 3.9.2. <a href=#serport>Port Name</a><br> 117 3.9.3. <a href=#serbaud>Baud Rate</a><br> 118 3.9.4. <a href=#serparity>Parity</a><br> 119 3.9.5. <a href=#serdata>Data Bits</a><br> 120 3.9.6. <a href=#serstop>Stop Bits</a><br> 121 3.9.7. <a href=#serauto>NMEA</a><br> 122 3.9.8. <a href=#serfile>File</a><br> 123 3.9.9. <a href=#serheight>Height</a><br> 124 3.10. <a href=#advnote>Outages</a><br> 125 3.10.1. <a href=#obsrate>Observation Rate</a><br> 126 3.10.2. <a href=#advfail>Failure Threshold</a><br> 127 3.10.3. <a href=#advreco>Recovery Threshold</a><br> 128 3.10.4. <a href=#advscript>Script</a><br> 129 3.11. <a href=#misc>Miscellaneous</a><br> 130 3.11.1. <a href=#miscmount>Mountpoint</a><br> 131 3.11.2. <a href=#miscperf>Log Latency</a><br> 132 3.11.3. <a href=#miscscan>Scan RTCM</a><br> 133 3.12. <a href=#streams>Streams</a><br> 85 3.1. <a href=#topmenu>Top Menu Bar</a><br> 86 3.1.1 <a href=#file>File</a><br> 87 3.1.2 <a href=#help>Help</a><br> 88 3.2. <a href=#proxy>Proxy</a><br> 89 3.3. <a href=#general>General</a><br> 90 3.3.1. <a href=#genlog>Logfile</a><br> 91 3.3.2. <a href=#genapp>Append Files</a><br> 92 3.3.3. <a href=#genconf>Reread Configuration</a><br> 93 3.3.4. <a href=#genstart>Auto Start</a><br> 94 3.4. <a href=#rinex>RINEX Observations</a><br> 95 3.4.1. <a href=#rnxname>File Names</a><br> 96 3.4.2. <a href=#rnxdir>Directory</a><br> 97 3.4.3. <a href=#rnxinterval>File Interval</a><br> 98 3.4.4. <a href=#rnxsample>Sampling</a><br> 99 3.4.5. <a href=#rnxskl>Skeleton Extension</a><br> 100 3.4.6. <a href=#rnxscript>Script</a><br> 101 3.4.7. <a href=#rnxvers>Version</a><br> 102 3.5. <a href=#ephemeris>RINEX Ephemeris</a><br> 103 3.5.1. <a href=#ephdir>Directory</a><br> 104 3.5.2. <a href=#ephint>Interval</a><br> 105 3.5.3. <a href=#ephport>Port</a><br> 106 3.5.4. <a href=#ephvers>Version</a><br> 107 3.6. <a href=#correct>Broadcast Corrections</a><br> 108 3.6.1. <a href=#corrdir>Directory</a><br> 109 3.6.2. <a href=#corrint>Interval</a><br> 110 3.6.3. <a href=#corrport>Port</a><br> 111 3.6.4. <a href=#corrwait>Wait for Full Epoch</a><br> 112 3.7. <a href=#syncout>Feed Engine</a><br> 113 3.7.1. <a href=#syncport>Port</a><br> 114 3.7.2. <a href=#syncwait>Wait for Full Epoch</a><br> 115 3.7.3. <a href=#syncsample>Sampling</a><br> 116 3.7.4. <a href=#syncfile>File</a><br> 117 3.7.5. <a href=#syncuport>Port (unsynchronized)</a><br> 118 3.8. <a href=#serial>Serial Link</a><br> 119 3.8.1. <a href=#sermount>Mountpoint</a><br> 120 3.8.2. <a href=#serport>Port Name</a><br> 121 3.8.3. <a href=#serbaud>Baud Rate</a><br> 122 3.8.4. <a href=#serparity>Parity</a><br> 123 3.8.5. <a href=#serdata>Data Bits</a><br> 124 3.8.6. <a href=#serstop>Stop Bits</a><br> 125 3.8.7. <a href=#serauto>NMEA</a><br> 126 3.8.8. <a href=#serfile>File</a><br> 127 3.8.9. <a href=#serheight>Height</a><br> 128 3.9. <a href=#advnote>Outages</a><br> 129 3.9.1. <a href=#obsrate>Observation Rate</a><br> 130 3.9.2. <a href=#advfail>Failure Threshold</a><br> 131 3.9.3. <a href=#advreco>Recovery Threshold</a><br> 132 3.9.4. <a href=#advscript>Script</a><br> 133 3.10. <a href=#misc>Miscellaneous</a><br> 134 3.10.1. <a href=#miscmount>Mountpoint</a><br> 135 3.10.2. <a href=#miscperf>Log Latency</a><br> 136 3.10.3. <a href=#miscscan>Scan RTCM</a><br> 137 3.11. <a href=#streams>Streams</a><br> 138 3.11.1 <a href=#streamedit>Edit Streams</a><br> 139 3.11.2 <a href=#streamdelete>Delete Streams</a><br> 140 3.11.3 <a href=#streamconf>Reconfigure Streams On-the-fly</a><br> 141 3.12. <a href=#bottom>Bottom Menu Bar</a><br> 134 142 3.12.1. <a href=#streamadd>Add Streams - Coming from Caster</a><br> 135 3.12.2. <a href=#streamhost>Caster Host and Port</a><br> 136 3.12.3. <a href=#streamtable>Caster Table</a><br> 137 3.12.4. <a href=#streamuser>User and Password</a><br> 138 3.12.5. <a href=#streamtable>Get Table</a><br> 139 3.12.6. <a href=#streamntrip>NTRIP Version</a><br> 140 3.12.7. <a href=#streamdelete>Delete Streams</a><br> 141 3.12.8. <a href=#streamedit>Edit Streams</a><br> 142 3.12.9. <a href=#streamconf>Reconfigure Streams On-the-fly</a><br> 143 3.12.10. <a href=#streamip>Add Streams - Coming from TCP/IP Port</a><br> 144 3.13. <a href=#start>Start</a><br> 145 3.14. <a href=#stop>Stop</a><br> 146 3.15. <a href=#cmd>Command Line Options</a><br> 147 3.15.1. <a href=#nw>No Window Mode</a><br> 148 3.15.2. <a href=#post>Offline Mode</a><br> 149 3.15.3. <a href=#conffile>Configuration File</a><br> 150 </p> 151 152 <p><a name="file"><h4>3.1. File</h4></p> 143 3.12.1.1 <a href=#streamhost>Caster Host and Port</a><br> 144 3.12.1.2 <a href=#streamtable>Caster Table</a><br> 145 3.12.1.3 <a href=#streamuser>User and Password</a><br> 146 3.12.1.4 <a href=#gettable>Get Table</a><br> 147 3.12.1.5 <a href=#ntripv>NTRIP Version</a><br> 148 3.12.2 <a href=#streamip>Add Streams - Coming from TCP/IP Port</a><br> 149 3.12.3 <a href=#start>Start</a><br> 150 3.12.4 <a href=#stop>Stop</a><br> 151 3.13. <a href=#cmd>Command Line Options</a><br> 152 3.13.1. <a href=#nw>No Window Mode</a><br> 153 3.13.2. <a href=#post>Offline Mode</a><br> 154 3.13.3. <a href=#conffile>Configuration File</a><br> 155 </p> 156 157 <p><a name="topmenu"><h4>3.1. Top Menu Bar</h4></p> 158 <p> 159 The top menu bar allows to select a font the BNC windows, save configured options or quit the program execution. It also provides access to a program documentation. 160 </p> 161 162 <p><a name="file"><h4>3.1.1 File</h4></p> 153 163 154 164 <p> … … 166 176 </p> 167 177 168 <p><a name="help"><h4>3. 2.Help</h4></p>178 <p><a name="help"><h4>3.1.2 Help</h4></p> 169 179 170 180 <p> … … 188 198 </p> 189 199 190 <p><a name="proxy"><h4>3. 3. Proxy - for usage in a protected LAN</h4></p>200 <p><a name="proxy"><h4>3.2. Proxy - for usage in a protected LAN</h4></p> 191 201 192 202 <p> … … 195 205 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. 196 206 </p> 197 <p><a name="general"><h4>3. 4. General</h4></p>207 <p><a name="general"><h4>3.3. General</h4></p> 198 208 <p> 199 209 The following defines general settings for BNC's logfile, file handling and reconfiguration on-the-fly. 200 210 </p> 201 211 202 <p><a name="genlog"><h4>3. 4.1 Logfile - optional</h4></p>212 <p><a name="genlog"><h4>3.3.1 Logfile - optional</h4></p> 203 213 <p> 204 214 Records of BNC's activities are shown in the 'Logs' canvas on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. The logfile name will automatically be extended by a string '_YYMMDD' carrying the current date. This leads to series of daily logfiles when running BNC continuously for extended. Message logs cover 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 'Logfile (full path)' is an empty option field, meaning that BNC logs will not saved into a file. 205 215 </p> 206 216 207 <p><a name="genapp"><h4>3. 4.2 Append Files - optional</h4></p>217 <p><a name="genapp"><h4>3.3.2 Append Files - optional</h4></p> 208 218 <p> 209 219 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. 210 220 </p> 211 221 212 <p><a name="genconf"><h4>3. 4.3 Reread Configuration - optional</h4></p>222 <p><a name="genconf"><h4>3.3.3 Reread Configuration - optional</h4></p> 213 223 <p> 214 224 When operating BNC online in 'no window' mode (command line option -nw), some configuration options can nevertheless be changed on-the-fly without interrupting the running process. For that you force the program to reread parts of its configuration in pre-defined intervals from the disk. Select '1 min', '1 hour', or '1 day' to let BNC reread on-the-fly changeable configuration options every full minute, hour, or day. This lets in between edited options become effective without interrupting uninvolved threads. See annexed section 'Configuration Example' for a configuration file example and a list of on-the-fly changeable options. 215 225 </p> 216 226 217 <p><a name="genstart"><h4>3. 4.4 Auto Start - optional</h4></p>227 <p><a name="genstart"><h4>3.3.4 Auto Start - optional</h4></p> 218 228 <p> 219 229 You may like to auto-start BNC at startup time in window mode with preassigned configuration options. This may be required i.e. immediately after booting your system. Tick 'Auto start' to supersede the usage of the 'Start' button. Make sure that you maintain a link to BNC for that in your Autostart directory (Windows systems) or call BNC in a script below directory /etc/init.d (Unix/Linux/Mac systems). … … 223 233 </p> 224 234 225 <p><a name="rinex"><h4>3. 5. RINEX Observations</h4></p>235 <p><a name="rinex"><h4>3.4. RINEX Observations</h4></p> 226 236 <p> 227 237 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. 228 238 </p> 229 239 230 <p><a name="rnxname"><h4>3. 5.1 RINEX File Names</h4></p>240 <p><a name="rnxname"><h4>3.4.1 RINEX File Names</h4></p> 231 241 <p> 232 242 RINEX file names are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named</p> … … 259 269 </p> 260 270 261 <p><a name="rnxdir"><h4>3. 5.2 Directory - optional</h4></p>271 <p><a name="rnxdir"><h4>3.4.2 Directory - optional</h4></p> 262 272 <p> 263 273 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. 264 274 </p> 265 275 266 <p><a name="rnxinterval"><h4>3. 5.3 File Interval - mandatory if 'Directory' is set</h4></p>276 <p><a name="rnxinterval"><h4>3.4.3 File Interval - mandatory if 'Directory' is set</h4></p> 267 277 <p> 268 278 Select the length of the RINEX Observation file generated. The default value is 15 minutes. 269 279 </p> 270 280 271 <p><a name="rnxsample"><h4>3. 5.4 Sampling - mandatory if 'Directory' is set </h4></p>281 <p><a name="rnxsample"><h4>3.4.4 Sampling - mandatory if 'Directory' is set </h4></p> 272 282 <p> 273 283 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. 274 284 </p> 275 285 276 <p><a name="rnxskl"><h4>3. 5.5 Skeleton Extension - optional</h4></p>286 <p><a name="rnxskl"><h4>3.4.5 Skeleton Extension - optional</h4></p> 277 287 <p> 278 288 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. … … 323 333 </p> 324 334 325 <p><a name="rnxscript"><h4>3. 5.6 Script - optional</h4></p>335 <p><a name="rnxscript"><h4>3.4.6 Script - optional</h4></p> 326 336 <p> 327 337 Whenever a RINEX Observation file is saved, you might want to compress, copy or upload it immediately via FTP. BNC allows you to execute a script/batch file to carry out these operations. To do that specify the full path of the script/batch file here. BNC will pass the RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux/Mac systems). … … 334 344 </p> 335 345 336 <p><a name="rnxvers"><h4>3. 5.7 Version - optional</h4></p>346 <p><a name="rnxvers"><h4>3.4.7 Version - optional</h4></p> 337 347 <p> 338 348 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. 339 349 </p> 340 350 341 <p><a name="ephemeris"><h4>3. 6. RINEX Ephemeris</h4></p>351 <p><a name="ephemeris"><h4>3.5. RINEX Ephemeris</h4></p> 342 352 <p> 343 353 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 … … 348 358 </ul> 349 359 350 <p><a name="ephdir"><h4>3. 6.1 Directory - optional</h4></p>360 <p><a name="ephdir"><h4>3.5.1 Directory - optional</h4></p> 351 361 <p> 352 362 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. 353 363 </p> 354 364 355 <p><a name="ephint"><h4>3. 6.2 Interval - mandatory if 'Directory' is set</h4></p>365 <p><a name="ephint"><h4>3.5.2 Interval - mandatory if 'Directory' is set</h4></p> 356 366 <p> 357 367 Select the length of the RINEX Navigation file generated. The default value is 1 day. 358 368 </p> 359 369 360 <p><a name="ephport"><h4>3. 6.3 Port - optional</h4></p>370 <p><a name="ephport"><h4>3.5.3 Port - optional</h4></p> 361 371 <p> 362 372 BNC can output broadcast ephemeris in RINEX Version 3 ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. This function is introduced in order to support i.e. the 'BKG Ntrip Sate Space Server' (BNS) which transforms IGS clocks and orbits into corrections to broadcast ephemeris. 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. … … 366 376 </p> 367 377 368 <p><a name="ephvers"><h4>3. 6.4 Version - optional</h4></p>378 <p><a name="ephvers"><h4>3.5.4 Version - optional</h4></p> 369 379 <p> 370 380 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. … … 374 384 </p> 375 385 376 <p><a name="correct"><h4>3. 7. Broadcast Corrections</h4></p>386 <p><a name="correct"><h4>3.6. Broadcast Corrections</h4></p> 377 387 <p> 378 388 </p> … … 399 409 </p> 400 410 401 <p><a name="corrdir"><h4>3. 7.1 Directory - optional</h4></p>411 <p><a name="corrdir"><h4>3.6.1 Directory - optional</h4></p> 402 412 <p> 403 413 Specify a directory for saving Broadcast Corrections in files. If the specified directory does not exist, BNC will not create Broadcast Correction files. Default value for Broadcast Corrections 'Directory' is an empty option field, meaning that no Broadcast Correction files will be created. … … 431 441 </pre> 432 442 433 <p><a name="corrint"><h4>3. 7.2 Interval - mandatory if 'Directory' is set</h4></p>443 <p><a name="corrint"><h4>3.6.2 Interval - mandatory if 'Directory' is set</h4></p> 434 444 <p> 435 445 Select the length of the Broadcast Correction files. The default value is 1 day. 436 446 </p> 437 447 438 <p><a name="corrport"><h4>3. 7.3 Port - optional</h4></p>448 <p><a name="corrport"><h4>3.6.3 Port - optional</h4></p> 439 449 <p> 440 450 BNC can output epoch by epoch synchronized Broadcast 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 Broadcast Correction output via IP port is generated. … … 463 473 </p> 464 474 465 <p><a name="corrwait"><h4>3. 7.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p>475 <p><a name="corrwait"><h4>3.6.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p> 466 476 <p> 467 477 When feeding a real-time GNSS network engine waiting epoch by epoch for synchronized Broadcast Corrections, BNC drops (only concering IP port output) 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 Broadcast Corrections stream and the delay acceptable by your application. A message such as "COCK1: Correction overaged by 5 sec" shows up in BNC's logfile if 'Wait for full epoch' is exceeded. 468 478 </p> 469 479 470 <p><a name="syncout"><h4>3. 8. Feed Engine</h4></p>480 <p><a name="syncout"><h4>3.7. Feed Engine</h4></p> 471 481 <p> 472 482 BNC can generate synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed a real-time GNSS network engine. The output can be produced in a binary format through an IP port and/or a plain ASCII format to save the observations in a local file. It comprises the following observations where available:</p> … … 530 540 </p> 531 541 532 <p><a name="syncport"><h4>3. 8.1 Port - optional</h4></p>542 <p><a name="syncport"><h4>3.7.1 Port - optional</h4></p> 533 543 <p> 534 544 BNC can produce synchronized observations in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Scynchronized means that BNC collects all data for any specific epoch which become available within a certain number of latency seconds (see 'Wait for Full Epoch' option). It then - epoch by epoch - outputs whatever has been received. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary synchronized output is generated.</p> … … 536 546 </p> 537 547 538 <p><a name="syncwait"><h4>3. 8.2 Wait for Full Epoch - mandatory if 'Port' is set</h4></p>548 <p><a name="syncwait"><h4>3.7.2 Wait for Full Epoch - mandatory if 'Port' is set</h4></p> 539 549 <p> 540 550 When feeding a real-time GNSS network engine waiting for synchronized 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. … … 544 554 </p> 545 555 546 <p><a name="syncsample"><h4>3. 8.3 Sampling - mandatory if 'File' or 'Port' is set</h4></p>556 <p><a name="syncsample"><h4>3.7.3 Sampling - mandatory if 'File' or 'Port' is set</h4></p> 547 557 <p> 548 558 Select the synchronized observation output sampling interval in seconds. A value of zero '0' tells BNC to send/store all received epochs. This is the default value. 549 559 </p> 550 560 551 <p><a name="syncfile"><h4>3. 8.4 File - optional</h4></p>561 <p><a name="syncfile"><h4>3.7.4 File - optional</h4></p> 552 562 <p> 553 563 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. … … 557 567 </p> 558 568 559 <p><a name="syncuport"><h4>3. 8.5 Port (unsynchronized) - optional</h4></p>569 <p><a name="syncuport"><h4>3.7.5 Port (unsynchronized) - optional</h4></p> 560 570 <p> 561 571 BNC can produce unsynchronized observations from all configured streams in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Unscynchronized means that BNC immediately forwards any received observation to the port. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary unsynchronized output is generated.</p> 562 572 <p> 563 573 564 <p><a name="serial"><h4>3. 9. Serial Link</h4></p>574 <p><a name="serial"><h4>3.8. Serial Link</h4></p> 565 575 <p> 566 576 You may use BNC to feed a serial connected device like an GNSS rover. For that one of the incoming streams can be forwarded to a serial port. 567 577 </p> 568 578 569 <p><a name="sermount"><h4>3. 9.1 Mountpoint - optional</h4></p>579 <p><a name="sermount"><h4>3.8.1 Mountpoint - optional</h4></p> 570 580 <p> 571 581 Enter a 'Mountpoint' to forward its corresponding stream to a serial connected device. … … 575 585 </p> 576 586 577 <p><a name="serport"><h4>3. 9.2 Port Name - mandatory if 'Mountpoint' is set</h4></p>587 <p><a name="serport"><h4>3.8.2 Port Name - mandatory if 'Mountpoint' is set</h4></p> 578 588 <p> 579 589 Enter the serial 'Port name' selected on your host for communication with the serial connected device. Valid port names are … … 592 602 </p> 593 603 594 <p><a name="serbaud"><h4>3. 9.3 Baud Rate - mandatory if 'Mountpoint' is set</h4></p>604 <p><a name="serbaud"><h4>3.8.3 Baud Rate - mandatory if 'Mountpoint' is set</h4></p> 595 605 <p> 596 606 Select a 'Baud rate' for the serial link. Note that using a high baud rate is recommended. 597 607 </p> 598 608 599 <p><a name="serparity"><h4>3. 9.4 Parity - mandatory if 'Mountpoint' is set</h4></p>609 <p><a name="serparity"><h4>3.8.4 Parity - mandatory if 'Mountpoint' is set</h4></p> 600 610 <p> 601 611 Select the 'Parity' for the serial link. Note that parity is often set to 'NONE'. 602 612 </p> 603 613 604 <p><a name="serdata"><h4>3. 9.5 Data Bits - mandatory if 'Mountpoint' is set</h4></p>614 <p><a name="serdata"><h4>3.8.5 Data Bits - mandatory if 'Mountpoint' is set</h4></p> 605 615 <p> 606 616 Select the number of 'Data bits' for the serial link. Note that often '8' data bits are used. 607 617 </p> 608 618 609 <p><a name="serstop"><h4>3. 9.6 Stop Bits - mandatory if 'Mountpoint' is set</h4></p>619 <p><a name="serstop"><h4>3.8.6 Stop Bits - mandatory if 'Mountpoint' is set</h4></p> 610 620 <p> 611 621 Select the number of 'Stop bits' for the serial link. Note that often '1' stop bit is used. 612 622 </p> 613 623 614 <p><a name="serauto"><h4>3. 9.7 NMEA - mandatory for VRS streams</h4></p>624 <p><a name="serauto"><h4>3.8.7 NMEA - mandatory for VRS streams</h4></p> 615 625 <p> 616 626 Select 'Auto' to automatically forward all NMEA-GGA messages coming from your serial connected device to the NTRIP broadcaster and/or save them in a file. … … 623 633 </p> 624 634 625 <p><a name="serfile"><h4>3. 9.8 File - optional if 'Auto' NMEA is set</h4></p>635 <p><a name="serfile"><h4>3.8.8 File - optional if 'Auto' NMEA is set</h4></p> 626 636 <p>Specify the full path to a file where NMEA messages coming from your serial connected device are saved. 627 637 </p> 628 <p><a name="serheight"><h4>3. 9.9 Height - mandatory if 'Manual' NMEA is set</h4></p>638 <p><a name="serheight"><h4>3.8.9 Height - mandatory if 'Manual' NMEA is set</h4></p> 629 639 <p> 630 640 Specify an approximate 'Height' above mean sea level in meter for your VRS to simulate an inital NMEA-GGA message. Latitude and longitude for that (editable) are taken from the broadcaster's source-table. … … 634 644 </p> 635 645 636 <p><a name="advnote"><h4>3. 10. Outages</h4></p>646 <p><a name="advnote"><h4>3.9. Outages</h4></p> 637 647 638 648 <p> … … 649 659 </p> 650 660 651 <p><a name="obsrate"><h4>3. 10.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', and 'Script' is set</h4></p>661 <p><a name="obsrate"><h4>3.9.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', and 'Script' is set</h4></p> 652 662 <p> 653 663 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. 654 664 </p> 655 665 656 <p><a name="advfail"><h4>3. 10.2 Failure Threshold - optional</h4></p>666 <p><a name="advfail"><h4>3.9.2 Failure Threshold - optional</h4></p> 657 667 <p> 658 668 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. … … 662 672 </p> 663 673 664 <p><a name="advreco"><h4>3. 10.3 Recovery Threshold - optional</h4></p>674 <p><a name="advreco"><h4>3.9.3 Recovery Threshold - optional</h4></p> 665 675 <p> 666 676 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. … … 670 680 </p> 671 681 672 <p><a name="advscript"><h4>3. 10.4 Script - optional </h4></p>682 <p><a name="advscript"><h4>3.9.4 Script - optional </h4></p> 673 683 <p> 674 684 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 stream's 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/Mac systems) together with date and time information. … … 699 709 </p> 700 710 701 <p><a name="misc"><h4>3.1 1. Miscellaneous</h4></p>711 <p><a name="misc"><h4>3.10. Miscellaneous</h4></p> 702 712 <p> 703 713 This section describes a number of miscellaneous options which can be applied for a single stream (mountpoint) or for all configured streams. 704 714 </p> 705 715 706 <p><a name="miscmount"><h4>3.1 1.1 Mountpoint - optional </h4></p>716 <p><a name="miscmount"><h4>3.10.1 Mountpoint - optional </h4></p> 707 717 <p> 708 718 Specify a mountpoint to apply one or several of the 'Miscellaneous' options to the corresponding stream. Enter 'ALL' if you want to apply these options to all configured streams. An empty option field (default) means that you don't want BNC to apply any of these options. 709 719 </p> 710 720 711 <p><a name="miscperf"><h4>3.1 1.2 Log Latency - optional </h4></p>721 <p><a name="miscperf"><h4>3.10.2 Log Latency - optional </h4></p> 712 722 <p> 713 723 BNC can average 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 or correction to Broadcast Ephemeris per second. Note that computing correct latencies requires the clock of the host computer to be properly synchronized. … … 737 747 738 748 739 <p><a name="miscscan"><h4>3.1 1.3 Scan RTCM - optional</h4></p>749 <p><a name="miscscan"><h4>3.10.3 Scan RTCM - optional</h4></p> 740 750 <p> 741 751 When configuring a GNSS receiver for RTCM stream generation, the setup interface may not provide details about RTCM message types. As reliable information concerning stream contents should be available i.e. for NTRIP broadcaster operators to maintain the broadcaster's source-table, BNC allows to scan RTCM streams for incoming message types and printout some of the contained meta-data. The idea for this option arose from 'InspectRTCM', a comprehensive stream analyzing tool written by D. Stoecker. … … 763 773 </p> 764 774 765 <p><a name="streams"><h4>3.1 2. Streams</h4></p>775 <p><a name="streams"><h4>3.11. Streams</h4></p> 766 776 <p> 767 777 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 streams and their 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. … … 783 793 </table> 784 794 795 <p><a name="streamedit"><h4>3.11.1 Edit Streams</h4></p> 796 <ul> 797 <li> 798 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'. 799 </li> 800 <li> 801 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 streams 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. 802 </li> 803 <li> 804 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. VRS streams are indicated by a 'yes' in the source-table as well as in the 'nmea' column on the 'Streams' canvas in BNC's main window. They are customized exactly to the latitude and longitude transmitted to the NTRIP broadcaster via NMEA-GGA messages. 805 <br>If NMEA-GGA messages are not coming from a serial connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'long' columns on the 'Streams' canvas. However, in most cases you would probably want to change these defaults 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 streams with a 'yes' in their 'nmea' column can be edited. The position must preferably be a point within the VRS 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. 806 <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. 807 </li> 808 </ul> 809 810 <p><a name="streamdelete"><h4>3.11.2 Delete Streams</h4></p> 811 <p> 812 To remove a stream from the 'Streams' canvas in the main window, highlight it by clicking on it and hit the 'Delete Streams' button. You can also remove multiple streams simultaneously by highlighting them using +Shift and +Ctrl.</p> 813 814 <p><a name="streamconf"><h4>3.11.3 Reconfigure Streams On-the-fly</h4></p> 815 <p> 816 The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process. 817 </p> 818 <p> 819 <u>Window mode:</u> Hit 'Save & Activate Options' while BNC is in window mode and already processing data to let changes of your streams selection immediately become effective. 820 <p> 821 <u>No window mode:</u> When operating BNC online in 'no window' mode (command line option -nw), you force BNC to reread its 'mountPoints' configuration option from disk at pre-defined intervals. Select '1 min', '1 hour', or '1 day' as 'Reread configuration' option to reread the 'mountPoints' option every full minute, hour, or day. This lets a 'mountPoints' option edited in between in the configuration file become effective without terminating uninvolved threads. See annexed section 'Configuration Example' for a configuration file example and a list of other on-the-fly changeable options. 822 </p> 823 824 825 <p><a name="bottom"><h4>3.12. Bottom Menu Bar</h4></p> 826 <p> 827 The bottom menu bar allows to add or delete streams to BNC's configuration and to start or stop it. 828 </p> 829 785 830 <p><a name="streamadd"><h4>3.12.1 Add Streams - Coming from Caster</h4></p> 786 831 <p> … … 788 833 </p> 789 834 790 <p><a name="streamhost"><h4>3.12. 2Caster Host and Port - mandatory</h4></p>835 <p><a name="streamhost"><h4>3.12.1.1 Caster Host and Port - mandatory</h4></p> 791 836 <p> 792 837 Enter the NTRIP broadcaster host IP and port number. Note that EUREF and IGS operate NTRIP broadcasters at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u>. 793 838 </p> 794 839 795 <p><a name="streamtable"><h4>3.12. 3Caster Table - optional</h4></p>840 <p><a name="streamtable"><h4>3.12.1.2 Caster Table - optional</h4></p> 796 841 <p> 797 842 It may be that your are not sure about your NTRIP broadcasters host and port number or you are interested in other broadcaster installations operated elsewhere. Hit 'Show' for a table of known broadcasters maintained at <u>www.rtcm-ntrip.org/home</u>. A window opens which allows to select a broadcaster for stream retrieval. 798 843 </p> 799 844 800 <p><a name="streamuser"><h4>3.12. 4User and Password - mandatory for protected streams</h4></p>845 <p><a name="streamuser"><h4>3.12.1.3 User and Password - mandatory for protected streams</h4></p> 801 846 <p> 802 847 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>. 803 848 </p> 804 849 805 <p><a name=" streamtable"><h4>3.12.5Get Table</h4></p>850 <p><a name="gettable"><h4>3.12.1.4 Get Table</h4></p> 806 851 <p> 807 852 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 or 20 and 21 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. … … 814 859 </p> 815 860 816 <p><a name=" streamntrip"><h4>3.12.6NTRIP Version - mandatory</h4></p>861 <p><a name="ntripv"><h4>3.12.1.5 NTRIP Version - mandatory</h4></p> 817 862 <p> 818 863 Some limitations and deficiencies of the NTRIP version 1 stream transport protocol are solved in NTRIP version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Version 2 is backwards compatible to Version 1. Options implemented in BNC are: … … 834 879 </p> 835 880 836 <p><a name="streamdelete"><h4>3.12.7 Delete Streams</h4></p> 837 <p> 838 To remove a stream from the 'Streams' canvas in the main window, highlight it by clicking on it and hit the 'Delete Streams' button. You can also remove multiple streams simultaneously by highlighting them using +Shift and +Ctrl.</p> 839 840 <p><a name="streamedit"><h4>3.12.8 Edit Streams</h4></p> 841 <ul> 842 <li> 843 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'. 844 </li> 845 <li> 846 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 streams 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. 847 </li> 848 <li> 849 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. VRS streams are indicated by a 'yes' in the source-table as well as in the 'nmea' column on the 'Streams' canvas in BNC's main window. They are customized exactly to the latitude and longitude transmitted to the NTRIP broadcaster via NMEA-GGA messages. 850 <br>If NMEA-GGA messages are not coming from a serial connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'long' columns on the 'Streams' canvas. However, in most cases you would probably want to change these defaults 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 streams with a 'yes' in their 'nmea' column can be edited. The position must preferably be a point within the VRS 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. 851 <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. 852 </li> 853 </ul> 854 855 <p><a name="streamconf"><h4>3.12.9 Reconfigure Streams On-the-fly</h4></p> 856 <p> 857 The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process. 858 </p> 859 <p> 860 <u>Window mode:</u> Hit 'Save & Activate Options' while BNC is in window mode and already processing data to let changes of your streams selection immediately become effective. 861 <p> 862 <u>No window mode:</u> When operating BNC online in 'no window' mode (command line option -nw), you force BNC to reread its 'mountPoints' configuration option from disk at pre-defined intervals. Select '1 min', '1 hour', or '1 day' as 'Reread configuration' option to reread the 'mountPoints' option every full minute, hour, or day. This lets a 'mountPoints' option edited in between in the configuration file become effective without terminating uninvolved threads. See annexed section 'Configuration Example' for a configuration file example and a list of other on-the-fly changeable options. 863 </p> 864 865 <p><a name="streamip"><h4>3.12.10 Add Streams - Coming from TCP/IP Port</h4></p> 881 <p><a name="streamip"><h4>3.12.2 Add Streams - Coming from TCP/IP Port</h4></p> 866 882 <p> 867 883 Button 'Add Streams' > 'Coming from TCP/IP Port' allows to retrieve streams via TCP directly from an IP address without using the NTRIP transport protocol. For that you: … … 882 898 </p> 883 899 884 <p><a name="start"><h4>3.1 3.Start</h4></p>900 <p><a name="start"><h4>3.12.3 Start</h4></p> 885 901 <p> 886 902 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. 887 903 </p> 888 904 889 <p><a name="stop"><h4>3.1 4.Stop</h4></p>905 <p><a name="stop"><h4>3.12.4 Stop</h4></p> 890 906 <p> 891 907 Hit the 'Stop' button in order to stop BNC. 892 908 </p> 893 909 894 <p><a name="cmd"><h4>3.1 5. Command Line Options</h4></p>910 <p><a name="cmd"><h4>3.13. Command Line Options</h4></p> 895 911 <p> 896 912 Command line options are available to run BNC in 'no window' mode or let it read data from a file in offline mode. BNC will then use processing options from the configuration file. Note that the self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration file name instead of using the default name 'BNC.ini'. 897 913 </p> 898 914 899 <p><a name="nw"><h4>3.1 5.1 No Window Mode - optional</h4></p>915 <p><a name="nw"><h4>3.13.1 No Window Mode - optional</h4></p> 900 916 <p> 901 917 Apart from its regular windows mode, BNC can be started on all systems as a background/batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file on disk. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems. … … 906 922 </p> 907 923 908 <p><a name="post"><h4>3.1 5.2 Offline Mode - optional</h4></p>924 <p><a name="post"><h4>3.13.2 Offline Mode - optional</h4></p> 909 925 <p> 910 926 Although BNC is primarily a real-time online tool, it can be run in offline mode to read data from a file for post processing purposes. Enter the following four command line options for that: … … 925 941 </p> 926 942 927 <p><a name="conffile"><h4>3.1 5.3 Configuration File - optional</h4></p>943 <p><a name="conffile"><h4>3.13.3 Configuration File - optional</h4></p> 928 944 The default configuration file name is 'BNC.ini'. You may change this name at startup time using the command line option '--conf <<u>confFileName</u>>'. This allows to run several BNC jobs in parallel on the same host using different sets of configuration options. <u>confFileName</u> stands either for the full path to a configuration file or just for a file name. If you introduce only a filename, the corresponding file will be saved in the current working directory from where BNC is started. 929 945 </p>
Note:
See TracChangeset
for help on using the changeset viewer.
