Vehicle fault scanning method and device, electronic equipment and computer storage medium

Abstract

The invention discloses a vehicle fault scanning method and device, electronic equipment and a computer storage medium. The method comprises the steps of searching vehicle cache information corresponding to a vehicle based on an identification code of the vehicle; when the vehicle cache information of the vehicle is not found, a standard ECU list of the vehicle is obtained, and a first instruction is sent to the vehicle based on the standard ECU list so as to inquire a real ECU list of the vehicle; when the vehicle cache information of the vehicle is found, analyzing the vehicle cache information to obtain a real ECU list of the vehicle; based on the real ECU list, a second instruction is sent to the vehicle, fault scanning is conducted on the vehicle, a whole vehicle system topological graph is formed, and the whole vehicle system topological graph serves as vehicle cache information to be stored in a preset unit. According to the embodiment of the invention, the problems of low fault scanning efficiency and resource waste in the existing whole automobile scanning technology can be solved.

Description

Technical Field

[0001] The present invention relates to the technical field of automobile fault diagnosis, and in particular to a vehicle fault scanning method, device, electronic equipment and computer storage medium. Background Art

[0002] With the rapid development of automotive electronics, the number of electronic control units (ECUs) in vehicles continues to increase, significantly increasing the difficulty and complexity of vehicle fault diagnosis. Vehicle scanning, a common method for improving diagnostic efficiency, utilizes diagnostic software to send 19 service commands to all ECUs in the vehicle, thereby obtaining system fault codes.

[0003] However, in the actual diagnostic process, the entire vehicle must be scanned for each diagnosis, and the list of ECUs to be scanned is based on the entire vehicle model. However, vehicles with different configurations actually have different ECUs installed. For example, some low-end vehicles may not be equipped with certain ECUs. Even so, the diagnostic software will still send commands to these unconfigured ECUs. If no command feedback is received, it will need to wait for a timeout period, and sometimes even multiple timeout periods, which greatly wastes diagnostic time. In particular, when users diagnose the same vehicle multiple times, the entire vehicle must be scanned again each time the diagnostic software is restarted, resulting in low fault scanning efficiency, seriously affecting the user experience, and also causing a waste of resources. Summary of the Invention

[0004] In response to the above technical problems, the embodiments of the present application provide a vehicle fault scanning method, device, electronic device and computer storage medium to solve the problems of low fault scanning efficiency and waste of resources in the existing vehicle scanning technology.

[0005] A first aspect of an embodiment of the present application provides a vehicle fault scanning method, the method comprising:

[0006] Reading a vehicle identification code, and searching a preset storage unit for vehicle cache information corresponding to the vehicle based on the vehicle identification code;

[0007] When no vehicle cache information of the vehicle is found, performing a first fault scan, including: obtaining a standard ECU list corresponding to the vehicle from a vehicle model configuration file of the vehicle, and sending a first instruction to the vehicle based on the standard ECU list to query a real ECU list contained in the vehicle, and sending a second instruction to the vehicle based on the real ECU list to perform a fault scan on the vehicle to form a whole vehicle system topology map, and storing the whole vehicle system topology map as vehicle cache information in the preset unit;

[0008] When the vehicle cache information of the vehicle is found, a fault scan is performed again, including: parsing the vehicle cache information to obtain a real ECU list of the vehicle, sending a second instruction to the vehicle based on the real ECU list, performing a fault scan on the vehicle, forming a whole vehicle system topology map, and storing the whole vehicle system topology map as updated vehicle cache information in the preset unit.

[0009] In a specific implementation of the first aspect, when performing a second fault scan, sending a second instruction to the vehicle based on the real ECU list to perform a fault scan on the vehicle includes:

[0010] Obtaining the items to be scanned in the real ECU list;

[0011] A second instruction is sent to the vehicle based on the item to be scanned to perform a fault scan on the vehicle.

[0012] In a specific implementation of the first aspect, the items to be scanned include preset must-scan ECUs and ECUs diagnosed as having faults included in a previous fault scan result.

[0013] In a specific implementation of the first aspect, searching a preset storage unit for vehicle cache information corresponding to the vehicle based on the vehicle identification code includes:

[0014] Determine whether the network connection with the server is normal;

[0015] When the network connection with the server is normal, the vehicle identification code is uploaded to the server, and the query result of the vehicle cache information returned by the server is received;

[0016] When the network connection with the server is abnormal, a query is performed locally based on the vehicle identification code to obtain a query result of the vehicle cache information.

[0017] In a specific implementation of the first aspect, when performing the initial fault scan and the secondary fault scan, sending the second instruction to the vehicle to perform a fault scan on the vehicle to form a vehicle system topology map includes:

[0018] Based on the real ECU list of the vehicle, a second instruction is sent to the vehicle to read the status information of the ECU, wherein the status information includes normal and faulty;

[0019] Generate a topology diagram of the entire vehicle system based on the recorded normal and faulty ECUs.

[0020] In a specific implementation of the first aspect, before parsing the vehicle cache information, the method further includes:

[0021] Determining whether the vehicle cache information is within a validity period;

[0022] When the vehicle cache information is not within the validity period, performing the step of obtaining the standard ECU list corresponding to the vehicle from the vehicle model configuration file;

[0023] When the vehicle cache information is within the validity period, the step of parsing the vehicle cache information to obtain a real ECU list of the vehicle is performed.

[0024] In a specific implementation of the first aspect, the method further includes:

[0025] The vehicle system topology diagram and the vehicle identification code, scanning time and validity period are encrypted and stored locally on the client and uploaded to the server at the same time.

[0026] In a second aspect, an embodiment of the present application provides a vehicle fault scanning device, the device comprising:

[0027] A query module is used to read the vehicle identification code and search the vehicle cache information corresponding to the vehicle in a preset storage unit based on the vehicle identification code;

[0028] a first fault scanning module, configured to, when no vehicle cache information for the vehicle is found, obtain a standard ECU list corresponding to the vehicle from the vehicle model configuration file of the vehicle, and based on the standard ECU list, send a first instruction to the vehicle to query a real ECU list contained in the vehicle, and based on the real ECU list, send a second instruction to the vehicle to perform a fault scan on the vehicle to form a whole vehicle system topology map, and store the whole vehicle system topology map as vehicle cache information in the preset unit;

[0029] The fault re-scanning module is used to parse the vehicle cache information of the vehicle when the vehicle cache information is found, obtain the real ECU list of the vehicle, send a second instruction to the vehicle based on the real ECU list, scan the vehicle for faults, form a whole vehicle system topology map, and store the whole vehicle system topology map as updated vehicle cache information in the preset unit.

[0030] In a third aspect, an embodiment of the present application further provides an electronic device, comprising a memory storing a plurality of instructions; a processor loading instructions from the memory to execute the steps of any vehicle fault scanning method provided in the embodiment of the present application.

[0031] In a fourth aspect, an embodiment of the present application further provides a computer storage medium storing a plurality of instructions suitable for loading by a processor to execute the steps of any one of the vehicle fault scanning methods provided in the embodiment of the present application.

[0032] In the embodiment provided by the embodiment of the present application, during the first fault scan of the vehicle, a first instruction for querying whether a certain ECU is included in the vehicle is sent to the vehicle based on the standard ECU list of the vehicle. If a reply command to the first instruction is received, it indicates that the vehicle is equipped with the ECU. The use of the first instruction can identify the ECU actually carried by the vehicle, avoid invalid scanning of unconfigured ECUs, optimize the fault scanning process, and improve the fault scanning efficiency; further, after each scan of the vehicle, the vehicle system topology will be generated according to the fault scanning results of the ECU actually carried by the vehicle, and stored in a preset storage unit. When the vehicle performs a fault scan again, the vehicle's real ECU list can be obtained according to the vehicle system topology, and a fault scan is performed according to the real ECU list, which further saves the time of fault scanning and improves the fault scanning efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0034] Figure 1 Schematic diagram of the standard ECU list and the real ECU list provided in the embodiment of the present application;

[0035] Figure 2 Schematic diagram of the application environment of the vehicle fault scanning method provided in the embodiment of the present application;

[0036] Figure 3 This is a flow chart of an embodiment of a vehicle fault scanning method provided in an embodiment of the present application;

[0037] Figure 4 This is a flow chart of one of the steps in the vehicle fault scanning method provided in an embodiment of the present application;

[0038] Figure 5 This is a flow chart of another step in the vehicle fault scanning method provided in an embodiment of the present application;

[0039] Figure 6 Schematic diagram of the structure of the vehicle fault scanning device provided in an embodiment of the present application;

[0040] Figure 7It is a schematic diagram of the internal structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0042] The terms "first," "second," and the like in the specification and claims of this application and the accompanying drawings are used to distinguish between different objects, not to describe a particular order. Furthermore, the terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

[0043] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0044] The following describes the relevant contents, concepts, meanings, technical issues, technical solutions, beneficial effects, etc. involved in the embodiments of this application.

[0045] The Electronic Control Unit (ECU) is a key component in a car. It receives signals from various sensors, processes them according to pre-set programs, and controls the operation of the vehicle's actuators to ensure proper operation. An ECU failure can impact the vehicle's powertrain, safety systems, comfort features, diagnostics, and repair.

[0046] Vehicle scanning is a common method for diagnosing ECU faults. Diagnostic software sends 19 service commands to all ECUs in the vehicle to obtain system fault codes. These codes are then displayed as a system topology diagram or list, providing diagnosticians with intuitive vehicle fault information to help identify the faulty ECU. These 19 service commands are services used during vehicle diagnostics that allow external diagnostic software to read the status information of the Diagnostic Trouble Codes (DTCs) stored within the ECU chip.

[0047] ECU configurations vary across different vehicle models. Even for the same vehicle model, the ECU system configuration may differ to meet the needs of different consumers. For example, some consumers who prioritize driving safety and stability may prefer safety-related ECUs such as Electronic Stability Control (ESC). Consumers who prioritize vehicle comfort and convenience may be more interested in features like automatic air conditioning and heated seats, requiring the vehicle to be equipped with ECUs that control these features. To reduce costs, some consumers may reduce the number of ECUs associated with features like automatic parking and adaptive cruise control. However, in traditional diagnostics, the diagnostic software sends commands to all ECUs corresponding to the vehicle model. If no command feedback is received, the software must wait for a timeout, sometimes even multiple timeouts. This significantly increases fault scanning time.

[0048] In view of this, the embodiments of the present application provide a vehicle fault scanning method, device, electronic device and computer storage medium to solve the problem of long waiting time and wasted fault scanning time in traditional vehicle fault scanning in the prior art.

[0049] When it is determined that the vehicle is being scanned for the first fault, an embodiment of the present invention obtains a list of standard ECUs corresponding to the vehicle model from the vehicle model configuration file corresponding to the vehicle. The standard ECU list is a complete set of ECUs that may be installed under all configurations of a certain vehicle model. Different models of the same vehicle may have multiple configurations, and the ECUs installed in different configurations may be different. For example, a low-end model may not have ESC. The standard ECU list contains all possible ECUs that may appear in all configurations of the model, and its number will be more than the number of ECUs actually installed on any specific vehicle, providing a basic framework for vehicle diagnosis. Figure 1 As shown, the standard ECU list of model A of a certain brand of vehicle may include ECU1, ECU2, ECU3, ECU4, ECU5, ECU6, ECU7...ECUM, while the real ECU list of a specific vehicle of model A may include ECU1, ECU3, ECU4, ECU7...ECUN, where M can be greater than N.

[0050] Furthermore, an embodiment of the present invention sends a first instruction to the vehicle based on each ECU included in the standard ECU list, and the first instruction is used to query whether the vehicle includes the ECU. For example, if the standard ECU list of a vehicle includes ESC (Electronic Stability Control), PACU (Parking Assist Control Unit), etc., then an embodiment of the present application sends a first instruction for ESC to the vehicle. If a reply command to the first instruction of ESC is received, it indicates that the vehicle is equipped with ESC. Furthermore, a first instruction for PACU is sent to the vehicle. If a reply command to the first instruction of PACU is not received, it indicates that the vehicle is not equipped with PACU. Afterwards, a second instruction is sent to the ECU that received the reply command of the first instruction to read the fault code of the ECU. The use of the first instruction can identify the ECU actually installed on the vehicle, avoid invalid scanning of unconfigured ECUs, optimize the fault scanning process, and improve the efficiency of fault scanning.

[0051] In an embodiment of the present invention, a vehicle system topology map is generated based on the fault codes of all ECUs obtained as described above, wherein the vehicle system topology map includes a list of real ECUs in the vehicle, and the vehicle system topology map is stored in a preset storage unit, such as a cloud server or locally, and in subsequent fault scanning, the real ECU list in the vehicle is directly obtained from the storage unit for fault scanning, thereby further saving the time of fault scanning and improving the efficiency of fault scanning.

[0052] Figure 2 The figure shows a schematic diagram of an application environment for a vehicle fault scanning method according to an embodiment of the present application. In one embodiment of the present invention, the application environment of the vehicle fault scanning method includes one or more clients (only one is shown in the figure), a server, and a vehicle to be diagnosed. The client and the server can be connected via a network, and the client and the vehicle to be diagnosed can be connected via a network or Bluetooth.

[0053] The client can be fixed in any automobile sales and service organization, such as a 4S store, or it can be a portable device carried by automobile diagnostic personnel. Furthermore, the client is installed with diagnostic software for obtaining the identification code (Vehicle Identification Number, VIN) of the vehicle to be diagnosed, and based on the identification code of the vehicle, searches the server for the vehicle cache information corresponding to the vehicle in an online state. The vehicle cache information stores the vehicle's previous fault scanning information. The fault scanning information includes the fault scanning results of the ECU actually installed in the vehicle, such as the ECU diagnosed as normal and the ECU with a fault.

[0054] When the vehicle cache information of the vehicle does not exist in the server, it means that the vehicle may be undergoing the first fault scan. At this time, the diagnostic software obtains the standard ECU list corresponding to the vehicle model from the vehicle model configuration file. During the first fault scan, the embodiment of the present invention performs a vehicle fault scan based on the standard ECU list to obtain the entire vehicle system topology. The entire vehicle system topology includes the fault scan results of the ECUs actually installed on the vehicle, such as normal ECUs and faulty ECUs. The entire vehicle system topology can be uploaded to the server and can also be stored locally on the client to generate vehicle cache information. In the subsequent re-fault scanning process, the embodiment of the present invention can obtain the entire vehicle system topology from the server or local vehicle cache information to obtain the vehicle's real ECU list for fault scanning.

[0055] The server can be a cloud server. Since the server's storage environment is relatively stable, uploading the vehicle's entire system topology to the server can avoid data damage or loss caused by equipment failure, loss, replacement, etc. on the client, thereby ensuring data integrity and providing a reliable basis for subsequent vehicle diagnosis.

[0056] See Figure 3 FIG2 is a flow chart of one embodiment of a vehicle fault scanning method of the present application. As an implementation method, the vehicle fault scanning method provided in the embodiment of the present application is applied to a client. The client can be a mobile phone, tablet, desktop computer, laptop computer, etc.

[0057] S31. Read the vehicle identification code.

[0058] The vehicle identification number (VIN code) is the "identity card" of the car. It is unique and can accurately identify the identity of the vehicle.

[0059] S32: Determine whether the vehicle cache information corresponding to the vehicle can be found in a preset storage unit based on the vehicle identification code.

[0060] The preset storage unit can be a storage unit in a cloud server or a local storage unit of a client. The vehicle cache information stores the vehicle's previous fault scan information. The fault scan information includes the diagnostic results of the ECUs actually installed in the vehicle, such as normal ECUs and faulty ECUs.

[0061] In the embodiment of the present invention, the vehicle identification code is bound to the vehicle cache information and stored.

[0062] In one embodiment of the present invention, searching for vehicle cache information corresponding to the vehicle in a preset storage unit based on the identification code includes:

[0063] Determine whether the network connection with the server is normal;

[0064] When the network connection with the server is normal, the vehicle identification code is uploaded to the server, and the query result of the vehicle cache information returned by the server is received;

[0065] When the network connection with the server is abnormal, a query is performed locally based on the vehicle identification code to obtain a query result of the vehicle cache information.

[0066] When the vehicle cache information of the vehicle is not found in the preset storage unit, it indicates that the vehicle is being scanned for faults for the first time, and S33 is executed to obtain the standard ECU list corresponding to the vehicle from the vehicle model configuration file, and based on the standard ECU list, a first instruction is sent to the vehicle to query the real ECU list in the vehicle.

[0067] As described above, the standard ECU list includes a complete set of ECUs that may be installed in all vehicle configurations. However, the ECUs actually installed in the vehicle may differ from the standard ECU list. Therefore, embodiments of the present invention require obtaining the vehicle's actual ECU list from the standard ECU list. In one embodiment of the present invention, a first instruction is first sent to the vehicle based on each ECU included in the standard ECU list. The first instruction is used to query whether the vehicle includes the ECU. For example, if a vehicle's standard ECU list includes ESC (Electronic Stability Control) and PACU (Parking Assist Control Unit), the embodiment of the present application sends a first instruction for the ESC to the vehicle. If a reply command to the first ESC instruction is received, it indicates that the vehicle is equipped with ESC. Furthermore, a first instruction for the PACU is sent to the vehicle. If a reply command to the first PACU instruction is not received, it indicates that the vehicle is not equipped with PACU. The first instruction can be, for example, the 0X1001 instruction.

[0068] For details, see Figure 4 As shown, the sending of a first instruction to the vehicle based on the standard ECU list to query the real ECU list contained in the vehicle includes:

[0069] S330, selecting one ECU from the standard ECU list;

[0070] S331, sending a first instruction for the selected ECU to the vehicle to determine whether the vehicle is equipped with the ECU;

[0071] When a reply message from the vehicle to the first instruction is received, S332 determines that the vehicle is equipped with the above-selected ECU, and executes S334 to determine whether all ECUs in the standard ECU list have been selected. If not, the process returns to S330 until all ECUs in the standard ECU list have been selected.

[0072] When no reply message is received from the vehicle to the first instruction, S333 determines that the vehicle is not equipped with the above-selected ECU, and executes S334 to determine whether all ECUs in the standard ECU list have been selected. If not, the process returns to S330 until all ECUs in the standard ECU list have been selected.

[0073] When all ECUs in the standard ECU list have been selected, S335 is executed to obtain a real ECU list carried in the vehicle based on the first instructions of all received reply messages.

[0074] S34. Based on the real ECU list included in the vehicle, send a second instruction to the vehicle, perform fault scanning on the vehicle, form a whole vehicle system topology map, and store the whole vehicle system topology map as vehicle cache information in the preset unit.

[0075] In an embodiment of the present invention, the second instruction may be a 0X1902 instruction.

[0076] Based on the vehicle's actual ECU list, an embodiment of the present invention sends a second instruction to the vehicle to read the ECU's status information. After all ECU systems in the standard ECU list are scanned, the ECU's status information can be divided into three categories: "normal" (the vehicle is equipped with the ECU and has no fault codes), "faulty" (the vehicle is equipped with the ECU and has fault codes), and "unconfigured" (the vehicle is not equipped with the ECU). This embodiment of the present invention removes the "unconfigured" ECU node information, records normal and faulty ECUs, and generates a vehicle system topology map based on the records of normal and faulty ECUs. The vehicle system topology map, the vehicle's identification code, the scan time, and other information are encrypted and stored, with the vehicle's identification code as the key. This information is stored locally on the client and simultaneously uploaded to the server.

[0077] The vehicle system topology diagram visually displays the vehicle's ECU system architecture and connection relationships, making it easier for maintenance personnel to quickly locate faults. It covers vehicle identification information, ECU nodes, and their connection relationships. The vehicle system topology diagram shows the distribution of each ECU in the vehicle, such as "EMS," "FCS," "BCM," "ESC," and "GW." These ECUs are connected via different network buses, such as "Hybrid_CAN," "Chassis CAN," and "Body_CAN." By showing the location and connection methods of each ECU within the vehicle system, the architecture of the vehicle's electronic system is clearly demonstrated. Maintenance personnel can use the topology diagram to quickly determine signal transmission paths. When a fault occurs in a specific ECU, they can follow the connection relationships to identify related lines and other potentially affected ECUs, improving fault scanning efficiency.

[0078] When the vehicle cache information of the vehicle is found in the preset storage unit, it indicates that the vehicle is being scanned for faults again, and S35 is executed to parse the vehicle cache information to obtain a real ECU list of the vehicle.

[0079] As mentioned above, the vehicle cache stores the vehicle's previous fault scan information. This fault scan information includes the diagnostic results of the vehicle's actual ECUs. Therefore, the vehicle's actual ECU list can be obtained based on this fault scan information. The diagnostic results include both ECUs diagnosed as normal and those diagnosed as faulty.

[0080] S36. Based on the real ECU list, send a second instruction to the vehicle, perform a fault scan on the vehicle, form an updated vehicle system topology map, and store the updated vehicle system topology map in the preset unit.

[0081] In one embodiment of the present invention, the sending of a second instruction to the vehicle based on the real ECU list to perform a fault scan on the vehicle in step S36 includes: obtaining an item to be scanned in the real ECU list; and sending a second instruction to the vehicle based on the item to be scanned to perform a fault scan on the vehicle.

[0082] In an embodiment of the present invention, the items to be scanned in the real ECU list may include preset must-scan ECUs and ECUs diagnosed as faulty during the previous fault scan. Among them, the must-scan ECUs may include important ECUs set by the user, such as the EMS (Engine Management System) system, which is a very important system and must be scanned every time. Furthermore, the ECU diagnosed as faulty during the previous fault scan is the faulty ECU diagnosed during the previous scan, and the fault code is included in the diagnosis result. When performing a fault scan on the vehicle, the embodiment of the present invention gives priority to sending a scan instruction to the ECUs that must be scanned, and secondly sends a scan instruction to the faulty ECU diagnosed during the previous scan. Other normal ECUs do not need to be scanned, and a whole vehicle system topology diagram is directly formed.

[0083] In the embodiment of the present invention, a vehicle fault scan is performed based on important ECUs and faulty ECUs diagnosed in the last scan, while normal, less important ECUs do not need to be scanned every time, further saving fault scanning time and improving fault scanning efficiency.

[0084] In other embodiments of the present invention, the item to be scanned may also be the entire real ECU list.

[0085] Furthermore, the updated vehicle system topology map is synchronously updated to the server and client. Furthermore, maintenance personnel can obtain vehicle fault information from the vehicle system topology map by reading the code. Based on the fault code, they can locate the faulty system and possible causes, allowing for targeted inspection and repair. After confirming the fault has been cleared, they can perform a code clearing operation, which will also generate an updated vehicle system topology map. This updated map will also be synchronously updated to the server and client.

[0086] In another embodiment of the present invention, see Figure 5 As shown, when the vehicle cache information of the vehicle is found in the preset storage unit, before step S35, the process further includes: S37, determining whether the vehicle cache information is within the validity period.

[0087] When the vehicle cache information is within the validity period, the above step S35 is executed, and when the vehicle cache information is not within the validity period, the process returns to the above step S33.

[0088] Sometimes a vehicle may be modified, such as by adding an ECU. In this case, the vehicle system topology map in the cached information may not be appropriate. Therefore, it is necessary to re-send a first command to the vehicle based on the vehicle's standard ECU list to query the vehicle's actual ECU list. In one embodiment of the present invention, the validity period can be set to, for example, three days.

[0089] In an embodiment of the present invention, the set validity period may also be encrypted and stored together with the vehicle system topology map, the vehicle identification code, the scanning time, etc.

[0090] By using the vehicle fault scanning method provided in the embodiment of the present application, during the first fault scan of the vehicle, a first instruction for querying whether a certain ECU is included in the vehicle is sent to the vehicle based on the vehicle's standard ECU list. If a reply command to the first instruction is received, it indicates that the vehicle is equipped with the ECU. The use of this first instruction can identify the ECU actually carried by the vehicle, avoid invalid scanning of unconfigured ECUs, optimize the fault scanning process, and improve the efficiency of fault scanning. Furthermore, after each fault scan of the vehicle, the vehicle system topology will be generated based on the diagnostic results of the ECU actually carried by the vehicle and stored in a preset storage unit. In the subsequent fault scan of the vehicle, the vehicle's real ECU list can be obtained based on the vehicle system topology, and fault scanning can be performed based on the real ECU list, thereby further saving the time of fault scanning and improving the efficiency of fault scanning.

[0091] It should be understood that, although each step in the flowcharts involved in the above-mentioned embodiments is displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0092] Based on the same inventive concept, an embodiment of the present application further provides a vehicle fault scanning device for implementing the above-mentioned vehicle fault scanning method. The vehicle fault scanning device can be integrated into a client.

[0093] See Figure 6 , Figure 6 1 is a structural diagram of a vehicle fault scanning device provided in an embodiment of the present application. The vehicle fault scanning device 60 includes: a query module 61, a fault first scanning module 62, and a fault second scanning module 63.

[0094] In one embodiment of the present invention, the query module 61 reads the vehicle identification code and searches for the vehicle cache information corresponding to the vehicle in a preset storage unit based on the vehicle identification code; the fault first scanning module 62 is used to obtain the standard ECU list corresponding to the vehicle from the vehicle model configuration file of the vehicle when the vehicle cache information of the vehicle is not found, and based on the standard ECU list, send a first instruction to the vehicle to query the real ECU list of the vehicle, and based on the real ECU list, send a second instruction to the vehicle to perform a fault scan on the vehicle to form a whole vehicle system topology map, and store the whole vehicle system topology map as the vehicle cache information in the preset unit; the fault re-scanning module 63 is used to parse the vehicle cache information when the vehicle cache information of the vehicle is found, obtain the real ECU list of the vehicle, send a second instruction to the vehicle based on the real ECU list, perform a fault scan on the vehicle to form a whole vehicle system topology map, and store the whole vehicle system topology map as the updated vehicle cache information in the preset unit.

[0095] In one embodiment of the present invention, when the fault re-scan module 63 sends a second instruction to the vehicle based on the real ECU list to perform a fault scan on the vehicle, the module performs the following steps: obtaining items to be scanned from the real ECU list; and sending a second instruction to the vehicle based on the items to be scanned to perform a fault scan on the vehicle. The items to be scanned include preset mandatory ECUs and ECUs diagnosed as faulty in the diagnosis results of the previous fault scan.

[0096] In one embodiment of the present invention, when the query module 61 searches for the vehicle cache information corresponding to the vehicle in a preset storage unit based on the vehicle identification code, it executes: determining whether the network connection with the server is normal; when the network connection with the server is normal, uploading the vehicle identification code to the server and receiving the query result of the vehicle cache information returned by the server; when the network connection with the server is abnormal, performing a local query based on the vehicle identification code to obtain the query result of the vehicle cache information.

[0097] In one embodiment of the present invention, the first fault scanning module 62 and the second fault scanning module 63 send a second instruction to the vehicle to perform a fault scan on the vehicle to form a vehicle system topology diagram, and then execute: based on the real ECU list of the vehicle, send a second instruction to the vehicle to read the status information of the ECU, wherein the status information includes normal and faulty; and generate a vehicle system topology diagram based on the ECUs recorded as normal and faulty.

[0098] In one embodiment of the present invention, the vehicle fault scanning device 60 may further include a judgment module for: judging whether the vehicle cache information is within the validity period; when the vehicle cache information is not within the validity period, notifying the fault first scanning module 62 to obtain the standard ECU list corresponding to the vehicle from the vehicle model configuration file of the vehicle; when the vehicle cache information is within the validity period, notifying the fault re-scanning module 63 to execute the step of parsing the vehicle cache information to obtain the real ECU list of the vehicle.

[0099] In one embodiment of the present invention, the vehicle fault scanning device 60 may further include an encryption module for encrypting and saving the vehicle system topology map and the vehicle identification code, scanning time and validity period, and storing them locally on the client, and uploading them to the server at the same time.

[0100] Using the vehicle fault scanning device provided in the embodiment of the present application, when the vehicle is scanned for faults for the first time, a first instruction for querying whether a certain ECU is included in the vehicle is sent to the vehicle based on the vehicle's standard ECU list. If a reply command to the first instruction is received, it indicates that the vehicle is equipped with the ECU. The use of the first instruction can identify the ECU actually installed on the vehicle, avoid invalid scanning of unconfigured ECUs, optimize the fault scanning process, and improve the fault scanning efficiency; further, after each scan of the vehicle, the vehicle system topology will be generated based on the fault scanning results of the ECU actually installed on the vehicle and stored in a preset storage unit. When the vehicle is scanned for faults again, the vehicle's real ECU list can be obtained based on the vehicle system topology, and fault scanning can be performed based on the real ECU list, thereby further saving fault scanning time and improving fault scanning efficiency.

[0101] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0102] Based on the same inventive concept, an embodiment of the present application further provides an electronic device, which may be a server or a terminal device. The electronic device includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, the steps of the above-mentioned vehicle fault scanning method are implemented, thereby achieving various functions, such as:

[0103] Reading a vehicle identification code, and searching a preset storage unit for vehicle cache information corresponding to the vehicle based on the vehicle identification code;

[0104] When no vehicle cache information of the vehicle is found, performing a first fault scan, including: obtaining a standard ECU list corresponding to the vehicle from the vehicle model configuration file, and sending a first instruction to the vehicle based on the standard ECU list to query a real ECU list contained in the vehicle; sending a second instruction to the vehicle based on the real ECU list to perform a fault scan on the vehicle to form a whole vehicle system topology map, and storing the whole vehicle system topology map as vehicle cache information in the preset unit;

[0105] When the vehicle cache information of the vehicle is found, a fault scan is performed again, including: parsing the vehicle cache information to obtain a real ECU list of the vehicle; based on the real ECU list, a second instruction is sent to the vehicle to perform a fault scan on the vehicle to form a whole vehicle system topology map, and the whole vehicle system topology map is stored as updated vehicle cache information in the preset unit.

[0106] Figure 7A schematic block diagram of an electronic device provided in an embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.

[0107] like Figure 7 As shown, the electronic device 70 of this embodiment includes: a processor 71, a memory 72, and a computer program 73 stored in the memory 72 and executable on the processor 71. When the processor 71 executes the computer program 73, the steps in the above-mentioned vehicle fault scanning method embodiments are implemented, such as Figure 3 Alternatively, when the processor 71 executes the computer program 73, the functions of each module / unit in the embodiment of the vehicle fault scanning device 60 are realized, for example Figure 6 The functions of modules 61 to 63 are shown.

[0108] Exemplarily, the computer program 73 may be divided into one or more modules / units, which are stored in the memory 72 and executed by the processor 71 to implement the present application. The one or more modules / units may be a series of computer program instruction segments capable of implementing specific functions, and the instruction segments are used to describe the execution process of the computer program 73 in the electronic device 70.

[0109] The electronic device 70 may include but is not limited to desktop computers, notebook computers, PDAs, servers and other computing devices. It will be understood by those skilled in the art that Figure 7 It is merely an example of the electronic device 70 and does not constitute a limitation of the electronic device 70. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the electronic device 70 may also include input and output devices, network access devices, buses, etc.

[0110] The processor 71 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0111] The memory 72 may be an internal storage unit of the electronic device 70, such as a hard disk or memory of the electronic device 70. The memory 72 may also be an external storage device of the electronic device 70, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 70. Furthermore, the memory 72 may include both an internal storage unit of the electronic device 70 and an external storage device. The memory 72 is used to store the computer program and other programs and data required by the electronic device 70. The memory 72 may also be used to temporarily store data that has been output or is about to be output.

[0112] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0113] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0114] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0115] In the embodiments provided in the present application, it should be understood that the disclosed devices / electronic devices and methods can be implemented in other ways. For example, the device / electronic device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0116] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0117] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0118] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer storage medium, and when the computer program is executed by the processor, it can implement the steps of the above-mentioned various method embodiments. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer storage medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer storage medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer storage media do not include electric carrier signals and telecommunication signals.

[0119] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

Claims

1. A vehicle fault scanning method, characterized in that: The method comprises: Reading a vehicle identification code, and searching a preset storage unit for vehicle cache information corresponding to the vehicle based on the vehicle identification code; When no vehicle cache information of the vehicle is found, performing a first fault scan, including: obtaining a standard ECU list corresponding to the vehicle from the vehicle model configuration file of the vehicle, and sending a first instruction to the vehicle based on the standard ECU list to query a real ECU list of the vehicle, and sending a second instruction to the vehicle based on the real ECU list to perform a fault scan on the vehicle to form a whole vehicle system topology map, and storing the whole vehicle system topology map as the vehicle cache information in the preset storage unit; When the vehicle cache information of the vehicle is found, a fault scan is performed again, including: parsing the vehicle cache information to obtain a real ECU list of the vehicle; based on the real ECU list, a second instruction is sent to the vehicle to perform a fault scan on the vehicle to form a whole vehicle system topology map; and the whole vehicle system topology map is stored as updated vehicle cache information in the preset storage unit.

2. The method according to claim 1, wherein When performing a second fault scan, sending a second instruction to the vehicle based on the real ECU list to perform a fault scan on the vehicle includes: Obtaining the items to be scanned in the real ECU list; Based on the items to be scanned, a second instruction is sent to the vehicle to perform a fault scan on the vehicle.

3. The method according to claim 2, wherein The items to be scanned include preset must-scan ECUs and ECUs diagnosed as having faults in the diagnosis result of the previous fault scan.

4. The method according to claim 1, wherein The searching for vehicle cache information corresponding to the vehicle in a preset storage unit based on the vehicle identification code includes: Determine whether the network connection with the server is normal; When the network connection with the server is normal, the vehicle identification code is uploaded to the server, and the query result of the vehicle cache information returned by the server is received; When the network connection with the server is abnormal, a query is performed locally based on the vehicle identification code to obtain a query result of the vehicle cache information.

5. The method according to claim 4, wherein When performing the first fault scan and the second fault scan, the second instruction is sent to the vehicle to perform a fault scan on the vehicle to form a vehicle system topology diagram, including: Based on the real ECU list of the vehicle, a second instruction is sent to the vehicle to read the status information of the ECU, wherein the status information includes normal and faulty; Generate a topology diagram of the entire vehicle system based on the recorded normal and faulty ECUs.

6. The method according to claim 1, wherein Before parsing the vehicle cache information, the method further includes: Determining whether the vehicle cache information is within a validity period; When the vehicle cache information is not within the validity period, performing the step of obtaining the standard ECU list corresponding to the vehicle from the vehicle model configuration file; When the vehicle cache information is within the validity period, the step of parsing the vehicle cache information to obtain a real ECU list of the vehicle is performed.

7. The method according to claim 6, wherein The method further comprises: The vehicle system topology diagram and the vehicle identification code, scanning time and validity period are encrypted and stored locally on the client and uploaded to the server at the same time.

8. A vehicle fault scanning device, characterized in that: The device comprises: A query module, configured to read a vehicle identification code and search a preset storage unit for vehicle cache information corresponding to the vehicle based on the vehicle identification code; a first fault scanning module, configured to, when no vehicle cache information for the vehicle is found, obtain a standard ECU list corresponding to the vehicle from the vehicle model configuration file of the vehicle, and based on the standard ECU list, send a first instruction to the vehicle to query a real ECU list contained in the vehicle, and based on the real ECU list, send a second instruction to the vehicle to perform a fault scan on the vehicle to form a whole vehicle system topology map, and store the whole vehicle system topology map as vehicle cache information in the preset unit; The fault re-scanning module is used to parse the vehicle cache information of the vehicle when the vehicle cache information is found, obtain the real ECU list of the vehicle, send a second instruction to the vehicle based on the real ECU list, scan the vehicle for faults, form a whole vehicle system topology map, and store the whole vehicle system topology map as updated vehicle cache information in the preset unit.

9. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a plurality of instructions; the processor loads instructions from the memory to execute the steps of the vehicle fault scanning method according to any one of claims 1 to 7.

10. A computer storage medium, characterized in that The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the steps of the vehicle fault scanning method according to any one of claims 1 to 7.

Images