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

Asset Management

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 for an industrial food plant. In your daily life, you work with IIoT and Industry 4.0. These promise many advantages for process and performance optimization in manufacturing.

However, at the moment, there is no solution for acquiring data from sensors and actuators in the production plants. This  affects your work, as you have to leave data unused because the HART devices are connected with 4-20mA analogue signals. Besides the process values, you cannot 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.

What is the solution ?

The available solutions do not provide standardized open interfaces to access device data, nor can they permanently read data from many devices. So you look for a new solution…Your search ends here. There is a solution that addresses exactly this problem. CodeWrights software runs on an IIoT edge device connected via Ethernet to remote I/O systems or field gateways, and scans and detects the connected HART field devices within a few seconds. 

Connecting Field Device

The information from EDDs or FDI Device Packages helps create a device information model automatically for each device. This includes all device variables of the individual device type, and maps the device models 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, and hosts this 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.

This way, the selected variables are read periodically from the devices and published to the cloud. This is really 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.

Connecting any Field Device with PF,Neoception,CW Logos

The solution is also in-line with the proposed NAMUR Open Architecture (NOA). This is because it realizes a second communication channel and ensures read-only access via OPC-UA. It also secures connectivity and data encryption.

Together with our partners Pepperl+Fuchs and Neoception, we showed a product study about the described solution at ACHEMA fair this year. In this product study, an industrial PC acting as edge device connects 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.

 

Related tags: Article Asset Management Codewrights English iDTM-EDD Intermediate Principal Software Solutions
Comments
Access the data you need - with Remote I/O systems or field gateways via Ethernet for IIoT
What is chlorine and why do we measure it?
Everything you need to know about wireless communication
#WishIknew – How do I measure dissolved oxygen in liquids?
#WishIknew - How do I find solution's concentration with conductivity sensors?
See related devices