Safety Integrated Functions
8.9 Acceptance test and acceptance report
Function Manual
462 Function Manual, 01/2011, 6SL3097-4AB10-0BP3
5. Test of the SI function "Safe Operating Stop" (SOS)
– Only required when used in Extended Functions
– This test is also required if you are not explicitly using SOS, but just one function for
which STOP D or STOP E occurs as an error response.
Alternatively, you can also carry out the qualitative test using STOP C, STOP D or
STOP E yourself, if you use the table from section Acceptance test for Safe Operating
Stop (SOS) (Page 489).
– Trace recordi
ng is required
6. Test of the SI function "Safely Limited Speed" (SLS)
– Only required when used in Extended Functions
– Trace recordings are required for each SLS limit
7. Test of the SI function "Safe Direction" (SDI)
– Only required when used in Extended Functions
– Trace recordings are required for each stop response used
8. Test of the SI function "Safe Speed Monitor" (SSM)
– Only required when used in Extended Functions
– Trace recording is required
C) Functional testing of forced dormant error detection
Testing the forced dormant error detection of the safety functions for each control type.
1. Test of the forced dormant error detection of the safety function on the drive
– If you are using Basic Functions, you need to activate and then deactivate STO once
again.
– If you are using Extended Functions, you need to carry out a test stop.
D) Conclusion of the report
Report of the commissioning status tested and countersignatures
1. Inspection of SI parameters
2. Logging of checksums (for each drive)
3. Issuing of the Safety password and documenting this process (do not specify the Safety
password in the report!)
4. RAM to ROM backup, upload of project data to STARTER, and backup of the project
5. Countersignature
To Next Page
Loading...
