Changeset 175 in ntrip
- Timestamp:
- Sep 14, 2006, 6:47:22 PM (18 years ago)
- Location:
- trunk/BNC
- Files:
-
- 2 edited
-
bncabout.html (modified) (1 diff)
-
bnchelp.html (modified) (23 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bncabout.html
r173 r175 15 15 <br> 16 16 This software is provided 'as is'.<br> 17 Make sure you installed the latest version available from :<br>17 Make sure you installed the latest version available from<br> 18 18 <u>http://igs.bkg.bund.de/index_ntrip_down.htm</u><br> 19 19 <br> -
trunk/BNC/bnchelp.html
r173 r175 8 8 <p> 9 9 <h3>Contents</h3> 10 <h4><a href=#purpose>A - Purpose<br> 10 <h4> 11 <a href=#purpose>A - Purpose<br> 11 12 <a href=#options>B - Options<br> 12 13 <a href=#limits>C - Limitations<br> 13 14 <a href=#authors>D - Authors<br> 14 <a href=#annex>E - Annex</h4> 15 <a href=#annex>E - Annex<br> 16 </h4> 15 17 </p> 16 18 <br> … … 30 32 <ul> 31 33 <li> RTCM <a href=#rtcm2>Version 2.x</a> Format containing message types 18 and 19, </li> 32 <li> RTCM <a href=#rtcm3>Version 3</a> Format containing message types 1001, 1002, 1003, and 1004, and</li>34 <li> RTCM <a href=#rtcm3>Version 3</a> Format containing message types 1001, 1002, 1003, and 1004,</li> 33 35 <li> <a href=#rtigs>RTIGS</a> Format.</li> 34 36 </ul> … … 36 38 37 39 <p> 38 BNC is available for Windows, Linux, and Solari xsystems. It has been developed under GNU General Public License.40 BNC is available for Windows, Linux, and Solaris systems. It has been developed under GNU General Public License. 39 41 </p> 40 42 … … 97 99 <li> 98 100 Help Contents.<br> 99 You may keep the 'Help Conten s' window open while setting BNC options.101 You may keep the 'Help Contents' window open while setting BNC options. 100 102 </li> 101 103 </ul> … … 106 108 107 109 <p> 108 You may like to run BNC on a host in a Local Area Network (LAN). LAN's are often protected by a proxy server. Enter your proxy server IP and port number in case one is operated in front of you. In case you don't know the IP and port of your proxy server, check out the proxy server settings of your Windows browser or ask your network administ ator.</p>109 <p> 110 Note that IP-streaming may be generally denied in a LAN. In such a case you need to contact your network administ ator for an appropriate modification of your security policy or the installation of a TCP relay to involved NTRIP broadcasters. If that doesn't work out, run BNC on a host that is connected to the Internet through an Internet Service Provider (ISP).110 You may like to run BNC on a host in a Local Area Network (LAN). LAN's are often protected by a proxy server. Enter your proxy server IP and port number in case one is operated in front of you. In case you don't know the IP and port of your proxy server, check out the proxy server settings of your Windows browser or ask your network administrator.</p> 111 <p> 112 Note that IP-streaming may be generally denied in a LAN. In such a case you need to contact your network administrator for an appropriate modification of your security policy or the installation of a TCP relay to involved NTRIP broadcasters. If that doesn't work out, run BNC on a host that is connected to the Internet through an Internet Service Provider (ISP). 111 113 </p> 112 114 … … 120 122 <p><h4>B - 4.1 Wait for Full Epoch</h4></p> 121 123 <p> 122 When feeding a real-time GNSS engine waiting for input epoch by epoch, BNC ignores whatever is received later n then 'Wait for full epoch' seconds. A value of 2 to 5 seconds may be an appropriate choise for that, depending on the delay you can accept for your real-time product. Note that 'Wait for full epoch' does not influence the RINEX file contents. Observations coming in later than 'Wait for full epoch' will still be included there.124 When feeding a real-time GNSS engine waiting for input epoch by epoch, BNC ignores whatever is received later then 'Wait for full epoch' seconds. A value of 2 to 5 seconds may be an appropriate choice for that, depending on the delay you can accept for your real-time product. Note that 'Wait for full epoch' does not influence the RINEX file contents. Observations coming in later than 'Wait for full epoch' will still be included there. 123 125 </p> 124 126 … … 132 134 <p><h4>B - 4.3 Port for Binary Output</h4></p> 133 135 <p> 134 BNC outputs synchronized observations in a binary format through an IP port with the following format: ..... Sou ce code of an example program 'test_bnc.cpp' that reads the binary data to feed real-time GNSS applications is available.136 BNC outputs synchronized observations in a binary format through an IP port with the following format: ..... Source code of an example program 'test_bnc.cpp' that reads the binary data to feed real-time GNSS applications is available. 135 137 </p> 136 138 … … 140 142 Observations are converted to RINEX format version 2.1. Note that RINEX file names are derived by BNC from the first 4 characters of the corresponding mountpoint (4Char Station ID). Thus, retrieving data from mounpoints FFMJ1 and KARL0 leads to RINEX files named FFMJ*.* and KARL*.*.</p> 141 143 <p> 142 In case you retrieve str aeams that show mountpoints with an identical 4Char Station ID, the full mountpoint string will become part of the RINEX file name. Example: When simultaneously retrieving mountpoints FFMJ1 and FFMJ3, there RINEX file names will be FFMJ*_1.* and FFMJ*_3.*.144 In case you retrieve streams that show mountpoints with an identical 4Char Station ID, the full mountpoint string will become part of the RINEX file name. Example: When simultaneously retrieving mountpoints FFMJ1 and FFMJ3, there RINEX file names will be FFMJ*_1.* and FFMJ*_3.*. 143 145 </p> 144 146 … … 152 154 <p><h4>B - 5.2 RINEX Script</h4></p> 153 155 <p> 154 Whenever a RINEX file is generated, you may like to compress, copy, or upload it immediately. For that you enter the full path of a script or ba ch file carrying out these operations. The RINEX file name will be passed to the script as a command line parameter. Note the following example for a 'RINEX Script' file: ${HOME}/upload_script156 Whenever a RINEX file is generated, you may like to compress, copy, or upload it immediately. For that you enter the full path of a script or batch file carrying out these operations. The RINEX file name will be passed to the script as a command line parameter. Note the following example for a 'RINEX Script' file: ${HOME}/upload_script 155 157 </p> 156 158 … … 179 181 </li> 180 182 <li> 181 Concerning RTCM Version 3 streams: If the ambiguity field is not set, the output will be no valid RINEX. All values will be stored modulo 299792.458. A COMMENT line will tell you, when this happens. It would be necessary to approximately calculate the range to fix the ambiguity (needing ephemeris/al amanac and easy positioning algorithm).183 Concerning RTCM Version 3 streams: If the ambiguity field is not set, the output will be no valid RINEX. All values will be stored modulo 299792.458. A COMMENT line will tell you, when this happens. It would be necessary to approximately calculate the range to fix the ambiguity (needing ephemeris/almanac and easy positioning algorithm). 182 184 </li> 183 185 </ul> … … 185 187 </p> 186 188 <p> 187 Example: Moutpoints FFMJ1 and KARL0 lead to the generation of RINEX files FFMJ*.* and KARL*.*. The header part of these files would be overwritten by the content of the skeleton files FFMJ.skl and KARL.skl in case 'RINEX skelet ion extension"is set to 'skl' .189 Example: Moutpoints FFMJ1 and KARL0 lead to the generation of RINEX files FFMJ*.* and KARL*.*. The header part of these files would be overwritten by the content of the skeleton files FFMJ.skl and KARL.skl in case 'RINEX skeleton extensionis set to 'skl' . 188 190 </p> 189 191 … … 197 199 <p><h4>B - 6.1 Add Mountpoints</h4></p> 198 200 <p> 199 Button e'Add Mountpoints' opens a window that lets you select data streams by their mountpoint.201 Button 'Add Mountpoints' opens a window that lets you select data streams by their mountpoint. 200 202 </p> 201 203 … … 221 223 <p><h4>B - 7. Delete Mountpoints</h4></p> 222 224 <p> 223 To delete a stream shown under 'Mountpoints' in BNC's main windows select it by mouse click and hit 'Delete Mountpoints'. You may tag more than one stream for simultaneous del ition through using +Shift and +Strg.</p>224 <p> 225 BNC automatically select es the decoder for a stream based on the 'format' and 'format-details' given in the sourcetable. It may happen that you need to overrule this decoder selection because of sourcetable setup deficiencies. Therefore BNC allows to edit the decoder part for each stream shown under 'Mountpoints'. Accepted decoder strings are are 'RTCM 2.x', 'RTCM 3', and 'RTIGS'.225 To delete a stream shown under 'Mountpoints' in BNC's main windows select it by mouse click and hit 'Delete Mountpoints'. You may tag more than one stream for simultaneous deletion through using +Shift and +Strg.</p> 226 <p> 227 BNC automatically selects the decoder for a stream based on the 'format' and 'format-details' given in the sourcetable. It may happen that you need to overrule this decoder selection because of sourcetable setup deficiencies. Therefore BNC allows to edit the decoder part for each stream shown under 'Mountpoints'. Accepted decoder strings are are 'RTCM 2.x', 'RTCM 3', and 'RTIGS'. 226 228 </p> 227 229 … … 229 231 <p><h4>B - 8. Log File</h4></p> 230 232 <p> 231 BNC's comments its activities in the 'Log file' section on the main windows. All comments can be saved and concat inated in a file through entering the full path of 'Log file'. Information is given about the dialog with the NTRIP broadcaster as well as any problem that might occure concering communication, stream availability, stream delay, stream conversion etc.233 BNC's comments its activities in the 'Log file' section on the main windows. All comments can be saved and concatenated in a file through entering the full path of 'Log file'. Information is given about the dialog with the NTRIP broadcaster as well as any problem that might occur concerning communication, stream availability, stream delay, stream conversion etc. 232 234 </p> 233 235 <p> … … 264 266 <p><h3>D - Authors</h3></p> 265 267 <p> 266 Based on a Qt Graphic User In ferface (GUI) developed for BKG by Leos Mervart (TU Prague), BNC integrates the following already existing GNU GPL software components:268 Based on a Qt Graphic User Interface (GUI) developed for BKG by Leos Mervart (TU Prague), BNC integrates the following already existing GNU GPL software components: 267 269 <ul> 268 270 <li> RTCM 2.x decoder, written by John Sager with contributions from Carsten Becker (DLR)</li> … … 303 305 304 306 <p> 305 NTRIP is an RTCM standard designed for disseminating differential correction data (e.g in the RTCM-104 format) or other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC, Laptop, PDA, orreceiver connections to a broadcasting host. NTRIP supports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS.307 NTRIP is an RTCM standard designed for disseminating differential correction data (e.g in the RTCM-104 format) or other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC, Laptop, PDA, or receiver connections to a broadcasting host. NTRIP supports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS. 306 308 </p> 307 309 … … 316 318 <li>Application not limited to one particular plain or coded stream content; ability to distribute any kind of GNSS data.</li> 317 319 <li>Potential to support mass usage; disseminating hundreds of streams simultaneously for up to thousand users possible when applying modified Internet Radio broadcasting software.</li> 318 <li>Considering security needs; stream providers and users don't necessarily get into contact, streams often not blocked by firewalls or proxy servers protecting Local Area Networks.</li>320 <li>Considering security needs; stream providers and users don't necessarily get into contact, streams often not blocked by firewalls or proxy servers protecting Local Area Networks.</li> 319 321 <li>Enables streaming over any mobile IP network because of using TCP/IP.</li> 320 322 </ul> … … 328 330 </p> 329 331 330 <p>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. Note that BNC's 'Get Table' only shows STR records of a sourcetable. You may like to use a Windows bro swer to retrieve the full sourcetable content entering the URL http://host:port/dummy.332 <p>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. Note that BNC's 'Get Table' only shows STR records of a sourcetable. You may like to use a Windows browser to retrieve the full sourcetable content entering the URL http://host:port/dummy. 331 333 </p> 332 334 … … 352 354 </li> 353 355 <li> 354 T pye 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.356 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. 355 357 </li> 356 358 <li> … … 408 410 </li> 409 411 <li> 410 Type 1009 message carr es GLONASS L1 code and phase.412 Type 1009 message carries GLONASS L1 code and phase. 411 413 </li> 412 414 <li> … … 420 422 </li> 421 423 <li> 422 Type 1013 message carries Modified julian date, le ep second, configured message types and intervall.424 Type 1013 message carries Modified julian date, leap second, configured message types and interval. 423 425 </li> 424 426 <li> … … 442 444 <p><h4>E - 3. RTIGS</h4></p> 443 445 <p> 446 Input from by Ken? 444 447 </p> 445 448 … … 447 450 <p><h4>E - 3.1 SOC</h4></p> 448 451 <p> 449 </p> 452 Input from by Ken? 453 </p> 454
Note:
See TracChangeset
for help on using the changeset viewer.
