Vehicle remote fault diagnosis method, device and equipment and storage medium

Abstract

The invention discloses a vehicle remote fault diagnosis method, device and equipment and a storage medium, and the method comprises the steps: obtaining a set fault flag bit in response to a fault flag bit of a fault monitoring code of a main control unit, and recording the set fault flag bit as a target fault flag bit; determining a controller fault code corresponding to the target fault flag bit as a target controller fault code based on a pre-established first mapping relationship between the fault flag bit and the controller fault code; and determining a fault reason corresponding to the target controller fault code based on a pre-established second mapping relationship between the controller fault code and the fault reason. According to the method, the vehicle fault reason can be accurately and efficiently diagnosed when the vehicle has the fault only by monitoring the fault monitoring code of the main control unit in combination with the hierarchical monitoring strategy and the preset mapping relationship, so that the dependence on technicians in the diagnosis process is reduced, the diagnosis efficiency is improved, the diagnosis resources are saved, and the diagnosis cost is reduced. And powerful technical support is provided for vehicle repair and maintenance.

Description

Technical Field

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

[0002] In the existing field of vehicle fault diagnosis, the commonly used method is to connect to various control units on the vehicle (such as engine control unit, transmission control unit, body control unit, etc.) through a diagnostic instrument, read the fault codes stored in these control units, and then locate and analyze the cause of the fault.

[0003] However, this traditional method requires reading and diagnosing multiple control units one by one. The operation process is cumbersome and time-consuming. At the same time, after reading the fault code, it is necessary to rely on technicians to locate and analyze the cause of the fault. The lack of efficient troubleshooting strategies can easily lead to low diagnostic efficiency and waste of resources. Summary of the invention

[0004] In view of the above problems, the present invention is proposed to provide a vehicle remote fault diagnosis method, device, equipment and storage medium that overcome the above problems or at least partially solve the above problems. By combining the hierarchical monitoring strategy and the preset mapping relationship, it is only necessary to monitor the fault monitoring code of the main control unit. When a vehicle fault occurs, the cause of the vehicle fault can be accurately and efficiently diagnosed, reducing the dependence on technicians in the diagnosis process, improving the diagnosis efficiency, saving diagnosis resources, and providing strong technical support for vehicle repair and maintenance.

[0005] In a first aspect, a vehicle remote fault diagnosis method is provided, comprising:

[0006] In response to a fault flag bit of a fault monitoring code from a main control unit of the vehicle being set, acquiring the set fault flag bit and recording it as the target fault flag bit;

[0007] Based on a pre-established first mapping relationship between a fault flag and a controller fault code, determining that the controller fault code corresponding to the target fault flag is a target controller fault code;

[0008] Based on a pre-established second mapping relationship between the controller fault code and the fault cause, the fault cause corresponding to the target controller fault code is determined.

[0009] Optionally, each of the fault flag bits is mapped to at least one of the controller fault codes;

[0010] When the fault flag bit is mapped to a plurality of the controller fault codes, the method of determining the controller fault code corresponding to the target fault flag bit as the target controller fault code based on a pre-established first mapping relationship between the fault flag bit and the controller fault code includes:

[0011] Based on a pre-established first mapping relationship between a fault flag and a controller fault code, determining a plurality of controller fault codes corresponding to the target fault flag as candidate controller fault codes;

[0012] Determining fault association weights corresponding to a plurality of candidate controller fault codes based on preset fault association weights of the respective controller fault codes;

[0013] From the multiple candidate controller fault codes, the candidate controller fault code with the highest fault association weight is selected as the target controller fault code.

[0014] Optionally, after determining the fault cause corresponding to the target fault code, the method further includes:

[0015] Acquiring fault-related data, wherein the fault-related data includes vehicle status data within a set time period before and after the fault occurs;

[0016] Based on the fault-related data, determining whether the fault cause is accurate;

[0017] When the fault cause is inaccurate, the fault association weight is corrected, and the target controller fault code and the corresponding fault cause are re-determined.

[0018] Optionally, the modifying the fault association weight includes:

[0019] The fault association weight is modified based on the following formula:

[0020] D=X*N*A*B*C adjusted ;

[0021] Where D is the fault association weight after correction; A is the fault association weight before correction; X is the expert factor, X∈(0,1]; N is the vehicle weight, N∈(0,0.2]; B is the reliability factor, B∈(0,1]; C adjusted represents the experience factor, C adjusted ∈(0,1].

[0022] Optionally, before determining the candidate controller fault code, the method further includes:

[0023] Determine the probability of occurrence of different faults in the functional components corresponding to each control unit;

[0024] Normalizing the occurrence probabilities of different faults in the same functional component so that the sum of the occurrence probabilities of different faults in the same functional component is 1;

[0025] Setting the normalized probability of occurrence of each fault as the fault association weight of the controller fault code corresponding to each fault;

[0026] The functional components are internal functional components of each of the control units, or external functional components whose faults are recorded by each of the control units.

[0027] Optionally, after determining the target controller fault code and before determining the fault cause, the method further includes:

[0028] Based on the target controller fault code, determining that the faulty control unit is the target control unit;

[0029] Obtaining a controller fault code stored in the target control unit, and recording it as a verification controller fault code;

[0030] Determining whether the target controller fault code is consistent with the verification controller fault code;

[0031] When the target controller fault code is inconsistent with the verification controller fault code, it is determined that the verification controller fault code and the fault monitoring code are invalid, and fault diagnosis error information is generated.

[0032] Optionally, before obtaining the target fault flag bit, the method further includes:

[0033] Based on the connection relationship and dependency strength of each control unit in the vehicle network architecture, a fault diagnosis network is established, wherein the fault diagnosis network includes a main control unit and at least one primary control unit associated with the main control unit, and the dependency strength of the main control unit is greater than the dependency strength of the at least one primary control unit;

[0034] Acquire the controller fault codes corresponding to the functional components corresponding to the control units in the fault diagnosis network when different faults occur, and determine the fault cause corresponding to each controller fault code to establish the second mapping relationship;

[0035] Configuring a fault monitoring code including a plurality of the fault flag bits for the main control unit, and defining a mapping between each of the fault flag bits and the at least one controller fault code for indicating different faults of the same functional component, so as to establish the first mapping relationship;

[0036] The functional components are internal functional components of each of the control units, or external functional components whose faults are recorded by each of the control units.

[0037] In a second aspect, a vehicle remote fault diagnosis device is provided, comprising:

[0038] An acquisition module, configured to acquire the set fault flag bit in response to a fault flag bit of a fault monitoring code from a main control unit of the vehicle, and record the set fault flag bit as the target fault flag bit;

[0039] A first determination module, configured to determine, based on a pre-established first mapping relationship between a fault flag and a controller fault code, that the controller fault code corresponding to the target fault flag is a target controller fault code;

[0040] The second determination module is used to determine the fault cause corresponding to the target controller fault code based on a pre-established second mapping relationship between the controller fault code and the fault cause.

[0041] Optionally, each of the fault flag bits is mapped to at least one of the controller fault codes;

[0042] When the fault flag bit is mapped to a plurality of controller fault codes, the first determining module is further configured to:

[0043] Based on a pre-established first mapping relationship between a fault flag and a controller fault code, determining a plurality of controller fault codes corresponding to the target fault flag as candidate controller fault codes;

[0044] Determining fault association weights corresponding to a plurality of candidate controller fault codes based on preset fault association weights of the respective controller fault codes;

[0045] From the multiple candidate controller fault codes, the candidate controller fault code with the highest fault association weight is selected as the target controller fault code.

[0046] Optionally, the device further comprises a fault cause correction module, which is used to:

[0047] Acquiring fault-related data, wherein the fault-related data includes vehicle status data within a set time period before and after the fault occurs;

[0048] Based on the fault-related data, determining whether the fault cause is accurate;

[0049] When the fault cause is inaccurate, the fault association weight is corrected, and the target controller fault code and the corresponding fault cause are re-determined.

[0050] Optionally, the fault cause correction module is further used to:

[0051] The fault association weight is modified based on the following formula:

[0052] D=X*N*A*B*C adjusted ;

[0053] Where D is the fault association weight after correction; A is the fault association weight before correction; X is the expert factor, X∈(0,1]; N is the vehicle weight, N∈(0,0.2]; B is the reliability factor, B∈(0,1]; C adjusted represents the experience factor, C adjusted ∈(0,1].

[0054] Optionally, the device further includes a fault association weight setting module, which is used to:

[0055] Determine the probability of occurrence of different faults in the functional components corresponding to each control unit;

[0056] Normalizing the occurrence probabilities of different faults in the same functional component so that the sum of the occurrence probabilities of different faults in the same functional component is 1;

[0057] Setting the normalized probability of occurrence of each fault as the fault association weight of the controller fault code corresponding to each fault;

[0058] The functional components are internal functional components of each of the control units, or external functional components whose faults are recorded by each of the control units.

[0059] Optionally, the device further includes a verification module, configured to:

[0060] Based on the target controller fault code, determining that the faulty control unit is the target control unit;

[0061] Obtaining a controller fault code stored in the target control unit, and recording it as a verification controller fault code;

[0062] Determining whether the target controller fault code is consistent with the verification controller fault code;

[0063] When the target controller fault code is inconsistent with the verification controller fault code, it is determined that the verification controller fault code and the fault monitoring code are invalid, and fault diagnosis error information is generated.

[0064] Optionally, the device further comprises:

[0065] A diagnostic network establishment module, used to establish a fault diagnosis network based on the connection relationship and dependency strength of each control unit in the vehicle network architecture, wherein the fault diagnosis network includes a main control unit and at least one primary control unit associated with the main control unit, and the dependency strength of the main control unit is greater than the dependency strength of the at least one primary control unit;

[0066] A second mapping relationship establishing module, used for obtaining the controller fault codes corresponding to the functional components corresponding to the control units in the fault diagnosis network when different faults occur, and determining the fault cause corresponding to each controller fault code to establish the second mapping relationship;

[0067] A first mapping relationship establishing module, used for acquiring a fault monitoring code including a plurality of fault flag bits configured for the main control unit, and defining a mapping between each of the fault flag bits and the at least one controller fault code for indicating different faults of the same functional component, so as to establish the first mapping relationship;

[0068] The functional components are internal functional components of each of the control units, or external functional components whose faults are recorded by each of the control units.

[0069] In a third aspect, an electronic device is provided, comprising: a memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the vehicle remote fault diagnosis method as described in the first aspect by executing the computer instructions.

[0070] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the vehicle remote fault diagnosis method as described in the first aspect.

[0071] The technical solution provided in the embodiments of the present invention has at least the following technical effects or advantages:

[0072] A vehicle remote fault diagnosis method, device, equipment and storage medium provided by an embodiment of the present invention can quickly lock the candidate controller fault code related to the current fault by responding to the fault flag position of the fault monitoring code of the main control unit and according to the first mapping relationship between the fault flag and the controller fault code established in advance. This strategy avoids the tedious process of checking each control unit one by one, and significantly improves the efficiency and speed of fault diagnosis. Based on the second mapping relationship between the controller fault code and the fault cause established in advance, the fault cause corresponding to the target controller fault code can be directly determined, avoiding complex logical reasoning and manual judgment processes, simplifying the operation process of fault diagnosis, and making the diagnosis process more intuitive and convenient. This method adopts a hierarchical monitoring strategy, and only needs to pay attention to the fault monitoring code of the main control unit, without the need to comprehensively monitor all control units. This not only reduces the amount of data required in the diagnosis process, reduces the system load, but also saves diagnostic equipment and human resources, and realizes the optimal allocation of resources. At the same time, by combining the mapping relationship with the hierarchical monitoring strategy, the method can efficiently and accurately diagnose the cause of the vehicle fault without the participation of technicians, reduces the dependence on technicians in the diagnosis process, improves the diagnostic efficiency, saves diagnostic resources, and provides strong technical support for vehicle repair and maintenance.

[0073] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0074] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0075] Figure 1 is a flow chart of a vehicle remote fault diagnosis method provided by an embodiment of the present invention;

[0076] Figure 2 is a flow chart of another vehicle remote fault diagnosis method provided by an embodiment of the present invention;

[0077] Figure 3 is a schematic diagram of a first mapping relationship provided by an embodiment of the present invention;

[0078] Figure 4 The present invention provides a structural block diagram of a vehicle remote fault diagnosis device. DETAILED DESCRIPTION

[0079] In order to better understand the above-mentioned technical scheme, the above-mentioned technical scheme will be described in detail below in combination with the accompanying drawings and specific implementation methods of the specification. It should be understood that the embodiments of the present disclosure and the specific features in the embodiments are detailed descriptions of the technical scheme of the present application, rather than limitations on the technical scheme of the present application. In the absence of conflict, the embodiments of the present application and the technical features in the embodiments can be combined with each other.

[0080] An embodiment of the present invention provides a vehicle remote fault diagnosis method, and the execution subject of the vehicle remote fault diagnosis method can be a remote electronic device (such as a cloud device) that is communicatively connected to a main control unit, so as to achieve remote diagnosis of vehicle faults.

[0081] Figure 1 is a flow chart of a vehicle remote fault diagnosis method provided by an embodiment of the present invention, such as Figure 1 As shown, the method includes:

[0082] Step S110 , in response to a fault flag bit of a fault monitoring code from a main control unit of the vehicle being set, obtaining the set fault flag bit and recording it as a target fault flag bit.

[0083] The main control unit is a control unit in the vehicle network architecture with fault diagnosis and storage functions. The fault monitoring code may include one or more fault flags, and the setting of the fault flag indicates that a fault has occurred. Exemplarily, when the vehicle has no fault, the fault flag is 0, and when the fault flag changes from 0 to 1, it indicates that the fault flag has been set.

[0084] Step S120: Based on a pre-established first mapping relationship between the fault flag and the controller fault code, determine that the controller fault code corresponding to the target fault flag is the target controller fault code.

[0085] Exemplarily, the first mapping relationship may be stored in the remote electronic device in the form of a table, and the target fault report may be determined to be the corresponding controller fault code by looking up the table.

[0086] Step S130: determining the fault cause corresponding to the target controller fault code based on a pre-established second mapping relationship between the controller fault code and the fault cause.

[0087] Exemplarily, the second mapping relationship may be stored in the remote electronic device in the form of a table, and the fault cause corresponding to the fault code of the target controller may be determined by looking up the table.

[0088] The above method adopts a hierarchical monitoring strategy, and only needs to pay attention to the fault monitoring code of the main control unit, without the need to conduct comprehensive monitoring of all control units. This not only reduces the amount of data required in the diagnosis process, reduces the system load, but also saves diagnostic equipment and human resources, and realizes the optimal allocation of resources. At the same time, the method can realize remote active diagnosis of vehicle faults. The remote electronic equipment can monitor the fault code in real time to realize vehicle fault diagnosis, without the need for the remote electronic equipment to passively send remote diagnosis instructions to the vehicle control unit to request the acquisition of the vehicle fault code, and then perform vehicle fault diagnosis, which greatly improves the real-time nature of the diagnosis. And active diagnosis can locate the cause of the fault more accurately, reducing the possibility of misdiagnosis and missed diagnosis. At the same time, it can also timely discover and warn potential faults, avoid vehicle damage or safety accidents caused by faults, so that the owner no longer needs to drive the vehicle to the repair shop for diagnosis, which greatly saves time and energy. For serious faults, it can also actively remind the owner to take emergency measures to ensure driving safety and provide maintenance suggestions to the owner in time, which brings significant benefits in terms of technical level, owner experience and after-sales service quality of automobile manufacturers.

[0089] Figure 2 is another flow chart of a vehicle remote fault diagnosis method provided by an embodiment of the present invention, such as Figure 2 As shown, in one embodiment of the present invention, before executing each step of the above method, the method may further include:

[0090] Step S210: Establish a fault diagnosis network based on the connection relationship and dependency strength of each control unit in the vehicle network architecture. The fault diagnosis network includes a main control unit and at least one first-level control unit associated with the main control unit, and the dependency strength of the main control unit is greater than the dependency strength of at least one first-level control unit.

[0091] In a specific implementation, the dependency strength of each control unit can be comprehensively evaluated through the three aspects of communication request ratio, number of interfaces, and fault impact factor, which can be achieved by weighted averaging the corresponding quantitative indicators of the above aspects or adopting other appropriate evaluation methods. Among them, the quantitative indicators of the communication request ratio can include request frequency ratio and bandwidth ratio. The request frequency ratio can be quantified by counting the number of communication requests sent by each control unit in a unit time. High-frequency communication requests indicate that it is active and important in the system; bandwidth ratio can be quantified by evaluating the proportion of communication load occupied by communication requests. High bandwidth ratio indicates high importance. The number of interfaces can be quantified by counting the association between the control unit and other control units. More direct associations mean that their interactions are complex and important. The quantitative indicators of fault impact factor can include exposure, severity and controllability. Exposure is determined by the corresponding scenario and can be estimated in two ways. The first is based on the duration of a single scenario, and the second is based on the frequency of faults in a single scenario. Severity represents the estimation of the potential degree of harm in a specific driving scenario, and controllability measures the difficulty of the driver or other road traffic participants to avoid the considered accident in the considered operating scenario. The controllability assessment also needs to take into account the possibility that a representative driver or other person involved could influence the scenario to avoid harm.

[0092] It should be noted that each of the above-mentioned control units is a control unit on the vehicle with fault diagnosis and storage functions, and each control unit can not only diagnose its own faults but also diagnose faults of other elements associated with the control unit (such as sensors, actuators, communication buses, etc.).

[0093] Step S220: Obtain controller fault codes corresponding to functional components corresponding to various control units in the fault diagnosis network when different faults occur, and determine the fault cause corresponding to each controller fault code to establish a second mapping relationship.

[0094] Among them, the functional components corresponding to each control unit are the internal functional components of each control unit (such as a central processing unit, a memory, an input / output interface, a communication bus, a power supply, etc.), or the external functional components (such as sensors, actuators, communication buses, etc.) that record faults by each control unit. When different faults occur in each functional component, if the fault causes of some faults are the same, the corresponding controller fault codes may also be the same. Each control unit may be set with at least one controller fault code, and each controller fault code includes a plurality of second fault code flags (for distinction, the first fault code flag is used to represent the fault code flag of the fault monitoring code in the following text), each second fault code flag corresponds to a different fault cause, when different second fault code flags change from 0 to 1 and are set, the corresponding controller fault codes are also different, and the technicians can determine the actual fault causes corresponding to different controller fault codes based on historical data and actual experience, so as to pre-establish a second mapping relationship between the controller fault code and the fault cause. Since the second fault code flag bits are limited, one second fault code flag bit may actually correspond to multiple fault causes. At this time, the technician can assign weights to the fault causes corresponding to each second fault code flag bit based on the actual probability of each fault cause occurring in the historical data and actual experience, and determine the actual fault cause corresponding to each second fault code flag bit in order of weight from high to low combined with the actual fault data.

[0095] Step S230: configure a fault monitoring code including a plurality of fault flags for the main control unit, and define a mapping between each fault flag and at least one controller fault code for indicating different faults of the same functional component, so as to establish a first mapping relationship.

[0096] Specifically, the fault flag bits in the fault monitoring code can be divided into multiple groups according to the number of control units, each group of fault flag bits corresponds to a control unit, and the number of first fault flag bits in each group of first fault flag bits can also be set according to the number of functional components corresponding to the control unit. For example, when the vehicle network architecture includes a total of 10 control units, the fault flag bits in the fault monitoring code can be divided into 10 groups accordingly; when the number of functional components corresponding to control unit A is 3, the group A of fault flag bits corresponding to control unit A includes 3 first fault flag bits bit1, bit2, and bit3, which correspond to 3 functional components a, b, and c respectively.

[0097] Exemplarily, each first fault flag bit in the fault monitoring code corresponds to a functional component, and when the functional components corresponding to each control unit generate different faults, there will be corresponding controller fault codes. Therefore, each first fault flag bit can be associated with the controller fault code used to represent the same functional component to establish a corresponding first mapping relationship. For example, when the first fault flag bit1 in the fault monitoring code corresponds to the functional component a, and the controller fault codes D1 and D2 are used to represent different faults generated by the functional component a, the first fault flag bit1 can be associated with the controller fault codes D1 and D2, and the controller fault codes corresponding to the first fault flag bit1 are set to D1 and D2.

[0098] Figure 3 is a schematic diagram of a first mapping relationship provided by an embodiment of the present invention, such as Figure 3 As shown, at this time, the fault monitoring code 310 includes N groups of fault flags, and each controller corresponds to a controller fault code. The Ath group of fault flags 310a corresponds to the controller fault code 320a of the Ath controller.

[0099] The A-th group fault flag 310a includes fault flag bits bit0, bit1 and bit2, wherein bit0 is a total fault flag bit for indicating the fault state of the A-th group fault flag 310a, and is set when there is a set fault flag bit in the A-th group fault flag 310a. The A-th controller includes three functional components, and correspondingly, bit1 in the A-th group fault flag 310a is a first fault flag bit corresponding to the first functional component of the A controller, and is set when the first functional component fails; bit2 is a first fault flag bit corresponding to the second functional component of the A controller, and is set when the second functional component fails; bit3 is a first fault flag bit corresponding to the third functional component of the A controller, and is set when the third functional component fails.

[0100] Depend on Figure 3 It can be seen that when the controller fault code of controller A is 1100…0, it corresponds to a fault in the first functional component of controller A. At this time, controller A will transmit the fault code 1100…0 to the main control unit. When the main control unit detects the fault code 1100…0, bit 1 in the A-th group fault flag 310a corresponding to the first functional component will change from 0 to 1, and a set bit will be generated. At the same time, bit 0 will also change from 0 to 1, and a set bit will be generated.

[0101] The selection of the main control unit in the above steps S110 to S130 and the establishment of the first mapping relationship and the second mapping relationship can be completed through the above steps S210 to S230.

[0102] It should be noted that the national standard GB / T 32960 states that the enterprise platform needs to have vehicle fault monitoring and safety alarm functions, totaling 19 items. Each monitoring content is assigned a national standard data coding group consisting of bits, which is used to mark when the data is pushed. Therefore, in addition to the customized fault flags, the fault monitoring code and each controller fault code in the embodiment of the present invention also need to include the codes corresponding to the monitoring content that meets the national standard. When the corresponding coding bit is 1, it means that the fault has been pushed, and the fault will not be pushed again for a period of time to optimize the push, reduce the repeated push of the same problem due to different requirements, and avoid information redundancy and interference. If a fault does not occur again for a period of time, or the system needs to restart monitoring a specific fault, the bit related to the fault will be reset to 0 so that the system can re-detect and push the fault. The reset mechanism helps to maintain the real-time monitoring and ensure that the system can respond to new faults or abnormal conditions in a timely manner.

[0103] In one embodiment of the present invention, each fault flag bit is mapped to at least one controller fault code. When the fault flag bit is mapped to multiple controller fault codes, step S120 may include:

[0104] Based on a pre-established first mapping relationship between a fault flag and a controller fault code, multiple controller fault codes corresponding to a target fault flag are determined as candidate controller fault codes; based on preset fault association weights of each controller fault code, fault association weights corresponding to multiple candidate controller fault codes are determined; from the multiple candidate controller fault codes, the candidate controller fault code with the highest fault association weight is selected as the target controller fault code.

[0105] By introducing the concept of fault association weights, and based on the preset fault association weights of each controller fault code, selecting the candidate controller fault code with the highest fault association weight as the target controller fault code can further improve the accuracy of diagnosis and reduce the possibility of misdiagnosis and missed diagnosis. In addition, each fault flag bit and the controller fault code have a one-to-many mapping relationship, which can further reduce the storage resources occupied by the fault monitoring code in the main control unit, and at the same time effectively reduce the amount of data uploaded to the remote electronic device, reduce the redundancy and resource consumption of cloud data collection, and optimize resource utilization.

[0106] In one embodiment of the present invention, before determining the candidate controller fault code, the method further includes:

[0107] Determine the occurrence probabilities of different faults in the functional components corresponding to each control unit; normalize the occurrence probabilities of different faults in the same functional component so that the sum of the occurrence probabilities of different faults in the same functional component is 1; set the normalized occurrence probabilities of each fault as the fault association weight of the controller fault code corresponding to each fault.

[0108] Among them, the probability of occurrence of different faults in each functional component can be determined by technicians through historical data and actual experience. By normalizing the probability of fault occurrence, normalization can convert the probability of fault occurrence of different magnitudes or ranges to the same metric, so that they can be directly compared and calculated. For example, the probability of occurrence of faults A, B, and C in the same functional component are PA1, PB1, and PC1, respectively. The corresponding fault distribution weights of A, B, and C on this fault branch are PA2, PB2, and PC2, respectively. The sum of PA2, PB2, and PC2 must be 1, PA2 = PA1 / (PA1+PB1+PC1), PB2 = PB1 / (PA1+PB1+PC1), and PC2 = PC1 / (PA1+PB1+PC1).

[0109] After multiple candidate controller fault codes are determined, the fault association weights of the candidate controller fault codes may be arranged in order from high to low, so as to select the candidate controller fault code with the highest fault association weight as the target controller fault code.

[0110] In one embodiment of the present invention, after determining the target controller fault code in step S120 and before determining the fault cause in step S130, the method may further include:

[0111] Based on the target controller fault code, determine that the faulty control unit is the target control unit; obtain the controller fault code stored inside the target control unit and record it as the verification controller fault code; determine whether the target controller fault code is consistent with the verification controller fault code; when the target controller fault code is inconsistent with the verification controller fault code, determine that the verification controller fault code and the fault monitoring code are invalid, and generate fault diagnosis error information.

[0112] According to the diagnostic requirements of OBD (On-Board Diagnostics) and UDS (Unified Diagnostic Services), the controller fault code needs to be stored in the fault memory when the fault occurs. After the fault occurs, when the vehicle is in a safe state, the functional or physically addressed control unit fault memory is read. The fault memory is an area specifically used to store fault information, and it can keep the stored data from being lost after the vehicle is powered off. Therefore, the controller fault code can be determined and verified by reading the fault memory, and mutually verified with the target controller fault code, ensuring the consistency of the controller fault code from two different failure mechanism perspectives, which can improve the accuracy of detection and eliminate missed or misjudgment caused by data errors, tampering or loss.

[0113] Exemplarily, since the controller fault code and the control unit are in a one-to-one correspondence, the target control unit with the fault can be determined based on the determined target controller fault code. When the verification controller fault code actually stored in the target control unit is inconsistent with the target controller fault code determined by the mapping relationship and the fault association weight, a fault diagnosis error message can be generated to indicate that the currently determined verification controller fault code and fault monitoring code are invalid.

[0114] In an embodiment of the present invention, after determining the cause of the fault in step S130, the method may further include:

[0115] Obtain fault-related data, which includes vehicle status data within a set time period before and after the fault occurs; determine whether the fault cause is accurate based on the fault-related data; when the fault cause is inaccurate, correct the fault-related weight, and re-determine the target controller fault code and the corresponding fault cause.

[0116] Exemplarily, the vehicle status data may include, but is not limited to, vehicle driving parameters (such as vehicle driving speed, mileage, steering angle, etc.), engine related parameters (such as engine temperature, speed, continuous working time, etc.), electrical system parameters (power battery voltage, motor operating status, etc.), brake system parameters (such as ABS operating status, etc.) and other parameters (such as the operating status of various auxiliary equipment such as lighting system, audio system, air conditioning system, etc. on the vehicle). In a specific implementation, the acquired fault-related data can be input into a pre-established fault diagnosis model, and the fault diagnosis model predicts the cause of the fault based on the fault-related data and outputs it. The fault model can be obtained through training based on historical fault data. This is a conventional technology and will not be repeated here. By comparing whether the predicted fault cause is consistent with the determined fault cause, it can be determined whether the fault cause is accurate. By continuously correcting the fault-related weight, the method can be continuously adapted to market changes and user needs, and continuously optimized to improve accuracy. At the same time, the remote electronic device can only intercept the rated data related to the fault cause and input it into the fault model to improve the diagnostic efficiency.

[0117] In one embodiment of the present invention, the fault association weight is modified, including:

[0118] The fault association weight is modified based on the following formula:

[0119] D=X*N*A*B*C adjusted ;

[0120] Where D is the fault association weight after correction; A is the fault association weight before correction; X is the expert factor, X∈(0,1]; N is the vehicle weight, N∈(0,0.2]; B is the reliability factor, B∈(0,1]; C adjusted represents the experience factor, C adjusted ∈(0,1].

[0121] In a specific implementation, the reliability factor B is the score of the maintenance party for the accuracy of providing fault directionality after the fault group occurs, with complete accuracy of 1, partial accuracy of 0.7, and no reference value of 0.4; the experience factor C adjusted It is the feedback result of whether the problem recurs after the acceptance party (user) takes back the vehicle. There is no recurrence weight value to give the initial value experience factor C adjustedThe weight is 0.7, and the weight is multiplied by 0.7 each time it recurs. If there is no recurrence within three months after maintenance, it will increase to 0.9, and if there is no recurrence within one year, it will be 1; N is the value calculated by the system through big data, that is, the weight of the current link with the same fault; for example, if the link has occurred 100 times, the N value of this vehicle accounts for 0.01. As the number of system operations continues to accumulate, the probability of fundamental errors in the system drops sharply. Therefore, the accumulation of initial training sets and validation sets is particularly important. The initial link accumulation is recommended to be greater than 5, that is, the system determines that the given initial N value is not greater than 0.2. Expert systems are usually an effective intervention and adjustment mechanism. Based on design principles, system operation effects, and collecting user feedback, as an important basis for correcting correlation factors, in principle, intervention once a month can help the system make more accurate judgments to a certain extent.

[0122] It should be noted that when a fundamental pointing deviation occurs, that is, the difference between the initial value A of the fault association weight before correction and the fault association weight D after correction is greater than the initial value A, (AD) / A, if it is greater than 0.6, a deviation alarm needs to be triggered, and some associations need to be closed in real time, and the synchronization expert system needs to intervene to effectively maintain the link while efficiently ensuring the accuracy of the link. By correcting the information link in real time, it is possible to respond to market feedback more quickly, solve user problems, improve after-sales efficiency, and improve user experience and satisfaction.

[0123] Based on the same inventive concept, an embodiment of the present invention further provides a vehicle remote fault diagnosis device for performing vehicle remote fault diagnosis. Figure 4 is a structural block diagram of a vehicle remote fault diagnosis device provided by an embodiment of the present invention, such as Figure 4 As shown, the device 400 includes an acquisition module 410 , a first determination module 420 , and a second determination module 430 .

[0124] An acquisition module 410 is used for acquiring the set fault flag bit in response to the fault flag bit of the fault monitoring code from the main control unit of the vehicle, and recording the set fault flag bit as a target fault flag bit;

[0125] A first determination module 420, configured to determine, based on a pre-established first mapping relationship between a fault flag and a controller fault code, a controller fault code corresponding to a target fault flag as a target controller fault code;

[0126] The second determination module 430 is used to determine the fault cause corresponding to the target controller fault code based on a pre-established second mapping relationship between the controller fault code and the fault cause.

[0127] Optionally, each fault flag bit is mapped to at least one controller fault code;

[0128] When the fault flag is mapped to multiple controller fault codes, the first determination module 420 is further configured to:

[0129] Based on a pre-established first mapping relationship between the fault flag and the controller fault code, determining multiple controller fault codes corresponding to the target fault flag as candidate controller fault codes;

[0130] Determining fault association weights corresponding to multiple candidate controller fault codes based on preset fault association weights of each controller fault code;

[0131] From multiple candidate controller fault codes, a candidate controller fault code with the highest fault association weight is selected as the target controller fault code.

[0132] Optionally, the device 400 further includes a fault cause correction module, which is used to:

[0133] Acquire fault-related data, the fault-related data including vehicle status data within a set time period before and after the fault occurs;

[0134] Determine whether the fault cause is accurate based on the fault-related data;

[0135] When the fault cause is inaccurate, the fault association weight is corrected, and the target controller fault code and the corresponding fault cause are re-determined.

[0136] Optionally, the fault cause correction module is also used to:

[0137] The fault association weight is modified based on the following formula:

[0138] D=X*N*A*B*C adjusted ;

[0139] Where D is the fault association weight after correction; A is the fault association weight before correction; X is the expert factor, X∈(0,1]; N is the vehicle weight, N∈(0,0.2]; B is the reliability factor, B∈(0,1]; C adjusted represents the experience factor, C adjusted ∈(0,1].

[0140] Optionally, the device further includes a fault association weight setting module, which is used to:

[0141] Determine the probability of occurrence of different faults in the functional components corresponding to each control unit;

[0142] Normalize the probability of occurrence of different faults in the same functional component so that the sum of the probability of occurrence of different faults in the same functional component is 1;

[0143] The normalized probability of occurrence of each fault is set as the fault association weight of the controller fault code corresponding to each fault;

[0144] The functional components are internal functional components of each control unit, or external functional components whose faults are recorded by each control unit.

[0145] Optionally, the device further includes a verification module, which is used to:

[0146] Based on the target controller fault code, determining that the faulty control unit is the target control unit;

[0147] Obtaining a controller fault code stored in a target control unit, and recording it as a verification controller fault code;

[0148] Determine whether the target controller fault code is consistent with the verification controller fault code;

[0149] When the target controller fault code is inconsistent with the verification controller fault code, the verification controller fault code and the fault monitoring code are determined to be invalid, and a fault diagnosis error message is generated.

[0150] Optionally, the device further comprises:

[0151] A diagnostic network establishment module, used to establish a fault diagnosis network based on the connection relationship and dependency strength of each control unit in the vehicle network architecture, wherein the fault diagnosis network includes a main control unit and at least one primary control unit associated with the main control unit, and the dependency strength of the main control unit is greater than the dependency strength of the at least one primary control unit;

[0152] A second mapping relationship establishing module is used to obtain controller fault codes corresponding to functional components corresponding to various control units in the fault diagnosis network when different faults occur, and determine the fault cause corresponding to each controller fault code to establish a second mapping relationship;

[0153] The first mapping relationship establishing module is used to obtain a fault monitoring code including multiple fault flag bits configured for the main control unit, and define each fault flag bit to be mapped with at least one controller fault code used to represent different faults of the same functional component to establish a first mapping relationship.

[0154] The specific details of the vehicle remote fault diagnosis involved in the above-mentioned device can be understood by corresponding to the relevant descriptions and effects in the above-mentioned vehicle remote fault diagnosis method embodiment, and will not be repeated here.

[0155] Based on the same inventive concept as the above-mentioned vehicle remote fault diagnosis method, the present invention also provides an electronic device, which may include a processor and a memory, wherein the processor and the memory may be connected to each other through a bus or other means. The processor may be a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components and other chips, or a combination of the above-mentioned various types of chips. The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs, non-transient computer executable programs and modules, such as program instructions / modules corresponding to the vehicle remote fault diagnosis method in the embodiment of the present invention. The processor executes various functional applications and data processing of the processor by running the non-transient software programs, instructions and modules stored in the memory, that is, to realize the vehicle remote fault diagnosis in the above-mentioned method embodiment.

[0156] The memory may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required by at least one function; the data storage area may store data created by the processor, etc. In addition, the memory may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. The one or more modules are stored in the memory, and when executed by the processor, the execution is as follows: Figure 1 The vehicle remote fault diagnosis method in the illustrated embodiment.

[0157] For details of the above electronic equipment, please refer to Figure 1 The corresponding related descriptions and effects in the illustrated embodiments can be understood and will not be repeated here.

[0158] Based on the same inventive concept as the vehicle remote fault diagnosis method, the present invention also provides a computer-readable storage medium, on which computer instructions are stored, and the computer program instructions are used to enable a computer to execute the vehicle remote fault diagnosis method in the above embodiment.

[0159] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium can be a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above-mentioned types of memory.

[0160] The technical solutions provided in the above embodiments of the present application have at least the following technical effects or advantages:

[0161] A vehicle remote fault diagnosis method, device, equipment and storage medium provided by an embodiment of the present invention can quickly lock the candidate controller fault code related to the current fault by responding to the fault flag position of the fault monitoring code of the main control unit and according to the first mapping relationship between the fault flag and the controller fault code established in advance. This strategy avoids the tedious process of checking each control unit one by one, and significantly improves the efficiency and speed of fault diagnosis. Based on the second mapping relationship between the controller fault code and the fault cause established in advance, the fault cause corresponding to the target controller fault code can be directly determined, avoiding complex logical reasoning and manual judgment processes, simplifying the operation process of fault diagnosis, and making the diagnosis process more intuitive and convenient. This method adopts a hierarchical monitoring strategy, and only needs to pay attention to the fault monitoring code of the main control unit, without the need to comprehensively monitor all control units. This not only reduces the amount of data required in the diagnosis process, reduces the system load, but also saves diagnostic equipment and human resources, and realizes the optimal allocation of resources. At the same time, by combining the mapping relationship with the hierarchical monitoring strategy, the method can efficiently and accurately diagnose the cause of the vehicle fault without the participation of technicians, reduces the dependence on technicians in the diagnosis process, improves the diagnostic efficiency, saves diagnostic resources, and provides strong technical support for vehicle repair and maintenance.

[0162] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.

[0163] Similarly, it should be understood that in order to streamline the present disclosure and aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of the present invention, various features of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, this disclosed method should not be interpreted as reflecting the intention that the claimed invention requires more features than those explicitly recited in each claim. More specifically, as reflected in the claims below, inventive aspects lie in less than all the features of the individual embodiments disclosed above. Therefore, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, with each claim itself serving as a separate embodiment of the present invention.

[0164] It should be noted that the above-mentioned embodiments illustrate rather than limit the invention and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims.

Claims

1. A vehicle remote fault diagnosis method, characterized in that: The method comprises: In response to a fault flag bit of a fault monitoring code from a main control unit of the vehicle being set, acquiring the set fault flag bit and recording it as the target fault flag bit; Based on a pre-established first mapping relationship between a fault flag and a controller fault code, determining that the controller fault code corresponding to the target fault flag is a target controller fault code; Based on a pre-established second mapping relationship between the controller fault code and the fault cause, the fault cause corresponding to the target controller fault code is determined.

2. The method according to claim 1, characterized in that Each of the fault flag bits is mapped to at least one of the controller fault codes; When the fault flag bit is mapped to a plurality of the controller fault codes, the method of determining the controller fault code corresponding to the target fault flag bit as the target controller fault code based on a pre-established first mapping relationship between the fault flag bit and the controller fault code includes: Based on a pre-established first mapping relationship between a fault flag and a controller fault code, determining a plurality of controller fault codes corresponding to the target fault flag as candidate controller fault codes; Determining fault association weights corresponding to a plurality of candidate controller fault codes based on preset fault association weights of the respective controller fault codes; From the multiple candidate controller fault codes, the candidate controller fault code with the highest fault association weight is selected as the target controller fault code.

3. The method according to claim 2, characterized in that After determining the fault cause corresponding to the target fault code, the method further includes: Acquiring fault-related data, wherein the fault-related data includes vehicle status data within a set time period before and after the fault occurs; Based on the fault-related data, determining whether the fault cause is accurate; When the fault cause is inaccurate, the fault association weight is corrected, and the target controller fault code and the corresponding fault cause are re-determined.

4. The method according to claim 3, characterized in that The modifying of the fault association weight comprises: The fault association weight is modified based on the following formula: D=X*N*A*B*C adjusted ; Where D is the fault association weight after correction; A is the fault association weight before correction; X is the expert factor, X∈(0,1]; N is the vehicle weight, N∈(0,0.2]; B is the reliability factor, B∈(0,1]; C adjusted represents the experience factor, C adjusted ∈(0,1].

5. The method according to claim 2, characterized in that: Before determining the candidate controller fault code, the method further includes: Determine the probability of occurrence of different faults in the functional components corresponding to each control unit; Normalizing the occurrence probabilities of different faults in the same functional component so that the sum of the occurrence probabilities of different faults in the same functional component is 1; Setting the normalized probability of occurrence of each fault as the fault association weight of the controller fault code corresponding to each fault; The functional components are internal functional components of each of the control units, or external functional components whose faults are recorded by each of the control units.

6. The method according to claim 2, characterized in that After determining the target controller fault code and before determining the fault cause, the method further includes: Based on the target controller fault code, determining that the faulty control unit is the target control unit; Obtaining a controller fault code stored in the target control unit, and recording it as a verification controller fault code; Determining whether the target controller fault code is consistent with the verification controller fault code; When the target controller fault code is inconsistent with the verification controller fault code, it is determined that the verification controller fault code and the fault monitoring code are invalid, and fault diagnosis error information is generated.

7. The method according to claim 1, characterized in that Before acquiring the target fault flag bit, the method further includes: Based on the connection relationship and dependency strength of each control unit in the vehicle network architecture, a fault diagnosis network is established, wherein the fault diagnosis network includes a main control unit and at least one primary control unit associated with the main control unit, and the dependency strength of the main control unit is greater than the dependency strength of the at least one primary control unit; Acquire the controller fault codes corresponding to the functional components corresponding to the control units in the fault diagnosis network when different faults occur, and determine the fault cause corresponding to each controller fault code to establish the second mapping relationship; Configuring a fault monitoring code including a plurality of the fault flag bits for the main control unit, and defining a mapping between each of the fault flag bits and the at least one controller fault code for indicating different faults of the same functional component, so as to establish the first mapping relationship; The functional components are internal functional components of each of the control units, or external functional components whose faults are recorded by each of the control units.

8. A vehicle remote fault diagnosis device, characterized in that: The device comprises: An acquisition module, configured to acquire the set fault flag bit in response to a fault flag bit of a fault monitoring code from a main control unit of the vehicle, and record the set fault flag bit as the target fault flag bit; A first determination module, configured to determine, based on a pre-established first mapping relationship between a fault flag and a controller fault code, that the controller fault code corresponding to the target fault flag is a target controller fault code; The second determination module is used to determine the fault cause corresponding to the target controller fault code based on a pre-established second mapping relationship between the controller fault code and the fault cause.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the vehicle remote fault diagnosis method as described in any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the vehicle remote fault diagnosis method according to any one of claims 1 to 7.

Images