End users and everybody interested in reliable solutions for device integration including device manufacturer and system vendor staff.


Device manufacturer searching for cost efficient deivce integration or for support in the development of tailored solutions.

Interoperability Partner

System or tool vendors with the wish to offer a generic integration solution as part of their existing solutions.



Communication protocols mainly used in the process industry. Please choose from the list below. You may combine aspects from different tabs of the solution finder in order to find the best match!







by Jill Stark on 5. July 2018 in General

Access the data you need – with Remote I/O systems or field gateways via Ethernet for IIoT

Imagine you are working in the process industry on a food industrial plant. In your daily work you are confronted with IIoT and Industry 4.0 which promise many advances for process and performance optimization in manufacturing, but at the moment there is no solution to acquire data from sensors and actuators in the production plants. This lack of solution affects your work as you have to let data unused, because the HART devices are connected with 4-20mA analogue signals. Therefore, besides the process values, you are not able to access all the additional dynamic values as well as device specific diagnostics information. However, this information would be very useful for anomaly detection and predictive maintenance.


You are looking for a new solution as the available solutions do not provide standardized open interfaces to access device data or are not suited for permanently reading data from many devices.

Stop searching – There is a solution for your described problem. CodeWrights software is running on an IIoT edge device that is connected via Ethernet to remote I/O systems or field gateways. The connected HART field devices are scanned and detected within a few seconds.  Based on the information from EDDs or FDI Device Packages, a device information model is created automatically for each device and includes all device variables of the individual device type. The device models are mapped to an OPC-UA information model according to the OPC-UA for Devices companion specification and the FDI Information Model for process automation.


With this “Plug-and-Play Integration” you can now access the device information from any OPC-UA client. How does it work? A cloud agent connects the OPC-UA server with an IIoT platform which can be hosted in a public or private cloud. In your cloud application, you can directly access all the device variables. Once you have selected a set of variables, this information is transferred back to the cloud agent which then subscribes to the variables in the OPC-UA server. Hence, the selected variables are read periodically from the devices and published to the cloud. This really is plug-and-play integration of device data into your cloud applications for monitoring and optimization as it does not require engineering efforts to get the device specific data. The solution is also in-line with the proposed NAMUR Open Architecture (NOA) as it realizes a second communication channel and ensures read-only access via OPC-UA as well as secure connectivity and data encryption.


A product study, about the described solution, has been shown at ACHEMA fair this year together with our partners Pepperl+Fuchs and Neoception. In this product study, an industrial PC acting as edge device is connected to a new Pepperl+Fuchs Remote I/O system via HART/IP and HART devices from different manufacturers. A cloud agent connects the OPC-UA Server to Microsoft Azure IoT Hub. The application by Neoception demonstrates the easy access to the device data. The edge device software can run on different hardware platforms and operating systems such as Linux and Windows IoT.


For more information, please contact

Dr. Michael Gunzert,

No comments

Leave a Reply