Changeset 1448 in ntrip


Ignore:
Timestamp:
Jan 6, 2009, 3:44:30 PM (16 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r1422 r1448  
    104104&nbsp; &nbsp; &nbsp; 3.7.4. <a href=#corrwait>Wait for Full Epoch</a><br>
    1051053.8. <a href=#syncout>Feed Engine</a><br>
    106 &nbsp; &nbsp; &nbsp; 3.8.1. <a href=#syncport>Port (synchronized)</a><br>
    107 &nbsp; &nbsp; &nbsp; 3.8.2. <a href=#syncwait>Wait for Full Epoch</a><br>
    108 &nbsp; &nbsp; &nbsp; 3.8.3. <a href=#syncuport>Port (unsynchronized)</a><br>
     106&nbsp; &nbsp; &nbsp; 3.8.1. <a href=#syncuport>Port (unsynchronized)</a><br>
     107&nbsp; &nbsp; &nbsp; 3.8.2. <a href=#syncport>Port (synchronized)</a><br>
     108&nbsp; &nbsp; &nbsp; 3.8.3. <a href=#syncwait>Wait for Full Epoch</a><br>
    109109&nbsp; &nbsp; &nbsp; 3.8.4. <a href=#syncfile>File</a><br>
    110110&nbsp; &nbsp; &nbsp; 3.8.5. <a href=#syncsample>Sampling</a><br>
    … …  
    455455</p>
    456456
    457 <p><a name="syncport"><h4>3.8.1 Port (synchronized) - optional</h4></p>
    458 <p>
    459 BNC can produce synchronized observations in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary output is generated.</p>
    460457<p>The binary output is a continuous stream in the following order:</p>
    461458<pre>
    … …  
    507504</p>
    508505<p>
    509 Note that any socket connection of an application to BNC's synchronized observations 'Port' is recorded in the 'Logs' canvas on the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'.
    510 </p>
    511 
    512 <p><a name="syncwait"><h4>3.8.2 Wait for Full Epoch - mandatory if 'Port (synchronized)' is set</h4></p>
     506Note that any socket connection of an application to BNC's synchronized or unsynchronized observations ports is recorded in the 'Logs' canvas on the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'.
     507</p>
     508
     509<p><a name="syncuport"><h4>3.8.1 Port (unsynchronized) - optional</h4></p>
     510BNC can produce unsynchronized observations from all configured streams in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary unsynchronized output is generated.</p>
     511
     512<p><a name="syncport"><h4>3.8.2 Port (synchronized) - optional</h4></p>
     513<p>
     514BNC can produce synchronized observations in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Scynchronized means that BNC collects all data for any specific epoch which become available within a certain number of latency seconds (see 'Wait for Full Epoch' option). It then - epoch by epoch - outputs whatever has been received. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary synchronized output is generated.</p>
     515<p>
     516</p>
     517
     518<p><a name="syncwait"><h4>3.8.3 Wait for Full Epoch - mandatory if 'Port (synchronized)' is set</h4></p>
    513519<p>
    514520When feeding a real-time GNSS engine waiting for synchronized input epoch by epoch, BNC drops whatever is received later than 'Wait for full epoch' seconds. A value of 3 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming streams and the delay acceptable for your real-time GNSS product. Default value for 'Wait for full epoch' is 5 seconds.
    … …  
    517523Note that 'Wait for full epoch' does not effect the RINEX Observation file content. Observations received later than 'Wait for full epoch' seconds will still be included in the RINEX Observation files.
    518524</p>
    519 
    520 <p><a name="syncuport"><h4>3.8.3 Port (unsynchronized) - optional</h4></p>
    521 An application may want to receive unsynchronized observations from reference stations. If so, BNC can produce such unsynchronized observations in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary unsynchronized output is generated.</p>
    522 
    523 <p>
    524 The example program 'test_bnc_qt.cpp' allows you to read BNC's unsynchronized binary observation output from the IP port and print the observations in a plain ASCII format on standard output.
    525 </p>
    526 <p>
    527 Note that any socket connection of an application to BNC's unsynchronized observations 'Port' is recorded in the 'Logs' canvas on the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'.
    528 </p>
    529 
    530525
    531526<p><a name="syncfile"><h4>3.8.4 File - optional</h4></p>
Note: See TracChangeset for help on using the changeset viewer.