5 - peer-to-peer messaging, Messaging between the eni/eniw and df1 devices, Chapter 5 – Rockwell Automation 1761-NET-ENIW MicroLogix Ethernet Interface (ENI) User Manual User Manual

Page 67: Peer-to-peer messaging, Messaging between the eni/eniw and df1 devices -1, Er 5, Chapter

Advertising
background image

1

Publication 1761-UM006E-EN-P - August 2005

Chapter

5

Peer-to-Peer Messaging

This chapter describes messaging between the ENI/ENIW and DF1
devices. The following topics are covered:

Messaging Between the ENI/ENIW and DF1 Devices
Message to Configuration Nodes (Nodes 100 to 149) and

Sending a Message to a Destination Controller (Nodes 0 to 49)

Messaging Between the
ENI/ENIW and DF1 Devices

The ENI/ENIW can route a DF1 message received from the attached
controller to a compatible destination TCP/IP device, using DF1 node
addresses 0 through 49. ENI/ENIW Node addresses 100 through 149
store TCP/IP destination addresses. When the ENI/ENIW receives a
write message to nodes 100 to 149, it stores the TCP/IP destination
address in the corresponding map register.

To configure the destination TCP/IP addresses, you can use either the
ENI/ENIW Configuration Utility, or you can send a 485CIF/PLC2
message to each node as described in this section.

The table below illustrates the relationship between messages and
their corresponding configuration addresses.

Table 5.1 Message Routing

ENI/ENIW receives read
or write 485CIF/PLC2
message to

ENI/ENIW
TCP/IP route
configuration

Message forwarded to destination
node TCP/IP address

Node 0

Node100

111.222.233.200 (stored at Node 100)

Node 1

Node101

111.222.233.201 (stored at Node 101)

Advertising
This manual is related to the following products: