Fault processing method and device for hard-wired wake-up pin of vehicle control unit

Abstract

The application relates to a fault processing method and device for a hard-wire wake-up pin of a vehicle controller, wherein the method comprises the following steps: detecting a time type of current hard-wire failure of the vehicle controller; identifying actual fault influence of the current hard-wire failure according to the time type, and determining corresponding fault judgment conditions according to the time type; detecting whether the hard-wire wake-up pin of the vehicle controller satisfies the fault judgment conditions, and when it is detected that the fault judgment conditions are satisfied, performing fault processing according to the best processing mode matched according to the actual fault influence. The application diagnoses the hard-wire wake-up pin based on the time of hard-wire failure and the failure influence, thereby confirming the fault of the hard-wire wake-up pin and performing corresponding processing, avoiding the increase of vehicle maintenance time and maintenance cost caused by the fault which does not affect vehicle driving, improving the reliability and humanization level of the vehicle, and improving the driving and riding experience of users.

Description

Technical Field

[0001] This application relates to the field of new energy vehicle control technology, and in particular to a fault handling method and device for the hard-wired wake-up pin of a vehicle controller. Background Technology

[0002] For new energy vehicles, when a user needs to use the vehicle, the vehicle controller is first activated, followed by the motor controller, DC-DC controller, etc., via hard wiring. However, if the hard wiring used for activation malfunctions, the relevant controllers cannot be activated normally, causing the vehicle to be unable to receive high voltage or operate properly. Therefore, for ease of maintenance, the vehicle controller usually detects faults such as short circuits, short-to-ground faults, or open circuits in the activation pins, records the faults, and stores them in the controller as fault codes. Service stations then use diagnostic tools to read the fault codes and perform targeted repairs based on the fault type.

[0003] Currently, the related technology (KR1020210021541) can use a signal comparator to compare the signal output from the output terminal of the integrated circuit chip of the external open circuit diagnostic object with a specified reference voltage to confirm whether there is an open circuit. In addition, the related technology (CN105425766A) can also send a detection command through the host computer, and the signal processing and acquisition module generates a detection signal according to the command of the host computer, sends it to the corresponding input pin of the vehicle controller, collects the detection result signal from the vehicle controller and returns it to the host computer.

[0004] However, the relevant technologies do not consider the impact of faults when diagnosing hard-wired pins of the controller, thus identifying random failures that do not affect the user's vehicle use as faults. This makes the diagnosis too stringent, increases repair time and costs, and the availability of fault detection equipment in actual vehicles is low, which greatly affects the user's driving experience and urgently needs to be addressed. Summary of the Invention

[0005] This application provides a fault handling method and device for the hard-wired wake-up pin of a vehicle controller, in order to solve the problems that related technologies do not consider the impact of faults when diagnosing hard-wired pins of the controller, thus identifying random failures that do not affect the user's vehicle use as faults, making the diagnosis too stringent, increasing maintenance time and cost, and the low availability of fault detection equipment in actual vehicles.

[0006] The first aspect of this application provides a fault handling method for a hard-wire wake-up pin of a vehicle controller, comprising the following steps: detecting the timing type of the current hard-wire failure of the vehicle controller; identifying the actual fault impact of the current hard-wire failure according to the timing type, and determining the corresponding fault judgment condition according to the timing type; and detecting whether the hard-wire wake-up pin of the vehicle controller meets the fault judgment condition, and when the fault judgment condition is detected to be met, performing fault handling according to the optimal handling method matching the actual fault impact.

[0007] Based on the above technical means, this application embodiment diagnoses the hard-wire wake-up pin based on the timing and impact of hard-wire failure, thereby confirming the fault type of the hard-wire wake-up pin and performing corresponding processing, avoiding the increase in vehicle repair time and repair costs due to faults that do not affect vehicle operation, improving the reliability and humanization level of the vehicle, and improving the user's driving experience.

[0008] Optionally, in one embodiment of this application, the timing type for detecting the current hardwire failure of the vehicle controller includes: when the vehicle controller is woken up and completes initialization and pulls the hardwire wake-up pin of the relevant controller high, the timing type is a short-ground and open-circuit timing type; when the vehicle is powered down and the vehicle controller sends a sleep request to the relevant controller through the CAN network while pulling the hardwire wake-up pin low, the timing type is a short-power timing type.

[0009] Based on the above technical means, the embodiments of this application combine the timing of hard-wired wake-up pin failure to provide a basis for subsequent fault confirmation and handling, thereby reducing false alarms and improving the reliability of subsequent fault judgment.

[0010] Optionally, in one embodiment of this application, identifying the actual fault impact of the current hardwire failure based on the timing type includes: when the timing type is the short-ground and open-circuit timing type, determining that the actual fault impact is that the hardwire wake-up pin cannot normally hardwire wake up the relevant controller; when the timing type is the short power supply timing type, determining that the actual fault impact is that the relevant controller cannot enter sleep mode and the overall vehicle dark current increases.

[0011] Based on the above technical means, the embodiments of this application analyze and combine the impact of each fault type in different scenarios, and random failures that have no impact on the user's vehicle use are no longer identified as faults, thereby avoiding overdiagnosis, improving the user's driving experience, and optimizing the diagnostic process from a software strategy perspective. This does not increase hardware costs, reduces false alarms, is easy to implement, and greatly improves the reliability of fault determination.

[0012] Optionally, in one embodiment of this application, the fault handling according to the optimal handling method matching the actual fault impact includes: generating diagnostic fault information based on the actual fault impact of the short ground and open circuit, and providing acoustic and / or optical reminders to the user; generating the diagnostic fault information based on the actual fault impact of the short power supply, and recording the fault information after fault confirmation to facilitate maintenance personnel in troubleshooting the fault.

[0013] Based on the above-mentioned technical means, this application embodiment identifies random failures affecting users' vehicle use as faults, records fault codes, and reminds users, thereby not only reducing the workload of after-sales maintenance personnel and reducing maintenance time or costs, but also improving the safety and user-friendliness of the vehicle.

[0014] Optionally, in one embodiment of this application, determining the corresponding fault judgment condition according to the timing type includes: when the timing type is the short-ground or open-circuit timing type, the short-ground and open-circuit fault judgment condition is that if the hard-wire wake-up pin is detected to be short-ground or open-circuit, and the vehicle controller does not receive a CAN message from the relevant controller after hard-wire wake-up, both conditions are met simultaneously and the duration exceeds a first preset period; if the CAN message from the relevant controller is received normally, then the short-ground or open-circuit fault diagnosis is not performed on the wake-up pin; when the timing type is the short-power timing type, the short-power fault judgment condition is that the hard-wire wake-up pin is detected to be short-power, and the vehicle controller continuously receives CAN messages from the relevant controller after the hard-wire wake-up pin is pulled low, both conditions are met simultaneously and the duration exceeds a second preset period.

[0015] Based on the above technical means, the embodiments of this application effectively improve the accuracy of fault judgment, reduce the probability of false fault judgment, and improve the reliability and safety of the vehicle by setting reasonable fault judgment conditions.

[0016] A second aspect of this application provides a fault handling device for a hard-wire wake-up pin of a vehicle controller, comprising: a detection module for detecting the timing type of a current hard-wire failure in the vehicle controller; an identification module for identifying the actual fault impact of the current hard-wire failure based on the timing type, and determining corresponding fault judgment conditions based on the timing type; and a processing module for detecting whether the hard-wire wake-up pin of the vehicle controller meets the fault judgment conditions, and, when the fault judgment conditions are met, performing fault handling according to the optimal processing method matching the actual fault impact.

[0017] Optionally, in one embodiment of this application, the detection module includes: a first timing unit, configured to, when the vehicle controller is woken up and completes initialization and pulls the hard-wire wake-up pin of the relevant controller high, the timing type is a short-ground and open-circuit timing type; and a second timing unit, configured to, when the vehicle is powered down and the vehicle controller sends a sleep request to the relevant controller via the CAN network, pulls the hard-wire wake-up pin low, the timing type is a short-power timing type.

[0018] Optionally, in one embodiment of this application, the identification module includes: a first determination unit, configured to determine that when the timing type is the short-ground and open-circuit timing type, the actual fault impact is that the hard-wire wake-up pin cannot normally hard-wire wake up the relevant controller; and a second determination unit, configured to determine that when the timing type is the short-power timing type, the actual fault impact is that the relevant controller cannot enter sleep mode and the overall vehicle dark current increases.

[0019] Optionally, in one embodiment of this application, the processing module includes: a reminder unit, used to generate diagnostic fault information based on the actual impact of the short-circuit and open-circuit faults, and to provide acoustic and / or optical reminders to the user; and a sleep unit, used to generate the diagnostic fault information based on the actual impact of the short power supply fault, and to record the fault information after fault confirmation, so as to facilitate maintenance personnel in troubleshooting the fault.

[0020] Optionally, in one embodiment of this application, the identification module includes: a first condition unit, configured to, when the timing type is the short-ground or open-circuit timing type, the short-ground or open-circuit fault judgment condition is that if the hard-wire wake-up pin is detected to be short-ground or open-circuit, and the vehicle controller does not receive a CAN message from the relevant controller after hard-wire wake-up, both conditions are met simultaneously and the duration exceeds a first preset period; if the CAN message from the relevant controller is received normally, then the short-ground or open-circuit fault diagnosis is not performed on the wake-up pin; a second condition unit, configured to, when the timing type is the short-power timing type, the short-power fault judgment condition is that the hard-wire wake-up pin is detected to be short-power, and the vehicle controller continuously receives a CAN message from the relevant controller after the hard-wire wake-up pin is pulled low, both conditions are met simultaneously and the duration exceeds a second preset period.

[0021] A third aspect of this application provides a vehicle, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the program to implement the fault handling method for the hard-wired wake-up pin of the vehicle controller as described in the above embodiments.

[0022] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described fault handling method for the hard-wired wake-up pin of a vehicle controller.

[0023] Therefore, the embodiments of this application have the following beneficial effects:

[0024] (1) The embodiments of this application diagnose the hard wire wake-up pin based on the timing and impact of hard wire failure, thereby confirming the fault type of the hard wire wake-up pin and handling it accordingly, avoiding the increase in vehicle maintenance time and maintenance cost due to faults that do not affect vehicle operation, improving the reliability and humanization level of the vehicle, and improving the user's driving experience.

[0025] (2) The embodiments of this application combine the timing of the failure of the hard-wire wake-up pin to provide a basis for the confirmation and handling of subsequent faults, thereby reducing false alarms and improving the reliability of subsequent fault judgment.

[0026] (3) The embodiments of this application analyze and combine the impact of each fault type in different scenarios, and random failures that have no impact on the user's vehicle use are no longer identified as faults, thereby avoiding overdiagnosis, improving the user's driving experience, and optimizing the diagnostic process from the software strategy, without increasing hardware costs, reducing false alarms, and being easy to implement, which greatly improves the reliability of fault determination.

[0027] (4) In this embodiment of the application, random failures that affect the user’s vehicle use are identified as faults, fault codes are recorded, and the user is reminded, thereby not only reducing the workload of after-sales maintenance personnel, reducing maintenance time or maintenance costs, but also improving the safety and humanization level of the vehicle.

[0028] (5) By setting reasonable fault judgment conditions, the embodiments of this application effectively improve the accuracy of fault judgment, reduce the probability of fault misjudgment, and improve the reliability and safety of the vehicle.

[0029] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0030] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0031] Figure 1 This is a flowchart illustrating a fault handling method for the hard-wired wake-up pin of a vehicle controller according to an embodiment of this application.

[0032] Figure 2A schematic diagram of the electrical connection between a vehicle controller and related controllers is provided as an embodiment of this application;

[0033] Figure 3 A schematic diagram of the low-voltage power-on and power-off process of a vehicle is provided as an embodiment of this application;

[0034] Figure 4 A schematic diagram of a fault diagnosis process for a hard-wired wake-up pin of a vehicle controller, provided as an embodiment of this application;

[0035] Figure 5 A schematic diagram of a fault diagnosis process for a hard-wired wake-up pin short power supply of a vehicle controller is provided as an embodiment of this application;

[0036] Figure 6 This is an example diagram of a fault handling device for the hard-wired wake-up pin of a vehicle controller according to an embodiment of this application;

[0037] Figure 7 This is a schematic diagram of the vehicle structure provided in an embodiment of this application.

[0038] Among them, 10-fault handling device for hard-wired wake-up pin of vehicle controller, 100-detection module, 200-identification module, 300-processing module, 701-memory, 702-processor, and 703-communication interface. Detailed Implementation

[0039] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0040] The following describes a fault handling method and apparatus for a hard-wired wake-up pin of a vehicle controller according to embodiments of this application, with reference to the accompanying drawings. Addressing the problems mentioned in the background section, this application provides a fault handling method for a hard-wired wake-up pin of a vehicle controller. In this method, the timing type of the current hard-wired failure of the vehicle controller is detected; the actual fault impact of the current hard-wired failure is identified based on the timing type, and corresponding fault judgment conditions are determined based on the timing type; it is detected whether the hard-wired wake-up pin of the vehicle controller meets the fault judgment conditions, and when the fault judgment conditions are met, fault handling is performed according to the optimal handling method matching the actual fault impact. This application diagnoses the hard-wired wake-up pin based on the timing and impact of the hard-wired failure, thereby confirming the fault type of the hard-wired wake-up pin and performing corresponding processing. This avoids increased vehicle repair time and costs due to faults that do not affect vehicle operation, improves vehicle reliability and user-friendliness, and enhances the user's driving experience. This solves the problems of related technologies not considering the impact of faults when diagnosing controller hard-wired pins, thus identifying random failures that do not affect the user's vehicle use as faults, making the diagnosis too stringent, increasing maintenance time and costs, and the low availability of fault detection equipment in actual vehicles.

[0041] Specifically, Figure 1 This is a flowchart illustrating a fault handling method for the hard-wired wake-up pin of a vehicle controller, as provided in an embodiment of this application.

[0042] like Figure 1 As shown, the troubleshooting method for the hard-wired wake-up pin of the vehicle controller includes the following steps:

[0043] In step S101, the timing type of the current hardwire failure of the vehicle controller is detected.

[0044] The embodiments of this application can first detect the timing type of the current hard wire failure of the vehicle controller based on the electrical connection principle of the vehicle controller and related controllers and the low-voltage power-on and power-off process of the vehicle, and identify the specific scenario of hard wire pin failure.

[0045] Figure 2 This is a schematic diagram of the electrical connections between the vehicle controller and related controllers, such as... Figure 2As shown, the hardwired pin P10 of the Vehicle Control Unit (VCU) is connected to the Induction Unit (IPU), the hardwired pin P11 is connected to the DC-DC controller, and the hardwired pin P12 is connected to the Engine Management System (EMS). When the VCU hardwired pin is pulled high, the connected controller can be woken up. Among them, the hardwired pins P20 and P21 of the Vehicle Control Unit are CAN (Controller Area Network) buses. The VCU, IPU, DC-DC and EMS are in the same network segment and connected to the same CAN bus.

[0046] Figure 3 This is a schematic diagram of the low-voltage power-on and power-off process of the entire vehicle, as shown below. Figure 3 As shown, the specific process of powering on and off the vehicle's low voltage in the embodiments of this application is as follows:

[0047] S301: When the vehicle receives a power-on request, the VCU is activated;

[0048] S302: After the vehicle controller completes initialization, the relevant controller's hard-wire wake-up pin is pulled high. Once the wake-up pin is pulled high, the relevant controller can be woken up. After the relevant controller is woken up and completes initialization, it sends a CAN message to communicate with the vehicle controller to jointly implement the relevant functions of the vehicle.

[0049] S303: When the vehicle has a power-down request, the vehicle first performs high-voltage power-down, and after the high-voltage power-down is completed, it enters the low-voltage power-down stage. In the low-voltage power-down stage, the vehicle controller sends a sleep request to the relevant controller via CAN, and at the same time pulls the wake-up hardwire pin low.

[0050] S304: When the relevant controller detects that the wake-up hardwire pin is pulled low and receives a sleep request sent by the vehicle controller via CAN, it closes CAN communication and enters sleep mode; after the vehicle controller sends the sleep request for a period of time, it closes CAN communication and enters sleep mode.

[0051] Therefore, the embodiments of this application, based on the electrical connection principle between the vehicle controller and related controllers and the low-voltage power-on and power-off process of the vehicle, provide reliable theoretical support for detecting the timing type of current hardwire failure of the vehicle controller.

[0052] Optionally, in one embodiment of this application, the timing type for detecting the current hardwire failure of the vehicle controller includes: when the vehicle controller is woken up and completes initialization and pulls the hardwire wake-up pin of the relevant controller high, the timing type is short ground and open circuit; when the vehicle is powered down and the vehicle controller sends a sleep request to the relevant controller through the CAN network while pulling the hardwire wake-up pin low, the timing type is short power.

[0053] It should be noted that, in the embodiments of this application, after the VCU is woken up and completes initialization and pulls the wake-up hardwire pin of the relevant controller high, the VCU begins to determine whether the hardwire wake-up pin is shorted to ground or open-circuited; when the vehicle is powered down, the VCU sends a sleep request to the relevant controller via CAN and at the same time pulls the wake-up hardwire low. After the VCU sends a sleep request via CAN and hardwire, the VCU begins to determine whether there is a short power supply fault.

[0054] Therefore, the embodiments of this application, by combining the timing of hard-wired wake-up pin failure, provide a corresponding basis for subsequent fault confirmation and handling, thereby reducing false alarms and improving the reliability of subsequent fault judgment.

[0055] In step S102, the actual fault impact of the current hard wire failure is identified according to the timing type, and the corresponding fault judgment conditions are determined according to the timing type.

[0056] After detecting the current hardwire failure time type of the vehicle controller, the embodiments of this application can further analyze the impact on the vehicle system when the hardwire wake-up pin fails in the above-mentioned specific time type, so as to further improve the rationality and reliability of hardwire wake-up pin fault judgment.

[0057] Optionally, in one embodiment of this application, identifying the actual fault impact of the current hardwire failure based on the timing type includes: when the timing type is short ground and open circuit, determining that the actual fault impact is that the hardwire wake-up pin cannot normally wake up the relevant controller; when the timing type is short power supply, determining that the actual fault impact is that the relevant controller cannot enter sleep mode and the dark current of the whole vehicle increases.

[0058] It should be noted that, in the embodiments of this application, the specific actual impact of a short-ground fault is as follows:

[0059] 1. When the VCU is powered on and the hard-wire wake-up pin is pulled high, the above timing type is a short-ground timing type. At this time, if there is a short-ground fault in the hard-wire wake-up line, it will not affect the whole vehicle system. The relevant controller will enter the sleep state only when it receives the CAN sleep request and the hard wire is pulled low.

[0060] 2. If there is a short-to-ground fault in the hard-wire wake-up line before the VCU is powered on and the hard-wire wake-up pin is pulled high, the relevant controllers will not be able to be woken up normally after the hard-wire wake-up pin is pulled high.

[0061] 3. When the VCU is powered down and pulls the hard-wire wake-up pin low, if there is a short-to-ground fault in the hard-wire wake-up line, it will not affect the entire system.

[0062] The impact of an open-circuit fault is as follows:

[0063] 1. Before the VCU powers on and pulls the hard-wire wake-up pin high, there is an open circuit fault in the hard-wire wake-up circuit. Failure of this scenario will cause the relevant controllers to fail to be hard-wired woken up normally after the hard-wire wake-up pin is pulled high.

[0064] 2. When the VCU is powered on and the hard-wire wake-up pin is pulled high, there is an open circuit fault in the hard-wire wake-up line. This failure has no impact on the system. The relevant controller will enter the sleep state only when it receives both the CAN sleep request and the hard wire is pulled low.

[0065] 3. When the VCU is powered down and pulls the hard-wire wake-up pin low, there is an open circuit fault in the hard-wire wake-up line. This scenario has no impact on the system.

[0066] The impact of a short-power supply failure is as follows:

[0067] 1. Before the VCU powers on and pulls the hard-wire wake-up pin high, there is a short power supply fault in the hard-wire wake-up line. This failure will not affect the system, and the relevant controllers will power on normally.

[0068] 2. When the VCU is powered on and pulls the hard-wire wake-up pin high, there is a short power supply fault in the hard-wire wake-up circuit. This failure has no impact on the system, and the vehicle controller cannot identify whether the external line is shorted to the power supply.

[0069] 3. When the VCU is powered down and pulls the hard-wire wake-up pin low, there is a short power supply fault in the hard-wire wake-up circuit. In this scenario, the relevant controller cannot enter sleep mode, which will result in a large dark current in the whole vehicle and increase the risk of the small battery being drained when the vehicle is idle.

[0070] Therefore, the embodiments of this application analyze and combine the impact of each fault type in different scenarios, and random failures that have no impact on the user's vehicle use are no longer identified as faults, thereby avoiding overdiagnosis, improving the user's driving experience, optimizing the diagnostic process from a software strategy perspective, without increasing hardware costs, reducing false alarms, being easy to implement, and greatly improving the reliability of fault determination.

[0071] Optionally, in one embodiment of this application, the corresponding fault judgment condition is determined according to the timing type, including: when the timing type is short ground or open circuit, the short ground and open circuit fault judgment condition is that if a short ground or open circuit is detected on the hard-wire wake-up pin, and the vehicle controller does not receive a CAN message from the relevant controller after hard-wire wake-up, both conditions are met simultaneously and the duration exceeds a first preset period. If a CAN message from the relevant controller is received normally, then no short ground or open circuit fault diagnosis is performed on the wake-up pin; when the timing type is short power, the short power fault judgment condition is that a short power is detected on the hard-wire wake-up pin, and the vehicle controller continuously receives CAN messages from the relevant controller after the hard-wire wake-up pin is pulled low, both conditions are met simultaneously and the duration exceeds a second preset period.

[0072] Specifically, in the embodiments of this application, after the VCU is woken up, completes initialization, and pulls the wake-up hardwire pin of the relevant controller high, if the timing type is a short-ground timing type, the VCU can determine whether the hardwire wake-up pin is short-grounded by the following conditions:

[0073] 1. Hard-wire wake-up pin short ground;

[0074] 2. After the VCU hard-wires wakes up the relevant controller, it never receives a CAN message from the relevant controller.

[0075] When all the above conditions are met and continue for 80 cycles (initial value, to be calibrated), the VCU can determine that there is a short-to-ground fault in the current hard-wired wake-up pin.

[0076] After the VCU is woken up, completes initialization, and pulls the wake-up hardwire pin of the relevant controller high, if the timing type is open-circuit timing, the VCU can determine whether there is an open-circuit fault on the hardwire wake-up pin through the following conditions:

[0077] 1. Hard-wire wake-up pin short ground;

[0078] 2. After the VCU hard-wires wakes up the relevant controller, it never receives a CAN message from the relevant controller.

[0079] When all the above conditions are met and continue for 80 cycles (initial value, to be calibrated), the VCU can determine that there is an open circuit fault in the current hard-wired wake-up pin.

[0080] When the vehicle is powered down, the VCU sends a sleep request to the relevant controller via CAN, and simultaneously pulls the wake-up hardwire low. When the VCU sends the sleep request via CAN and the hardwire, and the timing type is a short power timing type, the VCU can determine whether there is a short power fault on the hardwire wake-up pin by using the following conditions:

[0081] 1. Short the power supply to the wake-up pin using a hard wire;

[0082] 2. After the VCU hard-wired wake-up pin is pulled low, it continuously receives CAN messages from the relevant controller.

[0083] When all of the following conditions are met and continue for 10 cycles (initial value, to be calibrated), the VCU determines that there is a short power supply fault on the current hard-wired wake-up pin.

[0084] Therefore, the embodiments of this application effectively improve the accuracy of fault determination, reduce the probability of false fault determination, and improve the reliability and safety of the vehicle by setting reasonable fault judgment conditions.

[0085] In step S103, it is detected whether the hard-wired wake-up pin of the vehicle controller meets the fault judgment conditions, and when the fault judgment conditions are met, the fault is handled according to the best handling method matching the actual fault impact.

[0086] Furthermore, embodiments of this application can also detect whether the hard-wired wake-up pin of the vehicle controller meets the above-mentioned fault judgment conditions, and, in combination with the actual impact of the hard-wired wake-up pin fault, handle the fault accordingly and provide corresponding reminders to the user.

[0087] Optionally, in one embodiment of this application, fault handling is performed according to the optimal handling method matching the actual fault impact, including: generating diagnostic fault information based on the actual fault impact of short ground and open circuit, and providing acoustic and / or optical reminders to the user; generating diagnostic fault information based on the actual fault impact of short power supply, and recording the fault information after fault confirmation to facilitate troubleshooting by maintenance personnel.

[0088] It should be noted that, in the embodiments of this application, when the VCU confirms a short-circuit or open-circuit fault, the VCU records a DTC (Diagnostic Trouble Code) and requests the instrument panel to illuminate the red indicator light of the vehicle system fault and display the text "Vehicle system fault, please contact the service station for repair" via CAN. At the same time, related voice prompts can be given. After the VCU hard-wires the relevant controller, if the VCU receives the CAN message of the relevant controller normally, it will no longer perform open-circuit fault diagnosis on the hard-wired wake-up pin.

[0089] Once the VCU confirms a short power supply fault, it records a DTC. After the VCU sends a sleep request via CAN and hardwire, it waits for 200 cycles (initial value, to be calibrated) before entering sleep mode. For short power supply fault diagnosis, the focus is on the period before and after the VCU hardwires wakes up the relevant controllers. During this period, the short power supply has no impact on the system, and this scenario is not diagnosed.

[0090] Therefore, the embodiments of this application, by identifying random failures affecting the user's vehicle use as faults, recording fault codes, and reminding the user, not only reduce the workload of after-sales maintenance personnel and reduce maintenance time or costs, but also improve the safety and user-friendliness of the vehicle.

[0091] The following description, in conjunction with the accompanying drawings, explains the execution process of the fault handling method for the hard-wired wake-up pin of the vehicle controller in this application.

[0092] Figure 4 A schematic diagram illustrating the diagnostic process for short-to-ground or open-circuit faults in the hardwired wake-up pin of the vehicle controller, as follows: Figure 4 As shown, the fault diagnosis process for the hard-wired wake-up pin of the vehicle controller in this application, including short-circuit or open-circuit faults, is as follows:

[0093] S401: After the VCU wake-up initialization is complete, pull the relevant controller hard-wired wake-up pin high;

[0094] S402: After the VCU is woken up by the relevant controller through the influence request, it begins to diagnose short-ground or open-circuit faults;

[0095] S403: Determine whether the hard-wire wake-up pin is shorted to ground or open-circuited, and whether the CAN message of the relevant controller has never been received. If both of the above conditions are met and continue for a certain period of time, then proceed to S404; otherwise, proceed to S405.

[0096] S404: The VCU confirms a short or open circuit fault in the hard-wire wake-up pin, records the fault code, and requests the instrument panel to illuminate and display a text message.

[0097] S405: Hard-wire wake-up pin short ground or open circuit fault diagnosis completed.

[0098] Figure 5 This is a schematic diagram illustrating the fault diagnosis process for a short power supply to the hard-wired wake-up pin of the vehicle controller. Figure 5 As shown, the fault diagnosis process for the hard-wired wake-up pin short power supply of the vehicle controller in this application is as follows:

[0099] S501: When the vehicle is powered off, the VCU sends a sleep request through the CAN-related controller and pulls the wake-up hardline low.

[0100] S502: After the VCU requests the relevant controller to go to sleep via CAN and hardwire, it begins to determine the short power supply fault.

[0101] S503: Determine if there is a short power supply to the hard-wired wake-up pin and if CAN messages from the relevant controller are continuously received. If both conditions are met and last for a certain period of time, proceed to S504; otherwise, proceed to S505.

[0102] S504: VCU confirms a power failure in the hard-wired wake-up pin and records the fault code;

[0103] S505: After the VCU short power supply fault diagnosis time window ends, it enters sleep mode.

[0104] The fault handling method for the hard-wire wake-up pin of the vehicle controller proposed in this application involves detecting the timing type of the current hard-wire failure in the vehicle controller; identifying the actual fault impact of the current hard-wire failure based on the timing type; determining the corresponding fault judgment conditions based on the timing type; detecting whether the hard-wire wake-up pin of the vehicle controller meets the fault judgment conditions; and, when the fault judgment conditions are met, performing fault handling according to the optimal handling method matching the actual fault impact. This application diagnoses the hard-wire wake-up pin based on the timing and impact of hard-wire failure, thereby confirming the fault type of the hard-wire wake-up pin and performing corresponding handling. This avoids increased vehicle repair time and costs due to faults that do not affect vehicle operation, improves vehicle reliability and user-friendliness, and enhances the user's driving experience.

[0105] Secondly, with reference to the accompanying drawings, a fault handling device for the hard-wired wake-up pin of the vehicle controller according to an embodiment of this application is described.

[0106] Figure 6 This is a block diagram of a fault handling device for the hard-wired wake-up pin of the vehicle controller according to an embodiment of this application.

[0107] like Figure 6 As shown, the fault handling device 10 for the hard-wired wake-up pin of the vehicle controller includes: a detection module 100, an identification module 200, and a processing module 300.

[0108] The detection module 100 is used to detect the timing and type of current hardwire failure in the vehicle controller.

[0109] The identification module 200 is used to identify the actual fault impact of the current hard wire failure according to the timing type, and to determine the corresponding fault judgment conditions according to the timing type.

[0110] The processing module 300 is used to detect whether the hard-wired wake-up pin of the vehicle controller meets the fault judgment conditions, and when the fault judgment conditions are detected, it performs fault handling according to the best handling method matching the actual fault impact.

[0111] Optionally, in one embodiment of this application, the detection module 100 includes: a first timing unit and a second timing unit.

[0112] The first timing unit is used when the vehicle controller is woken up, completes initialization, and pulls the hard-wire wake-up pin of the relevant controller high, and the timing type is either short-ground or open-circuit.

[0113] The second timing unit is used to pull the hard-wire wake-up pin low when the vehicle is powered down and the vehicle controller sends a sleep request to the relevant controller through the CAN network. The timing type is the short power supply timing type.

[0114] Optionally, in one embodiment of this application, the identification module 200 includes: a first determination unit and a second determination unit.

[0115] The first determination unit is used to determine that the actual fault impact is that the hard-wire wake-up pin cannot properly hard-wire wake up the relevant controller when the timing type is short ground and open circuit.

[0116] The second determination unit is used to determine, when the timing type is a short power supply, that the actual fault impact is that the relevant controller cannot enter sleep mode and the dark current of the whole vehicle increases.

[0117] Optionally, in one embodiment of this application, the processing module 300 includes: a reminder unit and a sleep unit.

[0118] The reminder unit is used to generate diagnostic fault information based on the actual impact of short-circuit and open-circuit faults, and to provide acoustic and / or optical reminders to the user.

[0119] The hibernation unit is used to generate diagnostic fault information based on the actual impact of short power supply faults. After the fault is confirmed, the fault information is recorded to facilitate troubleshooting by maintenance personnel.

[0120] Optionally, in one embodiment of this application, the identification module 200 includes: a first condition unit and a second condition unit.

[0121] The first condition unit is used to determine the short ground or open circuit fault condition when the timing type is short ground or open circuit. If a short ground or open circuit is detected on the hard-wire wake-up pin, and the vehicle controller does not receive a CAN message from the relevant controller after hard-wire wake-up, both conditions are met at the same time and the duration exceeds the first preset period. If a CAN message from the relevant controller is received normally, then the short ground or open circuit fault diagnosis of the wake-up pin is not performed.

[0122] The second condition unit is used to determine the short power supply fault condition when the timing type is short power supply. The condition is that a short power supply is detected on the hard-wire wake-up pin, and the vehicle controller continuously receives CAN messages from the relevant controller after the hard-wire wake-up pin is pulled low. Both conditions are met at the same time and the duration exceeds the second preset period.

[0123] It should be noted that the explanation of the above-mentioned method for handling faults in the hard-wired wake-up pin of the vehicle controller also applies to the fault handling device for the hard-wired wake-up pin of the vehicle controller in this embodiment, and will not be repeated here.

[0124] The fault handling device for the hard-wire wake-up pin of the vehicle controller proposed in this application detects the timing type of the current hard-wire failure of the vehicle controller; identifies the actual fault impact of the current hard-wire failure based on the timing type, and determines the corresponding fault judgment conditions based on the timing type; detects whether the hard-wire wake-up pin of the vehicle controller meets the fault judgment conditions, and when the fault judgment conditions are detected, performs fault handling according to the optimal handling method matching the actual fault impact. This application diagnoses the hard-wire wake-up pin based on the timing and impact of hard-wire failure, thereby confirming the fault type of the hard-wire wake-up pin and performing corresponding processing, avoiding increased vehicle repair time and costs due to faults that do not affect vehicle operation, improving vehicle reliability and user-friendliness, and enhancing the user's driving experience.

[0125] Figure 7 A schematic diagram of the structure of a vehicle provided in an embodiment of this application. The vehicle may include:

[0126] The memory 701, the processor 702, and the computer program stored on the memory 701 and executable on the processor 702.

[0127] When the processor 702 executes the program, it implements the fault handling method for the hard-wired wake-up pin of the vehicle controller provided in the above embodiments.

[0128] Furthermore, the vehicle also includes:

[0129] Communication interface 703 is used for communication between memory 701 and processor 702.

[0130] The memory 701 is used to store computer programs that can run on the processor 702.

[0131] The memory 701 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0132] If the memory 701, processor 702, and communication interface 703 are implemented independently, then the communication interface 703, memory 701, and processor 702 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 7 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0133] Optionally, in a specific implementation, if the memory 701, processor 702, and communication interface 703 are integrated on a single chip, then the memory 701, processor 702, and communication interface 703 can communicate with each other through an internal interface.

[0134] The processor 702 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0135] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described fault handling method for the hard-wired wake-up pin of the vehicle controller.

[0136] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0137] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0138] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0139] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0140] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0141] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0142] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0143] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A fault handling method for the hard-wired wake-up pin of a vehicle controller, characterized in that, Includes the following steps: Detect the type of current hardwire failure in the vehicle controller; Identify the actual fault impact of the current hardwire failure based on the timing type, and determine the corresponding fault judgment conditions based on the timing type; as well as The system detects whether the hard-wired wake-up pin of the vehicle controller meets the fault judgment condition, and when the fault judgment condition is met, it performs fault handling according to the optimal handling method matching the actual fault impact. The types of times when the current hardwire failure of the vehicle controller is detected include: When the vehicle controller is woken up, completes initialization, and pulls the hard-wire wake-up pin of the relevant controller high, the timing type is either short-ground or open-circuit. When the vehicle is powered down and the vehicle controller sends a sleep request to the relevant controller via the CAN network, and at the same time pulls the hard-wire wake-up pin low, the timing type is the short power timing type. The step of determining the corresponding fault judgment condition based on the timing type includes: When the timing type is the short ground or open circuit timing type, the short ground and open circuit fault judgment condition is that if the hard-wire wake-up pin is detected to be short ground or open circuit, and the vehicle controller does not receive the CAN message of the relevant controller after hard-wire wake-up of the relevant controller, both conditions are met at the same time and the duration exceeds the first preset period. If the CAN message of the relevant controller is received normally, then the short ground or open circuit fault diagnosis is not performed on the wake-up pin. When the timing type is the short power supply timing type, the short power supply fault judgment condition is that the hard-wire wake-up pin is detected as short power, and the vehicle controller continuously receives CAN messages from the relevant controller after the hard-wire wake-up pin is pulled low, and both conditions are met at the same time and the duration exceeds the second preset period.

2. The method according to claim 1, characterized in that, The step of identifying the actual fault impact of the current hardwire failure based on the timing type includes: When the timing type is the short-ground and open-circuit timing type, it is determined that the actual fault impact is that the hard-wired wake-up pin cannot normally hard-wire wake up the relevant controller; When the timing type is the short power supply timing type, the actual fault impact is determined to be that the relevant controller cannot enter sleep mode and the overall vehicle dark current increases.

3. The method according to claim 2, characterized in that, The fault handling according to the optimal handling method matching the actual fault impact includes: Based on the actual impact of the short-ground and open-circuit faults, diagnostic fault information is generated, and acoustic and / or optical alerts are provided to the user. Based on the actual impact of the short power supply failure, the diagnostic fault information is generated. After the fault is confirmed, the fault information is recorded to facilitate maintenance personnel in troubleshooting the fault.

4. A fault handling device for the hard-wired wake-up pin of a vehicle controller, characterized in that, include: The detection module is used to detect the timing and type of current hardwire failure in the vehicle controller. The identification module is used to identify the actual fault impact of the current hard wire failure according to the timing type, and to determine the corresponding fault judgment conditions according to the timing type. as well as The processing module is used to detect whether the hard-wired wake-up pin of the vehicle controller meets the fault judgment condition, and when the fault judgment condition is detected, to perform fault processing according to the optimal processing method matching the actual fault impact. The detection module includes: The first timing unit is used when the vehicle controller is woken up, completes initialization, and pulls the hard-wire wake-up pin of the relevant controller high, and the timing type is a short-ground and open-circuit timing type. The second timing unit is used to pull the hard-wired wake-up pin low when the vehicle is powered down and the vehicle controller sends a sleep request to the relevant controller through the CAN network. The timing type is a short power supply timing type. The identification module includes: The first condition unit is configured to, when the timing type is the short ground or open circuit timing type, determine the short ground or open circuit fault condition as follows: if the hard-wire wake-up pin is detected to be short ground or open circuit, and the vehicle controller does not receive a CAN message from the relevant controller after hard-wire wake-up of the relevant controller, and both conditions are met simultaneously and the duration exceeds the first preset period, then if the CAN message from the relevant controller is received normally, the short ground or open circuit fault diagnosis is not performed on the wake-up pin. The second condition unit is used to determine the short power supply fault condition when the timing type is the short power supply timing type. The condition is that the short power supply is detected when the hard-wire wake-up pin is short-powered, and the vehicle controller continuously receives CAN messages from the relevant controller after the hard-wire wake-up pin is pulled low. Both conditions are met simultaneously and the duration exceeds the second preset period.

5. The apparatus according to claim 4, characterized in that, The identification module includes: The first determination unit is used to determine, when the timing type is the short-ground and open-circuit timing type, that the actual fault impact is that the hard-wired wake-up pin cannot normally hard-wire wake up the relevant controller. The second determination unit is used to determine, when the timing type is the timing type of the short power supply, that the actual fault impact is that the relevant controller cannot enter sleep mode and the dark current of the whole vehicle increases.

6. The apparatus according to claim 5, characterized in that, The processing module includes: The reminder unit is used to generate diagnostic fault information based on the actual impact of the short-ground and open-circuit faults, and to provide acoustic and / or optical reminders to the user. The sleep unit is used to generate diagnostic fault information based on the actual impact of the short power supply failure, and record the fault information after the fault is confirmed, so as to facilitate maintenance personnel to troubleshoot the fault.

7. A vehicle, characterized in that, include: The system includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the fault handling method for the hard-wired wake-up pin of the vehicle controller as described in any one of claims 1-3.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the fault handling method for the hard-wired wake-up pin of the vehicle controller as described in any one of claims 1-3.

Images