Publish-Subscribe Field Communication for Multi-Protocol Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing process control systems face complexity in integrating advanced communication protocols like Ethernet and IP-based protocols with traditional field devices, leading to cumbersome communication setups and reduced effectiveness due to the need for multiple I/O devices and precise mapping of physical and logical connections, which hampers efficient data exchange and prioritization of communications.
Innovation Solution
A highly versatile field device capable of operating as a data server, supporting multiple applications and protocols, and communicating directly with various client devices using a common communication network infrastructure, including IP-based protocols and Advanced Physical Layer (APL) networks, enabling simultaneous communication with different client devices and systems while performing standard process control functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple specialized I/O devices are used to support different communication protocols, then protocol compatibility is improved, but device complexity increases
Solution Approach 1:
The field device is designed with multi-functionality to support multiple communication protocols (HART, Fieldbus, Profibus, Ethernet/IP, Profinet, Modbus) through a single device interface. The device can dynamically adapt to different protocols without requiring separate specialized I/O devices for each protocol, thereby reducing overall system complexity while maintaining broad protocol compatibility.
2Reliability
If precise mapping of physical and logical connections is implemented, then communication reliability is improved, but system complexity increases
Solution Approach 1:
The field device implements self-service through automatic device discovery and configuration capabilities. The device can autonomously identify itself on the network, obtain an endpoint identification from a DHCP server, and establish communication sessions without requiring manual precise mapping of physical and logical connections. This self-configuration process maintains communication reliability while eliminating the complexity of manual mapping.
3Productivity
If field devices communicate directly with multiple client devices, then data exchange efficiency is improved, but communication protocol complexity increases
Solution Approach 1:
The field device uses IP-based communication as an intermediary layer to enable direct communication with multiple client devices (process controllers, asset management systems, monitoring systems). The device implements a communication stack that handles protocol translation and session management, allowing efficient data exchange while abstracting the complexity of multiple protocol interactions from the application layer.
4Adaptability or versatility
If advanced protocols like Ethernet and IP-based protocols are integrated, then communication versatility is improved, but integration complexity increases
Solution Approach 1:
The communication architecture is segmented into distinct layers: the field device layer handles protocol-specific operations, the IP network layer provides standardized communication services, and the application layer handles protocol translation and data exchange. This segmentation allows advanced protocols like Ethernet and IP to be integrated without creating integration complexity, as each layer independently manages its own protocols and services.
Data Source
AI summary
A method and system for publish-subscribe communication architecture for highly-versatile (HV) field devices in control and automation system implements reception at an HV field device, from a client device or application, of a message indicating a selection of one of a plurality of publish categories. The publish category corresponds to a type of information desired by the client device or application. The field device transmits to the client device or application an identification of each of a plurality of publish lists corresponding to the selected publish category, which publish lists are each stored on the field device and each include a set of parameters associated with the field device. The field device receives, from the client device or application, a selection of one of the publish lists identified by the field device, and transmits to the client device or application the set of parameters associated with the selected publish list.