A method for fast real-time diagnosis of vehicle status

Abstract

The present application belongs to the field of automobile working state monitoring and diagnosis technology, and particularly relates to a method for rapidly and real-timely diagnosing automobile state. The method comprises the following steps: obtaining the automobile ECU model of the diagnosed automobile through a diagnostic instrument; selecting the corresponding automobile state original standard library data according to the automobile ECU model; processing the corresponding automobile state original standard library data, redefining the parameters with unclear parameter definitions, obtaining the processed standard library data, and then storing the processed standard library data into a Flash memory, and simultaneously displaying the processed standard library data to an LCD display in the form of a list; periodically and real-timely reading the automobile original state data in the automobile ECU storage unit, storing the read real-time original state data into the Flash memory; selecting the corresponding automobile state processed standard library data according to the automobile ECU model, processing the real-time original state data and the processed standard library data to obtain real-time diagnosis data, and storing the real-time diagnosis data into the Flash memory, and simultaneously displaying the real-time diagnosis data to the LCD display in the form of a list. The method has the advantages of high real-time performance, fast transmission speed, simple operation, accurate diagnosis result, and the like.

Description

[0001] The field

[0002] This invention belongs to the field of automotive operating status monitoring and diagnosis technology, specifically relating to a method for rapid real-time diagnosis of automotive status. Background Technology

[0003] With the rapid development of the automotive industry and the national economy, automobiles, as an indispensable means of transportation, are becoming increasingly popular and widespread. During the use of automobiles, various problems inevitably arise. If a problem occurs while a car is in operation, it can lead to incalculable losses and impacts. Therefore, how to effectively diagnose and monitor the condition of automobiles is a concern for many companies and scholars.

[0004] Automotive diagnostics is a technology that uses specialized instruments and equipment to check the condition of a vehicle. It can test some performance indicators of the car and detect faults without affecting its use. Currently, automotive diagnostic equipment is broadly divided into three types: online diagnostics, offline diagnostics, and portable diagnostics. Online diagnostics involves the car's ECU (Electronic Control Unit) uploading collected status data to a cloud server via a mobile network. A background program reads and analyzes the status data stored on the cloud server, obtains the diagnostic results, and then sends them to the user. While this method can provide relatively accurate results, it suffers from high costs and significant latency. Offline diagnostics is characterized by its simplicity and low cost, but it also has many drawbacks, such as being limited to diagnosing relatively simple faults and lacking real-time capability. To address the problems of the above two methods, portable diagnostics has received widespread attention since its inception. Portable diagnostics, employing advanced microelectronics and software technologies, can quickly read the rich status data from the car's ECU, then process and store the read data in real time, thus effectively solving the problems of automotive diagnostics.

[0005] For portable diagnostic devices, Li Xiaojie ("Design and Implementation of Automotive Fault Diagnostic Instrument for Embedded Systems," Microcomputer Applications, vol.35, no.1, pp.132-134, 2019.) proposed a diagnostic instrument based on an embedded system and provided a brief introduction to its hardware structure. To address the control problem of the diagnostic instrument, Shi Yashan ("Software Development of Automotive Diagnostic Instrument Based on C Programming," Master's Thesis, Anhui University of Technology, 2016) proposed control software for an automotive diagnostic instrument designed using C language. The designed control software can control the diagnostic instrument to diagnose different brands and types of vehicles. To solve the problem of remote control of the diagnostic instrument, Zhan Hongyu ("Remote Automotive Diagnostic Instrument Based on Bluetooth Wireless Communication Technology," Master's Thesis, Dalian University of Technology, 2017) designed remote control software for an automotive diagnostic instrument based on the Bluetooth protocol. Huang Zhiyu et al. (Huang Zhiyu, Su Xiaolong, Li Rui, “Design of a general-purpose automotive fault diagnostic instrument on the iOS platform”, Computer Applications and Software, vol.33, no.6, pp.96-99, 2016) designed a remote control software for an automotive diagnostic instrument based on the Bluetooth communication protocol and the iOS platform.

[0006] Analysis reveals significant limitations in the hardware and control software of the proposed diagnostic tools. Firstly, the tools are functionally limited, only connecting to a limited number of vehicle types. Given the diverse range of car models and types on the market, each employing different diagnostic protocols, the tool's applicability is severely restricted. Secondly, the proposed tools operate independently and cannot collaborate with smartphones. In situations requiring prolonged diagnostic and monitoring of vehicles, this inability to work with smartphones will cause considerable inconvenience for users. The control software also presents several issues. Firstly, communication connectivity is limited. Many control software programs currently establish communication with the diagnostic tool via Bluetooth. However, Bluetooth's low-speed transmission, coupled with the diverse range of vehicle diagnostic needs, reduces real-time performance and the breadth of diagnostic capabilities due to transmission speed limitations. Finally, there is the issue of protocol conflicts. In certain scenarios requiring prolonged vehicle diagnostics and monitoring, the Bluetooth protocol can become permanently occupied, preventing its use for other purposes such as audio-visual entertainment. This creates a protocol conflict and significantly reduces the user-friendliness of the control software. Therefore, designing a portable diagnostic system that offers diverse operating modes, communication connections, functions, support for a wide range of vehicle models, convenient operation, abundant diagnostic information, strong real-time performance, and good cost-effectiveness to effectively address these issues is a topic worthy of in-depth research and has significant practical implications. Summary of the Invention

[0007] This invention provides a method for rapid real-time diagnosis of vehicle status, offering a fast, real-time, convenient, efficient, and intelligent diagnostic approach to the problem of how to monitor and diagnose the operating status of a vehicle. This overcomes the limitations of existing methods that can only mechanically read data from the vehicle's ECU without in-depth analysis.

[0008] To achieve the above objectives, the present invention provides a method for rapid real-time diagnosis of vehicle status, the method comprising:

[0009] Obtain the ECU model of the vehicle being diagnosed using a diagnostic tool;

[0010] Select the corresponding original standard library data for vehicle status based on the vehicle ECU model;

[0011] The original standard library data of the corresponding vehicle status is processed, and the parameters with unclear parameters are redefined. The processed standard library data is then stored in the Flash memory and displayed on the LCD screen in the form of a list.

[0012] The system periodically reads the vehicle's original state data from the vehicle's ECU storage unit in real time and stores the read real-time original state data in the Flash memory.

[0013] Select the corresponding standard library data after processing the vehicle status according to the vehicle ECU model, process the real-time raw status data and the processed standard library data to obtain real-time diagnostic data, store the real-time diagnostic data in the Flash memory, and display it on the LCD screen in the form of a list.

[0014] Furthermore: Two data communication buses are set up. One uses a general protocol to establish communication connections with many automotive ECUs on the market; the other is set up as a function-specific bus to establish communication connections with niche automotive ECUs on the market.

[0015] Before obtaining the ECU model of the vehicle being diagnosed using a diagnostic tool, it is necessary to determine whether the general protocol can communicate with the vehicle ECU. If the general protocol of the diagnostic tool cannot communicate with the vehicle ECU, it is necessary to test whether the dedicated protocol can communicate.

[0016] Once communication is established using any one of the communication methods, the vehicle identification code is read from the ECU.

[0017] Furthermore, real-time raw status data includes two types: operational data and static data. Operational data is the monitoring data collected by the vehicle's ECU through various sensors, including power supply voltage regulation data, fuel injection quantity data, DPF regeneration status data, SCR injection status data, EGR data, TVA data, vehicle speed data, and throttle angle data. Static data is constant data stored in the vehicle's ECU, including the vehicle identification code. Operational data is used for mathematical processing to diagnose the vehicle's status. The Flash memory stores raw standard library data of vehicle status from different manufacturers. Static data is used to identify the vehicle's ECU model, thereby selecting the corresponding raw standard library data of vehicle status to assist in mathematical processing.

[0018] Furthermore:

[0019] The real-time diagnostic data obtained through mathematical processing includes:

[0020] The diagnostic value is obtained by directly subtracting the real-time raw status data from the processed standard library data;

[0021] Obtain basic values ​​A1 and B1 from the processed standard library data, and basic values ​​A2 and B2 from the real-time raw state data. Obtain the standard integrated value and the raw integrated value according to the formula A*B. Subtract the standard integrated value from the raw integrated value to obtain the diagnostic value.

[0022] The basic values ​​A1 and B1 are obtained from the processed standard library data, and the basic values ​​A2 and B2 are obtained from the real-time raw state data. The standard integrated value and the raw integrated value are obtained according to the formula A±B. The diagnostic value is obtained by subtracting the standard integrated value from the raw integrated value.

[0023] Obtain the gain value a1, the basic value A, and the offset value B from the processed standard library data. Obtain the gain value a2 from the original state data. Obtain the standard integrated value and the original integrated value according to the formula a*A±B. Subtract the standard integrated value from the original integrated value to obtain the diagnostic value.

[0024] Furthermore, it also includes: determining whether the diagnostic instrument interacts with the remote control center via wired or wireless means. If not, the diagnostic instrument independently diagnoses and displays the data. If it does, it receives parameter settings from the control center, sends historical raw status data and diagnostic data to the control center, and displays and stores the data through the control center after turning off its own display.

[0025] Furthermore, it also includes switching between multiple modes, which include:

[0026] In pause mode, the LCD display keeps showing the current data and only pauses the display of updated diagnostic data;

[0027] Data transmission mode: Determine whether a communication connection has been established with the control center. If a communication connection is established, stop the diagnostics and send historical raw status data and historical diagnostic data to the control center in two data packets in sequence; otherwise, do not send data and prompt the user to establish a communication connection.

[0028] Normal working mode: Stop the current pause mode or data transmission mode and return to normal periodic diagnostics;

[0029] Enter screen-off or on-screen mode: If the LCD display is already on, turn off the LCD display; if the LCD display is already off, turn on the LCD display.

[0030] This invention also provides a method for rapidly diagnosing vehicle status in real time, the method comprising:

[0031] Set the parameters and commands for the diagnostic instrument to work, parse and reassemble the command data, and then send the reassembled command data to the diagnostic instrument.

[0032] The system receives data sent by the diagnostic tool, parses the data to generate corresponding controls, including selecting the corresponding standard library data M2 based on the determined vehicle ECU model to correct the physical meaning of the parameters, resulting in the processed standard library data N2; simultaneously, it displays the processed standard library data N2; displays the real-time diagnostic data sent by the diagnostic tool; and stores the historical raw state data and historical diagnostic data sent by the diagnostic tool.

[0033] Furthermore, the parameter commands include setting the diagnostic cycle of the diagnostic instrument and turning off the LCD display of the diagnostic instrument.

[0034] Furthermore, it also includes storing the data in four parts: the first part stores the original standard library data M2 of the vehicle status and the processed standard library data N2; the second part stores the real-time diagnostic data sent by the diagnostic instrument; the third part stores the historical original status data sent by the diagnostic instrument; and the fourth part stores the historical diagnostic data sent by the diagnostic instrument.

[0035] Furthermore, the original standard library data M2 is obtained and backed up from the diagnostic instrument during idle time, and the same method is used to process the original standard library data M2 to obtain the processed standard library data N2.

[0036] The present invention has the following advantages and beneficial effects:

[0037] This invention provides a fast, real-time, convenient, efficient, and intelligent diagnostic method to overcome the problems of existing methods that can only mechanically read data from the vehicle's ECU without in-depth analysis. Attached Figure Description

[0038] Figure 1 The diagram shows a schematic of the diagnostic instrument structure used in a method for rapid real-time diagnosis of vehicle status provided by an exemplary embodiment of the present invention.

[0039] Figure 2 The diagram illustrates a processor hardware structure used in a method for rapid real-time diagnosis of vehicle status provided by an exemplary embodiment of the present invention.

[0040] Figure 3 The diagram illustrates the workflow of a diagnostic instrument for a method of rapid real-time diagnosis of vehicle status provided by an exemplary embodiment of the present invention.

[0041] Figure 4 This diagram illustrates the structure of a control center used in a method for rapid real-time diagnosis of vehicle status provided by an exemplary embodiment of the present invention.

[0042] Figure 5 The diagram illustrates a workflow of a control center for a method for rapid real-time diagnosis of vehicle status provided by an exemplary embodiment of the present invention. Detailed Implementation

[0043] To enable those skilled in the art to better understand the technical solutions of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0044] This invention provides a method for rapid real-time diagnosis of vehicle status, which runs on a diagnostic instrument and collects and diagnoses data through the diagnostic instrument.

[0045] Obtain the ECU model of the vehicle being diagnosed using a diagnostic tool;

[0046] Select the corresponding original standard library data for vehicle status based on the vehicle ECU model;

[0047] The original standard library data of the corresponding vehicle status is processed, and the parameters with unclear parameters are redefined. The processed standard library data is then stored in the Flash memory and displayed on the LCD screen in the form of a list.

[0048] The system periodically reads the vehicle's original state data from the vehicle's ECU storage unit in real time and stores the read real-time original state data in the Flash memory.

[0049] Based on the vehicle ECU model, the corresponding standard library data after vehicle status processing is selected. The real-time raw status data and the processed standard library data are processed to obtain real-time diagnostic data, which is then stored in the Flash memory and displayed on the LCD screen in a list format.

[0050] Two data communication buses are set up. One uses a general protocol to establish communication connections with many automotive ECUs on the market; the other is set up as a function-specific bus to establish communication connections with niche automotive ECUs on the market.

[0051] Before obtaining the ECU model of the vehicle being diagnosed using a diagnostic tool, it is necessary to determine whether the general protocol can communicate with the vehicle ECU. If the general protocol of the diagnostic tool cannot communicate with the vehicle ECU, it is necessary to test whether the dedicated protocol can communicate.

[0052] Once communication is established using any one of the communication methods, the vehicle identification code is read from the ECU.

[0053] Real-time raw status data includes two types: operational data and static data. Operational data is the monitoring data collected by the vehicle's ECU through various sensors, including power supply voltage regulation data, fuel injection quantity data, DPF regeneration status data, SCR injection status data, EGR data, TVA data, vehicle speed data, and throttle angle data. Static data is constant data stored in the vehicle's ECU, including the vehicle identification code. Operational data is used for mathematical processing to diagnose the vehicle's status. The Flash memory stores raw standard library data of vehicle status from different manufacturers. Static data is used to identify the vehicle's ECU model, thereby selecting the corresponding raw standard library data of vehicle status to assist in mathematical processing.

[0054] In this embodiment, see Figure 1 The diagram shown is a schematic of the diagnostic instrument used.

[0055] Figure 1 A schematic diagram of a diagnostic instrument structure provided by an exemplary embodiment of the present invention is shown. The diagnostic instrument can operate independently and display diagnostic-related data on its built-in LCD display. Alternatively, the diagnostic instrument can operate entirely under the control of a control center, displaying all diagnostic-related data on the control center. Once a communication connection is established between the diagnostic instrument and the control center, control of the diagnostic instrument can be completely delegated to the control center. In addition to controlling the start / stop and data upload functions of the diagnostic instrument, the control center can also control the on / off state of the diagnostic instrument's LCD display to reduce power consumption.

[0056] To provide a more intuitive display of diagnostic results, the diagnostic instrument's LCD display or the control center's result visualization module can display the modified vehicle status standard library data and real-time diagnostic data in a list format. When an abnormality is detected, the LCD display or control center highlights the data to indicate a problem with that vehicle status and uses "↑" and "↓" icons to indicate whether the status is too high or too low. This invention's method is implemented using the following diagnostic instrument, including:

[0057] LCD Display: This display has both display and interactive functions. The display is used to show data related to vehicle diagnostics, while the interactive function is used by the user to set the working parameters of the diagnostic tool, such as the diagnostic cycle.

[0058] Data transmission module: This module connects the diagnostic instrument and the control center via wired or wireless means. Once connected, the diagnostic instrument can send diagnostic data to the control center and receive parameter setting data from the control center. This module includes both wired and wireless modules. The wired module transmits data via a data cable, while the wireless module transmits data via Bluetooth and Wi-Fi. For this system, wired communication has higher priority than wireless communication; that is, when both communication methods are available, wired communication is used preferentially.

[0059] Mode switching key: This module triggers the corresponding function of the diagnostic instrument or puts the diagnostic instrument into the corresponding mode by different numbers of consecutive presses and different press times. The mode switching key has two buttons, and the specific functions of each button are as follows: (1) The first button, a short press once enters the pause mode, that is, after the processor detects the signal, the LCD display keeps displaying the current data unchanged, that is, the display of updated diagnostic data is paused, but the rest of the part still works normally; a quick short press twice enters the data transmission mode, that is, after the processor detects the signal, it first determines whether to establish a communication connection with the control center. If a communication connection is established, the diagnostics will stop and the historical original state data and historical diagnostic data stored in the Flash memory will be sent to the control center in two data packets in sequence; otherwise, no data will be sent and the user will be prompted to establish a communication connection; press and hold once to return to the normal working mode, that is, after the processor detects the signal, it will stop the current pause mode or data sending mode, return to the normal periodic diagnostics, and display and store the relevant diagnostic data; the three modes of the first button have the same priority. When the diagnostic instrument enters another mode from the current mode, it needs to stop the current mode before it can enter; (2) the second button, press once to enter the screen off or on mode, that is, if the LCD display is on, the LCD display will be off, and if the LCD display is off, the LCD display will be on; press and hold once to enter the power on / off mode, if the diagnostic instrument is on, the diagnostic instrument will be off, and if the diagnostic instrument is off, the diagnostic instrument will be on.

[0060] Bus Conversion Module: This module converts SPI and UART buses to CAN buses. One CAN bus is configured as a general-purpose bus, exchanging data according to general protocols such as J1939, enabling the diagnostic tool to establish communication connections with many automotive ECUs on the market. The other CAN bus is configured as a dedicated bus, exchanging data according to dedicated protocols such as ISO15765 and ISO14229, enabling the diagnostic tool to establish communication connections with less common automotive ECUs on the market. This module increases the types and range of vehicles that the diagnostic tool can diagnose.

[0061] Processor: This module is the control and decision-making core of the entire diagnostic instrument. It periodically reads the original vehicle status data from the vehicle ECU storage unit in real time and stores the read real-time original status data in the Flash memory; it performs mathematical processing on the real-time original status data to obtain real-time diagnostic data, stores the real-time diagnostic data in the Flash memory, and displays it on the LCD screen in list form; it selects the corresponding original standard library data M1 of the vehicle status according to the vehicle ECU model, performs mathematical processing to obtain the processed standard library data N1, and stores it in the Flash memory, while also displaying it on the LCD screen in list form; it detects the information input by the mode switch key and generates corresponding control; it detects whether the diagnostic instrument has established a communication connection with the control center, and determines whether to send real-time diagnostic data to the control center based on the communication connection status; it processes the information input to the LCD screen and the information sent by the control center to generate corresponding control; it reads the historical original status data and historical diagnostic data stored in the Flash memory and uploads the read data to the control center.

[0062] Flash memory: This memory is divided into three areas for storage. One area stores the original standard library data M1 and the processed standard library data N1. Another area stores the real-time raw status data, and the last area stores the real-time diagnostic data. Once the real-time raw status data is stored in the Flash memory, it becomes historical raw status data; similarly, once the real-time diagnostic data is stored in the Flash memory, it becomes historical diagnostic data.

[0063] Figure 2 This diagram illustrates the processor hardware structure used in a method for rapid real-time diagnostics of vehicle status according to an exemplary embodiment of the present invention. All control and decision-making of the diagnostic tool are performed within the processor. The processor consists of the following functional units: a Bluetooth / Wi-Fi control unit, a wired transmission control unit, an LCD display control unit, a mode switching detection unit, a data processing unit, an ECU interaction unit, an SPI / UART transceiver unit, a Flash control unit, and a kernel unit.

[0064] Bluetooth / Wi-Fi Control Unit: This unit detects whether the diagnostic instrument and the control center have established a connection via Bluetooth / Wi-Fi and outputs an indication signal to the core unit. Once a communication connection is established, the Bluetooth control unit controls the Bluetooth module to receive parameter setting data from the control center, and the Wi-Fi control unit controls the Wi-Fi module to send historical raw status data and diagnostic data to the control center. The diagnostic data here includes real-time diagnostic data and historical diagnostic data. If the control center cannot send setting parameters via Bluetooth due to distance limitations, it can automatically switch to sending setting parameters via Wi-Fi.

[0065] Wired transmission control unit: This unit functions the same as the Bluetooth / WIFI control unit, specifically detecting whether the diagnostic instrument and the control center have established a connection via data cable and outputting an indication signal to the core unit. Once the communication connection is established, the diagnostic instrument can receive parameter setting data from the control center via data cable and can also upload data to the control center.

[0066] LCD Display Control Unit: This unit can display standard library data N2 and real-time diagnostic data on the LCD screen. It can also collect parameter data set by the user via the LCD screen and transmit the collected data to the kernel unit. Furthermore, this unit can receive commands from the kernel unit to turn the LCD screen on or off and execute the corresponding controls.

[0067] Mode switching detection unit: This unit is used to detect information such as the number of times and the duration of key presses, then encodes and processes this information and outputs it to the kernel unit.

[0068] Data Processing Unit: This unit performs mathematical processing on the read real-time raw status data to obtain real-time diagnostic data, and outputs the real-time diagnostic data to the core unit. The real-time raw status data read by the diagnostic tool from the vehicle ECU includes both operational data and static data. Operational data is monitoring data collected by the vehicle ECU through various vehicle sensors, including but not limited to power supply voltage regulation data, fuel injection quantity data, DPF regeneration status data, SCR injection status data, EGR data, TVA data, vehicle speed data, and throttle angle data. Static data is constant data stored in the vehicle ECU, including but not limited to the Vehicle Identification Number (VIN). Operational data is used for mathematical processing to diagnose the vehicle's status. The Flash memory and control center both store raw standard library data of vehicle status from different manufacturers. Static data can be used to identify the vehicle ECU model, thereby selecting the corresponding vehicle status standard library data to assist in mathematical processing. The specific mathematical processing methods of this unit include, but are not limited to: (1) directly subtracting the real-time raw state data from the original standard library data to obtain the diagnostic value; (2) obtaining the basic values ​​A1 and B1 from the original standard library data, obtaining the basic values ​​A2 and B2 from the real-time raw state data, obtaining the standard integrated value and the original integrated value according to the formula A*B, and subtracting the original integrated value from the standard integrated value to obtain the diagnostic value; (3) obtaining the basic values ​​A1 and B1 from the original standard library data, obtaining the basic values ​​A2 and B2 from the real-time raw state data, obtaining the standard integrated value and the original integrated value according to the formula A±B, and subtracting the original integrated value from the standard integrated value to obtain the diagnostic value; (4) obtaining the gain value a1, the basic value A, and the offset value B from the original standard library data, obtaining the gain value a2 from the original state data, obtaining the standard integrated value and the original integrated value according to the formula a*A±B, and subtracting the original integrated value from the standard integrated value to obtain the diagnostic value.

[0069] ECU Interaction Unit: This unit is designed with general-purpose protocols, such as the J1939 protocol, and specific-purpose protocols, such as the ISO15765 and ISO14229 protocols. During operation, this unit selects the appropriate interaction protocol based on the identified vehicle ECU model. After selection, the unit can acquire the vehicle's raw status data in real time according to the chosen protocol and output the acquired raw status data to the kernel unit.

[0070] SPI / UART transceiver unit: Both general-purpose and dedicated protocols only specify and define the content and order of data transmission and reception, but do not define the underlying communication method. This unit enables data transmission and reception for general-purpose and dedicated protocols using either SPI or UART bus methods.

[0071] Flash control unit: This unit is used to control the read and write operations of the original standard library data M1 and the processed standard library data N1, control the write operations of real-time raw status data and real-time diagnostic data, and control the read operations of historical raw status data and historical diagnostic data.

[0072] Kernel Unit: This unit is the control core of the processor. Its main functions include: triggering commands to periodically read the vehicle ECU status data in real time; sending the received real-time raw status data to the Flash control unit, and sending the received real-time diagnostic data to the Flash control unit and the LCD display control unit; selecting the corresponding raw standard library data M1 according to the vehicle ECU model, performing mathematical processing to obtain the processed standard library data N1, and then sending it to the Flash control unit and the LCD display control unit; receiving setting data sent by the user through the LCD display control unit, receiving setting data and indication signals sent by the Bluetooth / WIFI control unit or the wired transmission control unit, receiving data sent by the mode switching detection unit, and then parsing and processing all the received data to generate corresponding controls, including start / stop operations and setting the cycle for reading the vehicle ECU status data, including sending commands to turn the LCD display on or off to the LCD display control unit, and controlling the Flash control unit to read raw status data and historical diagnostic data, and sending the read data to the WIFI control unit or the wired transmission control unit.

[0073] Figure 3 This diagram illustrates the workflow of a diagnostic tool for a system that provides rapid real-time diagnosis of vehicle status, according to an exemplary embodiment of the present invention. When the diagnostic tool is powered on, it proceeds according to... Figure 3 The diagnostic instrument operates according to the specified workflow. It should be noted that the diagnostic instrument handles the first and second button presses using an interrupt-driven approach. Therefore, steps 26-33 and 34-42 in the flowchart are not selectively executed from the main program, but rather run concurrently. The specific workflow of the diagnostic instrument is as follows:

[0074] Step 1: Power on the diagnostic instrument.

[0075] Step 2, Initialize the diagnostic instrument. Initialization includes setting initial values ​​for some variables, resetting the registers and functional modules in the processor, and resetting external modules connected to the processor.

[0076] Step 3: Determine if the diagnostic instrument has established a communication connection with the control center. The diagnostic instrument can operate independently of the control center or under its control. If a communication connection has been established, the diagnostic instrument will perform diagnostics under the control of the control center; proceed to Step 4. If no communication connection has been established, the diagnostic instrument will operate independently; proceed to Step 13.

[0077] Step 4: Assign the identifier link_soft the value 1. A value of 1 for link_soft indicates that the diagnostic tool will operate under the control of the control center. After completing the assignment, proceed to step 5.

[0078] Step 5: Determine if the diagnostic tool and control center have established a wired communication connection. The diagnostic tool and control center can establish a communication connection via both wired and wireless methods, with wired connections having higher priority than wireless connections. If the diagnostic tool and control center have established a wired communication connection, proceed to Step 6. Otherwise, proceed to Step 7.

[0079] Step 6: Assign the value 0 to the identifier "wireless". A value of 0 for "wireless" indicates that the diagnostic tool and control center have established a wired communication connection. After completing the assignment, proceed to step 12.

[0080] Step 7: Determine if the diagnostic tool and control center have established a communication connection via Bluetooth. The control center typically sends command data to configure the diagnostic tool via Bluetooth and receives diagnostic data via Wi-Fi. If the diagnostic tool and control center have not established a communication connection via Bluetooth, proceed to step 8; otherwise, proceed to step 9.

[0081] Step 8: Assign the value 0 to the identifier "bluetooth". Due to the short communication range of Bluetooth, there are situations where the diagnostic tool cannot establish a communication connection with the control center via Bluetooth. When a Bluetooth connection cannot be established, the control center will automatically establish a communication connection via Wi-Fi. A value of 0 for "bluetooth" indicates that the Bluetooth connection has failed. After completing the assignment, proceed to step 10.

[0082] Step 9: Assign the value 1 to the identifier "bluetooth". A value of 1 for "bluetooth" indicates that a communication connection has been successfully established via Bluetooth. After the assignment is complete, proceed to step 10.

[0083] Step 10: Determine if the diagnostic instrument and control center have established a communication connection via Wi-Fi. If a Wi-Fi connection is established, proceed to Step 11. If not, proceed to Step 3, which indicates that the wireless communication connection is invalid and the connection method needs to be re-tested.

[0084] Step 11: Assign the value 1 to the identifier "wireless". A value of 1 for "wireless" indicates that the diagnostic instrument and the control center have successfully connected wirelessly. After the assignment is complete, proceed to step 12.

[0085] Step 12: Turn off the LCD display. Once the diagnostic instrument establishes a communication connection with the control center via wired or wireless means, it can operate under the control of the control center. Diagnostic results can be displayed on the result visualization module in the control center. To reduce power consumption, the LCD display needs to be turned off. After completing this step, proceed to step 14.

[0086] Step 13: Assign the identifier link_soft to 0. To adapt to different application scenarios, the diagnostic instrument can operate independently of the control center. When operating independently, assign the identifier link_soft to 0. After the assignment is complete, proceed to step 14.

[0087] Step 14: Wait for parameter setting commands. The diagnostic instrument determines its communication connection status based on various identifiers, and then waits to receive parameter commands to configure its operation. Once the parameter setting commands are received, the diagnostic instrument is configured, and then the process proceeds to Step 15.

[0088] Step 15: Wait for the start command. The diagnostic instrument waits for the command to start diagnostics. Once the start command is received, the diagnostic instrument begins diagnostics, proceeding to step 16.

[0089] Step 16: Determine if the diagnostic tool's universal protocol can communicate with the vehicle's ECU. Different manufacturers and types of vehicles use different ECU models, which may cause the diagnostic tool's universal protocol to be unable to communicate with the vehicle's ECU. If the universal protocol can communicate with the vehicle's ECU, proceed to step 19; otherwise, proceed to step 17.

[0090] Step 17: Determine if the diagnostic tool's proprietary protocol can communicate with the vehicle's ECU. If the diagnostic tool's general protocol cannot communicate with the vehicle's ECU, it is necessary to test whether the proprietary protocol can communicate. If communication is possible, proceed to step 19; otherwise, proceed to step 18.

[0091] Step 18: The diagnostic tool alarms and indicates that it cannot diagnose. When neither the general-purpose nor the dedicated protocol of the diagnostic tool can communicate with the vehicle's ECU, it indicates that the diagnostic tool cannot effectively connect to the vehicle's ECU. In this case, the diagnostic tool needs to alarm the user and indicate that it cannot diagnose.

[0092] Step 19: Read the Vehicle Identification Code. When the diagnostic tool can communicate with the vehicle's ECU, the first step is to read the Vehicle Identification Code from the ECU. The Vehicle Identification Code contains the specific model number of the vehicle's ECU. After reading, proceed to Step 20.

[0093] Step 20: Select the corresponding raw standard library data M1 from the Flash memory. The Flash memory stores different types of raw standard library data for vehicle status. After the diagnostic tool reads the vehicle identification code, it selects the corresponding raw standard library data M1 based on this identification code. After selection, proceed to step 21.

[0094] Step 21: Perform mathematical processing to obtain the processed standard library data N1. Not all data in the standard library data M1 has a clearly defined physical meaning. To address this, mathematical processing is needed to obtain a clearer and more explicit standard library data N1. After obtaining the standard library data N1, proceed to step 22 to store the data in the Flash memory, and then proceed to step 23.

[0095] Step 22: Store in Flash memory. This step involves storing the obtained data, including standard library data N1, the original status data of the vehicle ECU, and the diagnostic data of the vehicle ECU, into Flash memory.

[0096] Step 23: Periodically read the raw status data from the vehicle's ECU. The diagnostic tool begins periodically reading the status data of the vehicle's ECU in real time at a set interval. After the reading is complete, it proceeds to step 22 to store the data in the Flash memory, and then proceeds to step 24.

[0097] Step 24: Perform mathematical processing to obtain diagnostic data. In the raw status data obtained by the diagnostic tool from the vehicle's ECU, some data has unclear physical meaning. Therefore, mathematical processing is required to obtain diagnostic data with clear physical meaning. After completing the mathematical processing, the process proceeds to step 22 to store the data in the Flash memory, and then to step 25.

[0098] Step 25: Display standard library data N1 and real-time diagnostic data. After obtaining the diagnostic data, the diagnostic instrument displays the standard library data N1 and real-time diagnostic data on the LCD screen or the control center, depending on the communication connection with the control center. After completing this step, return to step 23 to begin the next diagnostic cycle.

[0099] Step 26: Determine if the information is input from the first key. After the diagnostic instrument completes initialization, the detection of the first and second keys is performed in an interrupt manner. If the information is input from the first key, proceed to step 27; otherwise, continue the detection.

[0100] Step 27: Determine if the first button was pressed briefly once. If a brief press of the first button is detected, proceed to step 28; otherwise, proceed to step 29.

[0101] Step 28: Enter Pause Mode. Entering pause mode only pauses the diagnostic tool's display updates; other functional modules continue to operate normally. Pause mode is used to capture and display diagnostic data at a specific moment. Upon entering this mode, the system immediately proceeds to step 33 to detect the information input by the next first key press.

[0102] Step 29: Determine if the first button has been pressed twice. If the signal of pressing the first button twice is detected, proceed to step 30; otherwise, proceed to step 31.

[0103] Step 30: Enter data transmission mode. Upon entering data transmission mode, the diagnostic instrument first determines if a communication connection has been established with the control center. If a connection is established, diagnostics stops, and the instrument sends historical raw status data and historical diagnostic data stored in the Flash memory to the control center in two data packets sequentially; otherwise, no data is sent, and a connection failure message is displayed. Once this mode is entered, the system immediately proceeds to step 33 to detect the information input by the next first key press.

[0104] Step 31: Determine if the first button was pressed and held once. If it was pressed and held once, proceed to step 32; otherwise, immediately proceed to step 33 to check the information input by the next first button press.

[0105] Step 32: Enter normal mode. The diagnostic instrument stops its current pause mode or data transmission mode and returns to normal periodic diagnostics, displaying and storing relevant diagnostic data. Upon entering this mode, it immediately proceeds to step 33 to detect the information input by the next first key press.

[0106] Step 33, return to step 1. This return does not mean returning to the starting state, but rather returning to step 26 to check the information for the next first key input.

[0107] Step 34: Determine if the information is input from the second button. After the diagnostic instrument completes initialization, it performs interrupt-based testing on the first and second buttons. If the information is input from the second button, proceed to step 35; otherwise, continue testing.

[0108] Step 35: Determine if it is a short press of the second button. If yes, proceed to step 36; otherwise, proceed to step 39.

[0109] Step 36: Determine if the diagnostic device screen is off. If it is off, proceed to step 37; otherwise, proceed to step 38.

[0110] Step 37: Turn on the screen. The diagnostic instrument's screen is activated. After completing this step, immediately proceed to step 42 to test the information entered via the second button.

[0111] Step 38, turn off the screen. The diagnostic instrument's screen is turned off. After completing this step, immediately proceed to step 42 to test the information entered by the next second key.

[0112] Step 39: Determine if the diagnostic instrument is powered on. If the diagnostic instrument is powered on, proceed to step 41; otherwise, proceed to step 40.

[0113] Step 40: Power on the diagnostic instrument. After completing this step, immediately proceed to step 42 to test the information entered by the second button.

[0114] Step 41: Power off the diagnostic instrument. After completing this step, immediately proceed to step 42 to test the information entered by the second button.

[0115] Step 42, Return to step 2. This return does not mean returning to the starting state, but rather returning to step 34 to check the information for the next second key input.

[0116] Another aspect of the present invention also provides a method for rapid real-time diagnosis of vehicle status via a control center, the method comprising:

[0117] Set the parameters and commands for the diagnostic instrument to work, parse and reassemble the command data, and then send the reassembled command data to the diagnostic instrument.

[0118] The system receives data sent by the diagnostic tool, parses the data to generate corresponding controls, including selecting the corresponding standard library data M2 based on the determined vehicle ECU model to correct the physical meaning of the parameters, resulting in the processed standard library data N2; simultaneously, it displays the processed standard library data N2; displays the real-time diagnostic data sent by the diagnostic tool; and stores the historical raw state data and historical diagnostic data sent by the diagnostic tool.

[0119] The parameter commands include setting the diagnostic cycle of the diagnostic instrument and turning off the LCD display of the diagnostic instrument.

[0120] It also includes storing the data in four parts: the first part stores the original standard library data M2 of the vehicle status and the processed standard library data N2; the second part stores the real-time diagnostic data sent by the diagnostic instrument; the third part stores the historical original status data sent by the diagnostic instrument; and the fourth part stores the historical diagnostic data sent by the diagnostic instrument.

[0121] The original standard library data M2 is retrieved and backed up from the diagnostic instrument during idle time, and the processed standard library data N2 is obtained by processing the original standard library data M2 using the same method as the diagnostic instrument.

[0122] Figure 4 This diagram illustrates the structure of a control center for a system for rapid real-time diagnostics of vehicle status, provided by an exemplary embodiment of the present invention. To adapt to different operating scenarios, the diagnostic tool is designed to operate independently of the control center or under its complete control. The control center comprises several modules, primarily including a communication connection module, a parameter setting module, a software storage module, a result visualization module, and a kernel analysis module.

[0123] Communication connection module: This module is used to establish a communication connection between the control center and the diagnostic instrument. Once established, the control center can send and receive data through this module.

[0124] Parameter setting module: This module is used to set the parameters for the operation of the diagnostic instrument. Once the settings are complete, the settings data is sent to the kernel analysis module.

[0125] Software storage module: This module is divided into four storage areas. One area stores the original standard library data M2 and the processed standard library data N2 of the vehicle status; one area stores the real-time diagnostic data sent by the diagnostic tool; one area stores the historical original status data sent by the diagnostic tool; and the last area stores the historical diagnostic data sent by the diagnostic tool. The standard library data M2 in the control center is a pre-backup of the standard library data M1, meaning they are identical. During initialization of the diagnostic tool and the control center, both process the standard library data M1 and M2 according to the same specific formula, ensuring that the processed standard library data N1 and N2 are also identical. This design reduces the amount of data transmission between the diagnostic tool and the control center.

[0126] Results visualization module: This module first receives data sent by the kernel analysis module. After receiving the data, it displays the processed standard library data N2 and real-time diagnostic data in a list format.

[0127] Kernel Analysis Module: This module is the core of the control center's control, decision-making, and analysis functions. Its main functions include: receiving command data from the parameter setting module, parsing and reassembling the command data, and then sending the reassembled command data to the diagnostic tool via the communication connection module; receiving data from the diagnostic tool via the communication connection module, parsing the data to generate corresponding controls, including selecting the corresponding standard library data M2 based on the determined vehicle ECU model, performing mathematical processing to obtain the processed standard library data N2, storing it in the software storage module, and simultaneously sending the processed standard library data N2 to the result visualization module for display; receiving real-time diagnostic data from the diagnostic tool and then sending the data to the result visualization module for display; and receiving historical raw state data and historical diagnostic data from the diagnostic tool and then forwarding the data to the software storage module for storage.

[0128] Figure 5 This diagram illustrates the workflow of a control center for a system providing rapid real-time diagnostics of vehicle status, according to an exemplary embodiment of the present invention. Once the control center is started, it proceeds according to... Figure 5 The control center operates according to the following workflow:

[0129] Step 1: Open the Control Center.

[0130] Step 2: Initialize the control center. Initialization includes setting initial values ​​for some variables and resetting the various functional modules in the control center.

[0131] Step 3: Determine if the control center has established a communication connection with the diagnostic instrument. The diagnostic instrument can operate independently of the control center or under its control. If a communication connection is established, the diagnostic instrument will perform diagnostics under the control of the control center, proceeding to Step 4. If no communication connection is established, the diagnostic instrument will operate independently, and the control center will remain in this state.

[0132] Step 4: Determine if the control center and diagnostic instrument have established a wired communication connection. The control center and diagnostic instrument can establish a communication connection via both wired and wireless methods, with wired connections having higher priority than wireless connections. If the control center and diagnostic instrument have established a wired communication connection, proceed to Step 5. Otherwise, proceed to Step 6.

[0133] Step 5: Assign the value 0 to the identifier "wireless". A value of 0 for "wireless" indicates that the control center and the diagnostic instrument have established a wired communication connection. After completing the assignment, proceed to step 11.

[0134] Step 6: Determine if the control center and the diagnostic tool have established a communication connection via Bluetooth. The control center typically sends command data to configure the diagnostic tool via Bluetooth and receives diagnostic data via Wi-Fi. If the control center and the diagnostic tool have not established a communication connection via Bluetooth, proceed to Step 7; otherwise, proceed to Step 8.

[0135] Step 7: Assign the value 0 to the identifier "bluetooth". Due to the short communication range of Bluetooth, there are situations where the control center and the diagnostic tool cannot establish a communication connection via Bluetooth. When a Bluetooth connection cannot be established, the control center will automatically establish a communication connection via Wi-Fi. A value of 0 for "bluetooth" indicates that the Bluetooth connection has failed. After completing the assignment, proceed to step 9.

[0136] Step 8: Assign the value 1 to the identifier "bluetooth". A value of 1 for "bluetooth" indicates that a communication connection has been successfully established via Bluetooth. After the assignment is complete, proceed to step 9.

[0137] Step 9: Determine if the control center and the diagnostic instrument have established a communication connection via Wi-Fi. If a Wi-Fi connection has been established, proceed to Step 10. If not, proceed to Step 23.

[0138] Step 10: Assign the value 1 to the identifier "wireless". A value of 1 for "wireless" indicates that the control center and the diagnostic instrument have successfully connected wirelessly. After the assignment is complete, proceed to step 11.

[0139] Step 11: Send parameter setting commands. The control center determines the communication connection status with the diagnostic instrument based on various identifiers, and then sends parameter commands to set the diagnostic instrument's operating parameters. These commands include setting the diagnostic cycle and turning off the LCD display, among other things. After the commands are sent, proceed to step 12.

[0140] Step 12: Send the start diagnostic command. The control center issues the start diagnostic command. After completing this step, proceed to step 13.

[0141] Step 13: Determine if the diagnostic tool can communicate with the vehicle's ECU. Different manufacturers and types of vehicles use different ECU models, which may cause the diagnostic tool's universal protocol to be unable to communicate with the vehicle's ECU. If neither the universal protocol nor the dedicated protocol can communicate with the vehicle's ECU, proceed to step 23; otherwise, proceed to step 14.

[0142] Step 14: Receive Vehicle Identification Code. When the diagnostic tool can communicate with the vehicle's ECU, it first needs to read the Vehicle Identification Code from the ECU. The Vehicle Identification Code contains the specific model number of the vehicle's ECU. After reading, the Vehicle Identification Code is uploaded to the control center. After completing this step, proceed to Step 15.

[0143] Step 15: Select the corresponding raw standard library data M2 from the software storage module. The software storage module stores different types of raw standard library data for vehicle status. When the control center receives the vehicle identification code, it selects the corresponding raw standard library data M2 based on this identification code. After selection, proceed to step 16.

[0144] Step 16: Perform mathematical processing to obtain the processed standard library data N2. Not all data in the standard library data M2 has a clearly defined physical meaning. To address this, mathematical processing is needed to obtain a clearer and more explicit standard library data N2. After obtaining the standard library data N2, proceed to step 18 to store the data in the software storage module, and simultaneously proceed to step 17.

[0145] Step 17: Receive periodic raw status data sent by the diagnostic tool. The diagnostic tool periodically reads the vehicle's ECU status data in real time at a set interval. After completing the reading, it uploads the data to the control center. Upon receiving the data, the control center proceeds to step 18 to store the data in the software storage module, and simultaneously proceeds to step 19.

[0146] Step 18: Store in the software storage module. This step involves storing the obtained data, including standard library data N2, the original status data of the vehicle ECU, and the diagnostic data of the vehicle ECU, into the software storage module.

[0147] Step 19: Perform mathematical processing to obtain diagnostic data. Some of the raw state data obtained from the vehicle's ECU has unclear physical meaning, so mathematical processing is required to obtain diagnostic data with clear physical meaning. After completing the mathematical processing, proceed to step 18 to store the data in the software storage module, and then proceed to step 20.

[0148] Step 20: Display standard library data N2 and real-time diagnostic data. After obtaining the diagnostic data, the control center displays the standard library data N2 and real-time diagnostic data on the results visualization module. After completing this step, proceed to step 21.

[0149] Step 26: Determine if the diagnostic instrument is in data transmission mode. If the diagnostic instrument is in data transmission mode, proceed to step 22; otherwise, proceed to step 17 to wait for the reception of raw status data for the next cycle.

[0150] Step 22: Receive historical raw status data and historical diagnostic data. When the diagnostic instrument is in data transmission mode, it will transmit this information to the control center. After receiving this information, the control center will simultaneously proceed to step 18 to store the received data in the software storage module and step 21 to monitor the current mode of the diagnostic instrument.

[0151] Step 23, Return. This return does not mean returning to the starting state, but rather returning to step 3, which means re-checking whether a communication connection has been established with the diagnostic instrument.

Claims

1. A method for rapid real-time diagnosis of vehicle status, characterized in that: The method includes: Obtain the ECU model of the vehicle being diagnosed using a diagnostic tool; Select the corresponding original standard library data for vehicle status based on the vehicle ECU model; The original standard library data of the corresponding vehicle status is processed, and the parameters with unclear parameters are redefined. The processed standard library data is then stored in the Flash memory and displayed on the LCD screen in the form of a list. The system periodically reads the vehicle's original state data from the vehicle's ECU storage unit in real time and stores the read real-time original state data in the Flash memory. Select the corresponding standard library data after processing the vehicle status according to the vehicle ECU model, process the real-time raw status data and the processed standard library data to obtain real-time diagnostic data, store the real-time diagnostic data in the Flash memory, and display it on the LCD screen in the form of a list. Set the parameters and commands for the diagnostic instrument to work, parse and reassemble the command data, and then send the reassembled command data to the diagnostic instrument. The system receives data sent by the diagnostic tool, parses the data to generate corresponding controls, including selecting the corresponding standard library data M2 based on the determined vehicle ECU model to correct the physical meaning of the parameters, resulting in the processed standard library data N2; simultaneously, it displays the processed standard library data N2; displays the real-time diagnostic data sent by the diagnostic tool; and stores the historical raw state data and historical diagnostic data sent by the diagnostic tool.

2. The method for rapid real-time diagnosis of vehicle status according to claim 1, characterized in that: Two data communication buses are set up. One uses a general protocol to establish communication connections with many automotive ECUs on the market; the other is set up as a function-specific bus to establish communication connections with niche automotive ECUs on the market. Before obtaining the ECU model of the vehicle being diagnosed using a diagnostic tool, it is necessary to determine whether the general protocol can communicate with the vehicle ECU. If the general protocol of the diagnostic tool cannot communicate with the vehicle ECU, it is necessary to test whether the dedicated protocol can communicate. Once communication is established using any one of the communication methods, the vehicle identification code is read from the ECU.

3. The method for rapid real-time diagnosis of vehicle status according to claim 1, characterized in that: Real-time raw status data includes two types: operational data and static data. Operational data is the monitoring data collected by the vehicle's ECU through various sensors, including power supply voltage regulation data, fuel injection quantity data, DPF regeneration status data, SCR injection status data, EGR data, TVA data, vehicle speed data, and throttle angle data. Static data is constant data stored in the vehicle's ECU, including the vehicle identification code. Operational data is used for mathematical processing to diagnose the vehicle's status. The Flash memory stores raw standard library data of vehicle status from different manufacturers. Static data is used to identify the vehicle's ECU model, thereby selecting the corresponding raw standard library data of vehicle status to assist in mathematical processing.

4. The method for rapid real-time diagnosis of vehicle status according to claim 1, characterized in that: The real-time diagnostic data obtained through mathematical processing includes: The diagnostic value is obtained by directly subtracting the real-time raw status data from the processed standard library data; Obtain basic values ​​A1 and B1 from the processed standard library data, and basic values ​​A2 and B2 from the real-time raw state data. Obtain the standard integrated value and the raw integrated value according to the formula A*B. Subtract the standard integrated value from the raw integrated value to obtain the diagnostic value. The basic values ​​A1 and B1 are obtained from the processed standard library data, and the basic values ​​A2 and B2 are obtained from the real-time raw state data. The standard integrated value and the raw integrated value are obtained according to the formula A±B. The diagnostic value is obtained by subtracting the standard integrated value from the raw integrated value. Obtain the gain value a1, the basic value A, and the offset value B from the processed standard library data. Obtain the gain value a2 from the original state data. Obtain the standard integrated value and the original integrated value according to the formula a*A±B. Subtract the standard integrated value from the original integrated value to obtain the diagnostic value.

5. The method for rapid real-time diagnosis of vehicle status according to claim 1, characterized in that, Also includes: Determine whether the diagnostic instrument interacts with the remote control center via wired or wireless means. If not, the diagnostic instrument independently diagnoses and displays the data. If it does, it receives parameter settings from the control center, sends historical raw status data and diagnostic data to the control center, and then displays and stores the data through the control center after turning off its own display.

6. The method for rapid real-time diagnosis of vehicle status according to claim 5, characterized in that, It also includes multiple modes that can be switched, and the multiple modes include: In pause mode, the LCD display keeps showing the current data and only pauses the display of updated diagnostic data; Data transmission mode: Determine whether a communication connection has been established with the control center. If a communication connection is established, stop the diagnostics and send historical raw status data and historical diagnostic data to the control center in two data packets in sequence; otherwise, do not send data and prompt the user to establish a communication connection. Normal working mode: Stop the current pause mode or data transmission mode and return to normal periodic diagnostics; Enter screen-off or on-screen mode: If the LCD display is already on, turn off the LCD display; if the LCD display is already off, turn on the LCD display.

7. A method for rapid real-time diagnosis of vehicle status according to claim 1, characterized in that, The parameter commands include setting the diagnostic cycle of the diagnostic instrument and turning off the LCD display of the diagnostic instrument.

8. A method for rapid real-time diagnosis of vehicle status according to claim 7, characterized in that, It also includes storing the data in four parts: the first part stores the original standard library data M2 of the vehicle status and the processed standard library data N2; the second part stores the real-time diagnostic data sent by the diagnostic instrument; the third part stores the historical original status data sent by the diagnostic instrument; and the fourth part stores the historical diagnostic data sent by the diagnostic instrument.

9. A method for rapid real-time diagnosis of vehicle status according to claim 8, characterized in that, The original standard library data M2 is obtained and backed up from the diagnostic instrument during idle time, and the processed standard library data N2 is obtained by processing the original standard library data M2 using the same method as the diagnostic instrument.

Images