Changeset 1953 in ntrip

Timestamp:

Nov 13, 2009, 12:39:51 PM (14 years ago)

Author:

weber

Message:

* empty log message *

File:

• trunk/BNC/bnchelp.html (modified) (6 diffs)

trunk/BNC/bnchelp.html

@@ -76 +76 @@
 </p>
 <p>
-The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various tabs to select a combination of processing options before you start the program ('Start'). Records of BNC's activities are shown in the 'Logs' canvas on the bottom of the main window.
+The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various configuration tabs to select a combination of input, processing and output options before you start the program ('Start'). Records of BNC's activities are shown in the 'Log' tab and bandwidth consumtion per stream in the 'Throughput' tab on the bottom of the main window.
 </p>
 <p>
@@ -216 +216 @@
 <p><a name="genlog"><h4>3.3.1 Logfile - optional</h4></p>
 <p>
-Records of BNC's activities are shown in the 'Logs' canvas on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. The logfile name will automatically be extended by a string '_YYMMDD' carrying the current date. This leads to series of daily logfiles when running BNC continuously for extended. Message logs cover the communication status between BNC and the NTRIP broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Logfile (full path)' is an empty option field, meaning that BNC logs will not saved into a file.
+Records of BNC's activities are shown in the 'Log' tab on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. The logfile name will automatically be extended by a string '_YYMMDD' carrying the current date. This leads to series of daily logfiles when running BNC continuously for extended. Message logs cover the communication status between BNC and the NTRIP broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Logfile (full path)' is an empty option field, meaning that BNC logs will not saved into a file.
 </p>
 
@@ -678 +678 @@
 </p>
 <p>
-Note 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, resulting in log records like 'New client connection on sync/usync port: # 1'.
+Note that any socket connection of an application to BNC's synchronized or unsynchronized observations ports is recorded in the 'Log' tab on the bottom of the main window together with a connection counter, resulting in log records like 'New client connection on sync/usync port: # 1'.
 </p>
 
@@ -802 +802 @@
 </p>
 <p>
-Outage and corruption events are reported in the 'Logs' canvas. They can also be passed on as parameters to a shell script or batch file to generate an advisory note to BNC operator or affected stream providers. This functionality lets users utilise BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations.
+Outage and corruption events are reported in the 'Log' tab. They can also be passed on as parameters to a shell script or batch file to generate an advisory note to BNC operator or affected stream providers. This functionality lets users utilise BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations.
 </p>
 
@@ -883 +883 @@
 </p>
 <p>
-Latencies of observations or corrections to Broadcast Ephemeris and statistical information can be recorded in the 'Logs' canvas at the end of each 'Performance log' interval. A typical output from a 1 hour 'Performance log' interval would be:
+Latencies of observations or corrections to Broadcast Ephemeris and statistical information can be recorded in the 'Log' tab at the end of each 'Performance log' interval. A typical output from a 1 hour 'Performance log' interval would be:
 </p>
 <pre>
@@ -1521 +1521 @@
 <tr><td>serialPortName=</td><td>Serial Output: Port name</td></tr>
 <tr><td>serialStopBits=1</td><td>Serial Output: Stop bits</td></tr>
-<tr><td>startTab=0</td><td>Internal memory: Top tab</td></tr>
+<tr><td>startTab=0</td><td>Internal memory: Top tab index</td></tr>
+<tr><td>statusTab=0</td><td>Internal memory: Bottom tab index</td></tr>
 <tr><td>waitTime=5</td><td>Feed Engine: Wait for full epoch</td></tr>
 </table>