S e r v i c e B u l l e t i n SLC -500 Error Codes

Address S:5 C l a s s i f i c a t i o n

2002-4 27 March 2002

5/02 5/03 5/04 5/05

Description
Minor Error Bits The bits of this word are set by the processor to indicate that a minor error has occurred in your ladder program. Minor errors, bits 0 to 7, revert to major error 0020H if any bit is detected as being set at the end of the scan. HHT users: If the processor faults for error code 0020H, you must clear minor error bits S:5/07 along with S:1/13 to attempt error recovery.

Fixed 5/01

S:5/0

Dynamic Config

Overflow Trap Bit When this bit is set by the processor, it indicates that a mathematical overflow has occurred in the ladder program. See S:0/1 for more information. If this bit is ever set upon execution of the END, TND, or REF instruction, major error (0020) will be declared. To avoid this type of major error from occurring, examine the state of this bit following a math instruction (ADD, SUB, MUL, DIV, DDV, NEG, SCL, TOD, or FRD), take appropriate action, and then clear bit S:5/0 using an OTU instruction with S:5/0 or a CLR instruction with S:5. Reserved Control Register Error Bit The LFU, LFL, FFU, FFL, BSL, BSR, SQO, SQC, and SQL instructions are capable of generating this error. When bit S:5/2 is set, it indicates that the error bit of the control instruction has been set. If this bit is ever set upon execution of the END, TND, or REF instruction, major error (0020) will be declared. To avoid this type of major error from occurring, examine the state of this bit following a control register instruction, take appropriate action, and then clear bit S:5/2 using an OTU instruction with S:5/2 or a CLR instruction with S:5.

S:5/1 S:5/2

NA

Dynamic config

Sb 02-4 Page 1 of 12

Address S:5/3

C l a s s i f i c a t i o n Dynamic Config

Description
Major Error Detected while Executing User Fault Routine Bit When set, the major error code (S:6) represents the major error that occurred while processing the fault routine due to another major error. If this bit is ever set upon ececution of the END, TND, or REF instruction, major error (0020) will be declared. To avoid this type of major error from occurring, examine the state of this bit inside your fault routine, take appropriate action, and then clear bit S:5/3 using an OTU instruction with S:5/3 or a CLR instruction with S:5. Application example: Suppose you are executing your fault routine for a fault code 0016H Startup Protection. At rung 3 inside this fault routine, a TON containing a negative preset is executed. When rung 4 is executed, fault code 0016H is overwritten to indicated code 0034H, and S:5/3 is set. If your fault routine did not determine that S:5/3 was set, major error 0020H would be declared at the end of the first scan. To avoid this problem, examine S:5/3, followed by S:6, prior to retruning from your fault routine. If S:5/3 is set, take appropriate action to remedy the fault, then clear S:5/3. M0-M1 Referenced on Disabled Slot Bit This bit is set whenever any instruction references an M0 or M1 module file element for a slot that is disabled (via its I/O slot enable bit). When set, the bit indicates that an instruction could not execute properly due to the unavailability of the addressed or M0 or M1 data. If this bit is ever set upon execution of the END, TND, or REF instruction, major error (0020) is declared. To avoid this type of major error from occurring, examine the state of this bit following a M0-M1 referenced instruction, take appropriate action, and then clear bit S:5/ 4 using and OTU instruction with S:5/4 or a CLR instruction with S:5. Reserved Reserved for minor errors that revert to major errors at the end of the scan.

Fixed 5/01

5/02

5/03

5/04

5/05

S:5/4

Dynamic Config

S:5/5 to S:5/7

NA

Sb02-4 Page 2 of 12

Address S:5/8

C l a s s i f i c a t i o n Status

Description
Memory Module Boot Bit When this bit is set by the processor, it indicates that a memory module program has been transferred to the processor. This bit is not cleared by the processor. Your program can examine the state of this bit on entry into the REM Run mode to determine if the memory module content has been transferred. Bit S:1/15 will be set to indicate REM Run mode entry. This information is useful when you have an application that contains retentive data and a memory module that has only bit S:1/10 set (Load Memory Module on Memory error). Use this bit to indicate that retentive data has been lost. This bit is also helpful when using bits S:1/11 (Load Memory Module Always) or S:1/12 (Load Memory Module Always and Run) to distinguish a power up REM Run mode entry from a REM Program (or REM Test) mode to REM run mode entry. Memory Module Password Mismatch Bit This bit is set on REM Run mode entry, whenever loading from the memory module is specified (word 1, bits 11 or 12) and the processor user program is password protected, and the memory module program does not match that password. Use this bit to inform your application program that an autoloading memory module is installed but did not load due to password mismatch. STI (Selectable Timed Interrupt) Overflow Bit This bit is set whenever the STI timer expires while the STI routine is either executing or disabled and the pending bit is already set. Battery Low Bit This bit is set whenever the Batter Low LED is on. The bit is cleared when the Battery Low LED is off. Discrete Input Interrupt Overflow Bit This bit is set whenever the DII interrupt occurs while still executing the DII subroutine or whenever the DII interrupt occurs whild pending or disabled.

Fixed 5/01

5/02

5/03

5/04

5/05

Status

S:5/10

Status

S:5/11

Status

S:5/12

Status

Sb 02-4 Page 3 of 12

Address S:5/13

C l a s s i f i c a t i o n Dynamic Config

Description
Unsuccessful Operating System Load Was Attempted This bit is set whenever an operating system memory module loade is attempted and is unsuccessful. Unsuccessful loads can occur when either the protection jumper is in the protect position or is missing, or if the operating system memory moduleis incompatible with the SLC 5/03, SLC 5/ 04, or SLC 5/05 processors hardware platform. Examine the state of this bit with your user program to diagnose this condition. Channel 0 Modem Lost This bit indicates the status of the modem connected to Channel 0 (RS232 serial port). The state of the bit is determined by: the protocol Channel 0 is configured for the Control Line selected the states of DCD (Data Carrier Detect) and DSR (Data Set Ready). If the bit is set, then the modem is not properly connected to Channel 0 or it is in a state where unreliable communication exchanges may take place via Channel 0. The following conditions apply: If Channel o is disabled or configured for DH485, the bit is always cleared. If Channel 0 is configured for one of the DF-1 protocols in System Mode or Generic ASCII in User Mode, then the Control Line selection determines how DCD and DSR affect the modem status: -If Control Line=NO HANDSHAKING: The bit is always set -If Control Line=FULL-DUPLEX or HALFDUPLEX WITHOUR CONTINUOUS CARRIER: The bit is set if DSR goes inactive and cleared when DSR goes active. (DCD has no affect on modem status in this case). -If Control Line=HALF-DUPLEX WITH CONTINUOUS CARRIER: The bit is set is either DSR goes inactive or DCD remaine inactive for more than 10 seconds. This bit is cleared when both DSR and DCD go active.

Fixed 5/01

5/02

5/03

5/04

5/05

S:5/14

Status

Sb02-4 Page 4 of 12

Address S:5/15

C l a s s i f i c a t i o n Status

Description
ASCII String Manipulation Error This bit applies to SLC5/03 (OS301and higher), SLC 5/04, and SLC 5/05 processors. This bit is set to 1 when an attempt is made to process a string using an ASCII instruction that exceeds 82 characters in length. Major Error Fault Code A hexadecimal code is entered in this word by the processor when a major error is declared. Refer to S:1/13. The code defines the type of fault, as indicated on the following pages. This word is not cleared by the processor Error codes are presented, stored and displayed in a hexadecimal format. Refer to appendix G for more information on the hexadecimal numbering system. If you enter a fault code as a parameter in an instruction in your ladder program, you must convert the code to decimal. For example, if you program an EQU instruction to go true when the error 0016 occurs, enter S:6 as source A and 22, the decimal equivalent of 0016H, as source B:

Fixed 5/01

5/02

5/03

5/04

5/05

S:6

Status

Application Example: You can declare your own application specific major fault by writing a unique value to S:6 and then setting bit S:1/13. SLC 5/02 processor users: Interrogate the value of S:6 in your fault routine to determine the type of fault that occured. If your program was saved with the test single step enabled, you can also interrogate S:20 and S:21 to pinpoint the exact rung that was executing when the fault occurred. Fault Classifications: Faults are classified as Non-User, NonRecoverable, and Recoverable. Non-User Fault The fault routine does not execute. Non-Recoverable User Fault The fault routine executes for 1 pass. (You may initiate a MSG instruction to another node to identify the fault condition of the processor). Recoverable User Fault The fault routine may clear the fault by clearing bit S:1/13. Sb 02-4 Page 5 of 12

Address S:6 contd

C l a s s i f i c a t i o n Status

Description
Error code descriptions and classifications are listed on pages through. Categories are: powerup errors going-to-run errors runtime errors user program instruction errors II/O errors See chapter 15 of this manual for fault cause and recovery information.

Fixed 5/01

5/02

5/03

5/04

5/05

Fault Classification Error Code Address (Hex) S:6 contd User

PO W E R U P E RRORS
NVRAM error. Unexpected hardware watchdog timeout. Memory module memor error. This error can also occur while going into REM Run mode. Reserved. Reserved. Failure during memory module transfer. Internal software error. Interal hardware error.

NonUser

NonRecov

Recov

Fixed 5/01

5/02

5/03

5/04

5/05

0001 0002 0003

X X X

0005 0006 0007 0008 0009 0010

X X X X X X

GOING TO RUN ERRORS

The Processor does not meet the required revision level. The executable program file number 2 is absent. The ladder program has a memory error. The required memory module is absent or S:1/10 or S:1/11 is not set as required by the program. Internal file error. Configuration file error. Startup protection after power loss. Error condition exisits at powerup when bit S:1/9 is set and powerdown occured while running. NVRAM/memory module user program mismatch.

0011 0012 0013

X X X

0014 0015 0016

X X X

0017

Sb02-4 Page 6 of 12

Fault Classification Error Code Address (Hex) S:6 contd 0018 User Non-

G O I N GTO R U N E RRORS User

Incompatible user program-operating system type mismatch. This error can also occur during powerup. Missing or duplicate label was detected. A program integrity problem occured during an online editing session X

NonRecov

Recov

Fixed 5/01

5/02

5/03

5/04

5/05

X X

0019 001F

RUNTIME E RRORS
0004 0020 Memory error occured while in the Run mode. A minor error bit is set at the end of the scan. Refer to S:5 minor error bits. Remote power failure of an expansion I/O chassis occured. Note: a modular system that encounters an over-voltage or over-current condition in any of its power supplies can produce any of the I/O error codes listed on pages B-33 and B-35 (instead of code 0021). The over-voltage or overcurrent condition is indicated by the power supply LED being off. Fixed and FRN 1 to 4 SLC 5/01processors. If the remote power failure occurred while the processor was in the REM Run mode, error 0021 will cause the major error halted bit (S:1/13) to be cleared at the next powerup of the local chassis. SLC 5/02 processors and FRN 5 SLC 5/01 processors - Power to the local chassis does not need to be cycled to resume the REM Run mode. Once the remote chassis is re-powered, the CPU will restart the system. X X

0021

Sb 02-4 Page 7 of 12

Fault Classification Error Code Address (Hex) 0022 S:6 contd 0023 User

RUNTIME E RRORS

C O N T D

NonUser

NonRecov X X

Recov

Fixed 5/01

5/02

5/03

5/04

5/05

0024

0025 0026

0027

0028

0029

002A

002B

002C

002D

002E 002F

The user watchdog scan time hsa been exceeded. Invalid or non-existant STI interrupt file. Runtime Errors Invalid STI interrupt interval (greater than 2559 ms or negative) Excessive stack depth/ JSR calls for STI routine. Excessive stack depth/ JSR calls for I/O interrupt routine. Excessive stack depth/ JSR calls for user fault routine. Invalid or non-existent startup protection fault routine file value. Indexed address reference outside of entire data file space (range of B3:0 through the last file). The SLC 5/02 processor uses an index value of zero for the faulted instruciton following error recovery. Indexed address reference is beyond specific referenced data file. The file number exists, but it is not the correct file type or the file number does not exist. The indirectly referenced element does not exist, but the file type is correct and it exists. For example, T4:[N7:0] N7:0=10, but T4 only goes to T4:9. Either a subelement is referenced incorrectly or an indirect reference has been made to an M-file. Invalid DII Input slot. Invalid or non-existent DII interrupt file.

X X

X X

Sb02-4 Page 8 of 12

Fault Classification Error Code (Hex) S:6 contd User

RUNTIME E RRORS
I/O Errors

NonUser

NonRecov

Recov

Fixed 5/01

5/02

5/03

5/04

5/05

SLOT NUMBERS (xx) IN HEXADECIMAL Slot 0 1 2 3 4 5 6 7 xx 00 01 02 03 04 05 06 07 Slot 8 9 10 11 12 13 14 15 xx 08 09 0A 0B 0C 0D 0E 0F Slot 16 17 18 19 20 21 22 23 xx 10 11 12 13 14 15 16 17 Slot 24 25 26 27 28 29 30 xx 18 19 1A 1B 1C 1D 1E 1E

ERROR CODES: The characters xx in the following codes represtent the slot number, in hxadecimal. If the exact slot cannot be determined, the characters xx become 1F. RECOVERABLE I/O FAULTS (SLC 5/02, SLC 5/03, SLC 5/04, and SLC 5/05 processors only): Many I/O faults are recoverable. To recover, you must disable the specified slot, xx, in the user fault routine. If you do not disable slot xx, the processor will fault at the end of the scan. Note: An I/O card that is severely damaged may cause the processor to indicate that an error exists in slot 1 even though the damaged card is installed in a slot other than 1. S:6 contd 0030 Attempt was made to jump to one too many nested subroutine files. This code can also mean that a program has potentially recursive routines. An unsupported instruction reference was detected. A sequencer lenght/ position parameter points past the end of a data file. The length of LFU, LFL, FFU, FFL, BSL, or BSR instruction points past the end of a data file. A negative value for a timer accumulator or preset value was detected. Fixed processors with 24 VDC inputs only: A negative or zero HSC preset was detected in a HSC instruction.

This value indicates that the slot was not found (SLC 5/01, SLC 5/02, SLC 5/04 and SLC 5/05 processors). this value indicates that the slot was not found (500 fixed controller).

0031

0032

0033

0034

Sb 02-4 Page 9 of 12

Fault Classification Error Code (Hex) User

Address

U SER P R O G R A M I NSTRUCTION E RRORS

TND, SVC, or REF instruction is called within an interrupting or user fault routine. An invalid value is being used for a PID instruction parameter. A RET instruction was detected in a nonsubroutine file. Invalid string length was detected in a string file. (xx=data file number) A chassis data error is detected. (xx-slot number) A stuck runtime error is setected on an I/O module. (xx=31) A module required for the user program is detected as missing or removed. (xx=slot number)

NonUser

NonRecov X

Recov

Fixed 5/01

5/02

5/03

5/04

5/05

S:6 0035 contd

0036

0038

xx39

xx50

xx51

xx52

I / 0ERRORS
xx53 When going-to-run, a user program declares a slot as unused and that slot is detected as having an I/O module inserted. This can also mean that and I/O module has reset itself. (xx=slot number) An attempt to enter the run or test mode was made with an empty chassis. A module required for the user program is detected as being the wrong type. (xx=slot number) A discrete I/O module required for the user program is detected as having the wrong I/O count. This code can also mean that a specialty card driver is incorrect. (xx=slot number) X

xx54

xx55

Sb02-4 Page 10 of 12

Fault Classification Error Code (Hex) xx56 User

Address

U SER P R O G R A M I NSTRUCTION E RRORS

The chassis configuration specified in the user program is detected as being incorrect. A specialty I/O module has not responded to a lock shared memory command withing the required time limit. (xx=slot number) A specialty I/O module has generated a generic fault. The card fault bit is set (1) in the modules status byte. (xx=slot number) A specialty I/O module has not responded to a command as being completed within the required time limit. (xx=slot number) Hardware interrupt problem. (xx=slot number) G file configuration error - user program G file size exceeds capacity of the module. (xx=slot number) M0-M1 file configuration error - user program M0M1 file sixe exceeds capacity of the module. (xx=slot number) Interrupt service requested is not supported by the processor. (xx=slot number) Processor I/O driver (software) error. (xx=slot number) Identifies and I/O module specific recoverable major error. Refer to the user manual supplied with the specialty module. (xx=slot number)

NonUser X

Recov Non-

Recov

Fixed 5/01

5/02

5/03

5/04

5/05

S:6 contd

xx57

xx58

xx59

xx5A

xx5B

xx5C

xx5D

xx5E

xx60 to xx6F

Sb 02-4 Page 11 of 12

Fault Classification Error Code (Hex) xx70 to xx7F User

Address

U SER P R O G R A M I NSTRUCTION E RRORS

Identifies an I/O module specific non-recoverable major error. Refer to the user manual supplied with the specialty module. (xx=slot number) Identifies a specialty I/O module specific major error. Refer to the user manual supplied with the specialty module. (xx=slot number) Interrupt problem on disabled slot. A disabled slot has faulted. An invalid or non-existent module interrupt subroutine (ISR) file. Unsupported I/O module specific major error. In the REM Run or REM Test mode, a module has been detected as being inserted under power. This can also mean that an I/O module had reset itself. (xx=slot number) Indicates a communication channel hardware fault has occurred. With the SLC 5/05 only, the Ethernet channel (channel 1) may generate this fault, so the only possible value for this fault, so the only possible value for this fault is 0x01A0. The fault maly be cleared via a write to the System Status File, but Ethernet communications will be disabled until a power cycle is performed. Word 15 of the System Status File provides a specific fault code for the Ethernet Daughterboard when user fault code 0x01A0 is generated. (YY-channel number)

NonUser

Recov NonX

Recov

Fixed 5/01

5/02

5/03

5/04

5/05

S:6 contd

xx80 to xx8F

xx90 xx91 xx92

X X X

xx93 xx94

X X

0xYY A0

Sb02-4 Page 12 of 12