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

Rockwell Automation Publication DNET-IN001B-EN-P - January 2012 49
1756 DeviceNet Status Indicators and Data Structures Appendix A
Status Codes
This table summarizes the DeviceNet status codes that appear on the
alphanumeric display.
Table 7 - 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 the following 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.
77 During initialization, the data size expected by the device does
not match the scan list entry. Use RSNetWorx for DeviceNet software to check the slave
device and the scan list for the correct input and output sizes
for the slave device.
78 The device is configured in the scan list, but not
communicating. The device has failed to communicate during
the scanner’s second scan, which followed the display of
status error code 72. Verify device’s power and communication connections.
If the device is polled, make sure the interscan delay is long
enough for the device to return its data.
If necessary, use RSNetWorx for DeviceNet software to do the
following:
• Add the device to the DeviceNet network.
• Delete the device from scanner’s scan list.
• Inhibit the device in the scanner’s scan list.
79 The scanner has failed to transmit a message. The error status
usually displays after the duplicate node check completes and
power is applied to the module. • Make sure the scanner is connected to a valid network.
• Check for disconnected cables.
• Verify the network communication rate.
80 The scanner is in Idle mode. • Put the controller in Run or Remote Run mode by using the
keyswitch on the controller or through RSLogix 5000
software.
• Turn on the bit O.CommandRegister and run for the scanner.