Methods for Validating the IO-Link Configuration. Festo CTEU-EP, CPX-FB36, CPX-CTEL-LK

Methods for Validating the IO-Link Configuration

5 Methods for Validating the IO-Link Configuration

For a customer to validate a configuration, he must retrieve the vendor and device ID manually via an explicit message. This will assure the correct device is connected to an IO-link port.

5.1 CPX-FB36

For the FB36, the General Object Parameter Object 101d will be used. This currently exists in the CPX system since these values are stored as parameters from the CTEL-LK. An explicit message to Object class 101 with the correct instance and attribute based on the channel & slot number will work.

Figure 4: This ladder example will retrieve the Vendor ID of a device in port 2 of the CTEL-LK plugged into the

5th CPX slot.

Parameter Value Description

Message Type

Service Type

Class

Instance

Attribute

CIP Generic CIP-specific message

Get Attribute Single Read only access to single CIP attribute -> Service Code “e”

65 h / 101 d

6 d

CIP-Class-ID to access CPX-Parameter-Object

Slot number where CTEL-LK resides + 1

Possible Values: 1-10 d

In the example a value of 6d means CPX module number 5

73 h / 115 d Service-Data: Vendor ID Port 2, Word

Possible Values Service Data

71 h / 113 d

73 h / 115 d b5 h / 181 d b8 h / 184 d

7b h / 123 d

7d h / 125 d

Vendor ID Port 1, Word

Vendor ID Port 2, Word

Device ID Port 1, DWord*

Device ID Port 1 DWord*

Errorcode Port 1, Word

Errorcode Port 2, Word

*Mask MSB when accessing Device ID

Table 5.1: Service code table to Read Device Type and Vendor ID to CPX-FB36

Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 11 von 30

Methods for Validating the IO-Link Configuration

5.2 CTEU

First, each of the CTEU ports must be set to allow 3 rd party IO-link devices. Use the CTEU

Port Configuration Object 107d. The details are as follows:

Parameter Value Description

Message Type

Service Type

Class

Instance

Attribute

CIP Generic CIP-specific message

Set Attribute Single Write access to single CIP attribute -> Service Code “10h”

6B h / 107 d Vendor-specific object for IO-Link Ports

1, 2

5

Port 1 or 2

(Port 2 only available when using CAPC Adapter)

Service-Data: IO-Link support, SINT

Possible Values Comment

0

1

Disable IO-Link Support (Default)

Enable IO-Link Support for 3 rd Party

Table 5.2: CTEU Service code table to Set IO-Link mode

Next, the CTEU Slave Information Object 104d will be used. This object stores device information for each of the

2 CTEU ports. An explicit message to Object class 104d with the correct instance and attribute based on port 1 or

2 will allow the user to retrieve the Vendor or Device ID.

Parameter Value Description

Message Type

Service Type

Class

Instance

Attribute

CIP Generic

Get Attribute Single Read only access to single CIP attribute -> Service Code “e”

68 h / 104 d

1, 2

6

2

CIP-specific message

CIP-Class-ID for Slave-Information-Object

Port 1 or 2

(Port 2 only available when using CAPC Adapter)

Service-Data: Vendor ID,

Possible Values Service-Data:

6

2

Vendor ID, 2 Bytes (UINT)

Device ID, 3 Bytes (DWord)*

*Mask MSB when accessing Device ID

Table 5.3: Service code table to Read Device Type and Vendor ID from CTEU-EP Slave Information Object

Seite 12 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30