OSP-P300M
OSP-P300M Chapter 2 Alarm and Error List (Alarm P)
0700 NC startup error
An error occurred during NC startup.
[Index]
None
[Character-string]
None
[Code]
0x10000000: NC configuration file (CONF-NC.OSF) read error
0x10003000: Spec code file read error
0x2000XXXX: SVDN initialization error
XXXX:
0x8001: SVDN1 (interrupt board) not found.
0x8002: Two SVDN1 (interrupt boards) exist.
0x8003: SVDN mapping failed.
0x30000000: No thread pitch data file
0x3XXX00YY: NC data file read error
XXX:
0x002: HD backup status file
0x004: Low-speed backup data file
0x008: High-speed backup data file
0x010: PLC variable data file
0x020: PLC-HMI backup file
0x040: Alarm history file
0x080: PLC axis backup data file
0x100: POT&TOOL data file (M/C only)
0x200: MOP TOOL tool data file (M/C only)
0x400: MOP TOOL parameter file (M/C only)
0x410: Synchronized tapping data file
0x420: Thermal deformation compensation V2 data file
0x430: Thermal deformation compensation M2 data file
0x440: Geometric error compensation system constant data file
0x500: Alarm message file
0x540: Alarm A category definition file
0x600: Error message file
0x700: Layout information file
0x800: PPC data file (M/C only)
0x900: Collision avoidance system backup data file
0xA00: I-MAP-C data file
0xB00: P300M backup data file (MEOP*.PBU)
0xB01: P300M tool shape data file (MEGF*.PBU)
0xB02: P300M Advanced One-Touch IGF data file (MERK*.PBU)
0xB10: P300M TOOL-ID data file (MTLID01*.PBU)
0xB20: Machining monitor function data file (MWTH*.PBU)
0xD00: Volumetric error compensation function data file (SPATIALCOM*.PBU)
0xE00: Machining center M-i data file (MVAUTF*.PBU)
0xE10: Machining center M spindle speed variation control data file (MSSVC*.CNS)
0xF00: Newly generated error compensation function data file (MNCPNP*.PBU)
0xF10: PLC axis pitch error compensation function data file (PLCPSP*.PBU)
0xFFF: B-No. data file (MNCPZ*.PBU)
YY:
0x01: File read/open error
0x02: File read error
0x03: Version check error
0x04: Checksum error
0x05: Re-checksum
0x06: Backup memory error
0x07: File write/open error
0x08: File write error
0x09: Memory search error
0x0A: Axis name is not A to C (newly generated error compensation function data file).
Number of transfer points is ”0″ (new error compensation function data file)
Compensation pitch is ”0″ (new error compensation function data file)
0x0B: Alarm number out of range. (Alarm A category definition file)
0x0C: Format error (Alarm A category definition file)
0x0D: Data error (New error compensation function data file)
0x0E: Multiple files with the same axis name exist (New error compensation function data file)
0x0F: No axis group matching rotary axis system parameters (Geometric error compensation system constant data file)
0x10: Value of geometric error system is out of range (Geometric error compensation system constant data file)
0x11: Backup variable/structure size exceeds backup range.
0x40000000: Axis information initialization error
The number of usable axes is 8 or more.
0x40000001: The specified number of additional axis names is less than the number of control axes.
0x4000XXYY: Error in IMC preset data. (For OSP-P1)
XX: IMC number -1
YY:
0x01: IMC name is duplicated.
0x02: IMC spec and axis spec are different.
0x03: Servo ID number is invalid.
0x04: Servo ID number is duplicated.
0x05: Axis name is duplicated.
0x07: Inclination range of parallel axis is invalid.
0x08: Encoder parameter is invalid.
0xFF: Number of axes exceeded. (>8)
0x4000FXXY: Axis ID number definition file read error
XX: Line number
Y:
0x1: File open error
0x2: File read error
0x3: Axis name character error number
0x4: Axis ID number acquisition error
0x5: Axis ID number range error
0x6: Target number error
0x7: Channel number error
0x8: Channel number range error
0x9: Additional axis ID definition error
0x50000000: PLC data file read error
Failed to read M-code data file (”MCDTF” file in CONF-NC.OSF).
0x6000XYYY: I/O connection initialization error
X:
X = 0: PLC variable data file (“PLCVF” file in CONF-NC.OSF)
YYY:
1: File read/open error
2: File read error
3: Version check error
X = 1: Input/output forced ON/OFF master data file (”PLCMSKF” file in CONF-NC.OSF)
YYY:
1: File read/open error
2: File read error
0x70000000: Servo link initialization error
0x80000000: Run buffer search error
0x90000000: PBU data file read error
0xA0000000: Shared memory capacity definition error
0xA1XXXXXX: AlarmService startup error
XXXXXX: AlarmService library function error code
0xA2400002: Alarm history read error
0xA3000000: Thread monitor initialization error
0xA400XYYY: DeviceNet definition file read error
X:
X = 0: DeviceNet definition file read error (”DNCOMF” file in CONF-NC.OSF)
YYY:
1: No file is specified.
2: File read/open error
3: File read error
4: File attribute error
(Scan list or I/O address conversion file is not in little-endian format.)
5: File data error (Effective range of I/O address conversion file exceeds 1KB.)
X = 1: DeviceNet scan list change file read error (“DNCHGF” file in CONF-NC.OSF)
YYY:
1: No file (The file specified by “DNCHGF” in “CONF-NC.OSF” was not found.)
2: File read/open error
3: File read error
4: File attribute error (Not little-endian)
5: File attribute error (File type is not “PBU1″.)
6: File size error (File too small)
7: File size error (File too large)
X = 2: MTB screen I/O address conversion data file read error (“MTBIODF” file in CONF-NC.OSF)
YYY:
1: No file is specified.
2: File read/open error
3: File read error
4: File attribute error (Not little-endian)
5: File attribute error (File type is not “PBU1″.)
6: File data error (Effective range of MTB screen I/O address conversion data file exceeds 1KB.)
0xA500XXXX: System I/O file read error (“SYSIOF” file in CONF-NC.OSF)
XXXX:
1: No file is specified.
2: File read/open error
3: File read error
4: File attribute error (Not little-endian)
5: File data error (Sum of I buffer and O buffer capacities exceeds 440B.)
0xA6000000: If non-compensation spec is valid, the main board is not of non-compensation type.
0xA7000000: In GOT-HMI spec, data definition count of LGOTHMI*.DAT exceeds 1024.
0xA9000000: Safety controller safety logic initialization process was not completed within 20 seconds.
0xA9000001: Failed to open axis structure file under new European safety standards.
0xA9000002: Failed to load axis structure file under new European safety standards.
0xA9000003: Incorrect axis structure under new European safety standards.
0xFFFF0001: SYNC1 remains invalid after setting SVDN SYNC1 setting register for a certain period. (SVDN error)
0xFFFF0002: WDCLK remains invalid after setting SVDN WDCLK setting register for a certain period. (SVDN error)
0xFFFFFFFF: DEBUG information file read error
0701 P100-Menu initialize failed
An error was detected in P100-Menu during system startup.
(OSP-P1) An error was detected in P1-Menu during system startup.
[Index]
None
[Character-string]
None
[Code]
1: No NC Control execution file.
(OSP-P1) No Motion Control execution file.
2: No PLC Control execution file.
3: No NC-HMI execution file.
(OSP-P1) No System HMI execution file.
4: No 3D Virtual Graphic execution file.
5: No MacMan executable file.
No (OSP-P1) MTB Control 2 executable file.
6: P100-Menu and PLC Control version mismatch.
7: P100-Menu and MacMan version mismatch.
8: P100-Menu and NC Control version mismatch.
11: Failed to load Conf-P100-menu.csv.
12: An RTOS error occurred.
13: An error occurred in USP service.
21: Failed to start NC Control.
Failed to start (OSP-P1) Motion Control.
22: Failed to get shared object.
23: Failed to start PLC Control.
24: Failed to start NC-HMI.
Failed to start (OSP-P1) System HMI.
25: Failed to start 3D Virtual Monitor.
Failed to start (OSP-P1) MTB Control 1.
26: Failed to start MacMan.
Failed to start (OSP-P1) MTB Control 2.
101: Failed to receive startup sequence 0x10.
200: Failed to send startup sequence 0x10.
201: Failed to receive startup sequence 0x20.
300: Failed to send startup sequence 0x20.
301: Failed to receive startup sequence 0x30.
400: Failed to send startup sequence 0x30.
401: Failed to receive startup sequence 0x60.
500: Failed to send startup sequence 0x60.
501: Failed to receive startup sequence 0x70.
600: Failed to send startup sequence 0x70.
601: Failed to receive startup sequence 0x70.
700: Failed to send startup sequence 0x7c.
701: Failed to start AlarmService.
702: Failed to receive startup sequence 0x80.
E001: No MTB Control 3 executable file. (OSP-P1)
E002: Failed to start MTB Control 3. (OSP-P1)
F001: No EDOS executable file. (OSP-P1)
F002: Failed to start EDOS. (OSP-P1)
80001: Alarm service error (OSP-P1)
80002: Hardware exception (OSP-P1)
[Probable Fault Sites]
1) Executable file name error
2) Data file error
3) RTOS error
4) UPS function error
5) Software error
6) Version mismatch between P100-Menu and applications.
(OSP-P1) Version mismatch between P1-Menu and applications.
0702 Power failure signal active
A power failure error occurred at system startup.
[Index]
None
[Character-string]
None
[Probable Fault Sites]
1) A power failure error occurred at system startup
2) Power was turned off at system startup
0703 Load info file not found
The download info file was not found.
[Index]
None
[Character-string]
None
[Code]
None
0704 File illegal load
The target file was not downloaded properly.
[Index]
None
[Character-string]
None
[Code]
1: File not found
2: Incorrect file attribute
3: Incorrect file download address info
4: An error occurred during file download
FFFFFFFF: Detailed alarm information is displayed as OS information
0705 Default schedule table error
An error was detected in the default schedule table.
[Index]
None
[Character-string]
None
[Code]
0x00010001: RTIN default schedule table error (element number)
0x00010002: RTIN default schedule table error (end element)
0x00020001: TSMN default schedule table error (element number)
0x00020002: TSMN default schedule table error (initial attribute)
[Probable Fault Sites]
1) NC software error
0706 Backup data file error
An error occurred while reading/writing the backup file.
[Index]
None
[Character-string]
None
[Code]
XXXXYYYY
XXXX: Corresponding data file
0002: HD backup status file
0004: Low-speed NC backup data file
0008: High-speed NC backup data file
0010: PLC variable data file
0020: PLC-HMI backup data file
0040: Alarm history data file
0080: PLC axis backup data file
0100: POT&TOOL data file (M/C only)
0200: MOP TOOL tool data file (M/C only)
0400: MOP TOOL parameter data file (M/C only)
0420: Thermal deformation compensation V2 data file
0430: Thermal deformation compensation M2 data file
0440: Geometric error compensation system parameter data file
0800: Thermal deformation compensation data file (lathe only)
0900: Collision avoidance system backup data file
0A00: I-MAP-C data file
0B00: P300M backup data file
0B01: P300M tool shape data file
0B02: P300M One-Touch IGF ADV data file
0B10: TOOL-ID data file
0B20: Machining monitor function data file
0C00: Pitch error compensation data file
0C10: I/O link function data file
0C20: Kit periodic maintenance data file
0E00: Machining vibration auto control function adaptive control result history data file
0F10: PLC axis pitch error compensation data file
0FF4: Log function PBU data file
0FFF: B data file
YYYY: Error cause
1: File read/open error
2: File read error
3: Version check error
4: Checksum error
5: Re-checksum error
6: Backup memory check error
File size is not appropriate for the NC software version. (File is small.)
Data file structure is destroyed.
7: File write/open error
8: File write error
[Probable Fault Sites]
1) PBU backup file
0707 DTL link/unlink error
An error occurred during DTL link or unlink.
[Index]
None
[Character-string]
None
[Code]
1: RTIN refresh error
2: TSMN refresh error
[Probable Fault Sites]
1) Hardware error
2) Software error
0708 RT thread stack overflow
An RT thread stack overflow was detected.
[Index]
None
[Character-string]
Faulty RT thread name
[Code]
None
[Probable Fault Sites]
1) NC software error
0709 Hardware exception
A hardware exception occurred.
[Index]
None
[Character-string]
Faulty RT thread name
[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 (NPX) error
0x8108: Double fault
0x8109: Unknown device error
0x810A: Invalid TSS error
0x810B: Segment not present error
0x810C: Stack fault
0x810D: General protection fault
0x810E: Page fault
0x8110: Unknown device error
0x8111: Alignment check error
[Probable Fault Sites]
1) Hardware error
2) Software error
[Notice]
Alarm information is also displayed on the control window.
0710 System call error
A system call error occurred.
[Index]
None
[Character-string]
Faulty RT thread name
[Code]
XXXXYYYY
XXXX: RTOS system call code
YYYY: Return value or RTOS system call status
[Probable Fault Sites]
1) NC software error
[Notice]
Alarm information is also displayed on the control window.
0711 AlarmService library error
An error occurred in the AlarmService library function.
[Index]
None
[Character-string]
Faulty RT thread name
[Code]
XXYYYYYY
XX: AlarmService library function code
YYYYYY: AlarmService library function error code
[Probable Fault Sites]
1) NC software error
[Notice]
Alarm information is also displayed on the control window.
0712 AlarmService internal error (exception)
An internal error occurred in AlarmService.
[Index]
None
[Character-string]
ALMS
[Code]
AlarmService internal error code
[Probable Fault Sites]
1) NC software error
[Notice]
Alarm information is also displayed on the control window.
0713 AlarmService inactive
AlarmService error.
[Index]
None
[Character-string]
None
[Code]
None
[Probable Fault Sites]
1) NC software error
0714 Blue Screen
A blue screen (stop error) occurred.
[Index]
None
[Character-string]
None
[Code]
None
[Probable Faulty Locations]
1) Win32 application error
2) Windows error
3) Windows driver error
0715 P100-Menu error
P100-Menu error was detected.
[Index]
None
[Character-string]
None
[Code]
None
[Probable Faulty Locations]
1) P100-Menu error
0716 Floating-point exception
Floating-point error occurred.
[Index]
None
[Character-string]
RT thread name where the error occurred
[Code]
XXXXYYZZ
XXXX: Error code
YY: Cannot be used (Fixed to 0)
ZZ: FPU status word
Bit 5: PE (Precision error flag)
Bit 4: UE (Underflow error flag)
Bit 3: OE (Overflow error flag)
Bit 2: ZE (Zero divide error flag)
Bit 1: DE (Denormalized operand error flag)
Bit 0: IE (Invalid operation error flag)
[Probable Faulty Locations]
1) NC software error
0717 PLC Control error
PLC Control error occurred.
[Index]
None
[Character-string]
None
[Code]
XXXXYYYY
XXXX: PLC Control status
Failed to obtain PLC program file.
YYYY: PLC Control error code
[Probable Faulty Locations]
1) PLC software error
0718 Real-time thread timeout
Real-time thread was not completed within the fixed time.
[Index]
None
[Character-string]
RT thread name exceeding the fixed time
[Code]
None
[Probable Faulty Locations]
1) NC software error
0719 HXCP thread error
Abnormal condition was detected in the HXCP thread.
[Index]
None
[Character-string]
None
[Code]
None
[Probable Faulty Locations]
1) NC software error
0720 AlarmService internal error
AlarmService internal error occurred.
[Index]
None
[Character-string]
ALMS
[Code]
AlarmService internal error code
[Probable Faulty Locations]
1) NC software error
0721 DeviceNet error
DeviceNet error occurred.
[Index]
None
[Character-string]
CH* SC$
*: Channel number where error occurred
$: Sequence counter
[Code]
XXYYZZZZ
XX: MacID of slave station where error occurred
YY: Error status of slave station XX
0x00: Normal or no slave station
0x46: Duplicate MacID error
0x48: Communication stopped
0x49: Identification information incompatible with scan list
0x4D: Data size incompatible with scan list
0x4E: Connection check no response
0x4F: No other slave stations exist on the network
0x50: Idle condition
0x53: Connection check reception error
0x54: Connection check timeout occurred
0x56: Switched to idle mode
0x5B: Bus-off
0x5C: Network power off
(If not caused by a slave station, such as a communication relay, 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 status error
Bit 7: Memory parity error
Bit 8: Input data reception error (single)
Bit 9: Input data reception error (double)
Bit 10: Output data transmission error (single)
Bit 11: Output data transmission error (double)
Bit 12: Slave communication relay error (single)
Bit 13: Slave communication relay error (double)
Bit 14: Bus-off
Bit 15: Diagnostic information entry error
[Probable Faulty Locations]
Hardware fault
Software fault
0725 M-code data file
The read M-code data file contains invalid data.
[Index]
None
[Character-string]
Displays the M-code containing invalid data.
[Code]
1 -> Abnormal cancel data
[Measures to Take]
Correct the target M-code data.
0726 Safe speed data illegal
Safe speed data in the CE mark safe speed monitoring is abnormal.
[Index]
None
[Character-string]
None
[Code]
X
1: Safe speed data guard number is not 0 through 9.
[Measures to Take]
Replace the safe speed monitoring data file for axis control.
0727 MCS firmware does not match POS2.
MCS firmware is incompatible with the new POS unit.
When the new POS unit is installed, the MCS firmware ROM version used for the NC axis/machine (PLC) axis MIV unit is not version 540 or later.
MCS firmware ROM version is not version 540 or later.
[Character-string]
None
[Code]
None
0728 FL-net illegal
An error occurred during startup of the FL-net board.
[Index]
None
[Character-string]
None
[Code]
Y000XXX
Y:
0
XXXX:
7F00: System error
7F01: Flash memory error
7F02: DRAM test error
7F03: NICE test error
7F04: EEPROM checksum error
7F05: CPU bus error
7F06: Illegal instruction
1
XXXX:
0004: Timeout error of 4 seconds or longer occurred
F
XXXX:
FFFF: FL-net board is not installed
[Probable Faulty Locations]
1) FL-net board error
0729 Software no response detected
Unresponsive software was detected.
[Index]
None
[Character-string]
None
[Code]
Name of the unresponsive software.
4E484D49:NHMI-> NC-HMI
4D41434D:MACM-> MACMAN
414E494D:ANIM-> SIMULATION
414C4D4E:ALMN-> ALARM MONITOR
5348544D:SHTM-> SHUT DOWN MONITOR
4E435741:NCWA-> NC WATCHER
5646554E:VFUN-> VERTICALLY-ARRANGED FUNCTION KEY
45425657:EBVW-> EASY OPERATION SCREEN
4542574E:EBWN-> EASY OPERATION SCREEN
57475549:WGUI-> COLLISION AVOID SYSTEM
57494E47:WING-> COLLISION AVOID SYSTEM
49474641:IGFA-> ADVANCED ONE TOUCH IGF
50524F54:PROT-> ADVANCED ONE TOUCH IGF
54454454:TEDT-> TOOL DATA EDIT
4558544E:EXTN-> EXTENDED OPERATION AREA
[Probable Faulty Locations]
1) NC software error
0730 NC download or startup error
0731 R Spec. illegal
An error was found in R specifications.
[Index]
None
[Code]
1: \"NC spec code non-R spec: OFF\" and \"SVDN board ID R spec: Invalid\"
2: \"NC spec code non-R spec: ON\" and \"SVDN board ID R spec: Valid\"
3: \"When two SVDN boards are installed, the R spec is valid on one SVDN board and invalid on the other.\"
4: \"NC spec code non-R spec: OFF\" and \"SVDN board ID R spec: Valid\", limit spec is valid
4X: \"NC spec code non-R spec: OFF\" and \"SVDN board ID R spec: Valid\", and any of the following specs is valid.
X=1: Number of NC control axes (1 deg/5 deg indexing rotary axis / excluding W-axis) is 5 or more.
X=2: 0.1 micrometer spec exists.
X=3: Inductosyn axis exists among the NC linear axes.
5: \"NC spec code non-R spec: ON\" and \"NC spec code non-RII spec: OFF\"
6: MCS firmware version is not ICBH618 or MCS31669 or later, and ”NC spec code non-RII spec: OFF”.
0732 Backlash compensation illegal
0735 MCS DD encoder communication error
An error occurred during encoder link communication.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX=$FF: Fixed
YY=$00: DD encoder error was detected.
$01: DD encoder (slave sensor) error was detected.
ZZZZ= Encoder link status when error was detected
Bit 15: Undefined
Bit 14: Undefined
Bit 13: Communication error of DD encoder (slave sensor)
Bit 12: Communication error of DD encoder
Bit 11: MT buffer error
Bit 10: AT mode transmission loop error
Bit 9: Reception IF section data overflow error
Bit 8: Undefined
Bit 7: Undefined
Bit 6: Modulation code error
Bit 5: CRC error
Bit 4: Format error
Bit 3: Bidirectional transmission error
Bit 2: Bidirectional reception error
Bit 1: Parity error
Bit 0: Timeout error
[Probable Faulty Locations]
– DD encoder or DD encoder (slave sensor) of the relevant axis
– Encoder link cable or connector
– Inverter unit control board
0736 MCS DD encoder error
DD encoder cannot perform detection.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Position detection data status
Bit 7: Error bit (Error when set to 1)
Bit 6: Absolute position sensor gap warning (0: Normal, 1: Alarm)
Bit 5: Pitch warning ("1" when pitch is small; triggered when pitch is large)
Bit 4: Tilt warning ("1" when tilt in reverse direction is large; triggered when tilt in forward direction is large)
Bit 3: Auto setting mode ON. (0: Normal, 1: Auto setting mode)
Bit 2: Communication error (Triggered every time error is detected)
Bits 1, 0: Number of error bits of absolute position code
YY= Alarm code
01: Stopped by stop command
02: Control parameter error
04: Absolutization error
05: Initialization speed error
08: Auto setting data error
0D: Overspeed
0E: Synchronization error
20: Absolute position inconsistency (Format 5 only)
21: Master communication error (Format 5 only)
3E: Absolute position sensor code error
3F: Absolute position code check error
40: Positive side tilt error
41: Negative side tilt error
42: Pitch small
43: Pitch large
ZZZZ=0000 fixed
[Probable Faulty Locations]
Defective sensor unit of DD encoder, magnetization near the sensor unit,
or abnormal temperature rise around the sensor unit.
0737 MCS DD encoder (slave sensor) error
DD encoder (slave sensor) cannot perform detection.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Position detection data status
Bit 7: Error bit (Error when set to 1)
Bit 6: Absolute position sensor gap warning (0: Normal, 1: Alarm)
Bit 5: Pitch warning ("1" when pitch is small; triggered when pitch is large)
Bit 4: Tilt warning ("1" when tilt in reverse direction is large; triggered when tilt in forward direction is large)
Bit 3: Auto setting mode ON. (0: Normal, 1: Auto setting mode)
Bit 2: Communication error (Triggered every time error is detected)
Bits 1, 0: Number of error bits of absolute position code indicated in 2 bits
YY= Alarm code
01: Stopped by stop command
02: Control parameter error
04: Absolutization error
05: Initialization speed error
08: Auto setting data error
0D: Overspeed
0E: Synchronization error
20: Absolute position inconsistency (Format 5 only)
21: Master communication error (Format 5 only)
3E: Absolute position sensor code error
3F: Absolute position code check error
40: Positive side tilt error
41: Negative side tilt error
42: Pitch small
43: Pitch large
ZZZZ=0000 fixed
[Probable Faulty Locations]
Defective sensor unit of DD encoder (slave sensor), magnetization near the sensor unit,
or abnormal temperature rise around the sensor unit.
0738 MCS DD encoder initialization failed
An error occurred during initialization of the DD encoder.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Encoder link initialization sequence number when error was detected (1B)
0: Reset
1: Address setting
2: Request for basic communication information transmission
3: Communication version change
4: Device information acquisition
5: Parameter change
6: Position detection start
7: AT mode start
YY= Error content (1B)
0: Communication error
1: Transmission start time timeout
2: Transmission end time timeout
3: Reception end time timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ= Data (2B)
If YY=0
Encoder link status C2ERR when error was detected
If YY=1, 2, 3
Transmitted frame information QC2MTINF
If YY=4
Address of responding device
If YY=5
Alarm code + Position detection data status
Alarm code
01: Stopped by stop command
02: Control parameter error
04: Absolutization error
05: Initialization speed error
08: Auto setting data error
0D: Overspeed
0E: Synchronization error
20: Absolute position inconsistency (Format 5 only)
21: Master communication error (Format 5 only)
3E: Absolute position sensor code error
3F: Absolute position code check error
40: Positive side tilt error
41: Negative side tilt error
42: Pitch small
43: Pitch large
Position detection data status
Bit 7: Error bit (Error when set to 1)
Bit 6: Absolute position sensor gap warning (0: Normal, 1: Alarm)
Bit 5: Pitch warning ("1" when pitch is small; triggered when pitch is large)
Bit 4: Tilt warning ("1" when tilt in reverse direction is large;
triggered when tilt in forward direction is large)
Bit 3: Auto setting mode ON. (0: Normal, 1: Auto setting mode)
Bit 2: Communication error (Triggered every time error is detected)
Bits 1, 0: Number of error bits of absolute position code indicated in 2 bits
If YY=6
Indicates the parameter number detected as an error.
1: Insufficient number of received parameters
2: Basic communication information incompatibility
3: Multi-turn detection range mismatch
4: Communication protocol version incompatibility
5: Position data format incompatibility
6: Abbreviated data mode incompatibility
[Probable Faulty Locations]
- DD encoder
– Encoder link cable or connector
– Inverter unit control board
0739 MCS DD encoder (slave sensor) initialization failed
An error occurred during initialization of the DD encoder (slave sensor).
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Encoder link initialization sequence number when error was detected (1B)
0: Reset
1: Address setting
2: Request for basic communication information transmission
3: Communication version change
4: Device information acquisition
5: Parameter change
6: Position detection start
7: AT mode start
YY= Error content (1B)
0: Communication error
1: Transmission start time timeout
2: Transmission end time timeout
3: Reception end time timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ= Data (2B)
If YY=0
Encoder link status when error was detected
C2ERR
If YY=1, 2, 3
Transmitted frame information QC2MTINF
If YY=4
Address of responding device
If YY=5
Alarm code + Position detection data status
Alarm code
01: Stopped by stop command
02: Control parameter error
04: Absolutization error
05: Initialization speed error
08: Auto setting data error
0D: Overspeed
0E: Synchronization error
20: Absolute position inconsistency (Format 5 only)
21: Master communication error (Format 5 only)
3E: Absolute position sensor code error
3F: Absolute position code check error
40: Positive side tilt error
41: Negative side tilt error
42: Pitch small
43: Pitch large
44 Position detection data status
Bit 7: Error bit (Error when set to 1)
Bit 6: Absolute position sensor gap warning (0: Normal, 1: Alarm)
Bit 5: Pitch warning ("1" when pitch is small; triggered when pitch is large)
Bit 4: Tilt warning ("1" when tilt in reverse direction is large; triggered when tilt in forward direction is large)
Bit 3: Auto setting mode ON. (0: Normal, 1: Auto setting mode)
Bit 2: Communication error (Triggered every time error is detected)
Bits 1, 0: Number of error bits of absolute position code indicated in 2 bits
If YY=6
Indicates the parameter number detected as an error.
1: Insufficient number of received parameters
2: Basic communication information incompatibility
3: Multi-turn detection range mismatch
4: Communication protocol version incompatibility
5: Position data format incompatibility
6: Abbreviated data mode incompatibility
[Probable Faulty Locations]
- DD encoder (slave sensor)
– Encoder link cable or connector
– Inverter unit control board
0740 Slave MCS Version is different from master
Regarding the synchronized axis interface version, the slave or tandem slave axis version is different from the master axis version.
[Index]
None
[Character-string]
Master axis name
[Code]
None
[Measures to Take]
Set the same MCS version for both the slave axis and the master axis.
0741 MCS software version error
[Index]
None
[Character-string]
Axis name where error occurred, or none.
[Code]
1-> With premium threading specification, the MCS firmware version of the XA-axis is not ICBH590 or later.
2-> MCS firmware version is not MCS31620 or later.
[Probable Faulty Locations]
Specification code error, MCS firmware version error
[Measures to Take]
Reinstall, rearrange installation disks, upgrade MCS firmware version
0742 Machine relocation monitor error
[Index]
None
[Character-string]
ComErr: Communication error
PBU: PBU error
PJ: PJ mismatch
PwdTout: Password application start timeout
PwdChk: Password check
PwdTerm: Password application abnormal end
[Code]
For communication error
Bit 2: Communication error between Atmegas
Bit 1: Communication error with RTC
Bit 0: Relocation module error
For password check
Password check error code
0743 Sub braking unit initialize failed
An error occurred during initialization of the braking unit.
[Index]
Axis
[Character-string]
Error axis name
[Code]
XXYY
XX: Cause YY: CH No.
XX:
1: Regular drive axis and controlled stop axis are in the same link (channel).
2: Failed to obtain communication slave among slaves.
[Measures to Take]
1. Connect regular drive axis and controlled stop axis to the same link (channel).
2. Maximum number of connected axes for the braking axis (excluding this axis) link is 7.
0744 MCS Power Supply Unit over load
The load on the power supply unit exceeded the specified value, and the overload protection (electronic thermal relay) function activated.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXXXXX=1 (Fixed)
[Probable Faulty Locations]
Operation
Conditions
Cutting load torque
Power supply unit
Inverter unit
Motor
0745 MCS drive unit external cooling fan stop
The external cooling fan of the drive unit stopped.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXXXXX=1 (Fixed)
[Probable Faulty Locations]
Fan
Fan power supply connector
0747 MCS drive unit internal cooling fan stop
The internal cooling fan of the drive unit stopped.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXXXXX=1 (Fixed)
[Probable Faulty Locations]
Fan
Fan power supply connector
0748 MCS power supply unit external cooling fan stop
The external cooling fan of the power supply unit stopped.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXXXXX=1 (Fixed)
[Probable Faulty Locations]
Fan
Fan power supply connector
0749 MCS power supply unit internal cooling fan stop
The internal cooling fan of the power supply unit stopped.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXXXXX=1 (Fixed)
[Probable Faulty Locations]
Fan
Fan power supply connector
0750 The spec.-code or select-soft. was wrong.
The NC software does not match the PLC software.
Or composite specification code is abnormal.
[Index]
None
[Character-string]
None
[Code]
1: PLC software does not conform to tool offset 999 sets specification.
2-3: Reserved
4: Cannot be used together with the spindle speed command (unit: 0.1min-1) function.
5: Duplicate PLC axis number.
[Probable Faulty Locations]
Specification code setting error
PLC software version selection error
0752 VDU communication error
An error occurred in communication with the VDU (acceleration sensor unit).
[Index]
Axis
[Character-string]
Provided (VFA)
[Code]
XXYYZZZZ:
XX = FF [HEX] fixed
YY = 00 [HEX] fixed
ZZZZ = E-link error status when error was detected
Bits 15 to 13: Undefined
Bit 12 = 1: VDU communication error in AT mode.
Bit 11 = 1: VDU communication error in MT mode.
Bit 10 = 1: AT mode transmission loop error
Bit 9 = 1: Data volume overflow error in reception IF section
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: Dual transmission error
Bit 2 = 1: Dual reception error
Bit 1 = 1: Modulation code error
Bit 0 = 1: Timeout error
[Probable Faulty Locations]
1) VDU
2) Encoder link cable
3) VFA unit
0753 VDU error
VDU (acceleration sensor unit) cannot be detected.
[Index]
Axis
[Character-string]
Provided (VFA)
[Code]
XXYYZZZZ
XX = VDU status
Bit 7 = 1: Error bit (1 error)
Bit 6 = 1: Vacant bit
Bit 5 = 1: Latest Y-axis acceleration overflow
Bit 4 = 1: Latest X-axis acceleration overflow
Bit 3 = 1: Vacant bit
Bit 2 = 1: Communication error (occurred at error detection)
Bit 1 = 1: Previous Y-axis acceleration overflow
Bit 0 = 1: Previous X-axis acceleration overflow
YY = VDU alarm code
01: Stop command stop
02: Control parameter error
07: User parameter checksum error
0E: Synchronization error
15: X-axis acceleration sensor signal error
16: Y-axis acceleration sensor signal error
17: X/Y-axis acceleration sensor signal error
ZZZZ = 0 fixed
[Probable Faulty Locations]
1) VDU
0754 VDU initialize failed
An error occurred during VDU (acceleration sensor unit) initialization.
[Index]
Axis
[Character-string]
Provided (VFA)
[Code]
XXYYZZZZ
XX = Initialization sequence number at error detection
0: Reset
1: Address setting
2: Communication basic information request
3: Change of communication version
4: Device information acquisition
5: Parameter change
6: AT mode start
YY = Error details
0: Communication error
1: Transmission start timeout
2: Transmission completion timeout
3: Reception completion timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ = Data
When YY = 0
E-link error status at error detection
ZZZZ When YY = 1, 2, or 3
Transmission frame data
ZZZZ When YY = 4
Address of responding device
ZZZZ When YY = 5
Reception frame information
ZZZZ When YY = 6
Indicates error detection parameter number
1: Insufficient number of received parameters.
2: Communication basic information mismatch.
4: Communication protocol version mismatch.
[Probable Faulty Locations]
1) VDU
2) Encoder link cable
3) VFA unit
0755 SIO Link Error
An error occurred in SIO link communication.
[Index]
None
[Character-string]
Refer to the following "Code" description.
[Code]
During constant torque
FFFFFFFF:
The same data was received twice from the safety controller in a regular frame.
XXXXYYYY:
XXXX: Command + data length
0303: Error received in frame 0
1303: Error received in frame 1
04FF: SSIO error status is not 0
YYYY: Error status
Bit 15 -> Error occurred
Bit 14 -> Undefined
Bit 13 -> Undefined
Bit 12 -> Duplicate MAC ID
Bit 11 -> Internal error detected in slave
Refer to "Alarm A 1126" for details
Bit 10 -> Receive buffer capacity setting is too large
Bit 9 -> Disconnection error
Bit 8 -> Modulation code error
Bit 7 -> CRC error
Bit 6 -> Format error
Bit 5 -> Dual transmission error
Bit 4 -> Dual reception error
Bit 3 -> Parity error occurred when SIO controller read transmission buffer
Bit 2 -> Parity error occurred when CPU read transmission buffer
Bit 1 -> Parity error occurred when CPU read reception buffer
Bit 0 -> Timeout error
Character-string: Suffix number of the ID is the address of the slave station where the error was detected
0: MPIF
40: MF-SAFETY
8c: CIO, MACID 70, symbol S570
90: CIO, MACID 72, symbol S572
94: CIO, MACID 74, symbol S574
98: CIO, MACID 76, symbol S576
9c: CIO, MACID 78, symbol S578
a0: CIO, MACID 80, symbol S580
a4: CIO, MACID 82, symbol S582
a8: CIO, MACID 84, symbol S584
ac: CIO, MACID 86, symbol S586
b0: CIO, MACID 88, symbol S588
b4: CIO, MACID 90, symbol S590
b8: CIO, MACID 92, symbol S592
bc: CIO, MACID 94, symbol S594
XXYYZZZZ:
XX is 80.
YY: Cause of configuration detection error
00: Pair file mismatch
01: Duplicate MacID exists.
02: Input bit error
Allocated input bits exceed the specified input range
Character string AABBCCDD: Problematic bit is enabled
For CIO unit
AA: X1 (connector)
BB: X3 (connector)
CC: X5 (connector)
DD: X7 (connector)
For non-CIO unit
AABBCCDD: Bit number from the beginning of input
03: Output bit error
Allocated output bits exceed the specified output range
Character string AABBCCDD: Problematic bit is enabled
For CIO unit
AA: X2 (connector)
BB: X4 (connector)
CC: X6 (connector)
DD: X8 (connector)
For non-CIO unit
AABBCCDD: Bit number from the beginning of output
04: Product code error
Character string AAAABBBB:
AAAA: Product code in PIOD file
BBBB: Product code received at slave station
3570: MPIF-BS-SIOP
3620: MF-SAFETY
3630: CIO-P2M2S
3631: CIO-P3M3S
3632: CIO-P4M4S
B570: MPIF-BS-SION
FF: Communication error
Character string: sts= reception status error, data= reception data error
ZZZZ: Applied error MacID
0000 – 0006: MPIF
XX is not 80.
XX: Frame
YY: Command
00: Reset
01: Data collection
02: Timeout duration setting
05: File transfer
ZZZZ: Cause of error
0007: Time-out occurred while waiting for reception completion
0008: Time-out occurred while waiting for transmission completion
0009: Error status bit 15 ON after reception completion.
000A: Error status bit 15 ON while waiting for reception completion.
000B: Error status bit 15 ON while waiting for transmission completion.
000C: Call during transmission.
000D: Error status other than 0.
000E: Error command received.
000F: Command different from transmission received.
[Probable Faulty Locations]
1. SSIO
2. MF-SAFETY
3. MPIF
4. CIO
5. SIO link cable
6. SIO-DIVIDE
7. Power supply unit or voltage level
When an error occurs during NC initialization and error code ”XX” is 80
8. PIOD file or MAC ID switch setting
0756 PSC Optical scale encoder error
An error was detected in the PSC optical scale position encoder.
[Character-string]
None
[Code]
XXYYZZ
XX: Excessive error between type J position encoder value and optical scale position encoder value
Bit 1: Excessive negative direction signals
Bit 0: Excessive positive direction signals
YY: Optical scale pulse count value
Bit 0: A/B-phase pulses changed simultaneously
ZZ: Optical scale signal amplitude abnormality
Bit 1: B-phase amplitude abnormality
Bit 0: A-phase amplitude abnormality
[Probable Faulty Locations]
1) Optical scale failure
2) Optical scale cable failure
[Measures to Take]
1) Replace the optical scale.
2) Replace the optical scale cable.
0757 MF-SAFETY Error
An abnormality was detected in MF-SAFETY.
[Index]
None
[Character-string]
None
[Code]
When alarm occurs on MF-SAFETY CPU0 side
0x1000XXXX-> CPU exception occurred in MF-SAFETY.
XXXX-> Exception number
0x1100XXXX-> NMI occurred in MF-SAFETY.
XXXX-> NMI occurrence factor
Bit 15-> An error occurred.
Bit 9 -> CPU1 voltage drop.
Bit 8 -> CPU0 watchdog timer overflow.
Bit 1 -> CPU0 voltage drop.
Bit 0 -> CPU1 watchdog timer overflow.
0x1200XXXX-> An abnormality was detected in the MF-SAFETY CPU bus.
XXXX-> CPU ID where error was detected
Bit 15-> CPU ID (0: CPU0, 1: CPU1)
0x130000XX-> MF-SAFETY CPU1 does not respond
XX-> Request number to CPU1
0x160000XX-> CPU0/1 mismatch detected in data processed by MF-SAFETY.
XX-> Processing details
01-> Alarm request
02-> SIO link data communication
0x170000XX-> Steady processing of MF-SAFETY could not be completed within the specified time.
XX-> End time of steady processing (1 bit = 62.5 us)
0x1800XXXX-> Error detected by MF-SAFETY.
XXXX-> Error details
Bit 15-> Error occurred in MFU I/O unit.
Bit 14-> Parity error occurred in MFU I/O bus.
Bit 12-> Unable to synchronize with NC via SIO link.
Bit 11-> Abnormality in SIO link transmission timing setting of MF-SAFETY.
0x19000000-> MF-SAFETY CPU stack usage exceeded the specified amount.
0x1A00XXXX-> Address registered in label table is incorrect.
XXXX-> Label table index
0x1B000000-> NC started in MF-SAFETY software rewrite mode.
0x1C0000XX-> Mode setting mismatch between NC and MF-SAFETY.
XX-> Mismatched item
01-> MF-SAFETY mode setting abnormality.
02-> NC operation mode setting abnormality.
0x1E000000-> Safety logic interface version mismatch.
When alarm occurs on MF-SAFETY CPU1 side
0x9xxxxxxx-> Same as 0x1xxxxxxx
[Probable Faulty Locations]
MF-SAFETY
MF-SAFETY mode setting
NC operation mode setting
MFU I/O unit
[Measures to Take]
Replace the MF-SAFETY unit.
Replace the MFU I/O unit.
Turn OFF all MF-SAFETY switches (SW1).
Correct the MF-SAFETY software (safety logic).
0758 Safety I/O Error
MF-SAFETY detected an I/O communication or input/output error.
[Index]
None
[Character-string]
None
[Code]
When alarm occurs on MF-SAFETY CPU0 side
0x20000000-> CPU0/1 discrepancy detected in safety transmission frame during SIO link initialization.
0x21XX0000-> Command was not received within the specified time during SIO link initialization.
XX-> Command waiting for reception
00-> Reset command
01-> Information collection command
02-> Timeout timer setting command
0x22XXYYYY-> Communication error detected during SIO link initialization.
XX-> Command waiting for reception
00-> Reset command
01-> Information collection command
02-> Timeout timer setting command
YYYY-> Error status of SIO link module
Bit 15-> An error occurred.
Bit 10-> Receive buffer capacity setting is too large.
Bit 9 -> Disconnection error occurred.
Bit 8 -> Modulation code error occurred.
Bit 7 -> CRC error occurred.
Bit 6 -> Format error occurred.
Bit 5 -> Duplicate transmission error occurred.
Bit 4 -> Duplicate reception error occurred.
Bit 3 -> Parity error occurred while reading transmission buffer of SIO link controller.
Bit 2 -> Parity error occurred while reading transmission buffer of CPU.
Bit 1 -> Parity error occurred while reading reception buffer of CPU.
Bit 0 -> Timeout error occurred.
0x23XXYYYY-> Error command received during SIO link initialization.
XX-> Address of slave station that issued the error command
YYYY-> Received error status
Bit 15-> An error occurred.
Bit 10-> Receive buffer capacity setting is too large.
Bit 9 -> Disconnection error occurred.
Bit 8 -> Modulation code error occurred.
Bit 7 -> CRC error occurred.
Bit 6 -> Format error occurred.
Bit 4 -> Duplicate reception error occurred.
Bit 3 -> Parity error occurred while reading transmission buffer of SIO link controller.
Bit 2 -> Parity error occurred while reading transmission buffer of CPU.
Bit 1 -> Parity error occurred while reading reception buffer of CPU.
Bit 0 -> Timeout error occurred.
0x24XX00YY-> Unexpected command received during SIO link initialization.
XX-> Command waiting for reception
YY-> Received command
0x25XX0000-> Safety slave information in SIO link does not match scan file.
XX-> Discrepant frame offset
0x2F000000-> Disconnection error detected in SIO link.
0x31000000-> Safety communication frame was not received within the specified time via SIO link.
0x3200XXXX-> Communication error detected in SIO link.
XXXX-> SIO link error status
Bit 15-> An error occurred.
Bit 10-> Receive buffer capacity setting is too large.
Bit 9 -> Disconnection error occurred.
Bit 8 -> Modulation code error occurred.
Bit 7 -> A CRC error occurred.
Bit 6 -> A format error occurred.
Bit 5 -> A duplicate transmission error occurred.
Bit 4 -> A duplicate reception error occurred.
Bit 3 -> A parity error occurred when reading the transmission buffer of the SIO link controller.
Bit 2 -> A parity error occurred when reading the transmission buffer of the CPU.
Bit 1 -> A parity error occurred when reading the reception buffer of the CPU.
Bit 0 -> A time-out error occurred.
0x33XXYYYY-> An error command was received during safe communication through the SIO link.
XX-> Slave address that issued the error command
YYYY-> Received error status
Bit 15-> An error occurred.
Bit 10-> The reception buffer capacity setting is too large.
Bit 9 -> A disconnection error occurred.
Bit 8 -> A modulation code error occurred.
Bit 7 -> A CRC error occurred.
Bit 6 -> A format error occurred.
Bit 4 -> A duplicate reception error occurred.
Bit 3 -> A parity error occurred when reading the transmission buffer of the SIO link controller.
Bit 2 -> A parity error occurred when reading the transmission buffer of the CPU.
Bit 1 -> A parity error occurred when reading the reception buffer of the CPU.
Bit 0 -> A time-out error occurred.
0x34XX0000-> Failed to establish the safe protocol of the SIO link.
XX-> Slave address
01-03->MPIF
07-20-> CIO
0x35XXYYZZ-> Safe communication cannot be performed after establishing the safe protocol of the SIO link.
XX-> Slave address
01-03-> MPIF
07-20-> CIO
YY-> Error status
00-> A reset command was received.
01-> An illegal command was received.
02-> An undefined command was received.
03-> Connection ID error.
04-> CRC error.
08-> A corrupted safe data command was received.
ZZ-> Received safe data
0x36000000-> CPU0/1 discrepancy detected in SIO link safe transmission frame.
0x37XX0000-> Failed to update SIO link frame.
XX-> Slave address
01-03-> MPIF
07-20-> CIO
0x3FXXYYZZ-> Discrepancy between CPU0 and CPU1 detected in safe physical output.
XX-> Physical output index
YY-> CPU0 output value
ZZ-> CPU1 output value
0x41X000YY-> An error was detected in the MFU I/O unit.
X-> Slot number
YY-> Error status of I/O unit
<MF-EC1>
Bit 7-> Overcurrent protection in the output circuit activated.
Bit 6-> Overcurrent protection in the input circuit activated.
Bit 4-> An error occurred in I/O bus check.
Bit 2-> Transistor command value and monitor value differ.
Bit 1-> A parity error occurred in I/O bus 1 during write.
Bit 0-> A parity error occurred in I/O bus 0 during write.
<MF-P2A16S>
Bit 6-> Overcurrent protection in the input circuit activated.
Bit 5-> An error occurred in self-check.
Bit 4-> An error occurred in I/O bus check.
<MF-P2M2S>
Bit 7-> Overcurrent protection in the output circuit activated.
Bit 6-> Overcurrent protection in the input circuit activated.
Bit 4-> An error occurred in I/O bus check.
Bit 2-> Transistor command value and monitor value differ.
Bit 1-> A parity error occurred in I/O bus 1 during write.
Bit 0-> A parity error occurred in I/O bus 0 during write.
0x42XYZZWW-> Input of MFU I/O unit between CPU0 and CPU1 does not match for longer than the specified time.
X-> Slot number
Y-> Safe input number in I/O unit (1 to 4)
ZZ-> CPU0 input value
WW-> CPU1 input value
0x43XYZZWW-> Values output to MFU I/O unit do not match between CPU0 and CPU1.
X-> Slot number
Y-> Safe input number in I/O unit (1 to 4)
ZZ-> CPU0 output value
WW-> CPU1 output value
0x44XYYZZWW-> Monitor error was detected twice consecutively in MFU I/O unit.
X-> Slot number
Y-> Safe output number in I/O unit (1 to 3); 0 when the monitor error bit position cannot be specified.
Bits 3-2-> 1st time
Bits 1-0-> 2nd time
ZZ, WW-> Monitor error bit position (error position is 1)
ZZ-> 1st time
WW-> 2nd time
However, when XYZZWW=2A0F0F, power is not supplied to MF-EC1 using the EC power supply.
If an alarm occurs on the MF-SAFETY CPU1 side
0xAxxxxxxx-> Same as 0x2xxxxxxx
0xBxxxxxxx-> Same as 0x3xxxxxxx
0xCxxxxxxx-> Same as 0x4xxxxxxx
[Probable Faulty Locations]
SIO link cable
MFU I/O unit
MF-SAFETY
IO data coupling file
Device connected to SIO link
[Measures to Take]
Replace the SIO link cable.
Replace the MFU I/O unit.
Replace the MF-SAFETY.
Correct the IO data coupling file.
Replace the device connected to the SIO link.
0759 Safety Servo Link Error
An error occurred in the safe communication servo link.
[Index]
None
[Character-string]
None
[Code]
0xFFFFXXXX
XXXX-> World clock after safe protocol reset procedure
If an alarm occurs on the MF-SAFETY CPU0 side
0x50000000-> Discrepancy between CPU0 and CPU1 detected in safe transmission frame at servo link initialization.
0x51XX0000-> No frame was received from slave at servo link initialization.
XX-> Axis ID of the corresponding axis
0x520XYYYY-> Communication error detected at servo link initialization.
X-> Servo link channel number
YYYY-> Servo link error status
Bit 15-> An error occurred.
Bit 11-> A protection error occurred.
Bit 9 -> A disconnection error occurred.
Bit 8 -> A modulation code error occurred.
Bit 7 -> A CRC error occurred.
Bit 6 -> A format error occurred.
Bit 4 -> A duplicate reception error occurred.
Bit 3 -> A parity error occurred when reading the transmission buffer of the servo link controller.
Bit 2 -> A parity error occurred when reading the transmission buffer of the CPU.
Bit 1 -> A parity error occurred when reading the reception buffer of the CPU.
Bit 0 -> When receiving buffer B, ID of SA part does not match the ID of the axis configuration register.
0x53XX0000-> No response was returned for longer than the specified time after servo link initialization.
XX-> Axis ID of the corresponding axis
0x54XX0000-> Failed to establish the safe protocol of the servo link.
XX-> Axis ID of the corresponding axis
0x55XXYYZZ-> Safe communication cannot be performed after establishing the safe protocol of the servo link.
XX-> Slave address
YY-> Cause
00-> A reset command was received.
01-> An illegal command was received.
02-> An undefined command was received.
03-> Connection ID error.
04-> CRC error.
08-> A corrupted safe data command was received.
ZZ-> Received safe data.
0x56000000-> Discrepancy between CPU0 and CPU1 detected in safe transmission frame of the servo link.
0x57XX0000-> No frame was received from slave even at servo link initialization.
XX-> Axis ID of the applicable axis
If an alarm occurs on the MF-SAFETY CPU1 side
0xDxxxxxxx-> Same as 0x5xxxxxxx
0xFFFFXXXX
XXXX-> World clock after exchanging safe protocol
[Probable Faulty Locations]
Servo link cable
MF-SAFETY
Device connected to servo link
Axis ID configuration data file
[Measures to Take]
Replace the servo link cable.
Replace the MF-SAFETY.
Replace the device connected to the servo link.
Correct the axis ID configuration data file.
0760 MCS Oil pressure level error
An error was detected in the hydraulic pressure detection value of the hydraulic unit.
[Index]
25:OPU1
26:OPU2
[Code]
XXXXYYYY
XXXX: Pressure command value
YYYY: Pressure detection value
However, it has special meaning for the following data.
FFFFFFFF: Disconnection detected.
[Probable Faulty Locations]
Pressure command value
SDF setting value
Pressure sensor cable
Pressure sensor
Hydraulic unit
0782 Magnetic encoder speed detection error
The difference between the speed feedback value detected by the magnetic encoder and the speed monitored from the current frequency is too large.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY:
XXXX = Detected speed reference value
YYYY = Detected speed value
[Probable Faulty Locations]
Motor or motor wiring
Servo data file
Magnetic encoder or its signal cable
Magnetic encoder gear
Magnetic encoder
0783 MCS Rotary encoder 5 initialization failed
Initialization of rotary encoder 5 (manufactured by other maker) failed.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
Details are not yet determined.
[Probable Faulty Locations]
Rotary encoder 5 (made by other manufacturer)
Encoder link cable or connector
Inverter unit control board
0784 MCS Rotary encoder 5 error
An error was detected by rotary encoder 5 (made by other manufacturer).
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
Details are not yet determined.
[Probable Faulty Locations]
Rotary encoder 5 (made by other manufacturer)
0785 MCS Rotary encoder 4 initialization failed
Initialization of rotary encoder 4 (made by Heidenhain) failed.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
Details are not yet determined.
[Probable Faulty Locations]
Rotary encoder 4 (made by Heidenhain)
Encoder link cable or connector
Inverter unit control board
0786 MCS Rotary encoder 4 error
Rotary encoder 4 (made by Heidenhain) failed to perform detection.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
Details are not yet determined.
[Probable Faulty Locations]
Rotary encoder 4 (made by Heidenhain)
0787 MCS Rotary encoder 3 initialization failed
Initialization of rotary encoder 3 (made by Heidenhain) failed.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= E-link sequence No. when error is detected
0: Reset
1: Address setting
2: Request transmission of communication basic information
3: Communication version change
4: Acquire device information
5: Parameter change
6: Position detection start
7: AT mode start
YY= Error description
0: Communication error
1: Transmission start time timeout
2: Transmission end time timeout
3: Reception end time timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ= Data
If YY=0,
Encoder link status when error is detected
If YY=1, 2, 3,
Transmitted frame information
If YY=4,
Address of responding device
If YY=5,
Received frame information
If YY=6,
Indicates the parameter No. detected as an error.
1: Insufficient number of received parameters
2: Communication basic information incompatible
3: Multi-turn detection range mismatch
4: Communication protocol version incompatible
[Probable Faulty Locations]
Rotary encoder 3 (made by Heidenhain)
Encoder link cable or connector
Inverter unit control board
0788 MCS Rotary encoder 3 error
Rotary encoder 3 (made by Heidenhain) failed to perform detection.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
XX= Rotary encoder 3 status
Bit 7: Alarm
Bit 6: Communication error (EnDat IF side)
Bit 5: Undefined
Bit 4: Undefined
Bit 3: Undefined
Bit 2: Communication error (triggered whenever communication error is detected on Elink side)
Bit 1: Undefined
Bit 0: For alarm judgment (Bit 0=1: Encoder side alarm)
YY= Alarm code of linear scale 1
If XX=81,
Bit 7: Response address error
Bit 6: Undefined
Bit 5: Overcurrent
Bit 4: Low power supply voltage
Bit 3: Overvoltage
Bit 2: Position data error
Bit 1: Signal amplitude error
Bit 0: Scale failure
If XX=80,
43: No response from encoder
44: Encoder ID error
If XX=C0,
10, 20: Gateway reception error
46: CRC error
[Probable Faulty Locations]
Rotary encoder 3 (made by Heidenhain)
0789 MCS Rotary encoder 2 error
Rotary encoder 2 (made by INA Bearing) failed to perform detection.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY:
XXXX= Error description
000A[HEX]: Phase A voltage error
000B[HEX]: Phase B voltage error
YYYY= Error data
If XXXX[HEX]=000A: Phase A voltage value
If XXXX[HEX]=000B: Phase B voltage value
[Probable Faulty Locations]
Rotary encoder 2 (made by INA Bearing)
0790 MCS Rotary encoder 2 initialization failed
An error occurred during initialization of rotary encoder 1 (rotary inductive sensor).
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= E-link sequence No. when error is detected
0: Reset
1: Address setting
2: Request transmission of communication basic information
3: Communication version change
4: Acquire device information
5: Parameter change
6: Position detection start
7: AT mode start
YY= Error description
0: Communication error
1: Transmission start time timeout
2: Transmission end time timeout
3: Reception end time timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ= Data
If YY=0,
Encoder link status when error is detected
If YY=1, 2, 3,
Transmitted frame information
If YY=4,
Address of responding device
If YY=5,
Received frame information
If YY=6,
Indicates the parameter No. detected as an error.
1: Insufficient number of received parameters
2: Communication basic information incompatible
3: Multi-turn detection range mismatch
4: Communication protocol version incompatible
[Probable Faulty Locations]
Rotary inductive sensor
Encoder link cable or connector
Inverter unit control board
0791 MCS Rotary encoder 1 error
Rotary encoder 1 (rotary inductive sensor) failed to perform detection.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Rotary inductive sensor status
Bit 7: Alarm
Bit 2: Communication error
8X: Output amplitude normal
9X: Output amplitude small
AX: Output amplitude large
BX: Output amplitude too small
YY= Alarm code of rotary inductive sensor
00: Not started
01: Stopped by stop command
02: Control parameter error
0E: Synchronization error
0F: Excitation output error
11: Phase B AD offset voltage low
12: Phase A AD offset voltage low
13: Phase A, B AD offset voltage low
15: Phase B AD offset voltage high
16: Phase A AD offset voltage high
17: Phase A, B AD offset voltage high
25: Phase B signal amplitude too large
26: Phase A signal amplitude too large
27: Phase A, B signal amplitude too large
29: Signal amplitude too small
2D: Phase B signal amplitude too small
2E: Phase A signal amplitude too small
2F: Phase A, B signal amplitude too small
80 to FF: CPU error
ZZZZ= Rotary inductive sensor position data
Position data for each pitch
[Probable Faulty Locations]
Rotary inductive sensor
0792 MCS Linear scale 4 initialization failed
An error occurred during initialization of linear scale 4 (made by other manufacturer).
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
Details are not yet determined.
[Probable Faulty Locations]
Linear scale 4 (made by other manufacturer)
Encoder link cable or connector
Inverter unit control board
0793 MCS Linear scale 4 error
Linear scale 4 (made by other manufacturer) failed to perform detection.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
Details are not yet determined.
[Probable Faulty Locations]
Linear scale 4 (made by other manufacturer)
0794 MCS Linear scale 3 initialization failed
An error occurred during initialization of linear scale 3 (made by Heidenhain).
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
Details are not yet determined.
[Probable Faulty Locations]
Linear scale 3 (made by Heidenhain)
Encoder link cable or connector
Inverter unit control board
0795 MCS Linear scale 3 error
Linear scale 3 (made by Heidenhain) failed to perform detection.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
Details are not yet determined.
[Probable Faulty Locations]
Linear scale 3 (made by Heidenhain)
0796 MCS Linear scale 2 initialization failed
An error occurred during initialization of linear scale 2 (made by Heidenhain).
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= E-link sequence No. when error is detected
0: Reset
1: Address setting
2: Request transmission of communication basic information
3: Communication version change
4: Acquire device information
5: Parameter change
6: Position detection start
7: AT mode start
YY= Error description
0: Communication error
1: Transmission start time timeout
2: Transmission end time timeout
3: Reception end time timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ= Data
If YY=0,
Encoder link status at error detection
If YY=1, 2, 3,
Transmitted frame information
If YY=4,
Address of response device
If YY=5,
Received frame information
If YY=6,
Indicates the parameter number detected as erroneous.
1: Insufficient number of received parameters
2: Basic communication information incompatibility
3: Multi-turn detection range mismatch
4: Communication protocol version incompatibility
[Probable Faulty Locations]
Linear scale 2 (manufactured by Heidenhain)
Encoder link cable or connector
Inverter unit control board
0797 MCS Linear scale 2 error
Linear scale 2 (manufactured by Heidenhain) cannot perform detection.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Linear scale 2 status
Bit 7: Alarm
Bit 6: Communication error
Bit 5: Warning level
Bit 4: Check level
Bit 3: Undefined
Bit 2: Communication error (triggered at each detection)
Bit 1: Undefined
Bit 0: Used for alarm judgment (Bit 0=1: Alarm occurred on encoder side.)
YY= Alarm code of linear scale 2
If YY=81,
Bit 7: Response address error
Bit 6: Undefined
Bit 5: Overcurrent
Bit 4: Low power supply voltage
Bit 3: Overvoltage
Bit 2: Position data error
Bit 1: Signal amplitude error
Bit 0: Optical scale failure
If YY=80,
01: Stop command stop
02: Control parameter error
0E: Synchronization error
44: Encoder ID error
If YY=C0,
10, 20: Gateway reception error (others)
46: CRC error
47: Forward timer error
48: Response error. Response data error.
49: Timeout error
ZZZZ= Linear scale 2 position data
Position data per 2mm pitch
[Probable Faulty Locations]
Linear scale 2 (manufactured by Heidenhain)
0798 MCS Linear scale 1 initialization failed
An error occurred during initialization of linear scale 1 (manufactured by Mitutoyo).
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= E-link sequence number at error detection
0: Reset
1: Address setting
2: Request to send basic communication information
3: Communication version change
4: Obtain device information
5: Change parameter
6: Position detection start
7: AT mode start
YY= Error content
0: Communication error
1: Transmission start time timeout
2: Transmission end time timeout
3: Reception end time timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ= Data
If YY=0,
Encoder link status at error detection
If YY=1, 2, 3,
Transmitted frame information
If YY=4,
Address of response device
If YY=5,
Received frame information
If YY=6,
Indicates the parameter number detected as erroneous.
1: Insufficient number of received parameters
2: Basic communication information incompatibility
3: Multi-turn detection range mismatch
4: Communication protocol version incompatibility
[Probable Faulty Locations]
Linear scale 1 (manufactured by Mitutoyo)
Encoder link cable or connector
Inverter unit control board
0799 MCS Linear scale 1 error
Linear scale 1 (manufactured by Mitutoyo) cannot perform detection.
[Index]
Axis or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Linear scale 1 status
Bit 7: Alarm
Bit 6: Communication error
Bit 2: Communication error (triggered at each detection)
Bit 0: Used for alarm judgment (Bit 0=1: Mitutoyo scale side alarm)
YY= Alarm code of linear scale 1
If XX=81,
Bit 7: Overspeed
Bit 6: Communication error
Bit 5: EEPROM error
Bit 4: CPU error
Bit 3: Electrostatic capacitance error
Bit 2: Photoelectric error
Bit 1: Digital matching error
Bit 0: Initialization error
If XX=80,
43: Mitutoyo scale no response
44: Mitutoyo scale ID error
If XX=C0,
00 to 3F: Gateway reception error
46: REQ timeout error
ZZZZ= Linear scale 1 position data
Position data per 2mm pitch
[Probable Faulty Locations]
Linear scale 1 (manufactured by Mitutoyo)
0812 MCS Start
An error occurred during MCS initialization at power-on.
[Index]
None or axis name
[Character-string]
Varies depending on code.
[Code]
XXXXYYYY
XXXX: Type of generated alarm
YYYY: Further information on alarm (varies depending on XXXX.)
XXXX
FFFF…YYYY is 00UV. Where,
U: Faulty channel number - 1
0 = Channel 1
1 = Channel 2
2 = Channel 3
V: Cause of alarm
V = 1 indicates that the servo link mode has not been established.
V = 2 indicates that more than one safe speed monitor is connected to 1 channel.
FF01… A memory error occurred during servo link I/O buffer read/write test.
YYYY = 0 (always)
Character-string indicates the address where the error occurred.
FF00… Communication LSI generated an error during servo link I/O buffer read/write test.
YYYY = Error status
Character-string indicates the address where the error occurred.
F000…
YYYY = Bit 7: Same ID number used
Bit 6: Erroneous ID number
Bit 5: ID number missing
Bit 4: Too many CH4 controllers
Bit 3: Too many CH3 controllers
Bit 2: Too many CH2 controllers
Bit 1: Too many CH1 controllers
Bit 0:
Another monitor displays connection information at the same time.
EF00… Servo link is not connected to all required axes or is connected to a wrong axis.
YYYY = Axis controller ID number
Character-string shows the faulty axis name.
Another monitor displays connection information at the same time.
EE00… An error occurred when downloading an optional file.
High-order digits of YYYY indicate the cause when low-order part is an error code.
If high-order digit =
1: File is not in OSP format.
2: File attributes are not consecutive.
3: File open error; low-order part is an error code.
4: Error in initial data reading; low-order part is an error code.
5: File does not start with ”MCS1″.
6: No ”OPFS” after file name.
7: Number of file groups is zero.
8: Data read error; low-order part is an error code.
9: File data sector length is 0.
A: Transferred bytes are zero.
B: File data sector length is smaller than transferred bytes.
C: Data read error; low-order part is an error code.
ED00… An error occurred when manual mode was switched to automatic mode. High-order digits of YYYY indicate the cause for which the low-order part is an error code.
High-order digit = 1: World clock has not started.
EC01… Time difference occurred when setting CH1 timer.
YYYY is the difference.
EC02… Time difference occurred when setting CH2 timer.
YYYY is the difference.
EC03… Time difference occurred when setting CH3 timer.
YYYY is the difference.
D000… A communication error occurred while buffering initial data in AT (automatic) reception mode.
YYYY is the communication error status.
D001… While buffering initial data in automatic reception mode, software synchronization bit does not appear within 3 seconds.
YYYY is always 0.
D002… While buffering initial data in AT (automatic) reception mode, buffer A received an erroneous format code.
2 low-order characters of YYYY are the received format code.
D003… While buffering initial data in automatic reception mode, buffer B received an erroneous format code in the 1st block.
YYYY is the received format code.
D004… While buffering initial data in automatic reception mode, buffer B received an erroneous format code in the 2nd block.
YYYY is the received format code.
D005… While buffering initial data in automatic reception mode, buffer B received an erroneous format code in the 3rd block.
YYYY is the received format code.
D006… While buffering initial data in automatic reception mode, buffer B received an erroneous format code in the 4th block.
YYYY is the received format code.
D007… While buffering initial data in automatic reception mode, buffer B received an erroneous format code in the 5th block.
YYYY is the received format code.
D008… While buffering initial data in automatic reception mode, buffer B received an erroneous format code in the 6th block.
YYYY is the received format code.
D009… While buffering initial data in automatic reception mode, buffer B received an erroneous format code in the 7th block.
YYYY is the received format code.
D00A… While buffering initial data in automatic reception mode, buffer B received an erroneous format code in the 8th block.
YYYY is the received format code.
D010… While buffering initial data in automatic reception mode, received self-diagnostic data is not $55.
YYYY is the received diagnostic data.
D011… While buffering initial data in automatic reception mode, bit data received by buffer A at bit Nos. 0 and 1 is error bit data.
YYYY is the received data.
D012… When buffering initial data in auto-reception mode, buffer A received bit data with an error at bit 2 and bit 3.
YYYY is the received data.
D013… When buffering initial data in auto-reception mode, buffer A received bit data with an error at bit 4 and bit 5.
YYYY is the received data.
D080… Initial data buffered in auto-reception mode includes erroneous data in ID data No. 441C.
YYYY is the received data.
D081… Initial data buffered in auto-reception mode includes erroneous data in ID data No. 2428.
D090… Initial data buffered in auto-reception mode includes erroneous data in ID data No. 4405.
YYYY is the received data.
D091… Initial data buffered in auto-reception mode includes erroneous data in ID data No. 4404.
YYYY is the received data.
D092… Initial data buffered in auto-reception mode includes offset data with an error for compensating positioning points.
YYYY is the received data.
[Probable Faulty Locations]
Inverter unit (Check the LEDs on the converter unit.)
Incorrect ID No. set in MCS
Spec code setting error
Faulty connection to MCS
0813 MCS communication error
An error occurred during communication with MCS when power was turned on.
[Index]
None
[Character-string]
[Command name] – [Channel No.] – URL (Control No.)
[Code]
XXXXYYYY
If 3000000, servo link cable failure
The NC checks all channels on the servo link and determines that all of them are disconnected.
XXXX:
1…NC received the data that the NC had sent.
YYYY: Received frame information
2…Data is received from a slave station other than the one to which data was sent.
YYYY: Received frame information
3…The received data size is 2 bytes or less.
YYYY: Always 0
4…Data is received from a slave station other than the one to which data was sent.
YYYY: Received frame information
5…NC received data that the NC had transmitted rather than sent.
YYYY: Received frame information
6…Data is received from a station whose network address is 0.
YYYY: Received frame information
7…No data reception response was sent within 1 or 0.1 s after data transmission.
YYYY: Always 0
At the "SI" command, one or more MCS on the link could not start normally. Or, power could not be turned on.
Open the box and check the LEDs on all MCS units connected to the channel where the error occurred.
Units displaying '22' are normal.
8…Data transmission did not end within 0.1 s.
YYYY: Always 0
9…A communication error occurred after data reception completed.
YYYY: Error status information
A…A communication error occurred while the NC was waiting for data reception or simultaneously after data transmission.
YYYY: Error status information
B…A communication error occurred while the NC was waiting for data transmission.
YYYY: Error status information
C…Data transmission was attempted during data transmission.
YYYY: Operation status information
D…Data transmission was attempted in communication error status.
YYYY: Error status information
E…An erroneous command was received.
The upper 2 digits of YYYY are a code (45: Abnormality; 41: Alarm; 57: Warning; 54: Error), and the lower digits are numbers.
[Refer to the handshake communication error table (5-10) in the MCS Controller Function External Specifications.]
100…The first 2 bytes received as a response to transmitted data are incorrect.
YYYY: First 2 bytes received
101…The received data length as a response to transmitted data is incorrect. When the lower YY is a normal value, the upper digits YYYY indicate the received data length.
102…Data No. 1 related to received data is incorrect.
YYYY: Upper 2 bytes of determined data are abnormal
SI command: Slave station connection No.
AS command: Slave station connection No.
ID command: Communication code + auxiliary code
103…Data No. 2 related to received data is incorrect.
YYYY: Upper 2 bytes of determined data are abnormal
SI command: Accumulated relay time
ID command: Data ID
104…Data No. 3 related to received data is incorrect.
YYYY: Upper 2 bytes of determined data are abnormal
105…Data No. 4 related to received data is incorrect.
YYYY: Upper 2 bytes of determined data are abnormal
ID command: ID data (4 bytes or less)
106…Data No. 5 related to received data is incorrect.
YYYY: Upper 2 bytes of determined data are abnormal
SI command: Controller count
ID command: ID data (8 bytes)
200…Data size differs from the data size specified by ID No.
Software error
FF80…Data was transferred to the SVDN communication buffer of FF80, but data was not written to the buffer normally.
YYYY: Transfer command failed
[Probable Faulty Locations]
. Inverter unit (Check the LEDs on the inverter unit.)
. MCS connection error
. Faulty MCS connection cable
. Software error
0814 MCS data file
If power has been turned on, an error occurred while reading or transferring a servo data file.
Or, there is an error in the data file data itself.
[Index]
[Character-string] [Axis name] [Device name] [File name] or none
[Code]
0x11YYAAAA: Axis type read error (NC axis)
0x30YYAAAA: Axis type read error (PLC axis)
The NC cannot read the axis data file name consisting of a path name and a file name.
YY = 01: A data file check error occurred when the NC searched for the file name.
AAAA = 000B: The file does not exist, or the corresponding axis data does not exist in the file.
0x210200YY: Axis type read error (Spindle)
YY is the read data.
0x210500YY: Parameter group count read error (Spindle)
YY is the read data.
0xee000001: MCS servo data file open error
The registered file does not exist in the load definition file. Or, registration of the load definition file failed.
0xee000002: MCS servo data file header read error
0xee000003: MCS servo data file header check "PBU1"
0xee000004: MCS servo data file header check "MI"
0xee000005: MCS servo data file read error
0xee000006: The axis was replaced with a different axis in the data group count loop.
0xee000007: Data group mismatch
0xee000008: Sequence No. and data group No. mismatch
0xee000009: Axis type mismatch
The axis type does not match the type in the load definition file.
Or, data for the NC axis and spindle determined by the spec code does not exist in the definition file.
0xee000010: Other axis data exists in the MCS servo data file.
0xee000011: MCS servo data file memory overflow
0xee000012: MCS servo PBU data file is corrupted.
0xee000013: The format of the MCS servo CNS file name differs from that of the auto-tuning compatible file name.
0xee000014: Master axis and slave axis are not in the same MCS servo CNS file.
0xee000015: Corresponding axis data does not exist in the PFC II data file
used as the servo data file for each application.
0xee001103: Acceleration/deceleration method error in single-speed range
0xee001104: No inductosyn
0xee0002YY: Axis type read error
YY is the read data.
0x11YYAABB: Error during servo data file check
0x11010000: No axis data file corresponding to heavy workpiece exists.
YY = 01: No NC axis data file for NC axis control applicable to heavy workpiece exists
= 02: Axis specifications (rotary/speed limit) differ. Or unit system differs.
AABB = Axis specification data
= 03: Acceleration/deceleration method differs
= 04: Inductosyn unavailable specification
= 05: Data group count error (Spindle: except 1 to 32)
AABB = Group count
= 06: Magnitude relation error in velocity constant characteristic data values
AA indicates the axis No., and BB indicates the content.
AA
00: X-axis
01: Y-axis
02: Z-axis
03: 4th axis
04: 5th axis
BB
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
31: FT1pmax=0
32: FT1pmax>FT1pmin
33: FT1pmax=FT1pmin and T1pmax<T1pmin
34: FT1pmax>FT1pmin and T1pmax>T1pmin
41: FT2pmax=0 (FT2pmax is determined by internal calculation.)
42: FT2pmax<FT2pmin
43: FT2pmax=FT2pmin and T2pmax>T2pmin
44: FT2pmax>FT2pmin and T2pmaxpmax<T2pmin
(50 to 5E are alarms for turning-specific parameters.)
50: Turning-specific parameter group No. for the 3 basic axes does not match.
51: Turning-specific parameter T1min for the 3 basic axes does not match.
52: Turning-specific parameter T1max for the 3 basic axes does not match.
53: Turning dedicated parameter T1pmax of basic 3 axes does not match.
54: Turning dedicated parameter FT1min of basic 3 axes does not match.
55: Turning dedicated parameter FT1max of basic 3 axes does not match.
56: Turning dedicated parameter FT1pmax of basic 3 axes does not match.
57: FT1max=0
58: FT1max>FT1min
59: FT1max>FT1min and T1max<T1min
5A: FT1max=FT1min and T1max>T1min
5B: FT1pmax=0
5C: FT1pmax<FT1pmin
5D: FT1pmax>FT1pmin and T1pmax>T1pmin
5E: FT1pmax=FT1pmin and T1pmax<T1pmin
70: FTmax=FTpmin
71: FTmax=FTpmax
72: Cross feed / rev (Rp360dgx)=0
73: Position encoder speed with rotary axis gear ratio (ID$4018) = 0
74: Speed of control target with rotary axis gear ratio (ID$4018) = 0
YY=07: No servo data corresponding to NC axis data applied to heavy workpiece
AABB = NC axis data set weight
=08: Error in data for high-quality thread cutting mode.
AABB=0000-> No dedicated group for high-quality thread cutting mode.
=0001-> Calculation result of acceleration completion exceeds allowable value.
=09: No data of the number of slave axes for spindle tandem control.
Or, the number of slave axes exceeds 4.
AABB: Spindle tandem slave axis count setting in axis data file
YY=0A: Axis data file setting is improper.
AA
00: X-axis
01: Y-axis
02: Z-axis
BB
01: Motor instantaneous maximum torque error
02: When inertia with no workpiece is 0, motor-side motor shaft converted inertia and
load-side motor shaft converted inertia are both abnormal value 0.
YY=0B: When using servo data file for Servonavi M, NC axis data
and servo data are not found in the same servo file.
AABB=0000
YY=0C: When equipped with auto backlash adjustment axis, the data file setting of PFC2 file
is improper.
AABB=0000: Minimum acceleration (|Amin|)=0
=0001: Point number to be set (n)=0
=0002: Common ratio (a)=0
0x1012AAAA: Error in replacing position encoder with ABSOSCALE
AAAA:
0000: Although position encoder can be replaced with ABSOSCALE, full-closed position encoder 1 (ID.203A) is set to ”0″.
0002: Although position encoder can be replaced with ABSOSCALE, full-closed position encoder 2 (ID.203B) is set to ”0″.
0x1013AAAA: Calculation of time constant for control wait for collision avoidance system is incorrect
(NC axis)
AAAA:
0001: T1 time constant is negative.
0002: T1 time constant exceeding 8192 exists.
0003: T2 time constant is negative.
0004: T2 time constant exceeding 2048 exists.
0x1014AAAA: Full-closed DD encoder specification error
AAAA:
0000: Full-closed DD encoder specification axis, but full-closed position encoder 1 designation (ID.203A) is 0
0002: Full-closed DD encoder specification axis, but full-closed position encoder 2 designation (ID.203B) is 0
0x2013AAAA: Calculation of time constant for control wait for collision avoidance system is incorrect
(Spindle)
AAAA:
0005: T1 time constant is negative.
0006: T1 time constant exceeding 8192 exists.
0007: T2 time constant is negative.
0008: T2 time constant exceeding 2048 exists.
0x21150000: Values of Servonavi L interpolation specification do not match between axis data files.
0x22000000: Servo data for hobbing is not set (Spindle).
0x22000001: Servo data for hobbing is not set (NC axis).
[Probable Faulty Locations]
1) Servo data file
0817 MCS error
An error in MCS control.
[Index]
None
[Character-string]
None
[Code]
XYZZAAAA
XYZZ: 0000
AAAA:
1: NC axis reset request was not accepted.
2: MCS does not respond to NC axis reset.
3: Spindle reset request was not accepted.
4: MCS does not respond to spindle reset.
X: Channel number 1 to 3
YZZAAAA: Communication error status
ZZ: Error slave station
Bit 7: Slave station 8 is processing transmission/reception.
Bit 6: Slave station 7 is processing transmission/reception.
Bit 5: Slave station 6 is processing transmission/reception.
Bit 4: Slave station 5 is processing transmission/reception.
Bit 3: Slave station 4 is processing transmission/reception.
Bit 2: Slave station 3 is processing transmission/reception.
Bit 1: Slave station 2 is processing transmission/reception.
Bit 0: Slave station 1 is processing transmission/reception.
AAAA: Error cause
Bit 15: Error present (normally 1)
Bits 14 to 12: Normally 0
Bit 11: Access error in MT mode
Bit 10: Transmission loop error in AT mode
Bit 9: Data overrun number error in reception IF section
Bit 8: Disconnection error
Bit 7: Normally 0
Bit 6: Modulation code error
Bit 5: Reception CRC error
Bit 4: Format error
Bit 3: Double transmission error
Bit 2: Double reception error
Bit 1: Memory parity error
Bit 0: Timeout error
[Probable Faulty Locations]
1) MCS controller fault
2) Servo connection failure
3) Software failure
0830 SPMC execution stop
When starting to respond to an execution request, reset request, or data transfer request, the SPM engine outputs an invalid value.
(High-speed contour control (SPM) = Hi-Cut Pro or Super-NURBS)
[Index]
None
[Character-string]
None
[Code]
XXYY
XX = 10: The SPM engine cannot start responding to an execution request within 20 seconds.
XX = 18: The SPM engine cannot respond to a reset request within 20 seconds.
XX = 20: The SPM engine sends an invalid value in response to a data transfer request.
XX = 28: The SPM engine cannot respond to a reset request within 10 seconds.
XX = 30: When a reset request is issued, the previous data transfer cannot be completed.
[Probable Faulty Locations]
Software fault
0833 MCS optional program file not transferred
Optional MCS program file was not transferred to MCS.
[Index]
Axis name or none
[Character-string]
None
[Code]
None
[Probable Faulty Locations]
The MCS optional program file has not been transferred.
The MCS optional program file is not found.
The MCS optional program file does not contain a program matching the MCS software version.
[Measures to Take]
Install the MCS optional program file.
Replace the MCS optional program file.
0834 MCS servo data error
Erroneous servo data was transferred to the MCS.
[Index]
Axis name or none
[Character-string]
None
[Code]
XXXXYYZZ
XXXX = ID number
YY = Parameter number
ZZ = Error description
01: Out of setting range
02: Setting timing error
03: No data transferred
04: Calculation error
05: Other
[Probable Faulty Locations]
The servo data file does not match the MCS software version.
NC software
[Measures to Take]
Replace the servo data file.
0835 MCS communication
An error occurred in the handshaking communication related to MCS.
[Index]
Axis name or none
[Character-string]
Handshaking communication error number (2 digits) and [Command name] – [Channel number] – Station address (Controller number)
[Code]
Error data at error occurrence (zero suppression effective for upper 8 digits) (Content varies depending on handshaking communication error number.)
[Probable Faulty Locations]
1) Software fault
[Measures to Take]
1) Replace software.
0839 Specification conditions error
Error in specification code or hardware configuration
[Index]
None
[Character-string]
None
[Code]
XXX:
2: 6 axes were found in spindle path control specification.
3: The necessary specification conditions for DNC-C Ethernet version are not satisfied.
6: Neither A-axis nor C-axis is selected in twin rotary table specification.
7: If tool axis direction manual feed function is valid, sloped surface machining function is invalid.
8: In tool tip control function specification (NC spec code No.5 bit 5),
there is no rotary axis other than index axis,
the number of axes in this specification does not exceed 4,
or Super Hi-NC specification is not turned ON.
9: In B-axis rotation limit function specification (Spec code No.32 bit 3):
Limited rotary axis B specification is not turned OFF.
4th-axis B-axis fixed specification is not turned ON.
B: In 5-axis machining specification (Spec code B No.2 bit 7):
B-axis is not selected.
C-axis is not selected.
Limited rotary axis B specification is not turned ON.
Limited rotary axis C specification is not turned OFF.
B-axis is fixed to 4th axis.
Sloped surface machining function is not turned ON.
Super Hi-NC specification is not turned ON.
Not 5-axis specification.
10: When pivot distance compensation function (NC spec code No.5, bit 6) is enabled, the following 3 types of rotary axis specification codes:
Spindle head side rotary axis (NC spec code No.13, bit 0),
Table side rotary axis (NC spec code No.13, bit 1), and
Spindle head and table side rotary axis (NC spec code No.13, bit 2),
are not in any of the following 3 states:
”Valid only on spindle head side code”,
”Valid only on table side code”, and
”Valid only on spindle head and table side code”.
11: When pivot distance compensation function (NC spec code No. 5, bit 6) is enabled;
Rotary axis on spindle head side (NC spec code No. 13, bit 0) does not satisfy ”Number of NC control axes is 5 && additional axis is not A or B”, or
Rotary axis on table side (NC spec code No. 13, bit 1) does not satisfy ”Number of NC control axes is 5 && additional axis is not A or C”, or
Rotary axis on spindle head and table side (NC spec code No. 13, bit 2) does not satisfy ”Number of NC control axes is 5 && additional axis is not A or C”.
12: When turning function spec (NC spec code No. 8, bit 4) is enabled, none of the following is enabled:
5-axis control spec (NC spec code No. 3, bit 1)
Additional axis A-axis spec (NC spec code No. 14, bit 3)
Additional axis C-axis spec (NC spec code No. 14, bit 5)
13: When inclined surface machining V2 (NC spec code No. 6, bit 5) is enabled, inclined surface machining (NC spec code No. 28, bit 5) is disabled.
14: When inclined surface indexing (NC spec code No. 6, bit 6) is enabled:
– Inclined surface machining (NC spec code No. 28, bit 5) is disabled
– Inclined surface machining (NC spec code No. 6, bit 5) is disabled, or
– There is no NC rotary axis or no AT spec.
15: When tool position compensation function (NC optional spec code No. 5, bit 7) is enabled,
Tool center point control spec (NC spec code No. 5, bit 5) is disabled.
16: When geometric error compensation function (NC spec code No. 19, bit 3) is enabled,
None of the following 3 rotary axis spec codes meets "Valid only on spindle head side",
"Valid only on table side", or "Valid only on spindle head and table side":
Rotary axis on spindle head side (NC spec code No. 13, bit 0),
Rotary axis on table side (NC spec code No. 13, bit 1), and
Rotary axis on spindle head and table side (NC spec code No. 13, bit 2).
17: Center deviation compensation function (NC spec code No. 5, bit 6) and geometric error
compensation function (NC spec code No. 19, bit 3) are enabled at the same time.
18: When new tool grinder spec (NC spec code No. 9, bit 3) is enabled,
None of the following specs is enabled:
6-axis control spec (NC spec code No. 3, bit 2),
Synchronized axis X-axis spec (NC spec code No. 7, bit 0),
Synchronized axis Y-axis spec (NC spec code No. 7, bit 1),
Synchronized axis Z-axis spec (NC spec code No. 7, bit 2),
Additional axis U-axis spec (NC spec code No. 14, bit 0),
Additional axis A-axis spec (NC spec code No. 14, bit 3),
Additional axis B-axis spec (NC spec code No. 14, bit 4),
5th axis limit spec (NC spec code No. 7, bit 4), or
Axis ID definition file spec (Version B spec code No. 7, bit 7).
19: Number of controlled axes in spindle path control spec is 8.
20: Spindle path control spec includes all of A-axis, B-axis, and C-axis specs.
21: When new insert machining spec (NC spec code No. 9, bit 3) is enabled,
7-axis control spec (NC spec code No. 30, bit 6)
or 8-axis control spec (NC spec code No. 30, bit 7) is enabled.
22: When tool point machining axis standard spec (Version B spec code No. 10, bit 6) is enabled,
Tool center point control spec (NC spec code No. 5, bit 5) is disabled.
23: When tool center point control cutting point command spec (Version B spec code No. 9, bit 2) is enabled,
Tool center point control spec (NC spec code No. 5, bit 5) is disabled.
24: When tool tip side compensation spec (Version B spec code No. 13, bit 6) is enabled,
Tool center point control spec (NC spec code No. 5, bit 5) is disabled, or
5-axis machining tool side compensation spec (NC spec code No. 19, bit 5) is disabled.
25: Dynamic tool load control spec (Version B spec code No. 11, bit 7) and
TOOL-ID spec (NC spec code No. 32, bit 4) are enabled at the same time.
26: When tool side machining function (NC optional spec code No. 14, bit 7) is enabled,
Tool center point control spec (NC spec code No. 5, bit 5) is disabled.
99: Low-speed SVP spec code (NC spec code No. 25, bit 7) is not enabled.
100: In the 3-axis control spec with X-axis slave, additional axis U or V is enabled.
101: In the 3-axis control spec with X-axis slave, there are 3 synchronized axes.
200: Synchronized control option
Number of controlled axes is not 5 and 6.
Neither A-axis nor C-axis is included in additional axes.
When there are 2 or more rotary axes, specs in the relevant status both exist.
300: SSU is not connected in relocation detection spec.
301: Corresponding SSU is not connected in relocation detection spec.
400: On Coburg machines, X1-axis and X2-axis are not set in the PLC spec code.
401: On Coburg machines, spindles for X1-axis and X2-axis are not set.
[Probable Fault Sites]
2: Error in determining specs
3: Although the spec code for DNC-C Ethernet version is ON, the DNC-C3 spec code is not ON.
99: For machines with OSP-P200, low-speed SVP spec code (NC spec code No. 25, bit 7) cannot be disabled. Therefore, make sure to enable this spec code.
[Measures to Take]
2: Reduce the number of controlled axes, or stop the spindle path control function.
0841 FCP4 illegal
0842 Safety speed monitor spec conditions
An error was found in the spec conditions of safety speed monitor spec.
[Index]
None
[Character-string]
None
[Code]
WXXYYZZ:
W:
1: The indicated axis position differs from the safety speed monitor position connected in software.
The guard number value for each axis in the safety speed monitor data file for axis control differs from the monitor position of the connected axis.
XX: Axis ID number
YY: Guard number
ZZ: Channel number connected to safety speed monitor
1CH=0, 2CH=1, 3CH=2
2: For the indicated axis, the guard number is not 1 to 9.
XX: Axis ID number
YY: Guard number
ZZ: Channel number connected to safety speed monitor
=0:1CH, 1:2CH, 2:3CH
3: In the AT spindle spec, the safety speed monitor (2nd unit) does not exist.
4: Enable the CE mark spec. Or, remove the safety speed monitor.
5: Check the guard number and input number in the safety speed monitor axis data file.
6: Safety speed monitor ROM version is incompatible with OSP.
7: Prepare a safety speed monitor of version 600 or higher for the stop monitor spec.
8: Turn off the CE mark safety logic spec. Or, remove the safety speed monitor.
[Measures to Take]
W:
1: Check whether the connection position is suitable for the safety speed monitor.
Or, check whether the value of the guard number in the safety speed monitor data file for axis control is correct.
2: Replace the safety speed monitor data file for axis control.
3: Add 1 safety speed monitor.
4: Enable the CE mark spec. Or, remove the safety speed monitor.
5: Check the guard number and input number in the safety speed monitor axis data file.
6: Replace the safety speed monitor.
7: Prepare a safety speed monitor of version 600 or higher for the stop monitor spec.
8: Turn off the CE mark safety logic spec. Or, remove the safety speed monitor.
0844 FWMB illegal
An error occurred on the FWMB (FWM board).
[Index]
None
[Character-string]
None
[Code]
XYYZZ
X : Motherboard 1=FWMB
YY: Self-diagnostic data
ZZ:
00= No error
01= General CPU exception
02= MSTP detected
03= Graphic accelerator failure
04= NMI detected
05= Kernel error detected.
06= Undefined interrupt detected.
11= UCMB SW status standby timeout
12= Memory error
21= Illegal instruction detected
22= Startup status standby timeout
24= Some error
31= IPL fatal error
41= Fatal error/internal logic error
71= Ended with EXIT
0849 Synchronized axis dual drive control initialization error
An error occurred during initialization of synchronized axis tandem control.
[Index]
Axis or none
[Character-string]
Error axis name or none
[Code]
XXYY:
XX: Cause YY: Group number (starting from 0)
XX:
1: Master control axis tandem control spec code is not 1.
2: Master control axis master tandem control spec code is not 1.
3: Slave control axis tandem control spec code is not 1.
4: Slave control axis master tandem control spec code is not 1.
5: Synchronized axis master control axis is not found.
6: Synchronized axis slave control axis is not found.
7: Master control axis and slave control axis are not connected on the same link (channel).
8: Connection order of master control axis and slave control axis is not set in order of master control axis to slave control axis.
9: There are only 8 slave stations on the connection, and slave stations used for communication between slave stations cannot be secured.
[Measures to Take]
XX:
1: Modify or replace the servo data file.
2: Modify or replace the servo data file.
3: Modify or replace the servo data file.
4: Modify or replace the servo data file.
7: Connect the master control axis and slave control axis to the same link (channel).
8: Connect the axes in the order of master control axis to slave control axis.
9: When connecting the master control axis and slave control axis, limit the maximum number of connected axes to 7.
0850 MCS unregistered alarm
MCS generated an error related to axis control.
[Index]
Axis name or none (spindle)
[Character-string]
Alarm number in decimal
[Code]
Alarm code
[Probable Fault Sites]
According to the number indicated in the character-string. Notify us of the code and character-string.
0851 MCS exception processing
A serious alarm occurred during execution of the MCS inverter unit and MCS software.
[Index]
Axis name or none (Spindle)
[Character-string]
Check alarm cause
“#1”-> Control board error
“#2”-> Control power supply ±12V/+24V abnormality
“#3”-> OPF error
“#8”-> Magnetic encoder power supply abnormality
“#9”-> Encoder power supply abnormality
“#10”-> Control power supply +3.3V/+1.5V abnormality
“#11”-> Control power supply +5V abnormality
“#12”-> Gate signal abnormality
“#13”-> Inverter bridge abnormality
“#14”-> Motor overcurrent
“#20”-> INT6 loop error. IR1MAIN loop error.
“#21”-> INT5 loop error. IR2MAIN loop error.
“#22”-> INT4 loop error
“#23”-> INT3 loop error
“#24”-> INT2 loop error
“#25”-> INT1 loop error. IR3MAIN loop error.
“#26”-> Access error
“#28”-> Parity error
“#29”-> Monitor error
“#30”-> IRQ7 interrupt. IRQ4 interrupt.
“#31”-> NMI interrupt
“#32”-> General illegal instruction
“#33”-> Slot illegal instruction
“#34”-> CPU address error
“#35”-> DMA address error. DMAC/DTC address error.
“#36”-> Undefined trap instruction
“#37”-> Undefined interrupt
“#38”-> DMAC
“#39”-> ITU, MTU
“#40”-> SCI
“#41”-> REF, BSC
“#42”-> A/D
“#43”-> Reserved system
“#44”-> User break
“#45”-> DTC
“#46”-> CMT
“#47”-> I/O
“#48”-> HUDI
“#50”-> POE
“#51”-> IIC3
“#52”-> BANK
“#53”-> DIV
“#54”-> WAVEIF
“#55”-> Power supply unit (IPM) abnormality
[Code]
#1 indicates control board error details.
#1: Access error
#2: PWM synchronization error
#3: PWM buffer operation error
#4: Control frequency error
Other codes: Offset error of current detection A/D converter
#2, #8-#9 and #11 indicate voltage detection values of each power supply.
#3 indicates error details of optional program file.
#1: Identification code "OPF1" error
#2: End code "ED" error
#3: Checksum error
#4: Board name error
#10, #12-#14, #20-#21 and #25-#26 indicate error status registers.
#22-#24, #28-#42, #44-#48 and #50-#55 indicate PC when error occurred.
[Probable Faulty Locations]
For #1, #2, #10-#14, #20-#26, #28-#42, #45-#48 or #50-#55:
Inverter unit
For #3:
Inverter unit
Optional program file
For #8:
Magnetic encoder and magnetic encoder cable
Inverter unit
For #9:
Encoder and encoder cable
Inverter unit
For #44:
User break controller
0852 MCS processing failure
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXZZAAAA
XX:
04… Self-diagnostic data error. ZZ: Received data
06… Software synchronization bit or buffer A format code error.
07… Software synchronization bit or buffer B format code error.
08… An error occurred during data communication.
ZZ indicates data type. AAAA is always 0.
ZZ:
1… Speed command (8408)
2… Laser linear scale value (4413)
3… Backlash (4406)
4… Actual position without pitch error compensation (440A)
5… Pitch error compensation amount (4403)
6… Full closed loop encoder value (4410)
7… Semi-closed loop encoder value (4411)
8… ODIFF (4415)
10.. APA in separated stroke (4404)
11.. Acceleration/deceleration time for positioning (4422)
12.. Zero offset amount
13.. In-position width (4420)
14.. Maximum value of separated stroke (4405)
15.. Point data change
16.. ODIF amount (4415)
17.. Point table number confirmation (140D)
18.. Point table number change (1409)
[Probable Faulty Locations]
Faulty MCS controller
Faulty software
0853 MCS CON/APA deviation
The difference between CON and APA exceeded the allowable limit.
CON-APC deviation is the absolute value of the difference between [calculated value written to MCS] and [actual position read from MCS].
The NC control software checks this deviation, while normally the MCS checks the DIFF value.
An alarm occurs if a fatal error occurs in the MCS and the DIFF value cannot be monitored.
[Index]
Axis name
[Character-string]
None
[Code]
Absolute value of deviation in hexadecimal (reference unit)
[Probable Faulty Locations]
Faulty MCS controller
Mismatch between MCS data and NC data
0854 MCS power supply unit abnormality
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 number
0: DC voltage alarm
1: AC input voltage alarm
2: Control power supply abnormality
3: Control status abnormality
4: Regeneration overload
5: Heat sink overheat
6: CPU error
7: Reserved
Y= Power supply unit status
Bit 3: Alarm occurred in power supply unit (0 for warning)
Bit 2: DC power is being supplied
Bit 1: OPRON input OFF
Bit 0: PWON input OFF
ZZ= Alarm data
When X (Alarm number) = 0, DC voltage is represented with 7F[HEX]=500V
When X (Alarm number) = 1, AC voltage is represented with 80[HEX]=300V
When X (Alarm number) = 2:
1: +5V voltage abnormality
2: +12V voltage abnormality
3: -12V voltage abnormality
4: +24V voltage abnormality
When X (Alarm number) = 3:
1: Power supply line overcurrent
2: Power supply unit abnormality
3: Converter bridge short-circuit
4: Regenerative circuit abnormality (power regeneration circuit type)
5: Regenerative circuit abnormality (resistor discharge feedback circuit type)
When X (Alarm number) = 4, undefined
When X (Alarm number) = 5, undefined
When X (Alarm number) = 6, undefined
[Probable Faulty Locations]
Power supply voltage
Operating conditions
Power supply unit
Inverter unit
0855 MCS inverter link abnormality
An error occurred in the converter link (communication between the power supply unit and the inverter unit), making it impossible to monitor the status of the power supply unit.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XYYYYYZZ
X=0: Communication error
X=1: Timeout error (communication interrupted)
YYYYY=0 fixed
ZZ
If X=0, communication error status
If X=1, 0 fixed
[Probable Faulty Locations]
Converter link cable or connector
Inverter unit control board
Power supply unit
0856 MCS inverter DC bus voltage abnormality
The DC bus voltage of the inverter unit has abnormally increased or dropped.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Overvoltage detection value
Displayed with 7FF8[HEX]=500V
YYYY= Undervoltage detection value
Displayed with 7FF8[HEX]=500V
[Probable Faulty Locations]
Power supply voltage
Inverter unit
Power supply unit
0857 MCS motor overcurrent
Excessive current was detected in the motor power line of the inverter unit.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
<For BL/PREX>
XXXX= U-phase current detection value
3FFF[HEX] = Displayed at maximum instantaneous current
YYYY = W-phase current detection value
3FFF[HEX] = Displayed at maximum instantaneous current
<For VAC>
XXXX = U-phase current detection value
AAA[HEX] = Displayed at maximum instantaneous current
YYYY = W-phase current detection value
AAA[HEX] = Displayed at maximum instantaneous current
[Probable Faulty Locations]
Motor insulation failure
Inverter unit
0858 MCS Inverter overheat
The temperature of the inverter unit rose abnormally.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXXXXX = 1 fixed
[Probable Faulty Locations]
Operating conditions
Inverter unit
0859 MCS Inverter overload
The inverter load exceeded the specified value, activating the overload protection function.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX = Gamma of protection curve used for overload detection
YYYY = Integrated data at overload detection
[Probable Faulty Locations]
Operating conditions
Cutting load torque
Servo data file
Inverter unit
0860 MCS Power supply voltage error
The input voltage of the power supply unit rose or dropped abnormally.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXXXXX = Voltage value when the error was detected
In hexadecimal notation: 01[HEX] = 0V
In hexadecimal notation: 80[HEX] = 300V
[Probable Faulty Locations]
Power supply voltage
Diameter and length of power supply cable
Power supply unit
0861 MCS Inverter unit version error
The allowable current 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]
XXXXXXXX = 1 fixed
[Probable Faulty Locations]
Inverter unit
Servo data file
0862 MCS Winding changeover failure
An error occurred in the winding changeover electromagnetic switch.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXXXXX
XXXXXXXX =
00000001[HEX]: ON detection of LOW-side MC
00000002[HEX]: ON detection of HIGH-side MC
00000003[HEX]: Simultaneous ON detection of LOW-side and HIGH-side MCs
00000004[HEX]: Winding changeover timeout
10100001[HEX]: Servo data file error
[Probable Faulty Locations]
Winding changeover electromagnetic switch
0863 MCS Encoder link communication error
An error occurred during encoder link communication.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX = FF[HEX] (fixed)
YY = 00[HEX]: Error detected at motor encoder.
01[HEX]: Error detected at shaft encoder.
02[HEX]: Error detected at separate encoder.
03[HEX]: Error detected at ABSOSCALE.
04[HEX]: Error detected at auxiliary slide
ZZZZ = Encoder link status when error was detected
Bit 15: Communication error of separate encoder
Bit 14: Communication error of ABSOSCALE 2
Bit 13: Communication error of shaft encoder or ABSOSCALE
Bit 12: Communication error of motor encoder
Bit 11: Undefined
Bit 10: AT mode transmission loop error
Bit 9: Data overflow error in reception IF section
Bit 8: Undefined
Bit 7: Undefined
Bit 6: Modulation code error
Bit 5: CRC error
Bit 4: Format error
Bit 3: Bidirectional transmission error
Bit 2: Bidirectional reception error
Bit 1: Parity error
Bit 0: Timeout error
[Probable Faulty Locations]
Motor encoder, ABSOSCALE, shaft encoder, or separate encoder of the relevant axis
Encoder link cable or connector
Inverter unit control board
0864 MCS Encoder error
The motor encoder failed to detect position data.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX = Encoder error code
YY = Detailed status of encoder
ZZZZ = Multi-turn position data.
When the multi-turn position data exceeds the allowable rotation range:
XX = 0 fixed
YY = 1 fixed
ZZZZ = Multi-turn position data
[Probable Faulty Locations]
Motor encoder
0865 MCS Encoder initialization error
An error occurred during initialization of the motor encoder.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX = E-link sequence number when error was detected
0: Reset
1: Address setting
2: Request transmission of basic communication information
3: Communication version change
4: Obtain device information
5: Change parameter
6: Start position detection
7: Start AT mode
YY = Error content
0: Communication error
1: Transmission start time timeout
2: Transmission end time timeout
3: Reception end time timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ = Data
If YY = 0: Encoder link status when error was detected
If YY = 1, 2, 3: Transmitted frame information
If YY = 4: Address of responding device
If YY = 5: Received frame information
If YY = 6: Parameter number detected as error.
1: Insufficient number of received parameters
2: Basic communication information incompatibility
3: Multi-turn detection range mismatch
4: Communication protocol version incompatibility
[Probable Faulty Locations]
Motor encoder
Encoder link cable or connector
Inverter unit control board
0866 MCS Shaft encoder error
The shaft encoder failed to detect position data.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX = Encoder error code
YY = Detailed status of encoder
ZZZZ = Multi-turn position data
When the multi-turn position data exceeds the allowable rotation range:
XX = 0 fixed
YY = 1 fixed
ZZZZ = Multi-turn position data
[Probable Faulty Locations]
Shaft encoder
0867 MCS Shaft encoder initialization error
An error occurred during initialization of the shaft encoder.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX = E-link sequence number when error was detected
0: Reset
1: Address setting
2: Request transmission of basic communication information
3: Communication version change
4: Obtain device information
5: Change parameter
6: Start position detection
7: Start AT mode
YY = Error content
0: Communication error
1: Transmission start time timeout
2: Transmission end time timeout
3: Reception end time timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ = Data
If YY = 0: Encoder link status when error was detected
If YY = 1, 2, 3: Transmitted frame information
If YY = 4: Address of responding device
If YY = 5: Received frame information
If YY = 6: Parameter number detected as error.
1: Insufficient number of received parameters
2: Basic communication information incompatibility
3: Multi-turn detection range mismatch
4: Communication protocol version incompatibility
[Probable Faulty Locations]
Shaft encoder
Encoder link cable or connector
Inverter unit control board
0868 MCS ABSOSCALE error
An error occurred in initialization of ABSOSCALE.
[Index]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX = Positional data status
bit7 : Error bit (1:error)
bit6 : Warning bit(1:warning)
bit5 : Signal amplitude status bit(1:signal amplitude is too large,0:signal amplitude is too small)
bit4 : 0 fixed
bit3 : 2 millimeter period signal error bit(1:error, 0:normal)
bit2 : 80 micron period signal error bit(1:error,0:normal)
bit1 : Communication error(Toggle by detecting)
bit0 : Absolutization error bit(1:error,0:normal)
YY = Alarm code
01 : Stop command has stopped.
02 : Control parameter error
05 : Initialization speed too high
08 : Auto-set-data error
0D : Speed too high
0E : Synchronization error
10 : Absolutization error
11 : Signal amplitude error of 80 micron period signal
12 : Signal amplitude error of 2 millimeter period signal
13 : Signal amplitude error of 80 micron and 2 millimeter period signal
14 : Signal amplitude error of 80 micron period signal, and Absolutization error
15 : Signal amplitude error of 2 millimeter period signal, and Absolutization error
16 : Signal amplitude error of 80 micron and 2 millimeter period signal,and Absolutization error
40 : Slider tilting error(for plus)
41 : Slider tilting error(for minus)
42 : Gap is narrow.
43 : Gap is wide.
E1 : Error of 1.5 volt power supply
E4 : Error of 3.1 volt power supply
ZZZZ = Upper position data larger than a signal period
[Probable Faulty Locations]
ABSOSCALE(Scale unit or Slider unit)
0869 MCS Scale initialization error
An error occurred during ABSOSCALE initialization.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= E-link sequence No. at error detection
0: Reset
1: Address setting
2: Request transmission of communication basic information
3: Communication version change
4: Device information acquisition
5: Parameter change
6: Position detection start
7: AT mode start
YY= Error details
0: Communication error
1: Transmission start time timeout
2: Transmission end time timeout
3: Reception end time timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ= Data
If YY=0, encoder link status at error detection
If YY=1, 2, 3, transmitted frame information
If YY=4, address of responding device
If YY=5, received frame information
If YY=6, indicates the parameter No. detected as an error.
1: Insufficient number of received parameters
2: Communication basic information incompatible
3: Multi-turn detection range mismatch
4: Communication protocol version incompatible
[Probable Faulty Locations]
ABSOSCALE
Encoder link cable or connector
Inverter unit control board
0870 MCS Magnetic encoder error
The magnetic encoder cannot detect position data, or the number of
magnetic encoder gear teeth does not match the set value in the servo data file.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Error details
000A[HEX]= Phase A voltage error
000B[HEX]= Phase B voltage error
000C[HEX]= Magnetic encoder pulse signal error
Others = Servo data file set value when magnetic encoder pulse count overflows or marker data error occurs
(Set pulse count or number of gear teeth)
YYYY= Error data
If XXXX=000A[HEX]: Phase A voltage value (represented by 7FFF[HEX]=2.5V)
If XXXX=000B[HEX]: Phase B voltage value (represented by 7FFF[HEX]=2.5V)
If XXXX=000C[HEX]: 0 (fixed) (represented by 7FFF[HEX]=2.5V)
Other cases: Magnetic encoder count detected value or gear teeth detected value
[Probable Faulty Locations]
Servo data file
Magnetic encoder
Magnetic encoder cable
0871 MCS Resolver error
The resolver cannot detect position data.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX
FFFFFFFF[HEX]: Disconnected
Other than FFFFFFFF[HEX]: Excessive acceleration
[Probable Faulty Locations]
Resolver
Resolver signal cable
Inverter unit
0872 MCS Pulse generator count overflow
The count per revolution of the PG (pulse generator) does not match the set value in the servo data file.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Servo data file set value (count value per PG revolution)
YYYY= Count value
[Probable Faulty Locations]
Servo data file
Magnetic encoder
Magnetic encoder cable
0873 MCS Motor overheat
Motor temperature rose abnormally.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Fixed at 0
If YYYY=0010[HEX]: Overheat
If YYYY=0011[HEX]: Motor overheat [BL/PREX]
If YYYY=0012[HEX]: Encoder overheat [BL/PREX]
If YYYY=0013[HEX]: Motor and encoder overheat [BL/PREX]
[Probable Faulty Locations]
Operating conditions
Motor of the relevant axis
Motor encoder
Encoder link cable
0874 MCS Servo link communication error
A communication error occurred in the servo link, making it impossible to receive commands from the NC.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Fixed at 0
YYYY= Each bit indicates the type of communication error (servo link error status at error detection)
Bit 15: Second B buffer error
Bit 14: Second A buffer error
Bit 13: First B buffer error
Bit 12: First A buffer error
Bit 11: MT buffer error
Bit 10: Relay processing error
Bit 9: Data overflow error in receiving IF section
Bit 8: Disconnection error
Bit 7: Address pointer error
Bit 6: Modulation code error
Bit 5: CRC error
Bit 4: Format error
Bit 3: Bidirectional transmission error
Bit 2: Bidirectional reception error
Bit 1: Parity error
Bit 0: Timeout error
[Probable Faulty Locations]
Servo link cable or connector
Inverter unit control board
SVDN board
0875 MCS Servo link disconnection
The servo link cable was disconnected, making it impossible to receive commands from the NC.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Disconnection position
0000[HEX]: Disconnected immediately before the faulty unit
8000[HEX]: Disconnected before the faulty unit
YYYY= Servo link error status at error detection
[Probable Faulty Locations]
Servo link cable or connector
Inverter unit control board
SVDN board
0876 MCS Servo link communication protocol error
Format or timing of data sent from NC to the inverter unit is incorrect.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX
Indicates error content 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 Faulty Locations]
NC software
Inverter unit control board
SVDN board
0877 MCS Servo data error
During initialization or operation, servo data sent by the NC is not applicable.
If this alarm occurs when replacing the inverter unit, the compatibility relationship
between the servo data file and the inverter unit is incorrect. If this alarm occurs when adjusting/changing servo data, the changed servo data is incorrect.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYZZ
XXXX= Data ID No. where error was detected [HEX]
YY= Data group No. where error was detected
ZZ= Error details
1: Out of setting range
2: Setting timing error
3: No transmission
4: Calculation error
5: Others
6: Number of ID Nos. exceeded (no extended servo data)
[Probable Faulty Locations]
Servo data file
NC software
Inverter unit control board
0878 MCS Command error
Command/response data is transmitted between NC and inverter unit via servo link.
However, the command sent from NC to the inverter unit is abnormal or unsupported.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX
0010[HEX]: Positioning mode command point count exceeded
0011[HEX]: Positioning mode negative command value
0012[HEX]: Positioning mode command position > 1 revolution of controlled object
0013[HEX]: Positioning mode positioning point table not transferred
0014[HEX]: Non-positioning mode rotary axis
0015[HEX]: Positioning mode command format is not point
0016[HEX]: Positioning mode positioning submode error
0021[HEX]: Group switching designated group count exceeded
0022[HEX]: Mode undefined mode
0023[HEX]: Mode positioning/tool path mode condition
0024[HEX]: Coordinate system Coordinate system designation error
0030[HEX]: Undefined bit data ON in S-link A buffer
0031[HEX]: Undefined bit data ON in S-link B buffer
0040[HEX]: Switched to AT mode without receiving time synchronization command
YYYY= Error data
When XXXX is 0010 to 0016[HEX], it indicates the positioning sub-mode.
0: Program mode
1: Search mode
2: Pulse handle mode
3: Teaching mode
[Probable Faulty Locations]
Servo data file
NC software
Inverter unit control board
0879 MCS CON speed overflow
Position command increment (SRCOND) sent from NC to inverter unit exceeded the allowable value.
If this alarm occurs on a positioning axis, the servo data file data may be incorrect.
(The inverter unit calculates the position command increment for the positioning axis.)
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX= Designated CON speed
2^-16[pr/Tp] (Speed mode: [su/Tc])
pr= One revolution of position encoder
Tp= Position control frequency
su= Basic unit
Tc= Command frequency
However, the following data have special meanings.
1: Increment is too large and was judged as an error during initial check.
2: Absolute value of position command value (SRCON) exceeds encoder measuring range (linear axis only).
3: Speed command value in thread cutting feedrate override mode exceeds allowable value.
[Probable Faulty Locations]
Servo data file
NC software
0880 MCS Speed command overflow
Speed command value sent from NC to inverter unit exceeded the allowable value.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX= Designated speed command value. 2^-32[2.5kHz]
[Probable Faulty Locations]
Inertia and frictional resistance of mechanical drive system
Inverter unit
Motor
Power supply voltage
0881 MCS DIFF overflow
Position error in position control is too large.
When an axis is at the target value (at standstill), the target value and calculated value
coincide with the current position. When a new axis movement command is specified, calculation of
the target value begins to generate calculated value (RCON). At this time, the current position lags
behind the calculated value by a certain amount. This lag amount ([calculated value] - [current position]) is called following error;
an alarm occurs when the following error exceeds the specified allowable value.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX= Detected position error
2^-16[pr]
pr= One revolution of position encoder
[Probable Faulty Locations]
Inertia and frictional resistance of mechanical drive system
Inverter unit
Motor
0882 MCS APA speed too large
Position encoder value (RAPA) changes with motor rotation. Amount of change in position
encoder value is monitored at designated time intervals. If axis feedrate is too fast relative to normal
rapid feedrate, or if amount of change is excessively large due to position encoder failure, etc.,
this alarm occurs when the amount of change per unit time continuously exceeds a specific allowable value.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX= Detected APA speed
2^-16[pr/Tp]
pr= One revolution of position encoder
Tp= Position control frequency
However, the following data have special meanings.
1: Linear axis exceeds stroke range.
2: Rotary axis exceeds stroke range (360°).
3: Limited axis exceeds stroke range.
[Probable Faulty Locations]
Inverter unit control board
Motor encoder (for BL motor)
Encoder link cable or connector (for BL motor)
PG or magnetic encoder (for VAC motor)
PG or magnetic encoder cable or connector (for VAC motor)
0883 MCS Full-closed position detection error
Difference between position detection value of full-closed encoder
and position detection value of motor encoder exceeded the allowable value.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX= Error detection count
[Probable Faulty Locations]
Full-closed synthesis offset value
Absolute scale or encoder with shaft
Backlash/play in drive system
0884 MCS Overspeed
Actual motor speed is too high.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX= Detected speed
[2.5kHz/4294967296]
[Probable Faulty Locations]
Inverter unit control board
Motor encoder (for BL motor)
Encoder link cable or connector (for BL motor)
Resolver or magnetic encoder (for VAC motor)
Resolver or magnetic encoder cable or connector (for VAC motor)
0885 MCS Speed deviation too large
Deviation between command speed and actual speed is too large.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Detected torque (Torque sum within 4 ms)
±[MAXTRQ/32768]
YYYY= Detected acceleration (Average value within 4 ms)
±[2.5kHz/4ms/65536]
When XXXXYYYY=00000001, error data is "0" due to underflow.
[Probable Faulty Locations]
Cutting load torque
Inverter unit
Motor
0886 MCS Collision detection
NC torque limiter detected axis interference through the relation of motor output torque = motor acceleration.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX= Detected torque (Torque sum within 4 ms)
±[MAXTRQ/32768]
YYYY= Detected acceleration (Average value within 4 ms)
±[2.5kHz/4ms/65536]
When XXXXYYYY=00000001, error data is "0" due to underflow.
[Probable Faulty Locations]
Interference of mechanical drive system
NC torque limiter setting value
Motor encoder
Inverter unit
Motor
0887 MCS Emergency stop time out
Machine failed to stop within the specified time after emergency stop function was activated.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX
1: Emergency stop time out
2: Deceleration time out at emergency stop
3: Deceleration time out at alarm stop
[Probable Faulty Locations]
Servo data file
NC software
Inverter unit control board
Motor
0888 MCS Servo axis belt breakage
Belt breakage detected on belt-driven axis.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX= Load torque at belt breakage detection [HEX]
[Probable Faulty Locations]
Belt
0889 MCS Axis change control error
Axis switching was not performed normally.
(This is not an alarm generated at MCS.)
[Code]
Newly selected axis
[Character-string]
None
[Code]
1: MCS does not reset within 10 seconds.
2: Specified and current parameter numbers do not match, or control ready signal is not ON.
3: NC failed to receive maximum APA value from encoder segment stroke within 10 seconds.
6: NC did not change in-position amount or zero offset within 10 seconds.
A: NC failed to change in-position amount or zero offset within 10 seconds after alarm occurrence.
[Probable Faulty Locations]
Wrong MCS controller for PLC axis
Faulty software
0890 MCS Stand-alone encoder initialize error
An error occurred during stand-alone encoder initialization.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= E-link sequence number at error detection
0: Reset
1: Address setting
2: Communication basic information send request
3: Communication version change
4: Device information acquisition
5: Parameter change
6: Position detection start
7: AT mode start
YY= Error description
0: Communication error
1: Transmission start time out
2: Transmission end time out
3: Reception end time out
4: Response address error
5: Response code error
6: Parameter error
ZZZZ= Data
If YY=0, encoder link status at error detection
If YY=1, 2, 3, transmitted frame information
If YY=4, address of responding device
If YY=5, received frame information
If YY=6, indicates the parameter number detected as faulty.
1: Number of received parameters is insufficient
2: Communication basic information is incompatible
3: Multi-turn detection range does not match
4: Communication protocol version is incompatible
[Probable Faulty Locations]
Stand-alone encoder
Encoder link cable or connector
Inverter unit control board
0891 MCS APA error
A calculation error occurred during APA calculation.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX
1: Linear axis assigned stroke too large
2: Semi-closed position data conversion overflow ([pr]->[pf])
3: Underflow during synthesis
4: Overflow during synthesis
5: Hybrid control input overflow
6: Hybrid control initialization overflow
[Probable Faulty Locations]
Motor encoder, encoder with shaft or scale
Servo data file
Inverter unit control board
Encoder origin offset
Motor coupling
0892 MCS Motor overload
The motor load has exceeded the specified value, activating the overload protection function.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX: Gamma of detected overload protection curve
YYYY: Cumulative data at overload detection
However, the following data has special meaning.
FFFFFFFF: The motor could not be determined automatically during electronic thermal relay initialization.
[Probable Faulty Locations]
Motor
Operation overload
Servo data file
0893 MCS Safety speed monitor E-Link error
The axis required by the specifications is not connected to the safety speed monitor via E-LINK.
[Index]
None
[Character-string]
None
[Code]
XX: Controller ID of unconnected axis
[Probable Faulty Locations]
1) The MIV unit of the axis indicated by the code is not connected via E-LINK.
2) E-LINK cable disconnected
[Measures to Take]
1) Connect the MIV unit of the axis indicated by the code via E-LINK.
2) Check the E-LINK cable.
0894 MCS Scale sub slider error
Detection cannot be performed with the sub slider of the switchable absolute scale.
[Index]
Axis or none (Spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Encoder error code
YY= Detailed status of encoder
ZZZZ= Multi-turn position data
If multi-turn position data exceeds the allowable rotation range:
XX= Fixed to 0
YY= Fixed to 1
ZZZZ= Multi-turn position data
[Probable Faulty Locations]
Sub slider
Encoder link cable of the sub slider
Inverter unit
0895 MCS Dual drive control communication error
In communication between slaves for synchronized axis tandem control,
communication data received by the slave axis is abnormal.
[Index]
Axis or none (Spindle)
[Character-string]
None
[Code]
XXXXYYZZ
XXXX= Error description
0001: The communication data counter upper limit is not reached
0002: Unknown communication data format code
YY= Communication method
00: Servo link
01: Encoder link
ZZ= Data
Fixed to "0" when XXXX=0001
Unknown format code when XXXX=0002
[Probable Faulty Locations]
Inverter unit
Servo link cable
0896 MCS Full absolute scale link error
A communication error occurred with the full absolute scale, disabling position/speed detection, etc.
[Index]
Axis or none (Spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX=FF[HEX] (Fixed)
YY=00[HEX] (Fixed)
ZZZZ= Encoder link status when error was detected
Bit 15: Separate encoder communication error
Bit 14: Absolute scale 2 communication error
Bit 13: Shaft-equipped encoder or absolute scale communication error
Bit 12: Motor encoder communication error
Bit 11: Undefined
Bit 10: AT mode transmission loop error
Bit 9: Data overflow error in reception IF section
Bit 8: Undefined
Bit 7: Undefined
Bit 6: Modulation code error
Bit 5: CRC error
Bit 4: Format error
Bit 3: Bidirectional transmission error
Bit 2: Bidirectional reception error
Bit 1: Parity error
Bit 0: Timeout error
[Probable Faulty Locations]
Full absolute scale of target axis
Encoder link cable or connector
Inverter unit control board
0897 MCS Full absolute scale error
Detection is not possible with the full absolute scale.
[Index]
Axis or none (Spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= Full absolute scale status
Bit 7: Alarm
Bit 6: Warning
Bit 5: 80um digital contrast out of range
Bit 4: 80um digital amplitude out of range
Bit 3: Undefined
Bit 2: 80um digital amplitude
1=80um digital amplitude large
0=80um digital amplitude small (valid only when bit 4 is ON)
Bits 1, 0: Absolute code check
11=3 bytes or more
10=2 bytes
01=1 byte
00=0 byte or 2 bits or less
YY= Alarm code of full absolute scale
01: Position data request after stop command
02: Control parameter error
05: Initialization speed too high
06: Pulse count error
0D: Overspeed
0E: Synchronization error
0F: Temperature abnormality
40: 80um digital amplitude level too low (offset level normal)
41: 80um digital amplitude level too low (and offset level too low)
42: 80um digital amplitude level too high
43: 80um digital contrast too low
44: 80um digital contrast too high
48: Absolute code check error
49: Absolute code check error on rise
4A: Absolute code all "0"
4B: Absolute code all "1"
ZZZZ= Full absolute scale position data
Position data per 2 mm pitch
[Probable Faulty Locations]
Full absolute scale
0898 MCS Full absolute scale initialize
An error occurred during initialization of the full absolute scale.
[Index]
Axis or none (Spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX= E-link sequence number when error was detected
0: Reset
1: Address setting
2: Request transmission of basic communication information
3: Communication version change
4: Acquire device information
5: Parameter change
6: Start position detection
7: Start AT mode
YY= Error description
0: Communication error
1: Transmission start time timeout
2: Transmission end time timeout
3: Reception end time timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ= Data
When YY=0,
Encoder link status when error was detected
When YY=1, 2, 3: Transmitted frame information
When YY=4: Address of responding device
When YY=5: Received frame information
When YY=6: Parameter number detected as erroneous.
1: Insufficient number of received parameters
2: Incompatible basic communication information
3: Multi-turn detection range mismatch
4: Incompatible communication protocol version
[Probable Faulty Locations]
Full absolute scale
Encoder link cable or connector
Inverter unit control board
0899 MCS Axis stop signal error
An abnormality was detected in the PSRDY signal input to the MCS unit.
[Index]
Axis name or none (Spindle)
[Character-string]
None
[Code]
XXXXXXXX=1 (Fixed)
[Probable Faulty Locations]
Stroke end limit switch or its signal wire
OPR cable or connector
Converter link cable or connector
POS unit
0949 IO diagnosis data file read
The NC cannot read the I/O diagnosis data file.
[Index]
None
[Character-string]
None
[Code]
1-> File not found
2-> Incorrect file attribute
[Probable Faulty Locations]
1: If the NC was operating normally before this alarm occurred, the I/O diagnosis data file must have been deleted or corrupted.
2: If the NC had not been operated after the control software was installed until this alarm occurred, the I/O diagnosis data file type must be wrong or the file is not contained in the control software.
[Measures to Take]
1: Re-install the control software.
2: Check the control floppy disk (file name, etc.) and recreate the floppy disk.
0950 IO macro data file read
The NC cannot read the macro data file.
[Index]
None
[Character-string]
None
[Code]
1-> File not found
2-> Incorrect file attribute
3-> Incorrect data arrangement in the I/O macro data file
[Probable Faulty Locations]
If the NC was operating normally before this alarm occurred, the I/O macro data file must have been deleted or corrupted.
If the NC had not been operated after the control software was installed until this alarm occurred, the I/O diagnosis data file type must be wrong or the file is not contained in the control software.
[Measures to Take]
For code 1, re-install the control software.
For codes 2 and 3, check the control floppy disk (file name, etc.) and recreate the floppy disk.
0951 SMP illegal
[Code]
WXXYYZZ
W: Main board on which an error occurred.
XX: Hexadecimal number of board status.
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
RUNHALTCPUOFF00SNMIMSTP
YY:
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
SBERSBPARCYCER0PROTDAILOOPECC
ZZ: Always 00
0952 Control board not mounted
0953 EC start
0954 Peripheral processor start
An error occurred in the peripheral processor at NC startup.
There is no response even after a certain time (20 seconds) has elapsed.
[Code]
XY
X:
A->TFP
B->FCP
Y: Internal sequence counter at startup.
X:
1-> 1st main board
2-> 2nd main board
3-> 3rd main board
4-> 4th main board
Y:
1-> Main processor startup timeout
2-> Task initialization timeout
4-> Task cannot start.
0955 Spec code data file
An error was found in the specification code.
[Index]
None
[Character-string]
[Code]
1E0000000: SVDN board is not R-spec.
1E1000000: No R-spec in spec code.
1E2000000: Spec check performed by R-spec.
ABCCCCCC
A:
1: NC spec code file (MNCSPEC*.DAT)
2: User-specific spec code file (MNCBSPC*.DAT)
B:
2: An error occurred in the following: file attributes, version information, or spec code data size of NC spec code file.
3: Project number mismatch.
4: Machine name mismatch
5: Spec code data mismatch
7: Failed to open NC spec code data change file
9: File open error
A: File read error
B: File close error
C: CRC check mismatch
D: Mismatch found in NC spec code registration
CCCCCC:
If B != 5, CCCCCC = 000000
If B = 5, XXYYZZ:
XX: Byte position causing spec code mismatch
YY: Mismatch spec code data
ZZ: Spec code data (before change)
0956 Backup data file read
Failed to read NC backup data file from memory.
[Code]
1-> There is no backup data file in memory, or the file name is incorrect.
2-> File type is not ”PBU1″.
3-> File DB is too large.
4-> File DB is too small.
0957 Graphic backup data file read
0958 Pitch error compensation data file read
[Index]
None
[Character-string]
None
An error was found in the compensation data file for inductosyn pitch error compensation specifications.
[Code]
XYYYYYYY
X:
1: B-axis
2: C-axis
YYYYYYY:
0000001: File read/open error
0000002: File read error
0000003: File attribute error (file type is not “PBU1″.)
0000004: File attribute error (no axis name)
0000005: File size error (file length is short)
0959 IGF spec mismatch
During IGF initialization, the NC detected a mismatch in specifications.
[Index]
None
[Character-string]
None
[Code]
1-> The common table in NCGEN does not match that in IGFMAIN.
2-> The number of control axes in IGF does not match the number determined by each axis data (such as axis name, linear/rotary axis).
[Probable Faulty Locations]
Defective combination of control programs
Software error
0960 IGF backup data file read
An error occurred while reading the PBU file for IGF.
[Index]
None
[Character-string]
None
[Code]
1-> MIGUC*. PBU not found.
2-> MIGUC*. PBU attribute error.
3-> MIGUC*. PBU size error.
11-> MIGUM*. PBU not found.
12-> MIGUM*. PBU attribute error.
13-> MIGUM*. PBU size error.
21-> MIGUG*. PBU not found.
22-> MIGUG*. PBU attribute error.
23-> MIGUG*. PBU size error.
31-> MIGU1*. PBU not found.
32-> MIGU1*. PBU attribute error.
33-> MIGU1*. PBU size error.
41-> MIGU4*. PBU not found.
42-> MIGU4*. PBU attribute error.
43-> MIGU4*. PBU size error.
[Probable Faulty Locations]
Memory board fault
Software error
0961 IGF abnormality
An error occurred during IGF initialization, preventing IGF from starting.
[Index]
None
[Character-string]
None
[Code]
None
[Probable Faulty Locations]
Software error
0962 CCP Roader file load
0963 CCP Application file load
0964 CCP Parameter file load
0965 Configuration file format error
The configuration file contains erroneous data.
[Index]
None
[Character-string]
Environment variable in the erroneous data line
[Code]
None
[Probable Faulty Locations]
Defective configuration file creation
0966 Configuration file open error
0967 Subscript range check table error
An alarm occurs if the system variable number to be set is not found in the array limit check table when setting the array-type system variable table in accordance with the spec code.
[Index]
None
[Character-string]
None
[Code]
None
[Measures to Take]
In MMSC,
check CQARCKT1 and CQARCKT12.
Make sure that the code corresponding to the system variable number that caused the alarm is registered in the table.
0968 No such specification
0969 Memory size mismatch
0970 Synchronized axis spec code
Improper setting of spec code used to designate synchronized control axes.
1) The number of axes (including slave axes) is greater than 16.
2) A rotary axis is designated as a synchronized control axis.
[Index]
None
[Character-string]
None
[Code]
In the case of 1) above, total number of axes including slave axes
In the case of 2) above, index of designated rotary axis
60-> 4th axis
80-> 5th axis
[Probable Faulty Locations]
Spec code
[Measures to Take]
Create spec code again.
[Related Specifications]
Synchronized axis specifications
0971 Cache data / initialization error
An error occurred during cache data initialization.
[Code]
XYYYY
X:
1-> An error occurred during initialization of No. 1 main macro.
2-> An error occurred during initialization of No. N main macro.
YYYY:
0001: TRAP branch information error
0010: Abnormal termination
0988 Cache data operation error termination
An error occurred during cache data operation.
[Code]
XYYYY
X:
1-> Cache data operation registration processing
2-> Cache data operation read processing
0989 CPU information table data incorrect
The value in the CPU information table is outside the setting range.
[Code]
XXYYZZZZ
XX:
1->No. 1 main board
2->No. 2 main board
3->No. 3 main board
4->No. 4 main board
5->No. 5 main board
6->No. 6 main board
YY: Application information table
1->No. 1 table
2->No. 2 table
3->No. 3 table
4->No. 4 table
ZZZZ: Table index value
0990 Task making error
Failed to create a task.
[Code]
XXXXYYYY
XXXX: Failed task ID creation
YYYY:
1-> Task ID error (target task already exists).
2-> No TCB area (number of tasks exceeds 16).
0991 Task information table data incorrect
The value in the task information table is 0.
[Code]
XXYYZZZZ
XX: Main processor where error was detected
1->No. 1 main board
2->No. 2 main board
3->No. 3 main board
4->No. 4 main board
5->No. 5 main board
6->No. 6 main board
YY: Application information table
1->No. 1 table
2->No. 2 table
3->No. 3 table
4->No. 4 table
ZZZZ: Table index value
0992 PLC backup data file reading
Failed to read the PLC backup data file or M-code data file from memory.
[Code]
None->M-code data file error
1->PLC backup data file is not available, or file name is different.
2->Failed to open PLC backup data file.
0996 PLC axis data file
PLC axis control constants do not match machine specifications.
[Index]
None
[Character-string]
PLC axis name
[Code]
1: Axis name loaded from PLC axis data file does not match actually mounted axis name.
2: File type is not ”PBU1″.
3: File has DB that is too large.
4: Data specified in PLC axis data file is different from that in SVP data file.
7: An error occurred when opening PLC axis data file. File is too short. File name or device name error.
8: Although axis name in PLC axis data file is an Okuma specification name, it differs from registered name.
9: PLC axis data file is too small.
15: Number of PLC axes exceeds 8.
16: A PLC axis number exceeds 8.
17: Although the axis changeover specification (function generation spec B bit 0) is set, the drive axis rotary axis gear ratio is 0.
18: Although the axis changeover specification (function generation spec B bit 0) is set, the driven axis rotary axis gear ratio is 0.
19: Although the axis changeover specification (function generation spec B bit 0) is set, the drive axis lead pitch is 0.
1A: Although the axis changeover specification (function generation spec B bit 0) is set, the driven axis lead pitch is 0.
1B: Although the point positioning specification (function generation spec B bit 6) is set, the rotary axis specification (servo data file) is not set.
1C: Although the arbitrary positioning specification (function generation spec B bit 7) is set, the linear axis is not set.
1D: The drive axis with an independent encoder axis was not found, or the drive axis is not set.
1E: Multiple axes are designated as drive axes with an independent encoder axis.
1F: The detected axis rotation speed with an independent encoder axis is 0; this data is set by MCS at power-on.
20: The rotary axis gear ratio (EQDGT) or conversion factor (ESRDGT) with an independent encoder axis is not set. (Set value: 0)
21: Axis changeover and table changeover are designated at the same time.
[Probable Faulty Locations]
1) PLC axis data file error
21… Power off during axis changeover control.
Or software error
0997 PLC monitor backup data file reading
The PLC monitor backup data file cannot be read from memory.
[Code]
1-> The file is not available, or the file name is different.
2-> Cannot open the file.
3-> Cannot read the file (no file data).
4-> Not a backup file.
5-> Cannot close the file.
6-> The file is too small.
7-> The file is too large.
0998 PLC sequence program load
The PLC sequence program cannot be loaded.
[Index]
None
[Character-string]
None
[Code]
XYYYY
When X=1, file is not available.
When X=2, an error occurred during loading.
YYYY=0001
End of file received without loading any characters.
YYYY=0002
End of file received during file loading.