Test method and device, electronic equipment and storage medium

Abstract

The invention provides a test method and device, electronic equipment and a storage medium, and the method comprises the steps: carrying out the fault simulation operation of a domain controller of a vehicle, and monitoring the target parameters of the domain controller after the fault simulation operation, the fault simulation operation comprises ground short circuit fault simulation operation, power supply short circuit fault simulation operation and overload fault simulation operation; monitoring a target parameter of the domain controller, and performing a fault report test on the domain controller based on the target parameter to obtain a fault report test result; if the fault report test result indicates that the domain controller performs fault report after performing the fault simulation operation, continuing to monitor target parameters of the domain controller, and performing a fault recovery test on the domain controller; and obtaining a fault recovery test result according to the monitored target parameter. According to the method and the device, the efficiency of testing the domain controller can be improved, testing and analysis are performed by monitoring the target parameters in real time, the accuracy of data is ensured, and personal errors are reduced.

Description

[0001] Technology Neighborhood

[0002] The present application relates to the field of autonomous driving technology, and more specifically, to a testing method, device, electronic device and storage medium. Background Art

[0003] With the rapid development of science and technology, the application of autonomous driving or assisted driving functions in vehicles is becoming more and more popular. In order to ensure the safety of vehicles when using autonomous driving or assisted driving functions, it is necessary to conduct multi-faceted tests on the domain controllers used to implement autonomous driving or assisted driving functions in advance. However, the current testing methods are mostly manual operations, which are inefficient and prone to errors. Therefore, how to improve the testing efficiency and accuracy of domain controllers has become an urgent problem to be solved. Summary of the invention

[0004] In view of this, the embodiments of the present application propose a testing method, device, electronic device and storage medium to improve the above problems.

[0005] According to a first aspect of an embodiment of the present application, a testing method is provided, the method comprising: performing a fault simulation operation on a domain controller of a vehicle, and monitoring target parameters of the domain controller after the fault simulation operation, wherein the fault simulation operation comprises a ground short circuit fault simulation operation, a power supply short circuit fault simulation operation, and an overload fault simulation operation; monitoring the target parameters of the domain controller, and performing a fault error reporting test on the domain controller based on the target parameters to obtain a fault error reporting test result; if the fault error reporting test result indicates that the domain controller reports a fault error after the fault simulation operation, continuing to monitor the target parameters of the domain controller, and performing a fault recovery test on the domain controller; and obtaining a fault recovery test result according to the monitored target parameters.

[0006] According to a second aspect of an embodiment of the present application, a testing device is provided, the device comprising: a fault simulation module, used to perform a fault simulation operation on a domain controller of a vehicle, and to monitor target parameters of the domain controller after the fault simulation operation, wherein the fault simulation operation comprises a short-circuit fault simulation operation to ground, a short-circuit fault simulation operation to a power supply, and an overload fault simulation operation; a fault error testing module, used to monitor the target parameters of the domain controller, and to perform a fault error testing on the domain controller based on the target parameters to obtain a fault error testing result; a monitoring module, used to continue to monitor the target parameters of the domain controller and to perform a fault recovery testing on the domain controller if the fault error testing result indicates that the domain controller reports a fault error after the fault simulation operation; and a fault recovery testing result determining module, used to obtain a fault recovery testing result according to the monitored target parameters.

[0007] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising: a processor; and a memory, wherein computer-readable instructions are stored in the memory, and when the computer-readable instructions are executed by the processor, the test method described above is implemented.

[0008] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor, the test method described above is implemented.

[0009] In the scheme of the present application, a fault simulation operation is first performed on the domain controller, wherein the fault simulation test includes a short-circuit fault simulation operation to the ground, a short-circuit fault simulation operation to the power supply, and an overload fault simulation operation, so as to monitor the target parameters of the domain controller after the fault simulation operation, and then perform a fault error test on the domain controller according to the monitored target parameters to obtain a fault error test result, so that the fault error test result indicates that the domain controller reports a fault error after the fault simulation operation, and continues to monitor the target parameters of the domain controller, and performs a fault recovery test on the domain controller, and then can obtain a fault recovery test result according to the monitored target parameters. The scheme of the present application tests whether the domain controller will report a fault error and whether it can automatically recover from the fault by performing fault simulations of different faults on the domain controller, thereby improving the efficiency of testing the domain controller, and testing and analyzing by real-time monitoring of target parameters to ensure the accuracy of the data and reduce human errors.

[0010] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0012] Figure 1 It is a testing device for implementing a testing method according to an embodiment of the present application.

[0013] Figure 2 It is a flowchart of a testing method according to an embodiment of the present application.

[0014] Figure 3 It is a flowchart of a testing method according to another embodiment of the present application.

[0015] Figure 4 It is a flowchart showing the specific steps of step 270 according to another embodiment of the present application.

[0016] Figure 5 It is a flowchart of a testing method according to another embodiment of the present application.

[0017] Figure 6 It is a flowchart showing the specific steps of step 360 according to another embodiment of the present application.

[0018] Figure 7 It is a flowchart of a testing method according to another embodiment of the present application.

[0019] Figure 8 It is a flowchart showing the specific steps of step 480 according to another embodiment of the present application.

[0020] Fig. 9 It is a flowchart of a testing method according to yet another embodiment of the present application.

[0021] Fig.10 is a block diagram of a testing device according to an embodiment of the present application.

[0022] Fig.11 It is a hardware structure diagram of an electronic device according to an embodiment of the present application.

[0023] Through the above-mentioned drawings, clear embodiments of the present invention have been shown, which will be described in more detail hereinafter. These drawings and textual descriptions are not intended to limit the scope of the present invention in any way, but to illustrate the concept of the present invention for those skilled in the art through specific embodiments. DETAILED DESCRIPTION

[0024] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; on the contrary, these embodiments are provided so that this application will be more comprehensive and complete, and the concept of example embodiments will be fully conveyed to technicians in the field.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof 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 necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0026] Figure 1 is a test device for implementing a test method according to an embodiment of the present application, such as Figure 1 As shown, the test equipment A1 includes a voltage acquisition module A11, a temperature acquisition module A12, a first programmable relay A13, a second programmable relay A14, a power short-circuit relay A15, a ground short-circuit relay A16, an overload relay A17 and other relays A18, wherein the test equipment is connected to a domain controller A2 and a CAN tool A3 respectively, the domain controller A2 is connected to a central controller A4 of the vehicle, the CAN tool A3 is connected to an electronic device A5, and the electronic device A5 is communicatively connected to a cloud server A6. Among them, the cloud server A6 is used to monitor the test data and analyze the data in real time; the electronic device A5 is used to upload the monitored data to the cloud server A6; the CAN tool A3 is used to monitor the bus communication between the domain controller A2 and the central controller A4 of the vehicle, for example, the signals related to the power distribution status include power distribution signals, fault signals, current value signals, etc. The first programmable relay A13 and the second programmable relay A14 are used to control the fault test of the power short-circuit relay A15, the ground short-circuit relay A16, and the overload relay A17; the temperature acquisition module A12 is used to detect the temperature of the wire and send the temperature value to the electronic device A5; the voltage acquisition module A11 is used to detect the voltage value of the power distribution port of the domain controller A4, and send the voltage value to the electronic device A5; the central controller A4 of the vehicle is used to control the domain controller for fault recovery.

[0027] See also Figure 2 , Figure 2The test method provided by an embodiment of the present application is shown. In a specific embodiment, the test method can be applied to Fig.10 The test device 600 and the electronic device 700 equipped with the test device 600 are shown in FIG. Fig.11 ). The specific process of this embodiment will be described below. Of course, it can be understood that the method can be executed by a vehicle terminal with computing and processing capabilities. Figure 2 The process shown is described in detail, and the testing method may specifically include the following steps:

[0028] Step 110, performing a fault simulation operation on a domain controller of the vehicle, and monitoring target parameters of the domain controller after the fault simulation operation, wherein the fault simulation operation includes a ground short circuit fault simulation operation, a power supply short circuit fault simulation operation, and an overload fault simulation operation.

[0029] As a way, due to the increasing demand for the use of domain controllers in vehicles, in order to enable the domain controller to ensure the safety of the vehicle during driving, the domain controller in the vehicle needs to be tested before the vehicle leaves the factory, so that the domain controller can be set in the vehicle for use if the test of the domain controller meets the use of the vehicle. The test of the domain controller can include a fault error test and a fault recovery test of the domain controller.

[0030] Optionally, a fault error test on the domain controller can be performed by creating corresponding different faults on the pins to be tested of the domain controller, and then determining whether the domain controller will report the corresponding fault error after the fault occurs, so as to determine whether the domain controller can report the fault in time when the fault occurs.

[0031] Optionally, the domain controller can be simulated for faults through the cloud-based automated domain controller power distribution test bench, and the corresponding faults of the domain controller can be created based on the characteristics of the fault. For example, when performing a power short circuit fault error test, the voltage of the domain controller's power supply port can be set to 0, and the voltage of the corresponding non-powered port can be set to the power supply voltage, so as to simulate the power short circuit fault of the domain controller; when performing a ground short circuit fault error test, the power supply port of the domain controller can be short-circuited to the ground, so as to simulate the ground short circuit fault of the domain controller; when performing an overload fault error test, the current of the power supply port of the domain controller can be increased, so as to simulate the overload fault of the domain controller.

[0032] Optionally, in order to determine whether the domain controller can report a fault in time after a fault simulation operation is performed on the domain controller, the parameters that can determine the occurrence of the fault can be monitored, so as to facilitate real-time monitoring of whether the domain controller reports an error for the corresponding fault simulation operation, thereby improving the accuracy of the fault reporting test of the domain controller. Optionally, the target parameter can include at least one of the voltage corresponding to the target port of the domain controller, the current corresponding to the target port of the domain controller, the network message corresponding to the domain controller, the temperature of the wire connected to the domain controller, or the temperature of the wire of the domain controller.

[0033] Step 120: monitor the target parameters of the domain controller, and perform a fault error test on the domain controller based on the target parameters to obtain a fault error test result.

[0034] As a method, since the target parameter is a parameter that can reflect the fault of the domain controller after the fault occurs, the domain controller can be tested for fault reporting by the monitored target parameter. Optionally, if the target parameter includes the network message corresponding to the domain controller, it can be determined based on the CAN network bus signal in the network message whether the domain controller reports a fault through the network message after the corresponding fault occurs. Optionally, if the target parameter includes the voltage or current of the target port or the pin to be tested of the domain controller, it can be determined whether the change is caused by the corresponding fault based on the change in the voltage or current of the target port or the pin to be tested of the domain controller.

[0035] Optionally, the fault error reporting test may include the domain controller reporting a fault, the domain controller not reporting a fault, the domain controller reporting a fault but the fault is different from the fault corresponding to the fault simulation operation, and the domain controller reporting a fault but the fault is the same as the fault corresponding to the fault simulation operation.

[0036] Step 130: If the fault error reporting test result indicates that the domain controller reports a fault error after performing the fault simulation operation, the target parameters of the domain controller continue to be monitored, and a fault recovery test is performed on the domain controller.

[0037] As a method, when it is determined that the result of the fault error test indicates that the domain controller has reported a fault error after fault simulation, it can be determined that the domain controller is capable of reporting a fault error. In order to enable the domain controller to meet factory standards and usage standards, the target parameters of the domain controller can continue to be monitored. In this way, it can be determined based on the monitored target parameters whether the domain controller is capable of autonomous fault recovery in the event of a fault, thereby ensuring the security of the domain controller in actual applications.

[0038] Optionally, when performing a fault recovery test on a domain controller, the fault recovery test on the domain controller can be performed through an automated program using a test bench for automated testing of the intelligent power distribution domain controller connected to the domain controller. The fault recovery test on the domain controller can also be performed through a cloud processor connected to the domain controller for communication. The domain controller can also be tested by a tester using a test device.

[0039] Step 140: Obtain a fault recovery test result according to the monitored target parameters.

[0040] As a method, the target parameter may be the same parameter as the target parameter corresponding to the fault report, or may be a different parameter. For example, the network message in the target parameter after fault recovery is the network message after fault recovery, which is different from the network message detected when the corresponding fault occurs in the domain controller.

[0041] Optionally, the fault recovery test result may include a fault recovery test success and a fault recovery test failure, or a fault recovery test meeting a design state and a fault recovery test not meeting a design state. Optionally, the fault recovery test on the domain controller may perform a recovery operation according to a specific fault of the fault simulation operation on the domain controller.

[0042] In an embodiment of the present application, a fault simulation operation is first performed on the domain controller, wherein the fault simulation test includes a short-circuit fault simulation operation to the ground, a short-circuit fault simulation operation to the power supply, and an overload fault simulation operation, so as to monitor the target parameters of the domain controller after the fault simulation operation, and then perform a fault error test on the domain controller according to the monitored target parameters to obtain a fault error test result, so that the fault error test result indicates that the domain controller reports a fault error after the fault simulation operation, and continues to monitor the target parameters of the domain controller, and performs a fault recovery test on the domain controller, and then can obtain a fault recovery test result according to the monitored target parameters. The scheme of the present application tests whether the domain controller will report a fault error and whether it can automatically recover from the fault by performing fault simulations of different faults on the domain controller, thereby improving the efficiency of testing the domain controller, and testing and analyzing by real-time monitoring of target parameters to ensure the accuracy of the data and reduce human errors.

[0043] See also Figure 3 , Figure 3 The test method provided by an embodiment of the present application is shown. The specific process of this embodiment will be described below. Of course, it can be understood that the method can be executed by a vehicle terminal with computing and processing capabilities. Figure 3The process shown in FIG. 1 is described in detail, the fault simulation operation is the power supply short circuit fault simulation operation, the target parameter is the first target port voltage of the domain controller, and the test method may specifically include the following steps:

[0044] Step 210, performing a fault simulation operation on a domain controller of the vehicle, and monitoring target parameters of the domain controller after performing the fault simulation operation, wherein the fault simulation operation includes a power short circuit fault simulation operation.

[0045] Step 220: If it is monitored that the voltage of the first target port of the domain controller is equal to a first preset value, a power short-circuit operation is performed on the domain controller, and the voltage of the first target port of the domain controller is obtained.

[0046] As a method, when simulating a power short circuit fault on a domain controller, the voltage corresponding to the power supply port of the domain controller is 0, and there is voltage on the non-power supply port of the domain controller. At this time, the voltage of the non-power supply port (i.e., the first target port) of the domain controller can be used to determine whether the power short circuit occurs in the domain controller. Optionally, in order to make the fault error test of the domain controller more accurate, before performing a power short circuit operation on the domain controller, it can be determined whether to perform a short circuit operation on the domain controller based on whether the voltage of the first target port is a first preset value, wherein the first preset value is 0. Optionally, in order to avoid a fault caused by an abnormal voltage being injected into the first target port, before performing a power short circuit operation on the domain controller, it is first determined whether the voltage of the first target port of the domain controller is 0, and then the power short circuit operation is performed on the domain controller when it is determined that the voltage of the first target port is 0. Optionally, performing a power short circuit operation on the domain controller can be performed by controlling the second program-controlled relay to open the main relay and the power short circuit relay and controlling the first program-controlled relay to open the relay corresponding to the first target port.

[0047] Optionally, after performing a power short-circuit operation on the domain controller, the voltage value of the first target port voltage continues to be monitored, so that a fault error test can be performed on the domain controller based on the first target port voltage.

[0048] Step 230: If the first target port voltage is greater than the first preset value, determine whether there is fault information in the first reference network message of the domain controller.

[0049] As a method, when a power short circuit occurs in a domain controller, it can be determined that the domain controller does not have power supply. At this time, there should be no voltage on the non-powered port of the domain controller. When the voltage of the first target port is greater than the first preset value, it can be determined that a power short circuit occurs in the domain controller. In order to accurately determine whether the domain controller has reported a fault error for the power short circuit after performing a fault simulation operation, it can be determined by obtaining the first reference network message of the domain controller. Optionally, when the domain controller is working, it will upload the network message including the working information of the domain controller to the gateway of the vehicle according to the set reporting cycle. Then, the domain controller can be tested for fault error by determining whether there is fault information in the first reference network message reported by the domain controller to the gateway.

[0050] Step 240: If the fault information exists in the first reference network message, determine that the fault error test result is a test success.

[0051] As a method, when it is determined that there is fault information in the first reference network message, it can be determined that after a fault occurs in the domain controller, the domain controller adds the fault information to the first reference network message based on the fault, thereby ensuring that the vehicle's gateway can receive the fault information from the domain controller, and then, the vehicle's central processing unit can handle the fault based on the fault information in the first network message, thereby ensuring the driver's safety while driving the vehicle, and then determining that the fault error test of the domain controller is successful.

[0052] Optionally, the fault information in the first reference network message may be information including a specific voltage value of the first target port voltage, or may be a fault identifier determined by the domain controller after performing a fault analysis based on the voltage value of the first target port voltage and indicating that a power short circuit fault has occurred in the domain controller, or may be other fault information that may indicate that a fault has occurred in the domain controller.

[0053] Step 250: If the fault information does not exist in the first reference network message, determine that the fault error test result is a test failure.

[0054] As a method, when it is determined that there is no fault information in the first reference network message, but the voltage of the first target port of the current domain controller indicates that a power failure has occurred in the domain controller, it can be determined that the domain controller cannot report a fault for the current fault, thereby determining that the fault reporting test of the domain controller has failed.

[0055] Step 260: If the fault error reporting test result indicates that the domain controller reports a fault error after performing the fault simulation operation, the target parameters of the domain controller continue to be monitored, and a fault recovery test is performed on the domain controller.

[0056] The specific step descriptions of step 210 and step 260 can refer to step 110 and step 130, which will not be repeated here.

[0057] Step 270, obtaining a fault recovery test result according to the monitored target parameters.

[0058] In some embodiments, Figure 4 As shown, step 270 includes:

[0059] Step 271: If the voltage of the first target port of the domain controller changes from being greater than the first preset value to being equal to the first preset value, and the first target network message of the domain controller indicates that there is no fault in the domain controller, then determine that the fault recovery test result is a test success.

[0060] As a method, after determining that the fault error test result of the domain controller indicates that the domain controller has reported a fault error after performing a fault simulation operation, the domain controller can be restored from a power short circuit fault, and then the target parameters after the fault recovery can be used to determine whether the domain controller meets the factory conditions or design conditions. Optionally, the power short circuit fault recovery of the domain controller can restore the power supply to the domain controller, that is, supply power to the power supply port of the domain controller. Optionally, the power short circuit fault recovery of the domain controller can be to turn off the first program-controlled relay and the second program-controlled relay.

[0061] As a method, in the process of continuously monitoring the voltage of the first target port of the domain controller, if it is determined that the voltage value of the first target port voltage changes from greater than a first preset value to equal to the first preset value during the process from the occurrence of a power short circuit fault in the domain controller to the recovery of the power short circuit fault of the domain controller, then it is determined that the domain controller has recovered from the power short circuit fault of the domain controller. In order to further ensure the accuracy of the fault recovery test of the domain controller for the power short circuit fault, it can be determined in the first target network message after the fault recovery of the domain controller whether the domain controller still has a fault, and then determine whether the domain controller can stop reporting fault errors in time after the fault recovery.

[0062] Optionally, when it is determined that the first target network message indicates that there is no fault in the domain controller, it can be determined that the domain controller can stop reporting fault errors in a timely manner after the fault is recovered. In this way, it can be determined that the fault recovery test of the domain controller is successful, thereby avoiding the domain controller from being unable to be used normally due to continuous fault errors.

[0063] Step 272: If the first target network message indicates that the domain controller continues to report a fault error, it is determined that the fault recovery test result is a test failure.

[0064] As a method, if it is determined that the first target network message indicates that the domain controller continues to report an error for a power short circuit fault, it can be determined that the domain controller cannot stop reporting an error after the fault is recovered, and thus it can be determined that the fault recovery test of the domain controller has failed. Optionally, it can be determined whether the domain controller continues to report an error by determining whether multiple consecutive frames of the first target network message indicate that the domain controller has a fault.

[0065] In this embodiment, the voltage value of the first target port voltage of the domain controller is monitored in real time to determine whether the corresponding power short circuit fault actually occurs in the domain controller, and then it is determined whether the domain controller reports the power short circuit fault based on whether fault information exists in the first reference network message obtained from the domain controller, thereby determining the fault error test of the domain controller, thereby improving the efficiency and accuracy of the fault error test of the domain controller for the power short circuit fault.

[0066] See also Figure 5 , Figure 5 The test method provided by an embodiment of the present application is shown. The specific process of this embodiment will be described below. Of course, it can be understood that the method can be executed by a vehicle terminal with computing and processing capabilities. Figure 5 The process shown is described in detail, the fault simulation operation is the short-circuit fault simulation operation, the target parameter is the second target port voltage of the domain controller, and the test method may specifically include the following steps:

[0067] Step 310 , performing a fault simulation operation on a domain controller of the vehicle, and monitoring target parameters of the domain controller after performing the fault simulation operation, wherein the fault simulation operation includes a short circuit to ground fault simulation operation.

[0068] Step 320: If it is monitored that the voltage of the second target port of the domain controller is equal to a second preset value, a ground short circuit operation is performed on the domain controller.

[0069] As a method, when a short circuit to ground occurs in the domain controller, the voltage in the ground port of the domain controller is not equal to the ground voltage. Therefore, when the voltage of the second target port is monitored to be equal to the second preset value (i.e., the ground port of the domain controller), the domain controller can be short-circuited to ground. Optionally, the short circuit to ground of the domain controller can be performed by controlling the second program-controlled relay in the test bench to open the main relay and the short circuit to ground relay and controlling the first program-controlled relay to open the relay corresponding to the ground port. The second preset value can be 12.

[0070] Step 330, determining a first target time duration from when a ground short circuit fault occurs to when the domain controller stops supplying power, and determining a first target wire temperature difference from when a ground short circuit fault occurs to when the domain controller stops supplying power.

[0071] As a way, in order to ensure that the domain controller can be powered off in time when a ground short circuit fault occurs to ensure that the domain controller is not damaged, it is necessary to determine that the domain controller can stop supplying power to the domain controller before it is damaged, and then it is necessary to determine the first target time from the occurrence of the ground short circuit fault to the stop of power supply to the domain controller, so as to determine whether the domain controller can perform emergency processing of the ground short circuit fault in time based on the first target time.

[0072] Optionally, since the wires of the domain controller will continue to heat up when a ground short circuit fault occurs in the domain controller, in order to avoid damage to the hardware of the domain controller due to temperature rise, the wire temperature of the domain controller from the time the ground short circuit fault occurs to the time the domain controller stops powering on can be monitored to determine the first target wire temperature difference. Optionally, the temperature rise rate of the domain controller from the time the ground short circuit fault occurs to the time the domain controller stops powering on can also be determined.

[0073] Step 340: If the first target duration is greater than a preset duration and / or the first target wire temperature is greater than or equal to a preset temperature difference, then determining that the fault error test result is a test failure.

[0074] As a method, the preset duration and preset temperature difference can be set in advance according to the hardware information of the domain controller. When it is determined that the first target duration is greater than the preset duration, it can be known that the domain controller cannot stop the power supply in time. At this time, it can be determined that the domain controller is damaged and it is impossible to perform a fault error test by obtaining the network message of the domain controller. In this way, the fault error test result for the domain controller can be determined as a test failure.

[0075] Optionally, when it is determined that the temperature difference of the first target wire is greater than or equal to the preset temperature difference, it can be known that the domain controller cannot stop the power supply operation in time. At this time, it can be determined that the domain controller is damaged and it is impossible to perform a fault error test by obtaining the network message of the domain controller, so that the fault error test result for the domain controller can be determined as a test failure. Optionally, it can also be determined by determining whether the temperature rise rate of the wire of the domain controller within the first time length is greater than the rate threshold. When it is determined that the temperature rise rate of the wire of the domain controller within the first time length is greater than the rate threshold, the fault error test result for the domain controller can be determined as a test failure; when it is determined that the temperature rise rate of the wire of the domain controller within the first time length is less than or equal to the rate threshold, the fault error test result for the domain controller can be determined as a test failure.

[0076] In some embodiments, before step 350, the method further includes: determining whether there is fault information in the second reference network message of the domain controller; if the fault information exists in the second reference network message and the fault information indicates that the domain controller has a power-on prevention false touch action, determining that the fault error test result is a test success; or if the fault information does not exist in the second reference network message, determining that the fault error test result is a test failure.

[0077] As a method, when the domain controller is working, it will upload the network message including the working information of the domain controller to the gateway of the vehicle according to the set reporting cycle, and then, the fault error test of the domain controller can be performed by determining whether there is fault information in the second reference network message reported by the domain controller to the gateway. Optionally, when it is determined that there is fault information in the second reference network message, it can be determined that after the domain controller fails, the domain controller adds the fault information to the second reference network message based on the fault, so as to ensure that the gateway of the vehicle can receive the fault information of the domain controller, and then, the central processing unit of the vehicle can handle the fault based on the fault information in the second network message, so as to ensure the safety of the driver in the process of driving the vehicle, and then determine that the fault error test of the domain controller is successful. Optionally, the fault information in the second reference network message can be information including the specific voltage value of the second target port voltage, or it can be a fault identifier that can indicate that the domain controller has a ground short circuit fault determined by the domain controller after fault analysis based on the voltage value of the second target port voltage, or it can be other fault information that can indicate that the domain controller has a fault. Optionally, in order to avoid a temporary change in the voltage of the ground port of the domain controller due to power-on, it can be determined whether the domain controller has performed power-on prevention of false touches, so as to ensure the accuracy of the fault error test of the domain controller. Optionally, it can also be determined whether the number of power-on prevention false touches is greater than a threshold. Only when the number of power-on prevention false touches is greater than the threshold, it can be ensured that the fault of the domain controller is a short circuit to ground.

[0078] When it is determined that there is no fault information in the first reference network message, but the voltage of the first target port of the current domain controller indicates that a power failure has occurred in the domain controller, it can be determined that the domain controller cannot report a fault for the current fault, thereby determining that the fault reporting test of the domain controller has failed.

[0079] Step 350: If the fault error reporting test result indicates that the domain controller reports a fault error after performing the fault simulation operation, the target parameters of the domain controller continue to be monitored, and a fault recovery test is performed on the domain controller.

[0080] The specific step descriptions of step 310 and step 350 can refer to step 110 and step 130, which will not be repeated here.

[0081] Step 360, obtaining a fault recovery test result according to the monitored target parameters.

[0082] In some embodiments, Figure 6 As shown, step 360 includes:

[0083] Step 361: If the voltage of the second target port of the domain controller changes from being equal to the second preset value to being equal to the third preset value, and the second target network message of the domain controller indicates that there is no fault in the domain controller, then determine that the fault recovery test result is a test success.

[0084] As a way, as a way, after determining that the fault error test result of the domain controller indicates that the domain controller has reported a fault error after performing a fault simulation operation, the domain controller can be grounded short-circuit fault recovery, and then the target parameters after the fault recovery can be determined to determine whether the factory conditions or design conditions of the domain controller are met. Optionally, the ground short-circuit fault recovery of the domain controller can restore the power supply to the ground port of the domain controller so that the voltage of the ground port is the same as the voltage value of the preset value. Optionally, the power supply short-circuit fault recovery of the domain controller can be to turn off the first program-controlled relay and the second program-controlled relay.

[0085] As a method, in the process of continuously monitoring the voltage of the second target port of the domain controller, if it is determined that the voltage value of the second target port voltage changes from being equal to the second preset value to being equal to the third preset value during the process from the occurrence of the ground short circuit fault in the domain controller to the recovery of the ground short circuit fault of the domain controller, then it is determined that the domain controller has recovered from the occurrence of the ground short circuit fault to the recovery of the ground short circuit fault of the domain controller. In order to further ensure the accuracy of the fault recovery test of the domain controller for the ground short circuit fault, it can be determined in the second target network message after the fault recovery of the domain controller whether the domain controller still has a fault, and then determine whether the domain controller can stop reporting fault errors in time after the fault recovery.

[0086] Optionally, when it is determined that the second target network message indicates that there is no fault in the domain controller, it can be determined that the domain controller can stop reporting fault errors in a timely manner after the fault is recovered. In this way, it can be determined that the fault recovery test of the domain controller is successful, thereby avoiding the domain controller from being unable to be used normally due to continuous fault errors.

[0087] Step 362: If the voltage of the second target port of the domain controller does not satisfy the change from being equal to the second preset value to being equal to the third preset value, and / or the second target network message of the domain controller indicates that the domain controller has a continuous fault error behavior, then the fault recovery test result is determined to be a test failure.

[0088] As a method, if it is determined that the second target network message indicates that the domain controller continues to report an error for the ground short circuit fault, it can be determined that the domain controller cannot stop reporting the fault error after the fault is recovered, so that it can be determined that the fault recovery test of the domain controller has failed. Optionally, it can be determined whether the domain controller continues to report the fault error by determining whether multiple consecutive frames of the second target network message indicate that the domain controller has a fault.

[0089] Optionally, in the process of continuously monitoring the voltage of the second target port of the domain controller, if it is determined that the voltage value of the second target port voltage does not satisfy the change from being equal to the second preset value to being equal to the third preset value during the process from the occurrence of the ground short circuit fault of the domain controller to the recovery of the ground short circuit fault of the domain controller, it can be determined that the fault recovery of the domain controller is not completed, thereby determining that the fault recovery test of the domain controller has failed. The third preset value can be 0.

[0090] In this embodiment, whether the corresponding ground short circuit fault actually occurs in the domain controller is determined by real-time monitoring of the voltage value of the second target port voltage of the domain controller, and then whether the domain controller reports the ground short circuit fault is determined based on whether fault information exists in the second reference network message of the domain controller obtained. In addition, whether the domain controller can perform emergency processing when a ground fault occurs is determined based on the first target time from the occurrence of the ground short circuit fault to the stop of power supply to the domain controller and the first target wire temperature difference from the occurrence of the ground short circuit fault to the stop of power supply to the domain controller monitored in real time, thereby determining the fault error test of the domain controller, thereby improving the efficiency and accuracy of the fault error test of the domain controller for the ground short circuit fault.

[0091] See also Figure 7 , Figure 7 The test method provided by an embodiment of the present application is shown. The specific process of this embodiment will be described below. Of course, it can be understood that the method can be executed by a vehicle terminal with computing and processing capabilities. Figure 7 The process shown is described in detail, the fault simulation operation is the overload fault simulation operation, the target parameter is the target port current of the domain controller, and the test method may specifically include the following steps:

[0092] Step 410: perform a fault simulation operation on a domain controller of the vehicle, and monitor target parameters of the domain controller after the fault simulation operation, wherein the fault simulation operation includes an overload fault simulation operation.

[0093] Step 420: When it is determined that the target port current of the domain controller is greater than the current threshold, control the domain controller to stop supplying power.

[0094] As a method, when it is determined that the current of the target port of the domain controller is greater than the current threshold, it can be determined that the load currently connected to the domain controller is too much. At this time, in order to avoid damage to the hardware of the domain controller due to overload of the domain controller, it is necessary to immediately control the domain controller to stop power supply.

[0095] Step 430, determining a second target duration from when the target port current is greater than the current threshold to when the domain controller stops supplying power, and determining a second target wire temperature difference of the domain controller within the second target duration.

[0096] As a way, in order to ensure that the domain controller can be powered off in time when an overload fault occurs to ensure that the domain controller is not damaged, it is necessary to determine that the domain controller can stop supplying power to the domain controller before it is damaged, and then it is necessary to determine the second target time from the occurrence of the overload fault (that is, when the target port current is greater than the current threshold) to the stop of power supply to the domain controller, so as to determine whether the domain controller can perform emergency processing of the overload fault in time based on the second target time.

[0097] Optionally, since the wires of the domain controller will continue to heat up when an overload fault occurs in the domain controller, in order to avoid damage to the hardware of the domain controller due to temperature rise, the wire temperature of the domain controller from the time the overload fault occurs to the time the domain controller stops supplying power can be monitored to determine the second target wire temperature difference. Optionally, the temperature rise rate of the domain controller from the time the overload fault occurs to the time the domain controller stops supplying power can also be determined.

[0098] Step 440: adjust the target port current to a first target value according to the second target time and the current threshold, and determine a third target port voltage of the domain controller after a preset time.

[0099] As a method, the load connected to the domain controller can be adjusted by an electronic load, and the adjusted current value can be determined according to the current threshold. Optionally, the current value is adjusted to 0.9 times the current threshold, and the duration after the current value is adjusted to 0.9 times the current threshold is a preset duration.

[0100] Optionally, in order to ensure the accuracy of the fault error reporting test of the domain controller, the third target port voltage is determined after a preset period of time, so that the fault error reporting test of the domain controller can be performed based on the third target port voltage.

[0101] Step 450: If the third target port voltage is not a fourth preset value, the second target conductor temperature difference is greater than or equal to the preset temperature difference, and there is no fault information in the third reference network message, then determine that the fault error test result is a test failure.

[0102] As a method, when it is determined that the voltage of the third target port is not equal to the fourth preset value, it can be determined that the domain controller still has an overload fault after the load of the domain controller is adjusted through the electronic load, and when it is determined that the temperature difference of the second target wire is greater than or equal to the preset temperature difference, it can be known that the domain controller cannot stop the power supply in time. At the same time, when it is determined that there is no fault information in the third reference network message, it can be determined that when the domain controller has an overload fault, the overload fault will not be reported, so that the fault error test result for the overload fault of the domain controller can be determined as a test failure.

[0103] Step 460: If the third target port voltage is the fourth preset value, the second target conductor temperature difference is less than the preset temperature difference, and there is fault information in the third reference network message, then determine that the fault error test result is a test success.

[0104] As a method, when it is determined that the voltage of the third target port is equal to the fourth preset value, it can be determined that the domain controller still has an overload fault after the load of the domain controller is adjusted through the electronic load, and when it is determined that the temperature difference of the second target wire is greater than or equal to the preset temperature difference, it can be known that the domain controller stops power supply in time. At the same time, when it is determined that there is fault information in the third reference network message, it can be determined that the overload fault is still reported when the domain controller has an overload fault, so that the fault error test result for the overload fault of the domain controller can be determined as a successful test.

[0105] Step 470: If the fault error reporting test result indicates that the domain controller reports a fault error after performing the fault simulation operation, the target parameters of the domain controller continue to be monitored, and a fault recovery test is performed on the domain controller.

[0106] The specific step descriptions of step 410 and step 470 can refer to step 110 and step 130, which will not be repeated here.

[0107] Step 480, obtaining a fault recovery test result according to the monitored target parameters.

[0108] In some embodiments, Figure 8As shown, step 480 includes:

[0109] Step 481: If the third target port voltage is equal to the fourth preset value and the second target conductor temperature difference is less than the preset temperature difference, the target port current is adjusted to the second target value according to the preset time length and the current threshold.

[0110] As a way, when it is determined that the third target port voltage is equal to the fourth preset value and the second target wire temperature difference is less than the preset temperature difference, it can be determined that the domain controller has not suffered hardware damage when the overload fault occurs. At this time, the target port current can be adjusted to the second target value again according to the preset duration and current threshold. Optionally, the second target value can be 1.1 times the current threshold. Optionally, when adjusting the target port current to the second target value, in order to ensure the stability of the current, the target port current is maintained at the second target value for a preset duration. Among them, the fourth preset value is 12.

[0111] Step 482: Perform overload fault recovery on the domain controller according to the adjusted target port current.

[0112] As a method, after adjusting the target port current, in order to perform a fault recovery test on the domain controller, the load connected to the domain controller can be reduced by an electronic load, thereby realizing overload fault recovery of the domain controller. Optionally, the overload fault recovery can be performed by controlling the domain controller to shut down and power it on again.

[0113] Step 483: If the voltage of the third target port after the domain controller recovers from an overload fault changes from being equal to the fourth preset value to being equal to the fifth preset value and the third target network message of the domain controller indicates that there is no fault in the domain controller, then the fault recovery test result is determined to be a successful test.

[0114] As a method, in the process of continuously monitoring the voltage of the third target port of the domain controller, if it is determined that the voltage value of the third target port voltage changes from being equal to the fourth preset value to being equal to the fifth preset value during the process from the occurrence of the overload fault of the domain controller to the recovery of the ground short circuit fault of the domain controller, then it is determined that the domain controller has recovered from the overload fault of the domain controller. In order to further ensure the accuracy of the fault recovery test of the domain controller for the overload fault, it can be determined in the third target network message after the fault recovery of the domain controller whether the domain controller still has a fault, and then determine whether the domain controller can stop reporting fault errors in time after the fault recovery.

[0115] Optionally, when it is determined that the third target network message indicates that there is no fault in the domain controller, it can be determined that the domain controller can stop reporting fault errors in a timely manner after the fault is recovered. In this way, it can be determined that the fault recovery test of the domain controller is successful, thereby avoiding the domain controller from being unable to be used normally due to continuous fault errors.

[0116] Step 484: If the voltage of the third target port after the domain controller is recovered from an overload fault does not satisfy the change from being equal to the fourth preset value to being equal to the fifth preset value, and / or the third target network message of the domain controller indicates that the domain controller has a continuous fault error behavior, then the fault recovery test result is determined to be a test failure.

[0117] As a method, if it is determined that the third target network message indicates that the domain controller continues to report an error for the overload fault, it can be determined that the domain controller cannot stop reporting the fault error after the fault is recovered, so it can be determined that the fault recovery test of the domain controller has failed. Optionally, it can be determined whether the domain controller continues to report the fault error by determining whether multiple consecutive frames of the third target network message indicate that the domain controller has a fault.

[0118] Optionally, in the process of continuously monitoring the voltage of the third target port of the domain controller, if it is determined that the voltage value of the third target port voltage does not satisfy the change from being equal to the fourth preset value to being equal to the fifth preset value during the process from the occurrence of the overload fault of the domain controller to the recovery of the overload fault of the domain controller, it can be determined that the fault recovery of the domain controller is not completed, thereby determining that the fault recovery test of the domain controller has failed. The third preset value can be 0.

[0119] In this embodiment, whether the corresponding overload fault actually occurs in the domain controller is determined by real-time monitoring of the current value of the target port current of the domain controller, and then the magnitude of the third target port voltage after emergency processing of the domain controller is determined by the second target time and current threshold from the time when the target port current is greater than the current threshold to the time when the domain controller stops powering off and the acquired third reference network message of the domain controller is used to determine whether the domain controller reports the overload fault, and whether the domain controller is capable of performing emergency processing when an overload occurs is determined based on the second target wire temperature difference from the time when the overload fault occurs to the time when the domain controller stops powering off, thereby determining the fault error test of the domain controller, thereby improving the efficiency and accuracy of the fault error test of the domain controller for overload faults.

[0120] See also Fig. 9 , Fig. 9The test method provided by an embodiment of the present application is shown. The specific process of this embodiment will be described below. Of course, it can be understood that the method can be executed by a vehicle terminal with computing and processing capabilities. Fig. 9 The process shown is described in detail, and the testing method may specifically include the following steps:

[0121] Step 510: Obtain the domain controller power distribution state of the domain controller in different modes of the vehicle and the power supply port voltage of the domain controller.

[0122] As a way, the domain controller will distribute power based on the different modes of the vehicle when used in the field, so that the domain controller can work in different modes of the vehicle, ensuring that users can use different functions in different modes of the vehicle. Optionally, the power distribution network message of the domain controller can be obtained in different modes, and then the power distribution status of the domain controller in different modes of the vehicle can be determined according to the power distribution network message. Optionally, the voltage acquisition module in the domain controller can be used to obtain the power supply port voltage of the domain controller in different modes of the vehicle.

[0123] Step 520: Determine whether the power distribution state of the domain controller and the power supply port voltage meet the power distribution conditions.

[0124] As a method, the power distribution state of the domain controller includes a power-on state and a power-off state. Optionally, the power distribution conditions in different modes may include that in standby mode, the normal power port is powered on, characterized by the bus signal being powered on and the port voltage being 12V, and the abnormal power port is in a power-off state, characterized by the bus signal being powered off and the port voltage being 0V. In comfort mode, both the normal power port and the abnormal power port are in a power-on state, and the corresponding power distribution conditions in different modes can be set according to actual needs, and no specific limitation is made here.

[0125] Step 530: If it is determined that the power distribution state of the domain controller and the power supply port voltage meet the power distribution condition, then determine that the power distribution test result of the domain controller is a test success.

[0126] As a way, when it is determined that the power distribution state of the domain controller and the power supply port voltage meet the power distribution conditions, it can be determined that the domain controller can complete power distribution in different modes, ensuring the use of the domain controller in practical applications.

[0127] In this embodiment, whether the domain controller can distribute power in different modes of the vehicle is determined by determining the power distribution status of the domain controller corresponding to the domain controller when the vehicle is in different modes and whether the voltage of the power supply port of the domain controller meets the power distribution conditions, thereby completing the power distribution test of the domain controller and ensuring the safety of the domain controller in subsequent use.

[0128] Fig.10 is a block diagram of a testing device according to an embodiment of the present application, such as Fig.11 As shown, the testing device 600 includes: a fault simulation module 610 , a fault error testing module 620 , a monitoring module 630 and a fault recovery testing module 640 .

[0129] A fault simulation module 610 is used to perform a fault simulation operation on a domain controller of a vehicle, and to monitor target parameters of the domain controller after the fault simulation operation, wherein the fault simulation operation includes a ground short-circuit fault simulation operation, a power short-circuit fault simulation operation, and an overload fault simulation operation; a fault error testing module 620 is used to monitor the target parameters of the domain controller, and to perform a fault error testing on the domain controller based on the target parameters to obtain a fault error testing result; a monitoring module 630 is used to continue to monitor the target parameters of the domain controller and to perform a fault recovery test on the domain controller if the fault error testing result indicates that the domain controller reports a fault error after the fault simulation operation; a fault recovery test result determination module 640 is used to obtain a fault recovery testing result based on the monitored target parameters.

[0130] In some embodiments, the fault simulation operation is the power short circuit fault simulation operation, the target parameter is the first target port voltage of the domain controller, and the fault error test module 620 includes: a power short circuit operation unit, which is used to perform a power short circuit operation on the domain controller and obtain the first target port voltage of the domain controller if it is monitored that the first target port voltage of the domain controller is equal to a first preset value; a first determination unit, which is used to determine whether there is fault information in the first reference network message of the domain controller if the first target port voltage is greater than the first preset value; a first fault error test result determination unit, which is used to determine that the fault error test result is a test success if the fault information exists in the first reference network message; or a second fault error test result determination unit, which is used to determine that the fault error test result is a test failure if the fault information does not exist in the first reference network message.

[0131] In some embodiments, the fault recovery test module 640 includes: a first fault recovery test result determination unit, which is used to determine that the fault recovery test result is a test success if the voltage of the first target port of the domain controller changes from greater than the first preset value to equal to the first preset value, and the first target network message of the domain controller indicates that there is no fault in the domain controller; or a second fault recovery test result determination unit, which is used to determine that the fault recovery test result is a test failure if the first target network message indicates that the domain controller continues to report a fault error.

[0132] In other embodiments, the fault simulation operation is the ground short-circuit fault simulation operation, the target parameter is the second target port voltage of the domain controller, and the fault error test module 620 includes: a ground short-circuit operation unit, which is used to perform a ground short-circuit operation on the domain controller if it is monitored that the second target port voltage of the domain controller is equal to a second preset value; a second determination unit, which is used to determine a first target time from the occurrence of a ground short-circuit fault to the stop of power supply to the domain controller, and to determine a first target wire temperature difference from the occurrence of a ground short-circuit fault to the stop of power supply to the domain controller; and a third fault error test result determination unit, which is used to determine that the fault error test result is a test failure if the first target time is greater than a preset time and / or the first target wire temperature is greater than or equal to a preset temperature difference.

[0133] In some embodiments, the fault error test module 620 also includes: a third determination unit, used to determine whether there is fault information in the second reference network message of the domain controller; a fourth fault error test result determination unit, used to determine that the fault error test result is a test success if the fault information exists in the second reference network message and the fault information indicates that the domain controller has a power-on prevention false touch action; or a fifth fault error test result determination unit, used to determine that the fault error test result is a test failure if the fault information does not exist in the first reference network message.

[0134] In other embodiments, the fault recovery test module 640 includes: a third fault recovery test result determination unit, which is used to determine that the fault recovery test result is a test success if the voltage of the second target port of the domain controller changes from being equal to the second preset value to being equal to the third preset value, and the second target network message of the domain controller indicates that there is no fault in the domain controller; or a fourth fault recovery test result determination unit, which is used to determine that the fault recovery test result is a test failure if the voltage of the second target port of the domain controller does not satisfy the change from being equal to the second preset value to being equal to the third preset value, and / or the second target network message of the domain controller indicates that the domain controller has continuous fault error reporting behavior.

[0135] In some other embodiments, the fault simulation operation is the overload fault simulation operation, the target parameter is the target port current of the domain controller, and the fault error test module 620 includes: a first control unit, used to control the domain controller to stop power supply when it is determined that the target port current of the domain controller is greater than the current threshold; a fourth determination unit, used to determine the second target time length from when the target port current of the domain controller is greater than the current threshold to when the domain controller stops power supply, and determine the second target wire temperature difference of the domain controller within the second target time length; a fifth determination unit, used to adjust the target time length according to the second target time length and the current threshold. the target port current to the first target value, and determining the third target port voltage of the domain controller after a preset time; a sixth fault error test result determination unit, for determining that the fault error test result is a test failure if the third target port voltage is not a fourth preset value, the second target wire temperature difference is greater than or equal to the preset temperature difference, and there is no fault information in the third reference network message; a seventh fault error test result determination unit, for determining that the fault error test result is a test success if the third target port voltage is the fourth preset value, the second target wire temperature difference is less than the preset temperature difference, and there is fault information in the third reference network message.

[0136] In some other embodiments, the fault recovery test module 640 includes: an adjustment unit, which is used to adjust the target port current to the second target value according to the preset time and the current threshold if the third target port voltage is equal to the fourth preset value and the second target wire temperature difference is less than the preset temperature difference; a third fault recovery unit, which is used to perform overload fault recovery on the domain controller according to the adjusted target port current; a fifth fault recovery test result determination unit, which is used to determine that the fault recovery test result is a test success if the third target port voltage after the overload fault recovery of the domain controller changes from being equal to the fourth preset value to being equal to the fifth preset value and the third target network message of the domain controller indicates that the domain controller does not have a fault; or a sixth fault recovery test result determination unit, which is used to determine that the fault recovery test result is a test failure if the third target port voltage after the overload fault recovery of the domain controller does not meet the change from being equal to the fourth preset value to being equal to the fifth preset value, and / or the third target network message of the domain controller indicates that the domain controller has a continuous fault error reporting behavior.

[0137] According to one aspect of the embodiments of the present application, an electronic device is also provided, such as Fig.11As shown, the electronic device 700 includes a processor 710 and one or more memories 720. The one or more memories 720 are used to store program instructions executed by the processor 710. When the processor 710 executes the program instructions, the above-mentioned test method is implemented.

[0138] Furthermore, the processor 710 may include one or more processing cores. The processor 710 runs or executes instructions, programs, code sets or instruction sets stored in the memory 720, and calls data stored in the memory 720. Optionally, the processor 710 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 710 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It is understandable that the above-mentioned modem may not be integrated into the processor, but may be implemented separately through a communication chip.

[0139] According to one aspect of the present application, the present application further provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or may exist independently without being assembled into the electronic device. The above computer-readable storage medium carries computer-readable instructions, and when the computer-readable storage instructions are executed by a processor, the method in any of the above embodiments is implemented.

[0140] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0141] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

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

[0143] Other embodiments of the present application will be readily apparent to those skilled in the art after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0144] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A testing method, characterized in that: The method comprises: Performing a fault simulation operation on a domain controller of the vehicle, and monitoring a target parameter of the domain controller after the fault simulation operation, wherein the fault simulation operation includes a short circuit to ground fault simulation operation, a short circuit to power supply fault simulation operation, and an overload fault simulation operation; Monitoring target parameters of the domain controller, and performing a fault error test on the domain controller based on the target parameters to obtain a fault error test result; If the fault error reporting test result indicates that the domain controller reports a fault error after performing the fault simulation operation, continue to monitor the target parameters of the domain controller and perform a fault recovery test on the domain controller; The fault recovery test results are obtained based on the monitored target parameters.

2. The method according to claim 1, characterized in that The fault simulation operation is the power short circuit fault simulation operation, the target parameter is the first target port voltage of the domain controller, and the fault error reporting test is performed on the domain controller based on the monitored target parameter to obtain the fault error reporting test result, including: If it is monitored that the voltage of the first target port of the domain controller is equal to a first preset value, a power short-circuit operation is performed on the domain controller, and the voltage of the first target port of the domain controller is obtained; If the first target port voltage is greater than the first preset value, determining whether there is fault information in the first reference network message of the domain controller; If the fault information exists in the first reference network message, determining that the fault error test result is a test success; or If the fault information does not exist in the first reference network message, it is determined that the fault error test result is a test failure.

3. The method according to claim 2, characterized in that Obtaining the fault recovery test result according to the monitored target parameters includes: If the voltage of the first target port of the domain controller changes from being greater than the first preset value to being equal to the first preset value, and the first target network message of the domain controller indicates that there is no fault in the domain controller, then determining that the fault recovery test result is a test success; or If the first target network message indicates that the domain controller continues to report a fault error, it is determined that the fault recovery test result is a test failure.

4. The method according to claim 1, characterized in that: The fault simulation operation is the short-circuit fault simulation operation to ground, the target parameter is the voltage of the second target port of the domain controller, and the fault error reporting test is performed on the domain controller based on the monitored target parameter to obtain the fault error reporting test result, including: If it is monitored that the voltage of the second target port of the domain controller is equal to a second preset value, performing a ground short circuit operation on the domain controller; Determine a first target time duration from when a ground short circuit fault occurs in the domain controller to when the domain controller stops supplying power, and determine a first target wire temperature difference from when a ground short circuit fault occurs in the domain controller to when the domain controller stops supplying power; If the first target duration is greater than a preset duration and / or the first target wire temperature is greater than or equal to a preset temperature difference, the fault error test result is determined to be a test failure.

5. The method according to claim 4, characterized in that The method further comprises: Determining whether there is fault information in the second reference network message of the domain controller; If the fault information exists in the second reference network message and the fault information indicates that the domain controller has a power-on prevention false touch action, then determining that the fault error test result is a test success; or If the fault information does not exist in the second reference network message, it is determined that the fault error test result is a test failure.

6. The method according to claim 4, characterized in that Obtaining the fault recovery test result according to the monitored target parameters includes: If the voltage of the second target port of the domain controller changes from being equal to the second preset value to being equal to a third preset value, and the second target network message of the domain controller indicates that there is no fault in the domain controller, then determining that the fault recovery test result is a test success; or If the voltage of the second target port of the domain controller does not satisfy the change from being equal to the second preset value to being equal to the third preset value, and / or the second target network message of the domain controller indicates that the domain controller has a continuous fault error behavior, then the fault recovery test result is determined to be a test failure.

7. The method according to claim 1, characterized in that The fault simulation operation is the overload fault simulation operation, the target parameter is the target port current of the domain controller, the target parameter of the domain controller is monitored, and a fault error test is performed on the domain controller based on the target parameter to obtain a fault error test result, including: When it is determined that the target port current of the domain controller is greater than the current threshold, controlling the domain controller to stop supplying power; Determine a second target duration of the domain controller from when the current of the target port is greater than the current threshold to when the domain controller stops supplying power, and determine a second target wire temperature difference of the domain controller within the second target duration; adjusting the target port current to a first target value according to the second target duration and the current threshold, and determining a third target port voltage of the domain controller after a preset duration; If the third target port voltage is not a fourth preset value, the second target wire temperature difference is greater than or equal to the preset temperature difference, and there is no fault information in the third reference network message, then determining that the fault error test result is a test failure; If the third target port voltage is the fourth preset value, the second target wire temperature difference is less than the preset temperature difference, and there is fault information in the third reference network message, it is determined that the fault error test result is a test success.

8. The method according to claim 7, characterized in that Obtaining the fault recovery test result according to the monitored target parameters includes: If the third target port voltage is equal to the fourth preset value and the second target wire temperature difference is less than the preset temperature difference, adjusting the target port current to the second target value according to the preset time length and the current threshold; Performing overload fault recovery on the domain controller according to the adjusted target port current; If the voltage of the third target port after the domain controller is recovered from an overload fault changes from being equal to the fourth preset value to being equal to the fifth preset value and the third target network message of the domain controller indicates that there is no fault in the domain controller, then the fault recovery test result is determined to be a test success; or If the voltage of the third target port after the domain controller is recovered from an overload fault does not satisfy the change from being equal to the fourth preset value to being equal to the fifth preset value, and / or the third target network message of the domain controller indicates that the domain controller has a continuous fault error behavior, then the fault recovery test result is determined to be a test failure.

9. A testing device, characterized in that: The device comprises: A fault simulation module, used to perform a fault simulation operation on a domain controller of a vehicle, and monitor target parameters of the domain controller after the fault simulation operation, wherein the fault simulation operation includes a short circuit to ground fault simulation operation, a short circuit to power supply fault simulation operation, and an overload fault simulation operation; A fault error reporting test module, used to monitor the target parameters of the domain controller, and perform a fault error reporting test on the domain controller based on the target parameters to obtain a fault error reporting test result; A monitoring module, configured to continue monitoring target parameters of the domain controller and perform a fault recovery test on the domain controller if the fault error reporting test result indicates that the domain controller reports a fault error after performing a fault simulation operation; The fault recovery test result determination module is used to obtain the fault recovery test result according to the monitored target parameters.

10. An electronic device, characterized in that: The electronic device comprises: processor; A memory having computer-readable instructions stored thereon, wherein when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 8 is implemented.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program codes, which can be called by a processor to execute the method according to any one of claims 1 to 8.

Images