Changeset 4427 in ntrip for trunk/BNC/src/bnchelp.html
- Timestamp:
- Jul 16, 2012, 8:52:49 AM (12 years ago)
- File:
-
- 1 edited
-
trunk/BNC/src/bnchelp.html (modified) (21 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r4280 r4427 99 99 <ul> 100 100 <li>RTCM Version 2 message types for GPS and GLONASS observations, </li> 101 <li>RTCM Version 3 'conventional' message types for observations and Broadcast Ephemeris for GPS, GLONASS, SBAS and Galileo (coming soon: COMPASS and QZSS),</li>101 <li>RTCM Version 3 'conventional' message types for observations and Broadcast Ephemeris for GPS, GLONASS, SBAS, Galileo, COMPASS and QZSS,</li> 102 102 <li>RTCM Version 3 'State Space Representation' (SSR) messages for GPS, GLONASS and Galileo,</li> 103 103 <li>Drafted RTCM Version 3 'Multiple Signal Messages' (MSM) and 'High Precision Multiple Signal Messages' (HP MSM),</li> … … 425 425 <p><a name="rinex"><h4>3.4. RINEX Observations</h4></p> 426 426 <p> 427 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 and SBAS (coming soon: 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.427 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. 428 428 </p> 429 429 … … 657 657 658 658 <p><img src="IMG/screenshot25.png"/></p> 659 <p><u>Figure 7:</u> Example for RINEX file editing with BNC in Post Processing mode.</p> 659 <p><u>Figure 8:</u> Example for RINEX file editing with BNC in Post Processing mode.</p> 660 661 <p><img src="IMG/screenshot29.png"/></p> 662 <p><u>Figure 9:</u> Example for RINEX quality check output with BNC in Post Processing mode. A multi-path analysis is presented in terms of a sky plot.</p> 660 663 661 664 <p><a name="reqccommand"><h4>3.6.5 Command Line, No Window - optional</h4></p> … … 1011 1014 </p> 1012 1015 <p><img src="IMG/screenshot12.png"/></p> 1013 <p><u>Figure 8:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p>1016 <p><u>Figure 10:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p> 1014 1017 1015 1018 <p><a name="syncport"><h4>3.8.1 Port - optional</h4></p> … … 1049 1052 </p> 1050 1053 <p><img src="IMG/screenshot11.png"/></p> 1051 <p><u>Figure 9:</u> BNC pulling a VRS stream to feed a serial connected RTK rover.</p>1054 <p><u>Figure 11:</u> BNC pulling a VRS stream to feed a serial connected RTK rover.</p> 1052 1055 1053 1056 <p><a name="sermount"><h4>3.9.1 Mountpoint - optional</h4></p> … … 1200 1203 </p> 1201 1204 <p><img src="IMG/screenshot14.png"/></p> 1202 <p><u>Figure 1 0:</u> RTCM message numbers and latencies.</p>1205 <p><u>Figure 12:</u> RTCM message numbers and latencies.</p> 1203 1206 1204 1207 … … 1275 1278 1276 1279 <p><img src="IMG/screenshot03.png"/></p> 1277 <p><u>Figure 1 1:</u> Precise Point Positioning with BNC, PPP Panel 1.</p>1280 <p><u>Figure 13:</u> Precise Point Positioning with BNC, PPP Panel 1.</p> 1278 1281 1279 1282 <p><img src="IMG/screenshot18.png"/></p> 1280 <p><u>Figure 1 2:</u> Precise Point Positioning with BNC, PPP Panel 2.</p>1283 <p><u>Figure 14:</u> Precise Point Positioning with BNC, PPP Panel 2.</p> 1281 1284 1282 1285 <p> … … 1565 1568 1566 1569 <p><img src="IMG/screenshot17.png"/></p> 1567 <p><u>Figure 1 3:</u> BNC in 'Quick-Start' mode (PPP, Panel 1)</p>1570 <p><u>Figure 15:</u> BNC in 'Quick-Start' mode (PPP, Panel 1)</p> 1568 1571 1569 1572 <p><img src="IMG/screenshot22.png"/></p> 1570 <p><u>Figure 1 4:</u> BNC in 'Quick-Start' mode (PPP, Panel 2)</p>1573 <p><u>Figure 16:</u> BNC in 'Quick-Start' mode (PPP, Panel 2)</p> 1571 1574 1572 1575 <p><a name="pppgap"><h4>3.12.7.8 Maximal Solution Gap - optional if Quick-Start is set</h4></p> … … 1708 1711 <br> 1709 1712 <p><img src="IMG/screenshot20.png"/></p> 1710 <p><u>Figure 1 5:</u> BNC combining Broadcast Correction streams.</p>1713 <p><u>Figure 17:</u> BNC combining Broadcast Correction streams.</p> 1711 1714 <p></p> 1712 1715 <p><img src="IMG/screenshot21.png"/></p> 1713 <p><u>Figure 1 6:</u> BNC uploading the combined Broadcast Corrections stream.</p>1716 <p><u>Figure 18:</u> BNC uploading the combined Broadcast Corrections stream.</p> 1714 1717 <p></p> 1715 1718 <p><img src="IMG/screenshot23.png"/></p> 1716 <p><u>Figure 1 7:</u> 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.</p>1719 <p><u>Figure 19:</u> 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.</p> 1717 1720 1718 1721 <p><a name="combimethod"><h4>3.13.1.2 Method - mandatory if 'Combine Corrections' table is populated</h4></p> … … 2038 2041 </p> 2039 2042 <p><img src="IMG/screenshot26.png"/></p> 2040 <p><u>Figure 18:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.</p>2043 <p><u>Figure 20:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.</p> 2041 2044 2042 2045 <p><a name="upeph"><h4>3.15. Upload Ephemeris</h4></p> … … 2065 2068 2066 2069 <p><img src="IMG/screenshot28.png"/></p> 2067 <p><u>Figure 2 8:</u> Producing 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>2070 <p><u>Figure 21:</u> Producing 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> 2068 2071 2069 2072 <p><a name="streams"><h4>3.16. Streams</h4></p> … … 2132 2135 2133 2136 <p><img src="IMG/screenshot08.png"/></p> 2134 <p><u>Figure 19:</u> Bandwidth consumption of incoming streams.</p>2137 <p><u>Figure 22:</u> Bandwidth consumption of incoming streams.</p> 2135 2138 2136 2139 <p><a name="latency"><h4>3.17.3 Latency</h4></p> … … 2140 2143 2141 2144 <p><img src="IMG/screenshot07.png"/></p> 2142 <p><u>Figure 2 0:</u> Latency of incoming streams.</p>2145 <p><u>Figure 23:</u> Latency of incoming streams.</p> 2143 2146 2144 2147 <p><a name="ppptab"><h4>3.17.4 PPP Plot</h4></p> … … 2148 2151 2149 2152 <p><img src="IMG/screenshot13.png"/></p> 2150 <p><u>Figure 2 1:</u> Time series plot of PPP session.</p>2153 <p><u>Figure 24:</u> Time series plot of PPP session.</p> 2151 2154 2152 2155 <p><a name="bottom"><h4>3.18. Bottom Menu Bar</h4></p> … … 2156 2159 2157 2160 <p><img src="IMG/screenshot06.png"/></p> 2158 <p><u>Figure 2 2:</u> Steam input communication links.</p>2161 <p><u>Figure 25:</u> Steam input communication links.</p> 2159 2162 2160 2163 <p><a name="streamadd"><h4>3.18.1 Add Stream - Coming from Caster</h4></p> … … 2176 2179 <p><img src="IMG/screenshot04.png"/></p> 2177 2180 2178 <p><u>Figure 2 3:</u> Casters table.</p>2181 <p><u>Figure 26:</u> Casters table.</p> 2179 2182 2180 2183 <p><a name="streamuser"><h4>3.18.1.3 User and Password - mandatory for protected streams</h4></p> … … 2194 2197 </p> 2195 2198 <p><img src="IMG/screenshot05.png"/></p> 2196 <p><u>Figure 2 4:</u> Broadcaster source-table.</p>2199 <p><u>Figure 27:</u> Broadcaster source-table.</p> 2197 2200 2198 2201 <p>Button 'Map' leads to the presentation of a map showing the distribution of streams offered through the downloaded source-table.</p> … … 2225 2228 </p> 2226 2229 <p><img src="IMG/screenshot24.png"/></p> 2227 <p><u>Figure 2 5:</u> Stream distribution map derived from NTRIP Broadcaster source-table.</p>2230 <p><u>Figure 28:</u> Stream distribution map derived from NTRIP Broadcaster source-table.</p> 2228 2231 2229 2232 <p><a name="streamip"><h4>3.18.2 Add Stream - Coming from TCP/IP Port</h4></p> … … 2299 2302 </p> 2300 2303 <p><img src="IMG/screenshot15.png"/></p> 2301 <p><u>Figure 2 6:</u> BNC setup for pulling a stream via serial port.</p>2304 <p><u>Figure 29:</u> BNC setup for pulling a stream via serial port.</p> 2302 2305 2303 2306 <p><a name="start"><h4>3.18.5 Start</h4></p> … … 2379 2382 </li> 2380 2383 2381 <li>Observations from COMPASS and QZSS are so far not supported.</li>2382 2384 <li> 2383 2385 Using RTCM Version 3 to produce RINEX files, BNC will properly handle most message types. However, when handling message types 1001, 1003, 1009 and 1011 where the ambiguity field is not set, the output will be no valid RINEX. All values will be stored modulo 299792.458 (speed of light). … … 2505 2507 <tr> 2506 2508 <td>Jul 2012 </td><td>Version 2.7 </td> 2507 <td>[Bug] Bug in L5 decoding fixed<br> [Bug] Bug in on-the-fly configuration fixed<br> [Add] Clock RINEX file header extended<br> [Add] Decoding/converting COMPASS and QZSS added<br> [Add] Work on RINEX quality check started</td>2509 <td>[Bug] Bug in L5 decoding fixed<br> [Bug] Bug in on-the-fly configuration fixed<br> [Add] Clock RINEX file header extended<br> [Add] Decoding/converting COMPASS and QZSS added<br> [Add] Work on RINEX v2 and v3 quality check started<br> [Mod] Source code completely re-arranged<br> [Add] QWT and QWTPOLAR graphics libraries added <br> [Add] RINEX v2 and v3 quality check through multi-path analysis and sky plot</td> 2508 2510 </tr> 2509 2511
Note:
See TracChangeset
for help on using the changeset viewer.
