Because of the variety of uses for the products described in this
publication, those responsible for the application and use of these
products must satisfy themselves that all necessary steps have been
taken to assure that each application and use meets all performance
and safety requirements, including any applicable laws, regulations,
codes and standards. In no event will Rockwell Automation be
responsible or liable for indirect or consequential damage resulting
from the use or application of these products.
Any illustrations, charts, sample programs, and layout examples
shown in this publication are intended solely for purposes of
example. Since there are many variables and requirements associated
with any particular installation, Rockwell Automation does not assume
responsibility or liability (to include intellectual property liability) for
actual use based upon the examples shown in this publication.
Allen-Bradley publication SGI-1.1, Safety Guidelines for the
Application, Installation and Maintenance of Solid-State Control
(available from your local Rockwell Automation office), describes
some important differences between solid-state equipment and
electromechanical devices that should be taken into consideration
when applying products such as those described in this publication.
Reproduction of the contents of this copyrighted publication, in whole
or part, without written permission of Rockwell Automation, is
prohibited.
Throughout this publication, notes may be used to make you aware of
safety considerations. The following annotations and their
accompanying statements help you to identify a potential hazard,
avoid a potential hazard, and recognize the consequences of a
potential hazard:
WARNING
Identifies information about practices or
circumstances that can cause an explosion in a
hazardous environment, which may lead to personal
injury or death, property damage, or economic loss.
!
ATTENTION
Identifies information about practices or
circumstances that can lead to personal injury or
death, property damage, or economic loss.
!
IMPORTANT
Identifies information that is critical for successful
application and understanding of the product.
Allen-Bradley, RSNetWorx for DeviceNet, PointBus, and POINT I/O are trademarks of Rockwell Automation.
DeviceNet is a trademark of Open DeviceNet Vendor Association.
Summary of Changes
Using Change Bars
New and Revised
Information
This document contains updated information. Changes are identified
by change bars in the margin, as shown to the left.
The table below lists the new and revised information included in this
release of the POINT I/O DeviceNet Adapter user manual.
Table Summary of Changes.A
Information aboutNew or revised:Location:
Guidelines for Using Your
Adapter
Using Auto Start ModeNewChapter 2
Using the Cycling I/O
Mapping Feature
Removing and Reinserting
Modules on the DeviceNet
Network
1734-ADNX Quick StartNewAppendix B
1734-ADNX Rules and
Guidelines on How to Use
the 1734-ADNX
NewPreface
Chapter 6
Chapter 3
Appendix B
NewChapter 2
Chapter 3
NewChapter 2
NewAppendix C
Use Default Data MapsNewAppendix D
1Publication 1734-UM002C-EN-P - July 2003
Summary of Changes 2
Notes:
Publication 1734-UM002C-EN-P - July 2003
Preface
Purpose of this Manual
This manual describes how to install, configure and operate your
POINT I/O DeviceNet™ Adapter, catalog number 1734-ADN.
For more information about:See page:
Who Should Use This ManualPreface-1
What the Manual ContainsPreface-2
Related TermsPreface-3
Related Products and DocumentationPreface-5
Guidelines for Using Your AdapterPreface-5
Conventions Used in This ManualPreface-6
IMPORTANT
In this manual, we use 1734-ADN(X) to refer to both
the 1734-ADN and 1734-ADNX modules. We use
1734-ADN to refer to only the 1734-ADN module. We
use 1734-ADNX to refer to only the 1734-ADNX
module.
In the rest of this manual (except Chapter 4), we
refer to the 1734-ADN(X) POINT I/O DeviceNet
adapter as the adapter.
Who Should Use
This Manual
In Chapter 4, we refer to the POINT I/O DeviceNet
adapter as the scanner because the chapter describes
how to configure the adapter for use with POINT
I/O modules.
You must be able to use RSNetWorx™ for DeviceNet software or
similar configuration software to configure your adapter.
In this manual, we assume you know how to configure an adapter. If
you do not, refer to your software user manuals or online help before
attempting to use this adapter.
We also assume you are familiar with the POINT I/O product line,
including other fieldbus interfaces, I/O modules and power supplies.
If you are not familiar with these components, you can read some of
the POINT I/O documents listed on page
Preface-5.
1Publication 1734-UM002C-EN-P - July 2003
Preface 2
What the Manual Contains
Chapter 1 - Installing the 1734-ADN(X) Adapter
Description of how to install and wire the adapter
Chapter 3 - Using Auto Start Mode
Description of how to use the Auto
Start Mode on your adapter to quickly
get your system up and running
This manual contains the following sections:
Chapter 2 - What is the 1734-ADN(X) Adapter?
Overview of the adapter’s features and functionality
Module
Status
DeviceNet
63
Status
DeviceBus
Status
1734-ADN
Or
1734-EP24DC
System
Power
Field
Power
Chapter 4 - Configuring the
1734-ADN(X) Adapter’s SubNet
Description of how to configure your
adapter
Chapter 5 - Adding the 1734-ADN(X) to
the DeviceNet Scanner’s Scanlist
Description of how to configure the
DeviceNet adapter and to add it to the
scanlist.
Appendix B - Quick Start
Learning how to use the 1734-ADNX with
a ControlLogix system on DeviceNet
Chapter 6 - Troubleshooting the
1734-ADN(X) Adapter
Description of how to use the status
indicators and to troubleshoot your adapter
Appendix C - 1734-ADNX Rules and
Guidelines
Regarding how to use the 1734-ADNX
Appendix A - Specifications
Listing of the 1734-ADN(X) specifications
Appendix D - Default Data Maps
Listing of the default data maps for
1734-POINT I/O modules
Publication 1734-UM002C-EN-P - July 2003
Preface 3
Related Terms
This manual uses the following terms:
Ter m:Definition:
AdapterPOINT I/O DeviceNet adapter (1734-ADN and 1734-ADNX).
Auto Catalog ReplaceThe POINT I/O DeviceNet adapter supports the swapping of
two identical modules connected to the adapter. I.e., if a
1734-IB4 is in slot 3 and another 1734-IB4 is in slot 7, the two
modules can be removed from the POINT system and the slot 3
module placed into slot 7, and vice-versa. When ADR is active,
the swapped modules will be reconfigured to match the
previous module in their new slot. When ADR is not active, the
configuration parameters will not be modified, the swapped
modules must have identical configuration, and values for
their EDS file parameters.
Auto Device ReplaceThis refers to the ADR feature of a ControlLogix System on
DeviceNet. With ADR active, any device on the DeviceNet link
may be removed and replaced with an out-of-the-box
checkmark compliant DeviceNet device. The ADR feature will
result in downloading the values of the configuration
parameters of the EDS file, of the removed device, to the new
device.
Auto Start ModeA feature that lets the POINT I/O system get “up and running”
without the prerequisite to configure any of the EDS
parameters for the POINTBus
Auto Start Mode will result in a scan list within the adapter
which stores the modules identity information.
™ or POINT I/O modules. Using
AutobaudFeature in devices (e.g. POINT I/O modules) on the DeviceNet
network that causes them to listen to communications on the
network and set their own baudrate to match the network
rate.
BackplaneThe PointBus that consists of POINT I/O modules connected to
the 1734-ADN(X) adapter.
BaudrateRate of communications between devices on the DeviceNet
network. Backplane baudrate is used for the 1734-ADN.
Subnet baudrate is used for the 1734-ADNX.
Change of State (COS)DeviceNet communications method in which the adapter
sends data based on detection of any changed value within
the input data. Data is independently received based on
change of state from the sender. Data in both directions can be
acknowledged or unacknowledged depending on the run time
configuration of the system.
CommissioningThe period in time associated with post startup activities.
Commissioning implies that the system has been validated
and all configuration parameters are correct, all modules are
in good operating condition, and the adapter scanlist is
complete.
ControlFlashUtility software you can use to update the adapter’s firmware
with the most current Boot and Application code.
Publication 1734-UM002C-EN-P - July 2003
Preface 4
Term:Definition:
CyclicDeviceNet communications method in which the adapter
sends data cyclically based on a configured time value. Data is
independently received cyclically from the sender. Data in both
directions can be acknowledged or unacknowledged
depending on the run time configuration of the system.
MAC IDMedia Access Control Identifier (DeviceNet network address).
MasterA DeviceNet network device (e.g., 1771-SDN) that initiates
communication with DeviceNet slave devices (e.g., POINT I/O
modules) to retrieve data. The master only receives
unprompted data when the slave is enabled for COS and there
is a change in the device’s operating state.
MAX BACKPLANE IDA unique attribute, Max(imum) Backplane MACID, has
been added to 1734-ADNX. This value represents the highest
node address of a module residing on the backplane. This
value must be greater than or equal to the rightmost
backplane POINT I/O module, but must be less than that of
any non-backplane Subnet module.
OfflineState of the adapter when it is not powered or maintaining
normal communications exchanges with other DeviceNet
devices.
OnlineState of the adapter when it is powered and maintaining
normal communications exchanges with other DeviceNet
devices.
PointBusThe POINT I/O backplane. PointBus maintains all DeviceNet
network protocol but also offers configuration capabilities.
PolledDeviceNet communications method in which a module sends
data in response to received data.
Primary NetworkThe Primary DeviceNet Network, and it is defined as the
DeviceNet link that provides the direct connection between
the POINT DeviceNet adapter and a DeviceNet scanner
RSNetWorx for DeviceNetConfiguration software for the adapter and Subnet modules.
ScanlistThe list of Subnet modules connected to the adapter. When
ADR is active, the scanlist stores the configured values of
each of the Subnet modules’ configurable parameters. When
ADR is not active, the scanlist stores only the module identity
information.
ScannerOperating state of the 1734-ADN(X) when it retrieves I/O data
from Subnet modules.
SlaveA DeviceNet network device that cannot initiate
communication (except when configured with COS enabled)
but responds to a DeviceNet master device.
StrobeAdapter sends data in response to the strobe command. The
single bit allocated to the adapter in the strobe message is not
used. If the configured size of the input data (sent from the
adapter) is greater than 8 bytes, the strobe connection
establishment will fail. In this case, the input size must be
reconfigure to 8 bytes or less.
Publication 1734-UM002C-EN-P - July 2003
Term:Definition:
Subnet1734-ADNX only.
The Subnet DeviceNet Network, and is defined as the
DeviceNet link that provides the expansion of the POINTBus to
allow the 1734-ADNX to use its lower connector to add an
additional 500 meters and up to 63 nodes which will be
bridged through the 1734-ADNX up to the Primary Network.
Note that backplane modules are also part of the Subnet.
Preface 5
Related Products and
The following table lists related POINT I/O products and
documentation:
Documentation
DocumentCat. No.Publication
POINT I/O Technical Data1734-Series1734-TD002
POINT I/O Digital and Analog I/O Modules and POINTBlock I/O Modules User Manual 1734-Series and
1734D-Series
POINT I/O Module Installation Instructions1734-Series1734-INxxx (Multiple numbers)
DeviceNet Communication Interface Installation Instructions1734-PDN1734-IN057
POINT I/O 24V dc Expansion Power Supply Installation Instructions1734-EP24DC1734-IN058
Field Potential Distributor Installation Instructions1734-FPD1734-IN059
General Installation InstructionsAll 17341734-IN510
Wiring Base Assembly Installation Instructions1734-TB, -TBS1734-IN511
Wiring Base Assembly Installation Instructions1734-TB3, -TB3S 1734-IN013
Terminal Marking Kit1492-PLTKIT1492-UM001 and 1492-5.0
DeviceNet Cable System Planning and Installation Manual DN-6.7.2 DN-6.7.2
Industrial Automation Wiring and Grounding GuidelinesN/A1770-4.1
1734-UM001
Guidelines for Using
Your Adapter
If you need more information on these products, contact your local
Rockwell Automation/Allen-Bradley distributor, integrator or sales
office for assistance. For more information on the documentation,
refer to the Allen-Bradley Publication Index, publication SD499.
Remember the following operational guidelines when using your
1734-ADN(X) adapter.
Publication 1734-UM002C-EN-P - July 2003
Preface 6
• Do not leave spaces in the I/O. Instead, install all POINT I/O
modules adjacent to each other.
IMPORTANT
• Populate every position on the DIN rail.
• Do not add new I/O modules to the end of the POINT I/O
system while the system is under power.
• Use both labels with the I/O modules and removable terminal
blocks (RTBs).
• Do not separate I/O modules and RTBs with the same number.
• Do not move I/O modules to different locations on the DIN rail
after they have been installed and configured. You should
always place modules with the matching RTB.
• If adjacent modules (i.e., 2 or more) are removed, replace all of
them to operate the POINT I/O system. Input data will hold last
state until all previously-removed modules are replaced.
If you must leave an I/O space open temporarily,
you must change the keying position on the
mounting base (1734-MB) to #5. This position will
prevent you from installing the wrong I/O module
on the base.
Conventions Used In
This Manual
• Use Allen-Bradley terminal markers to identify your POINT I/O
modules. The cards are easily ordered from your Rockwell
Automation representative under the Bulletin 1492 number.
For more information on the Allen-Bradley terminal marking
kits, see the documents list on page
The following conventions are used throughout this manual:
• bullet lists (such as this one) provide information, not
procedural steps
• number lists provide sequential steps
• text written like this identify screen, menu, toolbar names, field
names, buttons, and check boxes on screens
• a menu item in this format File>Save identifies the submenu item
after the caret (>) accessed from the main menu (name before
the caret)
• pictures of symbols and/or screens represent the actual symbols
This chapter describes how to install and wire your adapter.
For more information about:See page:
Installing the Adapter1-2
1
Installing a Replacement DeviceNet
Adapter in an Existing System
Wiring the Adapter1-5
Chapter Summary and What’s Next1-6
When properly installed, POINT I/O is grounded through the DIN rail
to chassis ground. We recommend using zinc plated, yellow
chromated steel DIN rail to assure proper grounding.
Other DIN rail materials (e.g. aluminum, plastic, etc.) can corrode or
oxidize and are poor conductors that may result in improper or
intermittent platform grounding.
If you choose not to use zinc plated, yellow chromated steel DIN rail
for your POINT I/O, we recommend occasional cleaning of the DIN
rail to prevent or lessen the effects of oxidation and corrosion.
1-4
1Publication 1734-UM002C-EN-P - July 2003
1-2 Installing the 1734-ADN(X) Adapter
Installing the Adapter
1734-ADN(X) communication interface
Orange screw slot
To install the adapter on the DIN rail prior to installing other base
units, proceed as follows.
1. Position the adapter vertically in front of the DIN rail.
2. Press firmly to install the adapter on the DIN rail. The locking
mechanism locks the adapter to the DIN rail.
DIN rail
31110-MC
3. Insert the DeviceNet network plug and tighten the
holding screws.
DeviceNet network plug
Holding screw
Holding screw
31111-MC
Publication 1734-UM002C-EN-P - July 2003
Installing the 1734-ADN(X) Adapter 1-3
4. Set the node address using the 2-position thumbwheel switch.
Valid physical settings range from 00 to 63. Press either the + or
- buttons to change the number.
You can also set the node address to some value between 64-99.
In this case, you can change the adapter’s node address via the
RSNetWorx for DeviceNet software. If a value between 64-99 is
used, at power-up the node address stored in the adapter’s
non-volatile memory is used.
Network Node
Address Thumbwheel
Adapter
Status
DeviceNet
Status
PointBus
Status
1734-ADN
System
Power
Field
Power
42510
5. Slide the safety end cap up to remove it. This exposes the
backplane and power interconnections.
Safety end cap
ATTENTION
!
31112-MC
Do not discard the safety end cap. Use this end cap
to cover the exposed interconnections on the last
mounting base on the DIN rail. Failure to do so
could result in equipment damage or injury from
electric shock.
Publication 1734-UM002C-EN-P - July 2003
1-4 Installing the 1734-ADN(X) Adapter
Installing a Replacement
DeviceNet Adapter in an
Existing System
Your existing control application may be using another DeviceNet
adapter (e.g., 1734-PDN) that you want to replace with a
1734-ADN(X) DeviceNet adapter. Remove the existing adapter from
the DIN rail
as follows:
1. Eliminate power to the adapter and all I/O modules in your
2. Remove the wiring assembly and DeviceNet cable from your
3. Remove the adjacent I/O module.
existing system.
existing adapter.
For information on how to remove POINT I/O modules from the
DIN rail, see the associated publications for those modules.
RTB removal handle
42511
4. Use a small bladed screwdriver to rotate the DIN rail locking
screw to a vertical position and release the locking mechanism.
42417
5. Pull the adapter off of the DIN rail to remove it from the
existing system.
Publication 1734-UM002C-EN-P - July 2003
Installing the 1734-ADN(X) Adapter 1-5
6. Insert the new adapter into slot 0 using the steps described on
1-2.
page
7. Reattach I/O modules to the new adapter.
Wiring the Adapter
Your adapter’s wiring and network designations are shown below.
Adapter
Adapter Status
Node Address
Thumbwheel
DeviceNet
Connector
Subnet
Connector
NC = No Connection
CHAS GND = Chassis Ground
C = Common
V = Supply
Status
DeviceNet
DeviceNet Status
Status
PointBus
PointBus/Subnet Status
Status
1734-ADNX
System
System Power
Power
Field
Field Power
Power
NC
CHAS GND
C
V
NC
CHAS GND
C
V
Adapter/Field Power
12/24V dc
01
NCNC
This dc supply is
3
CHASCHAS
5
C
connected to the
internal power bus.
You cannot supply
power to the adapter
from the DeviceNet
7
power supply.
42513
V dc
2
4
C
6
VV
NC = No ConnectionCHAS GND = Chassis Ground
C = CommonV = Supply (Do not connect 120/240V ac power to this supply.)
In this chapter, you learned how to install and wire your adapter.
Move to chapter 2 to learn about the 1734-ADN(X) adapter.
Publication 1734-UM002C-EN-P - July 2003
Chapter
2
What is the 1734-ADN(X) Adapter?
This chapter describes the POINT I/O DeviceNet adapter, including
descriptions of the adapter’s features and functionality.
For more information about:See page:
Using the Adapter2-2
Understanding the DeviceNet Network and Subnet2-6
Adapter Features2-8
Auto Start Mode2-9
Communicating Through the Adapter2-18
Communicating with I/O Modules2-22
Using Diagnostic Tables2-23
Chapter Summary and What’s Next2-24
1Publication 1734-UM002C-EN-P - July 2003
2-2 What is the 1734-ADN(X) Adapter?
Using the Adapter
The adapter resides on the primary DeviceNet network and the
Subnet simultaneously.
IMPORTANT
The PointBus maintains all DeviceNet network
protocol but also offers configuration capabilities.
From this position, the adapter interfaces between DeviceNet devices
and POINT I/O modules. The graphic below shows the adapter on
the DeviceNet network and PointBus.
computer with PLC
programming software
ControlNet network
PLC-5 processor
1784-PCD
PCMCIA card
computer with
RSNetWorx for
DeviceNet software
DeviceNet network
1734-ADN adapter
Subnet (1734-ADNX only)
After you have installed your adapter into a POINT I/O system, you
must perform the following tasks:
The steps mentioned above are explained briefly here and then in
greater detail throughout this manual. You must complete the steps for
the adapter to work with DeviceNet masters (e.g., 1756-DNB) on the
primary network and Subnet modules.
POINT I/O modules
Module
Status
DeviceNet
63
Status
DeviceBus
Status
1734-ADN
1734-EP24DC
System
Power
Field
Power
42407
1. Set Subnet/Backplane Baudrate
2. Set Subnet I/O Module Addresses
3. Configure the Subnet I/O
4. Configure the Primary DeviceNet Network
Publication 1734-UM002C-EN-P - July 2003
What is the 1734-ADN(X) Adapter? 2-3
Set Subnet/Backplane Baudrate
The adapter and Subnet modules must use the same baudrate to
communicate with each other. Use one or both of the following to set
a Subnet baudrate.
• Enable or disable the Backplane Autobaud feature for POINT
I/O modules. POINT I/O modules have Autobaud enabled as
the default- See page
• Set the adapter baudrate for the Subnet. The default for the
1734-ADN is 1Mbaud. The default for the 1734-ADNX is
125Kbaud - See page
2-12.
2-9.
IMPORTANT
You set the backplane baudrate for the 1734-ADN.
You set the Subnet baudrate for the 1734-ADNX.
Set Subnet I/O Module Addresses
Once the adapter and POINT I/O modules are communicating at the
same rate on the backplane, you must make sure all modules use a
valid MAC ID.
Set the Auto Address feature for POINT I/O modules - See
page 2-13.
Publication 1734-UM002C-EN-P - July 2003
2-4 What is the 1734-ADN(X) Adapter?
Configure the Subnet I/O
In the first two steps, you set a consistent communication rate and
made sure each module uses address for communication. Next you
must configure the PointBus (e.g., set scan list).
You can configure the PointBus using one of two methods: Auto Start
Mode (ASM) or manually. For more information on configuring the
PointBus using ASM, see Chapter 3 or see Chapter 4 for manual
configuration.
Configure the Primary DeviceNet Network
Finally, you must configure the adapter for communication with a
master (e.g., 1756-DNB).
For more information on configuring the DeviceNet network, see
Chapter 5,
Scanlist.
Adding the 1734-ADN(X) to the DeviceNet Scanner’s
You must understand all of the adapter’s features to effectively use it
in your POINT I/O system. Keep these four steps in mind as you read
this manual:
1. Set Subnet Baudrate
2. Set Subnet I/O Module Addresses
3. Configure the Adapter’s Scanlist
4. Configure the Primary DeviceNet Network
Publication 1734-UM002C-EN-P - July 2003
What is the 1734-ADN(X) Adapter? 2-5
Remove and Reinsert Modules on the Backplane
POINT I/O modules can easily be removed and reinserted on the
1734-ADN(X) backplane. If the removal and reinsertion is not done
with caution, you can affect the adapter’s operations and,
consequently, the entire POINT I/O application.
If you must remove and reinsert modules, we recommend the
following:
• Do not move I/O modules to different locations on the DIN rail
after they have been installed and configured.
• Always place modules with the matching Removable Terminal
Block.
• If adjacent modules (i.e., 2 or more) are removed from the
backplane, replace all of them before attempting to operate the
POINT I/O system. Input data will hold last state until all
previously-removed modules are replaced.
IMPORTANT
The 1734-ADN(X) can only detect the location of
POINT I/O modules residing on the 1734-ADN(X)
backplane. It is the user’s responsibility to maintain
all non-backplane devices, including POINT I/O
modules attached to the Subnet with a 1734-PDN
adapter.
– If adjacent modules are removed and all but one is returned,
the adapter cannot verify the location of the returned
modules. For example, if modules are removed from nodes 3
and 4 and only the module from node 4 is returned, the
adapter cannot verify the location. In this case, the adapter
alerts you (via RSNetWorx for DeviceNet) that it cannot verify
the presence of modules in the affected locations. I/O data
will not be exchanged with this node until both modules have
been reinserted.
– If modules of different types are removed and returned to
the wrong locations, the adapter identifies the returned
modules and alerts you (via RSNetWorx for DeviceNet) that
the error has occurred and must be corrected.
Publication 1734-UM002C-EN-P - July 2003
2-6 What is the 1734-ADN(X) Adapter?
– If modules of the same type are removed and returned to the
wrong locations, the adapter identifies the returned modules,
updates their MAC IDs and continues operation.
IMPORTANT
IMPORTANT
The removal and return scenario exists whether the
system is under power or not. If the system is under
power, the scenario arises immediately. If the system
is not under power, the scenario arises in the next
power cycle.
Also, the example above shows removal of two
adjacent modules. The scenario described exists
anytime 2 or more adjacent modules are removed
and not all are returned.
Care must be taken when replacing backplane I/O
modules. Each I/O module stores its configuration
parameters in internal non-volatile memory. You
must either enable ADR for all modules or manually
configure each module in a non-manufacturing
environment when the module is being replaced or
placed on the network for the first time. Failure to do
so could result in inadvertent control attributed to
different configuration settings.
Understanding the
DeviceNet Network
and Subnet
DeviceNet Network
Your adapter serves as a slave to DeviceNet masters. The adapter
receives data from and returns data to the master through the
following I/O connections:
• Change of State (COS)
• Cyclic
• Polled
• Strobe
Subnet Network
On the Subnet, your adapter acts as a scanner and is the master of the
Subnet modules. The adapter performs the following functions:
• Exchanges I/O data with devices on Subnet
Publication 1734-UM002C-EN-P - July 2003
What is the 1734-ADN(X) Adapter? 2-7
• Collects I/O data from the Subnet and sends it to devices on the
DeviceNet network (e.g., scanners or controllers)
• Supplies power to the backplane I/O modules (See Appendix A
for power supply rules regarding I/O modules power
requirements.)
Data Collection
The adapter collects I/O data from up to 63 modules via the Subnet.
The I/O modules appear on the primary DeviceNet network as a
single node, though, and require only one DeviceNet node address.
IMPORTANT
If Automatic Device Replacement (ADR) is enabled
on the adapter, you can only connect up to 62
modules via the Subnet.
For more information on ADR, see page 2-15.
Module Power
The adapter supplies 5V logic power to POINT I/O modules by
converting 24V dc field power to PointBus 5V power.
You can connect up to 63 I/O modules to each adapter, and you can
power to the backplane I/O modules from the adapter (with a
maximum of 10A of field power). You may use the integrated, isolated
24V dc expansion power unit (1734-EP24DC) to power additional I/O
modules, as shown below.
1734-ADN adapter12 POINT I/O modules
Adapter
Status
Network
63
Status
Subnet
Status
1734-ADNX
System
Power
Field
Power
1734-EP24DC expansion power unit
1734-EP24DC
System
Power
Field
Power
31114-M
Publication 1734-UM002C-EN-P - July 2003
2-8 What is the 1734-ADN(X) Adapter?
For more information on the 1734-EP24DC expansion power unit, see:
• POINT I/O Technical Data, publication 1734-TD002
• POINT I/O 24V dc Expansion Power Supply Installation
Instructions, publication 1734-IN058
Adapter Features
Your adapter uses the following features on both the DeviceNet
network and the PointBus:
• Self-Test
• Field Upgradable Firmware
• Fully Software Configurable
• Connections
• Baudrates
Self-Test
On power-up, the adapter performs a self-test. The adapter tests
various internal and programmatic memories and checks the status
indicators (LEDs).
Field Upgradable Firmware
You can update the adapter’s firmware with the ControlFlash Utility
software. This feature lets you always use the most current application
code.
Publication 1734-UM002C-EN-P - July 2003
Fully Software Configurable
The adapter is fully software configurable using RSNetWorx for
DeviceNet. You must configure the adapter for use with a DeviceNet
master (e.g., 1756-DNB) and separately for use with Subnet devices.
For more information on how to configure your adapter for use with a
DeviceNet master, see Chapter 5.
For more information on how to configure your adapter for use with
Subnet modules, see Chapter 4,
Adapter’s SubNet.
Configuring the 1734-ADN(X)
What is the 1734-ADN(X) Adapter? 2-9
Connections
Your adapter supports the following connections on both the primary
DeviceNet network and Subnet:
• I/O connections:
– Polled
– Strobe
– Cyclic
– COS
• Explicit connections
You can use I/O mapping to determine the data contained in each
connection.
The adapter supports Master/Slave connection types on the
DeviceNet network. On the Subnet, the adapter functions as a
scanner device, exchanging data with I/O modules.
Baudrates
Choose baudrates for the adapter in the RSNetWorx for DeviceNet
software. It supports these rates:
• 125Kbaud
• 250Kbaud
• 500Kbaud
• Autobaud - The adapter detects the primary DeviceNet network
baudrate and automatically sets its own baudrate to match
the network.
• For the 1734-ADN, the PointBus can be configured to operate at
1Mbaud (1000Kbaud).
Auto Start Mode
Auto Start Mode lets you easily get your adapter installed and
operating. In this mode, the adapter’s configurable features operate as
they were most recently configured. For example, if Autobaud on
DeviceNet was enabled in the adapter’s last configuration, it will be
enabled when Auto Start Mode is used.
For a more detailed explanation of how to use Auto Start Mode, see
Chapter 3.
Publication 1734-UM002C-EN-P - July 2003
2-10 What is the 1734-ADN(X) Adapter?
Auto Catalog Replace
Auto Catalog Replace corrects errors that might occur when backplane
modules of the same type are removed and replaced in the wrong
location. If modules of the same type are removed and returned to
the wrong locations, the adapter identifies the returned modules,
updates their MAC IDs and continues operation.
IMPORTANT
IMPORTANT
IMPORTANT
If modules of different types are removed and
returned to the wrong locations, the adapter
identifies the returned modules and alerts you (via
RSNetWorx for DeviceNet, the Node Status Table,
and the Faulted Node Table) that the error has
occurred and must be corrected.
The removal and return scenario exists whether the
system is under power or not. If the system is under
power, the scenario arises immediately. If the system
is not under power, the scenario arises in the next
power cycle.
Also, the example above shows removal of two
adjacent modules. The scenario described exists
anytime 2 or more adjacent modules are removed
and not all are returned.
Care must be taken when replacing backplane I/O
modules. Each I/O module stores its configuration
parameters in internal non-volatile memory. You
must either enable ADR for all modules or manually
configure each module in a non-manufacturing
environment when the module is being replaced or
placed on the network for the first time. Failure to do
so could result in inadvertent control attributed to
different configuration settings.
Publication 1734-UM002C-EN-P - July 2003
Backplane (1734-ADN)/Subnet (1734-ADNX) Baudrate
EDS parameter Backplane Baudrate is accessible from the primary
DeviceNet and sets a specific baudrate for all backplane I/O modules.
Loading...
+ 106 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.