Implementing Process Value Change Watchdogs and Motor Interlocks in SIMATIC PCS 7

In SIMATIC PCS 7 process applications where a motor or pump must verify physical material movement—such as detecting a measurable tank level change within a specified timeout following motor start—engineers construct an automated watchdog scheme using standard Advanced Process Library (APL) blocks. By coupling an analog difference or rate-of-change calculation with an on-delay timer block (TimerP) and interconnecting the timer output to the motor block's protective interlock (Protect) and external message (ExtMsg1) inputs, the system autonomously shuts down the motor and generates an operator alarm if the process variable remains stagnant.

Process Variable Change Supervision Principles

In industrial fluid handling and solids conveying, starting an electric motor (e.g. transfer pump, agitator, screw conveyor) without establishing physical flow or level change indicates serious mechanical or process failure:
- Failure Scenarios: Closed manual block valves, pump cavitation, dry running, broken mechanical drive couplings, or line blockages.
- Supervision Requirement: Upon receiving a valid run command, the automation system must confirm that an associated analog process variable (such as tank level, vessel pressure, or mass flow) deviates from its initial baseline value by a minimum threshold (Delta_PV) within a designated monitoring window (T_Watchdog). If the value fails to respond, the motor must trip automatically to prevent seal damage or tank overflow.

CFC Logic Architecture: Rate Detection, TimerP, and MotL

Because PCS 7 does not feature a single monolithic 'level change watchdog' block, engineers assemble the function using modular APL building blocks:

Baseline Capture and Deviation:
- Use an APL sample-and-hold logic or mathematical subtraction (Sub02) to compute the absolute difference:
$$\Delta L = |\text{Level}{\text{Current}} - \text{Level}|$$}
- Compare $\Delta L$ against minimum expected movement threshold (MinDelta, e.g. 2.0% level change).
Timer Supervision with TimerP:
- Place a TimerP block (FB 1810) configured in On-Delay Mode (Mode = 2).
- Wire the motor run feedback (MotL.FbkRun.Value) to TimerP.In.
- When $\Delta L \ge \text{MinDelta}$, reset the timer or disable execution.
- If the timer reaches its preset duration (Ti, e.g. 30 seconds) while $\Delta L < \text{MinDelta}$, output TimerP.Out transitions to 1.
Tripping the Motor and Alarming:
- Invert TimerP.Out and wire it into the Protect input of MotL (protective interlock with reset).
- Wire TimerP.Out into MotL.ExtMsg1 to generate a timestamped alarm: 'Pump Tripped: No Level Change Detected'.

Differentiating Protective Interlocks (Protect) vs Permissive (Intlock)

Selecting the correct interlocking input on MotL is vital for operator safety:

Using Protect (Recommended): The Protect input acts as an equipment protective trip. When Protect trips (transitions to 0), the motor stops immediately. Critically, when the timer condition clears, the motor remains tripped and cannot restart automatically until an authorized operator issues a manual reset command (RstOp or faceplate Reset button).
Using Intlock (Not Recommended for Watchdogs): The standard Intlock input trips the motor, but as soon as the interlocking condition returns to 1, a motor in Automatic mode would immediately attempt to restart, creating hazardous equipment hunting.

Watchdog Parameter Configuration and Signal Mapping Table

The following table details block interconnections for implementing a level change watchdog:

Source Block & PinTarget Block & PinSignal TypeOperational PurposeMotL.FbkRun.ValueTimerP.InBOOLStarts watchdog timing when motor run feedback confirms movementLevel_Diff_OKTimerP.ResetBOOLResets watchdog timer when measurable level change is confirmedTimerP.Out (Inverted)MotL.Protect.ValueBOOLTrips motor into safe stopped state if timeout expires before changeTimerP.OutMotL.ExtMsg1.ValueBOOLTriggers dedicated WinCC operator message in alarm logging banner16#80 (Constant)MotL.Protect.STBYTESets valid signal status for interlocking evaluation

Note: Configure the watchdog timer duration generously to allow for fluid inertia, deadband settling, and pipe filling times.

Verification

Verify watchdog tripping and reset behavior:
1. In WinCC Runtime, place the motor in Automatic mode and issue a start command.
2. Freeze or inhibit the tank level sensor in simulation mode so the level remains stagnant.
3. Observe TimerP.Time; verify the elapsed time accumulates towards the 30-second setpoint.
4. When 30 seconds expires, confirm that the motor trips immediately, MotL.ProtectAct flags 1, and the alarm 'Pump Tripped: No Level Change Detected' generates.
5. Restore the level signal; verify that the motor remains stopped until the operator clicks the Reset button on the MotL faceplate.

Limitations and Operational Precautions

Essential process control precautions:
- Set the timeout duration (Ti) longer than the physical piping filling delay; premature tripping will cause false nuisance shutdowns during normal startup.
- In vessels with turbulent surface waves, apply signal smoothing (filter time FilterTime on FbAnIn) to prevent false watchdog resets caused by surface sloshing.
- Ensure that the external message text configured on ExtMsg1 clearly identifies the failure mode so operators do not confuse the watchdog trip with an electrical overload.

Engineer FAQ

Can I use this watchdog on negative level changes (emptying tanks)?

Yes. By calculating the absolute value of the change ($|\Delta L|$), the logic supervises both filling (positive rate) and draining (negative rate) operations identically.

Where do I configure the text for ExtMsg1?

In SIMATIC Manager, right-click the MotL block in CFC, select Special Object Properties > Message, and enter your custom message text into the row corresponding to ExtMsg1.

Does TimerP consume a Process Object?

In modern PCS 7 APL, math and auxiliary timer blocks like TimerP or Sub02 do not consume Process Objects; POs are counted only on technological driver and control blocks.