Rockwell Automation 1503VC IntelliVAC Plus Contactor Control Module - Manual (Page 35)

4-8 Description of Features
1503-UM054C-EN-P – June 2013
Counters must be implemented to keep track of the Jog time as well
as for the Jog Repetition time. When a valid Jog command is
detected (Open input is active) and the close command is not active,
the contactor will be given a close command. The Open input
command can also originate from an Open network bit (see
Appendix B).
The IntelliVAC Plus will also keep track of the length of a jog command,
defined as the time from the beginning of the jog command to the
end of the jog command. The most five (5) recent jog events will be
logged to memory, containing the length of the jog as well as the
date/time stamp.
Event Log During operation of the IntelliVAC Plus unit, the contactor will
undergo many operations and experience faults and warning
conditions. All of these events will be logged in non-volatile
memory along with a time stamp. The events for any attached MC
units in an MC configuration will be logged as well. A list of the
available events is listed in Table 4.D. Once the memory array has
been filled with events, newer events will be written over older
events in a circular fashion. Note that the Fault and Warning data
will be written whenever a new fault or warning occurs. Therefore,
if a particular Fault occurs (i.e. CODE #16 – IE Fault) at a particular
time and later on a different IE Fault occurs, the #16 fault will be
written again with the new Fault data along with the new time stamp.
Note:
The ‘Faults/Status/Warnings’ word, from the Basic Module,
will not be written to the Event Log when either the ‘Contactor
Status’ or ‘Module Status’ bits become active. Jog even can only
store up to latest 5 events. This feature avoids too many continuous
job override other events.
Each of the 5 IntelliVAC units will provide for a maximum of 100
events. If fewer than 5 IntelliVAC units are present then there will
be a capability of storing more events per module. Table 4.C shows
the number of events that can be stored as a function of the number
of IntelliVAC units, before older events are overwritten by newer
events.
Table 4.C - Number of Events Stored per # of IntelliVAC Units
# of IntelliVAC Units Maxmimum Number of Events Stored
1 500
2 250
3 166
4 125
5 100