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

1 Publication 1738-UM001A-EN-P - February 2005
Appendix
B
Quick Start For the 1738-ADNX
What’s In This Appendix? In this Quick Start, you will learn how to use the 1738-ADNX with a
ControlLogix system on DeviceNet. You will also use one of the
1738-ADNX’s features (Auto Start Mode) in an exercise to
automatically configure devices on its Subnet
.
When you complete this quick start you will be familiar with:
• The 1738-ADNX as an adapter on the ControlLogix primary
DeviceNet network and as a scanner on the DeviceNet
expansion Subnet
• Configuring the 1738-ADNX with ArmorPoint I/O on its Subnet
• Using and applying the correct termination of the 1738-ADNX’s
Subnet
• Using the 1738-ADNX to expand the length of a DeviceNet
system
• Using the 1738-ADNX to implement a second baudrate for
Subnet devices
For rules and guidelines regarding how to use the 1738-ADNX,
see Appendix C of this manual.
Assumptions A ControlLogix DeviceNet system already exists to which you are
going to add new devices without modifying the existing system’s
architecture. You are going to expand the length of the system beyond
its maximum specification and add new devices that can operate at a
different baudrate than the existing system.
The existing system attributes include:
• ControlLogix processor in a Logix chassis of 4 or more slots.
• 1756-ENBT (EtherNet/IP) in the Logix chassis.
• Configuration to 125 Kbaud with thin trunk (max distance is
100 m (328 ft.) (ControlLogix chassis may be connected on any
DeviceNet network.)
• ControlLogix processor with a 1756-DNB (DeviceNet) in slot 3
(slot 3 was picked for this example. This can be any slot.)