![Beckhoff EPI3 Series Скачать руководство пользователя страница 14](http://html1.mh-extra.com/html/beckhoff/epi3-series/epi3-series_documentation_2719368014.webp)
IO-Link basics
EPI3xxx, ERI3xxx
14
Version: 1.2
• If no connection could be established to the slave, or if the saved parameters differ from those read,
the corresponding error is output.
• If the saved parameters differ from those read, the IO-Link device changes to the PREOP state.
If the IO-Link device specification is V1.1, the
is now executed. If the IO-Link
device specification is V1.0, this step is omitted and the device changes directly to OP.
• Finally the cycle time is written and the device changes to OP. After that the master cyclically
exchanges data with the slave.
3.3
Device description IODD
IO-Link devices possess individual system information in the form of an IO device description (IODD), which
contains:
• Communication features
• Device parameters with value range and default values
• Identification, process and diagnostic data
• Device data
• Text description
• Picture of the device
• Vendor's logo
If the IODD is imported, then the device data are automatically detected during
with TwinCAT and adopted in the System Manager (cf. integration of the IO-Link devices).
3.4
Parameter server
In order to be able to use the functionality of the parameter server, both the IO-Link master and the IO-Link
device must be specified to V1.1. The IO-Link revision of the device can be read for the individual port under
. The Beckhoff IO-Link master supports specification V1.1 from FW 07.
• The parameter server in the IO-Link master contains parameter data that are saved in the IO-Link
device. The memory capacity is max. 2 kbyte (including header).
If the IO-Link-Device is exchanged, then the data are loaded from the parameter server into the new
device. The requirement for this is that the device is of the same type (VendorID & DeviceID must be
the same).
• If a new IO-Link-Device is configured, then the IO-Link master loads the parameters from the IO-Link-
Device into the parameter server when starting for the first time.
Data from other IO-Link devices that are already configured (VendorID & DeviceID do not correspond
to the configured device) are overwritten.
• At each further start the IO-Link master uses a checksum to check whether the data in the parameter
server correspond to those on the IO-Link-Device and if necessary downloads them to the device.
• If the parameters change during the device runtime, this can be reported via the Master's special
event. The master then starts the parameter server with an upload.
• By default the event is not set each time the parameters are written, therefore the end of the
parameterization procedure has to be reported to the IO-Link device.
The IO-Link-Device then sends the corresponding event to the master. The data are loaded into the
parameter server.
• In the case of a pre-programmed IO-Link-Device, no download takes place from the parameter server
to the device.
Содержание EPI3 Series
Страница 1: ...Documentation EPI3xxx ERI3xxx IO Link Box Modules with analog inputs 1 2 2018 07 10 Version Date ...
Страница 2: ......
Страница 12: ...IO Link basics EPI3xxx ERI3xxx 12 Version 1 2 Fig 3 IO Link overview Peer to peer communication ...
Страница 31: ...Commissioning configuration of IO Link master device EPI3xxx ERI3xxx 31 Version 1 2 Fig 28 IO Link tab ...