FR2860895A1 - Motor vehicles malfunction diagnosing system, has acquisition network linked to central processing unit to acquire diagnosis data, where malfunction is diagnosed to deliver alarm, when vehicles functioning variable exceeds threshold - Google Patents

Abstract

The system has an acquisition network connected to a central processing unit (100) for acquiring diagnosis data. A storing unit stores the data and a communication unit (220) communicates with a fixed diagnosis station (2) and with a centralized diagnosis system (3) having a server associated to a database. Malfunction of a vehicle is diagnosed to deliver an alarm to a driver, when vehicles functioning variable exceeds a threshold.

Description

The present invention relates to the diagnosis of malfunctions of

motor vehicles.

  In the past, to carry out a diagnosis, a car mechanic collected the symptoms of malfunctions perceived by the driver of the vehicle, then, using these symptoms, he searched for the malfunction (s), examining the vehicle visually and / or using the physical measurement tools and electronic reading.

  Such a diagnostic method was cumbersome to implement and moreover unreliable. Indeed, it did not allow to find systematically dysfunctions. In addition, the increasing diversity and rapid evolution of vehicle electronic systems has made diagnostics malfunctions and, consequently, repairs increasingly complex.

  The more advanced diagnostic aid device of US Pat. No. 5,313,388 comprises means for acquiring symptomatic data provided by a user of the vehicle, means for acquiring operating data of the vehicle and allowing automate the development of diagnostics through the introduction of electronic and computer means. However, in this device of the prior art, in which a correlation database of symptomatic data and operating problems is used, the diagnosis remains rather empirical.

  Document EP 1 039 390 discloses a device comprising symptomatic data acquisition means provided by a user of the vehicle, prior symptomatic data acquisition means, first diagnostic assistance means by application, for each vehicle operating data, at least one predefined method for assisting the diagnosis, and second diagnostic assistance means by comparing the data of at least one of the two groups, respectively comprising the symptomatic data provided. by the vehicle user and vehicle operating data, together with previous symptomatic data.

  "Previous symptomatic data" refers to data relating to symptoms collected in the past on motor vehicles and for each of which at least one malfunction, which is the cause, is known.

  But this device, quite sophisticated, remains a device to carry out curative diagnoses, with all the disadvantages, certainly relative, related to the curative nature of diagnoses and, ultimately, troubleshooting.

  lo Well the plaintiff had the idea to propose to intervene before and not after the malfunctions or breakdowns and to develop the diagnosis of predictive or preventive motor vehicles.

  If we want to schematically define the curative diagnosis practiced so far, here is how the architecture looks: at the garage, * a vehicle, mobile, with, at least - an embedded CPU (UCE), which includes a module of low-level diagnosis, in that there is practically no diagnosis and is limited to storing and transmitting data, networks connected to the central unit, * a data acquisition probe of the ECU, * a landed or fixed diagnostic tool which analyzes the frames collected by the probe and implements diagnostic and repair algorithms, with a human-machine interface and a computer terminal connecting with the manufacturer, at the manufacturer, an entire information system, with - a database (or several), a computer meta-engine, which is a diagnostic server.

  The connection between the sensor and the garage mechanic's diagnostic tool, on the one hand, and the link between the garage tool and the server of the manufacturer 2860895, on the other hand, may be radio links.

  If one wants to enter a little more in the details of the diagnostic tool, one finds there, by taking again the terminology provided by the model s Open System Interconnection (OSI), which cuts the functions of communication in seven layers, - a layer very low level of physical control of components, - a communication layer, - a data acquisition layer, in particular standardized buses of the CAN vehicle (controller network) and VAN (vehicle network), - a link layer with the onboard central unit (or the central units) of the vehicle, a functional layer, a user interface layer GUI and a top layer of applications.

  The problem of predictive diagnostics is solved, according to the applicant, with a predictive diagnostic system malfunctions of a motor vehicle comprising, embedded in the vehicle, at least one central diagnostic management unit, a data acquisition network diagnostic device, connected to the central unit, means for storing diagnostic data and communication means for communicating with fixed diagnostic means and, on the ground, - one of the elements of the assembly comprising - a tool fixed diagnosis, on the one hand, - a diagnostic server associated with a diagnostic database, on the other hand.

  The server and the database, which constitute a central system, are located at the manufacturer while the diagnostic tool, which completes the on-board mobile diagnostic management unit, can be fixed, or disembarked, either at the garage is at the manufacturer.

  It should be noted that the central diagnostic management unit must not be confused with what is generally called the cabin central unit which is a calculator.

  The remarkable aspect of the invention lies in the integration of a portion of the diagnostic intelligence on board the vehicle to react in real time. In other words, the predictive or preventive diagnosis is associated with embedded intelligence whereas the curative diagnosis corresponds to the dismounted intelligence.

  lo Thus, and as an example, if a vehicle operating variable starts to drift and cross an alert threshold, it can be diagnosed on board to trigger an alert to the manufacturer in transparency for the driver - then , after treatment, towards the driver.

  The applicant also intends to protect, as intermediate means, the on-board diagnostic device in a motor vehicle, comprising: a central diagnostic management unit, - a diagnostic data acquisition network, connected to the central unit, means for storing diagnostic data and communication means for communicating with one of the elements of the set comprising a fixed diagnostic tool, on the one hand, and a fixed central diagnostic system, comprising a server associated with a database, on the other hand.

  Advantageously, the central management unit comprises an input diagnostics data management agent controller and 3o output computers of the vehicle, that is to say agents managing the physical data transmission resources computers including the CAN, VAN and LIN networks of the vehicle, and the software resources of these computers.

  The management agents respond to the management agent controller requests and issue alerts in the event of a malfunction and / or exceeding the threshold.

  It is interesting to note that for the manufacturer, with its 40 server and associated base, motor vehicles with their central diagnostic management unit behave like

S

  personal computers of a computer network, LAN or INTRANET.

  Preferably, the diagnostic data is associated with each other to form diagnostic frames in the means for storing the diagnostic data, each frame thus stored associating the data involved in a single malfunction or a single diagnosis.

  1 o Advantageously, the central management unit includes a search module in the storage means for extracting frames containing the diagnostic data that has been the subject of an alert issued by a management agent.

  Advantageously, the central management unit comprises an interrogation module for interrogating the fixed diagnostic tool and extracting therefrom frames containing at least the diagnostic data that has been the subject of alerts issued by at least one agent. Management.

  Advantageously also, the central management unit includes a module for updating the storage means of the diagnostic device for storing the frames containing the diagnostic data from which a diagnosis could be established on the operation of the vehicle.

  All these advantages and other interesting aspects of the invention will appear more clearly with the aid of the following description of a particular non-limiting form of the diagnostic device according to the invention and of the predictive diagnosis system of the 3o malfunctions using the diagnostic device according to the invention, with reference to the appended drawing, in which: FIG. 1 represents a functional block diagram of the predictive diagnostic system according to the invention, FIG. 2 represents a functional block diagram of the diagnostic device according to the invention. the invention and FIG. 3 represents a flowchart of the operation of the diagnostic device according to the invention.

  With reference to FIG. 1, the predictive diagnostic system 1 for malfunctions of a motor vehicle (not shown) comprises either a ground-based diagnostic tool 2, or a fixed or dismounted tool located at a garage or a central system. 3, located at a motor vehicle manufacturer, and comprising a diagnostic server 31 associated with a central diagnostic data base 32, the tool and the central system can be in radio link TR, or by any other network, with an on-board diagnostic device which will be discussed below.

  These devices are those known to those skilled in the art and do not have to be more detailed here. They are usually connected to conventional electronic equipment 4 of the motor vehicle as already mentioned above.

  These conventional electronic equipment 4, essentially the ECUs (electronic control units) 310, 320, ... 3i0, control by their control modules 313, 323, ..., 3i3 and through the connections CD, and / or control, by RA network links that may belong to the CAN, VAN and LIN networks of the vehicle, with sensors 314, 324,..., 3i4 associated with these ECUs, the functions 400 of the vehicle: its engine, the passenger compartment and its man-machine interface, its electrical, pneumatic, hydraulic, thermal, etc. servitudes The data of the sensors are collected by electronic cards 312, 322, ..., 3i2, or self-test cards BITE (built-in test equipment) or OBD cards (on board diagnosis), which issue malfunction or fault alerts, when the threshold is exceeded.

  Here, the electronic equipment 4 has been modified and completed as explained below.

  On the one hand, the ECUs are equipped with diagnostic data management agents 311, 321,..., That is to say, physical measurements taken on the organs providing the functions 400 and the parameters of 3i3 modules controlling these organs, collected by the OBD / BITE cards or not, and regardless of the alerts they deliver.

  In this diagnostic data are also included charts mathematically modeling the standard physical behavior of the organs of the functions 400, which will be designated in the following by operating standards.

  It should be noted that the diagnostic data thus defined are generic of the symptomatic data of dysfunction.

  The management agents 3i1 respond to requests from a management agent controller 110, explained below, and issue deviation data with respect to operating standards and malfunction alarms.

  Together with the software resources of the ECUs, the management agents also manage the physical data transmission resources of these computers by the CAN, VAN and LIN networks of the vehicle.

  On the other hand, it is therefore provided a diagnostic device 5 embedded in the motor vehicle, whose functions are provided through: a central unit 100 diagnostic management, detailed further Zo, connected to: - management agents 310 , ..., 3i0, by a diagnostic data acquisition network link RB, a network link belonging to one or the other of the CAN, VAN and LIN networks of the vehicle, to storage means 200 of diagnostic data from the vehicle comprising a memory 201 of the history and a memory 202 of diagnostic frames, by a parallel link 203, to means 220 for communication, comprising a transceiver 222 and a pilot module 221 (driver ), by a serial link 223 to communicate with at least the fixed diagnostic station 2 or the centralized diagnosis system 3, or the second through the first.

  The central diagnostic management unit 100 may comprise several subassemblies that naturally can communicate with each other and cooperate together to perform the diagnosis.

  The driver 221 is designed to communicate so that for the server and its associated base, or tool 2, the central diagnostic management unit 100 behaves like a personal computer of a computer network, LAN or INTRANET.

  There is further provided a link 213 with the HMI (human machine interface) of the passenger compartment of the vehicle and the 211 alert and interrogation 212 functions, specific to the management of diagnostics, in this HMI.

  The central management unit 100 will now be described, with reference to FIG. 2.

  This unit comprises a real-time controller 110, already mentioned above, 3i1 agents for managing the diagnostic data, input and output computers 3i0 of the vehicle.

  The controller 110 is connected at the output to a module 120 for searching the received data frames and alerts, itself connected to a memory 121 of the data being processed, to the memory 202 of the diagnostic frames via the link 203, and input to a module 140 for managing requests to be sent to the management agents 3i1, this module 140 being connected to a memory 141 of the current requests.

  The central unit 100 also comprises a diagnostic interrogation module 130.

  The diagnostic interrogation module 130 receives the candidate data frames to be analyzed, transmitted by the frame search module 120, and can send requests to the request management module 140 for the agents 3i 1, each of the o Agents managing and issuing these requests in the corresponding ECUs 3i0, either to the BITE 3i2 modules or to the 3i3 command control modules.

  The module 130 comprises at least two interrogation sub-modules 3s: an internal interrogation sub-module 132 connected to the memory 201 of the vehicle history of the storage means 200 via the link 203, to search for frames having already given rise, for the vehicle, to a preventive diagnosis 40 or predictive, that is to say a pre-diagnosis, an external interrogation sub-module 134, at the station 2 or centralized system 3 diagnosis, via a message generator module 170 and via the link 223, to extract frames which have already given rise, for the type of vehicle, to a pre-diagnosis.

  The diagnostic data is associated with each other to form significant pre-diagnosis frames, each frame being defined by the association of the data involved in a single pre-diagnosis, 1 o and when the pre-diagnosis is proven, for example when the occurrence of the fault, declared in the HMI, corresponding to the pre-diagnosis, or if the tool 2 or the central diagnostic system 3 confirms it, the frames are stored in the memory 202 of the storage means 200.

  The submodule 134 also controls, also connected to the memory 202 by the link 203, a module 160 for updating this memory 202 frames containing diagnostic data from which a pre-diagnosis could be established on the operation of the vehicle.

  Finally, the external interrogation sub-module 134 and the request management module 140 are connected to the HMI through a dialogue module 180 controlling the HMI via the link 213, and receiving the answers.

  The operation of the system will now be described, through a non-limiting example.

  The significant physical measurements of the operation of the engine 400 of the vehicle, to take this example, are cyclically carried out by the sensors 314 and collected by the card 312 via the network RA or directly calculated by the ECU 310, in this case a CCM ( engine control computer), when the measurement is not accessible by calculation. The management agent 310 takes some of these measurements, for example from the upstream and downstream lambda probes, in connection with significant pre-diagnosis frames related to the current operation, issued by the central processing unit 100. diagnostics, as well as the operating standards corresponding to the operating parameters being applied, here, for example the carburizing properties charts and the acceleration control angle, the torque, the engine oil temperature, etc. ..

  If a measurement is outside the operating standards of the engine, for example the oil temperature, the agent 310 issues a dated alert and all of the diagnostic data thus collected to the controller 110 via the network RB.

  1 n The controller 110, with reference to FIG. 3, collects, in step 10, all the alerts and the corresponding diagnostic data from all the ECUs of the vehicle and sorts them chronologically to prepare for the subsequent establishment of a history. , the dating may be a pre-diagnosis element, before communicating to the module 120 search frames.

  In the example chosen, in step 20, the module 120 synthesizes the diagnostic data received from the various ECUs and stored over time in the memory 121 of the data being processed by assembling them into a coherent candidate frame at the functional level of the vehicle, that is to say assembling data, engine control, electricity, cooling, ..., concerning physical quantities affecting the same functional process of the vehicle, for example engine operation, and according to a chronology corresponding to a possible degradation process. These candidate frames are built on the frame patterns stored in advance in the memory 202.

  In step 40, the candidate frame is compared, by the module 132, to the previous candidate frames stored in the memory 201 of the vehicle history. If she is not there, she is memorized. Otherwise, the module 120 takes into account the result of the treatment which then took place. In particular, if there has been pre-diagnosis, we go to a step 41 HMI alert, and again to step 20 to search for a new candidate frame.

  If in step 40 it turns out that the candidate frame is new for the vehicle, proceed to a step 50, executed by the module 134, in which the same interrogation as in the step 40 is carried out, but carrying , this time on the entire fleet of vehicles of the same type. For this, during this step 50, the module 134 sends requests to the message generation module 170 which, during a step 51, loads the communication means 220, via the link 223, the driver 221 ensuring the waiting, in a step 52, the responses of the tool 2 or the central diagnostic system 3, and possibly a restart in case of communication failure.

  In step 50, the module 134 retrieves the frames of the answers and pre-diagnostics communicated and, in step 60, analyzes them. These responses may be a pre-diagnosis corresponding to the candidate frame, in which case the alerting step 41 is executed, and the driver of the vehicle alerted, or frames of diagnostic data compatible with the candidate frame, in which case we pass in a step 70 of further research to be performed by the module 140, or an absence of risk, in which case no pre-diagnosis is possible and returns to step 10.

  It can be seen that if a vehicle operating variable starts drifting outside the standards and possibly crossing an alert threshold, it can be diagnosed on board to trigger an alert to the manufacturer and, after treatment, to the driver.

  By compatible frames is meant frames having the same diagnostic data in common, one more complete with more data than the other, among the data capable of generating at least one symptomatic data dysfunction.

  In this case, if the candidate frame is more complete, it is its restriction to the response frame that is processed, otherwise, during step 70, the module 140 records the missing data and analyzes the possibility of collecting them or no.

  In the latter case, it returns to step 10. Otherwise, a test request 71 may be requested from the driver of the vehicle via the instrument panel HMI and, after acknowledgment 72 of the driver, the module 120 executes a step 30 of updating the candidate frame for a new analysis in steps 40 and 50 executed by the internal and external interrogation modules 132 and 134.

  But it is possible that the intervention of the driver is not necessary. In this case, at a step 80, the module 140 generates a request for the management agents 3i1 concerned, a request sent by the controller 110 via the network RB during a step 90.

  At this stage, the agents concerned pass on the request to their ECU, which 1) via their control card 3i3, acts on the process to make the io more defective measures, and 2) programs the execution of complementary measures by their card. test BITE or OBD 312 3) completes its calculation functions by a complementary calculation of missing measurement. The necessary software can then be downloaded from the central system 3.

  In the latter case, there is provided in the central unit (100) a function (not shown) for downloading software, from the central diagnostic system 3, in the computers 3i0, to modify, via the agents 3i 1, ECU computer software that controls the acquisition of diagnostic data.

  At the end of execution of step 90, step 30 is reactivated.

Claims (13)

  A system (1) for predictive diagnosis of malfunctions of a motor vehicle comprising, on board the vehicle, at least one central unit (100) for diagnostic management, - a network (RA, RB) for data acquisition diagnostic device, connected 1 o to the central unit, means (200) for storing diagnostic data and - communication means (220) for communicating with fixed diagnostic means and, on the ground, - one of the elements of the set comprising - a fixed diagnostic tool (2), on the one hand, - a diagnostic server (31) associated with a diagnostic database (32), on the other hand.   2- System according to claim 1, characterized in that if a vehicle operating variable begins to drift and to cross an alert threshold, this is diagnosed on board to trigger an alert to the manufacturer and after treatment, towards the driver.   3- diagnostic device (5) embedded in a motor vehicle, comprising: - a central unit (100) diagnostic management, - a network (RA, RB) diagnostic data acquisition, connected to the unit central, - diagnostic data storage means (200) and communication means (220) for communicating with one of the elements of the set comprising a fixed diagnostic tool (2), on the one hand, and a fixed central diagnostic system (3) comprising a server (31) and a database (32), on the other hand.   4- Device according to claim 3, wherein the central management unit (100) comprises a controller (110) of agents (3i1) for managing the diagnostic data input and output ECU computers (3i0) of the vehicle .   5- Device according to claim 4, wherein the management agents (3i1) respond to requests from the controller (110) management agents and issue alerts in case of malfunctions.   6. Device according to one of claims 3 to 5, wherein the diagnostic data is associated with each other to form diagnostic frames in the means (200) for storing the diagnostic data.   7- Device according to claim 6 wherein each frame i o stored associate the data involved in a single malfunction that can lead to a single diagnosis.   8- Device according to one of claims 3 to 7, wherein the central management unit (100) comprises a module (120) for searching in the storage means (200) for extracting frames containing the diagnostic data having is the subject of an alert issued by a management agent (3i 1).   9- Device according to one of claims 3 to 8, wherein the central management unit (100) comprises an external interrogation module (134) for interrogating the fixed diagnostic station and extracting frames containing at least the Diagnostic data that has been alerted by at least one management agent (3i1).   10- Device according to one of claims 3 to 9, wherein the central processing unit (100) comprises a module (160) for updating the storage means (200) for storing the frames containing the data of diagnosis from which a diagnosis could be established on the operation of the vehicle. 3o   11.- Device according to one of claims 3 to 10, embedded in a vehicle and constituting part of the system of one of claims 1 and 2.   12- System according to one of claims 1 and 2, wherein there is provided a software download function from the server (31) for modifying the ECU computer software (3i0) controlling the acquisition of diagnostic data.   13.- System according to one of claims 1 and 2, wherein the central diagnostic management unit (100) comprises several sub-1.5 sets arranged to communicate with each other and cooperate together to perform the diagnosis.