Programming S7-300 Controllers and Skid Integration Constraints in SIMATIC PCS 7

While SIMATIC PCS 7 is fundamentally engineered around S7-400 and CPU 410-5H architectures, SIMATIC S7-300 controllers (such as CPU 315-2 PN/DP or CPU 319-3 PN/DP) can be incorporated into a PCS 7 Multiproject as auxiliary stations or package skids. However, S7-300 CPUs cannot execute standard Advanced Process Library (APL) blocks or the automated module driver wizard (Generate Module Drivers) because they lack S7-400 system status lists (SZL) and execution OBs. To program S7-300 within a PCS 7 environment, author logic using classic STEP 7 (LAD/FBD/STL), or deploy the SIMATIC PCS 7 Industry Library for S7, communicating with WinCC OS via S7 connections.

Executive Summary

Automation engineers designing distributed process architectures frequently question whether lower-cost SIMATIC S7-300 CPUs (such as 6ES7315-2EH14-0AB0 or 6ES7319-33HN01-0AB0) can be programmed as native Automation Stations (AS) in SIMATIC PCS 7. Because PCS 7 utilizes SIMATIC Manager as its primary portal, adding an 'S7-300 Station' into a multiproject is technically permitted by the user interface. However, attempting to apply standard PCS 7 methodologies (CFC chart compilation with APL, automated diagnostic driver generation, and AS Process Object licensing) triggers compilation aborts. Understanding the firmware boundaries between S7-300 and S7-400 allows engineers to architect compliant hybrid systems without violating product design limitations.

Architectural Differences Between S7-300 and S7-400 in PCS 7

The core engineering pipeline in PCS 7 relies on hardware features unique to the S7-400 family:

System Status Lists (SZL): S7-400 controllers implement specialized diagnostic records (SZL 0x00B1 to 0x00B4) that allow module driver blocks (MOD_D1, MOD_HA) to interrogate I/O modules dynamically.
Execution Organization Blocks: PCS 7 distributes blocks across cyclic interrupt OBs (OB30 through OB38). S7-300 CPUs support only a subset of cyclic OBs (OB35 only on smaller CPUs).
Work Memory Architecture: S7-400 CPUs offer megabytes of linear code and data work memory, whereas S7-300 CPUs feature constrained memory limits optimized for machine-level execution.

Why Standard APL and Module Drivers Fail on S7-300

When compiling CFC charts targeting an S7-300:

The Module Driver Generator refuses to generate channel driver blocks, reporting: 'The CPU type is not supported by the module driver generator'.
APL technological blocks call internal S7-400 system blocks (such as SFB35 / ALARM_8P with multi-instance acknowledgments), which are unsupported on S7-300 CPUs.
Delta download in RUN is restricted; interface changes force a CPU STOP.

Supported Programming Paradigms for S7-300 in PCS 7

Engineers can successfully leverage S7-300 within PCS 7 projects using two methods:

Classic STEP 7 Programming: Author logic in standard LAD/FBD/STL or plain CFC using elementary math and bit blocks. Export DB tags with S7_m_c = true for manual WinCC graphic animation.
SIMATIC PCS 7 Industry Library for S7: Use specialized OEM blocks (IL for S7) specifically designed for S7-300/1500 that interface with APL-styled WinCC faceplates.

Controller Architectural Capabilities Comparison

The following table compares S7-300 and S7-400 capabilities within SIMATIC PCS 7:

Engineering FeatureS7-400 / CPU 410-5HS7-300 (e.g. CPU 315 / 319)Operational Workaround on S7-300Advanced Process Library (APL)Fully Supported (Native)Not SupportedUse Industry Library for S7 (IL for S7).Module Driver GenerationFully AutomatedNot SupportedWire peripheral addresses (PIW/PQW) manually.Cyclic Interrupt OBsOB30 to OB38 (Full Range)Limited (OB35 only on small CPUs)Map all CFC tasks to available cyclic OBs.Bumpless Run Download (CiR)Fully SupportedNot SupportedPlanned plant outage for hardware changes.AS Process Object (PO) CountConsumes AS RT POsZero AS PO ConsumptionGoverned strictly by hardware memory limits.WinCC OS IntegrationFull AS-OS CompileFull AS-OS CompileTags compile into WinCC via S7 Connection.

Step-by-Step Procedure to Configure S7-300 in a Multiproject

Method: Configuring S7-300 Station in SIMATIC Manager

Open the PCS 7 Multiproject in SIMATIC Manager.
Select Insert > Station > SIMATIC 300 Station.
Open HW Config for the S7-300 station. Configure the rack, CPU (e.g. CPU 319-3 PN/DP), and I/O modules.
In CPU Properties > Cycle/Clock Memory, assign desired scan cycle times.
Save and compile HW Config.
In the S7-300 Program folder, open the Blocks container. Author application logic using standard STEP 7 blocks or insert CFC charts utilizing the Industry Library for S7.
In NetPro, establish an S7 Connection between the WinCC OS Server and the S7-300 CPU over Industrial Ethernet.
Open the WinCC OS project, compile OS tags, and link graphic symbols to the S7-300 data blocks.

Verification

To verify S7-300 operational integration:

Compilation Check: In the S7-300 program, compile blocks or charts. Confirm 0 syntax errors.
Download and Run: Download the program to the S7-300 controller. Transition the CPU mode selector to RUN. Confirm healthy green RUN LED.
WinCC Tag Monitoring: In WinCC Runtime, verify that S7-300 process values update cyclically and operator commands actuate physical outputs.

Limitations and Operational Precautions

Do Not Attempt 'Generate Module Drivers': In CFC chart compilation settings for S7-300, always uncheck 'Generate module drivers' to prevent compiler aborts.
No CPU 410 Sizing Scaling: S7-300 CPUs cannot be upgraded dynamically with System Expansion Cards; physical replacement is required if code exceeds work memory.
Procurement Disclaimer: Ensure S7-300 hardware MLFBs, firmware, and spare part availability are verified with an authorized Siemens distributor quotation.

Engineer FAQ

Can an S7-300 controller communicate with an S7-400H redundant system?

Yes, an S7-300 can exchange data with an S7-400H system using BSEND/BRECV blocks over an S7 connection or Open IE communication.

Does using an S7-300 in PCS 7 require an AS RT Process Object license?

No. Siemens AS Process Object licenses apply strictly to S7-400 and CPU 410 controllers; S7-300 execution consumes zero AS POs.

Can SFC charts be used on S7-300 in PCS 7?

Yes, Sequential Function Chart (SFC) for S7 can compile step sequences onto high-end S7-300 CPUs (e.g. CPU 317/319).

Technical References

Related Tags

https://industrialautomation.net/search?query=simatic-pcs7
https://industrialautomation.net/search?query=s7-300
https://industrialautomation.net/search?query=hardware
https://industrialautomation.net/search?query=step7

6 respuestas

Programming S7-300 Controllers and Skid Integration Constraints in SIMATIC PCS 7