Beckhoff EPI3 Series, Documentation

Page: 13 / 98

IO-Link basics
EPI3xxx, ERI3xxx 13 Version: 1.2
The connected IO-Link devices have individual parameter information, which is detected during automatic
scanning with TwinCAT and transferred to the System Manager (see chapter "Basic function principles",
integration of IO-Link devices). Module-specific information can be imported offline in the form of an IO-Link
Device Description (IODD) and transferred to TwinCAT.
• How to manually configure (physically non-existent) IO-Link masters and devices in TwinCAT is
described under the following two links: Offline configuration settings - TwinCAT (master) [
}
26] , 1.
Importing the device description IODD [
}
53]
• How to configure physically existent IO-Link masters and devices in TwinCAT is described under the
following two links: Online configuration settings - TwinCAT (master) [
}
32] , 2. Automatic scanning of
the IO-Link ports [
}
56]
3.2 Establishment of IO-Link communication
Establishment of IO-Link communication
The establishment of the IO-Link communication is illustrated in Fig. Establishment of IO-Link
communication. This illustrates in particular the sequence when automatically scanning [
}
56] the IO-Link
port.
Fig. 4: Establishment of IO-Link communication
• If an IO-Link device is connected to a master port, the master attempts to establish communication. A
defined signal level, the WakeUp pulse , signals to the slave that UART bytes are to be sent from now
on.
From this point on, all data will be interpreted by the IO-Link slave as UART bytes.
• The master runs through all baud rates [
}
15] , starting with the fastest baud rate (COM3 = 230
kbaud). A successful connection has been established when the slave responds to the WakeUp pulse.
• First of all the master reads the basic parameters (Vendor ID, Device ID, process data length,
telegram type and cycle time) and compares them with the existing configuration.