Technical data

Safety Integrated Functions
8.9 Acceptance test and acceptance report
Function Manual
Function Manual, 06/2012, 6SL3097-4AB10-0BP4
491
Acceptance test for Safe Operating Stop (SOS)
Table 8- 35 "Safe Operating Stop" function
No. Description Status
Note:
The acceptance test must be individually conducted for each configured control.
The control can be realized via terminals or via PROFIsafe.
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)
• SOS inactive (r9722.3 = 0)
1.
• No Safety faults and alarms (r0945[0...7], r2122[0...7], r9747[0...7]); see note "Non-
critical alarms" at the beginning of the section "Acceptance test".
2.
• It may be necessary to take measures in the higher-level control to be able to run the drive with activated
SOS.
• Please note that the internal limits r9733.0 and r9733.1 are canceled by the selection "Start acceptance test".
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
infringement of the SOS tolerance window (p9330/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
Run the drive beyond the standstill limit set in p9330/p9530
• Check whether the drive moves briefly and then decelerates 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)
3.
• C01700, C30700 (STOP A initiated)