
MDS 05-4131A01, Rev. A MDS iNET ENI Supplement 5
2.1.3 Differences Between Allen-Bradley ENI and
MDS iNET/ENI
The functional differences between the Allen-Bradley ENI and the MDS
iNET/ENI include the following:
• The ENI allows up to two peers for outgoing messaging, two peers
for incoming messaging, and two for messaging in either direction.
The iNET/ENI is limited to 128 peers in any direction.
• The ENI supports configuration of the BOOTP Enable flag. The
iNET/ENI supports configuration of DHCP Enable flags.
• The ENI supports saving configuration to both RAM and ROM. The
iNET/ENI always stores configuration in ROM.
• The ENI uses CRC error checking for fixed baud rates and
BCC/CRC auto-detect for autobaud. The iNET/ENI always uses
BCC/CRC autodetect. This simplifies DF1 controller configuration
while maintaining full backward compatibility.
• The ENI only has one serial port. The iNET/ENI has two serial
ports, and supports both of them for data transfer. For the older lad-
der programs written for the ENI, the COM2 port is used as the
default. To support setting a baud rate for the COM1 serial port, an
additional configuration channel 247 is supported.
• The ENI does not support Ethernet message routing (that is, you
cannot send a message from an Ethernet controller to the ENI and
have it re-sent to another Ethernet controller). iNET/ENI supports
Ethernet message routing to implement message transfer over the
wireless link between several iNETs.
NOTE: Configuration of the iNET/ENI can be accomplished using the
same two methods that function with Rockwell’s ENI module:
1. With Rockwell ENI configuration utility connected to
COM2 of the iNET/ENI.
2. Via EtherNet/IP using commands and structures listed for
ENI in the 1761-NET-ENI User Manual.
In addition to these methods, configuration may also be
performed using the standard user interface of the iNET trans-
ceiver and following through the Serial Port Configuration
Wizard for DF1 to EtherNet/IP.
Komentáře k této Příručce