Method of detecting systemic fault conditions in an intelligent electronic device

[0002] The present invention relates generally to intelligent electronic devices, e.g., electronic trip units, protective relays, energy meters and power quality meters. More specifically, the present invention relates to a method of detecting systemic event or fault conditions in an intelligent electronic device.

[0003] Intelligent electronic devices are well known. By way of example, an electronic trip unit (one such intelligent electronic device) typically comprises voltage and current sensors which provide analog signals indicative of the power line signals. The analog signals are converted by an A/D (analog/digital) converter to digital signals which are processed by a microcontroller. The trip unit further includes RAM (random access memory), ROM (read only memory) and EEPROM (electronic erasable programmable read only memory) all of which interface with the microcontroller. The ROM includes trip unit application code, e.g., main functionality firmware, including initializing parameters, and boot code. The EEPROM includes operational parameters for the application code.

[0004] The electronic trip unit detects fault conditions (i.e., events) such as breaker trips, relay events, downed conductors, or user defined event conditions. Once a fault condition is detected, the electronic trip unit generates an event message such as an alarm via a local display, external contacts, or by sending an event message to a centralized monitoring station such as a computer software program containing an event logging tool.

[0005] However, it is generally left to the user to analyze the raw event data to determine if the same event has occurred multiple times within a given time period such as to give indication that a systemic fault condition, i.e., a fault condition recurring due to the same root cause technical problem, exists which should be found and eliminated. There is especially a need in the area of utility relaying, where the physical environment surrounding the distribution systems often give rise to repeated faults which may be masked by automatic re-closure of breakers once the fault has cleared.

[0006] A method of detecting systemic fault conditions in an intelligent electronic device as indicated by repeated, similar fault events is presented. An electronic trip unit is described herein by way of example only, as the present invention applies to other intelligent electronic devices as well. In an exmplary embodiment of the invention the electronic trip unit comprises voltage and current sensors which provide analog signals indicative of the power line signals. The analog signals are converted by an A/D (analog/digital) converter to digital signals which are processed by a microcontroller. The trip unit further includes RAM (random access memory), ROM (read only memory) and EEPROM (electronic erasable programmable read only memory) all of which communicate with the microcontroller. The ROM includes trip unit application code, e.g., main functionality firmware, including initializing parameters, and boot code. The application code includes code for the systemic fault detection algorithm of the present invention. The EEPROM includes operational parameters, e.g., code for setting user defined events to be logged and/or time horizons for logging multiple similiar event occurrences, for the application code. These parameters may be stored in the trip unit at the factory and are selected to meet customer's requirements, but. can also be remotely downloaded.

[0007] For each such event that is detected by the intelligent electronic device the systemic fault detection algorithm logs the occurrence of the event. Optionally, the algorithm may also log the date and time of the event. The algorithm determines if this particular fault type (or event type) has occurred before (e.g., the same type of fault on the same phase). If such a fault has occurred before, the time since the last such fault occurrence and the total number of such fault type occurrences are determined. This is then compared against the user-input number of events and/or time frequency specified to merit the generation of a repeat event.

[0008] FIG. 1 is a schematic block diagram of an electronic trip unit in accordance with the present invention; and

[0009] FIGS. 2A-D are a user configured event storage table in accordance with the present invention.

[0010] Referring to the FIG. 1, a general schematic of a trip unit is generally shown at 30. It will be appreciated that the present invention is not limited to electronic trip units but is directed intelligent electronic devices in general. Trip unit 30 comprises a voltage sensor 32 which provides analog signals indicative of voltage measurements on a signal line 34 and a current sensor 36 which provides analog signals indicative of a current measurements on a signal line 38. The analog signals on lines 34 and 38 are presented to an AID (analog/digital) converter 40, which converts these analog signals to digital signals. The digital signals are transferred over a bus 42 to a microcontroller (signal processor) 44, such being commercially available from the Hitachi Electronics Components Group (Hitachi's H8/300 family of microcontrollers). Trip unit 30 further includes RAM (random access memory) 46, ROM (read only memory) 48 and EEPROM (electronic erasable programmable read only memory) 50 all of which communicate with the microcontroller 44 over a control bus 52. It will be appreciated that A/D converter 40, ROM 48, RAM 46, or any combination thereof may be internal to microcontroller 44, as is well known. EEPROM 50 is non-volatile so that system information and programming will not be lost during a power interruption or outage. Data, typically status of the circuit breaker, is displayed by a display 54 in response to display signals received from microcontroller 44 over control bus 52. An output control device 56, in response to control signals received from microcontroller 44 over control bus 52, controls a trip module 58 via a line 60. Calibration, testing, programming and other features are accomplished through a communications I/O port 62, which communicates with microcontroller 44 over control bus 52. A power supply 63 which is powered by the service electricity, provides appropriate power over a line 64 to the components of trip unit 30. ROM 48 includes trip unit application code, e.g., main functionality firmware, including initializing parameters, and boot code. The application code includes code for a systemic fault detection algorithm in accordance with the present invention.

[0011] EEPROM 50 includes operational parameter code, e.g., code for setting user defined events to be logged and/or time horizons for logging multiple similar event occurrences. These parameters may be stored in the trip unit at the factory and are selected to meet customers requirements, but can also be remotely downloaded as described hereinafter. The systemic fault detection algorithm is run in real-time and is initiated preferably from the boot code at start up.

[0012] When a trip or relay event, e.g., short time, long time, instantaneous, underfrequency, overfrequency, or ground fault, has been detected and a breaker tripped and/or a contact closed the device will send an event message out. This message may be displayed on a local display and/or be communicated to a remote monitoring station such as inequipment monitor or a remote computer with power management control software. In other words, the trip or relay event is processed as known in the prior art.

[0013] In an exemplary embodiment of the invention, for each such event that is detected by the intelligent electronic device the systemic fault detection algorithm logs the occurrence of the event. The algorithm determines if this particular fault has occurred before, e.g., the same type of fault on the same phase.

[0014] In an implementation of the exemplary embodiment of the invention, a user configured event storage table is shown in FIGS. 2A-D and a systemic fault detection algorithm is provided below. In the user configured event storage table the following logic is applied: keep X events then reset OR use sliding window of X days then reset events outside of window. In accordance with the invention the event table (FIGS. 2A-D) and detection algorithm are implemented in the firmware of the intelligent electronic device. When a fault event occurs, it is processed by trip unit 30 as in the prior art. Additionally, the repeat fault event algorithm will go through the following endless loop:

[0015] 1. If an event is received to 2, else proceed to 8.

[0016] 2. The appropriate counter in column 2 is incremented and logged in non-volatile memory (table of FIGS. 2A-D).

[0017] 3. Date and time for the event is logged in non-volatile memory (table of FIGS. 2A-D) if supported by trip unit 30.

[0018] 4. Interval between events is calculated and logged in non-volatile memory (table of FIGS. 2A-D).

[0019] 5. Total average interval between all events logged of the type in question is calculated and logged in non-volatile memory (table of FIGS. 2A-D).

[0020] 6. Steps 2, 34 are repeated for All Events field.

[0021] 7. It is verified if conditions in columns 5, 6 or 7 meriting a Repeat event has been met. If so the appropriate event(s) are renearated. Either a unique event number is associated with each condition or the event message passes along parameters allowing for the user to identify which condition was met to generate the event.

[0022] 8. The software verifies if the new event triggers a reset of the events based on the number of events or the sliding window time condition.

[0023] 9. Repeat program.

[0024] A limit may be set as to how many repeats should be observed before a repeat event/message is generated. Similarly a limit may be programmed in as to how many repeat events/messages should be generated regardless of the number of observations made. This information may be displayed at the trip unit 30 or at a central computer (not shown). This may be displayed (or printed) in the form of a log or by type of event along with the number of repeat events, the time since the prior event occurrence and/or the frequency of such event occurrences. This information is useful as an aid in determining the cause or root (i.e., systemic root cause) of these events as such would otherwise be difficult to determine.

[0025] This is because severe fault conditions often do not occur spontaneously but rather develop gradually over time, and often give rise to repeated lesser faults in the process. These repeated lesser faults may be masked by reclosures of circuit breakers, and can be difficult to detect manually from the raw event data. Additionally, if the raw event data is not properly analyzed, then only the symptoms of a problem may be addressed, while the preventable root cause could build up over time. Eventually, these root causes may become severe and cause a major fault event. Once this occurs, damage and costly delays to facility operations may occur. A major fault event caused by a systemic fault condition may cost a user substantial sums. By identifying repeating fault events automatically, these systemic fault conditions may be predicted, detected, and corrected before a major fault event occurs.

[0026] All of the aforementioned limits or settings are preferably stored in EEPROM 50 and can be altered by downloading desired settings via communications I/O port 62. This would include remotely downloading such data when the unit is connected to a system computer (not shown), either directly, over telephone lines, or any other suitable connection. It may also be preferred that EEPROM 50 comprises a flash memory whereby such data is flashed, as is well known.

[0027] While the invention has been described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims.