This box enables you to select the main build and execution options for the runtime application.
If you want step by step debugging to be available during simulation or On Line test, you need to select the "DEBUG" compiling mode. If step by step debugging is no more required, you should select the "RELEASE" compiling mode in order to give highest performance to the runtime application.
You must specify in this box how the cycles must be triggered at run-time:
- as fast as possible: the target does not wait between two
cycles. The target simply runs as fast as possible
- triggered: you must specify the duration of a cycle, expressed as a number of micro-seconds. Refer to OEM instructions for explanations of the supported accuracy for the cycle timing of your target system.
Depending on the value of the "Lock" entry, more or less locking features will be supported at run time. Below are possible values:
I/Os I/O variables can be
locked and forced at run time
All All variables can be locked and forced at run time
None Variable forcing is fully disabled
The "I/Os" choice applies to I/O boards only.
Arrays, structures and instances
Validate the "Store complex variables in a separate segment" option for indicating that complex variables (arrays, structures and FB instances must be managed separately from single variables. Setting this options enables you to manage more complex data types in your applications. See details...