Safety Considerations Guide for Triconex General ... - ICEWeb
Safety Considerations Guide for Triconex General ... - ICEWeb Safety Considerations Guide for Triconex General ... - ICEWeb
42 Chapter 3 Fault Management CM System Attributes Table 8 Module and Port Status Attribute Name Description CM.SLOT.BAD_MSGS_PORT_N Number of bad messages received CM.SLOT.BRDCSTS_PORT_N Number of broadcast messages received CM.SLOT.ELAPSED_PORT_N Milliseconds since last message was received CM.SLOT.MSGS_PORT_N Number of messages received CM.SLOT.NET1_OK NET1 Ethernet port is receiving messages CM.SLOT.NET2_OK NET2 Ethernet port is receiving messages CM.SLOT.RESET_STATS_PORT_N Resets statistics for a serial port CM.SLOT.RSPNS_PORT_N Number of response messages sent CM.SLOT.STATS_RESET_PORT_N Responds that the statistics were reset For more information about communication alarms, see the following manuals: • TriStation 1131 Developer’s Guide • Planning and Installation Guide for Triconex General Purpose v2 Systems • Communication Guide for Triconex General Purpose v2 Systems • TriStation 1131 Libraries Reference Safety Considerations Guide for Triconex General Purpose v2 Systems
4 Application Development Development Guidelines 44 Important TriStation 1131 Software Commands 46 Setting Scan Time 47 Sample Safety-Shutdown Programs 49 Alarm Usage 59 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 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: Module Diagnostics 41 External Comm
- 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
- 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
42 Chapter 3 Fault Management<br />
CM System Attributes<br />
Table 8 Module and Port Status<br />
Attribute Name<br />
Description<br />
CM.SLOT.BAD_MSGS_PORT_N Number of bad messages received<br />
CM.SLOT.BRDCSTS_PORT_N Number of broadcast messages received<br />
CM.SLOT.ELAPSED_PORT_N Milliseconds since last message was received<br />
CM.SLOT.MSGS_PORT_N<br />
Number of messages received<br />
CM.SLOT.NET1_OK<br />
NET1 Ethernet port is receiving messages<br />
CM.SLOT.NET2_OK<br />
NET2 Ethernet port is receiving messages<br />
CM.SLOT.RESET_STATS_PORT_N Resets statistics <strong>for</strong> a serial port<br />
CM.SLOT.RSPNS_PORT_N<br />
Number of response messages sent<br />
CM.SLOT.STATS_RESET_PORT_N Responds that the statistics were reset<br />
For more in<strong>for</strong>mation about communication alarms, see the following manuals:<br />
• TriStation 1131 Developer’s <strong>Guide</strong><br />
• Planning and Installation <strong>Guide</strong> <strong>for</strong> <strong>Triconex</strong> <strong>General</strong> Purpose v2 Systems<br />
• Communication <strong>Guide</strong> <strong>for</strong> <strong>Triconex</strong> <strong>General</strong> Purpose v2 Systems<br />
• TriStation 1131 Libraries Reference<br />
<strong>Safety</strong> <strong>Considerations</strong> <strong>Guide</strong> <strong>for</strong> <strong>Triconex</strong> <strong>General</strong> Purpose v2 Systems
Change language