You can use the Common Configurator to configure an Ethernet IP data source and set up the Ethernet IP communication channel to the PLCs for data acquisition.
Requirement
- Ethernet IP Connector must be running.
Procedure
To add an Ethernet IP data source, follow these steps:
- Launch Common Configurator application.
The Get data page opens, displaying available connectors. - Click Ethernet IP Connector tab.
Overview page of Ethernet IP Connector appears. - Click
icon.
The Add Data Source window appears. - Select Ethernet IP from the Communication protocol selection list.
The configuration options are displayed.
-
Enter the following information:
Field name Description * Name Defines the name of the data source. The name must be unique across all connectors. CPU type Select the CPU type corresponding to the PLC from the selection list. The following options are available: - ControlLogix
- CompactLogix
- MicroLogix
- Micro800
- PLC5
- SLC500
- LogixPCCC
- Omron
IPv4 address Defines the IP address of the PLC to be connected. The address format is decimal, e.g. 192.168.1.10. Communication path Set the CIP path from the Ethernet module to the PLC. This is used to establish a logical connection between the Ethernet module and PLC, even if the two devices are in different CIP networks.The communication path describes a series of point-to-point hops. The rules for setting up the path are as follows: - The starting point is the IP address of the first PLC Ethernet module to connect to this is part of the Edge connection configuration, not the path.
- Backplane slots are numbered left-to-right starting at 0.
- Path fields are separated with commas (except for IP and DH+ addresses).
- No brackets, angle-brackets, or spaces are allowed.
- All numbers are in decimal.
- Multiple Ethernet hops are not supported.
- Looping paths are not supported (such as exiting through the same interface the request came in on).
- Start with 1, which means "get to the backplane", following by a comma and number 0-15 for the next slot-number to go to. If this is a local path and for example your CPU is in slot 0, then a path of 1,0 is all you need. Otherwise, specify the slot number of the interface module you wish to exit the chassis.
To exit the chassis via an Ethernet module: Use,18or,19for the card’s A or B port (Use,18for a single-port card) followed by,a.b.c.dwherea.b.c.dis the IP address of the remote Ethernet module (Use dots, not commas, in the IP address).
To exit the chassis via a DH+ module:
Use,2or,3for DH+ A or B port, followed by,Destination node numberof the remote DH+ module (octal must be converted to decimal)
Use,1to get back to backplane of rack., slot numberto denote the position of the PLC in the rack. Example paths:
- Simple path within a single chassis to connect directly to a CPU module in slot 0:
1,0 - Multiple chassis with Ethernet
First chassis: Entrance Ethernet module at IP10.0.1.100, exit module in slot 5.
Second chassis: Entrance Ethernet module at IP192.168.254.123, CPU in slot 2.
Path:1,5,18,192.168.254.123,1,2
This path goes into the first Ethernet module, routes to the backplane, and exits through the module at slot 5 using its Port A. From there it goes into the remote chassis Ethernet module at192.168.253.123, then out to the backplane, and finally to the CPU module in slot 2
Routing via DH+ Bridge
Enter via Ethernet, exit via DH+ to a remote CPU:
Path:1,3,2,8,1,0
A connection via ControlNet
The communication path must be selected according to the following explanation:
An example communication path:1,1,2,1,1,0
1- From the ENBT to the backplane
1- To a CNBR in slot 1
2- Out of the CNBR to the ControlNet
1- To device address 1 on the ControlNet
1- To the backplane of the remote rack
0- To the PLC located in slot 0
- Simple path within a single chassis to connect directly to a CPU module in slot 0:
* Indicates that all fields are mandatory.
-
Click Save.
Result
The data source is added and it appears in the Tags page.