Safety Considerations Guide for Triconex General ... - ICEWeb

More documents

Recommendations

Info

82 Appendix C Safety-Critical Function Blocks Instructions for Use To initialize, invoke once with RESET := TRUE. To complete initialization, invoke again with these input settings: • RESET := FALSE • CI := TRUE • APP := DE_ENERGIZED • RELAY_OK := false To get the status of a safety-critical I/O module: • For each module, invoke specifying the input values: • IOP • SLOT • APP • RELAY_OK For example, if IOP 1 SLOT 1 is a critical DO module with a relay, and SCIO is the function block instance name: SCIO( IOP:=1, SLOT:=1, APP:=RELAY,RELAY_OK:=RELAY1_OK ); • Read the output values: • CO • TMR • GE_DUAL • GE_SINGLE Example For shutdown examples, see the sample project located at My Documents\Triconex\TriStation 1131 4.x\Projects\TdTUV.pt2 Runtime Errors Condition Return Value Error Flags If ERROR_NUM is non-zero Reset all BOOL outputs to false BADPARAM, ERROR Upon detection of a runtime error condition, the function block returns the indicated values and sets the error flags to true. For more information about error flags and runtime errors, see the TriStation 1131 Libraries Reference. Application Notes • Can be used in Safety or Control applications. Safety Considerations Guide for Triconex General Purpose v2 Systems
SYS_CRITICAL_IO 83 Library Trident and Tri-GP (TRDLIB) Structured Text FUNCTION_BLOCK SYS_CRITICAL_IO VAR_INPUT CI : BOOL := TRUE ; (* Control in. *) RESET : BOOL ; (* Reset *) IOP : DINT ; (* IOP number 0-15 *) SLOT : DINT ; (* SLOT number 0-56 *) APP : DINT ; (* Application number 1-2 *) RELAY_OK : BOOL := TRUE ; (* Relay is energized and not stuck. *) END_VAR VAR_OUTPUT CO : BOOL ; (* Critical IO Control out. *) TMR : BOOL ; (* Critical IO 3 channels operating. *) GE_DUAL : BOOL ; (* Critical IO 2 or more channels operating. *) GE_SINGLE : BOOL ; (* Critical IO 1 or more channels operating. *) NO_VOTER_FLTS : BOOL ; (* No voter faults on critical modules. *) ERROR : DINT ; (* Error number. *) (* * Error number: * 0 = No error. * -1 = IOP invalid. * -2 = Slot not valid. * -3 = Module not configured. * -4 = Wrong module type. * -5 = Application number is invalid. * -6 = Not initialized. *) END_VAR VAR PREVIOUS_RESET : BOOL ; (* All channels operating. *) IO : SYS_IO_STATUS ; (* IO module status. *) RELAY : DINT := 1 ; (* De-energized to trip with relay *) DE_ENERGIZED : DINT := 2 ; (* De-energized to trip with no relay *) U : BOOL ; (* Unused value. *) END_VAR (* *=F=============================================================================== * FUNCTION_BLOCK: SYS_CRITICAL_IO * Purpose: Calculate status of critical IO modules. * * Return: none * * Remarks: * Usage * 1. Invoke once with RESET := TRUE, to initialize. * 2. Invoke again with RESET := FALSE, CI := TRUE, APP := DE_ENERGIZED, and * RELAY_OK := FALSE to complete initialization. * 3. Invoke repeatedly, once for each critical IO module. * 4. Read outputs CO, TMR, GE_DUAL, and GE_SINGLE for safety critical results. * * In step 3, invoke with the IOP and SLOT of the critical IO module, * the module application, and the relay status. * For example, if IOP 1 SLOT 1 is a critical DO module with a relay, * and SCIO is the function block instance name: * SCIO( IOP:=1, SLOT:= 1, APP:=RELAY, RELAY_OK:=RELAY1_OK ); * Safety Considerations Guide for Triconex General Purpose v2 Systems
Page 1 and 2:
Triconex General Purpose v2 Systems
Page 3 and 4:
Contents Preface vii Summary of Sec
Page 5 and 6:
Contents v Partitioned Processes. .
Page 7 and 8:
Preface This guide provides informa
Page 9 and 10:
Preface ix • All other requests a
Page 11 and 12:
1 Safety Concepts Overview 2 Hazard
Page 13 and 14:
Overview 3 Protection Layers Method
Page 15 and 16:
Hazard and Risk Analysis 5 Hazard a
Page 17 and 18:
Hazard and Risk Analysis 7 Sample S
Page 19 and 20:
Hazard and Risk Analysis 9 Safety L
Page 21 and 22:
Hazard and Risk Analysis 11 • Eac
Page 23 and 24:
Safety Standards 13 CAN/CSA-C22.2 N
Page 25 and 26:
2 Application Guidelines Overview 1
Page 27 and 28:
General Guidelines 17 General Guide
Page 29 and 30:
Guidelines for Triconex Controllers
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42: 3 Fault Management Overview 32 Syst
Page 43 and 44: System Diagnostics 33 System Diagno
Page 45 and 46: Operating Modes 35 Operating Modes
Page 47 and 48: Module Diagnostics 37 Analog Output
Page 49 and 50: Module Diagnostics 39 Calculation f
Page 51 and 52: Module Diagnostics 41 External Comm
Page 53 and 54: 4 Application Development Developme
Page 55 and 56: Development Guidelines 45 Array Ind
Page 57 and 58: Setting Scan Time 47 application. T
Page 59 and 60: Sample Safety-Shutdown Programs 49
Page 69 and 70: Alarm Usage 59 Alarm Usage To imple
Page 71 and 72: A Triconex Peer-to-Peer Communicati
Page 73 and 74: Data Transfer Time 63 Data Transfer
Page 75 and 76: Data Transfer Time 65 A typical dat
Page 77 and 78: Examples of Peer-to-Peer Applicatio
Page 79 and 80: B HART Communication Overview 70 HA
Page 81 and 82: HART Position Paper from TÜV Rhein
Page 89 and 90: C Safety-Critical Function Blocks O
Page 91: SYS_CRITICAL_IO 81 SYS_CRITICAL_IO
Page 95 and 96: SYS_CRITICAL_IO 85 END_IF ; PREVIOU
Page 97 and 98: SYS_SHUTDOWN 87 Output Parameters (
Page 99 and 100: SYS_SHUTDOWN 89 * the safety system
Page 101 and 102: SYS_SHUTDOWN 91 ALARM_DISABLED_POIN
Page 103 and 104: SYS_VOTE_MODE 93 Example For shutdo
Page 105 and 106: Index A abbreviations, list of viii
Page 107 and 108: Index 97 N NFPA 85 12 O operating m
Page 110: Invensys Operations Management 5601
show all

Safety Considerations Guide for Triconex General ... - ICEWeb

Create successful ePaper yourself

Delete template?

Save as template?