Table of Contents
Advertisement
750-1657
4.5 Local Bus Processing
Data exchange between the 4-Port IO-Link Master and connected devices is performed
cyclically via the IO-Link interfaces; having been processing accordingly, the data is
transferred via the local bus according to the source. Process input data is transferred be-
tween the controller and the I/O module.
You can find details on the use of certain fieldbuses in
[} 74].
The process image of the IO-Link master can be set to up to 48 bytes. The process im-
age is broken down into a control/status byte, Mailbox bytes, SIO bytes and an area that
is divided into up to four segments and used for the process input and/or output data of
the four IO-Link ports. If the segment size setting of a port is not sufficient to transfer the
data in one cycle, the data of the individual IO-Link devices can also be transferred via
the corresponding segment in fragmented form.
The controller can access parameters and data of the IO-Link master and the connected
IO-Link devices via the acyclic service. In this way, any number of parameterization pro-
cesses and backup procedures can be carried out from a controller at runtime.
4.6 Diagnostic Functions
4.6.1 Diagnostics via Mailbox 2.0
In addition to configuration and parameterization, the Mailbox is also used to transmit di-
agnostic messages.
Unless disabled, diagnostics of the connected IO-Link devices and those of the IO-Link
Master itself are transferred to the controller via the "IOL_DIAG" diagnostic service (see
8 Diagnostic Telegram
brary "WagoLib_IO_Link.lib" provides the required function blocks to process the diag-
nostic messages.
The basic structure of the diagnostic telegram depends on the functional profile for IO-
Link, which is defined in IO-Link Specification V1.1.3. Diagnostics are transferred via
Mailbox using the "IOL_DIAG" diagnostic service.
For diagnostic purposes, the IO-Link master provides FIFO memory for 40 diagnostic
messages. "FIFO" describes storage in which the first element in the queue (first in) is
processed first (first out). If the memory is filled with one or more diagnostic telegrams, di-
agnostic telegrams are sent until the FIFO is empty. Confirmation from the controller is
not required. In the event of overflow, the I/O module discards incoming diagnostic tele-
grams.
You can find further information on how Mailbox 2.0 works and sample applications at
8 Communication Services of the IO-Link Master
4.6.2 Diagnostics via IO-Link
In IO-Link, errors and events are displayed in the form of a value of type "UNSIGNED16".
In addition to default values, device manufacturers are also allowed to use device or
manufacturer-specific event codes according to the IO-Link standard.
Product manual | Version: 1.1.0
4-Port IO-Link Master
[} 29]) of the Mailbox to the controller. The WAGO-I/O-PRO li-
8 Fieldbus-Specific Additions
[} 39].
Functions
23
Advertisement
Chapters
Table of Contents
