Technical data

Safety Integrated Functions
8.9 Acceptance test and acceptance report
Function Manual
464 Function Manual, 06/2012, 6SL3097-4AB10-0BP4
8.9.2.2 Content of the partial acceptance test
A) Documentation
Documentation of the machine and of safety functions
1. Extending/changing the hardware data
2. Extending/changing the software data (specify version)
3. Extending/changing the configuration diagram
4. Extending/changing the function table:
– Active monitoring functions depending on the operating mode and the protective door
– Other sensors with protective functions
– The table is part or is the result of the configuring work
5. Extending/changing the SI functions per drive
6. Extending/changing the specifications of the safety equipment
B) Functional testing of safety functions
Detailed function test and evaluation of SI functions used. For some functions this contains
trace recordings of individual parameters. The procedure is described in detail in section
Acceptance tests.
The function test can be left out if no parameters of the individual safety functions have been
changed. In the case that only parameters of individual functions have been changed, only
these functions need to be tested anew.
1. Test of the SI function "Safe Torque Off" (STO)
– Required when used in Basic and/or Extended Functions
– This test is also required if you are not explicitly using STO, but just one function for
which STOP A occurs as an error response.
Alternatively, you can also carry out the quantitative test using STOP A yourself, if you
use the tables from sections Acceptance test Safe Torque Off (Bas
ic Functions)
(Page 476) , Acceptance test Safe Torque Off with encoder
(Extended Functions)
(Page 482) or Acceptance test Safe Torque Off without encoder (E
xtended Functions)
(Page 528).
– You do not n
eed to prepare trace recording for this test.
2. Test of the SI function "Safe Stop 1" (SS1)
– Required when used in Basic and/or Extended Functions
– This test is also required if you are not explicitly using SS1, but just one function for
which STOP B occurs as an error response.
Alternatively, you can also carry out the quantitative test using STOP B yourself, if you
use the tables from sections Auto-Hotspot or Auto-Hotspot.
– Trace recording only required if Extended Functions are used