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.

Ex. No.<br />

7<br />

If you want to read data from the standard user program (flags<br />

or PII of standard I/O) in the safety program (here: COND),<br />

which can be changed by the standard user program or an operator<br />

control and monitoring system during the runtime of<br />

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

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

written to these flags immediately before calling the F runtime<br />

group. Only these flags may then be accessed in the<br />

safety program.<br />

This has already been implemented in this example. In general,<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 />

FB"F_PRG"<br />

(FB1,DB1)<br />

FB"F_FDBACK"<br />

(FB216,DB216)<br />

From the<br />

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

library<br />

FC"REINTEGRATION"<br />

(FC2)<br />

F-CALL (FC1)<br />

The obligatory F-CALL (FC 1) is called from the cyclic interrupt<br />

OB (OB 35). This OB calls the F runtime group (here FB 1).<br />

256 Functional Example No. AS-FE-I-007-V10-EN<br />

G_FB_XX_149<br />

FB "F_PRG" (FB 1, DB 1) und FB "F_FDBACK" (FB 216, DB<br />

216)<br />

Network 1<br />

FB "F_PRG" (FB1, DB1) first calls FB "F_FDBACK" (FB216, DB216).<br />

FB 216 is a certified block from the Distributed <strong>Safety</strong> library; this<br />

block is available from version 5.3.<br />

"ACK"<br />

"ESTP"<br />

#ERROR<br />

#N #EN<br />

N<br />

SR<br />

S<br />

>=1<br />

R Q<br />

"COND1"<br />

&<br />

"FEEDBACK K1"<br />

"F00009_<br />

4_F_DO_<br />

DC24V_<br />

2A".QBAD<br />

"ACK_NEC"<br />

"ACK"<br />

T#100MS<br />

"INSTANZ_<br />

FB216"<br />

"F_FDBACK"<br />

The acknowledgement signal ACK is responsible for the acknowledgement<br />

after activating and unlocking the emergency<br />

stop as well as after exceeding the feedback time<br />

FDB_TIME (on FB 1). The latter is indicated by #ERROR="1".<br />

The status of the flip-flop is stored in the static variable #EN<br />

and read as switch-on condition in OB 1.<br />

"1" signal on the formal parameter ACK_NEC indicates that a<br />

manual acknowledgement is required to set release (formal<br />

parameter Q). The bit #ACK_NEC is a static variable with initial<br />

value "0".<br />

Output Q is set to 1 as soon as input ON = 1. It is required that<br />

readback input FEEDBACK = 1 and no readback error must be<br />

stored.<br />

A readback error ERROR = 1 is detected if the signal state of the<br />

readback input FEEDBACK (to output Q) does not follow the<br />

signal state of the input ON within the maximum tolerable<br />

readback time FDB_TIME. K1_K2 is the bit from the F-output<br />

module, which sets the contactors K1 and K2.<br />

To ensure that no readback error is detected and that no acknowledgement<br />

is required in a passivation of failsafe the I/O<br />

modules controlled by output Q you have to supply the input<br />

QBAD_FIO with the variable QBAD of the corresponding failsafe<br />

I/O module DB.<br />

Note<br />

Before inserting the F application block F_FDBACK, you<br />

have to copy the F application block F_TOF from the<br />

block container F-Application Blocks\Blocks of the F library<br />

Distributed <strong>Safety</strong> (V1) into the block container of<br />

your S7 program if it is not available in this container<br />

(has already been done in this example project).<br />

EN<br />

ON<br />

FEEDBACK<br />

QBAD_FIO<br />

ACK_NEC<br />

ACK<br />

FDB_TIME<br />

Q "K1_K2"<br />

ERROR #ERROR<br />

ACK_REQ #ACK_REQ<br />

DIAG ...<br />

ENO<br />

G_FB_XX_150

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

Saved successfully!

Ooh no, something went wrong!