Rockwell Automation 1761-NET-ENIW MicroLogix Ethernet Interface (ENI) User Manual User Manual
Page 68
Publication 1761-UM006E-EN-P - August 2005
5-2 Peer-to-Peer Messaging
If the ENI/ENIW receives a 485CIF/PLC2 read message to any of its
configuration addresses (nodes 100 to 149), the ENI/ENIW responds
with the current configuration of that node/address.
Using the configuration shown in Table 5.1; if the controller initiates a
read or write message to node 0, the ENI/ENIW forwards the request
to the TCP/IP address at Node 100 (111.222.233.200).
Message to Configuration
Nodes (Nodes 100 to 149)
and Sending a Message to
a Destination Controller
(Nodes 0 to 49)
When the ENI/ENIW receives a message from the attached controller
to Node Address 0 to 49, it looks up the TCP/IP address associated
with the address at Nodes 100 to 149. The ENI/ENIW preserves the
original DF1 address when sending back a reply.
The following table illustrates the relationship between configuration
addresses and their corresponding messaging address.
IMPORTANT
When the ENI/ENIW receives a 485CIF/PLC2 write
message to a configuration node address (100
through 149), it closes any open communications
currently active on that connection and reconfigures
the IP address to match the new configuration.
If the received data matches the current
configuration, the ENI/ENIW closes any open
communications with the destination device.
You must wait at least one second before sending a
new message to that node address or you may
receive a connection error.
Table 5.2 Peer-to-Peer Message Routing
Node
Number
(1)
(1) See the IMPORTANT note below about assigning Nodes to various devices.
Function
Node
Number
Routing Table
Data Type
0
DF1 Route 0 MSG
100
Route 0 IP Address
Integer (4 words)
1
DF1 Route 1 MSG
101
Route 1 IP Address
Integer (4 words)
2
DF1 Route 2 MSG
102
Route 2 IP Address
Integer (4 words)
3
DF1 Route 3 MSG
103
Route 3 IP Address
Integer (4 words)
↓
↓
↓
↓
↓
49
DF1 Route 49 MSG 149
Route 149 IP Address
Integer (4 words)