02.02.2015 Views

Safety Considerations Guide for Triconex General ... - ICEWeb

Safety Considerations Guide for Triconex General ... - ICEWeb

Safety Considerations Guide for Triconex General ... - ICEWeb

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.

Sample <strong>Safety</strong>-Shutdown Programs 57<br />

Partitioned Processes<br />

You can achieve greater system availability if you can allocate modules to processes that do not<br />

affect each other. For example, you could have two processes with:<br />

• Outputs <strong>for</strong> one process on one DO module<br />

• Outputs <strong>for</strong> another process on a second DO module<br />

• Inputs from a shared DI module<br />

You do this by partitioning processes.<br />

Procedure<br />

1 Partition the safety-critical I/O modules into three function blocks:<br />

• SHARED_IO <strong>for</strong> the shared safety-critical I/O modules<br />

• PROCESS_1_IO <strong>for</strong> safety-critical I/O modules that do not affect process 2<br />

• PROCESS_2_IO <strong>for</strong> safety-critical I/O modules that do not affect process 1<br />

2 Connect the function blocks as shown in the EX03_SHUTDOWN example on page 58.<br />

CAUTION<br />

EX03_SHUTDOWN does not handle detected field faults, rare<br />

combinations of faults detected as field faults, or output voter faults<br />

hidden by field faults. The application, not the SYS_SHUTDOWN<br />

function block, must read the NO_FLD_FLTS module status or FLD_OK<br />

point status to provide the required application-specific action.<br />

<strong>Safety</strong> <strong>Considerations</strong> <strong>Guide</strong> <strong>for</strong> <strong>Triconex</strong> <strong>General</strong> Purpose v2 Systems

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

Saved successfully!

Ooh no, something went wrong!