Ethernet/IP integration

Integration in RSLogix EIP development tool

Example of how the module can be integrated into the RSLogix EIP development tool:

1. Go offline.

   

2. Right click on Ethernet (the correct scanner card) and select New Module….

   

3. Select the Generic Ethernet Module as Ethernet module in the communication path.

   

4. Enter tag name (user-defined), select the general format Data SINT, enter the IP address of the module and the correct connection parameters and confirm with OK.

   

   ⇒ The new module and the corresponding controller tags are automatically generated.

   

5. Download the configuration with Download.

   

After the download is completed the tags can be monitored and activated using the Controller tags option.

The entry, output and configuration data are described on the following pages.

Integration

Data configuration

Enter the values from Data configuration in the control system. They describe the data sizes of the entry, output and configuration data.

Automatic IO-Link – Adjustable IO-Link process data length

The Ethernet/IP master offers a variety of configurations for IO-Link process data lengths, ranging from 0 to 32 bytes. The EDS file (Electronic Data Sheet) contains several predefined connections under the Connection Manager section. One of these connections is, for example, Connection2 with the name Exclusive Owner Connections – 32 IOL Data. A connection is a compilation of a configuration. Part of this is the definition of the data from the control unit to the device (O->T), the data from the device to the control unit (T->O) and the device configuration. These definitions can be found in the EDS file under the Assembly section. Assem101 (a consuming module with 32 bytes of IO-Link output process data) is used for Connection2 and the direction O->T. _Assem100 (a producing module with 32 bytes of IO-Link input process data) is used for the direction T->O and Assem102 is used for the configuration.

For example, if 10 bytes of IO-Link input and output data are required, the path 20 04 2C 73 2C 72 (hex)_can be used, where the assembly sizes are _T->O 216, O->T 86 and the configuration assembly is 0 or 58 bytes.

Configuration modules

The Ethernet/IP master contains two configuration assemblies for managing the IO-Link settings. These are Assem102 and Assem103, which each serve different purposes:

• Assem102: The assignment of this module is described in detail in the EDS file and can be configured to a size of either 58 bytes or 0 bytes. If it is set to 0 bytes, the existing configuration is retained and is not overwritten.

• Assem103: This module is set to a length of 0 bytes and was specially developed to automatically set all ports to IO-Link mode.

If the configuration module is not included in the connection path, the device operates as if module 103 is being used. This means that all ports are automatically set to IO-Link mode.

Configuration data

Assignment of configuration data sequence shows an assignment of the configuration data sequence. The stated standard values describe a configuration with the IO-Link function on Pin 4 and standard I/O functions on Pin 2 and 4 of every port. The input and output functions of the configured standard I/O ports are set using the process data.

Module configuration

IO-Link Port configuration

Cycle settings

With this parameter, the IO-Link communication speed can be set. The IO-Link cycle time can be increased calculated by the multiplier and the time base.

The time base is described in time base table, the multiplier is entered as a decimal number from 0…63.

Possible values for MasterCycleTime and MinCycleTime:

Validation settings

No validation : Validation deactivated, every device is accepted.

Compatibility : Manufacturer ID and Device ID are compared with the data of the IO-Link device.

Parameter server

Switched on : Data retention functions active, parameter data and identification data of the IO-Link device are saved in a remanent memory.

Switched off : Data retention functions deactivated, saved parameter data and identification data of the IO-Link devices remain in the memory.

Enable download : If only the download is enabled, in each case the master starts a download of the parameter data. In this case the download is also performed irrespective of the upload flag of the IO-Link device. If there are no data in the master port, an upload takes place first (e.g. after deletion of the data or before the first data upload). Upload and download enabled: If the upload and download are enabled, a distinction is made for different parameter records depending on the upload flag of the IO-Link device. If there are no data in the IO-Link master port, an initial upload takes place (e.g. after deletion of the data or before the first data upload). If the upload flag is set at the IO-Link device, the parameter data are uploaded in each case. If no upload flag is set and parameter data have already been stored, a download of the parameter data takes place in each case.

Values for validation type and parameter server

Upload flag at IO-Link device

The upload flag is required in order to overwrite data already saved in the parameter server with new parameter data of the same IO-Link device.

In order to activate the upload flag of an IO-Link device, the data value 0x05 must be entered in the index 0x02, subindex 0.

(For information on setting parameters via IO-Link, see I/O ports or IO-Link device parameterization.

Configuration via Explicit Messages

PLC program

Fault State

For each output at the port pins, a safe state can be predefined, which should be adopted in the case of a loss of bus communication.

The Fault State settings can be implemented via the following Class Instance Attribute of the Explicit Messages.

Activate / deactivate Fault State

Fault State Action

IO-Link device parameterization

There are two ways to parameterize an IO-Link device connected to the IO-Link Port.

• Parameterization via the web server (see I/O ports)

• Parameterization via Explicit Messages

The following section describes, for example, how via Rockwell RSLogix 5000 an IO-Link device can be parameterized via Explicit Messages.

The MSG modules are used in the PLC program (see MSG modules).

Read IO-Link parameters

Source Length must at least correspond to the read parameters, but can also be bigger (in this example 100 bytes).

1. As a Source Element (Write) and as a Destination Element (Read), create a SINT[100] Array and select the first row [0].

   

2. In the Source Element Array (Write) enter which index should be read (in this example Index 0x4E).

   

   ⇒ The read value is displayed in the Destination Element Array (Read).
   ⇒ The error code is also displayed there in the event of a parameterization error.

3. In the Communication window select the Ethernet module for which parameters should be set.

   

Write IO-Link parameters

1. Select Source Element and Destination Element as described in the example Values for read IO-Link parameters.

   The Source Length must be the same length as the parameter data to be written. In this example the index 0x4E, subindex 0, value 0x02 are written in the _Source Element Array (Write).

   In the event of a parameterization error an error code is displayed in the Destination Element Array (Read).

   

2. In the Communication tab select the Ethernet module for which parameters should be set.

   

Process data

Process data inputs

The input data have a size of 392 bytes. The table below shows the assignment of the process data inputs.

Standard input data

IO-Link input data

Process data outputs

The output data have a size of 262 bytes. The table below shows the assignment of the process data outputs.

Standard output data

IO-Link output data

Quick Connect mode

The following points must be observed in Quick Connect operating mode:

• Ethernet port settings

  • Ethernet port 1: The connection must be set to a fixed speed of 100 Mbit/s in full duplex mode.

  • Ethernet port 2: The connection must be set to a fixed speed of 100 Mbit/s in full duplex mode.

• Device configuration: Quick Connect mode must be activated.

Auto-MDIX is not available in Quick Connect mode. Therefore, the automatic configuration of the ports at fixed speed and activated Quick Connect is as follows:

• Port 1: MDI

• Port 2: MDIX

This configuration is crucial, as port 2 can be connected to port 1 of another device with a non-crossover cable, but not to port 2. If the connection is incorrect, no Ethernet connection (link) can be established.

For more information, see Ethernet/IP Specification Volume 2: EtherNet/IP Adaption of CIP, Appendix E: EtherNet/IP Quick Connect™.