4.4.3 Connection diagrams
Connection diagram for RLY3-OSSD2 with restart interlock and external device moni‐
t
oring
1
2
4
3
5
2) PELV
r
System connection
+24 V DC
OSSD1
OSSD2
0 V
n.c.
1
2
4
3
5
s
System connection
+24 V DC
In2
In1
0 V
n.c
.
F2 F1
+24 V DC
0 V DC
K1K
2
E243749/01/2020-04-02
R1 Y1 Y2 24A
2 14
S1 I1 I2 23A1 13
RLY3-OSSD2
k2
z
k1 k2
k1
z
x
y
x
1)
y
F0
L+
L–
deTec2 Core
deT
ec4 Core
k2
k1
S1
Figure 14: Connection diagram for RLY3-OSSD2 with restart interlock and external device moni‐
t
oring
1) Output circuits: These contacts must be incorporated into the control such that the dan‐
gerous state is brought to an end if the output circuit is open. For categories 4 and 3, they
must be incorporated on dual-channels (x, y paths). Type 2 devices are suitable for use up
to PL c. Single-channel incorporation into the control (z path) is only possible with a single-
channel control and taking the risk analysis into account.
2) SELV/PELV safety extra-low voltage.
Task
•
C
onnection of a multiple light beam safety device deTem4 Core to a RLY3-OSSD2
safety relay. Operating mode: With restart interlock and external device monitoring.
Mode of operation
•
When the light path is clear, the OSSD1 and OSSD2 outputs carry voltage. The sys‐
tem can be switched on when K1 and K2 are in a fault-free de-energized position.
The RLY3-OSSD2 is switched on by pressing S1 (pushbutton is pressed and
released). The outputs (contacts 13-14 and 23-24) switch the K1 and K2 contac‐
tors on. When the light path is interrupted, the OSSD1 and OSSD2 outputs switch
the RLY3-OSSD2 off. Contactors K1 and K2 are switched off.
Fault analysis
•
Cross-circuits and short-circuits of the OSSDs are recognized and lead to the lock‐
ing status (lock-out). A malfunction with one of the K1 or K2 contactors is
detected. The switch-off function is retained. In the event of manipulation (e.g.,
jamming) of the S1 pushbutton, the RLY3-OSSD2 will not re-enable the output cur‐
rent circuits.
4.5 Testing plan
The manufacturer of the machine and the operating entity must define all required
c
hecks. The definition must be based on the application conditions and the risk assess‐
ment and must be documented in a traceable manner.
PROJECT PLANNING 4
8020453/14Q7/2020-04-27 | SICK O P E R A T I N G I N S T R U C T I O N S | deTem4 Core
23
Subject to change without notice