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

1 Publication 1738-UM001A-EN-P - February 2005
Appendix
C
Rules and Guidelines For the 1738-ADNX
RULE 1: A DeviceNet Subnet may not bridge directly to another
DeviceNet Subnet. A 1738-ADNX may not be used on the Subnet of
another 1738-ADNX.
NOTE: The 1738-ADNX will fault and report an error with any
attempt to route message beyond the Subnet. It is not possible,
therefore, to send explicit messages or browse through two
1738-ADNX adapters in series or through one 1738-ADNX and a
network bridge device (or similar device) in series.
RULE 2: The aggregate sum of the primary DeviceNet trunk and its
tributary Subnets cannot exceed the primary DeviceNet trunk
scanner’s I/O table size. The primary DeviceNet trunk scanner is the
primary scanner, which provides data directly to the controller that
owns the ArmorPoint I/O modules. For a complete list of scanners,
refer to the RA Knowledgebase, Document # G32941961.
RULE 3: The 1738-ADNX Subnet is subject to all of the rules of ODVA
requirements for DeviceNet compliant devices.
RULE 4: A DeviceNet Subnet may not bridge to any other network.
Network is defined in this case as any communication link that is
transmitting information from multiple devices to a single
channel for
further processing and transmission onto a separate network. A 1791D
CompactBlock I/O module can be used on the Subnet of a
1738-ADNX, the other ArmorPoint DeviceNet adapters (1738-ADN12,
-ADN18, and -ADN18P) cannot be used on the Subnet.
RULE 5: The 1738-ADNX DeviceNet Subnet is comprised of the
adapter (always MACID 0), any backplane I/O modules and ODVA
compliant devices attached to the lower DeviceNet connector.
RULE 6: The 1738-ADNX DeviceNet Subnet must be terminated, like
any other DeviceNet network, according to ODVA specifications.
RULE 7: The EDS parameter, ‘Max Backplane MACID’ must be set so
that it is not 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.