Rockwell Automation GMLC Reference Manual - Manual (Page 583)

Publication GMLC-5.2 - November 1999
546 Fault Variables
Failed Getting Data
An RIO failed getting data fault (RIO_fault_code = 3) indicates that the
motion controller’s RIO adapter received a block or discrete transfer from
the scanner, but the expected data was not present. Although this fault
does not directly cause a global fault, if the condition persists another
more serious RIO fault occurs.
Failed BTW Request
An RIO failed BTW request (RIO_fault_code = 2) indicates that the
motion controller’s RIO adapter could not be enabled to receive a block
transfer write from the scanner. This may be caused by improper BT
interlocking or logic in the PLC causing block transfers to be sent to the
motion controller in the wrong sequence. While this fault does not
directly cause a global fault, if the condition persists another more serious
RIO fault occurs. See Using the Remote I/O Adapter chapter for
information on proper block transfer interlocking.
Failed Sending BTR
An RIO failed sending BTR (RIO_fault_code = 1) indicates that the
motion controller’s RIO adapter could not be enabled to receive a block
transfer read from the scanner. This is usually caused by improper BT
interlocking or logic in the PLC causing block transfers to be sent to the
motion controller in the wrong sequence. While this fault does not
directly cause a global fault, if the condition persists another more serious
RIO fault undoubtedly occurs. See Using the Remote I/O Adapter chapter
for information on proper block transfer interlocking.
CNET Fault Code
CNET_fault_code is an integer value representing the most recent CNET
fault condition, as shown below. This variable applies only to the 1394
Turbo controllers.
Fault Code Fault Condition LED
4 Plug Fault Solid Red
3 Media Fault Flashing Red