Structure of the simulation file

A simulation file consists of two blocks: the periphery list and the notification list (contains notifications that should be sent; can be expanded by an alert list).

The simulation file is an ASCII file that has to be stored in the project directory.

Instead of using the periphery definition the config entry

autoHWObjects =
                "Y"

can be used in the [sim] section of the config file to automatically create configured HW objects for the Simulator.By default this config entry is set to "N" (the configured hardware objects will not be created automatically). Hardware objects symbolize peripheral address references. They do not have the data types of WinCC OA data point elements or attributes. The data types of peripheral addresses can be mapped onto WinCC OA data types.

autoHWObjects = "N" means that the HW addresses are generated with simulator transformation codes as defined in the simulation file. Therefore, if you want to use e.g. OPC addresses, autoHWObjects = "N" must be set and all addresses must be defined in the simulation file. In case of autoHWObjects = "Y", the addresses would be generated with OPC transformation codes from the address configuration, which cannot be processed by the simulator.

The entries in the simulation are separated by spaces or tabs (in the following documentation these are denoted with the term "white space"). A comment line begins with "#" and ends with the end-of-line character for that line. Comments can be inserted at any point in the file.. Strings are marked with "", if these are variable contents (value for string, alarm monitoring value).

Example of the structure of a simulation file

#object type object name

4 a1

8 a2

1 a3

9 a4

-99

#subindex name type value sec msec status bits time stamp

1 a1 i 5 0 25 G

2 a2 f3 4.1 7.0 8.5 0 25 GI

1 a3 b8 1 0 0 1 1 1 0 0 1 0 +1

0 a4 t "Hello world" 2 0 "2010.04.27;17:55:00,000"

-1

Comments for the log file

If a line begins with the code -88, the next field is read and raised at the corresponding point in the Simulator log file. This provides the insertion of comments between the outputs to mark the individual points of the simulation file.

Example

-88 "Text to be written in the log file"