HIMA HIQuad X - Automatic Forcing Reset; Forcing and Scalar Events; Cycle Sequence

Programming System
Page 84 of 110 HI 803 211 E Rev. 1.01.00
obsolete value! Press Ctrl+A to select and copy all the data, even if they are not in the visible
area.
6.2.4 Automatic Forcing Reset
The operating system resets forcing in the following cases:
 When the resource is restarted, e.g., after connecting the supply voltage.
 When the resource is stopped.
 When a new configuration is loaded by performing a download.
 When a user program is stopped: Reset of local forcing for this user program.
In these cases, the user program changes the force settings as follows:
 Force values to 0 or FALSE
 Individual force switch to OFF.
During a reload, local and global force values as well as forcing times and force timeout
reactions are still valid.
Global force values and force switches can be set when a resource is stopped. The configured
values become valid after restarting the resource and forcing.
Local force values and force switches can be set when the user program is stopped. The
configured values become valid after restarting the user program and forcing.
6.2.5 Forcing and Scalar Events
When forcing a global variable used to create scalar events, observe the following points:
 The events are created in accordance with the force value.
 The values of these variable-dependent status variables are not tracked to the force value!
In such cases, the corresponding status variables must also be forced!
6.3 Cycle Sequence
In a simplified overview, the processor module cycle (CPU cycle) of only one user program runs
through the following phases:
1. Processing of the input data.
2. Processing of the user program.
3. Provision of the output data.
These phases do not include special tasks such as reload, which might be executed within a
CPU cycle.
Global variables, results from function blocks, and other data are processed in the first phase
and represent the input data for the second phase. The first phase need not start at the
beginning of the cycle, but may be delayed. For this reason, inaccurate cycle times, potentially
exceeding the watchdog time, may result if timer function blocks are used to determine the cycle
time in the user program.
In the third phase, the user program results are forwarded for being processed in the following
cycles and supplied to the output channels.