Changeset 4041 in ntrip


Ignore:
Timestamp:
Apr 23, 2012, 11:11:16 PM (13 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r4039 r4041  
    4747<li>simultaneously process several incoming orbit and clock corrections streams to produce, encode and upload a combination solution,</li>
    4848<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>
     49<li>read GNSS clocks and orbits in a plain ASCII 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>
    5050<ul>
    5151<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>
    … …  
    936936<p><a name="serial"><h4>3.9. Serial Output</h4></p>
    937937<p>
    938 You may use BNC to feed a serial connected device like an GNSS receiver. For that one of the incoming streams can be forwarded to a serial port. The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an NTRIP broadcaster to feed a serial connected rover.
     938You may use BNC to feed a serial connected device like an GNSS receiver. For that an incoming streams can be forwarded to a serial port. The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an NTRIP broadcaster to feed a serial connected rover.
    939939</p>
    940940<p><img src="IMG/screenshot11.png"/></p>
    … …  
    13241324</p>
    13251325<p>
    1326 Note that Tomoji Takasu has written a Windows program called RTKPlot for visualizing NMEA strings. It is available from <u>http://gpspp.sakura.ne.jp/rtklib/rtklib.htm</u> and compatible with the NMEA output of BNC's 'PPP Client' option.
     1326Note that Tomoji Takasu has written a program called RTKPlot for visualizing NMEA strings. It is available from <u>http://gpspp.sakura.ne.jp/rtklib/rtklib.htm</u> and compatible with the NMEA output of BNC's 'PPP Client' option.
    13271327</p>
    13281328
    … …  
    13371337<p><a name="pppplot"><h4>3.12.4.3 PPP Plot - optional</h4></p>
    13381338<p>
    1339 PPP time series of North (red), East(green) and Up (blue) coordinate components will be plotted in the 'PPP Plot' tab when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified) or referred to the first estimated XYZ coordinate. The sliding PPP time series window will cover the period of the latest 5 minutes.
     1339PPP time series of North (red), East(green) and Up (blue) displacements will be plotted in the 'PPP Plot' tab when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified) or referred to the first estimated XYZ coordinate. The sliding PPP time series window will cover the period of the latest 5 minutes.
    13401340</p>
    13411341<p>
    … …  
    13451345<p><a name="ppppost"><h4>3.12.5 Post Processing - optional</h4></p>
    13461346        <p>When in 'Post-Processing mode<ul><li>specifying a RINEX Observation, a RINEX Navigation and a Broadcast Ephemeris corrections file leads to a PPP solution.</li><li>specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Ephemeris corrections file leads to a SPP solution.</ul></p>
    1347 <p>BNC accepts RINEX v2 as well as RINEX v3 observation or navigation file formats. Files carrying Broadcast Ephemeris corrections must have the format produced by BNC in the 'Broadcast Corrections' option.
    1348 <p>
    1349 Post Processing PPP results can be save in a specific output file.
     1347<p>BNC accepts RINEX v2 as well as RINEX v3 observation or navigation file formats. Files carrying Broadcast Ephemeris corrections must have the format produced by BNC in the 'Broadcast Corrections' tab.
     1348<p>
     1349Post Processing PPP results can be saved in a specific output file.
    13501350</p>
    13511351
    … …  
    15651565</p>
    15661566<p>
    1567 Note that the combination procedure in BNC also - formally - works with only one Broadcast Ephemeris corrections stream specified for combination.
     1567Note further that the combination procedure in BNC also - formally - works with only one Broadcast Ephemeris corrections stream specified for combination.
    15681568</p>
    15691569<p>
    … …  
    16081608<p>BNC combines all incoming clocks according to specified weights. Individual clock estimates that differ by more than 'Maximal Residuum' meters from the average of all clocks will be ignored.<p>
    16091609</p>It is suggested to specify a value of about 0.2 m for the Kalman filter combination approach and a value of about 3.0 meters for the Single-Epoch combination approach.</p>
    1610 <p>Default is a 'Maximal Residuum' 999.0 meters</p>
     1610<p>Default is a 'Maximal Residuum' of 999.0 meters</p>
    16111611
    16121612<p><a name="upclk"><h4>3.14. Upload (clk)</h4></p>
    … …  
    16161616either generated by BNC as a combination of several individual correctors streams coming from an number of real-time Analysis Centers (ACs), see section 'Combination',</li>
    16171617<li>
    1618 or generated by BNC because the program receives an ASCII stream of satellite orbits and clocks via IP port from a connected real-time GNSS engine. Such a stream would be expected in an SP3-like format and the associated 'decoder' string would have to be 'RTNET'. </li>
     1618or generated by BNC because the program receives an ASCII stream of satellite orbits and clocks via IP port from a connected real-time GNSS engine. Such a stream would be expected in a plain ASCII format and the associated 'decoder' string would have to be 'RTNET'. </li>
    16191619</ol>
    16201620The procedure taken by BNC to generate the clock and orbit corrections to Broadcast Ephemeris and upload them to an NTRIP Broadcaster is as follow:
    … …  
    16241624Then, epoch by epoch:
    16251625<ul>
    1626 <li>Continuously receive the best available clock and orbit estimates for all satellites in X,Y,Z Earth-Centered-Earth-Fixed IGS08 reference system. Receive them every epoch in a SP3-like format as provided by a real-time GNSS engine such as RTNet or generate them following a 'Combination' approach. </li>
     1626<li>Continuously receive the best available clock and orbit estimates for all satellites in X,Y,Z Earth-Centered-Earth-Fixed IGS08 reference system. Receive them every epoch in plain ASCII format as provided by a real-time GNSS engine such as RTNet or generate them following a 'Combination' approach. </li>
    16271627<li>Calculate X,Y,Z coordinates from Broadcast Ephemeris orbits. </li>
    16281628<li>Calculate differences dX,dY,dZ between Broadcast Ephemeris and IGS08 orbits. </li>
    … …  
    16381638</p>
    16391639<p>
    1640 BNC requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and in a specific SP3-like format. The clocks and orbits must be referred to satellite Center of Mass (CoM) and must not containing the conventional periodic relativistic effect. They may be provided by a real-time GNSS engine such as RTNet. The sampling rate for data transmission should not exceed 15 sec. Note that otherwise tools involved in IP streaming such as NTRIP Broadcasters or NTRIP clients may respond with a timeout.
    1641 
    1642 </p>
    1643 
    1644 <p>
    1645 Below you find an example of precise clocks and orbits coming in a SP3-like format from a real-time GNSS engine. Each epoch starts with an asterisk character followed by the time as year, month, day of month, hour, minute and second. Subsequent records provide the following set of parameters for each satellite:
     1640BNC requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and in a specific ASCII format. The clocks and orbits must be referred to satellite Center of Mass (CoM) and must not containing the conventional periodic relativistic effect. They may be provided by a real-time GNSS engine such as RTNet. The sampling rate for data transmission should not exceed 15 sec. Note that otherwise tools involved in IP streaming such as NTRIP Broadcasters or NTRIP clients may respond with a timeout.
     1641</p>
     1642
     1643<p>
     1644Below you find an example of precise clocks and orbits coming in ASCII format from a real-time GNSS engine. Each epoch starts with an asterisk character followed by the time as year, month, day of month, hour, minute and second. Subsequent records provide the following set of parameters for each satellite:
    16461645</p>
    16471646
Note: See TracChangeset for help on using the changeset viewer.