Daisy-Chained Fieldbus Interfaces for Plant Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing process control arrangements for plants with multiple fieldbus systems require extensive cabling and complicated data addressing, as each fieldbus interface must be individually connected to the supervisory communication plane, leading to increased complexity and inefficiency, especially when dealing with different fieldbus types and the need for separate addressing and configuration.
Innovation Solution
A daisy chain arrangement where only the first fieldbus interface is directly connected to the supervisory communication plane, with subsequent interfaces connected in series, allowing for simplified communication and reduced cabling efforts, enabling a single address for multiple fieldbus systems and facilitating the integration of various fieldbus types without the need for additional switches or complex configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If each fieldbus interface is individually connected to the supervisory communication plane, then reliable communication with each fieldbus system is ensured, but the cabling effort and system complexity increase significantly
Solution Approach 1:
The patent merges multiple fieldbus interfaces into a single daisy-chained connection to the supervisory communication plane. Instead of requiring separate cable connections from each fieldbus interface to the supervisory plane, the interfaces are connected in series (daisy-chain topology), where the first interface connects to the supervisory plane and subsequent interfaces connect to the previous interface in the chain. This combining approach maintains communication reliability while dramatically reducing cabling complexity.
Solution Approach 2:
The first fieldbus interface acts as an intermediary or gateway that mediates communication between the supervisory communication plane and the entire chain of fieldbus interfaces. It receives data from the supervisory plane and forwards it through the daisy-chained interfaces to the appropriate fieldbus systems, eliminating the need for direct connections from each interface to the supervisory plane.
2Ease of operation
If each fieldbus interface is individually connected to the supervisory communication plane, then direct access to each fieldbus system is achieved, but the addressing and configuration complexity increases
Solution Approach 1:
The patent segments the addressing and configuration management into two levels: the supervisory communication plane uses a single address to access the first fieldbus interface, which then handles internal routing to subsequent interfaces and fieldbus systems. This segmentation simplifies the supervisory plane's addressing task while maintaining the ability to access all fieldbus systems through the chained interfaces.
Solution Approach 2:
The first fieldbus interface serves multiple functions: it acts as a gateway to the supervisory communication plane, a router for data packets to subsequent interfaces in the chain, and a configuration manager for the entire fieldbus system. This multi-functionality reduces the need for complex individual addressing of each interface at the supervisory level.
3Adaptability or versatility
If multiple fieldbus interfaces are used to support different fieldbus types, then system versatility is improved, but the number of required connections and configuration efforts increase
Solution Approach 1:
The daisy-chained fieldbus interface system provides universal support for multiple fieldbus types (Profibus, Foundation Fieldbus, HART, CANopen) through a standardized series connection topology. Each interface in the chain can handle different fieldbus protocols while maintaining a uniform physical connection method, simplifying system integration and reducing configuration efforts despite the diversity of supported protocols.
Solution Approach 2:
The system dynamically routes data packets through the daisy-chained interfaces based on the destination fieldbus type and address. The first interface receives data from the supervisory plane and intelligently forwards it through the appropriate subsequent interfaces in the chain, allowing flexible support for multiple fieldbus types without requiring static, dedicated connections for each protocol type.
Data Source
AI summary
A process control arrangement (PKA), having a number of fieldbus systems (DP1, PA1, FH), especially different fieldbus systems (DP1, PA1, FH), and having a number of fieldbus interfaces (PAP1, PAP2, PAP3), wherein each of the fieldbus systems (DP1, PA1, FH) is connected to at least one of the fieldbus interfaces (PAP1, PAP2, PAP3), wherein the fieldbus interfaces (PAP1, PAP2, PAP3) serve for communication between the fieldbus systems (DP1, PA1, FH) and a communication plane (ET2) superordinated to the fieldbus systems, only a first of the fieldbus interfaces (PAP1) is directly connected to the superordinated communication plane (ET2), and wherein the fieldbus interfaces (PAP1, PAP2, PAP3) are connected in series with one another beginning with the first of the fieldbus interfaces (PAP1).