list of target recipe elements. A setpoint runtime you have determined for the equipment phase
can also be specified. This means that the equipment phase will end only when the setpoint
runtime has expired.
How it works
A command step can be inserted in your recipe at any position where a NOP object (No
Operation = placeholder, empty step) can be inserted.
When the command step starts, it sends the configured command to all the recipe steps that
have appropriate status as determined by the configured filter. The recipe step receiving the
command is documented in the batch data.
If a runtime is specified for the command step, the step remains in the RUNNING status for
this time. If no runtime was specified, the step ends immediately after sending the command.
If a command step transfers a command to the target recipe element, an operator message
is generated and displayed in the command list in the message system. In the Operator column,
instead of the logged-on user, the name of the command step is shown followed by the step
number. Example: Hold immediately_4:Transition Breakpoint set.
Restrictions
● The command step is processed sequentially and does not wait until the controlled recipe
steps have executed the transferred command.
Note
If it is important for the ongoing recipe operation that the target object first executes the
transferred command, a transition for querying the target object status needs to be inserted
after the command step.
● The system cannot fully prevent the recipe from stopping because no steps or too many
steps are active if a command step is used incorrectly.
● Note the following recipe constructions in which automatic execution may be disrupted:
– Due to the command step, not all objects in simultaneous branches are started.
– Due to the command step, an object is started before a synchronization that has already
finished.
– The command step completes all active recipe steps.
● The "Restart" command at a recipe element only takes effect when the target object has
the status "Aborted" or "Stopped".
Consistency check
When the command step starts or restarts, the BATCH Control server checks if a recipe step
is already running in the step sequence before and after the target steps. If this is true, the
start command is not performed and the command step goes to error status.
BATCH Recipe Editor
10.4 Creating recipes
SIMATIC BATCH V8.2
536 Operating Manual, 02/2016, A5E35958174-AA
To Next Page
Loading...
Need help?
General
