Collision-Related Diagnostic Trouble Code Identification System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current vehicle scan tools are unable to determine whether a diagnostic trouble code (DTC) is collision-related, posing challenges for insurance companies and vehicle repair professionals in assessing repair costs, as they struggle to differentiate between pre-existing and collision-induced malfunctions.

Innovation Solution

A computing system and method that determines whether a DTC is collision-related by matching the damaged vehicle portion with a reference vehicle portion associated with the vehicle model, using a scanner connected to the vehicle's electronic control unit to output a collision report.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If existing vehicle scan tools are used to read DTCs, then diagnostic trouble codes can be retrieved, but the tools cannot determine whether the DTCs are collision-related or pre-existing

Engineering Contradiction:
Improveinformation about DTC originVSAvoidscan tool functionality
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system segments the diagnostic process into distinct phases: (1) reading DTCs from the ECU, (2) obtaining collision data from the event data recorder, (3) comparing DTC timestamps with collision timestamps, and (4) categorizing DTCs as collision-related or pre-existing. This segmentation allows the system to retrieve comprehensive diagnostic information without overwhelming the user with undifferentiated data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by automatically recording collision event data (timestamp, location, severity) in the event data recorder before the actual diagnostic assessment is needed. This pre-recorded collision data is then used as a reference point to evaluate whether subsequently read DTCs are collision-related, eliminating the need for manual investigation of each DTC's origin.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If insurance companies require detailed DTC analysis to assess repair costs, then accurate cost estimation is improved, but the complexity of determining DTC origin increases

Engineering Contradiction:
ImproveDTC origin identificationVSAvoiddiagnostic system
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system implements feedback by automatically comparing DTC timestamps with collision event timestamps and providing immediate classification results. The event data recorder serves as a feedback mechanism that continuously monitors and records collision events, which then feed into the DTC assessment process to automatically determine whether each DTC is collision-related or pre-existing, eliminating manual analysis.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The diagnostic system performs self-service by automatically categorizing DTCs without requiring manual intervention from technicians or investigators. The system autonomously reads DTCs, compares them against recorded collision data, and generates a classified report indicating which DTCs are collision-related and which are pre-existing, thereby simplifying the insurance assessment process.

Inventive Principle:
Principle #25Self-service

3Loss of information

If vehicle body repair persons use complex scan tools to diagnose malfunctions, then diagnostic capability is improved, but the ease of operation deteriorates due to tool complexity

Engineering Contradiction:
Improvediagnostic informationVSAvoidscan tool usability
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system extracts only the essential diagnostic information needed for collision assessment by automatically filtering and categorizing DTCs based on their relationship to the collision event. Instead of presenting all raw diagnostic data, the system extracts and highlights only the collision-related DTCs, allowing body repair persons to focus on malfunctions caused by the collision without being overwhelmed by pre-existing issues.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system creates a simplified copy or representation of the diagnostic data by generating a categorized report that mirrors the actual DTCs but organizes them by collision relevance. This copied information structure maintains the essential diagnostic content while presenting it in an easily interpretable format that does not require deep technical expertise to understand.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11584321B2Method and system for reporting diagnostic trouble code set in vehicle is collision-related
Publication Date: 2023.02.21 SNAP ON INC
  • US11584321B2 patent drawing
  • US11584321B2 patent drawing
  • US11584321B2 patent drawing

AI summary

A method and computing system for determining whether a DTC set in a vehicle involved in a collision is collision-related or non-collision-related. The method can include determining a vehicle model associated with the vehicle, determining a DTC set within an ECU in the vehicle, determining a damaged portion in the vehicle, determining the DTC is collision-related, and outputting a collision report that indicates the DTC is collision-related. The determined damaged portion indicates where the vehicle was damaged by the collision. Determining the DTC is collision-related can include determining the damaged portion in the vehicle matches a reference vehicle portion associated with both a component attributable to setting the DTC and the vehicle model associated with the damaged vehicle. The collision report can indicate that a different DTC set by the same or a different ECU in the vehicle is non-collision-related.