Safety Considerations Guide for Triconex General ... - ICEWeb

More documents

Recommendations

Info

62 Appendix A Triconex Peer-to-Peer Communication Overview Triconex Peer-to-Peer protocol is designed to allow multiple Triconex controllers in a closed network to exchange safety-critical data. (If you plan to implement a complex Peer-to-Peer network, please contact the Invensys Global Customer Support (GCS) center.) To enable Peerto-Peer communication, you must connect each controller (also referred to as a node) to an Ethernet network by means of port on the. The controllers exchange data by using Send and Receive function blocks in their TriStation 1131 applications. Peer-to-Peer Network CM CM MP M M M P P P ABC N N C C MM 1 2 MP Tri-GP Controller Tricon Controller Trident Controller Figure 13 Basic Triconex Peer-to-Peer Network To configure a TriStation 1131 application for Peer-to-Peer communication, you must do the following tasks: • Configure the physical port connection for Peer-to-Peer mode • Allocate memory for Send and Receive function blocks • Add Send and Receive function blocks to your programs • Observe restrictions on data transmission speed In addition, Triconex recommends that you calculate the data transfer time to determine whether your control algorithms will operate correctly. Instructions for performing this calculation are provided on page 63. The sample programs described in this appendix can be found in the Tdpeer.pt2 project included as part of the TriStation 1131 software installation. These programs show how to send data at high speed and under controlled conditions. For more detailed information on Triconex Peer-to-Peer communication, please refer to the Communication Guide for Triconex General Purpose v2 Systems. Safety Considerations Guide for Triconex General Purpose v2 Systems
Data Transfer Time 63 Data Transfer Time In a Peer-to-Peer application, data transfer time includes the time required to initiate a send operation, send the message over the network, and have the message read by the receiving node. Additional time (at least two scans) is required for a sending node to get an acknowledgment from the MPs that the message has been acted on. These time periods are a function of the following parameters of the sending and receiving controllers: • Scan time • Configuration size • Number of bytes for aliased variables • Number of SEND function blocks, RECEIVE function blocks, printing function blocks, and Modbus master function blocks • Number of controllers (nodes) on the Peer-to-Peer network Send function blocks require multiple scans to transfer data from the sending controller to the receiving controller. The number of send operations initiated in a scan is limited to 5. The number of pending send operations is limited to 10. Estimating Memory for Peer-to-Peer Data Transfer Time This procedure explains how to estimate memory for Peer-to-Peer data transfer time between a pair of Triconex controllers (nodes). The more memory allocated for aliased points the slower the transfer time. Procedure 1 In the TriStation 1131 software, on the sending controller, expand the Controller tree, and double-click Configuration. On the Configuration tree, click Memory Allocation. 2 Find the bytes allocated for BOOL, DINT, and REAL points by doing this: • On the Configuration tree, click Memory Points, Input Points, or Output Points. Double-click the graphic for the point type. • Add the number of bytes allocated for all BOOL input, output, and aliased memory points. Enter the number on step 1 of the following worksheet. Enter the number for DINT and REAL points on step 1. 3 On the receiving controller, get the BOOL, DINT, and REAL points and enter the numbers on step 3 of the Data Transfer Time worksheet. Estimating the Data Transfer Time The basic formula for estimating the data transfer time is as follows: • Data transfer time in milliseconds = 2 * (larger of TS or SS) + 2 * (larger of TR or SR) 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 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: A Triconex Peer-to-Peer Communicati
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 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
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?