Changeset 2358 in ntrip for trunk/BNS


Ignore:
Timestamp:
Mar 10, 2010, 3:47:13 PM (12 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNS/bnshelp.html

    r2351 r2358  
    4242
    4343<ul>
    44 <li>read GNSS clocks and orbits in SP3 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.</li>
     44<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.</li>
    4545<li>read GNSS Broadcast Ephemeris in RINEX Navigation format from an IP port. This information can be provided in real-time by the 'BKG Ntrip Client' (BNC) program.</li>
    4646<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>
     
    6464Then, epoch by epoch:
    6565<ul>
    66 <li>Continuously receive the 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 SP3 format as provided by a real-time GNSS engine such as RTNet.</li>
     66<li>Continuously receive the 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 SP3-like format as provided by a real-time GNSS engine such as RTNet.</li>
    6767<li>Calculate X,Y,Z coordinates from Broadcast Ephemeris orbits.</li>
    6868<li>Calculate differences dX,dY,dZ between Broadcast Ephemeris and IGS05 orbits.</li>
     
    256256<p><a name="co"><h4>4.5. Clocks &amp; Orbits</h4></p>
    257257<p>
    258 BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system in SP3 format. They can be provided by a real-time GNSS engine such as RTNet. The sampling rate should not be much greater than 10 sec. Note that otherwise in IP streaming involved tools on the NTRIP Broadcaster or client side may respond with a timeout.
    259 </p>
    260 
    261 <p>
    262 Below you find an example of precise clocks and orbits coming in SP3 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:
     258BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system in a SP3-like format. They can be provided by a real-time GNSS engine such as RTNet. The sampling rate should not be much greater than 10 sec. Note that otherwise in IP streaming involved tools on the NTRIP Broadcaster or client side may respond with a timeout.
     259</p>
     260
     261<p>
     262Below 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:
    263263</p>
    264264
     
    290290</p>
    291291<p>
    292 Note that the '2nd order relativistic effect' is not used in BNS although it is required to provide it. If the relativistic effect is unavailable for you then you must at least send a dummy value.
     292Note that the '2nd order relativistic effect' is not used in BNS although it is required to provide it. If the relativistic effect is unavailable for you then you must at least send a dummy value.
     293</p>
     294<p>
     295In other words: The clocks in the ASCII stream from a real-time GNSS engine which feeds BNS must not contain the '2nd order relativistic effect'. Furthermore, BNS does not add this effect to the stream.
    293296</p>
    294297
    295298<p><a name="coport"><h4>4.5.1 Listening Port - mandatory</h4></p>
    296299<p>
    297 BNS is listening at an IP port for incoming GNSS clocks and orbits in SP3 format. Enter the respective IP port number to setup a server socket for incoming data, see section 'Flow Chart' under 'Help' for socket communication details. Make sure that the software providing clocks and orbits is up and running before you start BNS.
     300BNS is listening at an IP port for incoming GNSS clocks and orbits in a SP3-like format. Enter the respective IP port number to setup a server socket for incoming data, see section 'Flow Chart' under 'Help' for socket communication details. Make sure that the software providing clocks and orbits is up and running before you start BNS.
    298301</p>
    299302
Note: See TracChangeset for help on using the changeset viewer.