Safety Considerations Guide for Trident v2 Systems - TUV ...

More documents

Recommendations

Info

70 Appendix A Triconex Peer-to-Peer Communication This example packs 32 BOOL values into a DWORD and sends the DWORD and a diagnostic variable to a receiving node as fast as possible by setting the sendflag parameter to 1 all the time. The diagnostic variable is incremented every time a new SEND is initiated. The receiving node checks the diagnostic variable to verify that it has changed from the previous value received. The receiving node also determines whether it has received at least one data transfer within the process-tolerance time. If not, the application takes appropriate action, such as using the last data received or using default data to make safety-critical decisions. This example uses the following project elements: • PEER_EX4_SEND_FBD (for sending Node #1) • PEER_EX4_RCV_FBD (for receiving Node #3) Safety Considerations Guide for Trident v2 Systems
B HART Communication Overview 72 HART Position Paper from TÜV Rheinland 72 Safety Considerations Guide for Trident v2 Systems
Page 1 and 2:
Trident v2 Systems Safety Considera
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:
• All other requests are handled
Page 11 and 12:
1 Safety Concepts Overview 2 Hazard
Page 13 and 14:
Protection Layers Methods that prov
Page 15 and 16:
Hazard and Risk Analysis Hazard and
Page 17 and 18:
Sample SIL Calculation Hazard and R
Page 19 and 20:
Safety Life Cycle Model Hazard and
Page 21 and 22:
Hazard and Risk Analysis 11 • Eac
Page 23 and 24:
CAN/CSA-C22.2 No. 61010-1-04 Safety
Page 25 and 26:
2 Application Guidelines Overview 1
Page 27 and 28:
General Guidelines This section des
Page 29 and 30: General Guidelines 19 Safety Measur
Page 31 and 32: Emergency Shutdown Systems The safe
Page 33 and 34: Safety-Shutdown Guidelines for Tric
Page 35 and 36: Guidelines for Triconex Controllers
Page 43 and 44: 3 Fault Management Overview 34 Syst
Page 45 and 46: System Diagnostics System Diagnosti
Page 47 and 48: Operating Modes Each input or outpu
Page 49 and 50: Analog Output (AO) Modules Module D
Page 51 and 52: Calculation for Diagnostic Fault Re
Page 53 and 54: External Communication Module Diagn
Page 55 and 56: 4 Application Development Developme
Page 57 and 58: Array Index Errors Infinite Loops D
Page 59 and 60: Setting Scan Time 49 application. T
Page 61 and 62: Sample Safety-Shutdown Programs Sam
Page 63 and 64: Sample Safety-Shutdown Programs 53
Page 65 and 66: When Some I/O Modules Are Safety-Cr
Page 67 and 68: Sample Safety-Shutdown Programs 57
Page 69 and 70: Partitioned Processes Sample Safety
Page 71 and 72: Alarm Usage Alarm Usage 61 To imple
Page 73 and 74: A Triconex Peer-to-Peer Communicati
Page 75 and 76: Data Transfer Time Data Transfer Ti
Page 77 and 78: Data Transfer Time 67 A typical dat
Page 79: Examples of Peer-to-Peer Applicatio
Page 83 and 84: 2008-04-01 Automation, Software and
Page 85 and 86: 2008-04-01 HART Position Paper from
Page 87 and 88: 2008-04-01 A possible impact to the
Page 89 and 90: 2008-04-01 HART Position Paper from
Page 91 and 92: C Safety-Critical Function Blocks O
Page 93 and 94: SYS_CRITICAL_IO Accumulates the sta
Page 95 and 96: Library Trident and Tri-GP (TRDLIB)
Page 97 and 98: END_IF ; PREVIOUS_RESET := RESET ;
Page 99 and 100: Output Parameters (continued) Name
Page 101 and 102: SYS_SHUTDOWN 91 * the safety system
Page 103 and 104: ALARM_DISABLED_POINTS := MPX.POINTS
Page 105 and 106: Example For shutdown examples, see
Page 107 and 108: A abbreviations, list of viii actua
Page 109 and 110: message errors, external communicat
Page 112: Invensys Operations Management 5601
show all

Safety Considerations Guide for Trident v2 Systems - TUV ...

Create successful ePaper yourself

Delete template?

Save as template?