72
Remote I/O Allocations Section 4-3
IMPORTANT (1) For the NE1A-SCPU01-V1(-EIP), N = 2 and M = 1. For the NE1A-
SCPU02(-EIP), N = 5 and M = 2. The sizes of the local input status, test
output/muting lamp status, and local input monitor status data can be
specified in bytes.
(2) The measures required for handling data as safety data in the data gen-
eration process will not be executed for status and I/O tag data items with
a non-safety attribute. Therefore do not use those items to configure a
safety system.
Moreover, even if the attribute for an item is “safety,” it will become “non-
safety” for data input using standard I/O communications or for I/O tags
connected with standard devices. Therefore, those items must also not
be used to configure a safety system.
If the above data is combined, the I/O data will be configured as follows:
1. When status data is set, the status is allocated at the beginning of the re-
mote I/O area in the order shown below. (Status areas that are not set are
not reserved, i.e., no unassigned areas are left.)
General Status
↓
Local Input Status
↓
Local Output Status
↓
Test Output/Muting Lamp Status
2. When the local I/O monitor data is set (Controllers with unit version 1.0 or
later only, including Controllers that support EtherNet/IP), the local I/O
monitor data is attached after the other status data in the following order.
(When local I/O monitor data is not set, the data will be shifted forward and
that local I/O monitor area will not be reserved. This area does not exist in
Pre-Ver. 1.0 Controllers.)
Local Input Monitor
↓
Local Output Monitor
3. After the status data and local I/O monitor data, user-registered I/O tags
are allocated in the remote I/O area in the order of registration. At this time,
free areas are not reserved and all valid data is allocated with no unas-
signed areas.
Examples of settings from the Network Configurator are shown below, along
with the remote I/O area arrangements.
To Next Page
Loading...
