Micrologic X Control Unit Event Management
|
Event History |
Number of Events |
|---|---|
|
Trip |
50 |
|
Protection |
100 |
|
Diagnostic |
300 |
|
Metering |
300 |
|
Configuration |
100 |
|
Operation |
300 |
|
Communication |
100 |
A list of predefined events has been selected for user notification of alarms and traceability processed by a Micrologic X control unit.
These events are classified in seven families: trip, protection, diagnostic, metering, configuration, operation, and communication.
Definition and Categories of Events
Micrologic X control unit functions produce events available for alarm notification or history logging, in addition to their main action of tripping, measuring, and counting.
All events are time stamped and logged in non-volatile memory so they are maintained if control power is lost.
Events have two characteristics:
-
Event category: trip, protection, diagnostic, metering, configuration, operation, communication
-
Event severity: high-level, medium-level, low-level
Events can be of two types:
-
occurrence/completion
-
instantaneous/latched/unlatched
Event Logbooks
Events are logged according to the event category:
-
Trip : long-time trip, short-time trip, trip on invalid control unit self test...
-
Protection : setting change, I > 90% Ir long time, change from set A to set B ...
-
Diagnostic : voltage release, low battery ...
-
Metering : reset min/max, reset energy counters…
-
Configuration : digital module license …
-
Operation : opening, closing, alarm reset...
-
Communication : Bluetooth enabled ...
All events are logged regardless of their severity. Each history can log a predefined number of events. When that number is reached each new event overwrites the oldest event, and other histories are left unchanged (first-in first-out [FIFO]).
For the complete list of events see the Micrologic X control unit user guide DOCA0102EN.
Event Notification
-
High severity events generate pop-ups on embedded HMI with a red backlight.
-
Medium severity events generate pop-ups on embedded HMI with an orange backlight.
-
On the FDM128 display unit they change the related pictogram color to red for high severity events or orange for medium severity events.
-
All events can be signalled individually or by group to a digital output (M2C or IO module).
-
All events can trigger an email through EIFE or IFE communication interfaces.
-
High and medium severity events can be read on the embedded HMI, a PC or a smart phone.
-
All the events logged can be displayed with Ecoreach software, a smart phone or the FDM128 display. They are shown in chronological order. They can be sorted according to the following selections: date and time, severity, or category.
Event Type and Reset Mode
There are two types of events:
Occurrence / Completion events: These events have a beginning and an end (for example: long-time pick-up and dropout).
Instantaneous events: These events have no duration (for example reception of an opening order, circuit breaker tripping or settings changes).
An event may be latched or unlatched:
-
A latched event does not reset automatically. It remains in hold position after its cause has disappeared or until it is reset by the user.
-
An unlatched event is active while its cause is present and returns to inactive as soon as its cause disappears or is resolved.
For latched events a reset action can be made:
-
From the test/reset button on the front face of the Micrologic control unit.
-
From a PC.
-
From a smart phone.
-
Via Ethernet and Modbus SL (RTU) through the EIFE, IFE and IFM interfaces.
Use a PC, a smartphone, Ethernet or Modbus SL (RTU) to reset events managed by the Micrologic X control unit.