Changeset 4037 in ntrip for trunk/BNC


Ignore:
Timestamp:
Apr 23, 2012, 4:52:45 PM (13 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r4036 r4037  
    33
    44<p>
    5 The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding, converting and processing real-time GNSS data streams from NTRIP broadcasters like <u>http://www.euref-ip.net/home</u>, <u>http://www.igs-ip.net/home</u> or <u>http://products.igs-ip.net/home</u>. It furthermore allows to edit, concatenate or check the quality of RINEX files.
    6 </p>
    7 
    8 <p>
    9 BNC has been developed for the Federal Agency for Cartography and Geodesy (BKG) within the framework of EUREF's Real-time GNSS Project (EUREF-IP, IP for Internet Protocol) and the Real-Time IGS Pilot Project (RTIGS).
     5The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding, converting and processing real-time GNSS data streams from NTRIP broadcasters like <u>http://www.euref-ip.net/home</u>, <u>http://www.igs-ip.net/home</u> or <u>http://products.igs-ip.net/home</u>. It furthermore allows to edit and concatenate RINEX files or check their quality.
     6</p>
     7
     8<p>
     9BNC has been developed for the Federal Agency for Cartography and Geodesy (BKG) within the framework of the IAG subcommission for Europe (EUREF) and the International GNSS Service (IGS).
    1010</p>
    1111
    … …  
    1515
    1616<p>
    17 Please ensure that you have installed the latest version of BNC available from <u>http://igs.bkg.bund.de/ntrip/download</u>. We are continuously working on the program and would appreciate if you could send any comments, suggestions, or bug reports to [euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de].
     17Please ensure that you have installed the latest version of BNC available from <u>http://igs.bkg.bund.de/ntrip/download</u>. We are continuously working on the program and would appreciate if you could send comments, suggestions, or bug reports to [euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de].
    1818</p>
    1919
    … …  
    3535<ul>
    3636<li>retrieve real-time GNSS data streams available through NTRIP transport protocol,</li>
    37 <li>retrieve real-time GNSS data streams via TCP directly from an IP address without using the NTRIP transport protocol, and/or</li>
    38 <li>retrieve real-time GNSS data streams from a local UDP or serial port without using the NTRIP transport protocol, and/or</li>
    39 <li>generate high-rate RINEX Observation and Navigation files to support near real-time GNSS post-processing applications, and/or</li>
    40 <li>generate ephemeris and synchronized or unsynchronized observations epoch by epoch through an IP port to support real-time GNSS network engines, and/or</li>
    41 <li>generate clock and orbit corrections to broadcast ephemeris through an IP port to support real-time Precise Point Positioning on GNSS rovers, and/or</li>
    42 <li>generate synchronized or unsynchronized clock and orbit corrections to broadcast ephemeris epoch by epoch through an IP port to support the (outside) combination of such streams as coming simultaneously from various correction providers, and/or</li>
    43 <li>monitor the performance of a network of real-time GNSS data streams to generate advisory notes in case of outages or corrupted streams, and/or</li>
    44 <li>scan RTCM streams for incoming antenna information as well as message types and their repetition rates, and/or</li>
    45 <li>feed a stream into a GNSS receiver via serial communication link, and/or</li>
    46 <li>carry out a real-time Precise Point Positioning to determine a GNSS rover position, and/or</li>
    47 <li>simultaneously process several incoming orbit and clock corrections streams to produce, encode and upload a combination solution, and/or</li>
    48 <li>upload a Broadcast Ephemeris stream in RTCM Version 3 format, and/or</li>
    49 <li>read GNSS clocks and orbits in a SP3-like format from an IP port - they can be produced by a real-time GNSS engine such as RTNet and should be referenced to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system - and</li>
    50 <ul>
    51 <li>convert the IGS Earth-Centered-Earth-Fixed clocks and and orbits into corrections to Broadcast Ephemeris with radial, along-track and cross-track components.</li>
    52 <li>upload the clock and orbit corrections as an RTCM Version 3.x stream to an NTRIP Broadcaster.</li>
    53 <li>refer the clock and orbit corretions to a specific reference system.</li>
    54 <li>log the Broadcast Ephemeris clock corrections as Clock RINEX files for further processing using other tools than BNC</li>
    55 <li>log the Broadcast Ephemeris orbit corrections as SP3 files for further processing using other tools than BNC.</li>
     37<li>retrieve real-time GNSS data streams via TCP directly from an IP address without using the NTRIP transport protocol,</li>
     38<li>retrieve real-time GNSS data streams from a local UDP or serial port without using the NTRIP transport protocol,</li>
     39<li>generate high-rate RINEX Observation and Navigation files to support near real-time GNSS post-processing applications,</li>
     40<li>generate ephemeris and synchronized or unsynchronized observations epoch by epoch through an IP port to support real-time GNSS network engines,</li>
     41<li>generate clock and orbit corrections to broadcast ephemeris through an IP port to support real-time Precise Point Positioning on GNSS rovers,</li>
     42<li>generate synchronized or unsynchronized clock and orbit corrections to broadcast ephemeris epoch by epoch through an IP port to support the (outside) combination of such streams as coming simultaneously from various correction providers,</li>
     43<li>monitor the performance of a network of real-time GNSS data streams to generate advisory notes in case of outages or corrupted streams,</li>
     44<li>scan RTCM streams for incoming antenna information as well as message types and their repetition rates,</li>
     45<li>feed a stream into a GNSS receiver via serial communication link,</li>
     46<li>carry out a real-time Precise Point Positioning to determine a GNSS rover position,</li>
     47<li>simultaneously process several incoming orbit and clock corrections streams to produce, encode and upload a combination solution,</li>
     48<li>upload a Broadcast Ephemeris stream in RTCM Version 3 format,</li>
     49<li>read GNSS clocks and orbits in a SP3-like format from an IP port - they can be produced by a real-time GNSS engine such as RTNet and should be referenced to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and</li>
     50<ul>
     51<li>convert the IGS Earth-Centered-Earth-Fixed clocks and and orbits into corrections to Broadcast Ephemeris with radial, along-track and cross-track components,</li>
     52<li>upload the clock and orbit corrections as an RTCM Version 3.x stream to an NTRIP Broadcaster,</li>
     53<li>refer the clock and orbit corretions to a specific reference system,</li>
     54<li>log the Broadcast Ephemeris clock corrections as Clock RINEX files for further processing using other tools than BNC,</li>
     55<li>log the Broadcast Ephemeris orbit corrections as SP3 files for further processing using other tools than BNC,</li>
    5656</ul>
    5757<li>edit or concatenate RINEX files or check their quality.</li>
    … …  
    6060
    6161<p>
    62 BNC mainly supports decoding the following GNSS stream formats and message types:
     62BNC supports decoding the following GNSS stream formats and message types:
    6363</p>
    6464<p>
    6565<ul>
    6666<li>RTCM Version 2 message types for GPS and GLONASS observations, </li>
    67 <li>RTCM Version 3 'conventional' message types for observations and Broadcast Ephemeris for GPS, GLONASS, SBAS, Galileo, COMPASS, and QZSS.</li>
    68 <li>RTCM Version 3 'State Space Representation' (SSR) messages for GPS, GLONASS and Galileo.</li>
    69 <li>RTCM Version 3 'Multiple Signal Messages' (MSM) and 'High Precision Multiple Signal Messages' (HP MSM).</li>
     67<li>RTCM Version 3 'conventional' message types for observations and Broadcast Ephemeris for GPS, GLONASS, SBAS, Galileo, COMPASS, and QZSS,</li>
     68<li>RTCM Version 3 'State Space Representation' (SSR) messages for GPS, GLONASS and Galileo,</li>
     69<li>RTCM Version 3 'Multiple Signal Messages' (MSM) and 'High Precision Multiple Signal Messages' (HP MSM),</li>
    7070<li>RTNET, a plain ASCII format defined within BNC to receive orbits and clock from a serving GNSS engine.
    7171</ul>
    … …  
    7474
    7575<p>
    76 The first of the following figures shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link for the pupose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX files. The third figure shows a flow chart of BNC feeding a real-time GNSS engine. The engine then estimates satellite orbit and clock correctors. BNC is used in this scenario to encode correctors to RTCM Version 3 and upload them to an NTRIP Broadcaster..
     76The first of the following figures shows a flow chart of BNC connected to a GNSS receiver providing observations via serial or TCP communication link for the pupose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX files. The third figure shows a flow chart of BNC feeding a real-time GNSS engine which estimates satellite orbit and clock correctors. BNC is used in this scenario to encode correctors to RTCM Version 3 and upload them to an NTRIP Broadcaster. The fourth figure shows BNC combining several broadcast corrections streams to disseminate the combination product while saving results in SP3 and clock RINEX files.
    7777</p>
    7878<p><img src="IMG/screenshot10.png"/></p>
    … …  
    9797<p><a name="resources"><h3>2. Modes &amp; Resources</h3></p>
    9898<p>
    99 Although BNC is a real-time tool to be operated online, it can be run offline
     99Although BNC is mainly a real-time tool to be operated online, it can be run offline
    100100<ul>
    101101<li>to simulate real-time observation situations for debugging purposes,</li>
    … …  
    115115
    116116<p>
    117 The main window of BNC shows a top menu bar section, a sections for tabs to set processing options, a 'Streams' section and a section for 'Log' tabs, and a bottom menu bar section, see figure below.
     117The main window of BNC shows a 'Top menu bar' section, a 'Settings' sections with tabs to set processing options, a 'Streams' section, a section for 'Log' tabs, and a 'Bottom menu bar' section, see figure below.
    118118</p>
    119119<p><img src="IMG/screenshot09.png"/></p>
    … …  
    123123<p><a name="options"><h3>3. Settings &amp; Handling</h3></p>
    124124<p>
    125 This chapter describes BNC's settings and how to handle the program. It explains the top menu bar, the processing options, the 'Streams' and 'Log' sections, and the bottom menu bar.
    126 </p>
    127 
    128 <p>
    129 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 tabs to select a combination of input, processing and output options before you start the program ('Start'). Records of BNC's activities are shown in the 'Log' tab. The bandwidth consumption per stream, the latency of incoming observations and PPP time series for coordinate components are shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs of the main window.
     125This chapter describes how to handle BNC and how to set the program options. It explains the top menu bar, the processing options, the 'Streams' and 'Log' sections, and the bottom menu bar.
     126</p>
     127
     128<p>
     129The 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 tabs to select a combination of input, processing and output options before you start the program ('Start'). 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 of the main window.
    130130</p>
    131131<p>
    132132As a default, configuration files for running BNC on Unix/Linux/Mac systems are saved in directory '${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'. The default configuration file name is 'BNC.ini'.</p>
    133133<p>
    134 The default file name 'BNC.ini' can be changed and the file contents can easily be edited. On graphical user interfaces it is possible to Drag &amp; Drop a configuration file icon to start BNC (not on Mac systems). Some configuration options can be changed on-the-fly. See annexed 'Configuration Example' for a complete set of configuration options.
     134The default file name 'BNC.ini' can be changed and the file contents can easily be edited. On graphical user interfaces it is possible to Drag &amp; Drop a configuration file icon to start BNC (not on Mac systems). Some configuration options can be changed on-the-fly. See annexed 'Configuration Example' for a complete set of configuration options. It is also possible to start and configure BNC via command line.
    135135</p>
    136136<p>
Note: See TracChangeset for help on using the changeset viewer.