HIL Test Unit Model Linking Without Submodel Recompilation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The development of control units is complex, and existing hardware-in-the-loop simulators are costly and inflexible, especially when testing different variants or replacing individual submodels, as they require recompilation and reconfiguration of communication links between submodels.

Innovation Solution

A method for generating a technical system model executable on a test unit, where communication links between submodels are established based on communication characteristics and definitions, allowing for flexible configuration and replacement of submodels without recompiling, using separate address spaces and processors for real-time-capable testing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If communication links between submodels are configured before compilation in traditional HIL simulators, then the system ensures integrated technical system functionality, but the cost and complexity increase significantly when different variants are tested or submodels are replaced

Engineering Contradiction:

Improveflexibility in testing different variants and replacing submodelsVSAvoidcomplexity of recompilation and reconfiguration process

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the communication configuration process from the submodel compilation process. Communication characteristics are identified after compilation by analyzing metadata in the executable submodels, allowing independent configuration without recompiling the submodels themselves. This segmentation enables flexible variant testing and submodel replacement while maintaining system integration.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary identification of communication characteristics during the compilation phase by embedding metadata about communication interfaces, data types, and communication partners into the executable submodels. This preliminary action enables later flexible configuration and replacement without recompilation, as the communication information is already prepared and stored in the compiled artifacts.

Inventive Principle:

Principle #10Preliminary action

2Productivity

If submodels are compiled into executable code with fixed communication links, then execution efficiency is improved, but the ability to replace individual submodels without recompilation is lost

Engineering Contradiction:

Improveexecution efficiency of the technical system modelVSAvoidability to replace submodels without recompilation

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent creates a copy of communication information in the form of metadata embedded in the executable submodels. This metadata copy contains all necessary communication characteristics (communication partners, data types, interfaces) that can be read and used for configuration without accessing or recompiling the original source code. This copying mechanism enables both efficient execution and flexible replacement.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent changes the state of communication information from source-code-level parameters to compiled-metadata parameters. By storing communication characteristics as metadata in the executable format, the system can modify communication configurations (change parameters) without recompiling the submodels, thus maintaining execution efficiency while enabling adaptability.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If communication characteristics are identified from source code before compilation, then communication links can be established, but the process requires recompilation when any changes are made

Engineering Contradiction:

Improveaccuracy of communication link establishmentVSAvoidtime required for recompilation and reconfiguration

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent performs the action of identifying communication characteristics during compilation and embeds them as metadata in the executable submodels. This preliminary identification ensures accuracy of communication link establishment while eliminating the need for recompilation during later modifications, as the communication information is already captured and stored in the compiled artifacts.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces metadata as an intermediary between the source code communication definitions and the runtime communication link establishment. This metadata intermediary contains all necessary communication characteristics and can be read without accessing source code, enabling accurate communication configuration without recompilation and reducing time loss when changes are needed.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11022967B2Method for generating a technical system model, executable on a test unit, and the test unit

Publication Date: 2021.06.01 DSPACE DIGITAL SIGNAL PROCESSING & CONTROL ENGINEERING GMBH

AI summary

A method for generating a technical system model executable on a test unit, wherein the test unit and the executable model are designed for real-time-capable testing of a control unit connected to the test unit, and wherein the executable model is constructed from a plurality of executable submodels communicating with each other, wherein each executable submodel has a separate address space and/or is executed on a separate processor or separate processor core when a test of a control unit connected to the test unit is being run.