Take a Quantum Leap into

Integrated Architecture with...

1734-ADN X
eXtended DeviceNet adapter

March 2003
The 1734-ADNX is an I/O ADAPTER

1734 POINT I/O

Main DeviceNet trunk

The 1734-ADNX is a DNet to DNet Bridge

Main Device Net trunk

1734-ADNX DeviceNet Subnet

 The 1734-ADNX is a SCANNER

1734-ADNX supports Auto Device Replace (ADR) &

Auto Scan / Auto Configure of 3rd Party Devices
The 1734-ADNX Increases CONNECTIVITY

Main DeviceNet
trunk to controller
The ADNX CONNECTS
many devices to ONE NODE
on the Main DeviceNet
network
1734-ADNX DeviceNet Subnet
 What is an ADNX?

 The 1734-ADNx Extended DeviceNet adapter provides the

ability to connect additional DeviceNet components to a
distributed POINT I/O system.

Main DeviceNet trunk to controller

1734-ADNX DeviceNet subnet

Use the ADNX’s subnet

to TIE AN ENTIRE
CABINET OR AREA
TOGETHER AS A
SINGLE NODE ON
THE MAIN NETWORK
1734-ADNX Extends the Length of DeviceNet

Main DeviceNet trunk

500 meters (thick cable)
63 nodes

1734-ADNX DeviceNet subnet

+ 500 meters (thick cable)
+ 63 nodes
 1734-ADNX Features

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

Upgrade 1734-ADN
+ 500 meters (thick cable)
+ 63 nodes
DNet to DNet Bridge
DNet / DNet Isolation
 1734-ADNX Benefits

Main
DeviceNet
trunk

1734-ADNX DeviceNet subnet

Upgrade 1734-ADN – REDUCES SYSTEM UPGRADE COSTS

+ 500 meters (thick cable) – REDUCES INSTALLATION & OPERATING COSTS
+ 63 nodes – REDUCES COST OF CONTROL SYSTEM
DNet / DNet Isolation – REDUCES DOWNTIME, INCREASES PRODUCTIVITY
DNet to DNet Bridge – REDUCES DOWNTIME, INCREASES PRODUCTIVITY
 1734-ADNX Functionality

Main
DeviceNet
trunk

1734-ADNX DeviceNet subnet

DeviceNet Sensors/Devices
Motor Starters
More I/O
Push Button Stations
Tower Lights
 1734-ADNX - How It Works

 The 1734-ADNX DeviceNet adapter performs the following functions:

 DNet to DNet bridge
 I/O Scanner
 Slave device on main DeviceNet trunk
 Scanner on 1734-ADNX subnet

Micro ADNX Bus_Enable

Backplane
24VDC Processor

DeviceNet
CAN CAN CAN_H
CAN_H
CAN_L
Shield
5VDC
CAN_L
Ground
Ground
Note the separate DC/DC
Converter

Power
Common

Field
power supply required 24VDC
for the non-backplane
Wiring Arm
Protection

subnet DeviceNet Common 24VDC

SubNet
24VDC CAN_H
power
Shield
CAN_L
Subnet Ground
P/S
 1734-ADNX Rules

Main DeviceNet
trunk

NO
DeviceNet subnet
!
RULE #1:
No 1734-ADNX adapters or DeviceNet to
DeviceNet bridges on the subnet
 1734-ADNX Rules
Scanner Memory Sizes (bytes, max)
1771-SDN - 715 in, 715 out
1747-SDN - 362 in, 362 out
1756-DNB - 496 in, 492 out
(For a complete list of scanners refer Node Connection Size
to the RA Knowledgebase, 256 bytes Max
Document # G32941961) for each node
Software Limitation ADNX Delay Time
200us – 5msec
8-bit ‘size’ fields in RSNetWorx
scan list structure
limits connection sizes to 256
bytes per connection.
Main Device Net TRUNK

RULE #2:
Cannot ADNX Connection Sizes
COS Produce - 248 bytes max
exceed I/O Polled Produce - 248 bytes max
table size in Polled Consume - 248 bytes max
Strobe Produce - 8 bytes max 1734-ADNX DeviceNet subnet
scanner.
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

RULE #3:
Devices on the 1734-ADNX DeviceNet subnet
MUST BE compliant with ODVA requirements.
 1734-ADNX Rules
1734-ADNX

Main DeviceNet
trunk 1734-ADN

DeviceNet subnet NO
!
Device Net to
RS485 Bridge
RULE #4:
Networking beyond the subnet is not
NO recommended and operation of devices on a
! tertiary network is unpredictable. Do not add a
bridge or an intelligent network-to-network device
to the DeviceNet subnet of the 1734-ADNX.
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

RULE #5:
The subnet is comprised of the adapter (always
MACID 0), any backplane I/O modules (nodes 1 to
X), and ODVA compliant devices (nodes X+1 to
63) attached to the lower DeviceNet connector (on
the adapter). See Rule #7.
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

RULE #6:
The subnet must be terminated, in accordance
with ODVA specifications.
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

RULE #7:
The EDS parameter, “Max Backplane MACID”
must not be set 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 a DeviceNet
cable.
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

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.
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

RULE #9:
Subnet modules not on the backplane always
have MACIDs higher than those of the backplane
modules.
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

RULE #10:
Power must be supplied for non-backplane subnet modules.
(The 1734-ADNX supplies power to the backplane POINT I/O modules.)
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

RULE #11:
The 1734-ADNX connection sizes may have to be
manually entered into the main DeviceNet network
scanner scan list (1756-DNB, 1734-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.
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

RULE #12:
Explicit message requests will not transmit from the
subnet to the main DeviceNet trunk. For example, a
laptop computer connected to the subnet with RSLinx
will not be able to browse onto the main DeviceNet
trunk.
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

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
module.
 1734-ADNX Rules

Main DeviceNet trunk

1734-ADNX DeviceNet subnet

RULE #14:
The 1734-ADNX does not Autobaud on the subnet.
 1734-ADNX Specifications

• Input Voltage Rating: 24 Vdc nominal; 10 to 28.8 Vdc range

• Field Side Power Requirements: 24 Vdc @ 400 mA maximum

• Inrush Current: 6 A maximum for 10 ms

• POINTBus Output Current: 1 A maximum @ 5 Vdc +/- 5%

• Input Over Voltage Protection: Reverse polarity protected

 1734-ADNX Positioning
Main DeviceNet
Scanner
Unique DeviceNet-based POINTBus
backplane allows 4 different levels
of connectivity to DeviceNet.
1734-PDN - DeviceNet Interface
• Each POINT module = 1 node
1734D POINTBlock
• Each POINT module = 1 node
• 16 points plus expansion modules
1734-ADN DeviceNet Adapter
• Entire POINT system = 1 node
1734-ADNX Extended Adapter
• Entire POINT system = 1 node
• Add any 3rd party ODVA compliant
devices to the backplane