Driveline Fault Diagnostics Using Shared Memory Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing automotive fault diagnostic systems face challenges such as programmatic rigidity, delays in integrating diagnostic applications into existing control architectures, and susceptibility to cascading component faults, which hinder efficient vehicle development and increase production time and costs.
Innovation Solution
A vehicle system with a controller comprising a first and second processing unit and a shared memory unit, where instructions are stored to efficiently transfer data between processing units, allowing independent updates of control and diagnostic applications without accessing firmware functions, and operating mechanical components in a fault state to prevent degradation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If fault diagnostic standards are implemented with programmatic rigidity, then diagnostic accuracy is improved, but integration into existing control architecture is hindered and development time increases
Solution Approach 1:
The system separates fault diagnostic functions from control functions by implementing them on different processing units within the controller. The diagnostic application runs independently on a first processing unit while control applications run on a second processing unit, allowing both to be updated and integrated without mutual interference, thus reducing development time while maintaining diagnostic accuracy
Solution Approach 2:
A shared memory unit acts as an intermediary between the diagnostic processing unit and control processing unit. This allows data to be exchanged between the two independent applications without requiring firmware function access or direct communication protocols, simplifying integration while maintaining diagnostic rigor
2Adaptability or versatility
If memory is partitioned between control and fault applications, then independence of applications is improved, but data access complexity increases due to firmware function requirements
Solution Approach 1:
The shared memory unit serves as a simplified intermediary that replaces complex firmware function calls for data access. Both diagnostic and control applications can read/write to the shared memory using standard memory access operations, eliminating the need for firmware intermediaries and reducing data access complexity while maintaining application independence
3Loss of information
If fault diagnostic functions access data through firmware functions, then data retrieval is achieved, but the system becomes susceptible to cascading component faults
Solution Approach 1:
By placing the diagnostic application on a separate processing unit from the control application, the system segments the data access paths. The diagnostic unit reads data directly from the shared memory unit without needing to access control application memory spaces or trigger firmware functions, thereby isolating diagnostic operations from potential control faults and preventing cascading failures
Data Source
AI summary
Methods and systems are provided for driveline control and diagnostics. In one example, a vehicle system may include a controller with instructions stored in a first memory unit and when executed by a first processing unit cause the controller to write mechanical vehicle component operating data to a shared memory unit. The controller further includes instructions stored in a second memory unit that when executed by a second processing unit cause the controller to read the mechanical vehicle component operating data to determine data validity.