The function block can detect two types of errors:
|
Type of detected error |
Example |
Description |
Reset |
|---|---|---|---|
|
Axis errors |
Following error |
The function block reacts on detected axis errors and provides the dedicated information. |
Axis errors must be reset outside the function block. |
|
Function block errors |
A parameter is outside the value range. |
These errors are detected by the function block when:
|
Function block errors are reset with a falling edge of the input i_xEnable or i_xStartOperation. |
If an error is detected, the output q_xError is set to TRUE and error information is provided at q_etResult and q_sResultMsg. The output q_xError remains TRUE and subsequent errors are not indicated until the function block is disabled and the error state is reset.
In general, two types of errors can be detected:
Axis errors (such as following errors)
The function block detects errors that are related to the axis and provides the corresponding error information but does not reset them. The reset must be performed outside the function block.
Function block-specific errors (such as parameters outside the value range)
The function block detects such errors while verifying the parameters (with a rising edge of the input i_xEnable) or while verifying the inputs (with a rising edge of the input i_xStartOperation) or while modifying during the operation. These errors are reset upon a falling edge of the input i_xEnable or i_xStartOperation respectively.
As a consequence, the function block does not have a specific input to reset detected errors.
If an error is detected while the axis is moving, the movement is stopped immediately with the deceleration ramp (lrStopDeceleration) without considering the process cycle.