Precharge fault diagnosis method and apparatus, device and medium

Abstract

A precharge fault diagnosis method and apparatus, a device and a medium. The precharge fault diagnosis method comprises: acquiring a precharge fault record of a vehicle and multiple pieces of signal data of the vehicle before and after the precharge fault record is generated, wherein the precharge fault record is generated when the vehicle monitors a fault in the precharge process; determining a diagnosis condition corresponding to fault data in the precharge fault record, and determining target signal data corresponding to the diagnosis condition among the multiple pieces of signal data, wherein the target signal data is battery data; and performing precharge fault diagnosis on the basis of the target signal data, to diagnose whether the precharge fault record is a false alarm record or not. According to the method, a precharge fault can be diagnosed, ensuring the safe operation of a battery system, and improving the safety of an electric vehicle.

Description

Precharge fault diagnosis method, device, equipment and medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on July 31, 2023, with application number 202310953384.8 and application name “Pre-charge fault diagnosis method, device, equipment and medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present disclosure relates to the technical field of electric vehicles, and in particular to, but not limited to, a pre-charging fault diagnosis method, device, equipment, and medium. Background Art

[0004] With the rapid development of the electric vehicle industry, the number of electric vehicles on the road is increasing. As a crucial component of electric vehicles, the safety of the battery system is of paramount importance. The power-on process for the power battery requires a pre-charge to ensure the proper operation of the main circuit contactor and protect the high-voltage load from being damaged by the high-voltage transient current directly input.

[0005] During the pre-charging process, power batteries can experience serious faults such as pre-charging timeouts due to external factors such as weather, as well as internal factors such as damage to hardware such as the charger, charging port, charging cable, and charging piles. This can even cause the vehicle to break down, posing a threat to the user's safety. Therefore, to ensure the safe operation of the battery system and improve the safety of electric vehicles, diagnosing pre-charging faults is crucial.

[0006] Summary of the Invention

[0007] In order to solve the above technical problems, the present disclosure provides a pre-charge fault diagnosis method, device, equipment and medium, which can diagnose pre-charge faults, ensure the safe operation of the battery system, and improve the safety of electric vehicles.

[0008] In a first aspect, an embodiment of the present disclosure provides a pre-charge fault diagnosis method, the method comprising:

[0009] Acquire a pre-charging fault record of a vehicle and a plurality of signal data of the vehicle before and after the pre-charging fault record is generated, wherein the pre-charging fault record is generated when a fault is detected by the vehicle during the pre-charging process;

[0010] Determining a diagnostic condition corresponding to the fault data in the pre-charge fault record, and determining target signal data corresponding to the diagnostic condition from the plurality of signal data, wherein the target signal data is battery data;

[0011] Pre-charge fault diagnosis is performed based on the target signal data to diagnose whether the pre-charge fault record is a false alarm record.

[0012] Optionally, the fault data includes a fault name.

[0013] Optionally, determining a diagnostic condition corresponding to the fault data in the pre-charge fault record, and determining target signal data corresponding to the diagnostic condition from the plurality of signal data, includes:

[0014] Determining a diagnostic condition corresponding to the fault name;

[0015] performing a data cleaning operation on the plurality of signal data to remove null values ​​and duplicate values ​​in the plurality of signal data to obtain cleaned signal data;

[0016] Target signal data corresponding to the diagnostic condition is determined from the cleaned signal data.

[0017] Optionally, the fault data includes the fault time, and the signal data includes the pre-charge time.

[0018] Optionally, determining target signal data corresponding to the diagnostic condition in the cleaned signal data includes:

[0019] First signal data whose pre-charge moment is before the fault moment and within a first preset time period is determined in the cleaned signal data, wherein the target signal data includes the first signal data.

[0020] Optionally, the signal data also includes a pre-charge signal.

[0021] Optionally, performing pre-charge fault diagnosis according to the target signal data includes:

[0022] determining whether the precharge signal in the first signal data is a first signal;

[0023] If not, a diagnosis result is generated that the pre-charge fault record is a false alarm record.

[0024] Optionally, the method further includes:

[0025] If the pre-charge signal is the first signal, determining a time at which the pre-charge signal is sent;

[0026] Determining, from the plurality of signal data, second signal data whose pre-charge time is after the issuing time and within a second preset time period, wherein the target signal data also includes the second signal data;

[0027] Pre-charge fault diagnosis is performed based on the second signal data.

[0028] Optionally, the signal data also includes a pre-charge current.

[0029] Optionally, performing pre-charge fault diagnosis according to the second signal data includes:

[0030] determining whether a variation range of the pre-charge current in the second signal data decreases from a first current value to a second current value, wherein the first current value is greater than the second current value;

[0031] If so, a diagnosis result is generated that the pre-filling fault record is a true alarm record; if not, a diagnosis result is generated that the pre-filling fault record is a false alarm record.

[0032] Optionally, generating the pre-charge fault record as a diagnosis result of a real alarm record includes:

[0033] Determine the maintenance measures corresponding to the fault name;

[0034] Generate a diagnostic result including the maintenance measures and the pre-charge fault record being a real alarm record.

[0035] In a second aspect, an embodiment of the present disclosure provides a pre-charge fault diagnosis device, the device comprising:

[0036] an acquisition part configured to acquire a pre-charging fault record of a vehicle and a plurality of signal data of the vehicle before and after the pre-charging fault record is generated, wherein the pre-charging fault record is generated when a fault is detected by the vehicle during the pre-charging process;

[0037] a determining part configured to determine a diagnostic condition corresponding to the fault data in the pre-charge fault record, and determine target signal data corresponding to the diagnostic condition from the plurality of signal data, wherein the target signal data is battery data;

[0038] The diagnosis part is configured to perform pre-charge fault diagnosis based on the target signal data to diagnose whether the pre-charge fault record is a false alarm record.

[0039] Optionally, determine the following configuration:

[0040] Determining a diagnostic condition corresponding to the fault name;

[0041] performing a data cleaning operation on the plurality of signal data to remove null values ​​and duplicate values ​​in the plurality of signal data to obtain cleaned signal data;

[0042] Target signal data corresponding to the diagnostic condition is determined from the cleaned signal data.

[0043] Optionally, the fault data in the device includes the fault time, and the signal data includes the pre-charge time.

[0044] Optionally, determine the following configuration:

[0045] First signal data whose pre-charge moment is before the fault moment and within a first preset time period is determined in the cleaned signal data, wherein the target signal data includes the first signal data.

[0046] Optionally, the signal data in the device also includes a pre-charge signal.

[0047] Optionally, the diagnostics section can be configured as follows:

[0048] determining whether the precharge signal in the first signal data is a first signal;

[0049] If not, a diagnosis result is generated that the pre-charge fault record is a false alarm record.

[0050] Optionally, the diagnostics section can be configured as follows:

[0051] If the pre-charge signal is the first signal, determining a time at which the pre-charge signal is sent;

[0052] Determining, from the plurality of signal data, second signal data whose pre-charge time is after the issuing time and within a second preset time period, wherein the target signal data also includes the second signal data;

[0053] Pre-charge fault diagnosis is performed based on the second signal data.

[0054] Optionally, the signal data in the device also includes a pre-charge current.

[0055] Optionally, the diagnostics section can be configured as follows:

[0056] determining whether a variation range of the pre-charge current in the second signal data decreases from a first current value to a second current value, wherein the first current value is greater than the second current value;

[0057] If so, a diagnosis result is generated that the pre-filling fault record is a true alarm record; if not, a diagnosis result is generated that the pre-filling fault record is a false alarm record.

[0058] Optionally, the diagnostics section can be configured as follows:

[0059] Determine the maintenance measures corresponding to the fault name;

[0060] Generate a diagnostic result including the maintenance measures and the pre-charge fault record being a real alarm record.

[0061] In a third aspect, an embodiment of the present disclosure provides an electronic device, including:

[0062] Memory;

[0063] processor; and

[0064] computer programs;

[0065] The computer program is stored in the memory and is configured to be executed by the processor to implement the pre-charge fault diagnosis method as described above.

[0066] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the pre-charge fault diagnosis method as described above when the computer program is executed by a processor.

[0067] An embodiment of the present disclosure provides a pre-charging fault diagnosis method, comprising: obtaining a pre-charging fault record of a vehicle and a plurality of signal data of the vehicle before and after the pre-charging fault record is generated, wherein the pre-charging fault record is generated when the vehicle detects a fault during the pre-charging process; determining the diagnostic conditions corresponding to the fault data in the pre-charging fault record, and determining target signal data corresponding to the diagnostic conditions in the plurality of signal data, wherein the target signal data is battery data; performing pre-charging fault diagnosis based on the target signal data to diagnose whether the pre-charging fault record is a false alarm record. The method provided by the present disclosure can diagnose pre-charging faults, ensure the safe operation of the battery system, and improve the safety of electric vehicles. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0069] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0070] FIG1 is a schematic diagram of an application scenario provided by an embodiment of the present disclosure;

[0071] FIG2 is a flow chart of a pre-charge fault diagnosis method provided by an embodiment of the present disclosure;

[0072] FIG3 is a flow chart of another pre-charge fault diagnosis method provided by an embodiment of the present disclosure;

[0073] FIG4 is a schematic diagram of an interface provided by an embodiment of the present disclosure;

[0074] FIG5 is a flow chart of another pre-charge fault diagnosis method provided by an embodiment of the present disclosure;

[0075] FIG6 is a schematic structural diagram of a pre-charge fault diagnosis device provided by an embodiment of the present disclosure;

[0076] FIG7 is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0077] In order to be able to more clearly understand the above-mentioned purposes, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure. All other embodiments obtained by those of ordinary skill in the art without making creative work are within the scope of protection of this application. It should be noted that, in the absence of conflict, the embodiments of the present disclosure and the features in the embodiments can be combined with each other.

[0078] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0079] With the rapid development of the electric vehicle industry and the increasing number of electric vehicles on the road, the safety of the battery system, a crucial component of electric vehicles, is of paramount importance. Therefore, for the sake of battery system safety, a pre-charge process is necessary during the power-on process. The reasons for pre-charging are as follows: 1. To ensure the proper operation of the main circuit contactors in the battery system; 2. To protect high-voltage loads from direct input, thereby preventing components in the battery system from being damaged by high-voltage transient currents.

[0080] Furthermore, in the actual operation of electric vehicles, power batteries are prone to serious faults such as pre-charge timeouts during use, which can even cause the vehicle to stall. Stalling occurs when a vehicle stops functioning due to a fault, seriously threatening the owner's safety and the vehicle's brand. Currently, no effective method for diagnosing pre-charge-related faults has been found.

[0081] In response to the above technical problems, the embodiments of the present disclosure provide a pre-charging fault diagnosis method, which connects the real-time signal data and pre-charging fault records of the vehicle through a distributed publish-subscribe message system, such as the distributed message system Kafka. The fault records include fault data, which are generated by the fault monitoring component in the vehicle according to the inherent monitoring process based on the battery data. By analyzing the characteristics of the signal data before and after the pre-charging fault occurs in the vehicle, combined with the battery pack, such as the battery system, and the pre-charging circuit design principle, a fault diagnosis method is established, which can quickly realize the diagnosis of pre-charging faults, diagnose whether the pre-charging fault is a real fault or a false alarm, and give a diagnosis result. The diagnosis result can also include maintenance measures to facilitate subsequent after-sales personnel to quickly locate vehicle problems and reduce maintenance time and customer waiting time. It will be explained in detail through at least one of the following embodiments.

[0082] For example, refer to Figure 1, which is a schematic diagram of an application scenario provided by an embodiment of the present disclosure. The pre-charge fault diagnosis method can be executed by a vehicle or a server, specifically by an electronic control unit with a control decision-making function on the vehicle. A cloud system is set up on the server, and the cloud system is used to collect battery data of the vehicle. The battery data includes signal data and fault data, and the pre-charge fault is diagnosed through the battery data. For example, in one application scenario, as shown in Figure 1, the vehicle 11 transmits the collected battery data to the server 12, and the server 12 performs a pre-charge fault diagnosis on the vehicle 11 based on the battery data and gives a diagnosis result. In another application scenario, the vehicle 11 performs a pre-charge fault diagnosis based on the collected battery data and gives a diagnosis result. It can be understood that the pre-charge fault diagnosis method provided by the embodiment of the present disclosure is not limited to the several possible scenarios described above, and other feasible scenarios are not described here. The following embodiment is described in detail by taking the server receiving the real-time battery data of the vehicle to diagnose the pre-charge fault as an example.

[0083] FIG2 is a flow chart of a pre-charge fault diagnosis method provided by an embodiment of the present disclosure, which is applied to a server and specifically includes the following steps S210 to S230 as shown in FIG2 :

[0084] S210: Acquire a pre-charging fault record of a vehicle and a plurality of signal data of the vehicle before and after the pre-charging fault record is generated.

[0085] The pre-charging fault record is generated when a fault is detected during the pre-charging process of the vehicle.

[0086] Optionally, the pre-charge fault record includes fault data, the fault data is uploaded to the server by the vehicle through the first channel, and the signal data is uploaded to the server by the vehicle through the second channel.

[0087] It is understandable that the vehicle collects battery data in real time and uploads it to the server through the Kafka system. The battery data includes fault data and signal data. Fault data is such as warn_data, and signal data is such as signal_data. Fault data can also be understood as alarm data. It is understandable that the vehicle will upload signal data to the server in real time or periodically, and there will be a large amount of signal data in the server. When the vehicle detects a pre-charging fault during the pre-charging process, it will generate a fault record in real time and upload the fault record to the server. The fault data and signal data are uploaded separately using different upload channels. The two do not affect each other. The detection of a vehicle fault does not affect the upload of signal data. The pre-charging fault record includes fault data. The pre-charging fault record can be understood as the fault monitoring component configured in the vehicle generated by the battery data and its fixed logic. The flexibility and intelligence are relatively poor. The generated pre-charging fault record may have false alarms. Therefore, the fault data can be understood as the data detected by the vehicle itself and has not yet been diagnosed as a false alarm.

[0088] It is understandable that the server receives the pre-charging fault record transmitted by the vehicle, and at the same time obtains multiple signal data of the vehicle before and after the pre-charging fault record is generated from the large amount of signal data received. The multiple signal data can be all data within a preset time period before the fault record is generated. The preset time period can be determined according to user needs and is not limited here.

[0089] S220 , determining a diagnostic condition corresponding to the fault data in the pre-charge fault record, and determining target signal data corresponding to the diagnostic condition from the plurality of signal data.

[0090] Wherein, the target signal data is battery data.

[0091] It can be understood that, based on the above S210, the target signal data is determined among multiple signal data based on the fault data recorded in the pre-charge fault record. The target signal data refers to at least one signal data among the multiple signal data, that is, the number of target signal data is not unique.

[0092] The fault data includes a fault name.

[0093] Optionally, target signal data is determined, specifically by the following steps:

[0094] Determine a diagnostic condition corresponding to the fault name; perform a data cleaning operation on the multiple signal data to remove null values ​​and duplicate values ​​in the multiple signal data to obtain cleaned signal data; and determine target signal data corresponding to the diagnostic condition in the cleaned signal data.

[0095] It is understandable that the server pre-stores diagnostic conditions associated with the fault name. Different faults correspond to different diagnostic conditions. Specifically, a script package corresponding to the diagnostic condition, such as a jar package, can be created and uploaded to the Flink computing platform. This allows the script package to be used to determine the target signal data corresponding to the diagnostic condition in multiple signal data and to perform pre-fault diagnosis according to the diagnostic condition. The script package corresponding to the diagnostic condition contains the signal data, diagnostic logic, and sub-conditions required for diagnosis. Subsequently, the signal data is cleaned by removing null values, removing duplicate values, and other data cleaning operations to obtain cleaned signal data.

[0096] It is understandable that after the diagnosis condition is determined and the cleaning is completed, the target signal data that meets the diagnosis condition is determined from the multiple signal data after cleaning, that is, the signal data required to meet the diagnosis condition is determined.

[0097] The fault data includes the fault time, and the signal data includes the pre-charge time.

[0098] Optionally, determining the target signal data corresponding to the diagnostic condition in the cleaned signal data is specifically implemented by the following steps:

[0099] First signal data whose pre-charge moment is before the fault moment and within a first preset time period is determined in the cleaned signal data.

[0100] It is understandable that the fault data includes the fault time, the vehicle identification number (VIN) and the fault description, etc. The fault description includes the fault name. The fault time refers to the time when the vehicle detects a fault, which can also be understood as the time when the fault record is generated. Each vehicle has a unique identification code. The fault name refers to the name of the fault detected by the vehicle. For example, the fault name is that the pre-charging time is too long or it is a pre-charging timeout. The signal data includes monitoring data such as the pre-charging time, basic data, current, voltage and temperature. The pre-charging time refers to the time when the signal data is generated. Specifically, the vehicle can generate a signal data every millisecond, and the time of each millisecond is the pre-charging time included in the signal data. Determine all signal data whose pre-charging time is before the fault time and whose pre-charging time is within the first preset time period in the multiple signal data after cleaning as the first signal data. For example, all signal data whose pre-charging time is within 5 seconds before the fault time in the multiple signal data are used as the first signal data, wherein the target signal data includes the first signal data.

[0101] S230. Perform pre-charge fault diagnosis based on the target signal data to diagnose whether the pre-charge fault record is a false alarm record.

[0102] It can be understood that on the basis of the above S220, pre-charging fault diagnosis is performed according to the target signal data and the diagnostic conditions to generate a diagnostic result. The diagnostic result includes whether the pre-charging fault record generated by the vehicle's self-monitoring is a real fault record or a false alarm record, that is, after a fault record occurs, it is diagnosed whether the fault record is a false alarm.

[0103] Wherein, the signal data also includes a pre-charge signal.

[0104] Optionally, the pre-charge fault diagnosis is performed based on the target signal data, and is specifically implemented by the following steps:

[0105] Determine whether the pre-charge signal in the first signal data is the first signal; if not, generate a diagnosis result that the pre-charge fault record is a false alarm record.

[0106] It is understandable that the following embodiments are explained using the fault name of "pre-charging time is too long" as an example. For example, the pre-charging time set for the vehicle is 500ms. The pre-charging time is fixed and has poor flexibility. If it is detected that the vehicle has not completed pre-charging for more than 500ms, the vehicle will generate a pre-charging fault record of too long pre-charging time, which is used to prompt the vehicle that a pre-charging fault may occur. However, there is a possibility that the pre-charging fault record is a false alarm. Among them, the diagnostic condition corresponding to the pre-charging time being too long includes two sub-conditions, which are respectively recorded as sub-condition A and sub-condition B. If the target signal data satisfies both sub-condition A and sub-condition B, it means that the vehicle has indeed had a pre-charging fault. If the target signal data does not meet any of the sub-conditions A and sub-condition B, it means that the vehicle has not had a pre-charging fault and the pre-charging fault record is a false alarm.

[0107] It is understandable that the signal data includes a pre-charge signal such as F_PreChgRelaySts. The pre-charge signal can be understood as a signal of whether to pre-charge. The vehicle will only pre-charge if the pre-charge signal is given. If the pre-charge signal is not given, pre-charging will not be performed, and there will be no pre-charging fault due to the pre-charging time being too long. Specifically, sub-condition A is whether the pre-charge signal included in the signal data is the first signal. The first signal can be 1, 1 means closed, that is, the battery pre-charge instruction has been issued, and 0 means open, that is, the pre-charging instruction has not been issued. For example, the large amount of signal data received 5s before the fault moment includes: first signal data, one signal data is generated every millisecond, and the signal data is sent to the server in batches once every second. Whether there is at least one signal data in the large amount of signal data with a pre-charge signal of 1. Specifically, if there is at least one signal data in the first signal data including a pre-charging signal that is a first signal, it means that a pre-charging instruction has been issued to the vehicle. In this case, continue to diagnose whether the target signal data meets sub-condition B; if there is no signal data in the first signal data including a pre-charging signal that is a first signal, it means that no pre-charging instruction has been issued to the vehicle. In this case, there is no need to diagnose whether the target signal data meets sub-condition B, and a diagnostic result that the pre-charging fault record is a false alarm record can be directly generated, that is, the vehicle will not be pre-charged if no pre-charging instruction is issued, and thus there will be no pre-charging timeout or pre-charging time being too long.

[0108] The embodiment of the present disclosure provides a pre-charging fault diagnosis method, which obtains the vehicle's pre-charging fault record and multiple signal data collected by the vehicle before and after the pre-charging fault record is generated. The fault data in the pre-charging fault record includes the fault name, and the diagnostic condition corresponding to the fault name is determined. Based on the fault moment in the fault data, the target signal data that meets the diagnostic condition is determined in the multiple signal data, that is, whether each signal data meets the diagnostic condition, and generates a diagnostic result to determine whether the pre-charging fault record is a false alarm record. The method provided by the present disclosure can quickly realize the diagnosis of pre-charging faults, reduce false alarm fault records, improve the accuracy of pre-charging fault diagnosis, and further improve vehicle safety by analyzing the characteristics of the signal data before and after the pre-charging fault occurs in the vehicle and the design principle of the pre-charging circuit.

[0109] Based on the above embodiment, FIG3 is a flow chart of another pre-charge fault diagnosis method provided by an embodiment of the present disclosure. Optionally, if at least one signal data in the first signal data includes a pre-charge signal that is a first signal, that is, a pre-charge instruction is issued, it is necessary to continue to diagnose whether the target signal data meets sub-condition B, specifically including the following steps S310 to S330 as shown in FIG3 :

[0110] S310: If the pre-charge signal is the first signal, determine a time point for sending the pre-charge signal.

[0111] It is understandable that if the pre-charging signal is the first signal, it means that sub-condition A is met. In this case, the time of issuing the pre-charging signal is determined. The time of issuing refers to the time when the vehicle issues a pre-charging instruction. If the pre-charging signals included in the first signal data are all first signals, any first signal data can be selected to determine the time of issuing the pre-charging signal. That is to say, the time of issuing the pre-charging signal is fixed, and the time of issuing the pre-charging signal recorded in each signal data is the same.

[0112] S320: Determine, from the plurality of signal data, second signal data whose pre-charge time is after the sending time and within a second preset time period.

[0113] It is understood that, based on the above S310, after determining the issuance time of the pre-fill signal, all signal data whose pre-fill time is after the issuance time and within a second preset time period are determined from the multiple signal data. All signal data are recorded as second signal data. The second preset time period can be 100 ms, wherein the target signal data also includes the second signal data. It is understood that pre-fill fault diagnosis can be performed after obtaining all signal data corresponding to the diagnostic conditions from the multiple signal data. For example, the first signal data corresponding to sub-condition A and the second signal data corresponding to sub-condition B can be directly determined, and then pre-fill fault diagnosis can be performed based on the first and second signal data, that is, determining whether the first and second signal data meet sub-conditions A and B. Alternatively, after determining the signal data corresponding to a sub-condition of the diagnostic condition, whether the signal data meets the sub-condition can be determined. For example, after determining the first signal data corresponding to sub-condition A, whether the first signal data meets sub-condition A can be determined. If not, the second signal data corresponding to sub-condition B can be determined. If it meets, the second signal data corresponding to sub-condition B can be calculated to determine whether the second signal data meets sub-condition B. Specifically, the method of determining the target signal data corresponding to the diagnostic condition is not limited and can be determined according to user needs, and will not be described in detail here.

[0114] S330: Perform pre-charge fault diagnosis according to the second signal data.

[0115] It is understandable that, based on the above S320, after the first signal data satisfies sub-condition A, it is determined based on the determined second signal data whether it satisfies sub-condition B to complete the diagnosis of whether the pre-charge fault record is a false alarm record.

[0116] Wherein, the signal data also includes pre-charge current.

[0117] Optionally, the pre-charge fault diagnosis is performed according to the second signal data in S330, which is specifically implemented by the following steps:

[0118] Determine whether the variation range of the pre-charge current in the second signal data drops from a first current value to a second current value, wherein the first current value is greater than the second current value; if so, generate a diagnosis result that the pre-charge fault record is a true alarm record; if not, generate a diagnosis result that the pre-charge fault record is a false alarm record.

[0119] It is understandable that the signal data also includes pre-charge current, which refers to the main circuit current in the battery system. It is determined whether the variation range of the pre-charge current included in the second signal data drops from the first current value to close to the second current value, wherein the first current value refers to the initial current value, which is related to the data of the vehicle model and is a fixed pre-charge current value that can be directly obtained. For example, the pre-charge current value is 100A and the second current value is 0A, that is, based on the second signal data, it is determined whether the main circuit current changes within the range of 100ms: whether it drops from 100A to close to 0A. If so, it means that the vehicle does have a pre-charge fault, and the generation of a pre-charge fault record is the diagnostic result of a real alarm record. If not, it means that the vehicle has been pre-charged for too long due to other reasons, and the pre-charge is still in progress and has not been completed. The generation of a pre-charge fault record is the diagnostic result of a false alarm record, and then the pre-charge is completed, but the pre-charge has timed out.

[0120] Optionally, the first current value may also be achieved by the following steps:

[0121] Obtain battery information of the vehicle, the battery information including a total voltage, a pre-charge resistance, and a total internal resistance; and calculate the first current value based on the total voltage and a sum of the pre-charge resistance and the total internal resistance.

[0122] It can be understood that the first current value is calculated by the total voltage of the battery system and the sum of the total pre-charge resistance and the total internal resistance, as shown in the following formula 1:

[0123] I_car_begin = V_total_packet / (R_precharge + R_total_packet) Formula 1

[0124] Where I_car_begin is the first current value, R_precharge is the precharge resistance value, for example, R_precharge is 300 ohms, V_packtotal is the total voltage of the battery pack, and R_packtotal is the total internal resistance of the battery pack. V_packtotal, R_precharge, and R_packtotal can all be directly obtained.

[0125] Optionally, the above-mentioned generation of the pre-charge fault record is a diagnosis result of a real alarm record, which is specifically achieved through the following steps:

[0126] Determine a maintenance measure corresponding to the fault name; and generate a diagnosis result including the maintenance measure and that the pre-charge fault record is a real alarm record.

[0127] It is understandable that after determining that the pre-charging fault record is a real alarm record, that is, after determining that the vehicle has a real fault, the maintenance measures and fault causes corresponding to the fault name are determined. The server pre-stores the fault name, the diagnostic conditions corresponding to the fault name, and the maintenance measures that also correspond to the fault name. For example, the fault name is that the pre-charging time is too long, the fault cause is the pre-charging resistor and relay failure, the fault cause can also be the pre-charging resistor or relay failure, the maintenance measure is to replace the pre-charging resistor and relay, the maintenance measure can also be to replace the pre-charging resistor or relay, and generate a diagnostic result of a real alarm record including the fault cause, fault name and maintenance measures. At the same time, the diagnostic result can also be returned to the vehicle to remind the user that the vehicle has a real pre-charging fault and to perform repairs in time.

[0128] For example, see Figure 4, which is a schematic diagram of an interface provided by an embodiment of the present disclosure, specifically an interface display diagram of the diagnosis result. The interface display diagram includes matters, vehicle identification code, alarm time, alarm name, fault cause and maintenance suggestions. The matter is "fault diagnosis", the vehicle identification code is used to locate the vehicle, the alarm time is also the fault time, the alarm name or fault name is "pre-charging time is too long", the fault cause includes "pre-charging resistor and relay fault", "pre-charging resistor or relay fault", and the maintenance suggestions or maintenance measures include "replace pre-charging resistor and relay", "replace pre-charging resistor or relay". The diagnosis result is sent to the vehicle according to the vehicle identification code, and the vehicle can display the interface diagram of Figure 4 to remind the user that the vehicle has a pre-charging fault and needs timely maintenance.

[0129] An embodiment of the present disclosure provides a pre-charging fault diagnosis method, in which, when the pre-charging signal included in the first signal data is the first signal, that is, under the premise that the pre-charging instruction has been issued to the vehicle, the issuance time of the pre-charging signal is determined, and then, in multiple signal data, all signal data with the pre-charging time after the issuance time and within a second preset time period are used as second signal data, and based on the design principle of the pre-charging main circuit, it is judged whether the variation range of the pre-charging current in the second signal data decreases from the first current value or approaches the second current value. If so, it means that a real fault has occurred in the vehicle, and a diagnosis result is generated that the pre-charging fault record is a real fault record. If not, it means that no pre-charging fault has occurred in the vehicle, and a diagnosis result is generated that the pre-charging fault record is a false alarm record. The pre-charging fault record can be diagnosed quickly to determine whether it is a de-alarm, thereby improving the accuracy of the pre-charging fault diagnosis, facilitating subsequent maintenance personnel to quickly identify the cause of the fault, reducing maintenance time and user waiting time, and improving user experience.

[0130] Based on the above embodiment, FIG5 is a flow chart of another pre-charge fault diagnosis method provided by an embodiment of the present disclosure, which is applied to a server and specifically includes the following steps S510 to S580 as shown in FIG5 :

[0131] S510: Acquire vehicle fault data and multiple signal data.

[0132] S520: Match the fault data with the plurality of signal data according to the vehicle identification code.

[0133] It is understandable that the server will receive a large amount of signal data and battery data uploaded by vehicles, so it can filter out multiple signal data of the target vehicle according to the vehicle identification code, and match the fault data with multiple signal data to conduct subsequent diagnosis on whether the pre-charging fault record is a false alarm.

[0134] S530: Determine a diagnosis condition according to the fault name in the fault data.

[0135] S540 : Based on the fault time in the fault data, determine target signal data corresponding to the diagnostic condition from the matched plurality of signal data.

[0136] S550: Perform pre-charge fault diagnosis based on the target signal data to determine whether the diagnosis conditions are met.

[0137] Understandably, if not, execute S560; if so, execute S570.

[0138] S560: Generate a diagnosis result of a false alarm.

[0139] S570. Determine maintenance measures based on the fault name.

[0140] S580: Generate a diagnosis result of the actual fault including maintenance measures.

[0141] It is understandable that the specific implementation description of S510 to S580 can be found in the above embodiment and will not be repeated here.

[0142] FIG6 is a schematic diagram of the structure of a pre-fill fault diagnosis device provided in an embodiment of the present disclosure. The pre-fill fault diagnosis device provided in an embodiment of the present disclosure can execute the processing flow provided in the above-mentioned pre-fill fault diagnosis method embodiment. As shown in FIG6 , the pre-fill fault diagnosis device 600 includes an acquisition part 610, a determination part 620, and a diagnosis part 630, wherein:

[0143] An acquisition section 610 is configured to acquire a pre-charging fault record of a vehicle and a plurality of signal data of the vehicle before and after the pre-charging fault record is generated, wherein the pre-charging fault record is generated when a fault is detected by the vehicle during the pre-charging process;

[0144] a determining portion 620 configured to determine a diagnostic condition corresponding to the fault data in the pre-charge fault record, and to determine target signal data corresponding to the diagnostic condition from the plurality of signal data, wherein the target signal data is battery data;

[0145] The diagnosis part 630 is configured to perform pre-charge fault diagnosis based on the target signal data to diagnose whether the pre-charge fault record is a false alarm record.

[0146] Optionally, the fault data in the device 600 includes a fault name.

[0147] Optionally, the determining portion 620 is configured as follows:

[0148] Determining a diagnostic condition corresponding to the fault name;

[0149] performing a data cleaning operation on the plurality of signal data to remove null values ​​and duplicate values ​​in the plurality of signal data to obtain cleaned signal data;

[0150] Target signal data corresponding to the diagnostic condition is determined from the cleaned signal data.

[0151] Optionally, the fault data in the device 600 includes the fault time, and the signal data includes the pre-charge time.

[0152] Optionally, the determining portion 620 is configured as follows:

[0153] First signal data whose pre-charge moment is before the fault moment and within a first preset time period is determined in the cleaned signal data, wherein the target signal data includes the first signal data.

[0154] Optionally, the signal data in the device 600 also includes a pre-charge signal.

[0155] Optionally, the diagnosis portion 630 is configured to:

[0156] determining whether the precharge signal in the first signal data is a first signal;

[0157] If not, a diagnosis result is generated that the pre-charge fault record is a false alarm record.

[0158] Optionally, the diagnosis portion 630 is configured to:

[0159] If the pre-charge signal is the first signal, determining a time at which the pre-charge signal is sent;

[0160] Determining, from the plurality of signal data, second signal data whose pre-charge time is after the issuing time and within a second preset time period, wherein the target signal data also includes the second signal data;

[0161] Pre-charge fault diagnosis is performed based on the second signal data.

[0162] Optionally, the signal data in the device 600 also includes a pre-charge current.

[0163] Optionally, the diagnosis portion 630 is configured to:

[0164] determining whether a variation range of the pre-charge current in the second signal data decreases from a first current value to a second current value, wherein the first current value is greater than the second current value;

[0165] If so, a diagnosis result is generated that the pre-filling fault record is a true alarm record; if not, a diagnosis result is generated that the pre-filling fault record is a false alarm record.

[0166] Optionally, the diagnosis portion 630 is configured to:

[0167] Determine the maintenance measures corresponding to the fault name;

[0168] Generate a diagnostic result including the maintenance measures and the pre-charge fault record being a real alarm record.

[0169] The pre-charge fault diagnosis device of the embodiment shown in FIG6 can be used to implement the technical solution of the above-mentioned method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0170] FIG7 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure. Referring specifically to FIG7 below, it shows a schematic diagram of the structure of an electronic device 700 suitable for implementing the embodiment of the present disclosure. The electronic device 700 in the embodiment of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (PADs), portable multimedia players (PMPs), in-vehicle terminals such as in-vehicle navigation terminals, wearable electronic devices, and the like, as well as fixed terminals such as digital TVs, desktop computers, smart home devices, and the like. The electronic device shown in FIG7 is merely an example and should not impose any limitations on the functions and scope of use of the embodiment of the present disclosure.

[0171] As shown in FIG7 , the electronic device 700 may include a processing device 701 such as a central processing unit (CPU), a graphics processing unit (GPU), etc., which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703 to implement the pre-charge fault diagnosis method according to the embodiment of the present disclosure. Various programs and data required for the operation of the electronic device 700 are also stored in the RAM 703. The processing device 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input I or output O interface 705 is also connected to the bus 704.

[0172] Typically, the following devices may be connected to the I / O interface 705: an input device 706 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 707 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; a storage device 708 including, for example, a magnetic tape, hard disk, etc.; and a communication device 709. The communication device 709 may allow the electronic device 700 to communicate with other devices wirelessly or by wire to exchange data. Although FIG. 7 illustrates the electronic device 700 with various devices, it should be understood that not all of the illustrated devices are required to be implemented or present. More or fewer devices may alternatively be implemented or present.

[0173] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart, thereby implementing the pre-charge fault diagnosis method as described above. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 709, or installed from the storage device 708, or installed from the ROM 702. When the computer program is executed by the processing device 701, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0174] It should be noted that the computer-readable medium described above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. Computer-readable storage media may include, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or components, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or flash memory, optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. This propagated data signal may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or convey a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code embodied on the computer-readable medium may be conveyed using any suitable medium, including but not limited to wires, optical cables, radio frequency (RF), or any suitable combination thereof.

[0175] In some embodiments, the client and server may communicate using any currently known or future developed network protocol, such as the HyperText Transfer Protocol (HTTP), and may be interconnected with any form or medium of digital data communication, such as a communication network. Examples of communication networks include local area networks (LANs), wide area networks (WANs), internets such as the Internet, and peer-to-peer networks such as ad hoc peer-to-peer networks, as well as any currently known or future developed networks.

[0176] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0177] Optionally, when the above one or more programs are executed by the electronic device, the electronic device may also execute other steps described in the above embodiments.

[0178] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer: for example, through the Internet using an Internet service provider.

[0179] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or part of the code, and the module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and flowchart, each box in the block diagram or flowchart, the combination of boxes in the block diagram and flowchart, and the combination of boxes in the block diagram or flowchart can be implemented using a dedicated hardware-based system that performs the specified function or operation, or can be implemented using a combination of dedicated hardware and computer instructions.

[0180] The units involved in the embodiments described in this disclosure may be implemented in software or hardware, wherein the name of a unit does not necessarily limit the unit itself.

[0181] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0182] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or apparatus. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing. More specific examples of machine-readable storage media may include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory RAM, a read-only memory ROM, an erasable programmable read-only memory such as an EPROM or flash memory, an optical fiber, a portable compact disk read-only memory CD-ROM, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0183] It should be noted that, in this article, relational terms such as "first" and "second" are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or pre-charge fault diagnosis method that includes a series of elements includes not only those elements, but also other elements that are not explicitly listed, or also includes elements that are inherent to such process, method, article or pre-charge fault diagnosis method. In the absence of further restrictions, the elements defined by the sentence "including a..." do not exclude the presence of other identical elements in the process, method, article or pre-charge fault diagnosis method that includes the elements.

[0184] The foregoing description is intended only to provide specific embodiments of the present disclosure, intended to enable those skilled in the art to understand and implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the embodiments described herein, but rather to be construed in the broadest manner consistent with the principles and novel features disclosed herein. Industrial Applicability

[0185] The embodiments of the present application provide a pre-charging fault diagnosis method, apparatus, equipment and medium, the pre-charging fault diagnosis method comprising: obtaining a pre-charging fault record of a vehicle and a plurality of signal data of the vehicle before and after the pre-charging fault record is generated, wherein the pre-charging fault record is generated when the vehicle detects a fault during the pre-charging process; determining the diagnostic condition corresponding to the fault data in the pre-charging fault record, and determining the target signal data corresponding to the diagnostic condition in the plurality of signal data, wherein the target signal data is battery data; performing pre-charging fault diagnosis based on the target signal data to diagnose whether the pre-charging fault record is a false alarm record. The implementation scheme using the above method can diagnose pre-charging faults, ensure the safe operation of the battery system, and improve the safety of electric vehicles.

Claims

1. A pre-charge fault diagnosis method, the method comprising: Acquire a pre-charging fault record of a vehicle and a plurality of signal data of the vehicle before and after the pre-charging fault record is generated, wherein the pre-charging fault record is generated when a fault is detected by the vehicle during the pre-charging process; Determine a diagnostic condition corresponding to the fault data in the pre-charge fault record, and determine target signal data corresponding to the diagnostic condition from the plurality of signal data, wherein the target signal data is battery data; Pre-charging fault diagnosis is performed based on the target signal data to diagnose whether the pre-charging fault record is a false alarm record.

2. The method according to claim 1, wherein: The fault data includes a fault name, and the determining of a diagnostic condition corresponding to the fault data in the pre-charge fault record and determining target signal data corresponding to the diagnostic condition from the plurality of signal data includes: Determine the diagnostic condition corresponding to the fault name; Performing a data cleaning operation on the plurality of signal data to remove null values ​​and duplicate values ​​in the plurality of signal data to obtain cleaned signal data; Target signal data corresponding to the diagnostic condition is determined in the cleaned signal data.

3. The method according to claim 2, wherein: The fault data also includes the fault time, the signal data includes the pre-charge time, and the target signal data corresponding to the diagnostic condition is determined in the signal data after cleaning, including: The first signal data whose pre-charging moment is before the fault moment and within a first preset time period is determined in the cleaned signal data, wherein the target signal data includes the first signal data.

4. The method according to claim 3, wherein: The signal data further includes a pre-charge signal, and the pre-charge fault diagnosis is performed according to the target signal data, including: determining whether the precharge signal in the first signal data is a first signal; If not, a diagnosis result is generated that the pre-charging fault record is a false alarm record.

5. The method according to claim 4, wherein: The method further comprises: If the pre-charge signal is the first signal, determining a time of sending the pre-charge signal; Determine, from the plurality of signal data, second signal data whose pre-charging time is after the issuing time and within a second preset time period, wherein the target signal data also includes the second signal data; Pre-charge fault diagnosis is performed based on the second signal data.

6. The method according to claim 5, wherein: The signal data further includes a pre-charge current, and the pre-charge fault diagnosis is performed according to the second signal data, including: Determine whether the variation range of the pre-charge current in the second signal data decreases from a first current value to a second current value, wherein the first current value is greater than the second current value; If so, a diagnosis result is generated that the pre-filling fault record is a true alarm record; if not, a diagnosis result is generated that the pre-filling fault record is a false alarm record.

7. The method according to claim 6, wherein: The generating of the pre-charging fault record is a diagnostic result of a real alarm record, including: Determine the maintenance measures corresponding to the fault name; Generate a diagnostic result including the maintenance measures and the pre-charge fault record which is a real alarm record.

8. A pre-charge fault diagnosis device, the device comprising: an acquisition part, configured to acquire a pre-charging fault record of a vehicle and a plurality of signal data of the vehicle before and after the pre-charging fault record is generated, wherein the pre-charging fault record is generated when a fault is detected by the vehicle during the pre-charging process; a determination part configured to determine a diagnosis condition corresponding to the fault data in the pre-charge fault record, and determine target signal data corresponding to the diagnosis condition from among the plurality of signal data, wherein the target signal data is battery data; The diagnosis part is configured to perform pre-charge fault diagnosis based on the target signal data to diagnose whether the pre-charge fault record is a false alarm record.

9. An electronic device, comprising: Memory; processor; as well as Computer programs; Wherein, the computer program is stored in the memory and is configured to be executed by the processor to implement the pre-charge fault diagnosis method as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the pre-charge fault diagnosis method as claimed in any one of claims 1 to 7.

Images