EP4147210A1 - Procédé et dispositif de diagnostic pour effectuer des diagnostics de véhicule - Google Patents

Procédé et dispositif de diagnostic pour effectuer des diagnostics de véhicule

Info

Publication number
EP4147210A1
EP4147210A1 EP21722886.5A EP21722886A EP4147210A1 EP 4147210 A1 EP4147210 A1 EP 4147210A1 EP 21722886 A EP21722886 A EP 21722886A EP 4147210 A1 EP4147210 A1 EP 4147210A1
Authority
EP
European Patent Office
Prior art keywords
vehicle
diagnostic device
sensor
error codes
error
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.)
Pending
Application number
EP21722886.5A
Other languages
German (de)
English (en)
Inventor
Martin Gütlein
Uwe Riegger
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.)
Hella Gutmann Solutions GmbH
Original Assignee
Hella Gutmann Solutions 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 Hella Gutmann Solutions GmbH filed Critical Hella Gutmann Solutions GmbH
Publication of EP4147210A1 publication Critical patent/EP4147210A1/fr
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME 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/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0808—Diagnosing performance data
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME 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/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME 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
    • G07C2205/00—Indexing scheme relating to group G07C5/00
    • G07C2205/02—Indexing scheme relating to group G07C5/00 using a vehicle scan tool

Definitions

  • the present invention relates to a method and a diagnostic device for carrying out a vehicle diagnosis, the cause of the fault in the vehicle being determined automatically.
  • a vehicle diagnosis interface is usually provided in the vehicle, which is often arranged in the driver's footwell.
  • an external vehicle diagnostic device is connected to the vehicle diagnostic interface in order to read out the stored fault codes.
  • the fault codes are then analyzed by the vehicle diagnostic device to diagnose which components need to be repaired or replaced in order to correct the problem.
  • vehicle diagnostic devices have proven themselves in everyday workshop life.
  • the vehicle diagnostic device can generally read out the error codes, but cannot access all of the other relevant information stored in the vehicle.
  • the error codes also differ according to manufacturer, vehicle type and vehicle year. The type and meaning of the error code are often known to the vehicle manufacturer (OEM), but are usually not the subject of manufacturer information / instructions and are therefore not known to the company involved in vehicle diagnostics.
  • the method comprises at least the following steps:
  • the vehicle fault condition representing a condition of the vehicle in which at least one of the fault codes was triggered in the vehicle, based on the respective fault code and historical vehicle data from a database
  • the method is used to determine the vehicle fault condition in which the fault code was triggered. Because the vehicle fault condition is subsequently brought about, the exact cause of the fault message can be determined via an evaluation of the sensor measurements of the vehicle in the vehicle fault condition, depending on the fault code. Overall, the proposed method simplifies and speeds up vehicle diagnosis.
  • the method is characterized, among other things, by the fact that the steps are carried out automatically, in particular by a control unit such as a processor or controller. This can significantly reduce the workload for a motor vehicle mechanic.
  • the error code can include, for example, a diagnostic error code, a so-called Diagnostic Trouble Code (DTC), which is generated by a control device of the vehicle with the aid of sensors of the vehicle.
  • DTC Diagnostic Trouble Code
  • Such a diagnostic error code can, for example, be provided by a vehicle diagnostic system, a so-called on-board diagnosis (OBD), during operation of the vehicle if an error condition is present.
  • OBD on-board diagnosis
  • historical data refer to data that were determined or measured in the past and are stored in the database.
  • Vehicle data of the vehicle can therefore be compared with the historical vehicle data, in particular also from vehicles from other vehicle manufacturers, in order to be able to make a statement about the vehicle condition or the vehicle fault condition.
  • the historical vehicle data preferably include vehicle identification means, vehicle manufacturer, vehicle type, vehicle equipment, error codes, mileage, vehicle age, sensor measured values and / or sensor measured variables.
  • the vehicle data mentioned are preferably combined in at least one matrix and, in particular, assigned to a specific vehicle or a specific vehicle group.
  • the database can be part of a storage medium, a server and / or a diagnostic device. In particular, the database is not part of the vehicle and can be referred to as an external database.
  • the request to bring about the first vehicle fault condition can contain at least one of the following instructions or requests:
  • Vehicle functions can also be activated, e.g. regeneration of the diesel particulate filter.
  • the instructions or requests are preferably followed by a user, such as a car mechanic, and carried out on the vehicle.
  • the request may be sent to the vehicle itself and then implemented by the vehicle.
  • the at least one actuator, vehicle module and / or vehicle control unit are changed, set, switched on or off accordingly, or the at least one vehicle parameter is changed accordingly.
  • Feedback from the vehicle or a user can be used to identify that the first vehicle fault condition was caused.
  • the method can thus include the step of receiving a confirmation that the vehicle is in the first vehicle fault state.
  • the method can include the additional step: determining a relevance of the respective error code.
  • the relevance of the respective error code can be determined based on an average time span between triggering and deleting the same historical error codes.
  • the fault is usually deleted manually in the workshop by the mechanic after the vehicle has been repaired or the fault has been rectified.
  • the average time span can, for example, be stored in the database mentioned and can, for example, be based on experience evaluation values or logged data. If an error code remains set on average for a long time before the error is deleted, this can be an indication that the vehicle operation is not significantly disrupted by the error and that there is no serious error.
  • the time span between triggering the error and clearing the error is short on average, this can be an indication that trouble-free vehicle operation can only be guaranteed by quickly eliminating the error, only possible to a limited extent due to the error that occurs or even being canceled under certain circumstances is closed. It can thus be provided that the relevance is comparatively high if the average time span falls below a predetermined value. The relevance can be comparatively low if the average time span exceeds a predetermined value.
  • the error codes can be classified by comparison with historical error codes from the database according to vehicle assemblies and / or customer groups and / or correlating historical error codes. Correlating error codes can be error codes that occur more frequently when the error code occurs. If the fault code is assigned to a specific vehicle assembly, then the correlating fault codes can also be assigned to this vehicle assembly. The relevance of the respective error code can then be determined using the classification of the error code.
  • the error codes can be sorted and / or evaluated according to relevance.
  • the relevance can be expressed by a number, e.g. either 0 (not relevant) or 1 (relevant) or a number between 0 and 1.
  • the determination of the first vehicle error state, the relevant sensor parameters to be measured and / or the at least one potentially defective component can be done based on the relevance of the error codes.
  • the diagnostic device can receive information about the current state of the vehicle and the errors present. Furthermore, there is usually a user interface such as a display with a user interface in the diagnostic device, via which additional information information can be queried or entered by the user.
  • a user interface such as a display with a user interface in the diagnostic device, via which additional information information can be queried or entered by the user.
  • historical logging data from diagnostic devices can also be taken into account, which can in particular be stored in the database.
  • Logging is usually the creation of a log of a diagnostic process, which is usually created automatically.
  • the historical logging data preferably include called up repair information and / or called up vehicle component information that was called up during earlier (historical) vehicle diagnoses, for example. If, after reading / receiving a certain error code, certain repair information and / or vehicle component information is often or always called up by the mechanic, this is an indication that a certain component is defective when this certain error code occurs. Taking the historical logging data into account when determining the potentially defective component can thus considerably accelerate the automatic vehicle diagnosis.
  • a target range can be determined for each sensor measured variable.
  • the target range here preferably comprises a target measured value and / or a tolerance range around the target measured value. Measured values that lie within the target range are accordingly assessed as positive, while measured values that lie outside the target range are assessed as negative.
  • the target range depends on several parameters internal to the vehicle (e.g. vehicle age, mileage) or external parameters (e.g. outside temperature), which can also be stored in the database. Correlating sensor measured variables and / or related sensor measured variables can also be taken into account for the determination of the setpoint range.
  • Related sensor measurement variables can, for example, be assigned to the same vehicle assembly (e.g. engine, air conditioning, brake system, infotainment system, etc.).
  • the method can further have at least one of the following steps:
  • the user interface can in particular be a display or the above-mentioned user interface on the vehicle diagnostic device.
  • the process can include at least one of the following steps:
  • the vehicle identification means includes in particular a vehicle identification number and / or an engine code and / or a control unit identification number and / or short name,
  • the vehicle identification means indicates, for example, the vehicle manufacturer and / or a vehicle type of the vehicle and, if necessary, equipment features of the vehicle such as the engine variant or injection system.
  • the vehicle identification means can include, for example, a vehicle-specific number, for example a vehicle identification number (hereinafter: FIN, Vehicle Identification Number, VIN) with which a vehicle can be uniquely identified.
  • FIN Vehicle Identification Number
  • VIN Vehicle Identification Number
  • information on the vehicle or on comparable vehicles can be determined from the database in a simple manner. It turned out that the VIN is not always sufficient to clearly determine the identity of the vehicle.
  • at least one further vehicle identification means can be used, for example an engine code and / or a control unit identification number and / or a short description of the vehicle.
  • the short description of the vehicle can be stored in a control unit of the vehicle and can provide information about the manufacturer, type and / or equipment of the vehicle.
  • the identity of the vehicle can be inferred and the vehicle (manufacturer, type and / or equipment) recognized.
  • the identity of the vehicle can be determined by recognizing a pattern in the vehicle identification means and comparing it with the same or similar patterns in the database.
  • the step of receiving the vehicle identification means can include, for example, that the vehicle identification means is transmitted by the vehicle or is entered by a user. If necessary, the vehicle identification means can be transmitted or entered after a request.
  • the method can include the following step: determining context-related repair information on the basis of the error codes and / or the sensor measured variables and / or the potentially defective components.
  • Context-related repair information is, for example, circuit diagrams, work values or component test values that the user needs to repair the vehicle or to rectify the fault.
  • the context-related repair information can be determined by comparing it with the historical logging data.
  • the at least one potentially defective component is additionally determined on the basis of customer service data and / or invoice data from motor vehicle workshops and / or access to repair information in the database.
  • the error codes can be evaluated based on the measured sensor parameters.
  • the at least one potentially defective component can be determined.
  • the at least one potentially defective component can then be determined using the error codes and the measured sensor measurement variables.
  • the method comprises at least one, several or all of the following steps:
  • the diagnostic results can be displayed on the display device, the display device preferably being part of a diagnostic device or of the above-mentioned user interface.
  • the automatic method described above can speed up and simplify the operation of the diagnostic device.
  • extensive knowledge of the diagnostic device is no longer required.
  • the user no longer has to navigate through approx. 10 or more interfaces / categories with approx. 75 "clicks".
  • extensive vehicle knowledge is also no longer necessary to combine the displayed error codes and the read out sensor readings.
  • the automatic, data-driven identification of potentially affected components is more accurate than the previous listing of possibly affected components per individual error code.
  • the above-mentioned method can in particular be carried out by a vehicle diagnostic device, a server and / or a system comprising a vehicle diagnostic device and a server.
  • the vehicle diagnostic device, the server or the system can preferably be connected to the vehicle via a vehicle diagnostic interface, e.g. directly or indirectly.
  • the invention provides a diagnostic device which is designed to carry out the above method.
  • the diagnostic device is designed to carry out at least the following steps:
  • the vehicle fault condition representing a condition of the vehicle in which at least one of the fault codes was triggered in the vehicle, based on the respective fault code and historical vehicle data from a database
  • the diagnostic device is not part of the vehicle and can, for example, be arranged outside the vehicle or in a vehicle interior, preferably temporarily for the duration of the diagnosis.
  • the diagnostic device can comprise a vehicle diagnostic device and / or a mobile device and / or a server or be a vehicle diagnostic device or a server.
  • the diagnostic device can be a system or part of a system which comprises a vehicle diagnostic device and a server.
  • the diagnostic device can set up a communication link with the vehicle, in particular the vehicle-based control units.
  • the device for receiving and / or sending data can have a communication device.
  • the diagnostic device typically comprises a control unit, e.g. for processing data and / or controlling further units.
  • the database can be part of the diagnostic device. Alternatively, the database can also be provided outside the diagnostic device, e.g. part of an external server.
  • FIG. 1 shows a schematic representation of a vehicle diagnostic device connected to a vehicle
  • FIG. 2 shows a schematic representation of a system for performing a vehicle diagnosis
  • FIG. 3 shows a schematic illustration of a communication sequence between a vehicle and a vehicle diagnostic device
  • FIG. 4 shows a schematic representation of a further communication sequence between a vehicle and a system.
  • the invention provides a method for performing a diagnosis of a vehicle 10.
  • the method is preferably carried out by means of a vehicle diagnostic device 20 indicated in FIGS. 1 and 3 or a system 40 indicated in FIGS. 2 and 4, the system in the exemplary embodiment of FIGS. 2 and 4 comprises a vehicle diagnostic device 20 and a server 30.
  • FIG. 1 shows a vehicle 10 which has a multiplicity of control units 11, 12, for example at least 10 or more.
  • the control units 11, 12 can be connected to one another, for example via a CAN bus system.
  • at least one control unit 11 is connected to a vehicle diagnosis interface 13.
  • 1 shows a vehicle diagnosis device 20, which typically includes a control and processing unit, a communication unit, a memory and an input and output unit for communication with a user such as a motor vehicle mechanic.
  • the vehicle diagnostic device 20 can usually be connected to the vehicle diagnostic interface 13 of the vehicle via signal lines (i.e. wired). tool 10 can be connected.
  • the vehicle diagnostic device 20 typically has a plug that is compatible with the vehicle diagnostic interface 13. When connecting the plug to the vehicle diagnostic interface 13, both are electrically connected to one another.
  • a wireless communication link between the vehicle diagnostic device 20 and the vehicle 10 and the control devices 11, 12 is possible.
  • the control units 11, 12 are usually each connected to a multiplicity of sensors which record measured values during the operation of the vehicle.
  • Conceivable sensor measurements include, for example, a coolant temperature, an engine temperature, a vehicle speed, an engine speed, an engine torque, an ambient temperature, an ambient air pressure, a boost pressure of an exhaust gas turbocharger of the drive engine, an engaged gear of a transmission of the vehicle 10, etc. If a sensor If the measured value falls below or exceeds a certain target value range, the corresponding control device 11, 12 generates an error code.
  • the error code is assigned to an error state and contains, for example, a code number to identify malfunctions that can occur during the operation of a vehicle.
  • the trouble code is also known as a diagnostic trouble code or Diagnostic Trouble Code (DTCj.
  • the aim of the vehicle diagnosis is to be able to determine which component in the vehicle 10 is defective and how this component can be repaired.
  • the vehicle diagnostic device 20 evaluates the error codes, which during operation of the vehicle 10 via an evaluation of the sensor measured values by the at least one Vehicle control unit 11, 12 are generated and stored in a vehicle-mounted memory.
  • the vehicle control devices 11, 12 are designed to read out the error codes stored in the vehicle 10 and to transmit them to the diagnostic device 20 (or the server 30).
  • the vehicle diagnostic device 20 can therefore communicate directly with the respective vehicle control device 11, 12 in order to retrieve the required error codes from the vehicle Control unit 11, 12 to obtain.
  • the fault codes can then be analyzed by the vehicle diagnostic device 20 in order to diagnose whether and which vehicle components need to be repaired or replaced in order to rectify the problem.
  • a statement can be made about which vehicle components are defective and require repair.
  • Fig. 3 shows schematically a preferred communication flow between tween the vehicle 10 and the vehicle diagnostic device 20.
  • the sending and receiving steps are each summarized in an arrow with a reference number.
  • An identification of the vehicle is usually required so that the vehicle diagnostic device 20 can assign the error codes to a specific vehicle 10, in particular the manufacturer, type and equipment of the vehicle 10. Therefore, the vehicle diagnostic device 20 sends (Sil) a request for identifying the vehicle 10 to the vehicle. The vehicle 10 then sends (S12) at least one vehicle identification means of the vehicle 10, which can be stored in a vehicle memory, 1 to the vehicle diagnostic device 12. In alternative embodiments, the manufacturer, type and / or equipment of the vehicle 10 or the vehicle identification means are carried out manually a technician or vehicle mechanic entered the vehicle diagnostic device 12.
  • the vehicle diagnostic device 20 can then, for example, request the error codes from the vehicle 10 (S13).
  • the vehicle 10 then sends the requested error codes to the vehicle diagnostic device 20, and the vehicle diagnostic device 20 receives (S14) the vehicle error codes. After receipt, the Error codes are analyzed or evaluated by the vehicle diagnostic device 12.
  • vehicle diagnostic device 20 can additionally request currently measured sensor measured values or sensor measured values stored in the vehicle from vehicle 10. This is done, for example, via a corresponding request (S15).
  • the vehicle control device 11, 12 calls up the requested sensor measured values, e.g. from a memory in the vehicle, or addresses corresponding vehicle sensors to issue or record the sensor measured values.
  • the measured sensor values are then sent from the vehicle control device 11, 12 to the vehicle diagnostic device 20 for further evaluation or processing (S16). Based on the error codes and the sensor measured values, the vehicle diagnostic device 20 can determine which component in the vehicle is defective and requires repair.
  • steps Sil and S13, S12 and S14 can each be combined.
  • the vehicle diagnostic device 20 can also send commands to the vehicle control device 11, 12.
  • a command to the vehicle control unit includes a setting of the sensor or a change in the setting of the sensor, where the setting includes, for example, a sensitivity of the sensor, a frequency of the measurements and / or a time sequence of the measurements.
  • the status of the vehicle control device 11, 12 can be changed or set by the vehicle diagnostic device 20 via a corresponding message. It would be conceivable in this context, for example. Inspection interval, control of actuators or the like. The course of the vehicle diagnosis is described below.
  • the vehicle diagnosis can alternatively also be carried out with the system 40 shown in FIG. 2.
  • the system 40 comprises the vehicle diagnostic device 20 described above and a server 30.
  • the vehicle diagnostic device 20 is preferably connected to the vehicle 10 via the vehicle interface 13.
  • the vehicle diagnostic device 20 is also wirelessly or wired to an external server 30. This enables communication between the server 30 and the diagnostic device 20. The communication between the vehicle 10, the diagnostic device 20 and the server 30 is discussed below.
  • a communication link is established between the diagnostic device 20 and the vehicle 10 (S10). Thereafter (or before or at the same time) a communication connection is established between the diagnostic device 20 and the server 30 (S20). The diagnostic device 20 is now able to mediate communication between the server 30 and the vehicle 10. In this way, the diagnostic device 20 can convey data or messages between the vehicle 10 and the server 30.
  • An identification of the vehicle 10 is usually required so that the server 30 can assign the error codes to a specific manufacturer and vehicle type.
  • the server 30 therefore sends (S21) a request for identifying the vehicle 10 to the diagnostic device 20, which forwards the request to the vehicle 10 (Sil).
  • the vehicle 10 then sends (S12) at least one identification means of the vehicle 10, which can be stored in a vehicle-side memory, via the diagnostic device 20 to the server 30 (S22).
  • the server 30 can then request error codes from the vehicle 10, for example.
  • the diagnostic device 20 forwards, for example, the request from the server 30 to the vehicle control device 10 (S23, S13).
  • the vehicle 10 then sends (S14) the requested error codes to the diagnostic device 20, which sends the error codes to the server 30 (S24).
  • the error codes can be analyzed or evaluated by the server 30.
  • the server 30 can also request measured sensor values from the vehicle 10. This is done, for example, via a request that is forwarded from the diagnostic device 20 to the vehicle 10 (S25, S15).
  • the vehicle 10 calls up the requested sensor measured values from the vehicle-side memory or addresses corresponding vehicle sensors to issue or to acquire the sensor measured values.
  • the sensor readings are then sent from the vehicle 10 to the diagnostic device 20 (S16) and from the diagnostic nos réelle 20 is sent to the server 30 for further evaluation or processing (S26). Based on the error codes, the identification means and the sensor measured values, the server 30 can determine which component in the vehicle 10 is defective and requires repair.
  • steps S21 and S23, Sil and S13, S12 and S14, and S22 and S24 can each be combined.
  • the server 30 can also send commands to the vehicle 10 via the diagnostic device 20.
  • a command to the vehicle includes a setting of the sensor or a change in the setting of the sensor, the setting including, for example, a sensitivity of the sensor, a frequency of the measurements and / or a time sequence of the measurements.
  • the status of the vehicle 10 can be changed or set by the server 30 via a corresponding message.
  • e.g. inspection intervals, actuation of actuators or the like would be conceivable.
  • the vehicle 10 can also receive new software components or updates that the server 30 sends to the vehicle 10 via the diagnostic device 20.
  • a mobile device such as a mobile phone, laptop, computer, tablet PC or the like can alternatively be provided, which on the one hand with the vehicle 10, in particular via the vehicle interface 13, and on the other hand with the server 30 is connected, and which the communication between the vehicle 10 and the server 30 mediated.
  • the mobile device therefore preferably forwards messages such as commands and / or inquiries or data such as measured values and / or DTCs from vehicle 10 to server 30 and vice versa.
  • the actual vehicle diagnosis which can be carried out in particular by the vehicle diagnosis device 20, the server 30 or the system 40, will be discussed in greater detail below.
  • VIN vehicle identification number
  • engine code / or a control unit identification number and / or a short description.
  • the vehicle identification means is compared with known vehicle means from the database in order to identify the vehicle 10. In some cases, the VIN is insufficient to unequivocally identify the vehicle 10. In these cases, on the basis of manually selected vehicles with an existing VIN in the database, patterns are extracted that can also be used for unknown VINs. By including the engine code and the abbreviation, vehicles from all manufacturers can be identified for which the VIN alone is not sufficient.
  • the procedure also has the following steps:
  • the vehicle error state representing a state of the vehicle 10 in which at least one of the error codes in the vehicle 10 was triggered, based on the respective error code and historical vehicle data from a database outside the vehicle 10,
  • Request to bring about at least the first vehicle fault condition preferably by displaying a request on a display of the diagnostic device 20, and receiving S16, S26 of the measured sensor parameters of the vehicle 10.
  • the historical vehicle data in the database is preferably used, the database being stored in a storage medium that is, for example, part of the diagnostic device 20, the server 30 or another server.
  • the historical vehicle data include at least the vehicle manufacturer, vehicle type, vehicle equipment, error codes, mileage, vehicle age, sensor measured values and / or sensor measured values.
  • a check is made as to how the vehicle condition was before the error code (e.g. based on the speed or engine speed) or whether an actuator test / control element test was carried out on components (e.g. blower or air conditioning activated).
  • historical data can be used, for example, to check which sensor measured variables (sensor parameters) are increasingly selected by the user if a corresponding error code is present. By bringing about the first vehicle fault condition, relevant measured values can therefore be recorded, which can then be used for the diagnosis.
  • the vehicle state can be brought about, for example, by changing or setting at least one actuator, changing or setting at least one vehicle parameter, switching on or off at least one vehicle module and / or switching on or off at least one vehicle control device.
  • a corresponding confirmation can be sent to the vehicle diagnostic device 20 or the server 30. If necessary, depending on the error code, several vehicle error states can be brought about successively, in each of which the relevant sensor parameters to be measured are measured.
  • the relevance of the respective error code can be determined.
  • the error codes are then sorted and weighted according to relevance. For example, only the most relevant error codes are taken into account for the diagnosis. Less relevant error codes can be ignored. If, for example, an average period of time between triggering and deleting the error code exceeds a predetermined time period, the error can be classified as irrelevant. On the other hand, the error code can be classified as relevant if the average time span between triggering and deleting the error code falls below a predetermined duration.
  • the error codes can be classified by comparison with historical error codes from the database according to vehicle assemblies and / or customer groups and / or correlating historical error codes. Correlating error codes are error codes that occur more frequently when the error code occurs. If the error code is assigned to a specific vehicle assembly, then the correcting error codes can also be assigned to this vehicle assembly. The relevance of the respective error code can then be determined using the classification of the error code.
  • the procedure also includes the following step:
  • Determining at least one potentially defective component in the vehicle 10 in particular on the basis of the error codes, the measured sensor values and the mileage of the vehicle.
  • calls to technical information such as repair information or vehicle component information are stored by the mechanic on the diagnostic device 20 in a log, which is also referred to as logging.
  • the logging data are preferably also in the data deposited in a bank. The logging data can be taken into account when determining the potentially defective component.
  • the selection of relevant information on the diagnostic device 20 that is necessary for the repair is usually based on his motor vehicle expert knowledge.
  • the mechanic often has up to 18 different categories with additional sub-categories in the diagnostic device: e.g. circuit diagrams, labor values or component test values. According to conventional solutions, the mechanic had to make a suitable selection in each category.
  • the corresponding categories are stored in the database (e.g. on the server 30 and / or the diagnostic device 20).
  • relevant components or component formations are extracted, for example from a memory of the diagnostic device 20 or the database.
  • the at least one potentially defective component is additionally determined on the basis of customer service data and / or invoice data from motor vehicle workshops and / or access to repair information in the database.
  • the method can include the following step: Determination of context-related repair information on the basis of the error codes and / or the sensor measured variables and / or the potentially defective components.
  • Context-related repair information is e.g. wiring diagrams, labor values or component test values that the user needs to repair the vehicle or to rectify the fault.
  • the context-related repair information can be determined using the historical logging data.
  • the relevance of the error codes can be determined, for example on the basis of the same historical error codes. For example, if the error codes remain set for a longer period of time, this is an indicator that the error code is less relevant. Historical error codes from customer groups can also be used to classify the relevance that relate to the re- Focus on repairing less critical problems (e.g. "Glaser"). If error codes are read out of their focus there (e.g. error codes that were generated based on engine sensor readings), then this is also an indicator that the error code is less relevant Customer concerns are another problem.
  • Prediction models can be developed on the basis of the historical vehicle data (relevant error codes, sensor readings and mileage readings) in conjunction with the extracted components.
  • Anomalies in the sensor readings can also be determined.
  • a self-learning system (diagnostic device 20, server 30 or system 40) should identify correlating sensor measurement values and related sensor sensor measurement values and form a main cluster (majority of all healthy measurement points) on which outlier models can be trained. Error codes can also be included to identify the main cluster. This means that no error codes or a number of error codes that do not exceed a predetermined limit are preferably set for the measured values in the main cluster.
  • These models can be applied to current sensor measurements and calculate a probability of whether the measurement should be classified as an outlier / anomaly. Measured values that lie within a target range are accordingly assessed as positive, while measured values that lie outside the target range are assessed as negative.
  • Correlating and / or related sensor measured variables can be taken into account to determine the target range.
  • the measured sensor parameters can be compared with the respective target ranges in order to identify outliers in the sensor parameters.
  • the degree of deviation of the measured value from the target range can be specified, for example by showing it on the display on the diagnostic device 20.
  • the method optionally has at least one of the following steps: Creating and displaying a list of potentially defective components, creating and displaying context-related component information on the defective components and / or determining and displaying necessary repair steps.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
  • Vehicle Body Suspensions (AREA)

Abstract

L'invention concerne un procédé de réalisation de diagnostics de véhicule, comprenant les étapes suivantes : - recevoir (S14, S24) une pluralité de codes de défaillance provenant d'un véhicule (10), - déterminer au moins un premier état de défaillance de véhicule, l'état de défaillance de véhicule constituant un état du véhicule (10) dans lequel au moins un des codes de défaillance a été déclenché dans le véhicule (10), en fonction du code de défaillance respectif et de données de véhicule historiques provenant d'une base de données, - déterminer des variables mesurées de capteur pertinentes à mesurer, en fonction des codes de défaillance, - demander la production d'au moins le premier état de défaillance de véhicule, - recevoir (S16, S26) les variables mesurées de capteur qui sont mesurées à partir du véhicule (10), - déterminer au moins un composant potentiellement défectueux. L'invention concerne en outre un dispositif de diagnostic pour réaliser le procédé.
EP21722886.5A 2020-05-07 2021-05-04 Procédé et dispositif de diagnostic pour effectuer des diagnostics de véhicule Pending EP4147210A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP20173583.4A EP3907707A1 (fr) 2020-05-07 2020-05-07 Procédé et dispositif permettant d'effectuer un diagnostic de véhicule
PCT/EP2021/061617 WO2021224202A1 (fr) 2020-05-07 2021-05-04 Procédé et dispositif de diagnostic pour effectuer des diagnostics de véhicule

Publications (1)

Publication Number Publication Date
EP4147210A1 true EP4147210A1 (fr) 2023-03-15

Family

ID=70617041

Family Applications (2)

Application Number Title Priority Date Filing Date
EP20173583.4A Withdrawn EP3907707A1 (fr) 2020-05-07 2020-05-07 Procédé et dispositif permettant d'effectuer un diagnostic de véhicule
EP21722886.5A Pending EP4147210A1 (fr) 2020-05-07 2021-05-04 Procédé et dispositif de diagnostic pour effectuer des diagnostics de véhicule

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP20173583.4A Withdrawn EP3907707A1 (fr) 2020-05-07 2020-05-07 Procédé et dispositif permettant d'effectuer un diagnostic de véhicule

Country Status (5)

Country Link
US (1) US20230252829A1 (fr)
EP (2) EP3907707A1 (fr)
AU (1) AU2021269012A1 (fr)
CA (1) CA3181930A1 (fr)
WO (1) WO2021224202A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102021213965A1 (de) 2021-12-08 2023-06-15 Zf Friedrichshafen Ag Verfahren zur Fehlerdiagnose für ein Kraftfahrzeug
DE102021132801A1 (de) 2021-12-13 2023-06-15 Audi Aktiengesellschaft Verfahren und Prozessorschaltung zum Verifizieren einer Kilometerstandsangabe einer Kilometerstandsanzeigeeinheit eines Kraftfahrzeugs sowie zugehöriges System und zugehörige Servervorrichtung
CN115933619A (zh) * 2023-01-05 2023-04-07 中国第一汽车股份有限公司 一种远程诊断方法、系统、电子设备及存储介质
CN117434927B (zh) * 2023-12-20 2024-04-02 中汽研（天津）汽车工程研究院有限公司 一种检测电子控制器故障状态的云端诊断系统及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100324376A1 (en) * 2006-06-30 2010-12-23 Spx Corporation Diagnostics Data Collection and Analysis Method and Apparatus
JP4720770B2 (ja) * 2007-04-02 2011-07-13 トヨタ自動車株式会社 車両用情報記録システム
US8924071B2 (en) * 2013-04-26 2014-12-30 Ford Global Technologies, Llc Online vehicle maintenance
DE102015214739B4 (de) * 2015-08-03 2022-12-29 Volkswagen Aktiengesellschaft Verfahren zur Bestimmung einer Fehlerursache bei einem Fahrzeug und Server zum Durchführen der Bestimmung der Fehlerursache
GB201710048D0 (en) * 2017-06-23 2017-08-09 Remote Asset Man Ltd Electrical connector

Also Published As

Publication number Publication date
US20230252829A1 (en) 2023-08-10
CA3181930A1 (fr) 2021-11-11
WO2021224202A1 (fr) 2021-11-11
AU2021269012A1 (en) 2023-01-19
EP3907707A1 (fr) 2021-11-10

Similar Documents

Publication Publication Date Title
DE102015214739B4 (de) Verfahren zur Bestimmung einer Fehlerursache bei einem Fahrzeug und Server zum Durchführen der Bestimmung der Fehlerursache
EP4147210A1 (fr) Procédé et dispositif de diagnostic pour effectuer des diagnostics de véhicule
DE102014105674A1 (de) Online-fahrzeugwartung
DE4441101B4 (de) Verfahren und Vorrichtung zur Bestimmung von Diagnoseschwellwerten für einen bestimmten Kraftfahrzeugtyp im Feld
EP2676115B1 (fr) Système et procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule
DE10235525B4 (de) Verfahren und System zur Überwachung des Zustands eines Fahrzeugs
EP2718908B1 (fr) Interface de communication mobile, système ayant une interface de communication mobile et procédé d'identification, de diagnostic, d'entretien et de réparation d'un véhicule
WO2001043079A1 (fr) Procede de reconnaissance de defauts d'un vehicule automobile
DE112009000439T5 (de) Fahrzeuginformationsaufzeichnungsvorrichtung, Fahrzeuginformationskommunikationssystem und Fahrzeuginformationskommunikationsverfahren
DE102019108446A1 (de) Verfahren und Vorrichtung zum Isolieren eines fahrzeugseitigen Fehlers
EP2146262A1 (fr) Procédé de détermination de composants défectueux dans un système
EP2676116A1 (fr) Interface de communication mobile, système équipé d'une interface de communication mobile et procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule
DE102018003801B4 (de) Verfahren und Steueranordnung zur Vorhersage einer Fehlfunktion einer Radlagereinheit einer Achse in einem Fahrzeug
WO2006056355A2 (fr) Systeme de diagnostic et d'entretien pour une automobile
EP3001380A1 (fr) Procede de diagnostic et procede de levage pour vehicules
DE102012011538A1 (de) Verfahren und System zur Telediagnose von Fahrzeugen
DE102014114202A1 (de) Verfahren zum Prognostizieren einer Panne und/oder eines Reparatur- und/oder Wartungsbedarfs
WO2007022849A2 (fr) Procede d'identification de situations de diagnostic complexes dans le service apres-vente
DE19722188A1 (de) Vorrichtung zur Funktionsüberprüfung eines elektronisch gesteuerten Regelsystems in einem Kraftfahrzeug nach einem Fertigungsvorgang
EP4167040A1 (fr) Éditeur de modèle de défaut et outil de diagnostic
EP2166514B1 (fr) Système de diagnostic de véhicule automobile
DE102015214987B4 (de) Bestimmung eines defekten Bauteils eines Fahrzeugs
DE102021202177A1 (de) Verfahren zum bestimmen des betriebszustands von fahrzeugkomponenten
DE10024211B4 (de) Diagnoseverfahren für den Zustand eines Kraftfahrzeuges
DE102005014308A1 (de) Verfahren und Anordnung zur Nutzerführung bei der Diagnose komplexer Systeme sowie ein entsprechendes Computerprogramm und ein entsprechendes computerlesbares Speichermedium

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

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

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

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

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20221107

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)