Troubleshooting CEMAT C_GROUP Block Start and Interlock Failures

When a CEMAT group block C_GROUP (FB1010) fails to execute a start command in SIMATIC PCS 7, the root cause typically stems from unresolved group interlocks, subordinate drives not being ready in Automatic mode, or broken object coupling links. Forcing start command inputs on C_GROUP will not activate downstream equipment if any assigned object (C_DRIVE_1D, C_DRIVE_2D, C_DAMPER, or C_VALVE) exhibits an active protection interlock, an unacknowledged electrical fault, or a local field isolation stop. Systematic diagnosis requires verifying group interlock conditions (GEVT, GEX1, GEX2), auditing subordinate drive operating modes (AUT_ON = 1), inspecting run-up feedback timers (GST_TIME), and using the built-in CEMAT diagnostic buttons to pinpoint the blocking object.

CEMAT Group Control Architecture

In the Siemens CEMAT Minerals & Cement DCS environment, C_GROUP (FB1010) acts as a supervisory coordinator for plant sections (such as raw material transport belts, bucket elevators, and kiln feed systems). The group coordinates startup and shutdown sequences for multiple subordinate objects via bidirectional object coupling.

The group does not directly energize motor contactors; instead, it broadcasts start signals to linked subordinate drives (C_DRIVE_1D / C_DRIVE_2D) through internal link communication structures (OBJ_LINK / GR_LINK). If any single prerequisite fails across the hierarchy, the group halts execution to protect mechanical and electrical plant assets.

Diagnostic Checklist for C_GROUP Start Failures

Systematic diagnosis follows three mandatory validation stages:

1. Group Interlock Validation

Check the primary safety and operational interlock inputs on C_GROUP in CFC:
- GEVT (Group Start Interlock): Must be 1 (True). If 0, the group is locked against starting.
- GEX1 (Group Operating Interlock 1): Must be 1 (True). If 0, the group trips or will not start.
- GEX2 (Group Operating Interlock 2): Must be 1 (True). Often used for auxiliary equipment health or lubrication systems.
- GVEV (Group Release Interlock): Must be 1 (True). Determines permission to start from upstream process units.

2. Subordinate Object Readiness

Every drive, damper, and valve coupled to the group must satisfy all readiness conditions:
- Operating Mode: All linked objects must be in Automatic mode (AUT_ON = 1). If even one motor switchgear is in 'Local' or 'Manual' mode without being explicitly marked as 'Not in Operation' (STA2.N_IN_OP), the group start is blocked.
- Fault State: No subordinate object may have an active unacknowledged fault (FAULT = 0).
- Drive Interlocks: Verify individual drive interlocks: ELON (Start Interlock, must be 1), ELOF (Operation Interlock, must be 1), and EBMS (Local Field Switch, must be 1).

3. Object Coupling Integrity

C_GROUP.NO_OF_OBJ: Verify that the configured number of objects matches the actual quantity of connected child blocks.
OBJ_LINK: Ensure the group structure pointer is correctly interconnected to each subordinate drive's GR_LINK pin.

Signal Flow and Interlock Matrix

The following table specifies the critical input and feedback states required for C_GROUP execution:

ParameterTypeRequired State for StartDescription / Diagnostic CheckGEVTBOOL1 (Healthy)Start Interlock: If 0, start command is ignored. Interconnected to safety or process prerequisites.GEX1BOOL1 (Healthy)Operation Interlock 1: If 0, running group trips immediately; stopped group cannot start.GEX2BOOL1 (Healthy)Operation Interlock 2: Operational permissives (cooling water, dust collectors).GVEVBOOL1 (Healthy)Release Interlock: Permissive signal from downstream transport routes.GREVBOOLDynamic Feedback (1 when running)Group Feedback: Aggregated running feedback from all assigned drives.GST_TIMEINTSet > maximum plant acceleration timeGroup Run-up Time: Time allowed for all drives to reach running status before timeout alarm.GLO_OFFBOOL0 (Normal)Group Local Stop: Field safety lock. If 1, group is locked.

Verification

To verify group operation and confirm problem resolution:

Open the WinCC Runtime process graphic containing the C_GROUP block icon.
Click the group icon to display the standard faceplate.
Observe the group status bar:
- Verify the group indicates Ready to Start (light green status without flashing).
- If the group indicates Not Ready, click the Diagnosis tab.
On the Diagnosis tab, locate and press the 'Show Not Ready Objects' button:
- CEMAT will automatically open the faceplate of the exact drive or damper preventing group startup.
- Inspect the drive faceplate to determine whether it has a tripped circuit breaker (ELON = 0), active overload, or is switched to Local mode.
Remediate the field condition or switch the subordinate drive to Automatic.
Return to the C_GROUP faceplate and issue the Group Start command via the operator interface.
Confirm that the group enters run-up mode, subordinate drives start sequentially according to their pre-warning and run delay timers, and GREV asserts within GST_TIME.

Limitations and Operational Precautions

Operational boundaries in CEMAT group sequencing:

Avoid Forcing Internal Structure Pins: Attempting to force internal composite link structures (OBJ_LINK, GR_LINK) in CFC can cause CPU buffer corruptions or inconsistent CEMAT diagnostic messaging. Forcing should only be applied to external physical binary inputs if strictly permitted during dry commissioning.
Route Selection Dependencies: If C_GROUP is interconnected with C_ROUTE route blocks, confirm that the intended route is actively selected (SEL_DES = 1). An unselected route isolates downstream drives from the group start sequence.
Pre-Warning Horn Timers: CEMAT standards mandate an audible start pre-warning (HORN_TIM). Ensure the pre-warning time has fully elapsed before expecting motor contactors to close.

Engineer FAQ

Why did forcing the start input on C_GROUP work previously but not now?

If forcing worked earlier, the group interlocks (GEVT/GEX1) and all subordinate drives were healthy at that time. If even one subordinate drive subsequently tripped on a thermal overload, lost its control voltage permissive, or had its local isolator opened, C_GROUP will reject the start command regardless of forced start inputs.

What is the purpose of the C_GROUP parameter G_STANDBY?

G_STANDBY configures the group to remain in hot standby mode. When set, drives can be pre-energized without immediate material feed, allowing instant process synchronization upon receipt of upstream demand.

How do I bypass an offline drive without removing it from the group in CFC?

In the subordinate drive's faceplate (e.g., C_DRIVE_1D), authorized operators can switch the drive to 'Not in Operation' mode (Out of Service / Disconnected), provided this function is enabled in CEMAT project parameters. This excludes the drive from group interlock checks.

Where can I check if a group tripped on run-up timeout?

Check the WinCC Alarm Journal for message class CEMAT Group Alarm indicating Run-up time elapsed (GST_TIME). The alarm detail will identify which drive failed to return running feedback within the configured duration.