Automation System Configuration for IEC 61131-3 to 61499 Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing automation systems face challenges in configuring and programming Programmable Logic Controllers (PLCs) for distributed systems, as applications compliant with IEC 61131-3 cannot be directly used in IEC 61499 systems, requiring tedious rewriting of function blocks and manual configuration of communication between controllers.
Innovation Solution
A method and device that enable the creation of a platform-independent model incorporating a second function block with an event interface, allowing for the execution of IEC 61131-3 applications on IEC 61499 systems by allocating and compiling parts of the application on multiple controllers, thereby facilitating collaboration between IEC 61499 and IEC 61131-3 applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If function blocks are rewritten to comply with IEC 61499 for distributed applications, then compatibility with distributed systems is improved, but programming time and effort increase significantly
Solution Approach 1:
The patent creates a copy mechanism where IEC 61131-3 function blocks are replicated and adapted to IEC 61499 format. The conversion tool generates IEC 61499-compatible function blocks by copying the logic and functionality from existing IEC 61131-3 blocks, then automatically adjusting them to meet IEC 61499 standards, thereby avoiding manual rewriting while ensuring compatibility
Solution Approach 2:
The patent introduces an intermediary conversion tool that acts as a bridge between IEC 61131-3 and IEC 61499 standards. This intermediary automatically translates function blocks from one standard to another, eliminating the need for programmers to manually rewrite code and reducing programming time while maintaining distributed system compatibility
2Ease of operation
If IEC 61131-3 applications are executed on a single centralized PLC, then implementation simplicity is maintained, but system scalability and distributed control capability are limited
Solution Approach 1:
The patent segments the centralized PLC application into multiple distributed controller instances. Each controller executes a portion of the overall application, with function blocks distributed across multiple devices. This segmentation enables scalable distributed control while maintaining the simplicity of IEC 61131-3 programming through automatic distribution management
Solution Approach 2:
The patent creates a universal execution environment that can run both IEC 61131-3 and IEC 61499 applications. The system provides multi-functionality by allowing centralized execution for simple applications and distributed execution for scalable applications, all through the same programming interface, thus maintaining ease of operation while enabling distributed control capability
3Reliability
If communication between controllers is configured manually for distributed systems, then system reliability is improved through explicit configuration, but configuration complexity and time increase
Solution Approach 1:
The patent implements self-service automatic configuration of communication between controllers. The system automatically detects controller connections, configures communication parameters, and establishes data exchange routes without requiring manual configuration. This self-service approach maintains system reliability through automated validation while reducing configuration complexity and time
Solution Approach 2:
The patent performs preliminary automatic configuration of communication settings before application deployment. Communication pathways, data formats, and exchange protocols are pre-configured and validated automatically, ensuring system reliability is established in advance while eliminating the need for complex manual configuration during deployment
Data Source
AI summary
A method configuring an automation system with plural controllers including first and second controllers, the method including: obtaining a first function block, having a first interface, suitable for a first application, and created by a first tool compliant with a first standard; creating a platform independent model for a second application with a second tool compliant with a second standard; creating a platform definition model of the first controller for the second application; creating a platform specific model for the second application, including: allocating and compiling, with the second tool, a primary part of the second application including the second function block for the first controller and a secondary part of the second application for the second controller; and downloading the first controller configuration, the first application, and the primary part of the second application to the first controller.


