Changeset 669 in ntrip

Timestamp:

Jan 30, 2008, 5:51:07 PM (17 years ago)

Author:

weber

Message:

* empty log message *

Location:

trunk/BNC

Files:

• bncgetthread.cpp (modified) (4 diffs)
• bnchelp.html (modified) (2 diffs)

trunk/BNC/bncgetthread.cpp

@@ -479 +479 @@
             // ---------------------
             if ( begCorrupt && !endCorrupt && secSucc > _adviseReco * 60 ) {
-              emit(newMessage(_staID + ": End_Corrupted, Recovery threshold exceeded"));
+              emit(newMessage(_staID + ": Corrupted recovery threshold exceeded"));
               callScript("End_Corrupted");
               endCorrupt = true;
@@ -490 +490 @@
               // -----------------------
               if ( !begCorrupt && secFail > _adviseFail * 60 ) {
-                emit(newMessage(_staID + ": Begin_Corrupted, Failure threshold exceeded"));
+                emit(newMessage(_staID + ": Corrupted failure threshold exceeded"));
                 callScript("Begin_Corrupted");
                 begCorrupt = true;
@@ -508 +508 @@
         _decodeStart.setDate(QDate());
         _decodeStart.setTime(QTime());
-        emit(newMessage(_staID + ": End_Outage, Recovery threshold exceeded"));
+        emit(newMessage(_staID + ": Outage recovery threshold exceeded"));
         callScript("End_Outage");
       }
@@ -613 +613 @@
         _decodeStop.setDate(QDate());
         _decodeStop.setTime(QTime());
-        emit(newMessage(_staID + ": Begin_Outage, Failure threshold exceeded"));
+        emit(newMessage(_staID + ": Outage failure threshold exceeded"));
         callScript("Begin_Outage");
       }

trunk/BNC/bnchelp.html

@@ -365 +365 @@
 </p>
 <p>
-<u>Stream outages:</u> BNC considers a connection to be broken when there are no incoming data detected for more than 20 seconds. When this occurs, BNC will attempt to reconnect at a decreasing rate. It will first try to reconnect with 1 second delay, and again in 2 seconds if the previous attempt failed. If the attempt is still unsuccessful, it will try to reconnect within 4 seconds after the previous attempt and so on. The wait time doubles each time with a maximum wait time of 256 seconds. This reconnection process is documented in the 'Log' file/section.
+<u>Stream outages:</u> BNC considers a connection to be broken when there are no incoming data detected for more than 20 seconds. When this occurs, BNC will attempt to reconnect at a decreasing rate. It will first try to reconnect with 1 second delay, and again in 2 seconds if the previous attempt failed. If the attempt is still unsuccessful, it will try to reconnect within 4 seconds after the previous attempt and so on. The wait time doubles each time with a maximum wait time of 256 seconds.
 </p>
 <p>
@@ -371 +371 @@
 </p>
 <p>
-If the stream failures or recoveries caused by an outage or corrupted data exceed the 'Failure' or 'Recovery' thresholds, BNC can inform its users about this event. The information becomes available in the 'Log' file/section as a 'Begin_Outage', 'End_Outage', 'Begin_Corrupted', or 'End_Corrupted' message. It can also be passed on as an Advisory note to an 'Advisory script' or batch file to keep BNC's operator or affected stream providers up-to-date by email. This functionality lets you use BNC as a real-time performance monitor and alarm system for the network of GNSS reference stations in use.
+If the stream failures or recoveries caused by an outage or corrupted data exceed the 'Failure' or 'Recovery' thresholds, BNC can inform its users about this event. The information becomes available in the 'Log' file/section. It can also be passed on as an Advisory note to an 'Advisory script' or batch file to keep BNC's operator or affected stream providers up-to-date by email. This functionality lets you use BNC as a real-time performance monitor and alarm system for the network of GNSS reference stations in use.
 </p>