Starting the manager and running the simulation
Starting the simulator
The WinCC OA simulator is started by the options of the Simulator manager in the Console
WCCILsim [-num <manager number>] [-t <file name>]
If more than one simulator is to be run at once, a unique manager number must be assigned when starting each simulator. If testing is to be performed, the absolute path must also be specified to the simulation file.
If you want to repeat the simulation with the same simulation file once a simulator has finished working through it, the simulator must first be stopped (see "Stopping the simulator" item) and then re-started with the simulation file as argument.
In addition to the basic functions that every manager can perform, there is also the following command line option for specifying the simulation file:
WCCILsim -t <simFile>
The Simulator sets the connection state to "Connected", if a active periphery address has been configured for the corresponding Simulator manager.
Running the simulation with start and stop signals
Starting the simulator does not actually launch the simulation run. It simply opens a simulator process and passes an input file. A simulation run is initiated by a Kill command with parameter -1, with the job number or process ID for the simulator concerned as argument. The command is entered in the shell of the operating system.
The process ID can be found with the command ps for simulators started from their own shell.
Starting the simulation under Windows
Under Windows a simulation run is started by the command
pkill -1 <pid>
where pidstands for the process ID of the manager to be run. This ID can also be found using the task manager.
Example
Simulation run for the simulator with process ID 8287.
pkill -1 8287
Starting the simulation under Linux
A simulation run is started under Linux by the command:
kill -1 %<jobno>
or
kill -1 <pid>
where jobno stands for the job number, pid for the process ID of the manager to be run. The job number can be found with the following command for simulators started from their own shell:
jobs [-l]
Example
Simulation run for the simulator with process ID 8287.
kill -1 8287