Rockwell Automation 1769-ADN DeviceNet Modules Installation Instructions - Manuel (Page 61)

Rockwell Automation Publication DNET-IN001B-EN-P - January 2012 61
1769 DeviceNet Modules Status Indicators and Data Structures Appendix B
1769-SDN Scanner Status
Codes The 1769-SDN scanner has a 2-character numeric display that provides the
DeviceNet node address and diagnostic information about the status of the
module.
Numeric Display Description
0…63 Indicates the 1769-SDN module’s DeviceNet node address.
70…99 Indicates a status code for the displayed node address.
Alternating numbers • 0…63—Indicates the node number that has generated an
error.
• 70…99—Indicates the status code.
Numeric Display
Table 14 - Status Codes
Status Code Description Recommended Action
0…63 Indicates the scanner’s DeviceNet node address. None.
65 The AutoScan option is on and the device is in Idle mode. None.
67 The scanner is the secondary scanner. None.
68 The primary scanner has detected no secondary scanner. Configure another scanner to be the secondary scanner.
69 The primary and secondary configurations are mismatched. Check configuration of the secondary scanner.
70 The address of the device is already in use by another device
on the network. The scanner failed the duplicate node address
check. Change the address of the device to an unused address.
71 There is invalid data in the scan list. Use RSNetWorx for DeviceNet software to reconfigure the
scan list.
72 The slave device stopped communicating. If the slave device
does not recover communication during the next scan, the
status code changes to 78. Verify the slave device’s power and communication
connections.
If the slave device is polled, verify that the interscan delay
time is adequate for the device to return data.
73 The slave device’s identity information does not match the
electronic key in the scanner. • Make sure that the correct device is connected at this
address.
• Make sure that the device matches the specified electronic
key, such as vendor, product code, or product type.
74 The scanner detected a data overrun on the DeviceNet
communication port. • Modify your configuration and check for invalid data.
• Check network communication traffic.
75 Either or both of these may be true:
• The device does not have a scan list.
• The device has not received communication from any other
device.
Verify that the device has the following:
• A configured scan list
• A properly-wired connection to the network
76 There is no direct network traffic for the scanner. The scanner
hears other network communication but does not hear any
communication directed to it. None.