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 />

3<br />

The acknowledgement for the enable is given at the input<br />

ACK_NEC depending on the parameters:<br />

■ For ACK_NEC = 0 an automatic acknowledgement is given<br />

(as implemented in this example).<br />

■ For ACK_NEC = 1 an enable requires acknowledging ACK at<br />

the input by means of a rising edge.<br />

In order for the F application block to recognize whether the<br />

inputs IN1 and IN2 are only "0" due to a passivation of the respective<br />

F-periphery, you must supply the inputs QBAD_IN1<br />

and QBAD_IN2 with the variable QBAD of the respective F periphery<br />

DB. This prevents for example that for a passivation of<br />

the F-periphery the safety door must be completely opened<br />

prior to acknowledgement.<br />

Warning!<br />

The parameterization of the variables ACK_NEC=0 is<br />

only permitted, if an automatic restart of the respective<br />

process is excluded otherwise.<br />

Should you supplement the example by means of a manual<br />

acknowledgement, please note the following:<br />

Note<br />

For safety door applications, the acknowledge signal<br />

must be read via a failsafe input module (F-DI), if it is an<br />

accessible hazardous area. For a non-accessible hazardous<br />

area, the acknowledge signal can also be read via a<br />

standard input module.<br />

The F-application module supports the requirements according<br />

to EN954-1 and EN 1088.<br />

After restarting the F system, the enable signal Q is reset to<br />

"0". The acknowledgement for the enable is given at the input<br />

OPEN_NEC and ACK_NEC depending on the parameters:<br />

■ For OPEN_NEC = 0 an automatic acknowledge is given<br />

independent of ACK_NEC, as soon as both inputs IN1 and<br />

IN2 have the signal status 1 for the first time after reintegration<br />

of the respective F periphery (safety door is closed).<br />

In this example this variant has not been activated.<br />

■ For OPEN_NEC = 1 or if at least on of both inputs IN1 and<br />

IN2 have the signal status "0" even after reintegration of<br />

the respective periphery, an automatic acknowledgement<br />

is given depending on ACK_NEC, or the enable requires<br />

acknowledging ACK at the input by means of a rising edge.<br />

Prior to acknowledgement both inputs IN1 and IN2 must<br />

have had the signal status 0 (safety door completely<br />

opened) and subsequently signal status 1 (safety door<br />

closed).<br />

204 Functional Example No. AS-FE-I-003-V10-EN<br />

Warning!<br />

The parameterization of the variables OPEN_NEC=0<br />

is only permitted, if an automatic restart of the respective<br />

process is excluded otherwise.<br />

At the output DIAG a non-failsafe information on occurred errors<br />

is provided for service purposes. You can read it out via<br />

HMI systems or if necessary evaluate them in your standard<br />

user program.<br />

Note<br />

The safety program does not allow accessing the output<br />

DIAG!<br />

FB "COORDINATION" (FB1, DB1)<br />

After processing the FB 217, processing is continued in FB 1:<br />

Network 2<br />

#COND1<br />

The machine must only start at valid enable from FB 217 (#RE-<br />

LEASE="1") and the start request ("COND1"="1") from the<br />

standard user program. Additionally the tumbler (E_MAGNET)<br />

must be monitored (see "Network 3" below). The "machine"<br />

stops by a failure locking.<br />

Network 3<br />

#RELEASE<br />

"E_MAGNET"<br />

#COND1<br />

#RELEASE<br />

&<br />

"ACT_PAS"<br />

&<br />

>=1<br />

#ACTUATOR<br />

=<br />

"COIL"<br />

=<br />

G_FB_XX_103<br />

G_FB_XX_104

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

Saved successfully!

Ooh no, something went wrong!