Programming
Description of Application Faults
Introduction
Soft stops
These faults are indicated by the AX_ERR bit (%Ixy.i.5). The parameters can be accessed by the Adjustment screen of the configuration editor. There is no fault checking associated with the soft stops for the unlimited axes (modulo).
The following table shows the cause, indication and the solution if a Soft stops fault should occur. This is a blocking fault and cannot be deactivated.
Cause
Parameter
Result
Indication
Remedy
The moving part is no longer situated between the 2 thresholds: lo and hi software limits (this check is activated as soon as the axis is referenced)
Software hi limit: SL_MAX (%MDxy.i.31)
Software lo limit: SL_MIN (%MDxy.i.33)
Moving part is forced to stop
%MWxy.i.3:X8 bit: Software hi limit exceeded
%MWxy.i.3:X9 bit: Software lo limit exceeded
Acknowledge the fault and in manual mode release the moving part outside of the soft stops within the valid measurement space. To do this you must check: l l l l l that there is no movement in progress, that manual mode is selected, that the STOP command is at 0, that the axis on which this command is carried out is referenced, that there is no other fault with stop on the axis.
The moving part can either be repositioned manually or by using the
JOG+ and JOG- commands.
Overspeed The following table shows the cause, the signal and the solution if an Overspeed fault should occur. This is a blocking fault and can be deactivated.
Cause
Parameter
Result
Indication
Remedy
On one of the axes, the speed of the moving part has exceeded the increased max. speed of the overspeed threshold: VMAX (1 +
OVR_SPD)
Overspeed threshold OVR_SPD (%MWxy.i.23). If this parameter is equal to 0, the monitoring is inhibited.
The moving part is stopped
%MWxy.i.3:X10 bit
Acknowledge the fault
TLX DS 57 PL7 xxE
173
Programming
Stop The following table shows the cause, the signal and the solution if a Stop fault should occur. This is a non-blocking fault and can be deactivated.
Cause
Parameter
Result
Indication
Remedy
As soon as the speed setpoint value calculated by the module becomes equal to 0, the module activates a T_STOP time-out: l l
If this parameter is equal to 0, the fault monitoring is inhibited.
If this parameter is different from 0, when the time-out has elapsed, the module compares the moving part’s measured speed with the stop speed S_STOP. If the measured speed is greater than
S_STOP, the module indicates a stop fault.
T_STOP (%MWxy.i.25): maximum delay for detecting a stop
S_STOP (%MWxy.i.24): speed at which moving part is considered to be at a stop the fault is signaled
%MWxy.i.3:X14 bit
Eliminate the drive fault or perform further adjustments then acknowledge the fault
Target window The following table shows the cause, the signal and the solution if a Target window fault should occur. This is a non-blocking fault and can be deactivated.
Cause
Parameter
Result
Indication
Remedy
When a movement to a position with stop is requested, the module checks that the position reached corresponds to the requested position, according to the theoretical stop, using a tolerance that you defined in the parameter TW (Setpoint – TW <= measurement <=
Setpoint + TW)
If this parameter is equal to 0, the check is inhibited
TW (%MDxy.i.49): target window
If the moving part is not in the target window, the fault is signaled
%MWxy.i.3:X13 bit: target window fault
Check the control loop then acknowledge the fault
174
TLX DS 57 PL7 xxE
Recalibration
Zero latch presence monitoring
Programming
The following table shows the cause, the signal and the solution if a Recalibration fault should occur. This is a non-blocking fault and can be deactivated.
Cause
Parameter
Result
Indication
Remedy
During a recalibration event, the error between the current position and the recalibration reference value is higher than the recalibration threshold
The check is inhibited if you have chosen the Recalibration function missing configuration parameter
RE_WDW (%MDxy.i.51): recalibration deviation threshold
RE_POS (%MDxy.i.43): recalibration reference value
If the deviation exceeds the threshold, the fault is signalled
%MWxy.i.3:X12 bit: recalibration fault
Check the control loop then acknowledge the fault
The following table shows the cause, the signal and the solution if a Zero Pulse
Presence Monitoring fault should occur.
Cause
Parameter
Result
Indication
Remedy
During a reference point short cam with zero pulse
None
The axis stops
%Ixy.i.6 bit
%MWxy.i.7word = 16#0015 (CMD_FLT)
Mechanically adjust the cam then restart the operation
TLX DS 57 PL7 xxE
175
Programming
Movement monitoring
The following table shows the cause, the signal and the solution if a Movement
monitoring fault should occur: This is a blocking fault and can be deactivated.
Cause
Parameter
Result
Indication
Remedy
When the analog output from a channel exceeds a VLIM limit (in absolute value), a time delay is activated
When T is reached, a fault is signaled if the position value is the same as that of the internal cycle of the module
VLIM limit analog output: %MWxy.i.27
The time-out T is programmed to TACC / 2. TACC is the acceleration adjustment parameter (%MWxy.i.26)
If the fault is detected the moving part is stopped (analog output set to
0 and speed control authorization relay open)
The check is only enabled if VLIM > 0
%MWxy.i.3:X11 bit: MAX_F1 deviation exceeded
Check the control loop then acknowledge the fault
Note: Movement monitoring is active in direct control, manual and automatic modes.
Following error The following table shows the cause, the signal and the solution if a Tracking error fault should occur. The MAX_F1 fault is a blocking fault and can be deactivated. The
MAX_F2 fault is a non-blocking fault and can be deactivated.
Cause
Parameter
Result
Indication
Remedy
During a movement, the module compares the measured position of the moving part. A fault is signalled when the tracking error becomes higher than the maximum authorized error that you defined
Abnormal non-critical following error MAX_F2 (%MDxy.i.47)
Abnormal critical following error MAX_F1 (%MDxy.i.45)
If these parameters are at 0, monitoring is inhibited.
If the MAX_F2 error is exceeded, the fault is signalled
If the MAX_F1 error is exceeded, the moving part is stopped. This fault is only taken into account if MAX_F1 is different from 0
%MWxy.i.3:X15 bit (MAX_F2 error exceeded)
%MWxy.i.3:X11 bit (MAX_F1 error exceeded)
Check the control loop then acknowledge the fault
176
TLX DS 57 PL7 xxE
