V01.00 | 2019/10
111
9.2 IO-Link functions for acyclic communication
The acyclic access to the data of IO-Link devices is realized via IO-Link CALLs. A distinction must
be made between data of the IO-Link master (IOLM) and data of connected IO-Link devices
(IOLD).
The addressing of the IO-Link CALL defines which device is addressed via the CALL:
The addressing is defined by the so called Entitiy_Port:
n Entity_Port 0 = IO-Link master module (IOLM)
n Entity_Port 1 = IO-Link device at IO-Link port 1
n …
n Entity_Port 4 = IO-Link device at IO-Link port 4
9.2.1 Port functions for Port 0 (IO-Link Master)
IO-Link Index (port function invocation)
The access to the IO-Link master functionalities (port 0) is done via index 65535:
Subindex 64: Master Port Validation Configuration
The object writes a specific configuration of the Devices to be connected to the IO-Link port to
the Master. The master stores the data for the The IO-Link device expected at the port and then
accepts only one device at the port with exactly matching data (vendor ID, device ID and serial
number).
The Master Port Validation Configuration is only useful in combination with an operation mode
with validation (IO-Link with family compatible device, IO-Link with compatible device, IO-
Link with identical device.
Entity_Port IO-Link sub index Read/write Length
0 64 Write Max. 96 byte
Structure of the command IOL_Port_Config:
Content Size Format Comment
IOL1 VENDOR_ID 2 byte Unsigned 16
DEVICE_ID 4 byte Unsigned 32
FUNCTION_ID 2 byte Unsigned 16 Value: 0
SERIAL_NUMBER 16 byte String
IOL2 VENDOR_ID 2 byte Unsigned 16
DEVICE_ID 4 byte Unsigned 32
FUNCTION_ID 2 byte Unsigned 16 Value: 0
SERIAL_NUMBER 16 byte String
IOL3 VENDOR_ID 2 byte Unsigned 16
DEVICE_ID 4 byte Unsigned 32
FUNCTION_ID 2 byte Unsigned 16 Value: 0
SERIAL_NUMBER 16 byte String
IOL4 VENDOR_ID 2 byte Unsigned 16
DEVICE_ID 4 byte Unsigned 32
FUNCTION_ID 2 byte Unsigned 16 Value: 0
SERIAL_NUMBER 16 byte String
To Next Page
Loading...
