Method, device and equipment for solving abnormal reset of ECU and readable storage medium

Abstract

The application provides a solution method, device and equipment for ECU abnormal reset and a readable storage medium. The method comprises the following steps: when the electric control unit (ECU) is reset and fails to recover, the number of continuous resets of the ECU, the maximum interval duration between all adjacent two resets during the continuous multiple resets of the ECU, the battery temperature and the current vehicle speed are obtained; when the number of continuous resets of the ECU, the maximum interval duration, the battery temperature and the current vehicle speed meet preset conditions, the battery motor relay switch is enabled through a hardware circuit. Through the application, when the ECU of a vehicle running at a high speed suddenly resets and fails to recover, the vehicle loses power, and the problem of great traffic risk is solved.

Description

Technical Field

[0001] This invention relates to the field of autonomous driving technology for electric vehicles, and in particular to a solution, apparatus, device, and readable storage medium for abnormal ECU reset. Background Technology

[0002] When a vehicle is traveling at high speed, if the electronic control unit (ECU) of the vehicle's battery management system suddenly resets and cannot be restored, the connection signal controlling the connection between the battery and the battery motor relay will be suddenly lost. This will cause the connection between the battery and the battery motor relay to break, resulting in the vehicle losing power and posing a significant traffic risk. Therefore, there is an urgent need for a technical solution that can prevent the connection between the battery and the battery motor relay from breaking when the ECU suddenly resets and cannot be restored. Summary of the Invention

[0003] The main objective of this invention is to provide a solution, device, equipment, and readable storage medium for abnormal ECU reset, aiming to solve the problem of loss of vehicle power and significant traffic risks when the electronic control unit of a vehicle traveling at high speed suddenly resets and cannot be restored.

[0004] In a first aspect, the present invention provides a solution to an abnormal ECU reset, the solution to the abnormal ECU reset including:

[0005] When the electronic control unit (ECU) resets and fails to recover, obtain the number of consecutive ECU resets, the maximum interval between all adjacent ECU resets during the period of multiple consecutive ECU resets, the battery temperature, and the current vehicle speed.

[0006] When the number of consecutive resets of the electronic control unit, the maximum interval duration, the battery temperature, and the current vehicle speed meet the preset conditions, the battery motor relay switch is enabled by controlling the hardware circuit.

[0007] Optionally, the preset condition is:

[0008] The number of times the electronic control unit is continuously reset is greater than the preset number of resets, the maximum interval time is less than the preset reset time, the battery temperature is less than the preset temperature, and the current vehicle speed is greater than the preset vehicle speed.

[0009] Optionally, before the electronic control unit resets and fails to recover, the following steps are included:

[0010] When the electronic control unit is reset, the various modules of the battery management system controller are initialized;

[0011] If the electronic control unit remains in a reset state after each module has been initialized a preset number of times, then an abnormal state of the battery management system controller is determined.

[0012] Locate the faulty module from the modules corresponding to the abnormal state;

[0013] Initialize the other modules of the battery management system controller, where "other modules" refers to modules other than the faulty module.

[0014] If the electronic control unit is still in a reset state after the other modules have been initialized a preset number of times, then the marking module in the battery management system controller is initialized, wherein the marking module is the module that affects the opening or closing of the battery motor relay;

[0015] If the electronic control unit remains in a reset state after the marking module has initialized a preset number of times, it is determined that the electronic control unit has been reset and recovery has failed.

[0016] Optionally, determining the abnormal state of the battery management system controller includes:

[0017] Obtain the current state of the battery management system controller;

[0018] When the current state of the battery management system controller is different from the normal current state, the previous state of the normal current state is determined to be the abnormal state of the battery management system controller.

[0019] Optionally, determining the abnormal state of the battery management system controller includes:

[0020] Retrieve the current state of the battery management system controller recorded in the volatile memory;

[0021] The current state is compared with the next state that the latest historical state in the non-volatile memory will transition to;

[0022] If the comparison result shows that the current state recorded in the volatile memory is different from the next state that the latest historical state in the non-volatile memory will jump to, then the latest historical state in the non-volatile memory is determined to be an abnormal state.

[0023] Optionally, the step of searching for the faulty module from the modules corresponding to the abnormal state includes:

[0024] Check the flag bits of each module corresponding to the abnormal state in the register of the main control chip of the electronic control unit;

[0025] The module whose flag bit is determined to be the preset flag bit is the faulty module.

[0026] Optionally, the step of searching for the faulty module from the modules corresponding to the abnormal state includes:

[0027] Get the number of normal state records of the module corresponding to the abnormal state during the abnormal state period by performing state detection on the module corresponding to the abnormal state according to the module abnormal detection cycle. The abnormal state period is from the end of the previous state to the time when the abnormal state changes.

[0028] The detection module checks whether the number of normal state records of the target module is the same as the number of ideal detection result records. The number of ideal detection result records is the quotient of the abnormal state period divided by the module abnormal detection cycle. When the quotient is a decimal, the quotient is rounded up. The target module is the module that performs state detection first among all modules corresponding to the abnormal state in the module abnormal detection cycle.

[0029] If they are different, then the target module is determined to be the faulty module;

[0030] If they are the same, the target module is removed from all modules corresponding to the abnormal state, and the process returns to the step of checking whether the number of normal state records of the target module is the same as the number of ideal detection result records.

[0031] Secondly, the present invention also provides a device for resolving ECU abnormal reset, the device comprising:

[0032] The acquisition module is used to acquire the number of consecutive resets of the electronic control unit, the maximum interval between all adjacent resets during the period of multiple consecutive resets of the electronic control unit, the battery temperature, and the current vehicle speed when the electronic control unit is reset and fails to recover.

[0033] The calculation and decision module is used to detect the number of times the electronic control unit is continuously reset, the maximum interval duration, the battery temperature, and whether the current vehicle speed meets the preset conditions.

[0034] The control module is used to enable the battery motor relay switch through hardware circuitry when the number of consecutive resets of the electronic control unit, the maximum interval duration, the battery temperature, and the current vehicle speed meet preset conditions.

[0035] Thirdly, the present invention also provides an ECU abnormal reset solution device, the ECU abnormal reset solution device including a processor, a memory, and an ECU abnormal reset solution program stored in the memory and executable by the processor, wherein when the ECU abnormal reset solution program is executed by the processor, the steps of the ECU abnormal reset solution method described above are implemented.

[0036] Fourthly, the present invention also provides a readable storage medium storing a solution program for ECU abnormal reset, wherein when the ECU abnormal reset solution program is executed by a processor, the steps of the ECU abnormal reset solution program as described above are implemented.

[0037] In this invention, when the electronic control unit (ECU) resets and fails to recover, the following parameters are obtained: the number of consecutive ECU resets, the maximum interval between all adjacent resets during multiple consecutive ECU resets, the battery temperature, and the current vehicle speed. When the number of consecutive ECU resets, the maximum interval, the battery temperature, and the current vehicle speed meet preset conditions, the battery motor relay switch is enabled via hardware circuitry. This invention addresses the issue where, when the ECU resets and fails to recover, and the number of consecutive ECU resets, the maximum interval between all adjacent resets during multiple consecutive ECU resets, the battery temperature, and the current vehicle speed meet preset conditions, a high-level hardware circuit output enables the battery motor relay switch, thereby restoring the connection between the battery and the battery motor relay. This prevents the ECU from suddenly resetting and failing to recover, solving the problem of vehicles losing power and posing a significant traffic risk when the ECU suddenly resets and fails to recover at high speeds. Attached Figure Description

[0038] Figure 1 This is a flowchart illustrating the first embodiment of the solution for abnormal ECU reset according to the present invention;

[0039] Figure 2 This is a flowchart illustrating the second embodiment of the solution for abnormal ECU reset according to the present invention;

[0040] Figure 3 for Figure 2 Detailed flowchart of step S002 of the first embodiment;

[0041] Figure 4 for Figure 2 Detailed flowchart of step S002 in the second embodiment;

[0042] Figure 5 for Figure 2 A detailed flowchart of an embodiment of step S003;

[0043] Figure 6 This is a functional module diagram of an embodiment of the ECU abnormal reset solution device of the present invention;

[0044] Figure 7 This is a schematic diagram of the hardware structure of the device for resolving ECU abnormal reset in the embodiments of the present invention.

[0045] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0046] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0047] Firstly, embodiments of the present invention provide a solution for abnormal ECU reset.

[0048] In one embodiment, reference is made to Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the solution for abnormal ECU reset according to the present invention. Figure 1 As shown, the solutions for abnormal ECU reset include:

[0049] Step S10: When the electronic control unit resets and fails to recover, obtain the number of times the electronic control unit has been reset consecutively, the maximum interval between all two adjacent resets during the period of multiple consecutive resets of the electronic control unit, the battery temperature, and the current vehicle speed.

[0050] In this embodiment, when the electronic control unit (ECU) detects an abnormality in its internal modules, the ECU's main control chip actively initiates a state transition from the abnormal state to the initialization state to achieve self-recovery; that is, the ECU resets. When it is determined that the ECU's main control chip has reset and recovery has failed, the hardware circuit acquires the number of consecutive resets of the ECU, the maximum interval between all adjacent resets during the period of multiple consecutive resets, the battery temperature, and the current vehicle speed. Specifically, when the ECU's main control chip resets, the reset port is at a low level; after successful recovery, the reset port is at a high level. The hardware circuit determines the number of times the ECU resets within a preset time period by detecting the number of times the reset port changes from high to low within that preset time period. It should be noted that when the main control chip of the electronic control unit is determined to have been reset and failed to recover, the electronic control unit will power down and will no longer output any control signals, communication signals, or other signals. It will completely stop communicating with other devices. Therefore, before enabling the battery motor relay switch through the hardware circuit, it is necessary to ensure that the electronic control unit that failed to recover has been powered down and will not interfere with the output signals of the hardware module.

[0051] Step S20: When the number of consecutive resets of the electronic control unit, the maximum interval duration, the battery temperature, and the current vehicle speed meet the preset conditions, the battery motor relay switch is enabled by controlling the hardware circuit.

[0052] In this embodiment, a hardware circuit is installed in the vehicle to detect whether the number of consecutive resets of the electronic control unit (ECU), the maximum interval between all adjacent resets during multiple consecutive resets, the battery temperature, and the current vehicle speed meet preset conditions. When the number of consecutive resets of the ECU, the maximum interval between all adjacent resets during multiple consecutive resets, the battery temperature, and the current vehicle speed meet the preset conditions, the hardware circuit outputs a high-level signal. This high-level signal enables the battery motor relay to switch, thus establishing an electrical connection between the battery motor relay and the battery.

[0053] This application does not limit the specific structure of the hardware circuit. The hardware circuit may consist of independent electronic components or integrated single or multiple chips, or a minimized low-cost controller, or another controller identical to the original controller, as long as the disconnection and connection between the battery relay and the battery can be achieved through the hardware circuit. In one possible implementation, the hardware circuit includes a control circuit, a level output circuit, and a drive circuit. The control circuit controls the level output circuit to output a high level, and then the drive circuit amplifies the drive current. The drive current is used to enable the battery motor relay switch, thereby restoring the connection between the battery and the battery motor relay.

[0054] Furthermore, when the number of times the electronic control unit is reset, the maximum interval between all adjacent resets during multiple consecutive resets of the electronic control unit, the battery temperature, and the current vehicle speed do not meet the preset conditions, a low level is output through the set hardware circuit. The low level output by the hardware circuit cannot enable the switch of the battery motor relay, that is, the electrical connection between the battery motor relay and the battery cannot be realized.

[0055] This application uses the battery management system control unit as an example, but the solution for restoring the control unit that has been reset is not limited to restoring only this type of battery management control unit, but also includes restoring other similar control units to achieve similar important functions.

[0056] Furthermore, in one embodiment, the preset condition is:

[0057] The number of times the electronic control unit is continuously reset is greater than the preset number of resets, the maximum interval time is less than the preset reset time, the battery temperature is less than the preset temperature, and the current vehicle speed is greater than the preset vehicle speed.

[0058] In this embodiment, if the interval between two consecutive resets of the electronic control unit (ECU) is less than the preset reset duration, it is determined that the ECU has continuously reset. Taking a preset reset duration of 3 seconds, a preset number of resets of 18, a preset temperature of 80°C, and a preset vehicle speed of 30 km / h as an example, if the number of consecutive resets of the ECU is less than or equal to the preset number of resets, it is considered a normal reset condition. If the longest interval between all two consecutive resets during a period of multiple consecutive resets is greater than or equal to the preset reset duration, it indicates that the current ECU reset is a normal execution of the reset function. When the battery temperature is greater than or equal to 80°C, if the battery continues to supply power, there is a high probability of a fire. When the vehicle's current speed is less than or equal to 30 km / h, since the speed is already very low, even if the connection between the battery and the battery motor relay suddenly disconnects and the vehicle loses power, there will not be a significant traffic risk. This embodiment is only an example; the specific preset reset duration, preset number of resets, preset temperature, and preset vehicle speed can be appropriately adjusted according to actual needs, and this embodiment is not limited thereto.

[0059] Therefore, by setting the preset conditions such that the number of consecutive resets of the electronic control unit is greater than the preset number of resets, the maximum interval time is less than the preset reset time, the battery temperature is less than the preset temperature, and the current vehicle speed is greater than the preset vehicle speed, it is possible to enable the battery motor relay switch through hardware circuitry in scenarios where abnormal reset conditions are identified and the vehicle speed is high, thereby restoring the connection between the battery and the battery motor relay. At the same time, it avoids forcibly connecting the battery and the battery motor relay when the battery temperature is too high, which could lead to a fire risk in the vehicle.

[0060] In this embodiment, when the electronic control unit (ECU) resets and fails to recover, the system acquires the number of consecutive ECU resets, the maximum interval between all adjacent resets during multiple consecutive ECU resets, the battery temperature, and the current vehicle speed. When the number of consecutive ECU resets, the maximum interval, the battery temperature, and the current vehicle speed meet preset conditions, the battery motor relay switch is enabled via hardware circuitry. Through this embodiment, when the ECU resets and fails to recover, and the number of consecutive ECU resets, the maximum interval between all adjacent resets during multiple consecutive ECU resets, the battery temperature, and the current vehicle speed meet preset conditions, a high-level output via hardware circuitry enables the battery motor relay switch, thereby restoring the connection between the battery and the battery motor relay. This prevents the ECU from suddenly resetting and failing to recover, solving the problem of vehicles losing power and posing a significant traffic risk when the ECU suddenly resets and fails to recover at high speeds.

[0061] Furthermore, in one embodiment, reference is made to Figure 2 , Figure 2 This is a flowchart illustrating the second embodiment of the solution for abnormal ECU reset according to the present invention. Figure 2 As shown, before the electronic control unit resets and fails to recover, the following steps are included:

[0062] Step S001: When the electronic control unit is reset, initialize each module of the battery management system controller;

[0063] Step S002: If the electronic control unit is still in the reset state after each module has been initialized a preset number of times, then the abnormal state of the battery management system controller is determined.

[0064] Step S003: Locate the faulty module from the modules corresponding to the abnormal state;

[0065] Step S004: Initialize other modules of the battery management system controller, where other modules are modules other than the faulty module;

[0066] Step S005: If the electronic control unit is still in a reset state after the other modules have been initialized a preset number of times, then the marking module in the battery management system controller is initialized, wherein the marking module is the module that affects the opening or closing of the battery motor relay.

[0067] Step S006: If the electronic control unit is still in a reset state after the marking module initializes a preset number of times, it is determined that the electronic control unit has been reset and recovery has failed.

[0068] The preset number of times can be one or more. In this embodiment, two preset times are used as an example for illustrative purposes. In other possible implementations, it can also be three, four, five, etc., and this application embodiment is not limited to this.

[0069] Specifically, when the electronic control unit (ECU) is reset, the various modules of the battery management controller are initialized first. If the ECU is still in a reset state after initializing the various modules of the battery management controller twice, the abnormal state of the battery management system controller is determined, and the faulty module is found from the modules corresponding to the abnormal state.

[0070] After identifying the faulty module, the other modules of the battery management system controller are initialized again. These other modules are those excluding the faulty module.

[0071] After initializing other modules of the battery management system controller twice, if the electronic control unit is still in a reset state, then the marking modules that affect the opening or closing of the battery motor relay are initialized. Specifically, the marking modules include the battery temperature detection module, vehicle speed detection module, high and low level output module, drive circuit module, clock initialization module, timer initialization module, and memory initialization module.

[0072] If the electronic control unit is still in a reset state after the marking module affecting the opening or closing of the battery motor relay is initialized twice, it is determined that the electronic control unit has been reset and the recovery has failed.

[0073] In this embodiment, during the process of determining that the electronic control unit (ECU) has reset and failed to recover, multiple methods are used to restore the reset ECU, which can improve the probability of successful recovery. When it is determined that the ECU has reset and failed to recover, and the ECU can no longer be restored by software or hardware reset, the battery-motor relay switch is enabled by controlling the hardware circuit to restore the connection between the battery and the battery-motor relay, so that the ECU can resume normal control of the important function of deciding and executing whether to enable the connection between the battery and the power motor.

[0074] Furthermore, in one embodiment, reference is made to Figure 3 , Figure 3 for Figure 2 A detailed flowchart of step S002 in the first embodiment. (See attached diagram.) Figure 3 As shown, determining the abnormal state of the battery management system controller includes:

[0075] Step S021: Obtain the current state of the battery management system controller;

[0076] Step S022: When the current state of the battery management system controller is different from the normal current state, determine the previous state of the normal current state as the abnormal state of the battery management system controller.

[0077] In this embodiment, the battery management system controller's states include an initialization state, a normal operation state, a power-down save state, and a power-down state. The initialization state is the previous state of the normal operation state, the normal operation state is the previous state of the power-down save state, and the power-down save state is the previous state of the power-down state. The power-down state is the previous state of the initialization state.

[0078] After the vehicle is powered on, the normal state change of the battery management system controller (BMS) should be from the initialization state to the normal operating state, then to the power-down save state, and finally back to the power-down state. If, after the vehicle is powered on, the current state of the BMS is the initialization state, and the previous state was the normal operating state (meaning the BMS has changed back to the initialization state instead of following the normal state change pattern), then the current state (initialization state) of the BMS is determined to be different from the normal current state (power-down save state). Therefore, the previous state (normal operating state) of the normal current state (power-down save state) is determined to be an abnormal state of the BMS.

[0079] Furthermore, in one embodiment, reference is made to Figure 4 , Figure 4 for Figure 2 A detailed flowchart of step S002 in the second embodiment. (See attached diagram.) Figure 4 As shown, determining the abnormal state of the battery management system controller includes:

[0080] Step S023: Obtain the current state of the battery management system controller recorded in the volatile memory;

[0081] Step S024: Compare the current state with the next state that the latest historical state in the non-volatile memory will transition to;

[0082] Step S025: If the comparison result shows that the current state recorded in the volatile memory is different from the next state that the latest historical state in the non-volatile memory will jump to, then the latest historical state in the non-volatile memory is determined to be an abnormal state.

[0083] In this embodiment, each time the vehicle is powered on, the latest state of the battery management system controller after the current state transitions is recorded and stored in non-volatile memory (NVM). The current state recorded in volatile memory (RAM) is compared with the next state to which the latest historical state in NVM will transition.

[0084] If the current state recorded in the volatile memory (RAM) is the next state that the latest historical state in the non-volatile memory will transition to, then it is determined that the latest historical state in the non-volatile memory has not undergone an abnormal reset.

[0085] If the current state recorded in the volatile memory (RAM) is not the next state that the latest historical state in the non-volatile memory will transition to, then it is determined that the latest historical state in the non-volatile memory has undergone an abnormal reset, that is, the latest historical state in the non-volatile memory is determined to be an abnormal state.

[0086] Specifically, after the vehicle is powered on, if the current state in the volatile memory (RAM) is the initialization state, and the latest historical state in the non-volatile memory is the power-down state recorded during the last power failure, since the next state to which the power-down state recorded during the last power failure will jump is the initialization state, that is, the current state recorded in the volatile memory (RAM) is the next state to which the latest historical state recorded in the non-volatile memory will jump, then it is determined that the power-down state did not undergo an abnormal reset during the last power failure.

[0087] If the latest historical state in the non-volatile memory is not the power-down state recorded during the last power failure, that is, if the current state recorded in the volatile memory (RAM) is not the next state that the latest non-volatile state will transition to, then it is determined that the power-down state during the last power failure was abnormally reset, and that is, the power-down state during the last power failure is determined to be an abnormal state.

[0088] In another embodiment, after the vehicle is powered on, if the current state recorded in the volatile memory (RAM) is the initialization state, and the latest historical state in the non-volatile memory is the normal operating state after this power-on, since the next state to which the normal operating state after this power-on will transition is the power-down saved state, and the current state recorded in the volatile memory (RAM) is the initialization state, which is not the next state to which the latest historical state in the non-volatile memory will transition, it is determined that an abnormal reset has occurred in the normal operating state, i.e., the normal operating state is determined to be an abnormal state. The default value for the non-volatile current state when it is first shipped from the factory is the initialization state.

[0089] Further, in one embodiment, the step of searching for the faulty module from the modules corresponding to the abnormal state includes:

[0090] Check the flag bits of each module corresponding to the abnormal state in the register of the main control chip of the electronic control unit;

[0091] The module whose flag bit is determined to be the preset flag bit is the faulty module.

[0092] In this embodiment, by examining the flag bits corresponding to each module in the registers of the main control chip of the electronic control unit, the module whose flag bit is set to the preset flag bit is identified as the faulty module. Specifically, if the preset flag bit is 1, and a module malfunctions, causing the electronic control unit to reset, the flag bit of that module will change from the default flag bit 0 to 1. Therefore, the module whose flag bit is 1 is identified as a faulty module in an abnormal state of the battery management system controller. It is easy to understand that the parameters corresponding to the default flag bit and the preset flag bit in this embodiment are for reference only and are not intended to be limiting.

[0093] Furthermore, in one embodiment, reference is made to Figure 5 , Figure 5 for Figure 2 A detailed flowchart of an embodiment of step S003. (See attached diagram.) Figure 5 As shown, the fault module for locating the abnormal state includes:

[0094] Step S031: Obtain the number of normal state records of the module corresponding to the abnormal state during the abnormal state period by performing state detection on the module corresponding to the abnormal state according to the module abnormal detection cycle. The abnormal state period is from the end of the previous state to the moment when the abnormal state changes.

[0095] Step S032: Check whether the number of normal state records of the target module is the same as the number of ideal detection result records. The number of ideal detection result records is the quotient of the abnormal state period divided by the module abnormal detection cycle. When the quotient is a decimal, the quotient is rounded up. The target module is the module that performs state detection first among all modules corresponding to the abnormal state in the module abnormal detection cycle.

[0096] Step S033: If they are not the same, then the target module is determined to be the faulty module;

[0097] Step S034: If they are the same, remove the target module from all modules corresponding to the abnormal state, and return to the step of checking whether the number of normal state records of the target module is the same as the number of ideal detection result records.

[0098] In this embodiment, the abnormal state period is from the end time of the previous state to the time when the abnormal state transitions. Specifically, taking the abnormal state as the normal working state as an example, the start time of the abnormal state is the time when the battery management system controller transitions from the initialization state to the normal working state after this power-on, that is, the end time of the initialization state. The end time of the abnormal state is the time when the battery management system controller transitions from the normal working state to the initialization state after this power-on, that is, the time when the abnormal state transitions.

[0099] This function retrieves the number of times the normal state records of the modules corresponding to the abnormal state are performed according to the module abnormality detection cycle within the abnormal state period. Specifically, taking the abnormal state as the normal working state as an example, if all modules in the normal working state are module A, module B, module C, and module D, then it retrieves the number of times the normal state records of modules A, B, C, and D are performed according to the module abnormality detection cycle within the normal working state period. It's easy to see that all modules in the abnormal state are only for reference and are not considered a limitation.

[0100] Since module A performs state checks first, followed by module B, then module C, and finally module D during the module anomaly detection cycle, the target module is module A. The goal is to check whether the number of normal state records for module A matches the ideal number of records. The ideal number of records is the quotient of the normal working state period divided by the module anomaly detection cycle. Specifically, if the normal working state period is 60 seconds and the module anomaly detection cycle (the duration of one state check for modules A, B, C, and D) is 10 seconds, then the ideal number of records is 60 divided by 10, which is 6. If the normal working state period is 18 seconds and the module anomaly detection cycle (the duration of one state check for modules A, B, C, and D) is 10 seconds, then the ideal number of records is 18 divided by 10, rounded up, which is 2.

[0101] When the electronic control unit is reset, if the status of some modules is not updated to the normal state, it is highly likely that the first module whose status was not updated to the normal state in time is faulty. Therefore, if the number of normal state records for module A is 5, that is, the number of normal state records for the target module (module A) is 5, which is different from the number of records for the ideal detection result of 6, then module A is determined to be the faulty module in the module corresponding to the abnormal electrical state.

[0102] In one embodiment, if module A is faulty, subsequent modules B, C, and D will also be unable to update to the normal state in a timely manner. In the same module anomaly detection cycle, the number of normal state records for modules B, C, and D will also be different from the number of records for the ideal detection result. Therefore, after determining that module A is the faulty module among the modules corresponding to the abnormal state, the number of normal state records for modules B, C, and D will continue to be obtained to increase the accuracy of finding the faulty module.

[0103] In another embodiment, after determining that module A is a faulty module in the battery management system controller, the number of normal status records for modules B, C, and D is no longer obtained, thereby improving the efficiency of finding the faulty module.

[0104] If the number of normal state records for module A is 6, meaning the number of normal state records for the target module (module A) is not the same as the number of ideal test result records, then the target module is removed from all modules, i.e., module A is removed from all modules. The process then returns to the step of checking whether the number of normal state records for the target module is the same as the number of ideal test result records, until the faulty module is identified or all modules corresponding to the abnormal state have been tested.

[0105] Since module A has been removed, module B is the first module to perform status checks during the module anomaly detection cycle, and the target module is module B. If module B's normal state record count is 5, meaning the target module's (module B) normal state record count of 5 is different from the ideal detection result record count of 6, then module B is determined to be the faulty module among the modules corresponding to the anomaly state. If module B's normal state record count is 6, meaning the target module's (module B) normal state record count of 6 is the same as the ideal detection result record count of 6, then module B is removed, and the step of checking whether the target module's normal state record count is the same as the ideal detection result record count is returned. This process continues until the first faulty module among modules A, B, C, and D that has not been updated to a normal state in a timely manner is identified.

[0106] It should be noted that the step numbers in the embodiments of this application do not limit the order of operations in the technical solution of this application.

[0107] Secondly, embodiments of the present invention also provide a device for resolving abnormal ECU reset.

[0108] In one embodiment, reference is made to Figure 6 , Figure 6 This is a functional module diagram of an embodiment of the ECU abnormal reset solution device of the present invention. Figure 6 As shown, the device for resolving ECU abnormal reset includes:

[0109] The acquisition module 10 is used to acquire the number of consecutive resets of the electronic control unit, the maximum interval between all two adjacent resets during the period of multiple consecutive resets of the electronic control unit, the battery temperature, and the current vehicle speed when the electronic control unit is reset and fails to recover.

[0110] The calculation and decision module 20 is used to detect the number of times the electronic control unit is continuously reset, the maximum interval duration, the battery temperature, and whether the current vehicle speed meets the preset conditions.

[0111] The control module 30 is used to enable the battery motor relay switch through hardware circuitry when the number of consecutive resets of the electronic control unit, the maximum interval duration, the battery temperature, and the current vehicle speed meet preset conditions.

[0112] Furthermore, in one embodiment, the preset condition is:

[0113] The number of times the electronic control unit is continuously reset is greater than the preset number of resets, the maximum interval time is less than the preset reset time, the battery temperature is less than the preset temperature, and the current vehicle speed is greater than the preset vehicle speed.

[0114] Furthermore, in one embodiment, the ECU abnormal reset resolution device further includes a status determination module, used for:

[0115] When the electronic control unit is reset, the various modules of the battery management system controller are initialized;

[0116] If the electronic control unit remains in a reset state after each module has been initialized a preset number of times, then an abnormal state of the battery management system controller is determined.

[0117] Locate the faulty module from the modules corresponding to the abnormal state;

[0118] Initialize the other modules of the battery management system controller, where "other modules" refers to modules other than the faulty module.

[0119] If the electronic control unit is still in a reset state after the other modules have been initialized a preset number of times, then the marking module in the battery management system controller is initialized, wherein the marking module is the module that affects the opening or closing of the battery motor relay;

[0120] If the electronic control unit remains in a reset state after the marking module has initialized a preset number of times, it is determined that the electronic control unit has been reset and recovery has failed.

[0121] Furthermore, in one embodiment, the ECU abnormal reset resolution device further includes a status determination module, used for:

[0122] Obtain the current state of the battery management system controller;

[0123] When the current state of the battery management system controller is different from the normal current state, the previous state of the normal current state is determined to be the abnormal state of the battery management system controller.

[0124] Furthermore, in one embodiment, the state determination module is also used for:

[0125] Retrieve the current state of the battery management system controller recorded in the volatile memory;

[0126] The current state is compared with the next state that the latest historical state in the non-volatile memory will transition to;

[0127] If the comparison result shows that the current state recorded in the volatile memory is different from the next state that the latest historical state in the non-volatile memory will jump to, then the latest historical state in the non-volatile memory is determined to be an abnormal state.

[0128] Furthermore, in one embodiment, the ECU abnormal reset resolution device further includes a fault finding module, used for:

[0129] Check the flag bits of each module corresponding to the abnormal state in the register of the main control chip of the electronic control unit;

[0130] The module whose flag bit is determined to be the preset flag bit is the faulty module.

[0131] Furthermore, in one embodiment, the fault finding module is also used for:

[0132] Get the number of normal state records of the module corresponding to the abnormal state during the abnormal state period by performing state detection on the module corresponding to the abnormal state according to the module abnormal detection cycle. The abnormal state period is from the end of the previous state to the time when the abnormal state changes.

[0133] The detection module checks whether the number of normal state records of the target module is the same as the number of ideal detection result records. The number of ideal detection result records is the quotient of the abnormal state period divided by the module abnormal detection cycle. When the quotient is a decimal, the quotient is rounded up. The target module is the module that performs state detection first among all modules corresponding to the abnormal state in the module abnormal detection cycle.

[0134] If they are different, then the target module is determined to be the faulty module;

[0135] If they are the same, the target module is removed from all modules corresponding to the abnormal state, and the process returns to the step of checking whether the number of normal state records of the target module is the same as the number of ideal detection result records.

[0136] The functions of each module in the above-mentioned ECU abnormal reset solution device correspond to the steps in the above-mentioned ECU abnormal reset solution embodiment, and their functions and implementation processes will not be described in detail here.

[0137] Thirdly, embodiments of the present invention provide a device for resolving ECU abnormal reset. This device can be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.

[0138] Reference Figure 7, Figure 7 This is a schematic diagram of the hardware structure of the ECU abnormal reset solution device involved in the embodiment of the present invention. In this embodiment, the ECU abnormal reset solution device may include a processor 1001 (e.g., a Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to realize communication between these components; the user interface 1003 may include a display screen or an input unit such as a keyboard; the network interface 1004 may optionally include a standard wired interface or a wireless interface (e.g., Wireless Fidelity, Wi-Fi interface); the memory 1005 may be high-speed random access memory (RAM) or stable memory (non-volatile memory), such as a disk storage device; the memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001. Those skilled in the art will understand that… Figure 7 The hardware structure shown does not constitute a limitation of the invention and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0139] Continue to refer to Figure 7 , Figure 7 The memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a solution program for ECU abnormal reset. The processor 1001 can call the ECU abnormal reset solution program stored in the memory 1005 and execute the ECU abnormal reset solution provided in this embodiment of the invention.

[0140] Fourthly, embodiments of the present invention also provide a readable storage medium.

[0141] The present invention stores a solution program for ECU abnormal reset on a readable storage medium, wherein when the ECU abnormal reset solution program is executed by a processor, the steps of the ECU abnormal reset solution described above are implemented.

[0142] The method implemented when the ECU abnormal reset solution is executed can be referred to in various embodiments of the ECU abnormal reset solution of the present invention, and will not be repeated here.

[0143] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0144] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0145] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of the present invention.

[0146] The above are merely preferred embodiments of the present invention and do not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A solution to an abnormal ECU reset, characterized in that, include: When the electronic control unit (ECU) resets and fails to recover, obtain the number of consecutive ECU resets, the maximum interval between all adjacent ECU resets during the period of multiple consecutive ECU resets, the battery temperature, and the current vehicle speed. When the number of consecutive resets of the electronic control unit, the maximum interval duration, the battery temperature, and the current vehicle speed meet the preset conditions, the battery motor relay switch is enabled by controlling the hardware circuit. The preset conditions are: The number of times the electronic control unit is continuously reset is greater than the preset number of resets, the maximum interval time is less than the preset reset time, the battery temperature is less than the preset temperature, and the current vehicle speed is greater than the preset vehicle speed. Before the electronic control unit resets and fails to recover, the following is included: When the electronic control unit is reset, the various modules of the battery management system controller are initialized; If the electronic control unit remains in a reset state after each module has been initialized a preset number of times, then an abnormal state of the battery management system controller is determined. Locate the faulty module from the modules corresponding to the abnormal state; Initialize the other modules of the battery management system controller, where "other modules" refers to modules other than the faulty module. If the electronic control unit is still in a reset state after the other modules have been initialized a preset number of times, then the marking module in the battery management system controller is initialized, wherein the marking module is the module that affects the opening or closing of the battery motor relay; If the electronic control unit remains in a reset state after the marking module has initialized a preset number of times, it is determined that the electronic control unit has been reset and recovery has failed.

2. The solution to the ECU abnormal reset as described in claim 1, characterized in that, The determination of the abnormal state of the battery management system controller includes: Obtain the current state of the battery management system controller; When the current state of the battery management system controller is different from the normal current state, the previous state of the normal current state is determined to be the abnormal state of the battery management system controller.

3. The solution to the ECU abnormal reset as described in claim 1, characterized in that, The determination of the abnormal state of the battery management system controller includes: Retrieve the current state of the battery management system controller recorded in the volatile memory; The current state is compared with the next state that the latest historical state in the non-volatile memory will transition to; If the comparison result shows that the current state recorded in the volatile memory is different from the next state that the latest historical state in the non-volatile memory will jump to, then the latest historical state in the non-volatile memory is determined to be an abnormal state.

4. The solution to the ECU abnormal reset as described in claim 1, characterized in that, The step of finding the faulty module from the modules corresponding to the abnormal state includes: Check the flag bits of each module corresponding to the abnormal state in the register of the main control chip of the electronic control unit; The module whose flag bit is determined to be the preset flag bit is the faulty module.

5. The solution to the ECU abnormal reset as described in claim 1, characterized in that, The step of finding the faulty module from the modules corresponding to the abnormal state includes: Get the number of normal state records of the module corresponding to the abnormal state during the abnormal state period by performing state detection on the module corresponding to the abnormal state according to the module abnormal detection cycle. The abnormal state period is from the end of the previous state to the time when the abnormal state changes. The detection module checks whether the number of normal state records of the target module is the same as the number of ideal detection result records. The number of ideal detection result records is the quotient of the abnormal state period divided by the module abnormal detection cycle. When the quotient is a decimal, the quotient is rounded up. The target module is the module that performs state detection first among all modules corresponding to the abnormal state in the module abnormal detection cycle. If they are different, then the target module is determined to be the faulty module; If they are the same, the target module is removed from all modules corresponding to the abnormal state, and the process returns to the step of checking whether the number of normal state records of the target module is the same as the number of ideal detection result records.

6. A device for resolving ECU abnormal reset, characterized in that, in order to achieve the solution for ECU abnormal reset as described in any one of claims 1 to 5, The device for resolving ECU abnormal reset includes: The acquisition module is used to acquire the number of consecutive resets of the electronic control unit, the maximum interval between all adjacent resets during the period of multiple consecutive resets of the electronic control unit, the battery temperature, and the current vehicle speed when the electronic control unit is reset and fails to recover. The calculation and decision module is used to detect the number of times the electronic control unit is continuously reset, the maximum interval duration, the battery temperature, and whether the current vehicle speed meets the preset conditions. The control module is used to enable the battery motor relay switch through hardware circuitry when the number of consecutive resets of the electronic control unit, the maximum interval duration, the battery temperature, and the current vehicle speed meet preset conditions.

7. A device for resolving ECU abnormal reset, characterized in that, The ECU abnormal reset resolution device includes a processor, a memory, and an ECU abnormal reset resolution program stored in the memory and executable by the processor, wherein when the ECU abnormal reset resolution program is executed by the processor, it implements the steps of the ECU abnormal reset resolution method as described in any one of claims 1 to 5.

8. A readable storage medium, characterized in that, The readable storage medium stores a solution program for ECU abnormal reset, wherein when the ECU abnormal reset solution program is executed by the processor, it implements the steps of the solution program for ECU abnormal reset as described in any one of claims 1 to 5.

Images