Operation Of Batches After Restart Of Cpu, Sfc Types - Siemens SIMATIC BATCH Operating Manual

BATCH Control Center
9.8 Batch control
● If the "Abort (Emergency)" command is used when no connection to the AS is available,
the status of the batch and the active elements are aborted regardless of the block states.
The user is responsible for manually bringing the blocks in the AS to a non-critical state.
Even if the connection to the AS has been re-established, these SIMATIC BATCH blocks
must be reset before they can be used again.
● For safety, a prompt appears asking the user if he really wants to abort the batch with the
note that no AS connection is available and that the interface blocks of the allocated unit
may need to be released manually.
● The "Abort (Emergency)" command is not provided by the SIMATIC BATCH API.
● BatchCC has no information as to whether or not there is a connection between the BATCH
client and AS. This command is therefore always available, even when the connection
between the BATCH client and AS is intact.
9.8.5.17

Operation of batches after restart of CPU, SFC types

Batch operation after CPU restart using SFC types
A CPU stop and subsequent restart generates an error with a running batch which interrupts
this batch. To continue, cancel or stop, the batch must be manually operated.
In SIMATIC BATCH, there are two configuration possibilities. The following describes the
procedure when using SFC types
442
SIMATIC BATCH V8.2
Operating Manual, 02/2016, A5E35958174-AA