Graphical Control Models for Unsupported Signal Type Code Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing graphical control models do not support all signal types, leading to inefficiencies in creating control programs for target platforms, particularly in automotive systems, where regulatory standards require specific data types not supported by the graphical models.
Innovation Solution
A method that utilizes a definition database with a data memory object and identifiers to represent unsupported signal types in graphical control models, enabling the graphical control model to relay signals between blocks, and a data memory object to represent the variable, allowing unsupported signal types in graphical control models, and a data memory object to represent the graphical control models, and a data memory object to represent the variable, thereby enabling the creation of a control program for the target platform from the graphical control models, and a data memory object to represent the graphical control models, and a data memory object to represent the graphical control models, and a data memory object to represent the variable, thereby enabling the creation of a control program for the target platform.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the graphical control model uses only supported signal types, then the code generation is simple and reliable, but the model cannot represent all required data types for the target platform
Solution Approach 1:
The patent introduces an intermediary mapping mechanism between graphical control model signal types and target platform data types. A type mapping table stores correspondence relationships between signal types supported by the graphical control model and data types required by the target platform. When generating code, the system automatically resolves unsupported signal types by referencing this mapping table, thereby enabling support for additional data types without directly extending the graphical control model's native signal type capabilities.
2Adaptability or versatility
If the graphical control model supports all data types directly, then no type mapping is needed, but the model becomes overly complex and loses its abstraction benefits
Solution Approach 1:
The patent segments the type system into two distinct layers: the graphical control model layer with its supported signal types, and the target platform layer with its required data types. The type mapping table acts as a bridge between these segmented layers, allowing each layer to maintain its own complexity characteristics independently. This segmentation enables the graphical control model to remain simple while still achieving comprehensive data type coverage through the mapping mechanism.
3Reliability
If code generation creates variables for each block output, then type safety is ensured, but the generated code size increases unnecessarily
Solution Approach 1:
The patent applies optimization techniques to the generated code that identify and remove redundant variable declarations. By analyzing the control flow and data dependencies in the block diagram, the system determines which variables can be eliminated or merged without compromising type safety. This discarding of unnecessary variables reduces code size while maintaining the reliability guarantees provided by explicit type handling.
Data Source
AI summary
A method for processing an unsupported signal type in a graphical control model of a development platform includes: storing, by a computer system, a specification containing at least one identifier for a variable of a data type corresponding to an unsupported signal type in a definition database, and when the control program for the target platform is created, using, by the computer system, the data memory object as a representative of the variable via the identifier.