How to Use the Node Terminal Block
Appendix 2
221
Basic Procedure
Step 2. Wiring in software of Terminal to All Nodes Send
block or Terminal from All Nodes Receive block
Step 1. Initial setting to System Common blocks
Step 3. Connection/setting of Controller Link
Step 4. Preparation of Controller Link Data Link table, and
registration and download to all nodes
Step 5. Startup of Controller Link Data Link
Note
The Loop Control Unit can also use this function to exchange data with a CPU Unit at another
node via the Data Link even if a Loop Control Unit is not mounted at another node PC on the
Controller Link network.
Initial Setting of the System Common Block
To use the node terminals (excluding the DO and AO Terminal Settings from Computer blocks [Block Models
409 and 410]), CX-Process Tool must be used to set the leading addresses of the Data Memory (on CPU
Unit) for the node terminals to ITEM042 and ITEM043 of the System Common block.
Note
When only the DI and AI Terminal Setting from Computer blocks are used as the node terminals
and the data received from the computer is stored to the Area to send to all nodes and is not then
sent to a networked Loop Control Unit, operation is possible without the need to perform initial
setting of the System Common block as shown in the table below.
System Common block (Block Model 000)
ITEM
Data name
Data range
Default
043
Leading address (S) of Data Memory for the Node
Terminals (on CPU Unit)
0 to 32767
16020
042
Setting of LCU number: ID data of multiple (max. 3)
Loop Control Units mounted on CPU Rack
0 to 2
0
When the above ITEMs are set, the system information of the Loop Control Unit is automatically reflected in
eight words within leading address S to leading address S+23 words of the Data Memory (on CPU Unit) for
the Node Terminals.