Chapter 4 Deployment CPU 313SC/DPM Manual VIPA System 300S SPEED7
4-16 HB140E - CPU SC - RE_313-6CF03 - Rev. 07/45
Here the scan cycle monitoring time in milliseconds may be set. If the scan
cycle time exceeds the scan cycle monitoring time, the CPU enters the
STOP mode. Possible reasons for exceeding the time are:
• Communication processes
• a series of interrupt events
• an error in the CPU program
Using this parameter you can control the duration of communication
processes, which always extend the scan cycle time so it does not exceed
a specified length.
If there are no additional asynchronous events, the scan cycle time of OB1
is increased by following factor:
100
100 - cycle load from communication %
If the cycle load from communication is set to 50%, the scan cycle time of
OB 1 can be doubled. At the same time, the scan cycle time of OB 1 is still
being influenced by asynchronous events (e.g. process interrupts) as well.
The preset reaction of the CPU may be changed to an I/O access error that
occurs during the update of the process image by the system.
The CPU 313SC is preset such that OB 85 is not called if an I/O access
error occurs and no entry is made in the diagnostic buffer either.
Activate the check box if you want to use clock memory and enter the
number of the memory byte.
Note!
The selected memory byte cannot be used for temporary data storage.
Enter the number of retentive memory bytes from memory byte 0 onwards.
Enter the number of retentive S7 timers from T0 onwards. Each S7 timer
occupies 2 bytes.
Enter the number of retentive S7 counter from C0 onwards.
Cycle/Clock
memory
Scan Cycle
Monitoring Time
Scan Cycle Load
from
Communication
OB85-Call up at I/O
Access Error
Clock Memory
Retentive Memory
Number of Memory
Bytes from MB0
Number of S7
Timers from T0
Number of S7
Counters from C0
To Next Page
Loading...
Need help?
General
