OSP-U10L Chapter 7 Alarm D

SECTION 7 ALARM D

4035 Memory board battery change
Eeoelale6001 The battery on the memory board must be replaced. Battery life has expired. Do not turn off power.
Contact OKUMA.
[Code]
1-> Battery voltage has dropped to the level requiring replacement.
2-> A certain period of time has elapsed since software installation.
3-> Memory board has been removed for a certain period of time.
[Probable Fault Cause]
Battery life has expired
[Measures to Take]
Replace the battery.
4036 Key code data reception error
Eeoelale6002 CRP board has received abnormal data entered from the operation panel.
[Code]
XX
Bits 0-3-> Always 0
Bit 4-> Parity error in received data
Bit 5-> Timeout
Bit 6-> Framing error in received data
Bit 7-> Always 0
[Probable Fault Cause]
1) CRP board
2) Operation panel
3) Faulty connecting cable between them
4) CRP board and operation panel
[Measures to Take]
1) Replace the CRP board.
2) Replace the operation panel.
3) Check the connecting cable between the CRP board and the operation panel, and replace if necessary.
4037 CCP-CPU error
Eeoelale6003 An error occurred in the CPU of the CCP board used for DNC-B communication.
(To clear this alarm, power must be turned off and then on again).
[Code]
1-> Parity write error occurred during CCP memory test.
2-> Error loading CCP control program.
3-> CCP communication program is not functioning.
4-> CCP communication channel was not opened properly.
5-> Error detected during CCP self-diagnosis.
6-> An error occurred in the CPU of the CCP board.
7-> CCP control program operation error. (Task control error)
8-> CCP control program operation error. (Real-time task loop error)
9-> CCP control program operation error. (Time-sharing task switching control error)
[Measures to Take]
Defective CCP board
Check if CCP control software is stored in memory
Defective memory
CCP control software error
Switch setting error on CCP board
4052 PLC backup data file write disable
Eeoelale6004 PLC backup data file cannot be stored.
[Code]
LC37-003 P-342
SECTION 7 ALARM D
Type of backup data
[Probable Fault Cause]
Defective memory board
[Measures to Take]
Replace the memory board.
4054 ACP key code data reception error
Eeoelale6005 ACP board has received abnormal data entered from the operation panel.
[Code]
XX
XX:
Bit 0 (Fixed)
Bit 1 (Fixed)
Bit 2 (Fixed)
Bit 3 (Fixed)
Bit 4 (Fixed)
Bit 5 Operation panel CPU error
Bit 6 Initialization error
Bit 7 Communication error
[Probable Fault Cause]
Defective ACP board
Defective operation panel
Disconnection or poor contact of connecting cable between ACP board and operation panel.
4055 In safe speed limit
Eeoelale6111 Speed is limited to the safe speed limit value set in the data file.
[Object]
Axis
[Measures to Take]
Close the safety guard
4056 J-type encoder in adjustment
Eeoelale6112 Initial offset setting of J-type encoder in progress.
[Object]
None
[Character String]
Related axis name
[Code]
None
4150 MCS unregistered alarm
Eeoelale6006 An axis-control-related error occurred on the MCS.
[Object]
Axis name or none (spindle)
[Character String]
Alarm number (Decimal)
[Code]
Alarm code
[Probable Fault Cause]
Depends on the alarm number indicated by the character string.
Notify machine tool builder of the character string and code.
LC37-003 P-343
SECTION 7 ALARM D
4151 MCS exception processing
Eeoelale6007
Fatal error occurred in the MCS axis control unit or during MCS software execution.
[Object]
Axis name or none (spindle)
[Character String]
Detected alarm cause
“#1”-> Control board abnormality
“#2”-> Low control board ±12V power supply voltage
“#3”-> OPF error
“#11”-> Low control board 5V power supply voltage
“#12”-> Axis control unit inverter bridge short-circuited
“#13”-> IPM protection activated
“#14”-> Motor overcurrent
“#20”-> INT6 loop error
“#21”-> INT5 loop error
“#22”-> INT4 loop error
“#23”-> INT3 loop error
“#24”-> INT2 loop error
“#25”-> INT1 loop error
“#26”-> Access disabled
“#27”-> Initialization RAM check error
“#28”-> Parity check error
“#29”-> Watchdog error
“#30”-> IRQ7 interrupt
“#31”-> NMI (Non-maskable interrupt)
“#32”-> General illegal instruction
“#33”-> Slot illegal instruction
“#34”-> CPU address error
“#35”-> DMA address error
“#36”-> Undefined trap error
“#37”-> Undefined interrupt
“#38”-> DMAC
“#39”-> ITU
“#40”-> SCI
“#41”-> REF
“#42”-> A/D
“#43”-> System reserved
“#44″-> User break
[Code]
For #1, the code indicates the control board error details.
For #2, the code indicates the operation program file error details.
1: Identification code ”OPF1″ error
2: End code ”ED” error
3: Checksum error
4: Board name error
For #11 - #14, #20 - #21, #25 - #26, and #30 - #31, the code indicates error status register contents.
[Probable Fault Cause]
In the case of #1:
Inverter unit
In the case of #3:
Option program file error
Mismatch between option program file and inverter unit
When character string is #2 or #11:
Defective power supply unit (usually this alarm occurs on multiple inverter units simultaneously)
When character string is #12, #13, or #14:
Inverter unit
When character string is other:
Inverter unit
LC37-003 P-344
SECTION 7 ALARM D
4152 MCS process error
Eeoelale6008
MCS
[Object]
Axis name or none (spindle)
[Character String]
None
[Code]
XXZZAAAA
XX:
04… Self-diagnosis data error. (ZZ is received data)
06… A-buffer software sync bit or format code error.
07… B-buffer software sync bit or format code error.
08… Data communication error.
ZZ indicates data type; AAAA is always 0.
ZZ:
1… Command speed (8408)
2… Laser linear scale value (4413)
3… Backlash (4406)
4… Actual position without position error compensation (440A)
5… Position error compensation amount (4403)
6… Full-closed loop encoder value (4410)
7… Semi-closed loop encoder value (4411)
8… ODIFF (4415)
10… APA (actual position) within sector stroke (4404)
11… Acceleration/deceleration time during positioning (4422)
12… Zero offset amount
13… In-position width (4420)
14… Sector stroke maximum value (4405)
15… Point data change
[Probable Fault Cause]
Defective MCS controller
Software error
4153 MCS CON APA deviation
Eeoelale6009 The deviation between CON and APA exceeds the set value. The deviation between CON and APA (DIFF), also called following error, equals the difference (absolute value) between the command position value written to the MCS and the actual position
value read from the MCS. The NC control software monitors this deviation value during axis movement.
This alarm is issued when a fatal error occurs in the MCS, disabling monitoring of this deviation value.
[Object]
Axis name
[Character String]
None
[Code]
Absolute value of deviation expressed in hexadecimal (basic unit)
[Probable Fault Cause]
Defective MCS controller
Mismatch between MCS data and NC data
4154 MCS power supply unit abnormality
Eeoelale6010 Power supply unit failure occurred.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
AAAAAAXX
LC37-003 P-345
SECTION 7 ALARM D
AAAA is normally 0.
X: Alarm No.
0: DC voltage alarm
1: Input voltage error
2: Control power supply error
3: Control status error
4: Regenerative circuit overload
5: Heat sink overheat
6: CPU error
7: Reserve
Y: Power supply unit status
Bit 3 1: Power supply unit failure occurred (alarm signal status is 0)
Bit 2 1: DC applied
Bit 1 1: OPRON input point closed (axis control ON command)
Bit 0 1: PWON input point closed (input power ON command)
ZZ: Data
When X (alarm No.) is 0: Detected DC voltage represented in hexadecimal [3.9V]
When X (alarm No.) is 1: Detected AC voltage represented in hexadecimal [3.1V]
When X (alarm No.) is 2:
1: +5V voltage error
2: +12V voltage error
3: -12V voltage error
When X (alarm No.) is 3:
1: Inverter overcurrent
2: Power module error
3: Inverter short circuit
4: Regenerative circuit error (power regenerative type)
5: Regenerative circuit error (resistor discharge type)
When X (alarm No.) is 4: Undefined
When X (alarm No.) is 5: Undefined
When X (alarm No.) is 6: Undefined
[Probable Faulty Locations]
When control power supply is abnormal:
- Power supply unit
When voltage is low:
- Plant power supply voltage is low or faulty, power supply input power fuse blown, or instantaneous power failure
When voltage is high:
- Power supply unit
4155 MCS Converter loop error
Eeoelale6011 An error occurred in the converter loop (communication between the power supply unit and axis control unit), disabling the NC from monitoring the status of the power supply unit.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
XAAAAAYY
AAAAA is always 0.
X = 0: Communication error
X = 1: Time-out error (communication interrupted)
YY = Communication status
When X = 1, YY is 0
[Probable Faulty Locations]
- Converter loop cable or connector
- Power supply unit
- Inverter unit control board
LC37-003 P-346
SECTION 7 ALARM D
4156 MCS DC inverter DC link voltage error
Eeoelale6012 The DC link voltage of the inverter unit rose abnormally or dropped, interrupting the current supply.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX = Detected overvoltage value [15.3mV]
YYYY = Detected undervoltage value [15.3mV]
[Probable Faulty Locations]
When voltage rises:
- Power supply unit
When voltage drops:
- Power supply unit
- Inverter unit
- Instantaneous power failure
4157 MCS Motor overcurrent
Eeoelale6013 Motor winding overcurrent was detected in the inverter unit.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX = Detected U-phase current value at alarm occurrence represented in signed hexadecimal [3FFF rated value]
YYYY = Detected V-phase current value at alarm occurrence represented in signed hexadecimal [3FFF rated value]
[Probable Faulty Locations]
- Inverter unit fault
- Defective motor insulation
4158 MCS Inverter overheat
Eeoelale6014 The temperature of the inverter unit rose abnormally.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
1 fixed
[Probable Faulty Locations]
- Inverter unit
- Overload operation
4159 MCS Inverter overload
Eeoelale6015 The load on the inverter unit exceeded the rating, activating overload protection.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
LC37-003 P-347
SECTION 7 ALARM D
YYYYZZZZ
YYYY-> "GAMMA" protection curve value used to detect overload
ZZZZ-> Internally calculated overload data
[Probable Faulty Locations]
- Inverter unit
- Overload operation
4160 MCS Power supply voltage error
Eeoelale6016 The input power supply voltage of the power supply unit is excessively high or low.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
Detected abnormal voltage value represented in hexadecimal [V]
[Probable Faulty Locations]
- Power supply unit
- Power supply cable or connector
- Instantaneous power failure
4161 MCS Inverter version error
Eeoelale6017 The rated current value of the inverter unit is smaller than the current limit value specified by the servo data file.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
1 (fixed)
[Probable Faulty Locations]
- Inverter unit
- Servo data file
4162 MCS Winding changeover error
Eeoelale6018 The magnetic contactor used for motor winding changeover did not pick up.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
YYYYZZZZ
When YYYY = 0000:
ZZZZ = 0001: Low-speed winding changeover contactor picked up.
ZZZZ = 0002: High-speed winding changeover contactor picked up.
ZZZZ = 0003: Both high-speed winding changeover contactor and low-speed winding changeover contactor picked up simultaneously.
ZZZZ = 0004: Winding changeover operation timed out
When YYYY = 1010:
ZZZZ = 0001: Servo data file error
[Probable Faulty Locations]
Winding changeover magnetic contactor
LC37-003 P-348
SECTION 7 ALARM D
4163 MCS Encoder communication error
Eeoelale6019 Because of a communication link error with the position encoder, the speed and position of the controlled axis cannot be detected.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX = FF (fixed)
YY = 00: Motor encoder detection error.
01: Axis encoder detection error.
02: Separate encoder detection error.
03: Absolute linear scale detection error.
ZZZZ = Indicates the encoder connection status and type of each communication error at the time of error occurrence.
Bit 15 1: Error in communication with separate encoder
Bit 14 1: Error in communication with absolute linear scale 2
Bit 13 1: Error in communication with absolute linear scale and axis encoder
Bit 12 1: Error in communication with built-in motor encoder
Bit 11 1: Error in automatic mode transmission cycle
Bit 10 1: Data overflow error occurred in interface receiver
Bit 9 1: Undefined
Bit 8 1: Undefined
Bit 7 1: Undefined
Bit 6 1: Modulation code error
Bit 5 1: CRC error
Bit 4 1: Format error
Bit 3 1: Double transmission error
Bit 2 1: Double reception error
Bit 1 1: Parity check error
Bit 0 1: Time-out error
[Probable Faulty Locations]
- Built-in motor encoder, absolute linear scale, axis encoder, or separate encoder of the faulty axis
- Encoder connection cable or connector
- Inverter unit control board
4164 MCS Encoder error
Eeoelale6020 The motor encoder cannot detect position data.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX = Encoder error code related to encoder type
YY = Detailed status of encoder related to encoder type.
ZZZZ = Multi-turn position data when multi-turn position data is out of rotation range
XX = 0 (fixed)
YY = 1 (fixed)
ZZZZ = Multi-turn position data
[Probable Faulty Locations]
Motor encoder
4165 MCS Encoder initialization error
Eeoelale6021 An error occurred during initialization of the motor encoder.
[Object]
Axis name or none (spindle)
[Character-string]
LC37-003 P-349
SECTION 7 ALARM D
None
[Code]
XXYYZZZZ
XX = Link sequence No. at error occurrence
0: Reset
1: Network address setting
2: Communication basic information request
3: Communication version modification
4: Device information acquisition
5: Parameter modification
6: AT (automatic) mode start
YY = Error content
0: Communication error
1: Transmission start time exceeded
2: Transmission end time exceeded
3: Reception end time exceeded
4: Response address error
5: Response code error
6: Parameter error
ZZZZ = Additional data
If YY = 0, encoder link status "C2ERR" at error occurrence.
If YY = 1, 2, 3, transmitted frame information QC2MINF.
If YY = 4, network address of responding device.
If YY = 5, received frame information QC2RXINF.
If YY = 6, alarm cause number caused by parameter.
1 = All required parameters were not received.
2 = Basic communication information is incompatible.
3 = Multi-turn detection range does not match.
[Probable Faulty Locations]
- Motor encoder
- Encoder connection cable or connector
- Inverter unit control board
4166 MCS Axis encoder error
Eeoelale6022 The axis encoder cannot detect position data.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
Same as for <MCS Encoder error> alarm
[ Probable Fault Cause]
Shaft encoder.
4167 MCS Shaft encoder initialize error
Eeoelale6023 An error occurred during initialization of the shaft encoder.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
Same as alarm <MCS Encoder initialize error>
[ Probable Fault Cause]
Shaft encoder
Cable or connector connected to shaft encoder
Inverter unit control board
LC37-003 P-350
SECTION 7 ALARM D
4168 MCS Absolute scale error
Eeoelale6024 Position data cannot be detected by the absolute scale.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
Same as alarm <MCS Encoder initialize error>
[ Probable Fault Cause]
Absolute scale
Cable or connector connected to encoder
Inverter unit control board
4169 MCS Absolute scale initialize error
Eeoelale6025 An error occurred during absolute scale initialization.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
Same as alarm <MCS Encoder initialize error>
[ Probable Fault Cause]
Absolute scale
Cable or connector connected to encoder
Inverter unit control board
4170 MCS Magnetic encoder error
Eeoelale6026 Motor speed cannot be detected by magnetic pulse generator. Or, the number of magnetic encoder gear teeth does not match data in the MCS file.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
XXXXYYYY
XXXX = Error description
A->A – phase voltage error
B->B – phase voltage error
C-> Magnetic encoder data error
Others-> Servo data file setting value (PG teeth * 4 - 1) checked when magnetic encoder count overflows
YYYY = Additional error data (varies depending on XXXX)
If XXXX is A: A-phase voltage value
If XXXX is B: B-phase voltage value
If XXXX is C: 0 (fixed)
Others-> Detected magnetic encoder count value (PG teeth * 4 - 1)
[ Probable Fault Cause]
Defective magnetic encoder or faulty wiring, or clearance between magnetic pulse encoder and gear is too large
The number of magnetic encoder gear teeth does not match the servo data file
4171 MCS Resolver error
Eeoelale6027 Resolver does not output any signals.
LC37-003 P-351
SECTION 7 ALARM D
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
1 (fixed)
[ Probable Fault Cause]
Defective resolver, broken wire, or poor contact of connector
4172 MCS Pulse generator count overflow
Eeoelale6028 Count value per revolution of PG (pulse generator) differs from the specified value in the servo data file.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
XXXXYYYY
XXXX = Setting value in servo data file PBU (count value per revolution of PG)
YYYY = Actual count value
[ Probable Fault Cause]
Defective PG
The number of PG gear teeth does not match the servo data file
4173 MCS Motor overheat
Eeoelale6029 Motor temperature rose abnormally.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
YYYYZZZZ
YYYY = 0 (fixed)
ZZZZ = 0010: Motor overheat
ZZZZ = 0011: Overheat detected from motor.
ZZZZ = 0012: Overheat detected from encoder.
ZZZZ = 0013: Overheat detected from both motor and encoder.
[ Probable Fault Cause]
VAC motor fan failure, dirty heat sink, frequent forward/reverse rotation and stopping
BL motor
BL motor encoder detected overheat.
4174 MCS Servo link communication error
Eeoelale6030 A communication error occurred in the servo link, disabling the servo unit from receiving commands from NC.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
XXXXYYYY
XXXX = 0 (fixed)
YYYY = Bit number indicating the type of communication error (servo link error status when failure occurred)
Bit 15 1: 2B buffer error
Bit 14 1: 2A buffer error
LC37-003 P-352
SECTION 7 ALARM D
Bit 13 1: 1B buffer error
Bit 12 1: 1A buffer error
Bit 11 1: MT buffer error
Bit 10 1: Relay processing error
Bit 9 1: Data overrun error in interface receiver section
Bit 8 1: Wire breakage error
Bit 7 1: Address pointer error
Bit 6 1: Modulation code error
Bit 5 1: CRC format error
Bit 4 1: Format error
Bit 3 1: Double transmission error
Bit 2 1: Double reception error
Bit 1 1: Parity error
Bit 0 1: Timeout error
[ Probable Fault Cause]
Inverter unit control board
Servo link cable or wiring connector
FCP board
4175 MCS Servo link broken line
Eeoelale6031 The servo link is broken, disabling the servo unit from receiving commands from NC.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
XXXXYYYY
XXXX = Disconnected location:
0… Disconnected near the relevant unit
8000… Disconnected before the relevant unit
YYYY = Servo link error status at error occurrence
[ Probable Fault Cause]
Servo link cable or connector
Inverter unit control board
FCP board
4176 MCS Servo link protocol error
Eeoelale6032 The NC and inverter unit exchange commands and responses (communication) via the servo link at fixed cycles according to specified protocols; an incorrect protocol or timing causes communication failure between NC and inverter
unit.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
Error description number
1: A-buffer software synchronization error
2: A-buffer format code error
3: B-buffer software synchronization error
4: B-buffer format code error
5: B-buffer block number error
[ Probable Fault Cause]
Inverter unit control board
NC software
Mismatch between inverter unit control board and NC software
FCP board
LC37-003 P-353
SECTION 7 ALARM D
4177 MCS Servo data error
Eeoelale6033
Servo data sent from NC for initialization or operation does not match the inverter unit.
If this alarm occurs after replacing the inverter unit, the servo data may not match the control unit.
If this alarm occurs after adjusting or modifying servo data, modification of the servo data may be erroneous.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
XXXXYYZZ
XXXX = Data identification number ID of data causing error
YY = Group number of data causing error
ZZ = Error description
1: Setting range over
2: Setting timing error
3: Not transferred
4: Calculation error
5: Other
[ Probable Fault Cause]
Incompatibility between servo data file and inverter unit
Incompatibility between inverter unit and NC software
Inverter unit control board
NC software
4178 MCS Command error
Eeoelale6034 Commands and responses between the NC and inverter unit are exchanged via the servo link; if a command sent from the NC to the inverter unit is abnormal or cannot be executed, communication failure occurs.
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
XXXXYYYY
XXXX =
10: Positioning mode, commanded points exceeded
11: Positioning mode, negative command value
12: Positioning mode, commanded position too large (e.g., position commanded for rotary axis > 360 degrees:)
13: Positioning mode, R positioning point table not transferred
14: Positioning mode, non-rotary axis
15: Positioning mode, not point group command format
16: Positioning mode, positioning sub-mode error
21: Parameter change, number of parameters exceeds specified range
22: Mode, undefined mode
23: Mode, positioning/tool path mode condition
24: Coordinate system, coordinate system designation error
30: In control command for buffer A of S-connection, unused ”bit data” is set to ON.
31: In control command for buffer B of S-connection, unused ”bit data” is set to ON.
40: AT (automatic) mode was selected without receiving time synchronization command.
YYYY = Error data
X = 10 to 16 indicates positioning sub-mode
0: Program mode 1: Search mode 2: PH mode 3: Teach mode
[ Probable Fault Cause]
Incompatibility between inverter unit and NC software
Inverter unit control board
NC software
LC37-003 P-354
SECTION 7 ALARM D
4179 MCS CON overspeed
Eeoelale6035
Position command increment (SRCON) sent from NC to axis control unit exceeds allowable value.
If this alarm occurs on a positioning axis, the servo data file may be erroneous (because position command increment is verified by inverter unit).
[ Object]
Axis name or none (spindle)
[ Character-string]
None
[ Code]
Absolute value of position command increment during acceleration/deceleration [(pr/65536)/Tp]
pr = Position encoder 1 revolution Tp = Position control cycle
The following code has a specific meaning:
1: Because the position increment value is too large, an error was detected during pre-check.
2: Absolute value of position command value (SRCON) exceeded the encoder measurement range. (Linear axes only).
[Probable Fault Cause]
Servo data file
NC software
4180 MCS Velocity command overspeed
Eeoelale6036 The speed command issued from the NC to the inverter unit exceeded the limit value.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
Speed command value [(rev/4294967269)/Tv]
rev = 1 motor revolution; Tv = Speed control cycle
[Probable Fault Cause]
Servo data file
NC software
4181 MCS DIFF excessive
Eeoelale6037
Position error in position control is excessive.
When an axis reaches the target position or stops, the target position value and the calculated value are the same. When a new axis movement command starts executing, the NC begins calculating the command value
(RCON) toward the target value. This calculation continues until the target position is reached. During axis motion, the actual position has a certain delay relative to the commanded position; their difference is called "following error".
An alarm occurs when the following error exceeds the set value.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
Absolute value of following error [pr/65536]
pr = 1 revolution of position encoder
[Probable Fault Cause]
Overload due to ballscrew or bearing failure
Motor
Inverter unit
Servo data file
4182 MCS APA overspeed
Eeoelale6038
The position encoder count value (RAPA) changes with motor rotation. The NC periodically checks changes in the position encoder count value.
LC37-003 P-355
SECTION 7 ALARM D
This alarm occurs when the amount of change per unit time exceeds the set allowable range. For example, it occurs when an axis feedrate is abnormally higher than the normal rapid traverse rate, or when the count value changes abnormally due to a position encoder failure.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
Amount of change (absolute value) in position detection value per position control cycle [1/65536 revolution of position encoder/position control cycle]
The following code values have specific meanings:
1 = Linear axis overtravel.
2 = Rotary axis overtravel (360 degrees), or position data of limited axis is negative.
3 = Limited axis overtravel.
[Probable Fault Cause]
Motor encoder (BL motor)
Encoder connection cable or connector (BL motor)
PG or magnetic encoder (VAC motor)
PG or magnetic encoder connection cable or connector (VAC motor)
Inverter unit control board
4183 MCS Full-closed loop position detection error
Eeoelale6039 The difference between the position detection value of the full-closed loop encoder and that of the motor encoder exceeded the allowable value.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
Detected number of errors
[Probable Fault Cause]
Synchronous offset data of the full-closed loop encoder is not set or data is incorrect.
Defective absolute scale or position encoder on the axis
Excessive lost motion of drive system (poor rigidity between motor and moving part).
Timing belt tooth disengagement or broken belt
Loose coupling between motor shaft and ballscrew
Position loop gain does not match machine (too high)
4184 MCS Overspeed
Eeoelale6040 Actual motor speed is too high.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
Detected speed value when alarm occurred [(rev/4294967296)/Tv]
rev = 1 motor revolution; Tv = Speed control cycle
[Probable Fault Cause]
Motor encoder (BL motor)
Encoder connection cable or connector (VAC motor)
Resolver or magnetic encoder (VAC motor)
Resolver or magnetic encoder connection cable or connector (VAC motor)
LC37-003 P-356
SECTION 7 ALARM D
Inverter unit control board
4185 MCS Velocity deviation excessive
Eeoelale6041 The speed deviation between the actual motor speed and the command speed is excessive.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX: Detected torque (sum of torque data sampled for 3.2 ms)
2-12[MAXTRQ]
When Tv = 0.4 ms, instantaneous maximum torque is 7FFF (hexadecimal)
When Tv = 0.8 ms, instantaneous maximum torque is 3FFF (hexadecimal)
YYYY: Detected acceleration (average value over 3.2 ms)
2-16[vr/3.2ms/3.2ms]
= approx. 0.1 [rpm/ms]
00000001 indicates that data at error became zero due to exponent underflow.
[Probable Fault Cause]
Motor does not rotate due to mechanical failure or excessive load.
4186 MCS Collision detection
Eeoelale6042 By using the NC torque limit function and monitoring the relationship between motor output torque and acceleration, it is determined whether a collision has occurred.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXYYYY
XXXX: Detected torque (sum of torque data sampled for 3.2 ms)
± 2 ∽ 12[MAXTRQ]
When Tv = 0.4 ms, instantaneous maximum torque is 7FFF (hexadecimal)
When Tv = 0.8 ms, instantaneous maximum torque is 3FFF (hexadecimal)
YYYY: Detected acceleration (average value over 3.2 ms)
± 2 ∽ 16[vr/3.2ms/3.2ms]
= approx. 0.1 [rpm/ms]
[Probable Fault Cause]
Collision
Motor encoder
NC torque limit setting value
4187 MCS Emergency stop timeout
Eeoelale6043 Emergency stop operation was not completed within the specified time.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXXXXX
1: Emergency stop time exceeded
2: Deceleration time at emergency stop exceeded
3: Deceleration stop time at alarm occurrence exceeded
[Probable Fault Cause]
Inverter unit control board
LC37-003 P-357
SECTION 7 ALARM D
NC software
4188 MCS Servo axis belt breakage
Eeoelale6044 The drive belt of the belt-driven axis broke.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
Load torque when belt broke (hexadecimal)
[Probable Fault Cause]
Belt broken
4189 MCS Axis switching control error
Eeoelale6045 Axis switching operation error (this alarm is not displayed on MCS)
[Object]
Axis name after switching
[Character-string]
None
[Code]
1 MCS was not reset within 10 seconds.
2 "Parameter group number matched" signal or "Control ready completed" signal did not turn ON within 10 seconds.
3 The APA maximum value of the separate encoder could still not be received within 10 seconds.
6 In-position width or zero offset change was not completed within 10 seconds.
A In-position width or zero offset change was not completed within 10 seconds after alarm
[Probable Fault Cause]
MCS controller for PLC axis
Software error
4190 MCS Separate encoder initialization error
Eeoelale6046 An error occurred during initialization of the separate encoder.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXYYZZZZ
XX-> Connection sequence number when error occurred
0: Reset
1: Network address setting
2: Basic communication information request
3: Communication version change
4: Device information acquisition
5: Parameter change
6: AT (Auto) mode start
YY-> Error content
0: Communication error
1: Transmission start timeout
2: Transmission end timeout
3: Reception end timeout
4: Response address error
5: Response code error
6: Parameter error
ZZZZ-> Additional data
YY = 0: Encoder connection status at error "C2ERR"
YY = 1, 2, 3: Transmitted frame information QC2MINF
LC37-003 P-358
SECTION 7 ALARM D
YY = 4: Network address of responding device
YY = 5: Received frame information QC2RXINF
YY = 6: Cause of alarm due to parameter No.?1 = Not all required parameters were received
2 = Basic communication information is incompatible
3 = Multi-turn detection range mismatch
[Probable Fault Cause]
Separate encoder
Encoder connection cable or connector
Inverter unit control board
4191 MCS APA error
Eeoelale6047 An error occurred during APA calculation.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
XXXXXXXX
1: Linear axis partitioned stroke exceeded
2: Overflow during [pr]-[pf] conversion at semi-closed loop position
3: Underflow during axis composite data generation
4: Overflow during axis composite data generation
5: Overflow at hybrid control input
6: Overflow at hybrid control initialization
[Probable Fault Cause]
Motor encoder, axis encoder, or absolute linear scale
Inverter unit control board
Servo data file
If the alarm code is "1" or "3", the encoder (or sensor) zero offset data is faulty.
If the alarm code is "4", the servo data file is often faulty.
If the alarm code is "5" or "6", the motor coupling is often loose, or mounting of the shaft encoder or absolute linear scale is loose.
4192 MCS Motor overload
Eeoelale6048 The overload protection function activated because the motor load exceeded the specified value.
[Object]
Axis name or none (spindle)
[Character-string]
None
[Code]
YYYYZZZZ
YYYY-> g curve for overload detection protection
ZZZZ-> Cumulative data for overload detection
[Probable Faulty Locations]
Motor
Overload operation
Servo data file error
4200 Parameters requiring power-on to take effect are set
Eeoelale6049 A parameter that becomes effective only after turning power off and then on has been set.
Operation example: When the set parameter is related to RS232C, the corresponding alarm indicator lamp lights up.
[Measures to Take]
After backing up parameters with the function key, turn the power off and then on again.
LC37-003 P-359
SECTION 7 ALARM D
4201 Machining management data backup stop
Eeoelale6050 Machining management data cannot be stored in the backup data file.
[Probable Faulty Locations]
Memory board fault
Software error (the backup data file of management data has been corrupted).
[Measures to Take]
Replace the memory board.
Check the corresponding software.
The alarm can be cleared only after turning power off and then on again.
4202 DNC-B communication system error
Eeoelale6051 An unrecoverable error occurred in protocol A communication (this alarm can be cleared only after turning power off and then on again).
[Code]
1-> No reception response when operation ready is not completed.
2-> DR signal turned off when operation ready is not completed.
3-> Checksum parity error occurred when operation ready is not completed.
4-> "Time out" or "framing" error occurred when operation ready is not completed.
5-> Reception buffer register overflow
[Probable Faulty Locations]
RS232 interface fault
Host computer hardware or software fault
The actual communication specifications (baud rate, code, configuration, etc.) do not match the communication parameter settings.
[Measures to Take]
Check the host computer hardware or software.
Change communication to another channel by modifying communication parameters, and reconnect the communication connector on the RPP board to the other channel position.
Check the following parameters to verify whether the actual communication connection matches the parameter settings:
Channel of RS232C interface being used
Data parity
Number of stop bits
Transmission code specification
End code
Baud rate
[Related Specifications]
DNC-B
4203 DNC-B communication error
Eeoelale6052 Communication error occurred in protocol A communication with host computer.
[Code]
XXXXXXYZ
XXXXXX: Command received when error occurred, expressed in hexadecimal (ISO or ASCII code).
Y: CNC status when communication alarm occurred.
0-> Operation ready is not completed.
1-> CNC normal state
2-> Remote operation state
3-> Alarm state
Z: Cause
1-> "Checksum" error has occurred Ne times consecutively (parameter setting).
2-> "Parity" error (higher than RS232C) has occurred Ne times consecutively (parameter setting).
5-> DR signal is off or no response
6-> Unexpected information received (including [RTY]MING31 occurring Ne times consecutively).
9-> Information received from the host computer while the controller is not in response wait state.
[Probable Faulty Locations]
LC37-003 P-360
SECTION 7 ALARM D
RS232 interface fault
Host computer hardware or software fault
The actual communication specifications (baud rate, code, configuration, etc.) do not match the communication parameter settings.
[Measures to Take]
Check the host computer hardware or software.
Replace the FRP board, or change communication to another channel by modifying communication parameters, and reconnect the communication connector on the RPP board to the other channel position.
Check the following parameters to verify whether the actual communication connection matches the parameter settings:
Channel of RS232C interface being used
Data parity
Number of stop bits
Transmission code specification
End code
Baud rate
[Related Specifications]
DNC-B
4204 DNC-B message format error
Eeoelale6053
Error occurred in received message of protocol A.
This alarm occurs when unexpected message is sent to the host computer.
[Code]
None-> Message exceeds 72 bytes (NC program exceeds 4000 bytes).
XXXXYZ-> Error in data designated by [SET] command.
XXXX: Error data number expressed in hexadecimal (numerical data)
YY: Byte position within the data
[Probable Faulty Locations]
Hardware or software fault in host computer, or text format differs from DNC-B specification version.
[Measures to Take]
Check the set data according to the upper/lower limits of the text format specified by the DNC-B specification version.
[Related Specifications]
DNC-B
4214 RS232C communication abnormal
Eeoelale6054 During RS232C communication, data is in not-ready status.
[Code]
1-> Data is in not-ready status.
2-> Carriage return code was not detected.
[Probable Faulty Locations]
Host computer is not turned on.
RS232C interface or cable fault.
[Measures to Take]
Check the host computer power supply and communication cable.
If the RS232C is defective, replace the FRP board or change communication to another channel by changing the communication parameter setting (and reconnect the communication connector on the RPP board to the other channel position).
[Related Specifications]
DNC-B, C
4215 Communication buffer overflow
Eeoelale6055 Data overflow detected in the buffer when creating (formatting) data blocks for transmission during communication.
Data overflow occurred in the RS232C reception buffer or in the buffer used to analyze received data blocks or control commands.
[Code]
LC37-003 P-361
SECTION 7 ALARM D
1-> RS232C reception buffer data overflow
2-> Received data and command analyzer data overflow
3-> Transmission data buffer data overflow
[Probable Faulty Locations]
RS232C interface
[Measures to Take]
Replace the FRP board, or change communication to another channel by modifying communication parameters (and reconnect the communication connector on the RPP board to the other channel position).
[Related Specifications]
DNC-B, C
4216 Communication protocol no response
Eeoelale6056 Transmission from the remote station was interrupted during communication.
[Code]
XXYY (hexadecimal)
XX:
1-> When calling ENQ in phase 2 (sending station), no response after RC1+1 requests within TM1 time (sec).
2-> When sending text in phase 3 (sending station), no response after RC1+1 requests within TM1 time (sec).
3-> When sending TTD in phase 3 (sending station), no response after RC1+1 requests within TM1 time (sec).
4-> When waiting to receive text in phase 3 (receiving station), no response within TM2 time (sec).
5-> After sending WACK in phase 3 (receiving station), no response within TM2 time (sec).
6-> In phase 4 (receiving station), no response within TM2 time (sec) while waiting to receive EOT.
7-> In phase 3 (receiving station), text reception stopped for TM2 time (sec).
8-> In phase 3 (sending station), when sending TTD, final RC8+1 responses to ENQ, ACK, and WACK.
YY:
Bit 5-> RS232C framing error
Bit 4-> RS232C overrun error
Bit 3-> RS232C parity error
Because YY relates to RS232C errors, if the related parameter bit is set to 1 when no response is received, they will be ignored as an unnecessary request for response.
* Diagnostic times TM1 to TM9 and retry counts RC1 to RC8 can be changed by corresponding communication parameters.
Diagnostic time Description Application
TM1 3 No-response judgment time Send
TM2 15 Command wait time after response Receive
TM3 0 Transmission wait time after receiving WACK Send
TM4 10 TTD transmission wait time after receiving ACK Send
TM5 2 WACK transmission wait time after receiving select character or text Receive
TM6 0 Transmission wait time after receiving response NAK to select character Send
TM7 2 NAK transmission wait time after receiving select character Receive
TM8 3 Wait time between sent character blocks during text reception Receive
TM9 5 Time set to prevent overlap of characters sent from non-periodic stations in channel Send/Receive
Retry count Description Application
RC1 7 Number of times to request ENQ transmission when no response is received. Send
RC2 35 Number of times to send ENQ signal as response after receiving WACK. Send
RC3 7 Number of times to send NAK signal after receiving TTD. Receive
RC4 7 Number of times to resend select characters when overlap occurs between select characters. Send/Receive
RC5 7 Number of times to send NAK signal when abnormal text is received. Receive
LC37-003 P-362
SECTION 7 ALARM D
RC6 7 Number of times to send ENQ or text when NAK signal is received. Send
RC7 Number of times to send response request when reception is discontinuous. Receive
RC8 7 Number of times to send ENQ after transmitting TTD, or receiving ACK, WACK. Send
* The diagnostic times and retry counts in the table above are initial setting values.
* Diagnostic times and retry counts can be set by corresponding parameters. The diagnostic times should be set to satisfy the following conditions:
TM3 < TM1, TM5 < TM1, TM6 < TM1, TM7 < TM1. TM9 > TM1, TM2 > TM4
[Probable Faulty Locations]
Computer hardware or software fault
RS232C interface fault on NC side
The actual communication specifications (baud rate, code, configuration, etc.) do not match the communication parameter settings.
Operation example:
There is no operation related to this type in the CNC.
[Measures to Take]
Check the host computer hardware or software.
Replace the FRP board, or change communication to another channel by modifying communication parameters, and reconnect the communication connector on the RPP board to the other channel position.
Check the following parameters to verify whether the actual communication connection matches the parameter settings:
Channel of RS232C interface being used
Data parity
Number of stop bits
Transmission code specifications
Baud rate
Use of WACK/TTD control
Transparent mode valid/invalid
[Related Specifications]
DNC-C
4217 Communication protocol NAK/WACK reception
Eeoelale6057 During communication, NAK or WACK signals were received more times than the specified count.
[Code]
1-> In Phase 2 (transmitting station), NAK signal was received RC6+1 times consecutively
2-> In Phase 2 (transmitting station), WACK signal was received RC2+1 times consecutively
3-> In Phase 3 (transmitting station), NAK signal was received RC6+1 times consecutively
4-> In Phase 3 (transmitting station), WACK signal was received RC2+1 times consecutively
[Probable Fault Cause]
The "receive busy" status on the host computer side has not been cleared, or the text sent from the CNC was not received correctly.
[Measures]
Check the cause of the "receive busy" status on the host computer, or test whether data can be received correctly. Then set NC optional parameter (bit) No.11 bit 3 to "1" to reset
communication.
Check the cause why the host computer is in busy status or cannot receive correctly.
Then, set "1" in the parameter to reset communication.
(Optional parameter bit No.11 bit 3)
(Optional parameter bit No.29 bit 3)
[Related Specifications]
DNC-C
4218 Communication protocol Abnormal character reception
Eeoelale6058 During communication, the receiving station received character(s) with error RC5+1 times consecutively.
[Code]
YY: (Hexadecimal):
Bit 5->RS232C "Framing" error
Bit 4->RS232C "Time out" error
Bit 3->RS232C "Parity" error
LC37-003 P-363
SECTION 7 ALARM-D
Bit 2->Format error
Bit 1->BCC error
Bit 0->Transmission mode error
[Probable Fault Cause]
RS232C interface fault
Host computer hardware or software fault
Actual communication specifications (baud rate, code, configuration, etc.) do not match the communication parameter settings.
Operation example:
No operation related to this type in the CNC.
[Measures]
Check the host computer hardware or software.
Replace the FRP board, or change communication to another channel by modifying communication parameters. Accordingly, reconnect the communication connector on the board to the other channel position.
Check the following parameters and confirm whether the actual communication connection matches the parameter settings:
Channel of RS232C interface being used
Data parity
Number of stop bits
Transmission code specifications
Baud rate
Use of WACK/TTD control
Transparent mode valid/invalid
[Related Specifications]
DNC-C
4219 Communication protocol ENQ reception
Eeoelale6059 During communication, ENQ was received more times than the specified count.
[Code]
1-> In Phase 2 (transmitting station), interfered by ENQ signal RC4+1 times consecutively.
2-> In Phase 3 (receiving station), responded to ENQ signal RC7 times consecutively (Not generated on this system).
3-> In Phase 4 (receiving station), responded to ENQ signal RC7 times consecutively (Not generated on this system).
[Probable Fault Cause]
RS232C interface fault
Host computer hardware or software fault
Actual communication specifications (baud rate, code, configuration, etc.) do not match the communication parameter settings.
[Measures]
Check the host computer hardware or software.
Replace the FRP board, or change communication to another channel by modifying communication parameters; at the same time, reconnect the communication connector connected to the RPP board to the other channel position.
Check the following parameters and confirm whether the actual communication connection matches the parameter settings:
Channel of RS232C interface being used
Data parity
Number of stop bits
Transmission code specifications
Baud rate
Use of WACK/TTD control
Transparent mode valid/invalid
[Related Specifications]
DNC-C
LC37-003 P-364
SECTION 7 ALARM-D
4220 Communication protocol Abnormal EOT
Eeoelale6060 During communication, communication alarm EOT indicating parity error detection was received.
[Code]
1-> Error during reception in Phase 2 (transmitting station)
2-> Error during reception in Phase 3 (transmitting station)
3-> Error during reception in Phase 3 (receiving station)
[Probable Fault Cause]
RS232C interface fault
Host computer hardware or software fault
Actual communication specifications (baud rate, code, configuration, etc.) do not match the communication parameter settings.
[Measures]
Check the host computer hardware or software.
Replace the FRP board, or change communication to another channel by modifying communication parameters; at the same time, reconnect the communication connector connected to the RPP board to the other channel position.
Check the following parameters and confirm whether the actual communication connection matches the parameter settings:
Channel of RS232C interface being used
Data parity
Number of stop bits
Transmission code specifications
Baud rate
Use of WACK/TTD control
Transparent mode valid/invalid
[Related Specifications]
DNC-C
4221 Communication protocol TTD reception
Eeoelale6061 During communication, TTD signal was received RC3+1 times consecutively.
[Probable Fault Cause]
RS232C interface fault
Host computer hardware or software fault
Actual communication specifications (baud rate, code, configuration, etc.) do not match the communication parameter settings.
[Measures]
Check the host computer hardware or software.
Replace the FRP board, or change communication to another channel by modifying communication parameters; at the same time, reconnect the communication connector connected to the RPP board to the other channel position.
Check the following parameters and confirm whether the actual communication connection matches the parameter settings:
Channel of RS232C interface being used
Data parity
Number of stop bits
Transmission code specifications
Baud rate
Use of WACK/TTD control
Transparent mode valid/invalid
[Related Specifications]
DNC-C
4223 Motor ready
Eeoelale6062 Before the axis drive motor completed start preparation (several seconds are required after power-on or alarm A reset), a feed axis or spindle start command was issued.
[Code]
XY
LC37-003 P-365
SECTION 7 ALARM-D
X: VAC spindle motor
1-> 1st spindle (L-spindle)
2-> 2nd spindle (R-spindle, sub-spindle)
3-> 3rd spindle (VAC MA-spindle)
4-> 4th spindle (VAC MB-spindle)
Y: VAC axis number
1-> 1st axis (ZA)
2-> 2nd axis (XA)
3-> 3rd axis (ZB)
4-> 4th axis (XB)
5-> 5th axis
6-> 6th axis
7-> 7th axis
8-> 8th axis
9-> 9th axis
A-> 10th axis
[Probable Fault Cause]
Feed axis or spindle start command was issued too early after power-on or alarm A reset.
Motor drive unit cannot transmit operation ready signal to NC.
Wiring error
Motor drive unit failure
[Measures]
Issue the feed axis or spindle start command several seconds after power-on or alarm A reset.
Check whether the axis drive unit outputs the operation ready signal to the CNC correctly; if not, check the wiring between the motor and drive unit.
4225 Pitch error compensation data internal calculation
Eeoelale6063 In simple pitch error compensation, the number of compensation points is not between 1 and 299 due to data setting errors such as compensation interval or stroke limit position.
[Probable Fault Cause]
Data setting error in compensation interval, stroke limit position, etc.
4226 MSB load error
Eeoelale6064 A ***.MSB file cannot be loaded normally.
[Code]
1-> No program end code
2-> Block overflow
3-> Insufficient memory capacity
4-> MSB file is too large
[Probable Fault Cause]
Program error (Code 1)
Program is too long (Codes 2 and 4)
Insufficient memory capacity (Code 3)
[Measures]
1-> Add RTS code at the end of the program.
2-> Total number of MSBs exceeds 128; delete unnecessary contents.
3-> Expand RAM memory capacity.
4-> Rewrite program within RAM memory capacity.
4230 Torque limit recovery
Eeoelale6065 In manual mode when the torque limit switch was turned on, the input signal from torque limit was turned off.
[Code]
1-> ZA-axis
2-> XA-axis
3-> ZB-axis
4-> XB-axis
LC37-003 P-366
SECTION 7 ALARM-D
4232 Backup data read/write error
Eeoelale6066 Machining parameter file cannot be loaded or copied.
[Code]
1-> Alarm occurred when opening file during parameter load.
2-> Alarm occurred when reading file during parameter load.
3-> Alarm occurred when opening file during backup operation.
4-> Alarm occurred when writing file during backup operation.
4237 Magazine operation panel communication error
Eeoelale6067 An error occurred during communication via RS232C interface between CNC and magazine operation panel.
4240 Tool life management No spare tool
Eeoelale6068
Because there is no spare tool remaining in the tool group, the spare tool cannot be automatically exchanged when tool life expires.
Auto index: When a tool reaches its tool life, the spare tool in the same tool group is automatically indexed.
[Object]
System
[Code]
Tool group number with no spare tool (Hexadecimal)
[Measures]
After replacing a tool in a tool group having no spare tool, the tool life management data must be initialized.
Procedure: Select the tool data setting mode, press the function key [ITEM] several times until the screen displays the "TOOL LIFE MANAGEMENT" page, press the function key [INITIALIZE], and
"INITIALIZE OK (Y/N)" appears at the bottom of the screen. Input "Y" and press the [WRITE] key (to cancel initialization, input "N" and press the [WRITE] key), then input the tool group number to be
initialized and press the [WRITE] key. To initialize all tool groups, input "0" and press the [WRITE] key.
4242 Parameter setting value error
Eeoelale6069 The setting value in the parameter setting the turret rotation range is greater than the number of tools on the turret specified in the parameter, or the setting value for range 1 is greater than that for range 2.
[Code]
1-> Error in setting value for turret A rotation range 1.
2-> Error in setting value for turret A rotation range 2.
3-> Error in setting value for turret B rotation range 1.
4-> Error in setting value for turret B rotation range 2.
4247 Specified main spindle max speed error
Eeoelale6070 The specified main spindle maximum speed (G50 S****) is zero. (G50 S0)
[Target]
System
[Code]
1
[Measures]
Re-specify the main spindle maximum speed (G50 S****).
4248 DNC NC receive start condition
Eeoelale6071
A code was transmitted from the host computer before the NC was ready to receive data.
[Code]
1-> Transmission from the host computer to the NC was ready when the machine was not in the synchronized mode.
2-> A code was transmitted from the host computer to the NC while the machine was in warm-up cycle.
3-> Transmission from the host computer to the NC was ready immediately after power-on while the NC was reading MSB or a part program.
4-> Transmission from the host computer to the NC was ready after block sequence number search was completed.
5-> Transmission from the host computer to the NC was ready while the machine was executing a schedule program.
6-> Transmission from the host computer to the NC was ready while the machine was executing a part program.
LC37-003 P-367
SECTION 7 ALARM D
7-> Transmission from the host computer to the NC was ready while the machine was in an alarm state.
8-> Transmission from the host computer to the NC was ready while the machine was in a mode other than automatic mode.
[Measures]
Perform preparations before transmitting the send ready command from the host computer.
Prepare the lathe/NC so it is not in the states indicated by the codes above.
4249 Tool life advance notice
Eeoelale6072 When counting tool life by workpiece count, only 1 usable tool remains in a tool group.
[Code]
Tool group number (hexadecimal)
[Related Specifications]
Tool life management
4251 Axis feedrate limited
Eeoelale6073 The feedrate of an axis was clamped to 2 m/min because it exceeded the limit value of 2 m/min.
[Code]
Axis code data bit for which feedrate is limited to 2 m/min: Hexadecimal, up to 2 digits.
Bit 0 – ZA-axis : Bit 4 – ZB-axis
Bit 1 – XA-axis : Bit 5 – XB-axis
Bit 2 – CA-axis : Bit 6 – CB-axis
Bit 3 – WA-axis : Bit 7 – WB-axis
Example
1B -> Feedrates of ZA, XA, WA, and ZB axes are limited.
20 -> Feedrate of XB-axis is limited.
1 -> Feedrate of ZA-axis is limited.
[Probable Fault Cause]
Programmed feedrate F is too large.
[Measures]
Reduce feedrate F in the program.
4258 Y-axis mode forced cancel
Eeoelale6074
On machines with slanted Y-axis specification, this alarm occurs when "bit 0" of NC optional parameter (bit) No. 56 is set to 1. When cancelling Y-axis mode, the Y-axis mode ON/OFF pushbutton can be used
without considering the position of the YS-axis.
[Parameter]
Optional parameter bit No. 56 bit 0
4261 Work counter overflow
Eeoelale6075 Actual work counter data has exceeded the set count value.
[Code]
1-> Work counter A alarm
2-> Work counter B alarm
3-> Work counter C alarm
4-> Work counter D alarm
[Probable Fault Cause]
Workpiece count
[Measures]
Set a count value smaller than the set value.
Set a set value larger than the count value.
Clear the set value to zero.
After taking any of the above measures, reset the NC.
[Related Specifications]
NC work counter
LC37-003 P-368
SECTION 7 ALARM D
4267 PLC link error
Eeoelale6076 Error occurred in master PC during PLC link.
[Code]
X
1-> Master PC stop
2-> Master PC error
3-> Master communication error
4-> Master data link not shared
5-> Master offset illegal
6-> Master receive buffer insufficient
7-> Master receive buffer excess
[Probable Fault Cause]
Master PC fault
[Measures]
Check the master PC.
4268 PLC communication error
Eeoelale6077 An error occurred during RS232C data communication with the PLC.
[Code]
WXYYZZ
W=1: During initialization:
X=0 (YY: During channel transmission)
ZZ: During communication parameter setting
YY:
0-> Issued in a contracted channel
1-> Communication task initializing
2-> RS232C channel number error
3-> Requested channel not installed
4-> Identification information address error
5-> Standard function (read/punch) in use
6-> In use for other purpose
ZZ:
0-> Issued in a contracted channel
1-> Communication task initializing
2-> RS232C channel number error
3-> Requested channel not installed
4-> Identification information address error
5-> Standard function (read/punch) in use
6-> In use for other purpose
7-> Communication parameter error
W=2: During transmission
X=1-> Communication task initializing
2-> RS232C channel number error
3-> Requested channel not installed
4-> Identification information address error
5-> In use for other purpose
6-> Transmission error
YYZZ:
Bit 0-> Not ready (DSR signal error)
Bit 1-> RS232C device transmission not opened
Bit 2-> Transmission data was not written to work buffer within the preset time.
Bit 3-> Forced end interrupted management
W=3: During reception
X=1-> Communication task initializing
2-> RS232C channel number error
3-> Requested channel not installed
4-> Identification information address error
5-> In use for other purpose
6-> Transmission error
YYZZ:
Bit 0-> Parity error
Bit 1-> Overrun error
Bit 2-> Framing error
LC37-003 P-369
SECTION 7 ALARM D
Bit 3-> Not ready (DSR signal error)
Bit 4-> RS232C device reception not opened
Bit 5-> Receive work buffer overflow
Bit 6-> No data in receive work buffer
Bit 7-> Forced end interrupted management
[Probable Fault Cause]
For timeout errors, RS232C interface fault or broken cable.
NC command error
[Measures]
Check the PLC.
Check the NC command.
4269 Robot control
Eeoelale6078 The robot entered an alarm condition.
[Code]
XXYY
[Probable Fault Cause]
Robot entered alarm state during processing.
[Measures]
Release the alarm on the robot side.
[Related Specifications]
OKUMA robot
4281 Work counter overflow
Eeoelale6113 Current work counter data has exceeded the full count value.
[Code]
1-> Work counter A alarm
2-> Work counter B alarm
3-> Work counter C alarm
4-> Work counter D alarm
[Probable Fault Cause]
Workpiece quantity
[Measures]
Set count value smaller than set value.
Set set value larger than count value.
Clear set value to 0. Take any of the above measures, then reset NC.
[Related Specifications]
NC work counter
4283 ADP error
Eeoelale6154 An abnormality occurred on the TMP board, and the run check counter cannot increment.
[Index]
None
[Character-string]
None
[Code]
None
[Probable Fault Cause]
1) Defective TMP board