Pre-charging fault diagnosis method and device, equipment and medium

Abstract

The invention relates to a pre-charging fault diagnosis method, device, equipment and medium, and the pre-charging fault diagnosis method comprises the steps: 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, and the pre-charging fault record is generated when the vehicle monitors a fault in a pre-charging process; a diagnosis condition corresponding to fault data in the pre-charging fault record is determined, target signal data corresponding to the diagnosis condition is determined in the multiple pieces of signal data, and the target signal data is battery data; and performing pre-charging fault diagnosis according to the target signal data to diagnose whether the pre-charging fault record is a false alarm record. According to the method provided by the invention, the pre-charging fault can be diagnosed, the safe operation of the battery system is ensured, and the safety of the electric vehicle is improved.

Description

Technical Field

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

[0002] With the rapid development of the electric vehicle industry, the number of electric vehicles is increasing. As an important part of electric vehicles, the safety of the battery system is particularly important. The power battery power-on process must have a pre-charging process to protect the main circuit contactor from normal operation and to protect the high-voltage load from being burned out by the high-voltage instantaneous current directly input.

[0003] During the pre-charging process, the power battery may experience serious faults such as pre-charging timeout due to external factors such as weather and internal factors such as hardware damage such as chargers, charging ports, charging cables, and charging piles. This may even cause the vehicle to break down, posing a threat to the user's personal safety. Therefore, in order to ensure the safe operation of the battery system and improve the safety of electric vehicles, it is crucial to diagnose pre-charging faults. Summary of the invention

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

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

[0006] 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;

[0007] 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;

[0008] 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.

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

[0010] Optionally, the 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:

[0011] Determine a diagnostic condition corresponding to the fault name;

[0012] 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;

[0013] Target signal data corresponding to the diagnostic condition is determined in the cleaned signal data.

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

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

[0016] The first signal data whose pre-charging time is before the fault time and within a first preset time period is determined in the signal data after cleaning, wherein the target signal data includes the first signal data.

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

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

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

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

[0021] Optionally, the method further includes:

[0022] If the pre-charge signal is the first signal, determining a time of sending the pre-charge signal;

[0023] 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;

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

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

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

[0027] 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;

[0028] 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.

[0029] Optionally, the generating of the pre-charging fault record is a diagnosis result of a real alarm record, including:

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

[0031] Generate a diagnostic result including the maintenance measures and the pre-charge fault record which is a real alarm record.

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

[0033] An acquisition module, used 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;

[0034] a determination module, configured to determine a diagnosis condition corresponding to the fault data in the pre-charging 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;

[0035] The diagnosis module is used to perform pre-charging fault diagnosis according to the target signal data to diagnose whether the pre-charging fault record is a false alarm record.

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

[0037] Memory;

[0038] Processor; and

[0039] Computer programs;

[0040] 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 above.

[0041] 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.

[0042] The embodiment of the present disclosure provides a pre-charging fault diagnosis method, including: 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 according to 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

[0043] 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.

[0044] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0045] Figure 1 A schematic diagram of an application scenario provided by an embodiment of the present disclosure;

[0046] Figure 2 A flowchart of a pre-charging fault diagnosis method provided by an embodiment of the present disclosure;

[0047] Figure 3 A flowchart of another pre-charging fault diagnosis method provided by an embodiment of the present disclosure;

[0048] Figure 4 A schematic diagram of an interface provided by an embodiment of the present disclosure;

[0049] Figure 5 A flowchart of another pre-charging fault diagnosis method provided by an embodiment of the present disclosure;

[0050] Figure 6 A schematic diagram of the structure of a pre-charging fault diagnosis device provided in an embodiment of the present disclosure;

[0051] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0052] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0053] 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.

[0054] With the rapid development of the electric vehicle industry, the number of electric vehicles is increasing. As an important part of electric vehicles, the safety of the battery system is particularly important. Therefore, for the safety of the battery system, the power battery must be pre-charged during the power-on process. The reasons for pre-charging are as follows: 1. To protect the normal operation of the main circuit contactor in the battery system; 2. To protect the high-voltage load from being directly input, so as to avoid the components in the battery system from being burned out due to high-voltage transient current.

[0055] In addition, in the actual operation of electric vehicles, the power battery is prone to serious faults such as pre-charge timeout during use, and even causes the vehicle to break down. Breakdown means that the vehicle stops working due to a fault, which seriously threatens the personal safety of the owner and the vehicle brand. At present, no good method for diagnosing pre-charge related faults has been found for this situation.

[0056] In view of the above technical problems, the embodiments of the present disclosure provide a method for diagnosing pre-charging faults. The real-time signal data and pre-charging fault records of the vehicle are connected through a distributed publish-subscribe message system (Kafka system). The fault records include fault data. The fault records are generated by the fault monitoring components 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, a fault diagnosis method is established in combination with the design principle of the pre-charging circuit of the battery pack (battery system). The method 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, which is convenient for subsequent after-sales personnel to quickly locate vehicle problems and reduce maintenance time and customer waiting time. It is described in detail through at least one of the following embodiments.

[0057] For example, see Figure 1 , Figure 1This 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 built on the server. The cloud system is used to collect battery data of the vehicle. The battery data includes signal data and fault data. The pre-charge fault is diagnosed through the battery data. For example, in an application scenario, Figure 1 As shown, the vehicle 11 transmits the collected battery data to the server 12, and the server 12 performs a pre-charging 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-charging fault diagnosis based on the collected battery data and gives a diagnosis result. It is understandable that the pre-charging 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 using the example of a server receiving real-time battery data of a vehicle to diagnose a pre-charging fault.

[0058] Figure 2 A flow chart of a pre-charging fault diagnosis method provided by an embodiment of the present disclosure, which is applied to a server, specifically includes the following steps: Figure 2 The following steps S210 to S230 are shown:

[0059] 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.

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

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

[0062] 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 (warn_data) and signal data (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 vehicle faults 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 internal 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.

[0063] It can be understood 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.

[0064] S220, determining a diagnostic condition corresponding to the fault data in the pre-charging fault record, and determining target signal data corresponding to the diagnostic condition from the multiple signal data.

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

[0066] It can be understood that, based on the above S210, 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.

[0067] The fault data includes a fault name.

[0068] Optionally, the target signal data is determined, which is specifically achieved through the following steps:

[0069] Determine the 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 the target signal data corresponding to the diagnostic condition in the cleaned signal data.

[0070] It is understandable that the diagnostic conditions associated with the fault name are pre-stored in the server, and different faults correspond to different diagnostic conditions. Specifically, a script package (jar package) corresponding to the diagnostic condition can be established, and the script package can be uploaded to the flink computing platform, so as to facilitate the subsequent determination of the target signal data corresponding to the diagnostic condition in multiple signal data based on the script package and pre-charge fault diagnosis according to the diagnostic condition, wherein the script package corresponding to the diagnostic condition sets the signal data, diagnostic logic, and sub-conditions required for diagnosis. Subsequently, the signal data is cleaned by data cleaning operations such as null value removal and duplicate value removal to obtain cleaned signal data.

[0071] It can be understood that after the diagnosis condition is determined and the cleaning is completed, the target signal data satisfying the diagnosis condition is determined from the multiple signal data after cleaning, that is, the signal data required to satisfy the diagnosis condition is determined.

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

[0073] Optionally, the above-mentioned determination of the target signal data corresponding to the diagnostic condition in the cleaned signal data is specifically implemented by the following steps:

[0074] The first signal data whose pre-charging time is before the fault time and within the first preset time period is determined in the signal data after cleaning.

[0075] It is understandable that the fault data includes the time of the fault, the vehicle identification number (Vehicle Identification Number, VIN) and the fault description (fault name), etc. The time of the fault 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 (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 taken as the first signal data, wherein the target signal data includes the first signal data.

[0076] S230. Perform pre-charging fault diagnosis according to the target signal data to diagnose whether the pre-charging fault record is a false alarm record.

[0077] 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.

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

[0079] Optionally, the pre-charging fault diagnosis is performed according to the target signal data, and is specifically implemented by the following steps:

[0080] 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.

[0081] It is understandable that the following embodiments are explained using the fault name of the pre-charging time being 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 to prompt that the vehicle may have a pre-charging fault, but the pre-charging fault record may be a false alarm. Among them, the diagnostic condition corresponding to the pre-charging time being too long includes two sub-conditions, 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 B, it means that the vehicle has not had a pre-charging fault and the pre-charging fault record is a false alarm.

[0082] It can be understood that the signal data includes a pre-charging signal (F_PreChgRelaySts), which can be understood as a signal of whether to pre-charge. Only when the pre-charging signal is given will the vehicle pre-charge. If the pre-charging signal is not given, pre-charging will not be performed, and there will be no pre-charging fault due to too long pre-charging time. Specifically, sub-condition A is whether the pre-charging signal included in the signal data is the first signal. The first signal is 1, 1 means closed, that is, the battery pre-charging instruction has been issued, and 0 means open, that is, the pre-charging instruction has not been issued. For example, among the large amount of signal data received 5s before the fault (first signal data, one signal data is generated every millisecond, and signal data is sent to the server in batches every second), whether there is at least one signal data with a pre-charging 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 in which the pre-charging signal is the 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 / pre-charging time too long fault.

[0083] 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 a fault name, and the diagnostic condition corresponding to the fault name is determined. Based on the fault time in the fault data, the target signal data that meets the diagnostic condition is determined in the multiple signal data, that is, it is determined whether each signal data meets the diagnostic condition, and a diagnostic result is generated 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 vehicle has a pre-charging fault and the design principle of the pre-charging circuit.

[0084] Based on the above embodiments, Figure 3 A flow chart of another pre-charge fault diagnosis method provided by an embodiment of the present disclosure, optionally, if there is at least one signal data in the first signal data including a pre-charge signal as the 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 Figure 3 The following steps S310 to S330 are shown:

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

[0086] It can be understood 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. In other words, 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.

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

[0088] It is understandable that, based on the above S310, after determining the time of issuing the pre-charge signal, all signal data whose pre-charge time is after the time of issuing and within the second preset time period are determined in the multiple signal data, and all signal data are recorded as second signal data, and the second preset time period can be 100ms, wherein the target signal data also includes the second signal data. It is understandable that, after obtaining all signal data corresponding to the diagnostic conditions in the multiple signal data, the pre-charge fault diagnosis can be performed, for example, the first signal data corresponding to the sub-condition A and the second signal data corresponding to the sub-condition B are directly determined, and then the pre-charge fault diagnosis is performed according to the first signal data and the second signal data, that is, whether the first signal data and the second signal data meet the sub-condition A and the sub-condition B. It is also possible to determine the signal data corresponding to a sub-condition in the diagnostic condition, and then determine whether the signal data meets the sub-condition. For example, after determining the first signal data corresponding to the sub-condition A, it is determined whether the first signal data meets the sub-condition A. If not, it is not necessary to determine the second signal data corresponding to the sub-condition B. If it is satisfied, the second signal data corresponding to the sub-condition B is calculated to determine whether the second signal data meets the 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 elaborated here.

[0089] S330. Perform pre-charging fault diagnosis according to the second signal data.

[0090] It can be understood 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-charging fault record is a false alarm record.

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

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

[0093] 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.

[0094] 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 range of change 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, which can be directly obtained. For example, the pre-charge current value is 100A, and the second current value is 0A, that is, according to 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 a long pre-charge time 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.

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

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

[0097] 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, see the following formula (1):

[0098] I_car_begin=V _包总 / (R _预充 +R _包总 )Formula (1)

[0099] Where, I_car_begin is the first current value, R _预充 is the pre-charge resistance, for example, R _预充 300 ohms, V _包总 is the total voltage of the battery pack, R _包总 is the total internal resistance of the battery pack, V _包总 , R _预充 and R _包总 Can be directly obtained.

[0100] Optionally, the above-mentioned generation of the pre-charging fault record is a diagnosis result of a real alarm record, which is specifically implemented by the following steps:

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

[0102] 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, and the server pre-stores the fault name, the diagnostic conditions that correspond one-to-one to the fault name, and the maintenance measures that also correspond one-to-one 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 / or relay failure, and the maintenance measure is to replace the pre-charging resistor and / or relay. A diagnostic result of a real alarm record including the fault cause, fault name and maintenance measures is generated, and 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.

[0103] For example, see Figure 4 , Figure 4 An interface diagram provided for 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 suggestion, 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 (fault name) is "pre-charge time is too long", the fault cause is "pre-charge resistor and / or relay fault", and the maintenance suggestion (maintenance measure) is "replace pre-charge resistor and / or relay". The diagnosis result is sent to the vehicle according to the vehicle identification code, and the vehicle can display Figure 4 The interface diagram is displayed to remind the user that the vehicle has a pre-charging fault and needs timely maintenance.

[0104] The disclosed embodiment 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 determined 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 troubleshoot the cause of the fault, reducing maintenance time and user waiting time, and improving user experience.

[0105] Based on the above embodiments, Figure 5A flow chart of another pre-charging fault diagnosis method provided by an embodiment of the present disclosure, which is applied to a server, specifically includes the following steps: Figure 5 The following steps S510 to S580 are shown:

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

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

[0108] Understandably, 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.

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

[0110] S540 . Determine target signal data corresponding to the diagnosis condition from a plurality of matched signal data based on the fault time in the fault data.

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

[0112] It is understandable that if not, execute S560; if so, execute S570.

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

[0114] S570. Determine maintenance measures according to the fault name.

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

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

[0117] Figure 6 The schematic diagram of the structure of the pre-filling fault diagnosis device provided in the embodiment of the present disclosure is as follows. The pre-filling fault diagnosis device provided in the embodiment of the present disclosure can execute the processing flow provided in the above-mentioned pre-filling fault diagnosis method embodiment, such as Figure 6 As shown, the pre-charge fault diagnosis device 600 includes an acquisition module 610, a determination module 620 and a diagnosis module 630, wherein:

[0118] An acquisition module 610 is used 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;

[0119] A determination module 620, configured to determine a diagnosis condition corresponding to the fault data in the pre-charging 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;

[0120] The diagnosis module 630 is used to perform pre-charging fault diagnosis according to the target signal data to diagnose whether the pre-charging fault record is a false alarm record.

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

[0122] Optionally, the determination module 620 is used to:

[0123] Determine a diagnostic condition corresponding to the fault name;

[0124] 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;

[0125] Target signal data corresponding to the diagnostic condition is determined in the cleaned signal data.

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

[0127] Optionally, the determination module 620 is used to:

[0128] The first signal data whose pre-charging time is before the fault time and within a first preset time period is determined in the signal data after cleaning, wherein the target signal data includes the first signal data.

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

[0130] Optionally, the diagnosis module 630 is used to:

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

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

[0133] Optionally, the diagnosis module 630 is used to:

[0134] If the pre-charge signal is the first signal, determining a time of sending the pre-charge signal;

[0135] 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;

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

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

[0138] Optionally, the diagnosis module 630 is used to:

[0139] 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;

[0140] 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.

[0141] Optionally, the diagnosis module 630 is used to:

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

[0143] Generate a diagnostic result including the maintenance measures and the pre-charge fault record which is a real alarm record.

[0144] Figure 6 The pre-charging fault diagnosis device of the illustrated embodiment can be used to execute the technical solution of the above-mentioned method embodiment. Its implementation principle and technical effect are similar and will not be repeated here.

[0145] Figure 7 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. Figure 7 , which 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, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle terminals (such as vehicle navigation terminals), wearable electronic devices, etc., and fixed terminals such as digital TVs, desktop computers, smart home devices, etc. Figure 7 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0146] like Figure 7As shown, the electronic device 700 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 701, 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 to a random access memory (RAM) 703 to implement the pre-charge fault diagnosis method of the embodiment described in the present disclosure. In RAM 703, various programs and data required for the operation of the electronic device 700 are also stored. The processing device 701, ROM 702, and RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0147] Typically, the following devices may be connected to the I / O interface 705: an input device 706 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 707 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 708 including, for example, a magnetic tape, a 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 Figure 7 The electronic device 700 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0148] 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 executed.

[0149] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with 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 (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 above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

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

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

[0152] 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.

[0153] 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 separate 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 (e.g., through the Internet using an Internet service provider).

[0154] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square 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 square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0155] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware, wherein the name of a unit does not, in some cases, limit the unit itself.

[0156] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, 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), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0157] 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 equipment. 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 equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (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.

[0158] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply 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 including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements 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 one..." do not exclude the presence of other identical elements in the process, method, article or pre-charge fault diagnosis method including the elements.

[0159] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be 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 will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A pre-charge fault diagnosis method, characterized in that: The method comprises: 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, characterized in that 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 a 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, characterized in that 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 time is before the fault time and within a first preset time period is determined in the signal data after cleaning, wherein the target signal data includes the first signal data.

4. The method according to claim 3, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that: The device comprises: An acquisition module, used 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 module, configured to determine a diagnosis condition corresponding to the fault data in the pre-charging 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 module is used to perform pre-charging fault diagnosis according to the target signal data to diagnose whether the pre-charging fault record is a false alarm record.

9. An electronic device, characterized in that: include: 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, characterized in that: When the computer program is executed by a processor, the steps of the pre-charge fault diagnosis method as described in any one of claims 1 to 7 are implemented.

Images