Changeset 2444 in ntrip for trunk/BNC/bnchelp.html
- Timestamp:
- Apr 20, 2010, 4:04:10 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r2443 r2444 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. The purpose could i.e. be PPP or conversion of RTCM streams to RINEX files. Fig. 2 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. 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. 3 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 </p> 66 <p><img src=":/bnchelp/screenshot10.png"/></p> 67 <p><u>Fig. 1:</u> BNC connected to a GNSS receiver for Precise Point Positioning.</p> 68 69 <p> 65 70 </p> 66 71 <p><img src=":/bnchelp/screenshot01.png"/></p> 67 <p><u>Fig. 1:</u> BNC connected to a GNSS receiver.</p>72 <p><u>Fig. 2:</u> BNC converting RTCM streams to RINEX batches.</p> 68 73 69 74 <p> 70 75 </p> 71 76 <p><img src=":/bnchelp/screenshot02.png"/></p> 72 <p><u>Fig. 2:</u> BNC feeding a real-time GNSS engine.</p> 77 <p><u>Fig. 3:</u> BNC feeding a real-time GNSS engine.</p> 78 73 79 74 80 <p><a name="resources"><h3>2. Modes & Resources</h3></p> … … 88 94 <p><a name="options"><h3>3. Options</h3></p> 89 95 <p> 90 This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar, see Fig. 3.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. 91 97 </p> 92 98 <p><img src=":/bnchelp/screenshot09.png"/></p> 93 <p><u>Fig. 3:</u> Sections on BNC's main window.</p>99 <p><u>Fig. 4:</u> Sections on BNC's main window.</p> 94 100 95 101 </p> … … 970 976 </p> 971 977 <p> 972 Fig. 4. provides the screenshot of an example PPP session with BNC.978 Fig. 5. provides the screenshot of an example PPP session with BNC. 973 979 </p> 974 980 <p><img src=":/bnchelp/screenshot03.png"/></p> 975 <p><u>Fig. 4:</u> Precise Point Positioning (PPP) with BNC.</p>981 <p><u>Fig. 5:</u> Precise Point Positioning (PPP) with BNC.</p> 976 982 977 983 <p> … … 1166 1172 <p><a name="throughput"><h4>3.13.2 Throughput</h4></p> 1167 1173 <p> 1168 The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 5shows the bandwidth comsumption of a number of incoming streams.1174 The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 6 shows the bandwidth comsumption of a number of incoming streams. 1169 1175 </p> 1170 1176 … … 1172 1178 </p> 1173 1179 <p><img src=":/bnchelp/screenshot08.png"/></p> 1174 <p><u>Fig. 5:</u> Bandwidth consumption of a number of incoming streams.</p>1180 <p><u>Fig. 6:</u> Bandwidth consumption of a number of incoming streams.</p> 1175 1181 1176 1182 <p><a name="latency"><h4>3.13.3 Latency</h4></p> 1177 1183 <p> 1178 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. 6. shows the latency of a number of incoming streams.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 a number of incoming streams. 1179 1185 </p> 1180 1186 … … 1182 1188 </p> 1183 1189 <p><img src=":/bnchelp/screenshot07.png"/></p> 1184 <p><u>Fig. 6:</u> Latency of incoming streams.</p>1190 <p><u>Fig. 7:</u> Latency of incoming streams.</p> 1185 1191 1186 1192 <p><a name="ppptab"><h4>3.13.4 PPP Plot</h4></p> … … 1197 1203 1198 1204 <p> 1199 Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 7.1205 Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 8. 1200 1206 </p> 1201 1207 <p><img src=":/bnchelp/screenshot06.png"/></p> 1202 <p><u>Fig. 7:</u> Steam input communication links.</p>1208 <p><u>Fig. 8:</u> Steam input communication links.</p> 1203 1209 1204 1210 <p> … … 1213 1219 <p><a name="streamtable"><h4>3.14.1.2 Casters Table - optional</h4></p> 1214 1220 <p> 1215 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. 8.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. 1216 1222 </p> 1217 1223 </p> 1218 1224 <p><img src=":/bnchelp/screenshot04.png"/></p> 1219 <p><u>Fig. 8:</u> Casters table.</p>1225 <p><u>Fig. 9:</u> Casters table.</p> 1220 1226 1221 1227 <p><a name="streamuser"><h4>3.14.1.3 User and Password - mandatory for protected streams</h4></p> … … 1226 1232 <p><a name="gettable"><h4>3.14.1.4 Get Table</h4></p> 1227 1233 <p> 1228 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. 9provides an example source-table.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. 10 provides an example source-table. 1229 1235 </p> 1230 1236 <p> … … 1237 1243 </p> 1238 1244 <p><img src=":/bnchelp/screenshot05.png"/></p> 1239 <p><u>Fig. 9:</u> Broadcaster source-table.</p>1245 <p><u>Fig. 10:</u> Broadcaster source-table.</p> 1240 1246 1241 1247 <p><a name="ntripv"><h4>3.14.1.5 NTRIP Version - mandatory</h4></p>
Note:
See TracChangeset
for help on using the changeset viewer.