EasyManua.ls Logo

Bosch CL300 - Page 132

Bosch CL300
167 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
SoftwareDescription
FlexibleAutomation
5−10
I/O Allocation List On start−up following power on", an I/O allocation list is automatically
generated. This list specifies which module type is allocated to the indi
vidual modules. This actual allocation list can then be compared to a set
allocation list that can be programmed in OM7.
On start−up from the stop state, the present allocation list is also com
pared to the set allocation list that can be programmed in OM7.
If no start−up performance is programmed in OM7 and OM8, standard
start−up is performed. In this case, no allocation list checking is exe
cuted.
If an error is detected during I/O allocation list checking, it is displayed on
the 7−segment display in coded form, and controller start−up is inhib
ited.
Watchdog (Cycle time monitoring) The ZE central processing unit monitors the cycle time for the hard
ware−set maximum value of approx. 1.6 s.
Below this value, another cycle time limit can be programmed in the OM7
organizational module.
When the cycle time is exceeded, the special marker bit SM28.7 is set.
Subsequently, OM9 is called. In OM9 the user can program the system
response to exceeding cycle time. After execution of OM9 or if OM9 is not
programmed, the controller assumes the stop state, and all the outputs
are reset.
Standard cycle time monitoring is approx. 1.6 s.
Remanency The remanency ranges of markers, timers, and counters can be user−
programmed in the OM7 organizational module. If no range is pro
grammed, the remanency range Semi−remanent" (upper address
range) is standard. Remanency can be selected using the remanency
switch on the ZE.
Time Base The user can define 2 time bases in OM7 (Factor * 10 ms, 10 min. max.)
for time−controlled program execution using the OM5 and OM6 organ
izational modules. Without time bases being defined in OM7, no time−
controlled execution is possible.
Copy Data Module If the user wants to copy a given data module or parts of this data module
from the user program to a data buffer range (DB) upon controller start−
up, he/she can define this in OM7. No copy is standard.

Related product manuals