Safety Considerations Guide for Triconex General ... - ICEWeb
Safety Considerations Guide for Triconex General ... - ICEWeb Safety Considerations Guide for Triconex General ... - ICEWeb
36 Chapter 3 Fault Management Also, during each execution of the control application, each channel independently verifies the: • Integrity of the data path between the MPs • Proper voting of all input values • Proper evaluation of the control application • Calculated value of each output point Module Diagnostics Each system component detects and reports operational faults. Analog Input (AI) Modules Analog input module points useforce-to-value diagnostics (FVD). Under system control, each point is sequentially forced to a test value. The forced value is maintained until the value is detected by the system or a time-out occurs. Using the integral FVD capability, each point can be independently verified for its ability to accurately detect a transition to a different value, typically every 500 milliseconds. (For more information on fault reporting time, see Calculation for Diagnostic Fault Reporting Time on page 39.) Using these diagnostics, each channel can be verified independently, thus assuring near 100 percent fault coverage and fail-safe operation under all single-fault scenarios, and most common multiple-fault scenarios. Analog Input Module Alarms Analog input module faults are reported to the control application. These alarms can be used to increase availability during specific multiple-fault conditions. Loss of field power or logic power is reported to the control application. Analog Input/Digital Input (AI/DI) Modules Analog input/digital input module points useforce-to-value diagnostics (FVD). Under system control, each point is sequentially forced to a test value. The forced value is maintained until the value is detected by the system or a time-out occurs. Using the integral FVD capability, each point can be independently verified for its ability to accurately detect a transition to a different value, typically every 500 milliseconds. (For more information on fault reporting time, see Calculation for Diagnostic Fault Reporting Time on page 39.) Using these diagnostics, each channel can be verified independently, thus assuring near 100 percent fault coverage and failsafe operation under all single-fault scenarios, and most common multiple-fault scenarios. Analog Input/Digital Input Module Alarms Analog input/digital input module faults are reported to the control application. These alarms can be used to increase availability during specific multiple-fault conditions. Loss of field power or logic power is reported to the control application. Safety Considerations Guide for Triconex General Purpose v2 Systems
Module Diagnostics 37 Analog Output (AO) Modules Analog output modules use a combination of comparison and reference diagnostics. Under system control, each channel is given control of the output sequentially using the 2oo3 voting mechanism. Each channel independently measures the actual state of an output value by comparing it with the commanded value. If the values do not match, a channel switch is forced by voting another channel. Each channel also compares its measured values against internal references. Using these diagnostics, each channel can be independently verified for its ability to control the analog output value, thus assuring nearly 100 percent fault coverage and fail-safe operation under all single-fault scenarios, and most common multiple-fault scenarios. Analog Output Module Alarms Analog output module faults are reported to the control application. These alarms can be used to increase availability during specific multiple-fault conditions. Loss of field power or logic power is reported to the control application. Digital Input (DI) Modules Digital input module pointsuse force-to-value diagnostics (FVD). Under system control, each pointis sequentially forced to a test value. The forced value is maintained until the value is detected by the system or a time-out occurs. Using the integral FVD capability, each point can be independently verified for its ability to accurately detect a transition to the opposite state, typically every 500 milliseconds. (For more information on fault reporting time, see Calculation for Diagnostic Fault Reporting Time on page 39.) These diagnostics are executed independently by each channel, thus assuring nearly 100 percent fault coverage and fail-safe operation under all single-fault scenarios, and most common multiple-fault scenarios. Digital Input Module Alarms Digital input module faults are reported to the control application. These alarms can be used to increase availability during specific multiple-fault conditions. Loss offield power or logic power is reported to the control application. Digital Output (DO) Modules Digital output modules use output voter diagnostics (OVD). Under system control, each output point is commanded sequentially to both the energized and de-energized states. The forced state is maintained until the value is detected by the system or a time-out occurs (500 microseconds, typical case; 2 milliseconds, worst case). Using the integral OVD capability, each point can be independently verified for its ability to a transition to either state, typically every 500 milliseconds. (For more information on fault reporting time, see Calculation for Diagnostic Fault Reporting Time on page 39.) 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: Guidelines for Triconex Controllers
- Page 33 and 34: Guidelines for Triconex Controllers
- Page 35 and 36: Guidelines for Triconex Controllers
- Page 37 and 38: Guidelines for Triconex Controllers
- Page 39 and 40: Guidelines for Triconex Controllers
- Page 41 and 42: 3 Fault Management Overview 32 Syst
- Page 43 and 44: System Diagnostics 33 System Diagno
- Page 45: Operating Modes 35 Operating Modes
- 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 61 and 62: Sample Safety-Shutdown Programs 51
- Page 63 and 64: Sample Safety-Shutdown Programs 53
- Page 65 and 66: Sample Safety-Shutdown Programs 55
- Page 67 and 68: Sample Safety-Shutdown Programs 57
- 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 83 and 84: HART Position Paper from TÜV Rhein
- Page 85 and 86: HART Position Paper from TÜV Rhein
- Page 87 and 88: HART Position Paper from TÜV Rhein
- Page 89 and 90: C Safety-Critical Function Blocks O
- Page 91 and 92: SYS_CRITICAL_IO 81 SYS_CRITICAL_IO
- Page 93 and 94: SYS_CRITICAL_IO 83 Library Trident
- Page 95 and 96: SYS_CRITICAL_IO 85 END_IF ; PREVIOU
36 Chapter 3 Fault Management<br />
Also, during each execution of the control application, each channel independently verifies the:<br />
• Integrity of the data path between the MPs<br />
• Proper voting of all input values<br />
• Proper evaluation of the control application<br />
• Calculated value of each output point<br />
Module Diagnostics<br />
Each system component detects and reports operational faults.<br />
Analog Input (AI) Modules<br />
Analog input module points use<strong>for</strong>ce-to-value diagnostics (FVD). Under system control, each<br />
point is sequentially <strong>for</strong>ced to a test value. The <strong>for</strong>ced value is maintained until the value is<br />
detected by the system or a time-out occurs. Using the integral FVD capability, each point can<br />
be independently verified <strong>for</strong> its ability to accurately detect a transition to a different value,<br />
typically every 500 milliseconds. (For more in<strong>for</strong>mation on fault reporting time, see Calculation<br />
<strong>for</strong> Diagnostic Fault Reporting Time on page 39.) Using these diagnostics, each channel can be<br />
verified independently, thus assuring near 100 percent fault coverage and fail-safe operation<br />
under all single-fault scenarios, and most common multiple-fault scenarios.<br />
Analog Input Module Alarms<br />
Analog input module faults are reported to the control application. These alarms can be used to<br />
increase availability during specific multiple-fault conditions. Loss of field power or logic<br />
power is reported to the control application.<br />
Analog Input/Digital Input (AI/DI) Modules<br />
Analog input/digital input module points use<strong>for</strong>ce-to-value diagnostics (FVD). Under system<br />
control, each point is sequentially <strong>for</strong>ced to a test value. The <strong>for</strong>ced value is maintained until the<br />
value is detected by the system or a time-out occurs. Using the integral FVD capability, each<br />
point can be independently verified <strong>for</strong> its ability to accurately detect a transition to a different<br />
value, typically every 500 milliseconds. (For more in<strong>for</strong>mation on fault reporting time, see<br />
Calculation <strong>for</strong> Diagnostic Fault Reporting Time on page 39.) Using these diagnostics, each<br />
channel can be verified independently, thus assuring near 100 percent fault coverage and failsafe<br />
operation under all single-fault scenarios, and most common multiple-fault scenarios.<br />
Analog Input/Digital Input Module Alarms<br />
Analog input/digital input module faults are reported to the control application. These alarms<br />
can be used to increase availability during specific multiple-fault conditions. Loss of field power<br />
or logic power is reported to the control application.<br />
<strong>Safety</strong> <strong>Considerations</strong> <strong>Guide</strong> <strong>for</strong> <strong>Triconex</strong> <strong>General</strong> Purpose v2 Systems
Change language