|
This is the web edition of the original ⮫ AC500-S safety user manual, version 1.3.2. This web edition is provided for quick reference only. The original safety user manual must be used to meet functional safety application requirements. |
This example uses different reset signals to acknowledge the emergency stop and to acknowledge the monitoring violation of the drive. If the safety requirement specification of the application allows the acknowledgment of both situations with the same signaling device, the identical signal from the functional application may be used to reset the FB SF_EmergencyStop_1 as well as to reset the FB SF_SafeStop1_1.
Information on the diagnostics concept
The representation of the diagnostics concept is for information only. For the safety functionality, the dedicated safety inputs and outputs shall be used.
Daisy chain from Activate and Ready
The connection of the Ready output to an Activate input of the following FB ensures that no irrelevant diagnostic information is generated if a device is disabled. The daisy chain from Activate and Ready avoid subsequent error messages of related function blocks.
Pre-evaluation of hardware errors
If the target system supports an error signal, e.g., InputDevice_active, which represents the status (active or not active) of the relevant safety device, this signal can be used to disable the safety function blocks. This ensures no irrelevant diagnostic information is generated if a device is disabled. If no such error signal is provided by the target system, a static TRUE signal must be assigned to the Activate input.
Evaluation of the diagnostic information
The Error signals and DiagCodes of each safety function block are transferred to the non-safety application. Diagnosis information might be processed and displayed by an attached visualization. There are different possibilities to realize the evaluation of the diagnostic information:
-
Transfer these values into the visualization and realize the diagnostic evaluation in the visualization.
-
Realize the diagnostic evaluation in the non-safety logic and transfer the results to the visualization.
Because of the various possibilities and the differences in the target system to realize diagnostic processing, there is no special example showed here. Further diagnostic processing could be:
-
Display of the error status for each safety function block.
-
Providing an error overview which is linked to function block specific error displays.
-
Detection and display of the last error of the used safety function blocks in the safety application.
Information on the used function block parameters
|
Function block |
Input |
Constant value |
Description |
|---|---|---|---|
|
SF_Equivalent_1 |
DiscrepancyTime |
10 ms |
Maximum monitoring time for discrepancy status of both inputs. |
|
SF_EmergencyStop_1 |
S_StartReset |
FALSE |
Manual reset when PES is started (warm or cold). |
|
S_AutoReset |
FALSE |
Manual reset when emergency stop button is released. |
|
|
SF_SafeStop1_1 |
AxisID |
AxisID_1 |
Drive address, supplier specific value |
|
MonitoringTime |
100 ms |
Time until the drive shall be stopped. |
|
|
SF_ESPE |
S_StartReset |
FALSE |
Manual reset when PES is started (warm or cold). |
|
S_AutoReset |
FALSE |
Manual reset after safety demand condition is cleared. |