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

Publication 1738-UM001A-EN-P - February 2005
Use Auto Start Mode 3-9
Use the following procedures to attempt to remedy a problem:
• Verify that each non-backplane module’s address and
baudrate have been set correctly.
• Verify that each backplane module is configured to autobaud.
The adapter’s EDS parameter Set Backplane Autobaud can be
used to set each module’s autobaud parameter. It is necessary
to cycle a module’s power before the autobaud parameter
change takes effect. In rare situations, it may be necessary to
download the parameter and cycle power several times
before each backplane module’s autobaud parameter has
been changed.
Note that if the adapter is configured to autobaud on the
primary DeviceNet network, network traffic on the primary
network is required before the backplane modules will attempt
to communicate. For this reason, it is sometimes helpful to have
RSLinx continuously browsing the primary network while
attempting the ASM process and verification.
When it is believed that each non-backplane module is correctly
configured and that each backplane module is able to
communicate on the Subnet, the ASM process can be attempted
again.
After successfully configuring your adapter with the Auto Start Mode
feature, the adapter must still be added to the primary DeviceNet
network scanner’s scanlist. See Chapter 5 for more information.
Use Custom Configuration The Auto Start Mode is recommended to quickly and easily get your
ArmorPoint I/O system ‘up and running’. But this mode does not
prevent you from changing the adapter’s default configuration after
system operation has begun.
For more information on how to write custom configuration for your
adapter on DeviceNet, see Chapter 4, Configure the DeviceNet
Scanner Subnet and Chapter 5, Add the ArmorPoint DeviceNet
Adapter to the DeviceNet Scanner’s Scanlist.
IMPORTANT
The adapter’s ADR configuration for the Subnet
modules is reset when you run Auto Start Mode.