f fg gd df f

C Ch ha an ng gi in ng g t th he e c co on nf fi ig gu ur ra at ti io on n o of f a a D De ev vi ic ce eN Ne et t A Ad da ap pt te er r

Page 1 of 3

Problem Description
There are many DeviceNet devices that can be configured over the network using
RSNetworx for DeviceNet software. There are also many devices within this group
whose behavior on the network can be changed through this configuration. The most
common configuration change, of this type, is to modify the Input and Output Assembly
sizes, which also changes the transmit and/or receive size of the data being sent to/from
the scanner. The 1769-ADN and 1794-ADN are classic examples of this behavior (1798-
ADN, 1734-ADN also exhibit this), in that as modules are configured into or out of an IO
rack containing these adapters, the IO assemblies and data sizes will change
automatically.
Under normal conditions and with no IO connection established to a scanner from
a device, configuration changes can be made and downloaded to the devices without an
issue. The problem comes when one of these devices has been configured and an active
scan list entry in a scanner exists and the scanner is actively exchanging IO data with the
device. Modifying the configuration in the software and then attempting to download the
changes can cause an Object State Conflict error to appear in the software. Not all
devices limit configuration changes with an active IO connection. It is purely a behavior
designed into a device and varies from device to device.
Solution
If an active IO connection exists between a scanner and a device, it may be
necessary to break that connection, before downloading the configuration. The easiest
way to do this is to disconnect the scanner from the network and the Network LED on the
slave device should blink green. This will not work however if you are bridging through
the scanner to the network to do the configuration. The next alternative is to disable or
remove the scan list entry for the device, within the scanner, using RSNetworx for DNet.
Note: If device configuration was done that changed the data sizes of a device and the
scan list is not modified to reflect these changes, the scanner will of course still blink the
infamous error 77 meaning that the data sizes dont match. It will then be necessary to
modify the scan list entry for the device to the correct sizes, modify the mapping of the
f fg gd df f
C Ch ha an ng gi in ng g t th he e c co on nf fi ig gu ur ra at ti io on n o of f a a D De ev vi ic ce eN Ne et t A Ad da ap pt te er r

Page 2 of 3

data to/from the IO datatable of the scanner and download the new scan list to the
scanner.
Procedure

This document will explain the procedure on changing the I/O size or
configuration of a DeviceNet Adapter that has been mapped to a DeviceNet
Scanner.

These devices will include the 1794-ADN, 1798-ADN, 1734-ADN and 1769-ADN.

Problems encountered when trying to modify Adapters configuration:

Communication error 12. Error response received. Object state conflict. General error code.

Getting error 77 when trying to use the new I/O size expected.



Here are the basic steps needed to establish communications:

1.) Remove the Adapter from any scan lists.

The adapters will not save a configuration as long as a scanner is communicating with it.
Remove the adapter from scanlist and save. Make note where the adapter is mapped in your
scanner just in case you need to map it back to the same location in a data table. Usually when
you make changes or add modules the I/O size will change anyway.

Mod/Net and I/O Status will be flashing green.


2.) Remove the DeviceNet cable or connector from the Adapter.

Mod/Net and I/O Status will be flashing green.


3.) Cycle the Auxiliary power that is powering the Adapter.

This will reset the adapter so we can re-establish communication.
Mod/Net Status Indicator: OFF, No power or no network access.


4.) Connect the Adapter back on to the Network.

After cycling power the Mod/Net Status Indicator should be Flashing Green. ( On-line but not
connected ). If not then try the Clear/Reset Memory & Upload to get the Mod/Net Status
Indicator to flash green. Physically adding modules after power was restored will work also.

I/O Status Indicator: OFF, No power or Outputs off.



f fg gd df f
C Ch ha an ng gi in ng g t th he e c co on nf fi ig gu ur ra at ti io on n o of f a a D De ev vi ic ce eN Ne et t A Ad da ap pt te er r

Page 3 of 3



5.) In RSNetWorx for DeviceNet, right click and upload from the Adapter.

Now you will be able to make changes to the modules in the Adapter. Before this if you would of
uploaded from the Adapter and the module settings would not have been saved. The
RSNetWorx software does not indicate a successful save to the ADN. The only way to verify a
successful save is to upload from the Adapter and see if the changes were made.
Note: Save or Apply one modules configuration at a time. (Slot 0 to Slot X).


6.) Once the Adapter has been configured, now it can be added back into the
scanlist.

Prior to mapping the Mod/Net Status Indicator: Flashing Green, On-line but not connected.
When mapped the Mod/Net Indicator will be Solid Green, On-line, link okay, connected.
I/O Status Indicator will be Solid Green, Device operational - outputs live - run. (Scanner in RUN
mode).