In some examples, the primary IED 44 and the IEDs 46 and 48 may be used in conjunction to perform functions of the power distribution system. For example, the primary IED 44 and the IEDs 46 and 48 may be used to monitor and protect a particular portion of an electrical grid, and may communicate protection signals to and from each other IED. The IED 46 may provide supplemental capabilities (e.g., backup capabilities) for the IED 48, the primary IED 44 may send protection signals to the IED 46 based on sensed power distribution conditions, and so on. Further, the illustrated IEDs may rely on each other in response to anomalous conditions, and thus it may be desirable to test the illustrated IEDs together and/or simultaneously to properly characterize behavior of the illustrated IEDs in response to anomalous conditions.

While primary IED 44 is illustrated as the primary IED, in other examples, the IED 46 or the IED 48 may assume the role of primary IED. Each IED in the system 40 may include primary IED capabilities, and which IED of the system 40 is designated as the primary IED may depend on, for example, which IED the computing device 42 is communicatively coupled to. That is, the system 40 may be arranged with any of the illustrated IEDs as a primary IED. In any case, as will be described in more detail below, the primary IED 44 may provide capabilities for the IEDs 46 and 48 when performing an operation to test the system 40.

FIG. 5 is a schematic block diagram illustrating the system 40 in which simulation data 52 is distributed to the primary IED 44 and the IEDs 46 and 48. The simulation data 52 may be stored in the computing device 42 and selected by an operator of the computing device 42, generated by the computing device 42, or input by an operator of the computing device 42 via, for example, the UI of the computing device 42. Further, the simulation data 52 may include power delivery system measurements previously acquired by the primary IED 44, the IED 46, and/or the IED 48. The previously acquired power delivery system measurements may be representative of an electrical fault or other event of interest, and may be acquired by the primary IED 44, the IED 46, and/or the IED 48 acting as digital fault recorders (DFRs), for example. In the illustrated example, simulation data 52 is sent from the computing device to the primary IED 44 via, for example, a wired communicative connection (e.g., USB, ethernet, etc.). When the primary IED 44 receives the simulation data 52, it may send (e.g., forward, route) the simulation data 52 to the IED 46 and the IED 48 over, for example, ethernet connection.

Prior to or along with distribution of the simulation data 52, the primary IEDs 44 and the IEDs 46 and 48 may be placed in test configuration mode. As described herein, the test configuration mode may disable the protection communications of the IED, may block the warnings and alarms associated with the IED, and may enable test and/or simulation capabilities of the IED. Additionally, the test configuration mode may enable the IED to receive, load and configure simulation data, including event playback files and playback parameters. Each IED may store the simulation data in memory for later use, such as when a testing process is initiated.

FIG. 6 is a schematic block diagram illustrating the system 40 when a test is initiated at the primary IED 44 and the IEDs 46 and 48. As described herein, the illustrated IEDs may be placed in test mode prior to or along with a test being initiated. The test mode may include the protection communications of each of the IEDs being enabled. However, under the test configuration mode, the protection communications may not produce tangible protection outcomes in the power distribution system. For example, under the test configuration mode, the protection communications may be sent to and from IEDs 44, 46, and 48, but may be unable to trip a circuit breaker, sound an alarm, distribute warnings, and so on. Thus, faults or technical errors associated with the simulation data may not cause damage to the system 40 or an associated power distribution system, while protection signals may continue to be generated and transmitted for evaluation purposes.

The test may be initiated at the computing device 42 upon, for example, operator input via the UI or an automatic maintenance process. The computing device may then send a signal indicative of instructions to start the test 54 to the primary IED 44, and the primary IED may forward the instructions 54 to the IEDs 48 and 46. Additionally, the instructions 54 may include a time at which the test is to commence (e.g., 16:30 UTC, 2:00 p.m. EDT), or a countdown timer value (e.g., T-30 seconds) to start the test. As described herein, the primary IED 44 and IEDs 46 and 48 may maintain a common time via common time source 50. Common time source 50 may include, for example, a satellite, and the common time may be distributed via GNSS. In some examples, the common time may be generated at the primary IED 44 and distributed to the IEDs 46 and 48, and the primary IED 44 may control the timing of a testing procedure of the system 40.

FIG. 7 is a schematic block diagram illustrating the system 40 in which test results 56 are generated based on simulation data (e.g., simulation data 52) in response to the initiation of a test. The test results may be generated by the primary IED and the IEDs 46 and 48, and may represent protection signals (e.g., protection signals of a an 87L line current differential protection scheme), warnings, alarms, and/or other responses to the power distribution system conditions represented by the simulation data. For example, the simulation data may include an event report of an overcurrent condition and, in response, the IED 46 may generate test results 56 including instructions to trip a first circuit breaker, the primary IED 44 may generate test results 56 including instructions to trip a second circuit breaker, and the IED 48 may generate test results 56 instructions to activate a warning alarm. In another example, the simulation data 52 may include measurements previously recorded by the primary IED 44, the IED 46, and/or the IED 48, and the test results 56 may characterize behavior in response to the previously recorded measurements (e.g., as a “playback test”). Additionally, the test results may include a label (e.g., header portion, tag, etc.) that associates the test results 56 with a particular IED. In any case, the test results 56 may be routed (e.g., funneled) through the primary IED 44 to the computing device. In some examples, the primary IED 44 compiles the test results generated at the primary IED 44 along with the test results 56 generated by all connected IEDs (e.g., IEDs 46 and 48) before sending the compiled test results to the computing device 42.

Because the protection communications channels are operational during the test mode 34, the test results 56 may also characterize the behavior of the communication channels. For example, the test results 56 may include timestamps indicating the speed of the communication channels. Or, the test results may indicate an incorrect IED operation due to incorrect or missing data in the protection communications. In some examples, the illustrated IEDs may implement data security techniques to ensure the security and/or integrity of the communication channels.