Good/Bad Counter Handling
Original Publication Date: 1986-Apr-01
Included in the Prior Art Database: 2005-Mar-08
An effective method to handle good/bad counters for reporting error conditions is described. Many devices count how many good and bad operations take place during the activation of a hardware device. There has been no effective way of using these counters to determine when a condition occurs that should be logged as an error condition and/or requires operator intervention/notification. The problem is to define threshold logging criteria. Defining a ratio (%) between good/bad doesn't protect good count runaway nor provide protection from premature logging. An example of good count runaway is illustrated below. Assume that a design defines that when a good/bad count ratio is > 5% an error should be logged.