102
Description of Operation Section 3-2
Note (a) The capacitor is backed up by the battery in the CPU Unit element
for CJ-series CPU Units.
(b) Operation is different between CS-series CPU Units and CJ-se-
ries CPU Units for power interruptions of more than 24 hours
when the hot start within specified time mode is used. Refer to
Operations for hot starts, cold starts, and hot starts within speci-
fied time on page 97 for details.
The following table describes each of the Loop Controller states at a hot start,
cold start or in a stop state.
∗1: The following data is read from the HMI function bank of the EM Area in
the CPU Unit for a cold start: Operation and control block HMI
send/receive data and receive data (SPs, PID parameters, etc.). (Refer to
the column for HMI in the ITEM tables in the Function Block Reference
Description Start of running Run stop
Cold start Hot start
Basic operation Operation is started after
contact/analog I/O val-
ues and internally held
values are cleared to
zero.
State active before the
Board was stopped is
continued before running
is started.
Running is stopped with
the state active before the
stop held.
Control blocks Set Points If a “hot started within
specified time” is speci-
fied, but a cold start is
used:
The status before the
power interruption will be
maintained.
Other cases:
Data read from EM Area
bank for HMI function in
CPU Unit ∗1
State active before stop is
held. ∗3
State active before stop is
held. ∗3
MV 0%
Auto/Manual
switching
Manual state
Control blocks,
Operation blocks
Parameters If a “hot started within
specified time” is speci-
fied, but a cold start is
used:
The status before the
power interruption will be
maintained.
Other cases:
Data read from EM Area
bank for HMI function in
CPU Unit ∗1
Contact/analog I/O
value
Initialization ∗2
Internal hold value
for operation
Initialization ∗2
Step Ladder Program STEP01
Sequence Table STEP00 and STEP01
Data exchange
with CPU Unit
Status of the Loop
Controller (allo-
cated CIO area)
Execution at each 1s regardless of running state
Data exchange
with function
blocks
Refresh is executed at each running cycle. Data exchange stopped