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

Establishing Cross-CFC Block Interconnections Using the SIMATIC Process Object View

Establishing Cross-CFC Block Interconnections Using the SIMATIC Process Object View

To establish cross-chart interconnections between block outputs and block inputs across different Continuous Function Charts (CFCs) using the SIMATIC Manager Process Object View (POV), engineers must configure the connection under the 'Parameters' tab rather than the 'Signals' tab. In Process Object View, the 'Signals' tab is strictly reserved for physical process image addresses (I/O) and global Data Block addresses. To link CFC_A to CFC_B, navigate to the 'Parameters' tab, locate the destination block input row, and enter the fully qualified block-output path (CFC_A\BlockName.OutputName) into the 'Interconnection' column.

Table of Contents

Executive Summary

In large-scale SIMATIC PCS 7 engineering projects encompassing hundreds of Continuous Function Charts (CFCs), bulk editing tools are vital for engineering productivity. The Process Object View (POV) in SIMATIC Manager provides a centralized tabular interface allowing engineers to configure block parameters, messages, picture hierarchy assignments, and signal interconnections without opening individual CFC charts. A frequent stumbling block occurs when engineers attempt to create chart-to-chart block connections (e.g., passing an interlock signal from CFC_A\MotL.Fwd to CFC_B\VlvL.Intlock) by entering the path into the 'Signal' column. SIMATIC Manager rejects the entry or erroneously interprets it as a raw data block variable rather than a textual CFC interconnection. Navigating to the correct 'Parameters' tab resolves this behavior immediately.

Architecture and Fundamental Mechanics

The data architecture of SIMATIC Manager Process Object View distinguishes between hardware signal routing and software parameter interconnection:

1. The Functional Division in Process Object View

Process Object View categorizes automation data into dedicated tabular views:
- Signals Tab (Signals): Designed strictly for physical hardware addressing and global memory coupling. Entries in the 'Signal' column map directly to peripheral inputs/outputs (e.g., IW 512, Q 4.0) or absolute data block addresses (e.g., DB10.DBD4). Typing a chart-relative string like CFC_A\Block.Out into the Signal tab causes the parser to look for a global symbol or DB, returning syntax errors.
- Parameters Tab (Parameters): Designed for block-level parameterization and software interconnections. In this tab, every instantiated block parameter is exposed with columns for Value, Unit, and Interconnection.

2. The Interconnection Syntax Engine

When creating chart-to-chart links in the 'Interconnection' column of the Parameters tab:
- Resolved Interconnection: If the source chart and block already exist in the AS project, entering <ChartName>\<BlockInstance>.<OutputParameter> (e.g., PUMP101\MotL.Run) creates an immediate graphical sheet-bar cross-reference in CFC.
- Textual Interconnection: If the source chart has not yet been imported or created, the system stores the path as a Textual Interconnection. Once the source chart is created, executing Options -> Make Textual Interconnections in CFC automatically converts all textual references into live chart connections.

Step-by-Step Implementation Procedure

To bulk-configure cross-CFC block interconnections using Process Object View:

Step 1: Open Process Object View in SIMATIC Manager

  1. In SIMATIC Manager, navigate to the Plant View or Component View.
  2. Select the hierarchy folder or S7 Program containing the target CFC charts.
  3. In the menu bar, select View -> Process Object View (or press Ctrl+4).

Step 2: Navigate to the Parameters Tab

  1. In the lower pane of Process Object View, select the Parameters tab (do not select the 'Signals' tab).
  2. In the tree view on the left, highlight the specific chart folder or individual destination chart (CFC_B).
  3. The table populates with all block I/O parameters contained within the selected scope.

Step 3: Filter and Locate the Target Input Parameter

  1. Utilize the column filters to display only inputs:
    - Filter by Block: enter the target block instance (e.g., VlvL).
    - Filter by I/O Name: enter the destination parameter (e.g., Permit or Intlock).

Step 4: Populate the Interconnection Column

  1. Locate the row corresponding to the destination input parameter.
  2. Click inside the Interconnection column.
  3. Enter the fully qualified source path:
    <SourceChartName>\<SourceBlockName>.<SourceOutputName>
    (Example: CFC_A\MotL.Fwd).
  4. Press Enter.
  5. To copy identical connections across multiple blocks, utilize standard spreadsheet drag-and-drop or copy-paste within the column.

Step 5: Close Process Object View and Verify in CFC

  1. Open CFC_B in the CFC Editor.
  2. Verify that a dynamic sheet-bar connector appears on the destination pin, referencing CFC_A.

Verification

To confirm successful interconnection:

  1. CFC Graphical Inspection:
    - Open both CFC_A and CFC_B in the CFC Editor.
    - Verify that the margin sheet-bar shows green cross-chart references indicating a live connection.

  2. CFC Consistency Check:
    - In CFC, click Chart -> Check Consistency -> Entire Program.
    - Verify zero open or invalid textual interconnection errors.

  3. Online Signal Flow Test:
    - Download changes to the Automation Station (or S7-PLCSIM).
    - Force the output in CFC_A and confirm that the input in CFC_B tracks the signal change immediately.

Limitations and Operational Precautions

Operational limitations and precautions:

  1. Data Type Compatibility: Cross-CFC interconnections mandate strict data type matching (e.g., structured REAL with quality code Value.ST can only connect to matching structured inputs, not raw REAL).
  2. AS Boundary Restrictions: Process Object View interconnections configured this way function only within the same Automation Station. Cross-AS connections between different S7-400 controllers require S7 connection blocks or PCS 7 AS-AS communication wizards.
  3. Textual Connection Limits: Textual interconnections left unclosed before final plant commissioning will prevent compiling changes in RUN.
  4. Commercial Disclaimer: Verify all software libraries, engineering options, and SIMATIC PCS 7 versions with an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Why did the 'Signals' tab treat my CFC connection as a data block address?

The 'Signals' tab is engineered strictly for physical peripheral I/O addresses and global DB variables. Cross-CFC block links must be configured in the 'Parameters' tab.

What is the correct syntax for linking blocks in Process Object View?

The syntax is <ChartName>\<BlockName>.<ParameterName> (for example, CFC_A\Motor01.Run).

Can I copy and paste interconnections across multiple rows in Process Object View?

Yes. Process Object View supports bulk copy, paste, and drag-fill operations across parameter rows, substantially accelerating bulk engineering.

What happens if the source chart does not exist yet when I enter the interconnection?

The system creates a yellow Textual Interconnection. Once the source chart is created, execute 'Options -> Make Textual Interconnections' in CFC to resolve it.

Can I use Process Object View to connect blocks across different S7-400 CPUs?

No. Process Object View parameter interconnections apply within a single CPU. Cross-AS communication requires AS-AS communication blocks or Industrial Ethernet S7 connections.

Technical References

Related Articles

Related Tags

  • Process Object View
  • CFC Engineering
  • Bulk Engineering
  • Cross-Chart Connection
  • Textual Interconnection
20 respuestas