Rockwell Automation GMLC Reference Manual - Manual (Page 589)

Publication GMLC-5.2 - November 1999
552 Fault Variables
Response Timeout
A response timeout fault (DH485_fault_code = 3) indicates that a
message was successfully sent to the remote device, but no response was
received from the remote device within the timeout period. The timeout
period is approximately one second per valid network node address. For
example, if all 31 DH-485 nodes are used, the timeout period is about 31
seconds. Verify that the remote device is operating properly.
Transaction ID Mismatch
A transaction ID mismatch fault (DH485_fault_code = 2) indicates that a
message was successfully sent to the remote device, but that the
transaction ID of the received response was not the same as that of the
sent message. This error occurs when messages and responses get out of
sequence on the DH-485 network (the motion controller received the
response from another device’s message). This condition is most often
due to heavy network traffic combined with a slow response remote
device.
Bad Command
A bad command fault (DH485_fault_code = 1) indicates that the message
was not sent to the remote device. This fault is most often caused by
improper message syntax, sending a message with the motion controller
disconnected from the DH-485 network, or attempting to send a message
before the previous one has completed or timed out.
DSP Feedback Fault 1394
A DSP feedback fault occurs when the 1394 motion controller fails to
communicate to the DSP subsystem, which interfaces with the 1394 axis
modules. This fault indicates a hardware problem with the control board
in the system module.
After the underlying problem has been detected and remedied, clear this
fault with a Reset Fault block set to Reset 1394, or by pressing the
controller Reset button.
In the Tag Explorer select General System Variables, then select
DSP_feedback_fault_1394 in the Tag Window.