Changeset 7160 in ntrip


Ignore:
Timestamp:
Aug 3, 2015, 11:17:04 AM (9 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/src/bnchelp.html

    r7156 r7160  
    4848
    4949<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, 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].
     50BNC provides context-sensitive online help (Shift+F1: <i>What's This</i>) related to specific objects. It furthermore comes with the here presented documentation, 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 policy concept) is Dr. Georg Weber [georg.weber@bkg.bund.de].
    5151</p>
    5252
    … …  
    361361
    362362<p>
    363 The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various configuration panels to select a combination of input, processing and output options before you start the program ('Start'). Most configuration panels are dedicated to a certain functionality of BNC. If the first option field on such a configuration panel is empty, the affected functionality is - apart from a few exceptions - deactivated.</p>
    364 
    365 Records of BNC's activities are shown in the 'Log' tab. The bandwidth consumption per stream, the latency of incoming observations and a PPP time series for coordinates are shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs.
     363The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various configuration panels to set a combination of input, processing and output options before you start the program ('Start'). Most configuration panels are dedicated to a certain functionality of BNC. If the first option field on such a configuration panel is empty, the affected functionality is deactivated.</p>
     364
     365Records of BNC's activities are shown in the 'Log' tab whis is part of the 'Log' canvas. The bandwidth consumption per stream, the latency of incoming observations and a PPP time series for coordinate displacements are also part of that canvas and shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs.
    366366</p>
    367367
    … …  
    586586<p><a name="topmenu"><h4>3.1. Top Menu Bar</h4></p>
    587587<p>
    588 The top menu bar allows selecting a font for the BNC windows, save configured options, or quit the program execution. It also provides access to program documentation.
     588The top menu bar allows selecting a font for the BNC windows, save configured options, or quit the program execution. It also provides access to the program's documentation.
    589589</p>
    590590
    … …  
    624624</p>
    625625<p>
    626 BNC comes with a help system providing online information about its functionality and usage. Short descriptions are available for any widget. Focus to the relevant widget and press Shift+F1 to request help information. A help text appears immediately; it disappears as soon as the user does something else. The dialogs on some operating systems may provide a &quot;?&quot; button that users can click; click the relevant widget to pop up the help text.
     626BNC comes with a <i>What's This</i> help system providing online information about its functionality and usage. Short descriptions are available for any widget and program option. Focus to the relevant object and press Shift+F1 to request help information. A help text appears immediately; it disappears as soon as the user does something else. The dialogs on some operating systems may provide a '?' button that users can click; click the relevant widget to pop up the help text.
    627627</p>
    628628
    … …  
    654654Tick 'Ignore SSL authorization errors' if you generally trust the server and don't want to be bothered with this. Note that SSL communication is usually done over port 443.
    655655</p>
     656
     657<p><img src="IMG/screenshot40.png"/></p>
     658<p><u>Figure 7:</u> BNC's 'Network' panel configured to ignore eventually occuring SSL error messages.</p>
    656659
    657660<p><a name="general"><h4>3.3. General</h4></p>
    … …  
    725728<p><a name="rinex"><h4>3.4. RINEX Observations</h4></p>
    726729<p>
    727 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, files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS and/or BDS (BeiDou). 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.
    728 </p>
    729 <p>
    730 It is important to understand that converting RTCM streams to RINEX files requires a priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension' and 'Skeleton Mandatory') and switch to a default selection of observation types when such skeleton file is not available or does not contain the required information. The following is a default selection of observation types specified for a RINEX Version 3 file:
     730Observations 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, files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS and/or BDS (BeiDou). 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' or left blank. 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.
     731</p>
     732<p>
     733It is important to understand that converting RTCM streams to RINEX files requires a priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension' and 'Skeleton Mandatory') and switch to a default selection of observation types when such skeleton file is not available or does not contain the required information. The following is the default selection of observation types specified for a RINEX Version 3 file:
    731734</p>
    732735<pre>
    733 C    9 C2I L2I S2I C6I L6I S6I C7I L7I S7I                  SYS / # / OBS TYPES
    734 E   12 C1X L1X SX1 C5X L5X SX5 C7X L7X SX7 C8X L8X SX8      SYS / # / OBS TYPES
    735 G   15 C1C L1C S1C C1W L1W S1W C2X L2X S2X C2W L2W S2W C5X  SYS / # / OBS TYPES
    736 L5X S5X                                              SYS / # / OBS TYPES
    737 J   15 C1C L1C S1C C1W L1W S1W C2X L2X S2X C2W L2W S2W C5X  SYS / # / OBS TYPES
    738 L5X S5X                                              SYS / # / OBS TYPES
    739 R    6 C1C L1C S1C C2P L2P S2P                              SYS / # / OBS TYPES
    740 S    9 C1C L1C S1C C5I L5I S5I C5Q L5Q S5Q                  SYS / # / OBS TYPES
     736C    8 C1  C1P L1  S1  C2  C2P L2  S2                       SYS / # / OBS TYPES
     737E    8 C1  C1P L1  S1  C2  C2P L2  S2                       SYS / # / OBS TYPES
     738G    8 C1  C1W L1  S1  C2  C2W L2  S2                       SYS / # / OBS TYPES
     739J    8 C1  C1P L1  S1  C2  C2P L2  S2                       SYS / # / OBS TYPES
     740R    8 C1  C1P L1  S1  C2  C2P L2  S2                       SYS / # / OBS TYPES
     741S    8 C1  C1P L1  S1  C2  C2P L2  S2                       SYS / # / OBS TYPES
    741742</pre>
    742743
    … …  
    745746</p>
    746747<p>
    747 The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from various NTRIP Broadcasters as well as from a serial communication link. Specifying a decoder string 'ZERO' means to not convert the affected stream but save its contents as received.
     748The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from various NTRIP Broadcasters as well as from a serial communication link. Specifying a decoder string 'ZERO' means to not convert the affected stream but save its contents as received. The 'SSL Error' recorded in the 'Log' tab is caused by the fact that observation stream downloads from IGS and MGEX Broadcasters initiate the download of a RINEX skeleton file from a HTTPS (TLS/SSL) website and BNC has been configured in this example to ignore SSL errors as shown in the preceding 'Network' panel sreenshot.
    748749</p>
    749750
    750751<p><img src="IMG/screenshot16.png"/></p>
    751 <p><u>Figure 7:</u> BNC translating incoming streams to 15 min RINEX Version 3 files.</p>
    752 
     752<p><u>Figure 8:</u> BNC translating incoming streams to 15 min RINEX Version 3 files.</p>
    753753
    754754<p><a name="rnxname"><h4>3.4.1 RINEX File Names</h4></p>
    … …  
    855855<p>
    856856<pre>
    857             OBSERVATION DATA    M (MIXED)           RINEX VERSION / TYPE
     857                    OBSERVATION DATA    M (MIXED)           RINEX VERSION / TYPE
    858858CUT0                                                        MARKER NAME         
    85985959945M001                                                   MARKER NUMBER       
    8608605023K67889          TRIMBLE NETR9       5.01                REC # / TYPE / VERS
    8618614928353386          TRM59800.00     SCIS                    ANT # / TYPE       
    862 -2364337.2699  4870285.5624 -3360809.8398                  APPROX POSITION XYZ
    863 0.0000        0.0000        0.0000                  ANTENNA: DELTA H/E/N
     862 -2364337.2699  4870285.5624 -3360809.8398                  APPROX POSITION XYZ
     863        0.0000        0.0000        0.0000                  ANTENNA: DELTA H/E/N
    864864gnss@curtin.edu.au  CUT                                     OBSERVER / AGENCY   
    865865C   10 C1I L1I D1I S1I C6I L6I S6I C7I L7I S7I              SYS / # / OBS TYPES
    … …  
    867867G   13 C1C L1C D1C S1C C2W L2W S2W C2X L2X S2X C5X L5X S5X  SYS / # / OBS TYPES
    868868J   19 C1C L1C D1C S1C C1X L1X S1X C1Z L1Z S1Z C2X L2X S2X  SYS / # / OBS TYPES
    869 C5X L5X S5X C6L L6L S6L                              SYS / # / OBS TYPES
     869       C5X L5X S5X C6L L6L S6L                              SYS / # / OBS TYPES
    870870R   13 C1C L1C D1C S1C C1P L1P S1P C2C L2C S2C C2P L2P S2P  SYS / # / OBS TYPES
    871871S    7 C1C L1C D1C S1C C5I L5I S5I                          SYS / # / OBS TYPES
    872872PORTIONS OF THIS HEADER GENERATED BY THE IGS CB FROM        COMMENT             
    873873SITELOG cut0_20150507.log                                   COMMENT             
    874                                                     END OF HEADER
     874                                                            END OF HEADER
    875875</pre>
    876876<p>
    … …  
    12111211
    12121212<p><img src="IMG/screenshot27.png"/></p>
    1213 <p><u>Figure 8:</u> Example for 'RINEX Editing Options' window.</p>
     1213<p><u>Figure 9:</u> Example for 'RINEX Editing Options' window.</p>
    12141214
    12151215<p><img src="IMG/screenshot25.png"/></p>
    1216 <p><u>Figure 9:</u> Example for RINEX file concatenation with BNC.</p>
     1216<p><u>Figure 10:</u> Example for RINEX file concatenation with BNC.</p>
    12171217
    12181218<p><img src="IMG/screenshot29.png"/></p>
    1219 <p><u>Figure 10:</u> Example for creating RINEX quality check analysis graphics output with BNC.</p>
     1219<p><u>Figure 11:</u> Example for creating RINEX quality check analysis graphics output with BNC.</p>
    12201220
    12211221<p><img src="IMG/screenshot30.png"/></p>
    1222 <p><u>Figure 11:</u> Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC.</p>
     1222<p><u>Figure 12:</u> Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC.</p>
    12231223
    12241224<p><img src="IMG/screenshot33.png"/></p>
    1225 <p><u>Figure 12:</u> Sky plot examples for multipath, part of RINEX quality check analysis with BNC.</p>
     1225<p><u>Figure 13:</u> Sky plot examples for multipath, part of RINEX quality check analysis with BNC.</p>
    12261226
    12271227<p><img src="IMG/screenshot34.png"/></p>
    1228 <p><u>Figure 13:</u> Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC.</p>
     1228<p><u>Figure 14:</u> Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC.</p>
    12291229
    12301230<p><a name="reqccommand"><h4>3.6.8 Command Line, No Window - optional</h4></p>
    … …  
    14141414
    14151415<p><img src="IMG/screenshot36.png"/></p>
    1416 <p><u>Figure 14:</u> BNC configuration example for comparing two SP3 files with satellite orbit and clock data.</p>
     1416<p><u>Figure 15:</u> BNC configuration example for comparing two SP3 files with satellite orbit and clock data.</p>
    14171417
    14181418<p><a name="correct"><h4>3.8. Broadcast Corrections</h4></p>
    … …  
    17621762
    17631763<p><img src="IMG/screenshot37.png"/></p>
    1764 <p><u>Figure 15:</u> BNC configuration example for pulling, saving and output of Broadcast Corrections.</p>
     1764<p><u>Figure 16:</u> BNC configuration example for pulling, saving and output of Broadcast Corrections.</p>
    17651765
    17661766<p><a name="syncout"><h4>3.9. Feed Engine</h4></p>
    … …  
    18431843</p>
    18441844<p><img src="IMG/screenshot12.png"/></p>
    1845 <p><u>Figure 16:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p>
     1845<p><u>Figure 17:</u> Synchronized BNC output via IP port to feed a GNSS real-time engine.</p>
    18461846
    18471847<p><a name="syncport"><h4>3.9.1 Port - optional</h4></p>
    … …  
    18851885
    18861886<p><img src="IMG/screenshot35.png"/></p>
    1887 <p><u>Figure 17:</u> Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams.</p>
     1887<p><u>Figure 18:</u> Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams.</p>
    18881888
    18891889<p>
    … …  
    18921892
    18931893<p><img src="IMG/screenshot11.png"/></p>
    1894 <p><u>Figure 18:</u> BNC pulling a VRS stream to feed a serial connected RTK rover.</p>
     1894<p><u>Figure 19:</u> BNC pulling a VRS stream to feed a serial connected RTK rover.</p>
    18951895
    18961896<p><a name="sermount"><h4>3.10.1 Mountpoint - optional</h4></p>
    … …  
    20512051</p>
    20522052<p><img src="IMG/screenshot14.png"/></p>
    2053 <p><u>Figure 19:</u> RTCM message numbers, latencies and observation types.</p>
     2053<p><u>Figure 20:</u> RTCM message numbers, latencies and observation types.</p>
    20542054
    20552055
    … …  
    21742174
    21752175<p><img src="IMG/screenshot03.png"/></p>
    2176 <p><u>Figure 20:</u> Real-time Precise Point Positioning with BNC, PPP Panel 1.</p>
     2176<p><u>Figure 21:</u> Real-time Precise Point Positioning with BNC, PPP Panel 1.</p>
    21772177
    21782178<p><a name="pppdatasource"><h4>3.13.1.1 Data Source - optional</h4></p>
    … …  
    25692569
    25702570<p><img src="IMG/screenshot17.png"/></p>
    2571 <p><u>Figure 21:</u> Precise Point Positioning with BNC, PPP Panel 2.</p>
     2571<p><u>Figure 22:</u> Precise Point Positioning with BNC, PPP Panel 2.</p>
    25722572
    25732573<p><a name="pppsite"><h4>3.13.2.1 Station - mandatory</h4></p>
    … …  
    26142614
    26152615<p><img src="IMG/screenshot18.png"/></p>
    2616 <p><u>Figure 22:</u> Precise Point Positioning with BNC, PPP Panel 3.</p>
     2616<p><u>Figure 23:</u> Precise Point Positioning with BNC, PPP Panel 3.</p>
    26172617
    26182618<p><a name="ppplinecombi"><h4>3.13.3.1 Linear Combinations - mandatory</h4></p>
    … …  
    27202720
    27212721<p><img src="IMG/screenshot22.png"/></p>
    2722 <p><u>Figure 23:</u> BNC in 'Quick-Start' mode (PPP, Panel 2)</p>
     2722<p><u>Figure 24:</u> BNC in 'Quick-Start' mode (PPP, Panel 2)</p>
    27232723
    27242724<p><a name="pppaverage"><h4>3.13.3.NN Averaging - optional if XYZ is set</h4></p>
    … …  
    27582758
    27592759<p><img src="IMG/screenshot32.png"/></p>
    2760 <p><u>Figure 24:</u> Track of positions from BNC with Google Maps in the background.</p>
     2760<p><u>Figure 25:</u> Track of positions from BNC with Google Maps in the background.</p>
    27612761
    27622762<p><a name="pppmaptype"><h4>3.13.4.3.1 Google/OSM - mandatory before pushing 'Open Map'</h4></p>
    … …  
    28692869<br>
    28702870<p><img src="IMG/screenshot20.png"/></p>
    2871 <p><u>Figure 25:</u> BNC combining Broadcast Correction streams.</p>
     2871<p><u>Figure 26:</u> BNC combining Broadcast Correction streams.</p>
    28722872<p></p>
    28732873<p><img src="IMG/screenshot21.png"/></p>
    2874 <p><u>Figure 26:</u> BNC uploading the combined Broadcast Corrections stream.</p>
     2874<p><u>Figure 27:</u> BNC uploading the combined Broadcast Corrections stream.</p>
    28752875<p></p>
    28762876<p><img src="IMG/screenshot23.png"/></p>
    2877 <p><u>Figure 27:</u> 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.</p>
     2877<p><u>Figure 28:</u> 'INTERNAL' PPP with BNC using combined Broadcast Corrections stream.</p>
    28782878
    28792879<p><a name="combimethod"><h4>3.13.1.2 Method - mandatory if 'Combine Corrections' table is populated</h4></p>
    … …  
    31983198
    31993199<p><img src="IMG/screenshot38.png"/></p>
    3200 <p><u>Figure 28:</u> Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94'.</p>
     3200<p><u>Figure 29:</u> Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94'.</p>
    32013201
    32023202<p><a name="upcom"><h4>3.15.4 Center of Mass - optional</h4></p>
    … …  
    32873287</p>
    32883288<p><img src="IMG/screenshot26.png"/></p>
    3289 <p><u>Figure 29:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.</p>
     3289<p><u>Figure 30:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.</p>
    32903290
    32913291<p><a name="upantex"><h4>3.15.10 ANTEX File - mantatory if 'SP3 File' is specified</h4></p>
    … …  
    33183318
    33193319<p><img src="IMG/screenshot28.png"/></p>
    3320 <p><u>Figure 30:</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>
     3320<p><u>Figure 31:</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>
    33213321
    33223322<p><a name="streams"><h4>3.17. Streams</h4></p>
    … …  
    33853385
    33863386<p><img src="IMG/screenshot08.png"/></p>
    3387 <p><u>Figure 31:</u> Bandwidth consumption of incoming streams.</p>
     3387<p><u>Figure 32:</u> Bandwidth consumption of incoming streams.</p>
    33883388
    33893389<p><a name="latency"><h4>3.18.3 Latency</h4></p>
    … …  
    33933393
    33943394<p><img src="IMG/screenshot07.png"/></p>
    3395 <p><u>Figure 32:</u> Latency of incoming streams.</p>
     3395<p><u>Figure 33:</u> Latency of incoming streams.</p>
    33963396
    33973397<p><a name="ppptab"><h4>3.18.4 PPP Plot</h4></p>
    … …  
    34013401
    34023402<p><img src="IMG/screenshot13.png"/></p>
    3403 <p><u>Figure 33:</u> Time series plot of PPP session.</p>
     3403<p><u>Figure 34:</u> Time series plot of PPP session.</p>
    34043404
    34053405<p><a name="bottom"><h4>3.19. Bottom Menu Bar</h4></p>
    … …  
    34093409
    34103410<p><img src="IMG/screenshot06.png"/></p>
    3411 <p><u>Figure 34:</u> Steam input communication links.</p>
     3411<p><u>Figure 35:</u> Steam input communication links.</p>
    34123412
    34133413<p><a name="streamadd"><h4>3.19.1 Add Stream</h4></p>
    … …  
    34343434<p><img src="IMG/screenshot04.png"/></p>
    34353435
    3436 <p><u>Figure 35:</u> Casters table.</p>
     3436<p><u>Figure 36:</u> Casters table.</p>
    34373437
    34383438<p><a name="streamuser"><h4>3.19.1.1.3 User and Password - mandatory for protected streams</h4></p>
    … …  
    34523452</p>
    34533453<p><img src="IMG/screenshot05.png"/></p>
    3454 <p><u>Figure 36:</u> Broadcaster source-table.</p>
     3454<p><u>Figure 37:</u> Broadcaster source-table.</p>
    34553455
    34563456<p><a name="ntripv"><h4>3.19.1.1.5 NTRIP Version - mandatory</h4></p>
    … …  
    34893489
    34903490<p><img src="IMG/screenshot24.png"/></p>
    3491 <p><u>Figure 37:</u> Stream distribution map derived from NTRIP Broadcaster source-table.</p>
     3491<p><u>Figure 38:</u> Stream distribution map derived from NTRIP Broadcaster source-table.</p>
    34923492
    34933493<p><a name="streamip"><h4>3.19.1.2 Add Stream - Coming from TCP/IP Port</h4></p>
    … …  
    35633563</p>
    35643564<p><img src="IMG/screenshot15.png"/></p>
    3565 <p><u>Figure 38:</u> BNC setup for pulling a stream via serial port.</p>
     3565<p><u>Figure 39:</u> BNC setup for pulling a stream via serial port.</p>
    35663566
    35673567<p><a name="streamsdelete"><h4>3.19.2 Delete Stream</h4></p>
Note: See TracChangeset for help on using the changeset viewer.