OPC UA Instance Linking With PLC Code for Automation Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods require substantial programming effort to link OPC UA objects with PLC code objects in automation systems, hindering efficient data communication and information transfer across different automation system units.

Innovation Solution

A method that involves reading OPC UA node sets, generating OPC UA instances, and linking them with PLC objects, using Companion Specifications to define object types and data structures, thereby reducing the need for extensive programming and ensuring compatibility between OPC UA and PLC objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual linking methods are used to connect OPC UA objects with PLC code objects, then data communication between different automation system units can be achieved, but substantial programming effort is required

Engineering Contradiction:
Improvedata communication reliabilityVSAvoidprogramming effort
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent introduces a development environment as an intermediary tool that automatically generates linking code between OPC UA objects and PLC code objects. This mediator handles the complex mapping and connection logic, eliminating the need for manual programming of linkages while ensuring reliable data communication between different automation system units.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The development environment performs preliminary actions by automatically generating the linking code and configuration before the actual deployment. The tool pre-establishes the connections between OPC UA objects and PLC objects, so that when the system is deployed, the linking is already in place without requiring substantial programming effort during implementation.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If standardized OPC UA communication is implemented across different manufacturers' units, then interoperability is improved, but complex data communication structures are required to handle large volumes of data

Engineering Contradiction:
ImproveinteroperabilityVSAvoiddata communication structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal development environment that works with OPC UA objects from different manufacturers and different types of automation units. This single tool provides multi-functional capabilities to handle various data communication scenarios, generating appropriate linking code for different object types without requiring separate solutions for each manufacturer or device type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The development environment uses template-based copying mechanisms where standard linking patterns are predefined and automatically copied and adapted to specific cases. Instead of manually designing complex data communication structures for each scenario, the tool copies proven linking templates and instantiates them with the specific object parameters, simplifying the overall structure.

Inventive Principle:
Principle #26Copying

3Productivity

If automatic linking is implemented between OPC UA instances and PLC objects, then programming effort is reduced, but precise matching between objects is required

Engineering Contradiction:
Improvelinking speedVSAvoidobject matching accuracy
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The development environment incorporates feedback mechanisms that automatically verify the matching between OPC UA instances and PLC objects. The tool provides feedback on whether objects are correctly paired, highlighting mismatches and suggesting corrections. This feedback loop ensures high matching accuracy while maintaining automatic linking speeds.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent replaces manual mechanical matching processes with automated computational methods. Instead of manually comparing and matching object parameters, the development environment uses automated algorithms to identify and establish correct correspondences between OPC UA instances and PLC objects, achieving both speed and precision through computational rather than manual means.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20220255987A1Method for linking objects of a control program of a control unit of an automation system, and development environment
Publication Date: 2022.08.11 BECKHOFF AUTOMATION GMBH
  • US20220255987A1 patent drawing
  • US20220255987A1 patent drawing
  • US20220255987A1 patent drawing

AI summary

A method is provided for linking objects of an open platform communication unified architecture (OPC UA) data communication standard with objects of a programmable logic controller (PLC) code of a controller of an automation system is provided. The method comprises reading an OPC UA node set of a companion specification, generating OPC UA instances of the OPC UA object types of the OPC UA node set for the automation system, combining the OPC UA instances in an OPC UA instance node set, generating PLC objects in a PLC code of a control program of the automation system, and linking the OPC UA instances of the OPC UA instance node set with PLC objects of the PLC code of the control program. A development environment for carrying out the method is also provided.