Omron SYSMAC CS Series Operation Manual page 54

Outline
22
Note 1. For the CS1D-CPU@@P, data is refreshed over several CPU Unit cycles in
the operation cycle.
2. Data is refreshed each CPU Unit cycle for the CS1D-CPU@@P.
1. Function Block Operations (independent of and asynchronous with
CPU Unit)
The function blocks on the Loop Controller are cyclically executed according
to fixed operation cycles. Operations are executed asynchronously with the
user program on the CPU Unit.
The operation cycle is one of 0.01, 0.02, 0.05, 0.1, 0.2, 0.5, 1 or 2 seconds
(*1), and can be specified to each function block. (The default operation cycle
is one second for each function block.) or the LCB05D, cycles of 0.01, 0.02,
and 0.05 seconds cannot be set, and for LCB01, LCB03, and LCB05, cycles
of 0.01, 0.02, and 0.05 seconds cannot be set for some blocks, i.e., they can-
not be set for the System Common block (Block Model 000).
Operation is started when the PLC is turned ON regardless of the CPU Unit
operation mode.
*1 The execution cycle for commands in the Step Ladder Program block
(Block Model 301) on the Loop Controller is one of 0.01, 0.02, 0.05, 0.1,
0.2, 0.5, 1 or 2 seconds for each operation cycle in the Step Ladder Pro-
gram block. This applies to Sequence Table blocks (Block Model 302) as
well.
2. External I/O (via the CPU Unit I/O memory)
The Loop Controller actually updates external I/O data from each Unit via
CPU Unit I/O memory at each operation cycle of the Field Terminal block.
3. Constant Data Exchange with CPU Unit (by Function block)
The Loop Controller refreshes data I/O with specified CPU Unit I/O memory
areas at each operation cycle of the CPU Unit Terminal block or the Expanded
CPU Unit Terminal block.
4. On-demand Data Exchange with CPU Unit (by FINS command issued
to Unit)
The CPU Unit can read and write Loop Controller data by issuing the FINS
command to the Loop Controller by the CMND (DELIVER COMMAND) com-
mand in the Step Ladder Program whenever necessary.
5. CPU Unit Status Notification (by reflecting in System Common block)
The status of the CPU Unit (operation mode, fatal error, etc.) is reflected in the
System Common block on the Loop Controller. If necessary, the Loop Control-
ler extracts data from this System Common block.
6. Loop Controller Status Notification (by Auxiliary Area)
The status of the Loop Controller is reflected on the Auxiliary Area in the CPU
Unit. Note, however, that this status is reflected every second for LCB01 and
LCB05, and not at the I/O refresh cycle. For the LCB05D, this status is
reflected each CPU Unit cycle (split refresh).
7. Reading of Error Log Data on Loop Controller
Error log data is stored on the Loop Controller. (The error code, detailed infor-
mation, date (year/month) and time (hour/minute/second) of occurrence are
recorded as one error log data record, and the latest 256 data records are
stored.) The time information, including year, month, hour, minutes, and sec-
tions, are read from the CPU Unit. Adjust the time in the CPU Unit when nec-
essary. Error log data can be read using the read error log FINS command
(command code 2102 Hex).
Section 1-1