CONTROLLER INFORMATION SHEET Maple Model(s) Graphic HMCs PLC or Controller ODVA, CIP over EtherNet/IP P/N: 1036-0243 Rev. 01 Date: 05/02/2018 Summary Maple Systems Graphic HMIs communicate with any device using the Common Industrial Protocol (CIP) over an EtherNet/IP network to allow the Graphic HMI to act as a consumer, in a producer-consumer architecture. Communications Cable The Graphic HMI should be connected to the device s Ethernet port. Some controllers require straight through 10baseT Ethernet cables and others require crossover 10baseT Ethernet cables. A list of cables offered by Maple Systems as well as cable assembly instructions to assist you in assembling your own Ethernet cable is available on our website. WARNING If your communications cable is not wired exactly as shown in our cable assembly instructions, damage to the HMI or loss of communications can result. Controller Settings: The PLC s IP address must be the same as that specified in EZware s IP Address Settings. 1036-0243 Page 1 of 7 Rev. 01, 05/15/2018
Accessible CIP Data To gain access to data produced by a CIP device, the objects and attributes exposed by that device must be added to the EZwarePlus project. This is done in the tag editor window. This window will be accessible through a button on the Device tab of the System Parameter Settings window that will appear after the device is added to the Device List as described in the EZware Settings section at the end of this document: In the tag editor window there are two sections under Data Types in the browser window on the left: Struct-Defined and Object-Defined. The Struct-Defined section contains the class definitions that are available to select. Each class contains a listing of all of the attributes that make up the objects of that class. The Object-Defined section will contain all of the objects added for a particular device. Each object added to this list is an instance of the class defined in the Struct- Defined section. The objects added to the Object-Defined section will be available to select in the HMI project. The process for configuring a device is: Step 1: Cross reference the classes available in the device with the class definitions listed in the Struct-Defined list. If there are any objects in the device of a class that are not listed, add the class to the list and specify and add the attributes available (new object definition). Step 2: Add the objects available in the device to the Object-Defined section. 1036-0243 Page 2 of 7 Rev. 01, 05/15/2018
Step 1 Add New Object Definition To add a new object definition to the Struct-Defined list: 1. Right-click on Struct-Defined and select New data type 2. Enter the name of the data type under Name. (Note: The object is referenced by the Class ID and Instance ID so the name does not need to exactly match) 3. Add Attributes to the object by clicking on the Add button: 4. Enter the name for the attribute. The attribute name will contain the Class Identifier (Class ID), Instance Identifier (Instance ID), and Attribute Identifier (Attribute ID) in the following format: <attribute name>{<class ID>, <Instance ID>,<Attribute ID>} For example, a Position Controller (Class ID = 0x25 = 37 dec*) has an attribute called Actual Velocity with attribute ID = 14. For an Instance ID of 1, this would be entered as: Actual Velocity{37, 1, 14} * Class IDs are typically given in hex. Enter the decimal equivalent in EZwarePlus Note: For Class Instance variables enter zero for the Instance ID. 1036-0243 Page 3 of 7 Rev. 01, 05/15/2018
5. Select a Data type for the Attribute, and click OK to add the attribute to the class definition. 6. Verify Vendor ID. Here is an example of how to add the Vendor ID in the Tag Editor. In this example, the Identity Object > Class Code: 0x01 is the Class ID. The Class ID = 1, the Instance ID = 1, and the Attribute ID = 1. Under Struct-Defined, select Identity to add the Vendor_ID {1, 1, 1}. Enter UINT in the Data Type field according to the factory specifications. Click OK to save the changes. 7. Once all of the attributes are added, click the Save to default button. The class definition should now appear in the Struct-Defined list. 1036-0243 Page 4 of 7 Rev. 01, 05/15/2018
Step 2 Add Objects instances for the device 1. Right-click on the Object-Defined section and select New data type 2. Enter something in the name field. 3. Click the Add button to add an object. 4. Enter a name for the object instance. 5. Select the class of the object in the Data type field. All of the classes listed under Struct-Defined will be available to select. 6. Repeat steps 3 through 9 until all of the objects in the device are created. 7. Click OK and Save to default to save the objects. After the objects are added to the project, they will be available to select and use in an HMI screen: 1036-0243 Page 5 of 7 Rev. 01, 05/15/2018
EZware Settings The following table lists the communications settings that must be configured in EZware. These settings can be found on the Device tab of the System Parameter Settings window. Select Edit > System Parameters from the menu bar to access this window. Click New to add a new device to the list, or Click Settings to edit the settings of an existing device. Please note: Name The Recommended Settings column provides the recommended setting based upon default settings most commonly use in Devices which use the ODVA CIP protocol The Options column lists EZware s options; your controller may not support every option Recommended Settings Options Important Notes Name: ODVA EtherNet/IP Explicit Messaging HMI or PLC PLC Location Local Local; Remote Select Local if PLC directly connected to HMI; Remote if PLC connected thru another HMI. PLC type: ODVA EtherNet/IP Explicit Messaging PLC I/F: Ethernet Ethernet Settings: IP Address: xxx.xxx.xxx.xxx Settings: Port 44818 0-65535 Settings: Timeout (sec) 1 0.1-25.5 Settings: Turn around delay (ms) 0 0-1000 0.0.0.0 255.255.255.255 Using ODVA CIP requires the use of the Ethernet port. Use the IP Address assigned to the controller. Must be set to the TCP port used by the CIP device Adjust if longer timeout is required. Timeout period between HMI polls. Settings: Send ACK Delay: 0 Not Applicable Settings: Use UDP Unchecked Checked or Unchecked Must be Unchecked 1036-0243 Page 6 of 7 Rev. 01, 05/15/2018
Name Recommended Settings Options Important Notes PLC default station no.: 1 0-255 Does not apply to this driver. Default station no. use station no. variable Unchecked Optional Use broadcast command Unchecked Not Applicable Interval of block pack (words): Max. read-command size (words): Max. write command size (words): 5 0-512 120 1-512 120 1 512 See Help Optimizing the Update Rate with PLC Block Pack Max number of words for a read command Max number of words for a write command 1036-0243 Page 7 of 7 Rev. 01, 05/15/2018