Gateway Communication Interface Module for Multi-Protocol Field Device Parameterization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing automation systems lack complete parameterization of field devices connected to gateway devices via high-performance Ethernet buses or Profibus, requiring additional interfaces and configurations that are not fully integrated.
Innovation Solution
A system and method that utilize a communication interface module to generate sub-blocks from a data structure stored in a device description file, transmitting and combining these sub-blocks to form a single configuration block, which is then loaded into a field bus master stack and transmitted to field devices via different communication links, enabling parameterization across multiple field bus protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If additional interfaces (RS232, RS422, RS485, USB) are integrated in the gateway device for parameterization, then field devices can be parameterized, but device complexity and cost increase
Solution Approach 1:
The gateway device's communication interface is designed to handle multiple field bus protocols (CAN, CANopen, Profibus, EtherNet/IP) through a single integrated high-performance bus connection, eliminating the need for multiple dedicated interfaces. This multi-functional approach allows the same hardware interface to serve different parameterization needs across various protocols.
Solution Approach 2:
The parameterization functionality is extracted from the gateway device itself and relocated to the control unit. The control unit generates configuration data and transmits it to field devices through the gateway, separating the parameterization function from the gateway's core communication function and reducing the gateway's interface requirements.
2Reliability
If additional interfaces are integrated in the gateway device, then complete parameterization is achieved, but device costs increase
Solution Approach 1:
A single high-performance bus interface is designed to support multiple field bus protocols, allowing the gateway device to parameterize different types of field devices (CAN, CANopen, Profibus, EtherNet/IP) through one universal connection rather than requiring separate dedicated interfaces for each protocol type.
Solution Approach 2:
The gateway device acts as an intermediary that translates configuration data from the control unit into protocol-specific parameterization commands for field devices. This mediator role allows complete parameterization functionality to be achieved through software/firmware processing rather than through additional physical interfaces.
3Speed
If field devices are connected via high-performance Ethernet bus, then communication speed is improved, but parameterization capability is limited
Solution Approach 1:
The communication system is segmented into two functional layers: a high-speed data transmission layer using Ethernet for real-time control data, and a parameterization layer using protocol-specific communication patterns for device configuration. This segmentation allows both high-speed operation and complete parameterization capability to coexist.
Solution Approach 2:
The system changes communication parameters dynamically based on the operational mode. During normal operation, high-speed Ethernet communication is used for real-time data exchange. During parameterization operations, the communication interface switches to support lower-speed protocol-specific parameterization commands while maintaining the same physical connection.
Data Source
AI summary
A system for parameterizing field devices of an automation or control system includes a higher-ranking unit, which is connected via a first communication link based on a first field bus protocol to a communication interface module. The module is connected via a second communication link based on a second field bus protocol to at least one field device. In the higher-ranking unit, sub-blocks are generated and stored from a data structure for configuring the field device that is stored in a device description file for the field device. A first network service transmits the parameters of the field device from the higher-ranking unit via the first communication link into a first functionality of the module that operates as a slave function. A further functionality integrated into the module evaluates parameters of the field device that are stored in sub-blocks and combines the parameters to form a single configuration block.