19.08.2013 Views

Safety Integrated - Industry - Siemens

Safety Integrated - Industry - Siemens

Safety Integrated - Industry - Siemens

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Ex. No.<br />

5<br />

Program procedure<br />

OB 1 defines the start conditions for the hazardous machine<br />

(here simulated by an indicator light):<br />

"START"<br />

"P"<br />

P &<br />

"MS_11"<br />

"MS_12"<br />

"MS_21"<br />

"MS_22"<br />

"INSTANZ_<br />

FB1".FAULT<br />

STOP"<br />

>=1<br />

"SR"<br />

SR<br />

S<br />

R Q<br />

"COND"<br />

=<br />

G_FB_XX_128<br />

Parameter Adress Explanation<br />

START E 0.0 (NO) Start request<br />

MS_11 E 1.0 Optical proximity switch (as muting<br />

MS_12<br />

MS_21<br />

E 1.1<br />

E 2.0<br />

sensor) Any type of sensor can be<br />

used which need not be failsafe.<br />

Convention: At the "1" signal the ob-<br />

MS_22 E 2.1 ject is recognized.<br />

INSTANZ_FB1. DB1.DBX4.2 This bit causes a start of the "ma-<br />

FAULT<br />

chine" to only be possible after previous<br />

acknowledgement. The signal<br />

status of this bit is defined in the<br />

safety program (FB 1) and filed in its<br />

respective instance DB (DB1, byte 4,<br />

bit 2)<br />

STOP M 92.3 Dummy bit In this example, no operational<br />

stopping has been implemented.<br />

If you wish to extend the<br />

example accordingly, the memory bit<br />

can be replaced by the respective<br />

sensor signal.<br />

COND M 92.0 Sets or resets the machine (in FB 1 of<br />

the safety program).<br />

230 Functional Example No. AS-FE-I-005-V10-EN<br />

A start in this example shall only be possible if workpieces are<br />

out of the monitored area of the light curtain<br />

(MS_11…MS_22="0").<br />

The information of the memory bit "COND" is read as memory<br />

bit COND1 in the safety program. This allocation occurs in the<br />

cyclic interrupt OB 35 for the following reason:<br />

When reading data, which may be changed by the standard<br />

user program or an operation control and monitoring system<br />

during running of an F runtime group, from the standard user<br />

program (memory bits or PAE of standard I/O), in the safety<br />

program, it is necessary to use separate memory bits (here<br />

COND1). Data from the standard user program have to be<br />

written to these memory bits immediately before calling the F<br />

runtime group. Only these memory bits may then be accessed<br />

in the safety program.<br />

In this example it has already been implemented. Generally,<br />

however, the following applies:<br />

Note<br />

If the above section is not observed the F CPU may go to<br />

STOP mode.<br />

The failsafe program has the following program sequence:<br />

F-Call<br />

(FC1)<br />

FC"<strong>Safety</strong>_Prg"<br />

(FC10)<br />

FB"L_CURTAIN"<br />

(FB1,DB1)<br />

FC"REINTEGRATION"<br />

(FC2)<br />

FB"F_MUTING"<br />

(FB 189,DB 189)<br />

From the<br />

Distributed <strong>Safety</strong><br />

library<br />

F-CALL (FC1)<br />

F-CALL (FC 1) is the F runtime group and is called from the cyclic<br />

interrupt OB (OB 35). F-CALL calls the F-programe block<br />

(here the FC 10).<br />

FC "<strong>Safety</strong>_Prg" (FC 10)<br />

FC 10 ensures the modular setup of the safety program.<br />

G_FB_XX_129

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!