Generic Communication Driver for Fieldbus Device Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing hierarchical structure of device access software for fieldbus systems is prone to failures if a device driver or device description file is missing or faulty, leading to inaccessible field devices and complex nested communication structures.
Innovation Solution
A data transmission system with a generic communication driver integrated into the device access software and a coupler device connected to the fieldbus system, utilizing a central data transmission link for primary data traffic and routing information to ensure correct data routing, eliminating the need for additional communication drivers and reducing system susceptibility to faults.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a hierarchical structure with multiple device drivers is used to access field devices through gateways, then the system can support complex nested fieldbus topologies, but the system becomes highly susceptible to failures when a device driver or device description file is missing or faulty
Solution Approach 1:
The patent segments the device driver functionality into two independent parts: a generic communication driver that handles communication with the coupler device and field devices, and separate device-specific drivers that handle device-specific protocols. This segmentation allows the system to support complex nested fieldbus topologies while reducing susceptibility to failures, as a missing or faulty device-specific driver no longer causes the entire system to fail.
Solution Approach 2:
The patent introduces a coupler device as an intermediary between the device access software and the fieldbus system. This coupler device acts as a mediator that translates between different communication protocols and manages device access, eliminating the need for multiple nested device drivers and reducing system susceptibility to driver-related failures.
2Ease of operation
If device drivers are arranged in a hierarchical structure mirroring the fieldbus system, then device access can be organized systematically, but the complexity of the device access software increases
Solution Approach 1:
The patent extracts the communication management functionality from the device-specific drivers and places it in a separate generic communication driver. This extraction simplifies the device access software by removing the complexity of managing multiple nested device drivers, while still maintaining systematic device access organization through the coupler device.
Solution Approach 2:
The generic communication driver serves as a universal interface that can communicate with multiple different types of field devices through the coupler device, eliminating the need for separate device-specific communication logic in each driver and reducing overall software complexity.
3Adaptability or versatility
If multiple device drivers are required to access different field devices, then each device can be accessed with dedicated functionality, but additional communication drivers are needed and the system becomes more fault-prone
Solution Approach 1:
The generic communication driver provides universal communication functionality that can access multiple different types of field devices through the coupler device, eliminating the need for multiple dedicated communication drivers while still maintaining device-specific access functionality through protocol translation.
Solution Approach 2:
The coupler device acts as an intermediary that handles device-specific communication protocols, allowing the generic communication driver to maintain a simple, universal interface while still providing access to diverse field devices with different protocols.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
The invention relates to a data transmission system for a data exchange between a field bus system that comprises at least one field device, and a device access software that is installed on a host and by means of which components of the field bus system can be accessed. The data transmission system comprises a coupler device that is connected to the field bus system, and a generic communication driver, which is integrated in the device access software. In addition, at least one device driver is integrated in the device access software. The data transmission system further comprises a central data transmission path, which can be built between the generic communication driver and the coupler device, and via which a primary data traffic can be transmitted. The generic communication driver is configured to exchange data with at least one of the device drivers that is integrated in the device access software, and to transmit data received from the at least one device driver as part of the primary data traffic to the coupler device via the central data transmission path, and to forward data of the primary data traffic received by the coupler device via the central data transmission path to the respective device driver, for which the data are intended. The coupler device is configured to convert the primary data traffic received from the generic communication driver via the central data transmission path into a secondary data traffic while adding routing information and to send on the field bus system, and to convert data received from at least one of the field devices to the primary data traffic, and to transmit to the generic communication driver via the central data transmission path.