A method for combined debugging and fault positioning of a direct current fast charging pile in multiple working conditions

Abstract

The application discloses a kind of DC fast charging pile multi-working condition combined debugging and fault location method, it is related to DC charging equipment detection technical field, comprising: according to the operation state of DC fast charging pile constructs multiple debugging paths, sets the debugging working condition as action node, establishes action dependency relationship and configures action determination condition and fault object mapping relationship;According to action dependency relationship, the action node that satisfies predecessor condition or safety execution condition is executed, control instruction, execution feedback and electrical response data are collected;According to the control instruction event, execution feedback event and electrical response event generated according to the data collected, and according to the existence state of event, occurrence order, response timing and electrical response result determine abnormal link position or action response chain normal state;The determination result of each action node is associated, to identify root exception, propagation exception and dependent blocking action, determine target fault object and form fault location record Determine multi-working condition combined debugging result.

Description

Technical Field

[0001] This invention relates to the field of DC charging equipment testing technology, specifically a method for multi-condition joint debugging and fault location of DC fast charging piles. Background Technology

[0002] DC fast charging stations typically consist of a charging controller, power module, pre-charge circuit, main contactor, protection and disconnection unit, voltage acquisition unit, and current acquisition unit. After installation, commissioning, or maintenance, DC fast charging stations usually require commissioning under various operating conditions, including power module startup, pre-charge contactor closure, main contactor closure, low load output, high load output, normal stop, and protection disconnection, to verify the coordination between control command transmission, action execution, status feedback, and power output. Existing commissioning methods typically follow a preset commissioning procedure, sequentially performing various tests and collecting data such as control commands, contactor status, power module status, DC bus voltage, output voltage, and output current. The commissioning status is then determined based on comparisons between these data and their corresponding allowable ranges. Some commissioning equipment can also assist in identifying communication anomalies, contactor operation anomalies, power module output anomalies, and protection operation anomalies by incorporating fault codes, alarm information, or preset judgment rules.

[0003] There are continuous state transitions between different commissioning conditions of DC fast charging piles. The action result of the previous commissioning condition may affect the execution conditions and electrical response of the subsequent commissioning condition. For example, an abnormal pre-charging action may affect the establishment of the main circuit, an abnormal main circuit establishment may further affect the subsequent current regulation, and an abnormal pre-drive action may also prevent the execution of subsequent actions. When each commissioning condition is judged independently, there is a lack of a unified action dependency relationship between the abnormal data in different commissioning conditions, making it difficult to distinguish between the first abnormality, subsequent abnormalities caused by the preceding abnormality, and actions not executed due to the preceding abnormality. In addition, there is a corresponding timing relationship between the issuance of control commands, the formation of execution feedback, and the generation of electrical responses. The same commissioning action may manifest as the control command not being executed, the feedback state not being formed normally, the execution component completing the action but the main power circuit not generating a corresponding response, or the electrical response being generated but not reaching the expected target. Judging solely based on a single state parameter or the final voltage and current results makes it difficult to further determine the control execution link, state feedback link, main power response link, or output regulation link corresponding to the abnormality. For anomalies occurring in multiple commissioning paths, it is also necessary to correlate anomaly information under different commissioning conditions to identify the abnormal behavior of the same faulty object under different commissioning conditions and determine the scope of subsequent anomalies and action blockages caused by the faulty object. Therefore, it is necessary to conduct joint analysis of action nodes, control command events, execution feedback events, and electrical response events in different commissioning conditions to enhance the correlation between the commissioning results of DC fast charging piles under multiple conditions and improve the clarity of fault location results. Summary of the Invention

[0004] Based on the shortcomings of the prior art described above, the purpose of this invention is to provide a method for joint debugging and fault location of DC fast charging piles under multiple operating conditions, so as to solve the above-mentioned technical problems.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a method for multi-condition joint debugging and fault location of DC fast charging piles, comprising:

[0006] Multiple debugging paths are constructed based on the operating status of DC fast charging piles. The debugging conditions corresponding to each debugging path are set as action nodes. Action dependencies are established according to the execution order of each action node. The action judgment conditions and fault object mapping relationships corresponding to each action node are configured to form a multi-condition action dependency configuration.

[0007] Based on the multi-condition action dependency configuration, the action nodes that meet the precursor conditions and the condition execution action nodes that meet the safety execution conditions are executed sequentially according to the action dependency relationship. The control command data, execution feedback data and electrical response data corresponding to each executed action node are obtained to form an action acquisition record.

[0008] Based on the motion acquisition records, the control command events, execution feedback events, and electrical response events corresponding to each motion node are determined to form a motion event record;

[0009] Based on the existence, occurrence order, response timing, and electrical response results of control command events, execution feedback events, and electrical response events in the action event record, determine the abnormal link location or normal state of the action response chain corresponding to each action node, and form an action link determination record.

[0010] Based on the action dependency relationship, the action link judgment records corresponding to each action node are associated to determine the root anomaly, propagation anomaly, and dependency blocking action. Based on the action category and anomaly link location corresponding to the root anomaly, the target fault object is determined based on the fault object mapping relationship, forming one or more fault location records.

[0011] The results of multi-condition joint debugging are determined based on the action link judgment record and fault location record, and the target fault object, the condition in which the fundamental fault first occurs, and the link in which the fundamental fault first occurs are output.

[0012] The present invention is further configured such that the plurality of debugging paths include a normal adjustment path and a protection cut-off path; the normal adjustment path sequentially includes a power module start-up action node, a pre-charge contactor closing action node, a main contactor closing action node, a low target current adjustment action node, a high target current adjustment action node, and a main contactor disconnection action node; the protection cut-off path sequentially includes a power module start-up action node, a pre-charge contactor closing action node, a main contactor closing action node, a low target current adjustment action node, and a protection output cut-off action node.

[0013] The present invention is further configured such that establishing action dependencies includes:

[0014] Arrange the action nodes according to the execution order of each action node in the corresponding debugging path. The action node that is before and adjacent to the current action node in the same debugging path is determined as the preceding action node of the current action node, and a correspondence is established between the current action node identifier and the preceding action node identifier.

[0015] Set the preceding action node to be in a normal state in the action response chain as the preceding condition of the current action node;

[0016] Configure a predecessor exception handling method for the current action node with a predecessor action node. The predecessor exception handling method includes a blocking execution method and a conditional execution method.

[0017] When the current action node's exception handling method is the blocking execution method, the existence of a link exception in the previous action node is set as the blocking condition for the current action node;

[0018] When the current driver exception handling method is conditional execution, configure the safety execution conditions corresponding to the current action node. If the previous driver node has a link exception and the safety execution conditions are met, the current action node is determined as a conditional execution action. If the previous driver node has a link exception and the safety execution conditions are not met, the current action node is determined as a dependency blocking action.

[0019] Associating the current action node identifier, the preceding action node identifier, the preceding condition, the preceding exception handling method, and the corresponding safe execution conditions forms an action dependency relationship.

[0020] The present invention is further configured such that the action determination conditions corresponding to each action node include:

[0021] For each action node, configure the control object, control object identifier, target feedback status, electrical response parameter type, electrical response target value, reference value duration, allowable duration from command to feedback, allowable duration from feedback to electrical response, response observation duration, effective holding duration, response trigger ratio, and allowable deviation ratio;

[0022] Configure the target feedback state corresponding to the power module start-up action node as the power module ready state, and configure the corresponding electrical response parameter type as DC bus voltage;

[0023] Configure the target feedback state corresponding to the precharge contactor closing action node as the precharge contactor closing feedback state, and configure the corresponding electrical response parameter type as the output voltage;

[0024] Configure the target feedback state corresponding to the main contactor closing action node as the main contactor closing feedback state, and configure the corresponding electrical response parameter type as the voltage difference between the DC bus voltage and the output voltage.

[0025] Configure the target feedback state corresponding to the low target current regulation action node and the high target current regulation action node as the power module current regulation command reception confirmation state, and configure the corresponding electrical response parameter type as output current;

[0026] Configure the target feedback state corresponding to the main contactor disconnection action node as the main contactor disconnection feedback state, configure the target feedback state corresponding to the protection output cut-off action node as the protection cut-off execution state, and configure the electrical response parameter type corresponding to the main contactor disconnection action node and the protection output cut-off action node as the output current.

[0027] The control command transmission link, action execution component, status feedback link, main power circuit and output regulation circuit are respectively set as candidate fault object types. The combination of action type and abnormal link location is used as the mapping index to establish the fault object mapping relationship between each mapping index and the corresponding candidate fault object.

[0028] The present invention is further configured such that forming a motion acquisition record includes:

[0029] Under a unified time reference, obtain the control command corresponding to the current action node and record the time when the control command was issued;

[0030] Starting from the moment the command is issued, within the response observation interval limited by the response observation duration, the feedback state of the control object corresponding to the current action node and the feedback acquisition time corresponding to each feedback state are continuously acquired, and the feedback states are arranged in time sequence according to the feedback acquisition time to form a feedback state sequence.

[0031] Based on the electrical response parameter type corresponding to the current action node, within the benchmark value interval with the instruction issuance time as the termination time and the benchmark value duration as the interval length, each electrical response parameter and its corresponding response acquisition time are obtained, and each electrical response parameter is arranged in time sequence according to the response acquisition time to form a benchmark parameter sequence.

[0032] Within a response observation interval, which starts at the time of instruction issuance and has a duration of response observation as its length, each electrical response parameter and its corresponding response acquisition time are acquired. The electrical response parameters are then arranged in chronological order according to the response acquisition time to form an observation parameter sequence.

[0033] The current action node identifier, control object identifier, control command, command issuance time, feedback status sequence, baseline parameter sequence, and observation parameter sequence are associated to form the action acquisition record corresponding to the current action node.

[0034] The present invention is further configured such that forming an action event record includes:

[0035] The control command corresponding to the current action node and the time when the control command was issued are defined as the control command event.

[0036] Extract the electrical response parameter values ​​from the reference parameter sequence, and determine the median of each electrical response parameter value as the response reference value;

[0037] Starting from the moment the command is issued, the feedback state sequence is detected sequentially according to the feedback acquisition time. When the feedback state reaches the target feedback state for the first time and maintains the target feedback state continuously for a valid duration from the corresponding feedback acquisition time, the corresponding feedback acquisition time is determined as the valid feedback time for executing the feedback event. When no target feedback state that has been continuously maintained for a valid duration is detected within the response observation interval, the execution feedback event is determined to not exist.

[0038] Based on the change of each electrical response parameter value relative to the response reference value in the observation parameter sequence, and the target change of the electrical response target value relative to the response reference value, the directional response progress corresponding to each response acquisition time is determined.

[0039] The directional response progress is detected sequentially according to the response acquisition time. When the directional response progress reaches the response trigger ratio for the first time, and remains at or above the response trigger ratio for an effective holding time from the corresponding response acquisition time, the corresponding response acquisition time is determined as the effective electrical response time of the electrical response event. When no directional response progress that has been continuously maintained for an effective holding time is detected within the response observation interval, the electrical response event is determined to not exist.

[0040] Extract the electrical response parameter values ​​from the observation parameter sequence that are located at the end of the response observation interval and whose interval length is the effective holding time, and determine the median of the extracted electrical response parameter values ​​as the final electrical response value.

[0041] The control command event, execution feedback event, electrical response event, response baseline value, and electrical response final value are associated to form the action event record corresponding to the current action node.

[0042] The present invention is further configured such that forming the action link determination record includes:

[0043] Based on the existence status, occurrence order, response timing, and electrical response results of the execution feedback event and electrical response event, the action link judgment result corresponding to the current action node is determined according to the preset judgment order;

[0044] When neither the execution feedback event nor the electrical response event exists, the action link judgment result corresponding to the current action node is determined to be an abnormal control execution segment.

[0045] When the execution feedback event does not exist but the electrical response event does exist, the action link judgment result corresponding to the current action node is determined to be an execution status feedback segment anomaly.

[0046] When an execution feedback event exists but an electrical response event does not exist, the action link judgment result corresponding to the current action node is determined to be an anomaly in the main power response segment.

[0047] When both the execution feedback event and the electrical response event exist, and the effective electrical response time is earlier than the effective feedback time, the action link judgment result corresponding to the current action node is determined to be an execution status feedback segment anomaly.

[0048] When the effective feedback time is not earlier than the command issuance time, the effective electrical response time is not earlier than the effective feedback time, and the duration between the command issuance time and the effective feedback time exceeds the allowable duration from the command to the feedback, the action link judgment result corresponding to the current action node is determined as an abnormality in the control execution segment.

[0049] When the time between the instruction issuance time and the effective feedback time does not exceed the allowed time between instruction and feedback, and the time between the effective feedback time and the effective electrical response time exceeds the allowed time between feedback and electrical response, the action link judgment result corresponding to the current action node is determined to be an anomaly in the main power response segment.

[0050] When both the execution feedback event and the electrical response event exist, the order of occurrence of the effective feedback time and the effective electrical response time and the corresponding response timing both meet the action judgment conditions, and the response deviation ratio of the final value of the electrical response relative to the target value of the electrical response exceeds the allowable deviation ratio of the response, the action link judgment result corresponding to the current action node is determined as an output adjustment section anomaly.

[0051] When the existence status, occurrence order, response timing, and electrical response result of the execution feedback event and electrical response event all meet the action judgment conditions, the action link judgment result corresponding to the current action node is determined as the normal state of the action response chain.

[0052] The current action node identifier, action link determination result, and abnormal link location are associated to form the action link determination record corresponding to the current action node.

[0053] The present invention is further configured such that determining the fundamental anomaly, the propagation anomaly, and the dependent blocking action includes:

[0054] Based on the action dependencies, the execution status of each action node is associated with the action chain determination result;

[0055] When the action link determination result of the current action node is that the link is abnormal, and the current action node does not have a preceding action node or the preceding action node of the current action node is in a normal state of action response chain, the current action node is identified as a fundamental abnormal candidate action.

[0056] When the current action node completes execution according to the conditional execution method under the condition that the predecessor condition is not met, and the action link determination result of the current action node is that the link is abnormal, the current action node is determined to be a propagation abnormal action.

[0057] When the preceding action node of the current action node has a link anomaly, and the current action node does not execute according to the blocking execution method, or does not execute because the safe execution conditions are not met, the current action node is determined to be a dependent blocking action;

[0058] For abnormal propagation actions, trace along the preceding direction of the action dependency relationship, and identify the fundamental abnormal candidate action that is closest to the abnormal propagation action as the source of propagation;

[0059] For actions that depend on blocking, trace along the preceding direction of the action dependency and identify the fundamental abnormal candidate action that is closest to the action that depends on blocking as the source of blocking;

[0060] The fundamental abnormal candidate action, the propagation abnormal action, the dependent blocking action, the propagation source and the blocking source are associated with the corresponding action node identifiers to form an action abnormal association record.

[0061] The present invention is further configured such that forming one or more fault location records includes:

[0062] Obtain the action category and abnormal link location corresponding to each fundamental anomaly candidate action, and query the fault object mapping relationship based on the action category and abnormal link location to determine the candidate fault object and candidate fault object identifier corresponding to each fundamental anomaly candidate action.

[0063] Candidate actions of fundamental anomalies with the same candidate fault object identifier are assigned to the same fundamental anomaly evidence group, and the candidate fault objects corresponding to each fundamental anomaly evidence group are identified as target fault objects.

[0064] Obtain the instruction issuance time corresponding to each fundamental anomaly candidate action in the same fundamental anomaly evidence group, determine the fundamental anomaly candidate action with the earliest instruction issuance time as the first anomaly action, determine the debugging condition corresponding to the first anomaly action as the condition where the fundamental fault first occurs, and determine the abnormal link position corresponding to the first anomaly action as the link where the fundamental fault first occurs.

[0065] Based on the action anomaly association records, extract the propagation anomaly action whose propagation source corresponds to any fundamental anomaly candidate action in the fundamental anomaly evidence group, and the dependent blocking action whose blocking source corresponds to any fundamental anomaly candidate action in the fundamental anomaly evidence group.

[0066] The target fault object, the working condition in which the fundamental fault first occurs, the link in which the fundamental fault first occurs, the action chain judgment record corresponding to each candidate action of the fundamental anomaly, the propagation anomaly action and the dependent blocking action are associated to form the fault location record corresponding to the target fault object.

[0067] When multiple fundamental anomaly evidence groups are formed, fault location records are generated for each fundamental anomaly evidence group.

[0068] The present invention is further configured such that determining the results of multi-condition joint commissioning includes:

[0069] When all action nodes in each debugging path have been executed, and the action link judgment results corresponding to each action node are all in the normal state of the action response chain, the multi-condition joint debugging result is determined to be debugged successfully.

[0070] When one or more fundamental anomaly evidence groups are formed, the multi-condition joint debugging result is determined to be a debugging failure, and the fault location record corresponding to each fundamental anomaly evidence group is output. The fault location record includes the target fault object, the operating condition in which the fundamental fault first occurs, and the link in which the fundamental fault first occurs.

[0071] This invention provides a method for multi-condition joint debugging and fault location of DC fast charging piles. It constructs multiple debugging paths based on the operating status of the DC fast charging pile, sets the debugging conditions corresponding to each debugging path as action nodes, establishes action dependencies based on the execution order of each action node, and configures the action judgment conditions and fault object mapping relationships corresponding to each action node, forming a multi-condition action dependency configuration. Based on the multi-condition action dependency configuration, action nodes that meet the preceding conditions and conditionally execute action nodes that meet the safety execution conditions are executed sequentially according to the action dependencies. Control command data, execution feedback data, and electrical response data corresponding to each executed action node are acquired to form an action acquisition record. Based on the action acquisition record, the control command event, execution feedback event, and electrical response event corresponding to each action node are determined. Action event records are generated. Based on the existence, occurrence sequence, response timing, and electrical response results of control command events, execution feedback events, and electrical response events in the action event records, the abnormal link location or normal state of the action response chain corresponding to each action node is determined, forming an action link determination record. Based on the action dependency relationship, the action link determination records corresponding to each action node are associated to determine the fundamental anomaly, propagation anomaly, and dependent blocking actions. Based on the action category and abnormal link location corresponding to the fundamental anomaly, the target fault object is determined based on the fault object mapping relationship, forming one or more fault location records. Based on the action link determination records and fault location records, the results of multi-condition joint debugging are determined, and the target fault object, the operating condition where the fundamental fault first occurs, and the link where the fundamental fault first occurs are output. The beneficial effects include:

[0072] Based on the existence, occurrence sequence, response timing, and electrical response results of execution feedback events and electrical response events, the action link judgment results are divided into control execution segment abnormality, execution status feedback segment abnormality, main power response segment abnormality, output regulation segment abnormality, and normal action response chain state. This enables segmented identification of the link location where the action abnormality is located, and refines the overall judgment of the action execution result into separate judgments of the control execution, status feedback, main power response, and output regulation links, thereby narrowing the scope of fault investigation and improving the accuracy of fault location for DC fast charging piles.

[0073] By associating the execution status of each action node with the action chain determination results based on the action dependency relationship, the action node whose predecessor action node is in a normal action response chain state but whose current action node has a link abnormality is identified as a fundamental abnormality candidate action. The action node that executes and generates a link abnormality when the predecessor condition is not met is identified as a propagation abnormal action. The action node that is not executed due to the link abnormality of the predecessor action node is identified as a dependency blocking action. This enables the differentiation of the abnormality start position, the abnormality propagation range, and the action blocking range, reducing the situation where multiple subsequent abnormalities caused by the same fundamental fault are identified as independent faults.

[0074] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0075] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0076] Figure 1 The flowchart illustrates a method for joint debugging and fault location of DC fast charging piles under multiple operating conditions, as an exemplary embodiment of the present invention. Detailed Implementation

[0077] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.

[0078] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0079] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention.

[0080] A method for joint commissioning and fault location of DC fast charging piles under multiple operating conditions, such as Figure 1 As shown, it includes:

[0081] Multiple debugging paths are constructed based on the operating status of DC fast charging piles. The debugging conditions corresponding to each debugging path are set as action nodes. Action dependencies are established according to the execution order of each action node. The action judgment conditions and fault object mapping relationships corresponding to each action node are configured to form a multi-condition action dependency configuration.

[0082] Based on the multi-condition action dependency configuration, the action nodes that meet the precursor conditions and the condition execution action nodes that meet the safety execution conditions are executed sequentially according to the action dependency relationship. The control command data, execution feedback data and electrical response data corresponding to each executed action node are obtained to form an action acquisition record.

[0083] Based on the motion acquisition records, the control command events, execution feedback events, and electrical response events corresponding to each motion node are determined to form a motion event record;

[0084] Based on the existence, occurrence order, response timing, and electrical response results of control command events, execution feedback events, and electrical response events in the action event record, determine the abnormal link location or normal state of the action response chain corresponding to each action node, and form an action link determination record.

[0085] Based on the action dependency relationship, the action link judgment records corresponding to each action node are associated to determine the root anomaly, propagation anomaly, and dependency blocking action. Based on the action category and anomaly link location corresponding to the root anomaly, the target fault object is determined based on the fault object mapping relationship, forming one or more fault location records.

[0086] The results of multi-condition joint debugging are determined based on the action link judgment record and fault location record, and the target fault object, the condition in which the fundamental fault first occurs, and the link in which the fundamental fault first occurs are output.

[0087] The present invention is further configured such that the plurality of debugging paths include a normal adjustment path and a protection cut-off path; the normal adjustment path sequentially includes a power module start-up action node, a pre-charge contactor closing action node, a main contactor closing action node, a low target current adjustment action node, a high target current adjustment action node, and a main contactor disconnection action node; the protection cut-off path sequentially includes a power module start-up action node, a pre-charge contactor closing action node, a main contactor closing action node, a low target current adjustment action node, and a protection output cut-off action node; specifically, regarding the overall design of the debugging path and the protection triggering method, the debugging of the DC fast charging pile should cover both normal operation and protection cut-off processes. This embodiment constructs two independent debugging paths: a normal adjustment path and a protection cut-off path. The protection cut-off path injects a preset protection trigger signal into the protection test interface of the charging controller through the debugging control terminal, thereby triggering the protection output cut-off action node. It does not use actual overvoltage, overcurrent, or insulation failure to trigger the protection action. The two paths share the preceding power module start-up action node, pre-charge contactor closing action node, and main contactor closing action node. Points are established to ensure that the electrical preconditions of the protection disconnection path are consistent with those of the normal adjustment path. Regarding the allocation rules for path identifiers, operating condition identifiers, action node identifiers, and action category identifiers, each commissioning path is assigned a unique path identifier to distinguish it from the normal adjustment path and the protection disconnection path. Each commissioning operating condition is assigned a unique operating condition identifier according to the execution order of actions within the path, and operating conditions with the same name in different paths are assigned different operating condition identifiers to distinguish the paths to which they belong. A globally unique action node identifier is assigned to the specific commissioning action corresponding to each operating condition. Even if the same type of action appears in different paths, different action node identifiers are assigned to distinguish the paths to which they belong and the execution instances. At the same time, an action category identifier is assigned to each action node. The action category identifier does not distinguish the path but only represents the physical attributes of the action. The physical attributes include power module start-up, pre-charge contactor closing, main contactor closing, current regulation, main contactor opening, or protection output disconnection. Through the four-level identifier system consisting of path identifiers, operating condition identifiers, action node identifiers, and action category identifiers, any collected record can be traced back to the specific path, specific operating condition, specific action instance, and the action category to which it belongs.The specific construction method of the normal adjustment path is to construct the action nodes sequentially according to the physical cause-and-effect sequence of the DC fast charging pile from power-on to shutdown. The first node is the power module start-up action node, corresponding to the no-load start-up condition. At this time, both the pre-charge contactor and the main contactor are in the open state. Only the power module group is started to put its DC bus into the no-load ready state. The next node is the pre-charge contactor closing action node, corresponding to the pre-charge condition. After the power module starts, the pre-charge contactor closes, and the inrush current is limited by the pre-charge resistor, so that the output voltage gradually rises. The subsequent node is the main contactor closing action node, corresponding to the main circuit establishment condition. After the pre-charge is completed... When the voltage difference across the main contacts drops to a safe range, the main contactor closes, switching the pre-charge circuit to a low-resistance main circuit. The next node is a low-target current regulation node corresponding to a low-load output condition; the action type is current regulation, and the regulation target is a lower set output current. The following node is a high-target current regulation node corresponding to a high-load output condition; the action type is still current regulation, but the regulation target switches to a higher set output current. The final node is the main contactor disconnection node, corresponding to a normal stop condition; the action type is main contactor disconnection, cutting off the main output circuit and causing the output current to drop. These action nodes sequentially form a strict... The preceding nodes in the protection tripping path have a dependency relationship; each subsequent node requires the completion of the preceding node as a prerequisite, and skipping or reversing steps is not allowed. The specific construction method of the protection tripping path is that the preceding nodes are completely consistent with the normal adjustment path, in the following order: power module start-up node, pre-charge contactor closing node, main contactor closing node, and low target current adjustment node. The final node of the protection tripping path is the protection output tripping node, corresponding to the protection tripping condition. This node does not continue to increase the load, nor does it stop the output by normally disconnecting the main contactor. Instead, it triggers the protection tripping execution unit to forcibly cut off the output. The contact of the protection output tripping node... The method involves connecting the charging controller's protection test interface via a debugging control terminal, injecting a preset protection trigger signal into the controller. The preset protection trigger signal simulates overvoltage, overcurrent, or insulation abnormalities, enabling the controller to generate a protection output cut-off command without the need for an actual corresponding fault to occur. The preset protection trigger signal is only used to drive the control logic to generate the cut-off command and does not participate in the actual electrical abnormalities of the power circuit, thus not causing damage to the equipment. Moreover, the content, timing, and amplitude of each injected signal can be accurately reproduced. After receiving the cut-off command, the protection cut-off execution unit executes the output cut-off action. This action is performed as an independent node for event extraction and link determination.The node reuse and differences between the two paths, as well as the details of the protection test interface, are as follows: In both the normal adjustment path and the protection disconnection path, the action categories of the preceding shared nodes are completely identical, but the action node identifier is globally unique. This distinguishes instances of the same action in different paths and collects their respective command, feedback, and electrical response data. The difference between the two paths lies after the preceding shared nodes: in the normal adjustment path, it continues to the high target current adjustment action node and then to the main contactor disconnection action node; in the protection disconnection path, it directly enters the protection output disconnection action node. The protection test interface physically provides a test command channel for the charging controller's reserved debugging communication port, dedicated test pins, or the host computer communication bus. The preset protection trigger signal format is consistent with the signal used in actual protection judgment. The only difference is that the signal source is marked as a test source rather than a field sampling source, thus bypassing the actual sensor sampling value and directly participating in the protection logic judgment. When the debugging control terminal executes the protection output cut-off action node, it sends the preset protection trigger signal through the protection test interface according to the content and timing specified in the configuration table, and records the sending time as the instruction issuance time of the action node. Subsequent feedback status and output current observation are all collected according to a unified time base, so that the protection output cut-off action node and other action nodes use the same event extraction and link judgment process, without the need to design separate judgment logic for the protection path.

[0088] The present invention is further configured such that establishing action dependencies includes:

[0089] Arrange the action nodes according to the execution order of each action node in the corresponding debugging path. The action node that is before and adjacent to the current action node in the same debugging path is determined as the preceding action node of the current action node, and a correspondence is established between the current action node identifier and the preceding action node identifier.

[0090] Set the preceding action node to be in a normal state in the action response chain as the preceding condition of the current action node;

[0091] Configure a predecessor exception handling method for the current action node with a predecessor action node. The predecessor exception handling method includes a blocking execution method and a conditional execution method.

[0092] When the current action node's exception handling method is the blocking execution method, the existence of a link exception in the previous action node is set as the blocking condition for the current action node;

[0093] When the current driver exception handling method is conditional execution, configure the safety execution conditions corresponding to the current action node. If the previous driver node has a link exception and the safety execution conditions are met, the current action node is determined as a conditional execution action. If the previous driver node has a link exception and the safety execution conditions are not met, the current action node is determined as a dependency blocking action.

[0094] The current action node identifier, the preceding action node identifier, the preceding condition, the preceding exception handling method, and the corresponding safe execution condition are associated to form an action dependency relationship. Specifically, regarding the arrangement of action nodes according to the execution order and the determination of the preceding action node, for each debugging path, all action nodes in the path are sorted from first to last according to the predetermined execution order of each action node within that path. For any current action node after sorting, the action node that precedes and is adjacent to the current action node within the same debugging path is determined as the preceding action node of the current action node. At the same time, a relationship is established between the action node identifier of the current action node and the action node identifier of its preceding action node. In each debugging path, the first action node has no preceding action node because there are no other action nodes before it, and no corresponding relationship is established for the preceding action node identifier. The action link determination result of the preceding action node is determined as the preceding condition for the normal setting of the action response chain. The normal state of the action response chain means that after the preceding action node completes event extraction and link determination, both its execution feedback event and electrical response event exist. The order of events meets the requirements that the instruction issuance time is not later than the effective feedback time and the effective feedback time is not later than the effective electrical response time. The actual time from instruction issuance to the formation of execution feedback does not exceed the allowed time from instruction to feedback. The time from the formation of execution feedback to the generation of electrical response is... The preceding condition is considered met only if the actual duration of feedback to the electrical response does not exceed the allowable duration, and the response deviation ratio of the final electrical response value relative to the target electrical response value does not exceed the allowable deviation ratio. This condition is satisfied only if the link determination results of the current driving node do not show any abnormalities in the control execution segment, execution status feedback segment, main power response segment, or output regulation segment. The response deviation ratio is calculated by taking the absolute value of the difference between the final electrical response value and the target electrical response value as the numerator, taking the absolute value of the difference between the target electrical response value and the response reference value as the reference difference, and taking the larger of the preset minimum positive correction and the reference difference as the denominator. The quotient obtained by dividing the numerator by the denominator is the response deviation ratio, and the response reference value is the reference parameter. The median of each electrical response parameter value in the sequence is used. The final electrical response value is the median of each electrical response parameter value within the effective holding time interval at the end of the observed parameter sequence. A preset minimum positive correction is used to avoid division by zero when the reference difference approaches zero. Regarding the configuration of the preceding abnormality handling mode, for each current action node with a preceding action node, its preceding abnormality handling mode must be configured. The preceding abnormality handling mode includes blocking execution mode and conditional execution mode. The blocking execution mode is suitable for situations where continuing execution after the preceding action is abnormal may cause damage to the power module, contactor adhesion, or risk of injury or death to the test personnel. The conditional execution mode is suitable for situations where the preceding action is abnormal but continuing to execute the current action is still feasible for safe operation.Regarding the specific implementation of the blocking execution mode, when the current driver exception handling mode is configured as the blocking execution mode, the existence of a link exception in the previous driver node is set as the blocking condition for the current driver node. The link exception includes any one of the following: control execution segment exception, execution status feedback segment exception, main power response segment exception, and output regulation segment exception. During debugging execution, when any link segment exception is detected in the action link determination result of the previous driver node, the blocking condition is determined to be met. At this time, the execution of the current driver node is prevented, and a dependency blocking record is generated to record the blocking event. Regarding the specific implementation of the conditional execution mode, when the current driver exception handling mode is configured as the conditional execution mode, a corresponding safe execution condition is pre-configured for the current driver node. The content of the safe execution condition is to confirm the continuation of the current driver node's execution. The operation will not pose a safety risk to the power module, contactor, charging controller, or test personnel. During the debugging process, when a link anomaly is detected in the preceding drive node and the safety execution conditions are verified to be met, the current action node is allowed to execute, and it is identified as a conditional execution action. At the same time, a preceding condition not met flag is generated. When a link anomaly is detected in the preceding drive node and the safety execution conditions are not met, the current action node is not executed, and it is identified as a dependency blocking action. At the same time, a dependency blocking record is generated. The action node identifier of the current action node, the action node identifier of the preceding drive node, the specific content of the preceding conditions, the configured preceding anomaly handling method, and the corresponding safety execution conditions are all associated and stored in the multi-condition action dependency configuration table, thus forming a complete action dependency relationship.

[0095] The present invention is further configured such that the action determination conditions corresponding to each action node include:

[0096] For each action node, configure the control object, control object identifier, target feedback status, electrical response parameter type, electrical response target value, reference value duration, allowable duration from command to feedback, allowable duration from feedback to electrical response, response observation duration, effective holding duration, response trigger ratio, and allowable deviation ratio;

[0097] Configure the target feedback state corresponding to the power module start-up action node as the power module ready state, and configure the corresponding electrical response parameter type as DC bus voltage;

[0098] Configure the target feedback state corresponding to the precharge contactor closing action node as the precharge contactor closing feedback state, and configure the corresponding electrical response parameter type as the output voltage;

[0099] Configure the target feedback state corresponding to the main contactor closing action node as the main contactor closing feedback state, and configure the corresponding electrical response parameter type as the voltage difference between the DC bus voltage and the output voltage.

[0100] Configure the target feedback state corresponding to the low target current regulation action node and the high target current regulation action node as the power module current regulation command reception confirmation state, and configure the corresponding electrical response parameter type as output current;

[0101] Configure the target feedback state corresponding to the main contactor disconnection action node as the main contactor disconnection feedback state, configure the target feedback state corresponding to the protection output cut-off action node as the protection cut-off execution state, and configure the electrical response parameter type corresponding to the main contactor disconnection action node and the protection output cut-off action node as the output current.

[0102] The control command transmission link, action execution component, status feedback link, main power circuit, and output regulation circuit are each set as candidate fault object types. A mapping relationship between each mapping index and the corresponding candidate fault object is established, using the combination of action category and abnormal link location as a mapping index. Specifically, regarding the node-by-node configuration of action judgment conditions, twelve action judgment conditions are configured for each action node in the multi-condition action dependency configuration table. These twelve conditions are, in order: controlled object, controlled object identifier, target feedback status, electrical response parameter type, electrical response target value, baseline value duration, allowable duration from command to feedback, allowable duration from feedback to electrical response, response observation duration, effective holding duration, response trigger ratio, and allowable deviation ratio. Each condition is entered into the multi-condition action dependency configuration table along with the action node identifier. Regarding the judgment condition configuration for the power module start-up action node, the controlled object corresponding to the power module start-up action node is configured as the power module group, the controlled object identifier is configured as the device identifier of the power module group, the target feedback status is configured as the power module ready state, the electrical response parameter type is configured as DC bus voltage, and the electrical response target value is configured as the no-load bus target value. Voltage, remaining time, and proportional conditions are configured separately based on the measured timing and accuracy requirements of the power module startup. Regarding the judgment conditions for the pre-charge contactor closing action node, the control object corresponding to the pre-charge contactor closing action node is configured as the pre-charge contactor, the control object identifier is configured as the device identifier of the pre-charge contactor, the target feedback state is configured as the pre-charge contactor closing feedback state, the electrical response parameter type is configured as the output voltage, the electrical response target value is configured as the pre-charge target voltage, and the remaining time and proportional conditions are configured separately based on the electrical characteristics of the pre-charge circuit. Regarding the main contactor closing action... The node determination condition configuration sets the control object corresponding to the main contactor closing action node as the main contactor, the control object identifier as the device identifier of the main contactor, the target feedback state as the main contactor closing feedback state, and the electrical response parameter type as the voltage difference between the DC bus voltage and the output voltage. The voltage difference is obtained by subtracting the DC bus voltage sampling value and the output voltage sampling value at the same sampling time during the specific execution process. The electrical response target value is set as the main contactor conduction target voltage difference. The remaining time type and proportional type conditions are configured separately according to the electrical characteristics of the main contactor switching.Regarding the configuration of the judgment conditions for low-target current regulation action nodes and high-target current regulation action nodes, the control objects corresponding to both are configured as power module groups, the control object identifiers are configured as the device identifiers of the power module groups, the target feedback status is configured as the power module current regulation command reception confirmation status, and the electrical response parameter type is configured as output current. The electrical response target value of the low-target current regulation action node is configured as the target output current corresponding to the low load condition, and the electrical response target value of the high-target current regulation action node is configured as the target output current corresponding to the high load condition. The remaining time-type and proportional-type conditions are classified according to the response characteristics of the current regulation closed loop. Do not configure; Regarding the configuration of the judgment conditions for the main contactor disconnection action node and the protection output cut-off action node, configure the control object corresponding to the main contactor disconnection action node as the main contactor, configure the control object identifier as the device identifier of the main contactor, configure the target feedback state as the main contactor disconnection feedback state, configure the electrical response parameter type as output current, and configure the electrical response target value as the stop output target current. Configure the control object corresponding to the protection output cut-off action node as the protection cut-off execution unit, configure the control object identifier as the device identifier of the protection cut-off execution unit, configure the target feedback state as the protection cut-off execution state, configure the electrical response parameter type as output current, and configure the electrical response target value as the protection cut-off target current. The remaining duration and proportional conditions are configured separately based on the electrical characteristics of their respective disconnection and cutoff processes. Regarding the setting of candidate fault object types, the control command transmission link, action execution component, status feedback link, main power circuit, and output regulation circuit are respectively set as candidate fault object types, forming the target-side classification of fault object mapping relationships. The combination of action category and abnormal link location is used as the mapping index. Abnormal link locations include four types: control execution segment, execution status feedback segment, main power response segment, and output regulation segment. The specific construction method is as follows: For the power module start-up action category, the control execution segment is mapped to the power module start-up command transmission link or start-up drive link, and the execution status feedback segment is mapped to the power module... In the status feedback link, the main power response segment is mapped to the DC bus establishment circuit of the power module, and the output regulation segment is mapped to the voltage regulation circuit of the power module bus. For the pre-charge contactor closing action category, the control execution segment is mapped to the pre-charge contactor drive circuit, the execution status feedback segment is mapped to the pre-charge contactor auxiliary contact or feedback acquisition line, the main power response segment is mapped to the pre-charge contactor main contact or pre-charge circuit, and the output regulation segment is mapped to the pre-charge voltage establishment circuit. For the main contactor closing action category, the control execution segment is mapped to the main contactor closing drive circuit, the execution status feedback segment is mapped to the main contactor closing feedback circuit, the main power response segment is mapped to the main contactor main contact or output main circuit, and the output regulation segment is mapped to the main circuit conduction state.For low-target current regulation and high-target current regulation action categories, the control execution segment is mapped to the current regulation command transmission link, the execution status feedback segment is mapped to the power module command response link, the main power response segment is mapped to the power module power output circuit, and the output regulation segment is mapped to the power module group or current closed-loop regulation circuit. For the main contactor disconnection action category, the control execution segment is mapped to the main contactor disconnection drive circuit, the execution status feedback segment is mapped to the main contactor disconnection feedback circuit, the main power response segment is mapped to the main contactor main contact or output disconnection circuit, and the output regulation segment is mapped to the output residual current release circuit. For the protection output cut-off action category, the control execution segment is mapped to the protection control logic or protection command transmission link, the execution status feedback segment is mapped to the protection execution status feedback link, the main power response segment is mapped to the protection cut-off execution circuit, and the output regulation segment is mapped to the residual output elimination circuit after protection cut-off. Each combination of the above action categories and abnormal link locations is associated with a specific candidate fault object identifier. The correspondence between all combinations and identifiers is entered into the multi-condition action dependency configuration table to form a fault object mapping relationship.

[0103] The present invention is further configured such that forming a motion acquisition record includes:

[0104] Under a unified time reference, obtain the control command corresponding to the current action node and record the time when the control command was issued;

[0105] Starting from the moment the command is issued, within the response observation interval limited by the response observation duration, the feedback state of the control object corresponding to the current action node and the feedback acquisition time corresponding to each feedback state are continuously acquired, and the feedback states are arranged in time sequence according to the feedback acquisition time to form a feedback state sequence.

[0106] Based on the electrical response parameter type corresponding to the current action node, within the benchmark value interval with the instruction issuance time as the termination time and the benchmark value duration as the interval length, each electrical response parameter and its corresponding response acquisition time are obtained, and each electrical response parameter is arranged in time sequence according to the response acquisition time to form a benchmark parameter sequence.

[0107] Within a response observation interval, which starts at the time of instruction issuance and has a duration of response observation as its length, each electrical response parameter and its corresponding response acquisition time are acquired. The electrical response parameters are then arranged in chronological order according to the response acquisition time to form an observation parameter sequence.

[0108] The current action node identifier, controlled object identifier, control command, command issuance time, feedback status sequence, reference parameter sequence, and observation parameter sequence are associated to form the action acquisition record corresponding to the current action node. Specifically, a unified time base is established on the debugging control terminal side. The debugging control terminal provides this unified time base signal to the charging controller, power module communication interface, contactor status acquisition interface, and electrical parameter acquisition interface. When the charging controller issues a control command, it marks the timestamp according to the unified time base. When the contactor status acquisition interface reports the feedback status, it marks the timestamp according to the unified time base. When the electrical parameter acquisition interface samples voltage or current, it marks the timestamp according to the unified time base. This ensures that the control command, feedback status, and electrical response parameters all carry the time identifier under the unified time base in subsequent processing, eliminating the need to calculate the time offset for each data source separately. Regarding the acquisition of control commands and command issuance times, when executing the current action node, the controlled object identifier and control command corresponding to the action node are read from the multi-condition action dependency configuration table. The debugging control terminal then uses the charging control... The device sends the control command to the controlled object and records the actual time of the control command issuance under a unified time reference as the command issuance time. Taking the command issuance time as the starting time, a range equal to the response observation time is extracted as the response observation range. Within the response observation range, the feedback status returned by the controlled object corresponding to the current action node and its corresponding feedback acquisition time are continuously collected according to the unified time reference. The specific content of the feedback status is determined according to the action category. Among them, the power module start action node corresponds to the power module ready status, the precharge contactor closing action node corresponds to the precharge contactor closing feedback status, the main contactor closing action node corresponds to the main contactor closing feedback status, the low target current adjustment action node and the high target current adjustment action node both correspond to the power module current adjustment command reception confirmation status, the main contactor disconnection action node corresponds to the main contactor disconnection feedback status, and the protection output cut-off action node corresponds to the protection cut-off execution status. All the collected feedback statuses are arranged in chronological order of the feedback acquisition time to form a feedback status sequence.Using the instruction issuance time as the termination time, a period equal to the duration of the baseline value is extracted forward as the baseline value interval. Based on the electrical response parameter type corresponding to the current action node, electrical response parameters and their corresponding acquisition times are continuously collected within the baseline value interval according to a unified time base. The electrical response parameter type is determined by the action category. The electrical response parameter type corresponding to the power module start action node is DC bus voltage; the electrical response parameter type corresponding to the pre-charge contactor closing action node is output voltage; the electrical response parameter type corresponding to the low target current adjustment action node and the high target current adjustment action node is output current; the electrical response parameter type corresponding to the main contactor opening action node and the protection output disconnection action node is output current; and the electrical response parameter type corresponding to the main contactor closing action node is the voltage difference between the DC bus voltage and the output voltage. Within the baseline value interval, for each response acquisition time, both the DC bus voltage sample value and the output voltage sample value must be collected simultaneously. The voltage difference obtained by subtracting the two values ​​at the same sampling time is taken as the voltage difference for that time. The electrical response parameters are arranged chronologically according to their acquisition times to form a baseline parameter sequence. Starting from the command issuance time, a period equal to the response observation duration is extracted as the response observation interval. Within this interval, electrical response parameters and their corresponding acquisition times are continuously acquired according to a unified time base, based on the electrical response parameter type corresponding to the current action node. The method for determining the electrical response parameter type is consistent with the baseline parameter sequence. For the main contactor closing action node, the voltage difference obtained by subtracting the DC bus voltage sample value from the output voltage sample value at the same sampling time is used as the electrical response parameter for that time. All acquired electrical response parameters are arranged chronologically according to their acquisition times to form an observation parameter sequence. The action node identifier, controlled object identifier, control command and command issuance time, feedback state sequence, baseline parameter sequence, and observation parameter sequence of the current action node are interconnected, forming a single action acquisition record corresponding to the same current action node.

[0109] The present invention is further configured such that forming an action event record includes:

[0110] The control command corresponding to the current action node and the time when the control command was issued are defined as the control command event.

[0111] Extract the electrical response parameter values ​​from the reference parameter sequence, and determine the median of each electrical response parameter value as the response reference value;

[0112] Starting from the moment the command is issued, the feedback state sequence is detected sequentially according to the feedback acquisition time. When the feedback state reaches the target feedback state for the first time and maintains the target feedback state continuously for a valid duration from the corresponding feedback acquisition time, the corresponding feedback acquisition time is determined as the valid feedback time for executing the feedback event. When no target feedback state that has been continuously maintained for a valid duration is detected within the response observation interval, the execution feedback event is determined to not exist.

[0113] Based on the change of each electrical response parameter value relative to the response reference value in the observation parameter sequence, and the target change of the electrical response target value relative to the response reference value, the directional response progress corresponding to each response acquisition time is determined.

[0114] The directional response progress is detected sequentially according to the response acquisition time. When the directional response progress reaches the response trigger ratio for the first time, and remains at or above the response trigger ratio for an effective holding time from the corresponding response acquisition time, the corresponding response acquisition time is determined as the effective electrical response time of the electrical response event. When no directional response progress that has been continuously maintained for an effective holding time is detected within the response observation interval, the electrical response event is determined to not exist.

[0115] Extract the electrical response parameter values ​​from the observation parameter sequence that are located at the end of the response observation interval and whose interval length is the effective holding time, and determine the median of the extracted electrical response parameter values ​​as the final electrical response value.

[0116] The control command event, execution feedback event, electrical response event, response reference value, and electrical response final value are associated to form an action event record corresponding to the current action node. Specifically, the control command corresponding to the current action node and the time when the command is issued are jointly determined as the control command event. A reference parameter sequence is extracted from the action acquisition record. All electrical response parameter values ​​in the reference parameter sequence are arranged in ascending order, and the value in the middle position of the arrangement is taken as the response reference value. When the number of values ​​in the reference parameter sequence is even, the average of the two adjacent values ​​in the middle position of the arrangement is taken as the response reference value. Regarding the execution feedback event and... The extraction of effective feedback moments begins from the moment the command is issued. Feedback states in the feedback state sequence are detected sequentially from earliest to latest, based on the feedback acquisition time. When the feedback state corresponding to a certain feedback acquisition moment first reaches the target feedback state configured for that action node, and the feedback state remains at the target feedback state for a continuous period from that feedback acquisition moment for a duration that meets the configured effective holding time, the feedback acquisition moment that first reaches the target feedback state is determined as the effective feedback moment for executing the feedback event. If, after traversing the feedback state sequence within the response observation interval, the target feedback state that continuously maintains for the effective holding time is not detected, then the execution feedback event is determined. If a response is missing, a missing feedback flag is generated. For each response acquisition time in the observed parameter sequence, for the corresponding electrical response parameter value, first calculate the difference between the parameter value and the response baseline value as the actual change, then calculate the difference between the electrical response target value and the response baseline value as the target change. Multiply the actual change by the target change to obtain the directional product, and multiply the target change by itself to obtain the target squared change. The larger of the preset minimum positive correction and the target squared change is used as the actual denominator. The quotient obtained by dividing the directional product by the actual denominator is the directional response progress corresponding to that response acquisition time. Regarding the extraction of electrical response events and valid electrical response times... The directional response progress is detected sequentially according to the time sequence of response acquisition time. When the directional response progress corresponding to a certain response acquisition time reaches the configured response trigger ratio for the first time, and the directional response progress is not lower than the response trigger ratio and the duration of continuous maintenance reaches the configured effective maintenance duration from the response acquisition time, the response acquisition time that first reaches the response trigger ratio is determined as the effective electrical response time of the electrical response event. If the directional response progress that has been continuously maintained to the effective maintenance duration is not detected after traversing the observation parameter sequence within the response observation interval, the electrical response event is determined to be non-existent and an electrical response missing flag is generated.The final value interval is defined as the interval whose length equals the effective holding time is truncated from the end of the observed parameter sequence. This final value interval is located at the end of the response observation interval. Electrical response parameter values ​​corresponding to each response acquisition time within the final value interval are extracted. These extracted electrical response parameter values ​​are arranged in ascending order, and the middle value is taken as the final electrical response value. When the number of extracted values ​​is even, the average of the two adjacent values ​​at the middle position is taken as the final electrical response value. The effective feedback time or feedback missing flag of the control command event, the effective electrical response time or electrical response missing flag of the execution feedback event, the response reference value, and the final electrical response value are correlated and bound to the same action event record corresponding to the current action node.

[0117] The present invention is further configured such that forming the action link determination record includes:

[0118] Based on the existence status, occurrence order, response timing, and electrical response results of the execution feedback event and electrical response event, the action link judgment result corresponding to the current action node is determined according to the preset judgment order;

[0119] When neither the execution feedback event nor the electrical response event exists, the action link judgment result corresponding to the current action node is determined to be an abnormal control execution segment.

[0120] When the execution feedback event does not exist but the electrical response event does exist, the action link judgment result corresponding to the current action node is determined to be an execution status feedback segment anomaly.

[0121] When an execution feedback event exists but an electrical response event does not exist, the action link judgment result corresponding to the current action node is determined to be an anomaly in the main power response segment.

[0122] When both the execution feedback event and the electrical response event exist, and the effective electrical response time is earlier than the effective feedback time, the action link judgment result corresponding to the current action node is determined to be an execution status feedback segment anomaly.

[0123] When the effective feedback time is not earlier than the command issuance time, the effective electrical response time is not earlier than the effective feedback time, and the duration between the command issuance time and the effective feedback time exceeds the allowable duration from the command to the feedback, the action link judgment result corresponding to the current action node is determined as an abnormality in the control execution segment.

[0124] When the time between the instruction issuance time and the effective feedback time does not exceed the allowed time between instruction and feedback, and the time between the effective feedback time and the effective electrical response time exceeds the allowed time between feedback and electrical response, the action link judgment result corresponding to the current action node is determined to be an anomaly in the main power response segment.

[0125] When both the execution feedback event and the electrical response event exist, the order of occurrence of the effective feedback time and the effective electrical response time and the corresponding response timing both meet the action judgment conditions, and the response deviation ratio of the final value of the electrical response relative to the target value of the electrical response exceeds the allowable deviation ratio of the response, the action link judgment result corresponding to the current action node is determined as an output adjustment section anomaly.

[0126] When the existence status, occurrence order, response timing, and electrical response result of the execution feedback event and electrical response event all meet the action judgment conditions, the action link judgment result corresponding to the current action node is determined as the normal state of the action response chain.

[0127] The current action node identifier, action link judgment result, and abnormal link location are associated to form an action link judgment record corresponding to the current action node. Specifically, after forming the action event record, the control command event, execution feedback event and its valid feedback time or feedback missing flag, electrical response event and its valid electrical response time or electrical response missing flag, response baseline value, and electrical response final value in the record are read. These are then progressively judged according to a preset judgment order: event missing judgment, event sequence judgment, response time difference judgment, and response final value judgment. Each judgment level is executed only if the previous level has not determined an abnormality. Each action node... Ultimately, only one action link determination result is formed. When neither the execution feedback event nor the electrical response event exists, the action link determination result of the current action node is determined to be a control execution segment anomaly, with the anomaly link position corresponding to the control execution segment. When neither the execution feedback event nor the electrical response event exists, the action link determination result is determined to be an execution status feedback segment anomaly, with the anomaly link position corresponding to the execution status feedback segment. When neither the execution feedback event nor the electrical response event exists, the action link determination result is determined to be a main power response segment anomaly, with the anomaly link position corresponding to the main power response segment. When both the execution feedback event and the electrical response event exist, if the effective electrical response time is earlier than... If a valid feedback time is found, the action link determination result is determined to be an execution status feedback segment anomaly, with the anomaly link location corresponding to the execution status feedback segment. Provided that the valid feedback time is not earlier than the command issuance time and the valid electrical response time is not earlier than the valid feedback time, the actual duration between the command issuance time and the valid feedback time, and the actual duration between the valid feedback time and the valid electrical response time, are calculated. If the actual duration between the command issuance time and the valid feedback time exceeds the allowed duration from command to feedback, the action link determination result is determined to be a control execution segment anomaly, with the anomaly link location corresponding to the control execution segment. If the actual duration between the command issuance time and the valid feedback time does not exceed... If the actual time between the effective feedback moment and the effective electrical response moment exceeds the allowable time from feedback to electrical response, the action link determination result is determined to be an anomaly in the main power response segment, and the location of the anomaly link corresponds to the main power response segment. When both the execution feedback event and the electrical response event exist, and the occurrence order and duration relationship between the effective feedback moment and the effective electrical response moment meet the corresponding allowable conditions, the response deviation ratio is further calculated based on the final value of the electrical response, the target value of the electrical response, and the response reference value. If the response deviation ratio exceeds the allowable response deviation ratio, the action link determination result is determined to be an anomaly in the output regulation segment, and the location of the anomaly link corresponds to the output regulation segment.When both the execution feedback event and the electrical response event exist, the order and duration of the effective feedback time and the effective electrical response time meet the corresponding allowable conditions, and the response deviation ratio does not exceed the allowable response deviation ratio, the action link determination result of the current action node is determined to be in the normal state of the action response chain. In this state, no abnormal link position is associated. The current action node identifier, the action link determination result, and the corresponding abnormal link position are correlated. In the normal state of the action response chain, the abnormal link position field is empty. For results determined to be abnormal, the abnormal link position is filled with the corresponding specific link segment, thus forming the action link determination record corresponding to the current action node.

[0128] The present invention is further configured such that determining the fundamental anomaly, the propagation anomaly, and the dependent blocking action includes:

[0129] Based on the action dependencies, the execution status of each action node is associated with the action chain determination result;

[0130] When the action link determination result of the current action node is that the link is abnormal, and the current action node does not have a preceding action node or the preceding action node of the current action node is in a normal state of action response chain, the current action node is identified as a fundamental abnormal candidate action.

[0131] When the current action node completes execution according to the conditional execution method under the condition that the predecessor condition is not met, and the action link determination result of the current action node is that the link is abnormal, the current action node is determined to be a propagation abnormal action.

[0132] When the preceding action node of the current action node has a link anomaly, and the current action node does not execute according to the blocking execution method, or does not execute because the safe execution conditions are not met, the current action node is determined to be a dependent blocking action;

[0133] For abnormal propagation actions, trace along the preceding direction of the action dependency relationship, and identify the fundamental abnormal candidate action that is closest to the abnormal propagation action as the source of propagation;

[0134] For actions that depend on blocking, trace along the preceding direction of the action dependency and identify the fundamental abnormal candidate action that is closest to the action that depends on blocking as the source of blocking;

[0135] The fundamental anomaly candidate actions, propagation anomaly actions, dependency blocking actions, propagation sources, and blocking sources are associated with their corresponding action node identifiers to form action anomaly association records. Specifically, the action dependency relationships between each action node are read from the multi-condition action dependency configuration table. Each action node can be configured with zero or more preceding action nodes and zero or more succeeding action nodes. The preceding action node represents the upstream action node that must have been completed or met its conditions before the current action node can be executed. At the same time, the execution status of each action node is read from the execution log of the actual multi-condition execution process. The execution status includes executed, not executed, completed according to conditional execution, and not executed due to unmet safety execution conditions. The execution status is defined as follows: "Completed execution" indicates that the current action node was triggered and completed even though its predecessor conditions were not met. "Not executed due to unmet safety execution conditions" indicates that the current action node was not issued a command because safety interlocking or protection conditions were not met. The execution status of each action node is associated with the corresponding action link judgment result according to the action node identifier, serving as the data basis for subsequent anomaly classification. All action nodes are traversed. When the action link judgment result of an action node is an anomaly, the predecessor status of that action node is further checked. If the current action node has no predecessor action node, or if the action link judgment results of all predecessor action nodes of the current action node are in a normal action response chain state, then... If the link anomaly is not propagated from upstream actions but originates from the current action node itself, then the current action node is identified as the fundamental anomaly candidate action. By traversing the execution status and action link determination results of all action nodes, if an action node completes execution according to conditional execution mode while its predecessor condition is not met, and there is a node among the predecessor action nodes that is not in a normal action response chain state, and the action link determination result of this action node itself is a link anomaly, then the abnormal behavior of this action node is caused by the upstream unmet condition and manifested after its own execution. In this case, the current action node is identified as the propagating abnormal action. By traversing all action nodes, if a link anomaly exists in the predecessor action node of an action node... If the current action node fails to execute according to the blocking execution method, or fails to execute due to the failure to meet the safety execution conditions, it indicates that the failure of the current action node is due to the influence of upstream anomalies or safety condition propagation, rather than its own fault. In this case, the current action node is identified as a dependent blocking action. For each action node identified as a propagating abnormal action, trace its predecessor action node layer by layer upward along the predecessor direction of the action dependency relationship until the link start point. On the tracing path, check each predecessor node from near to far in terms of distance to see if it is a fundamental abnormal candidate action. The fundamental abnormal candidate action closest to the propagating abnormal action is identified as the propagation source. If no fundamental abnormal candidate action is found after tracing to the start point, the propagation source is recorded as empty.For each action node identified as a dependent blocking action, its predecessor action node is traced upwards layer by layer along the predecessor direction of the action dependency relationship until the link start point. Along the tracing path, each predecessor node is checked for fundamental anomaly candidate actions in order of distance from nearest to farthest. The fundamental anomaly candidate action closest to the dependent blocking action is identified as the blocking source. If no fundamental anomaly candidate action is found after tracing to the start point, the blocking source is recorded as empty. Each fundamental anomaly candidate action, each propagation anomaly action, and each dependent blocking action are associated with their respective corresponding action node identifiers. Each propagation anomaly action is associated with the action node identifier of its traced propagation source, and each dependent blocking action is associated with the action node identifier of its traced blocking source. All associations are summarized to form an action anomaly association record. In this record, the same action node can be labeled with multiple anomaly roles simultaneously. The propagation source and blocking source point in reverse to the corresponding fundamental anomaly candidate action in the form of action node identifiers.

[0136] The present invention is further configured such that forming one or more fault location records includes:

[0137] Obtain the action category and abnormal link location corresponding to each fundamental anomaly candidate action, and query the fault object mapping relationship based on the action category and abnormal link location to determine the candidate fault object and candidate fault object identifier corresponding to each fundamental anomaly candidate action.

[0138] Candidate actions of fundamental anomalies with the same candidate fault object identifier are assigned to the same fundamental anomaly evidence group, and the candidate fault objects corresponding to each fundamental anomaly evidence group are identified as target fault objects.

[0139] Obtain the instruction issuance time corresponding to each fundamental anomaly candidate action in the same fundamental anomaly evidence group, determine the fundamental anomaly candidate action with the earliest instruction issuance time as the first anomaly action, determine the debugging condition corresponding to the first anomaly action as the condition where the fundamental fault first occurs, and determine the abnormal link position corresponding to the first anomaly action as the link where the fundamental fault first occurs.

[0140] Based on the action anomaly association records, extract the propagation anomaly action whose propagation source corresponds to any fundamental anomaly candidate action in the fundamental anomaly evidence group, and the dependent blocking action whose blocking source corresponds to any fundamental anomaly candidate action in the fundamental anomaly evidence group.

[0141] The target fault object, the working condition in which the fundamental fault first occurs, the link in which the fundamental fault first occurs, the action chain judgment record corresponding to each candidate action of the fundamental anomaly, the propagation anomaly action and the dependent blocking action are associated to form the fault location record corresponding to the target fault object.

[0142] When multiple fundamental anomaly evidence groups are formed, fault location records are created for each group. Specifically, for each action node identified as a fundamental anomaly candidate action, the action category of the action node is parsed from its corresponding action node identifier. Simultaneously, the abnormal link location is read from the action link determination record corresponding to the action node. Using the combination of action category and abnormal link location as the query key, the fault object mapping relationship stored in the multi-condition action dependency configuration table is queried. The retrieved and matched candidate fault objects and their identifiers are assigned to the corresponding fundamental anomaly candidate actions, serving as the fault attribution information for those fundamental anomaly candidate actions. After all fundamental anomaly candidate actions have completed fault object parsing, they are grouped according to their candidate fault object identifiers. All fundamental anomaly candidate actions with the same candidate fault object identifier are grouped into the same fundamental anomaly evidence group. Each fundamental anomaly evidence group uniquely corresponds to a candidate fault object identifier, and the candidate fault object corresponding to that identifier is determined as the target fault object for that evidence group. For each fundamental anomaly evidence group, the instruction issuance time corresponding to each fundamental anomaly candidate action within the group is read. All instruction issuance times within the group are compared, and the fundamental anomaly candidate action corresponding to the instruction issuance time with the smallest value (i.e., the earliest time) is determined as the first anomaly action. The debugging condition corresponding to the normal action is determined as the condition where the fundamental fault first occurs. The abnormal link position corresponding to the first abnormal action is determined as the link where the fundamental fault first occurs. The action abnormality association record is read. For the current fundamental abnormality evidence group, the propagation abnormal actions in the action abnormality association record are traversed. When the propagation source action node identifier of a propagation abnormal action matches the action node identifier of any fundamental abnormality candidate action within the group, the propagation abnormal action is added to the propagation abnormal action set corresponding to the current evidence group. The same method is used to traverse dependent blocking actions. When the blocking source action node identifier of a dependent blocking action matches the action node identifier of any fundamental abnormality candidate action within the group, the dependent blocking action is blocked. Actions are categorized into the dependency blocking action set corresponding to the current evidence group. For each fundamental anomaly evidence group, the target fault object and its candidate fault object identifiers, the first occurrence condition of the fundamental fault, the first occurrence stage of the fundamental fault, the action link judgment record corresponding to each fundamental anomaly candidate action within the group, the set of propagation anomaly actions extracted from the group, and the set of dependency blocking actions extracted from the group are interconnected and bound into a fault location record. When there are multiple fundamental anomaly evidence groups, a fault location record is generated independently for each fundamental anomaly evidence group according to the above association formation process, and each fault location record points to an independent target fault object.

[0143] The present invention is further configured such that determining the results of multi-condition joint commissioning includes:

[0144] When all action nodes in each debugging path have been executed, and the action link judgment results corresponding to each action node are all in the normal state of the action response chain, the multi-condition joint debugging result is determined to be debugged successfully.

[0145] When one or more fundamental anomaly evidence groups are formed, the multi-condition joint debugging result is determined to be debugging failure, and a fault location record corresponding to each fundamental anomaly evidence group is output. The fault location record includes the target fault object, the operating condition in which the fundamental fault first occurs, and the link in which the fundamental fault first occurs. Specifically, it is confirmed that all action nodes in each debugging path have been executed, and the action link judgment result corresponding to each action node is in the normal state of the action response chain. The judgment criterion for all being executed is that the execution status of each action node is executed or executed according to the conditional execution method. When the aforementioned conditions are met, the multi-condition joint debugging result is determined to be debugging success, and no fault location record is output. When one or more fundamental anomaly evidence groups are formed, the multi-condition joint debugging result is determined to be debugging failure. For each fundamental anomaly evidence group, a fault location record corresponding to that evidence group is output. The fault location record includes the target fault object, the operating condition in which the fundamental fault first occurs, and the link in which the fundamental fault first occurs. When multiple fundamental anomaly evidence groups are formed, a fault location record corresponding to each fundamental anomaly evidence group is formed.

[0146] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for multi-condition joint debugging and fault location of DC fast charging piles, characterized in that, include: Multiple debugging paths are constructed based on the operating status of DC fast charging piles. The debugging conditions corresponding to each debugging path are set as action nodes. Action dependencies are established according to the execution order of each action node. The action judgment conditions and fault object mapping relationships corresponding to each action node are configured to form a multi-condition action dependency configuration. Based on the multi-condition action dependency configuration, the action nodes that meet the precursor conditions and the condition execution action nodes that meet the safety execution conditions are executed sequentially according to the action dependency relationship. The control command data, execution feedback data and electrical response data corresponding to each executed action node are obtained to form an action acquisition record. Based on the motion acquisition records, the control command events, execution feedback events, and electrical response events corresponding to each motion node are determined to form a motion event record; Based on the existence, occurrence order, response timing, and electrical response results of control command events, execution feedback events, and electrical response events in the action event record, determine the abnormal link location or normal state of the action response chain corresponding to each action node, and form an action link determination record. Based on the action dependency relationship, the action link judgment records corresponding to each action node are associated to determine the root anomaly, propagation anomaly, and dependency blocking action. Based on the action category and anomaly link location corresponding to the root anomaly, the target fault object is determined based on the fault object mapping relationship, forming one or more fault location records. The results of multi-condition joint debugging are determined based on the action link judgment record and fault location record, and the target fault object, the condition in which the fundamental fault first occurs, and the link in which the fundamental fault first occurs are output.

2. The method for multi-condition joint debugging and fault location of DC fast charging piles according to claim 1, characterized in that, The multiple debugging paths include normal adjustment paths and protection disconnection paths; The normal adjustment path includes, in sequence, the power module start-up action node, the pre-charge contactor closing action node, the main contactor closing action node, the low target current adjustment action node, the high target current adjustment action node, and the main contactor opening action node. The protection disconnection path includes, in sequence, the power module start-up action node, the pre-charge contactor closing action node, the main contactor closing action node, the low target current adjustment action node, and the protection output disconnection action node.

3. The method for multi-condition joint debugging and fault location of DC fast charging piles according to claim 2, characterized in that, Establishing action dependencies includes: Arrange the action nodes according to the execution order of each action node in the corresponding debugging path. The action node that is before and adjacent to the current action node in the same debugging path is determined as the preceding action node of the current action node, and a correspondence is established between the current action node identifier and the preceding action node identifier. Set the preceding action node to be in a normal state in the action response chain as the preceding condition of the current action node; Configure a predecessor exception handling method for the current action node with a predecessor action node. The predecessor exception handling method includes a blocking execution method and a conditional execution method. When the current action node's exception handling method is the blocking execution method, the existence of a link exception in the previous action node is set as the blocking condition for the current action node; When the current driver exception handling method is conditional execution, configure the safety execution conditions corresponding to the current action node. If the previous driver node has a link exception and the safety execution conditions are met, the current action node is determined as a conditional execution action. If the previous driver node has a link exception and the safety execution conditions are not met, the current action node is determined as a dependency blocking action. Associating the current action node identifier, the preceding action node identifier, the preceding condition, the preceding exception handling method, and the corresponding safe execution conditions forms an action dependency relationship.

4. The method for multi-condition joint debugging and fault location of DC fast charging piles according to claim 3, characterized in that, The configuration of the action determination conditions for each action node includes: For each action node, configure the control object, control object identifier, target feedback status, electrical response parameter type, electrical response target value, reference value duration, allowable duration from command to feedback, allowable duration from feedback to electrical response, response observation duration, effective holding duration, response trigger ratio, and allowable deviation ratio; Configure the target feedback state corresponding to the power module start-up action node as the power module ready state, and configure the corresponding electrical response parameter type as DC bus voltage; Configure the target feedback state corresponding to the precharge contactor closing action node as the precharge contactor closing feedback state, and configure the corresponding electrical response parameter type as the output voltage; Configure the target feedback state corresponding to the main contactor closing action node as the main contactor closing feedback state, and configure the corresponding electrical response parameter type as the voltage difference between the DC bus voltage and the output voltage. Configure the target feedback state corresponding to the low target current regulation action node and the high target current regulation action node as the power module current regulation command reception confirmation state, and configure the corresponding electrical response parameter type as output current; Configure the target feedback state corresponding to the main contactor disconnection action node as the main contactor disconnection feedback state, configure the target feedback state corresponding to the protection output cut-off action node as the protection cut-off execution state, and configure the electrical response parameter type corresponding to the main contactor disconnection action node and the protection output cut-off action node as the output current. The control command transmission link, action execution component, status feedback link, main power circuit and output regulation circuit are respectively set as candidate fault object types. The combination of action type and abnormal link location is used as the mapping index to establish the fault object mapping relationship between each mapping index and the corresponding candidate fault object.

5. The method for multi-condition joint debugging and fault location of DC fast charging piles according to claim 4, characterized in that, The creation of motion capture records includes: Under a unified time reference, obtain the control command corresponding to the current action node and record the time when the control command was issued; Starting from the moment the command is issued, within the response observation interval limited by the response observation duration, the feedback state of the control object corresponding to the current action node and the feedback acquisition time corresponding to each feedback state are continuously acquired, and the feedback states are arranged in time sequence according to the feedback acquisition time to form a feedback state sequence. Based on the electrical response parameter type corresponding to the current action node, within the benchmark value interval with the instruction issuance time as the termination time and the benchmark value duration as the interval length, each electrical response parameter and its corresponding response acquisition time are obtained, and each electrical response parameter is arranged in time sequence according to the response acquisition time to form a benchmark parameter sequence. Within a response observation interval, which starts at the time of instruction issuance and has a duration of response observation as its length, each electrical response parameter and its corresponding response acquisition time are acquired. The electrical response parameters are then arranged in chronological order according to the response acquisition time to form an observation parameter sequence. The current action node identifier, control object identifier, control command, command issuance time, feedback status sequence, baseline parameter sequence, and observation parameter sequence are associated to form the action acquisition record corresponding to the current action node.

6. The method for multi-condition joint debugging and fault location of DC fast charging piles according to claim 5, characterized in that, The creation of action event logs includes: The control command corresponding to the current action node and the time when the control command was issued are defined as the control command event. Extract the electrical response parameter values ​​from the reference parameter sequence, and determine the median of each electrical response parameter value as the response reference value; Starting from the moment the command is issued, the feedback state sequence is detected sequentially according to the feedback acquisition time. When the feedback state reaches the target feedback state for the first time and maintains the target feedback state continuously for a valid duration from the corresponding feedback acquisition time, the corresponding feedback acquisition time is determined as the valid feedback time for executing the feedback event. When no target feedback state that has been continuously maintained for a valid duration is detected within the response observation interval, the execution feedback event is determined to not exist. Based on the change of each electrical response parameter value relative to the response reference value in the observation parameter sequence, and the target change of the electrical response target value relative to the response reference value, the directional response progress corresponding to each response acquisition time is determined. The directional response progress is detected sequentially according to the response acquisition time. When the directional response progress reaches the response trigger ratio for the first time, and remains at or above the response trigger ratio for an effective holding time from the corresponding response acquisition time, the corresponding response acquisition time is determined as the effective electrical response time of the electrical response event. When no directional response progress that has been continuously maintained for an effective holding time is detected within the response observation interval, the electrical response event is determined to not exist. Extract the electrical response parameter values ​​from the observation parameter sequence that are located at the end of the response observation interval and whose interval length is the effective holding time, and determine the median of the extracted electrical response parameter values ​​as the final electrical response value. The control command event, execution feedback event, electrical response event, response baseline value, and electrical response final value are associated to form the action event record corresponding to the current action node.

7. The method for multi-condition joint debugging and fault location of DC fast charging piles according to claim 6, characterized in that, The formation of action chain determination records includes: Based on the existence status, occurrence order, response timing, and electrical response results of the execution feedback event and electrical response event, the action link judgment result corresponding to the current action node is determined according to the preset judgment order; When neither the execution feedback event nor the electrical response event exists, the action link judgment result corresponding to the current action node is determined to be an abnormal control execution segment. When the execution feedback event does not exist but the electrical response event does exist, the action link judgment result corresponding to the current action node is determined to be an execution status feedback segment anomaly. When an execution feedback event exists but an electrical response event does not exist, the action link judgment result corresponding to the current action node is determined to be an anomaly in the main power response segment. When both the execution feedback event and the electrical response event exist, and the effective electrical response time is earlier than the effective feedback time, the action link judgment result corresponding to the current action node is determined to be an execution status feedback segment anomaly. When the effective feedback time is not earlier than the command issuance time, the effective electrical response time is not earlier than the effective feedback time, and the duration between the command issuance time and the effective feedback time exceeds the allowable duration from the command to the feedback, the action link judgment result corresponding to the current action node is determined as an abnormality in the control execution segment. When the time between the instruction issuance time and the effective feedback time does not exceed the allowed time between instruction and feedback, and the time between the effective feedback time and the effective electrical response time exceeds the allowed time between feedback and electrical response, the action link judgment result corresponding to the current action node is determined to be an anomaly in the main power response segment. When both the execution feedback event and the electrical response event exist, the order of occurrence of the effective feedback time and the effective electrical response time and the corresponding response timing both meet the action judgment conditions, and the response deviation ratio of the final value of the electrical response relative to the target value of the electrical response exceeds the allowable deviation ratio of the response, the action link judgment result corresponding to the current action node is determined as an output adjustment section anomaly. When the existence status, occurrence order, response timing, and electrical response result of the execution feedback event and electrical response event all meet the action judgment conditions, the action link judgment result corresponding to the current action node is determined as the normal state of the action response chain. The current action node identifier, action link determination result, and abnormal link location are associated to form the action link determination record corresponding to the current action node.

8. The method for multi-condition joint debugging and fault location of DC fast charging piles according to claim 7, characterized in that, Identifying the underlying anomaly, propagation anomaly, and dependent blocking actions includes: Based on the action dependencies, the execution status of each action node is associated with the action chain determination result; When the action link determination result of the current action node is that the link is abnormal, and the current action node does not have a preceding action node or the preceding action node of the current action node is in a normal state of action response chain, the current action node is identified as a fundamental abnormal candidate action. When the current action node completes execution according to the conditional execution method under the condition that the predecessor condition is not met, and the action link determination result of the current action node is that the link is abnormal, the current action node is determined to be a propagation abnormal action. When the preceding action node of the current action node has a link anomaly, and the current action node does not execute according to the blocking execution method, or does not execute because the safe execution conditions are not met, the current action node is determined to be a dependent blocking action; For abnormal propagation actions, trace along the preceding direction of the action dependency relationship, and identify the fundamental abnormal candidate action that is closest to the abnormal propagation action as the source of propagation; For actions that depend on blocking, trace along the preceding direction of the action dependency and identify the fundamental abnormal candidate action that is closest to the action that depends on blocking as the source of blocking; The fundamental abnormal candidate action, the propagation abnormal action, the dependent blocking action, the propagation source and the blocking source are associated with the corresponding action node identifiers to form an action abnormal association record.

9. The method for multi-condition joint debugging and fault location of DC fast charging piles according to claim 8, characterized in that, Creating one or more fault location records includes: Obtain the action category and abnormal link location corresponding to each fundamental anomaly candidate action, and query the fault object mapping relationship based on the action category and abnormal link location to determine the candidate fault object and candidate fault object identifier corresponding to each fundamental anomaly candidate action. Candidate actions of fundamental anomalies with the same candidate fault object identifier are assigned to the same fundamental anomaly evidence group, and the candidate fault objects corresponding to each fundamental anomaly evidence group are identified as target fault objects. Obtain the instruction issuance time corresponding to each fundamental anomaly candidate action in the same fundamental anomaly evidence group, determine the fundamental anomaly candidate action with the earliest instruction issuance time as the first anomaly action, determine the debugging condition corresponding to the first anomaly action as the condition where the fundamental fault first occurs, and determine the abnormal link position corresponding to the first anomaly action as the link where the fundamental fault first occurs. Based on the action anomaly association records, extract the propagation anomaly action whose propagation source corresponds to any fundamental anomaly candidate action in the fundamental anomaly evidence group, and the dependent blocking action whose blocking source corresponds to any fundamental anomaly candidate action in the fundamental anomaly evidence group. The target fault object, the working condition in which the fundamental fault first occurs, the link in which the fundamental fault first occurs, the action chain judgment record corresponding to each candidate action of the fundamental anomaly, the propagation anomaly action and the dependent blocking action are associated to form the fault location record corresponding to the target fault object. When multiple fundamental anomaly evidence groups are formed, fault location records are generated for each fundamental anomaly evidence group.

10. The method for multi-condition joint debugging and fault location of DC fast charging piles according to claim 9, characterized in that, The results of the multi-condition joint commissioning were determined as follows: When all action nodes in each debugging path have been executed, and the action link judgment results corresponding to each action node are all in the normal state of the action response chain, the multi-condition joint debugging result is determined to be debugged successfully. When one or more fundamental anomaly evidence groups are formed, the multi-condition joint debugging result is determined to be a debugging failure, and the fault location record corresponding to each fundamental anomaly evidence group is output. The fault location record includes the target fault object, the operating condition in which the fundamental fault first occurs, and the link in which the fundamental fault first occurs.

Images