Vehicle Simulation System for Software-in-the-Loop Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current vehicle simulation systems, such as HIL testing, require expensive physical or real-time simulated loads and are limited in flexibility, especially when testing vehicle control modules written in C code, and do not allow for early development cycle evaluations without special hardware.

Innovation Solution

A vehicle simulation system comprising a compiler, parser, wrapper, modeling, and simulation module that generates compatible object code, definitions, and model-based source code for a virtual model, enabling software-in-the-loop testing without physical hardware, allowing for early development cycle evaluations and flexibility in simulating vehicle control systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If HIL testing with physical loads or real-time simulated loads is used, then testing effectiveness is improved, but development cost increases and testing can only be performed late in the development cycle

Engineering Contradiction:
Improvetesting effectivenessVSAvoiddevelopment cycle timing
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a virtual copy of the vehicle control module through software-in-the-loop simulation. Instead of using physical hardware or real-time simulated loads, the system generates a virtual model that replicates the control module's behavior, allowing early testing in the development cycle without requiring actual hardware components.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent replaces the mechanical/physical testing system with a software-based simulation system. The virtual model substitutes for physical loads and hardware devices, enabling testing to occur in a software environment rather than requiring physical infrastructure, thereby allowing earlier development cycle evaluation.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Measurement precision

If HIL testing with physical loads is used, then testing accuracy is improved, but device complexity and cost increase

Engineering Contradiction:
Improvetesting accuracyVSAvoidhardware requirements
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent creates a virtual representation of the control module that captures its essential behaviors and characteristics. This virtual model serves as a simplified copy that maintains testing accuracy for software validation while eliminating the need for complex physical hardware setups, signal simulators, and specialized testing equipment.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent extracts the essential functional behavior of the control module from its physical hardware implementation. By separating the control logic from the hardware dependencies, the system creates a standalone virtual model that can be tested independently without requiring the full physical system, thereby reducing device complexity while preserving testing accuracy.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If cross-compiler is used to generate object code, then operating system compatibility is improved, but code conversion complexity increases

Engineering Contradiction:
Improveoperating system compatibilityVSAvoidcode conversion process
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a cross-compiler as an intermediary tool that bridges different operating system environments. The cross-compiler translates source code written for one operating system into object code compatible with another operating system, enabling the virtual model to run on different platforms without manually rewriting code, thus managing conversion complexity through automated translation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal code generation approach where the cross-compiler can produce object code for multiple different operating systems from a single source code base. This multi-functionality allows the same virtual model to be adapted to various operating system environments (Windows, Linux, QNX, etc.) without requiring separate development efforts for each platform.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8739049B2Vehicle system modeling systems and methods
Publication Date: 2014.05.27 GM GLOBAL TECHNOLOGY OPERATIONS LLC
  • US8739049B2 patent drawing
  • US8739049B2 patent drawing
  • US8739049B2 patent drawing

AI summary

A vehicle simulation system includes a compiler module, a parser module, a wrapper module, a modeling module, and a simulation module. The compiler module generates object code that is compatible with a first type of operating system based on source code that is executable by a vehicle control module and that is compatible with a second type of operating system. The parser module generates a definitions file and an extensible markup language (XML) file based on the source code and the object code. The wrapper module generates a library file based on the object code and the definitions file. The modeling module generates model-based source code for a virtual model based on the XML file and a user configuration of the virtual model. The simulation module simulates operation of a plant of a vehicle with the virtual model.