Automation Object Binding for Hardware-Agnostic Controller Code
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In industrial automation, existing methods require significant rewriting of controller logic and visualization code whenever hardware modifications are made, such as introducing new controllers or hardware components, leading to inefficiencies and increased processing costs.
Innovation Solution
The approach involves creating base code with generic placeholders for automation objects, which are later replaced with specific objects based on available hardware resources, allowing for late binding and load balancing across industrial controllers, enabling reuse of code without extensive rewrites.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If controller logic and visualization code are written with specific hardware specifications known in advance, then the code can be optimized for that specific hardware configuration, but significant rewriting is required when hardware modifications are made or new controllers are introduced
Solution Approach 1:
The code is segmented into hardware-agnostic logic and hardware-specific binding layers. The controller logic is divided into functional modules that can operate independently of specific hardware implementations, with binding layers that map generic code to actual hardware components. This allows the core logic to remain unchanged while only the binding layer needs adjustment for different hardware configurations.
Solution Approach 2:
The system implements universal placeholder objects that can represent multiple types of hardware components through a common interface. These placeholder objects serve as universal intermediaries between the controller logic and various hardware devices, allowing the same base code to control different hardware types by simply changing the bound object instances rather than rewriting the logic.
2Productivity
If code is specifically written for existing hardware, then optimal performance can be achieved for that hardware, but new hardware resources cannot be easily utilized without extensive code rewrites
Solution Approach 1:
The system performs preliminary binding of placeholder objects to hardware components during system initialization or configuration phase, before the controller logic needs to execute. This preliminary action establishes the mapping between generic code and specific hardware, allowing new hardware to be integrated by simply creating new bound objects and attaching them to the existing logic structure without time-consuming code rewrites.
Solution Approach 2:
The system creates copies of existing bound object patterns for new hardware integration. When new controllers or hardware components are introduced, the system can replicate the binding structure and configuration from existing hardware objects, allowing rapid adaptation to new resources by copying proven binding patterns rather than developing new integration code from scratch.
3Ease of operation
If hardware specifications are known in advance when writing code, then precise optimization for that hardware is possible, but system flexibility and ease of modification are reduced
Solution Approach 1:
The system introduces placeholder objects as intermediaries between the controller logic and actual hardware components. These intermediaries maintain the precise hardware interface requirements while shielding the core logic from hardware-specific details. The placeholder objects act as mediators that translate generic control commands into hardware-specific operations, preserving both ease of modification and hardware optimization precision.
Data Source
Figure 1
Figure 2
Figure 3
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.