Tracking Fault Origins and Trip Signals on APL MotSpdCL Motors

To diagnose sudden machine trips on electric drives controlled by the PCS 7 Advanced Process Library (APL) block MotSpdCL (FB1854), track the critical protection, interlock, monitoring, and command pins in CFC and WinCC. The primary shutdown origins are Protect (interlock with protection/emergency stop), Intlock (process interlock requiring reset), and Permit (activation enable). Check feedback monitoring errors via MonDynErr / MonStaErr (run feedback lost), thermal trips via Trip / TripErr, group faults via GrpErr, and internal calculation faults via ErrorNum. In WinCC, open the MotSpdCL faceplate standard and preview views to inspect active interlock condition bypasses.

APL MotSpdCL Shutdown Logic: Interlocks vs Automatic Commands

The Advanced Process Library block MotSpdCL (FB1854, Controllable Speed Motor) governs variable-frequency drives (VFDs) operating in continuous process environments. When an essential production machine halts unexpectedly, the trip originates from one of three distinct software layers:

Safety and Process Interlocks: Hardwired safety relays, emergency stops, or high-vibration trips assert through interlock inputs, shutting down the drive regardless of operating mode (Manual or Auto).
Dynamic Feedback Monitoring: The block initiates a start command, but physical run feedback contacts (FbkFwd / FbkRev) fail to arrive within the configured static or dynamic monitoring time (MonTiDynamic).
Automatic Sequence Logic: Higher-level Sequential Function Charts (SFC) or upstream step chains issue an automated stop command (StopAut = 1 or drop FwdAut = 0).

Disentangling these causes requires systematic inspection of the block's input/output status words.

Critical Control and Diagnostic Signal Pins on FB1854

When interrogating MotSpdCL online in CFC or WinCC, examine these foundational pins:

Protect (Interlock with Protection): Highest-priority interlock. If Protect.Value = 0, the motor stops immediately and cannot be restarted in any mode. The operator faceplate displays the blue padlock symbol.
Intlock (Interlock without Protection): Operational interlock. If Intlock.Value = 0, the motor stops. If configured with Feature.Bit22 = 1 (interlock latching), the motor requires an operator reset even after conditions normalize.
Permit (Activation Enable): Governs motor start from standstill. If Permit.Value = 0, an idle motor is blocked from starting. (Standard behavior allows a running motor to continue running if Permit drops, unless configured otherwise).
Trip: External motor protection relay or circuit breaker auxiliary contact. If Trip.Value = 0, TripErr triggers.
MonDynErr / MonStaErr: Dynamic and static run feedback monitoring errors. Set when drive run feedback drops during operation.
GrpErr: Group error output combining all active monitoring, interlock, and drive device faults.
ErrorNum: Integer output indicating internal parameter faults (e.g. invalid speed limits, missing interconnection).

Step-by-Step Fault Tracing Workflow in CFC and WinCC

Execute this troubleshooting sequence immediately following an unexpected machine stop:

Inspect WinCC Operator Faceplate:
- Click the motor block icon to open the MotSpdCL faceplate.
- Switch to the Standard View: Look at the interlock status field. If a padlock is closed or blinking, click the interlock button to navigate to the active interlock logic block (Intlk02 / Intlk04 / Intlk08).
- Switch to the Preview View: Identify whether the stop was requested by 'Automatic', 'Manual', or 'Interlocked'.
Check WinCC Alarm Logging:
- Open the WinCC Alarm List and filter for the motor tag name.
- Look for alarms: 'Feedback monitoring error', 'Motor protection tripped', or 'Interlock active' to identify the exact second of trip.
Online CFC Signal Inspection:
- Open the CFC chart containing the MotSpdCL instance.
- Turn on Test -> Test Mode.
- Inspect GrpErr and ErrorNum. If GrpErr = 1, trace backwards from Protect, Intlock, Trip, and MonDynErr.
- Check the speed setpoint pins: SP_Ext (external setpoint) and Rbk (readback speed from FbDrive).

MotSpdCL Diagnostic Pin and Status Parameter Reference

The following table summarizes essential fault-tracing parameters for APL block MotSpdCL (FB1854):

Signal Pin NameData TypePin DirectionHealthy StateDescription / Trip MechanismProtectStruct (BOOL+ST)Input1 (True)Interlock with protection; shuts down motor in all modesIntlockStruct (BOOL+ST)Input1 (True)Process interlock; stops motor; may require operator resetPermitStruct (BOOL+ST)Input1 (True)Start permit; blocks start from standstill if 0TripStruct (BOOL+ST)Input1 (True)External thermal overload / breaker fault inputStopAutStruct (BOOL+ST)Input0 (False)Automatic stop command from SFC or step logicFwdAut / RevAutStruct (BOOL+ST)Input1 (When running)Automatic forward/reverse run commandMonDynErrBOOLOutput0 (False)Dynamic monitoring error; run feedback lost while runningGrpErrBOOLOutput0 (False)Group fault summary output combining all errorsErrorNumINTOutput0Internal block calculation error code

[!NOTE]
Commercial Accuracy Notice: The MotSpdCL block is an integral component of the SIMATIC PCS 7 Advanced Process Library > (6ES7658-1EX58-0YA5). Utilizing MotSpdCL consumes standard AS and OS Process Objects, but signal diagnostic tracking > consumes no additional licenses.

Verification

Verify that the fault origin is identified and that the drive restarts safely:

Interlock Clearance: Confirm that the offending sensor condition (e.g. lube oil pressure restored) returns to 1 on the Intlk block inputs.
Operator Reset: In the MotSpdCL faceplate, click the Reset button (if interlock latching is enabled). Verify that the fault indicator resets and the padlock opens.
Controlled Motor Restart: Issue a start command in Manual mode, then transfer control back to Automatic. Confirm that FbkRun asserts and the motor stabilizes at commanded speed.

Limitations and Operational Precautions

Adhere to these operational boundaries when diagnosing motor trips:

Feature Bit Configuration: Check Feature.Bit22 (Reset interlocks in manual mode) and Feature.Bit24 (Local authorization). Improper feature bit configuration can lock motors in stopped state after faults clear.
Fluttering Sensors: If an interlock input flutters for a single CPU scan cycle, standard CFC online monitoring may miss it. Deploy first-in detection blocks (FirstIn) or check WinCC Alarm Logging to capture transient drops.
Inverter Fault Codes: MotSpdCL manages the control logic, but internal drive trips (e.g. overcurrent, DC bus overvoltage) must be checked on the physical VFD or via the FbDrive parameter FaultNum.

Engineer FAQ

What is the difference between Protect and Intlock on MotSpdCL?

Protect is the highest-level protection interlock (emergency stop, machine damage prevention); it stops the motor in all modes and cannot be bypassed. Intlock is a process interlock (e.g. tank level low) that can be bypassed in local mode.

Why did the motor stop even though all interlocks are healthy?

Check StopAut and FwdAut. An upstream sequential function chart (SFC) or safety interlock block may have withdrawn the automatic run command. Alternatively, check MonDynErr to see if run feedback was momentarily lost.

Why does the motor require a Reset after an interlock clears?

If Feature.Bit22 = 1 is configured, the block latches the interlock trip to ensure an operator explicitly acknowledges and verifies the field condition before the motor can restart.

What does ErrorNum = 1 mean on MotSpdCL?

ErrorNum = 1 typically indicates an invalid parameter configuration, such as the low speed limit (SP_LoLim) being set higher than the high speed limit (SP_HiLim).