Fanuc 15 Model B - Alarm List
Fanuc 15 Model B - Alarm List
Fanuc 15 Model B - Alarm List
363
C. ERROR CODE TABLE APPENDIX B–62075E/04
C.1
ALARM LIST (CNC)
NOTE
PSxxx indicates alarms related to programs or settings in
the foreground. Background alarms corresponding to
PSxxx are displayed in the format BGxxx.
Similarly, background alarms corresponding to RSxxx are
also displayed in the format BGxxx.
364
B–62075E/04 APPENDIX C. ERROR CODE TABLE
365
C. ERROR CODE TABLE APPENDIX B–62075E/04
366
B–62075E/04 APPENDIX C. ERROR CODE TABLE
367
C. ERROR CODE TABLE APPENDIX B–62075E/04
368
B–62075E/04 APPENDIX C. ERROR CODE TABLE
369
C. ERROR CODE TABLE APPENDIX B–62075E/04
MISSING VALUE AT CNR, When a block with cornering or chamfering was inserted, the origi- M
CHF nal movement command range was exceeded.
PS 430 CODE ISN’T G01 AFTER The command following a block in which cornering or chamfering
CNR, CHF was specified is not G01.
Example) N1 G01X–––K––– ; N2 G00Z––– I ––– ;
PS 431 MISSING MOVE AFTER The direction or movement distance specified in the block follow- T
CNR, CHF ing a block in which cornering or chamfering is specified is incor-
rect.
370
B–62075E/04 APPENDIX C. ERROR CODE TABLE
371
C. ERROR CODE TABLE APPENDIX B–62075E/04
372
B–62075E/04 APPENDIX C. ERROR CODE TABLE
373
C. ERROR CODE TABLE APPENDIX B–62075E/04
374
B–62075E/04 APPENDIX C. ERROR CODE TABLE
Axis type : Error codes of this type are specified for each axis for which it occurs.
375
C. ERROR CODE TABLE APPENDIX B–62075E/04
376
B–62075E/04 APPENDIX C. ERROR CODE TABLE
377
C. ERROR CODE TABLE APPENDIX B–62075E/04
378
B–62075E/04 APPENDIX C. ERROR CODE TABLE
379
C. ERROR CODE TABLE APPENDIX B–62075E/04
380
B–62075E/04 APPENDIX C. ERROR CODE TABLE
381
C. ERROR CODE TABLE APPENDIX B–62075E/04
382
B–62075E/04 APPENDIX C. ERROR CODE TABLE
THERE IS NO ALARM Normal condition. Machine usually operates under this condition.
ER01 ROM CASSETE ROM PARITY ROM PARITY occurred in the FLASH ROM. (PMC–NA) Corrective
action: Refer to the Chapter III–7.5 “Data Input/Output From/To RAM
Board (PMC–NA)” in the Programming Manual of FANUC PMC–N/NA
(B–61013E).
ER03 PROGRAM SIZE ERROR Sequence data exceeding the print board capacity was input.
ER10 TCB SETTING ERROR The task entry address setting. Stack address, level, or starting condi-
tion parameter is incorrect.
ER12 PASCAL DATA ORIGIN ERROR Another data area is used instead of the PASCAL DATA AREA, or an
odd number address is set.
ER13 PASCAL ORIGIN ERROR Another area is used instead of the PASCAL AREA, or an odd number
address is set.
ER22 SLC ERROR (xGROUP) LSI detection of an I/O device has occurred in the x group, or abnormal
communication has occurred.
Corrective action: Replace the print board or the I/O device.
ER23 SLOT SETTING ERROR An attempt was made to specify 11 or greater as a slot number.
ER24 TOO MUCH DATA (xGROUP INPUT) More than 33 bytes were allocated to the input x group.
ER24 TOO MUCH DATA (xGROUP OUTPUT) More than 33 bytes were allocated to the output x group.
ER25 I/O SETTING ERROR (xGROUP INPUT) Insufficient I/O area (allocation after the output x group is invalid).
ER25 I/O SETTING ERROR Insufficient I/O area (allocation after the output x group is invalid).
(xGROUP OUTPUT)
ER26 I/O DEVICES ARE UNLINKED I/O devices are connected only up to the (x–1) group although alloca-
(AFTER xGROUP) tion data is created for the x and subsequent groups.
Note) If the system is started, the ladder program is not automatically
executed. (Pressing the “RUN” key, however, executes the
ladder program.)
Corrective action:
Correct I/O device allocation, or check the I/O device configuration.
383
C. ERROR CODE TABLE APPENDIX B–62075E/04
ER27 I/O DEVICES ARE UNDEFINED The I/O allocation data is created for only up to the (x–1) group al-
(AFTER xGROUP) though I/O devices are connected to the x and subsequent groups.
Note) If the system is started with the ROM cassette mounted, the
ladder program is not automatically executed. (Pressing the
“RUN” key, however, executes the ladder program.)
Corrective action:
Correct I/O device allocation, or check the I/O device configuration.
ER28 I/O ALLOCATION ERROR (xGROUP) Because I/O UNIT Model A exists in x group, data can not be automat-
ically allocated.
Note) In this case, I/O is not inputted output.
Corrective action:
Press the “IOSTAT” key or power on again after making alloca-
tion data.
ER31 I/O DEVICES ARE UNLINKED I/O devices were connected only for groups “X–1” and lower, when
(AFTER xGROUP) they had been assigned for groups X and higher. In addition:
Value specified at “NUMBER OF I/O LINK GROUP” on the [MODE]
screen > number of connected groups
Note) In this case, no sequence program is started when the power is
switched on. (Pressing the [RUN] key starts a sequence pro-
gram, however).
Corrective action:
Correct the I/O device assignment, or check the configuration of
the I/O devices.
(2) PMC–NB
ER02 PROGRAM SIZE OVER The size of sequence program exceeds the maximum size of LAD-
DER.
(solution) Please change MAX LADDER AREA SIZE at the SYSPRM
screen and restart the system.
ER03 PROGRAM SIZE ERROR (OPTION) The size of sequence program exceeds the option specification size.
(solution) Please increase the option specification size.
Or, reduce the size of sequence program.
ER04 PMC TYPE UNMATCH The PMC model setting of the sequence program is not corresponding
to an actual model.
(solution) Please change the PMC model setting by the offline program-
mer.
ER17 PROGRAM PARITY The parity error occurred on memory for sequence program or the
debugging RAM.
384
B–62075E/04 APPENDIX C. ERROR CODE TABLE
ER18 PROGRAM DATA ERROR BY I/O Transferring the sequence program from offline programmer was inter-
rupted by the power off etc.
(solution) Please clear the sequence program and transfer the se-
quence program again.
ER19 LADDER DATA ERROR Editing the LADDER was interrupted by the power off or by the switch
to the CNC screen by the function key etc.
(solution) Please edit LADDER once on PMC.
Or, please input LADDER again.
ER20 SYMBOL/COMMENT DATA ERROR Editing the symbol and comment was interrupted by the power off or
by the switch to the CNC screen by the function key etc.
(solution) Please edit symbol and comment once on PMC.
Or, please input symbol and comment again.
ER21 MESSAGE DATA ERROR Editing the message data was interrupted by the power off or the
switch to the CNC screen by the function key etc.
(solution) Please edit message data once on PMC.
Or, please input message data again.
ER23 PLEASE TURN OFF POWER There is a change in setting LADDER MAX AREA SIZE etc.
(solution) Please restart the system to make the change effective.
ER32 NO I/O DEVICE Any DI/DO unit of I/O Unit or the connection unit etc. is not connected.
If I/O devices, such as the I/O Unit, are in use:
Make sure that power is supplied to the I/O devices. Also check the
cable connection.
ER34 SLC ERROR (xx) The communication with the DI/DO units of the xx group failed.
(solution) Please confirm the connection of the cable connected to the DI/
DO units of the xx group.
Please confirm whether the DI/DO units turned on earlier than
CNC and PMC. Or, please exchange the module of PMC en-
gine on the DI/DO units of the xx group.
ER35 TOO MUCH OUTPUT DATA IN GROUP The number of the output data in the xx group exceeded the max.
(xx) The data, which exceed 32 bytes, become ineffective.
(solution) Please refer to the following for the number of the data for each
group.
“FANUC I/O Unit–MODEL A connecting and maintenance
manual” (B–61813E)
“FANUC I/O Unit–MODEL B connecting manual”(B–62163E)
ER36 TOO MUCH INPUT DATA IN GROUP The number of the input data in the xx group exceeded the max. The
(xx) data, which exceed 32 bytes, become ineffective.
(solution) Please refer to the following for the number of the data for each
group.
“FANUC I/O Unit–MODEL A connecting and maintenance
manual” (B–61813E)
“FANUC I/O Unit–MODEL B connecting manual”(B–62163E)
385
C. ERROR CODE TABLE APPENDIX B–62075E/04
ER38 MAX SETTING OUTPUT DATA OVER The assignment data for a group exceeds 128 bytes.
(xx) (The assignment data of output side of xx group or later become inef-
fective.)
(solution) Please reduce the assignment data to 128 bytes or less for the
number of the output data of each group.
ER39 MAX SETTING INPUT DATA OVER (xx) The assignment data for a group exceeds 128 bytes.
(The assignment data of input side of xx group or later become infective.)
(solution) Please reduce the assignment data to 128 bytes or less for the
number of the input data of each group.
WN01 LADDER MAX SIZE ERROR The MAX LADDER AREA SIZE in the system parameter is illegal.
(solution) Set the correct value to MAX LADDER AREA SIZE and re
start the system.
WN02 OPERATE PANEL ADDRESS ERROR The address setting data of the operator’s panel for FS–0 is illegal.
(solution) Please correct the address setting data.
WN03 ABORT NC–WINDOW/EXIN LADDER was stopped while CNC and PMC were communicating.
The functional instruction WINDR, WINDW, EXIN, DISPB, and etc.
may not work normally.
(solution) When restarting the system, this alarm will be released.
Execute the sequence program(Press RUN key) after con-
firming whether there is a problem in LADDER or not.
WN07 LADDER SP ERROR (STACK) When functional instruction CALL(SUB65) or CALLU(SUB66) was
executed, the stack of the LADDER overflowed.
(solution) Please reduce the nesting of the subprogram to 8 or less.
WN17 NO OPTION (LANGUAGE) There is no C language option.
WN18 ORIGIN ADDRESS ERROR The LANGUAGE ORIGIN address of the system parameter is wrong
(solution) Please set the address of symbol RC_CTLB_INIT in the map file
to the LANGUAGE ORIGIN of the system parameter.
WN19 GDT ERROR (BASE, LIMIT) The value of BASE, LIMIT or ENTRY of user defined GDT is illegal.
(solution) Please correct the address in link control statement and build
file.
WN20 COMMON MEM. COUNT OVER The number of common memories exceeds 8.
(solution) Please reduce the number of common memories to 8 or less.
It is necessary to correct a link control statement,build file and
the source file for the common memory.
WN21 COMMON MEM. ENTRY ERROR GDT ENTRY of the common memory is out of range.
(solution) Please correct the address of GDT ENTRY of the common
memory in the link control statement.
WN22 LADDER 3 PRIORITY ERROR The priority of LADDER LEVEL 3 is out of range.
(solution) Please correct the value of LADDER LEVEL 3 in the link con-
trol statement within the range of 0 or 10–99 or –1.
WN23 TASK COUNT OVER The number of user tasks exceeds 16.
(solution) Please confirm TASK COUNT in the link control statement.
When the number of tasks is changed, it is necessary to cor-
rect the link control statement, build file and the composition
of the files to be linked.
386
B–62075E/04 APPENDIX C. ERROR CODE TABLE
WN24 TASK ENTRY ADDR ERROR The selector of the entry address to the user task is out of range.
(solution) Please correct the table of GDT in build file to the value within
32(20H)–95(5FH).
WN25 DATA SEG ENTRY ERROR The entry address of the data segment is out of range.
(solution) Please correct DATA SEGMENT GDT ENTRY in the link con-
trol statement and the table of GDT in build file within
32(20H)–95(5FH).
WN26 USER TASK PRIORITY ERROR The priority of the user task is out of range.
(solution) Please correct the TASK LEVEL in link control statement with-
in the range of 10–99 or –1.
Note: Only one task can have TASK LEVEL –1 (including
LADDER LEVEL 3).
WN27 CODE SEG TYPE ERROR The code segment type is illegal. The code segment of RENAMESEG
in the binding control file is wrong.
(solution) Please correct the entry of the code segment in the link control
statement to correspond to the entry in the build file.
WN28 DATA SEG TYPE ERROR The data segment type is illegal. The data segment of RENAMESEG
in the binding control file is wrong.
(solution) Please correct the entry of the code segment in the link control
statement to correspond to the entry in the build file.
WN29 COMMON MEM SEG TYPE ERROR The segment type of common memory is illegal. The segment of RE-
NAMESEG in the building control file of the common memory is wrong.
(solution) Please correct the entry of common memory in the link control
statement to correspond to the entry in the build file.
WN30 IMOPSSIBLE ALLOCATE MEM. The memories for the data and stack etc. cannot be allocated.
(solution) Please confirm whether the value of code segment in build file
and USER GDT ADDRESS in link control statement is correct
or not.
Or please reduce the value of MAX LADDER AREA SIZE of
the system parameter and the size of the stack in link control
statement at the least.
WN32 LNK CONTROL DATA ERROR Link control statement data is illegal.
(solution) Please confirm whether the address of symbol RC_CTLB_
INIT in map file is set to LANGUAGE ORIGIN of the system pa-
rameter. Or, please make the link control statement again.
387
C. ERROR CODE TABLE APPENDIX B–62075E/04
C.3 The following appears on the screen if an alarm condition (error) occurs:
SYSTEM ALARM
PMC ERRORS 08:511D:SERI:0005:0094H581
BUS ERROR FFEC8D (005DC6):PC040
08: : Slot number
511D : ID number of printed circuit board
SERI : ROM series
0005 : ROM version
0094h581 : Last 8 digits of drawing number
BUS : Description of error (See 5.6 (2).)
388
B–62075E/04 APPENDIX C. ERROR CODE TABLE
389
C. ERROR CODE TABLE APPENDIX B–62075E/04
390
B–62075E/04 APPENDIX C. ERROR CODE TABLE
391
C. ERROR CODE TABLE APPENDIX B–62075E/04
NOTE
Subtracting 1 from this number yields the I/O group number.
Assume “00011” is displayed. 3 – 2 = 2. Therefore, the
alarm occurred in an I/O device in group 2. Note, however,
that this information is valid only when bits 0 and 1 of xx (host
SLC error detail information) are 1.
392
B–62075E/04 APPENDIX C. ERROR CODE TABLE
(3) PMC–NA
Display error messages Error contents
1 ROM PARITY add bbb : PC010 PMC ROM parity error has occurred aaa,bbb: defecitive ROM
number
2 RAM PARITY <a.RAM> bb (yyyyyy) : PC020 PMC RAM parity error has occurred
a. RAM: kind of RAM PARITY (B.RAM: BASIC RAM, O.RAM:
OPTION RAM S.RAM: STATIC RAM and P.RAM: PMC RAM
boards)
bb: RAM PARITY ERROR information
3 BUS ERROR xxxxxx (yyyyyy) : PC040 Bus error (impossible to use address access) has occurred
4 ADR ERROR xxxxxx (yyyyyy) : PC040 Address error (odd number address access) has occurred
6 ZDV ERROR (yyyyyy) : PC040 Tried to execute division with a divisor of zero
7 CHK (yyyyyy) : PC040 Register has exceeded the range in the register limit check
11 L10 (yyyyyy) : PC040 Attempted to execute a command with the command code ap-
pearing to be Axxx
12 L11 (yyyyyy) : PC040 Attempted to execute a command with the command code ap-
pearing to be Fxxx
393
C. ERROR CODE TABLE APPENDIX B–62075E/04
(4) PMC–NB
Message STATUS LED Contents and solution
RAM ERROR <a> bbcc xxxx: yyyyyyyy: PC010 The parity error occurs on the debugging RAM of PMC.
a : RAM which generates RAM parity.
B BASIC RAM
O OPTION RAM
S STATIC RAM
bb, cc : RAM PARITY information.
xxxx : Segment selector where system error occurred.
yyyyyyyy : Offset address where system error occurred.
STATUS LED LJ or jL
ROM ERROR aaaaaaaa: PC020 The parity error occurs in PMC system ROM.
STATUS LED lL aaaaaaaa : ROM parity information
DIVIDE ERROR xxxx: yyyyyyyy: PC040 Division error occurs such as a divisor is 0 in the division instruction.
xxxx : Segment selector where system error occurred.
STATUS LED lL yyyyyyyy : Offset address where system error occurred.
BUS ERROR xxxx: yyyyyyyy: PC040 The BUS error (access on illegal address).
xxxx : Segment selector where system error occurred.
STATUS LED lL yyyyyyyy : Offset address where system error occurred.
STACK FAULT xxxx: yyyyyyyy: PC040 The stack exception such as the violation of the limit of the stack.
xxxx : Segment selector where system error occurred.
STATUS LED lL yyyyyyyy : Offset address where system error occurred.
GENERAL PROTECTION xxxx: yyyyyyyy: The general protection exception such as segment limit over was
PC040 generated.
xxxx : Segment selector where system error occurred.
STATUS LED lL yyyyyyyy : Offset address where system error occurred.
SLC ERROR aa (cc) : PC050 The communication error occurred in the I/O Link.
aa, cc : I/O Link error information.
This error may occur by the following causes.
1. When I/O Unit–MODEL A is used, base1, 2 or 3 is not connected
though allocated.
2. The connection of cable is insufficient.
3. Defects of cable.
4. Defects of DI/DO units (I/O unit, Power Mate etc.)
5. Defects of PMC board (printed circuit board on host side where I/O
Link cable is connected.)
(solution) Investigate the cause of error.
1. Please confirm the allocation data (by “EDIT”→“MODULE” screen)
and compare with the actual connection.
2. Please confirm whether the cable is correctly connected.
If you cannot find the cause with the ways above, it may be the defect
of hardware.
Please investigate a defective place by the following methods.
3. Please confirm the specification of the cable referring to “FANUC I/O
Unit–MODEL B connecting manuals(B–62163E)”.
4. Exchange the interface module of I/O Unit, the cable and the PMC
board, etc. one by one and, confirm whether this error occurs again.
The communication may fail by the noise etc. when this error still oc-
curs after replacing all DI/DO units.
STATUS LED JL Please investigate the cause of noise.
394