Rockwell Automation 1746-BAS-T SLC 500 Basic Basic-T Modules - Manual (Page 70)

Publication 1746-UM004B-EN-P - December 2005
4-22 Programming Overview
Application errors such as divide by zero error, syntax error, receipt of
a CONTROL-C, and execution of STOP or END statements cause the
module to return to the Command mode from Run mode. Use CALL
38 (EXPANDED ONERR) to jump to an interrupt routine instead of
returning to the Command mode.
5AH Hardware interrupt
problem. Module hardware problem. Verify that the module
slot is enabled. Cycle
power to the module to
re-initialize parameters
and re-run the program.
Module internal stacks,
pointers (if XBY instructions
are used) are corrupted by the
user program.
5BH G file configuration error. Module is trying to be
configured using G files. Verify the module is not
configured with G files.
5CH M0/M1 file configuration
error. Wrong M0/M1 file size is
chosen. Verify the module is
configured with M0 or
M1 files no larger than
64 words.
5DH Interrupt requested but
the processor will not
support the interrupt. SLC 500 fixed controller or
5/01 modular processor does
not support module
interrupts. A 5/02 or higher
processor must be used
for interrupt capability.
75H Module watchdog
timeout. Module hardware problem. Cycle power to the
module to re-initialize
parameters and re-run
the program.
Module internal stacks,
pointers (if XBY instructions
are used) are corrupted by the
user program.
90H Module issued an
interrupt while the slot
was disabled. Module is issuing an I/O
interrupt. CALL 26 causes this
interrupt. Enable the slot before
using interrupts.
91H Module has faulted while
slot was disabled. Module hardware problem. Cycle power to the
module to re-initialize
parameters and re-run
the program.
Module internal stacks,
pointers (if XBY instructions
are used) are corrupted by the
user program.
92H Module I/O or ISR
configuration is incorrect. Module slot was configured
incorrectly in the SLC ladder
logic program. Verify the slot
configuration for the
module.
93H Processor did not
recognize the error code
from the Module. Module hardware problem. Cycle power to the
module to re-initialize
parameters and re-run
the program.
Module internal stacks,
pointers (if XBY instructions
are used) are corrupted by the
user program.
SLC
Fault
Code Description Possible Cause Recommended Action