Parameterize via Mailbox Function:
7 Parameterize via Mailbox Function:
IO-Link Device parameters are accessed via the ISDU Access Object 768d.
This object exists in both the CPX-FB36 and the CTEU-EP. It is handled exactly the same in either case.
Informationen
“ISDU-Access” (Index Service Data Unit Access) is the mechanism used for accessing data objects in all IO-Link devices.
The parameters are device specific, and can be both read / write. The user shall use a MSG instruction to access these parameters. This is known as the “Mailbox Function”. Since the MSG instruction must use the source element for the index number, one index at a time can be accessed.
The following tables show the general Mailbox Function message instruction requirements:
Parameter Value Description
Message Type CIP Generic
Service Type Custom
Service Code
Class
Instance
32 h / 50 d
300 h / 768 d
1-2
CIP-specific message
Write access to single CIP attribute -> Service Code “10h”
Read ISDU
CIP-Class-ID for vendor specific „ISDU Access Object“
Port where device is connected
Attribute 0-9 or
0
Source Element Tag of user defined type
CPX slot number of CPX-CTEL-LK module or
0 in case of CTEU-EP
Data Order of user defined data-type:
Index (INT) 0...65535
Subindex (SINT) 0...255
Source Length 3
Destination Element
Source Length is always “3” for read access.
Tag of SINT[1+n] Response to read access
Status (SINT)
Data 0(SINT)
Status / Errorcode of read request, see table below
Byte 0 read from device
Data 1(SINT)
Data n(SINT)
Byte 1 read from device
Byte n read from device
Table 7.1: Message Instruction for ISDU Access (read)
Parameter Value Description
Message Type
Service Type
Service Code
Class
Instance
Attribute
CIP Generic
Custom
33h / 51 d
300 h / 768 d
1-2
0-9 or
0
CIP-specific message
Write access to single CIP attribute -> Service Code “10h”
Write ISDU
CIP-Class-ID for vendor specific „ISDU Access Object“
Port where device is connected
CPX slot number of CPX-CTEL-LK module or
0 in case of CTEU-EP
Seite 18 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
Parameterize via Mailbox Function:
Parameter
Source Element Tag of user
Source Length
Destination Element
Value defined type
3 + “Length of
Data” Bytes
SINT
Description
Data Order of user defined data-type:
Index (INT)
Subindex (SINT)
Data 0 (write only)
0...65535
0...255
Data 1(write only)
Data n (write only)
Byte 0 of data to write to ISDU addressed by Index and Subindex
Byte 1 of data to write to ISDU addressed by Index and Subindex
Byte n of data to write to ISDU addressed by Index and Subindex
When writing 4 Bytes of data to an ISDU, then Source Length is 3+4=7
Bytes.
Response to write access
Status (SINT) Status / Errorcode of write request, see table below
Table 7.2: Message Instruction for ISDU Access (write)
Response Status Description
E5 h
E6 h
E7 h
E8 h
E9 h
FF h
0
E1 h
E2 h
E3 h
E4 h
Success
Write data length too long
Port unknown
Device busy
Write failed
Read failed
Read answer too long
State unknown
Port on master not support
Port in invalid state
Timeout
Table 7.3: Status- and errorcodes for read and write ISDU access
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 19 von 30
Parameterize via Mailbox Function:
We will use a commercially available IO-Link RFID tag reader model number BIS-4xx as an example with CTEU-
EP. Below are the device specific parameters that may need to be modified for proper operation.
Figure 7.1
Seite 20 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30