Fieldbus Gateway With Function Mapping for Component Interchangeability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional fieldbus systems struggle with adaptability to changing production requirements, especially when components from different manufacturers are used or when integrating new functions into existing industrial plants, leading to complex reprogramming and system shutdowns due to hardware and software mismatches.
Innovation Solution
A gateway system that uses function-based representations of components, allowing easy interchangeability and integration of components from different manufacturers by mapping their functions to virtual addresses, independent of their physical positions, using a data processing module and interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional fieldbus systems use hardware-based component mapping with fixed configurations, then system reliability and error detection are improved, but adaptability to changing production requirements and component interchangeability deteriorate
Solution Approach 1:
The patent introduces a configuration server as an intermediary between the controller and field devices. This server manages configuration data independently from the controller's runtime operation, allowing configuration changes to be made without affecting system reliability. The configuration server acts as a mediator that decouples the rigid hardware mapping from the flexible configuration management, enabling adaptability while maintaining reliable controller operation.
Solution Approach 2:
The system performs preliminary configuration actions by pre-defining configuration data in the configuration server before runtime. Configuration templates and device parameters are prepared in advance, allowing rapid adaptation when production requirements change. This preliminary setup enables the system to maintain reliable hardware mappings during operation while allowing flexible reconfiguration when needed.
2Reliability
If the system uses fixed hardware configurations with all endpoints expected to be present, then error detection and system stability are improved, but ease of modification and component replacement deteriorate
Solution Approach 1:
The configuration server serves as an intermediary that separates error detection functionality from the fixed hardware configuration. It maintains the expected configuration structure for error detection while allowing the actual deployed configuration to differ. This enables the system to detect configuration errors reliably while simultaneously making modification easy through the configuration server's flexible data management.
Solution Approach 2:
The system uses configuration templates as copies or representations of ideal device configurations. These templates define the expected structure and parameters for error detection, while the actual device configurations can be instantiated from these templates with modifications. This copying approach allows error detection based on the template structure while enabling easy customization and modification of actual device configurations.
3Adaptability or versatility
If components from different manufacturers with different data interfaces are used, then versatility and adaptability are improved, but device complexity and reprogramming requirements worsen
Solution Approach 1:
The configuration server provides a universal interface for managing configurations of diverse field devices from different manufacturers. It implements a standardized data model that can represent various device types and interfaces uniformly, allowing the controller to interact with all devices through a common configuration structure. This universality enables component interchangeability while hiding the underlying interface differences, thus not increasing device complexity.
Solution Approach 2:
The configuration server acts as an intermediary layer between the controller and heterogeneous field devices. It translates between the controller's unified configuration requests and the specific data interfaces of different manufacturers' devices. This mediation allows versatile use of different components while preventing interface complexity from propagating to the controller level.
4Speed
If the controller directly maps and addresses all field level components, then communication speed and system simplicity are improved, but adaptability to modular configurations and brownfield integrations deteriorate
Solution Approach 1:
The configuration server is introduced as an intermediary for configuration management while maintaining direct controller-to-device communication paths for runtime operations. This allows the system to preserve fast direct communication during operation while using the configuration server for adaptive configuration management in modular and brownfield scenarios. The intermediary handles configuration complexity without interfering with runtime communication speed.
Solution Approach 2:
The system segments configuration management functions from runtime communication functions. The configuration server handles configuration data management separately from the controller's real-time communication with field devices. This segmentation allows the controller to maintain fast direct communication while the configuration server provides adaptability for modular configurations and brownfield integrations through independent configuration management.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
The invention relates to a gateway for a fieldbus system (12) for connecting a controller (18) to an industrial plant (10) which has a plurality of different components (16).The gateway (34) comprises at least one component interface (36) via which the different components (16) can be connected simultaneously or sequentially, a control interface (38) to which a controller (18) of the industrial plant (10) can be connected, and a data processing module (40) configured to identify the at least one component (16) by means of an assigned hardware address and to communicate with the at least one component (16) via the component interface (36) when at least one of the components (16) is connected to the at least one component interface (36), and configured to communicate with the controller (18) when the controller (18) is connected to the control interface (38) and to represent the at least one component (16) to the controller (18) as a function-based representation (42). The invention further relates to a fieldbus system (12).