Telematic Logger Component for Automated Fault Root Cause Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current automotive telematic systems face challenges in efficiently logging and diagnosing complex malfunctions, particularly in volatile systems with many interdependent components, leading to inconclusive results and increased complexity in error detection and root cause analysis, which can result in delayed issue identification and resolution.
Innovation Solution
A telematic system that includes a logger component capable of generating log files from application components, allowing for ad-hoc on-board logging without special equipment, and an analyzer component that performs automatic fault root cause analysis using pre-defined use cases and state flow diagrams to identify the root cause of issues.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional on-board diagnostics systems are used to detect problems early, then problem detection capability is improved, but device complexity increases due to the need for specialized scan tools and physical connections
Solution Approach 1:
The telematic system performs self-diagnosis and self-logging of errors without requiring external diagnostic equipment. The system automatically monitors its own components, logs errors to memory, and transmits diagnostic data wirelessly, eliminating the need for specialized scan tools and manual intervention.
Solution Approach 2:
A telematic control unit acts as an intermediary between various vehicle systems and the external world. It centralizes the logging and diagnostics functions, receiving data from multiple sources, processing errors, and managing wireless communication, thereby simplifying the overall system architecture.
2Measurement precision
If comprehensive logging of all system states is implemented, then measurement precision is improved, but loss of information increases due to the large volume of data requiring storage and transmission
Solution Approach 1:
The system extracts only the most relevant error information and diagnostic data for storage and transmission. Instead of logging all system states, it focuses on capturing error codes, timestamps, and critical system parameters that are essential for diagnosis, thereby reducing data volume while maintaining diagnostic effectiveness.
Solution Approach 2:
Different levels of logging detail are applied to different system components based on their importance and failure rates. Critical safety-related systems are logged with higher precision and frequency, while less critical systems use reduced logging, optimizing the balance between measurement precision and data management burden.
3Ease of operation
If manual diagnostics procedures are used for complex malfunctions, then ease of operation is maintained, but loss of time increases due to delayed issue identification and resolution
Solution Approach 1:
The system continuously and automatically performs diagnostics and logs errors in real-time, so that when a problem occurs, the diagnostic information is already available. This preliminary automated action eliminates the need for time-consuming manual inspection and speeds up issue identification while keeping the user interface simple.
Solution Approach 2:
The system provides continuous feedback about system health and detected errors through wireless communication to external devices. This automated feedback mechanism keeps users informed without requiring manual checking, reducing issue identification time while maintaining ease of operation through simple alert notifications.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
Various embodiments relate to a method and an apparatus for logging for telematic systems, comprising: an automotive telematic component, at least one processing unit, at least one application component providing a service of the telematic component, wherein the at least one application component is implemented in the at least one processing unit and adapted to transmit its state in the form of a logging message to a logger component, and the logger component implemented in a processing unit and adapted to receive the logging message from the at least one application component and to generate a log file based on the received logging message. Furthermore, the logged information is transmitted to on-board or off-board analysis components which provide respectively light-weight or full analysis of the logged data and represent the analysis in human-readable format. Additionally, a system is described for fully automated analysis of the log-files from predefined use cases based on identification of components, their messages, and additional metadata.