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

How to Resolve the Could Not Release Batch: No Connection Error in SIMATIC BATCH

How to Resolve the Could Not Release Batch: No Connection Error in SIMATIC BATCH

To resolve the "Could not release batch. No connection" error in SIMATIC BATCH Control Center (BatchCC), verify that the BATCH Control Server (BFW.exe) has established active communication channels to both the WinCC Server and the target Automation System (AS). This error occurs when BatchCC requests batch release validation, but the central BATCH Server cannot communicate with the AS interface blocks (BMASTER, BA_AS) or query the WinCC message archive. Re-establish the connection by verifying Simatic Shell network adapter prioritization, confirming the named S7 connection in NetPro and Station Configuration Editor, and executing a complete "Generate, Propagate, Merge, and Download" sequence from SIMATIC Manager.

Table of Contents

Communication Architecture Between SIMATIC BATCH, WinCC, and AS

SIMATIC BATCH executes batch control across a three-tier distributed architecture:
1. Automation System (AS) Tier: Technological blocks (BMASTER, BA_AS, IEPH, IEPAR) manage unit allocations, phase states, and recipe parameter handshakes in controller memory.
2. WinCC Operator Station (OS) Tier: WinCC acts as the process data and alarm highway, logging batch messages via Alarm Logging and routing operator setpoints.
3. BATCH Server Tier: The BATCH Control Server application (BFW.exe) and the communication driver (CDV.exe) coordinate recipe logic, unit reservation, and recipe state execution.

When an operator releases a batch in BatchCC, the BATCH Server performs an online validation handshake:
* It queries the AS via the configured S7 named connection to confirm that the assigned process units and equipment phases (IEPH) are operational and reachable.
* It interrogates the WinCC runtime database via OLE-DB / internal C-APIs to ensure the alarm archive channel is ready to capture regulatory batch messages.
* If either channel fails to respond within the internal timeout window, BatchCC aborts the release operation and posts: Could not release batch. No connection.

Root Causes of the 'No Connection' Batch Release Failure

Following server reinstallations, hypervisor host maintenance, or network changes, the "No connection" failure typically stems from one of four architectural misconfigurations:

Failure CategorySpecific MechanismImpact on BatchCC ReleaseSimatic Shell Network BindingOperating system update or network adapter initialization reorders physical NIC priority, causing Simatic Shell to bind to a corporate or management IP rather than the isolated Terminal Bus / Plant Bus.Multicast discovery packets fail; BFW.exe cannot locate OS runtime partners or peer redundant BATCH servers.S7 Named Connection MismatchStation Configuration Editor (SCE) index on the newly reinstalled server does not match the configured rack/slot indices in STEP 7 NetPro.S7 communication driver (s7oiehsx.sys) rejects connection attempts between BATCH and the AS CPU.Missing AS Engineering SynchronizationBATCH data was generated and downloaded to the server, but the updated BATCH blocks (BMASTER, DB41/DB42) were not downloaded to the AS controller.AS rejects phase reservation requests due to mismatched recipe header identifiers.DCOM / Windows Firewall BlocksMissing SIMATIC user group assignments (SIMATIC BATCH, SIMATIC HMI) or blocked TCP ports 102 (RFC 1006) and 135 (RPC/DCOM).BATCH client successfully renders cached recipes but server rejects remote execution requests.

Verifying Simatic Shell and S7 Named Connection Status

Before making database alterations, verify physical and logical network connectivity across all stations:
1. Inspect Simatic Shell:
- Open Windows File Explorer on the BATCH Server and click Simatic Shell.
- Right-click Simatic Shell and select Settings....
- Verify that the selected network adapter points to the dedicated Terminal Bus network interface card (NIC).
- Confirm that the Multicast Time to Live (TTL) matches your network topology (default 1 for flat subnets; 2 or higher if routed).
- Ensure all OS Servers, OS Clients, and BATCH Servers appear blue and active in the Simatic Shell window.
2. Check Station Configuration Editor (SCE):
- Open Station Configuration Editor on the BATCH Server.
- Verify that the station name exactly matches the computer name in capital letters.
- Confirm that the Application and communication processors (CP 1623 / IE General) occupy the identical virtual rack slots assigned in the PCS 7 project hardware configuration.
3. Verify AS S7 Connection:
- In NetPro, verify that a named connection exists between the WinCC/BATCH application and the AS CPU.
- Compile NetPro and download connection changes to both the AS controller and the PC station.

Method: Step-by-Step Recovery and AS-OS-BATCH Synchronization

Follow this standardized engineering sequence to synchronize the BATCH database, WinCC runtime, and the automation controllers:

Step 1: Verify Windows User Rights and Services

  1. Open Windows Computer Management (compmgmt.msc) on the BATCH Server and Client.
  2. Ensure the logged-on Windows account is an active member of:
    - SIMATIC BATCH
    - SIMATIC HMI
    - SIMATIC NET
  3. Launch Windows Services (services.msc) and verify that the following services are running:
    - SIMATIC BATCH Control Server (BFW.exe)
    - SIMATIC BATCH CDV
    - SIMATIC BATCH Start Coordinator

Step 2: Regenerate and Compile BATCH Data in SIMATIC Manager

  1. In SIMATIC Manager, select the multiproject root and open the SIMATIC BATCH engineering dialog.
  2. Execute the compilation workflow in strict sequential order:
    - Click Generate: Compiles plant hierarchy equipment properties and recipe phase types.
    - Click Propagate: Transfers technological interface parameters across all AS projects.
    - Click Merge: Consolidates multiple AS controller descriptors into a unified plant model.
    - Click Compile / Download: Select Entire Scope and download the compiled BATCH database to the active BATCH Server and redundant partner.

Step 3: Download Blocks and Connections to the AS

  1. In SIMATIC Manager, open each AS controller chart folder.
  2. Perform a partial or change download to the AS to ensure that updated BMASTER block instances and allocation DBs are active in controller RAM.
  3. Open NetPro, select the AS CPU, and choose PLC -> Download -> Connections and Gateways.

Step 4: Update Process Cell in BatchCC

  1. Launch BatchCC on the engineering station or active BATCH client.
  2. Select Process Cell -> Update Process Cell.
  3. Confirm that the process cell status indicator turns green with zero validation errors.
  4. Open the target Master Recipe, select Recipe -> Validate, and confirm that all equipment unit allocations report valid status.
  5. Right-click the batch order and select Release. The batch transitions to Released without connection errors.

Verification

To verify that the communication link is fully operational:
- In BatchCC, check the bottom status bar: the active BATCH Server must show Online / Connected with no flashing yellow disconnect warnings.
- Open the Batch Control Server window (BFW.exe) and confirm that the status reads Running and the internal communication log records successful polls to the AS IP addresses.
- Execute a test batch release: verify that the batch order transitions from Planned to Released and subsequently starts execution upon reaching its scheduled trigger time.
- Verify in WinCC AlarmControl that batch message category events (Batch start, recipe phase transition) populate the alarm list with correct batch ID timestamps.

Limitations and Operational Precautions

  • Do Not Delete BATCH System DBs While AS is in RUN: Manually clearing or deleting BMASTER instance DBs directly in online CPU memory disrupts all active batches and can trigger an AS emergency shutdown.
  • Redundant Server Failover Synchronization: On redundant BATCH server pairs, perform the process cell update on the active master server first. Ensure database replication completes before initiating failover testing.
  • Firewall Rules: If third-party firewalls or Windows Defender Advanced Firewall are enabled, verify that incoming TCP port 102 and the executable exceptions for BFW.exe, BatchCC.exe, and BcsBatchCDV.exe are explicitly permitted.
  • Avoid Renaming NetPro S7 Connections: Changing an existing S7 named connection identifier requires a complete OS compile and full BATCH engineering download.

Engineer FAQ

Why did BatchCC allow me to create recipes if there was no connection?

BatchCC allows offline recipe creation and modification because recipe modeling operates against the local or server-cached BATCH SQL database. The physical connection to the AS and WinCC is only tested and strictly enforced during batch release and execution handshakes.

Can a wrong network card binding in Simatic Shell cause this issue?

Yes. If Simatic Shell binds to a secondary network adapter (such as a remote desktop management NIC or second corporate adapter), the BATCH server communication driver cannot resolve the S7 named connections to the AS or communicate with WinCC, generating the "No connection" error.

What should I do if BFW.exe fails to start after an operating system reboot?

Check the Windows Event Viewer under Application Logs for DCOM or SQL Server startup timeouts. Ensure that Microsoft SQL Server (MICROSOFT##SSEE or BATCH instance) is set to Automatic startup and is fully initialized before the SIMATIC BATCH services start.

Does updating the process cell interrupt running batches?

A process cell update in BatchCC synchronizes engineering definitions (units, phases, parameters). Running batches continue executing their current phase steps, but new recipes cannot be released during the brief seconds while the database schema re-indexes.

Technical References

  • Siemens Industry Online Support: SIMATIC BATCH Operating Manual (A5E38012658).
  • SIOS Entry 109742323: SIMATIC PCS 7 Compendium Part A - Configuration Guidelines.
  • SIOS Entry 109809264: SIMATIC Process Control System PCS 7 Released Modules and Network Configuration.
  • Siemens FAQ 109751476: Resetting Stale Alarms and Re-establishing Runtime Communications in PCS 7.

Related Articles

Related Tags

  • SIMATIC BATCH
  • PCS 7
  • BatchCC
  • Simatic Shell
  • WinCC
  • S7 Connection
  • Industrial Automation
20 respuestas