Rockwell Automation 57C650 AutoMax Programming Executive Version 3.8 - Manual (Page 233)

BĆ3 Processor Module Error and Status Codes
13 Runbase boot error
Ć a check on the runbase failed
14 Processor overlap limit exceeded
Ć ran out of processing capacity (time)
15 External watchdog timeĆout detected
Ć another Processor in the same rack stopped
17 Address error detected
Ć caused by a read/write to an invalid address
18 Spurious interrupt or hardware failure
19 Power failure detected
1A Watchdog on this Processor failed
1b Hardware event count limit exceeded
Ć too many interrupts set without being
acknowledged
Ć program too long
Ć collective scans too fast
1C Illegal instruction detected
Ć runbase software fault
Ć bad processor module
Ć bad EPROMs
1d Privilege violation detected
Ć runbase software fault
Ć bad processor module
1E UnĆimplemented instruction detected
Ć runbase software fault
Ć bad processor module
1F Illegal interrupt detected
Ć runbase software fault
Ć bad processor module
31 Bus error
Ć attempt to access invalid address
32 Define channel error
Ć problem in application software
33 Define scan error
Ć hardware fault
34 Memory integrity lost
Ć hardware fault
35 DC drive CML block initialization error
36 Communication between drive Processor and I/O
controller lost
37 DC drive I/O controller runĆtime board error
Ć hardware fault
38 UDC module generated a STOP ALL
39 UDC module interrupt allocation failed
3A Processor OS incompatible with UDC OS
Corrective action: correct the problem in application software. Try to reset by
cycling power and reĆloading configuration and application tasks. Replace the
Processor module. For error code 31, see JĆ3650; for error code 37, see JĆ3669.
For error code 17: If you define bits in a register that is also defined as a register,
neither the bits nor the register can be forced. For error code 38, examine the
error logs for all UDC tasks in the rack. Error code 38 can be caused by enabling
CCLK on more than one module in the rack. Verify that CCLK is enabled on only
one module in the rack. For error code 39, cycle power to the rack and reĆload
the configuration and application tasks. For error code 3A, check OS
compatibility.