Woodward HighPROtec MCDLV4, Руководство пользователя

Страница: 1123 / 1275

Service and Commissioning Support
The behavior is basically the same if there has been an assignment of a signal to the
Ex ForcePost parameter, and
if this signal is becoming active during the simulation, so that it interrupts the Pre-fault or Failure state: With
ProtCom being
active, the local device first sends a corresponding signal to the remote device, then waits for a time
corresponding to the propagation delay of the signal, until finally it makes the transition to the Post-fault state.
If the Protection Communication is
inactive (regardless whether this is due to
disconnected FO cables, bad connection quality or a temporary blocking of the
ProtCom module), only the local Fault Simulator is started, and no trigger signal
is sent to the remote device. (After all, the behavior of the local device is
exactly like starting the Fault Simulator on a stand-alone protective device.)
If the ProtCom becomes inactive while the Fault Simulators are already running then both Simulators continue
independently (without being interrupted or blocked), using only the respective local currents (assuming zero values
for the remote currents).
As mentioned before, the simulation is terminated, if a phase current exceeds
0.1 ⋅ In. This happens immediately on both devices, without any additional
ProtCom delay. (This may generate a short false differential current, but since
all protection functions are in a reset phase for about 100 ms anyway (see the
beginning of the “Fault Simulator” chapter), this false differential current cannot
trigger any false trip decision.)
1123 MCDLV4 DOK-HB-MCDLV4-2E