Fieldbus Access Unit Automatic Configuration via Identification Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing fieldbus access units require manual user intervention to store and configure field device information, making it cumbersome for evaluating data traffic.
Innovation Solution
A method and fieldbus access unit that automatically retrieve field device information from a higher-level unit using identification data within telegrams, allowing for automatic configuration and interpretation of data without user intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If field device information is manually stored and configured by the user, then the fieldbus access unit can interpret data traffic, but the user effort and configuration time increase significantly
Solution Approach 1:
The fieldbus access unit automatically retrieves field device information from a higher-level unit using identification data from monitored telegrams, enabling self-configuration without manual user intervention. The system performs self-service by autonomously obtaining device master data, GSD files, or DTM information needed for interpreting fieldbus communication.
Solution Approach 2:
The required field device information is pre-stored in a higher-level unit (server or application) before the fieldbus access unit needs it. When the access unit connects to the fieldbus, it automatically retrieves the necessary information from the pre-prepared higher-level unit, eliminating the need for users to manually configure devices beforehand.
2Productivity
If field device information is automatically retrieved from a higher-level unit, then configuration time is reduced, but the system requires additional communication infrastructure
Solution Approach 1:
The higher-level unit serves multiple functions: it stores field device information (GSD files, device master data), provides identification data matching, and supplies configuration parameters to the fieldbus access unit. This multi-functional approach consolidates what could be separate systems into a single comprehensive solution.
Solution Approach 2:
The higher-level unit acts as an intermediary between the fieldbus access unit and the field devices. Instead of the access unit directly interacting with field devices for configuration, it retrieves all necessary information through the higher-level unit, which mediates the information exchange using identification data from fieldbus telegrams.
3Loss of information
If the fieldbus access unit monitors all data traffic, then complete diagnostic information is available, but the data volume requiring interpretation increases
Solution Approach 1:
The fieldbus access unit extracts and retrieves only the specific field device information needed for interpretation from the higher-level unit, using identification data from telegrams as keys. This extraction approach obtains complete diagnostic information while avoiding the complexity of processing all raw fieldbus data manually.
Data Source
Figure 1
AI summary
Method for operating a fieldbus access unit (16), telegrams transmitted via a fieldbus (4, 6) being monitored by the access unit (16), in particular without the access unit (16) participating in a data transmission via the field bus (4, 6). The field device information required for interpreting the monitored telegrams is retrieved by a higher-level unit (34, 24) on the basis of identification data contained in the telegrams.