Fieldbus Data Objects for Simpler Cloud Transfer Gateways
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing fieldbus network systems require extensive device-specific information on connection devices for data transmission to the cloud, leading to complexity and high maintenance efforts due to the need for addressing and address space allocation information for various device types.
Innovation Solution
A standardized data structure is implemented using a head class with derived classes for devices, allowing devices to generate data objects that include header and device-specific attributes, shifting the data retrieval and compilation effort to the devices and simplifying the connection device's role to data format conversion and cloud writing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If connection devices store extensive device-specific information for various device types, then data transmission capability is improved, but device complexity and maintenance effort increase
Solution Approach 1:
The patent introduces a standardized data object structure as an intermediary between field devices and the connection device. This data object contains standardized header information (device ID, type, status) that the connection device can process without needing device-specific knowledge. The standardized interface acts as a mediator that decouples the connection device from individual device variations, reducing complexity while maintaining transmission capability for multiple device types
Solution Approach 2:
The patent segments device information into standardized header fields (device identification, device type, status) that are universally applicable. By dividing the data transmission protocol into standardized segments rather than requiring complete device-specific information, the connection device only needs to handle the segmented header portion, reducing its complexity while maintaining versatility across different device types
2Productivity
If connection devices store addressing and address space allocation information for various device types, then data retrieval capability is improved, but maintenance effort increases
Solution Approach 1:
The patent enables field devices to self-identify through standardized header information containing device ID and type. Instead of requiring the connection device to store and manage addressing information for each device type, the devices themselves provide their identification data in the standardized protocol. This self-service approach improves data retrieval capability while eliminating the maintenance burden of managing device-specific addressing information at the connection device
3Device complexity
If standardized data structure is implemented, then device complexity is reduced, but flexibility in parameter selection may be limited
Solution Approach 1:
The patent implements a dynamic standardized data object structure where the header contains essential standardized fields (device ID, type, status) while allowing for flexible additional parameters. The standardized portion provides the simplified processing needed to reduce connection device complexity, while the extensible nature of the data object allows users to select and include specific parameters based on their application requirements, maintaining flexibility within the standardized framework
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The invention relates to a fieldbus network comprising at least one device (7) and a connecting apparatus (14), wherein the connecting apparatus (14) is designed to transfer data from the fieldbus network into a cloud (13). A derived class (17), which is derived from a specified base class (15), is installed on at least one of the devices (7), wherein base attributes (16) are defined by the specified base class (15) and additional attributes (19) specific to the devices may be specified through the derived class (17), wherein the at least one of the devices (7) is designed to generate a data object (20) for data transfer to the cloud (13), proceeding from the derived class (17). The connecting apparatus (14) is designed to receive the data object (20) from the relevant device (7), to convert at least a part of the data (23, 24) contained in the data object (20) into a format for an interface to the cloud (13) and to write the data (23, 24) to the cloud (13).