Smart Object Allocation in Industrial IDEs for Multi-Controller Reuse
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current industrial control program development platforms require initial binding to a specific industrial controller, limiting flexibility and scalability, as they support a one-to-one relationship between the control project and the controller, making it difficult to deploy control programs across multiple controllers and hindering the ability to decouple software development from hardware selection.
Innovation Solution
An integrated development environment (IDE) system that allows for decoupled development of industrial control programs by defining and storing them as smart objects, which can be allocated to multiple industrial controllers, enabling a one-to-many relationship and facilitating the reuse of control programs across different automation systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a control project is bound to a single industrial controller at the early stage of development, then the project structure is simple and easy to manage, but the flexibility and scalability are limited when deploying to multiple controllers
Solution Approach 1:
The control project is segmented into a master project and multiple controller-specific subprojects. The master project contains the common control program as a smart object definition, while each controller subproject references this definition. This segmentation allows the same control logic to be deployed across multiple controllers without creating a complex monolithic structure.
Solution Approach 2:
The smart object definition serves as a universal template that can be instantiated multiple times across different controller projects. This universal definition contains the common control program that can be allocated to any number of controllers, providing multi-functionality and reusability while maintaining a clean project structure.
2Ease of manufacture
If the control program is developed with initial binding to a specific controller, then the development process is straightforward, but the ability to decouple software development from hardware selection is hindered
Solution Approach 1:
The control program is developed and defined as a smart object in advance, before being allocated to any specific controller. This preliminary definition phase allows the control logic to be fully developed and tested in isolation, decoupling the software development process from hardware selection while maintaining ease of development through a structured approach.
Solution Approach 2:
The smart object definition acts as an intermediary between the control program and the industrial controller. This intermediate layer allows the control program to be developed independently of the controller, then allocated to the controller when needed, thereby decoupling software development from hardware selection while maintaining a straightforward development process.
3Ease of operation
If a one-to-one relationship is maintained between control project and controller, then the project management is simple, but the reuse of control programs across multiple controllers becomes difficult
Solution Approach 1:
The control program is created once as a smart object definition and then copied (instantiated) multiple times across different controller projects. This copying mechanism maintains simple project management through clear reference relationships while dramatically improving productivity by eliminating the need to manually recreate the same control logic for each controller.
Solution Approach 2:
The smart object definition serves as a universal template that can be instantiated multiple times across different controller projects. This universal definition contains the common control program that can be allocated to any number of controllers, providing multi-functionality and reusability while maintaining a clean project structure.
Data Source
AI summary
An industrial integrated development environment (IDE) supports decoupled development of industrial control programs without requiring the programs to be initially bound to a specific industrial controller. The IDE system allows industrial control programs to be defined as smart objects within an industrial control project. These smart objects can be created without an initial binding to an industrial controller, and can subsequently be assigned to selected industrial controllers after development of the control programs is complete, or while program development is in progress. A smart object can be reused and deployed to multiple industrial controllers, providing a simple means to implement common control functionality on multiple different automation systems. To allow for deployment of smart objects to selected controllers, the IDE system supports creation of a control project having a one-to-many relationship with industrial controllers, such that multiple controllers can be defined within a single project.