HIL Launcher Automates Component Startup Sequence

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current hardware-in-the-loop (HIL) simulation setups face challenges in orchestrating a complex startup process due to human error in launching software applications in the correct order and establishing proper interconnectivity, leading to inaccurate and inconsistent simulation outputs, which can result in improper development and testing of controllers.

Innovation Solution

A launcher application is introduced to automate the startup and interconnectivity process by receiving sequence and interconnectivity information for software components, ensuring they are launched in the correct order and monitored for failures, using configuration files that can be reused across various simulation environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual startup process is used for HIL simulation, then flexibility in configuration is maintained, but human error occurs in launching software applications in correct order and establishing proper interconnectivity

Engineering Contradiction:
Improvesimulation output accuracyVSAvoidmanual configuration complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs self-configuration through automated detection and establishment of interconnectivity between software components. The launcher application automatically identifies components, determines their relationships, and configures connections without requiring manual intervention, thereby eliminating human error while maintaining adaptability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements automated monitoring and feedback mechanisms to track the startup process, detect failures, and verify proper interconnectivity establishment. This feedback loop ensures reliable simulation outputs by continuously monitoring component status and correcting issues automatically.

Inventive Principle:
Principle #23Feedback

2Reliability

If automated launcher application is implemented, then consistency and accuracy of simulation results improve, but system complexity increases

Engineering Contradiction:
Improvesimulation consistencyVSAvoidlauncher application structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The launcher application is divided into distinct functional modules: component detection module, interconnectivity analysis module, startup orchestration module, and failure monitoring module. Each module handles a specific aspect of the automated startup process, making the overall system more manageable and maintainable despite its complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The launcher application is designed as a universal platform that can handle multiple software components, various interconnectivity patterns, and different failure scenarios through a single unified interface. This multi-functionality reduces the need for multiple specialized tools and simplifies the user interaction model.

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

3Reliability

If extensive training is provided for manual configuration, then operational accuracy improves, but time consumption and cost increase

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidtraining duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system eliminates the need for extensive training by implementing self-service automation. The launcher application automatically performs component detection, interconnectivity analysis, and configuration without requiring users to have specialized knowledge or undergo lengthy training programs.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The automated launcher application acts as an intermediary between the user and the complex simulation environment. It translates simple user actions into complex automated processes, shielding users from technical complexity while delivering accurate results.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240193073A1Configuring a launch of components of a hardware-in-the-loop simulation environment
Publication Date: 2024.06.13 DISNEY ENTERPRISES INC
  • US20240193073A1 patent drawing
  • US20240193073A1 patent drawing
  • US20240193073A1 patent drawing

AI summary

In some implementations, a hardware-in-the-loop simulation (HIL) platform may receive component information regarding a plurality of software components of an HIL simulation environment. The component information may be received using a launcher application of the HIL simulation platform. The component information may include sequence information indicating a sequence for launching the plurality of software components during an HIL simulation, and interconnectivity information indicating an interdependency between two or more software components of the plurality of software components. The HIL simulation platform may receive a request to perform the HIL simulation. The HIL simulation platform may execute, based on the request, a computer model to perform the HIL simulation. Executing the computer model to perform the HIL simulation comprises launching, using the launcher application, the plurality of software components in an order that is based on the sequence.