Quick Start Guide for Rockwell PLC’s

DX Advanced / MW100 EtherNet IP Communications

IM-DXA/MW-EIP-013

Contents 1 -EtherNet IP Overview

1.0 Industrial Ethernet Protocol………………………………………………………… 1 1.1 Common Industrial Protocol……………………………………………………….. 1

2 - Message Type Definitions 2.0 Explicit Message…………………………………………………………….. …… 2 2.1 Implicit Message…………………………………………………………….. …… 2

3 - RS Linx Configuration 3.0 RS Linx EDS and Icon Files………….………………………………………… 2 3.1 DX Advanced and MW100 device registration configuration in RS Linx…… 2

4 - DX Advanced, MW100 EtherNet IP Data Formats

4.0 Data type and specific PLC usage explanation………………………………… 13 4.1 DX Advanced Explicit Messaging Data Mapping Tables……………………….. 13 4.2 MW100 Explicit Data Mapping Tables……………………………………………. 14 4.3 DX Advanced Implicit Messaging Data Mapping Tables……………………….. 15 4.4 MW100 Implicit Data Mapping Tables……………………………………………. 15 4.5 Communication Considerations…………………………………………………… 15

5 - Explicit Messaging Examples

5.0 SLC 5/05 Example………………………………………………………………….. 18 5.1 CompactLogix Example……………………………………………………………. 23 5.2 MicroLogix 1100 Example…………………………………………………………. 26 5.3 SLC 5/04 via 1761-NET-ENET Example…………………………………………. 30

6 - Implicit Messaging Example 6.0 CompactLogix……………………………………………………………………….. 37

7 - Device Communication Watchdog Implementation Example

7.0 SLC 5/05 Watchdog Example……………………………………………………… 42

8 – Reading Recorder Status Example 8.0 MicroLogix 1100 / MW100 Recorder Status Monitor Example………………… 45

Appendix A – Rockwell Processor EtherNet IP Compatibility Reference A.0 MicroLogix Series…………………………………………………………………… 53 A.1 SLC 500 Series……………………………………………………………………… 53 A.2 CompactLogix Series……………………………………………………………….. 53 A.3 ControlLogix Series…………………………………………………………………. 54 A.4 FlexLogix Series…………………………………………………………………….. 54 A.5 PLC 5 Series………………………………………………………………………… 55

Important Notice

This Quick Start Guide assumes that the user has a fundamental understanding of the various Rockwell PLC platforms (MicroLogix, SLC 500, CompactLogix, and ControlLogix), Rockwell software packages (RSLogix 500 and RSLogix 5000), and the Yokogawa DX Advanced and MW100 Data Acquisition Recorders. It is not intended to be an instructional manual for the above items. Yokogawa Corporation provides this book “As Is”, without warranty of any kind, either expressed or implied. Because of the variety of uses for the products described in this publication, those responsible for the application and use of this equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards. The illustrations, charts, sample programs and layout examples shown in this guide are intended solely for purposes of example. Since there are many variables and requirements associated with any particular installation, Yokogawa Corporation does not assume responsibility or liability (to include intellectual property liability) for actual use based upon the examples shown in this publication. This book could contain technical inaccuracies or typographical errors. Changes are made periodically to the information herein. Yokogawa Corporation may make improvements and changes at any time to the product(s) and/or program(s) described in this book. “ControlLogix”, “CompactLogix”, “SLC500”, “SLC-5/03”, “SLC 5/04”, “SLC 5/05”, “PLC 5”, “FlexLogix”, “MicroLogix, “RS Linx”, “RSLogix 500”, and “RSLogix 5000”, are all licensed trademarks of Rockwell Automation.

1 - EtherNet IP Overview 1.0 Industrial Ethernet Protocol The Industrial Ethernet Protocol (Ethernet IP) was originally developed by Rockwell Automation and is now managed by the Open DeviceNet Vendors Association (ODVA). It is a well-established Industrial Ethernet communication system with Real-Time capabilities. EtherNet IP has a strong presence in America and Asia and has been selected by many major manufacturers as a plant wide communication system for factories worldwide. EtherNet IP is standardized in the International standard IEC 61158 and EtherNet IP devices are certified by ODVA for interoperability and conformance. EtherNet IP extends commercial off-the-shelf Ethernet to the Common Industrial Protocol (CIP) — the same upper-layer protocol and object model found in DeviceNet and ControlNet. CIP allows EtherNet IP and DeviceNet system integrators and users to apply the same objects and profiles for plug-and-play interoperability among devices from multiple vendors and in multiple sub-nets. Combined, DeviceNet, ControlNet and EtherNet IP promote transparency from sensors to the enterprise software. 1.1 Common Industrial Protocol (CIP) CIP provides a wide range of standard objects and services for access to data and for control of network devices via so-called "implicit" and "explicit" messages. The CIP data packets are encapsulated before they will be send with standard TCP or UDP telegrams on the Ethernet.

EtherNet IP uses all the transport and control protocols of standard Ethernet including the Transport Control Protocol TCP), the User Datagram Protocol (UDP), the Internet Protocol (IP) and the media access and signaling technologies found in off-the-shelf Ethernet technology. Building on these standard communication technologies means that EtherNet IP works transparently with all the standard Ethernet devices found in today's market place. It also means that EtherNet IP automatically benefits from all further technology enhancements such as Gigabit Ethernet and Wireless technologies.

1

2 - Message Type Definitions 2.0 Explicit Message

Explicit messages contain addressing and service information that directs the receiving device to perform a certain service (action) on a specific part (e.g., an attribute) of a device. Explicit message data can be sent or received from any available instance in the EtherNet IP device being communicated to. Explicit messages allow for easy management of different data types.

2.1 Implicit (I/O) Message Implicit messages do not carry address and/or service information; the consuming node(s) already know what to do with the data based on the connection ID that was assigned when the connection was established. Implicit messages are so named because the meaning of the data is ―implied‖ by the connection ID. When an Implicit message procedure is setup for a specific device. All data sent to or received from the device must be of the same type.

The DX Advanced and MW100 platforms support both Explicit and Implicit messaging. The choice of which is based on the actual application requirements.

3 - RSLinx Configuration 3.0 For devices to communicate with Rockwell (Allen Bradley) PLC’s, they should first be configured as devices in

Rockwell’s RSLinx communications utility software. While the DX2000 Advanced and MW100 platforms can be configured as generic devices in RSLinx, Yokogawa provides EDS (Electronic Data Sheet) files and ICO (icon) files for both, making for a more intuitive environment as well as providing additional data to the PLC processor about the device. Copy these files from the supplied CD to a directory on the PC.

3.1 Configuration of RSLinx for use with DX Advanced and MW100 via direct Ethernet Connection

For this example, the DX2000’s IP address will be configured as: 192.168.1.100. The MW100’s IP address will be configured as: 192.168.1.101.

A) Register DX Advanced and MW100 EDS files for use in RSLinx Steps:

1. From Window’s Program Manager, Start the ―EDS Hardware Installation Tool‖

Thumbnails for .EDS and .ICO files……..

2

2. Select ―Add‖ from the EDS Hardware Installation Tool Menu

3. At this point, single EDS files may be registered or an entire directory of EDS files may be registered. In this example, a directory containing the DX Advanced and MW100 EDS files is registered. Select ―Register a directory of EDS files‖ and ―Browse‖ for the folder where the EDS files are located. Then press ―Next‖.

3

4. When the ―EDS File Installation Test Results‖ window appears, it indicates whether or not the selected

manufacturer’s EDS files contain valid data. A green check will appear on the left of each file indicating that the files contain no errors for use with RSLinx. Press ―Next‖.

5. In the ―Change Graphic Image window, the default icons for the DX1000/2000 and MW100 will appear. Unless a different icon image is desired, press ―Next‖.

4

6. The ―Final Task Summary‖ window lists a review of the requested tasks. In this case it show that the

DX1000/2000 and MW100 EDS files are going to be registered. Press ―Next‖.

7. A status window will briefly appear as the EDS files are being registered and then the completion window will be shown. Press ―Finish‖.

5

8. Select ―Exit‖ from the EDS Hardware Installation Tool Menu

The DX Advanced and MW100 EDS files are now ready for use by RSLinx. B) Configure RSLinx Ethernet Driver for use with DX Advanced and MW100

1. From the Windows Program Manager, Start ―RSLinx‖. (Note: If RSLinx is already running as a service, click the RSLinx icon in the Windows System Tray).

2. From the RSLinx Main window, select the ―RS Who‖ icon (RS Who may also be activated from the ―Communications‖ pull down menu)

6

3. The ―RS Who‖ window will open showing current running drivers. In this example, there is an Ethernet driver

entitled ―AB_ETH-1, Ethernet‖. Click on the ―+‖ symbol to the left of the driver. In the right window, connected devices are shown.

4. Any devices connected to the ―AB_ETH-1, Ethernet‖ driver now appear in the driver’s tree. In this example, there is a Compact Logix processor located at IP address 192.168.1.95. For the DX Advanced or MW100 to be used as an EtherNet IP device communicating to a Rockwell processor, the DX Advanced or MW100 must be mapped to an Ethernet driver in RSLinx. An existing driver such as the ―AB_ETH-1, Ethernet‖ below may be used or a new driver created. For this example, we are going to create a new driver in the next step.

7

5. From the RSLinx Main window, select the ―Configure drivers‖ icon (―Configure Drivers‖ may also be activated from

the ―Communications‖ pull down menu).

6. The ―Configure Drivers‖ window will open listing any running drivers. Go to the pull down arrow at the ―Available Driver Types‖ area and click.

8

7. A list of available drivers will then be displayed. Select ―Ethernet devices‖ or ―EtherNet IP Driver‖ (either will work). In this example, the ―Ethernet devices‖ driver is used. (Note: If the ―EtherNet IP Driver‖ is selected, RSLinx will automatically search the network and populate the driver with any EtherNet IP compatible devices found)

8. Click on ―Add New‖.

9

9. When the ―Add New RSLinx Driver‖ dialog box opens, enter a name for the new driver and click ―OK‖.

10. The ―Station Mapping‖ window for the new driver will now open with Station ―0‖ as a blank. Enter the IP address of the first station for use with the driver (in this example, 192.168.1.100 for the DX1000/2000). The click ―Add New‖.

10

11. Station 1 will is now created. Enter the IP address for the next station (in this example, 192.168.1.101 for the MW100). Then click ―Add OK‖.

12. The new driver will now be displayed in the ―Configure Drivers‖ screen along with the Running Status. Click ―Close‖.

11

13. The new driver (―Yokogawa‖ in this example) will now appear in the ―RS Who‖ list. 14. By clicking the ―+‖ icon on the left side of the driver, the devices configured in the driver will be listed. If they are offline or not connected, a large, red ―X‖ will appear thru the device icon. RSLinx is now configured to allow connectivity between the DX1000/2000, MW100, and Rockwell PLC’s on the network.

12

4 -DX Advanced / MW100 EtherNet IP Data Format 4.0 EtherNet IP communications are available for current as well as some legacy Rockwell PLC’s. Communications

are supported for the PLC 2, PLC 5, SLC500, Micro Logix, Compact Logix, and Control Logix platforms.

The PLC 2, PLC5, SLC 500, and Micro Logix series support Explicit Messaging functions. The Control Logix and Compact Logix platforms support both Implicit (I/O) and Explicit Message Functions.

Explicit Messages are created using the ―MSG‖ command in all of the above PLC’s. Implicit (I/O) commands are created thru I/O mapping on the Control Logix and Compact Logix platforms.

When using Explicit Messaging, data type is very important. Various data types (INT, DINT (INT32), and Float (Real), are supported. When using Implicit Messaging, only one data type can be selected for both Read and Write instances. Refer to the following tables:

4.1 DX Advanced Data Table Map for Explicit Messaging

13

DX Advanced Data Table Map continued…

DX Advanced Data Table Map for Explicit Messaging continued…

Commands: Control Logix, Compact Logix, CIP Data Table Read/Write Mapping

4.2 MW100 Data Table Map for Explicit Messaging

14

4.5 Communication Considerations

About Communication Interval

Data Update The DX Advanced and MW100 data is updated in a scan interval. Even if a PLC accesses the data at shorter intervals than the DX or MW100 scan intervals, the data is updated only at scan intervals.

Communication Interval A PLC should access the DX or MW100 at intervals of 125 ms or longer. * This is required to maintain compatibility with other protocols supported by the DX than EtherNet IP.

Access to Non-existent Data If non-existent data is accessed, either of the following operations occurs. • 0 is read if non-existent data is read. Nothing is done if non-existent data is written. When the DX Data Type Differs from the Data Type Specified in a Command Each data set on the DX/MW100 has a fixed data type. Data on the DX/MW100, which includes special data, accessed using the same data type is transmitted unchanged. Data on the DX/MW100 accessed using a different data has its data type converted. The following explains the conversion rules:

4.3 DX Instance ID Map for Implicit Messaging

4.4 MW100 Instance ID Map for Implicit Messaging

15

Reading Data from DX Advanced / MW100:

*2 The following values are used….

Writing Data to DX Advanced / MW100:

*1

*1 Special data will have the following values….

16

DX Advanced / MW100 Data Type Usage Explanation In the tables above, INT, INT32, and Float addresses are shown for the same Measurement Channel. Any of the data type may be used dependant on the application. For example, with an SLC 5/05, if the data from the DX Advanced or MW100 Measurement Channel #1 was required to be in a Float (Real) format when received by the PLC, address F10:0 would be used. If needed in an INT format, N10:0 would be used.

*2 A FLOAT value with the same number of decimal places as the one specified for the channel is converted to INT16. Other numbers are ignored. Example: If the number of decimal places of channel 201 is "2" (For example, the range can be set is from -200.00 to 200.00). A FLOAT value up to two decimal places is rounded to an integer. See the example in the following table.

Values are written as follows:

17

5 - Explicit Messaging Examples

5.0 SLC 5/05 In this example, the system consists of a 1747-L551C (5/05CPU – 16K Mem, OS501 Series C FRN 10 and Later) processor and a 1746-NT4 Thermocouple Input Module residing in slot #1. The SLC 5/05’s IP address is 192.168.1.95. The 1746-NT4 module’s four input channels are sent to the DX Advanced Communication Channels C01 thru C04. The 1746 NT4’s channels are configured for ―Engineering Units‖ which will result in an integer value with an implied decimal point (i.e. 66.8 = 668). The DX Advanced Measurement Channels 001 thru 010 are being read and stored in 10 words starting with F10:0. Data File ―N10:0‖ has been created for Message Instruction Control Block Data. ―N11‖ contains I/O Configuration Data. Configuration of Channel 1 On the Project Tree, under the ―Controller‖ folder, double-click on ―Channel Configuration‖ (or right click and select ―Open‖). In the ―Channel Configuration‖ dialog box, select the ―Chan. 1 – System‖ tab.

18

In this example, the ―BOOTP‖ function is not used and the IP address and Subnet mask are fixed. Enter the IP address and subnet mask for the SLC 5/05. Enter other network information (Gateway, Domain Name, etc.) as required. Other settings such as ―Msg Connection Timeout‖ are left at default values. These should be reviewed and set per the application requirements. When settings are completed, click ―OK‖. The SLC 5/05’s Ethernet configuration is now complete.

19

In the example below, on Rung 0000, the 1746-NT4 Thermocouple Input module is being configured on the SLC 5/05’s first scan. The next rung (Rung 0001) contains a MSG instruction, which writes Input words I:1.0 thru I:1.3 (1746-NT4 Input Channels 0-3) to the DX Advanced Communication Channels C01-C04. In Rung 003, a MSG instruction reads data from the DX Advanced, Measurement Channels 1-10, and stores the data in F8:0-F8:9. The MSG Write instruction on Rung 0001 is configured as follows: Type – Peer-To-Peer (default value, cannot be changed) Read/Write – Write Target Device – 500CPU Local/Remote – Local Control Block – N10:0 The Control Block Length will be set automatically based on the information contained in the MSG instruction. DO NOT ALLOW CONTROL BLOCK ADRESSES TO OVERLAP AS UNPREDICABLE RESULT MAY OCCUR. The Control Block’s Enable Bit (N10:0/15) is used to continuously toggle the instruction. If another data transmission interval is required, configure the rung appropriately. Double clicking on the ―Setup Screen‖ portion of the instruction accesses the MSG Instruction configuration.

20

In the ―This Controller‖ area, enter the starting data table address for the data to be sent (I:1.0), the Size in Elements (number of data words) (4), and the Channel (1 for Ethernet). In the ―Target Device‖ area, enter the starting data table address of the DX Advanced (N30:0 for Communication Channel C01). In the ―MultiHop‖ selection box, select ―Yes‖. Then click on the ―MultiHop tab at the top of the Setup Screen. In the ―To Address‖ area, enter the IP address of the DX Advanced (192.168.1.100). Then click on the close window (X) at the top right of the Setup Screen (the screen can also be closed by clicking on the ―Setup Screen‖ In the MSG instruction. The MSG Write to the DX Advanced is now complete.

21

The MSG Read instruction on Rung 0002 is configured as follows: Type – Peer-To-Peer (default value, cannot be changed) Read/Write – Read Target Device – 500CPU Local/Remote – Local Control Block – N10:51 In the ―This Controller‖ area, enter the starting data table address for the data to be received (F8:0), the Size in Elements (number of data words) (10), and the Channel (1 for Ethernet). In the ―Target Device‖ area, enter the starting data table address of the DX Advanced (F10:0 for Measurement Channel C01). In the ―MultiHop‖ selection box, select ―Yes‖. Then click on the ―MultiHop tab at the top of the Setup Screen. In the ―To Address‖ area, enter the IP address of the DX Advanced (192.168.1.100). Then click on the close window (X) at the top right of the Setup Screen (the screen can also be closed by clicking on the ―Setup Screen‖ In the MSG instruction. The MSG Read from the DX Advanced is now complete.

22

5.1 CompactLogix In this example, the system consists of a 1769-L32E (Compact Logix 5332E Controller) processor and a 1769-IT6 Thermocouple Input Module residing in slot #1. The Compact Logix IP address is 192.168.1.95. The 1769-IT6 module’s six input channels are sent to the DX Advanced Communication Channels C01 thru C06. The 1769-IT6’s channels are configured for ―Engineering Units‖ which will result in an integer value with an implied decimal point (i.e. 66.8 = 668). The DX Advanced’s IP address is 192.168.001.100, The DX Advanced’s Measurement Channels 001 thru 010 are being read and stored in 10 words starting with an Array Tag named ―DX_Advanced_Measurement Channels‖, configured for REAL format. Two ―MESSAGE‖ tags were created for use with the MSG instructions, ―DX_Advanced_Data_Read‖ and ―DX_Advanced_Data_Write‖. In the ladder example below, the ―Write‖ and ―Read‖ MSG instruction’s Message Control Tag’s Enable bit (.EN) is used to continuously toggle the instruction. If another data transmission interval is required, configure the rung appropriately.

23

The Write Message is configured as shown below…… Message Type – CIP Data Table Write Source Element – Tag - Local1:I.Ch0Data (1769-IT6 Channel 0) Number of Elements – 6 Destination Element – int[3000] (DX Advanced Communication Channel C01) The Message Write instruction on Rung 0 is configured as follows…… Click on the Message instruction ―View Configuration Dialog‖ button In the ―Configuration area, select the Message Type (CIP Data Table Write), select the Source Element tag (Local:1:I.Ch0Data), enter the Number of Elements (6), and the Destination Element (int[3000], DX Advanced Communication Channel C01). Then click on the ―Communication‖ tab. Enter the ―Path‖ information. In this case the Ethernet port on the Compact Logix is used which would be ―LocalENB,2,192.168.001.100 (the ―2‖ is the communication depth on the Compact Logix). Select ―Connected‖ and ―Cache Connections‖ (speeds up communications). Click ―OK‖. The DX Advanced Write Message configuration is complete.

24

The Read Message on Rung 0002 is configured as shown below…… Message Type – CIP Data Table Read Source Element – real[1000] (DX Advanced Measurement Channel 0) Number of Elements – 10 Destination Element – Tag – DX_Advanced_Measurement_Channels (Array Tag, Real format) The Message Read instruction is configured as follows…… Click on the Message instruction ―View Configuration Dialog‖ button In the ―Configuration area, select the Message Type (CIP Data Table Read), select the Source Element tag (real[1000]), enter the Number of Elements (10), and the Destination Element (DX_Advanced_Measurement_Channels). Then click on the ―Communication‖ tab. Enter the ―Path‖ information. In this case the Ethernet port on the Compact Logix is used which would be ―LocalENB,2,192.168.001.100 (the ―2‖ is the communication depth on the Compact Logix). Select ―Connected‖ and ―Cache Connections‖ (speeds up communications). Click ―OK‖. The DX Advanced Read Message configuration is complete.

25

5.2 MicroLogix 1100 In this example, the system consists of a 1763 MicroLogix 1100, Series A processor and a 1762-IT4 Thermocouple Input Module residing in the first expansion slot. The MicroLogix 1100’s IP address is 192.168.1.96. The MW100’s IP address is 192.168.001.101. The 1762-IT4 module’s four input channels are sent to the MW100’s Communication Channels C01 thru C04. The 1762-IT4’s channels are configured for ―Engineering Units‖ which will result in an integer value with an implied decimal point (i.e. 66.8 = 668). The MW100’s Measurement Channels 001 thru 010 are being read and stored in 10 words starting with F8:0. Data File ―MG10‖ has been created for Message Files. ―Data File RI11 has been created for storing Message Routing Information. Configuration of Channel 1 On the Project Tree, under the ―Controller‖ folder, double-click on ―Channel Configuration‖ (or right click and select ―Open‖). When the ―Channel Configuration‖ dialog box opens, click on the ―Channel 1‖ tab.

26

In this example, the ―BOOTP‖ function is not used and the IP address and Subnet mask are fixed. Enter the IP address and subnet mask for the MicroLogix 1100. Enter other network information (Gateway, Domain Name, etc.) as required. Other settings such as ―Msg Connection Timeout‖ are left at default values. These should be reviewed and set per the application requirements. When settings are completed, click ―OK‖. The MicroLogix 1100 Ethernet configuration is now complete. In the example below, on Rung 0000, a MSG instruction writes Input words I:1.0 thru I:1.3 (1762-IT4 Input Channels 0-3) to the MW100, Communication Channels C01-C04. In Rung 001, a MSG instruction reads data from the MW100, Measurement Channels 1-10, and stores the data in F8:0-F8:9. The MSG Write instruction is configured to use MSG File MG10:0 The MSG File Word Enable Bit (MG10:0/EN) is used to continuously toggle the instruction. If another data transmission interval is required, configure the rung appropriately. Double clicking on the ―Setup Screen‖ portion of the instruction accesses the MSG Instruction configuration.

27

In the ―This Controller‖ area, select the ―Channel‖ (1(Integral)), select the ―Communication Command‖ (500CPU Write), the starting data table address for the data to be sent (I:1.0), and the Size in Elements (number of data words) (4). In the ―Target Device‖ area, enter the starting data table address of the MW100 (N30:0 for Communication Channel C01), and the ―Routing Information File (RI)‖ (RI11:0). Then click on the ―MultiHop tab at the top of the Setup Screen. In the ―To Address‖ area, enter the IP address of the MW100 (192.168.1.101). Then click on the close window (X) at the top right of the Setup Screen (the screen can also be closed by clicking on the ―Setup Screen‖ In the MSG instruction. The MSG Write to the MW100 is now complete.

28

The MSG Read instruction is configured to use MSG File MG10:1 The MSG File Word Enable Bit (MG10:1/EN) is used to continuously toggle the instruction. If another data transmission interval is required, configure the rung appropriately. Double clicking on the ―Setup Screen‖ portion of the instruction accesses the MSG Instruction configuration. In the ―This Controller‖ area, select the ―Channel‖ (1(Integral)), select the ―Communication Command‖ (500CPU Read), the starting data table address for the data to be received (F:8.0), and the Size in Elements (number of data words) (10). In the ―Target Device‖ area, enter the starting data table address of the MW100 (F10:0 for Measurement Channel #1), and the ―Routing Information File (RI) (RI11:1). Then click on the ―MultiHop tab at the top of the Setup Screen. In the ―To Address‖ area, enter the IP address of the MW100 (192.168.1.101). Then click on the close window (X) at the top right of the Setup Screen (the screen can also be closed by clicking on the ―Setup Screen‖ In the MSG instruction. The MSG Read from the MW100 is now complete.

29

5.3 SLC 5/04 via 1761-NET-ENI In this example, the system consists of a 1747-L541C (5/04 CPU, 16K Mem, OS401 Series C FRN 3-8) processor and a 1747-NT4 Thermocouple Input Module residing in slot #1. The SLC 5/04 is connected to EtherNet IP via a 1761-NET-ENI (Ver. D, Rev. A, Firmware 3.21) Network Interface connected to Channel 0. The 1761-NET-ENI’s IP address is 192.168.1.125. The MW100’s IP address is 192.168.001.101. The 1747-NT4 module’s four input channels are sent to the MW100’s Communication Channels C01 thru C04. The 1747-NT4’s channels are configured for ―Engineering Units‖ which will result in an integer value with an implied decimal point (i.e. 66.8 = 668). The MW100’s Measurement Channels 001 thru 010 are being read and stored in 10 words starting with F8:0. Data File ―N9:0‖ has been created for I/O Configuration Data. When using processors that do not have a built in Ethernet port, communications to an EtherNet IP device is accomplished by sending a message via DF1 serial protocol to the 1761-NET-ENI, which in turn re-routes the message in a CIP format.

The 1761-NET-ENI Network Inteface is configured via Rockwell’s ―ENI Configuration Utility,‖ available from Rockwell’s website. The same cable that is used to connect the 1761-NET-ENI to the SLC 5/04 can be used to connect the 1761-NET-ENI to a PC’s 9-pin serial port. 1761-NET-ENI Configuration Under the ―ENI IP Addr‖ tab, select the ENI Series (D), set the 232 Baud Rate (38400), set the 1761-NET-ENI’s IP address (192.168.001.125) and subnet mask (255.255.255.0). Uncheck ―Obtain via BootP‖ as this application utilizes a fixed IP address. Then click on the ―Message Routing‖ tab.

SLC 5/04 MW100

1761-NET-ENI

To plant wide network….

Hub or Switch

Typical 1761-NET-ENI connection example.

1761-CBL-PM02 Cable

30

The ―Destn‖ numbers signify DF1 node addresses that would be entered into the SLC 5/04’s MSG instruction. The IP address of the EtherNet IP device that the SLC 5/04 is going to send or read data from is entered under the ―IP Address‖ row corresponding to the selected ―Destn‖ node address. In the example, node address ―45‖ is mapped to 192.168.001.101 (MW100). Note that to communicate with ControlLogix or CompactLogix systems or other devices that utilize CIP (DX Advanced, MW100), node addresses 45 thru 49 must be used. After entering the destination IP address, click on the ―Utility Settings‖ tab. Under ―COM Port‖, select the com port on the PC, which will be used to upload/download to the 1761-NET-ENI. When first taken out of the box, the 1761-NET-ENI’s (Series B or higher) RS232 baud rate is set to ―Auto‖. In this example, the baud rate to ―38400‖ (the fastest setting allowed in the SLC 5/04 Channel 0 configuration). The click on the ―ENI IP Addr‖ tab. At this point, with the PC connected to the 1761-NET-ENI, under the ―Save To‖ area on the right, select ―ENI ROM‖ (the configuration may also be saved to a file for future use, or in the 1761-NET-ENI’s RAM. If the configuration is stored in RAM, it will be lost upon power down). Once the download is complete, the 1761-NET-ENI is now ready for use.

31

SLC 5/04 Channel 0 Configuration On the Project Tree, under the ―Controller‖ folder, double-click on ―Channel Configuration‖ (or right click and select ―Open‖). In the ―Channel Configuration‖ dialog box, select the ―Chan. 0 – System‖ tab.

32

Configure the channel as follows: Driver - select “DF1 Full Duplex”. Baud – select “38.4K” Parity – select “None” Stop Bits – select “1” Source ID – In this example, the SLC 5/04’s DF1 address is “1” Under the ―Protocol Control‖ area, enter the following: Control Line – select “No Handshaking Error Detection – select “CRC” Embedded Response – select “Enabled” Duplicate Packet Detect – check the box. When finished, click ―OK‖. The SLC 5/04 channel configuration is complete.

33

In the example below, on Rung 0000, the 1746-NT4 Thermocouple Input module is being configured on the SLC 5/04’s first scan. The next rung (Rung 0001) contains a MSG instruction, which writes Input words I:1.0 thru I:1.3 (1746-NT4 Input Channels 0-3) to the MW100’s Communication Channels C01-C04. In Rung 003, a MSG instruction reads data from the MW100, Measurement Channels 1-10, and stores the data in F8:0-F8:9. The MSG Write instruction on Rung 0001 is configured as follows: Type – Peer-To-Peer (default value, cannot be changed) Read/Write – Write Target Device – 500CPU Local/Remote – Local Control Block – N7:0 The MSG Write instruction is configured to use Control Block N7:0. The Control Block Length will be set automatically based on the information contained in the MSG instruction. DO NOT ALLOW CONTROL BLOCK ADRESSES TO OVERLAP AS UNPREDICABLE RESULT MAY OCCUR. The Control Block Word Enable Bit (N7:0/15) is used to continuously toggle the instruction. If another data transmission interval is required, configure the rung appropriately. Double clicking on the ―Setup Screen‖ portion of the instruction accesses the MSG Instruction configuration.

34

In the ―This Controller‖ area, enter the starting data table address for the data to be sent (I:1.0), the Size in Elements (number of data words) (4), and the Channel (0). In the ―Target Device‖ area, enter the starting data table address of the MW100 (N30:0 for Communication Channel C01). Enter the Local Node Address (45 – DF1 equivalent to 192.168.001.096 in the ENI configuration. The ―Octal‖ section will fill in automatically). Then click on the close window (X) at the top right of the Setup Screen (the screen can also be closed by clicking on the ―Setup Screen‖ In the MSG instruction. The MSG Write to the MW100 is now complete.

35

The MSG Read instruction on Rung 0002 is configured as follows: Type – Peer-To-Peer (default value, cannot be changed) Read/Write – Read Target Device – 500CPU Local/Remote – Local Control Block – N7:14 In the ―This Controller‖ area, enter the starting data table address for the data to be received (F8:0), the Size in Elements (number of data words) (10), and the Channel (0). In the ―Target Device‖ area, enter the starting data table address of the MW100 (F10:0 for Measurement Channel 1). Enter the Local Node Address (45 – DF1 equivalent to 192.168.001.096 in the ENI configuration. The ―Octal‖ section will fill in automatically). Then click on the close window (X) at the top right of the Setup Screen (the screen can also be closed by clicking on the ―Setup Screen‖ In the MSG instruction. The MSG Write to the MW100 is now complete.

36

6 - Implicit I/O Messaging Examples 6.0 CompactLogix In this example, the system consists of a 1769-L32E (Compact Logix 5332E Controller) processor and a 1769-IT6 Thermocouple Input Module residing in slot #1, sending and receiving data with an MW100 configured as an I/O device. The CompactLogix’s IP address is 192.168.1.95. The MW100’s IP address is 192.168.001.101. The 1769-IT6’s channels are configured for ―Engineering Units x 1‖ which will result in an integer value with an implied decimal point (i.e. 66.8 = 668). With the 1769-IT6 module configured, the Channel Tags are listed under ―Controller Tags‖. From the Project tree, select ―I/O Configuration‖……. Select ―Backplane, CompactLogix System‖……

37

Select ―1769-L32E Ethernet Port LocalENB‖…… Right click on ―Ethernet‖……

38

Select ―New Module‖…… When the ―Select Module‖ dialog box opens, select ―Communications‖……

39

Select ―Ethernet-Module Generic Ethernet Module‖ from the listing…… Enter the following items: Name: ―MW100‖ Description: Yokogawa MW100 Data Acquisition Unit (description is optional). Comm Format: DINT (Note: Once the COMM Format is set, it may not be changed in the future. To change the COMM Format, the module will need to be deleted and recreated). Address/Host Name – IP Address: 192.168.001.101 Input – Assembly Instance:110 (MW100 Measurement Channels), Size: 10 (MW100 Measurement Channels 1 thru 10) Output – Assembly Instance: 130 (MW100 Communication Channels), Size: 6 (MW100 Communication Channels C01 thru C06) Configuration – Assembly Instance: 190, Size: 0

40

Then select the ―Connection Tab‖…… Enter the ―Requested Packet Interval (RPI)‖ for the application. The default is 10.0ms. This value will be based on the EtherNet IP network traffic and may need to be adjusted based on the application requirements. Press ―OK‖ when finished. The MW100 Implicit (I/O) Configuration is complete and MW100 Tags are automatically created in the ―Controller Tags‖ area……(Note: Descriptions must be entered manually). The MW100 Measurement Channels are now available for use in logic programs. The next step is to send the 1769-IT6 Channels 0 thru 5 to the MW100 Channels C01 thru C06. This is accomplished via a ―COP‖ instruction in logic. Refer to example below……

41

7 - Device Communication Watchdog Example 7.0 DX Advanced / SLC 5/05 Watchdog Example For any control application, communications validity is a key factor, especially when utilizing I/O devices. If the PLC is utilizing a DX Advanced for analog input data with which the process will use for output determinations, it is critical that should communication between the PLC and DX Advanced be lost, the situation be detected and the appropriate actions taken to insure the application’s proper steps, whether it be to shut down the process or compensate in another manner. In this example, an SLC 5/05, IP address 192.168.001.010 is communicating with a DX Advanced, IP address 192.168.001.100. Using Math Channel 110 in the DX Advanced, an equation is set up to toggle the channel value between 1 and 0 on a time interval determined by the DX Advanced Scan Interval (1 Second in this example). When using an MW100, if a faster scan interval is being used, take steps to insure that the interval selected allows for a complete communication cycle between the MW100 and PLC so that each Watchdog Value transition (Math Channel 110 in this example) is successfully transmitted to the PLC on each communication cycle. The equation in Math Channel 110 is as follows: When the channel is first scanned, it will be equal to ―0‖. Since it is not equal to Math Constant K11(1), the value will be set to equal K11 (1). On the next scan, since the value is equal to K11 and the equal statement is true, the channel value will be set to equal K10 (0). The channel will continue to toggle at 1-second intervals. Below is an example of logic used to determine the SLC 5/05 and DX Advanced Communication status……

Scan Interval setting in DX Advanced “Basic Setting” area

42

In Rung 0000, a ―MSG‖ instruction reads Math Channel 110 from the DX Advanced and places the value (0 or 1) in word N7:100. The ―MSG‖ instruction is configured as follows…… Note: SLC 5/05 Data Files start with position 0 (i.e. N7:0). DX Advanced Match Channels start with 101. As a result, based on the DX Advanced EtherNet IP data mapping tables in chapter 4, there exists an address offset of 1 and the DX Advanced Math Channel 110 is mapped as N20:9. (N20 for Computation Channel, Integer Value, element #10)

43

Since N7:100 will contain either a ―0‖ or ―1‖, bit ―0‖ status can be examined for a toggling condition. In this example, when N7:100/0 is true, Timer T4:0 starts timing. When N7:100/0 is false, Timer T4:1 starts timing. Both timers have a preset value of 2 seconds. If N7:100/0 stays in either a true or false state for more than 2 seconds, B3:0/0 will energize indicating a loss of communications with the DX Advanced. This bit could be used to disable any modes or processes that could be adversely affected by the loss of communication with the channels in the DX Advanced.

44

8 – Reading Recorder Status Example 8.0 MicroLogix 1100 / MW100 Recorder Status Monitor Example In applications where recorded data is necessary for the end product’s certification or validity, it is important that the operational status of the DX Advanced or MW100 be flagged so that the PLC can take appropriate action with the process should the recorder not be measuring or recording at the required time. This is accomplished by developing a data word containing a ―0‖ or ―1‖ to indicate recording status, and reading the status value back to the PLC. While the DX Advanced and MW100 EtherNet IP drivers allow for the reading of Measurement and Math channel data as well as receiving data for placement into the Communication channels, several operational areas in the recorders such as Status is not available for direct read via EtherNet IP. The DX Advanced and MW100 recorders also support the industry standard Modbus protocol. The recorders have a mapped area of Modbus addresses that reflect Measurement, Math, and Communication channels as well as other information such as recorder Status. (Refer to the DX Advanced and MW100 Communication Manuals for more information) To access the Status data via EtherNet IP, the Status values must be moved into Communication channels via utilizing the recorder’s Modbus Client Function. In the following example, five (5) Status indicators will be read into a MicroLogix 1100 from an MW100 recorder using Communication Channels 1-5.

The Status data will contain:

a) Measurement Started/Stopped b) Math Channels Started/Stopped c) Recording Started/Stopped d) Alarm Present e) Waiting to confirm (ACK) Alarm Status

The Modbus mapping for the Status data is available in both word and bit formats. For word data, the mapping is as follows: For bit (Coil) data, the mapping is as follows: 38001 - Measurement Started/Stopped (0/1) 18001 - Measurement Started/Stopped (0/1) 38002 - Math Channels Started/Stopped (0/1) 18002 - Math Channels Started/Stopped (0/1) 38003 - Recording Started/Stopped (0/1) 18003 - Recording Started/Stopped (0/1) 38004 - Alarm Present (0/1) 18004 – Alarm present (0/1) 38005 – Waiting to confirm (ACK) Alarm Status (0/1) 18005 – Waiting to confirm (ACK) Alarm Status (0/1) For EtherNet IP purposes, either word or bit (Coil) addresses can be used. However, the result read back to the Rockwell processor will be in a word format containing a value of ―0‖ or ―1‖. IP Addressing used for this example: MicroLogix 1100 - 192.168.1.96 MW100 – 192.168.1.200 The Status data must first be moved into the Communication channels via the Modbus Client Configuration as follows:

With ―Measurement‖, ―Math‖, and ―Recording‖ stopped on the MW100, from the MW100 ―TOP‖ web page, select ―Communication Setting‖……

45

From the ―Communication Setting‖ screen, select ―Server Setting‖……

From the ―Server Setting‖ screen, if the Modbus Server is not set to ―On‖ under ―Action‖, click on the pull down arrow and turn it on. Leave the ―Port‖ set to ―502‖.……

Select ‖Apply‖ when settings are complete…..

Select ―Communication Setting‖ at top of screen……

46

Select ―Communication Setting‖ at top of screen……

From the ―Communication Setting‖ screen, Select ―Modbus Client Setting 1‖…..

From the ―Modbus Client Setting 1‖ screen, Check the ‖Enable‖ box next to ―Client Function‖…..

The Modbus Client Cycle update rate should be set at a rate that is appropriate for the application (this is the time period reflecting how often the Modbus addresses are updated)…..

The ―Connection‖ and ―Recovery Action‖ settings do not apply for use in this example…..

Select ‖Apply‖ when settings are complete…..

47

From the ―Communication Setting‖ screen, Select ―Modbus Client Setting 2‖…..

In the ―Server List‖, enter the MW100’s IP address in the ―No. 01‖ position. Leave the ―Port‖ set at ―502‖…..

Select ‖Apply‖ when settings are complete…..

Select ―Communication Setting‖ at top of screen……

48

From the ―Communication Setting‖ screen, Select ―Modbus Client Setting 3‖…..

This page is where Modbus addresses are mapped into Communication Channels for Reads/Writes to other devices via a ―Command List‖. For Command ―No. 1‖, select ―Read‖…..

Enter ―1‖ for Server, ―255‖ for Unit, ―18001‖ for Register. Then Select ―Bit String‖ under ―Data Type‖. Enter ―C001 for the ―First Channel‖ and ―C005‖ for the ―last Channel‖. Modbus addresses 18001 thru 18005 are now mapped to Communication Channels 1 thru 5 which will now reflect the Status data contained in Modbus addresses 18001 thru 18005…..

Select ‖Apply‖ when settings are complete…..

49

Next, the MicroLogix 100 will be setup to read the Status information from the MW100 via a Message Instruction. It is assumed that the MicroLogix’ Channel 1 has already been setup as IP address 192.168.1.96. A rung is entered containing a ―MSG‖ instruction assigned to address MG10:0 and an XIC (normally closed contact assigned to MG10:0.EN (MSG Instruction MG10:0, ―Enabled‖ bit) which will toggle the instruction as follows:

Select ―Top‖ to return to main menu……

Once the instructions are entered into the rung, double click on the ―Setup Screen‖ portion of the MSG instruction……

50

The MSG Read instruction on Rung 0000 is configured as follows: On the ―General‖ tab, in the ―This Controller‖ area, enter the Channel (1 for Ethernet), Communication Command (500CPU Read), Data Table Address (B3:0), and the Size in Elements (number of data words) (5). In the ―Target Device‖ area, enter the starting data table address of the MW100 (N30:0 for Communication Channel C001). Enter ―RI11:0‖ for the Routing Information File (RI). PLC Data File R1:11 will automatically be created in the MicroLogix 1100. Then click on the ―MultiHop tab at the top of the Setup Screen. In the ―To Address‖ area, enter the IP address of the MW100 (192.168.1.200). Then click on the close window (X) at the top right of the Setup Screen (the screen can also be closed by clicking on the ―Setup Screen‖ In the MSG instruction. The MSG Write to the MW100 is now complete.

51

Next Rungs will be added to monitor the MW100’s current Status. With the Status words (B3:0 thru B3:4) reflecting either a ―0‖ or ―1‖. Since only Bit 0 of each word is used, we can utilize Bit instructions for Status monitoring. In this example, the MW100 Status Bit information is moved from Binary File #3 addresses into PLC Output addresses. With the MicroLogix Project downloaded to the CPU and the CPU placed into ―Run‖ mode, here is a screen snapshot showing the Status of the MW100 (Measurement Started, Math Channels Started, and Recording Started)…..

52

Appendix A – Rockwell Processor EtherNet IP Compatibility A.0 MicroLogix Series A.1 SLC 500 Series

A.2 CompactLogix Series

** Explicit Messaging only supported with 1761-Net-ENI

53

A.3 ControlLogix Series *1756-ENET must be series B to allow implicit messaging. 1756-ENET Series A version 1.18 from factory may be upgraded to Series B. Other Series A's cannot be upgraded. All support Explicit Messaging ** Explicit Messaging only supported with 1761-NET-ENI. Like CompactLogix, Bridging via CNET or DNET solutions always exist in Logix family. A.4 FlexLogix Series ** Explicit Messaging only supported with 1761-NET-ENI. Like CompactLogix, Bridging via CNET or DNET solutions always exist in Logix family.

54

A.5 PLC 5 Series Note: In certain EtherNet topologies, where bridges exist between PLC and target MW100, PLC AND 1785-ENET firmware may need to be upgraded, in order to support Multihop capability. To order specific firmware with a PLC 5 Processor: The part number is the letter "F" followed by the complete catalog number, and then terminated with "SER" followed by the actual series letter of your controller. Example: F1785L40BSERC - 5/40B series C controller

55