Automation Object Binding for Flexible Industrial Controller Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In industrial automation, existing systems require significant rewrites of controller logic and visualization code whenever hardware modifications are made, such as introducing new controllers or changing hardware components, leading to inefficiencies and increased processing costs.

Innovation Solution

The implementation of late binding of automation objects to controller logic and load balancing across industrial controller resources, allowing for the creation of base code with generic placeholders that can be replaced with specific automation objects and executed on selected controllers based on requirements like execution rate and scan rate, reducing the need for extensive code rewriting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If controller logic and visualization code are written with specific hardware specifications known in advance, then the code can be optimized for that hardware, but significant rewrites are required when hardware modifications are made

Engineering Contradiction:
Improvecode execution reliabilityVSAvoidhardware adaptability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The code is segmented into hardware-specific sections and hardware-agnostic sections. The hardware-agnostic portions can be reused across different hardware configurations, while only the hardware-specific sections need to be modified when hardware changes occur, reducing rewrite requirements

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The code is designed with universal interfaces and abstractions that can work with multiple hardware types. By creating a hardware-independent layer that handles common operations, the same code base can adapt to different hardware configurations without requiring complete rewrites

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

2Adaptability or versatility

If new controllers are introduced to the automation system, then system capabilities are enhanced, but large portions of code must be re-written to accommodate the new controllers

Engineering Contradiction:
Improvecontroller flexibilityVSAvoidcode rewriting time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

Hardware interfaces and communication protocols are pre-configured and standardized before new controllers are introduced. This preliminary setup of universal interfaces allows new controllers to be integrated with minimal code changes, as the framework is already prepared to accommodate diverse hardware

Inventive Principle:
Principle #10Preliminary action

3Productivity

If code is specifically written for known hardware specifications, then optimization for that hardware is achieved, but processing costs increase when hardware modifications are required

Engineering Contradiction:
Improvecode execution efficiencyVSAvoidcode maintenance cost
Core Design Contradiction:
ProductivityVSEase of manufacture

Solution Approach 1:

The code uses configurable parameters and variables that can be adjusted when hardware changes occur, rather than requiring structural code modifications. By changing parameters such as hardware addresses, communication rates, and I/O mappings, the same optimized code can adapt to new hardware with minimal impact on execution efficiency

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11320806B2Intelligent binding and selection of hardware via automation control objects
Publication Date: 2022.05.03 ROCKWELL AUTOMATION TECH INC
  • US11320806B2 patent drawing
  • US11320806B2 patent drawing
  • US11320806B2 patent drawing

AI summary

The present disclosure is directed to systems, methods and devices for facilitating object-based industrial automation control. An automation control library comprised of a plurality of objects may be maintained in association with one or more industrial automation applications. Code defining the execution of an industrial automation process may be received. A plurality of objects in the object library for implementing the industrial automation control process may be identified. The plurality of identified objects may be matched to one or more hardware components based on one or more operational requirements included in the code, and available hardware resources for performing the automation control process.