Function Module Wrapping for Periodic Control Program Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Designers face challenges in incorporating non-periodic-execution function modules into periodic-execution control programs due to the need to understand both programming languages, which increases design complexity and process requirements.
Innovation Solution
A development support program that acquires correspondence relationships and definition information between data types in different programming languages to generate a periodic-execution function module as a wrapper, allowing for the invocation of non-periodic-execution function modules without requiring knowledge of the non-periodic-execution programming language, and enabling synchronization or asynchronous execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a non-periodic-execution function module is incorporated into a periodic-execution control program, then the functionality and versatility of the control program is improved, but the design complexity increases because the designer must know both periodic-execution and non-periodic-execution programming languages
Solution Approach 1:
The patent introduces an intermediary conversion process that translates non-periodic-execution function modules into periodic-execution compatible modules. The development support device automatically performs this conversion by mapping data types and execution patterns, allowing designers to use non-periodic-execution modules in periodic-execution programs without needing to understand both programming paradigms. This intermediary layer resolves the contradiction by enabling functionality expansion while maintaining design simplicity.
Solution Approach 2:
The patent creates a copied version of the non-periodic-execution function module that is adapted for periodic-execution environments. The development support device generates a periodic-execution equivalent by copying the functional logic and transforming it to match periodic-execution requirements. This copying approach allows the original non-periodic module to remain unchanged while providing a compatible version for periodic programs, thus improving versatility without increasing design complexity.
2Ease of operation
If automatic conversion between data types in different programming languages is implemented, then the ease of operation is improved, but the device complexity increases due to the need for conversion rules and correspondence relationships
Solution Approach 1:
The patent implements preliminary action by pre-defining correspondence relationships between data types in periodic-execution and non-periodic-execution programming languages. The development support device stores these mapping rules in advance, so when conversion is needed, the system can automatically apply the pre-established rules without complex real-time analysis. This preliminary preparation simplifies the conversion process while maintaining ease of operation for users.
Solution Approach 2:
The patent applies parameter changes by systematically transforming data type parameters from one programming language paradigm to another. The development support device identifies data type parameters in the source module and automatically changes them to corresponding types in the target paradigm based on stored correspondence relationships. This parameter transformation approach enables automatic conversion while keeping the conversion mechanism manageable through structured parameter mapping.
Data Source
AI summary
The present invention provides an environment that makes it possible to incorporate a non-periodic-execution function module into a periodic-execution control program. A development support program that makes a computer execute steps that generate a periodic-execution second function module that invokes a non-periodic-execution first function module. Said steps include: a step in which a data type that is in a periodic-execution programming language and corresponds to the data type of an argument for the first function module is specified, and an input variable of said data type is established for the second function module; and a step in which a data type that is in a periodic-execution programming language and corresponds to the data type of a return value for the first function module is specified, and an output variable of said data type is established for the second function module.