Fieldbus Gateway With Function-Based Device Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing industrial plants face challenges in adapting to rapidly changing production requirements due to the use of modular components with different manufacturers and fieldbuses, leading to complex program changes and downtime when components are replaced or modified, especially in brownfield plants integrating IoT connections.
Innovation Solution
A gateway system that uses function-based representations of components, allowing easy integration and interchangeability by assigning virtual addresses to components, independent of their physical structure, and providing a data processing module to communicate with controllers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If components from different manufacturers with different interfaces are used, then adaptability and versatility are improved, but device complexity and difficulty of integration increase
Solution Approach 1:
The gateway serves as an intermediary device between the controller and components from different manufacturers. It translates between different component interfaces and the unified controller interface, enabling components with different physical interfaces to be integrated without increasing controller complexity. The gateway handles the adaptation layer that maps various component protocols to the standard fieldbus protocol.
Solution Approach 2:
The gateway provides a universal interface that can connect to multiple types of components from different manufacturers. Instead of requiring the controller to have multiple specialized interfaces, the single gateway device performs multiple functions: protocol translation, address mapping, and device abstraction, making the system universally compatible with diverse components.
2Adaptability or versatility
If hardware configuration is adapted for each machine with modular components, then adaptability is improved, but loss of time for reconfiguration increases
Solution Approach 1:
The gateway creates a virtual copy or abstraction of the component configuration that is independent of the physical hardware. Instead of reprogramming the controller for each hardware change, the gateway maintains a mapping between the virtual configuration and actual physical components, allowing rapid reconfiguration by updating the gateway's internal mapping rather than the controller's hardwired configuration.
Solution Approach 2:
The system performs preliminary configuration by pre-defining the virtual device representations and their expected functions in the gateway. When physical components are connected, the gateway automatically detects them and maps them to the pre-defined virtual configurations, eliminating the need for time-consuming reprogramming of the controller for each new component arrangement.
3Measurement precision
If traditional hardware configuration with explicit component representation is used, then measurement precision of component status is improved, but device complexity increases
Solution Approach 1:
The gateway extracts the complexity of component representation from the controller by creating independent virtual device representations in itself. Each component is represented as a virtual device with standardized data structures in the gateway, separating the precise status detection function from the configuration management function. This allows the controller to work with simplified abstract representations while the gateway handles the detailed component modeling.
Data Source
AI summary
A gateway for a fieldbus system for connecting a controller to an industrial plant having a plurality of different components. The gateway includes at least one component interface via which the different components can be connected simultaneously or sequentially, a control interface to which a controller of the industrial plant can be connected, and a data processing module which, when at least one of the components is connected to the at least one component interface, is configured to identify the at least one component on the basis of a hardware address assigned thereto and to communicate with the at least one component via the component interface, and which, when the controller is connected to the control interface, is configured to communicate with the controller and to represent the at least one component with respect to the controller as a function-based representation. Furthermore, a fieldbus system is described.