A vehicle instrument abnormality analysis method, device, equipment and medium

Abstract

Embodiments of the present application disclose a vehicle instrument abnormality analysis method, device, equipment and medium. The method comprises: acquiring a test case result and a test log file of a vehicle instrument, and determining a fault classification category of the vehicle instrument according to a keyword in the test case result; determining an abnormality of the vehicle instrument according to the fault classification category, the test log file and an interface document; and determining a display abnormality reason of the vehicle instrument according to the abnormality. According to the embodiments of the present application, the fault classification category of the vehicle instrument is determined through the keyword, the abnormality of the vehicle instrument is determined according to the fault classification category, the test log file and the interface document, and the display abnormality reason of the vehicle instrument is determined, so that the problem that multiple parties need to communicate when the vehicle instrument is abnormal to analyze the instrument fault can be solved, time cost and development cost are reduced, and simple and fast classification of the fault and automatic instrument abnormality troubleshooting of the classified fault are realized.

Description

Technical Field

[0001] This invention relates to the field of automatic troubleshooting technology for automotive instrument panel malfunctions, and in particular to a method, device, equipment, and medium for analyzing vehicle instrument panel malfunctions. Background Technology

[0002] The LCD instrument cluster industry is experiencing rapid market growth due to mature related technologies. With the development of intelligent vehicles, LCD instrument clusters, as one of the mainstream visual interaction solutions for automobiles in the coming years, will gradually become a standard feature of intelligent vehicles. In the future, with the development of intelligent vehicles, in order to gain a competitive edge and achieve better human-machine experience optimization, more and more automakers will adopt a self-developed approach to create matching LCD instrument clusters. Compared with previous mechanical instrument clusters, LCD instrument clusters no longer rely solely on the dashboard to display single information such as vehicle speed and RPM. The instrument display corresponding to the driver's side also incorporates vehicle infotainment functions, multi-screen interaction, or text-based fault alarm prompts, enriching both human-machine interaction and the user's driving experience.

[0003] However, due to the complexity of the display logic and content of vehicle instrument clusters, a black screen could be caused by hardware or software issues. Inconsistencies between the central control display and the instrument cluster display could be due to data processing errors at the system level or data transmission errors at the adaptation layer. The absence of warning lights and text indicators could be due to false alarm signals being triggered by the instrument cluster. Furthermore, designers of various functions, underlying system developers, instrument cluster software application developers, and even testers cannot solve these problems independently. Each fault requires multi-party communication and confirmation before a solution can be found, increasing costs and time while also placing a heavy workload on the system. Therefore, there is an urgent need for an automated method to analyze and deduce the causes of vehicle instrument cluster malfunctions. Summary of the Invention

[0004] In view of this, the present invention provides a method, apparatus, device and medium for analyzing vehicle instrument panel anomalies, which can solve the problem of needing multiple parties to communicate to analyze instrument panel faults when analyzing vehicle instrument panel anomalies, reduce time and development costs, and achieve simple and quick classification of faults and automated instrument panel anomaly troubleshooting after classification.

[0005] According to one aspect of the present invention, an embodiment of the present invention provides a method for analyzing vehicle instrument anomalies, the method comprising:

[0006] Obtain the test case results and test log files of the vehicle instrument panel, and determine the fault classification category of the vehicle instrument panel based on the keywords in the test case results;

[0007] The abnormal conditions of the vehicle's instruments are determined based on the fault classification categories, test log files, and predefined interface documents;

[0008] The cause of the abnormal display on the vehicle's instrument panel is determined based on the aforementioned abnormal situation.

[0009] According to another aspect of the present invention, embodiments of the present invention also provide a vehicle instrument panel anomaly analysis device, the device comprising:

[0010] The category determination module is used to obtain the test case results and test log files of the vehicle instrument panel, and determine the fault classification category of the vehicle instrument panel based on the keywords in the test case results;

[0011] An anomaly determination module is used to determine the anomaly status of the vehicle instrument panel based on the fault classification category, test log file, and predefined interface document;

[0012] The cause determination module is used to determine the cause of the abnormal display of the vehicle instrument panel based on the abnormal situation.

[0013] According to another aspect of the present invention, embodiments of the present invention also provide an electronic device, the electronic device comprising:

[0014] At least one processor; and

[0015] A memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the vehicle instrument anomaly analysis method according to any embodiment of the present invention.

[0017] According to another aspect of the present invention, embodiments of the present invention also provide a computer-readable storage medium storing computer instructions for causing a processor to execute and implement the vehicle instrument anomaly analysis method according to any embodiment of the present invention.

[0018] The technical solution of this invention determines the fault category of the vehicle instrument panel by using keywords in the test case results, determines the abnormal situation of the vehicle instrument panel based on the fault category, test log file and predefined interface document, and determines the cause of the abnormal display of the vehicle instrument panel based on the abnormal situation. This can solve the problem of needing multiple parties to communicate to analyze the instrument panel fault when an abnormality occurs, reduce time and development costs, and achieve simple and quick fault classification and automated instrument panel anomaly troubleshooting after classification.

[0019] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 A flowchart of a vehicle instrument panel anomaly analysis method provided in an embodiment of the present invention;

[0022] Figure 2 A flowchart of another vehicle instrument anomaly analysis method provided in an embodiment of the present invention;

[0023] Figure 3 This is a schematic diagram of a test case result provided in an embodiment of the present invention;

[0024] Figure 4 This is a structural block diagram of a vehicle instrument anomaly analysis device provided in an embodiment of the present invention;

[0025] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0026] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0028] In one embodiment, Figure 1 This is a flowchart of a vehicle instrument panel anomaly analysis method provided in an embodiment of the present invention. This embodiment is applicable to the situation of analyzing vehicle instrument panel anomalies during the development stage. The method can be executed by a vehicle instrument panel anomaly analysis and processing device, which can be implemented in hardware and / or software and can be configured in an electronic device.

[0029] like Figure 1 As shown, this method is applied to the vehicle manufacturer, and the method specifically includes the following steps:

[0030] S110. Obtain the test case results and test log files of the vehicle instrument panel, and determine the fault classification category of the vehicle instrument panel based on the keywords in the test case results.

[0031] The test case results can be understood as the test case report obtained by testers based on the product designer's requirements document. The test log file refers to the test log file generated during bench testing when testers simulate corresponding signals. This simulation process includes the interface ID passed during the test, the index value corresponding to that interface ID, the interface description, the interface function, parameter types, and parameter values.

[0032] In this embodiment, the fault classification category refers to the possible categories corresponding to the faults of the vehicle instrument panel. Of course, different fault functions are caused by different reasons within the instrument panel fault categories. The fault classification categories can be divided into various fault categories such as indicator light faults, warning light and text prompt faults, function display faults, and multi-screen interaction faults. This allows for a general classification of possible faults of the vehicle instrument panel, filtering according to different categories, and then classifying the faults based on the filtering results.

[0033] In this embodiment, during test integration, testers will compile test cases based on the product designer's requirements document. Testers can manually input specified signals according to the user's input. If the test phenomenon does not match the expected test value, the testers will describe the current phenomenon to form the test case results for the vehicle instrument panel. These test case results will include at least: the user-input operation information, the test phenomenon, and the expected test value. In this embodiment, keywords can be extracted from the test phenomena within the test case results, and the vehicle instrument panel faults can be classified according to the extracted keywords to obtain corresponding fault classification categories. In some embodiments, the test phenomena in the test case results can also be graded, and the vehicle instrument panel faults can be classified according to the grade information and fault index. This embodiment does not impose any limitations on this method.

[0034] S120. Determine the abnormal conditions of the vehicle's instruments based on the fault classification category, test log file, and predefined interface documentation.

[0035] The interface document refers to the predefined interface-related documents. These predefined interface documents may include, but are not limited to, the first interface document corresponding to the indicator light, the second interface document corresponding to the alarm light and text prompts, the third interface document corresponding to the function display, and the fourth interface document corresponding to the multi-screen interaction. It should be noted that each interface document may include, but is not limited to, the interface ID, interface description, interface function, the interface index value corresponding to the interface ID, the transmission parameter type, and the parameter value.

[0036] In this embodiment, abnormal conditions of the vehicle instrument panel may include, but are not limited to, the failure to transmit the interface ID, errors in the parameter value and / or parameter type transmitted during the transmission of the interface ID when the interface ID is transmitted, and errors in the display of the vehicle instrument panel even though the parameter value and / or parameter type transmitted during the transmission of the interface ID is correct.

[0037] In this embodiment, under different fault classification categories, the abnormal condition of the vehicle instrument can be determined by matching the test log file during the test with the corresponding interface ID, interface description, interface function, interface index value corresponding to the interface ID, transmission parameter type and parameter value in the predefined interface document. In this embodiment, the test log file includes the test log file corresponding to different fault classification categories.

[0038] In some embodiments, when the fault classification category is indicator light fault, the first interface transmission status is determined based on the first test log file and the first interface document corresponding to the vehicle instrument cluster, and the first type of abnormal condition of the vehicle instrument cluster is determined based on the first interface transmission status. In some embodiments, when the fault classification category is warning light and text prompt fault, the second type of abnormal condition of the vehicle instrument cluster is determined based on the second test log file, the second interface document, and the preset alarm priority level corresponding to the vehicle instrument cluster. In another embodiment, when the fault classification category is function display fault, the third type of abnormal condition of the vehicle instrument cluster is determined based on the third test log file and the third interface document corresponding to the vehicle instrument cluster. In still other embodiments, when the fault classification category is function display fault, the fourth type of abnormal condition of the vehicle instrument cluster is determined based on the fourth test log file and the fourth interface document corresponding to the vehicle instrument cluster. In still other embodiments, the fault analysis script in the host computer can be enabled, the map file of the vehicle instrument cluster can be imported, the fault index of the map file can be decomposed according to a predetermined priority, and the response information of the vehicle instrument cluster can be parsed into vehicle fault data based on the index data to analyze the abnormality of the vehicle instrument cluster.

[0039] S130. Determine the cause of the abnormal display on the vehicle's instrument panel based on the abnormal situation.

[0040] In this embodiment, the abnormal display of the vehicle instrument panel may include one or more causes. Different abnormal situations correspond to different vehicle instrument panel fault categories. Accordingly, the abnormal display causes corresponding to different abnormal situations may be the same or different. In some embodiments, if the abnormal situation is that the transmitted interface ID cannot be found in the pre-defined interface document, it indicates that the interface has not been transmitted. In this case, it suggests that the underlying development logic has not been implemented. This can be understood as the host's internal implementation not being implemented, and the abnormal display of the vehicle's instrument cluster is due to a problem with the host. Conversely, if the transmitted interface ID is found in the pre-defined interface document and is correct, but one of the corresponding parameter values ​​or types is incorrect, it indicates that the transmitted parameters are abnormal. In this case, the underlying development logic has not been implemented, leading to the abnormal instrument cluster display. In some embodiments, if the interface transmission is normal, and the parameter type, value, and index corresponding to the interface ID are transmitted correctly, but the vehicle's instrument cluster still displays an error, it indicates that the vehicle's instrument cluster is not implementing the corresponding function according to the parameter values ​​or types transmitted by the host. This means the instrument cluster itself is the cause of the abnormal display. Of course, besides the abnormal situations described above that determine the cause of the abnormal display of the vehicle's instrument cluster, other aspects may also be included, which will not be described in detail in this embodiment.

[0041] The technical solution of this invention determines the fault category of the vehicle instrument panel by using keywords in the test case results, determines the abnormal situation of the vehicle instrument panel based on the fault category, test log file and predefined interface document, and determines the cause of the abnormal display of the vehicle instrument panel based on the abnormal situation. This can solve the problem of needing multiple parties to communicate to analyze the instrument panel fault when an abnormality occurs, reduce time and development costs, and achieve simple and quick fault classification and automated instrument panel anomaly troubleshooting after classification.

[0042] In one embodiment, Figure 2 This is a flowchart of another vehicle instrument panel anomaly analysis method provided in an embodiment of the present invention. Based on the above embodiments, this embodiment further refines the determination of vehicle instrument panel fault classification categories based on keywords in test case results, and the determination of vehicle instrument panel anomalies based on fault classification categories, test log files, and predefined interface documents.

[0043] like Figure 2 As shown, the vehicle instrument panel anomaly analysis method in this embodiment may specifically include the following steps:

[0044] S210. Obtain the test case results and test log files of the vehicle instrument panel, and extract keywords from the test phenomena in the test case results using Boolean expressions.

[0045] The test case results should include at least: user input operation information, test phenomena, and test expected values.

[0046] In this embodiment, test case results from the vehicle's instrument panel and test log files can be obtained. Keywords from the test phenomena within the test case results are extracted using Boolean expressions. These keywords include at least: low beam headlights, high beam headlights off, turn signals, fog lights, text prompts, bulb malfunction, anti-theft malfunction, tire pressure information, driving mode, coolant temperature, ambient temperature, navigation, music, and news. In this embodiment, to facilitate a better understanding of the test case results... Figure 3 This is a schematic diagram of a test case result provided in an embodiment of the present invention. In this embodiment, the tester will input a specified signal according to the operator's manual test, simulate the actual vehicle operation on the test bench, and make a judgment based on the existing requirement description and the instrument display content. When the displayed content is inconsistent with the description, the tester will input the current displayed content in the phenomenon. For example... Figure 3 As shown, the test case results include a description of the test, the operation signals input by the tester, the phenomena observed during the test, the expected values ​​of the test, and the test regression conditions.

[0047] S220. When the test phenomenon and the test expectation are inconsistent, classify the faults of the vehicle instrument according to keywords to obtain the corresponding fault classification categories. The fault classification categories include: indicator light faults, warning light and text prompt faults, function display faults, and multi-screen interaction faults.

[0048] In this embodiment, if the test phenomenon in the test case result is inconsistent with the expected test value, it indicates that the test result is a problematic test case. In this case, by extracting keywords from the test phenomenon, the faults of the vehicle instrument panel can be classified according to the keywords to obtain the corresponding fault classification categories. Since different faults are caused by different reasons, and the handling methods and developers / designers of different faults are also different, in order to facilitate the rapid dissemination and resolution of problems, it is first necessary to classify the test faults according to the above-mentioned problems. For example, when the keywords are low beam headlights, high beam headlights, turn signals, and fog lights, they are classified as indicator light faults; when the keywords are bulb fault alarm, anti-theft fault alarm, and tire pressure information indication, they are classified as warning light and text faults.

[0049] For ease of understanding, Table 1 provides a quality attribute corresponding to each fault category in this embodiment of the invention. Each category includes corresponding quality examples, allowing designers to continuously enrich the quality attributes while developing product requirements. In testers' test reports, unlike other texts such as comments, benchmarking reports, and product descriptions which contain diverse information, each test case only contains the text of the current tested function. Therefore, no additional text preprocessing or semantic word expansion is required. By vectorizing the above quality attribute definitions, test cases are matched with keywords one by one. If a case contains a category, it is assigned to the corresponding category. For example, in "After operations 1 and 2, the rear fog lights do not display," the case contains "rear fog lights," thus it belongs to the display light fault category.

[0050] Table 1: Fault Attributes Corresponding to Different Fault Types

[0051] Indicator light Alarm lights and classical Chinese text Function display Multi-screen interaction Left turn signal Light bulb malfunction alarm Driving Mode navigation Right turn signal Anti-theft fault alarm Coolant temperature music low beam headlights Tire pressure information reminder Ambient temperature outside the vehicle news

[0052] S230. When the fault classification category is indicator light fault, determine the first interface transmission status based on the first test log file and first interface document corresponding to the vehicle instrument, and determine the first type of abnormal situation of the vehicle instrument based on the first interface transmission status.

[0053] The first test log file includes the first test interface ID, the index value corresponding to the first test interface ID, and the interface description.

[0054] In this embodiment, the predefined interface documents include: a first interface document corresponding to the indicator lights, a second interface document corresponding to the alarm lights and text prompts, a third interface document corresponding to the function display, and a fourth interface document corresponding to multi-screen interaction. The interface documents corresponding to different fault categories are different. Specifically, when the fault category is indicator light failure, the first interface document corresponding to the indicator lights is used; when the fault category is alarm lights and text prompts failure, the second interface document corresponding to alarm lights and text prompts is used; when the fault category is function display failure, the third interface document corresponding to function display is used; and when the fault category is multi-screen interaction failure, the fourth interface document corresponding to multi-screen interaction is used.

[0055] In this embodiment, when the fault classification is a display light fault, the first interface transmission status is determined based on the first test log file and the first interface document corresponding to the vehicle instrument cluster, and the first type of abnormal situation of the vehicle instrument cluster is determined based on the first interface transmission status. Specifically, the first interface ID that matches the first test interface ID in the first test log file, as well as the index value and interface description corresponding to the first interface ID, are searched in the first interface document to determine the first type of abnormal situation based on the matching result.

[0056] In one embodiment, the first type of abnormal situation includes: interface transmission abnormality. The first interface transmission status is determined based on the first test log file and the first interface document corresponding to the vehicle instrument cluster, and the first type of abnormal situation of the vehicle instrument cluster is determined based on the first interface transmission status, including:

[0057] The first interface document is used to find the first interface ID that matches the first test interface ID in the first test log file. The first interface document includes: the first interface ID, the index value corresponding to the first interface ID, and the interface description.

[0058] If the first interface ID is not found, it is determined that the vehicle instrument panel did not receive a display signal and the first test interface ID was not transmitted.

[0059] If the first interface ID is found, then it is determined whether the index value and interface description corresponding to the first interface ID are consistent with the index value and interface description corresponding to the first test interface ID. If they are consistent, it is determined that the vehicle instrument display is normal; if they are inconsistent, it is determined that the parameter transmission corresponding to the first interface ID is abnormal.

[0060] In this embodiment, a first interface ID matching the first test interface ID in the first test log file is searched in the first interface document. If the first interface ID is not found, it is determined that the vehicle instrument panel has not received a display signal and the first test interface ID has not been transmitted. If the first interface ID is found, it is further determined whether the index value and interface description corresponding to the first interface ID are consistent with the index value and interface description corresponding to the first test interface ID. If they are consistent, it is determined that the vehicle instrument panel display is normal. If they are inconsistent, it is determined that the parameter transmission corresponding to the first interface ID is abnormal. The first interface document includes: the first interface ID, the index value corresponding to the first interface ID, and the interface description.

[0061] For example, to better understand the abnormal situation when the fault classification is indicator light failure, Table 1 shows the relevant interface definitions in the first interface document. Each indicator light has a corresponding separate interface, which are defined one by one in the interface document as shown in Table 2:

[0062] Table 2 defines some indicator light interfaces.

[0063] TelltaleID Index illustrate TTID_TURNLEFT 1 Left turn signal TTID_TURNRIGHT 2 Right turn signal TTID_LOWBEAM 3 low beam headlights

[0064] In this embodiment, when the indicator light malfunctions, it is necessary to determine whether the interface is transmitting data by checking the test interface ID, the index value corresponding to the test interface ID, and the interface description in the vehicle's test log file. When the tester performs bench testing, the corresponding signal will be simulated. If the indicator light cannot be displayed normally, it is necessary to determine whether the interface is transmitting data and whether the interface parameters transmitted by the interface are incorrect. That is, the cause of the fault is found by determining whether the interface is transmitting data. If the corresponding interface is not found in the simulated bench, it means that the instrument application has not received the display signal, and the instrument indicator light displays abnormally.

[0065] S240. When the fault classification category is warning light and text prompt fault, determine the second type of abnormal situation of the vehicle instrument based on the second test log file, the second interface document and the pre-set alarm priority level of the vehicle instrument.

[0066] The second test log file includes the second test interface ID, the corresponding index value, and the interface description. In this embodiment, when the vehicle encounters an emergency malfunction or matters requiring user attention, the driver will be alerted through the instrument panel display, such as various warning lights and text prompts. Due to the limited size of the instrument panel interface, several warning lights share a reserved position, and the priority of the warning light is determined by the instrument panel alarm priority.

[0067] In this embodiment, when the fault classification is a warning light and text message fault, the second type of abnormal situation of the vehicle instrument is determined based on the second test log file, the second interface document, and the pre-set alarm priority level of the vehicle instrument. Specifically, the second interface document is searched for a second interface ID that matches the second test interface ID in the second test log file, and the index value and interface description of the second interface ID are checked to see if they are consistent with the index value and interface description of the second test interface ID, thus determining that the parameter transmission of the second test interface ID is abnormal. The warning light and text message information in the test case results are extracted by image recognition method, and the second test interface ID that matches the warning light and text message information, as well as the index value and interface description of the second test interface ID, are matched in the second interface document. Based on the alarm priority level, the second test interface ID, and the index value and interface description of the second test interface ID, it is checked whether it is a priority level signal mis-transmission.

[0068] In one embodiment, the second abnormal situation includes: interface transmission abnormality and priority level abnormality. The second type of abnormal situation for the vehicle instrument panel is determined based on the second test log file corresponding to the vehicle instrument panel, the second interface document, and the pre-set alarm priority level, including:

[0069] The system searches for a second interface ID in the second interface document that matches the second test interface ID in the second test log file. If no second interface ID is found, it is determined that the vehicle instrument panel did not receive a display signal, and the second test interface ID was not transmitted. If a second interface ID is found, it is further determined whether the index value and interface description corresponding to the second interface ID are consistent with those corresponding to the second test interface ID. If they are consistent, it is determined that the vehicle instrument panel display is normal; if they are inconsistent, it is determined that the parameter transmission corresponding to the second test interface ID is abnormal. The second interface document includes: the second interface ID, the index value corresponding to the second interface ID, and the interface description.

[0070] The alarm light and text information in the test case results are extracted using image recognition methods. The second test interface ID, the index value and interface description corresponding to the alarm light and text information are matched in the second interface document. Based on the alarm priority level, the second test interface ID, the index value and interface description corresponding to the second test interface ID, it is determined whether the signal is a false alarm of the priority level.

[0071] In this embodiment, a second interface ID matching the second test interface ID in the second test log file is searched in the second interface document. If the second interface ID is not found, it is determined that the vehicle instrument panel has not received a display signal and the second test interface ID has not been transmitted. If the second interface ID is found, it is further determined whether the index value and interface description corresponding to the second interface ID are consistent with the index value and interface description corresponding to the second test interface ID. If they are consistent, it is determined that the vehicle instrument panel display is normal; if they are inconsistent, it is determined that the parameter transmission corresponding to the second test interface ID is abnormal. The second interface document includes: the second interface ID, the index value corresponding to the second interface ID, and the interface description. In some embodiments, the alarm light and text information in the test case results are extracted by image recognition method. The second test interface ID, the index value corresponding to the second test interface ID, and the interface description are matched in the second interface document. The alarm priority level, the second test interface ID, and the index value and interface description corresponding to the second test interface ID are then used to check whether the priority level signal is mistakenly transmitted.

[0072] For example, to better understand the abnormal situations when the fault classification is alarm light and text prompt fault, Table 2 shows the relevant interface definitions in the second interface document. There is a corresponding separate interface for each alarm light and text prompt, which will be defined one by one in the interface document as shown in Table 3:

[0073] Table 3 lists some alarm lights and their corresponding classical Chinese prompts.

[0074]

[0075] Unlike indicator light malfunctions, the above interface transmissions are handled by the underlying system based on instrument alarm priority logic. The system then transmits the higher-priority interface to the instrument application. If the current alarm light or text is detected during testing, it indicates that the system is not transmitting the corresponding signal, or that the current signal priority is being mistakenly overridden by a higher-priority signal. For the first scenario, the method is the same as for indicator light malfunctions: check the vehicle's test log file to see if an interface anomaly is the cause. For the second problem, for the currently displayed alarm light or text, image recognition is used to automatically extract the current alarm light and text information, match the corresponding function and interface ID, and then compare it with the instrument alarm priority to check if a signal mistransmission is the cause. As shown in Table 4, if the priority of the currently displayed function signal is lower than the priority of the undisplayed abnormal text, but it is still displayed on the instrument panel, the system needs to re-check the logic code.

[0076] Table 4 Examples of Instrument Alarm Priorities

[0077] Function Priority Text (Chinese) DSM Level 1 Text Prompt 4.1 Please take a break. Left rear brake light malfunction 6.1 Left rear brake light malfunction Seatbelt not fastened 10 Seatbelt not fastened

[0078] S250. When the fault classification category is a function display fault, determine the third type of abnormality of the vehicle instrument based on the third test log file and the third interface document corresponding to the vehicle instrument.

[0079] The third test log file includes the third test interface ID, interface function, and the transmission parameter type and parameter value corresponding to the third test interface ID.

[0080] In this embodiment, when the fault classification is a functional display fault, the third type of abnormality of the vehicle instrument is determined based on the third test log file and the third interface document corresponding to the vehicle instrument. Specifically, the interface information and parameter information in the third test log file and the third interface document are compared respectively, and the abnormality of the third test interface ID transmission is determined based on the comparison result. If the third test interface ID is transmitted correctly, the target parameter that matches the transmission parameter type, parameter value, and interface function corresponding to the third test interface ID in the third test log file is searched in the third interface document, and the abnormality of the parameter corresponding to the interface transmission is determined based on the target parameter, interface function, transmission parameter type, and parameter value.

[0081] In one embodiment, the third type of abnormal situation includes: interface transmission abnormality and parameter abnormality corresponding to interface transmission. The third type of abnormal situation of the vehicle instrument is determined based on the third test log file and the third interface document corresponding to the vehicle instrument.

[0082] Find the third interface ID in the third interface document that matches the third test interface ID in the third test log file, and determine the abnormal situation of the third test interface ID transmission based on the matching result;

[0083] If the third test interface ID is transmitted correctly, find the target parameter in the third interface document that matches the transmission parameter type, parameter value, and interface function of the third test interface ID in the third test log file, and determine the parameter exception situation corresponding to the interface transmission based on the target parameter, interface function, transmission parameter type, and parameter value. The target parameter includes: the third interface ID in the third interface document, the interface function corresponding to the third interface ID, the transmission parameter type, and the parameter value.

[0084] In this embodiment, a third interface ID matching the third test interface ID in the third test log file is searched in the third interface document. If the third interface ID cannot be found, it is determined that the vehicle instrument panel did not receive a display signal and the third interface ID was not transmitted. If the third interface ID can be found and the third test interface ID is transmitted correctly, a target parameter matching the transmission parameter type, parameter value, and interface function corresponding to the third test interface ID in the third test log file is searched in the third interface document. Based on the target parameter, interface function, transmission parameter type, and parameter value, the parameter anomaly corresponding to the interface transmission is determined. The target parameter includes: the third interface ID in the third interface document, the interface function corresponding to the third interface ID, the transmission parameter type, and the parameter value.

[0085] For example, to better understand the abnormal situation when the fault classification is "functional display fault," the functional display, as the third display part of the LCD screen in the instrument cluster, adds an interface display and descriptions of the vehicle's design and system functions. Each function has a corresponding display effect to enhance human-machine interaction. The difference from the above is that each function is displayed as a functional interface, as shown in Table 5:

[0086] Table 5. Definitions of Some Functional Interfaces

[0087]

[0088] In this embodiment, after locating the instrument display function, the corresponding test interface is matched through the interface documentation, which is represented by the interface name in Table 4. Each interface represents a function. There are three types of instrument interfaces, each with different defined parameters. If no corresponding display occurs after the mode sends the specified signal in the instrument display, it indicates that the instrument application has not received the corresponding function interface, or the data sent by the system layer is incorrect. For the first case, the method described above is the same: log is used to detect whether the interface is lost. For the second case, the corresponding interface name and defined parameter type are found through the interface table. The parameters passed by this interface are found in the vehicle system test log file, and it is determined whether the parameters are incorrect. There are three parameter types: Int, double, and bool. If the parameter type of the interface API is Int, it means that the passed value can only be an integer. For example, if [0, 2] is defined, then the passed data can only contain the values ​​0, 1, and 2. Any value passed that is not one of these three values ​​is considered incorrect. If the parameter type of the API is double, it means that the value passed is floating point. The value passed can be within a range. For example, if the fuel level is defined as 0-100, then the data passed is acceptable as long as it is within this range.

[0089] S260. When the fault classification category is functional display fault, determine the fourth type of abnormality of the vehicle instrument based on the fourth test log file and the fourth interface document corresponding to the vehicle instrument.

[0090] The fourth test log file includes the fourth test interface ID and the corresponding JSON string.

[0091] In this embodiment, when the fault classification category is a functional display fault, the fourth type of abnormal situation of the vehicle instrument is determined according to the fourth test log file and the fourth interface document corresponding to the vehicle instrument. Specifically, the JSON string in the fourth test log file is matched with the transmission parameter type and parameter value in the fourth interface document to obtain the matching result. Based on the matching result, the transmission parameter abnormal situation of the fourth interface ID is determined.

[0092] In one embodiment, the fourth type of abnormal situation includes: abnormal transmission parameters. The fourth type of abnormal situation for the vehicle instrument cluster is determined based on the fourth test log file and the fourth interface document corresponding to the vehicle instrument cluster, including:

[0093] The JSON string in the fourth test log file is matched with the parameter types and values ​​in the fourth interface document to obtain the matching results. The JSON string includes at least the parameter values, parameter types, and connection methods passed by the interface. The fourth interface document includes: the fourth interface ID, the parameter values ​​and parameter types corresponding to the fourth interface ID.

[0094] Based on the matching results, determine the abnormality of the transmission parameters of the fourth interface ID.

[0095] In this embodiment, the JSON string in the fourth test log file is matched with the parameter type and parameter value in the fourth interface document to obtain the matching result. The JSON string includes at least the parameter value, parameter type, and connection method transmitted by the interface. The fourth interface document includes: the fourth interface ID, the parameter value and parameter type corresponding to the fourth interface ID. If the two match, it is determined that the parameter transmitted by the fourth interface ID is normal. If one of them does not match, it is determined that the parameter transmitted by the fourth interface ID is incorrect.

[0096] For example, to better understand the abnormal situation when the fault classification is multi-screen interaction fault, multi-screen interaction involves the application layer of the central control system transmitting data to the adaptation layer, which then passes it to the system layer. The system layer then transmits the data to the instrument panel. The instrument panel does not have the ability to process this data; it only displays the data transmitted from the system layer. The function of multi-screen interaction is to transmit JSON strings according to the interface definition, as shown in Table 6, IC communication protocol:

[0097] Table 6 Partial Function Definitions

[0098]

[0099]

[0100] In this embodiment, in Table 5, each function is defined according to the format of a JSON string, including the function type, the meaning of the assigned value, and the attached data function interface. If the current display does not match the central control, the interface in the log is matched with the interface defined in the interface document, and the transmitted parameters are compared with the defined parameters. The transmitted parameters are used to determine whether they are transmitted according to the defined interface parameters. If not, it means that they are different.

[0101] S270. Determine the cause of the abnormal display on the vehicle's instrument panel based on the abnormal situation.

[0102] Specifically, in the case of an indicator light malfunction where the interface is not transmitted, it indicates that the underlying development logic is not implemented. This can be understood as the failure to transmit the interface ID suggesting that the host's internal functionality is not working, causing the instrument cluster display to malfunction. This can be addressed by troubleshooting step-by-step. Similarly, in the case of an indicator light malfunction where the interface parameter is transmitted incorrectly, it also indicates that the underlying development logic is not implemented, leading to the instrument cluster display malfunction. Likewise, the situations where the warning light and text prompt malfunctions, functional display malfunctions, and multi-screen interaction malfunctions all involve an interface not transmitted, are consistent with the situation described above for the indicator light malfunction. In some embodiments, when a display light malfunctions and the abnormal condition is due to incorrect transmitted parameter information, it indicates that the underlying development logic has not been implemented, leading to abnormal instrument display. Similarly, the causes of malfunctions in warning lights and text prompts (due to incorrect interface parameter transmission), functional display malfunctions (due to incorrect interface parameter transmission), and multi-screen interaction malfunctions (due to incorrect interface parameter transmission) are all consistent with the aforementioned causes of incorrect interface parameter transmission. In some embodiments, if the interface transmission is normal, and the parameter type, parameter value, and index corresponding to the interface ID are transmitted normally, but the vehicle instrument display is incorrect, it indicates that the vehicle instrument has not implemented the corresponding function according to the parameter value or parameter type transmitted by the host, meaning that the instrument itself is the cause of the abnormal instrument display.

[0103] The technical solution described in this invention extracts keywords from test phenomena within test case results using Boolean expressions, classifies vehicle instrument panel faults according to these keywords to obtain corresponding fault categories. When the fault category is a display light fault, the first interface transmission status is determined based on the first test log file and first interface document corresponding to the vehicle instrument panel, and a first type of abnormal condition of the vehicle instrument panel is determined based on the first interface transmission status. When the fault category is a warning light and text prompt fault, a second type of abnormal condition of the vehicle instrument panel is determined based on the second test log file, second interface document, and pre-set alarm priority level corresponding to the vehicle instrument panel. When the fault category is a functional display fault, a third type of abnormal condition of the vehicle instrument panel is determined based on the third test log file and third interface document corresponding to the vehicle instrument panel. When the fault category is a multi-screen interaction fault, a fourth type of abnormal condition of the vehicle instrument panel is determined based on the fourth test log file and fourth interface document corresponding to the vehicle instrument panel. This further solves the problem of needing multiple parties to communicate and analyze instrument panel faults when troubleshooting, reducing time and development costs, and achieving simple and quick fault classification and automated troubleshooting of the classified faults.

[0104] In one embodiment, Figure 4 This is a structural block diagram of a vehicle instrument panel anomaly analysis device according to an embodiment of the present invention. This device is suitable for analyzing vehicle instrument panel anomalies during the development phase and can be implemented in hardware or software. It can be configured in an electronic device to implement a vehicle instrument panel anomaly analysis and processing method according to an embodiment of the present invention.

[0105] like Figure 4 As shown, the device is applied at the vehicle factory end, and the device includes: a category determination module 410, an anomaly determination module 420, and a cause determination module 430.

[0106] The category determination module 410 is used to obtain the test case results and test log files of the vehicle instrument, and determine the fault classification category of the vehicle instrument based on the keywords in the test case results.

[0107] The anomaly determination module 420 is used to determine the anomaly of the vehicle instrument based on the fault classification category, test log file and predefined interface document;

[0108] The cause determination module 430 is used to determine the cause of the abnormal display of the vehicle instrument based on the abnormal situation.

[0109] In this embodiment of the invention, the category determination module identifies the fault category of the vehicle instrument panel based on keywords in the test case results; the anomaly determination module determines the anomaly of the vehicle instrument panel based on the fault category, test log files, and predefined interface documents; and the cause determination module determines the cause of the display anomaly of the vehicle instrument panel based on the anomaly. This solves the problem of needing multiple parties to communicate and analyze instrument panel faults when troubleshooting anomalies, reducing time and development costs, and enabling simple and quick fault classification and automated troubleshooting of the classified faults.

[0110] In one embodiment, the category determination module 410 includes at least one of the following:

[0111] An extraction unit is used to extract keywords from the test phenomena within the test case results using Boolean expressions; wherein the keywords include at least: low beam headlights, high beam headlights off, turn signals, fog lights, text prompts, bulb malfunction, anti-theft malfunction, driving mode, coolant temperature, ambient temperature, navigation, music, and news; wherein the test case results include at least: user-input operation information, test phenomena, and test expectations.

[0112] The classification unit is used to classify the faults of the vehicle instrument according to the keywords when the test phenomenon and the test expectation are inconsistent, so as to obtain the corresponding fault classification categories; wherein, the fault classification categories include: indicator light faults, warning light and text prompt faults, function display faults, and multi-screen interaction faults.

[0113] In one embodiment, the predefined interface documents include: a first interface document corresponding to the indicator lights, a second interface document corresponding to the alarm lights and text prompts, a third interface document corresponding to the function display, and a fourth interface document corresponding to multi-screen interaction; the anomaly determination module 420 includes:

[0114] The first type of anomaly determination unit is used to determine the first interface transmission status based on the first test log file corresponding to the vehicle instrument and the first interface document when the fault classification category is indicator light fault, and to determine the first type of anomaly status of the vehicle instrument based on the first interface transmission status; wherein, the first test log file includes a first test interface ID, an index value corresponding to the first test interface ID, and an interface description.

[0115] The second type of anomaly determination unit is used to determine the second type of anomaly of the vehicle instrument based on the second test log file corresponding to the vehicle instrument, the second interface document, and the pre-set alarm priority level when the fault classification category is a warning light and text prompt fault; wherein, the second test log file includes a second test interface ID, the index value corresponding to the second test interface ID, and an interface description;

[0116] The third type of anomaly determination unit is used to determine the third type of anomaly of the vehicle instrument based on the third test log file corresponding to the vehicle instrument and the third interface document when the fault classification category is a functional display fault; wherein, the third test log file includes the third test interface ID, interface function, transmission parameter type and parameter value corresponding to the third test interface ID;

[0117] The fourth type of anomaly determination unit is used to determine the fourth type of anomaly of the vehicle instrument based on the fourth test log file corresponding to the vehicle instrument and the fourth interface document when the fault classification category is a functional display fault; wherein, the fourth test log file includes a fourth test interface ID and a JSON string corresponding to the fourth test interface ID.

[0118] In one embodiment, the first type of abnormal situation includes: interface transmission abnormality; the first type of abnormality determination unit includes:

[0119] The first interface lookup subunit is used to find the first interface ID in the first interface document that matches the first test interface ID in the first test log file; wherein, the first interface document includes: the first interface ID, the index value corresponding to the first interface ID, and the interface description;

[0120] The first result determination subunit is used to determine that the vehicle instrument panel has not received a display signal and the first test interface ID has not been transmitted if the first interface ID is not found.

[0121] The second result determination subunit is used to determine whether the index value and interface description corresponding to the first interface ID are consistent with the index value and interface description corresponding to the first test interface ID if the first interface ID is found. If they are consistent, the vehicle instrument display is determined to be normal; if they are inconsistent, the parameter transmission corresponding to the first interface ID is determined to be abnormal.

[0122] In one embodiment, the second abnormal situation includes: interface transmission abnormality and priority level abnormality; the second type of abnormality determination unit includes:

[0123] The interface transmission exception subunit is used to search for a second interface ID in the second interface document that matches the second test interface ID in the second test log file. If the second interface ID is not found, it is determined that the vehicle instrument panel has not received a display signal and the second test interface ID has not been transmitted. If the second interface ID is found, it is further determined whether the index value and interface description corresponding to the second interface ID are consistent with the index value and interface description corresponding to the second test interface ID. If they are consistent, it is determined that the vehicle instrument panel display is normal. If they are inconsistent, it is determined that the parameter transmission corresponding to the second test interface ID is abnormal. The second interface document includes: the second interface ID, the index value corresponding to the second interface ID, and the interface description.

[0124] The priority signal mistransmission subunit is used to extract alarm light and text information from the test case results using image recognition methods, match the second test interface ID that matches the alarm light and text information in the second interface document, as well as the index value and interface description corresponding to the second test interface ID, and check whether it is a priority level signal mistransmission based on the alarm priority level, the second test interface ID, and the index value and interface description corresponding to the second test interface ID.

[0125] In one embodiment, the third type of abnormal situation includes: interface transmission abnormality and parameter abnormality corresponding to interface transmission. The third type of abnormality determination unit includes:

[0126] The interface transmission exception subunit is used to find the third interface ID in the third interface document that matches the third test interface ID in the third test log file, and determine the transmission exception of the third test interface ID based on the matching result ID.

[0127] The interface transmission parameter exception subunit is used to, when the third test interface ID is transmitted correctly, search in the third interface document for a target parameter that matches the transmission parameter type, parameter value, and interface function corresponding to the third test interface ID in the third test log file, and determine the parameter exception situation corresponding to the interface transmission based on the target parameter, interface function, transmission parameter type, and parameter value; wherein, the target parameter includes: the third interface ID in the third interface document, the interface function corresponding to the third interface ID, the transmission parameter type, and the parameter value.

[0128] In one embodiment, the fourth type of abnormal situation includes: abnormal transmission parameters; the fourth type of abnormality determination unit includes:

[0129] The matching subunit is used to match the JSON string in the fourth test log file with the parameter types and values ​​in the fourth interface document to obtain a matching result. The JSON string includes at least the parameter values, parameter types, and connection methods transmitted by the interface. The fourth interface document includes: the fourth interface ID, the parameter values ​​and parameter types corresponding to the fourth interface ID.

[0130] A subunit is determined to identify any abnormalities in the transmission parameters of the fourth interface ID based on the matching results.

[0131] The vehicle instrument anomaly analysis and processing device provided in this embodiment of the invention can execute the vehicle instrument anomaly analysis and processing method applied to the vehicle manufacturer provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0132] In one embodiment, Figure 5 This is a schematic diagram of an electronic device provided for an embodiment of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0133] like Figure 5 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0134] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0135] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as vehicle instrument anomaly analysis methods.

[0136] In some embodiments, the vehicle instrument cluster anomaly analysis processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the vehicle instrument cluster anomaly analysis method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the vehicle instrument cluster anomaly analysis method by any other suitable means (e.g., by means of firmware).

[0137] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0138] Computer programs used to implement the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable vehicle instrument anomaly analysis device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on the machine, partially on the machine, as a standalone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0139] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0140] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0141] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0142] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0143] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0144] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for analyzing vehicle instrument panel anomalies, characterized in that, include: Obtain the test case results and test log files of the vehicle instrument panel, and determine the fault classification category of the vehicle instrument panel based on the keywords in the test case results; The abnormal conditions of the vehicle's instruments are determined based on the fault classification categories, test log files, and predefined interface documents; Determine the cause of the abnormal display on the vehicle's instrument panel based on the aforementioned abnormal situation; The step of determining the fault classification category of the vehicle instrument panel based on keywords in the test case results includes: Keywords in the test phenomena within the test case results are extracted using Boolean expressions; wherein, the test case results include at least: user-input operation information, test phenomena, and test expectations. When the test phenomenon and the expected test value are inconsistent, the faults of the vehicle instrument are classified according to the keywords to obtain the corresponding fault classification categories; wherein, the fault classification categories include: indicator light faults, warning light and text prompt faults, function display faults, and multi-screen interaction faults; The predefined interface documents include: a first interface document corresponding to the indicator lights, a second interface document corresponding to the alarm lights and text prompts, a third interface document corresponding to the function display, and a fourth interface document corresponding to the multi-screen interaction. The test log file refers to the test log file generated during bench testing when the tester simulates the corresponding signals. This simulation includes the interface ID transmitted during the test, the index value corresponding to the interface ID, the interface description, the interface function, the parameter type, and the parameter value. Under different fault classification categories, the abnormal conditions of the vehicle's instruments are determined by matching the test log file during the test with the corresponding interface ID, the index value corresponding to the interface ID, the interface description, the interface function, the parameter type, and the parameter value in the predefined interface document.

2. The method according to claim 1, characterized in that, The step of determining the abnormal condition of the vehicle instrument panel based on the fault classification category and the predefined interface document includes: When the fault classification category is indicator light fault, the first interface transmission status is determined based on the first test log file corresponding to the vehicle instrument and the first interface document, and the first type of abnormal situation of the vehicle instrument is determined based on the first interface transmission status; wherein, the first test log file includes the first test interface ID, the index value corresponding to the first test interface ID, and the interface description. When the fault classification category is warning light and text prompt fault, the second type of abnormal situation of the vehicle instrument is determined according to the second test log file corresponding to the vehicle instrument, the second interface document, and the pre-set alarm priority level; wherein, the second test log file includes the second test interface ID, the index value corresponding to the second test interface ID, and the interface description; When the fault classification category is a functional display fault, the third type of abnormality of the vehicle instrument is determined based on the third test log file corresponding to the vehicle instrument and the third interface document; wherein, the third test log file includes the third test interface ID, interface function, transmission parameter type and parameter value corresponding to the third test interface ID; In the case where the fault classification category is multi-screen interaction fault, the fourth type of abnormal situation of the vehicle instrument is determined based on the fourth test log file corresponding to the vehicle instrument and the fourth interface document; wherein, the fourth test log file includes the fourth test interface ID and the JSON string corresponding to the fourth test interface ID.

3. The method according to claim 2, characterized in that, The first type of abnormal situation includes: interface transmission abnormality. The step of determining the first interface transmission status based on the first test log file corresponding to the vehicle instrument cluster and the first interface document, and determining the first type of abnormal situation of the vehicle instrument cluster based on the first interface transmission status, includes: The first interface document is used to find the first interface ID that matches the first test interface ID in the first test log file; wherein, the first interface document includes: the first interface ID, the index value corresponding to the first interface ID, and the interface description; If the first interface ID is not found, it is determined that the vehicle instrument panel has not received a display signal and the first test interface ID has not been transmitted. If the first interface ID is found, then it is further determined whether the index value and interface description corresponding to the first interface ID are consistent with the index value and interface description corresponding to the first test interface ID. If they are consistent, it is determined that the vehicle instrument display is normal; if they are inconsistent, it is determined that the parameter transmission corresponding to the first interface ID is abnormal.

4. The method according to claim 2, characterized in that, The second type of abnormal situation includes: interface transmission abnormality and priority level abnormality. The determination of the second type of abnormal situation of the vehicle instrument based on the second test log file corresponding to the vehicle instrument, the second interface document, and the pre-set alarm priority level includes: The system searches for a second interface ID in the second interface document that matches the second test interface ID in the second test log file. If the second interface ID is not found, it is determined that the vehicle instrument panel has not received a display signal and the second test interface ID has not been transmitted. If the second interface ID is found, it is further determined whether the index value and interface description corresponding to the second interface ID are consistent with the index value and interface description corresponding to the second test interface ID. If they are consistent, it is determined that the vehicle instrument panel display is normal. If they are inconsistent, it is determined that the parameter transmission corresponding to the second test interface ID is abnormal. The second interface document includes: the second interface ID, the index value corresponding to the second interface ID, and the interface description. The alarm light and text information in the test case results are extracted using image recognition methods. The second test interface ID, the index value and interface description corresponding to the alarm light and text information are matched in the second interface document. Based on the alarm priority level, the second test interface ID, the index value and interface description corresponding to the second test interface ID, it is determined whether the signal is a false alarm of the priority level.

5. The method according to claim 2, characterized in that, The third type of abnormal situation includes: interface transmission abnormalities and corresponding parameter abnormalities during interface transmission. The determination of the third type of abnormal situation of the vehicle instrument based on the third test log file corresponding to the vehicle instrument and the third interface document includes: Search for the third interface ID in the third interface document that matches the third test interface ID in the third test log file, and determine the abnormal situation of the third test interface ID transmission based on the matching result; If the third test interface ID is transmitted correctly, the target parameter that matches the transmission parameter type, parameter value, and interface function of the third test interface ID in the third test log file is searched in the third interface document. Based on the target parameter, interface function, transmission parameter type, and parameter value, the parameter anomaly situation corresponding to the interface transmission is determined. The target parameter includes: the third interface ID in the third interface document, the interface function corresponding to the third interface ID, the transmission parameter type, and the parameter value.

6. The method according to claim 2, characterized in that, The fourth type of abnormal situation includes: abnormal transmission parameters. The determination of the fourth type of abnormal situation of the vehicle instrument based on the fourth test log file corresponding to the vehicle instrument and the fourth interface document includes: The JSON string in the fourth test log file is matched with the parameter types and values ​​in the fourth interface document to obtain the matching result. The JSON string includes at least the parameter values, parameter types, and connection methods passed by the interface. The fourth interface document includes: the fourth interface ID, the parameter values ​​and parameter types corresponding to the fourth interface ID. Based on the matching results, determine the abnormality of the transmission parameters of the fourth interface ID.

7. A vehicle instrument panel anomaly analysis device, characterized in that, include: The category determination module is used to obtain the test case results and test log files of the vehicle instrument panel, and determine the fault classification category of the vehicle instrument panel based on the keywords in the test case results; An anomaly determination module is used to determine the anomaly status of the vehicle instrument panel based on the fault classification category, test log file, and predefined interface document; The cause determination module is used to determine the cause of the abnormal display of the vehicle instrument panel based on the abnormal situation. The category determination module includes at least one of the following: An extraction unit is used to extract keywords from the test phenomena within the test case results using Boolean expressions; wherein the test case results include at least: user-input operation information, test phenomena, and test expectations. A classification unit is used to classify the faults of the vehicle instrument according to the keywords when the test phenomenon and the test expectation are inconsistent, so as to obtain the corresponding fault classification categories; wherein, the fault classification categories include: indicator light faults, warning light and text prompt faults, function display faults, and multi-screen interaction faults; The predefined interface documents include: a first interface document corresponding to the indicator lights, a second interface document corresponding to the alarm lights and text prompts, a third interface document corresponding to the function display, and a fourth interface document corresponding to the multi-screen interaction. The test log file refers to the test log file generated during bench testing when the tester simulates the corresponding signals. This simulation includes the interface ID transmitted during the test, the index value corresponding to the interface ID, the interface description, the interface function, the parameter type, and the parameter value. Under different fault classification categories, the abnormal conditions of the vehicle's instruments are determined by matching the test log file during the test with the corresponding interface ID, the index value corresponding to the interface ID, the interface description, the interface function, the parameter type, and the parameter value in the predefined interface document.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the vehicle instrument anomaly analysis method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the vehicle instrument anomaly analysis method according to any one of claims 1-6.

Images