Charging fault diagnosis method, electronic device, storage medium and program product

Abstract

The invention discloses a charging fault diagnosis method, electronic equipment, a storage medium and a program product. The method comprises the steps that a received fault signal is responded, a charging mode of a vehicle is recognized, a target charging mode of the vehicle is obtained, the fault signal is used for representing a fault occurring in the process that a charger is powered on or powered off or the vehicle is charged through the charger, and the target charging mode of the vehicle is obtained; the target charging mode comprises one of a direct current charging mode and an alternating current charging mode; acquiring system data of the vehicle and charging data corresponding to the target charging mode; and fault diagnosis is carried out on the system data and the charging data by using a target diagnosis algorithm corresponding to the target charging mode to obtain a charging fault diagnosis result, and the charging fault diagnosis result at least comprises a fault source with a fault. The technical problem that the charging fault diagnosis efficiency is low in the prior art is solved.

Description

Technical Field

[0001] This application relates to the field of vehicles, and more specifically, to a charging fault diagnosis method, electronic device, storage medium, and program product. Background Technology

[0002] Currently, the rapid development of the new energy vehicle industry has placed higher demands on charging technology. However, traditional charging fault diagnosis methods are often limited to a single dimension, making it difficult to comprehensively and quickly locate various faults that occur during the charging process, resulting in low efficiency in charging fault diagnosis in related technologies.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This application provides a charging fault diagnosis method, electronic device, storage medium, and program product to at least solve the technical problem of low charging fault diagnosis efficiency in related technologies.

[0005] According to one aspect of the embodiments of this application, a charging fault diagnosis method is provided, comprising: in response to receiving a fault signal, identifying the charging mode of a vehicle to obtain a target charging mode of the vehicle, wherein the fault signal is used to characterize a fault occurring during the charging process of the charger being powered on or off, or during the charging of the vehicle through the charger, and the target charging mode includes one of the following: DC charging mode, AC charging mode; acquiring system data of the vehicle and charging data corresponding to the target charging mode; and using a target diagnosis algorithm corresponding to the target charging mode to perform fault diagnosis on the system data and charging data to obtain a charging fault diagnosis result, wherein the charging fault diagnosis result includes at least: the fault source where the fault occurred.

[0006] Further, acquiring charging data corresponding to the target charging mode includes: in response to the target charging mode being a DC charging mode, acquiring a DC charging signal and a first charging handshake signal message, wherein the DC charging signal includes a first connection confirmation signal and a first control confirmation signal; in response to the target charging mode being an AC charging mode, acquiring an AC charging signal and a second charging handshake signal message, wherein the AC charging signal includes a second connection confirmation signal and a second control confirmation signal.

[0007] Furthermore, using the diagnostic algorithm corresponding to the target charging mode, fault diagnosis is performed on system data and charging data to obtain charging fault diagnosis results. This includes: using the target diagnostic algorithm, performing physical layer diagnosis, communication layer diagnosis, and execution layer diagnosis on the vehicle and charger respectively, and obtaining physical layer diagnosis results, communication layer diagnosis results, and execution layer diagnosis results. The physical layer is used to characterize the hardware structure and connection status of the vehicle and charger, the communication layer is used to characterize the communication status between the vehicle and charger, and the execution layer is used to characterize the charging status of the vehicle and charger. The physical layer diagnosis results, communication layer diagnosis results, and execution layer diagnosis results are then summarized to obtain the charging fault diagnosis results.

[0008] Furthermore, in response to the target charging mode being DC charging mode, a target diagnostic algorithm is used to perform physical layer diagnostics on the vehicle and the charger to obtain physical layer diagnostic results, including: detecting whether the DC charging signal in the charging data is normal to obtain a first signal diagnostic result; detecting whether the connection between the vehicle and the DC charging head of the charger is normal based on system data to obtain a connection diagnostic result; and obtaining a physical layer diagnostic result based on the first signal diagnostic result and the connection diagnostic result.

[0009] Furthermore, using the target diagnostic algorithm, communication layer diagnostics are performed on the vehicle and the charger to obtain communication layer diagnostic results, including: detecting whether the communication protocol between the vehicle and the charger matches based on system data to obtain protocol diagnostic results; detecting whether the first charging handshake signal message in the charging data times out to obtain timeout diagnostic results; and obtaining communication layer diagnostic results based on the protocol diagnostic results and timeout diagnostic results.

[0010] Furthermore, using a target diagnostic algorithm, execution-level diagnostics are performed on the vehicle and charger to obtain execution-level diagnostic results, including: based on system data, detecting the engagement state of the vehicle's DC contactor to obtain a first-state diagnostic result; based on system data, detecting whether the vehicle's charging parameters match the charger's output parameters to obtain a parameter diagnostic result; based on system data, detecting whether the state of the vehicle's DC charging controller is normal to obtain a second-state diagnostic result; and based on the first-state diagnostic result, the parameter diagnostic result, and the second-state diagnostic result, the execution-level diagnostic result is obtained.

[0011] Furthermore, in response to the target charging mode being AC charging mode, a target diagnostic algorithm is used to perform physical layer diagnostics on the vehicle and charger to obtain physical layer diagnostic results, including: detecting whether the AC charging signal in the charging data is normal to obtain a second signal diagnostic result; detecting whether the vehicle's power supply voltage is normal based on system data to obtain a voltage diagnostic result; detecting whether the vehicle's grounding signal is normal based on system data to obtain a third signal diagnostic result; and obtaining a physical layer diagnostic result based on the second signal diagnostic result, the voltage diagnostic result, and the third signal diagnostic result.

[0012] Furthermore, using a target diagnostic algorithm, communication layer diagnostics are performed on the vehicle and the charger to obtain communication layer diagnostic results, including: detecting whether the second charging handshake signal message in the charging data is normal and obtaining message diagnostic results; and obtaining communication layer diagnostic results based on the message diagnostic results.

[0013] Furthermore, using the target diagnostic algorithm, execution-level diagnostics are performed on the vehicle and charger to obtain execution-level diagnostic results, including: based on charging data, detecting whether the charger's working state is normal to obtain a third-state diagnostic result; based on system data, detecting whether the vehicle's battery management system allows charging to obtain a charging diagnostic result; based on system data, detecting whether the vehicle's high-voltage relay engagement state is normal to obtain a fourth-state diagnostic result; and based on the third-state diagnostic result, the charging diagnostic result, and the fourth-state diagnostic result, the execution-level diagnostic result is obtained.

[0014] According to another aspect of the embodiments of this application, a charging fault diagnosis device is also provided, comprising: an identification module, configured to identify the charging mode of a vehicle in response to receiving a fault signal, and obtain the target charging mode of the vehicle, wherein the fault signal is used to characterize a fault that occurs during the charging process of the charger being powered on or off, or during the charging of the vehicle through the charger, and the target charging mode includes one of the following: DC charging mode and AC charging mode; an acquisition module, configured to acquire system data of the vehicle and charging data corresponding to the target charging mode; and a diagnosis module, configured to perform fault diagnosis on the system data and charging data using a target diagnosis algorithm corresponding to the target charging mode, and obtain a charging fault diagnosis result, wherein the charging fault diagnosis result includes at least: the fault source where the fault occurred.

[0015] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of this application when it runs.

[0016] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0017] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0018] According to another aspect of the embodiments of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0019] According to another aspect of the embodiments of this application, a computer program is also provided, which, when executed by a processor, implements the methods of the various embodiments of this application.

[0020] In this embodiment, when a fault signal is received, the vehicle's charging mode is first identified to obtain the target charging mode. Next, the vehicle's system data and the charging data corresponding to the target charging mode are acquired. Finally, the target diagnostic algorithm corresponding to the target charging mode is used to diagnose the system data and charging data to obtain a charging fault diagnosis result. In this application, when the vehicle receives a fault signal, the current charging mode is first identified, determining whether the target charging mode is DC or AC. This step avoids the blind judgment of charging mode in traditional diagnostic methods, ensuring the targetedness and effectiveness of subsequent diagnostic strategies. Next, the system data and charging data associated with the target charging mode are acquired, further simplifying the data acquisition process and avoiding the analysis of redundant data, thereby improving the efficiency and accuracy of diagnosis. Finally, the target diagnostic algorithm corresponding to the target charging mode is used to diagnose the system data and charging data to obtain a charging fault diagnosis result. This differentiated diagnostic logic design avoids the problem of low diagnostic efficiency caused by a lack of in-depth understanding of specific charging modes, ensuring accurate location of the fault source from massive amounts of data in the shortest possible time. In summary, this application achieves the technical objective of quickly locating the source of the fault by adopting an adaptive diagnostic strategy to intelligently identify the current charging mode of the vehicle and collect and analyze relevant data in a targeted manner. This improves the efficiency of charging fault diagnosis and solves the technical problem of low charging fault diagnosis efficiency in related technologies. Attached Figure Description

[0021] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0022] Figure 1 This is a flowchart of a charging fault diagnosis method according to an embodiment of this application;

[0023] Figure 2 This is a flowchart of a charging fault diagnosis method according to an embodiment of this application;

[0024] Figure 3This is a schematic diagram of the architecture of a vehicle power system according to an embodiment of this application;

[0025] Figure 4 This is a schematic diagram of a high-voltage system architecture for a vehicle charger according to an embodiment of this application;

[0026] Figure 5 This is a power-on / off control logic diagram for a high-voltage power supply of a charger according to an embodiment of this application;

[0027] Figure 6 This is a schematic diagram of a charging fault diagnosis device according to an embodiment of this application. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0030] According to an embodiment of this application, an embodiment of a charging fault diagnosis method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0031] Figure 1 This is a flowchart of a charging fault diagnosis method according to an embodiment of this application, such as... Figure 1 As shown, the method includes the following steps:

[0032] Step S102: In response to receiving a fault signal, the charging mode of the vehicle is identified to obtain the target charging mode of the vehicle. The fault signal is used to characterize the fault that occurs when the charger is powered on or off, or when the vehicle is charging through the charger. The target charging mode includes one of the following: DC charging mode and AC charging mode.

[0033] The aforementioned fault signals can refer to signals emitted during the charger's power-on / off process, as well as signals emitted when a fault occurs during vehicle charging. The types of fault signals may include, but are not limited to, charging interruption signals, start-failure signals, slow charging signals, overheating alarm signals, insulation fault signals, communication fault signals, overvoltage or undervoltage signals, etc. The specific fault signal needs to be determined based on the actual fault situation. Upon receiving a fault signal, the vehicle's vehicle control unit (such as the Vehicle Control Unit, or VCU) or other controllers responsible for fault diagnosis will initiate a fault diagnosis program to check and locate the fault source, thereby taking appropriate measures, such as protecting the vehicle battery, disconnecting the high-voltage circuit, and notifying the driver and service center.

[0034] The aforementioned vehicles can refer to automobiles with hybrid drive capabilities. Vehicle types may include, but are not limited to, series hybrid vehicles, parallel hybrid vehicles, and series-parallel hybrid vehicles, with the specific vehicle type to be determined based on the actual diagnostic objectives. In this application, the vehicle can serve as the main component of the charging fault diagnosis method. By rapidly diagnosing and locating charging faults, the normal operating condition of the vehicle can be maintained, thereby improving vehicle driving safety.

[0035] The aforementioned charging modes can refer to strategies for charging the vehicle's battery in different ways. Charging modes can include, but are not limited to, AC charging mode and DC charging mode. The specific charging mode needs to be determined according to actual needs. Different charging modes adapt to the charging needs in different situations, and also affect the safety control, charging efficiency and selection of charging equipment during the charging process.

[0036] The aforementioned target charging mode refers to the mode used to determine the next diagnostic and handling strategy after receiving a fault signal by identifying the charging mode currently being used. The type of target charging mode may include, but is not limited to, AC charging mode and DC charging mode; the specific target charging mode needs to be determined based on the actual situation. Determining the target charging mode can be used to locate the fault source and to ensure that the fault diagnosis algorithm can be correctly applied to the correct charging environment, avoiding misjudgments.

[0037] The aforementioned charger can refer to a device that converts external power into the form of electricity required by the vehicle battery. The charger is the core part of the charging process, used to determine the charging speed, efficiency and safety. At the same time, the operating status of the charger is often closely related to the detection of fault signals.

[0038] The aforementioned DC charging mode refers to a charging method that directly supplies DC power to the vehicle battery during the charging process. In DC charging mode, the vehicle can directly accept high-voltage DC power without the need for conversion through an on-board converter, which can greatly shorten the charging time.

[0039] The aforementioned AC charging mode refers to a charging method in which AC power is supplied to the vehicle during the charging process, and then converted into DC power by the AC / DC converter inside the vehicle to supply the battery. AC charging mode has lower requirements for the load on the power grid, and the cost of charging equipment is also relatively low. Therefore, AC charging mode is more suitable for long-term parking and overnight charging.

[0040] In one optional embodiment, in the vehicle's charging system, when the charger detects an abnormality during power-on, power-off, or charging, such as failure to start, charging interruption, or slow charging, the system immediately generates a fault signal and transmits it to the vehicle's vehicle controller (e.g., VCU). Upon receiving the fault signal, the controller's primary task is to accurately identify the vehicle's current charging mode, determining whether it is in DC or AC charging mode. This initial identification step allows the diagnostic process to directly target the characteristics and potential problems of a specific charging mode, effectively avoiding the ambiguity and misjudgment that may arise from general diagnostic methods, thus ensuring the specificity and accuracy of fault diagnosis.

[0041] By identifying the target charging mode, the vehicle can intelligently select the most suitable diagnostic strategy for the current charging environment. Whether it's checking the tightness and signal integrity of the charging pile and vehicle interface in DC charging mode, or verifying the effectiveness of the power supply voltage and grounding signal in AC charging mode, this can be done immediately, accelerating fault location and reducing charging interruption time caused by unknown faults. This significantly improves the safety and efficiency of the vehicle charging process. This rapid response and accurate diagnostic capability based on charging mode not only enhances the driver's charging experience but also provides strong support for the continuity and reliability of the vehicle's overall operation.

[0042] Step S104: Obtain the vehicle's system data and the charging data corresponding to the target charging mode.

[0043] The aforementioned system data refers to various real-time operating parameters and status information collected by the vehicle's controller (such as the VCU) during vehicle operation, especially during charger power-on / off and charging. System data may include, but is not limited to, data from the Battery Management System (BMS), Charger Control Unit (CCU), Engine Management System (EMS), and other related electronic control units. Specific system data needs to be determined based on actual fault diagnosis requirements.

[0044] The aforementioned charging data refers to various data indicators during the charging process. This data may include, but is not limited to, AC charging connection confirmation hardwired signals / AC charging control confirmation pin signals (Connection Confirm 1 Control Pilot 1, abbreviated as CC1 / CP1 signals), DC charging connection confirmation hardwired signals / DC charging control confirmation pin signals (Connection Confirm 2 / Control Pilot 2, abbreviated as CC2 / CP2 signals), charging handshake signal messages, etc. Specific charging data needs to be determined based on the chosen target charging mode. By analyzing the charging data, the working status of the charger and the charging status of the battery can be assessed, and any abnormalities that may affect charging performance or safety can be detected in a timely manner.

[0045] In one optional embodiment, when performing charging fault diagnosis on a hybrid vehicle, the vehicle controller (such as the VCU) first initiates a data acquisition process to instantly acquire system data and charging data related to the current charging mode. The system data covers key information from multiple vehicle subsystems, including the operating status of the Battery Management System (BMS), Charger Controller (CCU), and Engine Management System (EMS), such as the battery's State of Charge (SOC), charger voltage and current output, and engine operating status. This data provides a foundation for a comprehensive assessment of the vehicle's health. Simultaneously, acquiring charging data specific to the charging mode is crucial. For example, in AC charging mode, the VCU acquires the CC1 and CP1 signals to ensure a good connection between the charging gun and the vehicle, and reads the charging handshake signal message to confirm whether the charging parameters match. In DC charging mode, the VCU focuses on the CC2 and CP2 signals to check the connection status between the DC charging station and the vehicle. Simultaneously, the VCU acquires real-time battery demand parameters, such as voltage and current, from the BMS to determine if they match the charging station's output parameters, ensuring a smooth charging process. The implementation of this step ensures that fault diagnosis is based on the most real-time and comprehensive vehicle and charging information. This not only helps to quickly and accurately identify the source of the fault, but also provides immediate, data-driven solutions when a fault occurs, thereby improving the stability and safety of the charging system and reducing the impact of faults on charging efficiency and vehicle performance.

[0046] Step S106: Using the target diagnostic algorithm corresponding to the target charging mode, perform fault diagnosis on the system data and charging data to obtain charging fault diagnosis results. The charging fault diagnosis results include at least the fault source where the fault occurred.

[0047] The aforementioned target diagnostic algorithm refers to a fault diagnosis strategy and algorithm designed for a target charging mode (DC or AC). This algorithm may include, but is not limited to, AC charging diagnostic sub-algorithms and DC charging diagnostic sub-algorithms, with the specific algorithm determined based on the target charging mode. The target diagnostic algorithm can quickly identify and isolate faults based on the current vehicle charging mode, avoiding the lengthy troubleshooting process that might be necessary under normal circumstances, reducing diagnostic time and costs, and improving the efficiency and accuracy of fault handling.

[0048] The aforementioned charging fault diagnosis results can refer to the conclusions drawn by the target diagnostic algorithm after analyzing system data and charging data, which at least include information on the fault source. Charging fault diagnosis results can be specific hardware components, such as the charger, BMS, or charging cable, or they can be software logic problems, such as communication protocol mismatches or control logic errors. Charging fault diagnosis results can provide clear guidance for subsequent fault handling, enabling maintenance or adjustment work to directly target the fault source and avoid blind operation or over-maintenance.

[0049] The aforementioned fault sources can refer to the specific location or cause of the fault. Fault sources can be, but are not limited to, hardware faults involving physical components such as chargers, batteries, charging cables, relays, and contactors; software faults involving software problems in the control system; and faults caused by environmental factors such as unstable external power supply during charging, abnormal charging environment temperature, and charging station compatibility issues. The specific fault source needs to be determined based on the actual fault diagnosis results.

[0050] In one optional embodiment, a target diagnostic algorithm corresponding to the target charging mode is used to perform in-depth analysis of system data and charging data. During this process, the target diagnostic algorithm intelligently identifies and analyzes abnormal situations occurring during vehicle charging based on the different characteristics of AC or DC charging. By comprehensively judging data from core subsystems such as the VCU (Vehicle Controller Unit), BMS (Battery Management System), and CCU (Charger Controller Unit), the source of the fault can be quickly located. Finally, the real-time output of diagnostic results enhances the targetedness and accuracy of fault handling, reduces vehicle downtime caused by fault diagnosis, avoids unnecessary repair costs, and increases user confidence in the vehicle charging system.

[0051] In this embodiment, when a fault signal is received, the vehicle's charging mode is first identified to obtain the target charging mode. Next, the vehicle's system data and the charging data corresponding to the target charging mode are acquired. Finally, the target diagnostic algorithm corresponding to the target charging mode is used to diagnose the system data and charging data to obtain a charging fault diagnosis result. In this application, when the vehicle receives a fault signal, the current charging mode is first identified, determining whether the target charging mode is DC or AC. This step avoids the blind judgment of charging mode in traditional diagnostic methods, ensuring the targetedness and effectiveness of subsequent diagnostic strategies. Next, the system data and charging data associated with the target charging mode are acquired, further simplifying the data acquisition process and avoiding the analysis of redundant data, thereby improving the efficiency and accuracy of diagnosis. Finally, the target diagnostic algorithm corresponding to the target charging mode is used to diagnose the system data and charging data to obtain a charging fault diagnosis result. This differentiated diagnostic logic design avoids the problem of low diagnostic efficiency caused by a lack of in-depth understanding of specific charging modes, ensuring accurate location of the fault source from massive amounts of data in the shortest possible time. In summary, this application achieves the technical objective of quickly locating the source of the fault by adopting an adaptive diagnostic strategy to intelligently identify the current charging mode of the vehicle and collect and analyze relevant data in a targeted manner. This improves the efficiency of charging fault diagnosis and solves the technical problem of low charging fault diagnosis efficiency in related technologies.

[0052] Optionally, acquiring charging data corresponding to the target charging mode includes: in response to the target charging mode being a DC charging mode, acquiring a DC charging signal and a first charging handshake signal message, wherein the DC charging signal includes a first connection confirmation signal and a first control confirmation signal; in response to the target charging mode being an AC charging mode, acquiring an AC charging signal and a second charging handshake signal message, wherein the AC charging signal includes a second connection confirmation signal and a second control confirmation signal.

[0053] The aforementioned DC charging signals refer to the signals used between the charging interface and the vehicle's battery management system (BMS) to confirm the connection status and control the charging process when the vehicle is charging via DC. DC charging signals may include, but are not limited to, the first connection confirmation signal (CC2), the first control confirmation signal (CP2), etc., and the specific DC charging signals need to be determined according to actual requirements. DC charging signals ensure effective communication between the vehicle and the charging infrastructure, and are fundamental to the safe and efficient operation of the charging process.

[0054] The aforementioned first charging handshake signal message refers to the signal message exchanged between the vehicle BMS and the DC charging pile at the start of DC charging. The first charging handshake signal message can be used to confirm information such as charging parameters and safety conditions, ensure the matching of communication protocols between the two parties, and thus ensure the efficiency and safety of the charging process.

[0055] The aforementioned first connection confirmation signal (CC2) can be a key signal used to confirm whether the charging gun has been correctly inserted into the vehicle's charging port, ensuring charging safety.

[0056] The aforementioned first control confirmation signal (CP2) can refer to a signal used to control the charging process, such as starting and stopping charging, and determining charging parameters. It is an important control signal in the charging process.

[0057] The aforementioned AC charging signals refer to the signals used between the charging interface and the vehicle's BMS to confirm the connection status and control the charging process when the vehicle is charging via AC. AC charging signals may include, but are not limited to, the second connection confirmation signal (CC1), the second control confirmation signal (CP1), etc., and the specific AC charging signals need to be determined according to actual needs. AC charging signals are used to ensure communication between the charging facility and the vehicle, control the charging process, and ensure charging safety.

[0058] The aforementioned second charging handshake signal message refers to the signal message exchanged between the vehicle BMS and the AC charging pile at the start of AC charging. The second charging handshake signal message can be used to confirm information such as charging parameters and safety conditions to ensure the consistency of the communication protocol.

[0059] The aforementioned second connection confirmation signal (CC1) can refer to a signal used to confirm the connection status between the AC charging gun and the vehicle's charging port.

[0060] The aforementioned second control confirmation signal (CP1) can refer to a signal used to control the AC charging start-up, stop, parameter adjustment, and other processes.

[0061] In one optional embodiment, when the vehicle selects DC charging mode, a DC charging signal and a first charging handshake signal message are acquired and analyzed. The DC charging signal consists of a first connection confirmation signal (CC2) and a first control confirmation signal (CP2). The first connection confirmation signal confirms the secure and reliable physical connection between the charging gun and the vehicle's charging interface, while the first control confirmation signal monitors and adjusts key parameters during the charging process, such as voltage and current. Simultaneously, the first charging handshake signal message ensures that the communication protocol between the vehicle's battery management system (BMS) and the DC charging pile is consistent, and that the charging parameters are negotiated correctly—a prerequisite for efficient and safe charging. For vehicles using AC charging mode, an AC charging signal and a second charging handshake signal message are acquired. The AC charging signal includes a second connection confirmation signal (CC1) and a second control confirmation signal (CP1), each responsible for confirming the connection status of the AC charging gun and controlling the AC charging process. The second charging handshake signal message acts as a communication bridge during AC charging, ensuring information synchronization between the AC charging pile and the vehicle's BMS, and ensuring the accuracy of the charging parameters. By acquiring and analyzing charging signals and handshake signal messages in real time, it is possible not only to detect abnormalities in the charging process immediately, such as poor contact of the charging gun or mismatch of charging parameters, but also to quickly locate the source of the fault, providing a solid data foundation for subsequent fault diagnosis.

[0062] Optionally, the system data and charging data are diagnosed using the diagnostic algorithm corresponding to the target charging mode to obtain charging fault diagnosis results. This includes: using the target diagnostic algorithm to perform physical layer diagnosis, communication layer diagnosis, and execution layer diagnosis on the vehicle and charger respectively, to obtain physical layer diagnosis results, communication layer diagnosis results, and execution layer diagnosis results. The physical layer is used to characterize the hardware structure and connection status of the vehicle and charger, the communication layer is used to characterize the communication status between the vehicle and charger, and the execution layer is used to characterize the charging status of the vehicle and charger. The physical layer diagnosis results, communication layer diagnosis results, and execution layer diagnosis results are then summarized to obtain the charging fault diagnosis results.

[0063] The aforementioned physical layer diagnostics refer to the diagnosis of the hardware structure and connection status of the charging system. Physical layer diagnostics may include, but are not limited to, diagnosing whether the physical connection between the charging gun and the vehicle's charging port is secure, whether the charging lines are damaged, and whether the contactors or relays are functioning properly. Specific physical layer diagnostics need to be determined based on actual diagnostic requirements. Through physical layer diagnostics, hardware problems such as wear on the charging interface, broken charging cables, and abnormal contactor engagement can be detected.

[0064] The aforementioned communication layer diagnostics focus on checking the communication status between the vehicle and the charger, ensuring the accuracy of data transmission and the compatibility of communication protocols. Communication layer diagnostics may include, but are not limited to, checking the Controller Area Network (CAN) bus communication status, verifying the integrity of charging handshake signal messages, and detecting communication protocol compatibility. The specific communication layer diagnostics need to be determined based on actual diagnostic requirements. Communication layer diagnostics can be used to detect problems during charging caused by communication interruptions, data loss, or protocol incompatibility, such as abnormal data transmission between the BMS and CCU (charger controller), or timeouts in charging handshake signal messages.

[0065] The aforementioned execution-level diagnostics refer to diagnosing the actual operating status of the charging system. Execution-level diagnostics may include, but are not limited to, checking charger output parameters, verifying BMS control logic, and monitoring the status of high-voltage system components. Specific execution-level diagnostics need to be determined based on actual requirements. Execution-level diagnostics can be used to reveal faults at the system's execution level, such as abnormal charger output, BMS control logic errors, and deviations in the status of high-voltage system components. These faults directly affect charging efficiency and safety.

[0066] The aforementioned physical layer diagnostic results refer to fault information obtained after inspecting the hardware structure and connection status of the vehicle's charging interface, charging lines, contactors, or relays during the charging process. Physical layer diagnostic results may include, but are not limited to, wear or blockage of the charging interface, wear, breakage, or short circuit of the charging lines, abnormal engagement of contactors or relays, and unstable connection between the charging gun and the vehicle's charging port. Specific physical layer diagnostic results need to be determined based on the actual physical layer diagnostic situation. Physical layer diagnostic results are used to confirm whether the physical connections of the charging system are correct and stable, and whether the charging hardware is functioning properly, which is fundamental to ensuring charging safety and efficiency.

[0067] The aforementioned communication layer diagnostic results refer to the diagnostic information obtained after checking the communication status between the vehicle and the charger. Communication layer diagnostic results may include, but are not limited to, abnormal CAN bus communication status, integrity or matching problems of charging handshake signal messages, mismatched communication protocol versions leading to data parsing errors, signal interference leading to increased communication data error rate, etc. The specific communication layer diagnostic results need to be determined based on the communication layer diagnostics. Communication layer diagnostic results can be used to reveal faults caused by data transmission errors, protocol inconsistencies, or communication interruptions during the charging process.

[0068] The aforementioned execution-level diagnostic results refer to the diagnostic information obtained after diagnosing the charging status of the vehicle and charger. These results may include, but are not limited to, discrepancies between the charger's output voltage or current and expected values, abnormal charging permission signals from the BMS, abnormal states of high-voltage system components such as positive and negative relays, and abnormal situations occurring during charging, such as charging interruptions or low charging efficiency. Specific execution-level diagnostic results need to be determined based on the specific execution-level diagnostic findings. Execution-level diagnostic results directly affect the normal progress of the charging process, enabling the detection of abnormal charger output, errors in the battery management system's control logic, and deviations in the state of high-voltage components in the vehicle. They are crucial for timely fault handling.

[0069] In one optional embodiment, firstly, physical layer diagnostics focus on the stability of hardware structure and connection status, checking the integrity and connection reliability of key hardware elements such as charging interfaces, charging lines, and contactors to ensure a safe charging environment, thus obtaining physical layer diagnostic results. Secondly, communication layer diagnostics assess the data transmission quality and communication protocol compatibility between the vehicle and the charger. By monitoring the CAN bus communication status and the integrity and accuracy of charging handshake signal messages, unimpeded information flow during charging is ensured, resulting in communication layer diagnostic results. Finally, execution layer diagnostics diagnose the operational efficiency of the charging system, including the correctness of charger output parameters, the consistency of battery management system control logic, and the operating status of high-voltage relays, ensuring efficient and safe charging, thus obtaining execution layer diagnostic results. Finally, the diagnostic results from these three levels are summarized to obtain charging fault diagnosis results, enabling rapid and accurate location of the fault. Whether it's hardware damage, communication anomalies, or low execution efficiency, all can be reflected in the report. This process significantly improves the efficiency and accuracy of fault diagnosis, reduces the detection time and cost required for troubleshooting, and provides strong protection for the charging safety and stable operation of hybrid vehicles.

[0070] Optionally, in response to the target charging mode being DC charging mode, a target diagnostic algorithm is used to perform physical layer diagnostics on the vehicle and the charger to obtain physical layer diagnostic results, including: detecting whether the DC charging signal in the charging data is normal to obtain a first signal diagnostic result; based on system data, detecting whether the connection between the vehicle and the DC charging head of the charger is normal to obtain a connection diagnostic result; and based on the first signal diagnostic result and the connection diagnostic result, obtaining a physical layer diagnostic result.

[0071] The aforementioned first signal diagnostic result refers to the initial diagnostic conclusion at the hardware level of the charging system, determined by detecting the integrity and validity of the DC charging signals (including CC2 and CP2 signals) in the charging data when the target charging mode is DC charging mode. The first signal diagnostic result may include, but is not limited to, the detection results of the CC2 signal (connection confirmation signal), confirming whether the physical connection between the charging gun and the vehicle interface is established; and the detection results of the CP2 signal (control confirmation signal), monitoring whether control parameters such as voltage and current during the charging process meet expectations. The specific first signal diagnostic result needs to be determined based on the actual detection results. The first signal diagnostic result can be used to quickly confirm whether the connection confirmation signal between the charging gun and the vehicle interface is normal, and whether the control confirmation signal is transmitted correctly.

[0072] The aforementioned DC charging gun head refers to the charging interface portion of a DC charging pile, used to connect to the vehicle's charging interface to achieve power transmission and charging control signal transmission. The DC charging gun head acts as a bridge during the charging process; it not only handles the physical connection but also bears the task of transmitting charging control signals. Its condition directly affects charging efficiency and safety.

[0073] The aforementioned connection diagnostic results refer to the diagnostic conclusions drawn from system data regarding the connection status of the DC charging gun between the vehicle and the charger when the target charging mode is DC charging mode. These connection diagnostic results can be used to ensure a secure connection between the DC charging gun and the vehicle's charging interface, preventing charging failures or safety hazards caused by poor contact, loosening, or disconnection.

[0074] In one optional embodiment, when the vehicle selects DC charging mode, the system first detects the CC2 and CP2 signals in the charging data to obtain a first signal diagnostic result, confirming whether the charging control signal is normal. Next, based on system data, a comprehensive evaluation of the connection status between the DC charging station nozzle and the vehicle's charging interface is performed to obtain a connection diagnostic result, ensuring the reliability and security of the power transmission channel. Finally, the first signal diagnostic result and the connection diagnostic result are combined to form a physical layer diagnostic result. This result covers the health status of hardware signals and the quality of physical connections, laying a solid foundation for subsequent higher-level diagnostics. Through this process, this application can accurately identify potential faults in the DC charging process and take timely measures, effectively improving the stability and safety of the charging process and reducing maintenance costs caused by charging system failures.

[0075] Optionally, a target diagnostic algorithm is used to perform communication layer diagnostics on the vehicle and the charger to obtain communication layer diagnostic results, including: detecting whether the communication protocol between the vehicle and the charger matches based on system data to obtain a protocol diagnostic result; detecting whether the first charging handshake signal message in the charging data times out to obtain a timeout diagnostic result; and obtaining a communication layer diagnostic result based on the protocol diagnostic result and the timeout diagnostic result.

[0076] The aforementioned communication protocol refers to a set of standards governing data exchange between the vehicle and the charger. The protocol defines signal formats, data transmission rates, signal transmission sequences, and error detection and correction mechanisms to ensure that both parties can correctly understand and respond to each other's communication requests. This protocol ensures accurate information transmission during charging and is crucial for efficient and reliable communication between the vehicle and the charger, directly impacting the smooth operation and safety of the charging process.

[0077] The aforementioned protocol diagnostic results refer to the results of comparing the communication standards of the vehicle and the charger during the charging process to check whether their communication protocols are fully compatible. Protocol diagnostic results can help determine if there are any communication protocol mismatch issues during communication. If the communication protocols are incompatible, data may not be interpreted correctly, leading to communication interruptions or data transmission errors, thereby affecting charging efficiency and user experience.

[0078] The aforementioned timeout diagnostic result refers to detecting whether the first charging handshake signal message is received and responded to within a predetermined time during the communication process, thereby determining whether there is a delay or interruption in the communication. The timeout diagnostic result can help identify timing problems in the communication process. If the communication times out, it may cause synchronization errors between the vehicle and the charger, leading to abnormal termination of the charging process or a decrease in charging performance.

[0079] In one optional embodiment, firstly, the compatibility of the communication protocols between the two parties is detected based on system data. This process effectively confirms whether the communication standard used by the charger is compatible with the vehicle's control system, and the resulting protocol diagnostic result is a primary indicator of the communication health status. The compatibility of the communication protocols directly affects the interpretation and execution of charging control information, and is crucial for preventing charging failures or system malfunctions due to protocol inconsistencies. Next, during the transmission of the first charging handshake signal message, it is monitored in real time whether it completes within a preset time threshold, serving as the result of a timeout diagnosis. This diagnostic step can quickly identify timing problems in the communication link, avoiding charging process stagnation caused by signal delays or loss, and ensuring timely response to charging control commands. Finally, the protocol diagnostic result is combined with the timeout diagnostic result to obtain a comprehensive communication layer diagnostic result. This result not only reflects the compatibility of the communication protocols but also reveals the stability and response speed of the communication link, providing precise guidance for subsequent charging fault troubleshooting. Through this series of diagnostic processes, this application significantly improves the efficiency and accuracy of fault handling, ensures real-time monitoring of vehicle charging status and immediate feedback of abnormal situations, reduces maintenance costs and waiting time caused by communication failures, and also improves the charging experience for drivers and users, as well as enhancing the stability and safety of the overall charging process.

[0080] Optionally, an execution-level diagnostic algorithm is used to perform execution-level diagnostics on the vehicle and the charger to obtain execution-level diagnostic results, including: detecting the engagement state of the vehicle's DC contactor based on system data to obtain a first-state diagnostic result; detecting whether the vehicle's charging parameters match the charger's output parameters based on system data to obtain a parameter diagnostic result; detecting whether the state of the vehicle's DC charging controller is normal based on system data to obtain a second-state diagnostic result; and obtaining the execution-level diagnostic result based on the first-state diagnostic result, the parameter diagnostic result, and the second-state diagnostic result.

[0081] The aforementioned DC contactor refers to a key electrical component in the charging system, used to control the on / off state of the charging current and ensure the safe transfer of power from the charger to the vehicle battery. The proper engagement and disengagement of the DC contactor ensures electrical safety during the charging process, preventing vehicle damage caused by sudden current interruptions or abnormal power supply.

[0082] The aforementioned engagement state refers to whether the contacts of a DC contactor can reliably close during the charging process. The engagement state can directly affect the stability of power transmission.

[0083] The aforementioned first-state diagnostic results can refer to the detection results of the DC contactor's engagement state. Through the first-state diagnostic results, faults or abnormalities of the DC contactor can be detected in a timely manner, such as contact wear or poor contact, thus avoiding major safety accidents during the charging process.

[0084] The charging parameters mentioned above can refer to the charging current and voltage requested by the vehicle's Battery Management System (BMS). The output parameters mentioned above can refer to the actual current and voltage provided by the charger. Matching the charging parameters with the output parameters ensures charging efficiency and battery life, avoiding problems such as overcharging, undercharging, or battery overheating caused by parameter mismatch.

[0085] The aforementioned parameter diagnostic results refer to the detection results of the matching degree between charging parameters and charger output parameters, ensuring the efficiency and safety of the charging process. These diagnostic results can be used to adjust the charger's output in a timely manner to meet the vehicle's actual charging needs, avoiding energy waste and potential safety risks during the charging process.

[0086] The aforementioned second-state diagnostic results may refer to the inspection results of the vehicle's DC charging controller (or VCU). The second-state diagnostic results can be used to ensure that the DC charging controller can perform charging tasks accurately and without error, and to avoid charging interruptions or abnormalities caused by controller failure.

[0087] In one optional embodiment, the engagement status of the vehicle's DC contactor is detected by analyzing system data between the vehicle and the charger to ensure unobstructed power transmission. The resulting first-state diagnostic result directly reflects the health status of the contactor as an electrical switch. Subsequently, the charging parameters (such as voltage and current) requested by the vehicle's battery management system are compared with the actual output parameters of the charger to improve charging efficiency and protect battery life. The obtained parameter diagnostic result indicates the technical matching degree and accuracy of the charging process. Next, the status of the vehicle's DC charging controller (or VCU) is evaluated to confirm whether its control logic and response speed are normal, ensuring intelligent monitoring and smooth execution of the charging process. The resulting second-state diagnostic result ensures the core functions of the control system. Finally, these three key diagnostic results—the first-state diagnostic result, the parameter diagnostic result, and the second-state diagnostic result—are integrated and analyzed to obtain a comprehensive evaluation of the execution layer diagnostics. This result accurately locates potential problems in the actual operation of the charging system, whether it is a faulty electrical component, improper parameter settings, or an abnormal controller status. By implementing layer-level diagnostics, this application can quickly identify and resolve charging faults, thereby effectively improving the stability and safety of the hybrid vehicle charging system. At the same time, it reduces maintenance costs caused by charging anomalies and enhances the user charging experience.

[0088] Optionally, in response to the target charging mode being AC charging mode, a target diagnostic algorithm is used to perform physical layer diagnostics on the vehicle and charger to obtain physical layer diagnostic results, including: detecting whether the AC charging signal in the charging data is normal to obtain a second signal diagnostic result; detecting whether the vehicle's power supply voltage is normal based on system data to obtain a voltage diagnostic result; detecting whether the vehicle's grounding signal is normal based on system data to obtain a third signal diagnostic result; and obtaining a physical layer diagnostic result based on the second signal diagnostic result, the voltage diagnostic result, and the third signal diagnostic result.

[0089] The aforementioned AC charging signals refer to signals used during AC charging to confirm the connection status between the charging gun and the vehicle and to control the charging process. AC charging signals may include, but are not limited to, connection confirmation signals (CC1) and control guidance signals (CP). Specific AC charging signals need to be determined based on the actual situation. Correct AC charging signals are a prerequisite for ensuring the start and normal operation of the charging process, playing a crucial role in confirming the connection status and controlling the charging process.

[0090] The aforementioned second signal diagnostic result refers to the diagnostic conclusion regarding whether the AC charging signals (CC1 and CP) are normal. This result can reflect the initialization state of the charging process and whether the control is appropriate. By utilizing the second signal diagnostic result, abnormalities in the charging signal transmission, such as signal loss, bit errors, or insufficient signal strength, can be detected in a timely manner, thereby preventing charging failures.

[0091] The aforementioned power supply voltage refers to the AC voltage level supplied to the vehicle from the power grid during vehicle charging, which is the energy basis for the charging process.

[0092] The voltage diagnostic results mentioned above refer to a conclusion based on system data, determining whether the power supply voltage is within the allowable range and thus whether the voltage condition is suitable for charging. Voltage diagnostic results may include, but are not limited to, various conditions such as low voltage, high voltage, large voltage fluctuations, or unstable voltage. The specific voltage diagnostic result needs to be determined based on the actual diagnostic situation. Voltage diagnostic results can be used to avoid overvoltage or undervoltage charging caused by abnormal voltage, prevent damage to the battery and other electrical components, and ensure a safe and efficient charging process.

[0093] The aforementioned grounding signal can refer to the signal used in the vehicle charging system to confirm the safe electrical connection between the vehicle and the ground. A correct grounding signal can be used to avoid leakage accidents during the charging process, protect the electrical system from electromagnetic interference, and ensure personnel safety.

[0094] The aforementioned third-signal diagnostic result refers to the conclusion of the detection of the vehicle's grounding signal status. This result may include situations such as excessively high grounding resistance, missing or unstable grounding signals, etc. The specific third-signal diagnostic result needs to be determined based on the actual situation. Obtaining the third-signal diagnostic result by detecting the normality of the grounding signal can be used to prevent electrical short circuits, electric shock accidents, etc., and to maintain electrical stability during the charging process.

[0095] In one optional embodiment, the AC charging signal in the charging data is first checked. This process verifies whether the CC1 (connection confirmation signal) and CP (control guidance signal) meet the expected specifications, ensuring effective connectivity between the charging gun and the vehicle and the controllability of the charging process. The resulting second signal diagnostic result reflects the health status of the signal transmission. Subsequently, based on system data, it is determined whether the power supply voltage is stable and suitable for charging. This voltage diagnostic result is an important reference for preventing overvoltage or undervoltage charging and avoiding damage to the battery and vehicle electrical system. Next, the vehicle's grounding signal is rigorously tested to ensure a good electrical connection between the vehicle's electrical system and the ground, avoiding potential leakage risks during charging. This yields a third signal diagnostic result. Finally, by comprehensively analyzing the second signal diagnostic result (AC charging signal status), the voltage diagnostic result (power supply voltage status), and the third signal diagnostic result (vehicle grounding signal status), a comprehensive assessment of the physical layer diagnostics is obtained, i.e., the physical layer diagnostic result. This result accurately depicts the actual performance of the charging process in terms of electrical transmission and safety, helps to quickly locate physical faults or anomalies, and provides a scientific basis for timely corrective measures, thereby significantly improving the overall stability and safety of the charging process and enhancing the user's charging experience.

[0096] Optionally, a target diagnostic algorithm is used to perform communication layer diagnostics on the vehicle and the charger to obtain communication layer diagnostic results, including: detecting whether the second charging handshake signal message in the charging data is normal and obtaining message diagnostic results; and obtaining communication layer diagnostic results based on the message diagnostic results.

[0097] The aforementioned message diagnostic results refer to the process of detecting whether the second charging handshake signal message in the charging data conforms to the established communication protocol based on system data during the charging process. This includes the integrity of the signal content, the accuracy of the format, and the reliability of transmission. Message diagnostic results may include, but are not limited to, message integrity diagnostic results, message format diagnostic results, and message transmission delay diagnostic results. The specific message diagnostic results need to be determined based on actual diagnostic requirements. Message diagnostic results can be used to ensure the accurate and error-free transmission of charging commands and status information, providing communication assurance for a smooth charging process. Message diagnostic results help identify and correct possible communication errors, such as message loss, incorrect formatting, or transmission delays, thereby avoiding problems such as charging interruptions or improper charging parameter settings, and ensuring charging efficiency and safety.

[0098] In one optional embodiment, firstly, the second charging handshake signal message in the charging data is inspected. This action focuses on verifying the message's integrity, format correctness, and transmission efficiency. The resulting message diagnostic results directly reflect the basic health status of the communication between the two parties. Next, based on the message diagnostic results, the overall performance of the communication layer is further analyzed to obtain communication layer diagnostic results. This process is not merely an evaluation of a single message, but rather a comprehensive consideration of the time series of message diagnostic results to identify potential periodic or transient problems in communication, such as frequent message loss, excessive latency, or incompatible message formats. The communication layer diagnostic results can be used to ensure the accurate issuance of charging control commands and real-time feedback of charging status information, thereby improving the reliability of the charging process and the user experience.

[0099] Optionally, an execution-level diagnostic algorithm is used to perform execution-level diagnostics on the vehicle and the charger to obtain execution-level diagnostic results, including: detecting whether the charger's working state is normal based on charging data to obtain a third-state diagnostic result; detecting whether the vehicle's battery management system allows charging based on system data to obtain a charging diagnostic result; detecting whether the vehicle's high-voltage relay engagement state is normal based on system data to obtain a fourth-state diagnostic result; and obtaining execution-level diagnostic results based on the third-state diagnostic result, the charging diagnostic result, and the fourth-state diagnostic result.

[0100] The aforementioned third-state diagnostic result refers to the diagnostic result obtained after a comprehensive inspection of the charger's operating status based on charging data. The third-state diagnostic result is directly related to charging efficiency, safety, and the charger's own health condition. It helps to promptly detect and address potential overheating, overload, or internal faults, ensuring a smooth charging process.

[0101] The aforementioned Battery Management System (BMS) refers to the core system that manages the state of a vehicle's battery, protects battery safety, and improves battery performance. It is responsible for monitoring key parameters such as battery voltage, current, temperature, and state of charge (SOC). During charging, the BMS communicates with the charger and vehicle control unit (VCU) to ensure that charging parameters match the battery's current optimal state, preventing overcharging or over-discharging and guaranteeing the battery's longevity and safety.

[0102] The aforementioned charging diagnostic results refer to the conclusions drawn from system data regarding whether the BMS (Battery Management System) permits charging. Charging diagnostic results may include, but are not limited to, charging permission (i.e., the battery state meets charging conditions, and the BMS sends a charging permission signal) and charging prohibition (i.e., the battery state is abnormal, such as excessively high temperature or near-full SOC, and the BMS sends a charging prohibition signal). Specific charging diagnostic results need to be determined based on actual diagnostic results. Charging diagnostic results can serve as safety checkpoints for initiating the charging process, preventing charging when the battery temperature is too high, the state of charge is saturated, or the battery health is poor, thus protecting the battery from damage.

[0103] The aforementioned fourth-state diagnostic result can refer to the diagnostic result based on system data, which detects the engagement status of the vehicle's high-voltage relay and determines whether the relay is in a normal operating state. The fourth-state diagnostic result can be used to confirm the integrity and safety of the power transmission path between the vehicle's high-voltage system and the charger.

[0104] In one optional embodiment, firstly, a detailed inspection of the charger's operating status is conducted. Based on charging data, its output parameters, temperature status, and control logic are evaluated to determine if they meet expectations, resulting in a third-state diagnostic result. This result directly relates to the charger's performance and stability, and is a key factor in ensuring the smooth progress of the charging process. Next, based on system data, it is determined whether the Battery Management System (BMS) allows charging, obtaining a charging diagnostic result. The BMS comprehensively monitors the battery, including voltage, current, temperature, and state of charge, ensuring that charging parameters match the battery's current state to prevent battery damage and guarantee charging safety. Then, the high-voltage relay's engagement status is verified. System data is used to detect whether it accurately responds to opening and closing commands during the charging process, resulting in a fourth-state diagnostic result. The normality of this state directly affects the electrical connection between the high-voltage system and the charger, and is crucial for preventing electrical accidents. Finally, the third-state diagnostic result (charger operating status), the charging diagnostic result (whether the BMS allows charging), and the fourth-state diagnostic result (high-voltage relay engagement status) are comprehensively analyzed to obtain the execution-level diagnostic result. This comprehensive result fully assesses the health status of the charging system at the execution level, and can quickly locate potential execution anomalies, such as charger overheating, BMS charging strategy errors, or high-voltage relay sticking, providing a scientific basis for timely diagnosis and appropriate handling of charging faults.

[0105] In one alternative embodiment, Figure 2 This is a flowchart of a charging fault diagnosis method according to an embodiment of this application, such as... Figure 2 As shown, this method starts with the selection of the charging mode, that is, determining whether the vehicle is currently in AC charging mode or DC charging mode. This determination determines the direction of the subsequent diagnostic path.

[0106] Once the charging mode is determined, the process enters the mode-specific diagnostic phase. For AC charging mode, the CC1 and CP1 signals and power status are checked first to confirm the effective connection of the charging cable to the vehicle and the availability of external power. Subsequently, the system verifies the communication status of AC charging, paying particular attention to the normal data exchange between the charger and the battery management system (BMS), including the integrity verification of charging parameter handshake messages. If any problems are found at the physical or communication layer, the system will immediately output the fault diagnosis results and provide a warning in the instrument cluster display (IC), allowing the driver to understand and take timely action.

[0107] For DC charging mode, the CC2 and CP2 signals are first detected to verify the connection status between the DC charging station and the vehicle. Next, a series of steps are performed to check whether the communication protocol between the DC charging station and the BMS is compatible, whether messages are delivered on time, and whether the charger is operating normally as instructed, including the engagement status of the high-voltage relay. Any abnormality in any of these steps will trigger a system alarm, indicating the specific location of the fault, whether it is a problem with the external charging station or a fault in the vehicle's internal charger or battery management system.

[0108] The above process embodies a comprehensive and detailed fault diagnosis method of this application, which covers the entire cycle from the insertion of the charging gun to the end of the charging process. Through layered diagnosis (physical layer, communication layer and execution layer) and mode-specific strategies, it ensures that problems can be identified and resolved quickly and accurately, thereby guaranteeing the safety and smoothness of the charging process for new energy vehicles.

[0109] In one alternative embodiment, Figure 3 This is a schematic diagram of the architecture of a vehicle powertrain system according to an embodiment of this application, such as... Figure 3 As shown, the powertrain system consists of components such as an engine, motor, battery, transmission, clutch, drive mechanism, charger, and DC-DC converter, along with corresponding controllers for each powertrain component. These controllers include the Engine Management System (EMS), Vehicle Control Unit (VCU), Motor Control Unit (MCU), Battery Management System (BMS), Transmission Control Unit (TCU), DC-DC converter, Instrument Cluster (IC), Charger Control Unit (CCU), and charger. The controllers communicate with each other via a CAN network. The VCU, as the core controller of the vehicle, coordinates and controls the other subsystems. The EMS controls the engine, the MCU controls the motor, the BMS controls the battery, the TCU controls the transmission, the DC-DC converter controls current conversion, the IC displays various information, and the CCU controls the on-board charger. Figure 3 By clearly identifying the relationships between each controller and the main powertrain, the system provides an intuitive perspective for understanding the complex control logic of a vehicle.

[0110] In one alternative embodiment, Figure 4 This is a schematic diagram of a high-voltage system architecture for a vehicle charger according to an embodiment of this application, such as... Figure 4 As shown, the system architecture details the three main operating modes: initial mode, charging mode, and safety mode, as well as the two power change states that accompany the mode transition: charging on and charging off.

[0111] The initial mode indicates the default state of the vehicle's high-voltage system before charging begins, with all high-voltage assembly components in standby mode. When charging demand is activated, the system enters charging mode, at which point the charger's high-voltage power supply begins the power-on process. Following a pre-set timing control strategy, relevant controllers and components are gradually activated to ensure safe charging. The safety mode is the system's emergency response to sudden faults or abnormal situations. If any non-compliant phenomena are detected during power changes or charging modes, such as abnormal charger parameters, excessively low or high battery SOC, or unstable charging gun connection, the VCU will comprehensively assess the situation and immediately switch to safety mode, controlling the vehicle to take necessary measures, such as safe parking or restricted driving mode, to avoid potential dangers. The charging power-on and charging power-off states in the power change states represent the formal start and orderly termination of the charging process, respectively. During the charging power-on phase, the system follows a specific sequence to activate the high-voltage system assemblies one by one, ensuring that the charger is smoothly connected to the power grid. During the charging power-off phase, once charging is complete or the charging gun is detected to be unplugged, the system will disconnect the high-voltage connection in reverse order, ensuring that all components return to their initial state in an orderly manner and preventing damage caused by sudden power outages.

[0112] In summary, Figure 4 The architecture design ensures the efficient operation and safety of hybrid vehicles during the charging process, and provides a reliable charging experience for drivers and vehicles through intelligent mode state switching and power change control.

[0113] In one alternative embodiment, Figure 5 This is a power-on / off control logic diagram for a charger's high-voltage power supply according to an embodiment of this application. Figure 5 The control logic flow of the charger's high-voltage power supply in a hybrid vehicle is intuitively described. This flow is crucial to ensuring the safe and stable operation of the vehicle during the charging process.

[0114] The process begins with a change in the vehicle key signal. When the key switches from the off state to the off state, it indicates that the vehicle is likely preparing to start charging. Next, the charging gun is inserted into the vehicle's charging port, triggering the system to enter the charging start state—the first step in the charging process. Subsequently, the system wakes up all critical controllers related to charging, including the Battery Management System (BMS), Vehicle Control Unit (VCU), Charger Control Unit (CCU), and the charger itself. These controllers are in standby mode, ready to receive and process charging commands. During this stage, the BMS monitors the battery's State of Charge (SOC). When the SOC falls below a predetermined threshold, the BMS sends a charging request to the VCU, triggering charging. Upon receiving the request, the VCU ensures that the vehicle's powertrain is functioning normally and without any abnormalities, then sends a signal to the BMS to allow charging. If the status check passes, the VCU sends a command to the CCU to close the positive and negative relays of the charger, allowing high-voltage current to flow to the battery. After confirming that both positive and negative relays are closed, the CCU sends the status back to the VCU, which then controls the charger to start the charging process.

[0115] Once the charging process is complete, or the charging gun is removed, the system enters the charging power-off procedure to safely disconnect the high-voltage power supply. This step is also triggered by the BMS. When the SOC reaches or exceeds the specified value, the BMS sends a charging completion signal to the VCU, or the CCU reports to the VCU when the charging gun is detected to have been removed. The VCU then sends a signal to the BMS to prohibit charging and further controls the CCU to disable the charger. After ensuring the charger is properly disconnected, the VCU issues a command to disconnect the charger's positive and negative relays, completely isolating the high-voltage power supply. Finally, the VCU sends a sleep signal, putting all relevant controllers into a low-power state, completing the entire charging power-off process.

[0116] Figure 5 The control logic clearly demonstrates the system's robustness during charging and de-charging, ensuring that every charging operation takes place in a safe environment without posing any potential risks to the vehicle or user. This process design is the core of the technical solution presented in this application, aiming to provide a reliable charging power control mechanism that effectively improves vehicle charging efficiency and safety.

[0117] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0118] According to an embodiment of this application, a charging fault diagnosis device is provided. It should be noted that this device can be used to execute the charging fault diagnosis method described above. The specific implementation method and preferred application scenarios are the same as those in the above embodiment, and will not be repeated here.

[0119] Figure 6 This is a schematic diagram of a charging fault diagnosis device according to an embodiment of this application, such as... Figure 6 As shown, the device includes: an identification module 602, an acquisition module 604, and a diagnostic module 606.

[0120] The identification module 602 is used to identify the vehicle's charging mode in response to receiving a fault signal, and obtain the vehicle's target charging mode. The fault signal is used to characterize a fault that occurs when the charger is powered on or off, or when the vehicle is charging through the charger. The target charging mode includes one of the following: DC charging mode and AC charging mode. The acquisition module 604 is used to acquire the vehicle's system data and the charging data corresponding to the target charging mode. The diagnosis module 606 is used to perform fault diagnosis on the system data and charging data using the target diagnosis algorithm corresponding to the target charging mode, and obtain a charging fault diagnosis result. The charging fault diagnosis result includes at least the fault source where the fault occurred.

[0121] Optionally, the acquisition module is configured to acquire a DC charging signal and a first charging handshake signal message in response to the target charging mode being a DC charging mode, wherein the DC charging signal includes a first connection confirmation signal and a first control confirmation signal; and to acquire an AC charging signal and a second charging handshake signal message in response to the target charging mode being an AC charging mode, wherein the AC charging signal includes a second connection confirmation signal and a second control confirmation signal.

[0122] Optionally, the diagnostic module is used to perform physical layer diagnosis, communication layer diagnosis, and execution layer diagnosis on the vehicle and the charger respectively using the target diagnostic algorithm, and obtain physical layer diagnosis results, communication layer diagnosis results, and execution layer diagnosis results. The physical layer is used to characterize the hardware structure and connection status of the vehicle and the charger, the communication layer is used to characterize the communication status between the vehicle and the charger, and the execution layer is used to characterize the charging status of the vehicle and the charger. The physical layer diagnosis results, communication layer diagnosis results, and execution layer diagnosis results are summarized to obtain the charging fault diagnosis result.

[0123] Optionally, the diagnostic module is also used to detect whether the DC charging signal in the charging data is normal and obtain a first signal diagnostic result; based on system data, detect whether the connection between the vehicle and the DC charging gun head of the charger is normal and obtain a connection diagnostic result; and based on the first signal diagnostic result and the connection diagnostic result, obtain a physical layer diagnostic result.

[0124] Optionally, the diagnostic module is also used to detect whether the communication protocol between the vehicle and the charger matches based on system data, and obtain a protocol diagnostic result; detect whether the first charging handshake signal message in the charging data times out, and obtain a timeout diagnostic result; and obtain a communication layer diagnostic result based on the protocol diagnostic result and the timeout diagnostic result.

[0125] Optionally, the diagnostic module is also used to detect the engagement state of the vehicle's DC contactor based on system data to obtain a first-state diagnostic result; to detect whether the vehicle's charging parameters match the charger's output parameters based on system data to obtain a parameter diagnostic result; to detect whether the state of the vehicle's DC charging controller is normal based on system data to obtain a second-state diagnostic result; and to obtain an execution layer diagnostic result based on the first-state diagnostic result, the parameter diagnostic result, and the second-state diagnostic result.

[0126] Optionally, the diagnostic module is also used to detect whether the AC charging signal in the charging data is normal, and obtain a second signal diagnostic result; based on system data, detect whether the vehicle's power supply voltage is normal, and obtain a voltage diagnostic result; based on system data, detect whether the vehicle's grounding signal is normal, and obtain a third signal diagnostic result; based on the second signal diagnostic result, the voltage diagnostic result, and the third signal diagnostic result, obtain a physical layer diagnostic result.

[0127] Optionally, the diagnostic module is also used to detect whether the second charging handshake signal message in the charging data is normal, and obtain the message diagnostic result; based on the message diagnostic result, obtain the communication layer diagnostic result.

[0128] Optionally, the diagnostic module is also used to detect whether the working status of the charger is normal based on charging data, and obtain a third-state diagnostic result; to detect whether the vehicle's battery management system allows charging based on system data, and obtain a charging diagnostic result; to detect whether the high-voltage relay of the vehicle is in a normal state based on system data, and obtain a fourth-state diagnostic result; and to obtain an execution layer diagnostic result based on the third-state diagnostic result, the charging diagnostic result, and the fourth-state diagnostic result.

[0129] Embodiments of this application also provide a vehicle, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods described in various embodiments of this application when it runs.

[0130] Embodiments of this application also provide a computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0131] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0132] Embodiments of this application also provide a computer program product, including a non-volatile computer-readable storage medium for storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0133] Embodiments of this application also provide a computer program that, when executed by a processor, implements the methods described in the various embodiments of this application.

[0134] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0135] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0136] 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 units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0137] Furthermore, the functional units in the various embodiments of this application 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.

[0138] If the integrated 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, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0139] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A charging fault diagnosis method, characterized in that, include: In response to receiving a fault signal, the charging mode of the vehicle is identified to obtain the target charging mode of the vehicle. The fault signal is used to characterize a fault that occurs when the charger is powered on or off, or when the vehicle is being charged through the charger. The target charging mode includes one of the following: DC charging mode and AC charging mode. Acquire the system data of the vehicle, and the charging data corresponding to the target charging mode; Using the target diagnostic algorithm corresponding to the target charging mode, fault diagnosis is performed on the system data and the charging data to obtain charging fault diagnosis results, wherein the charging fault diagnosis results include at least: the fault source where the fault occurred.

2. The charging fault diagnosis method according to claim 1, characterized in that, Obtaining the charging data corresponding to the target charging mode includes: In response to the target charging mode being the DC charging mode, a DC charging signal and a first charging handshake signal message are acquired, wherein the DC charging signal includes: a first connection confirmation signal and a first control confirmation signal; In response to the target charging mode being the AC charging mode, an AC charging signal and a second charging handshake signal message are acquired, wherein the AC charging signal includes: a second connection confirmation signal and a second control confirmation signal.

3. The charging fault diagnosis method according to claim 1, characterized in that, Using the diagnostic algorithm corresponding to the target charging mode, fault diagnosis is performed on the system data and the charging data to obtain charging fault diagnosis results, including: Using the target diagnostic algorithm, physical layer diagnostics, communication layer diagnostics, and execution layer diagnostics are performed on the vehicle and the charger respectively, to obtain physical layer diagnostic results, communication layer diagnostic results, and execution layer diagnostic results. The physical layer is used to characterize the hardware structure and connection status of the vehicle and the charger, the communication layer is used to characterize the communication status between the vehicle and the charger, and the execution layer is used to characterize the charging status of the vehicle and the charger. The charging fault diagnosis results are obtained by summarizing the physical layer diagnosis results, the communication layer diagnosis results, and the execution layer diagnosis results.

4. The charging fault diagnosis method according to claim 3, characterized in that, In response to the target charging mode being the DC charging mode, the target diagnostic algorithm is used to perform physical layer diagnostics on the vehicle and the charger to obtain physical layer diagnostic results, including: The DC charging signal in the charging data is checked for normality to obtain the first signal diagnosis result. Based on the system data, the connection between the vehicle and the DC charging head of the charger is checked to determine if it is normal, and the connection diagnosis result is obtained. Based on the first signal diagnostic result and the connection diagnostic result, the physical layer diagnostic result is obtained.

5. The charging fault diagnosis method according to claim 4, characterized in that, Using the target diagnostic algorithm, communication layer diagnostics are performed on the vehicle and the charger to obtain communication layer diagnostic results, including: Based on the system data, the system detects whether the communication protocol between the vehicle and the charger is compatible, and obtains the protocol diagnosis result. Detect whether the first charging handshake signal message in the charging data has timed out, and obtain the timeout diagnosis result; Based on the protocol diagnostic results and the timeout diagnostic results, the communication layer diagnostic results are obtained.

6. The charging fault diagnosis method according to claim 4, characterized in that, Using the target diagnostic algorithm, execution-level diagnostics are performed on the vehicle and the charger to obtain execution-level diagnostic results, including: Based on the system data, the engagement state of the DC contactor of the vehicle is detected to obtain the first state diagnostic result; Based on the system data, the system detects whether the charging parameters of the vehicle match the output parameters of the charger, and obtains the parameter diagnosis results. Based on the system data, the status of the vehicle's DC charging controller is checked to determine if it is normal, and a second status diagnosis result is obtained. Based on the first state diagnosis result, the parameter diagnosis result, and the second state diagnosis result, the execution layer diagnosis result is obtained.

7. The charging fault diagnosis method according to claim 3, characterized in that, In response to the target charging mode being the AC charging mode, the target diagnostic algorithm is used to perform physical layer diagnostics on the vehicle and the charger to obtain physical layer diagnostic results, including: The AC charging signal in the charging data is checked for normality to obtain a second signal diagnostic result. Based on the system data, the voltage of the vehicle's power supply is checked to determine if it is normal, and a voltage diagnosis result is obtained. Based on the system data, the grounding signal of the vehicle is checked to determine if it is normal, and a third signal diagnostic result is obtained. The physical layer diagnostic result is obtained based on the second signal diagnostic result, the voltage diagnostic result, and the third signal diagnostic result.

8. The charging fault diagnosis method according to claim 7, characterized in that, Using the aforementioned target diagnosis algorithm, Communication layer diagnostics are performed on the vehicle and the charger to obtain communication layer diagnostic results, including: Detect whether the second charging handshake signal message in the charging data is normal, and obtain the message diagnosis result; Based on the message diagnosis results, the communication layer diagnosis results are obtained.

9. The charging fault diagnosis method according to claim 7, characterized in that, Using the aforementioned target diagnosis algorithm, Execution layer diagnostics are performed on the vehicle and the charger to obtain execution layer diagnostic results, including: Based on the charging data, the working status of the charger is detected to determine whether it is normal, and a third-state diagnostic result is obtained. Based on the system data, it is determined whether the vehicle's battery management system allows charging, and a charging diagnostic result is obtained. Based on the system data, the system checks whether the high-voltage relay of the vehicle is in a normal operating state, and obtains the fourth state diagnostic result. Based on the third state diagnostic result, the charging diagnostic result, and the fourth state diagnostic result, the execution layer diagnostic result is obtained.

10. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program executes the charging fault diagnosis method according to any one of claims 1 to 9 when it runs.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device on which the storage medium is located to perform the charging fault diagnosis method according to any one of claims 1 to 9.

12. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the charging fault diagnosis method according to any one of claims 1 to 9.

Images