Application example
This example applies to a single-station system. If a UPS system undertakes the supply of
power to a BATCH server, the UPS system signals, e.g., the power failure event. In response
to the event, SIMATIC BATCH can be stopped and exited on the server. As a result, your plant
will automatically achieve a safe state in the event of a switchover to UPS.
Objective
Stopping and exiting SIMATIC BATCH automatically on an event-driven basis.
Creating a batch file
1. Create a file of type "*.bat", e.g., on partition D:.
2. On partition C:, look for the application "sblaunchcoordinatorservice32ux.exe".
3. Transfer the located storage location to the batch file.
4. Add the attribute "/-silentstop" at the end as a switch.
5. The entire instruction must be enclosed in quotation marks. Example:
"C:\Program Files (x86)\Common Files\Siemens\Bin
\sblaunchcoordinatorservice32ux.exe" /-silentstop
Note
The storage location of the application "sblaunchcoordinatorservice32ux.exe" depends on
the operating system.
Save the file.
6. Make sure that this batch file is run as administrator whenever the UPS system reports the
power failure event.
Result
SIMATIC BATCH will be automatically exited on an event-driven basis.
The instruction "sblaunchcoordinatorservice32ux.exe -silentstop" is executed as follows
without displaying confirmation dialogs. BATCH Runtime, BATCH project and BATCH Launch
Coordinator are exited. The instruction reacts the same way in a redundant environment, even
if the partner server is not ready to take over. This means all server applications and the
"SIMATIC BATCH Server Control Service" are exited. This behavior is independent of the
"manual" or "automatic" start mode set in the BATCH Launch Coordinator.
Recommended procedure
12.3 How does SIMATIC BATCH stop automatically on specific events?
SIMATIC BATCH V8.2
Operating Manual, 02/2016, A5E35958174-AA 675
To Next Page
Loading...
Need help?
General
