Method and system for the validation of fault symptoms

• US 7,248,976 B2
• Filed: 07/16/2004
• Issued: 07/24/2007
• Est. Priority Date: 07/31/2003
• Status: Expired due to Fees

• Current Assignee: Continental Automotive GmbH (Continental AG)
• Original Assignee: Siemens AG
• Inventors: Thiveos, Konstantin
• Primary Examiner(s): NGHIEM, MICHAEL P
• Application Number:
  US10/566,560
• Publication Number:
  US 20060229829A1
• Time in Patent Office: 1,103 Days
• Field of Search: 702/59, 702182-185
• US Class Current: 702/59
• CPC Class Codes: G06F 11/2257 using expert systems

Abstract

For the purpose of validating fault symptoms appearing at driver outputs, a symptom validation unit is provided, within a final stage, which undertakes a validation or a preliminary validation, as applicable, on the basis of a classification of symptoms. By assigning the item of validation data “invalid” to symptoms which cannot be unambiguously identified, it is possible to suppress the further consideration of the symptoms, or to initiate further diagnoses of the final stage output concerned, as appropriate.

Claims

1. A method of validating fault symptoms appearing at driver outputs, which comprises the following steps:

recording a symptom, present at a driver output, and classifying the symptom into one of several classes of different symptoms by way of a symptom recognition unit;

with a symptom validation unit, assigning to the symptom an item of symptom validation data of “

valid”

or “

invalid”

in dependence on a classification resulting from the classifying step;

if the symptom validation item is “

valid,”

reporting a classification that is valid, or if the symptom validation item is “

invalid,”

reporting a classification that is invalid; and

reporting the item of symptom validation data.

2. The method according to claim 1, which comprises:

providing at least four classes for classifying a symptom;

classifying an unambiguously identifiable electrical fault as a symptom in class 1;

classifying a not unambiguously identifiable electrical fault as a symptom in class 2;

classifying a symptom as belonging to class 3 if an unambiguous determination is possible that no electrical fault is present; and

classifying a symptom as belonging to class 4 if no electrical fault is present, but the absence of the electrical fault cannot be unambiguously identified.

3. The method according to claim 2, which comprises, if a fault symptom is classified as belonging to class 1, assigning the item of validation data “

valid”

to the fault symptom and reporting the classification together with the item of validation data.

4. The method according to claim 2, which comprises, if a fault symptom is classified as belonging to class 3, assigning the item of validation data “

valid”

to the fault symptom and reporting the classification together with the item of validation data.

5. The method according to claim 2, which comprises, if a fault symptom is classified as belonging to class 2 or class 4, assigning the item of validation data “

invalid”

to the fault symptom and reporting the classification as class 3 together with the item of validation data.

6. The method according to claim 1, which comprises, if the item of validation data is reported as “

invalid”

, causing the symptom validation unit to influence the respective driver output in order to acquire additional data about the fault symptom concerned.

7. A system for assigning an information item “

valid”

or “

invalid”

to fault symptoms appearing at a driver output, comprising;

a final stage including a symptom recognition unit with a symptom validation unit and a symptom output unit;

said symptom recognition unit recording symptoms present at the driver output and classifying each symptom into one of several classes of different symptoms;

said symptom validation unit being configured to assign to a symptom an item of symptom validation data of “

valid”

or “

invalid”

in dependence on a classification by said symptom recognition unit;

a symptom reporting unit connected to said final stage and to receive from said system output unit the classification and the item of validation data, and configured to report, if the information item “

valid”

is assigned, a classification that is valid and the symptom validation information, or, if the information item “

invalid”

is assigned, a classification that is invalid and the item of symptom validation data.

8. The system according to claim 7, wherein at least four classes are available for classifying a symptom, including class 1, class 2, class 3, and class 4, and wherein:

an unambiguously identifiable electrical fault is classified as a symptom in class 1;

a not unambiguously identifiable electrical fault is classified as a symptom in class 2;

a symptom is classified as belonging to class 3 if an unambiguous determination is possible that no electrical fault is present; and

a symptom is classified as belonging to class 4 if no electrical fault is present, but an absence of an electrical fault cannot be unambiguously identified.

9. The system according to claim 8, wherein, if a fault symptom is classified as belonging to class 1, said symptom validation unit assigns the item of validation data “

valid”

to the fault symptom and said symptom reporting unit reports the classification together with the item of validation data.

10. The system according to claim 8, wherein, if a fault symptom is classified as belonging to class 3, said symptom validation unit assigns the item of validation data “

valid”

to the fault symptom and said symptom reporting unit reports the classification together with the item of validation data.

11. The system according to claim 8, wherein, if a fault symptom is classified as belonging to class 2 or class 4, said symptom validation unit assigns the item of validation data “

invalid”

to the fault symptom, and said symptom reporting unit reports a class 3 classification together with the item of validation data.

12. The method according to claim 7, which comprises, when the item of validation data is reported as “

invalid”

, said symptom validation unit is caused to influence the respective driver output in order to acquire additional data about the fault symptom concerned.