Hardware troubleshooting method, device, medium and computer equipment for autonomous driving vehicles

Abstract

The hardware troubleshooting method, device, medium and computer equipment for an autonomous driving vehicle provided in the present application can first obtain the fault code corresponding to the hardware fault when the autonomous driving vehicle detects a hardware fault during the current hardware inspection process, and match the fault code with the fault code in a preset fault diagnosis file. Since the fault diagnosis file contains solutions corresponding to different fault codes, and there are multiple types of solutions, after screening out the solution that matches the fault code from the preset fault diagnosis file, the hardware troubleshooting of the autonomous driving vehicle can be directly performed according to the solution and the corresponding solution type. This method of solving hardware fault problems through fault diagnosis files can greatly reduce the number of manual troubleshooting, reduce labor costs, and release manpower, and can also improve the troubleshooting efficiency of hardware faults, thereby effectively ensuring the normal operation of the vehicle.

Description

Technical Field

[0001] The present application relates to the field of autonomous driving technology, and in particular to a method, apparatus, medium, and computer equipment for hardware troubleshooting of an autonomous driving vehicle. Background Art

[0002] In recent years, with the gradual maturity of autonomous driving technology, the use rate of autonomous vehicles has also been gradually increasing. Because autonomous vehicles require the use of radar systems, ultrasonic systems and / or camera systems to detect the driving environment in front of, behind, and on both sides of the vehicle and calculate information such as lanes, road types and / or vehicles, pedestrians and / or obstacles, as well as other driving-related data, such as the lane and steering data of the vehicle, and use the acquired driving-related data as reference data during the autonomous driving process, therefore, when an autonomous vehicle is started, it will generally conduct a comprehensive inspection of its onboard hardware to ensure the normal operation of the vehicle.

[0003] Currently, when inspecting the hardware of an autonomous vehicle, if a hardware failure occurs, the safety officer in the autonomous vehicle will contact the monitoring platform so that the engineers on the monitoring platform can analyze the hardware failure and inform the solution. This process is relatively cumbersome, and there is a certain delay in manual docking, which results in the hardware failure on the vehicle side cannot be resolved in time, affecting the normal travel of the vehicle. Summary of the Invention

[0004] The purpose of this application is to solve at least one of the above-mentioned technical defects, especially the technical defect in the prior art that hardware failures are manually analyzed and solutions are provided, which is a cumbersome process and there is a certain delay in manual docking, which leads to the inability to solve the hardware failure on the vehicle side in a timely manner, affecting the normal travel of the vehicle.

[0005] This application provides a method for troubleshooting hardware of an autonomous driving vehicle, the method comprising:

[0006] When the autonomous driving vehicle detects a hardware fault during the current hardware check process, obtaining a fault code corresponding to the hardware fault;

[0007] Screening out a solution that matches the fault code from a preset fault diagnosis file, wherein the fault diagnosis file stores solutions corresponding to different fault codes, and the solutions may be of multiple types;

[0008] Perform hardware troubleshooting on the autonomous driving vehicle based on the screened solutions and corresponding solution types.

[0009] Optionally, obtaining a fault code corresponding to the hardware fault includes:

[0010] Obtaining a hardware log generated by the autonomous driving vehicle during hardware inspection;

[0011] The fault code corresponding to the hardware fault is read through the hardware log.

[0012] Optionally, there is at least one hardware failure;

[0013] When there are multiple hardware faults and at least two fault codes corresponding to the multiple hardware faults match solutions, screening out solutions matching the fault codes from a preset fault diagnosis file includes:

[0014] Obtaining multiple solutions corresponding to each successfully matched fault code and the priority corresponding to each solution from a preset fault diagnosis file;

[0015] A solution with the highest priority among the solutions is determined according to the priorities of the solutions, and the solution with the highest priority is used as the solution that matches the fault code and is screened from the fault diagnosis file.

[0016] Optionally, performing hardware troubleshooting on the autonomous driving vehicle based on the screened solutions and corresponding solution types includes:

[0017] If the solution type of the screened solution is a direct solution type, the solution is directly sent to the safety officer in the autonomous driving vehicle, so that the safety officer can perform hardware troubleshooting on the autonomous driving vehicle according to the solution;

[0018] If the solution type of the screened solution is an indirect solution type, the hardware of the autonomous driving vehicle is re-checked based on the solution content, and when it is determined that the autonomous driving vehicle has detected a hardware fault during the current hardware inspection process, the step of obtaining the fault code corresponding to the hardware fault is returned to.

[0019] Optionally, re-checking the hardware of the autonomous driving vehicle according to the solution includes:

[0020] Get the check method set in the solution content of the solution;

[0021] Re-inspect the hardware of the autonomous driving vehicle according to the inspection method.

[0022] Optionally, the method further includes:

[0023] When there is no solution matching the fault code in the fault diagnosis file, the fault code is reported to the monitoring platform so that the monitoring platform can perform remote troubleshooting based on the fault code.

[0024] Optionally, the method further includes:

[0025] The solution for remote troubleshooting and the fault code are added to the fault diagnosis file to update the fault diagnosis file.

[0026] This application also provides a hardware troubleshooting device for an autonomous driving vehicle, comprising:

[0027] A fault code acquisition module is used to obtain a fault code corresponding to a hardware fault when the autonomous driving vehicle detects a hardware fault during the current hardware check process;

[0028] A solution determination module is used to filter out a solution that matches the fault code from a preset fault diagnosis file, wherein the fault diagnosis file stores solutions corresponding to different fault codes, and the solutions may be of multiple types;

[0029] The hardware troubleshooting module is used to perform hardware troubleshooting on the autonomous driving vehicle based on the screened solutions and corresponding solution types.

[0030] The present application also provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the hardware troubleshooting method for an autonomous driving vehicle as described in any of the above embodiments.

[0031] The present application also provides a computer device, comprising: one or more processors, and a memory;

[0032] The memory stores computer-readable instructions, which, when executed by the one or more processors, execute the steps of the hardware troubleshooting method for an autonomous driving vehicle as described in any one of the above embodiments.

[0033] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0034] The hardware troubleshooting method, device, medium and computer equipment for an autonomous driving vehicle provided in the present application can first obtain the fault code corresponding to the hardware fault when the autonomous driving vehicle detects a hardware fault during the current hardware inspection process, and match the fault code with the fault code in a preset fault diagnosis file. Since the fault diagnosis file contains solutions corresponding to different fault codes, and there are multiple types of solutions, after screening out the solution that matches the fault code from the preset fault diagnosis file, the hardware troubleshooting of the autonomous driving vehicle can be directly performed according to the solution and the corresponding solution type. This method of solving hardware fault problems through fault diagnosis files can greatly reduce the number of manual troubleshooting, reduce labor costs, and release manpower, and can also improve the troubleshooting efficiency of hardware faults, thereby effectively ensuring the normal operation of the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0036] Figure 1 A flowchart of a hardware troubleshooting method for an autonomous vehicle provided in an embodiment of the present application;

[0037] Figure 2 A schematic diagram of the process of troubleshooting an autonomous vehicle based on the solution type provided in an embodiment of the present application;

[0038] Figure 3 A schematic diagram of the structure of a hardware troubleshooting device for an autonomous vehicle provided in an embodiment of the present application

[0039] Figure 4 A schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0041] Currently, when checking the hardware of an autonomous vehicle, if a hardware failure is encountered, the safety officer in the autonomous vehicle will contact the monitoring platform so that the engineers on the monitoring platform can analyze the hardware failure and provide a solution. This process is relatively cumbersome, and there is a certain delay in manual connection, which results in the hardware failure on the vehicle side not being resolved in time, affecting the normal travel of the vehicle. Based on this, this application proposes the following technical solutions, which are detailed below:

[0042] In one embodiment, Figure 1 As shown, Figure 1 This is a flowchart of a hardware troubleshooting method for an autonomous vehicle provided in an embodiment of the present application. The present application provides a hardware troubleshooting method for an autonomous vehicle, which may include:

[0043] S110: When the autonomous driving vehicle detects a hardware fault during the current hardware inspection process, a fault code corresponding to the hardware fault is obtained.

[0044] In this step, the autonomous vehicle generally performs a hardware check on the autonomous driving system before starting it to ensure the normal operation of the autonomous vehicle. In this application, when the autonomous vehicle detects a hardware fault during the current hardware check, the corresponding fault code can be obtained and matched with the corresponding solution based on the fault code.

[0045] It is understandable that an autonomous vehicle is a comprehensive system that integrates environmental perception, planning and decision-making, and multi-level assisted driving. It uses computers, modern sensors, information fusion, communications, artificial intelligence, and automatic control technologies. In order to ensure the normal and stable operation of an autonomous vehicle, a hardware check is usually performed before the vehicle is started. If the check passes, the word [OK] is usually output. If the check fails, the following output is usually given: <error>Fields such as "PCANinterface cannot be detected" appear on the vehicle display. When a safety officer in an autonomous vehicle discovers a hardware fault, they can click the diagnostic tool to diagnose it and receive a specific solution.

[0046] Furthermore, autonomous vehicles generally have a hardware and software self-check function. Before the autonomous driving system of an autonomous vehicle is activated, the autonomous driving system can use this hardware self-check function to check the hardware information currently in the vehicle. For example, autonomous vehicles are equipped with a variety of sensors, cameras, radars, GPS, and other devices. Before the vehicle is activated, the autonomous driving system can send relevant instructions to each hardware device. If one or more hardware devices do not receive the instructions or receive incorrect instructions, the autonomous driving system can determine that there is a hardware fault in the hardware device and then generate a corresponding fault code. The diagnostic tool can then interpret the fault code to identify the possible cause and location of the fault and provide an effective solution.

[0047] S120: Filter out a solution that matches the fault code from a preset fault diagnosis file.

[0048] In this step, after obtaining the fault code corresponding to the hardware fault in S110, the fault code can be matched with the fault codes in the preset fault diagnosis file. Since the fault diagnosis file contains solutions corresponding to different fault codes, and there are multiple types of solutions, by matching the fault code corresponding to the current hardware fault with the fault codes in the fault diagnosis file, the corresponding solution and corresponding solution type can be obtained in a timely manner.

[0049] Specifically, when matching the fault code of the current hardware fault with the fault code in the fault diagnosis file, the present application may perform regular expression matching on the fault code of the current hardware fault with each fault code in the fault diagnosis file in sequence. The specific regular expression matching method is not limited herein. If the regular expression matching is successful, it indicates that the current fault diagnosis file contains a fault code corresponding to the fault code of the current hardware fault. If the regular expression matching fails, it indicates that the current fault diagnosis file does not contain a fault code corresponding to the fault code of the current hardware fault.

[0050] The fault diagnosis file of this application is obtained by summarizing the hardware faults and corresponding solutions found in the previous hardware inspection process and writing them into the yml configuration file. Therefore, this fault diagnosis file can effectively solve most hardware faults. Of course, the fault diagnosis file of this application can also support operations such as adding, modifying, and deleting, which can provide a more effective solution for subsequent hardware troubleshooting.

[0051] S130: Perform hardware troubleshooting on the autonomous driving vehicle based on the screened solutions and corresponding solution types.

[0052] In this step, after matching the fault code with the fault code in the preset fault diagnosis file through S120, if the match is successful, it means that there is a fault code corresponding to the fault code of this hardware fault in the current fault diagnosis file. At this time, the solution corresponding to the matched fault code in the fault diagnosis file can be obtained, and the autonomous driving vehicle can be troubleshooted according to the solution type.

[0053] Specifically, after obtaining the solution corresponding to the fault code that has been successfully matched in the fault diagnosis file, the present application will use different solution types, and the specific solution processes of solutions of different solution types are somewhat different. For example, some solutions only need to provide specific solutions, and the safety officer can perform corresponding operations according to the solution to troubleshoot the autonomous vehicle, while some solutions require further inspection to determine the specific cause of the fault and provide a suitable solution. Therefore, after obtaining the solution corresponding to the fault code, the autonomous vehicle can be troubleshooted according to the solution type, thereby reducing manual troubleshooting, effectively improving troubleshooting efficiency, and ensuring normal vehicle travel.

[0054] In the above embodiment, when the autonomous driving vehicle detects a hardware fault during the current hardware inspection process, the fault code corresponding to the hardware fault can be obtained first, and the fault code can be matched with the fault code in the preset fault diagnosis file. Since the fault diagnosis file contains solutions corresponding to different fault codes, and there are multiple types of solutions, after screening out the solution that matches the fault code from the preset fault diagnosis file, the hardware troubleshooting of the autonomous driving vehicle can be directly performed according to the solution and the corresponding solution type. This method of solving hardware fault problems through fault diagnosis files can greatly reduce the number of manual troubleshooting, reduce labor costs, and release manpower, and can also improve the troubleshooting efficiency of hardware faults, thereby effectively ensuring the normal operation of the vehicle.

[0055] In one embodiment, obtaining the fault code corresponding to the hardware fault in S110 may include:

[0056] S111: Obtain the hardware log generated by the autonomous driving vehicle when performing hardware inspection.

[0057] S112: Reading a fault code corresponding to the hardware fault through the hardware log.

[0058] In this embodiment, when the autonomous driving vehicle detects a hardware fault during the current hardware inspection process, the fault code corresponding to the hardware fault can be obtained, and the corresponding solution can be matched based on the fault code.

[0059] Specifically, this application can start hw_check to check for hardware problems when the autonomous driving vehicle starts the system. If the check passes, it will generally output the word [OK]. If the check fails, it will generally output the word [OK]. <error>Based on this, this application can obtain the hardware logs generated by the autonomous vehicle during hardware inspection and use grep <error>Operation, all the corresponding ERRORs in the hardware log are filtered out, and then, the application can extract the corresponding fault code from the filtered ERROR field to obtain the fault code corresponding to the hardware fault.

[0060] It can be understood that when the present application performs a hardware inspection on an autonomous driving vehicle and obtains fault codes through the hardware log generated during the hardware inspection, if there are multiple hardware faults, the fault codes corresponding to multiple hardware faults can be obtained at the same time, and each fault code can be matched with the fault code in the fault diagnosis file respectively. If there is only one hardware fault, the fault code corresponding to the hardware fault can be directly matched with the fault code in the fault diagnosis file.

[0061] In one embodiment, there is at least one hardware fault; when there are multiple hardware faults, and at least two fault codes corresponding to the multiple hardware faults match solutions, S120 may include filtering out solutions matching the fault codes from a preset fault diagnosis file:

[0062] S121: Acquire multiple solutions corresponding to each successfully matched fault code and the priority corresponding to each solution from a preset fault diagnosis file.

[0063] S122: Determine a solution with the highest priority among the solutions according to the priorities of the solutions, and use the solution with the highest priority as the solution that matches the fault code and is screened from the fault diagnosis file.

[0064] In this embodiment, when there are multiple hardware faults and at least two fault codes corresponding to the multiple hardware faults match corresponding solutions, this application can obtain multiple solutions corresponding to each successfully matched fault code and the priority corresponding to each solution from a preset fault diagnosis file, and select the solution with the highest priority among all solutions based on the priority of each solution, and then use the solution with the highest priority as the solution corresponding to the successfully matched fault code in the fault diagnosis file, and use this solution to perform hardware troubleshooting on the autonomous driving vehicle.

[0065] For example, after the present application obtains multiple solutions corresponding to each successfully matched fault code and the priority corresponding to each solution from the preset fault diagnosis file, each solution can be sorted according to the priority of each solution, and the solution with the highest priority can be selected as the final solution. For example, when the solutions obtained by the present application include restarting the card, restarting the computer, and restarting with the engine off, and restarting the card has the lowest priority and restarting with the engine off has the highest priority, the solution with a high priority can cover the solution with a low priority. In other words, after selecting the solution of restarting with the engine off, the hardware failures of both can be solved without restarting the card or restarting the computer. Therefore, when there are multiple solutions, and there is a solution with the highest priority among the multiple solutions, the solution with the highest priority can be selected as the final solution to perform hardware troubleshooting on the autonomous driving vehicle, thereby reducing troubleshooting time and improving troubleshooting efficiency.

[0066] In one embodiment, Figure 2 As shown, Figure 2 A schematic diagram of a process for troubleshooting an autonomous vehicle based on the solution type provided in an embodiment of the present application; S130 of troubleshooting hardware of the autonomous vehicle based on the screened solution and the corresponding solution type may include:

[0067] S131: If the solution type of the screened solution is a direct solution type, the solution is directly sent to the safety officer in the autonomous driving vehicle, so that the safety officer can troubleshoot the autonomous driving vehicle according to the solution;

[0068] S132: If the solution type of the screened solution is an indirect solution type, the hardware of the autonomous driving vehicle is re-checked according to the solution content, and when it is determined that the autonomous driving vehicle has detected a hardware fault during the current hardware inspection process, the process returns to execute S110 to S130.

[0069] In this embodiment, after obtaining the solution corresponding to the matching fault code in the fault diagnosis file, since the solutions are divided into different solution types and the specific solution processes of solutions of different solution types are somewhat different, the application can troubleshoot the autonomous driving vehicle according to the solution type.

[0070] Specifically, if Figure 2 As shown, if the solution type obtained is a direct solution type, the solution can be directly sent to the safety officer of the autonomous driving vehicle, and the safety officer can perform corresponding operations based on the solution to troubleshoot the autonomous driving vehicle; if the solution type obtained is an indirect solution type, the hardware of the autonomous driving vehicle can be re-checked according to the solution content of the solution, and when the autonomous driving vehicle detects a hardware fault, the fault code corresponding to the hardware fault is re-obtained, and the fault code is matched with the fault code in the fault diagnosis file. If the match is successful, the corresponding solution is obtained, and the autonomous driving vehicle is troubleshooted according to the solution type. If the match fails, the fault code is reported to the monitoring platform so that the monitoring platform can perform remote troubleshooting based on the fault code.

[0071] In one embodiment, re-checking the hardware of the autonomous driving vehicle according to the solution in S132 may include:

[0072] S1321: Obtain the inspection method set in the solution content of the solution.

[0073] S1322: Re-inspect the hardware of the autonomous driving vehicle according to the inspection method.

[0074] In this embodiment, when re-checking the hardware of the autonomous driving vehicle using the solution content of the obtained solution, the inspection method set in the solution content can be obtained first, and the hardware of the autonomous driving vehicle can be re-checked according to the inspection method, so as to obtain new fault codes and then match them with the fault diagnosis file.

[0075] For example, if the solution corresponding to the matching fault code in the acquired fault diagnosis file is displayed as "NEXT_CHECK_FUNCTION / NEXT_CHECK_LOG", it indicates that further inspection is required to confirm the specific solution. At this time, the corresponding preset method under "NEXT CHECK FUNCTION / NEXT CHECK LOG" will be automatically triggered to check. When a new fault code is found, the fault code matching operation will be carried out. Furthermore, the preset method here can be set according to the actual situation and is not limited here.

[0076] In one embodiment, the method may further include:

[0077] S140: When there is no solution matching the fault code in the fault diagnosis file, the fault code is reported to the monitoring platform so that the monitoring platform can perform remote troubleshooting based on the fault code.

[0078] In this embodiment, after the fault code is matched with the fault code in the preset fault diagnosis file through S120, if the match fails, it means that the fault code corresponding to the fault code of this hardware fault does not exist in the current fault diagnosis file. At this time, the fault code can be reported directly to the monitoring platform, or the result of the matching failure can be sent to the safety officer in the autonomous driving vehicle, and the fault code can be reported to the monitoring platform after the safety officer confirms it. Alternatively, the safety officer can also actively report the fault code to the corresponding hardware engineer in the monitoring platform, so that the hardware engineer in the monitoring platform can remotely troubleshoot the autonomous driving vehicle based on the fault code.

[0079] In the above embodiment, when the autonomous vehicle detects a hardware fault during the current hardware inspection process, the fault code corresponding to the hardware fault can be first obtained and matched with the fault code in the preset fault diagnosis file. Since the fault diagnosis file contains solutions corresponding to different fault codes, if the fault code successfully matches the fault code in the fault diagnosis file, it means that the fault diagnosis file contains a solution corresponding to the matched fault code. In this case, the autonomous vehicle can be directly troubleshooted according to the solution type of the solution, thereby effectively improving work efficiency. Furthermore, if the match fails, it means that the fault diagnosis file does not contain a solution corresponding to the fault code. In this case, the fault code can be reported to the monitoring platform so that engineers on the monitoring platform can perform remote troubleshooting based on the fault code. In this way, most hardware fault problems can be solved through the fault diagnosis file, reducing the number of manual troubleshooting, reducing labor costs, and freeing up manpower. In addition, when the fault diagnosis file cannot solve a small number of hardware fault problems, the hardware fault problem on the vehicle side can be promptly solved through remote troubleshooting, thereby effectively ensuring the normal operation of the vehicle.

[0080] In one embodiment, the method may further include:

[0081] S150: Adding the remote troubleshooting solution and the fault code to the fault diagnosis file to update the fault diagnosis file.

[0082] In this embodiment, when the fault code of the hardware fault fails to match the fault code in the fault diagnosis file, remote troubleshooting can be performed through the monitoring platform. After the remote troubleshooting is completed, this application can add the solution for remote troubleshooting and the corresponding fault code to the fault diagnosis file so as to update the fault diagnosis file. The updated fault diagnosis file can solve more hardware fault problems, thereby effectively improving the troubleshooting efficiency of hardware faults.

[0083] The hardware troubleshooting device for an autonomous driving vehicle provided in an embodiment of the present application is described below. The hardware troubleshooting device for an autonomous driving vehicle described below and the hardware troubleshooting method for an autonomous driving vehicle described above can be referenced to each other.

[0084] In one embodiment, Figure 3 As shown, Figure 3 This is a schematic diagram of the structure of a hardware troubleshooting device for an autonomous vehicle provided in an embodiment of the present application. The present application also provides a hardware troubleshooting device for an autonomous vehicle, including a fault code acquisition module 210, a solution determination module 220, and a hardware troubleshooting module 230, specifically including the following:

[0085] The fault code acquisition module 210 is used to obtain the fault code corresponding to the hardware fault when the autonomous driving vehicle detects a hardware fault during the current hardware inspection process;

[0086] A solution determination module 220 is configured to select a solution matching the fault code from a preset fault diagnosis file, wherein the fault diagnosis file stores solutions corresponding to different fault codes, and the solutions may be of various types.

[0087] The hardware troubleshooting module 230 is used to perform hardware troubleshooting on the autonomous driving vehicle based on the screened solutions and corresponding solution types.

[0088] In the above embodiment, when the autonomous driving vehicle detects a hardware fault during the current hardware inspection process, the fault code corresponding to the hardware fault can be obtained first, and the fault code can be matched with the fault code in the preset fault diagnosis file. Since the fault diagnosis file contains solutions corresponding to different fault codes, and there are multiple types of solutions, after screening out the solution that matches the fault code from the preset fault diagnosis file, the hardware troubleshooting of the autonomous driving vehicle can be directly performed according to the solution and the corresponding solution type. This method of solving hardware fault problems through fault diagnosis files can greatly reduce the number of manual troubleshooting, reduce labor costs, and release manpower, and can also improve the troubleshooting efficiency of hardware faults, thereby effectively ensuring the normal operation of the vehicle.

[0089] In one embodiment, the fault code acquisition module 210 includes:

[0090] A hardware log acquisition module, configured to acquire hardware logs generated by the autonomous driving vehicle when performing hardware inspection;

[0091] The fault code reading module is used to read the fault code corresponding to the hardware fault through the hardware log.

[0092] In one embodiment, there is at least one hardware fault; when there are multiple hardware faults and at least two fault codes corresponding to the multiple hardware faults match solutions, the solution determination module 220 includes:

[0093] The solution acquisition module is used to obtain multiple solutions corresponding to each successfully matched fault code and the priority corresponding to each solution from a preset fault diagnosis file.

[0094] The solution selection module is used to determine the solution with the highest priority among the solutions according to the priorities of the solutions, and use the solution with the highest priority as the solution that matches the fault code screened from the fault diagnosis file.

[0095] In one embodiment, the hardware troubleshooting module 230 includes:

[0096] The first troubleshooting module is used to directly send the solution to the safety officer in the autonomous driving vehicle if the solution type of the screened solution is a direct solution type, so that the safety officer can perform hardware troubleshooting on the autonomous driving vehicle according to the solution.

[0097] The second troubleshooting module is used to re-check the hardware of the autonomous driving vehicle based on the content of the solution if the solution type of the screened solution is an indirect solution type, and return to the step of obtaining the fault code corresponding to the hardware fault when it is determined that the autonomous driving vehicle detects a hardware fault during the current hardware inspection process.

[0098] In one embodiment, the second troubleshooting module includes:

[0099] The inspection method acquisition module is used to obtain the inspection method set in the solution content of the solution.

[0100] A hardware inspection module is used to re-inspect the hardware of the autonomous driving vehicle according to the inspection method.

[0101] In one embodiment, the apparatus may further include:

[0102] The remote troubleshooting module is used to report the fault code to the monitoring platform when there is no solution matching the fault code in the fault diagnosis file, so that the monitoring platform can perform remote troubleshooting based on the fault code.

[0103] In one embodiment, the apparatus may further include:

[0104] The fault diagnosis file update module is used to add the solution for remote troubleshooting and the fault code to the fault diagnosis file to update the fault diagnosis file.

[0105] In one embodiment, the present application also provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the hardware troubleshooting method for an autonomous driving vehicle as described in any of the above embodiments.

[0106] In one embodiment, the present application further provides a computer device, including: one or more processors, and a memory.

[0107] The memory stores computer-readable instructions, which, when executed by the one or more processors, execute the steps of the hardware troubleshooting method for an autonomous driving vehicle as described in any one of the above embodiments.

[0108] Schematically, as Figure 4 As shown, Figure 4 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. The computer device 300 can be provided as a server. Figure 4 Computer device 300 includes a processing component 302, which further includes one or more processors, and a memory resource represented by memory 301 for storing instructions executable by processing component 302, such as an application. The application stored in memory 301 may include one or more modules, each corresponding to a set of instructions. In addition, processing component 302 is configured to execute the instructions to perform the hardware troubleshooting method for an autonomous vehicle according to any of the above embodiments.

[0109] The computer device 300 may further include a power supply component 303 configured to perform power management of the computer device 300, a wired or wireless network interface 304 configured to connect the computer device 300 to a network, and an input / output (I / O) interface 305. The computer device 300 may operate based on an operating system stored in the memory 301, such as Windows Server™, Mac OS X™, Unix™, Linux™, Free BSD™, or the like.

[0110] Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0111] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprise," "include," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus comprising a set of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising the element.

[0112] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can be referenced to each other.

[0113] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present application. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.< / error> < / error> < / error>

Claims

1. A method for troubleshooting hardware of an autonomous vehicle, characterized in that: The method comprises: When the autonomous driving vehicle detects a hardware fault during the current hardware check process, obtaining a fault code corresponding to the hardware fault; Screening out a solution that matches the fault code from a preset fault diagnosis file, wherein the fault diagnosis file stores solutions corresponding to different fault codes, and the solutions may be of multiple types; Perform hardware troubleshooting on the autonomous vehicle based on the screened solutions and corresponding solution types, including: If the solution type of the screened solution is a direct solution type, the solution is directly sent to the safety officer in the autonomous driving vehicle, so that the safety officer can perform hardware troubleshooting on the autonomous driving vehicle according to the solution; If the solution type of the screened solution is an indirect solution type, the hardware of the autonomous driving vehicle is re-checked based on the solution content, and when it is determined that the autonomous driving vehicle has detected a hardware fault during the current hardware inspection process, the step of obtaining the fault code corresponding to the hardware fault is returned to.

2. The hardware troubleshooting method for an autonomous driving vehicle according to claim 1, characterized in that: The obtaining of the fault code corresponding to the hardware fault includes: Obtaining a hardware log generated by the autonomous driving vehicle during hardware inspection; The fault code corresponding to the hardware fault is read through the hardware log.

3. The hardware troubleshooting method for an autonomous driving vehicle according to claim 1, characterized in that: There is at least one hardware failure; When there are multiple hardware faults and at least two fault codes corresponding to the multiple hardware faults match solutions, screening out solutions matching the fault codes from a preset fault diagnosis file includes: Obtaining multiple solutions corresponding to each successfully matched fault code and the priority corresponding to each solution from a preset fault diagnosis file; A solution with the highest priority among the solutions is determined according to the priorities of the solutions, and the solution with the highest priority is used as the solution that matches the fault code and is screened from the fault diagnosis file.

4. The hardware troubleshooting method for an autonomous driving vehicle according to claim 1, wherein: The re-inspection of the hardware of the autonomous driving vehicle according to the solution includes: Get the check method set in the solution content of the solution; Re-inspect the hardware of the autonomous driving vehicle according to the inspection method.

5. The hardware troubleshooting method for an autonomous driving vehicle according to any one of claims 1 to 4, characterized in that: The method further comprises: When there is no solution matching the fault code in the fault diagnosis file, the fault code is reported to the monitoring platform so that the monitoring platform can perform remote troubleshooting based on the fault code.

6. The method for troubleshooting hardware of an autonomous driving vehicle according to claim 5, characterized in that: The method further comprises: The solution for remote troubleshooting and the fault code are added to the fault diagnosis file to update the fault diagnosis file.

7. A hardware troubleshooting device for an autonomous driving vehicle, characterized in that: include: A fault code acquisition module is used to obtain a fault code corresponding to a hardware fault when the autonomous driving vehicle detects a hardware fault during the current hardware check process; A solution determination module is used to filter out a solution that matches the fault code from a preset fault diagnosis file, wherein the fault diagnosis file stores solutions corresponding to different fault codes, and the solutions may be of multiple types; The hardware troubleshooting module is used to perform hardware troubleshooting on the autonomous driving vehicle based on the screened solutions and corresponding solution types, including: If the solution type of the screened solution is a direct solution type, the solution is directly sent to the safety officer in the autonomous driving vehicle, so that the safety officer can perform hardware troubleshooting on the autonomous driving vehicle according to the solution; If the solution type of the screened solution is an indirect solution type, the hardware of the autonomous driving vehicle is re-checked based on the solution content, and when it is determined that the autonomous driving vehicle has detected a hardware fault during the current hardware inspection process, the step of obtaining the fault code corresponding to the hardware fault is returned to.

8. A storage medium, characterized in that: The storage medium stores computer-readable instructions, which, when executed by one or more processors, cause the one or more processors to execute the steps of the hardware troubleshooting method for an autonomous driving vehicle as described in any one of claims 1 to 6.

9. A computer device, characterized in that: include: one or more processors, and memory; The memory stores computer-readable instructions, which, when executed by the one or more processors, execute the steps of the hardware troubleshooting method for an autonomous driving vehicle as described in any one of claims 1 to 6.

Images