Symbolic Device Access for Multi-Protocol Industrial Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Industrial automation systems face challenges in coordinating data exchange between devices of different brands, types, and generations due to varying communication protocols and data formats, leading to increased complexity and inefficiency in integrating new devices into existing systems.
Innovation Solution
Implementing symbolic data operations using symbol and template object instances to facilitate consistent reporting and control across devices with different information model formats, enabling a standardized, flexible interface for data exchange.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional data exchange methods are used between devices of different brands and types, then device compatibility and coordination are improved, but system complexity and integration difficulty increase
Solution Approach 1:
The patent introduces a gateway device as an intermediary between devices with different communication protocols. The gateway translates data between various protocols (Modbus, OPC UA, etc.) and a standardized internal format, enabling compatibility without direct complex point-to-point integrations between all device pairs. This mediator approach resolves the contradiction by maintaining adaptability while managing complexity centrally in the gateway rather than distributed across all device connections.
Solution Approach 2:
The gateway device implements multiple communication protocols and data formats simultaneously, providing universal interface capabilities. A single gateway can handle Modbus RTU, Modbus TCP, OPC UA, and other protocols, eliminating the need for separate dedicated integration solutions for each device type. This multi-functionality maintains high adaptability while reducing overall system complexity by consolidating integration logic in one universal component.
2Measurement precision
If custom integration methods are used for each new device, then data exchange accuracy is improved, but commissioning time and operational efficiency deteriorate
Solution Approach 1:
The gateway device pre-configures translation rules and data mapping templates for common device types and protocols. During commissioning, the system can automatically select and apply pre-defined templates based on device identification, eliminating the need to manually create custom integration configurations from scratch. This preliminary preparation maintains data exchange accuracy through pre-validated mappings while dramatically reducing commissioning time.
Solution Approach 2:
The system enables automatic device identification and configuration where the gateway autonomously detects device types, selects appropriate communication protocols, and applies corresponding data mapping templates without requiring extensive manual programming. This self-service capability ensures accurate data exchange through automated protocol selection while minimizing commissioning time by eliminating manual configuration steps.
3Measurement precision
If manual configuration methods are used for data access, then data access precision is improved, but computing resources and operational efficiency deteriorate
Solution Approach 1:
Data access paths and mapping relationships are pre-configured and cached in the gateway device before runtime operations. The gateway prepares translation tables and access routes in advance, allowing rapid data retrieval without performing complex real-time protocol conversions for every data access request. This preliminary preparation maintains precise data access while reducing computing resource consumption during operational phases.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments of this present disclosure may include systems that perform operations including receiving a first symbol instance from an industrial automation device (86). The first template object instance may characterize a dataset accessible to the industrial automation device. Symbol object instances may inherit a categorization with respect to categories associated with the industrial automation device including an identity, a state, a runtime status, a maintenance status, sustainability information, or any combination thereof. The operations may include identifying a type of the industrial automation device based on the first symbol instance and generating template data based on the type of the industrial automation device and the first symbol instance. The template data may include values associated with the dataset and the categories associated with the first symbol instance. The operations may also include sending a control signal to the industrial automation device based on the template data.