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

Implementing Cause-and-Effect Motor Interlocking with LogicMatrix and SFC in PCS 7 V9.1

Implementing Cause-and-Effect Motor Interlocking with LogicMatrix and SFC in PCS 7 V9.1

To implement cause-and-effect motor interlocking with SIMATIC LogicMatrix and SFC in PCS 7 V9.1, assign LogicMatrix matrix outputs to the 'Intlock' (interlock) or 'Permit' (starting condition) inputs of the 'MotL' block, while configuring SFC steps to control 'StartAut' and 'StopAut'. In PCS 7 V9.1, ensure that 'ModLiOp' is set to 1 and 'AutModLi' is set to 1 so the motor is in Automatic mode. If both manual pushbuttons and SFC commands must start the motor, merge them through an upstream 'Or04' block before 'StartAut' rather than creating competing CFC connections.

Table of Contents

Executive Summary

In process engineering under SIMATIC PCS 7 V9.1, cause-and-effect matrices defined via SIMATIC LogicMatrix provide rigorous safety and process interlocking, while SFC coordinates sequential plant automation. When commissioning motor drives (MotL), engineers frequently encounter scenarios where field DI pushbuttons, SFC recipe sequences, and LogicMatrix matrices must interact seamlessly. Attempting to directly connect matrix cause-and-effect outputs to StartAut prevents SFC control because continuous CFC links take execution precedence. This guide details the complete configuration workflow in PCS 7 V9.1, covering LogicMatrix generation, CFC parameter wiring, SFC action assignments, and runtime verification.

Architectural and System Mechanics

SIMATIC LogicMatrix and APL block architecture in PCS 7 V9.1:

  • LogicMatrix Architecture:
  • Causes: Field sensors, analog limit trips, and digital faults.
  • Effects: Process actions configured as de-energize trips, permissives, or alarms.
  • Generated CFC: LogicMatrix compiles into dedicated CFC charts containing LM_Cause and LM_Effect blocks.
  • APL Command Hierarchy on MotL:
  • Tier 1 (Highest): Interlocks (Protect > Intlock > Permit). If Intlock = 0, the motor is forced to 0 regardless of operational commands.
  • Tier 2: Manual / Auto Mode Switching (ModLiOp, AutModLi, ManModLi).
  • Tier 3: Automatic Operation (StartAut, StopAut). Evaluated only when in Auto mode (AutAct = 1) and interlocks are satisfied (Intlock = 1).
  • Signal Multiplexing: To allow multiple external triggers (e.g., field pushbuttons and SFC sequences) to command StartAut, use logical OR aggregation upstream.

Step-by-Step Engineering and Implementation Procedure

Step 1: Configure SIMATIC LogicMatrix Causes and Effects

  1. Open SIMATIC LogicMatrix Editor in the SIMATIC Manager project.
  2. Define Causes corresponding to process trips (e.g., thermal overload, high bearing temperature, emergency stop).
  3. Define an Effect linked to the target motor interlock.
  4. Compile the LogicMatrix to generate the underlying CFC charts.

Step 2: Interconnect LogicMatrix Effect to MotL Interlock Pins

  1. Open the CFC chart containing the MotL instance.
  2. Connect the output of the generated LM_Effect block to MotL.Intlock.
  3. For starting conditions (e.g., lube oil pump running before main motor start), connect the permissive effect to MotL.Permit.

Step 3: Implement Command Arbitration for Field DI and SFC

If an external DI signal and SFC sequence must both be able to start the motor in Auto mode:
1. Insert an Or04 block into the motor's CFC chart.
2. Wire the field DI channel driver (Pcs7DiIn.PV_Out.Value) to Or04.In1.
3. Create an internal binary parameter or flag connected to Or04.In2.
4. Connect Or04.Out to MotL.StartAut.
5. In the SFC chart, target the flag connected to Or04.In2 during the starting step.

Step 4: Configure SFC Steps and Verify Auto Mode Transition

  1. In the pre-start step of the SFC, write MotL.ModLiOp = 1 and MotL.AutModLi = 1.
  2. In the transition, check MotL.AutAct.Value == 1.
  3. In the motor start step, set the start flag to 1.
  4. In the transition, confirm MotL.FbkRunOut.Value == 1.

Verification

To verify system operation:
1. In CFC test mode, confirm that MotL.Intlock = 1 and MotL.Permit = 1.
2. Execute the SFC sequence. Verify that StartAut receives the pulse and the motor starts.
3. Trigger an alarm condition in LogicMatrix; verify that Intlock transitions to 0, immediately stopping the motor.
4. Verify that the LogicMatrix faceplate on WinCC highlights the triggering Cause, and the MotL faceplate displays the interlock trip banner.

Limitations and Operational Precautions

Operational precautions:
- Never configure an SFC step to override safety interlocks; interlocks must maintain hardwired and logical priority at all times.
- When compiling LogicMatrix, ensure delta compilation is selected to avoid wiping chart execution group order.
- APL blocks require both ModLiOp = 1 and AutModLi = 1 to switch into Auto mode; setting only one will leave the motor in Manual mode.

Engineer FAQ

Q: Can LogicMatrix trip a motor that is in Manual mode?

A: Yes. APL interlocks (Intlock, Protect) trip the motor regardless of whether it is operating in Manual, Auto, or Local mode.

Q: Why did StartAut remain inactive when triggered by SFC?

A: If AutAct is 0, the motor is in Manual mode and ignores all StartAut commands.

Q: How does Permit differ from Intlock?

A: Permit only gates the starting of the motor; it will not stop a motor that is already running if the condition drops.

Q: Can multiple SFCs command the same MotL instance?

A: Yes, by routing SFC command flags through an Or04 or selector block before StartAut.

Q: What does the purple circle mean on an APL interlock faceplate?

A: It indicates the first-in input signal that caused the interlock block to trip.

Technical References

Related Articles

Related Tags

LogicMatrix, PCS 7 V9.1, MotL, SFC Sequence, APL Engineering

20 respuestas