Changeset 2447 in ntrip for trunk/BNC/bnchelp.html
- Timestamp:
- Apr 21, 2010, 12:07:32 PM (15 years ago)
- File:
-
- 1 edited
-
trunk/BNC/bnchelp.html (modified) (12 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r2446 r2447 62 62 63 63 <p> 64 Fig. 1 shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link for the pupose of Precise Point Positioning. Fig. 2 shows the conversion of RTCM streams to RINEX batches. Fig. 3shows a flow chart of BNC feeding a real-time GNSS engine. The engine then estimates satellite orbit and clock correctors. The 'BKG Ntrip Server' (BNS) is used in this scenario to encode correctors to RTCMv3.64 The first of the following figures shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link for the pupose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX batches. The third figure shows a flow chart of BNC feeding a real-time GNSS engine. The engine then estimates satellite orbit and clock correctors. The 'BKG Ntrip Server' (BNS) is used in this scenario to encode correctors to RTCMv3. 65 65 </p> 66 66 <p><img src="IMG/screenshot10.png"/></p> 67 <p><u>Fig . 1:</u> BNC connected to a GNSS receiver for Precise Point Positioning.</p>67 <p><u>Figure:</u> BNC connected to a GNSS receiver for Precise Point Positioning.</p> 68 68 69 69 <p> 70 70 </p> 71 71 <p><img src="IMG/screenshot01.png"/></p> 72 <p><u>Fig . 2:</u> BNC converting RTCM streams to RINEX batches.</p>72 <p><u>Figure:</u> BNC converting RTCM streams to RINEX batches.</p> 73 73 74 74 <p> 75 75 </p> 76 76 <p><img src="IMG/screenshot02.png"/></p> 77 <p><u>Fig . 3:</u> BNC feeding a real-time GNSS engine.</p>77 <p><u>Figuge:</u> BNC feeding a real-time GNSS engine.</p> 78 78 79 79 … … 94 94 <p><a name="options"><h3>3. Options</h3></p> 95 95 <p> 96 This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar, see Fig. 4.96 This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar, see figure below. 97 97 </p> 98 98 <p><img src="IMG/screenshot09.png"/></p> 99 <p><u>Fig . 4:</u> Sections on BNC's main window.</p>99 <p><u>Figure:</u> Sections on BNC's main window.</p> 100 100 101 101 </p> … … 729 729 </p> 730 730 731 </p> 732 The following figure shows the screenshot of a BNC configuration where a number if streams is pulled from different NTRIP broadcasters to feed a GNSS engine via IP port output. 733 </p> 734 <p><img src="IMG/screenshot12.png"/></p> 735 <p><u>Figure:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p> 736 731 737 <p><a name="syncport"><h4>3.7.1 Port - optional</h4></p> 732 738 <p> … … 763 769 <p><a name="serial"><h4>3.8. Serial Output</h4></p> 764 770 <p> 765 You may use BNC to feed a serial connected device like an GNSS receiver. For that one of the incoming streams can be forwarded to a serial port. 766 </p> 771 You may use BNC to feed a serial connected device like an GNSS receiver. For that one of the 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. 772 </p> 773 </p> 774 <p><img src="IMG/screenshot11.png"/></p> 775 <p><u>Figure:</u> BNC pulling a VRS to feed a serial connected rover.</p> 767 776 768 777 <p><a name="sermount"><h4>3.8.1 Mountpoint - optional</h4></p> … … 976 985 </p> 977 986 <p> 978 Fig. 5.provides the screenshot of an example PPP session with BNC.987 The following figure provides the screenshot of an example PPP session with BNC. 979 988 </p> 980 989 <p><img src="IMG/screenshot03.png"/></p> 981 <p><u>Fig . 5:</u> Precise Point Positioning (PPP) with BNC.</p>990 <p><u>Figure:</u> Precise Point Positioning (PPP) with BNC.</p> 982 991 983 992 <p> … … 1172 1181 <p><a name="throughput"><h4>3.13.2 Throughput</h4></p> 1173 1182 <p> 1174 The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 6shows the bandwidth comsumption of incoming streams.1183 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. 1175 1184 </p> 1176 1185 … … 1178 1187 </p> 1179 1188 <p><img src="IMG/screenshot08.png"/></p> 1180 <p><u>Fig . 6:</u> Bandwidth consumption of incoming streams.</p>1189 <p><u>Figure:</u> Bandwidth consumption of incoming streams.</p> 1181 1190 1182 1191 <p><a name="latency"><h4>3.13.3 Latency</h4></p> 1183 1192 <p> 1184 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) are not considered here and shown in read color. Note that the calculation of correct latencies requires the clock of the host computer to be properly synchronized. Fig. 7.shows the latency of incoming streams.1193 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 read 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. 1185 1194 </p> 1186 1195 … … 1188 1197 </p> 1189 1198 <p><img src="IMG/screenshot07.png"/></p> 1190 <p><u>Fig . 7:</u> Latency of incoming streams.</p>1199 <p><u>Figure:</u> Latency of incoming streams.</p> 1191 1200 1192 1201 <p><a name="ppptab"><h4>3.13.4 PPP Plot</h4></p> 1193 1202 <p> 1194 Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in the 'PPP Plot' tab when a 'Plot 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. 1195 </p> 1203 Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in the 'PPP Plot' tab when a 'Plot 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 coordiate components. 1204 </p> 1205 1206 <p> 1207 </p> 1208 <p><img src="IMG/screenshot13.png"/></p> 1209 <p><u>Figure:</u> Time series plot of PPP session.</p> 1196 1210 1197 1211 <p><a name="bottom"><h4>3.14. Bottom Menu Bar</h4></p> … … 1203 1217 1204 1218 <p> 1205 Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 8.1219 Button 'Add Stream' opens a window that allows user to select one of several input communication links, see figure below. 1206 1220 </p> 1207 1221 <p><img src="IMG/screenshot06.png"/></p> 1208 <p><u>Fig . 8:</u> Steam input communication links.</p>1222 <p><u>Figure:</u> Steam input communication links.</p> 1209 1223 1210 1224 <p> … … 1219 1233 <p><a name="streamtable"><h4>3.14.1.2 Casters Table - optional</h4></p> 1220 1234 <p> 1221 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 Fig. 9.1235 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. 1222 1236 </p> 1223 1237 </p> 1224 1238 <p><img src="IMG/screenshot04.png"/></p> 1225 <p><u>Fig . 9:</u> Casters table.</p>1239 <p><u>Figure:</u> Casters table.</p> 1226 1240 1227 1241 <p><a name="streamuser"><h4>3.14.1.3 User and Password - mandatory for protected streams</h4></p> … … 1232 1246 <p><a name="gettable"><h4>3.14.1.4 Get Table</h4></p> 1233 1247 <p> 1234 Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. Fig. 10provides an example source-table.1248 Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example source-table. 1235 1249 </p> 1236 1250 <p> … … 1243 1257 </p> 1244 1258 <p><img src="IMG/screenshot05.png"/></p> 1245 <p><u>Fig . 10:</u> Broadcaster source-table.</p>1259 <p><u>Figure:</u> Broadcaster source-table.</p> 1246 1260 1247 1261 <p><a name="ntripv"><h4>3.14.1.5 NTRIP Version - mandatory</h4></p>
Note:
See TracChangeset
for help on using the changeset viewer.
