OSP-U10L Chapter 3 Alarm P-2

LC37-003 P-47
SECTION 3 ALARM-P

 Synchronous offset data of full-closed loop encoder is not set or set incorrectly.
 Absolute scale or position encoder
 Backlash of drive system is too large (motor and moving parts are not rigidly coupled)
 Axis belt teeth stripped or belt broken
 Loose coupling between motor and ball screw
 Position loop gain is abnormal (too high)
0884 MCS Velocity over
Eeoelale2074 Motor actual velocity is too high.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
Detected velocity at alarm occurrence [(rev/4294967296)/Tv]
rev= 1 motor revolution; Tv= velocity control cycle
[Probable Fault Cause]
 Motor encoder (BL motor)
 Encoder connecting cable or connector (VAC motor)
 Resolver or magnetic encoder (VAC motor)
 Resolver or magnetic encoder connecting cable or connector (VAC motor)
 Inverter unit control board
0885 MCS Velocity error over
Eeoelale2075 Difference between actual motor velocity and commanded velocity is too large.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX: Detected torque (sum of torque data sampled over 3.2 ms)
2-12[MAXTRQ]
At Tv=0.4 ms, instantaneous maximum torque is 7FFF (hexadecimal).
At Tv=0.8 ms, instantaneous maximum torque is 3FFF (hexadecimal).
YYY: Detected acceleration (average over 3.2 ms)
2-16[vr/3.2ms/3.2ms]
= approx. 0.1 [rpm/ms]
When 00000001, indicates data at error becomes zero due to exponent underflow.
[Probable Fault Cause]
Motor cannot rotate due to mechanical fault or excessive load.
0886 MCS Collision detection
Eeoelale2076 Collision was detected by monitoring the relation between motor output torque and acceleration using NC torque limit function.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX: Detected torque (sum of torque data sampled over 3.2 ms)
LC37-003 P-48
SECTION 3 ALARM-P
2-12[MAXTRQ]
At Tv=0.4 ms, instantaneous maximum torque is 7FFF (hexadecimal)
At Tv=0.8 ms, instantaneous maximum torque is 3FFF (hexadecimal)
YYYY: Detected acceleration (average over 3.2 ms)
2-16[vr/3.2ms/3.2ms]
= approx. 0.1 [rpm/ms]
[Probable Fault Cause]
 Collision
 Motor encoder
 NC torque limiter setting value
0887 MCS Emergency stop time over
Eeoelale2077 Axis did not stop within the preset time after receiving emergency stop command.
[Index]
Axis name or none (spindle)
[Character-string
None
[Code]
XXXXXXXX
1: Emergency stop time over
2: Deceleration time exceeded during emergency stop
3: Deceleration time exceeded during alarm stop
[Probable Fault Cause]
 Inverter unit control board
 NC software
0888 MCS Belt broken
Eeoelale2078 Belt of belt-driven axis is broken.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
Load torque at belt breakage (hexadecimal)
[Probable Fault Cause]
Broken belt
0889 MCS Axis switchover control error
Eeoelale2079 Axis control did not operate properly. (This alarm does not occur in MCS.)
[Index]
Axis name after switchover
[Character-string]
None
[Code]
MCS was not reset within 10 seconds.
Parameter group number match signal or control ready complete signal did not turn ON within 210 seconds.
Independent encoder APA maximum value could not be received within 310 seconds.
Modification of in-position width or zero offset was not completed within 610 seconds.
Modification of in-position width or zero offset was not completed within 10 seconds after alarm.
[Probable Fault Cause]
 MCS controller for PLC axis
 Software error
LC37-003 P-49
SECTION 3 ALARM-P
0890 MCS Position encoder initialize error
Eeoelale2080 An error occurred during MCS independent encoder initialization.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
Same as Alarm No. 865 "MCS Encoder initialize error".
[Probable Fault Cause]
 Independent position encoder
 Encoder connecting cable or connector
 Inverter unit control board
0891 MCS APA error
Eeoelale2081 Error occurred during APA calculation.
[Index]
Axis name or none (spindle)
[Code]
XXXXXXXX
1: Linear axis stroke over
2: Overflow during [pr]->[pf] conversion at semi-closed loop position
3: Underflow during axis composite data calculation
4: Overflow during axis composite data calculation
5: Overflow during hybrid control input
6: Overflow during hybrid control initialization
[Probable Fault Cause]
 Motor encoder, position encoder, or absolute scale, inverter unit control PCB, servo data file
 Pay particular attention to the following alarm data.
1, 3: Faulty encoder (or sensor) zero offset data.
4: Often a servo data file fault.
5, 6: Often a loose motor coupling.
0892 MCS Motor overload
Eeoelale2082 Overload protection activated because motor load exceeded specified value.
[Index]
Axis name or none (spindle)
[Code]
YYYYZZZZ
YYYY: GAMMA curve of protection used for overload detection
ZZZZ: Cumulative data of overload detection
[Probable Fault Cause]
 Motor
 Overload during operation
 Servo data file
0940 Time-sharing task control
Eeoelale2083 Time-sharing task control cannot be performed.
[Index]
None
[Character-string]
'A'
A=1 to 7... Main board number detecting this alarm
=B...... FCP detects this alarm.
LC37-003 P-50
SECTION 3 ALARM-P
[Code]
Data in supervisor stack at address 8 when interrupt occurred (hexadecimal)
[Probable Fault Cause]
 Faulty PTM (programmable timer) on main board
 Software error
 Faulty TMINT on FCP board
0941 Real-time task control
Eeoelale2084 Real-time task control cannot be performed because supervisor state was entered between two consecutive real-time control task interrupts.
[Index]
None
[Character-string]
A
A=1 to 7... Main board number detecting this alarm
=B...... FCP board detects this alarm.
[Code]
Data in supervisor stack at address 8 when interrupt occurred (hexadecimal)
[Probable Fault Cause]
 Timing board failure (TFP board or FCP board)
 Servo processor failure (SVP board or FCP board)
0942 Real-time task cycle error
Eeoelale2085 Real-time task indicated in character-string was not completed within the specified processing time.
[Index]
None
[Character-string]
Task name
[Code]
Program counter value when cycle error was detected.
[Probable Fault Cause]
 Timing error of sync signal
 Setting error of sync signal cycle
 Software error
0943 Master processor name error
Eeoelale2086 An illegal character-string was used to specify the master processor name in the configuration file.
[Index]
None
[Character-string]
Master processor name specified in configuration file.
[Code]
None
0944 Slave processor name error
Eeoelale2087 An illegal character-string was used to specify the slave processor name in the configuration file.
[Index]
None
[Character-string]
Slave processor name specified in configuration file.
LC37-003 P-51
SECTION 3 ALARM-P
[Code]
None
0945 Memory board battery exhausted
Eeoelale2088 Memory board battery has run down.
[Index]
None
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Memory board battery
[Measures]
Replace the memory board battery, then reinstall the software and user data.
0951 SMP error
Eeoelale2089 A CPU error occurred on a main board other than the 1st main board.
[Index]
None
[Character-string]
None
[Code]
*%%&&??
*-> Main board number CPU on which CPU error occurred
(e.g., 2: 2nd main board)
%%-> Board status (hexadecimal)
&&-> Bus error status (hexadecimal)
??-> Always 00
[Probable Fault Cause]
 Main board hardware fault indicated by code *
 Software error
0952 Processor board not mounted
Eeoelale2090 Board with the processor board name registered in configuration file is not mounted.
[Index]
None
[Character-string]
Master processor name or slave processor name registered in configuration file that is actually not mounted.
[Code]
None
0954 Peripheral processor start-up error
Eeoelale2091 Peripheral processor did not respond within the predetermined time (20 seconds) after NC start-up.
[Index]
None
[Character-string]
None
[Code]
XY
X=
A->TFP
LC37-003 P-52
SECTION 3 ALARM-P

1-> Main board 1
2-> Main board 2
3-> Main board 3
4-> Main board 4
When X=A
Y= Internal sequence counter at NC startup
When X=1 to 4
Y=
1-> Main processor start timeout
2-> Task initialization timeout
4-> Task initialization disabled
[Probable Fault Cause]
 Hardware failure
 Processor initialization data error (PBU file data)
 Program example: None
 Operation example: None
[Measures to Take]
 Check the processor initialization data indicated by the alarm code.
 Check the hardware.
 Referring to the alarm code, check the sequence counter value to locate the faulty external processor.
0955 Spec code data file
[Code] Eeoelale2092
ABXXYYZZ
A=
1-> NC side specification code file
2-> EC side specification code file
B=
1-> No protect function code file.
2-> Protect function code file attribute or section size mismatch.
3-> Protect function code file does not match machine number.
4-> Protect function code file does not match machine model.
5-> Code data in protect function code file mismatch.
XX-> Byte position of mismatched spec code in protect function code file
YY-> Mismatched spec code in protect function code file
ZZ-> Spec code data in protect function code file (before modification)
0956 Backup data file read
Eeoelale2093 NC backup data file cannot be read from memory.
[Target]
None
[Character-string]
None
[Code]
1-> No backup data file in memory, or specified file name error.
2-> File type is not "PBU1"
3-> DB size for file is too large
4-> DB size for file is too small
[Probable Fault Cause]
 If NC operated normally before alarm occurrence, the NC data file might have been deleted or the file contents corrupted.
 If NC has never operated after control software initialization up to alarm occurrence, the NC data file type may be wrong or the file is not included in the control software.
[Operation Example]
The operator accidentally deleted the NC backup data file.
[Measures to Take]
 For case 1), reinstall the control software.
LC37-003 P-53
SECTION 3 ALARM-P
 For case 2), check the control floppy disk (file name, etc.) and recreate the floppy disk.
0957 Graphic backup data file read
Eeoelale2094 Graphic data file cannot be read from memory.
[Target]
None
[Character-string]
None
[Code]
1-> No backup data file in memory, or specified file name error.
2-> File type is not "PBU1".
3-> DB size for file is too large.
4-> DB size for file is too small.
[Probable Fault Cause]
 If NC operated normally before alarm occurrence, the graphic data file might have been deleted or the file contents corrupted.
 If NC has never operated after control software initialization up to alarm occurrence, the graphic data file type may be wrong or the file is not included in the control software.
[Operation Example]
The operator accidentally deleted the graphic backup data.
[Measures to Take]
 For case 1), reinstall the control software.
 For case 2), check the control floppy disk (file name, etc.) and recreate the floppy disk.
[Related Specifications]
Graphic specifications
0958 Pitch error compensation data file read
Eeoelale2095 After power-on, the ballscrew pitch error compensation or Inductosyn pitch error compensation data file provided by NC was not found in memory.
[Target]
None
[Character-string]
None
[Code]
FFFFFFFF-> No compensation data file.
Other codes-> Compensation data size error in compensation data file.
[Probable Fault Cause]
No pitch error compensation data file, or compensation data size error
[Operation Example]
The operator accidentally deleted the pitch error compensation data file in memory.
[Measures to Take]
Reinstall the control software.
[Related Specifications]
Refer to Pitch Error Compensation Specification Manual.
Ballscrew pitch error compensation -> Special Function Manual 2
Inductosyn pitch error compensation -> High Accuracy Lathe Instruction Manual / Inductosyn Pitch Error Compensation Value Auto-Setting Operation Manual
0965 Configuration file format error
Eeoelale2096 Error in configuration file contents.
[Character-string]
Environment variable in error line
[Probable Fault Cause]
LC37-003 P-54
SECTION 3 ALARM-P
Error when creating configuration file
0971 Super cache data manipulation Init error
Eeoelale2097 An error occurred during super cache data initialization.
[Code]
XYYYY
X:
1-> Error occurred during master macro function initialization.
2-> Error occurred during master macro function initialization.
YYYY:
0001-> TRAP branch data error
0010-> Exception interrupt
0988 Super cache data manipulation Abnormally ended
Eeoelale2098 An error occurred during super cache data transfer.
[Code]
XYYYY
X:
1-> Error during data write to super cache
2-> Error during data read from super cache
YYYY:
0001-> TRAP branch data error
0020-> Invalid argument
0021-> Variable to be registered has already been registered.
0022-> Variable registration table is full.
0040-> Invalid argument
0041-> Specified variable name for reading was not found.
0042-> Read data size does not match cache data size.
0043-> Read data type does not match cache data type.
0989 CPU info table data error
Eeoelale2099 Out-of-range data in CPU information table
[Code]
XXYYZZZZ
XX: Faulty main processor number
1-> Main board 1
2-> Main board 2
3-> Main board 3
4-> Main board 4
5-> Main board 5
6-> Main board 6
YY: Application info table
1-> Table 1
2-> Table 2
3-> Table 3
4-> Table 4
5-> Table 5
ZZZZ: Table index value
0990 Task create error
Eeoelale2100 NC failed to create task.
[Target]
None
[Character-string]
'ABBBB'
A: 1 to 7... Main board number where error was detected
=B ...... Error detected from FCP.
BBBB= Task name
[Code]
XXXXYYYY
LC37-003 P-55
SECTION 3 ALARM-P
XXXX: -> ID of task that failed to be created
YYYY:
1-> Task ID error (Target task already exists.)
2-> Not within TCB range (Task number exceeds 16).
0991 Task info table data error
Eeoelale2101 Value in task info table is 0.
[Code]
XXYYZZZZ
XX: Main processor number where error was detected
1-> Main board 1
2-> Main board 2
3-> Main board 3
4-> Main board 4
5-> Main board 5
6-> Main board 6
YY: Application info table
1-> Table 1
2-> Table 2
3-> Table 3
4-> Table 4
5-> Table 5
ZZZZ: Table index value
0992 PLC backup data file read
Eeoelale2102 Backup data or M code data file cannot be read from memory.
[Character-string]
20001-> No M code data file, or file name error.
20002-> M code data file cannot be opened.
[Code]
None-> M code file error
1-> No PLC backup data file, or specified file name error.
2-> PLC backup data file cannot be opened.
[Probable Fault Cause]
 If alarm occurred during normal NC operation, the file might have been deleted or the file contents corrupted.
 If this alarm occurred before NC started running after control software initialization, the file type may be wrong or it is not stored in memory.
[Measures to Take]
 For case 1), reinstall the control software.
 For case 2), check the control floppy disk data and recreate the floppy disk.
0993 TCP/IP board error
Eeoelale2103 An error occurred on TCP/IP board.
[Code]
1-> TCP/IP board initialization not completed.
2-> TCP/IP board system operation preparation not completed.
0994 TCP/IP configuration file
Eeoelale2104 TCP/IP configuration file error.
[Code]
1-> No configuration file
2-> Configuration file attribute error
3-> Error occurred when opening configuration file.
4-> IP address specified at target station is wrong.
5-> Communication port specified at target station is wrong.
6-> Communication port specified at local station is wrong.
7-> Logical ON/OFF designation error.
8-> IP address specified at local station is wrong.
LC37-003 P-56
SECTION 3 ALARM-P
9-> Subnet mask designation error.
A-> Broadcast address designation error.
B-> Run file name present/absent designation error. The following are error codes related to TCP/IP driver.
C-> Sector device designation error
D-> Sector device not set.
E-> Description error
F-> Parameter setting abnormal
2E-> Configuration file not specified
2F-> Error occurred when opening configuration file
30-> Error during configuration file close
31-> Error during configuration file read
32-> No data in configuration file
33-> IP address error
34-> No IP address
0995 Machine axis data file error
Eeoelale2105 Constant data for axis control (such as magazine axis) does not match the machine specifications.
[Character-string]
Machine axis name
[Code]
1-> In data downloaded from the machine axis data file, the axis name does not match the actual axis name.
11-> Internal specification code in machine axis data file does not match NC specification code.
[Probable Fault Cause]
Error occurred when generating machine axis data file
Data entry error occurred when generating control software
0996 PLC axis data file
Eeoelale2106 Control constant data of PLC axis does not match the machine.
[Index]
None
[Character-string]
PLC axis name
[Code]
1-> Axis name downloaded from PLC axis data file does not match the actual installed axis name.
2-> File type is not "PBU1".
3-> DB size of file is too large.
4-> Specification data in PLC axis data file differs from specification data file in SVP data file.
5: Memory location table for axis backup data does not exist in PLC axis data file.
6: Memory location table for axis parameters does not exist in PLC axis data file.
7: Error occurred when opening PLC axis data file; file is short, file name or device name is incorrect.
8: Although axis name in PLC axis data file is OKUMA standard specification, it does not match registered name.
9: PLC axis data file is too small.
15: For OSP7030/OSP730, number of PLC axes exceeds 8.
16: For OSP7030/OSP730, PLC axis number exceeds 8.
17: For OSP7030/OSP730, although axis switching specification is set, rotary axis gear ratio data of driving axis is 0.
18: For OSP7030/OSP730, although axis switching specification (function generation spec B bit 0) is set, rotary axis gear ratio data of driven axis is 0.
19: For OSP7030/OSP730, although axis switching specification (function generation spec B bit 0) is set, lead pitch data of driving axis is 0.
1A: For OSP7030/OSP730, although axis switching specification (function generation spec B bit 0) is set, lead pitch data of driven axis is 0.
1B: For OSP7030/OSP730, although point positioning specification (function generation spec B bit 6) is set, rotary axis specification (servo data file) is not set.
1C: For OSP7030/OSP730, although point arbitrary positioning specification (function generation spec B bit 7=1) is set, linear axis specification (servo data file) is not set.
1D: For OSP7030/OSP730, driving axis with separate position encoder was not found, or driving axis is not set.
1E: For OSP7030/OSP730, driving axis with separate position encoder is designated as compound axis.
1F: For OSP7030/OSP730, detection rotational speed of independent encoder axis is 0 (this data is set by MCS at power-on).

20: For OSP7030/OSP730, rotary axis gear ratio (EQGDT ) or conversion factor (ESRGDT) for axis with independent encoder is not set (set value 0)

[Probable Fault Cause]

Error occurred when generating PLC axis data file

Power turned off suddenly during axis switching operation (alarm code 21).

0997 PLC monitor backup data file read

Eeoelale2107 PLC monitor backup data cannot be read from memory.

[Code]

1-> File does not exist or file name is incorrect.

2-> File cannot be opened.

3-> File cannot be read (no file data).

4-> Specified file is not a backup file.

5-> File cannot be closed.

6-> File size is small

7-> File size is large

[Probable Fault Cause]

If alarm occurs while NC is operating normally, file may have been deleted or file contents corrupted.

If alarm occurs after control software initialization before NC operates, file type may be wrong or file may not exist in memory.

[Remedy]

In case 1), reinstall control software.

In case 2), check control floppy disk data (such as file name), and remake floppy disk.

0998 PLC sequence program load

Eeoelale2108 Failed to load PLC program file.

[Code]

PLC program file loading status (hexadecimal)

1-> File ends before any characters are loaded

3-> File ends during file loading.

9-> Device name error

A-> File name error

B-> File does not exist.

100-> PLC machine model error

200-> PLC level error

300-> File version error

0999 Synchronized tapping data file read

Eeoelale2109 Synchronized tapping data file cannot be read.

[Code]

XYYYY

X:

1-> No synchronized tapping data file.

2-> Error occurred during loading.

YYYY:

0001-> File ends before even one character is input.

0002-> File ends during loading.