OSP-P200L-P20L
OSP-P200L-P20L Chapter 2 Alarm P
0700 NC start error
An error occurred during NC startup
[Object]
None
[Character-string]
None
[Code]
0x10000000: NC configuration read error
0x10003000: Special code read error
0x10004000: Special code read error for customer option B
0x20000000: Servo link board initialization error
0x3XXX00YY: NC data file read error
XXX:
0x002: HD backup status file
0x004: Parameter data file
0x008: Machine data file
0x010: PLC backup data file
0x020: PLC-HMI data file
0x040: Alarm history data file
0x080: PLC axis data pbu file
0x100: Pot tool data pbu file (Machining center only)
0x200: MOP TOOL tool data file (Machining center only)
0x400: MOP TOOL parameter file (Machining center only)
0x410: Synchronized tapping data file
0x420: Thermal deformation compensation V2 data file
0x430: TAS-S/TAS-C function data file
0x500: Alarm information file
0x600: Error information file
0x700: Layout information file
0x800: PPC function data file (Machining center only)
YY:
0x01: File read open error
0x02: File read error
0x03: Version check error
0x04: Checksum error
0x05: Double checksum error
0x06: Backup memory error
0x07: File write open error
0x08: File write error
0x40000001: Axis information initialization error
– More than 8 axes
0x50000000: PLC data file read error
– Failed to read M-code data file
0x6000XYYY: I/O initialization error
X:
0: PLC variable backup file read error
YYY:
1: File read open error
2: File read error
3: Version check error
1: I/O forced data file read error
YYY:
1: File read open error
2: File read error
0x70000000: Servo link initialization error
0x80000000: Operation buffer error
0x90000000: PBU data file read error
0xA0000000: Shared memory capacity definition error
0xA1XXXXXX: Alarm server start error
XXXXXX: Alarm server library function error code
0xA2400002: Alarm history read error
0xA3000000: Thread monitor initialization error
0xA400XYYY: DeviceNet definition file read error
X:
0: DeviceNet definition file read error
YYY:
1: File not found
2: File read open error
3: File read error
4: File attribute error
5: File data error
1: DeviceNet scan list change file read error
YYY:
1: File not found
2: File read open error
3: File read error
4: File attribute error
5: File attribute error
6: File size error
7: File size error
2: MTB-HMI IO address conversion data file read error
YYY:
1: File not found
2: File read open error
3: File read error
4: File attribute error
5: File attribute error
6: File data error
0xA500XXXX: System IO file read error
XXXX:
1: File not found
2: File read open error
3: File attribute error
4: File attribute error
5: File data error
0xA6000000: When SUPER-NURBS specification is present and the specification bit is not ON, it does not match the board.
0xFFFFFFFF: Debug information file read error
0703 Load information file not found
Load information file was not found.
[Object]
None
[Character-string]
None
[Code]
None
0704 Illegal load file
Target file was not loaded correctly.
[Object]
None
[Character-string]
None
[Code]
1: File not found
2: Incorrect file attribute
3: Load address information of file is incorrect
4: Error occurred when loading file
FFFFFFFF: Alarm details are displayed by information from OS
0705 Default dispatch table error
Default dispatch table error is detected.
[Object]
None
[Character-string]
None
[Code]
0x00010001: RTIN default dispatch table error (number of elements)
0x00010002: RTIN default dispatch table error (end element)
0x00020001: TSMN default dispatch table error (number of elements)
0x00020002: TSMN default dispatch table error (initial element)
[Probable Fault Cause]
NC software error
0706 Backup data file error
An error occurred while loading/saving backup file.
[Object]
None
[Character-string]
None
[Code]
XXXXYYYY
XXXX
0x0002: HD backup status file
0x0004: Low-speed NC backup data file
0x0008: High-speed NC backup data file
0x0010: PLC backup data file
0x0020: PLC-HMI data file
0x0040: Alarm history data file
0x0080: PLC axis data file
0x0100: Pot tool data file (Machining center only)
0x0200: MOP TOOL tool data file (Machining center only)
0x0400: MOP TOOL parameter data file (Machining center only)
0x0800: Thermal deformation compensation data file (Lathe only)
PPC function data file (Machining center only)
YYYY
1: File read open error
2: File read error
3: Version check error
4: Checksum error
5: Double checksum error
6: Backup memory check error
7: File write open error
8: File write error
0707 DTL link/unlink error
An error occurred during DTL link or unlink.
[Object]
None
[Character-string]
None
[Code]
1: RTIN refresh error
2: TSMN refresh error
[Probable Fault Cause]
1) Hardware failure
2) Software failure
0708 RT thread stack overflow
RT thread stack overflow was detected.
[Object]
None
[Character-string]
RT thread name where error occurred
[Code]
None
[Probable Fault Cause]
NC software error
0709 Hardware exception
A hardware exception occurred.
[Object]
None
[Character-string]
RT thread name where error occurred
[Code]
Hardware exception code
0x5555: CPU diagnostic error
0x8100: Divide by zero error
0x8101: Unexpected single-step interrupt
0x8102: Unexpected NMI
0x8103: Unexpected debug interrupt
0x8104: Overflow error
0x8105: Array bounds error
0x8106: Invalid opcode error
0x8107: Device not available (no NPX)
0x8108: Double fault
0x8109: Unknown device error
0x810A: Invalid TSS error
0x810B: Segment not present error
0x810C: Stack error
0x810D: General protection fault
0x810E: Page fault
0x8110: Unknown device error 1
0x8111: Alignment check error
[Probable Fault Cause]
1) Hardware failure
2) Software failure
[Notice]
Alarm message is also displayed on the console window.
0710 System call error
An RTOS system call error occurred.
[Object]
None
[Character-string]
RT thread name where error occurred
[Code]
XXXXYYYY
XXXX: RTOS system call code
YYYY: Return value or status of RTOS system call
[Probable Fault Cause]
NC software error
[Notice]
Alarm message is also displayed on the console window.
0711 Alarm server library error
An error occurred in the alarm server library function.
[Object]
None
[Character-string]
Thread name where error occurred
[Code]
XXYYYYYY
XX: Alarm server library function code
YYYYYY: Alarm server library function error code
[Probable Fault Cause]
NC software error
[Notice]
Alarm message is also displayed on the console window.
0712 Internal alarm server error (exception)
An error occurred inside the alarm server.
[Object]
None
[Character-string]
ALMS
[Code]
Alarm server internal error code
[Probable Fault Cause]
NC software error
[Notice]
Alarm message is also displayed on the console window.
0713 Alarm server invalid
An error occurred in the alarm server.
[Object]
None
[Character-string]
None
[Code]
None
[Probable Fault Cause]
NC software error
0714 Blue screen
A blue screen occurred (kernel stop error).
[Object]
None
[Character-string]
None
[Code]
None
[Probable Fault Cause]
1) Win32 application failure
2) Windows failure
3) Windows driver failure
0716 Floating-point exception
A floating-point exception occurred.
None
[Character-string]
Name of the RT thread where the error occurred
[Code]
XXXXYYZZ
XXXX: Exception code
YY: Not used (fixed to 0)
ZZ: FPU status word
Bit 5: PE (Precision exception flag)
Bit 4: UE (Underflow exception flag)
Bit 3: OE (Overflow exception flag)
Bit 2: ZE (Zero divide exception flag)
Bit 1: DE (Denormalized operand exception flag)
Bit 0: IE (Invalid operand exception flag)
[Probable Fault Cause]
NC software error
0717 PLC control error
An error occurred in PLC control.
[Target]
None
[Character-string]
None
[Code]
XXXXYYYY
XXXX: PLC control status
YYYY: PLC control error code
[Probable Fault Cause]
PLC software error
0718 Real-time thread timeout
The real-time thread did not finish within the specified time.
[Target]
None
[Character-string]
Name of the RT thread that exceeded the specified time
[Code]
None
[Probable Fault Cause]
NC software error
0719 HXCP thread error
An abnormal HXCP thread status was detected.
[Target]
None
[Character-string]
None
[Code]
None
[Probable Fault Cause]
NC software error
0720 Alarm service routine internal error
An error occurred inside the alarm service routine.
[Target]
None
[Character-string]
ALMS
[Code]
Alarm service routine internal error code
[Probable Fault Cause]
NC software error
0721 Local network error
An error occurred in the local network.
[Target]
None
[Character-string]
CH* SC$
*: Channel number where the error occurred
$: Sequence counter
[Code]
XXYYZZZZ
XX: MacID of the slave where the error occurred
YY: Error status of slave XX
0x00: Normal or nonexistent slave
0x46: Duplicate MacID error
0x48: Communication congested
0x49: Identification information mismatch with scan list
0x4D: Data size mismatch with scan list
0x4E: No response in connection check
0x4F: Other slave not on network
0x50: Idle status
0x53: Error received in connection check
0x54: Timeout in connection check
0x56: Transition to idle mode
0x5B: Bus off
0x5C: Network power supply off
(If the error was not caused by a slave, such as a communication delay, XXYY becomes 0xFFFF.)
ZZZZ: Scanner error status
Bit 0: Memory check error (during memory initialization)
Bit 1: Scan list initialization error
Bit 2: Scan list mismatch error (MacID)
Bit 3: Scan list mismatch error (input data)
Bit 4: Scan list mismatch error (output data)
Bit 5: Duplicate MacID error
Bit 6: Network power supply status error
Bit 7: Memory parity error
Bit 8: Input data receive error (simplex)
Bit 9: Input data receive error (duplex)
Bit 10: Output data transmit error (simplex)
Bit 11: Output data transmit error (duplex)
Bit 12: Slave communication delay error (simplex)
Bit 13: Slave communication delay error (duplex)
Bit 14: Bus off
Bit 15: Diagnostic information access error
[Probable Fault Cause]
• Hardware error
• Software error
0728 FL-net illegal
An error occurred when starting the FL-net board.
[Target]
None
[Character-string]
None
[Code]
Y000XXXX
Y:
0
XXXX:
7F00: System error
7F01: Flash memory error
7F02: DRAM test error
7F03: NICE test error
7F04: EEPROM sum check error
7F05: CPU bus error
7F06: Illegal instruction
1
XXXX:
0004: Abort for 4 seconds or longer error
F
XXXX:
FFFF: FL-net board not installed
[Probable Fault Cause]
FL-net board failure
0729 Unresponsive software detected
Unresponsive software was detected.
[Target]
None
[Character-string]
None
[Code]
NT process name
[Probable Fault Cause]
NC software error
0730 NC load or startup failed
0812 MCS start-up
An error occurred during MCS initialization at power-on.
[Target]
Axis name or none
[Character-string]
Varies depending on code
[Code]
XXXXYYYY
XXXX: Alarm type occurred
YYYY: Alarm information (Varies depending on XXXX.)
XXXX
FFFF…YYYY=00UV, U: Error channel number - 1
0= Channel 1
1= Channel 2
2= Channel 3
V: Indicates the cause of error (V=1 indicates that the servo link mode has not been established.)
FF01…. Indicates that a memory error occurred during the read/write test of the servo link I/O buffer memory.
YYYY=0 (Fixed)
The character-string indicates the error address.
FF00… Indicates that a communication LSI circuit error occurred during the read/write test of the servo link I/O buffer memory.
YYYY indicates the error status.
The character-string indicates the error address.
F000…YYYY= Bit 7: Same ID code used
Bit 6: Incorrect ID code
Bit 5: No ID code
Bit 4: Too many controllers on CH4
Bit 3: Too many controllers on CH3
Bit 2: Too many controllers on CH2
Bit 1: Too many controllers on CH1
Bit 0:
When this error occurs, link data is displayed at the center of the screen.
EF00… Indicates that the servo is not connected to all required axes, or is connected to an irrelevant axis. YYYY = ID code of the required axis controller
The character-string indicates the axis name in question. When this error occurs, link data is displayed at the center of the screen.
EE00… Indicates that an error occurred while downloading an option file.
The high-order byte of YYYY indicates the cause, and the low-order byte indicates the error code.
If high-order =
1: File is not in OSP format.
2: Irrelevant file attribute.
3: File open error. Low-order indicates error code.
4: Raw data read error. Low-order indicates error code.
5: File does not start with "MCS1".
6: File name does not follow "OPFS".
7: Number of files set to 0.
8: Data read error; low-order indicates error code.
9: One sector length in file data is 0.
A: Number of transferred bytes is 0.
B: One sector length in file data is smaller than the number of bytes sent.
C: Data read error; low-order indicates error code.
ED00… Indicates that an error occurred when switching from manual mode to automatic mode. The high-order byte of YYYY indicates the cause, and the low-order byte indicates the error code.
High-order byte = 1: World clock not started.
EC01… Indicates a timer error on CH1. YYYY is the difference value.
EC02… Indicates a timer error on CH2. YYYY is the difference value.
EC03… Indicates a timer error on CH3. YYYY is the difference value.
D001… Indicates that the software sync bit signal was not received within 3 seconds when receiving raw data in the buffer in automatic mode. YYYY is always 0.
D002… Indicates that a format error code was received in buffer A when receiving raw data in the buffer in automatic mode. The two low-order characters of YYYY are the received
format code.
D003… Indicates that a format error code was received in the 1st segment of buffer B when receiving raw data in the buffer in automatic mode.
YYYY is the received format code.
D004… Indicates that a format error code was received in the 2nd segment of buffer B when receiving raw data in the buffer in automatic mode.
YYYY is the received format code.
D005… Indicates that a format error code was received in the 3rd segment of buffer B when receiving raw data in the buffer in automatic mode.
YYYY is the received format code.
D006… Indicates that a format error code was received in the 4th segment of buffer B when receiving raw data in the buffer in automatic mode.
YYYY is the received format code.
D007… Indicates that a format error code was received in the 5th segment of buffer B when receiving raw data in the buffer in automatic mode.
YYYY is the received format code.
D008… Indicates that a format error code was received in the 6th segment of buffer B when receiving raw data in the buffer in automatic mode.
YYYY is the received format code.
D009… Indicates that a format error code was received in the 7th segment of buffer B when receiving raw data in the buffer in automatic mode.
YYYY is the received format code.
D00A… Indicates that a format error code was received in the 9th segment of buffer B when receiving raw data in the buffer in automatic mode.
YYYY is the received format code.
D010… Indicates that the received self-diagnostic data is not $55 when receiving raw data in the buffer in automatic mode. YYYY is the received self-diagnostic data.
D011… Indicates that bits 0 and 1 in the "bit" data received in buffer A are incorrect when receiving raw data in the buffer in automatic mode.
YYYY is the received data.
D012… Indicates that bits 2 and 3 in the "bit" data received in buffer A are incorrect when receiving raw data in the buffer in automatic mode.
YYYY is the received data.
D013… Indicates that bits 4 and 5 in the "bit" data received in buffer A are incorrect when receiving raw data in the buffer in automatic mode.
YYYY is the received data.
D080… Indicates that the raw data with ID code 441C buffered in automatic receive mode has an error. YYYY is the received data.
D081… Indicates that the raw data with ID number 2428 buffered in auto-receive mode has an error. YYYY is the received data.
D090… Indicates that the raw data with ID number 4405 buffered in auto-receive mode has an error. YYYY is the received data.
D091… Indicates that the raw data with ID number 4404 buffered in auto-receive mode has an error. YYYY is the received data.
D092… Indicates that the offset data used for target point compensation in the raw data buffered in auto-receive mode has an error. YYYY is the received data.
[Probable Fault Cause]
• Inverter unit (Check the inverter unit LED display).
• MCS ID setting error.
• Specification code setting error.
• Connection error with MCS.
0813 MCS communication error
An error occurred in communication between NC and MCS at power-on.
If servo link information is displayed in the center of the screen, the cause of the communication error can be determined based on the provided information.
[Object]
None
[Character-string]
[Command name] – [Channel No.] – Station address (Controller No.)
[Code]
XXXXYYYY
XXXX:
1…NC received the data transmitted by itself.
YYYY is the received frame information.
2…Public data transmitted from a non-slave station was received.
YYYY: Received frame information
3…Received data size is 2 bytes or less.
YYYY: Normally 0
4…Data transmitted from a non-slave station was received.
YYYY: Received frame information
5…NC received the data broadcasted by NC.
YYYY: Received frame information
6…Data transmitted from station address 0 was received.
YYYY: Received frame information
7…No response was received from the data receiver within 0.1 s after data transmission for 1 s. YYYY: Normally 0. At link connection, the "SI" command was designated before at least one MCS started normally or before
power-on. Check the connection inside the control cabinet and check the LED display on the inverter unit; the display is '22' when connection is normal.
8…Data transmission was not completed after approximately 0.1 s. YYYY is normally 0.
9…Communication failure occurred after data reception. YYYY is error status information.
A…Communication failure occurred while NC was waiting for data reception or just after data transfer completed. YYYY is error status information.
B…Communication failure occurred while waiting for data transmission. YYYY is error status information.
C…Attempted to send data while data was being transmitted. YYYY is NC operation status information.
D…Attempted to send data while a communication failure was already occurring. YYYY is error status information.
E…An erroneous command was received. When the lower digits are numbers, the upper two digits of YYYY indicate the code (45: Abnormality, 41: Alarm, 57: Warning, 54: Error)
[Refer to the handshake communication alarm table (5-10) in the MCS Controller Function External Specifications.]
100…Error in the first 2 bytes of the response information for transmitted data. YYYY: First 2 bytes received
101…Received data size does not match the response requirement for transmitted data. The upper digits of YYYY indicate the received data size, while the lower digits indicate the normal value.
102…Error in the 1st data attached to the received data. YYYY: Upper two bytes of data determined to be in error. SI command: Slave link No.
AS command: Slave link No. ID command: Communication code + auxiliary code
103…Error in the 2nd data attached to the received data. YYYY: Upper two bytes of data determined to be in error. SI command: Transit time value.
ID command: Data ID
104…Error in the 3rd data attached to the received data. YYYY: Upper two bytes of data determined to be in error. ID command: Reserved data
105…Error in the 4th data attached to the received data. YYYY: Upper two bytes of data determined to be in error. ID command: ID data (4 bytes or less)
106…Error in the 5th data attached to the received data. YYYY: Upper two bytes of data determined to be in error. SI command: Controller number.
ID command: ID data (8 bytes)
200…Data size differs from that specified by ID number. Software failure
[Probable Fault Cause]
• Inverter unit (Check the inverter unit LED.)
• FCP board
• MCS connection error
• MCS connection cable
• Software error
0814 MCS data file
An error occurred when reading or transferring the servo link data file after power-on, or the data file contains erroneous data.
[Object]
[Character-string],
[Axis name], [Device name], [File name] or none
[Code]
XYZZAAAA
X: Axis type; Y: Major classification; ZZ: Minor classification; AAAA: Data
X: 1 = NC control axis
2 = Spindle
3 = PLC control axis
Y: 0 = Error during servo data file read
ZZ:
01 = Error during file recovery. AAAA = Error code
AAAA indicates 000B: File does not exist, or required axis data is not in the file.
02 = Incompatible file attribute.
03 = File format is not OSP format.
04 = Error during file open. AAAA = Error code
05 = Error during file data read. AAAA = Error code
06 = File does not start with "PBU1".
07 = File name does not follow "MI".
08 = Corresponding axis data exceeded the maximum data value set in the file before data transfer.
09 = Error during file close. AAAA = Error code
0A = Data group capacity exceeds 8 sectors. AAAA = Number of data sectors
0B = Error during data read. AAAA = Error code
0C = Data file does not contain the predetermined data group number.
0D = Data serial number mismatch.
0E = Data type mismatch.
0F = Total number of data groups mismatch.
10 = Error during file close. AAAA = Error code
11 = Servo data for the existing NC axis does not exist in the data file.
Y: 1 = Error detected during servo data file check
ZZ:
01 = NC axis control data file for heavy workpiece machining specification not found.
02 = Axis specification (linear axis, rotary axis) does not match the inverter unit. AAAA = Axis specification data
03 = Acceleration/deceleration method mismatch.
04 = Synchronous sensor not provided.
05 = Data group number error (spindle group number outside 1 to 32). AAAA = Data group number
06 = Erroneous data not conforming to system specifications in speed constant characteristic data.
Upper two digits of AAAA indicate the axis number, and lower two digits indicate the error details.
Upper digits AA:
00 -> X-axis
01 -> Y-axis
02 -> Z-axis
03 -> 4th axis
04 -> 5th axis
Lower digits AA:
11 -> FT1max=0
12 -> FT1max < FT1min
13 -> FT1max=FT1min and T1max < T1min
14 -> FT1max > FT1min and T1max < T1min
21 -> FT2max=0 (FT2max is determined by internal calculation.)
22 -> FT2max < FT2min
23 -> FT2max=FT2min and T2max < T2min
24 -> FT2max > FT2min and T2max < T2min
07 = NC axis servo data for heavy workpiece machining NC control specification not found.
[Probable Fault Cause]
Axis data file error
0817 MCS abnormality
An error occurred during MCS control processing.
[Object]
Axis name or none
[Character-string]
None
[Code]
XXZZAAAA
When XXZZ=0
AAAA:
1 = Processing not completed within 5 seconds after MCS reset 1.
2 = Processing not completed within 5 seconds after MCS reset 2.
3 = Processing not completed within 5 seconds after PLC reset 1.
4 = Processing not completed within 5 seconds after PLC reset 2.
X: 1 to 3
X: Channel number
YZZAAAA: Communication error status
[Probable Fault Cause]
• MCS controller
• Servo link error on FCP board
• Software error
0833 MCS optional program file transfer
The optional program file for MCS was not transferred to MCS.
[Object]
Axis name or none
[Character-string]
None
[Code]
None
[Probable Fault Cause]
• MCS optional program file was not transferred.
• MCS was not found.
• Program matching the MCS software version number does not exist in the MCS optional program file.
[Measures to Take]
• Install the MCS optional program file.
• Replace the MCS optional program file.
0834 MCS servo data error
Servo data transferred to MCS has an error.
[Object]
Axis name or none
[Character-string]
None
[Code]
XXXXYYZZ
XXXX = ID No.
YY = Parameter No.
ZZ = Error details
01: Setting out of range
02: Setting timing error
03: Data not transferred
04: Calculation error
05: Other
[Probable Fault Cause]
• Mismatch between servo data file and MCS software version.
• NC software
[Measures to Take]
Replace the servo data file.
0835 MCS handshake communication
An error occurred during handshake communication with MCS.
[Object]
Axis name or none
[Character-string]
Handshake communication error No. (2 digits), error data (8 digits), and [Command name] - [Channel No.] - Station address (Controller No.)
[Code]
None
[Probable Fault Cause]
• Application software error
• MCS software error
[Measures to Take]
• Replace application software.
• Replace MCS software.
0836 Program request error
Processing request number from CNC software to loader software is illegal.
Request No. (hexadecimal)
[Probable Fault Cause]
CNC software error
0837 Loader spec code: data file
An error occurred in the loader spec code data file.
[Code]
1-> No spec code data file (search error).
2-> Not a contiguous file
3-> Not in OSP format
4-> Open error
5-> Read error
6-> Size mismatch
7-> Code mismatch
8-> Close error
0838 Loader backup data file read
Cannot read loader backup data file from memory.
[Code]
XYYZZZZ
X:
0-> Right side
1-> Left side
YY =00-> Loader backup data error
1-> No data file
ZZZZ =2-> Data file is not a "PBU1" file
ZZZZ =3-> Data file size mismatch
11-> No program file
ZZZZ =12-> Program file is not a "PBU1" file
ZZZZ =13-> Program file size mismatch
YY =11-> Data file search error
ZZZZ = Access status
Data file open error
ZZZZ = Access status
Data file read error
ZZZZ = Access status
YY =21-> Program file search error
ZZZZ = Access status
YY =22-> Program file open error
ZZZZ = Access status
YY =23-> Program file read error
ZZZZ = Access status
0840 Advanced HI-NC spec mismatch
The [NURBS command] spec is selected, but the [Advanced HI-NC] spec is not selected.
0841 FCP4 illegal
FCP4 board status is abnormal.
[Character-string]
AAAABB
AAAA: Task name being executed
BB: Program module being executed
[Code]
WWXXYYZZ
WW=0 (When omitted)
XXYYZZ: Same as alarm P809
WW=10 OS failure
XX=00 PLT0 task
=01 PLT1 task
=09 PLSY task
=10 PLR2 task
=20 PLR3 task
YYZZ= (Alarm content)
=0001 Forced task termination failed
=0002 Task startup failed
=0003 Task startup wait failed
=0004 Task startup wait failed
(After 1.6 ms delay)
WW=20 Internal memory check error
XXYYZZ indicates the header address of the check area
0842 Safety monitor spec error
Conditions for connecting the safety speed monitor are not satisfied.
Or, the guard number in the safety speed monitor axis data file is out of the allowable setting range.
[Code]
X
1-> Safety speed monitor connected to the displayed axis is in an incorrect position.
2-> A value other than 1 to 9 is set as the guard number of the safety speed monitor axis data file.
3-> The safety speed monitor is not installed, but machine CE marking is planned.
4-> The safety speed monitor is installed, but machine CE marking is not planned.
5-> The safety speed monitor axis data file has two identical positions where the safety monitor is connected to the spindle (M-spindle).
[Measures to Take]
1) Check if the safety speed monitor is at the connection position.
2) Set a number from 1 to 9 as the guard number in the safety speed monitor data file.
3) Connect the safety speed monitor.
4) Set the spec code for CE marking, or remove the safety speed monitor.
5) Check the safety speed monitor guard number and the data file input number.
0843 I-GAP backup data file read
Cannot read I-GAP backup data from memory.
[Code]
1-> The I-GAP backup file is not stored in memory, or the stored file name is incorrect.
2-> The file type is not PBU1.
3-> File DB is too large.
4-> File DB is too small.
[Probable Fault Cause]
1) If the NC operated normally before the alarm, the I-GAP data file may have been deleted or corrupted.
2) If the NC has not operated since the control software was installed until the alarm occurred, the I-GAP data file may be incorrect or does not exist.
[Measures to Take]
1) If the NC operated normally before the alarm, install the control software.
2) If the NC does not operate after installing the control software and before the alarm occurred, check the control floppy disk data (file name) and recreate the floppy disk.
[Related Specifications]
I-GAP
0844 FWMB illegal
An error occurred in the FWMB (FWM board).
[Object]
None
[Character-string]
None
[Code]
XYYZZ
X=1-> FWMB baseline board
YY: Self-diagnostic code
ZZ=00-> No error
=01-> General CPU exception occurred
=02-> MSTP detected
=03-> Graphic accelerator corrupted
=04-> NMI detected
=05-> Kernel program detected error
=06-> Undefined interrupt detected
=11-> UCMB switch wait state timeout error
=12-> Memory error
=21-> Illegal instruction detected
=22-> Console startup message timeout error
=24-> Other error
=31-> Fatal IPL error
=41-> Fatal error/internal logic error
=71-> Exit termination
0845 Spec code setting error
An unselectable spec code is set.
A required spec code is not set.
Inconsistent spec code combination.
[Code]
1-> Spec codes for all machine models are OFF.
[Probable Fault Cause]
Machine model spec code is not set.
[Measures to Take]
1) If the NC operated normally before the alarm, install the control software.
2) If the NC does not operate after installing the control software and before the alarm occurred, check the control floppy disk data (file name) and recreate the floppy disk.
0846 Thermal drift compensation backup data file read
Thermal drift compensation backup data file (LNCUF) was not found or file type is incorrect.
[Object]
None
[Character-string]
None
[Code]
1-> No backup file
2-> Backup file type is not PBU1
3-> Backup file is too long
4-> Backup file is too short
5-> Allocation table error
[Probable Fault Cause]
1) No thermal drift compensation backup file.
2) Error in thermal drift compensation backup file.
3) Error in allocation table in program.
0847 DNC-DT preload task startup error
Activation of the API read-ahead task did not terminate normally.
[Object]
None
[Character-string]
None
[Code]
API error code
0848 PSCB illegal
An error occurred in the PSC board that rotates the lathe.
[Code]
1-> Clock stop error
2-> Parity error in compensation data memory (C0)
4-> Parity error in compensation data memory (C1)
8-> Parity error in offset data memory
10-> Parity error in command data memory
20-> Parity error in main memory
40-> Overcycle error
80-> Loop error
[Probable Fault Cause]
PSC board error
[Measures to Take]
Replace the PSC board.
0849 Synchronous tandem axes initial error
An error occurred during initial modification of synchronous axes under tandem control.
[Object]
Axis or none
[Character-string]
None
[Code]
XXYY
XX= Cause, YY= Pair No.
=1: Tandem control spec soft-wire for master axis is not '1'
=2: Master tandem control spec soft-wire for master axis is not '1'
=3: Tandem control spec soft-wire for slave axis is not '1'
=4: Master tandem control spec soft-wire for slave axis is not '0'
=5: Master axis of synchronous axes not found
=6: Slave axis of synchronous axes not found
=7: Master axis and slave axis are not connected to the same link (channel)
=8: Link connection order of master axis and slave axis is not in master axis, slave axis order.
=9: Controllable stations for communication cannot be guaranteed
[Measures to Take]
XX=1: Correct or replace the servo data file.
=2: Correct or replace the servo data file.
=3: Correct or replace the servo data file.
=4: Correct or replace the servo data file.
=5: Check the application software.
=6: Check the application software.
=7: Connect the master axis and slave axis to the same link.
=8: Connect in the master axis, slave axis order.
=9: The maximum number of axes connected to the link with the master axis and slave axis is 7.
0850 MCS unregistered alarm
A fault related to axis control occurred on the MCS.
[Object]
Axis name or none (spindle)
[Character-string]
Alarm No. (decimal)
[Code]
Alarm code
[Probable Fault Cause]
Depends on the alarm No. displayed in the character-string. Inform the machine builder of the character-string and code.
0851 MCS exception processing
A serious fault occurred during execution of the MCS inverter unit and MCS software.
[Object]
Axis name or none (spindle)
[Character-string]
Detected alarm cause
"#1"-> Control board abnormality
"#2"-> Voltage of +/-12 V power supply used by control board is too low
"#3"-> OPF error
"#11"-> Voltage of 5 V power supply used by control board is low
"#12"-> Inverter bridge of inverter unit is short-circuited
"#13"-> IPM protection activated
"#14"-> Motor overcurrent
"#20"-> INT6 cycle error
"#22"-> INT4 cycle error
"#23"-> INT3 cycle error
"#24"-> INT2 cycle error
"#25"-> INT1 cycle error
"#26"-> Inaccessible
“#27”-> Initialized RAM check error
“#28”-> Parity check error
“#29”-> IRQ7 interrupt
“#31”-> NMI interrupt (non-maskable interrupt)
“#32”-> General illegal instruction
“#33”-> Slot illegal instruction
“#34”-> CPU address error
“#35”-> DMA address error
“#36”-> Undefined trap error
“#37”-> Undefined interrupt
“#38”-> DMAC
“#39”-> ITU
“#40”-> SCI
“#41”-> REF
“#42”-> A/D
“#43”-> System reserved
“#44”-> User break
[Code]
When the character-string is #1, code indicating the error content of the control board.
When the character-string is #3, code indicating the error content of the optional program file.
1: Identification code "OPF1" error
2: End code "ED" error
3: "Checksum" error
4: Board name error
When the character-string is #11 - 14, #20 - 21, #25 - 26, and #30 - 31, indicates the contents of the error status register.
[Probable Fault Cause]
In case of #1:
• Inverter unit
In case of #3:
• Error in the optional program file
• Mismatch between optional program file and unit
In case of #2 or #11:
• Power supply unit failure (this alarm occurs on multiple inverter units)
In case of #12, #13, or #14:
• Inverter unit
In other cases:
• Inverter unit
0852 MCS processing error
MCS
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXZZAAAA
XX:
04… Self-diagnostic data error (ZZ is received data)
06… A-buffer software sync bit or format code error.
07… B-buffer software sync bit or format code error.
08… Data communication error.
ZZ indicates the data type; AAAA is always 0.
ZZ:
1… Command speed (8408)
2… Laser linear scale value (4413)
3… Backlash (4406)
4… Actual position without position error compensation (440A)
5… Position error compensation value (4403)
6… Fully-closed loop encoder value (4410)
7… Semi-closed loop encoder value (4411)
8… ODIFF (4415)
10… APA (actual position) within section stroke (4404)
11… Acceleration/deceleration time for positioning (4422)
12… Origin offset
13… In-position width (4420)
14… Section stroke maximum value (4405)
15… Point data modification
[Probable Fault Cause]
• MCS controller failure
• Software error
0853 MCS CON-APA deviation
The deviation between CON (command position) and APA (actual position) exceeds the setting value. The deviation between CON and APA (DIFF), also called following error, is the absolute difference between the command position value written to the MCS and the actual position value read from the MCS; the NC control software monitors this deviation during axis movement.
This alarm occurs when a serious inverter unit failure prevents this deviation from being monitored.
[Index]
Axis name
[Character-string]
None
[Code]
Absolute value of deviation in hexadecimal (basic unit)
[Probable Fault Cause]
• MCS inverter unit failure
• Or mismatch between MCS data and NC data
0854 MCS power supply unit error
An error occurred in the power supply unit.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
AAAAXYZZ
AAAA is always 0.
X Alarm No.
0: DC voltage alarm
1: Input voltage error
2: Control power supply error
3: Control status error
4: Regenerative circuit overload
5: Heat sink overheat
6: CPU error
7: Reserved
Y: Power supply unit status
Bit 3 1: Power supply unit failure (alarm signal status is 0)
Bit 2 1: DC applied
Bit 1 1: OPRON input contact closed (axis control ON command)
Bit 0 1: PWON input contact closed (input power supply ON command)
ZZ: Data
When X (Alarm No.): 0... Detected DC voltage in hexadecimal [3.9V]
When X (Alarm No.): 1... Detected AC voltage in hexadecimal [3.1V]
When X (Alarm No.): 2
1: +5V voltage error
2: +12V voltage error
3: -12V voltage error
When X (Alarm No.): 3
1: Converter overcurrent
2: Power module error
3: Converter short-circuit
4: Regenerative circuit error (power regeneration type)
5: Regenerative circuit error (resistor discharge type)
When X (Alarm No.): 4 Undefined
When X (Alarm No.): 5 Undefined
When X (Alarm No.): 6 Undefined
[Probable Fault Cause]
In case of control power supply error:
• Power supply unit
In case of low voltage:
• Low input voltage, power supply failure, blown input circuit fuse, or instantaneous power failure
In case of high voltage:
• Power supply unit
0855 MCS converter link error
An error occurred in the converter link (communication between the power supply unit and the inverter unit), disabling the NC from monitoring the power supply unit status.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XAAAAAYY
AAAAA is always 0.
X=0: Communication error
X=1: Timeout error (communication interrupted)
YY: Communication status
When X=1, YY is 0
[Probable Fault Cause]
• Converter connection cable or connector
• Power supply unit
• Inverter unit control board
0856 MCS DC bus voltage alarm
The DC bus voltage of the inverter unit rose or dropped abnormally, interrupting the power supply.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX: Detected overvoltage value (hexadecimal) [15.3 mV]
XXXX: Detected undervoltage value (hexadecimal) [15.3 mV]
[Probable Fault Cause]
In case of voltage rise:
• Power supply unit
In case of voltage drop:
• Power supply unit
• Inverter unit
• Instantaneous power failure
0857 MCS motor overcurrent
The inverter unit detected overcurrent in the motor winding.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX = U-phase current value detected at alarm occurrence,
expressed as a signed hexadecimal number [Allowable value: 3FFF]
YYYY = V-phase current value detected at alarm occurrence,
expressed as a signed hexadecimal number [Allowable value: 3FFF]
[Probable Fault Cause]
• Inverter unit
• Faulty motor insulation
0858 MCS inverter overheat
The inverter unit detected overcurrent flowing through the motor cable. The inverter unit temperature rose abnormally.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
1 (fixed)
[Probable Fault Cause]
• Inverter unit
• Overload operation
0859 MCS inverter overload
The inverter unit load exceeded the rated value, and the overload protection activated.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
YYYYZZZZ
YYYY-> "GAMMA" protection curve value used to detect overload
ZZZZ-> Internally calculated overload data θ[n]
[Probable Fault Cause]
• Inverter unit
• Overload operation
0860 MCS power supply voltage error
The input power supply voltage of the power supply unit is too high or too low.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
Detected abnormal voltage value in hexadecimal [V]
[Probable Fault Cause]
• Power supply unit
• Power cable or terminal block
• Instantaneous power failure
0861 MCS inverter version error
The rated current value of the inverter unit is smaller than the current limit value specified in the servo data file.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
1 (fixed)
[Probable Fault Cause]
• Inverter unit
• Servo data file
0862 MCS winding changeover error
The magnetic contactor for motor winding changeover did not close.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
YYYYZZZZ
If YYYY=0000
ZZZZ=0001: Low-speed winding changeover contactor closed.
ZZZZ=0002: High-speed winding changeover contactor closed.
ZZZZ=0003: Both high-speed winding changeover contactor and low-speed winding changeover contactor closed simultaneously.
ZZZZ=0004: Winding changeover timeout
If YYYY=1010
ZZZZ =0001: Servo data file error
[Probable Fault Cause]
Winding changeover magnetic contactor
0863 MCS encoder communication error
The speed and position of the controlled axis cannot be detected due to a communication connection error with the position encoder.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX=FF (fixed)
YY=00: Motor encoder detection error.
01: Shaft encoder detection error.
02: Separate encoder detection error.
03: Absolute scale detection error.
ZZZZ= Indicates the encoder connection status when the error occurred.
Indicates the type of each communication error.
Bit 15 1: Communication error with separate encoder
Bit 14 1: Communication error with absolute scale 2
Bit 13 1: Communication error with absolute scale and shaft encoder
Bit 12 1: Communication error with motor built-in encoder
Bit 11 1: Transmission cycle error in auto mode
Bit 10 1: Data overrun error in interface receiver section
Bit 9 Undefined
Bit 8 Undefined
Bit 7 Undefined
Bit 6 1: Modulation code error
Bit 5 1: CRC error
Bit 4 1: Format error
Bit 3 1: Double transmission error
Bit 2 1: Double reception error
Bit 1 1: Parity check error
Bit 0 1: Time-out error
[Probable Fault Cause]
• Motor encoder, absolute scale, shaft encoder, or separate encoder of the relevant axis
• Encoder connection cable or connector
• Inverter unit control board
0864 MCS Encoder error
Motor encoder cannot detect position data.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Encoder error code depending on the encoder type
YY= Encoder status details depending on the encoder type.
ZZZZ= Multi-turn position data. Appears when multi-turn position data exceeds the revolution range.
XX=0 (Fixed)
YY=1 (Fixed)
ZZZZ= Multi-turn position data
[Probable Fault Cause]
Motor encoder
0865 MCS Encoder initialization error
An error occurred during initialization of the motor encoder.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Encoder connection sequence number when the error was detected
0: Reset
1: Network address setting
2: Communication basic information request
3: Communication version change
4: Acquisition of device information
5: Parameter change
6: AT (Auto) mode start
YY= Description of error
0: Communication error
1: Transmission start time exceeded
2: Transmission end time exceeded
3: Reception end time exceeded
4: Response address error
5: Response code error
6: Parameter error
ZZZZ= Additional data
YY=0, Encoder connection status "C2ERR" at error occurrence.
YY=1, 2, 3 Transmitted frame information QC2MINF.
YY=4, Network address of responding device.
YY=5, Received frame information QC2RXINF.
YY=6, Alarm cause number caused by parameter.
1= Not all required parameters were received.
2= Basic communication information is not compatible.
3= Multi-turn detection range does not match.
[Probable Fault Cause]
• Motor encoder
• Encoder connection cable or connector
• Inverter unit control board
0866 MCS Shaft encoder error
Shaft encoder cannot detect position data.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
Same as <MCS Encoder error> alarm
[Probable Fault Cause]
Shaft encoder
0867 MCS Shaft encoder initialization error
An error occurred during initialization of the shaft encoder.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
Same as <MCS Encoder initialization error> alarm
[Probable Fault Cause]
• Shaft encoder
• Shaft encoder connection cable or connector
• Inverter unit control board
0868 MCS Absolute scale error
Absolute scale cannot detect position data.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
Same as <MCS Encoder error> alarm
[Probable Fault Cause]
• Absolute scale
• Encoder connection cable or connector
• Inverter unit control board
0869 MCS Absolute scale initialization error
An error occurred during initialization of the absolute scale.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
Same as <MCS Encoder initialization error> alarm>
[Probable Fault Cause]
• Absolute scale
• Encoder connection cable or connector
• Inverter unit control board
0870 MCS Magnetic encoder
Magnetic pulse generator cannot detect motor speed. Or, the number of magnetic encoder gear teeth does not match the data in the MCS data file.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Description of error
A-> Abnormal A-phase voltage.
B-> Abnormal B-phase voltage.
C-> Magnetic encoder data error
Other-> Setting value in servo data file checked at magnetic encoder count overflow (Number of PG teeth * 4 - 1)
YYYY= Additional error data (varies depending on XXXX.)
If XXXX is A, A-phase voltage value appears.
If XXXX is B, B-phase voltage value appears.
If XXXX is C, 0 (fixed) appears.
Other-> Count value detected by magnetic encoder (Number of PG teeth * 4 - 1)
[Probable Fault Cause]
• Faulty magnetic encoder, incorrect wiring, or excessive clearance between magnetic encoder and gear
• Number of magnetic encoder gear teeth does not match data in the servo data file
0871 MCS Resolver alarm
Resolver does not output any signals.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
1 (Fixed)
[Probable Fault Cause]
Faulty resolver, broken wire, or loose contact in wiring connector
0872 MCS Pulse generator count overflow
The count value per revolution of the PG (pulse generator) does not match the specified value in the servo data file.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Servo data file PBU setting value (PG count value per revolution)
YYYY= Actual count value
[Probable Fault Cause]
• Faulty PG
• Number of PG gear teeth does not match data in the servo data file
0873 MCS Motor overheat
Motor temperature has risen abnormally.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
YYYYZZZZ
YYYY=0 (Fixed)
ZZZZ=0010: Motor overheat
ZZZZ=0011: Overheat detected from motor.
ZZZZ=0012: Overheat detected from encoder.
ZZZZ=0013: Overheat detected from both motor and encoder.
[Probable Fault Cause]
• VAC motor fan failure, dirty heat sink, excessively high frequency of forward/reverse rotation and stop
• BL motor
• Motor encoder (Overheat detected by BL motor encoder.)
0874 MCS Servo link error
A communication error occurred in the servo link, and the servo unit cannot receive commands from the NC.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX=0 (Fixed)
YYYY= Bit number indicating communication error type (Servo link error status at error occurrence)
Bit 15 1: Buffer 2B error
Bit 14 1: Buffer 2A error
Bit 13 1: Buffer 1B error
Bit 12 1: Buffer 1A error
Bit 11 1: MT buffer error
Bit 10 1: Relay processing error
Bit 9 1: Data overrun error in interface receiver section
Bit 8 1: Wire breakage error
Bit 7 1: Address pointer error
Bit 6 1: Modulation code error
Bit 5 1: CRC error
Bit 4 1: Format error
Bit 3 1: Double transmission error
Bit 2 1: Double reception error
Bit 1 1: Parity check error
Bit 0 1: Time-out error
[Probable Fault Cause]
• Inverter unit control board
• Servo link cable or connector
• FCP board
0875 MCS Servo link disconnect
The servo link is disconnected, and the servo unit cannot receive commands from the NC.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Disconnected location:
0… Disconnected near the relevant unit
8000… Disconnected before the relevant unit
YYYY= Servo link error status at error occurrence
[Probable Fault Cause]
• Servo link cable or connector
• Inverter unit control board
• FCP board
0876 MCS Servo link protocol error
The NC and inverter unit exchange commands and responses (communication) via the servo link at fixed cycles with a specified protocol. An incorrect protocol or timing causes communication failure between the NC and inverter unit.
[Target]
Axis name or none (spindle)
[Character-string]
None
[Code]
Error description number
1: A-buffer software synchronization error
2: A-buffer format code error
3: B-buffer software synchronization error
4: B-buffer format code error
5: B-buffer block number error
[Probable Fault Cause]
• Inverter unit control board
• NC software error
• Mismatch between inverter unit control board and NC software
• Faulty FCP board
0877 MCS Servo data error
Servo data sent from the NC for initialization or operation does not match the inverter unit.
If this alarm occurs after replacing the inverter unit, the servo data may not match the control unit.
If this alarm occurs after adjusting or modifying servo data, the modification of the servo data may be incorrect.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
XXXXYYZZ
XXXX= Data ID No. of the data that caused the error
YY= Data group No. of the data that caused the error
ZZ= Error contents
1: Setting range over
2: Setting timing error
3: Not transferred
4: Calculation error
5: Other
[Probable Faulty Locations]
• Incompatibility between the servo data file and the inverter unit
• Incompatibility between the inverter unit and the NC software
• Inverter unit control board
• NC software
0878 MCS Command illegal
Commands and responses between the NC and the inverter unit are exchanged via the servo link. Communication fails when a command transferred from the NC to the inverter unit is abnormal or cannot be executed.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
XXXXYYYY
XXXX=
10: Positioning mode: Commanded number of points exceeded
11: Positioning mode: Negative command value
12: Positioning mode: Commanded position too large (e.g., commanded position for rotary axis > 360 degrees:)
13: Positioning mode: R positioning point table not transferred
14: Positioning mode: Non-rotary axis
15: Positioning mode: Not in point group command format
16: Positioning mode: Positioning sub-mode error
21: Parameter change: Number of parameters exceeded specified range
22: Mode: Undefined mode
23: Mode: Positioning/tool path mode condition
24: Coordinate system: Coordinate system specification error
30: In the A-buffer control command for the S-link, an unused "bit data" is turned ON.
31: In the B-buffer control command for the S-link, an unused "bit data" is turned ON.
40: AT (automatic) mode was selected without receiving a time synchronization command.
YYYY= Error data
X: 10 to 16 indicate the positioning sub-mode.
0: Program mode 1: Search mode 2: PH mode 3: Teach mode
[Probable Faulty Locations]
• Incompatibility between the inverter unit and the NC software
• Inverter unit control board
• NC software
0879 MCS CON speed over
The position command increment (SRCON) sent from the NC to the inverter unit exceeded the permissible value.
If this alarm occurs on a positioning axis, the servo data file may be incorrect (because the position command increment is calculated by the inverter unit).
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
Absolute value of position command increment during acceleration/deceleration [(pr/65536)/Tp]
Here, pr= 1 rev of position encoder; Tp= Position control cycle
However, the following codes have specific meanings:
1: An error was detected during pre-check because the position increment value was too large.
2: The position command value (SRCON) exceeded the absolute value of the encoder measurement range (linear axes only).
[Probable Faulty Locations]
• Servo data file
• NC software
0880 MCS Velocity command overflow
The velocity command value sent from the NC to the inverter unit exceeded the limit value.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
Velocity command value [(rev/4294967269)/Tv]
rev= 1 motor rev; Tv= Velocity control cycle
[Probable Faulty Locations]
• Servo data file
• NC software
0881 MCS DIFF overflow
The positioning error caused during axis movement is too large.
When an axis reaches the target position or stops, the target position value and the calculated value are the same. When a new axis movement command starts execution, the NC begins calculating the command value (RCON)
for the target value, and this calculation does not end until the target position is reached. During axis movement, there is a certain delay of the actual position relative to the commanded position; this difference is called "following error".
An alarm is generated when the following error exceeds the set value.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
Absolute value of following error [pr/65536]
pr= 1 rev of position encoder
[Probable Faulty Locations]
• Overload due to ballscrew or bearing failure
• Motor
• Inverter unit
• Servo data file
0882 MCS APA speed overflow
The position encoder count value (RAPA) changes as the motor rotates.
The NC periodically checks the change in the position encoder count value.
This alarm occurs when the amount of change per unit time exceeds the set permissible range.
For example, this alarm occurs when an axis feedrate is abnormally higher than the normal rapid traverse rate, or when the count value changes abnormally due to a position encoder failure.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
Amount of change in position detection value within one position control cycle (absolute value) [position encoder 1/65536 rev/position control cycle]
The following code values have specific meanings:
1= Linear axis overtravel.
2= Rotary axis overtravel (360 degrees), or position data of limited axis is negative.
3= Limited axis overtravel.
[Probable Faulty Locations]
• Motor encoder (BL motor)
• Encoder connection cable or connector (BL motor)
• PG or magnetic encoder (VAC motor)
• PG or magnetic encoder connection cable or connector (VAC motor)
• Inverter unit control board
0883 MCS Full-closed APA error
The difference between the position detection value of the full-closed loop encoder and that of the motor encoder exceeded the permissible range.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
Number of detected errors
[Probable Faulty Locations]
• Synchronous offset data of the full-closed loop encoder is not set or data setting is incorrect.
• Absolute scale or axis encoder
• Drive system lost motion is too large (motor and moving parts are not rigidly connected)
• Axis timing belt teeth missing or belt broken
• Loose coupling between motor and ballscrew
• Position loop gain is abnormal (too high)
0884 MCS Velocity too high
The actual motor speed is too high.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
Velocity detection value when alarm occurred [(rev/4294967296)/Tv]
rev= 1 motor rev; Tv= Velocity control cycle
[Probable Faulty Locations]
• Motor encoder (BL motor)
• Encoder connection cable or connector (BL motor)
• Resolver or magnetic encoder (VAC motor)
• Resolver or magnetic encoder connection cable or connector (VAC motor)
• Inverter unit control board
0885 MCS Velocity deviation over
The deviation between the actual motor speed and the commanded speed is too large.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
XXXXYYYY
XXXX: Detected torque (sum of torque data collected over 3.2 ms)
2^-12[MAXTRQ]
When Tv=0.4 ms, the instantaneous maximum torque is H’FFFF (hexadecimal).
When Tv=0.8 ms, the instantaneous maximum torque is H’3FFF (hexadecimal).
YYY: Detected acceleration (average value over 3.2 ms)
2^-16[vr/3.2ms/3.2ms]
= approx. 0.1 [rpm/ms]
When 00000001, it indicates that the data at the time of error became zero due to exponent underflow.
[Probable Faulty Locations]
The motor cannot rotate due to mechanical failure or excessive load.
0886 MCS Collision detection
Using the NC torque limit function, the relationship between motor output torque and acceleration is monitored to determine whether a collision has occurred.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
XXXXYYYY
XXXX: Detected torque (sum of torque data collected over 3.2 ms)
2^-12[MAXTRQ]
When Tv=0.4 ms, the instantaneous maximum torque is H’7FFF (hexadecimal)
When Tv=0.8 ms, the instantaneous maximum torque is H’3FFF (hexadecimal)
YYYY: Detected acceleration (average value over 3.2 ms)
2^-16[vr/3.2ms/3.2ms]
= approx. 0.1 [rpm/ms]
[Probable Faulty Locations]
• Collision
• Motor encoder
• NC torque limiter setting value
0887 MCS Emergency stop timeout
After the emergency stop command was received, the axis did not stop within the preset time.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
XXXXXXXX
1: Emergency stop timeout
2: Deceleration time exceeded during emergency stop
3: Deceleration time exceeded during alarm stop
[Probable Faulty Locations]
• Inverter unit control board
• NC software
0888 MCS Belt broken
The belt of the belt-driven axis is broken.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
Load torque when belt broke (hexadecimal)
[Probable Faulty Locations]
Belt broken
0889 MCS Axis changeover control error
Axis control does not operate correctly. (This alarm is not generated in the MCS.)
[Object]
Switched axis name
[Character String]
None
[Code]
The MCS was not reset within 10 seconds.
The parameter group No. match signal or control ready complete signal did not turn ON within 210 seconds.
The APA maximum value of the independent encoder could not be received within 310 seconds.
Modification of in-position width or origin offset was not completed within 610 seconds.
Modification of in-position width or origin offset was not completed within 10 seconds after the alarm.
[Probable Faulty Locations]
• MCS controller for PLC axis
• Software error
0890 MCS Independent encoder initialization error
An error occurred during MCS independent encoder initialization.
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
Same as alarm No. 865 "MCS encoder initialize error".
[Probable Faulty Locations]
• Separate encoder
• Encoder connection cable or connector
• Inverter unit control board
0891 MCS APA error
An error occurred during APA calculation.
[Object]
Axis name or none (spindle)
[Code]
XXXXXXXX
1: Linear axis stroke over
2: Overflow during [pr]->[pf] conversion at semi-closed position
3: Underflow occurred during composite axis data calculation
4: Overflow occurred during composite axis data calculation
5: Overflow occurred at mixed control input
6: Overflow occurred during mixed control initialization
[Probable Faulty Locations]
• Motor encoder, on-axis encoder, or absolute scale
• Inverter unit control PCB
• Servo data file
Pay special attention when the following alarm data appears:
1, 3: Fault in encoder (or sensor) zero-point offset data.
4: Mostly caused by a fault in the servo data file.
5, 6: Mostly caused by a loose motor coupling.
0892 MCS Motor overload
The overload protection functioned because the motor load exceeded the specified value.
[Object]
Axis name or none (spindle)
[Code]
YYYYZZZZ
YYYY: GAMMA curve of protection for overload detection
ZZZZ: Integrated data of overload detection
[Probable Faulty Locations]
• Motor
• Overload during operation
• Servo data file
0992 PLC backup data file read
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 Faulty Locations]
• If the alarm occurs while the NC is operating normally, the file may have been deleted or the file contents corrupted.
• If this alarm occurs before the NC operates after the control software is initialized, the file type may be incorrect or the file may not be stored in memory.
[Measures to Take]
• In case 1), reinstall the control software.
• In case 2), check the control floppy disk data and remake the floppy disk.
0996 PLC axis data file
Control constant data of the PLC axis does not match the machine.
[Object]
None
[Character-string]
PLC axis name
[Code]
1->The axis name downloaded from the PLC axis data file does not match the actually installed axis name.
2->The file type is not "PBU1".
3->The DB size of the file is too large.
4->Specification data in the PLC axis data file differs from specification data in the SVP data file.
5: There is no memory location table for axis backup data in the PLC axis data file.
6: There is no memory location table for axis parameters in the PLC axis data file.
7: An error occurred when opening the PLC axis data file, the file is short, or the file name or device name is incorrect.
8: Although the axis name in the PLC axis data file is OKUMA standard specification, it does not match the registered name.
9: The PLC axis data file is too small.
15: For OSP7030/OSP730, the number of PLC axes exceeds 8.
16: For OSP7030/OSP730, the PLC axis number exceeds 8.
17: For OSP7030/OSP730, although the axis changeover specification is set, the rotary axis gear ratio data of the drive axis is 0.
18: For OSP7030/OSP730, although the axis changeover specification (function generation spec B bit 0) is set, the rotary axis gear ratio data of the driven axis is 0.
19: For OSP7030/OSP730, although the axis changeover specification (function generation spec B bit 0) is set, the pitch data of the drive axis is 0.
1A: For OSP7030/OSP730, although the axis changeover specification (function generation spec B bit 0) is set, the pitch data of the driven axis is 0.
1B: For OSP7030/OSP730, although the point positioning specification (function generation spec B bit 6) is set, the rotary axis specification (servo data file) is not set.
1C: For OSP7030/OSP730, although the arbitrary point positioning specification (function generation spec B bit 7=1) is set, the linear axis specification (servo data file) is not set.
1D: For OSP7030/OSP730, the drive axis with a separate position encoder is not found, or the drive axis is not set.
1E: For OSP7030/OSP730, the drive axis with a separate position encoder is designated as a compound axis.
1F: For OSP7030/OSP730, the detected speed of the separate encoder axis is 0 (this data is set by MCS at power-on).
20: For OSP7030/OSP730, the rotary axis gear ratio (EQGDT ), or the conversion coefficient (ESRGDT) for the axis with separate encoder is not set (setting value is 0).
[Probable Faulty Locations]
• Error when generating the PLC axis data file
• Sudden power off during axis changeover operation (alarm code 21).
0997 PLC monitor backup data file read
PLC monitor backup data cannot be read from memory.
[Code]
1->No file, or file name error.
2->File cannot be opened.
3->File cannot be read (no file data).
4->The specified file is not a backup file.
5->File cannot be closed.
6->File size is small.
7->File size is large.
[Probable Faulty Locations]
• If the alarm occurs while the NC is operating normally, the file may have been deleted or the file contents corrupted.
• If this alarm occurs before the NC operates after the control software is initialized, the file type may be incorrect or the file may not be stored in memory.
[Measures to Take]
• In case 1), reinstall the control software.
• In case 2), check the control floppy disk data (such as file names) and remake the floppy disk.
0998 PLC sequence program load
Loading of the PLC program file failed.
[Code]
PLC program file load status (hexadecimal)
1->The file ends without loading any characters.
3->The file ends during loading.
9->Device name error
A->File name error
B->File does not exist.
100->PLC machine type error
200->PLC rank error
300->File version error