Digitalization, Industry 4.0, the smart factory or the Industrial Internet of Things (IIoT) - the implementation of these trends requires data above all else. IO-Link point-to-point communication is an ideal channel for providing such data, usually measured values, parameter settings and device information.
The fieldbus-independent IO-Link devices reduce the large number of different I/O types in a machine to one IO-Link master, transmit data digitally and provide additional diagnostic information. They are connected via standard sensor cables. They communicate bidirectionally, meaning they can be parameterized and read out at runtime. All of this opens up a wide range of application functionalities - be it production in batch size 1, the locking of operating elements or the provision of pre-processed data. Intelligent sensors can even perform so-called smart tasks independently - for example counting or measuring lengths - and provide this information via IO-Link. More and more field devices - especially those that do not offer space for Ethernet - have the interface on board. Several hundred IO-Link devices in a machine line are no longer a rarity.

Closing integration gaps

'FieldEcho' parameterizes and monitors all IO-Link devices in a system and provides a web-based graphical user interface.

© Sick

Sick has developed the 'FieldEcho' software tool with the aim of closing any remaining integration gaps, making the use of IO-Link devices as simple and resource-saving as possible and at the same time making IO-Link data available for Industry 4.0 applications in a standard IT manner. It offers full access to all IO-Link device data at any time, allowing it to be called up, monitored or changed via a browser or a Human Machine Interface (HMI). The device descriptions (IODD) of the connected IO-Link devices recognized by 'FieldEcho' are automatically downloaded and made available at the ports of the configured IO-Link masters. This eliminates the need for manual downloads.
As communication is system-independent, it is possible via different PLCs, fieldbuses and IO-Link masters. This requires hardly any development effort, as the machine manufacturer's software developer only has to write a single line of PLC code that calls the generic function block supplied with 'FieldEcho' to send read or write requests to the IO-Link devices. Controllers from Beckhoff, Mitsubishi, Rockwell Automation and Siemens are currently supported.

For read and write data access, the software tool communicates with the machine PLC via OPC UA or TCP/IP. A REST API is also on board, which is used to send and receive data in JSON format. This allows IO-Link device data to be transferred to ERP and MES systems as well as cloud-based services in order to use the data in the Industry 4.0 world for data analysis, predictive maintenance or inventories, for example.

Clearly visualized

'FieldEcho' provides direct access to the process and service data of all IO-Link devices and warns or alerts autonomously in the event of an anomaly.

© Sick

The tool's graphical, web-based user interface can either be opened with a browser or integrated into the HMI of a machine or system. In the system and IO-Link master overview, it visualizes all configured IO-Link masters as well as the automatically detected IO-Link sensors and actuators connected to the respective ports. It also clearly displays the status of all IO-Link devices. It is also possible to open a device page in the software so that users can zoom in on the device data. This view displays the device identification with information such as the serial number or software version as well as the device name and image. Incoming and outgoing process data are visible at a glance. The graphical user interface also offers the option of fully parameterizing all IO-Link devices. The tool thus ensures transparency by allowing the operator to view the entire IO-Link system on his screen like an open book. Machine builders and system integrators save time and reduce the workload on the PLC.