Integrate an S7-300 Unit with SIMATIC BATCH Without Treating Industry Library as a Replacement
Use a documented PCS 7-side BATCH interface and an explicitly engineered link to the S7-300 unit. Industry Library V9.0 SP1 documents BatchIf for batch requests, but it still requires SIMATIC BATCH and its OS/API path. It does not establish that any S7-300 with Industry Library can replace a PCS 7 BATCH control architecture. The exact controller, library and phase mapping must be verified before this integration can be finalized.
Table of Contents
- Separate Unit Communication from Batch Management
- Prepare the Documented PCS 7-Side Interface
- Engineer the S7-300 Boundary
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Separate Unit Communication from Batch Management
The question asks whether an S7-300 application using Industry Library can be integrated with SIMATIC BATCH. The relevant documented PCS 7-side facility is BatchIf in Industry Library for PCS 7 V9.0 SP1. It uses the OS script BL_MainCycle.pas to issue requests through the BATCH interface to the Batch Control Server. This requires actual BATCH components; it is not a replacement batch system. Industry Library manual, section 21.3.
That facility does not independently establish direct BATCH phase execution on an arbitrary S7-300. Define which operations remain in the unit controller and how they are coordinated with the PCS 7 system.
Prepare the Documented PCS 7-Side Interface
For the documented V9.0 SP1 BatchIf implementation:
- Install SIMATIC BATCH Base on the relevant PCS 7 OS server/client stations.
- Configure a BATCH client for those OS stations and load the approved configuration.
- Place BatchIf in a cyclic interrupt OB, preferably OB32, in the unit-specific CFC with UNIT_PLC and UnitIf as applicable to the documented arrangement.
- Supply the required process-cell, order-category, recipe and batch parameters from the reviewed application.
- Run the relevant OS Runtime and BATCH Server, then verify command completion and the returned result.
Sections 21.3.1–21.3.3. This is the PCS 7-side method; S7-300-specific mapping and applicability remain unresolved.
Engineer the S7-300 Boundary
Prepare an explicit interface specification between the S7-300 unit and the PCS 7 control layer. Include requests, acknowledgements, status, command ownership and communication-loss behavior. Do not assume that transferring values alone provides complete batch-state coordination.
Identify the actual S7-300 CPU/firmware, Industry Library for S7 version, PCS 7 release and BATCH version. Confirm that the chosen communication and equipment-phase architecture is supported for those exact components. A library's product-family name does not establish every controller arrangement.
Verification
In an approved isolated test, verify the complete request path: originating unit logic, PCS 7-side interface, BATCH acceptance and the required resulting batch operation. Confirm the actual command result rather than only a changed request bit.
Test communication failure and recovery against the intended command-ownership specification. Verify that a restored link does not unintentionally repeat an operational request. These are proposed acceptance checks; no controller or batch tests were performed.
Limitations and Operational Precautions
The reported system versions and exact S7-300 architecture are missing. The documented BatchIf path establishes a closest PCS 7-side implementation, but not a complete supported S7-300 integration. The blanket implication that adding a library alone is sufficient therefore requires review.
Back up AS/OS and BATCH configuration. Test on nonproduction recipes and equipment. Keep library integration separate from licensing, installation, phase design and controlled deployment. Do not start production batches merely to validate a communication link.
Engineer FAQ
Does Industry Library replace SIMATIC BATCH? No; the documented interface depends on BATCH components.
Does BatchIf prove an arbitrary S7-300 can execute BATCH phases directly? No; verify the controller and phase architecture separately.
Is a changed command bit proof of success? No; inspect the returned result and intended batch behavior.