- Timestamp:
- May 18, 2012, 3:25:45 PM (13 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (97 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r4190 r4191 20 20 <p><b>Contents</b><br> 21 21 <a href=#purpose>1. Purpose</a><br> 22 <a href=#resources>2. Modes & Resources</a><br> 23 <a href=#opthandling>3. Handling</a><br> 24 <a href=#optsettings>4. Settings</a><br> 25 <a href=#limits>5. Limitations & Known Bugs</a><br> 26 <a href=#annex>6. Annex</a> 22 <a href=#opthandling>2. Handling</a><br> 23 <a href=#optsettings>3. Settings</a><br> 24 <a href=#limits>4. Limitations</a><br> 25 <a href=#annex>5. Annex</a> 27 26 </p> 28 27 … … 118 117 119 118 120 <p><a name="resources"><h3>2. Modes & Resources</h3></p>119 <p><a name="resources"><h3>2. Handling</h3></p> 121 120 <p> 122 121 Although BNC is mainly a real-time tool to be operated online, it can be run offline … … 143 142 <p><u>Figure 5:</u> Sections on BNC's main window.</p> 144 143 145 146 <p><a name="opthandling"><h3>3. Handling</h3></p>147 148 144 <p> 149 145 The usual handling of BNC is that you first select a number of streams ('Add Stream'). 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 configuration tabs to select a combination of input, processing and output options before you start the program ('Start'). Most configuration tabs are dedicated to a certain functionality of BNC. If the first option field on such a configuration tab is empty, the affected functionality is - apart from a few exceptions - deactivated.</p> … … 156 152 The default file name 'BNC.bnc' can be changed and the file contents can easily be edited. On graphical user interfaces it is possible to Drag & Drop a configuration file icon to start BNC (not on Mac systems). Some configuration options can be changed on-the-fly. See annexed 'Configuration Examples' for a complete set of configuration options. It is also possible to start and configure BNC via command line. 157 153 </p> 158 <p><a name="optsettings"><h3> 4. Settings</h3></p>154 <p><a name="optsettings"><h3>3. Settings</h3></p> 159 155 <p> 160 156 This chapter describes how to set the BNC program options. It explains the top menu bar, the processing options, the 'Streams' and 'Log' sections, and the bottom menu bar. … … 162 158 <p> 163 159 <b>Top Menu Bar</b><br> 164 4.1. <a href=#topmenu>Top Menu Bar</a><br>165 4.1.1 <a href=#file>File</a><br>166 4.1.2 <a href=#help>Help</a><br><br>160 3.1. <a href=#topmenu>Top Menu Bar</a><br> 161 3.1.1 <a href=#file>File</a><br> 162 3.1.2 <a href=#help>Help</a><br><br> 167 163 <b>Settings Canvas</b><br> 168 4.2. <a href=#network>Network</a><br>169 4.2.1 <a href=#proxy>Proxy</a><br>170 4.2.2 <a href=#ssl>SSL</a><br>171 4.3. <a href=#general>General</a><br>172 4.3.1. <a href=#genlog>Logfile</a><br>173 4.3.2. <a href=#genapp>Append Files</a><br>174 4.3.3. <a href=#genconf>Reread Configuration</a><br>175 4.3.4. <a href=#genstart>Auto Start</a><br>176 4.3.5. <a href=#rawout>Raw Output File</a><br>177 4.4. <a href=#rinex>RINEX Observations</a><br>178 4.4.1. <a href=#rnxname>File Names</a><br>179 4.4.2. <a href=#rnxdir>Directory</a><br>180 4.4.3. <a href=#rnxinterval>File Interval</a><br>181 4.4.4. <a href=#rnxsample>Sampling</a><br>182 4.4.5. <a href=#rnxskl>Skeleton Extension</a><br>183 4.4.6. <a href=#rnxscript>Script</a><br>184 4.4.7. <a href=#rnxvers>Version</a><br>185 4.5. <a href=#ephemeris>RINEX Ephemeris</a><br>186 4.5.1. <a href=#ephdir>Directory</a><br>187 4.5.2. <a href=#ephint>Interval</a><br>188 4.5.3. <a href=#ephport>Port</a><br>189 4.5.4. <a href=#ephvers>Version</a><br>190 4.6. <a href=#reqc>RINEX Editing & QC</a><br>191 4.6.1 <a href=#reqcact>Action</a><br>192 4.6.2 <a href=#reqcedit>Set Edit Options</a><br>193 4.6.3 <a href=#reqcinput>Input Files</a><br>194 4.6.4 <a href=#reqcoutput>Output Files</a><br>195 4.6.5 <a href=#reqccommand>Command Line, No Window</a><br>196 4.7. <a href=#correct>Broadcast Corrections</a><br>197 4.7.1. <a href=#corrdir>Directory, ASCII</a><br>198 4.7.2. <a href=#corrint>Interval</a><br>199 4.7.3. <a href=#corrport>Port</a><br>200 4.7.4. <a href=#corrwait>Wait for Full Epoch</a><br>201 4.8. <a href=#syncout>Feed Engine</a><br>202 4.8.1. <a href=#syncport>Port</a><br>203 4.8.2. <a href=#syncwait>Wait for Full Epoch</a><br>204 4.8.3. <a href=#syncsample>Sampling</a><br>205 4.8.4. <a href=#syncfile>File</a><br>206 4.8.5. <a href=#syncuport>Port (unsynchronized)</a><br>207 4.9. <a href=#serial>Serial Output</a><br>208 4.9.1. <a href=#sermount>Mountpoint</a><br>209 4.9.2. <a href=#serport>Port Name</a><br>210 4.9.3. <a href=#serbaud>Baud Rate</a><br>211 4.9.4. <a href=#serflow>Flow Control</a><br>212 4.9.5. <a href=#serparity>Parity</a><br>213 4.9.6. <a href=#serdata>Data Bits</a><br>214 4.9.7. <a href=#serstop>Stop Bits</a><br>215 4.9.8. <a href=#serauto>NMEA</a><br>216 4.9.9. <a href=#serfile>File</a><br>217 4.9.10. <a href=#serheight>Height</a><br>218 4.10. <a href=#advnote>Outages</a><br>219 4.10.1. <a href=#obsrate>Observation Rate</a><br>220 4.10.2. <a href=#advfail>Failure Threshold</a><br>221 4.10.3. <a href=#advreco>Recovery Threshold</a><br>222 4.10.4. <a href=#advscript>Script</a><br>223 4.11. <a href=#misc>Miscellaneous</a><br>224 4.11.1. <a href=#miscmount>Mountpoint</a><br>225 4.11.2. <a href=#miscperf>Log Latency</a><br>226 4.11.3. <a href=#miscscan>Scan RTCM</a><br>227 4.12. <a href=#pppclient>PPP Client</a><br>228 4.12.1 <a href=#pppmode>Mode & Mountpoints</a><br>229 4.12.1.1 <a href=#pppmodus>Mode</a><br>230 4.12.1.2 <a href=#pppobsmount>Obs Mountpoint</a><br>231 4.12.1.3 <a href=#pppcorrmount>Corr Mountpoint</a><br>232 4.12.2 <a href=#pppxyz>Marker Coordinates</a><br>233 4.11.3 <a href=#pppneu>Antenna Excentricity</a><br>234 4.12.4 <a href=#pppoutput>NMEA & Plot Output</a><br>235 4.12.4.1 <a href=#pppnmeafile>NMEA File</a><br>236 4.12.4.2 <a href=#pppnmeaport>NMEA Port</a><br>237 4.12.4.3 <a href=#pppplot>PPP Plot</a><br>238 4.12.5 <a href=#ppppost>Post Processing</a><br>239 4.12.6 <a href=#ppprecant>Antennas</a><br>240 4.12.6.1 <a href=#pppantex>ANTEX File</a><br>241 4.12.6.2 <a href=#ppprecantenna>Antenna Name</a><br>242 4.12.6.3 <a href=#pppsatant>Apply Satellite Antenna Offsets</a><br>243 4.12.7 <a href=#pppbasics>Basics</a><br>244 4.12.7.1 <a href=#pppphase>Use Phase Obs</a><br>245 4.12.7.2 <a href=#ppptropo>Estimate Tropo</a><br>246 4.12.7.3 <a href=#pppglo>Use GLONASS</a><br>247 4.12.7.4 <a href=#pppgal>Use Galileo</a><br>248 4.12.7.5 <a href=#pppsync>Sync Corr</a><br>249 4.12.7.6 <a href=#pppaverage>Averaging</a><br>250 4.12.7.7 <a href=#pppquick>Quick-Start</a><br>251 4.12.7.8 <a href=#pppgap>Maximal Solution Gap</a><br>252 4.12.8 <a href=#pppsigmas>Sigmas</a><br>253 4.12.8.1 <a href=#pppsigc>Code</a><br>254 4.12.8.2 <a href=#pppsigp>Phase</a><br>255 4.12.8.3 <a href=#pppsigxyzi>XYZ Init</a><br>256 4.12.8.4 <a href=#pppsigxyzn>XYZ White Noise</a><br>257 4.12.8.5 <a href=#pppsigtrpi>Tropo Init</a><br>258 4.12.8.6 <a href=#pppsigtrpn>Tropo White Noise</a><br>259 4.13. <a href=#combi>Combine Corrections</a><br>260 4.13.1 <a href=#combimounttab>Combine Corrections Table</a><br>261 4.13.1.1 <a href=#combiadd>Add Row, Delete</a><br>262 4.13.1.2 <a href=#combimethod>Method</a><br>263 4.13.1.3 <a href=#combimax>Maximal Residuum</a><br>264 4.13.1.4 <a href=#combismpl>Sampling</a><br>265 4.14. <a href=#upclk>Upload Corrections</a><br>266 4.14.1 <a href=#upadd>Add, Delete Row</a><br>267 4.14.2 <a href=#uphost>Host, Port, Mountpoint, Password</a><br>268 4.14.3 <a href=#upsystem>System</a><br>269 4.14.4 <a href=#upcom>Center of Mass</a><br>270 4.14.5 <a href=#upsp3>SP3 File</a><br>271 4.14.6 <a href=#uprinex>RNX File</a><br>272 4.14.7 <a href=#upinter>Interval</a><br>273 4.14.8 <a href=#upclksmpl>Sampling</a><br>274 4.14.8.1 <a href=#upclkorb>orbits</a><br>275 4.14.8.2 <a href=#upclksp3>SP3</a><br>276 4.14.8.3 <a href=#upclkrnx>RINEX </a><br>277 4.14.9 <a href=#upcustom>Custom Trafo</a><br>278 4.15. <a href=#upeph>Upload Ephemeris</a><br>279 4.15.1 <a href=#brdcserver>Host & Port</a><br>280 4.15.2 <a href=#brdcmount>Mountpoint & Password</a><br>281 4.15.3 <a href=#brdcsmpl>Sampling</a><br><br>164 3.2. <a href=#network>Network</a><br> 165 3.2.1 <a href=#proxy>Proxy</a><br> 166 3.2.2 <a href=#ssl>SSL</a><br> 167 3.3. <a href=#general>General</a><br> 168 3.3.1. <a href=#genlog>Logfile</a><br> 169 3.3.2. <a href=#genapp>Append Files</a><br> 170 3.3.3. <a href=#genconf>Reread Configuration</a><br> 171 3.3.4. <a href=#genstart>Auto Start</a><br> 172 3.3.5. <a href=#rawout>Raw Output File</a><br> 173 3.4. <a href=#rinex>RINEX Observations</a><br> 174 3.4.1. <a href=#rnxname>File Names</a><br> 175 3.4.2. <a href=#rnxdir>Directory</a><br> 176 3.4.3. <a href=#rnxinterval>File Interval</a><br> 177 3.4.4. <a href=#rnxsample>Sampling</a><br> 178 3.4.5. <a href=#rnxskl>Skeleton Extension</a><br> 179 3.4.6. <a href=#rnxscript>Script</a><br> 180 3.4.7. <a href=#rnxvers>Version</a><br> 181 3.5. <a href=#ephemeris>RINEX Ephemeris</a><br> 182 3.5.1. <a href=#ephdir>Directory</a><br> 183 3.5.2. <a href=#ephint>Interval</a><br> 184 3.5.3. <a href=#ephport>Port</a><br> 185 3.5.4. <a href=#ephvers>Version</a><br> 186 3.6. <a href=#reqc>RINEX Editing & QC</a><br> 187 3.6.1 <a href=#reqcact>Action</a><br> 188 3.6.2 <a href=#reqcedit>Set Edit Options</a><br> 189 3.6.3 <a href=#reqcinput>Input Files</a><br> 190 3.6.4 <a href=#reqcoutput>Output Files</a><br> 191 3.6.5 <a href=#reqccommand>Command Line, No Window</a><br> 192 3.7. <a href=#correct>Broadcast Corrections</a><br> 193 3.7.1. <a href=#corrdir>Directory, ASCII</a><br> 194 3.7.2. <a href=#corrint>Interval</a><br> 195 3.7.3. <a href=#corrport>Port</a><br> 196 3.7.4. <a href=#corrwait>Wait for Full Epoch</a><br> 197 3.8. <a href=#syncout>Feed Engine</a><br> 198 3.8.1. <a href=#syncport>Port</a><br> 199 3.8.2. <a href=#syncwait>Wait for Full Epoch</a><br> 200 3.8.3. <a href=#syncsample>Sampling</a><br> 201 3.8.4. <a href=#syncfile>File</a><br> 202 3.8.5. <a href=#syncuport>Port (unsynchronized)</a><br> 203 3.9. <a href=#serial>Serial Output</a><br> 204 3.9.1. <a href=#sermount>Mountpoint</a><br> 205 3.9.2. <a href=#serport>Port Name</a><br> 206 3.9.3. <a href=#serbaud>Baud Rate</a><br> 207 3.9.4. <a href=#serflow>Flow Control</a><br> 208 3.9.5. <a href=#serparity>Parity</a><br> 209 3.9.6. <a href=#serdata>Data Bits</a><br> 210 3.9.7. <a href=#serstop>Stop Bits</a><br> 211 3.9.8. <a href=#serauto>NMEA</a><br> 212 3.9.9. <a href=#serfile>File</a><br> 213 3.9.10. <a href=#serheight>Height</a><br> 214 3.10. <a href=#advnote>Outages</a><br> 215 3.10.1. <a href=#obsrate>Observation Rate</a><br> 216 3.10.2. <a href=#advfail>Failure Threshold</a><br> 217 3.10.3. <a href=#advreco>Recovery Threshold</a><br> 218 3.10.4. <a href=#advscript>Script</a><br> 219 3.11. <a href=#misc>Miscellaneous</a><br> 220 3.11.1. <a href=#miscmount>Mountpoint</a><br> 221 3.11.2. <a href=#miscperf>Log Latency</a><br> 222 3.11.3. <a href=#miscscan>Scan RTCM</a><br> 223 3.12. <a href=#pppclient>PPP Client</a><br> 224 3.12.1 <a href=#pppmode>Mode & Mountpoints</a><br> 225 3.12.1.1 <a href=#pppmodus>Mode</a><br> 226 3.12.1.2 <a href=#pppobsmount>Obs Mountpoint</a><br> 227 3.12.1.3 <a href=#pppcorrmount>Corr Mountpoint</a><br> 228 3.12.2 <a href=#pppxyz>Marker Coordinates</a><br> 229 3.11.3 <a href=#pppneu>Antenna Excentricity</a><br> 230 3.12.4 <a href=#pppoutput>NMEA & Plot Output</a><br> 231 3.12.4.1 <a href=#pppnmeafile>NMEA File</a><br> 232 3.12.4.2 <a href=#pppnmeaport>NMEA Port</a><br> 233 3.12.4.3 <a href=#pppplot>PPP Plot</a><br> 234 3.12.5 <a href=#ppppost>Post Processing</a><br> 235 3.12.6 <a href=#ppprecant>Antennas</a><br> 236 3.12.6.1 <a href=#pppantex>ANTEX File</a><br> 237 3.12.6.2 <a href=#ppprecantenna>Antenna Name</a><br> 238 3.12.6.3 <a href=#pppsatant>Apply Satellite Antenna Offsets</a><br> 239 3.12.7 <a href=#pppbasics>Basics</a><br> 240 3.12.7.1 <a href=#pppphase>Use Phase Obs</a><br> 241 3.12.7.2 <a href=#ppptropo>Estimate Tropo</a><br> 242 3.12.7.3 <a href=#pppglo>Use GLONASS</a><br> 243 3.12.7.4 <a href=#pppgal>Use Galileo</a><br> 244 3.12.7.5 <a href=#pppsync>Sync Corr</a><br> 245 3.12.7.6 <a href=#pppaverage>Averaging</a><br> 246 3.12.7.7 <a href=#pppquick>Quick-Start</a><br> 247 3.12.7.8 <a href=#pppgap>Maximal Solution Gap</a><br> 248 3.12.8 <a href=#pppsigmas>Sigmas</a><br> 249 3.12.8.1 <a href=#pppsigc>Code</a><br> 250 3.12.8.2 <a href=#pppsigp>Phase</a><br> 251 3.12.8.3 <a href=#pppsigxyzi>XYZ Init</a><br> 252 3.12.8.4 <a href=#pppsigxyzn>XYZ White Noise</a><br> 253 3.12.8.5 <a href=#pppsigtrpi>Tropo Init</a><br> 254 3.12.8.6 <a href=#pppsigtrpn>Tropo White Noise</a><br> 255 3.13. <a href=#combi>Combine Corrections</a><br> 256 3.13.1 <a href=#combimounttab>Combine Corrections Table</a><br> 257 3.13.1.1 <a href=#combiadd>Add Row, Delete</a><br> 258 3.13.1.2 <a href=#combimethod>Method</a><br> 259 3.13.1.3 <a href=#combimax>Maximal Residuum</a><br> 260 3.13.1.4 <a href=#combismpl>Sampling</a><br> 261 3.14. <a href=#upclk>Upload Corrections</a><br> 262 3.14.1 <a href=#upadd>Add, Delete Row</a><br> 263 3.14.2 <a href=#uphost>Host, Port, Mountpoint, Password</a><br> 264 3.14.3 <a href=#upsystem>System</a><br> 265 3.14.4 <a href=#upcom>Center of Mass</a><br> 266 3.14.5 <a href=#upsp3>SP3 File</a><br> 267 3.14.6 <a href=#uprinex>RNX File</a><br> 268 3.14.7 <a href=#upinter>Interval</a><br> 269 3.14.8 <a href=#upclksmpl>Sampling</a><br> 270 3.14.8.1 <a href=#upclkorb>orbits</a><br> 271 3.14.8.2 <a href=#upclksp3>SP3</a><br> 272 3.14.8.3 <a href=#upclkrnx>RINEX </a><br> 273 3.14.9 <a href=#upcustom>Custom Trafo</a><br> 274 3.15. <a href=#upeph>Upload Ephemeris</a><br> 275 3.15.1 <a href=#brdcserver>Host & Port</a><br> 276 3.15.2 <a href=#brdcmount>Mountpoint & Password</a><br> 277 3.15.3 <a href=#brdcsmpl>Sampling</a><br><br> 282 278 <b>Streams Canvas</b><br> 283 4.16. <a href=#streams>Streams</a><br>284 4.16.1 <a href=#streamedit>Edit Streams</a><br>285 4.16.2 <a href=#streamdelete>Delete Stream</a><br>286 4.16.3 <a href=#streamconf>Reconfigure Streams On-the-fly</a><br><br>279 3.16. <a href=#streams>Streams</a><br> 280 3.16.1 <a href=#streamedit>Edit Streams</a><br> 281 3.16.2 <a href=#streamdelete>Delete Stream</a><br> 282 3.16.3 <a href=#streamconf>Reconfigure Streams On-the-fly</a><br><br> 287 283 <b>Logging Canvas</b><br> 288 4.17. <a href=#logs>Logging</a><br>289 4.17.1 <a href=#logfile>Log</a><br>290 4.17.2 <a href=#throughput>Throughput</a><br>291 4.17.3 <a href=#latency>Latency</a><br>292 4.17.4 <a href=#ppptab>PPP Plot</a><br><br>284 3.17. <a href=#logs>Logging</a><br> 285 3.17.1 <a href=#logfile>Log</a><br> 286 3.17.2 <a href=#throughput>Throughput</a><br> 287 3.17.3 <a href=#latency>Latency</a><br> 288 3.17.4 <a href=#ppptab>PPP Plot</a><br><br> 293 289 <b>Bottom Menu Bar</b><br> 294 4.18. <a href=#bottom>Bottom Menu Bar</a><br>290 3.18. <a href=#bottom>Bottom Menu Bar</a><br> 295 291 4.18.1. <a href=#streamadd>Add Stream - Coming from Caster</a><br> 296 4.18.1.1 <a href=#streamhost>Caster Host and Port</a><br>297 4.18.1.2 <a href=#streamtable>Casters Table</a><br>298 4.18.1.3 <a href=#streamuser>User and Password</a><br>299 4.18.1.4 <a href=#gettable>Get Table</a><br>300 4.18.1.5 <a href=#ntripv>NTRIP Version</a><br>301 4.18.1.6 <a href=#map>Map</a><br>302 4.18.2 <a href=#streamip>Add Stream - Coming from TCP/IP Port</a><br>303 4.18.3 <a href=#streamudp>Add Stream - Coming from UDP Port</a><br>304 4.18.4 <a href=#streamser>Add Stream - Coming from Serial Port</a><br>305 4.18.5 <a href=#start>Start</a><br>306 4.18.6 <a href=#stop>Stop</a><br><br>292 3.18.1.1 <a href=#streamhost>Caster Host and Port</a><br> 293 3.18.1.2 <a href=#streamtable>Casters Table</a><br> 294 3.18.1.3 <a href=#streamuser>User and Password</a><br> 295 3.18.1.4 <a href=#gettable>Get Table</a><br> 296 3.18.1.5 <a href=#ntripv>NTRIP Version</a><br> 297 3.18.1.6 <a href=#map>Map</a><br> 298 3.18.2 <a href=#streamip>Add Stream - Coming from TCP/IP Port</a><br> 299 3.18.3 <a href=#streamudp>Add Stream - Coming from UDP Port</a><br> 300 3.18.4 <a href=#streamser>Add Stream - Coming from Serial Port</a><br> 301 3.18.5 <a href=#start>Start</a><br> 302 3.18.6 <a href=#stop>Stop</a><br><br> 307 303 <b>Command Line</b><br> 308 4.19. <a href=#cmd>Command Line Options</a><br>309 4.19.1. <a href=#nw>No Window Mode</a><br>310 4.19.2. <a href=#post>File Mode</a><br>311 4.19.3. <a href=#conffile>Configuration File</a><br>312 4.19.4. <a href=#confopt>Configuration Options</a><br>313 </p> 314 315 <p><a name="topmenu"><h4> 4.1. Top Menu Bar</h4></p>304 3.19. <a href=#cmd>Command Line Options</a><br> 305 3.19.1. <a href=#nw>No Window Mode</a><br> 306 3.19.2. <a href=#post>File Mode</a><br> 307 3.19.3. <a href=#conffile>Configuration File</a><br> 308 3.19.4. <a href=#confopt>Configuration Options</a><br> 309 </p> 310 311 <p><a name="topmenu"><h4>3.1. Top Menu Bar</h4></p> 316 312 <p> 317 313 The top menu bar allows to select a font for the BNC windows, save configured options, or quit the program execution. It also provides access to a program documentation. 318 314 </p> 319 315 320 <p><a name="file"><h4> 4.1.1 File</h4></p>316 <p><a name="file"><h4>3.1.1 File</h4></p> 321 317 322 318 <p> … … 334 330 </p> 335 331 336 <p><a name="help"><h4> 4.1.2 Help</h4></p>332 <p><a name="help"><h4>3.1.2 Help</h4></p> 337 333 338 334 <p> … … 356 352 </p> 357 353 358 <p><a name="network"><h4> 4.2. Network</h4></p>354 <p><a name="network"><h4>3.2. Network</h4></p> 359 355 <p> 360 356 You may need to specify a proxy when running BNC in a protected network. You may also like to use the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure NTRIP communication over the Internet. 361 357 </p> 362 <p><a name="proxy"><h4> 4.2.1 Proxy - Usage in a protected LAN</h4></p>358 <p><a name="proxy"><h4>3.2.1 Proxy - Usage in a protected LAN</h4></p> 363 359 <p> 364 360 If you are running BNC within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNC. If you don't know the IP and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.</p> … … 367 363 </p> 368 364 369 <p><a name="ssl"><h4> 4.2.2 SSL - Transport Layer Security</h4></p>365 <p><a name="ssl"><h4>3.2.2 SSL - Transport Layer Security</h4></p> 370 366 <p>Communication with an NTRIP Broadcaster over SSL requires the exchange of client and/or server certificates. Specify the path to a directory where you save certificates on your system. You may like to check out <u>http://software.rtcm-ntrip.org/wiki/Certificates</u> for a list of known NTRIP Server certificates. Don't try communication via SSL if you are not sure whether this is supported by the involved NTRIP Broadcaster. </p> 371 367 <p>SSL communication may involve queries coming from the NTRIP Broadcaster. Tick 'Ignore SSL authorization erros' if you don't want to be bothered with this. Note that SSL communication is usually done over port 443.</p> 372 368 373 <p><a name="general"><h4> 4.3. General</h4></p>369 <p><a name="general"><h4>3.3. General</h4></p> 374 370 <p> 375 371 The following defines general settings for BNC's logfile, file handling, reconfiguration on-the-fly, and auto-start. 376 372 </p> 377 373 378 <p><a name="genlog"><h4> 4.3.1 Logfile - optional</h4></p>374 <p><a name="genlog"><h4>3.3.1 Logfile - optional</h4></p> 379 375 <p> 380 376 Records of BNC's activities are shown in the 'Log' tab 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. 381 377 </p> 382 378 383 <p><a name="genapp"><h4> 4.3.2 Append Files - optional</h4></p>379 <p><a name="genapp"><h4>3.3.2 Append Files - optional</h4></p> 384 380 <p> 385 381 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. 386 382 </p> 387 383 388 <p><a name="genconf"><h4> 4.3.3 Reread Configuration - optional</h4></p>384 <p><a name="genconf"><h4>3.3.3 Reread Configuration - optional</h4></p> 389 385 <p> 390 386 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 Examples' for a configuration file example and a list of on-the-fly changeable options. 391 387 </p> 392 388 393 <p><a name="genstart"><h4> 4.3.4 Auto Start - optional</h4></p>389 <p><a name="genstart"><h4>3.3.4 Auto Start - optional</h4></p> 394 390 <p> 395 391 You may like to auto-start BNC at startup time in window mode with pre-assigned 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). … … 399 395 </p> 400 396 401 <p><a name="rawout"><h4> 4.3.5 Raw Output File - optional</h4></p>397 <p><a name="rawout"><h4>3.3.5 Raw Output File - optional</h4></p> 402 398 <p> 403 399 BNC can save all data coming in through various streams in one daily file. The information is recorded in the specified 'Raw output file' in the received order and format. This feature allows a BNC user to run the PPP option offline with observations, Broadcast Corrections, and Broadcast Ephemeris being read from a previously saved file. It supports the offline repetition of a real-time situation for debugging purposes. It is not meant for Post Processing. … … 414 410 </p> 415 411 416 <p><a name="rinex"><h4> 4.4. RINEX Observations</h4></p>412 <p><a name="rinex"><h4>3.4. RINEX Observations</h4></p> 417 413 <p> 418 414 Observations will be converted to RINEX if they come in either RTCM Version 2 or RTCM Version 3 format. Depending on the RINEX version and incoming RTCM message types, the files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS, and COMPASS. In case an observation type is listed in the RINEX header but the corresponding observation is unavailable, its value is set to zero '0.000'. Note that the 'RINEX TYPE' field in the RINEX Version 3 Observation file header is always set to 'M(MIXED)' or 'Mixed' even if the file only contains data from one system. … … 425 421 <p><u>Figure 6:</u> BNC translating incoming streams to 15 min RINEX Version 3 files.</p> 426 422 427 <p><a name="rnxname"><h4> 4.4.1 RINEX File Names</h4></p>423 <p><a name="rnxname"><h4>3.4.1 RINEX File Names</h4></p> 428 424 <p> 429 425 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> … … 456 452 </p> 457 453 458 <p><a name="rnxdir"><h4> 4.4.2 Directory - optional</h4></p>454 <p><a name="rnxdir"><h4>3.4.2 Directory - optional</h4></p> 459 455 <p> 460 456 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. 461 457 </p> 462 458 463 <p><a name="rnxinterval"><h4> 4.4.3 File Interval - mandatory if 'Directory' is set</h4></p>459 <p><a name="rnxinterval"><h4>3.4.3 File Interval - mandatory if 'Directory' is set</h4></p> 464 460 <p> 465 461 Select the length of the RINEX Observation file generated. The default value is 15 minutes. 466 462 </p> 467 463 468 <p><a name="rnxsample"><h4> 4.4.4 Sampling - mandatory if 'Directory' is set </h4></p>464 <p><a name="rnxsample"><h4>3.4.4 Sampling - mandatory if 'Directory' is set </h4></p> 469 465 <p> 470 466 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. 471 467 </p> 472 468 473 <p><a name="rnxskl"><h4> 4.4.5 Skeleton Extension - optional</h4></p>469 <p><a name="rnxskl"><h4>3.4.5 Skeleton Extension - optional</h4></p> 474 470 <p> 475 471 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 Version 2 header skeleton file for the Brussels EPN station. … … 522 518 </p> 523 519 524 <p><a name="rnxscript"><h4> 4.4.6 Script - optional</h4></p>520 <p><a name="rnxscript"><h4>3.4.6 Script - optional</h4></p> 525 521 <p> 526 522 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). … … 533 529 </p> 534 530 535 <p><a name="rnxvers"><h4> 4.4.7 Version - optional</h4></p>531 <p><a name="rnxvers"><h4>3.4.7 Version - optional</h4></p> 536 532 <p> 537 533 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. 538 534 </p> 539 535 540 <p><a name="ephemeris"><h4> 4.5. RINEX Ephemeris</h4></p>536 <p><a name="ephemeris"><h4>3.5. RINEX Ephemeris</h4></p> 541 537 <p> 542 538 Broadcast ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3 e.g. as message types 1019 (GPS) or 1020 (GLONASS) or 1045 (Galileo). 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 … … 551 547 </p> 552 548 553 <p><a name="ephdir"><h4> 4.5.1 Directory - optional</h4></p>549 <p><a name="ephdir"><h4>3.5.1 Directory - optional</h4></p> 554 550 <p> 555 551 Specify a 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. 556 552 </p> 557 553 558 <p><a name="ephint"><h4> 4.5.2 Interval - mandatory if 'Directory' is set</h4></p>554 <p><a name="ephint"><h4>3.5.2 Interval - mandatory if 'Directory' is set</h4></p> 559 555 <p> 560 556 Select the length of the RINEX Navigation file generated. The default value is 1 day. 561 557 </p> 562 558 563 <p><a name="ephport"><h4> 4.5.3 Port - optional</h4></p>559 <p><a name="ephport"><h4>3.5.3 Port - optional</h4></p> 564 560 <p> 565 561 BNC can output Broadcast Ephemeris in RINEX Version 3 format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number to activate this function. The default is an empty option field, meaning that no ASCII ephemeris output via IP port is generated. … … 569 565 </p> 570 566 571 <p><a name="ephvers"><h4> 4.5.4 Version - optional</h4></p>567 <p><a name="ephvers"><h4>3.5.4 Version - optional</h4></p> 572 568 <p> 573 569 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. … … 577 573 </p> 578 574 579 <p><a name="reqc"><h4> 4.6. RINEX Editing & QC</h4></p>575 <p><a name="reqc"><h4>3.6. RINEX Editing & QC</h4></p> 580 576 <p> 581 577 Besides stream conversion from RTCM to RINEX, BNC allows editing RINEX files or concatenate their contents. RINEX observation and navigation files can be handled. BNC can also carry out a RINEX file contents quality check. In summary this functionality in BNC covers … … 587 583 and hence follows UNAVCO's famous 'TEQC' program. The remarkable thing about BNC in this context is that it supports RINEX Version 3 under GNU General Public License. 588 584 589 <p><a name="reqcact"><h4> 4.6.1 Action - optional</h4></p>585 <p><a name="reqcact"><h4>3.6.1 Action - optional</h4></p> 590 586 <p>Select an action. Options are 'Edit/Concatenate' and 'Analyze'. 591 587 <ul> … … 595 591 </p> 596 592 597 <p><a name="reqcedit"><h4> 4.6.2 Set Edit Options - mandatory if 'Edit/Concatenate' is set</h4></p>593 <p><a name="reqcedit"><h4>3.6.2 Set Edit Options - mandatory if 'Edit/Concatenate' is set</h4></p> 598 594 <p>Once the 'Edit/Concatenate' action is selected, you have to 'Set Edit Options'. BNC lets you specify the RINEX version, sampling interval, begin and end of file, operator, comment lines, and marker, antenna, receiver details. 599 595 </p> … … 615 611 <p><u>Figure 7:</u> Example for 'RINEX Editing Options' window.</p> 616 612 617 <p><a name="reqcinput"><h4> 4.6.3 Input Files - mandatory if 'Action' is set</h4></p>613 <p><a name="reqcinput"><h4>3.6.3 Input Files - mandatory if 'Action' is set</h4></p> 618 614 <p> 619 615 Specify full path to input RINEX observation file(s), and<br> … … 622 618 <p>When specifying several input files BNC will concatenate their contents.</p> 623 619 624 <p><a name="reqcoutput"><h4> 4.6.4 Output Files - mandatory if 'Action' is set</h4></p>620 <p><a name="reqcoutput"><h4>3.6.4 Output Files - mandatory if 'Action' is set</h4></p> 625 621 <p> 626 622 If 'Edit/Concatenate' is selected, specifying the a path to output RINEX observation file(s) and specifying a full path to output RINEX navigation file(s) is mandatory.</p> … … 633 629 <p><u>Figure 7:</u> Example for RINEX file editing with BNC in Post Processing mode.</p> 634 630 635 <p><a name="reqccommand"><h4> 4.6.5 Command Line, No Window - optional</h4></p>631 <p><a name="reqccommand"><h4>3.6.5 Command Line, No Window - optional</h4></p> 636 632 <p> 637 633 BNC applies options from the configuration file but allows updating every one of them on the command line while the contents of the configuration file remains unchanged, see section on 'Command Line Options'. The syntax for that looks as follows … … 684 680 </table> 685 681 686 <p><a name="correct"><h4> 4.7. Broadcast Corrections</h4></p>682 <p><a name="correct"><h4>3.7. Broadcast Corrections</h4></p> 687 683 <p> 688 684 Differential GNSS and RTK operation using RTCM streams is currently based on corrections and/or raw measurements from single or multiple reference stations. This approach to differential positioning is using 'observation space' information. The representation with the RTCM standard can be called 'ObservationSpace Representation' (OSR). … … 866 862 </pre> 867 863 868 <p><a name="corrdir"><h4> 4.7.1 Directory, ASCII - optional</h4></p>864 <p><a name="corrdir"><h4>3.7.1 Directory, ASCII - optional</h4></p> 869 865 <p> 870 866 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. 871 867 </p> 872 868 873 <p><a name="corrint"><h4> 4.7.2 Interval - mandatory if 'Directory, ASCII' is set</h4></p>869 <p><a name="corrint"><h4>3.7.2 Interval - mandatory if 'Directory, ASCII' is set</h4></p> 874 870 <p> 875 871 Select the length of the Broadcast Correction files. The default value is 1 day. 876 872 </p> 877 873 878 <p><a name="corrport"><h4> 4.7.3 Port - optional</h4></p>874 <p><a name="corrport"><h4>3.7.3 Port - optional</h4></p> 879 875 <p> 880 876 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. … … 921 917 </p> 922 918 923 <p><a name="corrwait"><h4> 4.7.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p>919 <p><a name="corrwait"><h4>3.7.4 Wait for Full Epoch - mandatory if 'Port' is set</h4></p> 924 920 <p> 925 921 When feeding a real-time GNSS network engine waiting epoch by epoch for synchronized Broadcast Corrections, BNC drops (only concerning 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. … … 929 925 </p> 930 926 931 <p><a name="syncout"><h4> 4.8. Feed Engine</h4></p>927 <p><a name="syncout"><h4>3.8. Feed Engine</h4></p> 932 928 <p> 933 929 BNC can generate synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed a real-time GNSS network engine. Observations can be streamed out through an IP port and/or saved in a local file. The output is always in plain ASCII format and comprises the following parameters: … … 987 983 <p><u>Figure 8:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p> 988 984 989 <p><a name="syncport"><h4> 4.8.1 Port - optional</h4></p>985 <p><a name="syncport"><h4>3.8.1 Port - optional</h4></p> 990 986 <p> 991 987 BNC can produce synchronized observations in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Synchronized 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> 992 988 </p> 993 989 994 <p><a name="syncwait"><h4> 4.8.2 Wait for Full Epoch - mandatory if 'Port' is set</h4></p>990 <p><a name="syncwait"><h4>3.8.2 Wait for Full Epoch - mandatory if 'Port' is set</h4></p> 995 991 <p> 996 992 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. … … 1000 996 </p> 1001 997 1002 <p><a name="syncsample"><h4> 4.8.3 Sampling - mandatory if 'File' or 'Port' is set</h4></p>998 <p><a name="syncsample"><h4>3.8.3 Sampling - mandatory if 'File' or 'Port' is set</h4></p> 1003 999 <p> 1004 1000 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. 1005 1001 </p> 1006 1002 1007 <p><a name="syncfile"><h4> 4.8.4 File - optional</h4></p>1003 <p><a name="syncfile"><h4>3.8.4 File - optional</h4></p> 1008 1004 <p> 1009 1005 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. … … 1013 1009 </p> 1014 1010 1015 <p><a name="syncuport"><h4> 4.8.5 Port (unsynchronized) - optional</h4></p>1011 <p><a name="syncuport"><h4>3.8.5 Port (unsynchronized) - optional</h4></p> 1016 1012 <p> 1017 1013 BNC can produce unsynchronized observations from all configured streams in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Unsynchronized 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> 1018 1014 <p> 1019 1015 1020 <p><a name="serial"><h4> 4.9. Serial Output</h4></p>1016 <p><a name="serial"><h4>3.9. Serial Output</h4></p> 1021 1017 <p> 1022 1018 You may use BNC to feed a serial connected device like an GNSS receiver. For that an incoming streams can be forwarded to a serial port. The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an NTRIP Broadcaster to feed a serial connected rover. … … 1025 1021 <p><u>Figure 9:</u> BNC pulling a VRS stream to feed a serial connected rover.</p> 1026 1022 1027 <p><a name="sermount"><h4> 4.9.1 Mountpoint - optional</h4></p>1023 <p><a name="sermount"><h4>3.9.1 Mountpoint - optional</h4></p> 1028 1024 <p> 1029 1025 Enter a 'Mountpoint' to forward its corresponding stream to a serial connected GNSS receiver. … … 1033 1029 </p> 1034 1030 1035 <p><a name="serport"><h4> 4.9.2 Port Name - mandatory if 'Mountpoint' is set</h4></p>1031 <p><a name="serport"><h4>3.9.2 Port Name - mandatory if 'Mountpoint' is set</h4></p> 1036 1032 <p> 1037 1033 Enter the serial 'Port name' selected on your host for communication with the serial connected receiver. Valid port names are … … 1050 1046 </p> 1051 1047 1052 <p><a name="serbaud"><h4> 4.9.3 Baud Rate - mandatory if 'Mountpoint' is set</h4></p>1048 <p><a name="serbaud"><h4>3.9.3 Baud Rate - mandatory if 'Mountpoint' is set</h4></p> 1053 1049 <p> 1054 1050 Select a 'Baud rate' for the serial output link. Note that using a high baud rate is recommended. 1055 1051 </p> 1056 1052 1057 <p><a name="serflow"><h4> 4.9.4 Flow Control - mandatory if 'Mountpoint' is set</h4></p>1053 <p><a name="serflow"><h4>3.9.4 Flow Control - mandatory if 'Mountpoint' is set</h4></p> 1058 1054 <p> 1059 1055 Select a 'Flow control' for the serial output link. Note that your selection must equal the flow control configured to the serial connected device. Select 'OFF' if you don't know better. 1060 1056 </p> 1061 1057 1062 <p><a name="serparity"><h4> 4.9.5 Parity - mandatory if 'Mountpoint' is set</h4></p>1058 <p><a name="serparity"><h4>3.9.5 Parity - mandatory if 'Mountpoint' is set</h4></p> 1063 1059 <p> 1064 1060 Select the 'Parity' for the serial output link. Note that parity is often set to 'NONE'. 1065 1061 </p> 1066 1062 1067 <p><a name="serdata"><h4> 4.9.6 Data Bits - mandatory if 'Mountpoint' is set</h4></p>1063 <p><a name="serdata"><h4>3.9.6 Data Bits - mandatory if 'Mountpoint' is set</h4></p> 1068 1064 <p> 1069 1065 Select the number of 'Data bits' for the serial output link. Note that often '8' data bits are used. 1070 1066 </p> 1071 1067 1072 <p><a name="serstop"><h4> 4.9.7 Stop Bits - mandatory if 'Mountpoint' is set</h4></p>1068 <p><a name="serstop"><h4>3.9.7 Stop Bits - mandatory if 'Mountpoint' is set</h4></p> 1073 1069 <p> 1074 1070 Select the number of 'Stop bits' for the serial output link. Note that often '1' stop bit is used. 1075 1071 </p> 1076 1072 1077 <p><a name="serauto"><h4> 4.9.8 NMEA - mandatory for VRS streams</h4></p>1073 <p><a name="serauto"><h4>3.9.8 NMEA - mandatory for VRS streams</h4></p> 1078 1074 <p> 1079 1075 Select 'Auto' to automatically forward all NMEA-GGA messages coming from your serial connected GNSS receiver to the NTRIP Broadcaster and/or save them in a file. … … 1086 1082 </p> 1087 1083 1088 <p><a name="serfile"><h4> 4.9.9 File - optional if 'Auto' NMEA is set</h4></p>1084 <p><a name="serfile"><h4>3.9.9 File - optional if 'Auto' NMEA is set</h4></p> 1089 1085 <p>Specify the full path to a file where NMEA messages coming from your serial connected receiver are saved. 1090 1086 </p> 1091 <p><a name="serheight"><h4> 4.9.10 Height - mandatory if 'Manual' NMEA is set</h4></p>1087 <p><a name="serheight"><h4>3.9.10 Height - mandatory if 'Manual' NMEA is set</h4></p> 1092 1088 <p> 1093 1089 Specify an approximate 'Height' above mean sea level in meter for your VRS to simulate an initial NMEA-GGA message. Latitude and longitude for that (editable) are taken from the broadcaster's source-table. … … 1097 1093 </p> 1098 1094 1099 <p><a name="advnote"><h4> 4.10. Outages</h4></p>1095 <p><a name="advnote"><h4>3.10. Outages</h4></p> 1100 1096 1101 1097 <p> … … 1112 1108 </p> 1113 1109 1114 <p><a name="obsrate"><h4> 4.10.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold' and 'Script' is set</h4></p>1110 <p><a name="obsrate"><h4>3.10.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold' and 'Script' is set</h4></p> 1115 1111 <p> 1116 1112 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 explicit information from BNC about stream outages and incoming streams that cannot be decoded. 1117 1113 </p> 1118 1114 1119 <p><a name="advfail"><h4> 4.10.2 Failure Threshold - optional</h4></p>1115 <p><a name="advfail"><h4>3.10.2 Failure Threshold - optional</h4></p> 1120 1116 <p> 1121 1117 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 inundate user with too many event reports. … … 1125 1121 </p> 1126 1122 1127 <p><a name="advreco"><h4> 4.10.3 Recovery Threshold - optional</h4></p>1123 <p><a name="advreco"><h4>3.10.3 Recovery Threshold - optional</h4></p> 1128 1124 <p> 1129 1125 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. … … 1133 1129 </p> 1134 1130 1135 <p><a name="advscript"><h4> 4.10.4 Script - optional </h4></p>1131 <p><a name="advscript"><h4>3.10.4 Script - optional </h4></p> 1136 1132 <p> 1137 1133 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. … … 1162 1158 </p> 1163 1159 1164 <p><a name="misc"><h4> 4.11. Miscellaneous</h4></p>1160 <p><a name="misc"><h4>3.11. Miscellaneous</h4></p> 1165 1161 <p> 1166 1162 This section describes several miscellaneous options which can be applied for a single stream (mountpoint) or for all configured streams. … … 1174 1170 1175 1171 1176 <p><a name="miscmount"><h4> 4.11.1 Mountpoint - optional </h4></p>1172 <p><a name="miscmount"><h4>3.11.1 Mountpoint - optional </h4></p> 1177 1173 <p> 1178 1174 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. 1179 1175 </p> 1180 1176 1181 <p><a name="miscperf"><h4> 4.11.2 Log Latency - optional </h4></p>1177 <p><a name="miscperf"><h4>3.11.2 Log Latency - optional </h4></p> 1182 1178 <p> 1183 1179 BNC can average latencies per stream over a certain period of GPS time, the 'Log latency' interval. Mean latencies are calculated from the individual latencies of at most one (first incoming) observation or correction to Broadcast Ephemeris per second. The mean latencies are then saved in BNC's logfile. Note that computing correct latencies requires the clock of the host computer to be properly synchronized. Note further that the latencies available from the 'Latency' tab on the bottom of the main window represent individual latencies and not the mean latencies for the logfile. … … 1207 1203 1208 1204 1209 <p><a name="miscscan"><h4> 4.11.3 Scan RTCM - optional</h4></p>1205 <p><a name="miscscan"><h4>3.11.3 Scan RTCM - optional</h4></p> 1210 1206 <p> 1211 1207 When configuring a GNSS receiver for RTCM stream generation, the firmware's 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. … … 1233 1229 </p> 1234 1230 1235 <p><a name="pppclient"><h4> 4.12. PPP Client</h4></p>1231 <p><a name="pppclient"><h4>3.12. PPP Client</h4></p> 1236 1232 <p> 1237 1233 BNC can derive coordinates for a rover position following the Precise Point Positioning (PPP) approach. It uses either code or code plus phase data in ionosphere free linear combinations P3 or L3. Besides pulling a stream of observations from a dual frequency receiver, this also … … 1350 1346 </p> 1351 1347 1352 <p><a name="pppmode"><h4> 4.12.1 Mode & Mountpoints - optional</h4></p>1348 <p><a name="pppmode"><h4>3.12.1 Mode & Mountpoints - optional</h4></p> 1353 1349 <p> 1354 1350 Specify the Point Positioning mode you want to apply and the mountpoints for observations and Broadcast Corrections. 1355 1351 </p> 1356 1352 1357 <p><a name="pppmodus"><h4> 4.12.1.1 Mode - optional</h4></p>1353 <p><a name="pppmodus"><h4>3.12.1.1 Mode - optional</h4></p> 1358 1354 <p>Choose between plain Single Point Positioning (SPP) and Precise Point Positioning (PPP) in 'Realtime' or 'Post-Processing' mode.</p> 1359 1355 1360 <p><a name="pppobsmount"><h4> 4.12.1.2 Obs Mountpoint - optional</h4></p>1356 <p><a name="pppobsmount"><h4>3.12.1.2 Obs Mountpoint - optional</h4></p> 1361 1357 <p> 1362 1358 Specify an 'Observations Mountpoint' from the list of selected 'Streams' you are pulling if you want BNC to derive coordinates for the affected rover position through a Point Positioning solution. 1363 1359 </p> 1364 1360 1365 <p><a name="pppcorrmount"><h4> 4.12.1.3 Corr Mountpoint - optional</h4></p>1361 <p><a name="pppcorrmount"><h4>3.12.1.3 Corr Mountpoint - optional</h4></p> 1366 1362 <p> 1367 1363 Specify a Broadcast Ephemeris 'Corrections Mountpoint' from the list of selected 'Streams' you are pulling if you want BNC to correct your positioning solution accordingly. 1368 1364 </p> 1369 1365 1370 <p><a name="pppxyz"><h4> 4.12.2 Marker Coordinates - optional</h4></p>1366 <p><a name="pppxyz"><h4>3.12.2 Marker Coordinates - optional</h4></p> 1371 1367 <p> 1372 1368 Enter the reference coordinate components X,Y,Z of the receiver's position in meters if known. This option makes only sense for static observations. Default are empty option fields, meaning that the antenna's XYZ position is unknown. … … 1382 1378 </p> 1383 1379 1384 <p><a name="pppneu"><h4> 4.12.3 Antenna Excentricity - optional</h4></p>1380 <p><a name="pppneu"><h4>3.12.3 Antenna Excentricity - optional</h4></p> 1385 1381 <p> 1386 1382 You may like to specify North, East and Up components of an antenna eccentricity which is the difference between a nearby marker position and the antenna phase center. If you do so BNC will produce coordinates referring to the marker position and not referring to the antenna phase center.. 1387 1383 </p> 1388 1384 1389 <p><a name="pppoutput"><h4> 4.12.4 NMEA & Plot Output - optional</h4></p>1385 <p><a name="pppoutput"><h4>3.12.4 NMEA & Plot Output - optional</h4></p> 1390 1386 <p> 1391 1387 BNC allows to output results from Precise Point Positioning in NMEA format. It can also plot a time series of North, East and UP displacements of coordinate components. 1392 1388 </p> 1393 1389 1394 <p><a name="pppnmeafile"><h4> 4.12.4.1 NMEA File - optional</h4></p>1390 <p><a name="pppnmeafile"><h4>3.12.4.1 NMEA File - optional</h4></p> 1395 1391 <p> 1396 1392 The NMEA sentences generated about once per second are pairs of … … 1407 1403 </p> 1408 1404 1409 <p><a name="pppnmeaport"><h4> 4.12.4.2 NMEA Port - optional</h4></p>1405 <p><a name="pppnmeaport"><h4>3.12.4.2 NMEA Port - optional</h4></p> 1410 1406 <p> 1411 1407 Specify the IP port number of a local port where Point Positioning results become available as NMEA messages. The default value for 'NMEA Port' is an empty option field, meaning that BNC does not provide NMEA messages vi IP port. Note that the NMEA file output and the NMEA IP port output are the same. … … 1415 1411 </p> 1416 1412 1417 <p><a name="pppplot"><h4> 4.12.4.3 PPP Plot - optional</h4></p>1413 <p><a name="pppplot"><h4>3.12.4.3 PPP Plot - optional</h4></p> 1418 1414 <p> 1419 1415 PPP time series of North (red), East(green) and Up (blue) displacements will be plotted in the 'PPP Plot' tab when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified) or referred to the first estimated XYZ coordinate. The sliding PPP time series window will cover the period of the latest 5 minutes. … … 1423 1419 </p> 1424 1420 1425 <p><a name="ppppost"><h4> 4.12.5 Post Processing - optional</h4></p>1421 <p><a name="ppppost"><h4>3.12.5 Post Processing - optional</h4></p> 1426 1422 <p>When in 'Post-Processing mode<ul><li>specifying a RINEX Observation, a RINEX Navigation and a Broadcast Corrections file leads to a PPP solution.</li><li>specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Corrections file leads to a SPP solution.</ul></p> 1427 1423 <p>BNC accepts RINEX Version 2 as well as RINEX Version 3 observation or navigation file formats. Files carrying Broadcast Corrections must have the format produced by BNC in the 'Broadcast Corrections' tab. … … 1430 1426 </p> 1431 1427 1432 <p><a name="ppprecant"><h4> 4.12.6 Antennas - optional</h4></p>1428 <p><a name="ppprecant"><h4>3.12.6 Antennas - optional</h4></p> 1433 1429 <p> 1434 1430 BNC allows to correct observations for antenna phase center offsets and variations. 1435 1431 </p> 1436 1432 1437 <p><a name="pppantex"><h4> 4.12.6.1 ANTEX File - optional</h4></p>1433 <p><a name="pppantex"><h4>3.12.6.1 ANTEX File - optional</h4></p> 1438 1434 <p> 1439 1435 IGS provides a file containing absolute phase center corrections for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required for correcting observations for antenna phase center offsets and variations. It allows you to specify the name of your receiver's antenna (as contained in the ANTEX file) to apply such corrections. … … 1443 1439 </p> 1444 1440 1445 <p><a name="ppprecantenna"><h4> 4.12.6.2 Receiver Antenna Name - optional if 'ANTEX File' is set</h4></p>1441 <p><a name="ppprecantenna"><h4>3.12.6.2 Receiver Antenna Name - optional if 'ANTEX File' is set</h4></p> 1446 1442 <p> 1447 1443 Specify the receiver's antenna name as defined in your ANTEX file. Observations will be corrected for the antenna phase center's offset which may result in a reduction of a few centimeters at max. Corrections for phase center variations are not yet applied by BNC. The specified name must consist of 20 characters. Add trailing blanks if the antenna name has less than 20 characters. Examples: … … 1456 1452 </p> 1457 1453 1458 <p><a name="pppsatant"><h4> 4.12.6.3 Apply Satellite Antenna Offsets - optional if 'ANTEX File' is set</h4></p>1454 <p><a name="pppsatant"><h4>3.12.6.3 Apply Satellite Antenna Offsets - optional if 'ANTEX File' is set</h4></p> 1459 1455 <p> 1460 1456 BNC allows correcting observations for satellite antenna phase center offsets. (This option is not yet implemented.) … … 1466 1462 </p> 1467 1463 1468 <p><a name="pppbasics"><h4> 4.12.7 Basics</h4></p>1464 <p><a name="pppbasics"><h4>3.12.7 Basics</h4></p> 1469 1465 <p>BNC allows using different Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows introducing specific sigmas for code and phase observations as well as for reference coordinates and troposphere estimates. You may also like to carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold. 1470 1466 </p> 1471 1467 1472 <p><a name="pppphase"><h4> 4.12.7.1 Use Phase Obs - optional</h4></p>1468 <p><a name="pppphase"><h4>3.12.7.1 Use Phase Obs - optional</h4></p> 1473 1469 <p> 1474 1470 By default BNC applies a Point Positioning solution using an ionosphere free P3 linear combination of code observations. Tick 'Use phase obs' for an ionosphere free L3 linear combination of phase observations. 1475 1471 </p> 1476 1472 1477 <p><a name="ppptropo"><h4> 4.12.7.2 Estimate Tropo - optional</h4></p>1473 <p><a name="ppptropo"><h4>3.12.7.2 Estimate Tropo - optional</h4></p> 1478 1474 <p> 1479 1475 BNC estimates the tropospheric delay according to equation … … 1487 1483 </p> 1488 1484 1489 <p><a name="pppglo"><h4> 4.12.7.3 Use GLONASS - optional</h4></p>1485 <p><a name="pppglo"><h4>3.12.7.3 Use GLONASS - optional</h4></p> 1490 1486 <p> 1491 1487 By default BNC does not process GLONASS but only GPS observations when in Point Positioning mode. Tick 'Use GLONASS' to use GLONASS observations in addition to GPS (and Galileo if specified) for estimating coordinates in Point Positioning mode. 1492 1488 </p> 1493 1489 1494 <p><a name="pppgal"><h4> 4.12.7.4 Use Galileo - optional</h4></p>1490 <p><a name="pppgal"><h4>3.12.7.4 Use Galileo - optional</h4></p> 1495 1491 <p> 1496 1492 By default BNC does not process Galileo but only GPS observations when in Point Positioning mode. Tick 'Use Galileo' to use Galileo observations in addition to GPS (and GLONASS if specified) for estimating coordinates in Point Positioning mode. 1497 1493 </p> 1498 1494 1499 <p><a name="pppsync"><h4> 4.12.7.5 Sync Corr - optional</h4></p>1495 <p><a name="pppsync"><h4>3.12.7.5 Sync Corr - optional</h4></p> 1500 1496 <p> 1501 1497 Zero value (or empty field) means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value 'Sync Corr' means that the epochs of data are buffered and the processing of each epoch is postponed till the satellite clock corrections not older than 'Sync Corr' are available. Specifying a value of half the update rate of the clock corrections as 'Sync Corr' (i.e. 5 sec) may be appropriate. Note that this causes an additional delay of the PPP solutions in the amount of the update rate. … … 1508 1504 </p> 1509 1505 1510 <p><a name="pppaverage"><h4> 4.12.7.6 Averaging - optional if XYZ is set</h4></p>1506 <p><a name="pppaverage"><h4>3.12.7.6 Averaging - optional if XYZ is set</h4></p> 1511 1507 <p> 1512 1508 Enter the length of a sliding time window in minutes. BNC will continuously output moving average values ns and their RMS as computed from those individual values obtained most recently throughout this period. RMS values presented for XYZ coordinates and tropospheric zenit path delays are bias reduced while RMS values for Nort/East/Up (NEU) displacements are not. Averaged values for XYZ coordinates and their RMS are marked with string "AVE-XYZ" in BNC's log file and 'Log' section while averaged values for NEU displacements and their RMS are marked with string "AVE-NEU" and averaged values for the tropospheric delays and their RMS are marked with string "AVE-TRP". Example: … … 1521 1517 </p> 1522 1518 1523 <p><a name="pppquick"><h4> 4.12.7.7 Quick-Start - optional if XYZ is set</h4></p>1519 <p><a name="pppquick"><h4>3.12.7.7 Quick-Start - optional if XYZ is set</h4></p> 1524 1520 <p> 1525 1521 Enter the lenght of a startup period in seconds for which you want to fix the PPP solution to a known XYZ coordinate. Constraining coordinate components is done in BNC through setting the 'XYZ White Noise' temporarily to zero. … … 1537 1533 <p><u>Figure 14:</u> BNC in 'Quick-Start' mode (PPP, Panel 2)</p> 1538 1534 1539 <p><a name="pppgap"><h4> 4.12.7.8 Maximal Solution Gap - optional if Quick-Start is set</h4></p>1535 <p><a name="pppgap"><h4>3.12.7.8 Maximal Solution Gap - optional if Quick-Start is set</h4></p> 1540 1536 <p> 1541 1537 Specify a 'Maximum Solution Gap' in seconds. Should the time span between two consecutive solutions exceed this limit, the algorithm returns into the Quick-Start mode and fixes the introduced reference coordinate for the specified Quick-Start period. A value of '120' seconds could be an appropriate choice. … … 1545 1541 </p> 1546 1542 1547 <p><a name="pppsigmas"><h4> 4.12.8 Sigmas</h4></p>1543 <p><a name="pppsigmas"><h4>3.12.8 Sigmas</h4></p> 1548 1544 <p> 1549 1545 You may like to introduce specific sigmas for code and phase observations and for the estimation of troposphere parameters. 1550 1546 </p> 1551 1547 1552 <p><a name="pppsigc"><h4> 4.12.8.1 Code - mandatory if 'Use Phase Obs' is set</h4></p>1548 <p><a name="pppsigc"><h4>3.12.8.1 Code - mandatory if 'Use Phase Obs' is set</h4></p> 1553 1549 <p> 1554 1550 When 'Use phase obs' is set in BNC, the PPP solution will be carried out using both, code and phase observations. A sigma of 5.0 m for code observations and a sigma of 0.02 m for phase observations (defaults) are used to combine both types of observations. As the convergence characteristic of a PPP solution can be influenced by the ratio of the sigmas for code and phase, you may like to introduce you own sigmas for code and phase observations which differ from the default values. … … 1562 1558 </p> 1563 1559 1564 <p><a name="pppsigp"><h4> 4.12.8.2 Phase - mandatory if 'Use Phase Obs' is set</h4></p>1560 <p><a name="pppsigp"><h4>3.12.8.2 Phase - mandatory if 'Use Phase Obs' is set</h4></p> 1565 1561 <p> 1566 1562 Specify a sigma for phase observations. Default is 0.02 m. 1567 1563 </p> 1568 1564 1569 <p><a name="pppsigxyzi"><h4> 4.12.8.3 XYZ Init - mandatory</h4></p>1565 <p><a name="pppsigxyzi"><h4>3.12.8.3 XYZ Init - mandatory</h4></p> 1570 1566 <p> 1571 1567 Enter a sigma in meters for the initial XYZ coordinate components. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with known XZY position in Quick-Start mode. 1572 1568 </p> 1573 1569 1574 <p><a name="pppsigxyzn"><h4> 4.12.8.4 XYZ White Noise - mandatory</h4></p>1570 <p><a name="pppsigxyzn"><h4>3.12.8.4 XYZ White Noise - mandatory</h4></p> 1575 1571 <p> 1576 1572 Enter a sigma in meters for the 'White Noise' of estimated XYZ coordinate components. A value of 100.0 (default) may be appropriate considering the potential movement of a rover. 1577 1573 </p> 1578 1574 1579 <p><a name="pppsigtrpi"><h4> 4.12.8.5 Tropo Init - mandatory if 'Estimate tropo' is set</h4></p>1575 <p><a name="pppsigtrpi"><h4>3.12.8.5 Tropo Init - mandatory if 'Estimate tropo' is set</h4></p> 1580 1576 <p> 1581 1577 Enter a sigma in meters for the a-priory model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice. 1582 1578 </p> 1583 1579 1584 <p><a name="pppsigtrpn"><h4> 4.12.8.6 Tropo White Noise - mandatory if 'Estimate tropo' is set</h4></p>1580 <p><a name="pppsigtrpn"><h4>3.12.8.6 Tropo White Noise - mandatory if 'Estimate tropo' is set</h4></p> 1585 1581 <p> 1586 1582 Enter a sigma in meters per second to describe the expected variation of the tropospheric effect. Supposing 1Hz observation data, a value of 3e-6 (default) would mean that the tropospheric effect may vary for 3600 * 3e-6 = 0.01 meters per hour. 1587 1583 </p> 1588 1584 1589 <p><a name="combi"><h4> 4.13. Combine Corrections</h4></p>1585 <p><a name="combi"><h4>3.13. Combine Corrections</h4></p> 1590 1586 <p> 1591 1587 BNC allows to process several orbit and clock corrections streams in real-time to produce, encode, upload and save a combination of Broadcast Corrections from various providers. It is so far only the satellite clock corrections which are combined while orbit corrections in the combination product as well as the product update rates are just taken over from one of the incoming Broadcast Correction streams. Combining only clock corrections using a fixed orbit reference has the possibility to introduce some analysis inconsistencies. We may therefore eventually consider improvements on this approach. The clock combination can be based either on a plain 'Single-Epoch' or on a 'Kalman' Filter approach. … … 1651 1647 </p> 1652 1648 1653 <p><a name="combimounttab"><h4> 4.13.1 Combine Corrections Table - optional</h4></p>1649 <p><a name="combimounttab"><h4>3.13.1 Combine Corrections Table - optional</h4></p> 1654 1650 <p> 1655 1651 Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Corrections mountpoint from the 'Streams' section and hit Enter. Then double click on the 'AC Name' field to enter your choice of an abbreviation for the Analysis Center (AC) providing the stream. Finally, double click on the 'Weight' field to enter a weight to be applied to this stream in the combination. The stream processing can already be started with only one corrections stream configured for combination. … … 1667 1663 </p> 1668 1664 1669 <p><a name="combiadd"><h4> 4.13.1.1 Add Row, Delete - optional</h4></p>1665 <p><a name="combiadd"><h4>3.13.1.1 Add Row, Delete - optional</h4></p> 1670 1666 <p> 1671 1667 Hit 'Add Row' button to add another row to the 'Combine Corrections Table' or hit the 'Delete' button to delete the highlighted row(s). … … 1686 1682 <p><u>Figure 17:</u> 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.</p> 1687 1683 1688 <p><a name="combimethod"><h4> 4.13.1.2 Method - mandatory if 'Combine Corrections Table' is populated</h4></p>1684 <p><a name="combimethod"><h4>3.13.1.2 Method - mandatory if 'Combine Corrections Table' is populated</h4></p> 1689 1685 <p> 1690 1686 Select a clock combination method. Available options are Kalman 'Filter' and 'Single-Epoch. It is suggested to use the Kalman Filter approach in case the combined stream of Broadcast Corrections is intended for Precise Point Positioning support. 1691 1687 </p> 1692 1688 1693 <p><a name="combimax"><h4> 4.13.1.3 Maximal Residuum - mandatory if 'Combine Corrections Table' is populated</h4></p>1689 <p><a name="combimax"><h4>3.13.1.3 Maximal Residuum - mandatory if 'Combine Corrections Table' is populated</h4></p> 1694 1690 1695 1691 <p>BNC combines all incoming clocks according to specified weights. Individual clock estimates that differ by more than 'Maximal Residuum' meters from the average of all clocks will be ignored.<p> … … 1697 1693 <p>Default is a 'Maximal Residuum' of 999.0 meters</p> 1698 1694 1699 <p><a name="combismpl"><h4> 4.13.1.4 Sampling - mandatory if 'Combine Corrections Table' is populated</h4></p>1695 <p><a name="combismpl"><h4>3.13.1.4 Sampling - mandatory if 'Combine Corrections Table' is populated</h4></p> 1700 1696 <p>Specify a combination sampling interval. Clock and orbit corrections will be produced following that interval. A value of 10 sec may be an appropriate choice.</p> 1701 1697 1702 1698 1703 <p><a name="upclk"><h4> 4.14. Upload Corrections</h4></p>1699 <p><a name="upclk"><h4>3.14. Upload Corrections</h4></p> 1704 1700 <p> 1705 1701 BNC can upload streams carrying orbit and clock corrections to Broadcast Ephemeris in radial, along-track and cross-track components if they are<ol type=a> … … 1788 1784 </p> 1789 1785 1790 <p><a name="upadd"><h4> 4.14.1 Add, Delete Row - optional</h4></p>1786 <p><a name="upadd"><h4>3.14.1 Add, Delete Row - optional</h4></p> 1791 1787 <p>Hit 'Add Row' button to add another row to the stream 'Upload Table' or hit the 'Delete' button to delete the highlighted row(s). 1792 1788 </p> … … 1795 1791 </p> 1796 1792 1797 <p><a name="uphost"><h4> 4.14.2 Host, Port, Mountpoint, Password - mandatory if 'Upload Table' entries specified</h4></p>1793 <p><a name="uphost"><h4>3.14.2 Host, Port, Mountpoint, Password - mandatory if 'Upload Table' entries specified</h4></p> 1798 1794 1799 1795 <p>Specify the domain name or IP number of an NTRIP Broadcaster for uploading the stream. Furthermore, specify the caster's listening IP port, an upload mountpoint and an upload password. Note that NTRIP Broadcasters are often configured to provide access on more than one port, usually port 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s). … … 1806 1802 </p> 1807 1803 1808 <p><a name="upsystem"><h4> 4.14.3 System - mandatory if 'Host' is set</h4></p>1804 <p><a name="upsystem"><h4>3.14.3 System - mandatory if 'Host' is set</h4></p> 1809 1805 <p> 1810 1806 BNC allows to configure several Broadcast Correction streams for upload so that they refer to different reference systems and different NTRIP Broadcasters. You may use this functionality for parallel support of a backup NTRIP Broadcaster or for simultaneous support of several reference systems. Available options for referring clock and orbit corrections to specific target reference systems are … … 1951 1947 </p> 1952 1948 1953 <p><a name="upcom"><h4> 4.14.4 Center of Mass - optional</h4></p>1949 <p><a name="upcom"><h4>3.14.4 Center of Mass - optional</h4></p> 1954 1950 <p> 1955 1951 BNC allows to either refer Broadcast Corrections to the satellite's Center of Mass (CoM) or to the satellite's Antenna Phase Center (APC). By default corrections refer to APC. Tick 'Center of Mass' to refer uploaded corrections to CoM. 1956 1952 </p> 1957 1953 1958 <p><a name="upsp3"><h4> 4.14.5 SP3 File - optional</h4></p>1954 <p><a name="upsp3"><h4>3.14.5 SP3 File - optional</h4></p> 1959 1955 <p>Specify a path for saving the generated orbit corrections as SP3 orbit files. If the specified directory does not exist, BNC will not create SP3 orbit files. The following is a path example for a Linux system:<br>/home/user/BNC${GPSWD}.sp3<br>Note that '${GPSWD}' produces the GPS Week and Day number in the file name.</p> 1960 1956 <p> … … 1971 1967 </p> 1972 1968 1973 <p><a name="uprinex"><h4> 4.14.6 RNX File - optional</h4></p>1969 <p><a name="uprinex"><h4>3.14.6 RNX File - optional</h4></p> 1974 1970 <p> 1975 1971 The clock corrections generated by BNC for upload can be logged in Clock RINEX format. The file naming follows the RINEX convention. … … 1982 1978 </p> 1983 1979 1984 <p><a name="upinter"><h4> 4.14.7 Interval - mandatory if 'Upload Table' entries specified</h4></p>1980 <p><a name="upinter"><h4>3.14.7 Interval - mandatory if 'Upload Table' entries specified</h4></p> 1985 1981 <p> 1986 1982 Select the length of Clock RINEX files and SP3 Orbit files. The default value is 1 day. 1987 1983 </p> 1988 1984 1989 <p><a name="upclksmpl"><h4> 4.14.8 Sampling - mandatory if 'Upload Table' entries specified</h4></p>1985 <p><a name="upclksmpl"><h4>3.14.8 Sampling - mandatory if 'Upload Table' entries specified</h4></p> 1990 1986 <p>BNC requires an orbit corrections sampling interval for the stream to be uploaded and sampling interval for SP3 and Clock RINEX files. The outgoing stream's clock correction sampling interval follows that of incoming corrections and is therefore nothing to be specified here.</p> 1991 1987 1992 <p><a name="upclkorb"><h4> 4.14.8.1 Orbits - mandatory if 'Upload Table' entries specified</h4></p>1988 <p><a name="upclkorb"><h4>3.14.8.1 Orbits - mandatory if 'Upload Table' entries specified</h4></p> 1993 1989 <p>Select the stream's orbit correction sampling interval in seconds. A value of 60 sec may be appropriate. A value of zero '0' tells BNC to upload all available samples.</p> 1994 1990 1995 <p><a name="upclksp3"><h4> 4.14.8.2 SP3 - mandatory if 'SP3 File' is specified</h4></p>1991 <p><a name="upclksp3"><h4>3.14.8.2 SP3 - mandatory if 'SP3 File' is specified</h4></p> 1996 1992 <p>Select the SP3 orbit file sampling interval in minutes. A value of 15 min may be appropriate. A value of zero '0' tells BNC to store all available samples into SP3 orbit files.</p> 1997 1993 1998 <p><a name="upclkrnx"><h4> 4.14.8.3 RINEX - mandatory if 'RNX File' is specified</h4></p>1994 <p><a name="upclkrnx"><h4>3.14.8.3 RINEX - mandatory if 'RNX File' is specified</h4></p> 1999 1995 <p>Select the Clock RINEX file sampling interval in seconds. A value of 10 sec may be appropriate. A value of zero '0' tells BNC to store all available samples into Clock RINEX files.</p> 2000 1996 2001 <p><a name="upcustom"><h4> 4.14.9 Custom Trafo - optional if 'Upload Table' entries specified</h4></p>1997 <p><a name="upcustom"><h4>3.14.9 Custom Trafo - optional if 'Upload Table' entries specified</h4></p> 2002 1998 <p>Hit 'Custom Trafo' to specify your own 14 parameter Helmert Transformation instead of selecting a predefined transformation through 'System' button.</p> 2003 1999 … … 2008 2004 <p><u>Figure 18:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.</p> 2009 2005 2010 <p><a name="upeph"><h4> 4.15. Upload Ephemeris</h4></p>2006 <p><a name="upeph"><h4>3.15. Upload Ephemeris</h4></p> 2011 2007 <p> 2012 2008 BNC can upload a stream carrying Broadcast Ephemeris in RTCM Version 3 format to an NTRIP Broadcaster. 2013 2009 </p> 2014 2010 2015 <p><a name="brdcserver"><h4> 4.15.1 Host & Port - optional</h4></p>2011 <p><a name="brdcserver"><h4>3.15.1 Host & Port - optional</h4></p> 2016 2012 <p> 2017 2013 Specify the 'Host' IP name or number of an NTRIP Broadcaster to upload the stream. An empty option field means that you don't want to upload Broadcast Ephemeris. … … 2022 2018 </p> 2023 2019 2024 <p><a name="brdcmount"><h4> 4.15.2 Mountpoint & Password - mandatory if 'Host' is set</h4></p>2020 <p><a name="brdcmount"><h4>3.15.2 Mountpoint & Password - mandatory if 'Host' is set</h4></p> 2025 2021 <p> 2026 2022 BNC uploads a stream to the Caster by referring to a dedicated mountpoint that has been set by the Caster operator. Specify the mountpoint based on the details you received for your stream from the operator. It is often a four character ID (capital letters) plus an integer number.</p> … … 2028 2024 </p> 2029 2025 2030 <p><a name="brdcsmpl"><h4> 4.15.3 Sampling - mandatory if 'Host' is set</h4></p>2026 <p><a name="brdcsmpl"><h4>3.15.3 Sampling - mandatory if 'Host' is set</h4></p> 2031 2027 Select the Broadcast Ephemeris repetition interval in seconds. Defaut is '5' meaning that a complete set of Broadcast Ephemeris is uploaded every 5 seconds. 2032 2028 </p> … … 2035 2031 <p><u>Figure 28:</u> Producting a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an NTRIP Broadcaster.</p> 2036 2032 2037 <p><a name="streams"><h4> 4.16. Streams</h4></p>2033 <p><a name="streams"><h4>3.16. Streams</h4></p> 2038 2034 <p> 2039 2035 Each stream on an NTRIP Broadcaster (and consequently on BNC) 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. … … 2056 2052 </p> 2057 2053 2058 <p><a name="streamedit"><h4> 4.16.1 Edit Streams</h4></p>2054 <p><a name="streamedit"><h4>3.16.1 Edit Streams</h4></p> 2059 2055 <ul> 2060 2056 <li> … … 2071 2067 </ul> 2072 2068 2073 <p><a name="streamdelete"><h4> 4.16.2 Delete Stream</h4></p>2069 <p><a name="streamdelete"><h4>3.16.2 Delete Stream</h4></p> 2074 2070 <p> 2075 2071 To remove a stream from the 'Streams' canvas in the main window, highlight it by clicking on it and hit the 'Delete Stream' button. You can also remove multiple streams simultaneously by highlighting them using +Shift and +Ctrl.</p> 2076 2072 2077 <p><a name="streamconf"><h4> 4.16.3 Reconfigure Streams On-the-fly</h4></p>2073 <p><a name="streamconf"><h4>3.16.3 Reconfigure Streams On-the-fly</h4></p> 2078 2074 <p> 2079 2075 The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process. … … 2085 2081 </p> 2086 2082 2087 <p><a name="logs"><h4> 4.17. Logging</h4></p>2083 <p><a name="logs"><h4>3.17. Logging</h4></p> 2088 2084 <p> 2089 2085 A tabs section on the bottom of the main window provides online control of BNC's activities. Tabs are available to show the records saved in a logfile, for a plot to control the bandwidth consumption, for a plot showing stream latencies, and for time series plots of PPP results. 2090 2086 </p> 2091 <p><a name="logfile"><h4> 4.17.1 Log</h4></p>2087 <p><a name="logfile"><h4>3.17.1 Log</h4></p> 2092 2088 <p> 2093 2089 Records of BNC's activities are shown in the 'Log' tab. They can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. 2094 2090 </p> 2095 2091 2096 <p><a name="throughput"><h4> 4.17.2 Throughput</h4></p>2092 <p><a name="throughput"><h4>3.17.2 Throughput</h4></p> 2097 2093 <p> 2098 2094 The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). The following figure shows the bandwidth comsumption of incoming streams. … … 2102 2098 <p><u>Figure 19:</u> Bandwidth consumption of incoming streams.</p> 2103 2099 2104 <p><a name="latency"><h4> 4.17.3 Latency</h4></p>2100 <p><a name="latency"><h4>3.17.3 Latency</h4></p> 2105 2101 <p> 2106 2102 The latency of observations in each incoming stream is shown in the 'Latency' tab in milliseconds or seconds. Streams not carrying observations (i.e. those providing only Broadcast Ephemeris messages) or having an outage are not considered here and shown in red color. Note that the calculation of correct latencies requires the clock of the host computer to be properly synchronized. The next figure shows the latency of incoming streams. … … 2110 2106 <p><u>Figure 20:</u> Latency of incoming streams.</p> 2111 2107 2112 <p><a name="ppptab"><h4> 4.17.4 PPP Plot</h4></p>2108 <p><a name="ppptab"><h4>3.17.4 PPP Plot</h4></p> 2113 2109 <p> 2114 2110 Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in the 'PPP Plot' tab when a 'Origin' option is defined. Values are either referred to reference coordinates (if specified) or referred to the first estimated set of coordinate components. The time as given in format [hh:mm] refers to GPS Time. The sliding PPP time series window covers a period of 5 minutes. Note that it may take up to 30 seconds or more till the first PPP solutions becomes available. The following figure shows the screenshot of a PPP time series plot of North, East and Up coordinate components. … … 2118 2114 <p><u>Figure 21:</u> Time series plot of PPP session.</p> 2119 2115 2120 <p><a name="bottom"><h4> 4.18. Bottom Menu Bar</h4></p>2116 <p><a name="bottom"><h4>3.18. Bottom Menu Bar</h4></p> 2121 2117 <p> 2122 2118 The bottom menu bar allows to add or delete streams to BNC's configuration and to start or stop it. It also provides access to BNC's online help function. The 'Add Stream' button opens a window that allows user to select one of several input communication links, see figure below. … … 2126 2122 <p><u>Figure 22:</u> Steam input communication links.</p> 2127 2123 2128 <p><a name="streamadd"><h4> 4.18.1 Add Stream - Coming from Caster</h4></p>2124 <p><a name="streamadd"><h4>3.18.1 Add Stream - Coming from Caster</h4></p> 2129 2125 2130 2126 <p> … … 2132 2128 </p> 2133 2129 2134 <p><a name="streamhost"><h4> 4.18.1.1 Caster Host and Port - mandatory</h4></p>2130 <p><a name="streamhost"><h4>3.18.1.1 Caster Host and Port - mandatory</h4></p> 2135 2131 <p> 2136 2132 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> and <u>http://www.products.igs-ip.net/home</u>. 2137 2133 </p> 2138 2134 2139 <p><a name="streamtable"><h4> 4.18.1.2 Casters Table - optional</h4></p>2135 <p><a name="streamtable"><h4>3.18.1.2 Casters Table - optional</h4></p> 2140 2136 <p> 2141 2137 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, see figure below. … … 2146 2142 <p><u>Figure 23:</u> Casters table.</p> 2147 2143 2148 <p><a name="streamuser"><h4> 4.18.1.3 User and Password - mandatory for protected streams</h4></p>2144 <p><a name="streamuser"><h4>3.18.1.3 User and Password - mandatory for protected streams</h4></p> 2149 2145 <p> 2150 2146 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/ntrip/registeruser</u> for access to protected streams on <u>www.euref-ip.net</u> or <u>www.igs-ip.net</u> or <u>products.igs-ip.net</u>. 2151 2147 </p> 2152 2148 2153 <p><a name="gettable"><h4> 4.18.1.4 Get Table</h4></p>2149 <p><a name="gettable"><h4>3.18.1.4 Get Table</h4></p> 2154 2150 <p> 2155 2151 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, RTCM Version 3, or RTNET format. For access to observations, ephemeris or ephemeris corrections, an RTCM Version 2 streams must contain message types 18 and 19 or 20 and 21 while an RTCM Version 3 streams must contain … … 2173 2169 <p>Button 'Map' leads to the presentation of a map showing the distribution of streams offered through the downloaded source-table.</p> 2174 2170 2175 <p><a name="ntripv"><h4> 4.18.1.5 NTRIP Version - mandatory</h4></p>2171 <p><a name="ntripv"><h4>3.18.1.5 NTRIP Version - mandatory</h4></p> 2176 2172 <p> 2177 2173 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: … … 2195 2191 </p> 2196 2192 2197 <p><a name="map"><h4> 4.18.1.6 Map - optional</h4></p>2193 <p><a name="map"><h4>3.18.1.6 Map - optional</h4></p> 2198 2194 <p> 2199 2195 Button 'Map' opens a window to show a distribution map of the casters' streams. You may like to zoom in or out using option 'Zoom +' or 'Zoom -'. You may also like to 'Clean' or 'Reset' a map or let it 'Fit' exactly to the current size of the window. Option 'Close' shuts the window. … … 2202 2198 <p><u>Figure 25:</u> Stream distribution map derived from NTRIP Broadcaster source-table.</p> 2203 2199 2204 <p><a name="streamip"><h4> 4.18.2 Add Stream - Coming from TCP/IP Port</h4></p>2200 <p><a name="streamip"><h4>3.18.2 Add Stream - Coming from TCP/IP Port</h4></p> 2205 2201 <p> 2206 2202 Button 'Add Stream' > '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: … … 2221 2217 </p> 2222 2218 2223 <p><a name="streamudp"><h4> 4.18.3 Add Stream - Coming from UDP Port</h4></p>2219 <p><a name="streamudp"><h4>3.18.3 Add Stream - Coming from UDP Port</h4></p> 2224 2220 <p> 2225 2221 Button 'Add Stream' > 'Coming from UDP Port' allows to pick up streams arriving directly at one of the local host's UDP ports without using the NTRIP transport protocol. For that you: … … 2236 2232 <p> 2237 2233 2238 <p><a name="streamser"><h4> 4.18.4 Add Stream - Coming from Serial Port</h4></p>2234 <p><a name="streamser"><h4>3.18.4 Add Stream - Coming from Serial Port</h4></p> 2239 2235 <p> 2240 2236 Button 'Add Stream' > 'Coming from Serial Port' allows to retrieve streams from a GNSS receiver via serial port without using the NTRIP transport protocol. For that you: … … 2276 2272 <p><u>Figure 26:</u> BNC setup for pulling a stream via serial port.</p> 2277 2273 2278 <p><a name="start"><h4> 4.18.5 Start</h4></p>2274 <p><a name="start"><h4>3.18.5 Start</h4></p> 2279 2275 <p> 2280 2276 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. 2281 2277 </p> 2282 2278 2283 <p><a name="stop"><h4> 4.18.6 Stop</h4></p>2279 <p><a name="stop"><h4>3.18.6 Stop</h4></p> 2284 2280 <p> 2285 2281 Hit the 'Stop' button in order to stop BNC. 2286 2282 </p> 2287 2283 2288 <p><a name="cmd"><h4> 4.19. Command Line Options</h4></p>2284 <p><a name="cmd"><h4>3.19. Command Line Options</h4></p> 2289 2285 <p> 2290 2286 Command line options are available to run BNC in 'no window' mode or let it read data offline from one file or several files for debugging or Post Processing purposes. 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.bnc'. 2291 2287 </p> 2292 2288 2293 <p><a name="nw"><h4> 4.19.1 No Window Mode - optional</h4></p>2289 <p><a name="nw"><h4>3.19.1 No Window Mode - optional</h4></p> 2294 2290 <p> 2295 2291 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. … … 2300 2296 </p> 2301 2297 2302 <p><a name="post"><h4> 4.19.2 File Mode - optional</h4></p>2298 <p><a name="post"><h4>3.19.2 File Mode - optional</h4></p> 2303 2299 <p> 2304 2300 Although BNC is primarily a real-time online tool, for debugging purposes it can be run offline to read data from a file previously saved through option 'Raw output file'. Enter the following command line option for that … … 2317 2313 </p> 2318 2314 2319 <p><a name="conffile"><h4> 4.19.3 Configuration File - optional</h4></p>2315 <p><a name="conffile"><h4>3.19.3 Configuration File - optional</h4></p> 2320 2316 The default configuration file name is 'BNC.bnc'. You may change this name at startup time using the command line option '--conf <<u>confFileName</u>>'. This allows running 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. 2321 2317 </p> … … 2335 2331 </p> 2336 2332 2337 <p><a name="confopt"><h4> 4.19.4 Configuration Options - optional</h4></p>2333 <p><a name="confopt"><h4>3.19.4 Configuration Options - optional</h4></p> 2338 2334 <p> 2339 2335 BNC applies options from the configuration file but allows updating every one of them on the command line while the contents of the configuration file remains unchanged. The command line syntax for that looks as follows … … 2355 2351 </p> 2356 2352 2357 <p><a name="limits"><h3> 5. Limitations & Known Bugs</h3></p>2353 <p><a name="limits"><h3>4. Limitations</h3></p> 2358 2354 <ul> 2359 2355 <li> … … 2381 2377 </ul> 2382 2378 2383 <p><a name="annex"><h3> 6. Annex</h3></p>2384 <p> 2385 6.1. <a href=#history>Revision History</a><br>2386 6.2. <a href=#rtcm>RTCM</a><br>2387 6.2.1 NTRIP <a href=#ntrip1>Version 1</a><br>2388 6.2.2 NTRIP <a href=#ntrip2>Version 2</a><br>2389 6.2.3 RTCM <a href=#rtcm2>Version 2</a><br>2390 6.2.4 RTCM <a href=#rtcm3>Version 3</a><br>2391 6.3. <a href=#config>Configuration Examples</a><br>2392 6.4. <a href=#links>Links</a>2393 </p> 2394 2395 <p><a name=history><h4> 6.1 Revision History</h3></p>2379 <p><a name="annex"><h3>5. Annex</h3></p> 2380 <p> 2381 5.1. <a href=#history>Revision History</a><br> 2382 5.2. <a href=#rtcm>RTCM</a><br> 2383 5.2.1 NTRIP <a href=#ntrip1>Version 1</a><br> 2384 5.2.2 NTRIP <a href=#ntrip2>Version 2</a><br> 2385 5.2.3 RTCM <a href=#rtcm2>Version 2</a><br> 2386 5.2.4 RTCM <a href=#rtcm3>Version 3</a><br> 2387 5.3. <a href=#config>Configuration Examples</a><br> 2388 5.4. <a href=#links>Links</a> 2389 </p> 2390 2391 <p><a name=history><h4>5.1 Revision History</h3></p> 2396 2392 <table> 2397 2393 <tr></tr> … … 2490 2486 </p> 2491 2487 2492 <p><a name="rtcm"><h4> 6.2. RTCM</h4></p>2488 <p><a name="rtcm"><h4>5.2. RTCM</h4></p> 2493 2489 2494 2490 <p> … … 2498 2494 </p> 2499 2495 2500 <p><a name="ntrip1"><h4> 6.2.1 NTRIP Version 1</h4></p>2496 <p><a name="ntrip1"><h4>5.2.1 NTRIP Version 1</h4></p> 2501 2497 2502 2498 <p> … … 2537 2533 </p> 2538 2534 2539 <p><a name="ntrip2"><h4> 6.2.2 NTRIP Version 2</h4></p>2535 <p><a name="ntrip2"><h4>5.2.2 NTRIP Version 2</h4></p> 2540 2536 2541 2537 <p> … … 2555 2551 </p> 2556 2552 2557 <p><a name="rtcm2"><h4> 6.2.3 RTCM Version 2</h4></p>2553 <p><a name="rtcm2"><h4>5.2.3 RTCM Version 2</h4></p> 2558 2554 <p> 2559 2555 Transmitting GNSS carrier phase data can be done through RTCM Version 2 messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of some interest here are: … … 2593 2589 </ul> 2594 2590 2595 <p><a name="rtcm3"><h4> 6.2.4 RTCM Version 3</h4></p>2591 <p><a name="rtcm3"><h4>5.2.4 RTCM Version 3</h4></p> 2596 2592 <p> 2597 2593 RTCM Version 3 has been developed as a more efficient alternative to RTCM Version 2. Service providers and vendors have asked for a standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the Version 2 parity scheme was wasteful of bandwidth. Another complaint was that the parity is not independent from word to word. Still another was that even with so many bits devoted to parity, the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. The Version 3 standard is intended to correct these weaknesses. … … 2667 2663 </p> 2668 2664 2669 <p><a name="config"><h4> 6.3. Configuration Examples</h4></p>2665 <p><a name="config"><h4>5.3. Configuration Examples</h4></p> 2670 2666 2671 2667 <p>BNC comes with a number of configuration examples which can be used on all operating systems. There are two ways to start BNC using one of these files: … … 2922 2918 </p> 2923 2919 2924 <p><a name="links"><h4> 6.4 Links</h3></p>2920 <p><a name="links"><h4>5.4 Links</h3></p> 2925 2921 <table> 2926 2922 <tr></tr>
Note:
See TracChangeset
for help on using the changeset viewer.
