Flexible Automation
5.3
Program Execution
OM No.
1
2
OM3
3
OM4
4
5
6
OM6
7
8
OM8
9
Program execution is defined in the organizational modules. The user
can influence the system performance, e.g. start−up, by means of the
available OMs. Events like error detection, interrupt inputs and time−
outs during program execution result in the automatic call of the respec
tive organizational module.
The following table gives a summary of the criteria which define the or
ganizational modules for a given type of program execution. The user
program can be executed in cyclic, interrupt−controlled and time−con
trolled manner.
Execution
OM1
Cyclic
OM2
Interrupt−controlled, Interrupt Inputs
EI1.0
EI1.1
EI1.2
Time−controlled Execution
OM5
Time Base 1 for OM5 with priority
Time Base 2 for OM6
Time Base programmable in OM7
−
Start−up following "power on"
OM7
−
Define remanency range (T, C, M)
−
Allocation list generation
−
Define watchdog
−
Define time bases for time−controlled
execution (OM5,6)
−
Copy any data module to the data
buffer range
−
Start−up from the stop state
Error Detection
OM9
−
Cycle time exceeded
−
Module nesting depth > 32
−
Invalid command
−
Call of a non−existing module
Fig. 5−6 Organizational Modules
Software Description
1st Priority
2nd Priority
3rd Priority
5−11