OPC UA Nodeset Validation Logic for Field Device Settings
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current validation logic solutions for field devices, such as EDDL and FDT, are inefficient and costly to maintain, especially when transitioning to OPC UA connectivity, as they require duplicated effort and are not well-suited for OPC UA-based field devices, which need improved parameter setting validation.
Innovation Solution
Incorporating PYTHON script-described business logic into nodeset files to validate settings in the address space of OPC UA-connected field devices, allowing for generic validation without direct connection to the device, and enabling bridging between incompatible standards by storing validation logic in the nodeset file, reducing maintenance effort and providing a unified logic execution environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If EDDL or FDT standards are used for validation logic, then device parameter management is enabled, but duplicated effort and high maintenance costs occur
Solution Approach 1:
The patent uses XML-based nodeset files as a copyable, standardized representation of device address space and validation logic. Instead of implementing separate EDDL and FDT solutions, the invention creates a single XML nodeset file that can be imported by OPC UA clients, eliminating duplicated validation logic implementation while maintaining parameter management capabilities.
Solution Approach 2:
The XML nodeset file serves multiple functions simultaneously: it defines the device address space structure, specifies parameter validation rules, and provides the basis for OPC UA client configuration. This universal approach replaces the need for separate EDDL interpreters and FDT DTMs, reducing maintenance burden while enabling comprehensive device management.
2Reliability
If EDDL interpreter is used, then parameter validation is possible, but costly maintenance is required
Solution Approach 1:
The patent replaces the expensive, complex EDDL interpreter with lightweight XML nodeset files that are simpler to maintain and update. The XML format is a standardized, widely-supported data structure that requires minimal interpretation infrastructure, effectively replacing a costly long-term maintenance burden with a simpler, more maintainable solution.
Solution Approach 2:
The invention substitutes the complex EDDL interpretation mechanism with direct XML-based validation logic. Instead of requiring an EDDL interpreter to process and validate parameters, the system uses XML nodeset files with embedded validation rules that can be directly processed by OPC UA clients, eliminating the need for specialized interpretation software.
3Reliability
If validation logic is embedded in device firmware, then device setting integrity is protected, but logic duplication occurs across devices
Solution Approach 1:
The patent extracts validation logic from individual device firmwares and consolidates it into external XML nodeset files. This allows the same validation rules to be shared across multiple devices through a common nodeset file, eliminating duplication while maintaining integrity protection. The OPC UA client imports the nodeset file to obtain validation logic, rather than each device containing its own copy.
Solution Approach 2:
The XML nodeset file acts as an intermediary between the device and the OPC UA client, containing the validation logic that protects device setting integrity. Instead of embedding logic directly in firmware, the nodeset file serves as a shared intermediary that defines validation rules for multiple devices, reducing complexity while maintaining reliability.
4Adaptability or versatility
If OPC UA connectivity is implemented, then field device integration is enabled, but compatibility with legacy standards becomes challenging
Solution Approach 1:
The patent creates XML nodeset files that copy and represent the device address space in an OPC UA-compatible format. This allows legacy devices to be integrated into OPC UA systems by providing an XML-based representation of their parameters and validation logic, enabling compatibility without requiring changes to the original device firmware or communication protocol.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
There is provided a method performed by an OPC UA client (104), the method comprising: importing a nodeset (106) file pertaining to an OPC UA-enabled automation device, the nodeset file defining validation logic (108) used to validate data to be written to the automation device; preparing data to be written to the automation device; and using the validation logic to validate the prepared data. Further provided is a method performed by an OPC UA server (102), the method comprising: importing a nodeset file pertaining to an automation device in which the OPC UA server is embedded, the nodeset file defining validation logic used to validate data to be written to the automation device; receiving data to be written to the automation device; and using the validation logic to validate the received data.