Vehicle fault determination systems, methods, apparatus, and storage media

Abstract

This application discloses a vehicle fault determination system, method, device, and storage medium, belonging to the field of vehicle technology. In this system, a diagnostic device first determines the target controller based on multiple fault codes, then sends an acquisition request to the target controller. The target controller acquires signal values ​​from multiple functional modules within multiple cycles, generates a first data stream based on the signal values ​​of the multiple functional modules within each cycle, and sends the first data stream corresponding to the multiple cycles to the diagnostic device. The diagnostic device generates a second data stream based on the first data stream corresponding to the multiple cycles and sends the second data stream to the terminal. The terminal processes the second data stream using a processing script to obtain a first file, and determines the cause of the fault based on the first file. Therefore, when multiple fault codes occur, this system can directly acquire the signal values ​​of multiple functional modules corresponding to the target controller at once, eliminating the need for multiple acquisitions, saving time, and thus improving the efficiency of determining the cause of the fault.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a vehicle fault determination system, method, device and storage medium. Background Technology

[0002] Vehicles inevitably experience malfunctions during operation. When a vehicle malfunctions, it is necessary to first determine the cause of the malfunction, and then repair the vehicle accordingly.

[0003] The process for determining the cause of a fault in related technologies is as follows: first, determine the fault code; then, determine at least one faulty module in the controller based on the fault code; finally, read the signal value of each faulty module; and finally, determine the cause of the fault based on the read signal value.

[0004] However, when there are multiple fault codes, it is necessary to read the signal values ​​of the faulty module multiple times, which takes a long time and results in low efficiency in determining the cause of the fault. Summary of the Invention

[0005] This application provides a vehicle fault determination system, method, device, and storage medium, which can improve the efficiency of determining the cause of a fault. The technical solution is as follows:

[0006] On the one hand, a vehicle fault determination system is provided, the system comprising: a diagnostic device, a target controller, and a terminal, wherein the terminal and the target controller are both electrically connected to the diagnostic device;

[0007] The diagnostic device is used to acquire multiple fault codes, determine a target controller based on the multiple fault codes, and send an acquisition request to the target controller.

[0008] The target controller is configured to acquire signal values ​​of multiple functional modules within multiple cycles based on the acquisition request; generate a first data stream based on the signal values ​​of the multiple functional modules within each cycle; and send the first data stream corresponding to the multiple cycles to the diagnostic device, wherein the multiple functional modules are multiple modules corresponding to the target controller.

[0009] The diagnostic device is further configured to generate a second data stream based on the first data stream corresponding to the plurality of cycles, and send the second data stream to the terminal;

[0010] The terminal is used to process the second data stream through a first processing script to obtain a first file corresponding to the plurality of functional modules; and to determine the cause of the fault based on the first file corresponding to the plurality of functional modules.

[0011] In one possible implementation, the target controller is configured to, for any given period, based on the acquisition request, acquire the signal values ​​of the plurality of functional modules within the period according to the signal order of the plurality of functional modules in a pre-stored signal list; and assemble the signal values ​​of the plurality of functional modules within the period into the first data stream.

[0012] In another possible implementation, the terminal is further configured to acquire the first processing script, run the first processing script, wherein the first processing script is configured to write the signal values ​​of the multiple functional modules within the multiple cycles in the second data stream into a table based on the pre-stored signal order of the multiple functional modules, thereby obtaining a first table; and convert the first table into a file of a preset format, thereby obtaining the first file.

[0013] In another possible implementation, the terminal is further configured to display a change view corresponding to the plurality of functional modules based on the first file, the change view being used to represent the change of the signal value of the functional module over time;

[0014] Based on the change views corresponding to the multiple functional modules, at least one faulty module is identified from the multiple functional modules;

[0015] Based on the at least one faulty module, the cause of the fault is determined.

[0016] In another possible implementation, the terminal is further configured to open the first file via an analysis tool, display a variable selection interface, the variable selection interface including multiple variable selection options, each variable selection option corresponding to a functional module; and in response to a trigger operation on the multiple variable selection options, display a change view corresponding to the multiple functional modules.

[0017] In another possible implementation, the diagnostic device is further configured to combine the first data streams corresponding to the plurality of cycles into a second data stream in chronological order.

[0018] On the other hand, a vehicle fault determination method is provided, the method comprising:

[0019] The diagnostic equipment acquires multiple fault codes, determines the target controller based on the multiple fault codes, and sends an acquisition request to the target controller;

[0020] The target controller acquires signal values ​​of multiple functional modules within multiple cycles based on the acquisition request; generates a first data stream based on the signal values ​​of the multiple functional modules within each cycle; and sends the first data stream corresponding to the multiple cycles to the diagnostic device, wherein the multiple functional modules are multiple modules corresponding to the target controller.

[0021] The diagnostic device generates a second data stream based on the first data stream corresponding to the multiple cycles, and sends the second data stream to the terminal;

[0022] The terminal processes the second data stream using a first processing script to obtain a first file corresponding to the plurality of functional modules;

[0023] The terminal determines the cause of the fault based on the first file corresponding to the multiple functional modules.

[0024] In one possible implementation, the target controller generates a first data stream based on the signal values ​​of the plurality of functional modules in each cycle, including:

[0025] For any given period, the target controller, based on the acquisition request, acquires the signal values ​​of the multiple functional modules within the period according to the signal order of the multiple functional modules in the pre-stored signal list; and assembles the signal values ​​of the multiple functional modules within the period into the first data stream.

[0026] In another possible implementation, the terminal processes the second data stream using a first processing script to obtain a first file corresponding to the plurality of functional modules, including:

[0027] The terminal obtains the first processing script and runs the first processing script. The first processing script is used to write the signal values ​​of the multiple functional modules in the multiple cycles of the second data stream into a table based on the pre-stored signal order of the multiple functional modules to obtain a first table; and convert the first table into a file of a preset format to obtain the first file.

[0028] In another possible implementation, the terminal determines the cause of the fault based on a first file corresponding to the plurality of functional modules, including:

[0029] Based on the first file, the terminal displays a change view corresponding to the plurality of functional modules, and the change view is used to represent the change of the signal value of the functional module over time.

[0030] Based on the change views corresponding to the multiple functional modules, at least one faulty module is identified from the multiple functional modules;

[0031] Based on the at least one faulty module, the cause of the fault is determined.

[0032] In another possible implementation, the terminal displays a changed view corresponding to the plurality of functional modules based on the first file, including:

[0033] The terminal opens the first file through the analysis tool and displays a variable selection interface. The variable selection interface includes multiple variable selection options, and each variable selection option corresponds to a functional module. In response to the triggering operation of the multiple variable selection options, the change view corresponding to the multiple functional modules is displayed.

[0034] In another possible implementation, the diagnostic device generates a second data stream based on the first data stream corresponding to the plurality of cycles, and sends the second data stream to the terminal, including:

[0035] The diagnostic device combines the first data streams corresponding to the multiple cycles into a second data stream in chronological order.

[0036] On the other hand, an electronic device is provided, comprising a processor and a memory, wherein the memory stores at least one piece of program code, which is loaded and executed by the processor to implement the vehicle fault determination method described in any of the diagnostic devices, target controllers, or terminals described above.

[0037] On the other hand, a computer-readable storage medium is provided, wherein at least one piece of program code is stored in the computer-readable storage medium, the at least one piece of program code being loaded and executed by a processor to implement the vehicle fault determination method described in any of the preceding claims.

[0038] On the other hand, a computer program product is provided, wherein at least one piece of program code is stored in the computer program product, the at least one piece of program code being loaded and executed by a processor to implement the vehicle fault determination method described in any of the above claims.

[0039] This application provides a vehicle fault determination system. In this system, a diagnostic device first identifies a target controller based on multiple fault codes, then sends an acquisition request to the target controller. Based on the acquisition request, the target controller acquires signal values ​​from multiple functional modules within multiple cycles. Based on the signal values ​​of the multiple functional modules within each cycle, it generates a first data stream and sends the first data stream corresponding to the multiple cycles to the diagnostic device. The diagnostic device generates a second data stream based on the first data stream corresponding to the multiple cycles and sends the second data stream to a terminal. The terminal processes the second data stream using a processing script to obtain a first file, and based on the first file, determines the cause of the fault. Therefore, when multiple fault codes occur, this system can directly acquire the signal values ​​of multiple functional modules corresponding to the target controller at once, eliminating the need for multiple acquisitions, saving time, and thus improving the efficiency of determining the cause of the fault.

[0040] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this disclosure. Attached Figure Description

[0041] Figure 1 This is a schematic diagram of a vehicle fault determination system provided in an embodiment of this application;

[0042] Figure 2 This is a flowchart of a vehicle fault determination method provided in an embodiment of this application;

[0043] Figure 3 This is a schematic diagram illustrating how to determine the cause of a vehicle malfunction, provided in an embodiment of this application.

[0044] Figure 4 This is a structural block diagram of a terminal provided in an embodiment of this application;

[0045] Figure 5 This is a structural block diagram of a diagnostic device provided in an embodiment of this application. Detailed Implementation

[0046] To make the technical solution and advantages of this application clearer, the embodiments of this application will be described in further detail below.

[0047] The terms "first," "second," "third," and "fourth," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0048] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the signal values ​​and fault codes involved in this application were obtained with full authorization.

[0049] Figure 1 This is a schematic diagram of a vehicle fault determination system provided in an embodiment of this application. See also... Figure 1 The system includes: a diagnostic device 10, a target controller 11, and a terminal 12, both of which are electrically connected to the diagnostic device 10;

[0050] Diagnostic device 10 is used to acquire multiple fault codes, determine the target controller 11 based on the multiple fault codes, and send an acquisition request to the target controller 11.

[0051] The target controller 11 is used to acquire signal values ​​of multiple functional modules within multiple cycles based on an acquisition request; generate a first data stream based on the signal values ​​of multiple functional modules within each cycle; and send the first data stream corresponding to multiple cycles to the diagnostic device 10, wherein the multiple functional modules are multiple modules corresponding to the target controller 11.

[0052] The diagnostic device 10 is also used to generate a second data stream based on the first data stream corresponding to multiple cycles, and send the second data stream to the terminal 12;

[0053] Terminal 12 is used to process the second data stream through a first processing script to obtain a first file corresponding to multiple functional modules; and to determine the cause of the fault based on the first file corresponding to multiple functional modules.

[0054] In this embodiment, the diagnostic device 10 can be a vehicle diagnostic tool, which is a specialized instrument for vehicle testing and a tool for detecting vehicle faults. The target controller 11 can be any controller in the vehicle, such as a TCU (Transmission Control Unit), ECU (Engine Control Unit), or other control unit, without specific limitation. The terminal 12 can be at least one of the following devices: smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, smart voice interaction device, smart home appliance, in-vehicle terminal 12, etc., but is not limited thereto.

[0055] The electrical connection can be a circuit connection or a wireless connection, and there is no specific limitation on the latter. If the electrical connection is a circuit connection, the connection method can be a cable connection; if the electrical connection is a wireless connection, the connection method can be an infrared connection, a wireless local area network (WLAN), or a WiFi (Wireless Fidelity) network connection. In the embodiments of this application, there is no specific limitation on the latter. In addition, the vehicle can be a fuel-powered vehicle, an electric vehicle, or a hybrid vehicle, and there is no specific limitation on the latter.

[0056] In one possible implementation, the target controller 11 is configured to, for any given period, acquire the signal values ​​of multiple functional modules within the period based on an acquisition request and in accordance with the signal order of multiple functional modules in a pre-stored signal list; and to assemble the signal values ​​of the multiple functional modules within the period into a first data stream.

[0057] In another possible implementation, terminal 12 is also used to acquire a first processing script, run the first processing script, and the first processing script is used to write the signal values ​​of multiple functional modules in multiple cycles of the second data stream into a table based on the signal order of multiple pre-stored functional modules to obtain a first table; and convert the first table into a file of a preset format to obtain a first file.

[0058] In another possible implementation, terminal 12 is also used to display a change view corresponding to multiple functional modules based on the first file. The change view is used to represent the change of signal values ​​of functional modules over time.

[0059] Based on the change views corresponding to multiple functional modules, at least one faulty module is identified from the multiple functional modules;

[0060] Determine the cause of the failure based on at least one faulty module.

[0061] In another possible implementation, terminal 12 is also used to open the first file through the analysis tool, display a variable selection interface, which includes multiple variable selection options, one variable selection option corresponding to one functional module; in response to the triggering operation of multiple variable selection options, display the change view corresponding to multiple functional modules.

[0062] In another possible implementation, the diagnostic device 10 is also used to combine the first data streams corresponding to multiple cycles into a second data stream in chronological order.

[0063] This application provides a vehicle fault determination system. In this system, a diagnostic device first identifies a target controller based on multiple fault codes, then sends an acquisition request to the target controller. Based on the acquisition request, the target controller acquires signal values ​​from multiple functional modules within multiple cycles. Based on the signal values ​​of the multiple functional modules within each cycle, it generates a first data stream and sends the first data stream corresponding to the multiple cycles to the diagnostic device. The diagnostic device generates a second data stream based on the first data stream corresponding to the multiple cycles and sends the second data stream to a terminal. The terminal processes the second data stream using a processing script to obtain a first file, and based on the first file, determines the cause of the fault. Therefore, when multiple fault codes occur, this system can directly acquire the signal values ​​of multiple functional modules corresponding to the target controller at once, eliminating the need for multiple acquisitions, saving time, and thus improving the efficiency of determining the cause of the fault.

[0064] Figure 2 This is a flowchart of a vehicle fault determination method provided in an embodiment of this application. See also... Figure 2 The method includes:

[0065] Step 201: The diagnostic device acquires multiple fault codes, determines the target controller based on the multiple fault codes, and sends an acquisition request to the target controller.

[0066] When a vehicle malfunctions, the technician connects diagnostic equipment to the vehicle. The equipment reads the vehicle's fault codes, obtaining multiple codes. Different fault codes correspond to different controllers. Based on the correspondence between fault codes and controllers, the diagnostic equipment can determine the target controller to which multiple fault codes belong.

[0067] Multiple fault codes can correspond to the same controller or different controllers. That is, the target controller can be a single controller, such as a TCU, ECU, or other control unit, or multiple controllers, such as a TCU and an ECU. There is no specific limitation on this.

[0068] It should be noted that when there is only one fault code, the diagnostic device can also determine the cause of the fault using the method provided in this application. Accordingly, step 201 is: the diagnostic device obtains the fault code and determines the target controller based on the fault code.

[0069] After identifying the target controller, the diagnostic device sends an acquisition request to the target controller.

[0070] The diagnostic device and the target controller communicate and interact based on the UDS (Unified Diagnostic Services) diagnostic protocol. The diagnostic device is equipped with a start option. In response to the triggering operation of the start option, the diagnostic device sends an acquisition request to the target controller based on the UDS diagnostic protocol to request the acquisition of the DID (Data Identifier) ​​of multiple functional modules corresponding to the target controller.

[0071] The target controller comprises several functional modules, which are the drive units controlled by it. For example, a drive unit might be a solenoid valve. The start option can be either a virtual button or a physical button.

[0072] Step 202: The target controller acquires the signal values ​​of multiple functional modules within multiple cycles based on the acquisition request; generates a first data stream based on the signal values ​​of multiple functional modules within each cycle; and sends the first data stream corresponding to the multiple cycles to the diagnostic device.

[0073] In one possible implementation, for any given period, the target controller, based on an acquisition request, acquires the signal values ​​of multiple functional modules within that period according to the signal order of multiple functional modules in a pre-stored signal list, and then assembles the signal values ​​of the multiple functional modules within that period into a first data stream.

[0074] In this implementation, for any given cycle, the target controller directly acquires the signal values ​​of multiple functional modules according to their signal sequence, and then assembles them into the first data stream.

[0075] In this embodiment, the target controller acquires signal values ​​corresponding to multiple functional modules within a cycle, forms a first data stream, and then sends the first data stream corresponding to that cycle to the diagnostic device. The diagnostic device is also equipped with a stop option. When the first data streams corresponding to multiple cycles meet the fault analysis requirements, the maintenance personnel can trigger the stop option. Correspondingly, in response to the triggering operation of the stop option, the diagnostic device disconnects from the target controller, thereby the target controller stops sending the first data stream to the diagnostic device.

[0076] It should be noted that before step 202, the target controller first determines the signal order of multiple functional modules, that is, the arrangement order of the signals of multiple functional modules, and then generates a signal list. The signal list may also include the attributes of the signals of multiple functional modules, such as the unit of the signal, data format, data type, data length, offset (correction value), etc.

[0077] In this embodiment, developers can ensure that the customized UDS service development complies with the vehicle's diagnostic service specifications (enterprise standards and national standards) and communicate with the company's internal network diagnostic developers. Then, they add the customized UDS service and content to the target controller, creating a table that lists the signals from multiple functional modules controlled by the target controller, including the attributes and order of each signal. The code is then entered into the target controller's UDS service according to the signal order. Finally, the software is integrated to obtain software with the customized UDS service. This way, when a vehicle malfunctions, the target controller can directly obtain the signal values ​​of all corresponding functional modules at once, eliminating the need for multiple acquisitions and improving efficiency.

[0078] Step 203: The diagnostic device generates a second data stream based on the first data stream corresponding to multiple cycles and sends the second data stream to the terminal.

[0079] After acquiring the first data stream corresponding to multiple cycles, the diagnostic device combines the first data streams corresponding to multiple cycles into a second data stream according to the time sequence and sends the second data stream to the terminal.

[0080] The format of the second data stream can be set and changed as needed; for example, the second data stream can be in txt format.

[0081] Step 204: The terminal processes the second data stream through the first processing script to obtain the first file corresponding to multiple functional modules.

[0082] In this step, the terminal receives the second data stream sent by the diagnostic device, obtains the first processing script, and then runs the first processing script. The first processing script writes the signal values ​​of multiple functional modules in multiple cycles in the second data stream into a table based on the signal order of multiple pre-stored functional modules to obtain the first table. The first table is then converted into a file in a preset format to obtain the first file.

[0083] In this implementation, the first processing script first writes the signal values ​​of multiple functional modules into a table in chronological order according to the signal sequence of the multiple functional modules, thus obtaining the first table.

[0084] In this embodiment, the first processing script pre-stores the signal order of multiple functional modules. This signal order is written by the developer when writing the first processing script. The table format can be set and changed as needed. For example, the table includes the names of multiple functional modules, signal attributes, corresponding positions of signal values, and a timeline. The names of multiple functional modules are in one row, the signal values ​​and signal attributes of multiple functional modules read at the same time are in one row, and the signal values ​​and signal attributes of the same functional module read at different times are in one row, corresponding to the functional modules. Alternatively, the names of multiple functional modules are in one column, the signal values ​​and signal attributes of multiple functional modules read at the same time are in one column, and the signal values ​​and signal attributes of the same functional module read at different times are in one column, corresponding to the functional modules.

[0085] Before writing signal values ​​for multiple functional modules, the corresponding positions in the table can be either blank or non-blank. If blank, the first processing script directly writes the read signal value. If non-blank, the signal value at the corresponding position in the table is the initial signal value, and the first processing script replaces the initial signal value with the read signal value. The initial signal value can be 0 or any other value; there are no specific limitations on this.

[0086] In this embodiment, the function of the first processing script is to split the first data stream corresponding to each cycle in the second data stream and fill it into a table. The terminal writes the signal values ​​of multiple functional modules into the table through the first processing script, and can obtain the signal values ​​of each functional module at different times, which is convenient for subsequent display through a visual view.

[0087] After the terminal obtains the first table, it puts the first table into the project environment where the first processing script is located, and then converts the first table into a file with a preset format through the project environment.

[0088] The default format is a format readable by the analysis tool. For example, if the analysis tool is INCA (a calibration software) MDA (Measure Data Analyzer), the default format is ASCII (American Standard Code for Information Interchange).

[0089] The first processing script can be a Python (a programming language) script or other scripts. In this embodiment, only a Python script is used as an example for illustration.

[0090] Step 205: The terminal determines the cause of the fault based on the first file corresponding to multiple functional modules.

[0091] This step can be achieved through the following steps (1) to (3), including:

[0092] (1) The terminal displays a change view corresponding to multiple functional modules based on the first file.

[0093] This change view is used to show how the signal values ​​of a functional module change over time.

[0094] In one possible implementation, the terminal opens the first file through an analysis tool and displays a variable selection interface, which includes multiple variable selection options, with each variable selection option corresponding to a functional module; in response to the triggering operation of the multiple variable selection options, a change view corresponding to the multiple functional modules is displayed.

[0095] In this implementation, an analysis tool runs on the terminal. In response to a file open operation, the analysis tool opens the first file and then displays a variable selection interface. The variable selection interface includes multiple variable selection options, each corresponding to a functional module. In response to triggering multiple variable selection options, the terminal directly displays the change view corresponding to the multiple functional modules based on the signal values ​​of the multiple functional modules in the first file.

[0096] In this embodiment, maintenance personnel can also selectively view the change views corresponding to certain functional modules. Accordingly, in response to a trigger operation on one or more variable selection options, the terminal displays the change views corresponding to one or more functional modules based on the signal values ​​of the functional modules corresponding to the selected variable selection options.

[0097] In the embodiments of this application, for each functional module, the change view of the functional module can be set and changed as needed. For example, the change view of the functional module can be a line chart, bar chart, scatter plot or other visualization chart, and there is no specific limitation on this.

[0098] (2) The terminal determines at least one faulty module from the multiple functional modules based on the change view corresponding to the multiple functional modules.

[0099] For each functional module, the terminal determines whether the signal value and its changes for that functional module are within a preset range based on the corresponding change view. If they are not within the preset range, the functional module is determined to be a faulty module. The terminal identifies at least one faulty module from multiple functional modules using the above method.

[0100] In this embodiment, through a customized UDS service, the target controller can directly read the signal values ​​of all functional modules and then send them to the diagnostic device, which forwards them to the terminal. The terminal uses a processing script to convert the read data stream into a format readable by the analysis tool, and then uses the analysis tool to visualize the collected signals, thereby helping to shorten the time for determining the cause of the fault and improve efficiency.

[0101] (3) The terminal determines the cause of the fault based on at least one faulty module.

[0102] The terminal can highlight at least one faulty module on the display screen, identifying the faulty module as the cause of the fault. This allows maintenance personnel to perform targeted repairs on the faulty module and resolve the problem.

[0103] The terminal can determine maintenance guidance information based on the cause of the fault, and generate a solution report based on the maintenance guidance information. This allows maintenance personnel to refer to the maintenance guidance information in the solution report to repair at least one faulty module.

[0104] See Figure 3 The target controller and diagnostic device are connected via a diagnostic port. The diagnostic device is connected to a terminal. The diagnostic device acquires data streams by interacting with the target controller and then sends them to the terminal. The terminal processes the data streams using a Python script to obtain ASCII format files. Finally, it opens the files using an MDA tool to analyze the data and identify the cause of the fault. Figure 3 The multiple sensors and actuators in the system are all drive units, or functional modules, corresponding to the target controller. A customized UDS service is added to the target controller to acquire signal values ​​from multiple functional modules. Furthermore, the vehicle contains multiple controllers, and their normal operation requires their coordinated operation. Therefore, the target controller may interact with other controllers, acquiring their input signals, while also needing to output control signals itself.

[0105] In summary, the method provided in this application can not only quickly read the signals of electrical components in each module, but also convert these signals into visual charts, making it easier for maintenance personnel to compare data more clearly and intuitively. This reduces complex reading operations in after-sales service, allows for better and faster location of the root cause of the problem, and thus quickly resolves the fault and improves the efficiency of after-sales service.

[0106] This application provides a method for determining vehicle faults. In this method, a diagnostic device first identifies a target controller based on multiple fault codes, then sends an acquisition request to the target controller. Based on the acquisition request, the target controller acquires signal values ​​from multiple functional modules within multiple cycles. Based on the signal values ​​of the multiple functional modules within each cycle, it generates a first data stream and sends the first data stream corresponding to the multiple cycles to the diagnostic device. The diagnostic device generates a second data stream based on the first data stream corresponding to the multiple cycles and sends the second data stream to a terminal. The terminal processes the second data stream using a processing script to obtain a first file, and based on the first file, determines the cause of the fault. Therefore, when multiple fault codes occur, this system can directly acquire the signal values ​​of multiple functional modules corresponding to the target controller at once, eliminating the need for multiple acquisitions, saving time, and thus improving the efficiency of determining the cause of the fault.

[0107] refer to Figure 4 , Figure 4 This illustration shows a structural block diagram of a terminal 400 provided in an exemplary embodiment of this application. The terminal 400 can be a portable mobile terminal, such as a smartphone, tablet computer, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), laptop computer, or desktop computer. The terminal 400 may also be referred to as a user device, portable terminal, laptop terminal, desktop terminal, or other names.

[0108] Typically, terminal 400 includes a processor 401 and a memory 402.

[0109] Processor 401 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 401 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 401 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 401 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 401 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0110] The memory 402 may include one or more computer-readable storage media, which may be non-transitory. The memory 402 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 402 are used to store at least one piece of program code, which is executed by the processor 401 to implement the operations performed by the terminal in the vehicle fault determination method provided in the method embodiments of this application.

[0111] In some embodiments, the terminal 400 may also optionally include a peripheral device interface 403 and at least one peripheral device. The processor 401, memory 402, and peripheral device interface 403 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 403 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 404, a display screen 405, a camera assembly 406, an audio circuit 407, and a power supply 408.

[0112] Peripheral device interface 403 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 401 and memory 402. In some embodiments, processor 401, memory 402 and peripheral device interface 403 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 401, memory 402 and peripheral device interface 403 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0113] The radio frequency (RF) circuit 404 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 404 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 404 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 404 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 404 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 404 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0114] Display screen 405 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 405 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 401 for processing. In this case, display screen 405 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 405, disposed on the front panel of terminal 400; in other embodiments, there may be at least two display screens, disposed on different surfaces of terminal 400 or in a folded design; in other embodiments, display screen 405 may be a flexible display screen, disposed on a curved or folded surface of terminal 400. Furthermore, display screen 405 may be configured as a non-rectangular irregular shape, i.e., a non-rectangular screen. Display screen 405 may be made of materials such as LCD (Liquid Crystal Display) or OLED (Organic Light-Emitting Diode).

[0115] The camera assembly 406 is used to acquire images or videos. Optionally, the camera assembly 406 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 406 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cool light flash, which can be used for light compensation at different color temperatures.

[0116] The audio circuit 407 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting them into electrical signals that are input to the processor 401 for processing, or to the radio frequency circuit 404 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each positioned at a different location on the terminal 400. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 401 or the radio frequency circuit 404 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 407 may also include a headphone jack.

[0117] Power supply 408 is used to power the various components in terminal 400. Power supply 408 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 408 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, while a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0118] In some embodiments, the terminal 400 further includes one or more sensors 409. The one or more sensors 409 include, but are not limited to: an accelerometer 410, a gyroscope 411, a pressure sensor 412, an optical sensor 413, and a proximity sensor 414.

[0119] Accelerometer 410 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established with terminal 400. For example, accelerometer 410 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 401 can control display screen 405 to display the user interface in either a landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 410. Accelerometer 410 can also be used for games or for acquiring user motion data.

[0120] The gyroscope sensor 411 can detect the orientation and rotation angle of the terminal 400. The gyroscope sensor 411 can work in conjunction with the accelerometer sensor 410 to collect 3D motion data from the user on the terminal 400. Based on the data collected by the gyroscope sensor 411, the processor 401 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0121] The pressure sensor 412 can be disposed on the side bezel of the terminal 400 and / or on the lower layer of the display screen 405. When the pressure sensor 412 is disposed on the side bezel of the terminal 400, it can detect the user's grip signal on the terminal 400, and the processor 401 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 412. When the pressure sensor 412 is disposed on the lower layer of the display screen 405, the processor 401 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 405. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0122] Optical sensor 413 is used to collect ambient light intensity. In one embodiment, processor 401 can control the display brightness of display screen 405 based on the ambient light intensity collected by optical sensor 413. Specifically, when the ambient light intensity is high, the display brightness of display screen 405 is increased; when the ambient light intensity is low, the display brightness of display screen 405 is decreased. In another embodiment, processor 401 can also dynamically adjust the shooting parameters of camera assembly 406 based on the ambient light intensity collected by optical sensor 413.

[0123] The proximity sensor 414, also known as a distance sensor, is typically located on the front panel of the terminal 400. The proximity sensor 414 is used to detect the distance between the user and the front of the terminal 400. In one embodiment, when the proximity sensor 414 detects that the distance between the user and the front of the terminal 400 is gradually decreasing, the processor 401 controls the display screen 405 to switch from a screen-on state to a screen-off state; when the proximity sensor 414 detects that the distance between the user and the front of the terminal 400 is gradually increasing, the processor 401 controls the display screen 405 to switch from a screen-off state to a screen-on state.

[0124] Those skilled in the art will understand that Figure 4 The structure shown does not constitute a limitation on terminal 400 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0125] The structural block diagram of the diagnostic equipment can be found in [reference needed]. Figure 5The diagnostic device 500 can vary considerably depending on its configuration or performance. It may include a Central Processing Unit (CPU) 501 and a memory 502. The memory 502 stores at least one line of program code, which is loaded and executed by the processor 501 to perform the operations performed by the diagnostic device in the aforementioned vehicle fault determination method. Of course, the diagnostic device 500 may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The diagnostic device 500 may also include other components for implementing its functions, which will not be elaborated upon here.

[0126] The block diagram of the target controller can also be found in [reference needed]. Figure 5 This will not be elaborated upon here.

[0127] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores at least one piece of program code that is loaded and executed by a processor to implement the vehicle fault determination method in the above embodiments.

[0128] In an exemplary embodiment, a computer program product is also provided, which stores at least one piece of program code that is loaded and executed by a processor to implement the vehicle fault determination method in the above embodiments.

[0129] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0130] The above description is only for the purpose of enabling those skilled in the art to understand the technical solution of this application, and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A vehicle fault determination system, characterized in that, The system includes: a diagnostic device, a target controller, and a terminal, wherein the terminal and the target controller are both electrically connected to the diagnostic device; The diagnostic device is used to acquire multiple fault codes, determine a target controller based on the multiple fault codes, and send an acquisition request to the target controller. The target controller is configured to acquire signal values ​​of multiple functional modules within multiple cycles based on the acquisition request; generate a first data stream based on the signal values ​​of the multiple functional modules within each cycle; and send the first data stream corresponding to the multiple cycles to the diagnostic device, wherein the multiple functional modules are multiple modules corresponding to the target controller. The diagnostic device is further configured to generate a second data stream based on the first data stream corresponding to the plurality of cycles, and send the second data stream to the terminal; The terminal is used to process the second data stream through a first processing script to obtain a first file corresponding to the plurality of functional modules; and to determine the cause of the fault based on the first file corresponding to the plurality of functional modules.

2. The system according to claim 1, characterized in that, The target controller is configured to, for any given period, based on the acquisition request, acquire the signal values ​​of the multiple functional modules within the period according to the signal order of the multiple functional modules in a pre-stored signal list; and assemble the signal values ​​of the multiple functional modules within the period into the first data stream.

3. The system according to claim 1, characterized in that, The terminal is further configured to acquire the first processing script and run the first processing script. The first processing script is configured to write the signal values ​​of the multiple functional modules in the multiple cycles of the second data stream into a table based on the pre-stored signal order of the multiple functional modules, thereby obtaining a first table. The first table is converted into a file with a preset format to obtain the first file.

4. The system according to claim 1, characterized in that, The terminal is also configured to display a change view corresponding to the plurality of functional modules based on the first file, the change view being used to represent the change of the signal value of the functional module over time; Based on the change views corresponding to the multiple functional modules, at least one faulty module is identified from the multiple functional modules; Based on the at least one faulty module, the cause of the fault is determined.

5. The system according to claim 4, characterized in that, The terminal is also used to open the first file through an analysis tool and display a variable selection interface, which includes multiple variable selection options, each variable selection option corresponding to a functional module; in response to a trigger operation on the multiple variable selection options, a change view corresponding to the multiple functional modules is displayed.

6. The system according to claim 1, characterized in that, The diagnostic device is further configured to combine the first data streams corresponding to the plurality of cycles into a second data stream in chronological order.

7. A method for determining vehicle faults, characterized in that, The method includes: The diagnostic equipment acquires multiple fault codes, determines the target controller based on the multiple fault codes, and sends an acquisition request to the target controller; The target controller acquires signal values ​​of multiple functional modules within multiple cycles based on the acquisition request; generates a first data stream based on the signal values ​​of the multiple functional modules within each cycle; and sends the first data stream corresponding to the multiple cycles to the diagnostic device, wherein the multiple functional modules are multiple modules corresponding to the target controller. The diagnostic device generates a second data stream based on the first data stream corresponding to the multiple cycles, and sends the second data stream to the terminal; The terminal processes the second data stream using a first processing script to obtain a first file corresponding to the plurality of functional modules; The terminal determines the cause of the fault based on the first file corresponding to the multiple functional modules.

8. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing at least one piece of program code, which is loaded and executed by the processor to implement the vehicle fault determination method as described in claim 7 for a diagnostic device, target controller, or terminal.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one piece of program code, which is loaded and executed by a processor to implement the vehicle fault determination method as described in claim 7.

10. A computer program product, characterized in that, The computer program product stores at least one piece of program code, which is loaded and executed by a processor to implement the vehicle fault determination method as described in claim 7.

Images