19.08.2013 Views

Safety Integrated - Industry - Siemens

Safety Integrated - Industry - Siemens

Safety Integrated - Industry - Siemens

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

COND2), which can be changed by the standard user program<br />

or an operator control and monitoring system during the runtime<br />

of an F run-time group, it is required to use separate flags<br />

(here: COND1_F or COND2_F). Data from the standard user<br />

program have to be written to these flags immediately before<br />

calling the F run-time group. Only these flags may then be accessed<br />

in the safety program.<br />

F-Call<br />

(FC1)<br />

FB"SAFETY_PRG"<br />

(FB1,DB1)<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 follwoing structure:<br />

FB"F_TOF"<br />

(FB186,DB3)<br />

FB"F_BACK"<br />

(FB216,DB216)<br />

FC"REINTEGRATION"<br />

(FC2)<br />

Readback monitoring<br />

group 1<br />

(contactors K1 and K2)<br />

Readback monitoring<br />

group 2<br />

(contactors K3 and K4)<br />

Reintegration passivated<br />

F-DI/F-DO modules<br />

From the<br />

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

library<br />

Functional Example No. AS-FE-I-009-V10-EN 289<br />

G_FB_XX_173<br />

Ex. No.<br />

9

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

Saved successfully!

Ooh no, something went wrong!