- Timestamp:
- Sep 18, 2006, 2:53:43 PM (18 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (14 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r175 r176 1 1 2 <a name="back_contents"> 2 3 <p><h3>BKG Ntrip Client (BNC)</h3></p> 3 4 4 5 <p> 5 The BKG Ntrip Client (BNC) is a program for simultaneously retrieving real-time GNSS data streams from NTRIP broadcasters like <a class="link" href="http://www.euref-ip.net/home"><u>www.euref-ip.net</u></a> or <a class="link" href="http://www.igs-ip.net/home"><u>www.igs-ip.net</u></a>. BNC has been developed within the framework of the EUREF-IP Pilot Project (EUREF-IP) and the Real-Time IGS Working Group (RTIGS). 6 The BKG Ntrip Client (BNC) is a program for simultaneously retrieving real-time GNSS data streams from NTRIP broadcasters like <u>http://www.euref-ip.net/home</u> or <u>http://www.igs-ip.net/home</u>. 7 </p> 8 <p> 9 BNC has been developed for the Federal Agency for Cartography and Geodesy (BKG) within the framework of the EUREF-IP Pilot Project (EUREF-IP) and the Real-Time IGS Working Group (RTIGS). 6 10 </p> 7 11 … … 9 13 <h3>Contents</h3> 10 14 <h4> 11 <a href=#purpose>A - Purpose<br> 12 <a href=#options>B - Options<br> 13 <a href=#limits>C - Limitations<br> 14 <a href=#authors>D - Authors<br> 15 <a href=#annex>E - Annex<br> 15 <a href=#purpose>A - Purpose</a><br> 16 <a href=#options>B - Options</a><br> 17 <a href=#limits>C - Limitations</a><br> 18 <a href=#authors>D - Authors</a><br> 19 <a href=#links>E - Links</a><br> 20 <a href=#annex>F - Annex</a><br> 16 21 </h4> 17 22 </p> … … 24 29 25 30 <ul> 26 <li>Generate high-rate RINEX files to feed near real-time post-processing applications, and/or</li> 27 <li>Output synchronize observations through an IP port to feed real-time applications.</li> 28 </ul> 29 <p> 30 BNC decodes and converts streams carrying phase data coming in 31 </p> 32 <ul> 33 <li> RTCM <a href=#rtcm2>Version 2.x</a> Format containing message types 18 and 19, </li> 34 <li> RTCM <a href=#rtcm3>Version 3</a> Format containing message types 1001, 1002, 1003, and 1004,</li> 35 <li> <a href=#rtigs>RTIGS</a> Format.</li> 36 </ul> 37 </p> 38 39 <p> 40 BNC is available for Windows, Linux, and Solaris systems. It has been developed under GNU General Public License. 41 </p> 42 43 <br> 31 <li>Retrieve real-time GNSS data streams available through NTRIP transport protocol,</li> 32 <li>Generate high-rate RINEX files to feed near real-time GNSS post-processing applications, and/or</li> 33 <li>Output synchronize observations through an IP port to feed real-time GNSS engines.</li> 34 </ul> 35 <p> 36 BNC decodes and converts GNSS data streams carrying phase data coming in 37 </p> 38 <ul> 39 <li>RTCM Version 2.x format containing message types 18 and 19, </li> 40 <li>RTCM Version 3 format containing message types 1001, 1002, 1003, and 1004,</li> 41 <li>RTIGS format.</li> 42 </ul> 43 </p> 44 45 <p> 46 BNC has been developed 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 are available. 47 [<a href=#back_contents>Back</a>]<br> 48 </p> 49 50 <br> 51 <a name="back_options"> 44 52 <a name="options"> 45 53 <p><h3>B - Options</h3></p> 46 < table>47 <tr><td>B - 1.</td><td><a href=#file>File</a></td>48 <tr><td>B - 2.</td><td><a href=#help>Help</a></td>49 <tr><td>B - 3.</td><td><a href=#proxy>Proxy</a></td>50 <tr><td>B - 4.</td><td><a href=#output>Synchronized Output</a></td>51 <tr><td></td><td>B - 4.1.</td><td><a href=#wait>Wait for Full Epoch</a></td>52 <tr><td></td><td>B - 4.2.</td><td><a href=#ascii>ASCII Output File</a></td>53 <tr><td></td><td>B - 4.3.</td><td><a href=#binary>Port for Binary Output</a></td>54 <tr><td>B - 5.</td><td><a href=#rinex>RINEX</a></td>55 <tr><td></td><td>B - 5.1.</td><td><a href=#rnxpath>RINEX Path</a></td>56 <tr><td></td><td>B - 5.2.</td><td><a href=#rnxscript>RINEX Script</a></td>57 <tr><td></td><td>B - 5.3.</td><td><a href=#rnxinterval>RINEX File Interval</a></td>58 <tr><td></td><td>B - 5.4.</td><td><a href=#rnxsample>RINEX Sampling</a></td>59 <tr><td></td><td>B - 5.5.</td><td><a href=#rnxskeleton>RINEX Skeleton Extension</a></td>60 <tr><td>B - 6.</td><td><a href=#mountpoints>Mountpoints</a></td>61 <tr><td></td><td>B - 6.1.</td><td><a href=#AddMounts>Add Mountpoints</a></td>62 <tr><td></td><td>B - 6.2.</td><td><a href=#HostPort>Broadcaster Host and Port</a></td>63 <tr><td></td><td>B - 6.3.</td><td><a href=#account>Broadcaster User and Password</a></td>64 <tr><td></td><td>B - 6.4.</td><td><a href=#GetTable>Get Table</a></td>65 <tr><td>B - 7.</td><td><a href=#delete>Delete Mountpoints</a></td>66 <tr><td>B - 8.</td><td><a href=#log>Log File</a></td>67 <tr><td>B - 9.</td><td><a href=#start>Start</a></td>68 <tr><td>B - 10.</td><td><a href=#stop>Stop</a></td>69 <tr><td>B - 11.</td><td><a href=#nw>No Window</a></td>70 </table>54 <p> 55 B - 1. <a href=#file>File</a><br> 56 B - 2. <a href=#help>Help</a><br> 57 B - 3. <a href=#proxy>Proxy</a><br> 58 B - 4. <a href=#output>Synchronized Output</a><br> 59 B - 4.1. <a href=#wait>Wait for Full Epoch</a><br> 60 B - 4.2. <a href=#ascii>ASCII Output File</a><br> 61 B - 4.3. <a href=#binary>Port for Binary Output</a><br> 62 B - 5. <a href=#rinex>RINEX</a><br> 63 B - 5.1. <a href=#rnxpath>RINEX Directory Path</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 - 6. <a href=#mountpoints>Mountpoints</a><br> 69 B - 6.1. <a href=#AddMounts>Add Mountpoints</a><br> 70 B - 6.2. <a href=#HostPort>Broadcaster Host and Port</a><br> 71 B - 6.3. <a href=#account>Broadcaster User and Password</a><br> 72 B - 6.4. <a href=#GetTable>Get Table</a><br> 73 B - 6.5. <a href=#delete>Delete Mountpoints</a><br> 74 B - 7. <a href=#log>Log File</a><br> 75 B - 8. <a href=#start>Start</a><br> 76 B - 9. <a href=#stop>Stop</a><br> 77 B - 10. <a href=#nw>No Window</a> 78 [<a href=#back_contents>Back</a>]<br> 71 79 </p> 72 80 … … 79 87 <li> 80 88 Select an appropriate font.<br> 81 Use a small font size in case the BNC window exceed the size of your screen.89 Use a small font size in case the BNC window exceeds the size of your screen. 82 90 </li> 83 91 <li> Save selected options.<br> 84 Note that on Windows systems options are saved in the registry file. On Linux and Solaris systems options are saved in ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. 92 Note that on Windows systems options are saved in registers. On UNIX/Linux systems options are saved in ${HOME}/.config/BKG/BKG_NTRIP_Client.conf. 93 </li> 94 <li> 95 Quit the execution of BNC. 96 [<a href=#back_options>Back</a>]<br> 85 97 </li> 86 98 </ul> … … 94 106 <ul> 95 107 <li> 96 General information 'About BNC'.<br>97 Close the 'About BNC' window to continu ingwith BNC.108 General information about BNC.<br> 109 Close the 'About BNC' window to continue with BNC. 98 110 </li> 99 111 <li> 100 Help Contents.<br>112 Help contents.<br> 101 113 You may keep the 'Help Contents' window open while setting BNC options. 114 [<a href=#back_options>Back</a>]<br> 102 115 </li> 103 116 </ul> … … 105 118 106 119 <a name="proxy"> 107 <p><h4>B - 3. Proxy</h4></p> 108 109 <p> 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). 120 <p><h4>B - 3. Proxy - mandatory if BNC is operated in a protected LAN</h4></p> 121 122 <p> 123 You may like to run BNC in a Local Area Network (LAN) environment. 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 BNC. If 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> 124 <p> 125 Note that IP streaming may be generally denied in a LAN. In such a case you need to request an appropriate modification of the security policy from your network administrator or ask for 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). 126 [<a href=#back_options>Back</a>]<br> 113 127 </p> 114 128 115 129 <a name="output"> <p><h4>B - 4. Synchronized Output</h4></p> 116 130 <p> 117 BNC lets you output synchronized observations epoch by epoch. This output is made available in binary format and in ASCII format. The output comprises the following observations -if available:</p>131 BNC lets you output synchronized observations epoch by epoch. This output is made available in ASCII format and in binary format. The output comprises the following observations if available:</p> 118 132 StatID, SVPRN, GPSWeek, GPSWeeks, sec, C1, P2, L1, L2, SNR1, SNR2, pCodeIndicator, cumuLossOfCont. 133 [<a href=#back_options>Back</a>]<br> 119 134 </p> 120 135 121 136 <a name="wait"> 122 <p><h4>B - 4.1 Wait for Full Epoch</h4></p> 123 <p> 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. 137 <p><h4>B - 4.1 Wait for Full Epoch - optional</h4></p> 138 <p> 139 When feeding a real-time GNSS engine waiting for input from BNC 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. Default value for 'Wait for full ecpch' is zero '0', meaning that no synchronized output is generated. 140 </p> 141 <p> 142 Note that 'Wait for full epoch' does not influence the RINEX file contents. Observations received later than 'Wait for full epoch' seconds will still be included in the RINEX files. 143 [<a href=#back_options>Back</a>]<br> 125 144 </p> 126 145 127 146 <a name="ascii"> 128 <p><h4>B - 4.2 ASCII Output File</h4></p> 129 <p> 130 BNC lets you save synchronized observations in plain ASCII format in a file. Enter a full path for that file. 147 <p><h4>B - 4.2 ASCII Output File - optional</h4></p> 148 <p> 149 Enter the full path for a file to save synchronized observations in plain ASCII format. Default value is an empty option field, meaning that no ASCII output file is generated. 150 [<a href=#back_options>Back</a>]<br> 131 151 </p> 132 152 133 153 <a name="binary"> 134 <p><h4>B - 4.3 Port for Binary Output</h4></p> 135 <p> 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. 154 <p><h4>B - 4.3 Port for Binary Output - optional</h4></p> 155 <p> 156 BNC makes synchronized observations available in a binary format through an IP port. Enter the port number to activate this function. Default is an empty option field, meaning that no binary output is generated. 157 </p> 158 <p>The binary output is provided in the following format:<br> 159 Input from Leos? 160 [<a href=#back_options>Back</a>]<br> 137 161 </p> 138 162 … … 140 164 <p><h4>B - 5. RINEX</h4></p> 141 165 <p> 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> 143 <p> 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.*. 166 Observations are converted to RINEX Version 2.1. RINEX file names are derived by BNC from the first 4 characters of the corresponding mountpoint (4Char Station ID) while truncating the residual part of the mountpoint string. Thus, retrieving data from mountpoints FRANKFURT and WETTZELL leads to RINEX files named FRAN*.* and WETT*.*.</p> 167 <p> 168 In case you retrieve streams that show mountpoints with an identical 4Char Station ID (same first 4 characters), the mountpoint string is split in two sub-strings and both become part of the RINEX file name. Example: When simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, there RINEX file names are defined as FRAN*_KFURT.* and FRAN*_CE.*. 169 [<a href=#back_options>Back</a>]<br> 145 170 </p> 146 171 147 172 <a name="rnxpath"> 148 <p><h4>B - 5.1 RINEX Directory Path</h4></p> 149 <p> 150 Enther a path for saving the RINEX files in a directory. If this directory does not exist, BNC will not store these files. 173 <p><h4>B - 5.1 RINEX Directory Path - optional</h4></p> 174 <p> 175 Enter a path for saving the RINEX files in a directory. If this directory does not exist, BNC will not generate RINEX files. Default value for 'RINEX directory path' is an empty option field, meaning that streams are not converted to RINEX. 176 [<a href=#back_options>Back</a>]<br> 151 177 </p> 152 178 … … 154 180 <p><h4>B - 5.2 RINEX Script</h4></p> 155 181 <p> 156 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 182 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. 183 [<a href=#back_options>Back</a>]<br> 157 184 </p> 158 185 159 186 <a name="rnxinterval"> 160 <p><h4>B - 5.3 RINEX File Interval</h4></p> 161 <p> 162 Enter the interval for the RINEX file generation. Available options are 2 min, 5 min, 10 min, 15 min, 20 min, 30 min, 1 hour, or 1 day. 187 <p><h4>B - 5.3 RINEX File Interval - mandatory if 'RINEX directory path' set</h4></p> 188 <p> 189 Select the interval for RINEX file generation. Default for 'RINEX file interval' is 15 minutes. 190 [<a href=#back_options>Back</a>]<br> 163 191 </p> 164 192 165 193 <a name="rnxsample"> 166 <p><h4>B - 5.4 RINEX Sample Interval</h4></p> 167 <p> 168 Select the RINEX sample interval. Zero '0' stands for converting all incoming epochs to RINEX. 194 <p><h4>B - 5.4 RINEX Sampling - mandatory if 'RINEX directory path' set </h4></p> 195 <p> 196 Select the RINEX sample interval in seconds. Zero '0' stands for converting all incoming epochs to RINEX. Default for 'RINEX sampling' is '0'. 197 [<a href=#back_options>Back</a>]<br> 169 198 </p> 170 199 171 200 <a name="rnxskeleton"> 172 <p><h4>B - 5.5 RINEX Skeleton Extension</h4></p> 173 <p> 174 The generated RINEX is somewhat limited due to the streaming character of the conversion. 175 <ul> 176 <li> 177 Header records can only represent data, which is known after receiving the very first epoch. Data rate, position, number of observations and any such additional fields cannot be provided. 178 </li> 179 <li> 180 The number of observables cannot change during the program runtime. Only the observables, which exist in the first epoch are outputted. If there are new observables later on, these are ignored. 181 </li> 182 <li> 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). 184 </li> 185 </ul> 186 To overcome the problem BNC lets you introduce RINEX skeleton files that contain the header records you would like to see instead of the default header. You may like to derive RINEX skeleton files from the information given in sitelogs. Any file in the 'RINEX Directory Path' with the 'RINEX skeleton extension' is understood by BNC as a RINEX skeleton file. 187 </p> 188 <p> 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' . 201 <p><h4>B - 5.5 RINEX Skeleton Extension - optional</h4></p> 202 <p> 203 BNC lets you introduce RINEX skeleton files that contain the header records you would like to see instead of a default header. You may like to derive RINEX skeleton files from the information given in sitelogs. A file in the 'RINEX directory path' with the 'RINEX skeleton extension' is understood by BNC as a RINEX skeleton file for the affected stream. 204 </p> 205 <p> 206 Example: Mountpoint FRAN0 leads to the generation of RINEX files FRAN*.*. The header part of this files would be overwritten by the content of an existing skeleton file FRAN.skl in case 'RINEX skeleton extension' is set to 'skl' . 207 [<a href=#back_options>Back</a>]<br> 190 208 </p> 191 209 … … 193 211 <p><h4>B - 6. Mountpoints</h4></p> 194 212 <p> 195 Each stream on an NTRIP broadcaster is defined through a unique source ID called mountpoint. An NTRIP client can access the data of a desired stream by its mountpoint. Information about mountpoints as available through a sourcetable maintained by the NTRIP broadcaster. 213 Each stream on an NTRIP broadcaster is defined through a unique source ID called mountpoint. An NTRIP client like BNC can access the data of a desired stream by its mountpoint. Information about mountpoints is available through the sourcetable maintained by the NTRIP broadcaster. 214 [<a href=#back_options>Back</a>]<br> 196 215 </p> 197 216 … … 199 218 <p><h4>B - 6.1 Add Mountpoints</h4></p> 200 219 <p> 201 Button 'Add Mountpoints' opens a window that lets you select data streams by their mountpoint. 220 Button 'Add Mountpoints' opens a window that lets you select data streams by their mountpoints. 221 [<a href=#back_options>Back</a>]<br> 202 222 </p> 203 223 204 224 <a name="HostPort"> 205 <p><h4>B - 6.2 Broadcaster Host and Port</h4></p> 206 <p> 207 Enter the NTRIP broadcaster host IP and port number. http://www.rtcm-ntrip.org/home provides information about known NTRIP broadcaster installations. Note that EUREF and IGS maintains NTRIP broadcasters at http://www.euref-ip.net/home and http://www.igs-ip.net/home. 225 <p><h4>B - 6.2 Broadcaster Host and Port - mandatory</h4></p> 226 <p> 227 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>. 228 [<a href=#back_options>Back</a>]<br> 208 229 </p> 209 230 210 231 <a name="account"> 211 <p><h4>B - 6.3 Broadcaster User and Password</h4></p> 212 <p> 213 Enter the User and Password for access to NTRIP broadcaster streams. Note that usually account information is provided per NTRIP broadcaster through a registration procedure. Register for access to protected streams on www.euref-ip.net and www.igs-ip.net through http://igs.bkg.bund.de/index_ntrip_reg.htm. 232 <p><h4>B - 6.3 Broadcaster User and Password - mandatory for protected streams</h4></p> 233 <p> 234 Streams on NTRIP broadcasters may be password protected. Enter a valid User ID and Password for access to protected NTRIP broadcaster 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>. 235 [<a href=#back_options>Back</a>]<br> 214 236 </p> 215 237 … … 217 239 <p><h4>B - 6.4 Get Table</h4></p> 218 240 <p> 219 Hit button 'Get Table' to request a sourcetable from the NTRIP broadcaster. Various data fields of the sourcetable will be shown. Pay attention to data fields 'format' and 'format-details'. Remember that BNC can only decode and convert streams that come in RTCM 2.x, RTCM 3, or RTIGS format. RTCM 2.x streams must carry message types 18 and 19 while RTCM 3 streams must carry message type 1004, see data field 'format-details'. Select your streams line by line, use +Shift and +Strg when necessary. Hit 'OK' to return to BNC's main window. 241 Hit button 'Get Table' to download a sourcetable from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Remember 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 message types 1001 or 1003, better 1003 or 1004, 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. Hit 'OK' to return to the main window. 242 [<a href=#back_options>Back</a>]<br> 220 243 </p> 221 244 222 245 <a name="delete"> 223 <p><h4>B - 7. Delete Mountpoints</h4></p> 224 <p> 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'. 246 <p><h4>B - 6.5 Delete Mountpoints</h4></p> 247 <p> 248 To delete a stream shown under 'Mountpoints' in the main window select it by mouse click and then hit 'Delete Mountpoints'. For simultaneous deletion of several streams single them out through using +Shift and +Ctrl.</p> 249 <p> 250 BNC automatically selects one out of several internal decoders for a stream based on its 'format' and 'format-details' as given in the sourcetable. It may happen that you need to overrule the automated decoder selection because of sourcetable setup deficiencies. Therefore BNC allows to edit the decoder part for each stream shown under 'Mountpoints'. Accepted decoder strings allowed to be introduced are 'RTCM_2.x', 'RTCM_3', and 'RTIGS'. 251 [<a href=#back_options>Back</a>]<br> 228 252 </p> 229 253 230 254 <a name="log"> 231 <p><h4>B - 8. Log File</h4></p> 232 <p> 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. 234 </p> 235 <p> 236 Note that a connection to the NTRIP broadcaster may break or a stream requested may be temporarily unavailable. When this happens, a reconnect is tried with decreasing frequency. BNC frst tries to reconnect with 1 second delay, if unsuccessful, tries again in 2 seconds from the last attempt, if still unsuccessful tries with 4 seconds from the last attempt etc. Each attempt doubles the delay from the previous attempt. The maximum delay between attempts is limited to 60 seconds. The reconnection process is documented in 'Log File'. 255 <p><h4>B - 7. Log File - optional</h4></p> 256 <p> 257 BNC's comments its activities in the 'Log file' section on the main windows. Comments can be saved and concatenated in a file when entering a full path for 'Log file'. Information is given about the communication between BNC and the NTRIP broadcaster as well as about problems that occur concerning communication link, stream availability, stream delay, stream conversion etc. Default value for 'Log file' is an empty option field, meaning that BNC's comments are not saved in a file. 258 </p> 259 <p> 260 Note that a connection to the NTRIP broadcaster may break or a stream requested may be temporarily unavailable. When this happens, a reconnect is tried with decreasing frequency. BNC first tries to reconnect with 1 second delay, if unsuccessful, tries again in 2 seconds from the last attempt, if still unsuccessful tries with 4 seconds from the last attempt etc. Each attempt doubles the delay from the previous attempt. The maximum delay between attempts is limited to 60 seconds. The reconnection process is documented in 'Log file'. 261 [<a href=#back_options>Back</a>]<br> 237 262 </p> 238 263 239 264 <a name="start"> 240 <p><h4>B - 9. Start</h4></p> 241 <p> 242 Hit 'Start' to start retrieving, decodeing and converting GNSS data streams in real-time. 265 <p><h4>B - 8. Start</h4></p> 266 <p> 267 Hit 'Start' to start retrieving, decoding, and converting GNSS data streams in real-time. 268 [<a href=#back_options>Back</a>]<br> 243 269 </p> 244 270 245 271 <a name="stop"> 246 <p><h4>B - 10. Stop</h4></p> 247 <p> 248 Hit the 'Stop' button to terminate BNC. 272 <p><h4>B - 9. Stop</h4></p> 273 <p> 274 Hit the 'Stop' button to stop BNC. 275 [<a href=#back_options>Back</a>]<br> 249 276 </p> 250 277 251 278 <a name="nw"> 252 <p><h4>B - 11. No Window</h4></p> 253 <p> 254 On Linux und Solaris systems you may like to start BNC with the comman line option -nw. BNC will then start with 'No Window', reading configurations parameters from file ${HOME}/.config/BKG/BNC_NTRIP_Client.cfg or from the Windows registry file. 255 </p> 256 279 <p><h4>B - 10. No Window - optional</h4></p> 280 <p> 281 On UNIX/Linux systems you may like to use BNC with the command line option -nw. BNC then runs in 'no window' mode, reading options from the configuration file ${HOME}/.config/BKG/BNC_NTRIP_Client. 282 </p> 283 <p> 284 Note that the self-explaining contents of the configuration file can easily be edited and option -nw is not available under Windows. 285 [<a href=#back_options>Back</a>]<br> 286 </p> 257 287 <br> 258 288 <a name="limits"> 259 289 <p><h3>C - Limitations</h3></p> 260 <p> 261 So far BNC only handles GPS data while ignoring GLONASS and Galileo observations. Its current capacity is limited to process L1, L2, P1, and P2 observables. 262 </p> 263 290 <ul> 291 <li> 292 So far BNC only handles GPS data while ignoring GLONASS and Galileo observations. Furthermore, its function is limited today to processing L1, L2, P1, and P2 observations only. 293 </li> 294 <li> 295 Concerning RTCM Version 2.x, BNC handles only message types 18 and 19. Concerning RTCM Version 3, BNC handles only message types 1001, 1002, 1003, and 1004. 296 </li> 297 <li> 298 If the ambiguity field is not set in RTCM Version 3 streams, the BNC 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). 299 </li> 300 <li> 301 The generated RINEX is somewhat limited due to the streaming character of the conversion. 302 <ul> 303 <li> 304 Header records can only represent data, which is known after receiving the very first epoch. Data rate, position, number of observations and any such additional fields cannot be provided. 305 </li> 306 <li> 307 The number of observables cannot change during the program runtime. Only the observables, which exist in the first epoch are outputted. If there are new observables later on, these are ignored. 308 </li> 309 </ul> 310 </li> 311 <li> 312 BNC's 'Get Table' function only informs about the STR records of a sourcetable. Note that you can use an Internet browser to download the full sourcetable contents of any NTRIP broadcaster by simply entering its URL: http://host:port/dummy. Data field number 8 of the NET records may provide information about where to register for an NTRIP broadcaster account. 313 </li> 314 <li> 315 EUREF as well as IGS follow 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 anybody for any purpose. It is not clear today how many users will have to be supported simultaneously. The situation may develop in a way that it becomes difficult to serve all registered users at any time. In case limited dissemination resources on the NTRIP broadcaster side (software restrictions, bandwidth limitation etc.) make it necessary, first priority in stream provision will be given to stream providers, real-time analysis centres, and re-broadcasting activities while access for others may be temporarily denied. 316 [<a href=#back_contents>Back</a>]<br> 317 </li> 318 </ul> 264 319 <br> 265 320 <a name="authors"> 266 321 <p><h3>D - Authors</h3></p> 267 322 <p> 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: 269 <ul> 270 <li> RTCM 2.x decoder, written by John Sager with contributions from Carsten Becker (DLR)</li> 271 <li> RTCM 3 decoder, written by Dirk Stoecker (Euronik) for BKG</li> 272 <li> RTIGS decoder, written by Ken MacLeod (NRCan)</li> 273 </ul> 274 </p> 275 <p> 276 Note that this is a first version of BNC provided for test and evaluation. We are still working on the program and would very much appreciate if you could send your comments, suggestions, or bug reports to: 277 </p> 278 <p> 323 Basically BNC is an NTRIP Qt Graphic User Interface (GUI) developed for the Federal Agency for Cartography and Geodesy (BKG) by Leos Mervart (Czech Technical University Prague, Department of Advanced Geodesy). BNC integrates the following already existing GNU GPL software components: 324 <ul> 325 <li> RTCM 2.x decoder, written by John Sager with contributions from Carsten Becker (German Aerospace Center, DLR, Neustrelitz)</li> 326 <li> RTCM 3 decoder, written for BKG by Dirk Stoecker (Euronik GmbH, Schoenefeld)</li> 327 <li> RTIGS decoder, written by Ken MacLeod (Natural Resources Canada, NRCan)</li> 328 </ul> 329 </p> 330 <p> 331 Note that this is a betta version of BNC provided for test and evaluation. Make sure you installed the latest version available from <u>http://igs.bkg.bund.de/index_ntrip_down.htm</u>. We are still working on the program and would appreciate if you could send your comments, suggestions, or bug reports to: 332 </p> 333 <p> 334 Georg Weber<br> 279 335 Federal Agency for Cartography and Geodesy (BKG)<br> 280 336 Frankfurt, Germany<br> 281 337 euref-ip@bkg.bund.de 282 </p> 283 284 <br> 338 [<a href=#back_contents>Back</a>]<br> 339 </p> 340 <br> 341 342 <a name="links"> 343 <p><h3>E - Links</h3></p> 344 <table> 345 <tr><td>NTRIP </td><td><u>http://igs.bkg.bund.de/index_ntrip.htm</u></td></tr> 346 <tr><td>EUREF-IP NTRIP broadcaster </td><td><u>http://www.euref-ip.net/home</u></td></tr> 347 <tr><td>IGS-IP NTRIP broadcaster </td><td><u>http://www.igs-ip.net/home</u></td></tr> 348 <tr><td>NTRIP broadcaster overview </td><td><u>http://www.rtcm-ntrip.org/home</u></td></tr> 349 <tr><td>EUREF-IP Pilot Project </td><td><u>http://www.epncb.oma.be/euref_IP</u></td></tr> 350 <tr><td>Real-Time IGS Working Group </td><td><u>http://igscb.jpl.nasa.gov/projects/rtwg/index.html</u> 351 [<a href=#back_contents>Back</a>]<br> 352 </table> 353 <br><br> 354 355 <a name="back_annex"> 285 356 <a name="annex"> 286 <p><h3> E- Annex</h3></p>287 <p> 288 <table>289 <tr><td>E - 1.</td><td><a href=#ntrip>NTRIP</a></td>290 <tr><td></td><td>E - 1.1</td><td><a href=#source>Sourcetable</a></td>291 <tr><td>E - 2.</td><td><a href=#rtcm>RTCM</a></td>292 <tr><td></td><td>E - 2.1</td><td><a href=#rtcm2>RTCM Version 2.x</a></td>293 <tr><td></td><td>E - 2.2</td><td><a href=#rtcm3>RTCM Version 3</a></td>294 <tr><td>E - 3.</td><td><a href=#rtigs>RTIGS</a></td>295 <tr><td></td><td>E - 3.1</td><td><a href=#soc>SOC</a></td>296 </ table>297 < /p>357 <p><h3>F - Annex</h3></p> 358 <p> 359 F - 1. <a href=#ntrip>NTRIP</a><br> 360 E - 1.1 <a href=#source>Sourcetable</a><br> 361 F - 2. <a href=#rtcm>RTCM</a><br> 362 F - 2.1 RTCM <a href=#rtcm2> Version 2.x</a><br> 363 F - 2.2 RTCM <a href=#rtcm3> Version 3</a><br> 364 F - 3. <a href=#rtigs>RTIGS</a><br> 365 F - 3.1 <a href=#soc>SOC</a> 366 [<a href=#back_contents>Back</a>]<br> 367 </p> 368 <br> 298 369 299 370 <a name="ntrip"> 300 <p><h4> E- 1. NTRIP</h4></p>301 302 <p> 303 Networked Transport of RTCM via Internet Protocol 'Networked Transport of RTCM via Internet Protocol'(NTRIP) stands for an application-level protocol streaming Global Navigation Satellite System (GNSS) data over the Internet. NTRIP is a generic, stateless protocol based on the Hypertext Transfer Protocol HTTP/1.1. The HTTP objects are enhanced to GNSS data streams.304 </p> 305 306 <p> 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.371 <p><h4>F - 1. NTRIP</h4></p> 372 373 <p> 374 'Networked Transport of RTCM via Internet Protocol' Version 1.0 (NTRIP) stands for an application-level protocol streaming Global Navigation Satellite System (GNSS) data over the Internet. NTRIP is a generic, stateless protocol based on the Hypertext Transfer Protocol HTTP/1.1. The HTTP objects are enhanced to GNSS data streams. 375 </p> 376 377 <p> 378 NTRIP Version 1.0 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. 308 379 </p> 309 380 … … 319 390 <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> 320 391 <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> 321 <li>Enables streaming over any mobile IP network because of using TCP/IP.</li> 392 <li>Enables streaming over mobile IP networks because of using TCP/IP.</li> 393 [<a href=#back_annex>Back</a>]<br> 322 394 </ul> 323 395 </p><br> 324 396 325 397 <a name="source"> 326 <p><h4>E - 1.1 Sourcetable</h4></p> 327 328 <p> 329 The NTRIP broadcaster maintains a sourcetable containing information on available NTRIP sources, networks of NTRIP sources, and NTRIP broadcasters. The sourcetable is sent to an NTRIP client on request. Sourcetable records are dedicated to one of the following: Data STReams (record type STR), CASters (record type CAS), or NETworks of data streams (record type NET). 330 </p> 331 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. 398 <p><h4>F - 1.1 Sourcetable</h4></p> 399 400 <p> 401 The NTRIP broadcaster maintains a sourcetable containing information on available NTRIP streams, networks of NTRIP streams, and NTRIP broadcasters. The sourcetable is sent to an NTRIP client on request. Sourcetable records are dedicated to one of the following: Data STReams (record type STR), CASters (record type CAS), or NETworks of streams (record type NET). 402 </p> 403 404 <p> 405 Sourcetable 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'. 406 </p> 407 <p> 408 Sourcetable records of type NET contain the following data fields: 'identifiey', 'operator', 'authentication', 'fee', 'web-net', 'web-str', 'web-reg', 'misc'. 409 [<a href=#back_annex>Back</a>]<br> 333 410 </p> 334 411 335 412 <a name="rtcm"> 336 <p><h4> E- 2. RTCM</h4></p>413 <p><h4>F - 2. RTCM</h4></p> 337 414 338 415 <p> 339 416 The Radio Technical Commission for Maritime Services (RTCM) is an international non-profit scientific, professional and educational organization. Special Committees provide a forum in which government and non-government members work together to develop technical standards and consensus recommendations in regard to issues of particular concern. RTCM is engaged in the development of international standards for maritime radionavigation and radiocommunication systems. The output documents and reports prepared by RTCM Committees are published as RTCM Recommended Standards. Topics concerning Differential Global Navigation Satellite Systems (DGNSS) and handled by the Special Committee SC 104. 340 </p><br> 417 <p> 418 Copies of RTCM Recommended Standards can be ordered through <u>http://www.rtcm.org/orderinfo.php</u>. 419 [<a href=#back_annex>Back</a>]<br> 420 </p> 421 <br> 341 422 342 423 <a name="rtcm2"> 343 <p><h4> E- 2.1 RTCM Version 2.x</h4></p>344 <p> 345 Transmitting carrier phase data can be done by transmittingRTCM Version 2.x messages. Message that may be of interest here are types 1, 2, 3, 6, 9, 16,18/19, 20/21, and 22.424 <p><h4>F - 2.1 RTCM Version 2.x</h4></p> 425 <p> 426 Transmitting GNSS carrier phase data can be done through RTCM Version 2.x messages. Message that may be of interest here are types 1, 2, 3, 6, 9, 16,18/19, 20/21, and 22. 346 427 </p> 347 428 … … 369 450 </li> 370 451 <li> 371 Type 19 and 21 messages are the uncorrected pseudo-range measurements and pseudo- range corrections used in RTK. 372 </li> 373 </ul> 374 <p> 375 Note that this version of BNC handles only RTCM Version 2 message types 18 and 19. 376 </p> 452 Type 19 and 21 messages are the uncorrected pseudo-range measurements and pseudo-range corrections used in RTK. 453 [<a href=#back_annex>Back</a>]<br> 454 </li> 455 </ul> 377 456 378 457 <a name="rtcm3"> 379 <p><h4> E- 2.2 RTCM Version 3</h4></p>458 <p><h4>F - 2.2 RTCM Version 3</h4></p> 380 459 <p> 381 460 RTCM Version 3 has been developed as a more efficient alternative to RTCM 2.x. Service providers and vendors have asked for a new 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 new standard, Version 3, is intended to correct these weaknesses. … … 385 464 </p> 386 465 <ul> 387 <li> 388 Tpye 1001 message carries GPS L1 code and phase. 389 </li> 390 <li> 391 Type 1002 message carries GPS L1 code and phase and ambiguities and carrier to noise ratio. 392 </li> 393 <li> 394 Type 1003 message carries GPS L1 and L1 code and phase. 395 </li> 396 <li> 397 Type 1004 message carries GPS L1 and L2 code and phase and ambiguities and carrier to noise ratio. 398 </li> 399 <li> 400 Type 1005 message carries Station coordinates XZY for antenna reference point. 401 </li> 402 <li> 403 Type 1006 message carries Station coordinates XYZ for antenna reference point and antenna height. 404 </li> 405 <li> 406 Type 1007 message carries the Antenna descriptor and ID. 407 </li> 408 <li> 409 Type 1008 message carries the Antenna serial number. 410 </li> 411 <li> 412 Type 1009 message carries GLONASS L1 code and phase. 413 </li> 414 <li> 415 Type 1010 message carries GLONASS L1 code and phase and ambiguities and carrier to noise ratio. 416 </li> 417 <li> 418 Type 1011 message carries GLONASS L1 and L1 code and phase. 419 </li> 420 <li> 421 Type 1012 message carries GLONASS L1 and L2 code and phase and ambiguities and carrier to noise ratio. 422 </li> 423 <li> 424 Type 1013 message carries Modified julian date, leap second, configured message types and interval. 425 </li> 426 <li> 427 Type 1014 and 1017 messages carry Network RTK (MAK) messages (under development). 428 </li> 429 <li> 430 Type 1019 message carries GPS Ephemeris (under development). 431 </li> 432 <li> 433 Type 1020 message carries GLONASS Ephemeris (under development). 434 </li> 435 <li> 436 Type 4088 and 4095 messages carry Proprietary messages (under development). 437 </li> 438 </ul> 439 <p> 440 Note that this version of BNC handles only RTCM Version 3 message types 1001, 1002, 1003, and 1004. 441 </p> 466 <li>Tpye 1001, GPS L1 code and phase.</li> 467 <li>Type 1002, GPS L1 code and phase and ambiguities and carrier to noise ratio.</li> 468 <li>Type 1003, GPS L1 and L1 code and phase.</li> 469 <li>Type 1004, GPS L1 and L2 code and phase and ambiguities and carrier to noise ratio.</li> 470 <li>Type 1005, Station coordinates XZY for antenna reference point.</li> 471 <li>Type 1006, Station coordinates XYZ for antenna reference point and antenna height.</li> 472 <li>Type 1007, Antenna descriptor and ID.</li> 473 <li>Type 1008, Antenna serial number.</li> 474 <li>Type 1009, GLONASS L1 code and phase.</li> 475 <li>Type 1010, GLONASS L1 code and phase and ambiguities and carrier to noise ratio.</li> 476 <li>Type 1011, GLONASS L1 and L1 code and phase.</li> 477 <li>Type 1012, GLONASS L1 and L2 code and phase and ambiguities and carrier to noise ratio.</li> 478 <li>Type 1013, Modified julian date, leap second, configured message types and interval.</li> 479 <li>Type 1014 and 1017, Network RTK (MAK) messages (under development).</li> 480 <li>Type 1019, GPS Ephemeris (under development).</li> 481 <li>Type 1020, GLONASS Ephemeris (under development).</li> 482 <li>Type 4088 and 4095, Proprietary messages (under development). 483 [<a href=#back_annex>Back</a>]<br> 484 </li> 485 </ul> 442 486 443 487 <a name="rtigs"> 444 <p><h4>E - 3. RTIGS</h4></p> 445 <p> 446 Input from by Ken? 488 <p><h4>F - 3. RTIGS</h4></p> 489 <p> 490 Input from Ken? 491 [<a href=#back_annex>Back</a>]<br> 447 492 </p> 448 493 449 494 <a name="soc"> 450 <p><h4>E - 3.1 SOC</h4></p> 451 <p> 452 Input from by Ken? 453 </p> 454 495 <p><h4>F - 3.1 SOC</h4></p> 496 <p> 497 Input from Ken? 498 [<a href=#back_annex>Back</a>]<br> 499 </p> 500 <p> 501 [<a href=#back_contents>Back</a>]<br> 502 </p> 503 504 505 506
Note:
See TracChangeset
for help on using the changeset viewer.
