Changeset 2443 in ntrip
- Timestamp:
- Apr 20, 2010, 3:35:09 PM (15 years ago)
- Location:
- trunk/BNC
- Files:
-
- 1 added
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnc.qrc
r2439 r2443 15 15 <file alias="screenshot07.png">IMG/screenshot07.png</file> 16 16 <file alias="screenshot08.png">IMG/screenshot08.png</file> 17 <file alias="screenshot09.png">IMG/screenshot09.png</file> 17 18 </qresource> 18 19 </RCC> -
trunk/BNC/bnchelp.html
r2442 r2443 88 88 <p><a name="options"><h3>3. Options</h3></p> 89 89 <p> 90 This section describes BNC's top menu bar, its processing options, the 'Streams' and 'Log' sections, and the bottom menu bar. 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. 91 </p> 92 <p><img src=":/bnchelp/screenshot09.png"/></p> 93 <p><u>Fig. 3:</u> Sections on BNC's main window.</p> 94 91 95 </p> 92 96 <p> … … 966 970 </p> 967 971 <p> 968 Fig. 3. provides the screenshot of an example PPP session with BNC.972 Fig. 4. provides the screenshot of an example PPP session with BNC. 969 973 </p> 970 974 <p><img src=":/bnchelp/screenshot03.png"/></p> 971 <p><u>Fig. 3:</u> Precise Point Positioning (PPP) with BNC.</p>975 <p><u>Fig. 4:</u> Precise Point Positioning (PPP) with BNC.</p> 972 976 973 977 <p> … … 1162 1166 <p><a name="throughput"><h4>3.13.2 Throughput</h4></p> 1163 1167 <p> 1164 The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 4shows the bandwidth comsumption of a number of incoming streams.1168 The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). Fig. 5 shows the bandwidth comsumption of a number of incoming streams. 1165 1169 </p> 1166 1170 … … 1168 1172 </p> 1169 1173 <p><img src=":/bnchelp/screenshot08.png"/></p> 1170 <p><u>Fig. 4:</u> Bandwidth consumption of a number of incoming streams.</p>1174 <p><u>Fig. 5:</u> Bandwidth consumption of a number of incoming streams.</p> 1171 1175 1172 1176 <p><a name="latency"><h4>3.13.3 Latency</h4></p> 1173 1177 <p> 1174 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. 5. shows the latency of a number of incoming streams.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. 1175 1179 </p> 1176 1180 … … 1178 1182 </p> 1179 1183 <p><img src=":/bnchelp/screenshot07.png"/></p> 1180 <p><u>Fig. 5:</u> Latency of incoming streams.</p>1184 <p><u>Fig. 6:</u> Latency of incoming streams.</p> 1181 1185 1182 1186 <p><a name="ppptab"><h4>3.13.4 PPP Plot</h4></p> … … 1193 1197 1194 1198 <p> 1195 Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 6.1199 Button 'Add Stream' opens a window that allows user to select one of several input communication links, see Fig. 7. 1196 1200 </p> 1197 1201 <p><img src=":/bnchelp/screenshot06.png"/></p> 1198 <p><u>Fig. 6:</u> Steam input communication links.</p>1202 <p><u>Fig. 7:</u> Steam input communication links.</p> 1199 1203 1200 1204 <p> … … 1209 1213 <p><a name="streamtable"><h4>3.14.1.2 Casters Table - optional</h4></p> 1210 1214 <p> 1211 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. 7.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. 1212 1216 </p> 1213 1217 </p> 1214 1218 <p><img src=":/bnchelp/screenshot04.png"/></p> 1215 <p><u>Fig. 7:</u> Casters table.</p>1219 <p><u>Fig. 8:</u> Casters table.</p> 1216 1220 1217 1221 <p><a name="streamuser"><h4>3.14.1.3 User and Password - mandatory for protected streams</h4></p> … … 1222 1226 <p><a name="gettable"><h4>3.14.1.4 Get Table</h4></p> 1223 1227 <p> 1224 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. 8provides an example source-table.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. 9 provides an example source-table. 1225 1229 </p> 1226 1230 <p> … … 1233 1237 </p> 1234 1238 <p><img src=":/bnchelp/screenshot05.png"/></p> 1235 <p><u>Fig. 8:</u> Broadcaster source-table.</p>1239 <p><u>Fig. 9:</u> Broadcaster source-table.</p> 1236 1240 1237 1241 <p><a name="ntripv"><h4>3.14.1.5 NTRIP Version - mandatory</h4></p>
Note:
See TracChangeset
for help on using the changeset viewer.