Allen-Bradley 1769-SDN, Installation Instructions Manual, Page: 62 / 68

62 Rockwell Automation Publication DNET-IN001B-EN-P - January 2012
Appendix B 1769 DeviceNet Modules Status Indicators and Data Structures
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. To run the network, do these steps.
1. Put the controller in Run or Remote Run mode using the
keyswitch on the controller or through RSLogix5000
software.
2. Turn on the bit O.CommandRegister and run for the scanner.
81 The controller has set the scanner to the Faulted mode. The
Command bit also indicates a DeviceNet network fault state. The Bit O.CommandRegister.Fault for the scanner is on.
Correct the condition that caused the controller to set this bit
and then turn this bit off.
82 An error was detected in a sequence of fragmented I/O
messages from the device. Use RSNetWorx for DeviceNet software to do the following:
• Check the scan list of the device to make sure that its input
and output data sizes are correct.
• Check the configuration of the device.
83 The device returns error responses when the scanner attempts
to communicate with it. Use RSNetWorx for DeviceNet software to do the following:
• Check the accuracy of the scan list.
• Check the configuration of the device. The device may be in
another scanner’s scan list.
• Use the slave device’s documentation to verify that the
device supports the message type used by the scanner.
If the device’s message type does not match the scanner’s,
then use RSNetWorx for DeviceNet software to access the
scanner’s scan list and change the scanner’s message type
to one that is compatible with the slave device.
• Cycle power to the device.
84 The scanner is initializing the DeviceNet network. None. This code clears itself once the scanner attempts to
initialize all the devices on the network.
85 During runtime, the data size sent by the slave device does not
match the size in the corresponding scan list entry. Since variable length poll data is not supported, verify that the
slave device is functioning properly.
86 The device is in Idle mode, or not producing data, while the
scanner is in Run mode. • Check the configuration and status of the device.
• If you set up an interlock between two scanners
(controllers), make sure both scanners are in Run mode.
87 The scanner cannot listen to shared inputs from the slave
device because the owning scanner has not established
communication with that slave device. • Verify the primary scanner connection and configuration.
• Verify that the slave device is producing data.
88 The scanner cannot listen to shared inputs from the slave
device because I/O parameters, such as electronic key or data
size, for that slave device are configured differently between
this scanner and the owning scanner. In this scanner, reconfigure the I/O parameters for the shared
inputs scan list entry so that they match those same
parameters in the owning scanner.
Table 14 - Status Codes
Status Code Description Recommended Action