CP40 service manual.pdf - 第43页
MODULE ERROR CODE Symptom and Cause ACTION Service Manual $F00A Exception error Line 1010 emulator Occurs when serious damage such as failure of memory access or board connection occurs to system. $F01B Exception error L…

MODULE
ERROR
CODE
Symptom and Cause ACTION
Service
Manual
$E092
MPU initialization failed / Doc #2 Board not exist
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
$E093
MPU initialization failed / Dic Board not exist
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
$E100
SRAM checksum error
Occurs when battery lift of CPU board is exhausted or connection condition is bad.
$F001
Exception error
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
$F002
Exception error Access fault
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
$F003
Exception error Address error
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
12-3-3
$F004
Exception error Illegal instruction
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
12-3-6
$F005
Exception error Integer Divide zero
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
Motor & I/O
Part
$F006
Exception error CHK, CHK2 instruction
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
$F007
Exception error TRAP instruction
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
12-3-3
$F008
Exception error Privilege violation
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
12-3-6
$F009
Exception error Trace
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
Prepare again the data related to vision of PCB work file.
Try again after Power On/Off.
Prepare again the data related to vision of PCB work file.
Try again after Power On/Off.
- 30 -

MODULE
ERROR
CODE
Symptom and Cause ACTION
Service
Manual
$F00A
Exception error Line 1010 emulator
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
$F01B
Exception error Line 1111 emulator
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
12-3-3
$F00E
Exception error Format error
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
12-3-6
$F00F
Exception error Un-initialized interrupt
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
$F018
Exception error Spurious interrupt
Occurs when serious damage such as failure of memory access or board
connection occurs to system.
$F102
Exception error Head #1 Axis Board not Exist
Occurs when connection of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
$F103
Exception error Head #2 Axis Board not Exist
Occurs when connection of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
$F104
Exception error Head #3 Axis Board not Exist
Occurs when connection of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
7-3-1
$F110
Exception error I/O can't access
Occurs when connection of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
$F120
Exception error DPRAM can't access
Occurs when connection of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
$F201
Exception error XY Axis Board not Exist
Occurs when connection of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
$F202
Exception error Head #1 Axis Board not Exist
Occurs when connection of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
$F203
Exception error Head #2 Axis Board not Exist
Occurs when connections of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
Prepare again the data related to vision of PCB work file.
Try again after Power On/Off.
Try again after Power On/Off.
- 31 -

MODULE
ERROR
CODE
Symptom and Cause ACTION
Service
Manual
$F204
Exception error Head #3 Axis Board not Exist
Occurs when connections of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
Motor & I/O
Part
$F210
Exception error I/O can't access
Occurs when connections of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
$F220
Exception error DPRAM can't access
Occurs when connections of XY or Z, R control axis board is bad.
Occurs when connection of IODPRAM Board cable or its peripheral cable is bad.
$F801
Home tasks creation errorTH_create
Error occurred when checking the internal System.
$F802
Sequence tasks creation errorTS_create
Error occurred when checking the internal System.
$F803
Sequence tasks start errorTS_start
Error occurred when checking the internal System.
$F804
Task kill error
Error occurred when checking the internal System.
$F805
Mode task start errorMod_start
Error occurred when checking the internal System.
$F806
Task start error
Error occurred when checking the internal System.
$F807
Task suspend error Pause
Error occurred when checking the internal System.
$F808
Task resume error Rtask
Error occurred when checking the internal System.
$F809
Task resume error Stask
Error occurred when checking the internal System.
$F80A
Task resume error Satask
Error occurred when checking the internal System.
$F80B
Task suspend error Etask
Error occurred when checking the internal System.
Try to recover the system with Stop/Reset or Emergency Stop/Reset.
If failed, try again after Power On/Off.
Error may be occurred frequently or recovery can not be executed however some measures are
given with above corrective actions.
Try again after Power On/Off.
- 32 -