The SIG200 Sensor Integration Gateway is an IO-Link master for integrating IO-Link devices into common PLC environments and enterprise level systems. With the SIG200, digital inputs, digital outputs or IO-Link signals of several devices can be detected, combined, evaluated and transmitted via various fieldbus protocols. A second data channel is also available for higher-level processing via a REST-API. Parameterization is done via a web server or the SOPAS ET configuration software from SICK. Among other things, SOPAS ET contains a powerful logic editor. It creates unique logic combinations for the respective application - regardless of the programmable logic controller.
At a glance
4 configurable IO-Link master ports (standard I/O or IO-Link)
Easy parameterization via USB or Ethernet thanks to intuitive SOPAS ET user interface
“Dual Talk”: Access to sensor data from the company level and in parallel via industrial Ethernet
Solution of complex application tasks with the logic editor
Drag & drop logic
A powerful logic editor integrated into SOPAS ET enables the creation of unique sensor systems. Visualize all linked signals and solve your application tasks quickly and easily with pre-defined logic gates (e.g. AND gates, OR gates), a negation module, time delays or a counter. Simply drag and drop logic modules and connection points to create your system. Access is established via the USB or Ethernet connection of the SIG200 using the SOPAS ET software. Alternatively, the integrated web server can be used.
With the SIG200, the connected sensor and actuator signals and measured values can be efficiently combined and aggregated via the drag-and-drop function of the logic editor. This is easy and problem-free without special software knowledge, which considerably reduces programming effort, therefore saving time.
Take advantage of advantages and extended functions - using Smart Sensors and IO-Link
The SIG200 Sensor Integration Gateway is an IO-Link master. It can be connected to various types of controls to access information of connected IO-Link devices and the aggregated system information created in the logic editor. IO-Link offers countless benefits, e.g. the automated storage of device parameters and unique device identification. An IO-Link device can be identified automatically via the device- and manufacturer-specific ID. This identification is used to ensure that the right device is used for device exchange. For quick and error-free commissioning, the device parameter of a certain sensor is automatically transmitted to a replacement device so that the correct parameterization is available after exchange.
As co-founder of IO-Link, SICK offers one of the broadest IO-Link portfolios on the market for numerous sensor types with all kinds of detection technologies. The SIG200 gateway enables the quick and easy connection of IO-Link signals, binary sensors and the construction of complex sensor-actuator systems. Utilize SICK’s extensive experience regarding a wide range of sensor principles as well as IO-Link technology.
An IO-Link is a point-to-point communication protocol for connecting intelligent sensors and actuators to an automation network via an IO-Link master, e.g. SIG200. It allows central access to information which was previously only available within the connected devices. The visualization and configuration of IO-Link devices is made much easier with the SIG200 and SOPAS ET - the configuration software from SICK.
Industry 4.0 – “Dual Talk”
The SIG200 enables two parallel communication channels: One to the PLC and one to the cloud. That’s what we call “Dual Talk“.
The edge computing channel is used for the fieldbus communication (e.g. PROFINET) with the PLC. The cloud computing channel is used for data transmission via EST-API (JSON) to the cloud or any other Industry 4.0 application.
This enables real-time communication with the PLC parallel to the communication with the cloud, e.g. for condition monitoring or predictive maintenance. Industry 4.0 is happening now.
„Dual Talk“ enables two parallel communication channels – communication to the control (via the fieldbus) and to cloud applications (via REST-API).