A method, device and vehicle for diagnosing excessive static current of automobile controller

Abstract

An embodiment of the present application provides a method, device and vehicle for diagnosing excessive static current of an automobile controller. The method includes: when the automobile bus is detected to be asleep, starting a timer and monitoring the state corresponding to the state machine of the target controller; if the state of the state machine of the target controller continues to remain in the target state within the preset timing duration of the timer, then determining that the target controller is faulty. The present application aims to solve the problem that the diagnosis of excessive static current requires the reproduction of the automobile fault, which leads to high troubleshooting difficulty and long troubleshooting cycle.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of automobile technology, and more specifically, to a method, device and vehicle for diagnosing excessive static current of an automobile controller. Background Art

[0002] As cars become more and more electrified and intelligent, controller logic becomes more and more complex. The problem of battery failure caused by excessive static current in controllers is also increasing. Once a car fails to start after battery failure, it will have a great impact, high severity level, and easily cause strong complaints from users.

[0003] At present, the diagnosis of excessive static current depends on the reproduction of automobile faults, so that the faulty controller can be located by unplugging fuses and connectors. If the fault is not reproduced, the faulty controller cannot be located, which will lead to high difficulty in troubleshooting and a long troubleshooting cycle. Summary of the invention

[0004] The embodiments of the present application provide a method, device and vehicle for diagnosing excessive static current in an automobile controller, aiming to solve the problem that the diagnosis of excessive static current requires the reproduction of the automobile fault, which leads to high troubleshooting difficulty and long troubleshooting cycle.

[0005] A first aspect of an embodiment of the present application provides a method for diagnosing excessive static current of an automobile controller, the method comprising: when a vehicle bus is detected to be in sleep state, starting a timer and monitoring the state corresponding to a state machine of a target controller; if the state of the state machine of the target controller continues to remain in a target state within a preset timing duration of the timer, determining that the target controller is faulty; the target state indicates that the static current of the target controller exceeds a preset current threshold.

[0006] Optionally, when it is determined that the target controller is faulty, a first fault code of the target controller is generated; when vehicle wake-up is detected, the first fault code is displayed.

[0007] Optionally, if the state of the state machine of the target controller changes within the preset time period, the timer is reset based on the changed state; wherein the state of the state machine of the target controller changes includes:

[0008] Jump from the target state to the other state, and jump from the other state to the target state; wherein the other state represents that the static current of the target controller is lower than the preset current threshold.

[0009] Optionally, when it is detected that the vehicle changes from the bus sleep state to the bus wake state, the timing of the timer is stopped.

[0010] Optionally, within the preset time period, the number of state jumps of the state machine of the target controller is counted; when the number of jumps exceeds a target number, a second fault code of the target controller is generated.

[0011] Optionally, when it is detected that the vehicle is woken up, the second fault code is displayed.

[0012] Optionally, counting the number of jumps of the state machine of the target controller includes: starting a counter, and counting the number of state jumps of the state machine of the target controller through the counter; and clearing the counter when the number of jumps does not exceed a target number.

[0013] Optionally, the number of times recorded by the counter is stored in a memory.

[0014] The present application also provides a diagnostic device for excessive static current of an automobile controller, comprising: a monitoring module, for starting a timer and monitoring the state of a state machine of a target controller when a sleep state of the automobile bus is detected;

[0015] The diagnostic module is used to determine whether the state of the state machine of the target controller continues to remain in the target state within the preset timing duration of the timer, and if it continues to remain in the target state, it is determined that the target controller is faulty.

[0016] The present application also provides a vehicle, comprising one or more steps of the method described in the method for diagnosing excessive static current of an automobile controller in an embodiment of the present application, or comprising a diagnostic device for excessive static current of an automobile controller in an embodiment of the present application.

[0017] This application has the following advantages:

[0018] By adopting the technical solution of the embodiment of the present application, when the sleep state of the vehicle bus is detected, the timer is started and the quiescent current of the target controller is monitored; if the quiescent current of the target controller continues to exceed the preset current threshold within the preset timing time of the timer, the target controller is determined to be faulty. By adopting the method of the embodiment of the present application, after judging that the quiescent current of the controller exceeds the standard and continues for the preset timing time, it can be determined that the controller is faulty, and the problem of the vehicle can be quickly located without reproducing the fault, greatly shortening the time for troubleshooting. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0020] Figure 1 is a flow chart of the steps for detecting whether a target controller is faulty in an embodiment of the present application;

[0021] Figure 2 Different states of a state machine of a controller A in an embodiment of the present application and corresponding operating currents;

[0022] Figure 3 is a flow chart of the diagnosis of the static current exceeding the standard by the timer in the embodiment of the present application;

[0023] Figure 4 It is a flow chart of the diagnosis of the quiescent current exceeding the standard by the counter in the embodiment of the present application. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0025] Under normal circumstances, after the power of the car is turned off, the car bus goes into sleep mode (the car bus is a controller area network, which is a serial communication network that can effectively support distributed control and real-time control). After the car bus goes into sleep mode, the remaining controllers on the car will also enter a local sleep state within a specified time (meaning that after the entire vehicle bus goes into sleep mode, the controller stops some or all functions, and the controller reaches the static current target value).

[0026] If the controller does not enter the local sleep state within the specified time after the bus sleep, the static current in the controller exceeds the target value, which will cause the car to lose power. After the power loss occurs, it will not only damage the battery of the car, but also cause the car to fail to start, resulting in a poor user experience. The static current of most existing controllers exceeds the standard only occasionally. After an occasional occurrence, the fault will not recur, and it takes a long time to troubleshoot multiple times. Some problems may even cause repeated power loss on multiple vehicles because they have not been reproduced, and the problem cannot be solved.

[0027] For example, if a certain controller A fails once, the car will lose power and cannot start, and the user cannot find the faulty controller. The next time the car loses power, controller A may not fail, but another controller B may fail. Therefore, the user cannot find the faulty controller. In addition, if there is no subsequent power loss problem, the fault of controller A will not be reproduced.

[0028] In view of this, an embodiment of the present application provides a method for diagnosing excessive static current of an automobile controller. The technical concept adopted is: when the automobile bus is in sleep mode, the state of the controller's state machine is monitored, that is, the static current of the controller is monitored to determine the faulty controller, thereby solving the problem that the diagnosis of excessive static current requires the reproduction of the automobile fault, which leads to high troubleshooting difficulty and long troubleshooting cycle.

[0029] Reference Figure 1 As shown, a flow chart of the steps for detecting whether the target controller is faulty in the present application is shown, such as Figure 1 As shown, the following steps are included:

[0030] Step S21: First, when the vehicle bus is detected to be in sleep state, start the timer and monitor the state corresponding to the state machine of the target controller.

[0031] Step S22: If the state of the state machine of the target controller continues to remain in the target state within the preset timing duration of the timer, it is determined that the target controller is faulty; the target state indicates that the quiescent current of the target controller exceeds a preset current threshold.

[0032] In the embodiment of the present application, whether the static current of the controller exceeds the standard is determined when the vehicle bus is in sleep state.

[0033] In an embodiment of the present application, there may be multiple target controllers in a car, among which, there may be three situations for the multiple controllers after the car bus goes into sleep mode, wherein situation one is that all controllers are in sleep mode, at which time the quiescent current in the controller is at the lowest level and does not reach the standard for quiescent current exceeding the standard; situation two is that part of the controller is in a local sleep mode and the other part is in a wake-up mode, that is, there is working current in the controller, at which time the quiescent current of the controller exceeds the standard; situation three is that all controllers are in wake-up mode, at which time the quiescent current of the controller exceeds the standard.

[0034] In these three cases, the state machine of the controller in cases 2 and 3 is in the target state, which reflects that the static current in the controller exceeds the standard; the state machine of the controller in case 1 is in a state other than the target state, which reflects that the static current of the controller does not exceed the standard.

[0035] In the embodiment of the present application, the controller may have multiple functions, see Figure 2 The figure shows the state of a state machine of a controller A and the corresponding working current diagram. As shown in the figure, the controller A has function 1, function 2 and function 3. After turning on or off the function, the controller A appears in four states, namely state 1, state 2, state 3 and state 4.

[0036] Among them, state 1 is bus wake-up, function 1, function 2 and function 3 are all running normally, and the corresponding working current is 2000mA;

[0037] State 2 is the car bus sleep state, controller A function 1 is turned off, function 2 and function 3 are running normally, and the corresponding working current is 1500mA;

[0038] State 3 is the car bus sleep state, controller A function 1 and function 2 are turned off, function 3 is running normally, and the corresponding working current is 700mA;

[0039] State 4 is the car bus sleep state, and functions 1, 2, and 3 of controller A are all turned off. At this time, the corresponding operating current is 1mA.

[0040] like Figure 2 As shown, state two and state three both reflect the situation that the static current in controller A exceeds the standard after the bus goes into sleep mode, which is the target state. At this time, the static current in controller A exceeds the threshold value. Maintaining this state for a long time will cause damage to the car battery, and at the same time, the car will lose power, and even fail to start. State four is the state after both controller A and the car bus enter the sleep state, which is the other state except the target state. At this time, the static current in controller A is kept at the minimum, which is the threshold value of the static current. If the controller maintains this state after the car bus goes into sleep mode, it will not cause damage to the car battery.

[0041] In some embodiments, there may be multiple controllers, and the controllers may also have multiple functions. Generally, a vehicle with more functions corresponds to more controllers, and this application does not impose any limit on the number.

[0042] In the embodiment of the present application, the preset duration is the state monitoring time of the state machine of the controller set according to the specific situation. If the state duration of the state machine of the controller exceeds this preset duration, it is judged that the controller has a fault. The preset duration can be set to T. For example, if the controller A in the above is in state 2 or state 3 and the duration exceeds T, it is judged that the controller has a fault.

[0043] In some embodiments, the preset time length T is not a fixed time length and can be set according to the specific circumstances of the vehicle. Generally, the more controllers a vehicle has and the more functional controllers it has (often found in high-end models), the longer the preset time length T is.

[0044] If the state of the state machine of the target controller is always maintained at the target state within the preset timing duration of the timer, the timer is automatically terminated after exceeding the preset duration.

[0045] The technical solution of the embodiment of the present application is adopted. First, whether the vehicle bus is in a sleep state is monitored. After the vehicle bus is detected to be in sleep state, the timer is started and the state of the state machine of the target controller is monitored. If the state of the state machine of the target controller continues to remain in the target state within the preset timing duration of the timer, the target controller is determined to be faulty. The method of the embodiment of the present application does not require other sensors. It only needs the timer to measure the duration of the state of the state machine of the controller to determine whether the controller is faulty. Compared with the method in the prior art that requires the fault to be reproduced to determine that the static current of the controller exceeds the standard, the time for troubleshooting is greatly shortened and the implementation method is simpler and more convenient.

[0046] There are usually two application scenarios of this method. The first scenario is that after the car owner finishes using the car, some controllers cannot reach the local sleep state after the whole vehicle bus sleeps, resulting in excessive static current, which causes the car to run out of power or the battery power to decrease rapidly; the second scenario is that after the car owner finishes using the car, he adjusts the power mode to OFF, and the controller reaches the local sleep state after the whole vehicle bus sleeps, but after a period of time, due to unknown reasons, some controllers remain in the local wake-up state after being awakened locally and cannot enter the local sleep state again, which causes the car to run out of power or the battery power to decrease rapidly.

[0047] For the above two situations, refer to Figure 3 , is a flowchart of diagnosing excessive static current of a controller according to an embodiment of the present application. Figure 3 In the diagram, DTC (Diagnostic Trouble Cod) is a diagnostic trouble code, which is used to record the state of the controller's state machine. When the controller's state machine continues to maintain the target state, a corresponding diagnostic trouble code can be generated, which is convenient for finding a faulty controller after a power failure occurs.

[0048] Combination Figure 3 The controller static current exceeding standard detection method in the embodiment of the present application is introduced:

[0049] In another embodiment, when a fault is detected in the target controller, a fault code of the fault may be generated. Specifically, as follows: when the target controller is determined to be faulty, a first fault code of the target controller is generated; and when the vehicle wake-up is detected, the first fault code is displayed.

[0050] In the embodiment of the present application, after it is determined in step 21 that a fault occurs in the controller, a first fault code is generated, and a snapshot of the first fault code is saved after the first fault code occurs.

[0051] After the car bus goes to sleep, a corresponding fault code and snapshot are generated. Through this fault code, the controller that causes the car to run out of power can be quickly locked. The problem with the vehicle can be quickly located without reproducing the fault, greatly shortening the problem troubleshooting time; the diagnostic method of the embodiment of the present application is simple to implement, does not require battery sensors, smart fuse boxes and other current measuring devices, and has a wider applicability; the diagnostic method of the embodiment of the present application can directly locate the problem circuit, improves the efficiency of fault resolution, and makes the analysis of the problem clearer; after the fault code is generated, the problem controller can be located by reading the fault code, and there is no need to occupy the user's vehicle or disassemble vehicle parts, thereby improving user satisfaction.

[0052] In another embodiment, if the state of the state machine of the target controller repeatedly jumps between the target state and other states within a preset time period, in this case, in order to accurately detect the failure of the target controller, it can be determined whether a failure occurs according to the number of state machine state jumps or the duration.

[0053] First, the state transition of the state machine of the controller referred to in this application is described:

[0054] If the state of the state machine of the target controller changes within the preset time, the timer is reset; wherein the state of the state machine of the target controller changes including:

[0055] Jump from the target state to the other state, and jump from the other state to the target state;

[0056] The other states represent that the static current of the target controller is lower than the preset current threshold. It should be noted that the other states are states other than the target state.

[0057] In the application embodiment, the timer is used to count the duration of the state of the state machine of the target controller. If the state of the state machine of the controller continues to maintain the target state and the time exceeds the preset duration, the corresponding first fault code is generated and the snapshot is saved after the controller is judged to be faulty.

[0058] The diagnostic logic is: after the car bus goes to sleep, it starts to monitor whether the controller reaches the local sleep state, and starts the timer (hereinafter referred to as: Timer_QC) for timing;

[0059] If the controller is in local sleep mode (or the controller changes from local sleep mode to local wake-up mode) during the timing process, Timer_QC will be reset.

[0060] After the Timer_QC timing exceeds the preset time (T is the specified time), the first fault code is generated and the snapshot information is recorded (for example, the timing stops after T time in the local sleep state). The Timer_QC stops timing after exceeding the preset time.

[0061] In the application embodiment, if the state of the state machine of the target controller jumps and the timing time of the timer does not exceed the preset duration, for example, the state of the state machine of the above-mentioned controller jumps from other states to the target state, and the time in the timer does not reach T, the timing of the timer is reset; if the state of the state machine of the above-mentioned controller jumps from the target state to other states, and the timing in the timer does not reach T, the timing of the timer is also reset.

[0062] Resetting the timing of the timer is used to further judge whether the controller is faulty or not. Two situations may occur at this time. The first situation is that after the car bus sleeps, some controllers will continue to work for a period of time to maintain the normal needs of users. Usually, this duration is shorter than the above-mentioned preset time. If after this time, the state of the controller's state machine continues for the preset time and still does not reach other states, it can be determined that the controller has a static current exceeding the standard fault. The second situation is that if the car bus sleeps, the controllers sleep at the same time, but after a period of time (not exceeding the preset time), all or part of the controllers wake up for unknown reasons, and the state of the controller's state machine is in the target state, then the timer is reset and the timing starts again. The timer reset setting can better find the cause of the controller failure.

[0063] In the embodiment of the present application, if it is detected that the vehicle changes from the bus sleep state to the bus wake state, the timer is stopped. When the vehicle changes from the bus sleep state to the bus wake state, the strategy of determining the state of the controller's state machine is no longer applicable to this situation, and the time in the timer is cleared and stopped.

[0064] In other embodiments, reference Figure 4 , within the preset time length, counting the number of state jumps of the state machine of the target controller; when the number of jumps exceeds the target number, generating a second fault code of the target controller.

[0065] In the embodiment of the present application, the number of times recorded by the counter is stored in a memory, and the memory can store the counting number data of the counter.

[0066] The operation process of the counter is that after the car bus sleeps, each time the controller wakes up locally (the car bus is still in sleep state), the counter QC_Counter+=1 needs to be performed, where QC_Counter is a counter, and Counter+=1 is equivalent to count++, that is, count plus 1;

[0067] Each time the controller goes into local sleep mode, it needs to store QC_Counter+=1 in the memory, and accumulate the previous value after the next local wake-up.

[0068] When QC_Counter exceeds the specified number of times, a second fault code is generated and the snapshot information is recorded. QC_Counter stops after exceeding the specified number of times.

[0069] In the embodiment of the present application, if the state of the state machine in the target controller jumps frequently, and the number of jumps exceeds the specified target number, the controller is judged to be faulty and a second fault code is generated. After the car bus goes to sleep, the controller may frequently wake up and then go to sleep again, and so on repeatedly, and the duration of each wake-up or sleep does not exceed the preset duration T. After this situation occurs, since the duration does not reach the preset duration, the corresponding first fault code will not be generated, but this situation will still cause damage to the car's battery, causing the car to lose power. Therefore, if this kind of fault occurs, a second fault code is generated.

[0070] The first fault code and the second fault code may be different, wherein the first fault code is used to indicate that the state of the controller's state machine has been in the target state for longer than a specified time, and the second fault code is used to indicate that the state of the controller's state machine has jumped more than a specified number of times.

[0071] In an embodiment of the present application, after the second fault code is generated, when it is detected that the vehicle is awakened, the second fault code is displayed, and the displayed second fault code facilitates targeted maintenance when the fault is discovered.

[0072] In an embodiment of the present application, the device for counting the number of state jumps of the state machine of the target controller may be a counter, and the counter is used to count after each state jump of the state machine. The method includes: starting the counter, and counting the number of state jumps of the state machine of the target controller by the counter; and clearing the counter when the number of jumps does not exceed the target number.

[0073] In the embodiment of the present application, the numerical value of the target number of times specified on the counter can be set according to actual conditions.

[0074] In an embodiment of the present application, when the number of jumps does not exceed the target number, after the last state change of the controller state machine, the time it maintains the last existing state continues to exceed the preset time length. At this time, there are two situations. One is that the state of the last state machine is maintained as the target state, and the first fault code is generated at this time. The other is that the state of the last state machine is maintained as other states, and the counter is cleared at this time.

[0075] Based on the same inventive concept, another embodiment of the present application provides a diagnostic device for excessive static current of an automobile controller, the device comprising:

[0076] A monitoring module, used for starting a timer and monitoring the state of a state machine of a target controller when a sleep state of the vehicle bus is detected;

[0077] The diagnostic module is used to determine whether the state of the state machine of the target controller continues to remain in the target state within the preset timing time of the timer, and if it continues to remain in the target state, it is determined that the target controller is faulty.

[0078] Optionally, the device may further include the following modules:

[0079] A first fault code generating module, configured to generate a first fault code of the target controller when determining that the target controller is faulty;

[0080] The first fault code display module is used to display the first fault code when vehicle wake-up is detected.

[0081] Optionally, the device further comprises:

[0082] A timer resetting module, configured to reset the timer based on the state of the state machine of the target controller if the state of the state machine of the target controller jumps within the preset time period;

[0083] The state jump of the state machine of the target controller includes: jumping from the target state to the other state, and jumping from the other state to the target state; wherein the other state indicates that the static current of the target controller is lower than the preset current threshold.

[0084] Optionally, the device further comprises:

[0085] A timer stop module is used to stop the timer when detecting that the vehicle bus changes from a sleep state to a bus wake-up state. Optionally, the device further includes:

[0086] A static current change counting module, used for counting the number of state jumps of the state machine of the target controller, and determining that the target controller is faulty if the number of state jumps of the state machine of the target controller exceeds a specified number;

[0087] When the number of state transitions of the state machine of the target controller does not exceed the target number, the count number is cleared.

[0088] Optionally, the device further comprises:

[0089] A second fault code generating module, configured to generate a second fault code of the target controller when determining that the target controller is faulty;

[0090] The second fault code display module is used to display the second fault code when vehicle wake-up is detected.

[0091] Optionally, the device further comprises:

[0092] The memory module is used to store the number of times recorded by the counter.

[0093] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0094] Based on the same inventive concept, another embodiment of the present application provides a vehicle, which is provided with a monitoring device, a timing device, a feedback device and a counting device, so that the vehicle can execute the method for diagnosing excessive static current of the automobile controller described in the above-mentioned embodiment of the present application, or includes the above-mentioned diagnostic device for excessive static current of the automobile controller.

[0095] In the embodiment of the present application, vehicles of all types are suitable for installing the diagnostic device for excessive static current of automobile controllers, and controllers suitable for adopting the above-mentioned method for diagnosing excessive static current of automobile controllers are all common electrical controllers.

[0096] In general, the method for diagnosing excessive static current of an automobile controller and the device for diagnosing excessive static current of an automobile controller provided by the present application have the following advantages:

[0097] Strong applicability, can be adapted to different models and various commonly used controllers;

[0098] Simple implementation, no current measuring device is required to complete the diagnosis;

[0099] Distributed diagnosis of the static current of the controller can be realized by monitoring the state of the state machine of the controller. Each controller can independently complete the diagnosis process of static current exceeding the standard without the need for cooperation of other sensors and controllers. The diagnosis process is simpler and the diagnosis results are more intuitive.

[0100] After the car bus falls asleep, the state of the controller's state machine and the timing method are used to make fault judgments. Timing is used to avoid the state machine not jumping due to the design, thus avoiding misjudgment.

[0101] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0102] It should also be noted that, in this article, the orientation or position relationship indicated by the terms "center", "up", "down", "left", "right", "vertical", "horizontal", "inside", "outside", etc. is based on the orientation or position relationship shown in the drawings, which is only for the convenience of describing the present application and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present application. In addition, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations, nor can they be understood as indicating or implying relative importance. Moreover, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. Without more restrictions, an element defined by the phrase "comprising a ..." does not exclude the existence of other identical elements in the process, method, article or terminal device comprising the element.

[0103] The technical solution provided by the present application is described in detail above. The principle and implementation method of the present application are described in this article using specific examples. The description of the above embodiments is only used to help understand the present application, and the content of this specification should not be understood as limiting the present application. At the same time, for those of ordinary skill in the art, according to the present application, there will be different forms of changes in the specific implementation methods and application scopes. It is not necessary and impossible to list all the implementation methods here, and the obvious changes or modifications derived therefrom are still within the scope of protection of the present application.

Claims

1. A method for diagnosing excessive static current of an automobile controller, characterized in that: The method comprises: When the vehicle bus is detected to be asleep, a timer is started and a corresponding state of a state machine of a target controller is monitored; If the state of the state machine of the target controller continues to remain in the target state within the preset time length of the timer, it is determined that the target controller is faulty; the target state indicates that the static current of the target controller exceeds a preset current threshold; If the state of the state machine of the target controller jumps within the preset time length, resetting the timer; Within the preset time period, counting the number of state jumps of the state machine of the target controller; When the number of jumps exceeds the target number, generating a second fault code of the target controller; The state of the state machine of the target controller jumps, including: Jump from the target state to other states, and jump from other states to the target state; The other state indicates that the static current of the target controller is lower than the preset current threshold.

2. The method for diagnosing excessive static current of an automobile controller according to claim 1, characterized in that: The method further comprises: In the case of determining that the target controller is faulty, generating a first fault code of the target controller; When vehicle wake-up is detected, the first fault code is displayed.

3. The method for diagnosing excessive static current of an automobile controller according to claim 1, characterized in that: The method further comprises: When it is detected that the vehicle changes from the bus sleep state to the bus wake state, the timer is stopped.

4. The method for diagnosing excessive static current of an automobile controller according to claim 1, characterized in that: The method further comprises: When it is detected that the vehicle is woken up, the second fault code is displayed.

5. The method for diagnosing excessive static current of an automobile controller according to claim 1, characterized in that: Counting the number of jumps of the state machine of the target controller includes: Starting a counter, and counting the number of times the state of the state machine of the target controller jumps through the counter; When the number of jumps does not exceed the target number, the counter is cleared.

6. The method for diagnosing excessive static current of an automobile controller according to claim 5, characterized in that: The method further comprises: The number of times recorded by the counter is stored in a memory.

7. A diagnostic device for excessive static current of an automobile controller, the device comprising: A monitoring module, used for starting a timer and monitoring the state of a state machine of a target controller when a sleep state of the vehicle bus is detected; a diagnostic module, configured to determine whether the state of the state machine of the target controller continues to remain in a target state within a preset timing duration of the timer, and if so, determine that the target controller is faulty; the target state indicates that a quiescent current of the target controller exceeds a preset current threshold; A timer resetting module, configured to reset the timer based on the state of the state machine of the target controller if the state of the state machine of the target controller jumps within the preset timing duration; A static current change counting module, used for counting the number of state jumps of the state machine of the target controller, and determining that the target controller is faulty if the number of state jumps of the state machine of the target controller exceeds a specified number; The state jump of the state machine of the target controller includes: jumping from the target state to other states, and jumping from other states to the target state; wherein the other states represent that the static current of the target controller is lower than the preset current threshold.

8. A vehicle, comprising the diagnostic device for excessive static current of an automobile controller as claimed in claim 7.

Images