Fault cause location method, device, equipment and computer readable storage medium

By using the time stamps of domain controllers and designated devices in the autonomous driving system to process and analyze data, the target data related to failure is selected, which solves the problem of high and low labor cost in autonomous driving failure analysis and improves the location of fault causes efficiency.

CN117369411BActive Publication Date: 2024-11-19DONGFENG COMML VEHICLE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311451713.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-10-31
Publication Date
2024-11-19
Estimated Expiration
2043-10-31

AI Technical Summary

Technical Problem

In autonomous driving development testing, when a vehicle failure is detected, the labor cost and inefficient of problem analysis and positioning based on large amounts of data.

Method used

By sending the data of the acquisition device to the domain controller, the data timestamp of the data acquisition device is determined based on the timestamp received by the domain controller, and the module processes and serializes the data, specifying the device for deserialization processing and fault correspondence relationships. Table analysis to filter out target data related to failure.

Benefits of technology

The number of data analysis is reduced, the efficiency of failure cause analysis is improved, and labor costs is greatly reduced, and labor costs are solved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117369411B_ABST
    Figure CN117369411B_ABST
Patent Text Reader

Abstract

A method, device, equipment and computer-readable storage medium for locating the cause of a fault. The method sends the data collected by each collection device to a domain controller, and determines the second timestamp of the data collected by each data collection device; processes the data based on the domain controller and sends the processed data to a designated device; searches for a corresponding relationship table between faults and data based on the fault of the vehicle through the designated device, determines each target data corresponding to the fault in the data collected by each data collection device, and filters out each target data related to the fault of the vehicle from the data collected by each data collection device; determines the target data in the target data that is different from the corresponding standard data as the cause of the fault, thereby solving the technical problem in the related art that when a vehicle fault is detected, the labor cost for problem analysis and location based on a large amount of collected data is high and the efficiency is low.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of intelligent driving technology, and in particular to a method, device, equipment and computer-readable storage medium for locating the cause of a fault. Background Art

[0002] With the rapid development of autonomous driving technology, traditional distributed controllers are shifting to centralized domain controllers, and the input information of data acquisition devices has doubled. During the development and testing of autonomous driving, a large amount of raw data from the vehicle body or data acquisition devices and intermediate data from the domain controller need to be collected so that when a vehicle failure is detected, the problem can be analyzed and located based on the large amount of collected data. However, due to the large amount of collected data, the current analysis of the large amount of collected data mainly relies on manual labor to determine the cause of the vehicle failure. Therefore, not only is the labor cost high, but the efficiency is also low. Summary of the invention

[0003] The present application provides a method, device, equipment and computer-readable storage medium for locating the cause of a fault, which can solve the technical problems in the prior art of high labor costs and low efficiency in problem analysis and locating based on a large amount of collected data when a vehicle fault is detected.

[0004] In a first aspect, an embodiment of the present application provides a method for locating a fault cause, the method for locating a fault cause comprising:

[0005] Sending the data collected by each data collection device to the domain controller, and determining a second timestamp of the data collected by each data collection device based on a first timestamp when the domain controller receives the data collected by each data collection device;

[0006] The data is processed based on the modules included in the domain controller, and the data processed by each module is serialized and sent to the designated device via the central gateway;

[0007] The designated device performs deserialization processing on the received data to obtain data collected by each data collection device, and searches for a corresponding relationship table between faults and data based on the faults of the vehicle through the designated device, and determines each target data corresponding to the fault in the data collected by each data collection device;

[0008] Acquire standard data corresponding to the second timestamp of each target data;

[0009] It is determined that the target data among the target data that is different from the corresponding standard data is the cause of the fault.

[0010] In combination with the first aspect, in one implementation, the step of determining the second timestamp of the data collected by each data collection device based on the first timestamp of the data collected by each data collection device received by the domain controller includes:

[0011] For each data acquisition device, obtain the message sending time T1 when the message is sent to the domain controller, the message receiving time T2 when the domain controller receives the message, the response message sending time T3 when the domain controller sends a response message to the data acquisition device after receiving the message, and the response message receiving time T4 when the data acquisition device receives the response message;

[0012] Based on T1, T2, T3 and T4, the delay time of the message and the response message during the transmission process is calculated by the first preset formula. The first preset formula is as follows:

[0013]

[0014] Based on T1, T2, T3 and T4, the time difference between the data acquisition device and the domain controller is calculated by the second preset formula. The second preset formula is as follows:

[0015]

[0016] Among them, D1 is used to represent the delay time between the message and the response message during the transmission process, and D2 is used to represent the time difference between the data acquisition device and the domain controller;

[0017] For each data collection device, the difference between the first timestamp corresponding to the collected data received by the domain controller minus D1 and then minus D2 is used as the second timestamp of the data collected by the data collection device.

[0018] In combination with the first aspect, in one implementation, the data includes obstacle data collected by a camera, obstacle data collected by a radar, and lane line information collected by a camera, and the step of processing the data based on the modules included in the domain controller includes:

[0019] The perception module contained in the domain controller filters the obstacle data collected by the camera and the obstacle data collected by the radar through the EKF filtering algorithm to obtain the effective obstacle data collected by the camera and the effective obstacle data collected by the radar;

[0020] The effective obstacle data collected by the camera and the effective obstacle data collected by the radar are matched and fused through the Hungarian correlation matching algorithm to obtain fused obstacle information, and the fused obstacle information is sent to the planning module contained in the domain controller;

[0021] The planning module included in the domain controller generates a driving situation map based on the fused obstacle information, high-precision map information and lane line information collected by the camera through A* and polynomial algorithms, plans the vehicle's driving information based on the driving situation map, and sends the planned driving information of the vehicle to the control module included in the domain controller;

[0022] The control module included in the domain controller optimizes the vehicle's control instructions through a fuzzy PID algorithm based on the vehicle's planned driving information, controls the vehicle's driving based on the optimized control instructions, and obtains the vehicle's actual driving information.

[0023] In combination with the first aspect, in one implementation, the step of serializing the data after each module and sending the data to the designated device via the central gateway includes:

[0024] The fused obstacle information processed by the perception module included in the domain controller, the planned driving information of the vehicle processed by the planning module included in the domain controller, the actual driving information of the vehicle processed by the control module included in the domain controller, and the vehicle fault detection information output by the system module included in the domain controller are serialized respectively;

[0025] The serialized fused obstacle information, the serialized vehicle planned driving information, the serialized vehicle actual driving information and the vehicle fault detection information are sent to the designated device via the central gateway.

[0026] In combination with the first aspect, in one implementation, before the step of searching the corresponding relationship table between faults and data based on the faults of the vehicle by the designated device and determining each target data corresponding to the fault in the data collected by each data collection device, the method includes:

[0027] Obtain each fault that the vehicle has experienced and the corresponding impact factor of each fault;

[0028] A corresponding relationship table between faults and data is created based on each fault that has occurred in the vehicle and the influencing factors corresponding to each fault.

[0029] In a second aspect, an embodiment of the present application provides a device for locating a fault cause, the device for locating a fault cause comprising:

[0030] A data transmission module, used for sending the data collected by each data collection device to the domain controller, and determining a second timestamp of the data collected by each data collection device based on a first timestamp when the domain controller receives the data collected by each data collection device;

[0031] A data processing module, used to process the data based on the modules included in the domain controller, and serialize the data processed by each module and send it to the designated device via the central gateway;

[0032] The target data determination module is used to designate a device to perform deserialization processing on the received data to obtain data collected by each data collection device, and to search for a corresponding relationship table between faults and data based on the faults of the vehicle through the designated device, and to determine each target data corresponding to the fault in the data collected by each data collection device;

[0033] An acquisition module, used for acquiring standard data corresponding to the second timestamp of each target data;

[0034] The information determination module is used to determine that the target data that is different from the corresponding standard data among the various target data is the cause of the fault.

[0035] In conjunction with the second aspect, in one implementation, the data transmission module is used to:

[0036] For each data acquisition device, obtain the message sending time T1 when the message is sent to the domain controller, the message receiving time T2 when the domain controller receives the message, the response message sending time T3 when the domain controller sends a response message to the data acquisition device after receiving the message, and the response message receiving time T4 when the data acquisition device receives the response message;

[0037] Based on T1, T2, T3 and T4, the delay time of the message and the response message during the transmission process is calculated by the first preset formula. The first preset formula is as follows:

[0038]

[0039] Based on T1, T2, T3 and T4, the time difference between the data acquisition device and the domain controller is calculated by the second preset formula. The second preset formula is as follows:

[0040]

[0041] Among them, D1 is used to represent the delay time between the message and the response message during the transmission process, and D2 is used to represent the time difference between the data acquisition device and the domain controller;

[0042] For each data collection device, the difference between the first timestamp corresponding to the collected data received by the domain controller minus D1 and then minus D2 is used as the second timestamp of the data collected by the data collection device.

[0043] In conjunction with the second aspect, in one implementation, the data processing module is used to:

[0044] The perception module contained in the domain controller filters the obstacle data collected by the camera and the obstacle data collected by the radar through the EKF filtering algorithm to obtain the effective obstacle data collected by the camera and the effective obstacle data collected by the radar;

[0045] The effective obstacle data collected by the camera and the effective obstacle data collected by the radar are matched and fused through the Hungarian correlation matching algorithm to obtain fused obstacle information, and the fused obstacle information is sent to the planning module contained in the domain controller;

[0046] The planning module included in the domain controller generates a driving situation map based on the fused obstacle information, high-precision map information and lane line information collected by the camera through A* and polynomial algorithms, plans the vehicle's driving information based on the driving situation map, and sends the planned driving information of the vehicle to the control module included in the domain controller;

[0047] The control module included in the domain controller optimizes the vehicle's control instructions through a fuzzy PID algorithm based on the vehicle's planned driving information, controls the vehicle's driving based on the optimized control instructions, and obtains the vehicle's actual driving information.

[0048] In a third aspect, an embodiment of the present application provides a fault cause locating device, which includes a processor, a memory, and a fault cause locating program stored in the memory and executable by the processor, wherein when the fault cause locating program is executed by the processor, the steps of the fault cause locating method as described above are implemented.

[0049] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a fault cause locating program is stored, wherein when the fault cause locating program is executed by a processor, the steps of the fault cause locating method as described above are implemented.

[0050] The beneficial effects brought by the technical solution provided in the embodiments of the present application include:

[0051] The data collected by each collection device is sent to a domain controller, and the second timestamp of the data collected by each data collection device is determined based on the first timestamp of the data collected by each data collection device received by the domain controller; the data is processed based on each module contained in the domain controller, and the data after each module is serialized and sent to the designated device via the central gateway; the designated device deserializes the received data to obtain the data collected by each data collection device, and searches for the corresponding relationship table between the fault and the data based on the vehicle fault through the designated device, determines the target data corresponding to the fault in the data collected by each data collection device, and filters out the target data related to the vehicle fault in the data collected by each data collection device, thereby reducing the number of data analysis and improving the efficiency of fault cause analysis; obtains the standard data corresponding to the second timestamp of each target data; determines the target data in each target data that is different from the corresponding standard data as the fault cause, does not need to rely on manual analysis of a large amount of collected data, greatly reduces the labor cost, and solves the technical problem in the related technology that when a vehicle fault is detected, the labor cost for problem analysis and positioning based on a large amount of collected data is high and the efficiency is low. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 This is a flow chart of the first embodiment of the method for locating the cause of a fault of the present application;

[0053] Figure 2 For this application Figure 1 A detailed flow chart of step S10;

[0054] Figure 3 For this application Figure 1 Detailed flow chart of step S20;

[0055] Figure 4 This is a functional module diagram of an embodiment of a fault cause location device of the present application;

[0056] Figure 5 This is a schematic diagram of the hardware structure of a fault cause locating device involved in the embodiment of the present application. DETAILED DESCRIPTION

[0057] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. 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.

[0058] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be described in detail below with reference to the accompanying drawings.

[0059] In a first aspect, an embodiment of the present application provides a method for locating the cause of a fault.

[0060] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the fault cause location method of this application. Figure 1 As shown in the figure, the fault cause location method includes:

[0061] Step S10, sending the data collected by each data collection device to the domain controller, and determining the second timestamp of the data collected by each data collection device based on the first timestamp of the data collected by each data collection device received by the domain controller;

[0062] In this embodiment, the data collected by each data collection device is sent to the domain controller, and the second timestamp of the data collected by each data collection device is determined based on the first timestamp when the domain controller receives the data collected by each data collection device, so that the time of the data collected by the data collection device and the time when the domain controller receives the data collected by each data collection device are based on the same benchmark, which facilitates the subsequent positioning and analysis of vehicle failure problems.

[0063] Step S20, processing the data based on the modules included in the domain controller, and serializing the data processed by each module and sending the data to the designated device via the central gateway;

[0064] In this embodiment, the designated device is a general-purpose computer PC or an embedded device. The data collected by each data collection device is processed based on the modules contained in the domain controller, and then the data processed by each module is serialized and sent to the general-purpose computing PC or embedded device via the central gateway. The data processed by each module is serialized to reduce the amount of communication data and ensure data communication security. Among them, serialization is the process of converting the state information of an object into a form that can be stored or transmitted.

[0065] Step S30, the designated device performs deserialization processing on the received data to obtain data collected by each data collection device, and searches for a corresponding relationship table between faults and data based on the faults of the vehicle through the designated device, and determines each target data corresponding to the fault in the data collected by each data collection device;

[0066] In this embodiment, the designated device performs deserialization processing on the received data to obtain the data collected by each data collection device. Deserialization is the process of extracting data from the serialized representation, that is, restoring the ordered byte stream to an object.

[0067] After the designated device obtains the data collected by each data acquisition device, the designated device searches for the correspondence table between the fault and the data based on the fault of the vehicle, and determines the target data corresponding to the fault in the data collected by each data acquisition device. Specifically, if the fault of the vehicle is a sudden turn, the correspondence table between the fault and the data is searched, and the data corresponding to the fault of the sudden turn of the vehicle is determined in the data collected by each data acquisition device. It is easy to understand that the data corresponding to the fault of the sudden turn of the vehicle are the target data. If the data corresponding to the fault of the sudden turn of the vehicle are lane line information data and front obstacle information data, the target data are lane line information data and front obstacle information data. The data collected by each data acquisition device screens out the target data related to the vehicle fault, which greatly reduces the amount of data analysis and improves the efficiency of fault cause analysis.

[0068] Step S40, obtaining standard data corresponding to the second timestamp of each target data;

[0069] In this embodiment, if each target data is lane line information data and front obstacle information data, and the second timestamp of the lane line information data and the second timestamp of the front obstacle information data are time t1, then the standard lane line information data and standard front obstacle information data corresponding to time t1 are obtained.

[0070] Step S50, determining that the target data among the target data that is different from the corresponding standard data is the cause of the fault.

[0071] In this embodiment, the lane line information data collected by the data collection device at time t1 is compared with the standard lane line information data corresponding to time t1, and the front obstacle information data collected by the data collection device at time t1 is compared with the standard front obstacle information data corresponding to time t1. If the lane line information data collected by the data collection device at time t1 is different from the standard lane line information data corresponding to time t1, and the front obstacle information data collected by the data collection device at time t1 is the same as the standard front obstacle information data corresponding to time t1, it is determined that the cause of the sudden turning failure of the vehicle is the error of the lane line information data collected by the data collection device at time t1.

[0072] If the lane line information data collected by the data acquisition device at time t1 is the same as the standard lane line information data corresponding to time t1, and the front obstacle information data collected by the data acquisition device at time t1 is different from the standard front obstacle information data corresponding to time t1, then it is determined that the cause of the vehicle's sudden turning failure is that the front obstacle information data collected by the data acquisition device at time t1 is incorrect.

[0073] If the lane line information data collected by the data acquisition device at time t1 is different from the standard lane line information data corresponding to time t1, and the front obstacle information data collected by the data acquisition device at time t1 is different from the standard front obstacle information data corresponding to time t1, then it is determined that the cause of the vehicle's sudden turning failure is the error in the lane line information data collected by the data acquisition device at time t1 and the error in the front obstacle information data collected by the data acquisition device at time t1.

[0074] In this embodiment, the data collected by each collection device is sent to the domain controller, and the second timestamp of the data collected by each data collection device is determined based on the first timestamp of the data collected by each data collection device received by the domain controller; the data is processed based on each module included in the domain controller, and the data after each module is serialized and sent to the designated device via the central gateway; the designated device deserializes the received data to obtain the data collected by each data collection device, and searches the corresponding relationship table between the fault and the data based on the vehicle fault through the designated device, determines the target data corresponding to the fault in the data collected by each data collection device, and filters out the target data related to the vehicle fault in the data collected by each data collection device, thereby reducing the number of data analysis and improving the efficiency of fault cause analysis; obtains the standard data corresponding to the second timestamp of each target data; determines that the target data in each target data that is different from the corresponding standard data is the fault cause, and does not need to rely on manual analysis of the large amount of collected data, which greatly reduces the labor cost and solves the technical problem in the related technology that when a vehicle fault is detected, the labor cost for problem analysis and positioning based on the large amount of collected data is high and the efficiency is low.

[0075] Further, in one embodiment, referring to Figure 2 , Figure 2 For this application Figure 1 Detailed flow chart of step S10 in FIG. Figure 2 As shown, the step of determining the second timestamp of the data collected by each data collection device based on the first timestamp of the data collected by each data collection device received by the domain controller includes:

[0076] Step S101, for each data acquisition device, obtain the message sending time T1 when the message is sent to the domain controller, the message receiving time T2 when the domain controller receives the message, the response message sending time T3 when the domain controller sends a response message to the data acquisition device after receiving the message, and the response message receiving time T4 when the data acquisition device receives the response message;

[0077] Step S102, based on T1, T2, T3 and T4, the delay time of the message and the response message during the transmission process is calculated by a first preset formula, and the first preset formula is as follows:

[0078]

[0079] Step S103, based on T1, T2, T3 and T4, the time difference between the data acquisition device and the domain controller is calculated by a second preset formula, and the second preset formula is as follows:

[0080]

[0081] Among them, D1 is used to represent the delay time between the message and the response message during the transmission process, and D2 is used to represent the time difference between the data acquisition device and the domain controller;

[0082] Step S104: for each data collection device, the difference between the first timestamp corresponding to the data collected by the domain controller minus D1 and then minus D2 is used as the second timestamp of the data collected by the data collection device.

[0083] In this embodiment, for each data acquisition device, an NTP message is sent to the acquisition device to obtain the message sending time T1 when the message is sent to the domain controller, the message receiving time T2 when the domain controller receives the message, the response message sending time T3 when the domain controller sends a response message to the data acquisition device after receiving the message, and the response message receiving time T4 when the data acquisition device receives the response message;

[0084] Based on T1, T2, T3 and T4, the delay time of the message and the response message during the transmission process is calculated by the first preset formula. The first preset formula is as follows:

[0085]

[0086] Based on T1, T2, T3 and T4, the time difference between the data acquisition device and the domain controller is calculated by the second preset formula. The second preset formula is as follows:

[0087]

[0088] Among them, D1 is used to represent the delay time between the message and the response message during the transmission process, and D2 is used to represent the time difference between the data acquisition device and the domain controller;

[0089] For each data acquisition device, the difference between the first timestamp corresponding to the data collected by the domain controller minus D1 and then minus D2 is used as the second timestamp of the data collected by the data acquisition device. Among them, NTP time synchronization is a time synchronization network technology. In this project, the network UTC time is mainly used for data acquisition device time synchronization to ensure that the data time collected by the data acquisition device and the time when the domain controller receives the data collected by each data acquisition device are based on the same benchmark, which is convenient for the subsequent location and analysis of vehicle fault problems.

[0090] Furthermore, in one embodiment, the data includes obstacle data collected by the camera, obstacle data collected by the radar, and lane line information collected by the camera, referring to Figure 3 , Figure 3 For this application Figure 1 Detailed flow chart of step S20 in FIG. Figure 3 As shown, the step of processing the data based on the modules included in the domain controller includes:

[0091] Step S201: filtering the obstacle data collected by the camera and the obstacle data collected by the radar through an EKF filtering algorithm based on the perception module included in the domain controller to obtain valid obstacle data collected by the camera and the valid obstacle data collected by the radar;

[0092] Step S202, matching and fusing the effective obstacle data collected by the camera and the effective obstacle data collected by the radar through the Hungarian correlation matching algorithm to obtain fused obstacle information, and sending the fused obstacle information to the planning module included in the domain controller;

[0093] Step S203: The planning module included in the domain controller generates a driving situation map based on the fused obstacle information, high-precision map information, and lane line information collected by the camera through A* and polynomial algorithms, plans the vehicle's driving information based on the driving situation map, and sends the planned driving information of the vehicle to the control module included in the domain controller;

[0094] In step S204, the control module included in the domain controller optimizes the control instructions of the vehicle through a fuzzy PID algorithm based on the planned driving information of the vehicle, controls the driving of the vehicle based on the optimized control instructions, and obtains the actual driving information of the vehicle.

[0095] In this embodiment, the data collected by each data collection device includes obstacle data collected by the camera, obstacle data collected by the radar, and lane line information collected by the camera. The perception module contained in the domain controller filters the obstacle data collected by the camera and the obstacle data collected by the radar through the extended Kalman filter (EKF) algorithm to obtain valid obstacle data collected by the camera and the valid obstacle data collected by the radar.

[0096] The effective obstacle data collected by the camera and the effective obstacle data collected by the radar are matched and fused through the Hungarian correlation matching algorithm to obtain fused obstacle information, and the fused obstacle information is sent to the planning module contained in the domain controller;

[0097] The planning module included in the domain controller generates a driving situation map based on the fused obstacle information, high-precision map information and lane line information collected by the camera through A* and polynomial algorithms, plans the vehicle's driving information based on the driving situation map, and obtains the vehicle's planned driving information. Among them, the A* algorithm is a commonly used path finding and graph traversal algorithm; the polynomial algorithm is a type of algorithm whose calculation time does not exceed a polynomial of the initial data amount; the vehicle's planned driving information includes the vehicle's planned driving path, the vehicle's planned speed, the vehicle's planned acceleration and the vehicle's planned heading angle, and the vehicle's planned driving information is sent to the control module included in the domain controller. It is easy to imagine that the vehicle's planned driving information may also include other information about the vehicle during the planned driving process, which is not limited here.

[0098] The control module included in the domain controller optimizes the vehicle's control instructions based on the vehicle's planned driving information through a fuzzy PID algorithm, controls the vehicle's driving based on the optimized control instructions, and obtains the vehicle's actual driving information. Among them, the vehicle's actual driving information includes the vehicle's driving path, speed, acceleration, and heading angle during the vehicle's actual driving process. It is easy to imagine that the vehicle's actual driving information may also include other information about the vehicle during its actual driving process, which is not limited here.

[0099] Furthermore, in one embodiment, the step of serializing the data after each module and sending the data to the designated device via the central gateway comprises:

[0100] The fused obstacle information processed by the perception module included in the domain controller, the planned driving information of the vehicle processed by the planning module included in the domain controller, the actual driving information of the vehicle processed by the control module included in the domain controller, and the vehicle fault detection information output by the system module included in the domain controller are serialized respectively;

[0101] The serialized and fused obstacle information, the serialized vehicle planned driving information, the serialized vehicle actual driving information and the vehicle fault detection information are sent to the designated device via the central gateway.

[0102] In this embodiment, after the perception module included in the domain controller obtains the fused obstacle information, it serializes the fused obstacle information and sends the serialized fused obstacle information to the designated device via the central gateway.

[0103] After the planning module included in the domain controller obtains the planned driving information of the vehicle, it serializes the planned driving information of the vehicle and sends the serialized planned driving information of the vehicle to the designated device via the central gateway.

[0104] After the control module included in the domain controller obtains the actual driving information of the vehicle, it serializes the actual driving information of the vehicle and sends the serialized actual driving information of the vehicle to the designated device via the central gateway.

[0105] After the system module included in the domain controller detects the vehicle fault detection information, it serializes the vehicle fault detection information and sends the serialized vehicle fault detection information to the designated device via the central gateway.

[0106] By serializing the fused obstacle information, the vehicle's planned driving information, the vehicle's actual driving information, and the vehicle's fault detection information, the amount of communication data is reduced and data communication security is ensured.

[0107] Furthermore, in one embodiment, before the step of searching the corresponding relationship table between faults and data based on the faults of the vehicle by the designated device and determining each target data corresponding to the fault in the data collected by each data collection device, the step includes:

[0108] Obtain each fault that the vehicle has experienced and the corresponding impact factor of each fault;

[0109] A corresponding relationship table between faults and data is created based on each fault that has occurred in the vehicle and the influencing factors corresponding to each fault.

[0110] In this embodiment, before searching the correspondence table between faults and data based on the vehicle's faults through designated equipment and determining each target data corresponding to the vehicle's faults in the data collected by each data acquisition device, each fault that has occurred in the vehicle and the influencing factors corresponding to each fault are obtained. For example, the influencing factors corresponding to the sudden turn of the vehicle include the obstacle information ahead and the lane line information ahead. Then the data corresponding to the sudden turn fault of the vehicle is the obstacle information data ahead and the lane line information data ahead.

[0111] A correspondence table between faults and data is created based on each fault that has occurred in the vehicle and the influencing factors corresponding to each fault, so that the data collected by each data acquisition device can be filtered out through the correspondence table between faults and data to filter out data related to the vehicle's faults, reduce the amount of data analysis, and thus improve the efficiency of fault cause analysis.

[0112] In a second aspect, an embodiment of the present application also provides a device for locating the cause of a fault.

[0113] In one embodiment, referring to Figure 4 , Figure 4 This is a functional module diagram of an embodiment of a fault cause location device of the present application. Figure 4 As shown, the fault cause locating device comprises:

[0114] The data transmission module 10 is used to send the data collected by each data collection device to the domain controller, and determine the second timestamp of the data collected by each data collection device based on the first timestamp of the data collected by each data collection device received by the domain controller;

[0115] The data processing module 20 is used to process the data based on the modules included in the domain controller, and to serialize the data processed by each module and send it to the designated device via the central gateway;

[0116] The target data determination module 30 is used to designate a device to perform deserialization processing on the received data to obtain data collected by each data collection device, and to search for a corresponding relationship table between faults and data based on the faults of the vehicle through the designated device, and to determine each target data corresponding to the fault in the data collected by each data collection device;

[0117] An acquisition module 40, configured to acquire standard data corresponding to the second timestamp of each target data;

[0118] The information determination module 50 is used to determine that the target data that is different from the corresponding standard data among the target data is the cause of the fault.

[0119] Furthermore, in one embodiment, the data transmission module 10 is used to:

[0120] For each data acquisition device, obtain the message sending time T1 when the message is sent to the domain controller, the message receiving time T2 when the domain controller receives the message, the response message sending time T3 when the domain controller sends a response message to the data acquisition device after receiving the message, and the response message receiving time T4 when the data acquisition device receives the response message;

[0121] Based on T1, T2, T3 and T4, the delay time of the message and the response message during the transmission process is calculated by the first preset formula. The first preset formula is as follows:

[0122]

[0123] Based on T1, T2, T3 and T4, the time difference between the data acquisition device and the domain controller is calculated by the second preset formula. The second preset formula is as follows:

[0124]

[0125] Among them, D1 is used to represent the delay time between the message and the response message during the transmission process, and D2 is used to represent the time difference between the data acquisition device and the domain controller;

[0126] For each data collection device, the difference between the first timestamp corresponding to the collected data received by the domain controller minus D1 and then minus D2 is used as the second timestamp of the data collected by the data collection device.

[0127] Furthermore, in one embodiment, the data includes obstacle data collected by a camera, obstacle data collected by a radar, and lane line information collected by a camera, and the data processing module 20 is used to:

[0128] The perception module contained in the domain controller filters the obstacle data collected by the camera and the obstacle data collected by the radar through the EKF filtering algorithm to obtain the effective obstacle data collected by the camera and the effective obstacle data collected by the radar;

[0129] The effective obstacle data collected by the camera and the effective obstacle data collected by the radar are matched and fused through the Hungarian correlation matching algorithm to obtain fused obstacle information, and the fused obstacle information is sent to the planning module contained in the domain controller;

[0130] The planning module included in the domain controller generates a driving situation map based on the fused obstacle information, high-precision map information and lane line information collected by the camera through A* and polynomial algorithms, plans the vehicle's driving information based on the driving situation map, and sends the planned driving information of the vehicle to the control module included in the domain controller;

[0131] The control module included in the domain controller optimizes the vehicle's control instructions through a fuzzy PID algorithm based on the vehicle's planned driving information, controls the vehicle's driving based on the optimized control instructions, and obtains the vehicle's actual driving information.

[0132] Furthermore, in one embodiment, the data processing module 20 is used to:

[0133] The fused obstacle information processed by the perception module included in the domain controller, the planned driving information of the vehicle processed by the planning module included in the domain controller, the actual driving information of the vehicle processed by the control module included in the domain controller, and the vehicle fault detection information output by the system module included in the domain controller are serialized respectively;

[0134] The serialized fused obstacle information, the serialized vehicle planned driving information, the serialized vehicle actual driving information and the vehicle fault detection information are sent to the designated device via the central gateway.

[0135] Furthermore, in one embodiment, the fault cause locating device further includes a new module for:

[0136] Obtain each fault that the vehicle has experienced and the corresponding impact factor of each fault;

[0137] A corresponding relationship table between faults and data is created based on each fault that has occurred in the vehicle and the influencing factors corresponding to each fault.

[0138] Among them, the functional implementation of each module in the above-mentioned fault cause locating device corresponds to each step in the above-mentioned fault cause locating method embodiment, and its functions and implementation processes are no longer repeated here one by one.

[0139] In a third aspect, an embodiment of the present application provides a fault cause location device, which may be a personal computer (PC), a laptop computer, a server, or other device with a data processing function.

[0140] Reference Figure 5 , Figure 5 Schematic diagram of the hardware structure of the fault cause location device involved in the embodiment of the present application. In the embodiment of the present application, the fault cause location device may include a processor, a memory, a communication interface and a communication bus.

[0141] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0142] The communication interface includes input / output (I / O) interface, physical interface and logical interface, etc., which are used to realize the interconnection of devices inside the fault cause location device, and the interface used to realize the interconnection of the fault cause location device with other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, an optical fiber interface, an ATM interface, etc.; the user device can be a display (Display), a keyboard (Keyboard), etc.

[0143] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0144] The processor may be a general-purpose processor, and the general-purpose processor may call the fault cause location program stored in the memory and execute the fault cause location method provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the fault cause location program is called may refer to the various embodiments of the fault cause location method of the present application, and will not be repeated here.

[0145] Those skilled in the art will understand that Figure 5 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0146] In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium.

[0147] The computer-readable storage medium of the present application stores a fault cause locating program, wherein when the fault cause locating program is executed by a processor, the steps of the fault cause locating method as described above are implemented.

[0148] Among them, the method implemented when the fault cause locating program is executed can refer to the various embodiments of the fault cause locating method of the present application, and will not be repeated here.

[0149] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0150] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

[0151] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0152] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0153] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0154] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0155] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for locating the cause of a fault, characterized in that: The fault cause locating method comprises: Sending the data collected by each data collection device to the domain controller, and determining a second timestamp of the data collected by each data collection device based on a first timestamp when the domain controller receives the data collected by each data collection device; The data is processed based on the modules included in the domain controller, and the data processed by each module is serialized and sent to the designated device via the central gateway; The designated device performs deserialization processing on the received data to obtain data collected by each data collection device, and searches for a corresponding relationship table between faults and data based on the faults of the vehicle through the designated device, and determines each target data corresponding to the fault in the data collected by each data collection device; Acquire standard data corresponding to the second timestamp of each target data; Determining that target data among the target data that is different from the corresponding standard data is the cause of the fault; The step of determining the second timestamp of the data collected by each data collection device based on the first timestamp of the data collected by each data collection device received by the domain controller comprises: For each data acquisition device, obtain the message sending time T1 when the message is sent to the domain controller, the message receiving time T2 when the domain controller receives the message, the response message sending time T3 when the domain controller sends a response message to the data acquisition device after receiving the message, and the response message receiving time T4 when the data acquisition device receives the response message; Based on T1, T2, T3 and T4, the delay time of the message and the response message during the transmission process is calculated by the first preset formula. The first preset formula is as follows: Based on T1, T2, T3 and T4, the time difference between the data acquisition device and the domain controller is calculated by the second preset formula. The second preset formula is as follows: Among them, D1 is used to represent the delay time between the message and the response message during the transmission process, and D2 is used to represent the time difference between the data acquisition device and the domain controller; For each data collection device, the difference between the first timestamp corresponding to the data collected by the domain controller minus D1 and then minus D2 is used as the second timestamp of the data collected by the data collection device; The data includes obstacle data collected by a camera, obstacle data collected by a radar, and lane line information collected by a camera. The step of processing the data based on the modules included in the domain controller includes: The perception module contained in the domain controller filters the obstacle data collected by the camera and the obstacle data collected by the radar through the EKF filtering algorithm to obtain the effective obstacle data collected by the camera and the effective obstacle data collected by the radar; The effective obstacle data collected by the camera and the effective obstacle data collected by the radar are matched and fused through the Hungarian correlation matching algorithm to obtain fused obstacle information, and the fused obstacle information is sent to the planning module contained in the domain controller; The planning module included in the domain controller generates a driving situation map based on the fused obstacle information, high-precision map information and lane line information collected by the camera through A* and polynomial algorithms, plans the vehicle's driving information based on the driving situation map, and sends the planned driving information of the vehicle to the control module included in the domain controller; The control module included in the domain controller optimizes the vehicle's control instructions through a fuzzy PID algorithm based on the vehicle's planned driving information, controls the vehicle's driving based on the optimized control instructions, and obtains the vehicle's actual driving information.

2. The method for locating the cause of a fault according to claim 1, characterized in that: The step of serializing the data processed by each module and sending the data to the designated device via the central gateway comprises: The fused obstacle information processed by the perception module included in the domain controller, the planned driving information of the vehicle processed by the planning module included in the domain controller, the actual driving information of the vehicle processed by the control module included in the domain controller, and the vehicle fault detection information output by the system module included in the domain controller are serialized respectively; The serialized and fused obstacle information, the serialized vehicle planned driving information, the serialized vehicle actual driving information and the vehicle fault detection information are sent to the designated device via the central gateway.

3. The method for locating the cause of a fault according to claim 1, characterized in that: Before the step of searching the corresponding relationship table between faults and data based on the faults of the vehicle by the designated device and determining each target data corresponding to the fault in the data collected by each data collection device, the method includes: Obtain each fault that the vehicle has experienced and the corresponding impact factor of each fault; A corresponding relationship table between faults and data is created based on each fault that has occurred in the vehicle and the influencing factors corresponding to each fault.

4. A fault cause location device, characterized in that: The fault cause locating device comprises: A data transmission module, used for sending the data collected by each data collection device to the domain controller, and determining a second timestamp of the data collected by each data collection device based on a first timestamp when the domain controller receives the data collected by each data collection device; A data processing module, used to process the data based on the modules included in the domain controller, and serialize the data processed by each module and send it to the designated device via the central gateway; The target data determination module is used to designate a device to perform deserialization processing on the received data to obtain data collected by each data collection device, and to search for a corresponding relationship table between faults and data based on the faults of the vehicle through the designated device, and to determine each target data corresponding to the fault in the data collected by each data collection device; An acquisition module, used for acquiring standard data corresponding to the second timestamp of each target data; An information determination module, used for determining that target data among the target data that is different from the corresponding standard data is the cause of the fault; Data transmission module for: For each data acquisition device, obtain the message sending time T1 when the message is sent to the domain controller, the message receiving time T2 when the domain controller receives the message, the response message sending time T3 when the domain controller sends a response message to the data acquisition device after receiving the message, and the response message receiving time T4 when the data acquisition device receives the response message; Based on T1, T2, T3 and T4, the delay time of the message and the response message during the transmission process is calculated by the first preset formula. The first preset formula is as follows: Based on T1, T2, T3 and T4, the time difference between the data acquisition device and the domain controller is calculated by the second preset formula. The second preset formula is as follows: Among them, D1 is used to represent the delay time between the message and the response message during the transmission process, and D2 is used to represent the time difference between the data acquisition device and the domain controller; For each data collection device, the difference between the first timestamp corresponding to the data collected by the domain controller minus D1 and then minus D2 is used as the second timestamp of the data collected by the data collection device; Data processing module for: The perception module contained in the domain controller filters the obstacle data collected by the camera and the obstacle data collected by the radar through the EKF filtering algorithm to obtain the effective obstacle data collected by the camera and the effective obstacle data collected by the radar; The effective obstacle data collected by the camera and the effective obstacle data collected by the radar are matched and fused through the Hungarian correlation matching algorithm to obtain fused obstacle information, and the fused obstacle information is sent to the planning module contained in the domain controller; The planning module included in the domain controller generates a driving situation map based on the fused obstacle information, high-precision map information and lane line information collected by the camera through A* and polynomial algorithms, plans the vehicle's driving information based on the driving situation map, and sends the planned driving information of the vehicle to the control module included in the domain controller; The control module included in the domain controller optimizes the vehicle's control instructions through a fuzzy PID algorithm based on the vehicle's planned driving information, controls the vehicle's driving based on the optimized control instructions, and obtains the vehicle's actual driving information.

5. A fault cause location device, characterized in that: The fault cause locating device comprises a processor, a memory, and a fault cause locating program stored in the memory and executable by the processor, wherein when the fault cause locating program is executed by the processor, the steps of the fault cause locating method according to any one of claims 1 to 3 are implemented.

6. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a fault cause locating program, wherein when the fault cause locating program is executed by a processor, the steps of the fault cause locating method according to any one of claims 1 to 3 are implemented.