Rockwell Automation 1738-ADNX ArmorPoint I/O DeviceNet Adapters - Manual (Page 110)

Publication 1738-UM001A-EN-P - February 2005
C-2 Rules and Guidelines For the 1738-ADNX
RULE 9: Subnet modules not on the backplane must always have or
be assigned MACID’s higher than those of the backplane modules.
RULE 10: Power must be supplied for non-backplane Subnet modules.
The 1738-ADNX supplies only 5V dc power to the backplane
ArmorPoint I/O modules, and 24V dc power to the non-backplane
modules via the auxiliary power connector, pins 2 and 3.
RULE 11: The 1738-ADNX connection sizes may have to be manually
entered into the primary DeviceNet network scanner device’s scanlist
(1756-DNB, 1747-SDN, etc.). Those connection sizes can be read from
the EDS parameters 8-11 or deduced from the 1738-ADNX adapter’s
Subnet I/O mapping.
RULE 12: Explicit message requests will not transmit from the Subnet
to the primary DeviceNet trunk. For example, a laptop computer
connected to the Subnet with RSLinx will not be able to browse onto
the primary DeviceNet.
RULE 13: Any master connected to the Subnet cannot own a
ArmorPoint I/O module on the 1738-ADNX backplane.
RULE 14: The 1738-ADNX does not autobaud on the Subnet.