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.1 Implicit Message…………………………………………………………….. …… 2 2 3 - RS Linx Configuration 3.0 RS Linx EDS and Icon Files………….………………………………………… 3.1 DX Advanced and MW100 device registration configuration in RS Linx…… 2 2 4 - DX Advanced, MW100 EtherNet IP Data Formats 4.
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.
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.
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.
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‖.
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‖.
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‖.
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.
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.
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.
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. 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‖.
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‖.
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.
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.
DX Advanced Data Table Map for Explicit Messaging continued… Commands: Control Logix, Compact Logix, CIP Data Table Read/Write Mapping 4.
4.3 DX Instance ID Map for Implicit Messaging 4.4 MW100 Instance ID Map for Implicit Messaging 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.
Reading Data from DX Advanced / MW100: *1 Special data will have the following values…. *2 The following values are 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.
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.
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.
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.
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).
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).
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.
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.
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])
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.
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 ―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.
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.
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 ―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).
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.
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.
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.
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).
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).
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.
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.
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).
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.
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.
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.
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.
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…..
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…..
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…..
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‖.
Select ―Top‖ to return to main menu…… 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.
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).
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.
Appendix A – Rockwell Processor EtherNet IP Compatibility A.0 MicroLogix Series A.1 SLC 500 Series A.
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.
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.
