Changeset 1111 in ntrip for trunk/BNS


Ignore:
Timestamp:
Sep 10, 2008, 1:40:13 PM (16 years ago)
Author:
weber
Message:

* empty log message *

Location:
trunk/BNS
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNS/bnsabout.html

    r961 r1111  
    2121The Bundesamt fuer Geodaesie und Kartographie (BKG) may not be held liable for damages of any kind, direct or consequential, which may result from the use of this software.<br>
    2222<br>
    23 BKG, Frankfurt, Germany, August 2008<br>
     23BKG, Frankfurt, Germany, September 2008<br>
    2424E-Mail: <a><u>euref-ip@bkg.bund.de</u></a>.<br>
    2525</p>
  • trunk/BNS/bnshelp.html

    r1107 r1111  
    4141
    4242<ul>
    43 <li>read GNSS clocks and orbits in 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.</li>
    44 <li>read GNSS Broadcast Ephemeris in RINEX Navigation file format from an IP port. This information can be provided in real-time by the 'BKG Ntrip Client' (BNC) program.</li>
     43<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 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>
    4545<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>
    4646<li>upload the clock and orbit corrections as a stream to an NTRIP Broadcaster.</li>
     
    6565Then, epoch by epoch:
    6666<ul>
    67 <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 plain ASCII format as provided by a real-time GNSS engine such as RTNet.</li>
     67<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>
    6868<li>Calculate X,Y,Z coordinates from Broadcast Ephemeris orbits.</li>
    6969<li>Calculate differences dX,dY,dZ between Broadcast Ephemeris orbits and IGS05 orbits.</li>
     
    8484<p><a name="resources"><h3>3. Resources</h3></p>
    8585<p>
    86 The current size of the real-time stream produced by BNS is in the order 5 kbits/sec depending on the number of visible satellites. When uploading the stream to an NTRIP Broadcaster, user needs to ensure that the connection used can sustain the required bandwidth.
     86The current size of the real-time stream produced by BNS is in the order of 5 kbits/sec depending on the number of visible satellites. When uploading the stream to an NTRIP Broadcaster, user needs to ensure that the connection used can sustain the required bandwidth.
    8787</p>
    8888<p>
     
    185185</p>
    186186
    187 <p><a name="ephserver"><h4>4.5.1 Host & Port - mandatory</h4></p>
    188 <p>
    189 Enter the IP address and port number of a Broadcast Ephemeris server like BNC to establish a persistent socket connection, see section 'Flow Chart' under 'Help' for socket communication details. If BNS runs on the same host as BNC, 127.0.0.1 should be used as the server's IP address. Make sure that this server is up and running before you start BNS.
    190 </p>
    191 
    192 <p><a name="ephsave"><h4>4.5.2 Save - optional</h4></p>
    193 </p>
    194 Specify the full path to a file where received Broadcast Ephemeris will logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
    195 </p>
    196187<p>
    197188The following is an example log of Broadcast Ephemeris records in RINEX Version 3 Navigation file format for satellite GPS PRN32 and GLONASS PRN04:
     
    215206</p>
    216207
     208<p><a name="ephserver"><h4>4.5.1 Host & Port - mandatory</h4></p>
     209<p>
     210Enter the IP address and port number of a Broadcast Ephemeris server like BNC to establish a persistent socket connection, see section 'Flow Chart' under 'Help' for socket communication details. If BNS runs on the same host as BNC, 127.0.0.1 should be used as the server's IP address. Make sure that this server is up and running before you start BNS.
     211</p>
     212
     213<p><a name="ephsave"><h4>4.5.2 Save - optional</h4></p>
     214</p>
     215Specify the full path to a file where received Broadcast Ephemeris will be logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
     216</p>
     217
    217218<p><a name="co"><h4>4.6. Clocks & Orbits</h4></p>
    218219<p>
    219 BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. They can be provided by a real-time GNSS engine such as RTNet and are expected to refer to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system.
    220 </p>
    221 
    222 <p><a name="coport"><h4>4.6.1 Listening Port - mandatory</h4></p>
    223 <p>
    224 BNS is listening at an IP port for incoming GNSS clocks and orbits in a plain ASCII 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.
    225 </p>
    226 
    227 <p><a name="cosave"><h4>4.6.2 Save - optional</h4></p>
    228 <p>
    229 Specify the full path to a file where received clocks and orbits from a real-time engine will logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
    230 </p>
    231 
    232 <p>
    233 Below you find an example of precise clocks and orbits coming in plain ASCII format from a real-time GNSS engine. Each epoch starts with an asterisk character followed by GPS Week, Second in GPS Week and Number of satellites. Subsequent records provide the following set of parameters for each satellite:
     220BNS 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 and are expected to refer to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system.
     221</p>
     222
     223<p>
     224Below 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 GPS Week, Second in GPS Week and Number of satellites. Subsequent records provide the following set of parameters for each satellite:
    234225</p>
    235226
     
    277268</p>
    278269
     270<p><a name="coport"><h4>4.6.1 Listening Port - mandatory</h4></p>
     271<p>
     272BNS 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.
     273</p>
     274
     275<p><a name="cosave"><h4>4.6.2 Save - optional</h4></p>
     276<p>
     277Specify the full path to a file where received clocks and orbits from a real-time engine will be logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
     278</p>
     279
    279280<p><a name="ephc"><h4>4.7. Ephemeris Corrections</h4></p>
    280281<p>
     
    429430</li>
    430431<li>
    431 Currently BNS can only generate the tentative RTCM Version 3.x message Type 4056 and 4057 for combined GPS and GLONASS orbit and clock corrections. Note that the length of data fields in these messages is not yet standardized. What's implemented in BNS is just a temporary solutions.
     432Currently BNS can only generate the tentative RTCM Version 3.x message Type 4056 and 4057 for combined GPS and GLONASS orbit and clock corrections. Note that the length of data fields in these messages is not yet standardized. What's implemented in BNS is just a temporary solution.
    432433</li>
    433434<li>
     
    464465<table>
    465466<tr></tr>
    466 <tr><td>August 2008 &nbsp;</td><td>Version 1.0 &nbsp;</td><td>[Add] Beta Binaries published.</td></tr>
     467<tr><td>Sep 2008 &nbsp;</td><td>Version 1.0 &nbsp;</td><td>[Add] Beta Binaries published.</td></tr>
    467468</table>
    468469</p>
  • trunk/BNS/bnswindow.cpp

    r1094 r1111  
    164164
    165165  _clkPortLineEdit  = new QLineEdit(settings.value("clkPort").toString());
    166   _clkPortLineEdit->setWhatsThis(tr("BNS reads Clocks & Orbits referring to the IGS system (X,Y,Z, ECEF) in plain ASCII format from an IP port. Specify a local IP port e.g. of an RTNet installation to provide this information."));
     166  _clkPortLineEdit->setWhatsThis(tr("BNS reads Clocks & Orbits referring to the IGS system (X,Y,Z, ECEF) in SP3 format from an IP port. Specify a local IP port e.g. of an RTNet installation to provide this information."));
    167167  _clkPortLineEdit->setMaximumWidth(9*ww);
    168168
     
    298298  layout_eph->addWidget(new QLabel("Save (full path)"),       2, 0);
    299299  layout_eph->addWidget(_ephEchoLineEdit,                     2, 1);
    300   layout_eph->addWidget(new QLabel("Read broadcast ephemeris."), 3, 0, 1, 2, Qt::AlignLeft);
     300  layout_eph->addWidget(new QLabel("Read broadcast ephemeris in RINEX Version 3 Navigation format."), 3, 0, 1, 2, Qt::AlignLeft);
    301301//layout_eph->addWidget(new QLabel(""),                       4, 0);
    302302
     
    316316  layout_co->addWidget(new QLabel("Save (full path)"),                1, 0);
    317317  layout_co->addWidget(_inpEchoLineEdit,                              1, 1);
    318   layout_co->addWidget(new QLabel("Read IGS clocks and orbits."),     2, 0, 1, 2, Qt::AlignLeft);
     318  layout_co->addWidget(new QLabel("Read clocks and orbits in SP3 format."),     2, 0, 1, 2, Qt::AlignLeft);
    319319  layout_co->addWidget(new QLabel(""),                                3, 0);
    320320
     
    350350  layout_cas->addWidget(_outFile_2_LineEdit,                   2, 5, 1, 8);
    351351
    352   layout_cas->addWidget(new QLabel("Broadcast ephemeris corrections, upload to caster, reference system, local storage."), 3, 0, 1, 8, Qt::AlignLeft);
     352  layout_cas->addWidget(new QLabel("Produce broadcast ephemeris corrections, upload to caster, reference system, local storage."), 3, 0, 1, 8, Qt::AlignLeft);
    353353
    354354  tab_cas->setLayout(layout_cas);
Note: See TracChangeset for help on using the changeset viewer.