EP1376094B1 - Method and device for diagnosing components of a vehicle - Google Patents

Method and device for diagnosing components of a vehicle Download PDF

Info

Publication number
EP1376094B1
EP1376094B1 EP20030007512 EP03007512A EP1376094B1 EP 1376094 B1 EP1376094 B1 EP 1376094B1 EP 20030007512 EP20030007512 EP 20030007512 EP 03007512 A EP03007512 A EP 03007512A EP 1376094 B1 EP1376094 B1 EP 1376094B1
Authority
EP
European Patent Office
Prior art keywords
fault
components
data
vehicle
input
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP20030007512
Other languages
German (de)
French (fr)
Other versions
EP1376094A3 (en
EP1376094A2 (en
Inventor
Juergen Betz
Winfried Maihs
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Robert Bosch GmbH
Original Assignee
Robert Bosch GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Robert Bosch GmbH filed Critical Robert Bosch GmbH
Publication of EP1376094A2 publication Critical patent/EP1376094A2/en
Publication of EP1376094A3 publication Critical patent/EP1376094A3/en
Application granted granted Critical
Publication of EP1376094B1 publication Critical patent/EP1376094B1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841Registering performance data
    • G07C5/085Registering performance data using electronic data carriers
    • FMECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F02COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
    • F02DCONTROLLING COMBUSTION ENGINES
    • F02D41/00Electrical control of supply of combustible mixture or its constituents
    • F02D41/22Safety or indicating devices for abnormal conditions
    • FMECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F02COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
    • F02DCONTROLLING COMBUSTION ENGINES
    • F02D41/00Electrical control of supply of combustible mixture or its constituents
    • F02D41/24Electrical control of supply of combustible mixture or its constituents characterised by the use of digital means
    • F02D41/26Electrical control of supply of combustible mixture or its constituents characterised by the use of digital means using computer, e.g. microprocessor
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/008Registering or indicating the working of vehicles communicating information to a remotely located station

Definitions

  • the invention relates to a method and a device for testing components of a vehicle.
  • Such components may in particular be networked component systems of the vehicle, wherein the networking z. B. can be provided via a CAN bus, MOST or D2B bus.
  • An examination of the components of vehicles for possible errors is carried out on the one hand at the vehicle manufacturer in the context of a final inspection or final inspection. Furthermore, such testing or diagnostic procedures are carried out in the workshop in the event of complaints by the customer or regular service investigations.
  • a tester can also be connected to an internal data bus, for.
  • As the CAN bus to read out some components via the bus system to be connected.
  • DE 198 50 990 A1 describes a control device for motor vehicles with connection means for its connection to a diagnostic test device, wherein data relevant to the operation of the diagnostic test device, in particular data storage or documentation information, are stored in the control device and via the connection means to the diagnosis Test device and / or a computer for controlling the diagnostic test device are transferable. This allows the diagnostic test device or a computer controlling this without the use of additional paper files or floppy disks.
  • the relevant information in particular factory information, are stored in the control unit and can via a z.
  • B. serial interface can be read by the diagnostic test device.
  • DE 44 00 079 A1 describes a method for testing electronic control units and a control unit for using such a method, wherein in the control unit, a program module for the test of the control unit is stored, which is processed during the test.
  • a microcomputer of the control unit receives test commands from an external test device, which is connected to the control unit via a serial interface.
  • the control unit sends data, in particular measurement results and test results, to the external test device, which evaluates them and displays them.
  • test methods and test devices only allow a costly check or diagnosis of the individual components, in particular without taking into account the effects of networking of the individual components and the resulting errors.
  • test methods are usually easy to use and only allow a fully automatic test or manual testing of individual components through a complex initialization of individual test routines.
  • inventive method according to claim 1 and the inventive device according to claim 15, in contrast, have the particular advantage that a reliable detection of the presence of possible errors in the individual components and in the networked component system and a detailed examination of the error is possible. In this case, a small operating effort is required, wherein advantageously still a manual testing of individual components is possible.
  • the manual input of the vehicle data can via a keyboard or other input device, eg. B. a bar code scanner, by workshop personnel at a service investigation or at the removal in the factory to be entered.
  • the vehicle data can z. B. the VIN, equipment etc. include.
  • an actual / nominal comparison of the entered vehicle data with the stored vehicle data or vehicle data detected in the vehicle is carried out in particular, subsequently the software / hardware levels of the components and configurations are queried and the stored data of the error memory of the components is queried.
  • the individual components are checked individually as well as in the networked component system or overall system. All here determined errors - which also z. B.
  • deviations between stored vehicle data and input vehicle data may - are subsequently recognized as an error case, more detailed check routines are performed in the event of an error, and in the absence of an error case the operator still by issuing a corresponding display signal the ability to input a test signal for detailed manual Testing is given in the test routines.
  • determined error data are stored in the vehicle components. This can be done, in particular, in the control devices assigned to the faulty components.
  • the storage can be done in particular such that a subsequent falsification of the data is not possible, for. B. by storing in a programmable read-only memory (PROM).
  • PROM programmable read-only memory
  • the errors in particular the probable localization of faulty components, displayed in the vehicle and the operator the possibility of a manual configuration of the system, eg. B. also partially automatically be given.
  • the error memories are advantageously cleared and - if no manual abort is desired - the method is reset again to the step of error detection. If a manual abort is desired, advantageously a remote data transmission, e.g.
  • a vehicle 1 has a control device 2, z.
  • the control device 2, the data bus system 3 and the vehicle components 4 form a networked component system.
  • a test device 5 is connected to the control device 2 via data lines 6.
  • the test device 5 z. B. also have a CAN bus interface 7; Alternatively, the data lines 6 can also be connected directly.
  • the test method according to the invention is carried out, wherein an online data connection via an Internet interface 8 and an Internet 9 to a central database 10 is created.
  • the central database 10 receives data from a plurality of test devices 7, thereby forming an overall system 11 that continuously receives data.
  • the diagnostic method is started in step S1. It may in particular at the final inspection after the manufacture of the vehicle or during the inspection in a workshop, eg. B. in a regular inspection at service intervals or complaints by a customer.
  • Step S2 a self-test of the test apparatus 5 is carried out including the programs and test routines stored therein. This ensures that the required functions are ensured.
  • step S3 of z. B. the workshop personnel input data entered into the test device 5 manually, z. B. via keyboard or a barcode reader.
  • the input data relates to the relevant vehicle data including data about the equipment.
  • the logbook of the vehicle can be used for specification, in which the installed components and their changes are entered.
  • steps S4 to S6 whether an error occurs. For this purpose, it is first checked in the routine of step S4 whether the input data matches the data stored or detected in the vehicle. Subsequently, an output of the scope of the equipment and components of the vehicle can be done.
  • the tester and the stored test programs check the software and hardware levels of the connected components 4 in the networked component system, including the configurations of the individual components 4. The data stored in the components are read out and stored in the test apparatus 5.
  • step S5 an individual test of the components takes place here. Subsequently, the components in the networked component system are checked in step S6.
  • step S6 errors that occur due to the networking or the interaction of the individual components can not be detected which are not directly errors of the individual components 4.
  • a communication test is performed between all components 4 in the networked component system.
  • the individual networked systems are checked separately. Subsequently, the components and functionalities are displayed in step S6.
  • test steps S10 to S15 are initiated in the decision step S7. If no error is detected, a manual entry into the test sequences S10 to S15 is made possible in step S8; This can be done in particular by the workshop staff in customer complaints. If a manual check is desired or if a rework is made at the factory, the procedure is set to step S10.
  • step S10 the test routine required for the detected error case is performed. Due to the test sequences provided here, a possible error can be precisely located. The test is carried out both on the individual components 4 and on the networked component system. Subsequently, in step S11, the results of the test in a vehicle component, e.g. As the assigned for the faulty component control device 2, stored. The storage may in particular by a read-only memory, for. As a PROM, take place, which can not be easily reset by unauthorized persons. As a result, warranty claims can be reviewed and remedied by the manufacturer. In step S12, the determined errors, in particular the error data of the components 4 determined in step S10, are used as display data, e.g. B.
  • display data e.g. B.
  • step S13 for display on a display of the tester 5, issued. This gives more details on the errors and possible sources of error.
  • the operator or in step S13 based on detailed information to determine the exact error.
  • the fault location in the vehicle z. B. displayed graphically on a display.
  • step S14 the individual systems can be manually or partially automatically configured by the operator.
  • step S15 the current error data in the error memories of the components or the control devices 2 of the components 4 are deleted.
  • step S16 it is subsequently queried whether a manual abort is desired or not. If no manual abort is desired, the process is returned to step S4 to again perform error detection.
  • step S16 a manual termination by the user is desired.
  • step S17 a connection to the database 10 via the Internet 9 is made in step S17.
  • the error data is transmitted to the database 10 for further processing, it being possible for a return response to be made by the central control and storage device 9 to remedy the error.
  • the database 10 thus collects errors of a variety of test methods, allowing extensive error collection and accurate statistical evaluation.
  • step S19 the error data recorded in the vehicle are subsequently printed out and stored in the vehicle and the entries in the error memory are deleted. If no manual check is desired in step S9, the error memories in the components are also cleared in step S18 and proceeded to step S19.
  • step S20 the process is ended.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Chemical & Material Sciences (AREA)
  • Combustion & Propulsion (AREA)
  • Mechanical Engineering (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
  • Test And Diagnosis Of Digital Computers (AREA)

Description

Die Erfindung betrifft ein Verfahren und eine Vorrichtung zur Prüfung von Komponenten eines Fahrzeugs. Derartige Komponenten können insbesondere vernetzte Komponentensysteme des Fahrzeugs sein, wobei die Vernetzung z. B. über einen CAN-Bus, MOST- oder D2B-Bus vorgesehen sein kann.The invention relates to a method and a device for testing components of a vehicle. Such components may in particular be networked component systems of the vehicle, wherein the networking z. B. can be provided via a CAN bus, MOST or D2B bus.

Eine Prüfung der Komponenten von Fahrzeugen auf mögliche Fehler hin erfolgt zum einen beim Fahrzeughersteller im Rahmen einer Endabnahme bzw. Endprüfung, Weiterhin erfolgen derartige Prüfungs- bzw. Diagnoseverfahren in der Werkstatt bei Beanstandungen des Kunden oder regelmäßigen Serviceuntersuchungen.An examination of the components of vehicles for possible errors is carried out on the one hand at the vehicle manufacturer in the context of a final inspection or final inspection. Furthermore, such testing or diagnostic procedures are carried out in the workshop in the event of complaints by the customer or regular service investigations.

Bei herkömmlichen Prüfungsverfahren und Prüfungsvorrichtungen erfolgt in der Regel eine Einzelüberprüfung der jeweiligen Komponenten. Hierbei kann ein Prüfgerät auch an einen internen Datenbus, z. B. den CAN-Bus, zum Auslesen einiger Komponenten über das Bus-System angeschlossen werden.In conventional testing methods and testing devices, a single check of the respective components is usually carried out. In this case, a tester can also be connected to an internal data bus, for. As the CAN bus, to read out some components via the bus system to be connected.

Die DE 198 50 990 A1 beschreibt ein Steuergerät für Kraftfahrzeuge mit Verbindungsmitteln zu seiner Verbindung mit einem Diagnose-Testgerät, wobei für den Betrieb des Diagnose-Testgerätes relevante Daten, insbesondere Datenablage- oder Dokumentationsinformationen, im Steuergerät abgelegt sind und über die Verbindungsmittel auf das Diagnose-Testgerät und/oder einen Computer zur Steuerung des Diagnose-Testgerätes übertragbar sind. Hierdurch kann das Diagnose-Testgerät bzw. ein dieses steuernder Computer ohne Verwendung zusätzlicher Papierfiles oder Disketten verwendet werden. Die relevanten Informationen, insbesondere auch werkseitige Informationen, sind in dem Steuergerät abgelegt und können über ein z. B. serielles Interface von dem Diagnose-Testgerät ausgelesen werden.DE 198 50 990 A1 describes a control device for motor vehicles with connection means for its connection to a diagnostic test device, wherein data relevant to the operation of the diagnostic test device, in particular data storage or documentation information, are stored in the control device and via the connection means to the diagnosis Test device and / or a computer for controlling the diagnostic test device are transferable. This allows the diagnostic test device or a computer controlling this without the use of additional paper files or floppy disks. The relevant information, in particular factory information, are stored in the control unit and can via a z. B. serial interface can be read by the diagnostic test device.

Die DE 44 00 079 A1 beschreibt ein Verfahren zur Prüfung von elektronischen Steuergeräten und ein Steuergerät zur Verwendung eines derartigen Verfahrens, wobei im Steuergerät ein Programmmodul für die Prüfung des Steuergerätes abgespeichert ist, das während der Prüfung abgearbeitet wird. Bei der Prüfung empfängt ein Mikrorechner des Steuergerätes Prüfbefehle von einem externen Prüfgerät, das über eine serielle Schnittstelle mit dem Steuergerät verbunden ist. Das Steuergerät sendet während der Prüfung Daten, insbesondere Messergebnisse und Prüfergebnisse, an das externe Prüfgerät, das diese auswertet und zur Anzeige bringt.DE 44 00 079 A1 describes a method for testing electronic control units and a control unit for using such a method, wherein in the control unit, a program module for the test of the control unit is stored, which is processed during the test. During the test, a microcomputer of the control unit receives test commands from an external test device, which is connected to the control unit via a serial interface. During the test, the control unit sends data, in particular measurement results and test results, to the external test device, which evaluates them and displays them.

Derartige Prüfverfahren und Prüfvorrichtungen ermöglichen jedoch nur eine aufwendige Überprüfung bzw. Diagnose der einzelnen Komponenten, insbesondere auch ohne Berücksichtigung der Auswirkungen der Vernetzung der einzelnen Komponenten und der sich hieraus ergebenden Fehler. Weiterhin sind derartige Prüfverfahren in der Regel bedienungsaufwendig und ermöglichen lediglich eine vollautomatische Prüfung oder eine manuelle Prüfung einzelner Komponenten durch eine aufwendige Initialisierung einzelner Prüfroutinen.However, such test methods and test devices only allow a costly check or diagnosis of the individual components, in particular without taking into account the effects of networking of the individual components and the resulting errors. Furthermore, such test methods are usually easy to use and only allow a fully automatic test or manual testing of individual components through a complex initialization of individual test routines.

Das erfindungsgemäße Verfahren nach Anspruch 1 und die erfindungsgemäße Vorrichtung nach Anspruch 15 weisen demgegenüber insbesondere den Vorteil auf, dass eine sichere Detektion auf das Vorliegen möglicher Fehler in den einzelnen Komponenten sowie in dem vernetzten Komponentensystem und eine detaillierte Prüfung der Fehler möglich ist. Hierbei ist ein geringer Bedienungsaufwand erforderlich, wobei vorteilhafterweise dennoch eine manuelle Prüfung einzelner Komponenten möglich ist.The inventive method according to claim 1 and the inventive device according to claim 15, in contrast, have the particular advantage that a reliable detection of the presence of possible errors in the individual components and in the networked component system and a detailed examination of the error is possible. In this case, a small operating effort is required, wherein advantageously still a manual testing of individual components is possible.

Die manuelle Eingabe der Fahrzeugdaten kann über eine Tastatur oder eine andere Eingabeeinrichtung, z. B. einem Barcodescanner, durch Werkstattpersonal bei einer Serviceuntersuchung oder bei der Entabnahme im Herstellerwerk eingegeben werden. Die Fahrzeugdaten können z. B. die Fahrgestellnummer, Ausstattungen etc. umfassen. In der nachfolgenden Fehlerdetektion wird insbesondere ein Ist-Soll-Vergleich der eingegebenen Fahrzeugdaten mit den gespeicherten Fahrzeugdaten bzw. im Fahrzeug erkannten Fahrzeugdaten durchgeführt, nachfolgend die Software/Hardware-Stände der Komponenten und Konfigurationen abgefragt und die gespeicherten Daten des Fehlerspeichers der Komponenten abgefragt. Die einzelnen Komponenten werden sowohl einzeln als auch im vernetzten Komponentensystem bzw. Gesamtsystem überprüft. Sämtliche hierbei ermittelten Fehler - welche auch z. B. Abweichungen zwischen gespeicherten Fahrzeugdaten und eingegebenen Fahrzeugdaten umfassen können - werden anschließend als Fehlerfall erkannt, wobei bei Vorliegen eines Fehlerfalls detailliertere Prüfroutinen durchgeführt werden, und bei Ausbleiben eines Fehlerfalls dem Bediener dennoch durch Ausgabe eines entsprechenden Anzeigesignals die Möglichkeit zur Eingabe eines Prüfungssignals zur detaillierten manuellen Prüfung in den Prüfroutinen gegeben wird.The manual input of the vehicle data can via a keyboard or other input device, eg. B. a bar code scanner, by workshop personnel at a service investigation or at the removal in the factory to be entered. The vehicle data can z. B. the VIN, equipment etc. include. In the subsequent error detection, an actual / nominal comparison of the entered vehicle data with the stored vehicle data or vehicle data detected in the vehicle is carried out in particular, subsequently the software / hardware levels of the components and configurations are queried and the stored data of the error memory of the components is queried. The individual components are checked individually as well as in the networked component system or overall system. All here determined errors - which also z. B. deviations between stored vehicle data and input vehicle data may - are subsequently recognized as an error case, more detailed check routines are performed in the event of an error, and in the absence of an error case the operator still by issuing a corresponding display signal the ability to input a test signal for detailed manual Testing is given in the test routines.

Erfindungsgemäß werden ermittelte Fehlerdaten in den Fahrzeugkomponenten gespeichert. Dies kann insbesondere in den den fehlerhaften Komponenten zugeordneten Steuereinrichtungen erfolgen. Die Speicherung kann insbesondere derartig erfolgen, dass eine nachträgliche Fälschung der Daten nicht möglich ist, z. B. durch Abspeichern in einem programmierbaren Festwertspeicher (PROM). Nachfolgend können die Fehler, insbesondere auch die voraussichtliche Lokalisierung fehlerhafter Komponenten, im Fahrzeug angezeigt und dem Bediener die Möglichkeit einer manuellen Konfiguration des Systems, z. B. auch teilweise automatisch, gegeben werden. Nach den Prüfroutinen werden vorteilhafterweise die Fehlerspeicher gelöscht und - falls kein manueller Abbruch erwünscht ist - das Verfahren erneut zu dem Schritt der Fehlerdetektion zurückgesetzt. Falls ein manueller Abbruch erwünscht ist, wird vorteilhafterweise eine Datenfernübertragung, z. B. eine Online-Verbindung, zu einer zentralen Steuer- und Speichereinrichtung, z. B. einer Hotline des Herstellers, hergestellt, um die ermittelten Fehlerdaten zu übertragen und ggf. Daten zur Behebung der Fehler abzurufen. Durch eine nachfolgende Speicherung der Abläufe und hierbei gewonnenen Daten im Fahrzeug kann ein späterer Rückgriff auf diese Fehlerdaten ermöglicht werden.According to the invention, determined error data are stored in the vehicle components. This can be done, in particular, in the control devices assigned to the faulty components. The storage can be done in particular such that a subsequent falsification of the data is not possible, for. B. by storing in a programmable read-only memory (PROM). Subsequently, the errors, in particular the probable localization of faulty components, displayed in the vehicle and the operator the possibility of a manual configuration of the system, eg. B. also partially automatically be given. After the test routines, the error memories are advantageously cleared and - if no manual abort is desired - the method is reset again to the step of error detection. If a manual abort is desired, advantageously a remote data transmission, e.g. An online connection, to a central control and storage device, e.g. As a hotline of the manufacturer, to transmit the error data determined and possibly retrieve data to correct the error. By a subsequent storage of the processes and data obtained in the vehicle, a later recourse to these error data can be made possible.

Die Erfindung wird im Folgenden anhand der beiliegenden Zeichnungen an einer Ausführungsform näher erläutert. Es zeigen:

Fig. 1
ein Fahrzeug mit einer angeschlossenen Prüfvorrichtung;
Fig. 2
ein Flussdiagramm der erfindungsgemäßen Verfahrens.
The invention will be explained in more detail below with reference to the accompanying drawings to an embodiment. Show it:
Fig. 1
a vehicle with a connected test device;
Fig. 2
a flow chart of the method according to the invention.

Ein Fahrzeug 1 weist eine Steuereinrichtung 2, z. B. das Motorsteuergerät, auf, das über ein Datenbussystem, z. B. einen CAN-Bus 3, mit Fahrzeugkomponenten 4 verbunden ist. Die Steuereinrichtung 2, das Datenbussystem 3 und die Fahrzeugkomponenten 4 bilden ein vernetztes Komponentensystem. Eine Prüfvorrichtung 5 wird über Datenleitungen 6 an die Steuereinrichtung 2 angeschlossen. Hierzu kann die Prüfvorrichtung 5 z. B. ebenfalls eine CAN-Bus-Schittstelle 7 aufweisen; alternativ hierzu können die Datenleitungen 6 auch direkt angeschlossen werden. Mit der Prüfvorrichtung5 wird das erfindungsgemäße Prüfverfahren durchgeführt, wobei eine Online-Datenverbindung über eine Internet-Schnittstelle 8 und ein Internet 9 zu einer zentralen Datenbank 10 geschaffen wird. Die zentrale Datenbank 10 nimmt Daten von mehreren Prüfvorrichtungen 7 auf, wodurch ein Gesamtsystem 11 gebildet wird, das kontinuierlich Daten aufnimmt.A vehicle 1 has a control device 2, z. As the engine control unit, which via a data bus system, for. B. a CAN bus 3, is connected to vehicle components 4. The control device 2, the data bus system 3 and the vehicle components 4 form a networked component system. A test device 5 is connected to the control device 2 via data lines 6. For this purpose, the test device 5 z. B. also have a CAN bus interface 7; Alternatively, the data lines 6 can also be connected directly. With the test device 5, the test method according to the invention is carried out, wherein an online data connection via an Internet interface 8 and an Internet 9 to a central database 10 is created. The central database 10 receives data from a plurality of test devices 7, thereby forming an overall system 11 that continuously receives data.

Bei dem in Fig. 2 gezeigten erfindungsgemäßen Prüfverfahren wird in Schritt S1 das Diagnoseverfahren gestartet. Es kann insbesondere bei der Endabnahme nach der Herstellung des Fahrzeugs oder bei der Überprüfung in einer Werkstatt, z. B. bei einer Regeluntersuchung in Serviceintervallen oder bei Beanstandungen durch einen Kunden, durchgeführt werden. Im nachfolgenden Schritt S2 wird ein Selbsttest der Prüfvorrichtung 5 einschließlich der in ihr gespeicherten Programme und Prüfroutinen durchgeführt. Hierdurch wird eine Sicherstellung der erforderlichen Funktionen gewährleistet. Nachfolgend werden in Schritt S3 von z. B. dem Werkstattpersonal Eingabedaten in die Prüfvorrichtung 5 manuell eingegeben, z. B. über Tastatur oder einen Barcodeleser. Die Eingabedaten betreffen die relevanten Fahrzeugdaten einschließlich Daten über die Ausstattung. Hierzu kann zur Spezifizierung das Bordbuch des Fahrzeugs verwendet werden, in dem die verbauten Komponenten und deren Änderungen eingetragen sind.In the test method according to the invention shown in FIG. 2, the diagnostic method is started in step S1. It may in particular at the final inspection after the manufacture of the vehicle or during the inspection in a workshop, eg. B. in a regular inspection at service intervals or complaints by a customer. In the following Step S2, a self-test of the test apparatus 5 is carried out including the programs and test routines stored therein. This ensures that the required functions are ensured. Subsequently, in step S3 of z. B. the workshop personnel input data entered into the test device 5 manually, z. B. via keyboard or a barcode reader. The input data relates to the relevant vehicle data including data about the equipment. For this purpose, the logbook of the vehicle can be used for specification, in which the installed components and their changes are entered.

Nachfolgend wird in den Schritten S4 bis S6 ermittelt, ob ein Fehlerfall vorliegt. Hierzu wird in der Routine des Schrittes S4 zunächst überprüft, ob die Eingabedaten mit den gespeicherten bzw. im Fahrzeug erkannten Daten übereinstimmen. Anschließend kann eine Ausgabe des Umfangs der Ausstattungen und Komponenten des Fahrzeugs erfolgen. Im Schritt S5 werden von der Prüfvorrichtung und den gespeicherten Prüfprogrammen die Software- und Hardware-Stände der angeschlossenen Komponenten 4 im vernetzten Komponentensystem überprüft, einschließlich der Konfigurationen der einzelnen Komponenten 4. Die in den Komponenten gespeicherten Daten werden ausgelesen und in der Prüfvorrichtung 5 gespeichert. In Schritt S5 erfolgt hierbei eine Einzelprüfung der Komponenten. Anschießend werden in Schritt S6 die Komponenten im vernetzten Komponentensystem überprüft. Durch diesen Schritt können durch die Vernetzung bzw. das Zusammenwirken der einzelnen Komponenten auftretende Fehler erkannt werden, die nicht direkt Fehler der einzelnen Komponenten 4 sind. Hierzu wird ein Kommunikationstest zwischen allen Komponenten 4 im vernetzten Komponentensystem durchgeführt. Bei mehreren vernetzten Systemen, insbesondere einem ersten vernetzten System der Ausstattungskomponenten bzw. Interieur-Komponenten, einem zweiten System der Betriebskomponenten bzw. für den Fahrbetrieb erforderlichen Komponenten und Funktionen und einem dritten System der sicherheitsrelevanten Komponenten, werden die einzelnen vernetzten Systeme separat überprüft. Anschließend werden in Schritt S6 die Komponenten und Funktionalitäten angezeigt.Subsequently, it is determined in steps S4 to S6 whether an error occurs. For this purpose, it is first checked in the routine of step S4 whether the input data matches the data stored or detected in the vehicle. Subsequently, an output of the scope of the equipment and components of the vehicle can be done. In step S5, the tester and the stored test programs check the software and hardware levels of the connected components 4 in the networked component system, including the configurations of the individual components 4. The data stored in the components are read out and stored in the test apparatus 5. In step S5, an individual test of the components takes place here. Subsequently, the components in the networked component system are checked in step S6. Through this step, errors that occur due to the networking or the interaction of the individual components can not be detected which are not directly errors of the individual components 4. For this purpose, a communication test is performed between all components 4 in the networked component system. In the case of several networked systems, in particular a first networked system of the equipment components or interior components, a second system of the operating components or components and functions required for the driving operation, and a third system of the safety-relevant components, the individual networked systems are checked separately. Subsequently, the components and functionalities are displayed in step S6.

Wird in den Schritten S4 bis S6 ein Fehler erkannt, werden in dem Entscheidungsschritt S7 die Prüfungsschritte S10 bis S15 eingeleitet. Wird kein Fehlerfall erkannt, wird in Schritt S8 ein manueller Einsprung in die Prüfsequenzen S10 bis S15 ermöglicht; dies kann insbesondere durch das Werkstattpersonal bei Kundenbeanstandungen erfolgen. Falls eine manuelle Prüfung gewünscht wird oder bei einer Nacharbeit im Herstellerwerk, wird das Verfahren auf Schritt S10 gesetzt.If an error is detected in steps S4 to S6, the test steps S10 to S15 are initiated in the decision step S7. If no error is detected, a manual entry into the test sequences S10 to S15 is made possible in step S8; This can be done in particular by the workshop staff in customer complaints. If a manual check is desired or if a rework is made at the factory, the procedure is set to step S10.

In Schritt S10 wird die für den jeweils erkannten Fehlerfall erforderliche Prüfroutine durchgeführt. Durch die hierbei vorgesehenen Prüfsequenzen kann ein möglicher Fehler genau lokalisiert werden. Die Prüfung erfolgt sowohl auf die einzelnen Komponenten 4 als auch auf das vernetzte Komponentensystem. Nachfolgend werden in Schritt S11 die Ergebnisse der Prüfung in einer Fahrzeugkomponente, z. B. der für die fehlerhafte Komponente zugeordneten Steuereinrichtung 2, gespeichert. Die Speicherung kann insbesondere durch einen Festwertspeicher, z. B. ein PROM, erfolgen, der von Unbefugten nicht ohne weiteres zurückgesetzt werden kann. Hierdurch wird bei Garantiefällen eine Überprüfung und eine Ursachenbehebung beim Hersteller ermöglicht. In Schritt S12 werden die ermittelten Fehler, insbesondere die in Schritt S10 ermittelten Fehlerdaten der Komponenten 4, als Anzeigedaten, z. B. zur Anzeige auf einer Anzeige des Prüfgerätes 5, ausgegeben. Hierbei werden weitere Details zu den Fehlern und möglichen Fehlerquellen gegeben. Nachfolgend kann der Bediener bzw. in Schritt S13 aufgrund detaillierter Angaben den genauen Fehler ermitteln. Hierbei wird der Fehlerort im Fahrzeug z. B. grafisch auf einer Anzeige wiedergegeben. In Schritt S14 können nachfolgend vom Bediener die einzelnen Systeme manuell oder teilweise automatisch konfiguriert werden. Danach werden in Schritt S15 die aktuellen Fehlerdaten in den Fehlerspeichern der Komponenten bzw. der Steuereinrichtungen 2 der Komponenten 4 gelöscht. In Schritt S16 wird anschließend abgefragt, ob ein manueller Abbruch erwünscht ist oder nicht. Falls kein manueller Abbruch erwünscht ist, wird das Verfahren auf Schritt S4 zurückgesetzt, um wiederum eine Fehlerdetektion vorzunehmen. Die Schleife der Schritte S4 bis S6 und S10 bis S15 wird somit solange durchgeführt, bis in Schritt S7 kein Fehlerfall mehr erkannt wird oder in Schritt S16 - z. B. bei einem nicht behebbaren Fehler - ein manueller Abbruch durch den Benutzer erwünscht ist. Falls in Schritt S16 ein manueller Abbruch erwünscht ist, wird in Schritt S17 eine Verbindung mit der Datenbank 10 über das Internet 9 hergestellt. Hierbei werden die Fehlerdaten an die Datenbank 10 zur weiteren Verarbeitung übermittelt, wobei ggf. eine Rückantwort von der zentralen Steuer- und Speichereinrichtung 9 zur Behebung des Fehlers erfolgen kann. Die Datenbank 10 sammelt somit Fehler einer Vielzahl von Prüfverfahren, wodurch eine umfangreiche Fehlersammlung und genaue statistische Auswertung ermöglicht wird. In Schritt S19 werden anschließend die im Fahrzeug erfassten Fehlerdaten ausgedruckt und im Fahrzeug gespeichert und die Einträge im Fehlerspeicher gelöscht. Falls in Schritt S9 keine manuelle Prüfung gewünscht wird, werden in Schritt S18 ebenfalls die Fehlerspeicher in den Komponenten gelöscht und zu Schritt S19 übergegangen. In Schritt S20 ist das Verfahren beendet.In step S10, the test routine required for the detected error case is performed. Due to the test sequences provided here, a possible error can be precisely located. The test is carried out both on the individual components 4 and on the networked component system. Subsequently, in step S11, the results of the test in a vehicle component, e.g. As the assigned for the faulty component control device 2, stored. The storage may in particular by a read-only memory, for. As a PROM, take place, which can not be easily reset by unauthorized persons. As a result, warranty claims can be reviewed and remedied by the manufacturer. In step S12, the determined errors, in particular the error data of the components 4 determined in step S10, are used as display data, e.g. B. for display on a display of the tester 5, issued. This gives more details on the errors and possible sources of error. Subsequently, the operator or in step S13 based on detailed information to determine the exact error. Here, the fault location in the vehicle z. B. displayed graphically on a display. Subsequently, in step S14, the individual systems can be manually or partially automatically configured by the operator. Thereafter, in step S15, the current error data in the error memories of the components or the control devices 2 of the components 4 are deleted. In step S16 it is subsequently queried whether a manual abort is desired or not. If no manual abort is desired, the process is returned to step S4 to again perform error detection. The loop of steps S4 to S6 and S10 to S15 is thus performed until no error case is detected in step S7 or in step S16 - z. B. in an unrecoverable error - a manual termination by the user is desired. If a manual abort is desired in step S16, a connection to the database 10 via the Internet 9 is made in step S17. In this case, the error data is transmitted to the database 10 for further processing, it being possible for a return response to be made by the central control and storage device 9 to remedy the error. The database 10 thus collects errors of a variety of test methods, allowing extensive error collection and accurate statistical evaluation. In step S19, the error data recorded in the vehicle are subsequently printed out and stored in the vehicle and the entries in the error memory are deleted. If no manual check is desired in step S9, the error memories in the components are also cleared in step S18 and proceeded to step S19. In step S20, the process is ended.

Claims (14)

  1. Method for diagnosing components of a vehicle, in which
    a) vehicle-specific input data of the vehicle to be examined are input (S2),
    b) fault detection (S3, S4, S5, S6) is carried out in order to determine a fault situation,
    c) if a fault situation is determined at b), troubleshooting (S10, S11, S12, S13, S14, S15) is carried out during which fault data is determined and stored in at least one vehicle component, display data for recovering from the fault situation is output and an interrogation signal for an abort is then output (S16), wherein
    c1) if no abort signal is subsequently input, the method is reset to b), and
    c2) if an abort signal is input, the fault data is output (S17) and the method is then terminated (S20),
    d) if a fault situation is not detected in b), an interrogation signal for additional testing is output (S8), wherein
    d1) if a check signal is subsequently input, the method is set to c) for manual testing in the check routines and
    d2) if no check signal is subsequently input, the method is subsequently terminated (S20).
  2. Method according to Claim 1, characterized in that a self-test of a test device which is being used is preferably carried out with an update interrogation by means of remote data transmission before the input step a).
  3. Method according to Claim 1 or 2, characterized in that the software and/or hardware states of the components are tested (S5) in the fault detection section b).
  4. Method according to one of the preceding claims, characterized in that the input data is compared (S4) with stored component data in the fault detection section b).
  5. Method according to one of the preceding claims, characterized in that the connected components in the networked component system are tested in the fault detection section b).
  6. Method according to Claim 5, characterized in that functionalities of the checked components in the entire system and the type of components in the networked component system are displayed (S6) in the fault detection section b).
  7. Method according to one of the preceding claims, characterized in that during the troubleshooting, various test sequences are carried out (S10) in order to test the individual components and the components in the networked component system.
  8. Method according to Claim 7, characterized in that the fault data which is determined in the test sequences is stored in components, for example a ROM of a control device which is assigned to faulty components.
  9. Method according to Claim 8, characterized in that the fault data is displayed, preferably accompanied by an indication of possible fault sources (S12).
  10. Method according to Claim 9, characterized in that instruction data for detecting and eliminating the fault or faults is subsequently output (S13).
  11. Method according to one of the preceding claims, characterized in that fault memories in the components are deleted (S15) at the end of the troubleshooting.
  12. Method according to one of the preceding claims, characterized in that when an abort signal is input, the fault data is transmitted to an external database (10) by remote data transmission, preferably over the Internet.
  13. Method according to one of the preceding claims, characterized in that if a check signal is not input, fault memories in the components are cleared (S18) and the method is subsequently terminated (S20).
  14. Method according to one of the preceding claims, characterized in that, before the method ends, the sensed fault data is stored in the vehicle, preferably in a central storage device of the vehicle, and entries in the fault memory are deleted (S19).
EP20030007512 2002-06-22 2003-04-01 Method and device for diagnosing components of a vehicle Expired - Lifetime EP1376094B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE2002127992 DE10227992A1 (en) 2002-06-22 2002-06-22 Method and device for diagnosing components of a vehicle
DE10227992 2002-06-22

Publications (3)

Publication Number Publication Date
EP1376094A2 EP1376094A2 (en) 2004-01-02
EP1376094A3 EP1376094A3 (en) 2004-06-09
EP1376094B1 true EP1376094B1 (en) 2006-07-26

Family

ID=29716615

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20030007512 Expired - Lifetime EP1376094B1 (en) 2002-06-22 2003-04-01 Method and device for diagnosing components of a vehicle

Country Status (2)

Country Link
EP (1) EP1376094B1 (en)
DE (2) DE10227992A1 (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102004002771A1 (en) * 2004-01-20 2005-08-11 Daimlerchrysler Ag Controller area network device testing method in which a modified standard CAN signal is generated as a test signal in order to determine whether a CAN device generates a fault signal in response to it
DE102006029213A1 (en) * 2006-06-26 2007-12-27 Robert Bosch Gmbh Service and diagnostic data detecting and/or determining method for vehicle, involves contactlessly detecting and registering identification data of vehicle during stay of vehicle in workshop region
DE102007014143B4 (en) * 2007-03-23 2009-08-06 Audi Ag Test bench and method for the simulative functional testing of a component and / or a component system of a vehicle
CN102607860A (en) * 2012-02-23 2012-07-25 中联重科股份有限公司 Fault detection method, device and system for engineering mechanical vehicle
CN105954048A (en) * 2016-07-07 2016-09-21 百度在线网络技术(北京)有限公司 Method for testing normal driving of unmanned vehicle and device thereof
CN106248398B (en) * 2016-09-05 2018-11-02 北京新能源汽车股份有限公司 A kind of diagnostic method and device of automobile
CN107490491B (en) * 2017-07-28 2019-05-03 重庆长安汽车股份有限公司 The engine bench test system and test method of vehicle damped condition air-conditioning cutting situation

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0353331A1 (en) * 1988-08-05 1990-02-07 Robert Bosch Gmbh Fault finding system with selective interactive communication
DE3926097A1 (en) * 1989-08-08 1991-02-14 Bosch Gmbh Robert METHOD AND DEVICE FOR INQUIRING CONTROL UNIT DATA
DE4419189A1 (en) * 1994-06-01 1995-12-07 Bosch Gmbh Robert Device for diagnosing motor vehicles
DE4441101B4 (en) * 1994-11-18 2005-01-27 Robert Bosch Gmbh Method and device for determining diagnostic threshold values for a specific type of motor vehicle in the field
JP3333378B2 (en) * 1996-02-05 2002-10-15 本田技研工業株式会社 Vehicle diagnostic method and device
US5916287A (en) * 1996-09-30 1999-06-29 Hewlett-Packard Company Modular automotive diagnostic, test and information system
FR2816741B1 (en) * 2000-11-10 2003-03-14 Renault DEVICE AND METHOD FOR ASSISTING THE DIAGNOSIS OF A MOTOR VEHICLE

Also Published As

Publication number Publication date
EP1376094A3 (en) 2004-06-09
DE10227992A1 (en) 2004-01-08
EP1376094A2 (en) 2004-01-02
DE50304337D1 (en) 2006-09-07

Similar Documents

Publication Publication Date Title
DE10307342B4 (en) Device and method for model-based on-board diagnostics
DE102010052855A1 (en) Detecting deviations in field failure data
DE3810239A1 (en) Multifunction tester for fault diagnosis
DE102005014126B4 (en) Vehicle inspection management system and procedure
DE102012220338A1 (en) Repair support system for vehicle maintenance
EP2676115A1 (en) System and method for identifying diagnosing, servicing and repairing a vehicle
DE102005044236B4 (en) diagnostic device
DE102008040461A1 (en) Method for determining faulty components in a system
DE102004004572B4 (en) Fault diagnosis method for a vehicle communication network
WO2006105930A1 (en) Diagnostic system for determining a weighted list of possible defective components on the basis of vehicle data and customer specifications
WO2001043079A1 (en) Method for recognition of faults on a motor vehicle
WO2006133865A1 (en) Dynamic prioritisation of test steps in workshop diagnostics
DE10307365B4 (en) Device and method for fault diagnosis in vehicles
EP1376094B1 (en) Method and device for diagnosing components of a vehicle
WO2007022849A2 (en) Method for identifying complex diagnoses in customer services
DE10307344B4 (en) Device and method for decentralized on-board diagnostics for motor vehicles
DE102007041848A1 (en) Method and device for detecting faulty components of coupled chains of action
DE102007015140A1 (en) Diagnosis device for implementing diagnosis of mechatronical system, has evaluation unit including analysis unit and test proposing unit that determines and proposes implementable diagnostic examination
DE102009033806A1 (en) Method for manufacturing and testing functionality in production
DE102007049711A1 (en) Method for operating a control device
DE10024211B4 (en) Diagnostic method for the condition of a motor vehicle
WO2019179704A1 (en) Storage of device-related data relating to field devices in a cloud
DE19753730B4 (en) Device for controlling an internal combustion engine
DE10254393A1 (en) Motor vehicle network system diagnostics and checking method for e.g. vehicle CAN bus, uses evaluation unit to evaluate data and signals generated by system in response to request
WO2014005771A1 (en) Vehicle diagnostic device for ascertaining a requirement for a check of at least one motor vehicle component, and vehicle diagnostic method for ascertaining a requirement for a check of at least one motor vehicle component

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK

RIC1 Information provided on ipc code assigned before grant

Ipc: 7G 07C 5/08 B

Ipc: 7G 01M 17/007 A

Ipc: 7G 01R 31/00 B

Ipc: 7G 01M 15/00 B

17P Request for examination filed

Effective date: 20041209

AKX Designation fees paid

Designated state(s): DE FR GB IT

17Q First examination report despatched

Effective date: 20050309

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB IT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT;WARNING: LAPSES OF ITALIAN PATENTS WITH EFFECTIVE DATE BEFORE 2007 MAY HAVE OCCURRED AT ANY TIME BEFORE 2007. THE CORRECT EFFECTIVE DATE MAY BE DIFFERENT FROM THE ONE RECORDED.

Effective date: 20060726

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REF Corresponds to:

Ref document number: 50304337

Country of ref document: DE

Date of ref document: 20060907

Kind code of ref document: P

GBT Gb: translation of ep patent filed (gb section 77(6)(a)/1977)

Effective date: 20061101

ET Fr: translation filed
PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20070427

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20140423

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20140429

Year of fee payment: 12

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20150401

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150401

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150401

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 14

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20170424

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20170623

Year of fee payment: 15

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 50304337

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180430