Changeset 7556 in ntrip


Ignore:
Timestamp:
Oct 28, 2015, 6:35:53 PM (7 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/src/bnchelp.html

    r7555 r7556  
    311311<ul>
    312312<li> RTCM 2 decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, Germany;</li>
    313 <li> RTCM 3 decoder for conventional and MSM observation messages and a RTCM 3 encoder & decoder for SSR messages, both written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld, Germany.</li>
     313<li> RTCM 3 decoder for conventional and MSM observation messages and a RTCM 3 encoder & decoder for SSR messages, both written for BKG by Dirk St&ouml;cker, Alberding GmbH, Sch&ouml;nefeld, Germany.</li>
    314314</ul>
    315315</p>
     
    399399</p>
    400400<p>
    401 Note that BNC allows to by-pass its decoding and conversion algorithms for incoming streams, leave whatever is received untouched to save it in files or output it through local TCP/IP port.
     401Note that BNC allows to by-pass decoding and conversion algorithms for incoming streams, leave whatever is received untouched to save it in files or output it through local TCP/IP port.
    402402</p>
    403403
     
    556556
    557557<p>
    558 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 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>
    559 
    560 Records 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.
     558The 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.
     559</p>
     560
     561<p>
     562Records of BNC's activities are shown in the 'Log' tab which 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.
    561563</p>
    562564
     
    699701<li>File 'RinexQC.bnc'<br>
    700702The purpose of this configuration is to check the quality of a RINEX Version 3
    701 file through a multipath analysis. The results is saved in disk in terms of a
     703file through a multipath analysis. The results are saved on disk in terms of a
    702704plot in PNG format. See section 'RINEX Editing & QC' in the documentation for
    703705examples on how to call BNC from command line in 'no window' mode for RINEX
     
    879881<p><h3>2. <a name="optsettings">Settings Details</h3></p>
    880882<p>
    881 The following chapters describes how to set BNC program options. They explain the 'Top Menu Bar', the 'Settings Canvas' with the processing options, the contents of the 'Streams Canvas' and 'Logging Canvas', and the 'Bottom Menu Bar'.
     883The following chapters describe how to set BNC program options. They explain the 'Top Menu Bar', the 'Settings Canvas' with the processing options, the contents of the 'Streams Canvas' and 'Logging Canvas', and the 'Bottom Menu Bar'.
    882884</p>
    883885<p>
     
    935937
    936938<p><h4>2.2.2 <a name="ssl">SSL - Transport Layer Security</h4></p>
    937 <p>Communication with an Ntrip Broadcaster over Secure Sockets Layer (SSL) as well as the download of RINEX skeleton files when available from HTTPS websites require the exchange of client and/or server certificates. Specify the path to a directory where you save certificates on your system. You may like to check out <u>http://software.rtcm-ntrip.org/wiki/Certificates</u> for a list of known Ntrip Server certificates. You may also just try communication via SSL to check out whether this is supported by the involved Ntrip Broadcaster. </p>
     939<p>Communication with an Ntrip Broadcaster over Secure Sockets Layer (SSL) as well as the download of RINEX skeleton files when available from HTTPS websites requires the exchange of client and/or server certificates. Specify the path to a directory where you save certificates on your system. You may like to check out <u>http://software.rtcm-ntrip.org/wiki/Certificates</u> for a list of known Ntrip Server certificates. You may also just try communication via SSL to check out whether this is supported by the involved Ntrip Broadcaster. </p>
    938940<p>SSL communication may involve queries coming from the Ntrip Broadcaster or from a HTTPS website hosting RINEX skeletons. Such a query could show up under BNC's 'Log' tab as follows:
    939941<pre>
     
    941943   Server Certificate Issued by:
    942944   GNSS Data Center
    943    BKG (Bundesamt fuer Geodaesie und Kartographie)
     945   BKG (Bundesamt f&uuml;r Geod&auml;sie und Kartographie)
    944946   Cannot be verified
    945947
     
    25482550<p><h4>2.12.3 <a name="miscscan">Scan RTCM - optional</h4></p>
    25492551<p>
    2550 When configuring a GNSS receiver for RTCM stream generation, the firmware's setup interface may not provide details about RTCM message types and observation types. As reliable information concerning stream contents should be available i.e. for Ntrip Broadcaster operators to maintain the broadcaster's source-table, BNC allows to scan RTCM streams for incoming message types and printout some of the contained meta-data. Contained observation types are also printed because such information is required a priori for the conversion of RTCM Version 3 MSM streams to RINEX Version 3 files. The idea for this option arose from 'inspectRTCM', a comprehensive stream analyzing tool written by D. Stoecker.
     2552When configuring a GNSS receiver for RTCM stream generation, the firmware's setup interface may not provide details about RTCM message types and observation types. As reliable information concerning stream contents should be available i.e. for Ntrip Broadcaster operators to maintain the broadcaster's source-table, BNC allows to scan RTCM streams for incoming message types and printout some of the contained meta-data. Contained observation types are also printed because such information is required a priori for the conversion of RTCM Version 3 MSM streams to RINEX Version 3 files. The idea for this option arose from 'inspectRTCM', a comprehensive stream analyzing tool written by D. St&ouml;cker.
    25512553</p>
    25522554<p>
     
    25952597<p><h4>2.13 <a name="pppclient">PPP Client</h4></p>
    25962598<p>
    2597 BNC can derive coordinates for rover positions following the Precise Point Positioning (PPP) approach. It uses either code or code plus phase data from one or more GNSS systems in ionosphere-free linear combinations P3 or L3. Besides pulling streams of observations from dual frequency GNSS receiver, this also
     2599BNC can derive coordinates for rover positions following the Precise Point Positioning (PPP) approach. It uses code or code plus phase data from one or more GNSS systems in ionosphere-free linear combinations P3 or L3. Besides pulling streams of observations from dual frequency GNSS receiver, this also
    25982600<ul>
    25992601<li>Requires pulling in addition a stream carrying satellite orbit and clock corrections to Broadcast Ephemeris in the form of RTCM Version 3 'State Space Representation' (SSR) messages. Note that for BNC these Broadcast Corrections need to be referred to the satellite's Antenna Phase Center (APC). Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/orbits</u>. Stream 'CLK11' on Ntrip Broadcaster 'products.igs-ip.net:2101' is an example.</li>
     
    28032805</p>
    28042806<p>
    2805 Default is an empty check box, meaning to create filenames following the RINEX Version 2 standard. The file contents is not affected by this option. It only concerns the filename notation.
     2807Default is an empty check box, meaning to create filenames following the RINEX Version 2 standard. The file content is not affected by this option. It only concerns the filename notation.
    28062808</p>
    28072809<p>
     
    32903292</p>
    32913293<p>
    3292 The 'Open Map' button opens a windows showing a map according to the selected 'Google/OSM' option.
     3294The 'Open Map' button opens a window showing a map according to the selected 'Google/OSM' option.
    32933295</p>
    32943296
     
    37413743<p><h4>2.15.4 <a name="upcom">Center of Mass - optional</h4></p>
    37423744<p>
    3743 BNC allows to either refer Broadcast Corrections to the satellite's Center of Mass (CoM) or to the satellite's Antenna Phase Center (APC). By default corrections refer to APC. Tick 'Center of Mass' to refer uploaded corrections to CoM.
     3745BNC allows to either referring Broadcast Corrections to the satellite's Center of Mass (CoM) or to the satellite's Antenna Phase Center (APC). By default corrections refer to APC. Tick 'Center of Mass' to refer uploaded corrections to CoM.
    37443746</p>
    37453747
     
    38323834<p><u>Figure 32:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster.</p>
    38333835
    3834 <p><h4>2.15.10 <a name="upantex">ANTEX File - mantatory if 'SP3 File' is specified</h4></p>
     3836<p><h4>2.15.10 <a name="upantex">ANTEX File - mandatory if 'SP3 File' is specified</h4></p>
    38353837<p>
    38363838IGS provides a file containing absolute phase center variations for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required here for referring the SP3 file contents to the satellite's Center of Mass (CoM). If you don't specify a ANTEX file, the SP3 file will contain orbit information which is referred to Antenna Phase Center (APC) instead of CoM.
     
    39313933<p><h4>2.18 <a name="logs">Logging Canvas</h4></p>
    39323934<p>
    3933 The 'Logging Canvas' above the bottom menu bar on the main window labeled 'Log', 'Throughput', 'Lacenty', and 'PPP Plot' provides control of BNC's activities. Tabs are available for continuously showing logfile contents, for a plot controling the bandwidth consumption, for a plot showing stream latencies, and for time series plots of PPP results.
     3935The 'Logging Canvas' above the bottom menu bar on the main window labeled 'Log', 'Throughput', 'Lacenty', and 'PPP Plot' provides control of BNC's activities. Tabs are available for continuously showing logfile contents, for a plot controlling the bandwidth consumption, for a plot showing stream latencies, and for time series plots of PPP results.
    39343936</p>
    39353937<p><h4>2.18.1 <a name="logfile">Log</h4></p>
     
    47594761   reqcOldAntennaNumber  {Old antenna number [character string]}
    47604762   reqcNewAntennaNumber  {New antenna number [character string]}
    4761    reqcOldAntennadN      {Old north eccentritity [character string]}
     4763   reqcOldAntennadN      {Old north eccentricity [character string]}
    47624764   reqcNewAntennadN      {New north eccentricity [character string]}
    47634765   reqcOldAntennadE      {Old east eccentricity [character string]}
     
    48284830
    48294831PPP Client Panel 2 keys:
    4830    PPP/staTable {Station specifications table [character string, semicolon separated list, each element in quotaion marks, example:
     4832   PPP/staTable {Station specifications table [character string, semicolon separated list, each element in quotation marks, example:
    48314833                "FFMJ1,100.0,100.0,100.0,100.0,100.0,100.0,0.1,3e-6,7777";"CUT07,100.0,100.0,100.0,100.0,100.0,100.0,0.1,3e-6,7778"]}
    48324834
Note: See TracChangeset for help on using the changeset viewer.