Appendix B

Appendix B Triconex OPC Server 1 Internal



Triconex OPC Server Contents of This Appendix Triconex OPC Server Overview ......................................................4 Configuring the OPC Server...............................................................4 Redundant Configuration .................................................................5 Adjusting System Time ....................................................................5 Other OPC Products ...........................................................................5 OPC Data Manager .........................................................................5 OPC Redundancy Broker ................................................................5 Lab 1 : Configuring the OPC Server ...............................................7 Introduction .........................................................................................7 Objective ..............................................................................................7 Lab Procedure .....................................................................................7 Configure the OPC Server ...............................................................7 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 3 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Triconex OPC Server Triconex OPC Server Overview The Triconex OPC Server is a Windows application that allows OPC clients to have read- and-write access to Triconex program variables. OPC stands for OLE for Process Control, which is a standard set of non-proprietary interfaces used to develop client/server programs. The OPC Server workstation must be connected to an Ethernet port on a Triconex controller. For Tri-GP, the Net1 or Net2 port on the Communication Module must be used. OPC Server is configured by exporting an XML configuration file from a TriStation project and opening that file in OPC Server. After OPC Server is configured, an OPC client can send request to OPC Server to get data from a Triconex controller., Figure 1. Figure 1 – Triconex OPC Server You can include TriStation configurations for multiple networked controllers in one XML file by using the same file name when exporting each configuration. The information from each TriStation configuration is appended to the file. In OPC Server, you can edit the properties of aliases and tagnames and other aspects of the configuration. If you change the name of the configuration or alias, a new entry is created in the XML configuration file. If you change properties related to the entry, but do not change the configuration or alias name, those properties are changed for the entry. The Triconex OPC Server is available from Triconex and Matrikon. For more information about Triconex OPC Server and OPC client applications, see the Matrikon web site at www.matrikon.com. Configuring the OPC Server use the labs’ procedures to configure the OPC Server with alias information from a TriStation project. With TriStation 1131 3.1 and later, alias information can be exported to an XML file, and then imported to the OPC Server. To use OPC Server with TriStation versions earlier than 3.1, alias information must be manually entered to the OPC Server. 4 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Triconex OPC Server Redundant Configuration OPC Server can be configured for dual redundancy by using two OPC Server workstations. Each workstation must include two Ethernet adapter cards, which must be connected to a Triconex communication module on the primary network and a Triconex communication module on the redundant network. You must specify the properties of the redundant Triconex communication modules on the OPC Server Configuration window. Adjusting System Time An OPC client can use the Device Clock tagname to read or write the system time of a Triconex controller. The Device Clock tagname is derived from Triconex status information in the OPC Server Configuration. For more information, see the documentation for the OPC client software. Before you use the Device Clock tagname to adjust the system time of a Triconex controller, you must configure the TriStation project to allow writes by external devices on an open network. Other OPC Products For OPC Server users, two additional OPC products are available from Triconex and Matrikon: the OPC Data Manager and the OPC Redundancy Broker. OPC Data Manager The OPC Data Manager (ODM) is an application that transfers data from one OPC server to another. ODM is useful for sharing data between two or more control systems such as a Triconex controller and Foxboro™ Distributed Control System (DCS). Traditional OPC- enabled systems share data by implementing one application as an OPC client, and another as an OPC server. If two applications are servers instead of clients, they cannot exchange data. ODM solves this problem by acting as a double- headed or thin OPC client to both servers. It requests data from one OPC server and immediately sends it to the other OPC server. ODM includes these features: • Support for both COM and DCOM architectures. • Support for DDE and OPC message protocols. • Operation as a Windows service or a normal application. • Real-time data monitoring. • Extensive error tracking and management. For more information, see the Matrikon OPC Data Manager User’s Manual. OPC Redundancy Broker The OPC Redundancy Broker (ORB) is a messaging application designed for systems that must use redundant devices to ensure high reliability. ORB constantly monitors the primary OPC server and redirects communication to the standby OPC server when a failure is detected. ORB can integrate with any OPC compliant client/server configuration and can be retrofitted to existing configurations. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 5 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Triconex OPC Server ORB includes these features: • Intuitive configuration and monitoring features. • Choice of hot, cold, or warm fail-over for each OPC Server. • Automatic fail-over notification by e-mail, fax, log file, or pager. • Extensive error tracking and diagnostic capabilities. For more information, see the Matrikon OPC Redundancy Broker User’s Manual. 6 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Triconex OPC Server Lab 1 : Configuring the OPC Server Introduction This lab explains how to configure the OPC Server with alias information from a TriStation project. With TriStation 1131 v3.1 and later, alias information can be exported to an XML file and then imported to the OPC Server. To use OPC Server with TriStation versions earlier than v3.1, alias information must be manually entered to the OPC Server. Objective After completing this lab, you will be able to configure the OPC Server. Lab Procedure Configure the OPC Server 1. In TriStation, assign all aliases to be accessed by OPC Server. 2. To allow an OPC client to change the values of Triconex variables, you must enable write access in the TriStation application. 3. In TriStation, complete the project and download it to the controller. 4. Export the XML configuration file by exporting the tagnames (points). 5. Click the file type, such as Matrikon OPC XML Data Files(*.XML). Name the file using the XML extension, using a maximum of eight characters. If you include multiple configurations, use the same file name each time you use the export command. 6. If not already done, install OPC Server and start it. When OPC Server is loaded, a gray Triconex icon is displayed on the status bar. 7. To open the XML configuration file, right-click the Triconex icon from the status bar, and then click Configure. 8. The OPC Server for Triconex PLCs window is displayed. 9. On the File menu, click Open, and then click the .xml file you exported from TriStation. As the file loads, statistics are displayed. When finished, you can display Server Configuration and Alias configuration information. 10. To display Server Configuration information, click a node from the Current Configuration pane. This window shows the Server Configuration information. You can make changes to these properties by entering the changes and clicking Apply. 11. Under ProtocolSettings, specify the TCP/IP Address and the other properties of the Triconex communication module on tab 1. If the controller includes two communication modules, specify the properties of the left module and the right module on tabs 1 and 2. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 7 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Triconex OPC Server Note: Do not use tabs 3 through 7. 12. To display alias information, select a node under Alias Configuration in the Current Configuration pane. 13. To make changes to an alias, double-click the alias row. The Edit Alias window appears, as shown in the following figure. 8 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Triconex OPC Server 14. Repeat steps 8 to 11 for each node configuration included in the XML file. 15. If you made changes to any of the configurations and want to keep them save the configuration file. 16. To use OPC Server to get data from a Triconex controller, install an OPC client application. (Matrikon sells OPC client applications.) 17. In the OPC client application, you can specify the tagnames or aliases of the data to be accessed. A sample tagname is DO_02, as shown in the previous figure. 18. The location of the data is described as node: bin: offset in the Item Path column for the Alias Configuration. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 9 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal



Triconex OPC Server Action Plan List skills you learned in this course that you can use on the job. 1. ______________________________________________________________________ 2. ______________________________________________________________________ 3. ______________________________________________________________________ 4. ______________________________________________________________________ 5. ______________________________________________________________________ 6. ______________________________________________________________________ 7. ______________________________________________________________________ 8. ______________________________________________________________________ 9. ______________________________________________________________________ 10. _____________________________________________________________________ 11. _______________________________ ______________________________________ 12. _____________________________________________________________________ 13. _____________________________________________________________________ 14. _____________________________________________________________________ 15. _____________________________________________________________________ 16. _____________________________________________________________________ 17. _____________________________________________________________________ 18. _____________________________________________________________________ 19. _____________________________________________________________________ 20. _____________________________________________________________________ 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 9 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal



Triconex OPC Server 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 9 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal