Automobile fault detection method, device and equipment and storage medium

Abstract

The invention discloses an automobile fault detection method, device and equipment and a storage medium, and relates to the field of automobile electronic control, and the method comprises the steps: obtaining fault information when a fault is monitored; determining a fault type corresponding to the fault based on the fault information, wherein the fault type comprises an operating system fault, an abnormal interruption fault and an error tracking fault; the target analysis strategy is determined based on the fault type to analyze and process the fault, fault state information is quickly positioned, and stable operation and driving safety of an automobile software system are ensured.

Description

Technical Field

[0001] The present invention relates to the field of automobile electronic control, and in particular to an automobile fault detection method, device, equipment and storage medium. Background Art

[0002] As the complexity and functional integration of automotive electronic control systems have increased significantly, the complexity of the software layer has increased dramatically. For embedded systems, this trend means that when the software encounters anomalies or failures during vehicle operation, traditional debugging methods often make it difficult to quickly and accurately locate the root cause of the problem.

[0003] Therefore, building an efficient fault location mechanism and implementing immediate fault handling measures have become urgent needs to ensure driving safety and improve user experience.

[0004] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of the present invention is to provide a method, device, equipment and storage medium for automobile fault detection, aiming to solve the technical problem that the root cause of the fault cannot be quickly and accurately located.

[0006] To achieve the above object, the present invention provides a method for detecting a vehicle fault, the method comprising the following steps:

[0007] When a fault is detected, obtain fault information;

[0008] Determine the fault type corresponding to the fault based on the fault information, wherein the fault type includes operating system fault, abnormal interrupt fault and error tracking fault;

[0009] A target analysis strategy is determined based on the fault type to analyze and handle the fault.

[0010] In one embodiment, the step of determining a target analysis strategy based on the fault type to analyze and handle the fault includes:

[0011] When the fault is an operating system fault, determining that the target analysis strategy is a contextual relationship analysis strategy, calling the contextual relationship analysis strategy to analyze the fault, and obtaining context information of the fault;

[0012] Determine a fault scope based on the fault information and the context information, and isolate devices within the fault scope;

[0013] After the isolation is completed, a soft reset operation is performed on the system, the system is restarted and the fault information and the context information are stored.

[0014] In one embodiment, after the step of invoking the context relationship analysis strategy to analyze the fault and obtaining the context information of the fault, the method further includes:

[0015] Generate an error log based on the fault information and the context information, and optimize the system through the error log;

[0016] The step of performing a soft reset operation on the system, restarting the system and storing the fault information and the context information further includes:

[0017] Perform a soft reset operation on the system, restart the system and store the error log.

[0018] In one embodiment, when the fault is an operating system fault, determining the target analysis strategy as a contextual relationship analysis strategy, determining the target analysis strategy as a contextual relationship analysis strategy, calling the contextual relationship analysis strategy to analyze the fault, and obtaining the context information of the fault includes:

[0019] When the fault is an operating system fault, determining that the target analysis strategy is a context relationship analysis strategy, calling the context relationship analysis strategy to read the depth of the traceable context, and reading the context pointer in the register;

[0020] When the depth is not the first preset value, storing the address information corresponding to the context pointer;

[0021] When the depth reaches the first preset value, context information of the fault is generated based on the stored address information.

[0022] In one embodiment, the step of determining a target analysis strategy based on the fault type to analyze and handle the fault includes:

[0023] When the fault is an abnormal interruption fault, determining the target analysis strategy to be an abnormal interruption analysis strategy;

[0024] Calling the abnormal interrupt analysis strategy to obtain the interrupt vector number, abnormal address, machine state and stack frame content of the abnormal interrupt fault;

[0025] After the isolation is completed, a soft reset operation is performed on the system, the system is restarted, and the fault information and the interrupt vector number, exception address, machine state and stack frame content of the abnormal interrupt fault are stored.

[0026] In one embodiment, the step of determining a target analysis strategy based on the fault type to analyze and handle the fault includes:

[0027] When the fault is an error tracking fault, determining the target analysis strategy to be an error tracking analysis strategy;

[0028] The error tracking analysis strategy is called to store the fault information of the error tracking fault, and the fault handling process is ended.

[0029] In one embodiment, after the step of determining a target analysis strategy based on the fault type to analyze and handle the fault, the method further includes:

[0030] The corresponding fault light is lit based on the fault type to prompt the user to perform fault detection.

[0031] In addition, to achieve the above-mentioned purpose, the present invention also provides a vehicle fault detection device, the device comprising:

[0032] An information acquisition module is used to obtain fault information when a fault is detected;

[0033] A fault determination module, configured to determine a fault type corresponding to the fault based on the fault information, wherein the fault type includes an operating system fault, an abnormal interruption fault, and an error tracking fault;

[0034] The fault processing module is used to determine a target analysis strategy based on the fault type to analyze and process the fault.

[0035] In addition, to achieve the above-mentioned purpose, the present invention also proposes a vehicle fault detection device, which includes: a memory, a processor, and a vehicle fault detection program stored in the memory and executable on the processor, wherein the vehicle fault detection program is configured to implement the steps of the vehicle fault detection method described above.

[0036] In addition, to achieve the above-mentioned purpose, the present invention also proposes a storage medium, on which a car fault detection program is stored, and when the car fault detection program is executed by a processor, the steps of the car fault detection method described above are implemented.

[0037] One or more technical solutions proposed in this application have at least the following technical effects:

[0038] When a fault is detected, the fault information is obtained; based on the fault information, the fault type corresponding to the fault is determined, where the fault types include operating system failures, abnormal interrupt failures, and error tracking failures; based on the fault type, the target analysis strategy is determined to analyze and handle the fault, quickly locate the fault status information, and ensure the stable operation of the automotive software system and driving safety. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

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

[0041] Figure 1 A schematic diagram of a process flow provided for the first embodiment of the automobile fault detection method of the present application;

[0042] Figure 2 A flowchart of starting a fault light provided in Embodiment 1 of the automobile fault detection method of the present application;

[0043] Figure 3 A processing flow chart provided for the first embodiment of the automobile fault detection method of the present application;

[0044] Figure 4 A flow chart of the second embodiment of the vehicle fault detection method of the present application;

[0045] Figure 5 A context analysis flow chart provided for the second embodiment of the automobile fault detection method of the present application;

[0046] Figure 6 A flow chart of the third embodiment of the vehicle fault detection method of the present application;

[0047] Figure 7 This is a schematic diagram of the module structure of the automobile fault detection device according to an embodiment of the present application;

[0048] Figure 8 Schematic diagram of the device structure of the hardware operating environment involved in the automobile fault detection method in the embodiment of the present application.

[0049] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0050] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0051] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0052] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, an automobile fault detection device, etc. The following takes the automobile fault detection device as an example to illustrate this embodiment and the following embodiments.

[0053] Based on this, the present application embodiment provides a method for detecting vehicle faults. Figure 1 , Figure 1 This is a flow chart of the first embodiment of the automobile fault detection method of the present application.

[0054] In this embodiment, the vehicle fault detection method includes steps S10 to S30:

[0055] Step S10, when a fault is detected, obtaining fault information;

[0056] It should be noted that this strategy is applied to an automobile software fault monitoring and immediate alarm system. The system will monitor the software running status in real time. When a software fault is detected, the fault type will be classified and then handed over to the fault handling center for processing. The fault handling center will handle it according to different fault types. After processing, the data and on-site information will be stored, and then the fault information will be reported to the diagnosis module. The diagnosis module will give corresponding reminders to the user by lighting up the fault light and other means.

[0057] It should be understood that the fault information is a union, which is defined as shown in the following table:

[0058] Table 1

[0059] Fault type ID information Operating system fault structure (including error type, passed parameters, and context information) Exception interrupt structure (including interrupt vector, incoming parameters, context information) Other fault structures (including module ID, input parameters and context information)

[0060] Taking operating system failure as an example, the definition of the corresponding structure is shown in Table 2 below:

[0061] Table 2

[0062] Operating system fault structure Fault ID Service ID Operating system records fault parameters Fault Status Context address array

[0063] When a fault occurs, the corresponding information will be written into the corresponding element of the structure, where the context address is an array to save the backtracking address information.

[0064] In the specific implementation, the system will monitor the fault information in real time during operation. If a fault is determined to have occurred, the information at the time of the fault will be read.

[0065] Step S20, determining the fault type corresponding to the fault based on the fault information, wherein the fault type includes operating system fault, abnormal interrupt fault and error tracking fault;

[0066] It should be noted that other faults in the union table are error tracking faults.

[0067] In embedded software systems, real-time operating systems (RTOS) are essential for accurate execution and efficient scheduling of tasks. When the system encounters abnormal situations such as stack overflow, excessive CPU load leading to frequent task reentry, etc., the operating system will report these operating system failures to inform the system to handle them and ensure system stability and reliability.

[0068] When an embedded system faces abnormal situations such as non-maskable interrupts, instruction execution errors, memory access violations, etc., it will immediately trigger a specific type of abnormal interrupt. Each abnormal interrupt is designed to have its own unique entry point to ensure that when the system detects an abnormality, it can accurately jump to the corresponding interrupt service routine (ISR) to handle the abnormal interrupt fault.

[0069] Error tracking faults refer to some fault information that does not affect the function and safety during the operation of the software, such as some error information that appears during the operation of the basic software program. At this time, the software will not be reset, and only the data and information on site will be stored.

[0070] Step S30: determining a target analysis strategy based on the fault type to analyze and handle the fault.

[0071] It should be noted that once the fault type is determined, the next step is to select a targeted analysis strategy to collect data and information.

[0072] It should be understood that the target analysis strategy may include a context analysis strategy, an abnormal interruption analysis strategy, and an error tracking analysis strategy.

[0073] In the specific implementation, according to different fault characteristics or categories, specific analysis methods are selected and implemented to diagnose the problem, and corresponding measures are taken to solve the fault.

[0074] Furthermore, after step S30, the method further includes:

[0075] The corresponding fault light is lit based on the fault type to prompt the user to perform fault detection.

[0076] It should be noted that the fault handling center will periodically read the fault information and analyze the fault. If the corresponding fault mark is set, the fault will be managed through diagnostic event management, and then the corresponding fault light will be lit to prompt the user to perform fault detection.

[0077] like Figure 2As shown, the software monitoring module periodically reads fault information to determine whether a fault occurs. If so, the fault is analyzed and reported to the diagnostic event module according to different fault reports. The diagnostic event module then lights up the fault light according to the type of fault.

[0078] In a specific implementation, the fault information is reported to the diagnosis module, and the diagnosis module gives corresponding reminders to the user by lighting up the fault light or the like.

[0079] like Figure 3 As shown, Figure 3 To process the flow chart, first the system is in operation and monitoring state. When an abnormality is detected, the fault type is determined, including operating system fault, software abnormality fault and other types of faults. The fault status and related information are read, and then the stack backtrace is processed to read the function call relationship. Then the data assignment and key component output are turned off, and then the data is written to the NOINITRAM area and a soft reset is performed. After reinitialization, the fault information is read and stored, and the fault is reported to the alarm module. The fault alarm module classifies and determines the fault, alarms and performs function downgrade processing.

[0080] Not only does the detection accuracy rate is high, but it can also accurately locate the position of the software when a fault occurs. Even if a fault occurs during vehicle operation, the data can be saved and traced back. At the same time, there is an alarm system to remind users to check the relevant control systems.

[0081] This embodiment provides a method for automobile fault detection, which integrates online fault monitoring, deep data analysis, and intelligent processing mechanisms, and is supplemented by efficient data storage and flexible call functions to build a comprehensive and systematic solution. This solution aims to monitor the bottleneck of insufficient software security in the existing technology, quickly locate the fault status information, and ensure the stable operation and driving safety of the automobile software system.

[0082] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 4 , step S30, the automobile fault detection method comprises steps S301 to S303:

[0083] Step S301, when the fault is an operating system fault, determining that the target analysis strategy is a contextual relationship analysis strategy, calling the contextual relationship analysis strategy to analyze the fault, and obtaining contextual information of the fault;

[0084] It should be noted that in embedded software systems, real-time operating systems (RTOS) are crucial for accurate execution and efficient scheduling of tasks. When the system encounters abnormal situations such as stack overflow, excessive CPU load leading to frequent task reentry, etc., the operating system will report these faults to inform the system to handle them and ensure the stability and reliability of the system.

[0085] When the system detects an abnormal situation such as stack overflow, CPU overload, etc., the RTOS immediately triggers the fault hook function. This function is designed to respond quickly and preliminarily evaluate the nature of the fault. At this time, it can be determined that the fault is an operating system fault.

[0086] In the fault hook function, a protected read of key data is first performed, including but not limited to the fault type identification and the CPU register state when the exception occurs (especially the program counter, which is used to locate the address of the exception instruction or the address of the next instruction after the interrupt). In addition, a system status snapshot may be collected for subsequent analysis.

[0087] It should be understood that the above data can all be stored in the fault information to facilitate subsequent analysis.

[0088] In the specific implementation, the function call context analysis strategy uses the stack backtracking principle to deeply analyze the function call context when the fault occurs and trace the specific function call path that caused the fault. This process is crucial for locating the root cause of the problem and optimizing software design. The backtracking results will be recorded in detail as part of the error log.

[0089] Furthermore, the step S301 includes:

[0090] When the fault is an operating system fault, the target analysis strategy is determined to be a context relationship analysis strategy, the context relationship analysis strategy is called to read the depth of the traceable context, and the context pointer in the register is read;

[0091] When the depth is not the first preset value, storing the address information corresponding to the context pointer;

[0092] When the depth reaches a first preset value, context information of the fault is generated based on the stored address information.

[0093] It should be noted that if a fault occurs during vehicle operation, for embedded systems, obtaining or saving fault information is crucial for subsequent analysis of the problem. The fault stack information backtracking mainly records the address of the time when the fault occurred and the address information of the previous function call, so as to quickly find and locate the fault.

[0094] The principle of context relationship analysis is to use the rules of function calls and the mechanism of context switching. The so-called context switching means that before the program calls a subroutine, some current information needs to be saved, such as register information, system status, etc. Generally, this information will be saved in the stack, but in some chips of embedded systems, the chip will allocate a part of the area to store this part of the content to improve memory usage efficiency and real-time performance.

[0095] In the specific implementation, context information backtracking is mainly based on the principle of stack allocation when the function is called, to find out the hierarchical relationship of function calls when an exception occurs. When a function is called, the process of context saving is as follows:

[0096] 1. Push the next instruction address onto the stack and call the function.

[0097] 2. Save the current stack bottom pointer.

[0098] 3. Save the scene.

[0099] In general chips, there is a register to store a linked list pointer, which points to the last saved context segment, which is the top of the call stack.

[0100] When a fault occurs, the context information needs to be traced back. First, read the depth of the traceable context, then read the context pointer of the register, determine whether the depth is 0, read the corresponding address information from the pointer, and save the corresponding address information to the corresponding array, and repeat this cycle until the depth is 0. The corresponding flowchart is as follows: Figure 5 shown.

[0101] Furthermore, after step S301, the method further includes:

[0102] Generate error logs based on fault information and context information, and optimize the system through error logs;

[0103] The step of performing a soft reset operation on the system, restarting the system and storing the fault information and context information also includes:

[0104] Perform a soft reset on the system, restart the system and save the error log.

[0105] In the specific implementation, the collected fault information, context information results and system status snapshots are integrated into detailed error logs. These logs are of great value for subsequent problem analysis, system maintenance and possible software upgrades.

[0106] Step S302, determining the fault range based on the fault information and context information, and isolating the devices within the fault range;

[0107] It should be noted that by analyzing the fault information and context information, the scope of system components or services that may be affected by the fault is determined. This may involve a single hardware component, software module, network connection, or the entire system. Once the scope of the fault is determined, the next step is to isolate the affected device or component from the system, which may include shutting down or disabling specific hardware devices, stopping or uninstalling problematic software services or applications, and blocking connections to the faulty component at the network level.

[0108] In the specific implementation, in order to prevent the fault from spreading further, the system will automatically shut down or isolate the affected output devices, peripheral interfaces and other key resources. At the same time, it ensures the security of core data and services to prevent data damage or leakage.

[0109] Step S303: after the isolation is completed, a soft reset operation is performed on the system, the system is restarted and the fault information and context information are stored.

[0110] It should be noted that developers can read the fault data at the time of fault occurrence from the saved data and parse the data to accurately locate the location where the fault occurred.

[0111] It should be understood that a soft reset operation is a restart method that does not involve hardware power outages, and restarts the operating system through software commands. A soft reset terminates all running processes and reinitializes system services and applications; during a soft reset, the system shuts down all services and applications, clears all data in memory, and then reloads the system's core components and drivers to start the system startup process, where fault information and context information can be stored on non-volatile storage media, such as a hard disk, solid-state drive, or a dedicated log server, to ensure that this information is still available after the system restarts.

[0112] In a specific implementation, after completing the above steps, the system performs a soft reset operation. Soft reset is intended to restart the system by software means while retaining necessary configuration and state information so that the system can restart in a more stable state. After reset, the system should be able to return to a known safe or initial state and try to re-execute the task.

[0113] This embodiment provides a method for detecting automobile faults. When an operating system fails, a target analysis strategy is determined to be a contextual relationship analysis strategy, and detailed context information of the fault is collected and analyzed to identify the root cause of the fault, and corresponding measures are taken to restore the normal operation of the system and prevent future faults from occurring.

[0114] Based on the first and second embodiments of the present application, in the third embodiment of the present application, the same or similar contents as those in the above embodiments can be referred to the above introduction, and will not be described in detail later. Figure 6 , step S30, the automobile fault detection method further includes steps S310 to S330:

[0115] Step S310, when the fault is an abnormal interruption fault, determining the target analysis strategy to be an abnormal interruption analysis strategy;

[0116] It should be noted that when an embedded system faces abnormal situations such as non-maskable interrupts, instruction execution errors, memory access violations, etc., a specific type of abnormal interrupt will be triggered immediately. Each abnormal interrupt is designed to have its own unique entry point to ensure that the system can accurately jump to the corresponding interrupt service routine (ISR) for processing when an abnormal interrupt failure is detected.

[0117] The interrupt handling process will be based on different interrupt vector numbers (a unique code that identifies a specific interrupt type), and the system can automatically select and execute the corresponding interrupt handling function. This process not only improves the efficiency of exception handling, but also enhances the response speed and stability of the system.

[0118] Step S320, calling the abnormal interrupt analysis strategy to obtain the interrupt vector number, abnormal address, machine state and stack frame content of the abnormal interrupt fault;

[0119] In the specific implementation, in the interrupt handling service function, the system will record the relevant information of the exception event in detail, including but not limited to the interrupt vector number, the precise address where the exception occurred, the CPU machine state (such as register values), and the current stack frame content.

[0120] Step S330, after the isolation is completed, a soft reset operation is performed on the system, the system is restarted and the fault information and the interrupt vector number, exception address, machine state and stack frame content of the abnormal interrupt fault are stored.

[0121] In specific implementations, after the collection and recording of abnormal information is completed, the system usually performs a soft reset operation. Soft reset aims to safely restart the system through software means while retaining key configuration and status information as much as possible so that the system can quickly recover to a stable and predictable state after restart. This step is very important for reducing system downtime and protecting data integrity.

[0122] Further, when the fault is an error tracking fault, determining the target analysis strategy as an error tracking analysis strategy;

[0123] The error tracking analysis strategy is called to store the fault information of the error tracking fault and end the fault handling process.

[0124] It should be noted that error tracking type failures refer to some fault information that does not affect the function and safety during the operation of the software, such as some error information that appears during the operation of the basic software program. At this time, the software will not be reset, and only the data and information on site will be stored.

[0125] It should be understood that there are three types of faults involving basic software in this system. The first is the fault of the operating system, the second is the fault of abnormal interruption, and the third is the fault of error tracking, which is the fault information monitored by the standard module DET (diagnostic fault tracking module) in AUTOSAR. When each fault occurs, it will enter a different function for processing, extract the fault information, write it into the corresponding structure, and then enter the next step of processing.

[0126] This embodiment provides an automobile fault detection method, which focuses on collecting, analyzing and storing error-related information through the judgment and processing flow of abnormal interruption faults and error tracking faults, so as to effectively identify the root cause of the fault and take corresponding repair measures, quickly locate the fault status information, and ensure the stable operation of the automobile software system and driving safety.

[0127] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the automobile fault detection method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0128] This application also provides a vehicle fault detection device, please refer to Figure 7 , the automobile fault detection device comprises:

[0129] The information acquisition module 10 is used to acquire fault information when a fault is detected.

[0130] The fault determination module 20 is used to determine the fault type corresponding to the fault based on the fault information, wherein the fault type includes operating system fault, abnormal interrupt fault and error tracking fault.

[0131] The fault processing module 30 is used to determine a target analysis strategy based on the fault type to analyze and process the fault.

[0132] The automobile fault detection device provided by the present application adopts the automobile fault detection method in the above embodiment, which can solve the technical problem of being unable to quickly and accurately locate the root cause of the fault. Compared with the prior art, the beneficial effects of the automobile fault detection device provided by the present application are the same as the beneficial effects of the automobile fault detection method provided by the above embodiment, and other technical features in the automobile fault detection device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0133] In one embodiment, the fault processing module 30 is further used to, when the fault is an operating system fault, determine that the target analysis strategy is a contextual relationship analysis strategy, call the contextual relationship analysis strategy to analyze the fault, and obtain context information of the fault;

[0134] Determine a fault scope based on the fault information and the context information, and isolate devices within the fault scope;

[0135] After the isolation is completed, a soft reset operation is performed on the system, the system is restarted and the fault information and the context information are stored.

[0136] In one embodiment, the fault processing module 30 is further used to generate an error log based on the fault information and the context information, and optimize the system through the error log;

[0137] The step of performing a soft reset operation on the system, restarting the system and storing the fault information and the context information further includes:

[0138] Perform a soft reset operation on the system, restart the system and store the error log.

[0139] In one embodiment, the fault processing module 30 is further used to, when the fault is an operating system fault, determine that the target analysis strategy is a context relationship analysis strategy, call the context relationship analysis strategy to read the depth of the traceable context, and read the context pointer in the register;

[0140] When the depth is not the first preset value, storing the address information corresponding to the context pointer;

[0141] When the depth reaches the first preset value, context information of the fault is generated based on the stored address information.

[0142] In one embodiment, the fault processing module 30 is further configured to determine that the target analysis strategy is an abnormal interruption analysis strategy when the fault is an abnormal interruption fault;

[0143] Calling the abnormal interrupt analysis strategy to obtain the interrupt vector number, abnormal address, machine state and stack frame content of the abnormal interrupt fault;

[0144] After the isolation is completed, a soft reset operation is performed on the system, the system is restarted, and the fault information and the interrupt vector number, exception address, machine state and stack frame content of the abnormal interrupt fault are stored.

[0145] In one embodiment, the fault processing module 30 is further configured to determine that the target analysis strategy is an error tracking analysis strategy when the fault is an error tracking fault;

[0146] The error tracking analysis strategy is called to store the fault information of the error tracking fault, and the fault handling process is ended.

[0147] In one embodiment, the fault processing module 30 is further configured to light up a corresponding fault light based on the fault type to prompt the user to perform fault detection.

[0148] The present application provides an automobile fault detection device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the automobile fault detection method in the above-mentioned embodiment one.

[0149] Reference below Figure 8 , which shows a schematic diagram of the structure of an automobile fault detection device suitable for implementing the embodiment of the present application. The automobile fault detection device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8 The automobile fault detection device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0150] like Figure 8As shown, the automobile fault detection device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the automobile fault detection device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the automobile fault detection device to communicate wirelessly or wired with other devices to exchange data. Although the figure shows an automobile fault detection device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided alternatively.

[0151] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0152] The automobile fault detection device provided by the present application adopts the automobile fault detection method in the above embodiment, which can solve the technical problem of being unable to quickly and accurately locate the root cause of the fault. Compared with the prior art, the beneficial effects of the automobile fault detection device provided by the present application are the same as the beneficial effects of the automobile fault detection method provided by the above embodiment, and the other technical features in the automobile fault detection device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0153] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0154] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0155] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the automobile fault detection method in the above-mentioned embodiment.

[0156] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0157] The computer-readable storage medium may be included in the automobile fault detection device; or may exist independently without being assembled into the automobile fault detection device.

[0158] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the automobile fault detection device, the automobile fault detection device: obtains fault information when a fault is detected; determines the fault type corresponding to the fault based on the fault information, where the fault type includes operating system fault, abnormal interrupt fault and error tracking type fault; determines the target analysis strategy based on the fault type to analyze and handle the fault.

[0159] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0160] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0161] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0162] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned automobile fault detection method, and can solve the technical problem of being unable to quickly and accurately locate the root cause of the fault. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the automobile fault detection method provided by the above-mentioned embodiment, and will not be repeated here.

[0163] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned automobile fault detection method when executed by a processor.

[0164] The computer program product provided by the present application can solve the technical problem of being unable to quickly and accurately locate the root cause of a fault. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the automobile fault detection method provided by the above embodiment, which will not be repeated here.

[0165] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A method for detecting automobile faults, characterized in that: The automobile fault detection method comprises the following steps: When a fault is detected, obtain fault information; Determine the fault type corresponding to the fault based on the fault information, wherein the fault type includes operating system fault, abnormal interrupt fault and error tracking fault; A target analysis strategy is determined based on the fault type to analyze and handle the fault.

2. The automobile fault detection method according to claim 1, characterized in that: The step of determining a target analysis strategy based on the fault type to analyze and handle the fault includes: When the fault is an operating system fault, determining that the target analysis strategy is a contextual relationship analysis strategy, calling the contextual relationship analysis strategy to analyze the fault, and obtaining context information of the fault; Determine a fault scope based on the fault information and the context information, and isolate devices within the fault scope; After the isolation is completed, a soft reset operation is performed on the system, the system is restarted and the fault information and the context information are stored.

3. The automobile fault detection method according to claim 2, characterized in that: After the step of calling the context relationship analysis strategy to analyze the fault and obtain the context information of the fault, the method further includes: Generate an error log based on the fault information and the context information, and optimize the system through the error log; The step of performing a soft reset operation on the system, restarting the system and storing the fault information and the context information further includes: Perform a soft reset operation on the system, restart the system and store the error log.

4. The automobile fault detection method according to claim 2, characterized in that: When the fault is an operating system fault, determining the target analysis strategy as a contextual relationship analysis strategy, determining the target analysis strategy as a contextual relationship analysis strategy, calling the contextual relationship analysis strategy to analyze the fault, and obtaining the context information of the fault includes: When the fault is an operating system fault, determining that the target analysis strategy is a context relationship analysis strategy, calling the context relationship analysis strategy to read the depth of the traceable context, and reading the context pointer in the register; When the depth is not the first preset value, storing the address information corresponding to the context pointer; When the depth reaches the first preset value, context information of the fault is generated based on the stored address information.

5. The automobile fault detection method according to claim 1, characterized in that: The step of determining a target analysis strategy based on the fault type to analyze and handle the fault includes: When the fault is an abnormal interruption fault, determining the target analysis strategy to be an abnormal interruption analysis strategy; Calling the abnormal interrupt analysis strategy to obtain the interrupt vector number, abnormal address, machine state and stack frame content of the abnormal interrupt fault; After the isolation is completed, a soft reset operation is performed on the system, the system is restarted, and the fault information and the interrupt vector number, exception address, machine state and stack frame content of the abnormal interrupt fault are stored.

6. The automobile fault detection method according to claim 1, characterized in that: The step of determining a target analysis strategy based on the fault type to analyze and handle the fault includes: When the fault is an error tracking fault, determining the target analysis strategy to be an error tracking analysis strategy; The error tracking analysis strategy is called to store the fault information of the error tracking fault, and the fault handling process is ended.

7. The automobile fault detection method according to any one of claims 1 to 6, characterized in that: After the step of determining a target analysis strategy based on the fault type to analyze and handle the fault, the method further includes: The corresponding fault light is lit based on the fault type to prompt the user to perform fault detection.

8. An automobile fault detection device, characterized in that: The device comprises: An information acquisition module is used to obtain fault information when a fault is detected; A fault determination module, configured to determine a fault type corresponding to the fault based on the fault information, wherein the fault type includes an operating system fault, an abnormal interruption fault, and an error tracking fault; The fault processing module is used to determine a target analysis strategy based on the fault type to analyze and process the fault.

9. An automobile fault detection device, characterized in that: The device comprises: a memory, a processor, and an automobile fault detection program stored in the memory and executable on the processor, wherein the automobile fault detection program is configured to implement the steps of the automobile fault detection method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium stores an automobile fault detection program, and when the automobile fault detection program is executed by the processor, the steps of the automobile fault detection method according to any one of claims 1 to 7 are implemented.

Images