PLC Program Module Import with Automatic Variable Conflict Renaming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques, such as those disclosed in Japanese Patent Laid-Open No. H04-205355, fail to effectively improve the design efficiency and reusability of programs executed by control devices like PLCs, particularly in managing variable and program name overlaps during module importation.
Innovation Solution
A program development device and method that maintain first variable names and change second variable names upon import to prevent overlaps, allowing for automatic renaming according to predetermined rules, ensuring no conflicts in variable and program names within the project, thereby enhancing design efficiency and reusability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If program modules are imported into an existing project, then the reusability and design efficiency are improved, but variable name overlaps and conflicts occur between imported and existing modules
Solution Approach 1:
The system performs preliminary detection of variable name overlaps between imported program modules and existing project modules before the import is finalized. By identifying potential conflicts in advance, the system can present warnings to users or automatically rename conflicting variables, preventing name overlap issues from occurring in the final imported project structure.
Solution Approach 2:
The system introduces an intermediary processing layer that manages the import operation. This intermediary detects variable name conflicts, presents them to users for resolution, or automatically resolves them through renaming mechanisms. This intermediary layer acts as a mediator between the imported module and the existing project, ensuring name uniqueness without requiring direct integration.
2Reliability
If manual correction of variable names is required during module import, then naming conflicts are resolved, but design efficiency and time consumption are reduced
Solution Approach 1:
The system implements self-service functionality by automatically detecting variable name overlaps and performing renaming operations without requiring manual user intervention. The system autonomously identifies conflicting variable names, generates unique names according to predefined rules, and applies the changes automatically, thereby eliminating time-consuming manual correction processes while ensuring variable name uniqueness.
Solution Approach 2:
The system changes the parameter of variable names automatically when overlaps are detected. By modifying the name parameter of conflicting variables according to predefined naming conventions or rules, the system resolves conflicts without requiring manual user input, thus maintaining both reliability and efficiency.
3Productivity
If all variable names are maintained as-is during import, then import speed is maximized, but naming conflicts and program errors increase
Solution Approach 1:
The system extracts only the critical information needed for conflict detection (variable names and their scopes) during the import process, rather than processing all module contents immediately. This selective extraction allows for rapid identification of potential naming conflicts without significantly impacting import speed, while still ensuring program correctness through subsequent conflict resolution.
Solution Approach 2:
The system performs a preliminary skip-phase import where variable names are quickly scanned and checked for conflicts without full integration. This rushing-through approach identifies naming issues rapidly, allowing the system to maintain high import speed while flagging only the necessary corrections needed for program correctness.
Data Source
AI summary
This program development device comprises: a storage unit which holds a project; and an update means which imports one or a plurality of program modules into the project. Each of the program modules contains a program, and can define a first variable which is a variable that can be referenced among all program modules, a second variable which is a variable that can be referenced among the plurality of program modules, and a third variable which is a variable referenced in each program module. The update means maintains the variable name of the first variable contained in the imported program module, and when the variable name of the second variable contained in the imported program module overlaps the variable name of the second variable contained in any of the program modules of the project, the update means accepts a change of the overlapping variable name.