Integrating SIMATIC S7-1200 Controllers into PCS 7 via S7 Communication and Open OS

SIMATIC S7-1200 basic controllers cannot be configured or programmed directly inside SIMATIC PCS 7 CFC, as they do not belong to the qualified PCS 7 automation system family. To integrate an S7-1200 into a PCS 7 plant, establish peer-to-peer S7 Communication between the S7-400 and S7-1200 using an Unspecified S7 Connection with PUT/GET (SFB14/SFB15) or BSEND/BRECV blocks, configure PROFINET I-Device coupling via GSDML, or integrate the controller into the PCS 7 OS using SIMATIC PCS 7 Open OS.

Architectural Boundary Between S7-1200 (TIA Portal) and PCS 7

In process automation facilities operating SIMATIC PCS 7, auxiliary package units (skids, vendor packages, chiller units, or small water treatment skids) are frequently equipped with SIMATIC S7-1200 basic controllers (such as CPU 1214C MLFB 6ES7214-1AG40-0XB0 or CPU 1215C MLFB 6ES7215-1AG40-0XB0).

A fundamental engineering boundary exists between these platforms:
1. PCS 7 Ecosystem: Programmed and maintained exclusively within STEP 7 V5.x, CFC, SFC, and the Advanced Process Library (APL) running on S7-400 / S7-410 controllers. S7-1200 hardware cannot be inserted into the PCS 7 hardware catalog or programmed via CFC.
2. S7-1200 Ecosystem: Configured and programmed exclusively within TIA Portal (Totally Integrated Automation Portal) using LAD, FBD, or SCL.

To integrate S7-1200 process data, alarms, and control interlocks into the main PCS 7 DCS, automation engineers must implement deterministic cross-platform communication architectures without compromising the integrity of the process control system.

Integration Architecture Comparison Matrix

Evaluate the three standard methods for integrating S7-1200 data into a PCS 7 architecture:

Integration TopologyCommunication ProtocolConfiguration ToolsData Exchange CharacteristicsRecommended Plant ApplicationS7 Communication (PUT/GET)S7 Protocol / ISO-on-TCP (RFC 1006)NetPro (PCS 7) & TIA PortalAsynchronous block transfer via DBs; up to 160 bytes per telegramGeneral parameter exchange, skid status monitoring, setpoint transferPROFINET I-Device CouplingDeterministic PROFINET IO (RT)GSDML Export in TIA -> HW ConfigDeterministic cyclic I/O mirror (1-10 ms); direct peripheral addressingHigh-speed safety interlocks, fast digital trips, continuous analog loopsSIMATIC PCS 7 Open OSWinCC Channel / OPC / S7 ProtocolOpen OS Component ConfiguratorDirect integration of S7-1200 into WinCC with APL-like faceplatesComprehensive skid visualization with centralized operator controlsPROFIBUS-DP Slave (CM 1242-5)PROFIBUS DP-V1GSD file in HW ConfigDeterministic cyclic slave communication up to 12 MbpsLegacy plants lacking Industrial Ethernet plant bus extensions

Procurement and hardware notice: S7 communication requires no additional hardware; PROFIBUS coupling requires communication module CM 1242-5 (6GK7242-5DX30-0XE0). Always verify specifications with authorized Siemens distributors.

Configuring Peer-to-Peer S7 Communication (PUT/GET) in NetPro and TIA Portal

Follow this verified procedure to establish bilateral data exchange using S7 communication:

Configure S7-1200 in TIA Portal:
* Open the S7-1200 project in TIA Portal.
* Open CPU Device Configuration > Properties > Protection & Security > Connection Mechanisms.
* Mandatory: Check the box: Permit access with PUT/GET communication from remote partner.
* Create dedicated send and receive Data Blocks (e.g., DB100_SendToPCS7 and DB101_RecvFromPCS7).
* In DB properties, uncheck Optimized Block Access (configure as standard S7-300/400 compatible DB structure).
Configure Unspecified S7 Connection in NetPro (PCS 7):
* On the PCS 7 Engineering Station, open NetPro.
* Select the S7-400 CPU, right-click, and select Insert New Connection.
* Connection Partner: Unspecified. Connection Type: S7 connection.
* In Connection Properties:
- Enter the IP address of the S7-1200 CPU.
- Partner TSAP: Set to 03.01 (Rack 0, Slot 1 for S7-1200).
- Local TSAP: Defaults to S7-400 CPU handle (e.g., 10.02).
- Save and compile NetPro, then download network configuration to S7-400 in STOP or via CiR.
Instantiate PUT/GET Blocks in S7-400 CFC:
* Place PUT (SFB14) and GET (SFB15) into a cyclic CFC chart (OB 35).
* Assign input ID to the connection ID generated in NetPro (e.g., W#16#0001).
* Parameterize ADDR_1 pointing to the remote S7-1200 DB address (P#DB100.DBX0.0 BYTE 64).
* Parameterize RD_1 / SD_1 pointing to the local S7-400 DB buffers.
* Trigger the communication blocks with a 500 ms clock pulse.

Integrating S7-1200 into PCS 7 OS Using SIMATIC PCS 7 Open OS

If the S7-1200 package unit must be operated directly from PCS 7 WinCC OS stations:
1. In TIA Portal, export the S7-1200 tag and alarm data using the DB export utility.
2. In PCS 7, launch the SIMATIC PCS 7 Open OS configurator.
3. Import the tag mapping file to automatically generate WinCC tags, messages, and APL-style block icons for third-party packages.
4. Compile the OS to instantiate the package unit graphics within the PCS 7 Picture Tree navigation.

Verification

Verify cross-platform data exchange:
1. Online in TIA Portal: Force a known value (e.g., 123.45) in DB100_SendToPCS7.TestValue.
2. Online in PCS 7 CFC: Monitor the output of GET (SFB15); confirm that the data buffer registers 123.45 with output NDR = 1 (New Data Received) and ERROR = 0.
3. In S7-400 CFC: Write an integer command (e.g., 16#00FF) into PUT (SFB14); verify that the remote S7-1200 updates DB101_RecvFromPCS7 within 100 milliseconds.

Limitations and Operational Precautions

S7-1200 controllers do not support high-availability S7-REDCONNECT fault-tolerant connections; connecting an S7-1200 to an S7-400H cluster requires binding communication to a single CP or implementing dual independent connection logic.
Never enable PUT/GET communication across public corporate networks without industrial firewall protection (e.g., SCALANCE S615 6GK5615-0AA00-2AA2), as legacy S7 communication lacks cryptographic encryption.
S7-1200 standard CPUs do not support deterministic sequence of events (SOE) 1 ms timestamping within PCS 7.

Engineer FAQ

Can I program the S7-1200 using PCS 7 CFC Editor?

No. S7-1200 micro-architecture is incompatible with CFC and STEP 7 V5.x. All controller logic must be authored in TIA Portal.

Why does PUT/GET return error code 16#0001 or 16#0004?

Error 16#0001 indicates a communication timeout or invalid connection ID. Error 16#0004 indicates access violation, typically because 'Permit access with PUT/GET' was not enabled in S7-1200 CPU properties or the DB was configured with 'Optimized Block Access'.

Does S7-1200 integration consume PCS 7 Process Objects (PO)?

If data is routed through S7-400 CFC blocks (e.g., MotL, OpAnL), those CFC blocks consume AS RT Process Objects. If connected directly to WinCC via Open OS, only OS runtime tags are consumed.