ID 442426.04
154
WE KEEP THINGS MOVING
Basic properties
8
Manual SD6
8.4
Events
Event displays give you information about the status of the drive controller. A
list of event displays can be found in section 16 Diagnosis.
The response to an event can be set up in four levels: Inactive, Message,
Warning or Fault.
1. If an event is parameterized as a message, it will appear in the bottom line
of the display, flashing. An application is not affected by a message.
Operation continues normally. Messages are not acknowledged. They
persist until the cause is eliminated.
2. A warning is indicated by a flashing text. The event is also displayed. After
a defined time has elapsed, the warning becomes a fault. The remaining
time is shown in the display. If the cause is eliminated within the set time.
the warning is reset. An application is not affected by a warning.
3. If an event occurs with the
Fault
level, the device immediately switches to
the
Fault reaction
device state. The event is displayed in the bottom line of
the display. A fault must be reset.
The device provides notes about the cause for some of the events. They are
identified by a number which also appears in the list of events in the display:
Causes that are not documented with a number in the event description in
section 16 Diagnosis simply provide references to possible errors. They do not
appear in the display.
Events relate to several areas:
•
With active configuration
If device start-up is complete and configuration is active, the events
identified by the number monitor operation. Acknowledgement on the
operator panel or via binary input can be programmed for some of these
events. This does not affect communication or operation of the device. The
occurrence of the event is noted by a counter for use in further diagnostics.
The fault counter is saved in parameter group
Z..
.
Some of these events can be parameterized, for example event
39:TempDev i2t
.
•
Process errors detected by the CPU
Errors related to the drive controller CPU are identified by the number sign
"#". In this case the power board and menu function of the operator panel
are switched off and communication is interrupted. The only way to return
to normal operation is to turn the device off and back on again.
•
Errors while the device is starting
During device start-up, configuration parameter, flag and signal values are
loaded from the memory module. Then the configuration is started.
Detailed error messages can be generated for both steps. They are
identified by the asterisk sign "*" . If there is no ParaModul present or an
error occurs while it is being loaded from the memory module,
*ParaModul
ERROR
appears in the top line to identify this condition. If an error occurs
while the configuration is being started,
*ConfigStrtERROR
appears in the
display. To eliminate these errors, switch the device off and back on or
transfer a configuration.
