3.1 Event log
3 Supporting functions
Technical description
82
VAMP 24h support phone +358 (0)20 753 3264
VM55.EN005
3.
Supporting functions
3.1.
Event log
Event log is a buffer of event codes and time stamps including
date and time. For example each start-on, start-off, trip-on or
trip-off of any protection stage has a unique event number code.
Such a code and the corresponding time stamp is called an
event. The event codes are listed in a separate document
“Modbus_Profibus_Spabus_event.pdf”.
As an example of information included with a typical event an
overvoltage trip event of the first 59 stage U> is shown in the
following table.
EVENT
Description
Local
panel
Communication
protocols
Code: 30E2
Channel 30,
event 2
Yes
Yes
U> trip on
Event text
Yes
No
120 Un%
Fault value
Yes
No
2007-01-31
Date
Yes
Yes
08:35:13.413
Time
Yes
Yes
Type: 1-N, 2-N, 3-N
Fault type
Yes
No
Events are the major data for a SCADA system. SCADA
systems are reading events using any of the available
communication protocols. Event log can also be scanned using
the front panel or using VAMPSET. With VAMSET the events
can be stored to a file especially in case the relay is not
connected to any SCADA system.
Only the latest event can be read when using communication
protocols or VAMPSET. Every reading increments the internal
read pointer to the event buffer. (In case of communication
error, the latest event can be reread any number of times using
an other parameter.) On the local panel scanning the event
buffer back and forth is possible.
Event enabling/masking
In case of an uninteresting event, it can be masked, which
prevents the particular event(s) to be written in the event
buffer.
As a default there is room for 200 latest events in the buffer.
Event buffer size can be modified from 50 to 2000 in all v.10.xx
softwares. Modification can be done in “Local panel conf” –
menu. Alarm screen (popup screen) can also be enabled in this
same menu when Vampset –setting tool is used. The oldest one
