C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

How to Diagnose and Prevent Motor 'Ghost Tripping' Without Alarms in SIMATIC PCS 7

How to Diagnose and Prevent Motor 'Ghost Tripping' Without Alarms in SIMATIC PCS 7

To diagnose and eliminate motor 'ghost tripping'—where a motor unexpectedly stops in SIMATIC PCS 7 without triggering a feedback fault alarm on WinCC—engineers must analyze signal bounce on digital inputs and verify CFC execution order. In the Advanced Process Library (APL) MotL block, a running motor only generates a Feedback Fault alarm if the run feedback signal (FbkRun) drops continuously for longer than the static monitoring time (MonTiStatic, typically 2 to 5 seconds). If a motor trips without this alarm, the stop command is originating from an external interlock (Permit, Intlock, Protect) or an automation stop signal (StopAut) that drops momentarily (100–200 ms) due to contact chatter or sensor jitter. Implementing an on-delay debounce timer (TON), activating channel flutter filtering on Pcs7DiIn, and latching interlocks resolves the issue.

Table of Contents

Root Cause Analysis: Why Motors Trip Without Feedback Fault Alarms

When a running motor controlled by a PCS 7 motor block (such as APL MotL or legacy Standard Library MOTOR) suddenly de-energizes without an operator-visible alarm, plant personnel often report a 'ghost trip'.

Detailed high-speed signal logging (e.g., using PLC-Analyzer or high-frequency trend recorders) typically reveals that the feedback signal (FbkRun or FB_ON) or a safety sensor dropped for a brief interval (100 to 300 ms). However, because the motor block's static monitoring timer (MonTiStatic) is configured for a longer period (e.g., 3.0 to 5.0 seconds), the block does not register a feedback fault.

Instead, the motor de-energization is caused by one of two underlying mechanisms:
1. Transient Interlock De-assertion: An upstream interlock input (Intlock, Protect, or Permit) or automatic stop command (StopAut) is linked to a field sensor or upstream PLC output that dropped momentarily. When an interlock drops, MotL executes a normal commanded shutdown, clearing the start output (Start) without asserting a fault alarm.
2. First-Out Reset Logic: If First-Out alarming is configured on interlock blocks (e.g., Intlk02, Intlk04) but the fault condition self-cleared before the alarm scan cycle, the trip event occurs without latching an alarm state.

APL Feedback Monitoring Mechanics: MonTiDynamic vs MonTiStatic

Understanding how the APL MotL block monitors field feedback is vital for diagnostic troubleshooting:

1. Dynamic Monitoring (MonTiDynamic)

Activated when a start or stop command transitions the drive state. When Start is asserted, the drive has MonTiDynamic seconds (e.g., 5.0 s) for FbkRun to transition from 0 to 1. If feedback is not received within this window, the block enters a dynamic feedback fault, de-energizes the start output, and generates an alarm.

2. Static Monitoring (MonTiStatic)

Activated once the motor has reached a steady running state (FbkRun = 1) and the dynamic monitoring time has elapsed. If FbkRun drops back to 0 while the motor block is still commanding run (Start = 1), an internal timer begins counting.
* If FbkRun recovers to 1 within MonTiStatic seconds, the timer resets and no fault is reported.
* Only if FbkRun remains 0 continuously for greater than MonTiStatic does the block trip with a 'Feedback Run Fault' (FbkRunOut = 1) and generate an OS message.

Therefore, a brief 200 ms dropout of FbkRun cannot trip the motor via feedback monitoring. If the motor stopped, the drop occurred on an interlock pin or stop command.

Identifying Transient Drops in External Interlocks and Permissives

In many plant architectures, the running feedback signal is wired not only to FbkRun, but is also cross-connected into upstream interlock logic, permissive chains, or external drive safety circuits.

For example, if an auxiliary PLC (such as an S7-300 controlling drive excitation or lube oil) generates an interlock contact wired to Protect on the PCS 7 AS, and that auxiliary signal flickers for 150 ms due to sensor vibration:
* The Protect input drops to 0.
* The MotL block immediately de-asserts Start as a commanded safety shutdown.
* Because a commanded stop was executed, the feedback monitoring timer is cancelled.
* The operator station shows the motor simply changing state from 'Running' to 'Stopped' with no trip alarm.

CFC Runtime Group Sequencing and Signal Debounce Implementation

To eliminate ghost tripping caused by contact chatter, electromagnetic interference, or sensor jitter:

1. Implement Digital Input Debounce Filtering

In the channel driver block (Pcs7DiIn), configure input smoothing:
* Set FlutterEn = 1 to enable flutter suppression.
* Set FlutterCount and FlutterTime to filter out pulses shorter than the mechanical chatter threshold.
Alternatively, insert an elementary TimerP or TON block between the raw field input and the interlock logic with a debounce time of PT := T#300ms.

2. Configure Interlock Latching

On the upstream interlock block (Intlk02 / Intlk04), ensure that transient trips are latched so operators can identify the initiating sensor:
* Set L_Status and configure the reset mechanism (RstOp or automatic reset upon operator acknowledgement).
* This guarantees that even a 100 ms trip event remains visible on the faceplate First-Out display.

3. Verify CFC Execution Sequence

Ensure proper execution order within the cyclic interrupt OB (e.g., OB35):
1. Input Channel Drivers (Pcs7DiIn) must execute first.
2. Interlock and Logic Blocks (Intlk02) must execute second.
3. Control Blocks (MotL) must execute third.
4. Output Channel Drivers (Pcs7DiOu) must execute last.

Diagnostic Signal Comparison and Filter Parameter Matrix

The following table summarizes motor trip causes, monitoring timers, and diagnostic indicators:

Trip MechanismInitiating InputTrigger DurationWinCC Alarm GeneratedRemediation ActionStatic Feedback FaultFbkRun / FB_ON> MonTiStatic (e.g., 5 s)Yes (Feedback Error)Inspect auxiliary contactor, wiring continuityTransient Interlock DropIntlock / ProtectInstantaneous (1 cycle / >50 ms)None (or momentary First-Out)Add TON debounce filter; latch interlock blockCommanded Automation StopStopAutInstantaneous (1 cycle)None (normal stop)Trace upstream step sequence / CFC logicDynamic Start FailureFbkRun missing after start> MonTiDynamic (e.g., 5 s)Yes (Start Error)Check MCC contactor pick-up time, drive rampChannel Card FlutterRaw I/O terminal50–200 ms pulsesSporadic / NoneEnable FlutterEn on Pcs7DiIn; replace dry contact

Implementing proper signal filtering prevents nuisance shutdowns while maintaining plant protection integrity.

Verification

To verify that motor ghost tripping has been resolved:
1. In CFC test mode, verify that MonTiStatic and MonTiDynamic are parameterized with appropriate operational delays (e.g., 3.0 s and 5.0 s).
2. Simulate a brief 200 ms interruption on the raw field digital input; confirm that the debounce filter (FlutterEn or TON) prevents the interlock from dropping.
3. Verify that if a legitimate permanent trip occurs (> 5.0 s), the MotL block de-energizes the output and generates the 'Feedback Run Fault' alarm on WinCC.
4. Confirm that the interlock faceplate displays and latches the initiating fault condition until operator acknowledgement.

Limitations and Operational Precautions

  • Never increase interlock debounce delay times on personnel safety or emergency stop circuits; functional safety interlocks must trip instantly without software filtering.
  • Do not set MonTiStatic excessively high (> 10 s) on large mechanical equipment, as prolonged operation without feedback confirmation can damage coupling components.
  • Ensure that any external PLC sending digital feedback to the PCS 7 controller has synchronized scan cycles and solid-state or debounced relay outputs.
  • Verify that channel driver flutter suppression does not mask genuine loose wiring connections at field terminal strips.

Engineer FAQ

Why does the motor stop if FB_ON dropped for only 200 ms when MonTiStatic is 5 seconds?

A 200 ms drop on FB_ON will not trip the motor through the feedback monitoring logic. The stop occurs because the signal is also wired into an external interlock, emergency stop, or permissive input that trips instantaneously without delay.

How can I find which interlock caused the motor to stop if no alarm was logged?

Check the First-Out (FirstIn) display on the associated Intlk02 or Intlk04 block. If latching is not enabled, enable feature bit Feature.Bit22 (Update fault status) or configure L_Status to latch trip events.

What is the difference between MotL Protect and Intlock inputs?

Protect is an interlocking condition with protection (active in all operating modes including manual), whereas Intlock is a standard interlock condition that can be bypassed or configured differently in manual mode.

Technical References

Related Articles

Related Tags

  • Motor Ghost Tripping
  • MotL Block
  • Feedback Monitoring
  • Interlock Architecture
  • Signal Debounce
6 respuestas