Fault diagnosis method and device and cloud platform
By obtaining fault analysis data and determining the functional interaction logic and function timing, the problem of inaccurate fault positioning in the prior art is solved, and higher fault positioning accuracy is achieved.
Patent Information
- Application Number
- CN202510009083.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-02
- Publication Date
- 2025-04-15
AI Technical Summary
The prior art is difficult to accurately locate faulty components in fault diagnosis, especially in fault classification and alarm rules preparation, which is greatly affected by experience, resulting in inaccurate fault positioning.
By obtaining the fault analysis data of the components to be checked, obtaining the functional interaction logic and function timing of the components to be checked when a fault occurs, determining the functions to be checked, and determining the faulty components based on the functions to be checked.
The accuracy of fault location is improved, and the fault function can be determined from the perspective of software interaction based on the functional interaction logic and function timing, and the faulty components can be further located.
Smart Images
Figure CN119828661A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of vehicle technology, and more specifically, to a fault diagnosis method, device and cloud platform. Background Art
[0002] Fault diagnosis is crucial to vehicle driving safety. In related methods, the fault can be checked according to preset rules based on the vehicle information when the fault occurs. However, since the compilation of fault classification and alarm rules are affected by the developer's own experience, for example, if the airbag light and steering system fault light are on at the same time, it may be a chassis CAN communication failure, a low battery voltage failure or a single module failure. However, if there is not enough fault scenario information and effective fault classification rules, the fault location may be inaccurate. Summary of the invention
[0003] In view of the above problems, the present application proposes a fault diagnosis method, device and cloud platform to improve the above problems.
[0004] In a first aspect, the present application provides a fault diagnosis method, the method comprising: obtaining a component to be troubleshooted; based on fault analysis data corresponding to the component to be troubleshooted, obtaining a functional interaction logic and a functional timing for controlling the component to be troubleshooted when a fault occurs, the fault analysis data characterizing a control process of the component to be troubleshooted; based on the functional interaction logic and the functional timing, determining a function to be troubleshooted, the function to be troubleshooted being a function that fails when controlling the component to be troubleshooted; determining a faulty component based on the function to be troubleshooted.
[0005] In the second aspect, the present application provides a fault diagnosis device, which includes: a component acquisition unit to be checked, used to obtain the component to be checked; a function acquisition unit to be checked, used to obtain the function interaction logic and function timing when controlling the component to be checked based on the fault analysis data corresponding to the component to be checked, the fault analysis data characterizing the control process of the component to be checked; based on the function interaction logic and the function timing, determine the function to be checked, the function to be checked is a function that fails when controlling the component to be checked; a faulty component determination unit, used to determine the faulty component based on the function to be checked.
[0006] In a third aspect, the present application provides a cloud platform comprising one or more processors and a memory; one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the above-mentioned method.
[0007] In a fourth aspect, the present application provides a computer-readable storage medium, in which program code is stored, wherein the above method is executed when the program code is run.
[0008] The present application provides a fault diagnosis method, device, cloud platform and storage medium. After obtaining the component to be checked, based on the fault analysis data corresponding to the component to be checked, the function interaction logic and function timing when controlling the component to be checked when the fault occurs are obtained, based on the function interaction logic and function timing, the function to be checked is determined, and the faulty component is determined based on the function to be checked. Through the above-mentioned method, after obtaining the component to be checked, based on the fault analysis data corresponding to the component to be checked, the function interaction logic and function timing when controlling the component to be checked are obtained; based on the function interaction logic and function timing, the function to be checked is determined; based on the function interaction logic and function timing, the faulty component is determined based on the function to be checked, so that the faulty function can be determined from the perspective of software interaction according to the function interaction logic and function timing when controlling the component to be checked, and the faulty component is further located, thereby improving the accuracy of fault location. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.
[0010] Figure 1 A flowchart of a fault diagnosis method proposed in an embodiment of the present application is shown;
[0011] Figure 2 A flowchart of a fault diagnosis method proposed in another embodiment of the present application is shown;
[0012] Figure 3 A schematic diagram of an instrument mirror display interface proposed in an embodiment of the present application is shown;
[0013] Figure 4 A schematic diagram of an instrument mirror fault display interface proposed in an embodiment of the present application is shown;
[0014] Figure 5 A structural block diagram of a fault diagnosis device proposed in an embodiment of the present application is shown;
[0015] Figure 6 A structural block diagram of a cloud platform proposed in this application is shown. DETAILED DESCRIPTION
[0016] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0017] In the embodiment of the present application, the inventor proposes a fault diagnosis method, device and cloud platform. After obtaining the component to be checked, based on the fault analysis data corresponding to the component to be checked, the functional interaction logic and functional timing when controlling the component to be checked when the fault occurs are obtained. Based on the functional interaction logic and functional timing, the function to be checked is determined, and the faulty component is determined based on the function to be checked. Through the above method, after obtaining the component to be checked, based on the fault analysis data corresponding to the component to be checked, the functional interaction logic and functional timing when controlling the component to be checked are obtained; based on the functional interaction logic and functional timing, the function to be checked is determined; based on the functional interaction logic and functional timing, the faulty component is determined based on the function to be checked, so that the faulty function can be determined from the perspective of software interaction according to the functional interaction logic and functional timing when controlling the component to be checked, and the faulty component is further located, thereby improving the accuracy of fault location.
[0018] See also Figure 1 , an embodiment of the present application provides a fault diagnosis method, the method comprising:
[0019] S110: Obtain the components to be checked.
[0020] The parts to be checked may refer to parts in the vehicle that have abnormalities.
[0021] As a method, the cloud platform can obtain the parts to be checked through the vehicle data uploaded by the vehicle in real time.
[0022] The vehicle data may refer to data representing the operating status of each component in the vehicle. The vehicle data may be uploaded to the cloud platform in real time for the vehicle.
[0023] S120: Based on the fault analysis data corresponding to the component to be checked, obtaining the functional interaction logic and functional timing for controlling the component to be checked when a fault occurs, wherein the fault analysis data represents a control process for the component to be checked.
[0024] Among them, the fault analysis data may include bus signal data, SOA service data, etc., and the fault analysis data may be obtained based on vehicle data.
[0025] As a method, the status information of associated components can be obtained based on fault analysis data. The associated components can be components that directly or indirectly control the component to be checked; based on the status information of the associated components, the functional interaction logic and the functional timing can be obtained.
[0026] Among them, the functional interaction logic can refer to the information (data or instructions) interaction between related components when a fault occurs, such as related component 1 sending information to related component 2, etc. The functional timing can refer to the order of execution between related components when a fault occurs, such as first related component 1 sends information to related component 2, and then related component 2 sends the received information to related component 3, etc.
[0027] The component to be checked may correspond to one or more functions (such as the vehicle display screen can realize navigation function, reversing monitoring function, audio and video playback function, etc.). When each function has one or more implementation methods, one implementation method can be a subdivided function of the function, and the associated components involved in different subdivided functions may be different, so that the associated components corresponding to the component to be checked can include the associated components involved in all subdivided functions corresponding to the component to be checked.
[0028] For example, when executing the wiper control function, the vehicle can turn on the wiper by voice, manually, automatically after the rain sensor detects, or request to turn on the wiper by virtual buttons, etc. In the scenario where the vehicle turns on the wiper with voice control, the customer needs to wake up the vehicle computer with voice first, and then the vehicle computer tells the vehicle gateway controller to turn on the wiper. The gateway controller forwards the signal to tell the wiper controller to turn on the wiper. The wiper controller performs the wiping action on the wiper motor according to the instruction, the wiper strength detected by the rain sensor, etc. In the scenario where the vehicle turns on the wiper manually, the wiper switch, wiper motor, etc. are involved. In the scenario where the wiper is automatically turned on after the rain sensor detects, the rain sensor, wiper controller, wiper motor, etc. are involved. When the wiper cannot operate normally, the component to be checked may be the wiper motor, and the associated components may be the vehicle computer, vehicle gateway controller, wiper controller, rain sensor, wiper switch, wiper motor, etc.
[0029] In the embodiment of the present application, the associated component may be an executor or a controller, the executor may refer to a component that ultimately executes the corresponding function, and the controller may refer to a component that issues the corresponding function in the form of an instruction. The state information of the controller may include basic condition state information, interactive condition state information, and feedback condition state information, and the state information of the executor may include basic condition state information and execution state information.
[0030] Among them, the basic condition status information can indicate whether the corresponding component itself works normally, the interactive condition status information can indicate whether the corresponding component successfully sends information to other related components, the feedback condition status information can indicate whether the corresponding component successfully receives feedback information from other related components, and the execution status information can indicate whether the corresponding component successfully receives the task to be executed.
[0031] Exemplarily, as shown in Table 1, when the component is a controller, if the value of the basic condition status information is 1, it indicates that the controller itself is in a normal working state; if the value of the basic condition status information is 0, it indicates that the controller itself is not in a normal working state. If the value of the interactive condition status information is 1, it indicates that the controller successfully sends information to other associated components; if the value of the interactive condition status information is 0, it indicates that the controller fails to send information to other associated components. If the value of the feedback condition status information is 1, it indicates that the controller successfully receives feedback information from other associated components; if the value of the feedback condition status information is 0, it indicates that the controller fails to receive feedback information from other associated components.
[0032] Table 1
[0033] Controller status information normal abnormal Basic condition status information 1 0 Interaction condition status information 1 0 Feedback condition status information 1 0
[0034] For example, as shown in Table 2, when the component is an actuator, if the value of the basic condition status information is 1, it indicates that the actuator itself is in a normal working state; if the value of the basic condition status information is 0, it indicates that the actuator itself is not in a normal working state. If the value of the execution status information is 1, it indicates that the actuator has successfully received the task to be executed; if the value of the execution status information is 0, it indicates that the actuator has not successfully received the task to be executed.
[0035] Table 2
[0036] Actuator status information normal abnormal Basic condition status information 1 0 Execution status information 1 0
[0037] Optionally, the values of the status information of the associated components may be arranged in a preset order to obtain the functional interaction logic and functional timing.
[0038] The preset sequence may be a sequence obtained by performing multiple analyses and verifications on the associated components.
[0039] Exemplarily, the components involved in function x may include controller A, controller B, controller C, actuator E, and actuator F. The preset order may be: {status information of controller A, status information of controller B, status information of controller C, status information of actuator E, status information of actuator F}, the order of multiple status information corresponding to the controller is: {basic condition status information, interactive condition status information, feedback condition status information}, and the order of multiple status information corresponding to the actuator is: {basic condition status information, execution status information}. When a fault occurs, only controller B does not have the value of the status information, and the function interaction logic and function timing may be: 110XXX1111111, and "X" may indicate that the value of the corresponding status information is not detected.
[0040] It should be noted that as long as a value of a certain status information of a component exists, it can be indicated that when a fault occurs, the component participates in the implementation process corresponding to the status information.
[0041] S130: Determine a function to be checked based on the function interaction logic and the function sequence, where the function to be checked is a function that fails when controlling the component to be checked.
[0042] As a method, a functional expression can be obtained based on functional interaction logic and functional timing; the functional expression is matched with a functional expression library corresponding to the component to be checked, and the function to be checked is determined based on the matching result. The functional expression library contains functional expressions of all functions related to controlling the component to be checked.
[0043] Among them, the function expression in the function expression library can be the expression when the function is successfully implemented. The function expression in the function expression library can not only indicate the type of state information of the associated components involved, but also indicate that the state information of the associated components involved is normal. Therefore, the value of the abnormal state information in the function interaction logic and function sequence can be updated to the value of the normal state information, and the updated function interaction logic and function sequence can be used as the function expression.
[0044] Exemplarily, the function interaction logic and function timing may be: 110XXX1111111, and the corresponding function expression may be 111XXX1111111.
[0045] In an embodiment of the present application, the component to be checked may correspond to one or more functions (such as a vehicle display screen may realize a navigation function, a reversing monitoring function, an audio and video playback function, etc.). When each function has one or more implementation methods, an implementation method may be a subdivision of the function, and a subdivision function may correspond to a functional expression.
[0046] Exemplarily, the function expression library corresponding to the components to be checked can be as shown in Table 3. The components involved in function x can include A controller, B controller, C controller, E actuator, and F actuator. Function x can have subdivided functions x1, x2, x3, x4, etc. A1, A2, and A3 can respectively represent the basic condition status information, interactive condition status information, and feedback condition status information of controller A; B1, B2, and B3 can respectively represent the basic condition status information, interactive condition status information, and feedback condition status information of controller B; C1, C2, and C3 can respectively represent the basic condition status information, interactive condition status information, and feedback condition status information of controller C; E1 and E2 can respectively represent the basic condition status information and execution status information of controller E; and F1 and F2 can respectively represent the basic condition status information and execution status information of controller F. Among them, xiZj can represent the j-th state information of component Z under subdivision function xi. When the value corresponding to xiZj is 1, it indicates that the j-th state information of component Z is required to realize subdivision function xi (that is, component Z participates in the implementation process corresponding to the j-th state information); when the value corresponding to xiZj is X, it indicates that the j-th state information of component Z is not required to realize subdivision function xi. For example, if the value of x1A1 in Table 1 is 1, it can be indicated that the state information A1 of component A is required to realize subdivision function x1; for example, if the value of x1B1 in Table 1 is X, it can be indicated that the state information B1 of component B is not required to realize subdivision function x1.
[0047] Table 3
[0048]
[0049]
[0050] Exemplarily, when the function expression is 111XXX1111111, it can be determined from Table 3 that the function to be checked is x1.
[0051] S140: Determine a faulty component based on the function to be checked.
[0052] As a method, the fault analysis rules of the function to be troubleshooted can be determined based on the function to be troubleshooted. The fault analysis rules can include functional expressions when faults occur in different components corresponding to the function to be troubleshooted; the faulty components are determined based on the fault analysis rules, functional interaction logic and functional timing of the function to be troubleshooted.
[0053] Optionally, the function expression obtained based on the function interaction logic and the function timing may be matched with the function expression in the fault analysis rule, and the faulty component may be determined based on the matching result.
[0054] Exemplarily, the fault analysis rules corresponding to the function x3 to be checked may be as shown in Table 4. When the function interaction logic and function timing are 110XXX1111111, it can be determined that the faulty component is controller A.
[0055] Table 4
[0056]
[0057]
[0058] In the embodiment of the present application, by finely dividing the status information of the associated components, the function interaction logic and function timing of controlling the components to be checked when the fault occurs are obtained, and based on the fault analysis rules, function interaction logic and function timing of the functions to be checked, the faulty components are determined, which can not only accurately locate the faulty components, but also further locate the fault type of the faulty components, so that more accurate maintenance suggestions can be given according to the fault type. For example, when the fault type is confirmed to be x1-A1 abnormal, it can be indicated that there is a problem with the hardware or software of the A controller itself; for another example, when the fault type is confirmed to be x1-A2 abnormal, it can be indicated that there is a problem when the A controller sends information.
[0059] Existing diagnostic solutions usually require customers to go to the repair shop to obtain the faulty parts through local equipment / remote reading, and then confirm the fault type based on the experience of the maintenance expert. When the cause of this type of fault is a hard-wired fault that persists once it occurs before maintenance is performed (such as internal hardware abnormalities such as wiper motors, gateway controllers, and car computers), the fault diagnosis method proposed in this application and the existing diagnostic solution can accurately diagnose the fault and complete the maintenance work. However, when the cause of this type of fault is a software interaction fault or an occasional fault, because the scene is difficult to reproduce, the existing diagnostic solution has almost no way to accurately diagnose the fault, and can only rely on the experience of maintenance experts to judge. This solution can reproduce the real scene when the fault occurs according to the design logic of the vehicle and the status information of the related components, so that the faulty component can be accurately obtained. At the same time, the functional interaction logic and functional timing of the components to be checked when the fault occurs are automatically analyzed, so that the underlying software logic can be accurately obtained, thereby ensuring the accuracy and explainability of fault reasoning. For example, it is possible to detect which sub-function of the vehicle has failed and the type of fault in the sub-function, and to conduct a diagnostic analysis based on the idea that the cause of the failure is which controller's interactive logic has not issued an accurate execution instruction, and the actual reason why the execution instruction was not issued is what problem exists inside the controller.
[0060] A fault diagnosis method provided in this embodiment, after obtaining the component to be troubleshooted, based on the fault analysis data corresponding to the component to be troubleshooted, obtains the function interaction logic and function timing when controlling the component to be troubleshooted when the fault occurs, determines the function to be troubleshooted based on the function interaction logic and function timing, and determines the faulty component based on the function to be troubleshooted. Through the above method, after obtaining the component to be troubleshooted, based on the fault analysis data corresponding to the component to be troubleshooted, obtains the function interaction logic and function timing when controlling the component to be troubleshooted; determines the function to be troubleshooted based on the function interaction logic and function timing; determines the faulty component based on the function to be troubleshooted, so that the faulty function can be determined from the perspective of software interaction according to the function interaction logic and function timing when controlling the component to be troubleshooted, further locates the faulty component, and improves the accuracy of fault location.
[0061] See also Figure 2 , an embodiment of the present application provides a fault diagnosis method, the method comprising:
[0062] S210: Obtain the fault occurrence time period and the identification of the faulty vehicle.
[0063] The fault occurrence time period may refer to the time period when the user perceives the fault occurrence, and the identifier of the faulty vehicle may be the VIN (Vehicle Identification Number) of the faulty vehicle.
[0064] As a method, the cloud platform can obtain the time period of the fault occurrence and the identification of the faulty vehicle based on the user feedback information received.
[0065] The user feedback information may include the time period of the fault and the faulty vehicle information, and the faulty vehicle information may refer to information that can directly or indirectly obtain the identification of the faulty vehicle. For example, the faulty vehicle information may be the VIN of the faulty vehicle, or may be the user's mobile phone number, user name, or other information that can indirectly obtain the VIN of the faulty vehicle.
[0066] For example, when a user senses that a vehicle malfunctions, the user can upload user feedback information to the cloud platform through the vehicle management application on the mobile phone or the vehicle display screen.
[0067] S220: Based on the identification of the faulty vehicle, extract the vehicle information corresponding to the faulty vehicle in the time period when the fault occurred.
[0068] Among them, vehicle information may include fault analysis data, vehicle power on and off time, controller log, DTC (Diagnostic Trouble Code) information, vehicle speed, etc.
[0069] As a method, vehicle information corresponding to the faulty vehicle during the time period when the fault occurred may be extracted based on the identification of the faulty vehicle.
[0070] Among them, since all vehicles can upload their own vehicle data to the cloud platform in real time, the cloud platform stores vehicle information of different vehicles at different times.
[0071] S230: Perform simulation based on the vehicle information to determine the components to be checked.
[0072] As a method, simulation can be performed based on vehicle information to obtain instrument mirror display content, which includes fault prompt information; the instrument mirror display content is displayed on an instrument mirror display interface; and based on the fault prompt information in the instrument mirror display interface, the components to be checked are determined.
[0073] The instrument mirror display content may include vehicle fuel consumption, vehicle mileage and other content that can be displayed on the real vehicle dashboard, as well as fault prompt information, which may be a fault indicator light, text prompt information, etc. The instrument mirror display interface may refer to a display interface of instrument information deployed on a cloud platform.
[0074] Optionally, when simulating based on vehicle information, matching can be performed according to preset display rules, and the on-site information of the vehicle can be displayed in the instrument mirror display interface. The preset display rules can be rules formulated by experts based on vehicle specifications.
[0075] For example, Figure 3 As shown, when simulation is performed according to the vehicle, when the B fault light of vehicle A is on, the fault indicator light of the B fault can be displayed on the instrument mirror display interface, thereby truly reflecting that the B fault light of vehicle A is on; when the D instrument information prompt is displayed on the instrument panel of vehicle C, the text content corresponding to the D instrument information prompt can be displayed on the instrument mirror display interface, thereby truly reflecting the D instrument information prompt of vehicle C.
[0076] In the embodiment of the present application, the instrument mirror display interface can reproduce the real scene of the instrument when the fault occurs, so that subsequent maintenance experts can intuitively understand the on-site information of the vehicle when manually analyzing the fault.
[0077] S240: Based on the fault analysis data corresponding to the component to be checked, obtaining the functional interaction logic and functional timing for controlling the component to be checked when a fault occurs, wherein the fault analysis data represents a control process for the component to be checked.
[0078] S250: Determine a function to be checked based on the function interaction logic and the function sequence, where the function to be checked is a function that fails when controlling the component to be checked.
[0079] S260: Determine a faulty component based on the function to be checked.
[0080] S270: Obtaining fault information and maintenance suggestions based on the faulty component.
[0081] The fault information may be information obtained according to the fault prompt information in the instrument mirror display interface, such as the number and type of fault indicator lights that are lit. The maintenance suggestion may refer to suggestions for solving the fault type.
[0082] As a method, faulty components can be automatically analyzed based on functional interaction logic and functional timing to obtain fault information and maintenance suggestions.
[0083] For example, in the scenario of voice-controlled wiper activation, when the customer wakes up the car computer, the car computer needs to detect whether there is any abnormality in itself, correctly receive the customer's voice information and pass it to the gateway controller requiring the wiper controller to execute the wiper activation action. The wiper controller needs to detect whether there is any abnormality in itself, receive information such as the rain sensor and the wiper motor status to determine whether the wiper can accurately turn on the wipers. When the wiper motor and rain sensor can perform the action correctly, it is necessary to confirm that the status of the wiper motor and rain sensor are normal. When the wipers cannot be turned on, the car computer or the instrument can transmit information through the wiper controller to display "Please check the front wiper / rear wiper system".
[0084] S280: Displaying the fault information and the maintenance suggestion on the instrument mirror fault display interface.
[0085] Among them, Figure 4 As shown, the instrument mirror fault display interface can present key fault information points, key marking points, fault information and maintenance suggestions in the time period of the fault in the form of a timeline. The key fault information point content may include fault light lighting, text reminders, instrument black screen, car computer black screen, etc. The key marking point content may include vehicle power on, vehicle power off, charging gun plug, vehicle mode switching, range jump, smart driving start / exit, etc.
[0086] As a method, fault information and maintenance suggestions can be displayed on the instrument mirror fault display interface.
[0087] Optionally, upon receiving a request for obtaining the instrument mirror fault display interface from a terminal device corresponding to the maintenance personnel, the instrument mirror fault display interface may be displayed on the terminal device corresponding to the maintenance personnel, so that the maintenance personnel may perform maintenance according to maintenance suggestions.
[0088] Optionally, when maintenance personnel find that maintenance suggestions cannot solve the vehicle fault during the actual maintenance process, they can send feedback information to the cloud platform, which can indicate that the maintenance suggestion is wrong. After receiving the feedback information, the cloud platform can notify maintenance experts to repair the fault diagnosis logic to improve the accuracy of the functions to be checked and the faulty parts, thereby realizing closed-loop management of the fault diagnosis method.
[0089] The present embodiment provides a fault diagnosis method, through the above-mentioned method, after obtaining the component to be checked, based on the fault analysis data corresponding to the component to be checked, the function interaction logic and function timing when controlling the component to be checked are obtained; based on the function interaction logic and function timing, the function to be checked is determined; based on the function to be checked, the fault component is determined, so that the fault function can be determined from the perspective of software interaction according to the function interaction logic and function timing when controlling the component to be checked, and the fault component is further located, thereby improving the accuracy of fault location. Moreover, in the present embodiment, by displaying the instrument mirror display content on the instrument mirror display interface and displaying the fault information and maintenance suggestions on the instrument mirror fault display interface, the visualization degree of the fault diagnosis method proposed in the present application can be improved, and it is convenient to quickly promote and implement the fault diagnosis method proposed in the present application to the 4S store end, and solve the problem that the 4S store personnel are not familiar with the whole vehicle logic.
[0090] See also Figure 5 The present application provides a fault diagnosis device 600, the device 600 comprising:
[0091] A component to be checked obtaining unit 410 is used to obtain the component to be checked;
[0092] The function acquisition unit 420 to be checked is used to acquire the function interaction logic and function timing of the component to be checked when the fault occurs based on the fault analysis data corresponding to the component to be checked, wherein the fault analysis data represents the control process of the component to be checked; based on the function interaction logic and the function timing, determine the function to be checked, wherein the function to be checked is a function that fails when controlling the component to be checked;
[0093] The faulty component determining unit 430 is configured to determine the faulty component based on the function to be checked.
[0094] As a method, the component acquisition unit 410 to be checked is specifically used to obtain the fault occurrence time period and the identification of the faulty vehicle; based on the identification of the faulty vehicle, extract the vehicle information corresponding to the faulty vehicle in the fault occurrence time period; perform simulation based on the vehicle information to determine the component to be checked.
[0095] Optionally, the component to be checked acquisition unit 410 is specifically used to perform simulation based on the vehicle information to obtain instrument mirror display content, wherein the instrument mirror display content includes fault prompt information; display the instrument mirror display content on an instrument mirror display interface; and determine the component to be checked based on the fault prompt information in the instrument mirror display interface.
[0096] As a method, the fault analysis data includes status information of associated components, and the associated components are components that directly or indirectly control the components to be troubleshooted. The function acquisition unit 420 to be troubleshooted is specifically used to match the status information of the associated components with all functional paths corresponding to the components to be troubleshooted, and obtain the status information of the successfully matched associated components, wherein each of the functional paths includes the components involved in executing the corresponding function; based on the status information of the successfully matched associated components, the function interaction logic and the function timing are obtained.
[0097] Optionally, the function to be checked acquisition unit 420 is specifically used to obtain a function expression based on the function interaction logic and the function timing; match the function expression with a function expression library corresponding to the component to be checked, and determine the function to be checked based on the matching result, wherein the function expression library contains function expressions of all functions related to controlling the component to be checked.
[0098] Optionally, the associated components include a controller and an executor, the status information of the controller includes basic condition status information, interactive condition status information and feedback condition status information, the status information of the executor includes basic condition status information and execution status information, and the function acquisition unit 420 to be checked is specifically used to determine the basic condition status information, interactive condition status information and feedback condition status information of the controller based on the function interaction logic and the function timing; determine the basic condition status information and execution status information of the executor based on the function interaction logic and the function timing, wherein the basic condition status information represents whether the corresponding component itself works normally, the interactive condition status information represents whether the corresponding component successfully sends information to other associated components, the feedback condition status information represents whether the corresponding component successfully receives feedback information from other associated components, and the execution status information represents whether the corresponding component successfully receives the task to be executed; based on the basic condition status information, interactive condition status information, feedback condition status information of the controller and the basic condition status information and execution status information of the executor, the function expression is obtained.
[0099] As a method, the fault component determination unit 430 is specifically used to determine the fault analysis rules of the function to be troubleshooted based on the function to be troubleshooted, and the fault analysis rules include functional expressions when faults occur in different components corresponding to the function to be troubleshooted; based on the fault analysis rules of the function to be troubleshooted, the functional interaction logic and the functional timing, the faulty component is determined.
[0100] As a method, the fault component determination unit 430 is specifically used to obtain fault information and maintenance suggestions based on the fault component; and display the fault information and maintenance suggestions on the instrument mirror fault display interface.
[0101] The following will be combined Figure 6 A cloud platform provided by this application is described.
[0102] See also Figure 6 Based on the above fault diagnosis method and device, the embodiment of the present application also provides another cloud platform 100 that can execute the above fault diagnosis method. The cloud platform 100 includes one or more (only one is shown in the figure) processors 102, a memory 104, and a network module 106 that are coupled to each other. Among them, the memory 104 stores a program that can execute the content of the above embodiment, and the processor 102 can execute the program stored in the memory 104.
[0103] Among them, the processor 102 may include one or more processing cores. The processor 102 uses various interfaces and lines to connect various parts within the entire cloud platform 100, and executes various functions and processes data of the cloud platform 100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 104, and calling data stored in the memory 104. Optionally, the processor 102 can be implemented in at least one hardware form of a network processor (Neural network Processing Unit, NPU), a digital signal processing (Digital Signal Processing, DSP), a field programmable gate array (Field-Programmable Gate Array, FPGA), a programmable logic array (Programmable Logic Array, PLA), and an electronic control unit (Electronic Control Unit, ECU). The processor 102 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processor (Graphics Processing Unit, GPU), a network processor (Neural network Processing Unit, NPU) and a modem. The CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; the NPU is responsible for processing multimedia data such as video and images; and the modem is used to process wireless communications. It is understandable that the above-mentioned modem may not be integrated into the processor 102, but may be implemented separately through a communication chip.
[0104] The memory 104 may include a random access memory (RAM) or a read-only memory (ROM). The memory 104 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 104 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc. The data storage area may also store data (such as a phone book, audio and video data, chat record data) created by the cloud platform 100 during use.
[0105] The network module 106 is used to implement information exchange between the cloud platform 100 and other devices, for example, transmission of device control instructions, operation request instructions, and status information acquisition instructions, etc. When the cloud platform 100 is specifically different devices, the corresponding network modules 106 may be different.
[0106] An embodiment of the present application provides a computer-readable storage medium in which a program code is stored, and the program code can be called by a processor to execute the method described in the above method embodiment.
[0107] The computer readable storage medium may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read-only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer readable storage medium 800 includes a non-transitory computer-readable storage medium. The computer readable storage medium 800 has storage space for program codes that execute any of the method steps in the above method. These program codes can be read from or written to one or more computer program products. The program code can be compressed, for example, in an appropriate form.
[0108] In summary, the present application provides a fault diagnosis method, device and cloud platform. After obtaining the component to be checked, based on the fault analysis data corresponding to the component to be checked, the function interaction logic and function timing when controlling the component to be checked when the fault occurs are obtained, based on the function interaction logic and function timing, the function to be checked is determined, and the faulty component is determined based on the function to be checked. Through the above-mentioned method, after obtaining the component to be checked, based on the fault analysis data corresponding to the component to be checked, the function interaction logic and function timing when controlling the component to be checked are obtained; based on the function interaction logic and function timing, the function to be checked is determined; based on the function interaction logic and function timing, the faulty component is determined based on the function to be checked, so that the faulty function can be determined from the perspective of software interaction according to the function interaction logic and function timing when controlling the component to be checked, and the faulty component is further located, thereby improving the accuracy of fault location.
[0109] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims
1. A fault diagnosis method, characterized in that: The method comprises: Get the parts to be checked; Based on the fault analysis data corresponding to the component to be checked, the functional interaction logic and functional timing of the component to be checked when the fault occurs are obtained, wherein the fault analysis data represents the control process of the component to be checked; Based on the function interaction logic and the function sequence, determine the function to be checked, where the function to be checked is a function that fails when controlling the component to be checked; A faulty component is determined based on the function to be checked.
2. The method according to claim 1, characterized in that The acquiring, based on the fault analysis data corresponding to the component to be checked, the function interaction logic and function timing for controlling the component to be checked when a fault occurs, comprises: Based on the fault analysis data, status information of associated components is obtained, where the associated components are components that directly or indirectly control the component to be checked; Based on the status information of the associated components, the functional interaction logic and the functional timing are obtained.
3. The method according to claim 2, characterized in that The associated components include a controller and an actuator, the state information of the controller includes basic condition state information, interaction condition state information and feedback condition state information, the state information of the actuator includes basic condition state information and execution state information, and the function interaction logic and the function timing are obtained based on the state information of the associated components, including: Based on the function interaction logic and the function timing, determine the basic condition state information, the interaction condition state information, and the feedback condition state information of the controller; Based on the functional interaction logic and the functional timing, determine the basic condition status information and execution status information of the actuator, wherein the basic condition status information represents whether the corresponding component itself works normally, the interaction condition status information represents whether the corresponding component successfully sends information to other associated components, the feedback condition status information represents whether the corresponding component successfully receives feedback information from other associated components, and the execution status information represents whether the corresponding component successfully receives the task to be executed; The function interaction logic and the function timing are obtained based on the basic condition status information, interaction condition status information, feedback condition status information of the controller and the basic condition status information and execution status information of the actuator.
4. The method according to claim 1, characterized in that: The determining the function to be checked based on the function interaction logic and the function timing includes: Based on the functional interaction logic and the functional timing, a functional expression is obtained; The function expression is matched with a function expression library corresponding to the component to be checked, and the function to be checked is determined based on the matching result, wherein the function expression library contains function expressions of all functions related to controlling the component to be checked.
5. The method according to claim 1, characterized in that The determining of the faulty component based on the function to be checked includes: Based on the function to be checked, determining a fault analysis rule for the function to be checked, wherein the fault analysis rule includes a functional expression when different components corresponding to the function to be checked fail; The faulty component is determined based on the fault analysis rule of the function to be checked, the function interaction logic and the function timing.
6. The method according to claim 1, characterized in that The obtaining of the component to be checked includes: Obtain the time period when the fault occurred and the identification of the faulty vehicle; Based on the identification of the faulty vehicle, extracting the vehicle information corresponding to the faulty vehicle during the time period when the fault occurred; A simulation is performed based on the vehicle information to determine the components to be checked.
7. The method according to claim 6, characterized in that The simulating based on the vehicle information to determine the components to be checked includes: Perform simulation based on the vehicle information to obtain instrument mirror image display content, wherein the instrument mirror image display content includes fault prompt information; Displaying the instrument mirror image display content on the instrument mirror image display interface; The component to be checked is determined based on the fault prompt information in the instrument mirror display interface.
8. The method according to claim 1, characterized in that After the faulty component is determined based on the function to be checked, the method further includes: Based on the faulty component, obtaining fault information and maintenance suggestions; The fault information and the maintenance suggestion are displayed on the instrument mirror fault display interface.
9. A fault diagnosis device, characterized in that: The device comprises: A to-be-checked component acquisition unit, used to acquire the to-be-checked component; A function acquisition unit to be checked is used to obtain the function interaction logic and function timing of the component to be checked when the fault occurs based on the fault analysis data corresponding to the component to be checked, wherein the fault analysis data represents the control process of the component to be checked; based on the function interaction logic and the function timing, determine the function to be checked, wherein the function to be checked is a function that fails when controlling the component to be checked; A faulty component determining unit is used to determine the faulty component based on the function to be checked.
10. A cloud platform, characterized in that: The method comprises one or more processors and a memory; one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the method according to any one of claims 1 to 8.
11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program code, wherein when the program code is run, the method according to any one of claims 1 to 8 is executed.