Controller Development Tool Interface for Model-Based Source Code Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In model-based development for vehicle engine control units, there is a trade-off between control design freedom and software implementation flexibility, leading to reduced productivity and quality deterioration due to skill disparities among engineers during software design and implementation.
Innovation Solution
A controller development tool with an interface unit that allows for both high degree of freedom in control design and restricted scaling and packaging in software design and implementation, enabling the creation of source code through library models, scaling management, and packaging processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If standard blocks are used for control design, then degree of freedom in control design is improved, but corrections and modifications in software design and implementation are increased
Solution Approach 1:
The patent introduces an interface unit as an intermediary layer between the control design block and the software implementation. This interface unit contains standardized elements that mediate the translation from control design to software code, reducing the need for corrections and modifications while maintaining design freedom.
Solution Approach 2:
The patent segments the development process into distinct layers: control design layer, interface unit layer, and software implementation layer. The interface unit is segmented into specific elements that handle different aspects of the translation, allowing independent optimization of each layer without affecting others.
2Ease of manufacture
If specified blocks are used for control design, then software design and implementation restrictions are reduced, but degree of freedom in control design is reduced
Solution Approach 1:
The interface unit is designed with universal elements that can handle multiple functions and scenarios. These standardized interface elements work across different control designs and software implementations, providing ease of manufacture while maintaining adaptability through their multi-functional nature.
Solution Approach 2:
The interface unit provides dynamic adaptability where the standardized elements can be configured and adapted to different control designs without losing their standardization benefits. This allows the system to be both easy to manufacture and flexible in control design.
3Extent of automation
If model-based development is used, then automatic source code creation is improved, but high skills are required for control design, software design, and program development environment
Solution Approach 1:
The interface unit enables a form of self-service where the standardized interface elements automatically handle the translation from control design to software implementation. This reduces the skill requirement by making the system more self-configuring and less dependent on highly skilled engineers for manual software design and implementation.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Usability and productivity are improved in auto-coding to implement model-based development. A controller development tool for creating a source code to implement processing represented by a model includes an interface (1, 2, 3, 8) for describing the model as a library model (8A) including a combination of blocks capable of creating a source code, creating the source code through scaling management (8B) for the controller, and combining the source code with a plurality of functions to produce a source file (4, FIG. 9).