29
V01.0| 2017/04
TBPN-L1-FDIO1-2IOL - Standard IO-Link
4 IO-Link – Functions for Acyclic Communication
The acyclic access to the data of IO-Link devices is realized via IO-Link CALLs.
Therefore it is necessary to distinguish bet
ween data of an IO-Link master or of an IO-Link device.
The addressing of the IO-Link CALL is realized via
the Entity_Port. It defines which device is
addressed via the CALL:
Entity_Port 0 = IO-Link master module
(IOLM)
Entitiy_Port 1 = IO-Link device at
1st IO-Link channel (IOL1)
Entitiy_Port 2 = IO-Link device at
2nd IO-Link channel (IOL2)
4.1 Port Functions for Port 0 (IO-Link Master)
IO-Link-Index (Port function invocation)
The access to the IO-Link master-functions (Port 0) is done via index:
65535
4.1.1 Subindex 64: Master Port Validation Configuration
This object serves for writing a defined configuration of the devices to be connected to the IO-Link
port into the master. The master stores the data for the IO-Link device expected at the port and only
accepts a device at the port which has exactly the same data (Vendor-ID, Device-ID and Serial Num-
ber).
The usage of Master Port Validation Configuration is only reasonable if the parameter Mode is set
to a value 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 w max. 48 Bytes
Struture of the command IOL_Port_Config:
Content Size Format Comment
IOL1 VENDOR_ID 2 Bytes Unsigned 16
DEVICE_ID 4 Bytes Unsigned 32
FUNCTION_ID 2 Bytes Unsigned 16 Value: 0
SERIAL_NUMBER 16 Bytes String
IOL2 VENDOR_ID 2 Bytes Unsigned 16
DEVICE_ID 4 Bytes Unsigned 32
FUNCTION_ID 2 Bytes Unsigned 16 Value: 0
SERIAL_NUMBER 16 Bytes String
To Next Page
Loading...
Need help?
General
