7.2.8 Periodic Proof Tests
The following table shows the periodic proof tests, which are either automatically performed or have to be done
manually.
Test
Automatically
on Startup
Automatically
periodically
Instructions for user
CPU
yes
yes, < 500 ms
RAM
yes
yes, < 500 ms
Parameter CRC
yes
yes, <500 ms
Parameter
Consistency
yes
no
Safety program CRC yes
yes, < 500 ms
Safe Brake Control
no
yes, every 900 ms
Brake Output test pulses every 900ms for 1ms
STO circuit
no
yes
every 1000 ms
STO switch change every 1000ms
Safe Dig In
no
yes,
discrepancy time: 50 ms
Stuck at must be detected on the output module, e.g. with test
pulse
Safe Dig Out
yes,
Test pulses in high state
every 1100 ms,
discrepancy time: 50 ms
Input must be capable for test pulses. See also 7.13 - Safe Digital
Output.
Fieldbus CRC
no
yes
every bus cycle
Brake Test
no
no, the drive signalizes if
SBT Request Interval has
expired.
The SBT Request Interval (UPID 47DAh) must be configured
according to the applicational requirements. When the SBT
Request Interval has expired (Safety Fn State Brake Tst time Ov
UPID 1A21h becomes active) the SBT Request must be activated
for starting the SBT sequence. See chapter 7.17 - Safe Brake Test
(SBT)
Maintenance of
System
no
no
A periodic maintenance of the machine has to be planned. See
chapter 11.2 - Maintenance.
Table 25: Periodic proof tests
2S Drive Systems / 0185-1174_E_1V1_SM_C1251-2S / NTI AG
0185-1174_E_1V1_SM_C1251-2S / 2021-11-26 16:43 (Rev. 12500)
Page 55 of 150