5 Remote I/O Slave Communications
5-6
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
z User-set Remote I/O Allocations Using Device Variables for CJ-series Unit
Note Slave communications must be disabled prior to area allocation and must be enabled
after area allocation. The order of the procedure is 1) stop slave communications, allo-
cate areas, and then enable slave communications. The allocated areas will not be valid
if the procedure is done in any other order.
Precautions for Correct UsePrecautions for Correct Use
In fixed allocation or user-set allocations through the device variables for CJ-series Unit, area
allocations must be set with slave communications disabled and will be transferred to Units when
slave communications are enabled.
Allocations will not be valid if slave communications are enabled during area allocation.
Switch the CPU Unit to PROGRAM mode.
Change "*_Sw2SlavDsblCmd" (Slave Stop Switch) to TRUE from the Sysmac Studio.
Change "*_Sw2SlavEnblCmd" (Slave Enable Switch) to TRUE from the Sysmac Studio.
Define user-defined variables in the area to which I/O data is allocated.
Switch the CPU Unit to RUN mode.
Slave remote I/O communications will begin.
1) Input data in advance into "*_SlavAlocTblCfg[0]" to "*_SlavAlocTblCfg[5]" (Slave User-set Allocations
Setup Table) and the Allocation Size Setup Table from the Sysmac Studio.
2) Set "*_Sw2SlavAlocCmd" (Slave User Allocations Switch) to TRUE from the Sysmac Studio.
Pre
operations
Slave function
disabled
Slave function
enabled
Post operation
Area
allocations
To Next Page
Loading...
