Step 2: Monitor Diagnostics. Festo CTEU-EP, CPX-FB36, CPX-CTEL-LK

Diagnostic Reporting:

4. The data can be read in a similar manner using a Get Attribute Single service type in a separate MSG instruction. Copy the data to a destination element of the same data type.

6.1.2 Step 2: Monitor Diagnostics

Monitor basic CPX diagnostics, a fault with bits 3 (fault at function module) and 7 (other fault) of the CPX diagnostic byte should occur.

6.1.3 Step 3: Read Specific Error Information

Use the General Module Parameter Object 101d to read the specific error codes form the CPX-FB36 / CPX-CTEL-

LK. This is the same object as used to validate the IO-link device, however, in this case, use an explicit message to read attribute 7B or 7D for specific error codes of port 1 or 2 respectively.

Parameter Value Description

Message Type

Service Type

Class

Instance

Attribute

Source Element

CIP Generic CIP-specific message

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

65 h / 101 d CIP-Class-ID to access CPX-Parameter-Object

6 d

73 h / 115 d

Slot number where CTEL-LK resides + 1

Possible Values: 1-10 d

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

Service-Data: Vendor ID Port 2, Word

Tag

Possible Values

71 h / 113 d

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

7b h / 123 d

7d h / 125 d

Service Data

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

Datatype of Tag Source Length Attribute

VendorID

ErrorCode

DeviceID

INT

INT

DINT*

2

2

4

Table 6.2: Service code table to Read Error code from CPX-FB36

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