Changeset 7155 in ntrip for trunk/BNC/src/bnchelp.html
- Timestamp:
- Jul 28, 2015, 4:19:07 PM (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r7154 r7155 1 1 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> 2 2 3 <h3>BKG Ntrip Client (BNC) Version 2.12.0 Manual</h3>3 <h3>BKG Ntrip Client (BNC) Version 2.12.0</h3> 4 4 5 5 <p> … … 17 17 </p> 18 18 <p> 19 Feel free to send us comments, suggestions or bug reports. Your contribution would be appreciated. 20 </p> 21 22 <p><b>Contents</b><br> 23 <a href="#purpose">1. Purpose</a><br> 24 <a href="#opthandling">2. Handling</a><br> 25 <a href="#optsettings">3. Settings</a><br> 26 <a href="#limits">4. Limitations</a><br> 27 <a href="#annex">5. Annex</a> 28 </p> 29 30 <p> 31 <b><a name="authors">Authors</b><br> 19 Feel free to send us comments, suggestions or bug reports. Any contribution would be appreciated. 20 </p> 21 22 <p> 23 <b><a name="authors">Authors</b><br><br> 32 24 The BKG Ntrip Client (BNC) and its Qt Graphical User Interface (GUI) has been developed for 33 25 </p> 34 26 <p> 35 27 Federal Agency for Cartography and Geodesy (BKG)<br> 36 c/o Dr. Georg Weber<br>37 Department of Geodesy<br>28 Department of Geodesy, Section Navigation<br> 29 c/o Dr. Axel Rülke<br> 38 30 Frankfurt, Germany<br> 39 [ euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de]40 </p> 41 42 <p> 43 BNC waswritten by31 [axel.ruelke@bkg.bund.de] 32 </p> 33 34 <p> 35 The BNC software has been written by 44 36 </p> 45 37 … … 52 44 53 45 <p> 54 While work on BNC started in June 2005, Prof. Mervart's sole responsibility for the program code and concept lasted till February 2015. Since March 2015 the expert in charge at BKG for further developments is 55 </p> 56 57 <p> 58 Dipl.-Ing. Andrea Stürze<br> 59 Federal Agency for Cartography and Geodesy (BKG)<br> 60 Department of Geodesy<br> 61 Section Navigation<br> 62 Frankfurt, Germany<br> 63 [andrea.stuerze@bkg.bund.de] 46 Prof. Mervart started working on BNC in June 2005. His sole responsibility for the program code ended February 2015. Since March 2015 the expert in charge at BKG for further BNC programming is Dipl.-Ing. Andrea Stürze [andrea.stuerze@bkg.bund.de]. 47 </p> 48 49 <p> 50 BNC provides context-sensitive online help (Shift+F1: <i>'What's This'</i>) related to specific objects. It furthermore comes with this software documentation which is available as an integral part of the software and as a PDF file. Responsible for online and offline documentation, example configurations (and till February 2014 the overall BNC concept) is Dr. Georg Weber [georg.weber@bkg.bund.de]. 64 51 </p> 65 52 … … 72 59 </p> 73 60 <p> 74 Note that some figures presented in this documentation show screenshots from earlier versions of BNC. If so then there is either no relevant change compared to the current appearance of the program or no change at all.61 Note that some figures presented in this documentation may show screenshots from earlier versions of BNC. If so then there is either no relevant change compared to the current appearance of the program or no change at all. 75 62 </p> 76 63 … … 105 92 </p> 106 93 94 <p><b>Contents</b><br> 95 <a href="#purpose">1. Purpose</a><br> 96 <a href="#opthandling">2. Handling</a><br> 97 <a href="#optsettings">3. Settings</a><br> 98 <a href="#limits">4. Limitations</a><br> 99 <a href="#annex">5. Annex</a> 100 <br><br> 101 </p> 102 103 <p><b>List of Figures</b><br><br> 104 <table> 105 <tr><td><b>Fig. </b></td><td><b>Title</b></td><td><b>Chapter</b></td></tr> 106 <tr><td>1</td><td>Flowchart, BNC connected to a GNSS rover for Precise Point Positioning</b></td><td>1.2</td></tr> 107 <tr><td>2</td><td>Flowchart, BNC converting RTCM streams to RINEX batches</td><td>1.2</td></tr> 108 <tr><td>3</td><td>Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections</td><td>1.2</td></tr> 109 <tr><td>4</td><td>Flowchart, BNC combining Broadcast Correction streams</td><td>1.2</td></tr> 110 <tr><td>5</td><td>Sections on BNC's main window</td><td>2</td></tr> 111 <tr><td>6</td><td>Management of configuration options in BNC</td><td>2.1</td></tr> 112 <tr><td>7</td><td>BNC translating incoming streams to 15 min RINEX Version 3 files</td><td>3.4</td></tr> 113 <tr><td>8</td><td>Example for 'RINEX Editing Options' window</td><td>3.6.7</td></tr> 114 <tr><td>9</td><td>Example for RINEX file concatenation with BNC</td><td>3.6.7</td></tr> 115 <tr><td>10</td><td>Example for creating RINEX quality check analysis graphics output with BNC</td><td>3.6.7</td></tr> 116 <tr><td>11</td><td>Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC</td><td>3.6.7</td></tr> 117 <tr><td>12</td><td>Sky plot examples for multipath, part of RINEX quality check analysis with BNC</td><td>3.6.7</td></tr> 118 <tr><td>13</td><td>Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC</td><td>3.6.7</td></tr> 119 <tr><td>14</td><td>BNC configuration example for comparing two SP3 files with satellite orbit and clock data</td><td>3.7.3</td></tr> 120 <tr><td>15</td><td>BNC configuration example for pulling, saving and output of Broadcast Corrections</td><td>3.8.3</td></tr> 121 <tr><td>16</td><td>Synchronized BNC output via IP port to feed a GNSS real-time engine</td><td>3.9</td></tr> 122 <tr><td>17</td><td>Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams</td><td>3.10</td></tr> 123 <tr><td>18</td><td>BNC pulling a VRS stream to feed a serial connected RTK rover</td><td>3.10</td></tr> 124 <tr><td>19</td><td>RTCM message numbers, latencies and observation types</td><td>3.12</td></tr> 125 <tr><td>20</td><td>Real-time Precise Point Positioning with BNC, PPP Panel 1</td><td>3.13.1</td></tr> 126 <tr><td>21</td><td>Precise Point Positioning with BNC, PPP Panel 2</td><td>3.13.2</td></tr> 127 <tr><td>22</td><td>Precise Point Positioning with BNC, PPP Panel 3</td><td>3.13.3</td></tr> 128 <tr><td>23</td><td>BNC in 'Quick-Start' mode (PPP, Panel 2)</td><td>3.13.3.8</td></tr> 129 <tr><td>24</td><td>Track of positions from BNC with Google Maps in the background</td><td>3.13.4.3</td></tr> 130 <tr><td>25</td><td>BNC combining Broadcast Correction streams</td><td>3.14.1.1</td></tr> 131 <tr><td>26</td><td>BNC uploading the combined Broadcast Corrections stream</td><td>3.14.1.1</td></tr> 132 <tr><td>27</td><td>'INTERNAL' PPP with BNC using combined Broadcast Corrections stream</td><td>3.14.1.1</td></tr> 133 <tr><td>28</td><td>Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94'</td><td>3.15.3</td></tr> 134 <tr><td>29</td><td>Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster</td><td>3.15.9</td></tr> 135 <tr><td>30</td><td>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</td><td>3.16.3</td></tr> 136 <tr><td>31</td><td>Bandwidth consumption of incoming streams</td><td>3.18.2</td></tr> 137 <tr><td>32</td><td>Latency of incoming streams</td><td>3.18.3</td></tr> 138 <tr><td>33</td><td>Time series plot of PPP session</td><td>3.18.4</td></tr> 139 <tr><td>34</td><td>Steam input communication links</td><td>3.19</td></tr> 140 <tr><td>35</td><td>Casters table</td><td>3.19.1.1.2</td></tr> 141 <tr><td>36</td><td>Broadcaster source-table</td><td>3.19.1.1.4</td></tr> 142 <tr><td>37</td><td>Stream distribution map derived from NTRIP Broadcaster source-table</td><td>3.19.1.1.6</td></tr> 143 <tr><td>38</td><td>BNC setup for pulling a stream via serial port</td><td>3.19.1.4</td></tr> 144 </table> 145 </p> 146 147 <p><b>List of Tables</b><br><br> 148 <table> 149 <tr><td><b>Tab. </b></td><td><b>Title</b></td><td><b>Chapter</b></td></tr> 150 <tr><td>1</td><td>Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems</b></td><td>1.1</td></tr> 151 </table> 152 </p> 153 107 154 <p><a name="purpose"><h3>1. Purpose</h3></p> 108 155 … … 172 219 The table mentions if a message implementation in BNC could so far only be based on a 'RTCM Proposal'. 173 220 </p> 174 <p><u>Table:</u> Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems</p> 175 221 <p><u>Table 1:</u> Status of RTCM Version 3 message implementations in BNC supporting various GNSS systems</p> 176 222 <p></p> 177 223 <table border="1" rules="rows" frame="box" bgcolor="#FFF5EE" style="font-size:13"> … … 339 385 <p><u>Figure 6:</u> Management of configuration options in BNC:<br> 340 386 <table> 341 <tr></tr>342 387 <tr><td> </td><td>Left:</td><td>BNC in graphics mode; active configuration options are introduced through GUI input fields and finally saved on disk.</td></tr> 343 388 <tr><td> </td><td>Middle:</td><td>BNC in 'no window' mode; active configuration options are read from disk.</td></tr> … … 1177 1222 1178 1223 <p><img src="IMG/screenshot33.png"/></p> 1179 <p><u>Figure 12:</u> Sky plot examples for multipath, part of RINEX quality check analysis with BNC. .</p>1224 <p><u>Figure 12:</u> Sky plot examples for multipath, part of RINEX quality check analysis with BNC.</p> 1180 1225 1181 1226 <p><img src="IMG/screenshot34.png"/></p> 1182 <p><u>Figure 13:</u> Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC. .</p>1227 <p><u>Figure 13:</u> Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC.</p> 1183 1228 1184 1229 <p><a name="reqccommand"><h4>3.6.8 Command Line, No Window - optional</h4></p> … … 4300 4345 4301 4346 <p> 4302 The following table's left column is a list of options as contained in BNC's configuration files (default: BNC.bnc). 4303 </p> 4347 The following table shows a list of options contained in BNC's configuration files (default file name: BNC.bnc). 4348 </p> 4349 4350 <p><u>Table 2:</u> BNC configuration options<br> 4304 4351 <table> 4305 4352 <tr></tr> … … 4497 4544 <tr><td>mountPoints</td><td>Add stream coming from ...</td></tr> 4498 4545 <tr><td>ntripVersion</td><td>NTRIP Version</td></tr> 4499 4500 4546 </table> 4501 4547 </p> 4548 4502 4549 <p> 4503 4550 Note that the following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data:
Note:
See TracChangeset
for help on using the changeset viewer.