STOBER
9 | Monitoring and diagnostics
11/2019 | ID 442710.03
39
9.3
Events
The drive controller has a self-monitoring system that uses test rules to protect the drive system from damage. Violating
the test rules triggers a corresponding event. There is no possible way for you as the user to intervene in some events, such
as the Short/ground event. In others, you can influence the effects and responses.
Possible effects include:
§
Message: Information that can be evaluated by the controller
§
Warning: Information that can be evaluated by the controller and becomes a fault after a defined time span has
elapsed without the cause being resolved
§
Fault: Immediate drive controller response; the power unit is disabled and axis movement is no longer controlled by
the drive controller or the axis is brought to a standstill by a quick stop or emergency braking
ATTENTION!
Damage to property due to interruption of a quick stop or emergency braking
If, when executing a quick stop or emergency braking, another fault occurs or a safety function is activated, the quick stop
or emergency braking is interrupted. In this case, the machine can be damaged by the uncontrolled axis movement.
Events, their causes and suitable measures are listed below. If the cause of the error is corrected, you can usually
acknowledge the error immediately. If the drive controller has to be restarted instead, a corresponding note can be found
in the measures.
9.3.1
Event 52: Communication
The drive controller has a fault if A29 = 0: Inactive:
§
The power unit is disabled and axis movement is no longer controlled by the drive controller
§
The brakes are applied in the event of an inactive release override (F06)
The drive controller is interrupted with a quick stop if A29 = 1: Active:
§
The axis is stopped by a quick stop; meanwhile, the brakes remain released
§
At the end of the quick stop, the power unit is disabled and the axis movement is no longer controlled by the drive
controller; the brakes are applied in the event of an inactive release override (F06)
Cause
Check and action
4: PZD-Timeout
Missing process data
Check the IO cycle time in the PROFINET IO
controller and the timeout time in the drive
controller and correct them if necessary (A109)
14: PZD parameter figure faulty
Missing mapping
Check the mapping for unmappable
parameters and correct them if necessary
Tab. 8: Event 52 – Causes and actions