PCS 7 V9.0 SP2 APL Block Deployment: Cyclic OBs and ET200SP HA

David Krause11 min read
Process ControlSiemensTechnical Reference
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview

SIMATIC PCS 7 V9.0 SP2 with the Advanced Process Library (APL) imposes strict constraints on where and how function blocks can be instantiated and downloaded. The APL documentation set A5E39147331-AC requires that blocks such as Pcs7AnIn (FB 1869), Pcs7DiIn, Pcs7AnOu, and Pcs7DiOu be installed inside a cyclic interrupt OB (OB30 through OB38), not in OB1. CPU 410-5H (and the wider AS 410 family) further restricts the download path: only the CFC editor, SFC, NetPro, or HW Config can perform a download. A download from the S7 program folder (FBD/LAD source) is rejected by the firmware, even if the project file is renamed to look like an S7 project. This reference consolidates the deployment rules, licensing model, ET200SP HA compatibility, and verification procedures for engineers commissioning a PCS 7 V9.0 SP2 project.

Documentation baseline: The behavior described here is consistent with the PCS 7 Readme V9.0 incl. SP2 (PDF). Engineers planning upgrades should also review the SIMATIC PCS 7 V9.1 SP2 Software Updates entry for CFC V9.0 SP8 Upd9 and XML Transfer V9.0 patches that affect APL block revision counters.

Prerequisites

  • SIMATIC PCS 7 V9.0 SP2 engineering station with the AS/OS Engineering license installed. Order number 6ES7658-5AX58-0YA5 (also written 6ES76585AX580YA5) grants both AS and OS engineering rights, including CFC and SCL compilation rights, on a single floating license.
  • PCS 7 APL library installed and registered in the master data library of the project.
  • AS 410 controller (CPU 410-5H, CPU 410E, or CPU 410 SMART) for the strict-CFC rule. CPU 417-4H accepts partial downloads from LAD/FBD sources and may be used when gradual migration is required.
  • STEP 7 V5.6 or PCS 7 engineering toolset that matches the controller firmware baseline.
  • For ET200SP HA installations: a configured PROFINET IO subnet with the HA station assembled in HW Config and the matching IM 155-6 PN HA interface module.

APL Block Installation in Cyclic Interrupt OBs

APL documentation A5E39147331-AC section "Use the CFC editor to install the block in a cyclic interrupt OB (OB30 to OB38)" is a hard runtime requirement, not an editorial guideline. The block's internal timing structures (cycle-time normalization, ramp limiting, mode-tracking time bases, alarm deadbands) are computed against the OB run-time interval. When the same block executes inside OB1, the timer math degrades in two ways:

  1. Time-base drift. OB1 runs at the priority-1 cycle, which is influenced by image-partition updates and bus communication. APL blocks call TIME_TCK or system clock SFCs that assume a deterministic interval; OB1 jitter propagates into the LAG filter of Pcs7AnIn and the PID step response of Pcs7Cntrl.
  2. Watchdog trip. OB1 priority (1) is shared with many lower-priority services; if OB1 scan time exceeds the configured max cycle, the CPU enters STOP with diagnostic event SF: cycle time exceeded.
OB Typical use in PCS 7 Recommended APL phase
OB1 Free cyclic, low priority Reserved for non-time-critical glue logic only
OB30 Fast acquisition, 10 ms High-speed Pcs7AnIn for fast pressure/flow
OB35 Cyclic 100 ms (default PCS 7 phase) Standard analog and binary channel blocks
OB36 200 ms Slow analog inputs, temperature RTD
OB37 500 ms Averaging blocks, trend calculation
OB38 1 s Maintenance calculations, statistical blocks
Do not place Pcs7Cntrl (PID) or Pcs7MotSpd (motor speed) in OB1. These blocks require deterministic call intervals to satisfy the controller's dead-time assumption.

CFC vs FBD/LAD Programming Paths in PCS 7

FBD/LAD source code is allowed inside PCS 7, but only as a sub-chart that is referenced from a CFC chart. The CFC editor wraps the FBD/LAD network into a CFC-compatible block instance with I/O interconnects and run sequence. Trying to download a chart that lives outside the CFC container fails differently on each controller family:

Controller Direct FBD/LAD download (block folder) Wrapped in CFC chart
CPU 410-5H / 410E Rejected at download; diagnostic buffer entry Download rejected: not a CFC-generated configuration Accepted; standard run sequence applies
CPU 417-4H Accepted if project flag S7-m_mode = TRUE; partial download supported Accepted; full CFC run sequence
CPU 416-3 / 414-3 Accepted; partial download supported Accepted but not recommended outside migration projects

The CPU 410 family adds an integrity check that compares the chart's signature against the CFC compiler output. The signature is regenerated whenever the CFC run sequence is edited. Bypassing the check by switching the project type from PCS 7 to S7 is permitted on CPU 417 but not on CPU 410. On CPU 410 the firmware examines the S7 program container and refuses any block whose run-time attribute is missing the CFC container stamp.

PCS 7 V9.0 SP2 Download Decision Flow Chart authored in CFC editor Chart authored in LAD/FBD block folder Download accepted on all AS 410/417 CPU 417/416: accepted CPU 410: rejected, signature mismatch CFC encapsulates the LAD/FBD network into a container with run-sequence signature. CPU 410 validates this signature on every download. CPU 417/416 fall back to standard STEP 7 partial download. Result: LAD/FBD blocks must be referenced from CFC for CPU 410.

CPU410-5H Download Restrictions

CPU 410-5H was designed from the start as a PCS 7 controller with safety integration (H-system). Siemens removed the partial download path from the standard STEP 7 download dialog for this family. Permitted download sources:

  • HW Config — for hardware changes only.
  • NetPro — for connection table updates.
  • CFC / SFC editor — for chart and sequential function chart changes.
  • PCS 7 OS / WinCC Explorer — for OS-side picture tree updates.

The diagnostic buffer entries associated with rejected downloads are 0x05F2 0x0001 "Download canceled — invalid container" and 0x05F2 0x0002 "Download canceled — CFC signature missing". If you encounter these entries, do not attempt to switch the project type; rebuild the chart inside CFC and re-download.

CPU 410E with firmware V8.2 or higher supports the "PCS 7 V9 mode" attribute cpu_attribute.cfc_required = TRUE. Verify this attribute before commissioning; older firmware accepts both paths and would allow a partial download that later fails after a firmware upgrade.

APL Block Compatibility with ET200SP HA

The manual entry for Pcs7AnIn (FB 1869) reads: "Signal processing of an analog input value of S7-300/400 SM analog input modules including ET 200M Ex-io module in °C." Field experience and the latest readme file confirm that the same FB 1869 also supports ET200SP HA, ET200SP, ET200MP, and ET200pro analog input channels. The text in A5E39147331-AC is historical and has not been refreshed to list every distributed I/O family added since APL V8.0.

The following block-to-channel matrix applies for ET200SP HA projects in PCS 7 V9.0 SP2:

APL block Block number ET200SP HA channel type Notes
Pcs7AnIn FB 1869 AI 4xI 2/4-wire HA (6DL1134-6TB00), AI 8xRTD HA Use channel error word WORD 0x80 onward for diagnostics
Pcs7DiIn FB 1862 DI 16x24VDC HA, DI 8xNAMUR HA Channel-value inversion done inside block, not in HW Config
Pcs7AnOu FB 1870 AQ 4xI HART HA, AQ 8xI HART HA Check HART pass-through topology before enabling
Pcs7DiOu FB 1864 DO 16x24VDC HA, RQ 4x120VDC HA Substitute value must be configured for fail-safe state
Pcs7MotSpd FB 1873 Not applicable Use with ET200SP standard motor starter, not HA
If you require NAMUR or HART-specific scaling that Pcs7AnIn cannot deliver, use Pcs7HaIn (FB 1872) from the APL "HART" sub-library. Pcs7HaIn remains the correct block for HART multi-variable channels on ET200SP HA.

PCS 7 V9.0 SP2 Licensing Model

The licensing model groups PCS 7 engineering rights into two floating license buckets. AS/OS Engineering (6ES7658-5AX58-0YA5) covers:

  • CFC / SFC editor (compile, download, run sequence)
  • SCL editor
  • WinCC / PCS 7 OS picture editor
  • HW Config, NetPro, plant view

The standalone CFC license (6ES7658-1EX58-0YA5) covers CFC/SFC only and is typically added when an external integrator needs chart work but not full AS/OS engineering rights. For a single engineering station the AS/OS Engineering bundle is the more economical choice and supersedes the standalone CFC order.

License Order number Covers CFC Covers WinCC/OS Covers SCL
AS/OS Engineering V9.0 6ES7658-5AX58-0YA5 Yes Yes Yes
SIMATIC CFC V9.0 6ES7658-1EX58-0YA5 Yes No Limited

Configuration Procedure

  1. License check. Open the Automation License Manager and confirm the AS/OS Engineering license 6ES7658-5AX58-0YA5 is present and not in the grace period. Grace period expiry locks the CFC download dialog.
  2. Project type check. In SIMATIC Manager, right-click the project > Object Properties > confirm PCS 7 V9.0. Do not toggle to S7 type if the target is CPU 410.
  3. Master data library. Verify the APL master data library is installed and the block version matches the engineering toolset. Open CFC > Library > APL > confirm FB 1869 revision is compatible with V9.0 SP2.
  4. Insert chart into a cyclic OB. In the plant view, open the S7 program > Charts > right-click > Insert New Chart > assign OB35 (default) or another OB30-OB38 per cycle requirements. Drop Pcs7AnIn onto the chart sheet.
  5. Wrap any FBD/LAD networks. If you wrote block logic in FBD/LAD, drop the compiled FB onto a CFC sheet and interconnect the inputs and outputs from there. The block folder copy alone is not enough.
  6. Configure ET200SP HA channel. In HW Config assign the AI module's input range, scaling, and channel error behavior. In the CFC chart sheet, wire the process value, channel error, and substitute value inputs.
  7. Compile and download from CFC. Click the CFC download icon or use menu > PLC > Download. Do not invoke the S7 program-level download dialog.

Verification Checklist

Check Method Pass criteria
License Automation License Manager AS/OS Engineering license present, not in grace
OB assignment CFC > Chart properties OB35 (or chosen OB30-OB38) shown as run-time container
CPU 410 path Diagnostic buffer after download No entries 0x05F2 0x0001 or 0x05F2 0x0002
APL block revision CFC > Block properties > Version FB 1869 revision >= V9.0 SP2 baseline
ET200SP HA channel wiring CFC online view, signal attribute QBAD = 0 Channel quality good, value tracks physical input
PID cycle CFC online view, OB35 scan time Scan time < 80 ms with default 100 ms OB35 phase
OS faceplate WinCC Explorer > picture tree Faceplate appears, occupies standard APL style slot

Troubleshooting Matrix

Symptom Likely cause Resolution
Download rejected on CPU 410 Chart not compiled via CFC, signature missing Re-compile the chart from CFC, re-download
Block runs but QBAD = 1 for ET200SP HA AI Wrong APL block (e.g., S7-300 specific) selected Use FB 1869 Pcs7AnIn from APL V9.0 SP2 master data
PID output oscillates, integral term drifts Block placed in OB1 instead of OB30-OB38 Move the CFC chart to OB35 and update run sequence
CFC license dialog says "CFC not licensed" Standalone CFC license missing, AS/OS license not detected Reinstall AS/OS Engineering license 6ES7658-5AX58-0YA5
ET200SP HA channel value always 0 Channel error substitute value active, channel diagnosis not acknowledged Open CFC online, reset MSG_ACK, check IM 155-6 PN HA diagnostics
Block time stamp DTB stale after restart Block in OB that does not run during restart (OB30-OB38 not loaded into restart OBs) Verify OB30-OB38 are part of the restart OB set in HW Config
Diagnostic buffer entry cycle time exceeded OB1 scan time too long; APL block mis-placed in OB1 Move APL blocks to OB35, distribute heavy logic to OB30
Faceplate missing in OS APL block revision mismatch with OS picture block Recompile OS using the "Update OS" menu, regenerate picture tree

Practical Field Notes

  • Migrating from CPU 417 to CPU 410. Existing charts that were downloaded from the S7 block folder on a 417 will need to be re-compiled via CFC before the same project can run on a 410. Plan at least one full stop/start cycle for the re-compile.
  • Mixed phase OBs. You can split fast loops (OB30, 10 ms) from default loops (OB35, 100 ms) and run them on the same CPU 410. The run sequence in CFC controls the phase relationship; verify it via the CFC runtime monitor.
  • Update discipline. When upgrading to PCS 7 V9.1 SP2, install the CFC V9.0 SP8 Upd9 patch listed in the V9.1 SP2 Software Updates entry. APL block revision counters shift with this patch and old charts may report "incompatible revision" until re-compiled.
  • Faceplate style switch. If you switch faceplates from Classic style to APL style, do so chart-by-chart and verify the OS server sees the new picture block. The PCS 7 Readme V9.0 notes that only one faceplate style variant can be installed at a time on a given OS server.

FAQ

Can I use APL blocks in FBD or LAD without CFC?

You can author logic in FBD or LAD inside a CFC chart. On CPU 410-5H, CPU 410E, and other AS 410 controllers the firmware rejects any download that did not go through the CFC editor. Always wrap FBD/LAD networks inside a CFC chart and use the CFC download menu.

Which APL block should I use for ET200SP HA analog inputs?

Use Pcs7AnIn (FB 1869) from the APL V9.0 SP2 master data library. The manual entry that lists only S7-300/400 and ET200M is outdated; FB 1869 supports ET200SP HA, ET200SP, ET200MP, and ET200pro analog input modules. For HART multi-variable channels use Pcs7HaIn (FB 1872) instead.

Why must APL blocks be placed in OB30 to OB38?

APL blocks contain deterministic timing structures such as filters, ramp generators, and PID step responses that are calibrated against a fixed OB execution interval. OB1 scan time varies with image-partition and bus load, so placing APL blocks in OB1 introduces jitter that breaks the LAG filter of Pcs7AnIn and the dead-time assumption of Pcs7Cntrl.

What is the correct PCS 7 V9.0 AS/OS Engineering license order number?

The single-user AS/OS Engineering floating license for PCS 7 V9.0 is 6ES7658-5AX58-0YA5. It covers CFC, SFC, SCL, HW Config, NetPro, and the WinCC/PCS 7 OS editor. A standalone CFC-only license 6ES7658-1EX58-0YA5 is available for external integrators who only need chart work.

How do I tell whether a download rejection is due to the CPU 410 CFC signature check?

Open the CPU diagnostic buffer in SIMATIC Manager and look for entries with event ID 0x05F2. Sub-event 0x0001 means "invalid container" and 0x0002 means "CFC signature missing." Both indicate the chart was compiled outside the CFC editor; rebuild the chart inside CFC and re-download.

Back to blog