Safety Considerations Guide for Triconex General ... - ICEWeb
Safety Considerations Guide for Triconex General ... - ICEWeb
Safety Considerations Guide for Triconex General ... - ICEWeb
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
82 Appendix C <strong>Safety</strong>-Critical Function Blocks<br />
Instructions <strong>for</strong> Use<br />
To initialize, invoke once with RESET := TRUE.<br />
To complete initialization, invoke again with these input settings:<br />
• RESET := FALSE<br />
• CI := TRUE<br />
• APP := DE_ENERGIZED<br />
• RELAY_OK := false<br />
To get the status of a safety-critical I/O module:<br />
• For each module, invoke specifying the input values:<br />
• IOP<br />
• SLOT<br />
• APP<br />
• RELAY_OK<br />
For example, if IOP 1 SLOT 1 is a critical DO module with a relay, and SCIO is the<br />
function block instance name:<br />
SCIO( IOP:=1, SLOT:=1, APP:=RELAY,RELAY_OK:=RELAY1_OK );<br />
• Read the output values:<br />
• CO<br />
• TMR<br />
• GE_DUAL<br />
• GE_SINGLE<br />
Example<br />
For shutdown examples, see the sample project located at My Documents\<strong>Triconex</strong>\TriStation<br />
1131 4.x\Projects\TdTUV.pt2<br />
Runtime Errors<br />
Condition Return Value Error Flags<br />
If ERROR_NUM is non-zero Reset all BOOL outputs to false BADPARAM, ERROR<br />
Upon detection of a runtime error condition, the function block returns the indicated values and<br />
sets the error flags to true. For more in<strong>for</strong>mation about error flags and runtime errors, see the<br />
TriStation 1131 Libraries Reference.<br />
Application Notes<br />
• Can be used in <strong>Safety</strong> or Control applications.<br />
<strong>Safety</strong> <strong>Considerations</strong> <strong>Guide</strong> <strong>for</strong> <strong>Triconex</strong> <strong>General</strong> Purpose v2 Systems