Vehicle network non-sleep diagnosis method and device, vehicle and storage medium

Abstract

The application provides a vehicle network non-dormancy diagnosis method, device, vehicle and storage medium. The method comprises the following steps: acquiring a power mode signal, a vehicle network state and a high-voltage system state signal; when the power mode signal, the vehicle network state and the high-voltage system state signal meet corresponding conditions of vehicle network non-dormancy, starting a timer; when the timer counts up to a preset time, triggering fault data recording. The application can quickly determine the controller causing the network non-dormancy problem, and can determine the fault reason of the fault controller.

Description

Technical Field

[0001] This invention relates to the field of vehicle diagnostic technology, and in particular to a diagnostic method, device, vehicle, and storage medium for preventing vehicle networks from going into sleep mode. Background Technology

[0002] Currently, AUTOSAR network management is fundamental to ensuring vehicle communication and functionality. Each controller involved in AUTOSAR network management is connected to the gateway via a CAN bus. When the vehicle's power mode is OFF, each controller checks for sleep conditions. Once all controllers are in sleep mode, the entire vehicle network also enters a sleep state.

[0003] When the vehicle's power is off, if a message is still received on the CAN bus from a controller, this controller will not meet the sleep conditions to enter sleep mode. As a result, the vehicle network will remain active, leading to excessive vehicle current and potentially causing battery depletion. Current technology uses vehicle battery sensors to detect the current when the vehicle's power is off. When the current exceeds a preset value, the vehicle network is activated, and the onboard controller sends abnormal current data to the vehicle's backend monitoring system to alert the user for maintenance.

[0004] The inventors discovered that the background detector could not identify the abnormal controller based on the received abnormal current data, nor could it determine the cause of the fault. Summary of the Invention

[0005] This invention provides a diagnostic method, apparatus, vehicle, and storage medium for vehicle network non-sleep mode, to solve the problem of being unable to identify the abnormal controller and the cause of the fault when the vehicle network is not in sleep mode.

[0006] In a first aspect, embodiments of the present invention provide a diagnostic method for vehicle network non-sleep mode, applied to various controllers connected to the CAN bus, including:

[0007] Acquire power mode signals, vehicle network status, and high-voltage system status signals;

[0008] When the power mode signal, the vehicle network status, and the high-voltage system status signal meet the corresponding conditions for the vehicle to be in a non-dormant network state, the timer is started.

[0009] When the timer reaches the preset time, fault data recording is triggered, and the fault data includes the fault time and fault cause.

[0010] In one possible implementation, starting the timer when the power mode signal, the vehicle network status, and the high-voltage system status signal meet the corresponding conditions for the vehicle to be in a network non-sleep state includes:

[0011] Based on the power mode signal, detect whether the power mode is OFF;

[0012] When the power mode is OFF, it is detected whether the vehicle network status is in a wake-up state;

[0013] When the vehicle network status is in the wake-up state, the high-voltage system is detected as being in the power-down state based on the high-voltage system status signal.

[0014] When the high-voltage system is powered down, it is determined that the vehicle is in a network non-sleep state, and a timer is started.

[0015] One possible implementation also includes:

[0016] When the power mode is ON, or when the vehicle network status is in a dormant state, or when the high-voltage system is powered on, the corresponding power mode signal, vehicle network status, or high-voltage system status signal is reacquired for corresponding detection.

[0017] In one possible implementation, after the start timer, the following is also included:

[0018] During the timing process, when the high-voltage system is detected to be in a powered-on state, the timing is stopped, the timer is reset, and the corresponding high-voltage system status signal is reacquired. The timer is then checked to see if the high-voltage system corresponding to the new high-voltage system status signal is in a powered-off state.

[0019] In one possible implementation, before triggering fault data recording when the timer reaches a preset time, the method further includes:

[0020] During the timing process, when the high-voltage system is detected to be in a power-off state, the timer is checked to see if the preset time has been reached.

[0021] If the timer fails to reach the preset time and the vehicle network status is detected to be in a dormant state, the timer is stopped, the timer is reset, the vehicle network status is reacquired, and it is checked whether the new vehicle network status is in a wake-up state.

[0022] In one possible implementation, after triggering fault data recording when the timer reaches a preset time, the method further includes:

[0023] The fault data is reported via the CAN bus.

[0024] Secondly, embodiments of the present invention provide a diagnostic device for a vehicle network that does not sleep, the diagnostic device comprising various controllers connected to a CAN bus, including:

[0025] The acquisition module is used to acquire power mode signals, vehicle network status, and high-voltage system status signals.

[0026] The control module is used to start a timer when the power mode signal, the vehicle network status, and the high-voltage system status signal meet the corresponding conditions for the vehicle to be in a network non-sleep state.

[0027] The processing module is used to trigger fault data recording when the timer reaches a preset time. The fault data includes the fault time and fault cause.

[0028] In one possible implementation, the control module is used to:

[0029] Based on the power mode signal, detect whether the power mode is OFF;

[0030] When the power mode is OFF, it is detected whether the vehicle network status is in a wake-up state;

[0031] When the vehicle network status is in the wake-up state, the high-voltage system is detected as being in the power-down state based on the high-voltage system status signal.

[0032] When the high-voltage system is powered down, it is determined that the vehicle is in a network non-sleep state, and a timer is started.

[0033] Thirdly, embodiments of the present invention provide a terminal including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the diagnostic method for non-sleep mode of a vehicle network as described in the first aspect or any possible implementation thereof.

[0034] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the diagnostic method for vehicle network non-sleep as described in the first aspect or any possible implementation thereof.

[0035] This invention provides a diagnostic method, apparatus, vehicle, and storage medium for vehicle network non-sleep mode. By adding a network non-sleep mode diagnostic function to each controller, when the power mode signal, vehicle network status, and high-voltage system status signal meet the corresponding conditions for the vehicle to be in a network non-sleep mode, a timer is started. When the timer reaches a preset time, fault data recording is triggered, thereby quickly identifying the abnormal non-sleep controller and solving the problem of not being able to identify the non-sleep controller in the prior art. This invention can also record the cause of the faulty controller, thereby quickly identifying the cause of the non-sleep mode and facilitating user troubleshooting. Attached Figure Description

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

[0037] Figure 1 This is a flowchart illustrating the implementation of the diagnostic method for vehicle network non-sleep provided in this embodiment of the invention.

[0038] Figure 2 This is a schematic diagram of the connection system of each controller provided in the embodiments of the present invention;

[0039] Figure 3 This is a flowchart illustrating the implementation of a diagnostic method for vehicle network non-sleep mode provided in another embodiment of the present invention;

[0040] Figure 4 This is a schematic diagram of the structure of the vehicle network non-sleep diagnostic device provided in an embodiment of the present invention;

[0041] Figure 5 This is a schematic diagram of the controller provided in an embodiment of the present invention. Detailed Implementation

[0042] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of the invention. However, those skilled in the art will understand that the invention can be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods are omitted so as not to obscure the description of the invention with unnecessary detail.

[0043] To make the objectives, technical solutions, and advantages of the present invention clearer, specific embodiments will be described below in conjunction with the accompanying drawings.

[0044] Figure 1 A flowchart illustrating the implementation of a diagnostic method for vehicle network non-sleep mode provided in this embodiment of the invention is shown below. Figure 2 The diagnostic method for preventing vehicle network sleep is applied to various controllers connected to the CAN bus. The connection system of each controller is that each controller is connected to the vehicle's power system, high voltage system and vehicle network through an on-board gateway. Here, the on-board gateway can realize signal exchange between different controllers and can translate and forward different communication languages.

[0045] In this embodiment, a network sleep failure diagnostic function is added to each controller. This function records the time and cause of the controller's network sleep failure, enabling rapid fault location. Details are as follows:

[0046] Step 101: Obtain the power mode signal, vehicle network status, and high-voltage system status signal.

[0047] The power system controls the vehicle's power mode and feeds back the power mode signal to the CAN bus. The controller obtains the power mode signal from the CAN bus to detect whether the power mode is OFF.

[0048] The controller monitors the vehicle network status in order to detect whether the vehicle network is in a wake-up state.

[0049] The high-voltage system will feed back the high-voltage system status signal to the CAN bus. The controller will obtain the high-voltage system status signal on the CAN bus so as to detect whether the high-voltage system is in a power-off state.

[0050] Optionally, the power mode signal, vehicle network status, and high-voltage system status signal can be acquired at preset intervals to prevent frequent operation from causing battery depletion.

[0051] Step 102: When the vehicle network status, power mode signal, and high-voltage system status signal meet the corresponding conditions for the vehicle to be in a non-dormant network state, start the timer.

[0052] After acquiring the power mode signal, vehicle network status, and high-voltage system status signal, based on the power mode signal, it checks whether the power mode is OFF. If the power mode is OFF, it checks whether the vehicle network status is in a wake-up state. If the vehicle network status is in a wake-up state, based on the high-voltage system status signal, it checks whether the high-voltage system is in a power-down state. If the high-voltage system is in a power-down state, it determines that the vehicle is in a network non-sleep state and starts a timer. See details below. Figure 3 As shown.

[0053] When the power mode is switched from ON to OFF, it indicates that the user wants the vehicle network to go into sleep mode. If the vehicle network is in a wake-up state at this time, meaning it has been awakened from sleep mode, it means that a controller in the vehicle is still sending messages, and this controller may be faulty. It should be noted that when the vehicle switches from ON to OFF, the vehicle network will be in a wake-up state as long as a controller on the bus is sending messages; the vehicle network will only go into sleep mode when no controller is sending messages.

[0054] Before confirming that the vehicle is in a non-sleep network state, it is also necessary to check whether the high-voltage system is powered off. This is to prevent the high-voltage system from being powered on when the vehicle's power supply is off, as normal vehicle functions could cause the network to not be in sleep mode, leading to controller misjudgments. For example, when charging the vehicle with a charging gun, the vehicle's power supply needs to be off, at which point the high-voltage system is powered on. Or, if the driver leaves the vehicle but there is still a living being inside, the high-voltage system is powered on to turn on the air conditioning and prevent the air inside the vehicle from becoming stuffy.

[0055] The controller only starts the timer when the high-voltage system is powered down to ensure that the vehicle controller's failure to enter sleep mode is due to a fault. In this embodiment, a fault in the vehicle controller is only determined when the power mode is OFF, the vehicle network status is in an active state, and the high-voltage system is powered down. In this case, the timer starts and monitors the power mode, vehicle network status, and high-voltage system during the timer. The timer stops when these conditions are not met, preventing incorrect diagnostics.

[0056] See Figure 3 When the power mode is ON, or when the vehicle network status is in a sleep state, or when the high-voltage system is powered on, the corresponding power mode signal, vehicle network status, or high-voltage system status signal is reacquired for corresponding detection.

[0057] In other words, when the power mode is ON, it means that the power mode does not meet the conditions for the vehicle to be in a non-sleep state on the network. Therefore, it is necessary to reacquire the power mode signal and re-detect the newly acquired power mode signal.

[0058] When the vehicle network status is in a dormant state, it means that the vehicle network status does not meet the conditions for the vehicle to be in a non-dormant state. Therefore, it is necessary to reacquire the vehicle network status and re-detect the newly acquired vehicle network status.

[0059] When the high-voltage system is powered on, it indicates that the high-voltage system does not meet the requirement that the vehicle is in a non-sleep state on the network. Therefore, the timer will not start. It is necessary to reacquire the high-voltage system status signal and re-detect the newly acquired high-voltage system status. The timer can only be started after the high-voltage system is powered off.

[0060] Step 103: When the timer reaches the preset time, fault data recording is triggered. The fault data includes the fault time and the cause of the fault.

[0061] The timer can be a positive timer or a countdown timer; in this embodiment, the type of timer is not limited.

[0062] The preset time can be set according to actual needs, such as 50 minutes, 60 minutes, etc., but is not limited in this embodiment.

[0063] During the timer's timing process, it is also necessary to monitor in real time whether the power mode signal, vehicle network status, and high-voltage system status signal meet the corresponding conditions for the vehicle to be in a non-sleep state on the network. If any condition is not met during the timing process, the timer needs to be stopped.

[0064] See Figure 3 During the timing process, when the high-voltage system is detected to be in a powered-on state, the timing is stopped, the timer is reset, and the corresponding high-voltage system status signal is reacquired. The system then checks whether the high-voltage system corresponding to the new high-voltage system status signal is in a powered-off state.

[0065] When the high-voltage system does not meet the conditions, the timer needs to be reset so that when the power mode signal, vehicle network status, and high-voltage system status signal meet the corresponding conditions for the vehicle to be in a non-dormant network state, the timer can be restarted and the timer can start counting correctly again.

[0066] During the timing process, when the high-voltage system is detected to be in a power-off state, the timer is checked to see if the preset time has been reached.

[0067] When the timer has not reached the preset time, and the vehicle network status is detected to be in a sleep state (indicating normal vehicle sleep and no controller malfunction), the timer stops, resets, and reacquires the vehicle network status, checking if the new status indicates the vehicle is in a wake-up state. If the vehicle network status is detected to be awakened again, subsequent steps are executed, as detailed in [link to details]. Figure 3 The process is shown below.

[0068] See Figure 3 When the power mode is OFF, the network non-sleep diagnostic function is enabled so that when the fault controller cannot put the whole vehicle into sleep mode, it can be detected in time and the user can be reminded to perform fault repair in a timely manner.

[0069] When the timer reaches the preset time, after triggering fault data recording, the following steps are also taken: disabling the network non-sleep diagnostic function. Here, the controller can record a maximum of one set of network non-sleep diagnostic data within one ignition cycle. That is to say, after triggering fault data recording, the network non-sleep diagnostic function needs to be disabled. It will be re-enabled after the power mode is switched from ON to OFF to prevent fault data from being recorded repeatedly and wasting storage space.

[0070] It should be noted that fault data is recorded in local storage and can be stored in real time; the data will not be lost when the vehicle's battery is depleted. Users can retrieve fault data from the storage and quickly locate the fault based on the time and cause of the controller's failure to sleep, solving the problem of existing technologies being unable to locate faulty controllers or determine the cause of the fault. This allows for timely repairs and minimizes losses.

[0071] See Figure 2 Multiple controllers in the vehicle are connected via a CAN bus. If the current controller triggers fault data recording, the recorded fault data can be reported to the back-end server via the CAN bus for early warning. In this way, the back-end server can remind the customer to carry out timely maintenance.

[0072] Figure 2 The gateway plays a signal routing role in the vehicle network's non-sleep diagnostic function. The gateway transmits the power mode signal and high voltage status signal to the controller. After receiving the signal, the controller checks whether the power mode is OFF and whether the high voltage system is powered off.

[0073] Existing battery monitoring platforms can only provide background warnings when the battery is low on power, but they cannot determine the cause of the battery depletion or pinpoint the faulty controller causing the depletion. However, with the vehicle network non-sleep diagnostic method provided by this invention, the faulty controller can be identified in a timely manner and fault data can be recorded. After the background warning is issued, repairs can be carried out promptly based on the fault data to prevent the risk of the battery depleting again.

[0074] This invention adds a network non-sleep diagnostic function to each controller. When the controller detects that the power mode signal, vehicle network status, and high-voltage system status signal meet the corresponding conditions for the vehicle to be in a network non-sleep state, a timer is started. When the timer reaches a preset time, fault data recording is triggered. This allows for the rapid identification of the faulty controller causing the network non-sleep state. The recorded fault data can quickly pinpoint the cause of the faulty controller's non-sleep state, facilitating troubleshooting for users.

[0075] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0076] The following are device embodiments of the present invention. For details not described in detail, please refer to the corresponding method embodiments described above.

[0077] Figure 4 A schematic diagram of a diagnostic device for preventing vehicle network sleep mode provided in an embodiment of the present invention is shown. For ease of explanation, only the parts related to the embodiment of the present invention are shown, and are described in detail below:

[0078] like Figure 4 As shown, the diagnostic device for the vehicle network that does not sleep consists of various controllers connected to the CAN bus, including: an acquisition module 41, a control module 42, and a processing module 43.

[0079] Acquisition module 41 is used to acquire power mode signal, vehicle network status and high voltage system status signal;

[0080] Control module 42 is used to start a timer when the power mode signal, vehicle network status and high voltage system status signal meet the corresponding conditions for the vehicle to be in network non-sleep state.

[0081] The processing module 43 is used to trigger fault data recording when the timer reaches the preset time. The fault data includes the fault time and fault cause.

[0082] In one possible implementation, the control module 42 is used for:

[0083] Based on the power mode signal, detect whether the power mode is OFF;

[0084] When the power mode is OFF, check whether the vehicle network status is in a wake-up state.

[0085] When the vehicle network is in a wake-up state, it detects whether the high-voltage system is in a power-down state based on the high-voltage system status signal.

[0086] When the high-voltage system is powered down, the vehicle is confirmed to be in a non-dormant state on the network, and the timer is started.

[0087] In one possible implementation, when the power mode is ON, or when the vehicle network status is in a sleep state, or when the high-voltage system is powered on, the acquisition module 41 reacquires the corresponding power mode signal, vehicle network status, or high-voltage system status signal, and then the control module 42 performs the corresponding detection.

[0088] In one possible implementation, after starting the timer, the control module 42 is also used to stop the timer, reset the timer, and reacquire the corresponding high-voltage system status signal when it detects that the high-voltage system is in a powered-on state during the timer process, and detect whether the high-voltage system corresponding to the new high-voltage system status signal is in a powered-off state.

[0089] In one possible implementation, before the processing module 43 triggers fault data recording when the timer reaches a preset time, the control module 42 is further configured to:

[0090] During the timing process, when the high-voltage system is detected to be in a power-off state, the timer is checked to see if the preset time has been reached.

[0091] If the timer fails to reach the preset time and the vehicle network status is detected to be in a dormant state, the timer is stopped, the timer is reset, the vehicle network status is reacquired, and it is checked whether the new vehicle network status is in a wake-up state.

[0092] In one possible implementation, after the processing module 43 triggers fault data recording when the timer reaches a preset time, it is further configured to:

[0093] The fault data is reported via the CAN bus.

[0094] The aforementioned diagnostic device for vehicle network non-sleep mode adds a network non-sleep mode diagnostic function to each controller. When the control module controller detects that the power mode signal, vehicle network status, and high-voltage system status signal meet the corresponding conditions for the vehicle to be in a network non-sleep mode, a timer is started. When the timer reaches the preset time, the processing module triggers fault data recording, thereby quickly identifying the faulty controller causing the network non-sleep mode. The recorded fault data can quickly pinpoint the cause of the faulty controller's non-sleep mode, facilitating user troubleshooting.

[0095] Figure 5 This is a schematic diagram of a terminal provided in an embodiment of the present invention. Figure 5 As shown, the terminal 5 in this embodiment includes: a processor 50, a memory 51, and a computer program 52 stored in the memory 51 and executable on the processor 50. When the processor 50 executes the computer program 52, it implements the steps in the various vehicle network non-sleep diagnostic method embodiments described above, for example... Figure 1 Steps 101 to 103 are shown. Alternatively, when the processor 50 executes the computer program 52, it implements the functions of each module / unit in the above-described device embodiments, for example... Figure 4 The functions of modules / units 41 to 43 shown.

[0096] For example, the computer program 52 can be divided into one or more modules / units, which are stored in the memory 51 and executed by the processor 50 to complete the present invention. The one or more modules / units can be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program 52 in the terminal 5. For example, the computer program 52 can be divided into... Figure 4 Modules / units 41 to 43 are shown.

[0097] The terminal 5 may include, but is not limited to, a processor 50 and a memory 51. Those skilled in the art will understand that... Figure 5 This is merely an example of terminal 5 and does not constitute a limitation on terminal 5. It may include more or fewer components than shown, or combine certain components, or different components. For example, the terminal may also include input / output devices, network access devices, buses, etc.

[0098] The processor 50 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0099] The memory 51 can be an internal storage unit of the terminal 5, such as a hard disk or memory of the terminal 5. The memory 51 can also be an external storage device of the terminal 5, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the terminal 5. Furthermore, the memory 51 can include both internal storage units and external storage devices of the terminal 5. The memory 51 is used to store the computer program and other programs and data required by the terminal. The memory 51 can also be used to temporarily store data that has been output or will be output.

[0100] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0101] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0102] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0103] In the embodiments provided by this invention, it should be understood that the disclosed devices / terminals and methods can be implemented in other ways. For example, the device / terminal embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0104] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0105] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0106] If the integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the above embodiments of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the above embodiments of the vehicle network non-sleep diagnostic methods. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0107] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A diagnostic method for vehicle network not sleeping, characterized in that, Applied to various controllers connected to the CAN bus, including: Acquire power mode signals, vehicle network status, and high-voltage system status signals; When the power mode signal, the vehicle network status, and the high-voltage system status signal meet the corresponding conditions for the vehicle to be in a non-sleep state, the timer is started; wherein, the corresponding conditions for the non-sleep state include: when the power mode signal is in the OFF position, the vehicle network status is in the wake-up state, and the high-voltage system is in the power-down state. When the timer reaches the preset time, fault data recording is triggered, and the fault data includes the fault time and fault cause; The method further includes: During the timer's timing process, the power mode signal, the vehicle network status, and the high-voltage system status signal are monitored in real time to see if they meet the corresponding conditions for the vehicle to be in a non-sleep network state. If any condition is not met during the timing process, the timer is controlled to stop timing.

2. The diagnostic method for vehicle network not sleeping according to claim 1, characterized in that, When the power mode signal, the vehicle network status, and the high-voltage system status signal meet the corresponding conditions for the vehicle to be in a network non-sleep state, the timer is started, including: Based on the power mode signal, detect whether the power mode is OFF; When the power mode is OFF, it is detected whether the vehicle network status is in a wake-up state; When the vehicle network status is in the wake-up state, the high-voltage system is detected as being in the power-down state based on the high-voltage system status signal. When the high-voltage system is powered down, it is determined that the vehicle is in a network non-sleep state, and a timer is started.

3. The diagnostic method for vehicle network non-sleep according to claim 2, characterized in that, Also includes: When the power mode is ON, or when the vehicle network status is in a dormant state, or when the high-voltage system is powered on, the corresponding power mode signal, vehicle network status, or high-voltage system status signal is reacquired for corresponding detection.

4. The diagnostic method for vehicle network non-dormancy according to claim 2 or 3, characterized in that, Following the start timer, the following is also included: During the timing process, when the high-voltage system is detected to be in a powered-on state, the timing is stopped, the timer is reset, and the corresponding high-voltage system status signal is reacquired. The timer is then checked to see if the high-voltage system corresponding to the new high-voltage system status signal is in a powered-off state.

5. The diagnostic method for vehicle network not sleeping according to claim 4, characterized in that, Before triggering fault data recording when the timer reaches a preset time, the method further includes: During the timing process, when the high-voltage system is detected to be in a power-off state, the timer is checked to see if the preset time has been reached. If the timer fails to reach the preset time and the vehicle network status is detected to be in a dormant state, the timer is stopped, the timer is reset, the vehicle network status is reacquired, and it is checked whether the new vehicle network status is in a wake-up state.

6. The diagnostic method for vehicle network not sleeping according to any one of claims 1-3, characterized in that, After triggering fault data recording when the timer reaches a preset time, the method further includes: The fault data is reported via the CAN bus.

7. A diagnostic device for a vehicle network that does not go into sleep mode, characterized in that, The diagnostic device comprises various controllers connected to the CAN bus, including: The acquisition module is used to acquire power mode signals, vehicle network status, and high-voltage system status signals. The control module is used to start a timer when the power mode signal, the vehicle network status, and the high-voltage system status signal meet the corresponding conditions for the vehicle to be in a non-sleep state; wherein, the corresponding conditions for the non-sleep state include: when the power mode signal is in the OFF position, the vehicle network status is in the wake-up state, and the high-voltage system is in the power-down state. The processing module is used to trigger fault data recording when the timer reaches a preset time. The fault data includes the fault time and fault cause. The control module is also used to detect in real time whether the power mode signal, the vehicle network status and the high-voltage system status signal meet the corresponding conditions for the vehicle to be in a non-sleep state on the network during the timer's timing process. If any condition is not met during the timing process, the timer is controlled to stop timing.

8. The diagnostic device for non-dormant vehicle network according to claim 7, characterized in that, The control module is used for: Based on the power mode signal, detect whether the power mode is OFF; When the power mode is OFF, it is detected whether the vehicle network status is in a wake-up state; When the vehicle network status is in the wake-up state, the high-voltage system is detected as being in the power-down state based on the high-voltage system status signal. When the high-voltage system is powered down, it is determined that the vehicle is in a network non-sleep state, and a timer is started.

9. A vehicle, the vehicle including a controller, the controller including a memory and a processor, the memory for storing a computer program, the processor for calling and running the computer program stored in the memory, characterized in that, When the processor executes the computer program, it implements the steps of the diagnostic method for vehicle network not sleeping as described in any one of claims 1 to 6.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the diagnostic method for vehicle network not sleeping as described in any one of claims 1 to 6.

Images