Forced Dormant Error Detection - Siemens SINAMICS G130 Manual

● r9713[0...3] SI Motion diagnostics position action value load side
● r9714[0...1] SI Motion diagnostics speed
● r9724 SI Motion crosswise comparison clock cycle
● r9730 SI Motion safe maximum velocity
● r9731 SI Motion safe position accuracy
6.14

Forced dormant error detection

Forced dormant error detection and function test through test stop
The functions and switch-off signal paths must be tested at least once within a defined
period to establish whether they are working properly in order to meet the requirements of
EN ISO 13849-1 and IEC 61508 in terms of timely error detection.
The maximum permissible interval for forced dormant error detection with the Basic
Functions and Extended Functions is 9000 hours or once a year.
This functionality must be implemented by means of test stop triggering either in cyclic
manual mode or by the automated process.
The test stop cycle is monitored. On expiration of the parameterized timer (also after
POWER ON / warm restart), the alarm A01697: "SI Motion: Test of motion monitoring
required" is generated and a status bit is set which can be transferred to an output or to a
PZD bit via BICO. This alarm does not affect machine operation.
The test stop must be initiated application-specific and be executed at a time which suits
application requirements. This functionality is implemented by means of a single-channel
parameter p9705 which can be wired via BICO either to an input terminal on the drive unit
(CU), or to an IO-PZD in the drive telegram.
● p9559 SI Motion Forced dormant error detection timer (Control Unit)
● p9705 BI: SI Motion Test stop signal source
● r9723.0 CO/BO: SI Motion diagnostics signals integrated in the drive
A test stop does not require POWER ON. The acknowledgment is set by canceling the test
stop request.
When the appropriate safety devices are implemented (e.g. protective doors), it can be
assumed that running machinery will not pose any risk to personnel. For this reason, only an
alarm is output to inform the user that a forced dormant error detection run is due and to
request that this be carried out at the next available opportunity.
Examples of when to carry out forced dormant error detection:
● When the drives are at a standstill after the system has been switched on (POWER ON).
● Before the protective door is opened.
● At defined intervals (e.g. every 8 hours).
● In automatic mode (time and event dependent)
Safety Integrated
Function Manual, 05/2010, A5E03264275A
Safety Integrated Extended Functions
6.14 Forced dormant error detection
119