Fieldbus Connection Directory for Multi-Protocol Device Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Fieldbus networks in automation technology face inefficiencies due to the need for frequent device scans by mobile field operating devices to establish connections with field devices and components, which burdens the network and requires additional software.
Innovation Solution
A field detection device connected to the fieldbus network initiates queries for multiple connection protocols, creating a centrally managed connection directory that lists accessible field devices and components, allowing field operating devices to select suitable access methods without scanning the network, and optionally uses QR codes for quick access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If field operating devices initiate device scans to establish connections with field devices, then connection establishment is enabled, but network burden increases and additional software is required
Solution Approach 1:
The field detection device performs preliminary scanning and detection of field devices and their supported connection protocols before field operating devices need to connect. It creates and maintains a connection directory in advance, so when a field operating device needs to connect, it can directly query the pre-prepared directory rather than performing scans itself, thus reducing network burden and operational complexity
Solution Approach 2:
The field detection device acts as an intermediary between field operating devices and field devices. It receives connection requests from field operating devices, queries the connection directory to find suitable connection protocols, and provides the necessary connection information, thereby mediating the connection process and reducing the burden on both field operating devices and the fieldbus network
2Loss of information
If field operating devices perform scans to find connection possibilities, then access information is obtained, but network performance deteriorates due to additional queries
Solution Approach 1:
The scanning and detection function is extracted from field operating devices and centralized in the field detection device. The field detection device alone performs the resource-intensive scanning operations to build and maintain the connection directory, while field operating devices only perform lightweight queries on this pre-built directory, thereby extracting the harmful scanning burden from the network while preserving complete connection information availability
Solution Approach 2:
The patent merges the scanning, detection, and connection information management functions into a single field detection device. Instead of multiple field operating devices performing redundant scans, one device consolidates these functions and shares the results with all field operating devices through the connection directory, improving network performance while maintaining information availability
3Reliability
If multiple connection protocols are supported for redundancy, then fault tolerance improves, but device complexity increases
Solution Approach 1:
The field detection device automatically detects which connection protocols each field device supports and maintains this information in the connection directory without requiring manual configuration. When a field operating device needs to connect, it queries the directory to self-determine the appropriate connection protocol based on the field device's capabilities, eliminating the need for complex manual protocol configuration while maintaining fault tolerance through multiple protocol options
Data Source
AI summary
Disclosed is a field detection device designed to be connected to at least one access point of a fieldbus network via at least one interface. The field detection device is designed to initiate or execute, for each of at least two connection protocols, an associated query in at least one fieldbus segment of the fieldbus network and to detect which field devices and fieldbus components in said at least one fieldbus segment can be accessed via the connection protocol in question. Furthermore, the field detection device is designed to provide a connection directory in which at least one connection protocol is specified for each field device and for each fieldbus component of a set of field devices and fieldbus components of the at least one fieldbus segment, by means of which connection protocol the field device in question or the fieldbus component in question can be accessed.