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

When Some I/O Modules Are <strong>Safety</strong>-Critical<br />

For some applications, not all modules may be critical to a process. For example, an output<br />

module that interfaces to the status indicators on a local panel is usually not critical to a process.<br />

The EX02_SHUTDOWN sample program shows how to increase system availability by<br />

detecting the status of safety-critical modules. The user-defined function block CRITICAL_IO<br />

checks the safety-critical I/O modules. The CRITICAL_IO outputs are connected to the inputs<br />

of the CRITICAL_MODULES function block.<br />

Note<br />

The sample program is an element of project TdTUV.pt2 included as part of the<br />

TriStation 1131 software installation. The default location of the project is C:\Documents<br />

and Settings\\My Documents\<strong>Triconex</strong>\TriStation 1131 4.x\Projects.<br />

When the output CRITICAL_MODULES_OPERATING is true, all critical modules are<br />

operating properly. The input MAX_TIME_DUAL specifies the maximum time allowed with<br />

two channels operating (with no connection, defaults to 40000 days). The input<br />

MAX_TIME_SINGLE specifies the maximum time allowed with one channel operating (three<br />

days in the example).<br />

Note<br />

In typical applications, the operating time restrictions in the table on page 22 should be<br />

followed.<br />

When CRITICAL_MODULES_OPERATING is false, the time in degraded operation exceeds<br />

the specified limits; there<strong>for</strong>e, the control program should shut down the plant.<br />

CAUTION<br />

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

Program EX02_SHUTDOWN<br />

Figure 11<br />

EX02_SHUTDOWN Sample Program<br />

Table 12<br />

Parameter<br />

CI<br />

IO_CO<br />

IO_TMR<br />

IO_GE_DUAL<br />

IO_GE_SINGLE<br />

Input Parameters <strong>for</strong> SYS_SHUTDOWN Function Block in EX02_SHUTDOWN<br />

Description<br />

Control In<br />

If false, then CO is false—no change in the output value<br />

If true and ERROR_NUM is 0, then CO is true<br />

Critical I/O control out<br />

All critical I/O points are operating in triple modular<br />

redundant mode<br />

All critical I/O points are operating are operating in dual or<br />

TMR mode<br />

All critical I/O points are operating are operating in single,<br />

dual, or TMR mode<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!