Appendix
A.3 Acceptance tests (recommendations)
Acceptance test for Safe Operating Stop (SOS)
N o .
N o te:
The acceptance test must be individually performed for each configured control.
The control can be realized via TM54F, onboard terminals (CU310-2) or via PROFIsafe.
1.
Initial state
Drive in the "Ready" state (p0010 = 0)
•
Safety Integrated Extended Functions enabled (p9601.2 = 1)
•
Safety functions enabled (p9501.0 = 1)
•
Safety configured with encoder (p9506 = 0 or p9506 = 2)
•
SOS inactive (r9722.3 = 0)
•
No Safety faults and alarms (r0945[0...7], r2122[0...7], r9747[0...7]) at the drive and
•
TM54F (if used); see note "Non-critical alarms" at the beginning of Section "Ac-
ceptance test."
2.
It may be necessary to take measures in the higher-level controller to be able to run the drive with activated
•
SOS.
Note that the internal limits (r9733[0], r9733[1] and r9733[2]) are removed by selecting "Start acceptance
•
test".
3.
Configure and activate trace recording.
Trigger: Trigger on variable - bit pattern (r9722.7 = 0)
•
Record the following values: r9713[0], r9720, r9721, r9722
•
Select the time interval and pretrigger so you can recognize start-up of the drive and
•
violation of the SOS tolerance window (p9530)
For better analysis, display the following bit values:
r9720.3 (deselect SOS)
•
r9721.12 (STOP A or B active)
•
r9722.0 (STO active; set for STOP A)
•
r9722.1 (SS1 active; set for STOP B)
•
r9722.3 (SOS active)
•
r9722.7 (internal event; set when the first safety message occurs)
•
Select SOS
Traverse the drive beyond the standstill limit set in p9530
Check whether the drive moves briefly and then is braked back to a standstill
•
Check whether the following safety messages are pending:
C01707, C30707 (tolerance for safe operating stop exceeded)
•
C01701, C30701 (STOP B initiated)
•
C01700, C30700 (STOP A initiated)
•
4.
Analyze trace:
432
D e scri p ti o n
Function Manual, (FHS), 07/2016, 6SL3097-4AR00-0BP6
Sta tu s
Safety Integrated