Appendix F

Appendix F Schneider Electric Control HMI Viewer 1 Internal



Appendix Contents of This Appendix Dynamic Data Exchange..................................................................5 Wonderware SuiteLink........................................................................5 Control HMI I/O Addressing ............................................................7 Control HMI Access Names.............................................................8 Lab 1: Configuring Control HMI Access Names ...........................9 Introduction .........................................................................................9 Objectives ............................................................................................9 Lab Procedure .....................................................................................9 Create an Access Name ..................................................................9 Modify or Delete an Access Name.................................................11 Define I/O Item in Control HMI .......................................................12 Define I/O Type Tagname..............................................................12 Lab 2: Defining an I/O Item in Control HMI ................................. 13 Introduction .......................................................................................13 Objectives ..........................................................................................13 Lab Procedure ...................................................................................13 Define an I/O Tagname..................................................................13 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation 3 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix 4 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix Dynamic Data Exchange Dynamic Data Exchange (DDE) is a communication protocol developed by Microsoft® to allow applications in the Windows environment to send/receive data and instructions to/from each other. It implements a client-server relationship between two concurrently running applications. The server application provides the data and accepts requests from any other application interested in its data. Requesting applications are named clients. Some applications, such as InTouch® and Microsoft Excel® spreadsheet can simultaneously be both a client and a server. Note: NetDDE, used for network communication to non-Wonderware I/O sources, is supported on Windows® XP and Windows® 2000 operating systems, but not on Windows 2003 Server. For more information about NetDDE, refer to the InTouch User documents. Wonderware SuiteLink Wonderware SuiteLink™ uses a TCP/IP-based protocol. SuiteLink is designed specifically to meet industrial needs, such as data integrity, high-throughput, and easier diagnostics. This protocol standard is supported for both Windows 2000 and Windows XP. SuiteLink is not a replacement for DDE. Wonderware recommends that DDE be used for internal client communication, and SuiteLink for communication over the network. Each connection between a client and a server depends on your network situation. SuiteLink provides the following benefits: • Consistent high data volumes can be maintained between applications, regardless of whether the applications are on a single node or distributed over a large node count • Value Time Quality (VTQ) places a time stamp and quality indicator on all data values delivered to VTQ-aware clients • Extensive diagnostics of the data throughput, server loading, computer resource consumption, and network transport are made accessible through the Windows NT® operating system performance monitor. This feature is critical for the scheme and maintenance of distributed industrial networks. • The network transport protocol is TCP/IP using the standard Winsock interface of Microsoft 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation 5 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix To use the SuiteLink Communication Protocol, the following conditions must be satisfied: • You must have Microsoft TCP/IP configured and working properly • You must use computer names (Node Names) of no more than 15 characters Note: For more information on installing and configuring Microsoft TCP/IP, refer to the documentation of Windows operating system. • Wonderware SuiteLink must be running as a service. If for some reason SuiteLink has been stopped, you will need to start it again. (SuiteLink is automatically installed as a Common Component when you install Control HMI Viewer. It is configured to startup automatically as a Windows Service) 6 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix Control HMI I/O Addressing Control HMI identifies an element of data in an I/O Server program by using a three-part naming convention that includes the application name, topic name and item name. To obtain data from another application, the client program (Control HMI) opens a channel to the server program by specifying these three items. For Control HMI to acquire a data value from another application, it must also know the name of the application providing the data value, the name of the topic within the application that contains the data value, and the name of the specific item within the topic. In addition, Control HMI needs to know the data's type: discrete, integer, real (floating point), or message (string). This information determines the I/O type for the gagman when it is defined in the Control HMI database. When WindowViewer is running, it will automatically perform all required actions to acquire and maintain the value of this item. For example, in the case of Excel, the application name is Excel, the topic name is the name of the specific spreadsheet that contains the data. The item name is the identification of the cell on the spreadsheet to/from which the data is to be read/written. When another Windows application requests a data value from Control HMI, it also must know the three I/O address items. The following describes the I/O address convention for Control HMI: • VIEW (application name) identifies the Control HMI runtime program that contains the data element • TAGNAME (topic name) is the word always used when reading/writing to a tagname in the Control HMI database • ActualTagname (item name) is the actual tagname defined for the item in the Control HMI Tagname Dictionary For example, to access a data value in Control HMI from Excel spreadsheet (running on the same node), a DDE Remote Reference formula would be entered in the cell into which the data value is to be written: =VIEW|TAGNAME!'ActualTagname' 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation 7 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Control HMI Access Names When you create I/O-type tags or remote tagname references, they must be associated with an Access Name. Access Names contain the information that is used to communicate with other I/O data sources including the node name, application name, and topic name. 8 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix Lab 1: Configuring Control HMI Access Names Introduction When you create I/O-type tags or remote tagname references, they must be associated with an access name. access names contain the information that is used to communicate with other I/O data sources including the node name, application name, and topic name. Objectives After completing this lab, you can: • Create an access name • Modify or delete an access name Lab Procedure Create an Access Name The Access Name configured in the following steps is used in the subsequent lab. 1. Expand the Configure menu in the Application Explorer. 2. Right-click Access Names and click Open. Note: Access names can also be created while you are defining an I/O-type tag in the Tagname Dictionary. The Access Names dialog box appears. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation 9 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix 3. Click Add. The Add Access Name dialog box appears. 4. In the Add Access Name dialog box, in the Access Name field, enter the new Access Name. Note: For simplicity, use the same name that you will use for the topic name. 5. Use the Node Name property when the data is from a remote I/O Server over the network. 6. In the Application Name field, enter the actual program name for the I/O Server program from which the data value will be acquired. Note: If the value is coming from a Wonderware Modbus I/O Server, MODBUS is used. Do not enter the .exe extension portion of the program name. 7. In the Topic Name field, enter the topic name to access. Note: In the case of data coming from a Wonderware I/O Server program, the topic name must be the exact same name given to the spreadsheet when it was saved. For example, Book1.xls. 8. In the Which Protocol to use area, select DDE (internal) or SuiteLink (network). 9. In the When to advise server area, select either of the following options: • Click Advise all items if the server program is to poll for all data whether or not it is in visible windows, alarmed, logged, trended, or used in a script. This option will impact performance and is not recommended • Click Advise only active items if the server program is to poll only points in visible windows and points that are alarmed, logged, trended, or used in any script. A Touch Pushbuttons action script will not be polled unless it opens in a visible window. Figure 1 shows an example of a completed access name (if the I/O server is on the local node, the Node Name: can be left blank as shown in Figure 1): Figure 1 10 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix 10. Click OK to accept the new access name. 11. Click Close to close the dialog box. Modify or Delete an Access Name 12. Right-click Access Names or Open. The Access Names dialog box appears. 13. Click the access name to modify. 14. Click Modify. The Modify Access Name dialog box appears. 15. Make any changes (the following figure shows the Node Name that has been added) and click OK. 16. Repeat the previous process if you need to modify other access names. 17. To delete an Access Name, click it in the list and click Delete. A message box appears asking you to confirm the deletion. 18. Click Yes. 19. Click Close or repeat the previous procedure to delete other defined Access Names. Note: Access Names used by tags cannot be deleted. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation 11 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Define I/O Item in Control HMI Control HMI can receive data from other local or remote Windows applications when I/O- type tags are defined in the Tagname Dictionary. Each I/O-type tag references a valid item in the I/O Server program. Define I/O Type Tagname All I/O type tags receive their values from other Windows application programs such as Excel and I/O Servers. This value is referred to as the raw value. When you define a tag in the Tagname Dictionary, you must enter values for the Min and Max Raw. These values are used by the database as clamps on the actual raw value received from the I/O device. For example, if you set the Min Raw value to 50 and the actual value received from an I/O Server is 0, the database will force the Raw value to 50. Control HMI does not display raw values. Instead, it displays engineering units (EU). When you define an I/O type tag in the Tagname Dictionary, you must specify values for the Min- and Max EU. These values are used to scale the raw value to the displayed value. If you do not want to do scaling or your I/O device does the scaling for you, set the Min/Max EU values equal to the Min/ Max Raw values. For example, assume that a flow transmitter wired to a PLC register generates a value of zero at no flow and a value of 9999 at 100% flow. The following values would be entered: Min EU = 0 Max EU = 100 Min Raw=0 Max Raw = 9999 A raw value of 5000 would be displayed as 50. Assume that a flow transmitter wired to a PLC register generates a value of 6400 at no flow and a value of 32000 at 300 GPM. Min EU = 0 Max EU = 300 Min Raw = 6400 Max Raw = 32000 In this case, a raw value of 12800 would be displayed as 150. A raw value of 6400 would be displayed as 0 and a raw value of 0 would be displayed as 0 (all values outside the boundaries set by the Min Raw and Max Raw values are clamped). The above scaling works in reverse when the I/O tag data is written from the Control HMI Tagname Dictionary to other Windows applications. 12 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix Lab 2: Defining an I/O Item in Control HMI Introduction Control HMI can receive data from other local or remote Windows applications when I/O- type tags are defined in the Tagname Dictionary. Each I/O-type tag references a valid item in the I/O Server program. Objectives After completing this lab, you can define an I/O tagname. Lab Procedure Define an I/O Tagname 1. Press Ctrl+T. The Tagname Dictionary dialog box appears. 2. Click New to clear the Tagname field. The first time the Tagname Dictionary is accessed, the definition for the internal system tag $AccessLevel appears. When other tags have been defined in the Tagname Dictionary, the last edited tagname's definition appears. Note: Right-click any of the text entry fields in any of the Tagname Dictionary dialog boxes. A menu will open displaying the commands that you can apply to the selected text. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation 13 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix 3. In the Tagname field, enter a name for the new tagname. 4. Click Type. The Tag Types dialog box appears. 5. Click I/O Discrete for this tag. 6. Click OK. The respective details dialog box appears. Note: If the details portion of the dialog box does not open, click Details at the top of the window. 7. Specify all required details for defining the item. 8. In the Tagname Dictionary window, click Access Name. The Access Names dialog box appears. 14 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix 9. Double-click the access name that you will use and click Close. In the previous figure, the PLC1 access name is selected for this tag. Note: The Type cannot be changed after changing the Item. The selected Access Name (now associated with this tag definition) appears adjacent to the Access Name button in the Details dialog box. 10. In the Item field, enter the item name for the data value in the I/O Server program. Note: It is important to understand that the tagname is the name used within Control HMI to refer to a data value (tag). The Item is the name used by a remote Windows application to refer to the same value. These names do not have to be the same, but it is recommended (when applicable) to use the same names. 11. Click Close. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation 15 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal



Appendix 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 9 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal