Field Device Gateway for Multi-Standard Bus Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing fieldbus systems face complexity in configuring and accessing field devices across different standards, requiring intricate memory mappings and firmware adaptations, which hinders ease of use and maintenance, especially when coupling two fieldbus systems or networks.
Innovation Solution
A method where a first field device, operating according to a standard like CANopen, loads a customer-specific device description file for a second field device, allowing access to its objects and enabling communication, with the creation of a configuration file that maps parameters and variables between standards, facilitating access without mediation through a free memory area, and allowing extension to include multiple field devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If parameters or variables from one fieldbus system are made accessible to the second fieldbus system via a defined memory area in the coupling gateway, then communication between different fieldbus systems is enabled, but complex assignment of memory locations or memory areas to parameters or variables is required
Solution Approach 1:
The patent creates a copy of the object dictionary from the first fieldbus system within the gateway's object dictionary. This allows the gateway to directly map and access parameters from the first fieldbus system without requiring complex memory location assignments, as the object dictionary structure inherently provides the necessary parameter organization and addressing.
Solution Approach 2:
The gateway is designed with a universal object dictionary structure that can accommodate parameters from different fieldbus systems using a standardized interface. This multi-functional approach allows the same data structure to serve multiple communication protocols, eliminating the need for protocol-specific memory mapping configurations.
2Ease of operation
If field devices in subsystems are accessed without precise knowledge of the subsystem or the field devices, then ease of configuration is improved, but this requires a standardized interface that increases implementation complexity
Solution Approach 1:
The gateway automatically imports the object dictionary from the first fieldbus system and configures itself to access field devices in the subsystem. This self-service mechanism eliminates the need for manual configuration by users, as the gateway autonomously establishes the standardized interface and parameter mappings required for device access.
Solution Approach 2:
The object dictionary is pre-configured in the gateway before field devices need to be accessed. This preliminary setup of the standardized interface structure allows users to configure field devices without needing precise knowledge of the subsystem internals, as the foundation for standardized access is already in place.
3Reliability
If any change in the subsystem requires an adaptation of the firmware, then system reliability is maintained, but ease of maintenance and adaptability are reduced
Solution Approach 1:
The gateway's object dictionary is designed to be dynamically updatable, allowing changes in the subsystem to be reflected without firmware modifications. The system can adapt to subsystem changes by loading updated object dictionaries or reconfiguring parameter mappings, maintaining reliability through controlled changes while enabling flexibility.
Solution Approach 2:
The system separates the firmware (gateway core functionality) from the configuration data (object dictionary). This segmentation allows the firmware to remain stable and reliable while the object dictionary can be independently modified to accommodate subsystem changes, providing adaptability without requiring firmware adaptation.
4Loss of information
If a complete device description file is loaded for each field device, then comprehensive device information is available, but configuration time and data processing load increase
Solution Approach 1:
The gateway extracts and imports only the necessary object dictionary information from the first fieldbus system into its own structure. This selective extraction provides comprehensive device information where needed while avoiding the overhead of loading and processing complete device description files for every field device, reducing configuration time and data processing load.
Data Source
Figure 1
Figure 2
AI summary
The present invention relates to systems and methods for communication with field devices in a fieldbus system operating according to a first standard. A first field device and a second field device are arranged in the fieldbus system. The first field device and the second field device are coupled via a first fieldbus. A customer-specific device description file of the second field device, according to the first standard, is loaded into the first field device. Subsequently, communication with the second field device occurs via the first field device and the first fieldbus, so that customer-specific objects and/or parameters of the second field device are available on the first field device.