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

Configuring Control Module Type (CMT) Interconnections, Technological I-Os, and SFC Linking in PCS 7

Configuring Control Module Type (CMT) Interconnections, Technological I-Os, and SFC Linking in PCS 7

In SIMATIC PCS 7 Control Module Types (CMT), you are not strictly required to define an input like 'OpenAut' as a Technological I/O (green pin) if connecting it directly to an SFC within the same chart or as an external cross-chart link. Defining an I/O as Technological I/O (TIO) is mandatory when using Equipment Module Types (EMT), Equipment Phase Types (EPHT), or Plant Automation Accelerator (PAA) where SFC commands control CMT instances via abstract role assignments. For standard SFC Types, connecting directly to the block input (gray pin) functions normally, but TIO definition is recommended for standardized bulk engineering.

Table of Contents

Executive Summary

The Control Module Type (CMT) concept introduced in SIMATIC PCS 7 Advanced Process Library fundamentally shifted DCS engineering from unstructured chart copying to standardized object-oriented templates. When interconnecting sequential logic from Sequential Function Charts (SFC) to CMT instances (such as commanding a valve block VlvL.OpenAut), engineers frequently question whether input pins must be declared as 'Technological I/Os' (colored green in the CFC editor) or can remain standard chart pins (colored gray). This guide explains the architectural purpose of Technological I/Os, clarifies the rules governing CMT-to-instance synchronization, and provides best practices for SFC integration.

Architectural and System Mechanics

CMT Architecture and Technological Interface Mechanics:

  • CMT as an Encapsulated Black Box: A Control Module Type defines a technological device (valve, motor, transmitter). Its internal CFC sheet contains driver blocks, interlocks, and messaging logic.
  • Technological I/O (TIO - Green Pin):
  • Exposes an internal block parameter to the outer technological hierarchy.
  • Required when integrating with Plant Automation Accelerator (PAA) or SIMATIC BATCH.
  • Required when configuring role-based commands and statuses in Equipment Modules (EMT) and Equipment Phases (EPHT).
  • Standard Internal Pin (Gray Pin):
  • An unexposed parameter. In a Control Module instance (CM), gray pins cannot have internal connections modified that diverge from the master CMT template unless explicitly marked as 'Ignore I/O' (pink pin).
  • External Chart Interconnections: CFC allows external interconnections from other charts or global SFCs to reach any block input (whether green or gray) without breaking CMT synchronization.

Step-by-Step Engineering and Implementation Procedure

Step 1: Understand the Control Philosophy (Direct vs. Role-Based SFC)

Choose the appropriate integration pattern:
- Pattern A (Standard SFC / SFC Chart): SFC step directly writes to OpenAut via a runtime write action. Defining TIO is optional but good practice.
- Pattern B (SFC Type with Block Contacts): Uses SFC Type block contacts (VlvL interface). Interconnect the CM instance to the block contact.
- Pattern C (EMT / EPHT Role-Based Control): Commands defined in the CMT are called by EMT phase steps. Defining OpenAut as a Technological I/O is mandatory.

Step 2: Declare Technological I/O in the Master CMT (If using Pattern B/C)

  1. Open the master CMT in the Master Data Library.
  2. Open the Technological Editor window (View -> 'Technological view').
  3. In the technological hierarchy tree, select the Control Module.
  4. Drag the input parameter VlvL.OpenAut from the CFC sheet into the Technological Editor under 'Commands' or 'Control'.
  5. The pin color on the CFC block changes from gray to green, indicating it is now an exposed Technological I/O.

Step 3: Synchronize CMT to CM Instances

  1. In SIMATIC Manager Plant View, select the master data library folder containing the CMT.
  2. Select 'Options' -> 'Plant Automation Accelerator' -> 'Synchronize' or in CFC 'Options' -> 'Synchronize with CMT...'.
  3. The synchronizer updates all instance charts, exposing the green Technological I/O pin on all instantiated valves.

Step 4: Connect the SFC Command

  1. Open the SFC chart or SFC Type.
  2. In the target step actions, select the valve instance Vlv101.OpenAut.
  3. Set the action value to True.
  4. In the following transition, verify the feedback condition: Vlv101.FbkOpenOut.Value == True.

Verification

To verify CMT and SFC operation:
1. In CFC, open the CM instance chart; verify that the connection from the SFC to OpenAut is cleanly rendered.
2. Run the CMT Type-Instance Comparison tool (Options' -> 'Compare to CMT'); confirm that the external SFC connection does not trigger a synchronization discrepancy warning. 3. Execute the SFC sequence in test mode; verify that when the step activates,VlvL.OpenAut` asserts, and the valve opens in Auto mode.

Limitations and Operational Precautions

Operational precautions:
- Never modify internal block connections inside a CM instance if they are not declared as Technological I/Os or 'Ignore I/O' (pink); the next CMT synchronization will overwrite instance changes.
- Ensure the valve is commanded into Auto mode (ModLiOp = 1, AutModLi = 1) by the SFC before OpenAut is evaluated.
- In bulk engineering workflows with PAA, any parameter that needs to be configured via Excel import/export must be defined as a Technological I/O.

Engineer FAQ

Q: What does the green color on a CFC block pin mean?

A: A green pin indicates that the parameter has been declared as a Technological I/O in the CMT definition.

Q: What happens if I connect an SFC to a gray pin?

A: The connection functions normally at runtime. However, it cannot be managed as an abstract command in EMT/EPHT phase configurations.

Q: What does the pink color indicate on a CMT pin?

A: A pink pin indicates 'Ignore I/O', meaning that this specific parameter is exempt from template synchronization, allowing unique instance values.

Q: Can I delete a block inside a CM instance?

A: No. Blocks inside a CM instance are locked by the parent CMT template and can only be deleted or added at the master CMT level.

Q: What is the difference between CMT and standard Process Tag Types?

A: CMTs support advanced synchronization, optional elements, variant management, and bidirectional integration with Plant Automation Accelerator (PAA).

Technical References

Related Articles

Related Tags

Control Module Types, CMT, Technological IO, SFC Sequence, APL Engineering

16 respuestas