A method and system for predicting and maintaining charging facility faults
By acquiring operational data prior to the first anomaly in the charging facility, the formation process of latent faults can be identified and monitored, solving the problem of latent faults being missed in the charging facility and achieving more accurate fault prediction and operation and maintenance.
Patent Information
- Application Number
- CN202611618880.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-10-20
- Publication Date
- 2026-11-17
AI Technical Summary
In the fault prediction process of existing charging facilities, the first abnormality triggering protection action will stop the fault characterization process of other components, resulting in the omission of latent faults and the inability to accurately determine whether there are latent faults in components that have not yet formed a complete fault characterization.
By acquiring the operating data before the first anomaly triggers the protection action, the target operating conditions that caused the protection action to stop are determined, the associated components that have not yet formed a complete fault characterization are identified, and the response data is acquired when the verification conditions are met again after the first anomaly is handled, to determine the existence of latent faults.
It improves the accuracy of identifying latent faults, reduces the risk of missed detections due to protection actions, and ensures the correspondence between operation and maintenance information and actual fault status.
Smart Images

Figure CN123118079A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of charging facility condition monitoring technology, specifically a charging facility fault prediction and maintenance method and system. Background Technology
[0002] Existing charging facilities typically monitor the operating status of power modules, charging guns, output circuits, and insulation-related components by collecting operational data such as output voltage, output current, output power, component temperature, insulation status, and fault alarms. When a certain operating parameter first reaches the corresponding protection condition, the charging facility usually performs protective actions such as limiting the output current, reducing the output power, disconnecting the power module, or disconnecting the output circuit to prevent the abnormality from continuing to develop.
[0003] However, the fault characterization process of different components has different time characteristics. Some faults can form identifiable responses relatively quickly after an anomaly occurs, while some latent faults require continuous operation for a certain period under certain voltage, current, load, or temperature rise conditions before forming temperature rise, voltage drop, branch deviation, or insulation condition changes that can be used for fault judgment. When the first anomaly triggers the protection action early, the protection action not only suppresses the first anomaly but also changes the original operating conditions of other components, causing the formation process of the corresponding fault characterization to be stopped before the complete judgment conditions are reached.
[0004] For example, when a charging facility enters a high-current output state, if there is contact degradation at the charging gun connection point, it will take a certain period of time for a significant temperature rise or voltage drop to occur. However, if the power module experiences overcurrent and triggers disconnection after a short period of operation, the continuous high-current condition corresponding to the charging gun connection point disappears. At this time, the charging gun temperature has not yet reached the abnormal threshold, which only indicates that the fault characteristics have not yet fully formed, and cannot be used to determine that there is no fault in the connection point.
[0005] After the first anomaly is handled and operation resumes, the localized thermal state or other intermediate state that existed before the protection action may decay to varying degrees due to different downtime. Therefore, the two operating phases before and after protection cannot be simply judged by merging the cumulative operating time. Consequently, in the existing fault prediction process for charging facilities, for components that have not completed the fault characterization process due to the preceding protection action, it is easy to misjudge "fault verification conditions not fully executed" as "fault has been verified to not exist," causing latent faults with slower development speeds to be missed. Summary of the Invention
[0006] In the existing charging facility fault prediction process, the first abnormality triggering protection action simultaneously suspends the original fault characterization conditions of other components. Components that have not yet formed a complete fault characterization are easily determined to be in a fault-free state because no abnormal response is detected at present, leading to the omission of latent faults that exist at the same time as the first abnormality but whose fault characterization is slower. This application provides a charging facility fault prediction operation and maintenance method and system. By determining the target operating conditions suspended by the protection action, related components that have not yet completed the corresponding fault verification are retained as components to be verified. When the corresponding verification conditions are met again in subsequent operation after the first abnormality is handled, response data is obtained to complete the latent fault judgment of the components to be verified.
[0007] To achieve the above objectives, the technical solution adopted in this application is as follows: Firstly, this application provides a method for predicting and maintaining charging facility faults, including: The system acquires operational data prior to the first abnormality triggering a protection action during the operation of the charging facility, and determines the target operating conditions for the suspension due to the protection action based on the operational data. Based on the target operating conditions, it identifies associated components that have not yet formed a complete fault characterization before the protection action occurs, and identifies these associated components as components to be verified. After the first abnormality is handled, it determines the verification conditions for the components to be verified based on the target operating conditions, and acquires the response data of the components to be verified when the verification conditions are met in subsequent operations. Based on the response data, it determines whether the components to be verified have latent faults, obtains latent fault prediction results, and generates corresponding operation and maintenance processing information based on the latent fault prediction results.
[0008] In one possible implementation, determining the target operating conditions that are interrupted due to the protection action based on the operating data includes: The trigger time of the protection action is determined, and at least one of the output voltage, output current, output power, component temperature, and insulation status before the trigger time is extracted as operating parameters; a continuous running data segment within the corresponding operating parameter range is determined from the trigger time backward according to the sampling time, and the duration of the running data segment is determined; the operating parameters before and after the protection action are executed are compared, and when the corresponding operating parameters after the protection action are executed fall outside the operating parameter range, the operating parameters corresponding to the running data segment before the protection action are executed, the operating parameter range, and the duration are determined as the target operating conditions.
[0009] In one possible implementation, the associated components that have not yet formed a complete fault characterization before the protection action occurs are identified based on the target operating conditions, including: Obtain the fault characterization formation conditions corresponding to each component. The fault characterization formation conditions include verification working parameters, corresponding parameter ranges, and condition durations. Match the target working conditions with each of the fault characterization formation conditions. When the working parameters in the target working conditions are of the same type as the verification working parameters of any component, the working parameter values or working parameter ranges fall within the corresponding parameter ranges, and the duration is less than the condition duration, determine that the fault verification process of that component was not fully executed due to the protection action, and identify that component as the associated component.
[0010] In one possible implementation, determining the verification conditions for the component to be verified based on the target operating conditions includes: Obtain the fault characterization formation conditions corresponding to the component to be verified, and obtain the current state of the component to be verified after the first anomaly handling is completed; determine whether the state formed before the protection action occurs can be used for subsequent fault verification based on the current state; when it cannot be used for subsequent fault verification, determine the condition duration as the complete verification duration; when it can be used for subsequent fault verification, determine the subsequent verification duration based on the pre-established correspondence between the state parameter range and the continued verification duration; determine the complete verification duration or the subsequent verification duration as the verification duration, and determine the verification working parameters, the corresponding parameter range, and the verification duration as the verification conditions.
[0011] In one possible implementation, acquiring the response data of the component to be verified when the verification conditions are met in subsequent operations includes: Monitor subsequent operational data after the first anomaly handling is completed, and compare the corresponding working parameters with the corresponding parameter range of the verification working parameters; when the working parameters are within the corresponding parameter range, start the verification process of the component to be verified, and accumulate the current verification duration when the working parameters are continuously within the corresponding parameter range; during the verification process, acquire at least one status parameter through the status measurement channel corresponding to the component to be verified until the current verification duration reaches the verification duration or the working parameters exit the corresponding parameter range; arrange the status parameters according to the sampling time to obtain the response data.
[0012] In one possible implementation, determining whether the component to be verified has a latent fault based on the response data includes: At least one fault determination parameter is determined based on the component type of the component to be verified, and the response change amount corresponding to each fault determination parameter is determined from the response data; each response change amount is compared with the corresponding preset response change threshold; when the response change amount of at least one fault determination parameter reaches the corresponding preset response change threshold, it is determined that the component to be verified has a latent fault, and the latent fault prediction result is generated based on the component to be verified and the fault determination parameter that reaches the corresponding preset response change threshold.
[0013] In one possible implementation, when the protection action corresponds to multiple components to be verified, the verification conditions corresponding to each component to be verified are determined respectively; during subsequent operation, the verification conditions are monitored to see if they are met, and when the verification condition corresponding to any component to be verified is met, the response data of that component to be verified is obtained; when the verification conditions corresponding to multiple components to be verified are met simultaneously, the response data of each component to be verified is obtained respectively, and a corresponding latent fault prediction result is generated based on each response data.
[0014] In one possible implementation, after identifying the associated component as the component to be verified, a verification status record is established for each component to be verified. The verification status record includes at least a first anomaly identifier, a protection action identifier, a component to be verified identifier, the target operating conditions, and a verification status. When the first anomaly handling is completed but subsequent operation has not fully met the verification conditions, the verification status is maintained as a verification pending status. When the latent fault prediction result indicates the existence of a latent fault, the verification status is updated to a fault confirmation status. Only when subsequent operation has fully met the verification conditions and no latent fault is determined based on the response data, the verification status is updated to a verification passed status.
[0015] In one possible implementation, corresponding operation and maintenance processing information is generated based on the latent fault prediction results, including: When the verification status is a fault confirmation status, fault operation and maintenance information including the identifier of the component to be verified and the latent fault prediction result is generated; when the verification status is a pending verification status, continued verification information including the identifier of the component to be verified and the current verification incomplete status is generated; when the verification status is a verification passed status, verification passed information including the identifier of the component to be verified and the verification passed status is generated.
[0016] Secondly, this application discloses a charging facility fault prediction and maintenance system, and implements the aforementioned charging facility fault prediction and maintenance method, including: The system includes a working condition determination module, used to acquire operational data before the first abnormality triggers a protection action during the operation of the charging facility, and to determine the target working conditions for termination due to the protection action based on the operational data; a component to be verified module, used to determine, based on the target working conditions, related components that have not yet formed a complete fault characterization before the protection action occurs, and to identify the related components as components to be verified; a verification module, used to determine the verification conditions of the component to be verified based on the target working conditions after the first abnormality handling is completed, and to acquire the response data of the component to be verified when the verification conditions are met in subsequent operation; a fault prediction module, used to determine whether the component to be verified has a latent fault based on the response data and to generate a latent fault prediction result; and an operation and maintenance processing module, used to generate corresponding operation and maintenance processing information based on the latent fault prediction result.
[0017] Compared with related technologies, this application has the following advantages: By acquiring operational data prior to the first anomaly triggering the protection action and determining the target operating conditions that caused the protection action to be suspended, the protection event of the first anomaly can be further mapped to the fault verification process that was prematurely terminated by it. Based on the target operating conditions, related components that have not yet formed a complete fault characterization are identified and designated as components to be verified, ensuring that components that have not yet met the fault judgment conditions when the protection action occurs are not directly classified as fault-free. After the first anomaly is handled, the verification conditions for the components to be verified are determined based on the target operating conditions, and response data is acquired only when the verification conditions are met again in subsequent operations, ensuring that subsequent fault judgments are based on operational conditions adapted to the corresponding fault characterization formation process. Furthermore, latent fault prediction results and corresponding maintenance processing information are generated based on the response data, thereby distinguishing between the two states of "verification not completed due to protection action" and "no latent fault found after corresponding verification," reducing the risk of missed judgments due to the first anomaly protection action masking slower-developing latent faults, and improving the correspondence between subsequent maintenance processing information and the actual fault verification state. Attached Figure Description
[0018] Figure 1 This is a schematic diagram illustrating an application scenario of a charging facility fault prediction and maintenance method provided in an embodiment of this application. Figure 2 This application provides a schematic diagram of the application structure of a charging facility fault prediction and maintenance system. Figure 3 A flowchart of a charging facility fault prediction and maintenance method provided in this application embodiment; Figure 4 A flowchart illustrating a method for determining target working conditions provided in an embodiment of this application; Figure 5A flowchart illustrating a method for determining a component to be verified, provided in an embodiment of this application; Figure 6 A flowchart illustrating a method for acquiring response data of a component to be verified, as provided in an embodiment of this application; Figure 7 A flowchart illustrating a latent fault detection method provided in this application embodiment; Figure 8 This application provides a schematic diagram illustrating the verification status change of a component to be verified. Figure 9 A flowchart illustrating a method for generating operation and maintenance processing information provided in this application embodiment; Figure 10 This is a schematic diagram of the module structure of a charging facility fault prediction and maintenance system provided in an embodiment of this application. Detailed Implementation
[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be described below with reference to the accompanying drawings. The described embodiments are used to explain the technical solutions of this application and do not constitute a limitation on the scope of protection of this application.
[0020] In the embodiments of this application, terms such as "first" are used only to distinguish different objects and are not used to indicate the priority or importance between objects. In the embodiments of this application, "at least one" means one or more, and "more than one" means two or more.
[0021] like Figure 1 As shown, this application can be applied to operational scenarios where charging facilities charge electric vehicles. The charging facility may include at least one of a power module, a charging gun, an output circuit, a charging facility control unit, a voltage detection unit, a current detection unit, a temperature detection unit, and an insulation detection unit. The charging facility can communicate with an operation and maintenance management terminal, enabling the sending of operational data, fault protection records, and latent fault prediction results generated by the charging facility to the operation and maintenance management terminal.
[0022] Output voltage can be obtained through the existing voltage sampling circuit or voltage detection interface of the charging facility; output current can be obtained through the current sensor or the current sampling interface of the charging facility control unit; output power can be read directly from the charging facility control unit or the power module control interface, or it can be calculated based on the output voltage and output current at the corresponding sampling time; component temperature can be obtained through temperature sensors installed on the power module, charging gun terminals, or other monitored parts; insulation status can be obtained through the existing insulation detection unit of the charging facility to obtain the insulation resistance value or insulation status quantity.
[0023] The above-mentioned operational data is stored according to the timestamp of the corresponding sampling time. For different types of operational data that need to be used together, time alignment can be performed according to the timestamp, so that the data called at the same processing time corresponds to the same sampling time or is within the allowable time error range.
[0024] like Figure 2 As shown, the charging facility control unit reads the output of each detection unit and records protection events. The operation and maintenance processing equipment can be set up independently or implemented by the charging facility control unit. It is used to perform tasks such as determining target operating conditions, determining components to be verified, determining verification conditions, acquiring response data, judging latent faults, and generating operation and maintenance processing information.
[0025] The first anomaly in this application refers to an anomaly that first reaches the corresponding protection condition during a single operation and changes the original operating state of the charging facility. The protection action includes at least one of reducing output power, limiting output current, disabling one or more power modules, and disconnecting the output circuit.
[0026] The target operating conditions described in this application refer to operating conditions that exist before the protection action occurs but are no longer maintained after the protection action is performed. The target operating conditions include at least the corresponding operating parameters and the duration for which the operating parameters have remained continuously within the corresponding operating parameter range.
[0027] The fault characterization formation conditions described in this application refer to the verification working parameters and corresponding condition durations required to complete fault verification for a corresponding fault of a component. These fault characterization formation conditions do not indicate that the corresponding fault already exists, but rather specify the operating conditions under which response data can be used to determine the corresponding fault.
[0028] For example, in the case of abnormal charging gun connection, the fault status can be judged based on the temperature rise or voltage drop at the connection point. However, the temperature rise or voltage drop can only obtain a meaningful response after the corresponding output current has been applied continuously. Therefore, the corresponding output current range and its duration can constitute the fault characterization conditions corresponding to abnormal charging gun connection.
[0029] The fault characterization formation conditions can be established based on historical operational data of confirmed faults. Historical fault records with confirmed fault types are selected from the historical fault logs of charging facilities. The operational data before the fault occurred are associated with the corresponding maintenance confirmation results according to the equipment identification and fault time. The range and duration of working parameters before the fault judgment parameters first reached the corresponding fault judgment conditions are read, thereby establishing the correspondence between component identification, fault type, verification working parameters, condition duration, and fault judgment parameters.
[0030] The fault characterization formation conditions can also be established based on equipment test data. For example, by reading the response data of the corresponding component under different operating parameter conditions in existing type tests, factory tests, or fault reproduction tests, the operating parameter range and the required duration that can form the corresponding fault judgment response are recorded as the corresponding fault characterization formation conditions.
[0031] When the equipment manufacturer's parameters or equipment technical requirements have already provided the working parameters and duration required for the corresponding component fault verification, the corresponding fault characterization formation conditions can also be established directly based on the equipment technical parameters.
[0032] The fact that a complete fault characterization has not yet been formed in this application indicates that the corresponding component has not yet undergone complete fault verification operating conditions, and does not mean that the component has been determined to be faulty. Only after obtaining the response data of the component to be verified during the verification period will it be determined whether the component to be verified has a latent fault based on the response data.
[0033] like Figure 3 As shown in the figure, the charging facility fault prediction and maintenance method and system provided in this application embodiment includes steps S101 to S106.
[0034] Step S101: Obtain the operating data before the first abnormality triggers the protection action during the operation of the charging facility, and determine the target operating conditions that will be suspended due to the protection action based on the operating data. For example... Figure 4 As shown, the detailed implementation steps of step S101 include: Step S1011: Obtain the protection event record corresponding to the first anomaly, and determine the trigger time of the protection action from the protection event record.
[0035] When the charging facility control unit detects that a certain operating parameter has reached the corresponding safety protection condition, it generates a protection event record. This record includes at least the anomaly type, the protection action type, and a protection action trigger timestamp. For example, when the power module output current reaches the overcurrent protection condition, the charging facility control unit records the corresponding protection event and uses the moment of current limiting, power module shutdown, or output disconnection as the protection action trigger time. .
[0036] Step S1012: Based on the trigger time of the protection action, read the operating data prior to the protection action from the operating data storage area. Specifically, read at least one of the following data in the corresponding data window before the protection action trigger time: output voltage, output current, output power, power module temperature, charging gun temperature, and insulation status, according to the timestamp.
[0037] The data window is used to cover the operating state that existed before the protection action occurred. Specifically, the condition duration value in the fault characterization formation conditions corresponding to each component currently participating in fault prediction can be read, and the maximum condition duration value can be determined as the reference data window length, so that the data window can cover the historical operation process required for at least one complete fault characterization formation condition.
[0038] When the device controller has maintained a fixed-length cyclic running data cache, and the length of the cyclic running data cache is not less than the length of the baseline data window, the corresponding running data in the cyclic running data cache can also be read directly.
[0039] Step S1012 obtains the operating data before the protection action occurs, and the operating data is used by step S1013 to determine the continuous working state before the protection action occurs.
[0040] Step S1013: Determine the continuously established operating states before the protection action occurs based on the operating data. Specifically, for each operating parameter before the protection action occurs, read the operating parameter range corresponding to the current operating state from the charging facility control unit. The operating parameter range can be determined based on the current output setting value of the charging facility and its allowable fluctuation range, or it can be directly read from the allowable range of operating parameters corresponding to the current operating state already recorded by the charging facility control unit.
[0041] The operating parameters are arranged according to the sampling time, and the operating parameter values are compared one by one backward from the protection action trigger time to see if they are within the corresponding operating parameter range. The last consecutive running data segment within the corresponding operating parameter range is found backward from the protection action trigger time, and the first sampling time of the running data segment is determined as the first sampling time of the segment. The start time of the working conditions of each item .
[0042] No. The duration of the working condition prior to the occurrence of the protective action can be expressed as:
[0043] in, Indicates the first The duration of each working condition prior to the occurrence of the protective action; This indicates the trigger time of the protection action; Indicates the first The starting time of the last consecutive operating data segment that meets the corresponding operating parameter range before the protection action occurs; This indicates the working condition number. , and Use the same time unit, for example, all use seconds.
[0044] The maximum allowable missing duration can also be preset based on the normal data collection cycle. For example, when the normal collection cycle for a certain operating parameter is... At that time, it can be This serves as the preset maximum allowable missing duration for this working parameter.
[0045] When the timestamp difference between two adjacent running data is not greater than the preset maximum allowable missing duration, the two adjacent running data are regarded as data in the same continuous running data segment; when the timestamp difference is greater than the preset maximum allowable missing duration, the position between the two running data is regarded as the boundary of the continuous running data segment, and the condition duration is not accumulated across the missing data position.
[0046] Step S1013 obtains the operating parameters before the protection action occurs and the duration corresponding to the operating parameters. The operating parameters and the duration are used by step S1014 to determine whether the corresponding operating conditions are terminated due to the protection action.
[0047] Step S1014: Determine the target operating condition that is terminated due to the protection action based on the changes in operating parameters before and after the protection action is executed. Specifically, compare the corresponding operating parameters after the protection action is executed with the operating parameter range used in step S1013. When the corresponding operating parameters fall outside the operating parameter range after the protection action is executed, it is determined that the protection action has terminated the corresponding operating condition. For example, if the output current was continuously within the corresponding operating parameter range before the protection action, but the output current decreased to below the operating parameter range or became zero after the protection action was executed, then the operating parameter range corresponding to the output current and its duration are jointly determined as the target operating condition.
[0048] In one implementation, the target operating conditions are formed by an operating parameter, such as the output current and its corresponding duration.
[0049] In another implementation, the target operating conditions are formed by multiple operating parameters. For example, the duration is accumulated only when the output current is within the range of the corresponding operating parameters and the power module is in the output state.
[0050] In another implementation, existing operating status flags of the charging facility control unit can be used to assist in determining the target operating conditions. For example, the corresponding operating data segment can be determined based on the constant current operating status flag or normal output status flag output by the control unit.
[0051] In step S101, the protection action corresponding to the first anomaly is further converted into a target operating condition that is terminated by the protection action. The target operating condition includes at least operating parameters and the corresponding duration, and serves as the input for step S102 to determine the associated component and the component to be verified.
[0052] For example, consider a scenario where there might be a connection fault at the charging gun connection point, and the power module experiences an output overcurrent first. After the charging facility enters high-power charging, the output current enters the high-current operating parameter range corresponding to the charging gun connection fault verification. The charging facility control unit continuously records the output current according to the timestamp. After 5 seconds of charging operation, the power module experiences an output overcurrent and triggers a protection action to disconnect the output circuit. The charging facility control unit reads the trigger time of the protection action from the protection event record and reads the operating data backward from the trigger time. Following the continuous operating data segment determination method described in step S1013, the output current sample value is read one by one backward from the protection action trigger time. It is determined that the output current has been continuously within the corresponding high-current operating parameter range for 5 seconds before the protection action occurs, thus obtaining the duration corresponding to this operating parameter as 5 seconds. After the protection action is executed, the output circuit is disconnected, and the output current exits the high-current operating parameter range. This determines that the protection action has stopped the high-current operating condition, and the high-current operating parameter range and the corresponding 5-second duration are determined as the target operating condition for this processing. The target operating conditions are then provided to step S102 for matching with the fault characterization conditions of different components.
[0053] Step S102: Based on the target operating conditions, identify the associated components that have not yet formed a complete fault characterization before the protection action occurs, and determine the associated components as components to be verified; such as Figure 5 As shown, the detailed implementation steps of step S102 include: Step S1021: Obtain the component fault characterization formation conditions related to the target operating conditions. Specifically, read the pre-established correspondence between component identifiers, fault types, verification operating parameters, condition durations, and fault judgment parameters, and filter corresponding records with the same verification operating parameter type according to the operating parameter type in the target operating conditions. For example, for the charging gun connection part, the output current can be used as the verification operating parameter, and the temperature rise or connection voltage drop can be used as the fault judgment parameter; for the power module, the output load can be used as the verification operating parameter, and the module temperature rise, branch current deviation, or output deviation can be used as the fault judgment parameter; for insulation-related components, the corresponding electrical operating conditions can be used as the verification operating parameters, and the insulation resistance value or insulation state change can be used as the fault judgment parameter. Step S1021 obtains the fault characterization formation conditions corresponding to each component related to the target operating conditions, and the fault characterization formation conditions are used for matching with the target operating conditions in step S1022.
[0054] Step S1022: Match the target operating conditions with the fault characterization formation conditions corresponding to each component. Specifically, first, compare whether the operating parameter types in the target operating conditions are consistent with the verification operating parameter types in the fault characterization formation conditions. When the operating parameter types are consistent, then compare whether the operating parameter values or operating parameter ranges in the target operating conditions fall within the parameter range corresponding to the verification operating parameters.
[0055] When the working parameter type and working parameter range are both matched, the duration determined in step S101 is compared with the condition duration in the fault characterization formation conditions.
[0056] When the duration of the fault verification is less than the corresponding condition duration, it is determined that the operating conditions required for the fault verification of the corresponding component have occurred, but the operating conditions are aborted by the protection action before reaching the corresponding condition duration. It should be noted that step S1022 is only used to determine whether the fault verification process is complete, and not to determine whether a latent fault has occurred in the target component. Step S1022 obtains the fault verification integrity judgment results for each component, and these results are used by step S1023 to filter related components.
[0057] Step S1023: Determine the associated components based on the fault verification integrity judgment result. Specifically, determine the associated components as those whose verification working parameters match the target working conditions and whose fault verification has not been fully executed.
[0058] For a component whose verification operating parameters do not match the target operating conditions, it indicates that the target operating conditions for the protection action to be stopped are not the operating conditions on which the corresponding fault verification of the component depends, and the component is not identified as an associated component because of the current protection action.
[0059] Step S1024: Identify the associated component as the component to be verified and establish a verification status record, including the first anomaly identifier, protection action identifier, component to be verified identifier, target operating conditions, and verification status.
[0060] The verification state is initially set to a pending verification state, which means that the current response data is insufficient to determine whether the corresponding component to be verified has a latent fault or has passed verification.
[0061] The status record to be verified can be stored in the charging facility control unit, local fault record storage, or operation and maintenance processing equipment that is connected to the charging facility.
[0062] In step S102, a component is not directly identified as a normal component simply because it did not meet the fault determination conditions before the first abnormality triggers protection. Instead, it is determined whether the corresponding fault verification working conditions have been fully executed. The component to be verified, the verification status record, and the target working conditions generated in step S102 continue to serve as inputs for determining the verification conditions in step S103.
[0063] For example, let's continue using the target operating conditions obtained in step S101. Assume that, based on historically confirmed charging gun connection fault samples or equipment test data, the pre-established fault characterization conditions indicate that the charging gun connection abnormality needs to persist for 20 seconds within the high-current operating parameter range, and the temperature rise of the charging gun connection point must be read as a fault determination parameter under these conditions. Step S1021 first filters component records that use output current as a verification operating parameter from the pre-established correspondence, based on the output current operating parameter type in the target operating conditions, including the charging gun connection point. Step S1022 further compares the operating parameter range and the condition duration, determining that the high-current operating parameter range obtained in step S101 matches the verification operating parameter range corresponding to the charging gun connection point. However, the duration before the protection action occurs is only 5 seconds, less than the 20 seconds required for the fault characterization formation conditions. Therefore, it can only be determined that the fault verification operating conditions corresponding to the charging gun connection point have occurred but not been fully executed; it cannot be used to determine whether the charging gun connection point has a fault or not. Step S1023 identifies the charging gun connection part as an associated component, and step S1024 further identifies the charging gun connection part as a component to be verified, and establishes a verification status record including a first abnormality identifier, a protection action identifier, a charging gun connection part identifier, the high current operating parameter range, the duration of 5 seconds, and the verification status. The component to be verified and the verification status record continue to be used by step S103 to determine subsequent verification conditions.
[0064] Step S103: After the first anomaly handling is completed, the verification conditions of the component to be verified are determined according to the target operating conditions; the detailed implementation steps of step S103 include: Step S1031: Obtain the processing status corresponding to the first abnormality. Specifically, the processing status of the first abnormality can be obtained from the fault status flag, protection reset flag, and output enable flag output by the charging facility control unit.
[0065] When the fault status flag corresponding to the first anomaly has been cleared and the charging facility has entered an output-allowed state, the first anomaly is determined to have been resolved.
[0066] For the first anomaly requiring component replacement or manual maintenance, the maintenance completion record can be read from the maintenance terminal, and the output permission flag of the charging facility control unit can be further read. When the maintenance completion record has been written and the charging facility has returned to the output permission state, the first anomaly handling is determined to be complete. Step S1031 obtains the first anomaly handling completion status, which serves as the initiation condition for subsequently determining the verification conditions.
[0067] Step S1032: Obtain the current state of the component to be verified after the first anomaly handling is completed. Specifically, based on the fault characterization formation conditions corresponding to the component to be verified, determine the state parameters used to characterize the state formed before the protection action occurs, and after the first anomaly handling is completed, read the current parameter value of the state parameters through the state measurement channel corresponding to the component to be verified, and determine the state characterized by the current parameter value as the current state of the component to be verified.
[0068] For example, when the state formed before the protection action is the temperature rise state of the charging gun connection, the temperature of the charging gun connection is determined as the corresponding state parameter, and the current temperature of the charging gun connection after the first anomaly handling is completed is read. The thermal state represented by the current temperature is determined as the current state of the charging gun connection. When the state formed before the protection action is the thermal state of the power module, the temperature of the power module is determined as the corresponding state parameter, and the current temperature of the power module after the first anomaly handling is completed is read. The thermal state represented by the current temperature is determined as the current state of the power module. For the component to be verified that does not exist in the corresponding fault characterization formation conditions but can characterize the degree of retention of the state formed before the protection action, the current state of the component to be verified is directly determined as the unusable state of the preceding state.
[0069] Step S1032 obtains the current state of the component to be verified after the first anomaly handling is completed. The current state includes the current parameter value of the corresponding state parameter or the unusable state of the preceding state, and is used by step S1033 to determine whether the state formed before the protection action occurs can be used for subsequent fault verification.
[0070] Step S1033: Determine whether the state formed before the protection action occurred can be used for subsequent fault verification based on the current state. Specifically, establish a verification starting reference range for the component to be verified based on historical normal operation data or equipment technical parameters. The verification starting reference range indicates that within this state range, the state formed before the protection action occurred is no longer a usable preceding state for this subsequent verification.
[0071] Simultaneously, based on historically confirmed fault data or equipment test data, a correspondence is established in advance between different post-interruption state parameter ranges and the required duration of continued verification to meet the corresponding fault characterization conditions. This correspondence can be stored in the form of a data table, with each record including at least the lower limit of the state parameter, the upper limit of the state parameter, and the duration of continued verification.
[0072] Specifically, historical confirmed fault samples or equipment test data can be divided into intervals according to the status parameter values after the interruption; for each status parameter interval, the duration from when each sample in the status parameter interval re-enters the verification working parameter range to when the corresponding fault judgment parameter is formed is statistically analyzed, and the statistical value of the duration is used as the continued verification duration corresponding to the status parameter interval.
[0073] In one implementation, the arithmetic mean of the continued verification durations of each sample within the state parameter range can be used as the corresponding continued verification duration; in another implementation, to reduce insufficient verification caused by insufficient continued verification duration, the maximum value of the continued verification durations of each sample within the state parameter range can be used as the corresponding continued verification duration.
[0074] The current state parameter obtained in step S1032 is compared with the verification starting reference range. When the current state parameter is within the verification starting reference range, it is determined that the state formed before the protection action occurs cannot be used for subsequent fault verification.
[0075] When the current status parameter is not within the verification start reference range, the range of status parameters containing the current status parameter is further searched in the correspondence; when the corresponding status parameter range can be found, it is determined that the state formed before the protection action occurs can be used for subsequent fault verification.
[0076] When the current status parameter is not within the verification start reference range, but there is no status parameter range containing the current status parameter in the corresponding relationship, in order to avoid unfounded calculation of the operating status before and after protection, the status formed before the protection action occurs will be processed as not being used for subsequent fault verification.
[0077] Step S1033 obtains the judgment result of the previous state and the continued verification duration corresponding to the current state when a corresponding relationship exists, so as to provide step S1034 with the verification duration amount to be determined.
[0078] Step S1034: Based on the preceding state, the verification duration can be determined using the judgment result. Specifically, when step S1033 determines that the state formed before the protection action cannot be used for subsequent fault verification, the complete condition duration in the corresponding fault characterization formation conditions is read, and the complete condition duration is determined as the complete verification duration.
[0079] When step S1033 determines that the state formed before the protection action occurs can be used for subsequent fault verification, the duration of continued verification corresponding to the state parameter range of the current state is read, and the duration of continued verification is determined as the duration of subsequent verification.
[0080] Therefore, the running time before and after the protection action is not directly added mechanically. Instead, it is determined whether to use the subsequent verification duration based on whether the current state has entered the verification start reference range and the correspondence between the pre-established state parameter range and the continued verification duration. Step S1034 obtains the complete verification duration or the subsequent verification duration, which is then used by step S1035 to determine the verification conditions.
[0081] Step S1035: Determine the verification conditions based on the working parameters in the corresponding fault characterization formation conditions and the duration determined in step S1034. Specifically, the verification conditions include at least the verification working parameters and the verification duration.
[0082] When the complete verification duration is obtained in step S1034, the complete verification duration is used as the verification duration in the verification conditions; when the subsequent verification duration is obtained in step S1034, the subsequent verification duration is used as the verification duration in the verification conditions. The verification working parameters are determined according to the working parameters in the fault characterization formation conditions corresponding to the component to be verified, and should be within the normal operating range currently allowed by the charging facility after the first anomaly handling is completed.
[0083] Specifically, the allowable normal operating range can be read from the currently valid output allowable parameters of the charging facility control unit, the equipment technical parameters, or the currently enabled safety protection parameters, and is not expanded separately by the latent fault verification process in this application.
[0084] The verification conditions are only used to identify whether a working state that can support the component to be verified to complete fault verification naturally appears during normal operation after the first anomaly handling is completed.
[0085] If no corresponding verification conditions are met during subsequent operation, the component to be verified shall remain in the verification state and the charging facility shall not be actively put into a working state that exceeds the allowable operating range.
[0086] If any security protection condition is triggered again during the verification process, the current verification process will be terminated, and the corresponding pending verification state will continue to be retained.
[0087] In step S103, based on the current state of the component to be verified after the first anomaly handling is completed, the verification duration is objectively determined as either the complete verification duration or the subsequent verification duration obtained from a pre-established correspondence, and combined with the corresponding verification working parameters to form verification conditions. These verification conditions serve as the basis for step S104 to determine whether subsequent operation should initiate response data acquisition.
[0088] For example, the charging gun connection point is used as the component to be verified. After the power module completes the first abnormality handling, the first abnormality fault state flag in the charging facility control unit has been cleared and the output permission state has been re-established. Therefore, step S1031 determines that the first abnormality handling is complete. Step S1032 reads the current temperature through the temperature measurement channel corresponding to the charging gun connection point, assuming the current temperature is 32℃. Based on historical normal operation data or equipment technical parameters, the verification starting reference range is 30℃ to 34℃. Step S1033 compares 32℃ with the verification starting reference range. 32℃ is within the range of 30℃ to 34℃. Therefore, it is determined that the thermal state formed before the protection action can no longer be used as a usable preceding state for this subsequent fault verification. Step S1034 accordingly does not directly add the 5 seconds that have lasted before the protection action to the subsequent running time. Instead, it reads the 20-second complete condition duration in the fault characterization formation conditions corresponding to the charging gun connection abnormality and determines 20 seconds as the complete verification duration. Step S1035 further determines the high current operating parameter range and the 20-second complete verification duration corresponding to the charging gun connection fault verification as the verification conditions for the charging gun connection part, and provides the verification conditions to step S104.
[0089] In another scenario, if the current temperature of the charging gun connection point read after the first anomaly handling is not within the 30°C to 34°C verification starting reference range, and there exists a state parameter range that includes the current temperature in the pre-established correspondence between the state parameter range and the continued verification duration based on historically confirmed fault data or equipment test data, and the continued verification duration corresponding to this state parameter range is 12 seconds, then step S1033 determines that the thermal state formed before the protection action occurs can be used for subsequent fault verification; step S1034 determines the 12 seconds as the subsequent verification duration; and step S1035 jointly determines the high current operating parameter range and the 12-second subsequent verification duration as the verification condition. If there is no state parameter range covering the current temperature in the correspondence, no time conversion is performed, and the 20-second complete condition duration is still determined as the complete verification duration.
[0090] Step S104: Obtain the response data of the component to be verified when the verification conditions are met in subsequent operations; such as... Figure 6 As shown, the detailed implementation steps of step S104 include: Step S1041: Obtain subsequent running data after the first exception handling is completed, and determine whether the subsequent running meets the verification conditions. Specifically, read the verification working parameters and corresponding parameter ranges determined in step S103, and compare the corresponding working parameters in the subsequent running data with the parameter ranges one by one.
[0091] When the working parameters in the subsequent running data fall within the parameter range corresponding to the verification working parameters, the corresponding sampling time will be used as the verification process start time. .
[0092] When the working parameters do not fall within the parameter range corresponding to the verification working parameters, the verification process of the component to be verified is not started, and the status record to be verified is maintained.
[0093] Step S1041 obtains the verification process start result and the verification process start time. This provides the cumulative verification duration for step S1042.
[0094] Step S1042: Accumulate the verification duration from the start time of the verification process; the currently completed verification duration is represented as:
[0095] in, Indicates the current duration of verification; Indicates the current sampling time; This indicates the start time of this verification process. , and Use the same time unit.
[0096] The verification duration is accumulated only when the verification working parameters are continuously within the parameter range corresponding to the verification working parameters.
[0097] When the verification working parameter falls outside the parameter range, the current continuous verification interval is terminated, and the time spent outside the parameter range is not counted in the verification duration. When the subsequent operation re-enters the parameter range corresponding to the verification working parameter, a verification interval is restarted according to the corresponding fault characterization formation conditions.
[0098] Step S1042 obtains the current verification duration, which is used by step S1043 to determine whether to continue collecting status parameters, and by step S106 to determine whether the verification conditions have been fully executed.
[0099] Step S1043: During the period when the verification working parameters continuously meet the corresponding verification conditions, the status parameters of the component to be verified are obtained. Specifically, the status parameters corresponding to the component to be verified are obtained using the existing status measurement channel of the charging facility.
[0100] For the charging gun connection point, at least one of temperature and voltage drop can be obtained; For power modules, at least one of the following can be obtained: module temperature, branch current, and output parameters; For insulation-related components, insulation resistance values or insulation status quantities can be obtained.
[0101] For multiple state parameters that need to be used together, state parameter groups with the same verification time can be formed directly based on the same timestamp, or state parameters with timestamp differences not exceeding the corresponding sampling period can be time-aligned to form corresponding state parameter groups.
[0102] The acquisition period of the state parameters is determined based on the corresponding verification duration. For example, it can be set to obtain no less than 10 valid sample values within the shortest verification duration, i.e., the acquisition period of the state parameters is no greater than one-tenth of the corresponding shortest verification duration. This value is only one example and does not limit the use of the same sampling period.
[0103] This application can also directly use the sampling period already adopted by the existing detection unit of the charging facility, as long as multiple valid state parameters arranged in chronological order can be obtained within the corresponding verification duration. Step S1043 obtains the state parameters during the verification process, which are then used by step S1044 to form response data.
[0104] Step S1044: Form the response data according to the state parameters; specifically, arrange the state parameters obtained in step S1043 in order of sampling timestamps to form the response data sequence corresponding to the component to be verified.
[0105] In one implementation, the state parameters corresponding to the start time and end time of the verification process can be read from the response data sequence, and the difference between the two can be calculated as the response change.
[0106] Taking temperature as an example, the temperature rise during the verification process can be expressed as:
[0107] in, This indicates the temperature rise during the verification process; This indicates the temperature at the same temperature measurement point when the verification process begins. This indicates the temperature at the same temperature measurement point at the end of the verification or at the current judgment time.
[0108] When voltage drop at the connection point is used to characterize the connection status, the equivalent connection resistance can be calculated when the measured current reaches the effective measurement current condition:
[0109] in, Indicates the equivalent connection resistance of the connection point, in ohms; This represents the voltage drop at the two ends of the connection at the corresponding sampling time, in volts. This represents the current flowing through the connection at the corresponding sampling time, measured in amperes.
[0110] Only when the current The above formula is used to calculate the equivalent connection resistance only when the current is not less than the preset effective measurement current lower limit, so as to avoid the distortion of the calculation results when the current is close to zero.
[0111] The preset effective measurement current lower limit can be determined based on the effective measurement lower limit of the charging facility current sampling device or the device's technical parameters. For example, when the technical data of the current sampling device specifies that the corresponding measurement accuracy requirement is met when the current is not less than 10A, 10A can be set as the preset effective measurement current lower limit.
[0112] Step S1044 obtains the response data, which includes the component to be verified, at least one state parameter during the period when the verification conditions are met, or the response change amount calculated from the state parameter, and serves as the input for step S105 to determine the latent fault.
[0113] By using step S104, response data for judgment is obtained only when the component to be verified regains the verification conditions related to the formation of the corresponding fault characterization, thus avoiding the formation of a verification pass conclusion during the operation phase when the operating parameters do not meet the corresponding verification conditions or the verification duration is insufficient.
[0114] For example, the "high current operating parameter range + 20-second complete verification duration" determined in step S103 is used as the verification condition for the current charging gun connection. During subsequent charging after the first anomaly handling, step S1041 continuously reads the output current. When the output current re-enters the high current operating parameter range, the corresponding sampling time is determined as the start time of this verification process. Assuming the temperature of the charging gun connection is 32°C when the verification process starts, step S1042 accumulates the verification duration from the start time of the verification process. Simultaneously, step S1043 continuously reads the temperature of the charging gun connection according to the corresponding sampling period and associates each temperature value with the corresponding sampling timestamp. When the output current remains continuously within the high current operating parameter range for 20 seconds, the current verification duration reaches the 20-second complete verification duration determined in step S103. Step S1044 arranges the temperature parameters obtained during the 20 seconds according to the sampling timestamps from first to last, forming a response data sequence corresponding to the charging gun connection. Assuming the temperature is 32°C when the verification process starts and 47°C after 20 seconds of verification, the temperature rise is 15°C based on the starting and ending temperatures at the same temperature measurement point. The response data, including the temperature response data sequence and the 15°C temperature rise, is then provided to step S105 for latent fault judgment.
[0115] In another operating scenario, if the output current re-enters the high-current operating parameter range but only lasts for 8 seconds, and then exits the operating parameter range due to the user actively stopping charging, then the current verification duration obtained in step S1042 is only 8 seconds, which is less than the complete verification duration of 20 seconds. In this case, the current continuous verification interval is stopped, and the status parameters collected during the 8-second period are retained. However, a verification pass conclusion cannot be formed solely based on the 8-second response data; the completeness of the current verification is further processed in subsequent step S106.
[0116] Step S105: Determine whether the component to be verified has a latent fault based on the response data, and obtain the latent fault prediction result; such as Figure 7 As shown, the detailed implementation steps of step S105 include: Step S1051: Determine the corresponding fault determination parameters according to the component type of the component to be verified; specifically, based on the component identifier of the component to be verified, read the corresponding fault determination parameters from the correspondence between the component identifier, fault type, verification working parameters, condition duration and fault determination parameters used in step S1021.
[0117] For example, at least one of the following parameters can be used as fault determination parameters for the charging gun connection: temperature rise, connection voltage drop, or equivalent connection resistance. The power module can use at least one of the following as fault judgment parameters: module temperature rise, branch current deviation, or output parameter deviation; For insulation-related components, the insulation resistance value or the change in insulation condition can be used as fault judgment parameters.
[0118] Step S1051 obtains the fault determination parameters, which are used in step S1052 to determine the corresponding response change from the response data.
[0119] Step S1052: Determine the response change amount corresponding to each fault judgment parameter from the response data, first determining the normal baseline value of the mm-th fault judgment parameter. .
[0120] When the equipment's technical parameters already provide corresponding normal reference values, these normal reference values can be directly used as... .
[0121] When using historical normal operation data to determine the normal baseline value, only historical normal samples whose verification working parameters are within the same parameter range as the current verification conditions are selected for statistical participation, so that the historical normal samples and the current response data are at the corresponding working condition level.
[0122] Extracting the first from the historical normal samples The fault determination parameters are determined, and the normal baseline value is calculated according to the following formula:
[0123] in, Indicates the first The normal baseline value of each fault determination parameter; This indicates the number of historical normal samples used in the calculation of the normal baseline value; Indicates the first The first historical normal sample corresponding to the first Fault determination parameter values; Indicates the fault determination parameter number; This indicates the historical normal sample number.
[0124] when When the number of historical samples is not less than the minimum required number, the above-mentioned historical statistical method is used to determine the normal baseline value; when the number of historical normal samples is insufficient, the normal reference value given by the equipment technical parameters can be used directly to avoid forming a baseline value based on historical data with insufficient sample size.
[0125] For the upper limit of the abnormality judgment parameter corresponding to the increase in the abnormality degree as the parameter value increases, the first abnormality parameter is determined according to the following formula. The response change corresponding to each fault determination parameter:
[0126] For the lower limit of abnormal fault judgment parameters where a decrease in parameter value corresponds to an increase in the degree of abnormality, the following formula is used to determine the first abnormality parameter. The response change corresponding to each fault determination parameter:
[0127] in, Indicates the first The change in response of the fault determination parameter; This indicates the first verification obtained in the current verification phase. Fault determination parameter values; Indicates the first The normal baseline value corresponding to each fault judgment parameter.
[0128] Step S1052 obtains the response change corresponding to each fault determination parameter. The change in response is compared with the corresponding preset response change threshold in step S1053.
[0129] Step S1053: Compare each of the stated response changes with the corresponding preset response change threshold. Specifically, for the first... The fault determination parameter, and its response change. With the corresponding preset response change threshold Compare them.
[0130] when:
[0131] When, determine the first The fault determination parameters meet the corresponding anomaly determination conditions.
[0132] in, Indicates the first The preset response change threshold corresponding to each fault judgment parameter has the same dimensions as... same.
[0133] When the equipment manufacturer or equipment technical requirements have already given the first When determining the allowable change amount corresponding to a fault judgment parameter, the allowable change amount is used as a preset response change threshold. .
[0134] When no corresponding technical limit exists, the preset response change threshold can be established based on historical normal samples. Specifically, only historical normal samples whose verification working parameters are within the same parameter range as the current verification conditions are selected, the response change amount corresponding to each historical normal sample is calculated, and the mean of the response change amount is further calculated. and standard deviation .
[0135] In one implementation, the preset response change threshold can be determined according to the following formula:
[0136] in, Indicates the first The mean change in the response of each fault determination parameter in historical normal samples; Indicates the first Standard deviation of the response variation of each fault determination parameter in historical normal samples; Indicates the first The preset response change threshold corresponding to each fault judgment parameter.
[0137] Furthermore, the preset response change threshold can be verified using historically confirmed fault samples. Specifically, the response change corresponding to the historically confirmed fault samples is compared with... Compare and verify whether the confirmed fault samples can meet the corresponding anomaly judgment conditions; when the equipment technical requirements have given corresponding fault judgment limits, the equipment technical limits shall be used first, and historical statistical results shall not be used to cover existing safety or fault judgment limits.
[0138] Step S1053 obtains the anomaly determination results corresponding to each fault determination parameter, and the anomaly determination results are used by step S1054 to determine whether the component to be verified has a latent fault.
[0139] Step S1054: Determine whether the component to be verified has a latent fault based on the anomaly determination result. Specifically, when the component to be verified corresponds to only one fault determination parameter, when the response change of the fault determination parameter reaches the corresponding preset response change threshold, it is determined that the component to be verified meets the latent fault determination condition.
[0140] When the component to be verified corresponds to multiple fault determination parameters, the anomaly determination result corresponding to each fault determination parameter is read respectively. When the response change of at least one fault determination parameter reaches its corresponding preset response change threshold, it is determined that the component to be verified meets the latent fault determination condition, and it is determined that the component to be verified has a latent fault.
[0141] When the response change of each of the fault determination parameters does not reach the corresponding preset response change threshold, the latent fault of the component to be verified is not determined at the current time; whether the component to be verified can be determined as a verified pass state is further determined by step S106 in combination with whether the verification conditions have been fully executed.
[0142] Step S1054 obtains the latent fault judgment result of the component to be verified, and the latent fault judgment result is used by step S1055 to generate the latent fault prediction result.
[0143] Step S1055: Form a latent fault prediction result based on the latent fault judgment result. Specifically, the latent fault prediction result includes at least the identifier of the component to be verified and the latent fault judgment status. When it is determined that the component to be verified has a latent fault, the latent fault prediction result may also include a fault judgment parameter that reaches the corresponding preset response change threshold.
[0144] Step S1055 obtains the latent fault prediction result and provides it to step S106 to generate operation and maintenance processing information. Through step S105, the latent fault judgment uses the response data obtained during the period when the component to be verified re-meets the verification conditions, thereby distinguishing between "fault verification not yet completed due to the first abnormal protection action being stopped" and "fault judgment obtained after complete verification".
[0145] For example, the response data of the charging gun connection obtained in step S104 will continue to be used for explanation. Step S1051 reads the temperature rise as the current fault judgment parameter from the pre-established correspondence between component identifier, fault type, verification working parameters, condition duration, and fault judgment parameters, based on the component identifier corresponding to the charging gun connection. Step S1052 determines the temperature rise corresponding to the current verification process as 15°C based on the verification process start temperature of 32°C and the temperature of 47°C after 20 seconds of verification obtained in step S104. Assuming that the preset response change threshold corresponding to the temperature rise of the charging gun connection is predetermined to be 12°C based on the corresponding equipment technical parameters or historical normal samples within the same parameter range as the current verification working parameters, step S1053 compares the 15°C temperature rise with the 12°C preset response change threshold. Since 15°C is not less than 12°C, it is determined that the temperature rise fault judgment parameter meets the corresponding abnormal judgment condition. Step S1054 determines that the charging gun connection meets the latent fault judgment condition and determines that there is a latent fault in the charging gun connection. Step S1055 generates a latent fault prediction result including the charging gun connection part identification, the judgment status of latent fault existence, and the temperature rise fault judgment parameters, and provides the latent fault prediction result to step S106 to generate corresponding operation and maintenance processing information.
[0146] Specifically, if the verification conditions corresponding to step S104 have not been fully executed, for example, if the current verification duration is only 8 seconds, then even if the current temperature rise has not reached the preset response change threshold of 12°C, the charging gun connection part cannot be determined as having passed the verification. Step S105 only forms a judgment state that no latent fault has been determined at present, and step S106 further maintains the state to be verified based on the result that the verification conditions have not been fully executed.
[0147] Step S106: Generate corresponding operation and maintenance processing information based on the latent fault prediction results, such as... Figure 8 As shown, the verification status of the component to be verified includes at least the verification status, the fault confirmation status, and the verification passed status.
[0148] After the first abnormality triggers protection, the components that need further verification are determined according to step S102 and enter the pending verification state; when the verification conditions are met and a latent fault is confirmed based on the response data, the pending verification state is updated to the fault confirmation state; only when the verification conditions are fully executed and the response data does not meet the corresponding latent fault judgment conditions, the pending verification state is updated to the verification passed state. Figure 9 As shown, the detailed implementation steps of step S106 include: Step S1061: Read the latent fault prediction result obtained in step S105 and determine whether the current verification conditions have been fully executed. Specifically, read the current verification duration accumulated in step S1042. And compare it with the verification duration in the verification conditions determined in step S103.
[0149] When the current verification duration is not less than the verification duration, it is determined that the verification condition has been fully executed.
[0150] If the current verification duration is less than the verification duration, or if the verification parameters have already exited the corresponding parameter range before reaching the verification duration, it is determined that the current verification conditions have not been fully executed.
[0151] Step S1061 obtains the verification integrity result, which, together with the latent fault prediction result obtained in step S105, is used in steps S1062 to S1064 for state diversion.
[0152] Step S1062: When the latent fault prediction result indicates that the component to be verified has a latent fault, generate fault operation and maintenance information. Specifically, read the component identifier and latent fault judgment status from the latent fault prediction result, and generate fault operation and maintenance information including the component identifier of the component to be verified and the latent fault prediction result.
[0153] The fault maintenance information can be sent to the maintenance management terminal to indicate that the corresponding component to be verified needs to be repaired.
[0154] Step S1062 obtains fault maintenance information and updates the verification status in the corresponding pending verification status record to the fault confirmation status.
[0155] Step S1063: When it has not been determined that the component to be verified has a latent fault and the current verification conditions have not been fully executed, the state to be verified is maintained. Specifically, when step S105 has not determined that the component to be verified has a latent fault and step S1061 has determined that the verification conditions have not been fully executed, the component to be verified is not updated to the verification passed state.
[0156] Maintain the record of the state to be verified, and generate continued verification information including the identifier of the component to be verified and the current verification incomplete status.
[0157] When the corresponding verification conditions are met again in subsequent runs, the verification conditions corresponding to the component to be verified are reread according to the component identifier in the continued verification information, and steps S104 and S105 are continued.
[0158] Step S1063 obtains continued verification information, which is used to continue the verification task of the corresponding component to be verified in subsequent runs.
[0159] Step S1064: When the verification conditions have been fully executed and the response data does not meet the corresponding latent fault determination conditions, the component to be verified is updated to the verification passed state; specifically, when step S1061 determines that the verification conditions have been fully executed and step S105 does not determine that the component to be verified has a latent fault, the verification status in the verification status record is updated to the verification passed state, and verification passed information including the component to be verified identifier and the verification passed status is generated.
[0160] Step S106 allows for the differentiation of three states at the operational status level: "latent fault has been confirmed," "verification has not yet been completed," and "fully verified and no latent fault has been detected." This prevents the observation interruption caused by the first anomaly from directly being converted into a conclusion that other components are fault-free.
[0161] In one implementation, the same protection action can correspond to multiple components to be verified. For example, a single protection action that disconnects the output circuit may simultaneously halt the corresponding fault verification conditions for the charging gun connection, part of the power module, or insulation-related components.
[0162] Step S1024 is executed for each associated component to establish an independent state record to be verified for each associated component, and step S103 is executed according to the fault characterization formation conditions corresponding to each component to be verified to obtain the corresponding verification conditions.
[0163] During subsequent normal operation, the real-time operating parameters will be compared with the verification conditions corresponding to each component to be verified.
[0164] When the verification condition corresponding to a component to be verified is met, the corresponding response data is collected for that component.
[0165] When the verification conditions corresponding to multiple components to be verified are met simultaneously, the response data of multiple components to be verified can be obtained at the same time, and step S105 can be executed respectively to obtain the corresponding latent fault prediction results.
[0166] The completion of verification for one component to be verified does not change the verification status of other components to be verified. The other components to be verified continue to wait for the corresponding verification conditions to be met according to their respective verification status records.
[0167] like Figure 10 As shown, this application also provides a charging facility fault prediction and maintenance system, including a working condition determination module, a component to be verified determination module, a verification module, a fault prediction module, and an operation and maintenance processing module.
[0168] The operating condition determination module is used to acquire the operating data before the first abnormality triggers the protection action during the operation of the charging facility, and to determine the target operating conditions that will be suspended due to the protection action based on the operating data.
[0169] Specifically, the working condition determination module reads the protection event record to determine the protection action trigger time, reads the running data backward from the trigger time, determines the working parameters that were continuously within the corresponding working parameter range before the protection action occurred and their duration, and determines the target working conditions based on whether the corresponding working parameters exit the working parameter range after the protection action is executed.
[0170] The component to be verified module is used to determine, based on the target operating conditions, the associated components that have not yet formed a complete fault characterization before the protection action occurs, and to identify the associated components as components to be verified.
[0171] Specifically, the component to be verified determination module matches the target operating conditions with the corresponding fault characterization formation conditions of each component. When the operating parameters match and the duration before the protection action is less than the duration of the corresponding condition, the corresponding component is determined as an associated component, and a corresponding status record to be verified is established.
[0172] The verification module is used to determine the verification conditions of the component to be verified according to the target working conditions after the first exception handling is completed, and to obtain the response data of the component to be verified when the verification conditions are met in subsequent operation.
[0173] Specifically, the verification module reads the current state of the component to be verified, determines the complete verification duration or the subsequent verification duration based on the verification start reference range and the correspondence between the pre-established state parameter range and the continued verification duration, and determines the verification conditions in conjunction with the corresponding verification working parameters; when the subsequent normal operation reaches the verification working parameters, the verification process is started, and the corresponding state parameters are obtained to form response data.
[0174] The fault prediction module is used to determine whether the component to be verified has a latent fault based on the response data, and to obtain a latent fault prediction result.
[0175] Specifically, the fault prediction module reads the corresponding fault determination parameters according to the type of the component to be verified, determines the response change of the fault determination parameters relative to the normal baseline value, and compares the response change with the corresponding preset response change threshold to obtain the latent fault prediction result.
[0176] The operation and maintenance processing module is used to generate corresponding operation and maintenance processing information based on the latent fault prediction results. Specifically, when the latent fault prediction results indicate the existence of a latent fault, fault operation and maintenance information is generated; when the existence of a latent fault has not yet been determined and the verification conditions have not been fully executed, continued verification information is generated and the system remains in a pending verification state; when the verification conditions have been fully executed and the existence of a latent fault has not been determined, verification passed information is generated.
[0177] Each of the above modules can be implemented by one or more processors executing programs in memory, or it can be integrated into the charging facility control unit, fault diagnosis controller, or maintenance processing equipment that is communicatively connected to the charging facility. Specifically, operating data, records of states to be verified, fault characterization formation conditions, the correspondence between state parameter ranges and the duration of continued verification, and preset response change thresholds can all be stored in local memory or in data storage devices connected to the maintenance processing equipment.
[0178] It should be noted that the system module division in this embodiment is used to illustrate the correspondence between various processing functions, and does not limit each module to be implemented with an independent hardware structure.
[0179] The above description is merely a preferred embodiment of this application. It should be noted that, due to the limitations of written expression, there are objectively infinite specific structures. For those skilled in the art, without departing from the principles of this application, several improvements, modifications, or variations can be made, and the above technical features can be combined in an appropriate manner. These improvements, modifications, variations, or combinations, or the direct application of the concept and technical solution of this application to other situations without modification, should all be considered within the scope of protection of this application.
Claims
1. A method for predicting and maintaining charging facility faults, characterized in that, include: Obtain operational data before the first abnormality triggers the protection action during the operation of the charging facility, and determine the target operating conditions that will be suspended due to the protection action based on the operational data; Based on the target operating conditions, identify the associated components that have not yet formed a complete fault characterization before the protection action occurs, and determine the associated components as components to be verified. After the first exception handling is completed, the verification conditions of the component to be verified are determined according to the target working conditions, and the response data of the component to be verified is obtained when the verification conditions are met in subsequent operation. Based on the response data, determine whether the component to be verified has a latent fault, obtain the latent fault prediction result, and generate corresponding operation and maintenance processing information based on the latent fault prediction result.
2. The method for predicting and maintaining charging facility faults according to claim 1, characterized in that, The target operating conditions that cause the protection action to be suspended are determined based on the operating data, including: Determine the trigger time of the protection action, and extract at least one of the following as operating parameters: output voltage, output current, output power, component temperature, and insulation status before the trigger time; Based on the sampling time, determine the continuous running data segments within the corresponding working parameter range from the trigger time backward, and determine the duration of the running data segments; By comparing the operating parameters before and after the protection action is executed, when the corresponding operating parameters after the protection action are executed fall outside the range of operating parameters, the operating parameters corresponding to the running data segment before the protection action is executed, the range of operating parameters, and the duration of the operation are determined as the target operating conditions.
3. The method for predicting and maintaining charging facility faults according to claim 2, characterized in that, Based on the target operating conditions, the associated components that have not yet formed a complete fault characterization before the protection action occurs include: Obtain the fault characterization formation conditions corresponding to each component. The fault characterization formation conditions include verification working parameters, corresponding parameter ranges, and condition duration. Match the target operating conditions with each of the fault characterization conditions; When the working parameters in the target working conditions are of the same type as the verification working parameters of any component, the working parameter value or working parameter range falls within the corresponding parameter range, and the duration is less than the condition duration, it is determined that the fault verification process of the component was not fully executed due to the protection action, and the component is identified as the associated component.
4. The method for predicting and maintaining charging facility faults according to claim 3, characterized in that, Determine the verification conditions for the component to be verified based on the target operating conditions, including: Obtain the fault characterization formation conditions corresponding to the component to be verified, and obtain the current state of the component to be verified after the first anomaly handling is completed; Based on the current state, determine whether the state formed before the protection action occurred can be used for subsequent fault verification; When the condition duration cannot be used for subsequent fault verification, the condition duration is determined as the complete verification duration. When it can be used for subsequent fault verification, the duration of subsequent verification is determined according to the pre-established correspondence between the range of state parameters and the duration of continued verification; The complete verification duration or the subsequent verification duration is determined as the verification duration, and the verification working parameters, the corresponding parameter range, and the verification duration are determined as the verification conditions.
5. A method for predicting and maintaining charging facility faults according to claim 4, characterized in that, When the verification conditions are met in subsequent operations, the response data of the component to be verified is obtained, including: Monitor subsequent operational data after the first anomaly handling is completed, and compare the corresponding working parameters with the corresponding parameter range of the verification working parameters; When the working parameter is within the corresponding parameter range, the verification process of the component to be verified is started, and the current verification duration when the working parameter is continuously within the corresponding parameter range is accumulated; During the verification process, at least one state parameter is acquired through the state measurement channel corresponding to the component to be verified until the current verification duration reaches the verification duration or the working parameter exits the corresponding parameter range. The state parameters are arranged according to the sampling time to obtain the response data.
6. The method for predicting and maintaining charging facility faults according to claim 5, characterized in that, Determining whether the component to be verified has a latent fault based on the response data includes: At least one fault determination parameter is determined based on the component type of the component to be verified, and the response change corresponding to each fault determination parameter is determined from the response data; Each of the aforementioned response changes is compared with its corresponding preset response change threshold. When the response change of at least one of the fault determination parameters reaches the corresponding preset response change threshold, it is determined that the component to be verified has a latent fault, and the latent fault prediction result is generated based on the component to be verified and the fault determination parameter that has reached the corresponding preset response change threshold.
7. The method for predicting and maintaining charging facility faults according to claim 4, characterized in that, When the protection action corresponds to multiple components to be verified, the verification conditions corresponding to each component to be verified are determined respectively. During subsequent operation, the verification conditions are monitored to determine whether they are met, and the response data of the component to be verified is obtained when the verification condition corresponding to any component to be verified is met. When the verification conditions corresponding to multiple components to be verified are met simultaneously, the response data of each component to be verified is obtained, and the corresponding latent fault prediction results are generated based on the response data.
8. The method for predicting and maintaining charging facility faults according to claim 1, characterized in that, After identifying the associated component as the component to be verified, a verification status record is established for each component to be verified. The verification status record includes at least a first anomaly identifier, a protection action identifier, a component to be verified identifier, the target operating conditions, and a verification status. When the first anomaly handling is completed but subsequent operation has not yet fully met the verification conditions, the verification status is maintained as a verification status. When the latent fault prediction result indicates the existence of a latent fault, the verification status is updated to fault confirmation status; only when subsequent operations have fully met the verification conditions and no latent fault is determined based on the response data, the verification status is updated to verification passed status.
9. A method for predicting and maintaining charging facility faults according to claim 8, characterized in that, Based on the latent fault prediction results, corresponding operation and maintenance processing information is generated, including: When the verification status is a fault confirmation status, fault operation and maintenance information including the identifier of the component to be verified and the latent fault prediction result is generated; When the verification status is pending verification, continue verification information including the identifier of the component to be verified and the current verification incomplete status is generated; When the verification status is "verification passed", verification pass information is generated, including the identifier of the component to be verified and the verification pass status.
10. A charging facility fault prediction and maintenance system, implementing the charging facility fault prediction and maintenance method according to any one of claims 1 to 9, characterized in that, include: The working condition determination module is used to acquire the operating data before the first abnormality triggers the protection action during the operation of the charging facility, and to determine the target working conditions that will be suspended due to the protection action based on the operating data. The component to be verified module is used to determine, based on the target operating conditions, the associated components that have not yet formed a complete fault characterization before the protection action occurs, and to determine the associated components as components to be verified. The verification module is used to determine the verification conditions of the component to be verified according to the target working conditions after the first exception handling is completed, and to obtain the response data of the component to be verified when the verification conditions are met in subsequent operation. The fault prediction module is used to determine whether the component to be verified has a latent fault based on the response data and generate a latent fault prediction result. The operation and maintenance processing module is used to generate corresponding operation and maintenance processing information based on the latent fault prediction results.
