Fieldbus Slave Planning With Profile-Based Device Replacement

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current fieldbus system configuration methods often rely on universal slaves, which lack specific product information, leading to potential project planning errors when replacing them with unsuitable product slaves, and do not efficiently utilize the advantages of product slaves, especially in scenarios with insufficient information or legacy system migrations.

Innovation Solution

The method involves configuring fieldbus systems with universal slaves that can be automatically replaced by product slaves based on defined test criteria, allowing for the retention of fieldbus addresses and enhancement with additional product-specific data, and using multi-product slaves to replace sets of universal slaves, thereby preventing errors and improving configuration efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If universal slaves are used for field device configuration, then configuration flexibility and ease of initial setup are improved, but product-specific information is lost and replacement errors may occur

Engineering Contradiction:

Improveconfiguration flexibilityVSAvoidproduct-specific information

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The slave device is segmented into two distinct types: universal slaves for initial flexible configuration and product slaves for specific product information. This segmentation allows the system to benefit from both universality and product-specificity at different stages of the configuration process.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Universal slaves are configured first as a preliminary step before final product slave assignment. This preliminary configuration establishes the basic communication framework and allows later replacement with product-specific slaves without losing the established communication parameters.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If universal slaves are replaced with product slaves, then product-specific data and value-added functions are enhanced, but project planning errors may occur due to unsuitable replacements

Engineering Contradiction:

Improveconfiguration accuracyVSAvoidproject planning errors

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The system implements feedback mechanisms where the fieldbus master communicates with slaves to verify compatibility and proper configuration. This feedback loop ensures that product slave replacements are validated against the established communication parameters, preventing planning errors.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system takes preliminary actions to prevent replacement errors by establishing strict matching criteria between universal slave profiles and product slave specifications before replacement occurs. This preemptive measure ensures compatibility and prevents unsuitable replacements.

Inventive Principle:

Principle #9Preliminary anti-action

3Loss of information

If product slaves are used directly, then product information completeness is improved, but configuration complexity increases and adaptability to insufficient information scenarios decreases

Engineering Contradiction:

Improveproduct information completenessVSAvoidconfiguration complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The universal slave serves multiple functions: it acts as a placeholder during initial configuration, maintains communication parameters, and enables later product slave assignment. This multi-functionality simplifies the overall configuration process by providing a single initial configuration type that works across different scenarios.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The slave configuration is dynamic rather than static. Slaves can transition from universal to product-specific types based on information availability and project requirements. This dynamic approach allows the system to adapt its complexity level to match the available information and project needs.

Inventive Principle:

Principle #15Dynamics

4Stability of the object's composition

If universal slaves retain fieldbus addresses during replacement, then system stability is improved, but configuration flexibility is reduced

Engineering Contradiction:

Improvesystem stabilityVSAvoidconfiguration flexibility

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The fieldbus address retention applies specifically to the communication interface level while allowing product-specific configuration at the application level. This local quality approach maintains stability in the communication layer while preserving flexibility in the product configuration layer.

Inventive Principle:

Principle #3Local quality

Data Source

PatentEP2899603B1Planning of a field bus system

Publication Date: 2022.06.01 SIEMENS AG

Figure 1
Figure 2~3
Figure 4

AI summary

The invention relates to a method for configuring a fieldbus system (1) with a fieldbus master (2) and at least one field device (3). In this method, at least one field device (3) is initially configured as a universal slave (30 to 33) with a slave profile (50 to 53) containing the field device (3) properties required by the fieldbus master (2), and with a unique fieldbus address (60 to 63). Subsequently, at least one universal slave (30 to 33) is replaced by a product slave (300 to 312) corresponding to its slave profile (50 to 53), while retaining the fieldbus address (60 to 63) of the universal slave (30 to 33).