Changeset 962 in ntrip for trunk/BNS/bnshelp.html


Ignore:
Timestamp:
Jul 23, 2008, 6:52:56 PM (16 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNS/bnshelp.html

    r961 r962  
    22
    33<p>
    4 The BKG Ntrip Server (BNS) is a program for transforming GNSS satellite clocks and orbits into corrections to Broadcast Ephemeris. These corrections are then encode in RTCM Version 3 format and uploaded to NTRIP broadcasters like <u>http://www.euref-ip.net/home</u> or <u>http://www.igs-ip.net/home.</u> BNS is meant as a tool for service providers with real-time access to a network of continentally or globally distributet GNSS reference stations.
     4The BKG Ntrip Server (BNS) is a program for transforming GNSS satellite clocks and orbits into corrections to Broadcast Ephemeris. These corrections are then encode in RTCM Version 3.x format and uploaded to NTRIP broadcasters like <u>http://www.euref-ip.net/home</u> or <u>http://www.igs-ip.net/home.</u> BNS is meant as a tool for service providers with real-time access to a network of continentally or globally distributet GNSS reference stations.
    55</p>
    66
    … …  
    4949<p><a name="function"><h3>2. Functioning</h3></p>
    5050<p>
    51 The BNS procedure for generating RTCM Version 3 clock and orbit corrections to Broadcast ephemeris in radial, along-track and cross-track components is the following:
     51The BNS procedure for generating RTCM Version 3.x clock and orbit corrections to Broadcast ephemeris in radial, along-track and cross-track components is the following:
    5252</p>
    5353<p>
    5454<ul>
    5555<li>Continuously receive up to date Broadcast Ephemeris carrying approximate orbits and clocks for all satellites. Receive them in RINEX Version 3 Navigation file format. Read new Broadcast Ephemeris immediately whenever they become available. Tools like the 'BKG Ntrip Client' (BNC) provide this information.</li>
     56</ul>
     57</p>
     58<p>
     59Then, epoch by epoch:
     60<ul>
    5661<li>Continuously receive best available clock and orbit estimates for all satellites in X,Y,Z Earth-Centered-Earth-Fixed IGS05 reference system. Receive them every epoch in a plain ASCII format as provided by a real-time GNSS engine like RTNet.</li>
    57 </ul>
    58 <p>Then, once per epoch:</p>
    59 <ul>
    6062<li>Calculate X,Y,Z coordinates from Broadcast Ephemeris orbits.</li>
    6163<li>Calculate differences dX,dY,dZ between Broadcast Ephemeris orbits and IGS05 orbits.</li>
    … …  
    6365<li>Derive model-based estimation of corrections to Broadcast Ephemeris orbits.
    6466<li>Tranform model-based orbit corrections into radial, along-track and cross-track components.</li>
    65 <br><br>
    6667<li>Calculate differences dC between clocks from Broadcast Ephemeris and IGS05 clocks.</li>
    6768<li>Model clock differences through polynomial of low degree.</li>
    6869<li>Derive model-based estimation of corrections to Broadcast Ephemeris clocks.</li>
    69 <br><br>
    70 <li>Encode Broadcast Ephemeris clock and orbit corrections in RTCM Version 3 format.</li>
     70<li>Encode Broadcast Ephemeris clock and orbit corrections in RTCM Version 3.x format.</li>
    7171<li>Upload corrections in RTCM Verion 3 format to NTRIP Broadcaster.</li>
    7272</ul>
    73 <p>
     73</p>
     74<p>
     75Because BNS is quite demanding concerning communication links, is is recommended to run the three software components BNS, the Broadcast Ephemeris server (i.e. BNC), and the server providing orbits and clocks (i.e. RTNet) on the same host. However, this is not a must.
     76</p>
    7477
    7578<p><a name="resources"><h3>3. Resources</h3></p>
    … …  
    281284<p><a name="caster"><h4>4.6. NTRIP Caster</h4></p>
    282285<p>
    283 BNS can upload the resulting stream of cock and orbit corrections to Broadcast Ephemeris to an Ntrip Broadcaster. For that EUREF and IGS operate NTRIP broadcasters at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u> which might be used for stream upload. The stream's format is RTCM Version 3. Note that it only carries the thentative message types 4056 and 4057 for combined GPS and GLONASS clock and orbit corrections.
     286BNS can upload the resulting stream of cock and orbit corrections to Broadcast Ephemeris to an Ntrip Broadcaster. For that EUREF and IGS operate NTRIP broadcasters at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u> which might be used for stream upload. The stream's format is RTCM Version 3.x. Note that it only carries the thentative message types 4056 and 4057 for combined GPS and GLONASS clock and orbit corrections.
    284287</p>
    285288
    … …  
    329332</p>
    330333<p>
    331 The following is an example file contents based on combined GPS and GLONASS clock and orbit corrections carried in RTCM Version 3 message types 4056 and 4057:
     334The following is an example file contents based on combined GPS and GLONASS clock and orbit corrections carried in RTCM Version 3.x message types 4056 and 4057:
    332335</p>
    333336<p>
    … …  
    407410</li>
    408411<li>
    409 Currently BNS can only generate the tentative RTCM Version 3 message types 4056 and 4057 for combined GPS and GLONASS orbit and clock corrections.
     412Currently BNS can only generate the tentative RTCM Version 3.x message types 4056 and 4057 for combined GPS and GLONASS orbit and clock corrections.
    410413</li>
    411414<li>
    … …  
    498501</p>
    499502<p>
    500 RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications following the 'state space' approach.
     503RTCM Version 3.x streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications following the 'state space' approach.
    501504</p>
    502505
Note: See TracChangeset for help on using the changeset viewer.