Arbitrating APL Motor Block Control Between SFC Sequential Logic and LogicMatrix in PCS 7

When coordinating an APL motor block ('MotL') with both an SFC sequence and LogicMatrix causes the motor not to respond to SFC commands, the failure occurs because CFC input pins like 'StartAut' permit only one continuous interconnection. If LogicMatrix outputs are directly wired to 'StartAut', SFC actions targeting the same pin are either rejected during compilation or overwritten cyclically. To correctly architect combined control, use LogicMatrix exclusively for interlocking ('Intlock', 'Permit', 'Protect') and allow SFC to drive 'StartAut'/'StopAut', or arbitrate multiple automatic start sources through an upstream OR block ('Or04') or multiplexer ('SelA02In').

Executive Summary

In modern SIMATIC PCS 7 engineering, batch processing and complex recipe sequences rely on Sequential Function Charts (SFC), while cause-and-effect interlock architectures utilize SIMATIC LogicMatrix. A frequent architectural collision occurs when engineers attempt to command an Advanced Process Library (APL) motor block (MotL) from an SFC chart while simultaneously connecting LogicMatrix cause-and-effect outputs to the motor's automatic control inputs (StartAut / StopAut). Because CFC rules strictly enforce single-writer architecture on input parameters, direct parallel writing creates cyclic signal overwrites or blocks SFC control entirely. This article explains the signal arbitration model of APL motor blocks and provides structured design patterns for integrating SFC with LogicMatrix.

Architectural and System Mechanics

The APL MotL control model segregates automatic commands from safety interlocks:

Operating Modes:
Auto Mode (AutModLi = 1, ModLiOp = 1): Motor responds to StartAut and StopAut.
Manual Mode (ManModLi = 1): Motor responds to manual commands (StartMan, StopMan) or operator faceplate interactions.
Command Characteristics:
Feature.Bit4 (Button/Switch mode): Determines whether StartAut is evaluated as an edge-triggered pulse (0 = button mode) or static level (1 = switch mode).
Interlock Architecture:
Permit: Prerequisite for starting; does not stop a running motor.
Intlock: Interlock without reset; stops motor and prevents start while active.
Protect: Safety interlock requiring operator acknowledgment/reset.
Architectural Conflict: LogicMatrix is designed to generate permissive and trip interlocks. When misapplied to directly force StartAut = 0, it overrides SFC sequence commands because continuous CFC connections evaluate cyclically at the start of the block execution, erasing SFC step actions.

Step-by-Step Engineering and Implementation Procedure

Step 1: Align System Roles Between LogicMatrix and SFC

Establish clean functional separation:
- SFC: Acts as the operational commander, driving procedural steps via StartAut, StopAut, and setpoints.
- LogicMatrix: Acts as the supervisory protection matrix, driving safety and process interlocks via Permit, Intlock, and Protect.

Step 2: Rewire LogicMatrix Outputs to APL Interlock Inputs

Open the CFC chart containing the MotL instance.
Remove any direct connection between the LogicMatrix output and MotL.StartAut or MotL.StopAut.
Connect the LogicMatrix cause-and-effect trip output to MotL.Intlock (or through an Intlk02/Intlk04 block if combined with other trips).
Connect the LogicMatrix starting permissive output to MotL.Permit.

Step 3: Implement Command Arbitration if Multiple Auto Sources Exist

If both an SFC chart and an external field Digital Input (DI) must be able to start the motor in Auto mode:
1. Insert an Or04 (4-input OR) block or SelA02In (selector) block upstream of MotL.
2. Wire the field DI to input 1 of Or04.
3. Configure SFC to write to an internal binary marker or CFC block input connected to input 2 of Or04.
4. Wire the output of Or04 to MotL.StartAut.

Step 4: Ensure Motor is Commanded into Auto Mode

Verify in the SFC preparation step that the motor is commanded into Automatic mode:
- Set MotL.ModLiOp = 1.
- Set MotL.AutModLi = 1.
- Confirm that MotL.AutAct = 1 before pulsing StartAut.

Verification

To verify proper arbitration and execution:
1. In CFC test mode, confirm MotL.AutAct = 1 and MotL.Intlock = 1 (healthy).
2. Trigger the SFC sequence. When the step becomes active, verify that MotL.StartAut receives the start command and the motor output PmpRun energizes.
3. Simulate a trip in LogicMatrix: verify that MotL.Intlock transitions to 0, immediately de-energizing the motor and transitioning the SFC step to fault/holding state.
4. Clear the LogicMatrix condition: confirm that the motor does not restart automatically until permitted by the SFC sequence.

Limitations and Operational Precautions

Operational precautions:
- Never connect both an SFC step action and a continuous CFC chart link directly to the same input parameter; CFC compilation will generate a warning or error, or runtime behavior will exhibit cyclic overwrites.
- When using Feature.Bit4 = 0 (pulse mode), ensure the SFC step duration is sufficiently long (at least two OB execution cycles) so the motor block reliably registers the rising edge.
- Verify that LogicMatrix safety outputs adhere to certified safety integrity levels (SIL) if deployed within SIMATIC Safety Matrix environments.

Engineer FAQ

Q: Why did `StartAut` stay at 0 when SFC commanded it to 1?

A: Because a continuous CFC connection from another block was wired to StartAut, overwriting the SFC write operation in the same execution cycle.

Q: Can LogicMatrix write directly to `MotL.StartAut`?

A: While physically wireable in CFC, doing so violates recommended PCS 7 design practices because LogicMatrix is intended for cause-and-effect interlocks, not operational state machines.

Q: What is the purpose of `Feature.Bit4` on `MotL`?

A: It configures whether auto commands (StartAut/StopAut) are evaluated as push-button pulses (0) or maintained switch states (1).

Q: How does SFC put a motor into automatic mode?

A: By setting ModLiOp = 1 (enable link control) and pulsing AutModLi = 1 (switch to auto mode).

Q: What happens if `Intlock` goes to 0 while `StartAut` is 1?

A: The motor immediately stops. Interlocks always override automatic and manual operational commands.

Technical References

Related Tags

LogicMatrix, SFC, MotL, APL Interlocks, CFC Architecture

20 respuestas

Arbitrating APL Motor Block Control Between SFC Sequential Logic and LogicMatrix in PCS 7