Rockwell Automation 1734-ADNX POINT I/O DeviceNet Adpater User Manual - Manual (Page 114)

Publication 1734-UM002C-EN-P - July 2003
C-2 1734-ADNX Rules and Guidelines Regarding How to Use the 1734-ADNX
RULE 7: The EDS parameter, “Max Backplane MACID” must be set to
not be lower than that of any backplane modules. If no backplane
modules are used, this value can be set to be 0, allowing modules
1-63 to be attached to the Subnet using DeviceNet cable.
RULE 8: Backplane modules are always addressed in increasing order
from left to right. Gaps in the backplane addressing are permitted.
Empty slots in the backplane are NOT permitted.
RULE 9: Subnet modules not on the backplane must always have or
be assigned MAC ID’s higher than those of the backplane modules.
RULE 10: Power must be supplied for non-backplane Subnet modules.
The 1734-ADNX only supplies power to the backplane POINT I/O
modules.
RULE 11: The 1734-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 1734-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 POINT
I/O module on the 1734-ADNX backplane, but can own POINT I/O
modules on the subnet that are connected with a 1734-PDN or 1734D
POINTBlock.
RULE 14: The 1734-ADNX does not autobaud on the subnet.