Diagnostic Reporting. Festo CTEU-EP, CPX-FB36, CPX-CTEL-LK

Diagnostic Reporting:

6 Diagnostic Reporting:

Both the CPX and CTEU can be programmed in advance to detect and report errors related to the IO-link channels and devices. This includes if a device is missing, changed, or faulted.

This is generally a 3 step process:

1. Write the specific information to a “Port Configuration Object” via an explicit message. The data will be the

Vendor ID and the Device ID plugged into each port.

2. Monitor general diagnostics provided by the CPX or CTEU either from the input table or status table.

3. Read specific error information from a CIP object via an explicit message.

The next chapters describe in detail how these 3 steps apply to CPX-FB36 und CTEU-EP.

6.1 CPX-FB36

6.1.1 Step 1: Set VendorID and DeviceID

Use the following table to write the specific device information to the FB36 IO-Link Port Configuration Object

140d.:

Parameter Value Description

Message Type

Service Type

Class

Instance

Attribute

CIP Generic

Set Attribute Single

8C h / 140 d

0-10

1-2

Source Element Tag of user defined type

(see details below)

CIP-specific message

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

CIP-Class-ID for vendor specific „IO-Link Port Configuration

Object“ to set IO-Link Device Type.

Slot number where CTEL-LK resides + 1

Possible Values: 1-10 d

Channel of Device (Port of CPX-CTEL-LK where device is connected)

Possible values: 1 – 2

Data Order of user defined data-type:

Master Cycle Time (SINT)

Comm_Error (SINT)

VendorID (INT)

DeviceID (DINT)

0 (Default)

0, 1

Device specific

Device specific

Source Length 8 Bytes

Table 6.1: CPX-FB36 Service code table to Write to IO-Link Port Configuration Object

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

Diagnostic Reporting:

Since this object requires access to a data structure, this example will show how to enter the service data for an

IO-Link device in the Rockwell Logix environment with a CPX-FB36 /CPX-CTEL-LK:

1. Create a user Defined Data Type to include these 4 variables:

Figure 6.1

2. Create Controller Tags to be used as a source and destination for a message instruction to write / read to the module. The variables are of the data type created. Load the source data with the appropriate data for the

IO-Link device.

3. Use a MSG instruction to load the data to the FB36 so the Vendor ID, Device ID, and choice to monitor the

Comm_Error are entered. Instance 6 means CPX module number 5, and attribute 1 is for CPX-CTEL-LK channel

1.

Figure 6.2

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