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

Publication 1738-UM001A-EN-P - February 2005
3-8 Use Auto Start Mode
• Check that MACIDs are set to proper values
• Check scanlist
– browse to Subnet and view scanlist, or look at mapping text
– Make sure the scanlist was saved (if not, investigate why?)
– If you are using the 1738-ADNX adapter, check the
Max(imum) Backplane MACID parameter. It should equal the
number of modules residing on the backplane.
After ASM has completed (that is, Physical List Acquire Status
field is Idle), verify that the operation was successful and that
each I/O module was added to the adapter’s scanlist. The
PointBus Status LED should be solid green. This indicates only
that the adapter is able to establish I/O connections with each
module in its scanlist, not that each module on the Subnet was
successfully added to its scanlist.
To verify the presence of each module in the adapter’s scanlist,
perform one of the following checks:
• Each I/O module’s NET LED should be solid green. If the
device has neither LED, use one of the following methods.
– By browsing to the Subnet and uploading the adapter’s
scanlist using RSNetWorx for DeviceNet and verifying that the
device is found in the scanlist.
– By repeatedly uploading the EDS parameter Cycling I/O
Mapping to verify that a mapping for the concerned module
exists. See page 2-15 for more information about this
parameter.
If one of the following is observed, it is likely that one of the
Subnet modules has been addressed incorrectly or is
configured to communicate at the wrong baud rate.
• The adapter’s PointBus Status LED is solid or blinking red
• An I/O module’s NET LED is solid red
• It appears that the adapter has not saved a scanlist