3.18 Overload Recording (Function Group OL_RC)
3.18.1 Start of Overload Recording
An overload exists – and consequently overload recording begins – if at least the
signal THRM1: Starting k*Iref> is issued.
3.18.2 Counting Overload Events
Overload events are counted and identified by sequential numbers.
1: execute
MAIN:
General reset USER
[ 003 002 ]
MAIN:
General reset EXT
[ 005 255 ]
1: execute
OL_RC:
Reset record. USER
[ 100 003 ]
64Z80C3A
R
+
OL_RC:
No. overload
[ 004 101 ]
OL_RC:
Record. in progress
[ 035 003 ]
OL_RC:
Reset record. EXT
[ 005 241 ]
THRM1:
Starting k*Iref>
[ 039 151 ]
Fig. 3-68: Counting overload events.
3.18.3 Time Tagging
The date of each overload event is stored. The overload start or end signals are
likewise time-tagged by the internal clock. The date and time assigned to an
overload event when the event begins can be read out from the overload
memory on the local control panel or through the PC and communication
interfaces. The time information (relative to the onset of the overload) can be
retrieved from the overload memory or through the PC or one of the
communication interfaces.
P631
3 Operation
3-98 P631/EN M/R-11-C // P631-310-650