YASKAWA CPU 013C Manual page 67

VIPA System SLIO
Startup
Cycle/Clock memory
HB300 | CPU | 013-CCF0R00 | en | 16-40
n Plant designation
– Here is the possibility to specify a plant designation for the CPU.
– This plant designation identifies parts of the plant according to their function.
– Its structure is hierarchic according to IEC 81346-1.
n Location designation
– The location designation is part of the resource designation.
– Here the exact location of your module within a plant may be specified.
n Comment
– In this field information about the module may be entered.
n Startup when expected/actual configuration differs
– If the checkbox for 'Startup when expected/actual configuration differ' is dese-
lected and at least one module is not located at its configured slot or if another
type of module is inserted there instead, then the CPU does not switch to RUN
mode and remains in STOP mode.
– If the checkbox for 'Startup when expected/actual configuration differ' is selected,
then the CPU starts even if there are modules not located in their configured slots
of if another type of module is inserted there instead, such as during an initial
system start-up.
n Monitoring time for ready message by modules [100ms]
– This operation specifies the maximum time for the ready message of every con-
figured module after PowerON.
– Here connected PROFIBUS DP slaves are also considered until they are parame-
terized.
– If the modules do not send a ready message to the CPU by the time the moni-
toring time has expired, the actual configuration becomes unequal to the preset
configuration.
n Monitoring time for transfer of parameters to modules [100ms]
– The maximum time for the transfer of parameters to parameterizable modules.
– Here connected PROFINET IO devices also considered until they are parameter-
ized.
– If not every module has been assigned parameters by the time this monitoring
time has expired; the actual configuration becomes unequal to the preset configu-
ration.
n Update OB1 process image cyclically
– This parameter is not relevant.
n Scan cycle monitoring time
– 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
n Minimum scan cycle time
– This parameter is not relevant.
n Scan cycle load from Communication
– 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 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 influ-
enced by asynchronous events (e.g. hardware interrupts) as well.
Deployment CPU 013-CCF0R00
Setting standard CPU parameters > Parameter CPU
67